CN112131489A - Friend relationship management method, system, storage medium and electronic device - Google Patents

Friend relationship management method, system, storage medium and electronic device Download PDF

Info

Publication number
CN112131489A
CN112131489A CN202011044955.9A CN202011044955A CN112131489A CN 112131489 A CN112131489 A CN 112131489A CN 202011044955 A CN202011044955 A CN 202011044955A CN 112131489 A CN112131489 A CN 112131489A
Authority
CN
China
Prior art keywords
target
block
friend relationship
read
block chain
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202011044955.9A
Other languages
Chinese (zh)
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.)
Qingdao Haier Technology Co Ltd
Original Assignee
Qingdao Haier Technology 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 Qingdao Haier Technology Co Ltd filed Critical Qingdao Haier Technology Co Ltd
Priority to CN202011044955.9A priority Critical patent/CN112131489A/en
Publication of CN112131489A publication Critical patent/CN112131489A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/953—Querying, e.g. by the use of web search engines
    • G06F16/9536—Search customisation based on social or collaborative filtering
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
    • G06Q50/01—Social networking

Abstract

The invention discloses a friend relationship management method, a friend relationship management system, a storage medium and an electronic device. Wherein, the method comprises the following steps: acquiring a reading request sent by an application client, wherein the reading request is used for requesting to read a target friend relationship associated with a target user account, and the target friend relationship is a friend relationship stored in a block chain by the target user account according to a preset block data structure; verifying the reading certificate carried in the reading request; and under the condition that the read certificate passes the verification, the authorization application client side reads the target friend relationship in the block chain. The invention solves the technical problem of higher complexity of friend relationship management operation caused by the fact that friend relationships are stored in each application server.

Description

Friend relationship management method, system, storage medium and electronic device
Technical Field
The invention relates to the technical field of block chains, in particular to a friend relationship management method, a friend relationship management system, a friend relationship management storage medium and an electronic device.
Background
At present, in almost all applications with social attributes, friend relationship data of a user on each application usually independently exists in a server of each application, so that a client of each application respectively and independently manages each friend relationship, and the friend relationship data existing in the server of each application cannot be communicated. With the increase of the number of applications, the user needs to manage the friend relationship on the client of each application, which increases the management cost of the user.
That is, at present, servers of different applications cannot read other friend relationship data except for local friend relationship data. Correspondingly, clients of different applications cannot authorize the friend relationship managed by the clients to other applications for use. The user needs to re-establish the friend relationship among a plurality of clients of different applications, thereby causing the problem of higher complexity of friend relationship management operation.
In view of the above problems, no effective solution has been proposed.
Disclosure of Invention
Embodiments of the present invention provide a method, a system, a storage medium, and an electronic device for friend relationship management, so as to at least solve the technical problem of higher complexity of friend relationship management operations caused by friend relationships stored in application servers.
According to an aspect of the embodiments of the present invention, a method for managing a friend relationship is provided, including:
acquiring a reading request sent by an application client, wherein the reading request is used for requesting to read a target friend relationship associated with a target user account, and the target friend relationship is a friend relationship stored in a block chain by the target user account according to a preset block data structure; verifying the reading certificate carried in the reading request; and under the condition that the reading certificate passes the verification, authorizing the application client to read the target friend relationship in the block chain.
According to another aspect of the embodiments of the present invention, there is also provided a friend relationship management system, including: the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring a reading request sent by an application client, the reading request is used for requesting to read a target friend relationship associated with a target user account, and the target friend relationship is a friend relationship stored in a block chain by the target user account according to a preset block data structure; the verification module is used for verifying the reading certificate carried in the reading request; and the authorization module is used for authorizing the application client to read the target friend relationship in the block chain under the condition that the read certificate passes the verification.
According to still another aspect of the embodiments of the present invention, there is also provided a computer-readable storage medium, in which a computer program is stored, where the computer program is configured to execute the foregoing friend relationship management method when running.
According to another aspect of the embodiments of the present invention, there is also provided an electronic apparatus, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the method for friend relationship management through the computer program.
In the embodiment of the invention, a target user account stores a target friend relationship into a block chain according to a preset block data structure, and then a reading request sent by a client is applied to verify a reading certificate carried in the reading request; and under the condition that the reading certificate passes the verification, authorizing the application client to read the target friend relationship in the block chain. The target friend relationship is stored in a target block chain distributed for a target user account in the block chain, and is authorized for the application client through verifying and reading the certificate, so that the target friend relationship is separated from the application client and the terminal and is independently stored in the target block chain, the technical effects that the target friend relationship is managed only by the target user account and the friend relationship among the application clients is intercommunicated are achieved, and the technical problem that the friend relationship management operation complexity is high due to the fact that the friend relationship is stored in each application server is solved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:
fig. 1 is a flowchart illustrating an optional method for friend relationship management according to an embodiment of the present invention;
fig. 2 is an interaction timing diagram illustrating an alternative method for friend relationship management according to an embodiment of the present invention;
fig. 3 is a block data structure diagram of an alternative method for friend relationship management according to an embodiment of the present invention;
FIG. 4 is a schematic diagram illustrating an interaction timing sequence of an alternative method for friend relationship management according to an embodiment of the present invention;
fig. 5 is a flowchart illustrating an alternative method for friend relationship management according to an embodiment of the present invention;
fig. 6 is a schematic maintenance operation diagram of an optional friend relationship management method according to an embodiment of the present invention;
fig. 7 is a schematic diagram of a maintenance operation block structure of an optional friend relationship management method according to an embodiment of the present invention;
fig. 8 is a schematic structural diagram of an alternative buddy relationship management system according to an embodiment of the present invention;
fig. 9 is a schematic structural diagram of an alternative electronic device according to an embodiment of the invention.
Detailed Description
In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above 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 invention described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
According to an aspect of the embodiments of the present invention, a method for managing a buddy relationship is provided, and optionally, as an optional implementation manner, as shown in fig. 1, the method for managing a buddy relationship includes:
s102, a reading request sent by an application client is obtained, the reading request is used for requesting to read a target friend relationship associated with a target user account, and the target friend relationship is a friend relationship stored in a block chain by the target user account according to a preset block data structure;
s104, verifying the reading certificate carried in the reading request;
s106, under the condition that the read certificate is verified, the application client is authorized to read the target friend relationship in the block chain.
Optionally, the foregoing friend relationship management method may be applied to, but is not limited to, each application client that has an acquisition requirement for a user friend relationship. The application client can be but is not limited to a chat application client with social attributes, such as WeChat, QQ, Paibao. The obtaining requirement means that the application client needs to realize various application functions by using the loaded friend relationship of the user. In this embodiment, the friend relationship of the user is safely maintained by using the blockchain by combining the friend relationship of the user with the blockchain, so that different application clients can directly acquire the friend relationship of the user through interaction with the blockchain to apply to the respective application clients without re-establishing the friend relationship of the user in the respective application clients. Therefore, the purpose of simplifying the management operation of the friend relationship of the user is achieved, and the problem of more complex management operation in the related technology is further solved.
Optionally, in this embodiment, the target buddy relationship is stored in a third-party storage carrier independent of the application client, that is, a block chain. Here the blockchain may be, but is not limited to: the method has the characteristics of decentralization and confidentiality. Data stored on the blockchain network cannot be controlled by any single party, and private data can really be completely owned.
It should be noted that the above-mentioned blockchain refers to a blockchain system for storing friend relationships for users. The blockchain system allocates a target blockchain to each target user account for storing the target friend relationship of the target user account.
Optionally, in this embodiment, the target friend relationship may be, but is not limited to, a relationship that is established by the target user account and is capable of interacting with other user accounts. The method can be expressed that other user accounts are added into a communication list for the target user account so as to establish a friend account list capable of performing communication and interactive contact on an interactive interface of the application client. The user adds accounts of one or more other users to the list of friend accounts using the target user account to form the target friend relationship. The target user account is bound with the target friend relationship, the target user account can perform an update operation on the target friend relationship, and the update operation may include, but is not limited to: and continuously adding other user accounts into the target friend relationship, removing the user accounts in the target friend relationship to release the friend relationship, and changing the related information of the user accounts in the target friend relationship.
Optionally, the target user account may be, but is not limited to, an account used by the user to log in to a certain application client, or an account used in the blockchain independently of other application clients, that is, the target user account and the account used by the application client may have no association. It should be noted that: and the block chain allocates corresponding storage space for each target user account, and the storage spaces of different target user accounts are independent from each other and exist in the block chain. The target user account serves as a unique certificate of a storage space in which the target friend relationship is stored, and the user can only read the target friend relationship in the corresponding storage space by using the target user account to log in the blockchain, so that the storage safety of the target friend relationship and the independent management and storage characteristics of the target friend relationship independent of the application client and the terminal are guaranteed.
Optionally, in this embodiment, the read credential carried in the read request may be, but is not limited to, a key and a token used for reading data stored in a block chain. The read credential may be, but is not limited to, set to a public key in a secret key, and the blockchain is accordingly verified using a private key. And when the public key is matched with the private key, the read certificate is verified to be passed. Meanwhile, the public key is used as a reading certificate of the public key, and is updated based on algorithm change after preset time or use times, so that a new public key is generated, and the client is prevented from repeatedly using the same public key to initiate an acquisition request. Meanwhile, the update mechanism of the public key may be, but is not limited to: the method and the device perform automatic updating in effective time or effective times or combination of the effective time and the effective times, and avoid that the application client side relies on the same public key to initiate an acquisition request for a long time or too frequently, so that the acquisition of the target friend relationship by the application client side is limited.
Alternatively, the read credential may be, but is not limited to, set to a shared key in the key, and accordingly, the same shared key is used for authentication in the blockchain. And in the case that the shared key is consistent, the read certificate is considered to pass the verification. It should be noted that, although the symmetric shared key is updated at the same time, the read credential is received only when the application client requests to acquire the read credential, and therefore, the update of the shared key is mainly based on the shared key for authentication stored in the blockchain. The updating of the shared key can avoid that the application client side relies on the same shared key for a long time or multiple times to read the target friend relationship, and the shared key sets the valid times or the valid period or the limit of the valid times and the valid period together, thereby limiting the application client side to read the target friend relationship.
Alternatively, the read credential may be, but is not limited to, set as a token, and accordingly, the block chain is verified using a matching verification token. Optionally, the read credential is a token carrying a dynamic password, and the verification token stored in the blockchain may be a token capable of decrypting the dynamic password, or a token carrying the same dynamic password, which is not limited herein. Similarly, the dynamic password is configured with an update mechanism, which may be, but is not limited to: time-based, or a combination of both. The dynamic password updating mechanism realizes dynamic updating of the token, reduces the possibility that the block chain is maliciously accessed and attacked, and ensures that the storage of the target friend relationship is safer.
It should be noted that, no matter the read credential is any of the above embodiments, the read credential has a unique correspondence with the verification credential and the target friend relationship stored in the blockchain. And the block chain positions the target friend relationship according to the read certificate, verifies whether the read certificate is valid or not by utilizing the stored verification certificate, and authorizes the client to read the target friend relationship under the condition that the verification certificate passes verification.
That is, the security of the stored user's buddy relationship is guaranteed by means of the block chain's own security authentication mechanism. In addition, the user friend relations can be oriented and provided for the application client which passes the safety verification, so that the application client can run corresponding application functions by utilizing the user friend relations.
Optionally, in this embodiment, the verifying the read credential carried in the read request further includes verifying the read credential and the verification credential stored in the blockchain, checking whether the read credential matches the verification credential in the blockchain, and if the read credential matches the verification credential, determining that the read credential passes the verification. And in the case that the read certificate passes the verification, the blockchain is regarded as that the application client side is allowed to read the target friend relationship stored in the blockchain. And the block chain sends the relevant information of the read target friend relationship to the application client so as to authorize the application client to read the target friend relationship.
Optionally, the sending of the blockchain to the application client to read the relevant information of the target buddy relationship includes, but is not limited to: and the position of the target friend relationship is specifically stored, and the information of the block chain where the target friend relationship is located.
Optionally, the application client locates a specific location stored in the target friend relationship in the block chain according to the received related information for reading the target friend relationship, so as to read the target friend relationship.
According to the embodiment provided by the application, after the reading request sent by the application client is obtained, the reading certificate in the reading request is verified, and the stored target friend relationship is read from the block chain under the condition that the reading certificate passes the verification, so that the exclusive barrier of the friend relationship of the application client is broken, the friend relationship can be obtained through interaction with the block chain among different application clients, the management operation frequency and the time cost of the friend relationship of a user are saved, the purpose of simplifying the management operation of the friend relationship of the user is realized, and the problem of higher complexity of the management operation in the related technology is solved.
As an optional implementation, after verifying the read credential carried in the read request, the method further includes, in case that the read credential fails to be verified, broadcasting a message that the read credential fails to be verified to the rights management end and the application client, where the rights management end is configured to generate the read credential; in the event that the application client receives the message, it is determined that the application client is not allowed to read the target buddy relationship in the blockchain.
The rights management end may be, but is not limited to: a third party independent of the blockchain and the application client is used for the client of the blockchain authority management and a module for the authority management in the blockchain system. The authority management terminal is used for managing various operation authorities of the block chain.
Optionally, the right management end is further configured to generate a read authentication credential, send the read authentication credential to the block chain, where the block chain stores the read authentication credential, and is used to authenticate the read credential in the read request when the application client initiates the read request. Alternatively, the read authentication credential may be, but is not limited to: key, token. The read authentication credential is an encryption scheme corresponding to the read credential.
Optionally, before the obtaining the read request of the application client, the method further includes: the method comprises the steps that an application client sends a reading authority obtaining request for reading a target friend relationship to an authority management end, the authority management end generates a reading certificate corresponding to the target friend relationship after receiving the reading authority obtaining request of the application client, the reading certificate is sent to the application client, and the application client sends the reading request containing the reading certificate to a block chain after receiving the reading certificate.
Optionally, after the permission management end receives the read permission obtaining request of the application client, when generating the read certificate corresponding to the target friend relationship, the read verification certificate corresponding to the read certificate is generated at the same time, and the read verification certificate is sent to the block chain for verifying the read certificate, so that the application client is prevented from reading the target friend relationship by means of the expired or invalid read certificate.
According to the above alternative embodiment of the read credential, the read credential has a validity period to ensure the security of the target friend relationship stored in the target block chain. The reading certificate is invalid after the validity period passes, the application client side does not verify the invalid reading certificate under the condition that the application client side carries the invalid reading certificate in the reading request, and the block chain broadcasts a message that the reading certificate does not verify to the application client side and the authority management side. And the application client determines that the reading request is rejected when receiving the message that the verification certificate does not pass. After the reading request fails, if the application client still needs to read the target friend relationship, the application client needs to initiate a reading permission obtaining request to the permission management end again to obtain an effective reading certificate.
Optionally, the right management end is used as a generation end for reading the credential and the read authentication credential, and when receiving the read credential invalidation message, the right management end regenerates the read authentication credential corresponding to the target friend relationship and sends the read authentication credential to the block chain, so as to update the read authentication credential. The read authentication voucher is updated to solve the problem that the read authentication voucher fails due to the fact that the read authentication voucher is effective. And simultaneously, when the next application client side initiates a reading permission obtaining request, sending the reading certificate corresponding to the updated reading verification certificate to the application client side, so that the application client side carries the effective reading certificate and is authorized to read the target friend relationship.
For example, specifically referring to the following example, in a scenario where the application client applies for the target buddy relationship saved in the blockchain from the blockchain, the interaction scenario and timing sequence of the application client, the authority management terminal, and the blockchain may be, but are not limited to, as shown in fig. 2. The application client 202 executes step S201 to send a read permission acquisition request to the permission management terminal 204, when the application client 202 executes step S201 to send the read permission acquisition request, the read permission acquisition request includes target user account information associated with a target friend relationship to be read, the permission management terminal 204 receives the read permission acquisition request in step S201, and executes step S203 to generate a read credential and a read authentication credential according to the target user account information included therein. After completing step S203, the rights management end 204 executes step S205 to send the read credential to the application client 202, and executes step S207 to send the read verification credential to the blockchain 206. The application client 202 receives the read credential included in step S205, adds the read credential to the read request, and then executes step S209 to initiate the read request to the blockchain 206. After receiving the read request, the blockchain 206 performs step S211 to verify the read credential, where verifying the read credential includes performing matching check on the read credential included in the read request and the read verification credential stored in the blockchain 206, and if the read credential is matched with the read verification credential, the read credential passes verification, otherwise, the read credential does not pass verification. After obtaining the verification result of step S211, the blockchain 206 performs step S213 to send the verification result to the application client 202, where the verification result is to authorize reading or reject reading.
In the embodiment of the application, under the condition that the read certificate fails to pass the verification, the blockchain announces that the read request of the application client is rejected by broadcasting the message that the verification fails to pass to the application client and the authority management terminal, and simultaneously informs the authority management terminal of the message that the read certificate fails, so that the authority management terminal can regenerate an effective read certificate conveniently, dynamic management of the read certificate is realized, and meanwhile, the information closed loop of dynamic update of the read certificate is achieved. The dynamic updating mechanism for reading the certificate avoids malicious access and attack to the blockchain system with the target friend relationship, and further ensures the storage safety of the target friend relationship.
As an optional implementation, before the obtaining the read request sent by the application client, the method further includes:
s1, acquiring a target friend relationship associated with the target user account;
s2, saving the target friend relationship to the block of the target block of the block chain according to the preset block data structure.
Before the authorization application client reads the friend relationship of the target user, the user needs to log in the block chain by using the account of the target user, and the target friend relationship of the account relationship of the target user is stored in the block chain. The block chain allocates a special block for the target user account to store the friend relationship, and the target user account needs to write the target friend relationship into the block according to a preset block data structure. The predetermined block data structure can be shown in fig. 3, where each block includes a block number, header information, and a block body, and each block has a unique block number, and the block number is used as an identifier for distinguishing the block from other blocks in the block chain.
The data structure of each block can be divided into two parts, including but not limited to header information and a block body. The header information includes, but is not limited to: version information for representing a communication protocol, a hash value of a previous tile linked to the tile, a root hash of the tile, a workload proof difficulty target, a timestamp, a random number. The block is linked with the previous block by writing the hash value of the previous block into the header information, and the next block is linked with the current block by writing the root hash value of the current block into the header information, so that a plurality of blocks are linked into a single-chain-shaped block chain with an arrangement sequence, and all blocks in the block chain can be calculated by the block at the last tail end position of the block chain.
The block may be, but not limited to, used to store specific friend relationships, including, but not limited to, the number of records of friend relationships in the block and specific records of friend relationships. Specific records include, but are not limited to: the method comprises the steps of a friend relation initiator, a friend relation target, a friend relation state, friend relation recording time, a hash value recorded in the previous state and a hash of the record. A plurality of friend relationships can be recorded in the block body of a single block. In the specific record of each friend relationship, the hash value written in the previous state record is linked with the previous friend relationship, and the written-in friend relationship is linked with the friend relationship by writing the state hash value of the friend relationship in the specific record. The ordering of friend relationships in the same block may be, but is not limited to: time sequence. Therefore, a single chain-shaped recording chain with sequence is formed by the friend relationships in the same block, and the specific records of all the friend relationships recorded in the block can be calculated through the specific record of the last friend relationship in the block.
In the embodiment of the application, the block data structure in the block chain is designed for friend relationship storage, the friend relationship is stored in the block of the block, the friend relationship is stored in the block chain, the user can manage the friend relationship in the block chain by using the target user account, and the operation complexity of the user on friend relationship management is simplified.
As an optional implementation scheme, before the obtaining of the target friend relationship associated with the target user account, the method further includes:
s1, obtaining a saving instruction for requesting to save the target friend relationship in the block chain;
s2, responding to the saving instruction, and allocating a target block chain for the target user account in the block chain;
and S3, receiving and storing a reading verification certificate and a maintenance verification certificate which are generated by the authority management terminal according to the storage instruction, wherein the reading verification certificate is used for verifying the reading certificate, and the maintenance verification certificate is used for verifying the maintenance certificate by the user.
In this embodiment, when a user first uses a target user account to request for saving a friend relationship in a block chain, the block chain receives a saving instruction sent by the target user account, and determines that the target user account is a first initiation saving request through the saving instruction, that is, a friend relationship associated with the target user account does not exist in the block chain, and the block chain is a dedicated target block chain allocated to the target user account and simultaneously establishes a target block for the target block chain, so as to store the friend relationship in the saving instruction. And the block chain sends the block number of the target block to the target user account as a storage address of the initial friend relationship of the target user account. Therefore, the friend relationship of the target user account is stored in the block chain.
For example, in combination with the specific embodiment, in a scenario where a target user account initiates a request for saving a target friend relationship in a blockchain for the first time, as shown in fig. 4, the target user account 402 performs step S401 to send a saving instruction to the blockchain 404, after the blockchain 404 receives the saving instruction, the blockchain adds information of the target user account 402 to an authority granting request and performs step S403 to send the authority granting request to the authority management terminal 406, and after receiving the authority granting request, the authority management terminal 406 performs step S405 to generate a maintenance credential and a maintenance verification credential according to the information of the target user account 402 included in the authority granting request, where the maintenance credential and the maintenance verification credential are associated with the target account. After the right management terminal 406 finishes the step S405, the step S407 is executed to send the maintenance verification credential to the block chain 404, and then the block chain 406 executes the step S409 to send the maintenance credential to the target user account 402, so that the target user account 402 obtains the maintenance credential capable of performing the maintenance operation on the target friend relationship.
Optionally, in this embodiment, the maintenance credential and the maintenance verification credential may be, but are not limited to: key, token. The secret key may be but is not limited to a shared secret key, a public key and a private key, and the token may be but is not limited to a token carrying a dynamic password or a symmetric password or the same password.
In the embodiment of the application, when a user uses a target user account for the first time to apply for storing the friend relationship in the block chain, a maintenance certificate and a maintenance verification certificate corresponding to the target user account are generated through the authority management terminal, and the maintenance certificate and the maintenance verification certificate are added as verification means for maintaining the target friend relationship, so that the maintenance misoperation of the target friend relationship caused by singly using the target user account as an identifier for operating the target friend relationship is avoided, the maintenance operation authority of the target user account for the target friend relationship is further ensured, and meanwhile, the safety of the target friend relationship in the block chain is also ensured.
As an optional implementation, as shown in fig. 5, the storing the target buddy relationship into the blockchain according to the preset blockchain data structure further includes:
s502, obtaining a maintenance request of a target user account for a target friend relationship, wherein the maintenance request comprises a maintenance certificate;
s504, under the condition that the maintenance voucher passes the verification, a block is newly added in the target block chain to store the maintenance operation information contained in the maintenance request, wherein the starting block of the target block chain is the target block;
s506, the newly added block is linked with the end position block on the target block chain.
Optionally, in this embodiment, when the user uses the target user account to save the target friend relationship for the first time, the blockchain allocates a target block to the target user account, and the target user account saves the target friend relationship in a block of the target block. The target block is used as a first block for storing the target friend relationship by the target user account, and the target friend relationship at the moment is the initial friend relationship. The number of the friend relations included in the initial friend relation is recorded in a block, and the specific friend relation is linked with the previous friend relation by using the hash value of the previous state record in the record, so that the initial friend relation of the target user account is stored in the target block.
Optionally, in this embodiment, the target user account may maintain the friend relationship stored in the target zone. When the target user account has a maintenance requirement, the target user account sends a maintenance request carrying a maintenance certificate to a block chain, the block chain checks the maintenance certificate with a maintenance verification certificate stored by the block chain, if the maintenance certificate is matched with the maintenance verification certificate, the maintenance certificate passes verification, the block chain establishes a newly added block in the target block chain, the newly added block is used for storing information contained in the maintenance operation of the target user account on the target friend relationship, the newly added block is linked with a target block chain end position block, the target friend relationship stored in the target block chain is updated, and at the moment, the newly added block is updated to be the target block chain end position block. The maintenance of the target friend relationship by the target user account can only be operated by adding a block in the target block chain, and the target user account cannot change or delete the existing block in the target block chain, namely the block from the target block to the current terminal position, so that the misoperation of the target user account is avoided, the integrity and the safety of friend relationship storage are further ensured, and the operation complexity of a user on friend relationship management is simplified.
The maintenance operation may include, but is not limited to, at least one of: addition, deletion, modification. And the target user account writes specific friend relationship operation in the block body of the newly added block so as to store the maintenance operation information to update the target friend relationship.
For example, as shown in fig. 6, the current target block chain 600 includes a target block 602 with a block number of 1 at the start position and an end position block 604 with a block number of N at the end position, and there are N-2 blocks (not shown in the figure) linked in sequence between the target block 602 and the end position block 604, where N is a positive integer greater than or equal to 2. The end position block 604 writes the root hash value Hsah of the previous block in its header informationN-1Linked with the previous block to become the current end position block 604 of the target block chain 600. Specifically, the target block 602 serves as a starting position block and stores an initial friend relationship of the account of the target user, specifically, a friend account a, a friend account B, and a friend account C are recorded in an account list of the initial friend relationship recorded in the block of the target block, and a friend account X is added to the account list specifically recorded in the block of the end position block 604. Currently, a target user account application is set to remove the friend account B in the account list of the target friend relationship recorded in the target block chain 600, that is, delete the friend account B from the account list. When the verification certificate provided by the blockchain to the target user account passes, the blockchain system is newAdding a new block 606 with the block number N +1, writing in the block of the new block 606 to remove the friend account B from the target friend relationship, namely deleting the specific record of the friend account B, including the recording time and other information, and writing in the header information of the new block 606 to the Hash value of the end position block 604 of the current target block chain 600NThe newly added block 606 is linked with the end position block 604, and the friend account B is moved out of the account list of the target friend relationship by recording the maintenance operation information in the newly added block 606, that is, by removing the friend account B from the account list of the target friend relationship. The updated target block chain 600 is obtained through the maintenance operation, and at this time, the end position block 604 with the block number N becomes the nth block 608, and the newly added block 606 with the block number N +1 becomes the end position block 604 in the updated target block chain 600. This maintenance operation is thus completed, resulting in an updated target block chain 600.
In the embodiment of the application, each time the target user account maintains the target friend relationship, a block is newly added in the target block chain, and the operation is recorded in the newly added block, that is, the target user account cannot change the block existing in the target block chain, so that misoperation of the target user account is avoided, the problems of block invalidation and block waste caused by misoperation are avoided, and the storage security of the target friend relationship stored in the target block chain is further ensured by ensuring that the existing block in the target block chain cannot be changed.
As an alternative implementation, the linking the newly added block with the end position block on the target block chain includes: and linking the block head of the newly added block with the block head of the tail end position block on the target block chain.
In this embodiment, the newly added block records the root Hash value of the end position block of the current target block chain in its header information, as shown in fig. 6, the newly added block 606 hashes the root Hash value of the end position block 604, i.e. the block with block number NNWriting the header information to realize the newly added block 606 and the end position block 604, and thus updates the target block chain 600 to get the latest target block chain 600. At this time, the newly added block 606 with the block number N +1 is updated to the latest end position block 604 in the target block chain 600. All blocks are linked in sequence by writing the header information of each block into the root hash value of the previous block, and the target friend relationship stored in the whole target block chain 600 can be obtained through the link relationship between the blocks by only obtaining the block number of the block 604 at the end position of the current target block chain by the target user account.
In the embodiment of the application, the newly-added block is linked with the end position block through the information in the block header, so that the maintenance operation of the target friend relationship stored in the target block chain is realized. Meanwhile, the link relation and the sequence of the blocks are determined through the hash value of the header information, all the blocks in the target block chain can be calculated through the end position block, the target friend relation is further obtained, the reading and maintaining operation of the target friend relation is simplified, and therefore the management complexity of a user on the target friend relation is simplified.
As an optional scheme, the step of the authorization application client reading the target friend relationship in the blockchain includes:
and sending the reading token to the application client so that the application client can obtain all blocks contained in the target block chain according to the block number of the terminal position block contained in the reading token and a block chain algorithm, and reading the target friend relationship in the existing target block chain.
It should be noted that, when the read credential passes the verification, the block chain sends the read token with the block number of the block at the end position of the target block chain to the application client, and the application client receives the block number of the block at the end position of the target block chain, deduces all current blocks in the target block chain according to a block chain algorithm, and obtains the target friend relationship in the current state from the blocks of all the blocks.
In the embodiment of the application, the block chain sends the read token containing the block number of the terminal position block to the application client, and the application client can deduce to obtain all blocks in the target block chain, so as to read the target friend relationship stored in the target block chain, thereby simplifying the complexity of reading the token and the complexity of reading the friend relationship by the application client.
Optionally, in this embodiment, after the deriving and acquiring the target friend relationship by the application client, the method further includes:
and the application client stores the target friend relationship into a target storage address of the application client.
After the target friend relationship is deduced, the application client can store the deduced target friend relationship in a storage space of the application client, so that the target friend relationship becomes the friend relationship which can be applied by the application client. However, it should be noted that the read request of the application client only has the read and save permission, and does not have the permission to perform the maintenance operation on the target friend relationship. Optionally, the application client may read the target friend relationship at regular time, so as to store the latest target friend relationship in its own storage space, so as to update the target friend relationship of the application client. Optionally, the application client may perform editing and maintenance operations on the friend relationship stored in its own storage space.
Optionally, the user uses the target user account to send a storage instruction to the blockchain, after receiving the storage instruction, the blockchain initiates an authority granting request to the authority management terminal, the authority granting request carries account information of the target user account, the authority management terminal generates a maintenance certificate and a maintenance verification certificate according to the account information of the target user account, and sends the maintenance certificate and the maintenance verification certificate to the target user account and the blockchain, respectively.
For example, as shown in fig. 7, at time T0, the blockchain will assign a target tile to the target user account after receiving the save instruction. In this embodiment, the block number of the target block may be set to 1001, and the Hash value Hash of the block is written in the header information of the block with the block number of 10011The hash value of the previous block is empty, indicating that the block is the starting block of the target block chain. Then, in the blockIn this embodiment, a friend account a, a friend account B, a friend account C, and a friend account D are in an account list of the initial friend relationship of the target user account, and the related information of the friend account a, the friend account B, the friend account C, and the friend account D is written into the block. Therefore, the specific record number of the target friend relationships recorded in the target block is 4.
At time T1, the target user account initiates a maintenance request to the blockchain, where the maintenance request may include, but is not limited to, a maintenance credential and maintenance operation information: and adding a friend account E in the friend account list. The block chain utilizes the maintenance verification certificate to verify the maintenance certificate, under the condition of matching the block chain and the maintenance certificate, a newly added block is established, the block number of the newly added block is 1003, and Hash is written in preblockHash of header information of the block with the block number of 10031Writing Hash in merkleRoot3Indicating that block 1003 is linked to block 1001. A specific record of adding the friend account E is written in the block body of the block 1003. Therefore, the block 1003 becomes the end position block of the target block chain, and the account list of the target friend relationship is updated to the friend account a, the friend account B, the friend account C, the friend account D, and the friend account E.
At a time T2 after the time T1, the target user account initiates a maintenance request to the blockchain, and the specific maintenance operation is: and deleting the friend account B and modifying the friend account A into a friend account G. According to the steps, a block chain establishes a newly added block, the block number of the newly added block is 1006, and Hash is written in preblockHash written in the header information of the block with the block number of 10063Indicating that block 1006 is linked to block 1003, write Hash in merkleRoot6The hash table is used for recording the root hash value of the newly added block. A delete friend account B and a modify friend account a are sequentially written in the block of block 1006 as a friend account G, and meanwhile, a specific state hash value of the delete friend account B is written in a preStateHash in a specific record of the modify friend account a as the friend account G, so as to indicate the sequence of the two specific records. Whereby the blockchain 1006 is updated to the end position in the target blockchainAnd in the block, the account list of the target friend relationship is updated to a friend account G, a friend account C, a friend account D and a friend account E.
At some time T3 after time T2, assuming the target user account did not initiate a maintenance request at times T2 through T3, the application client M1 initiates a read request for the target buddy relationship. The application client M1 sends a read permission acquisition request to the permission management end, and the permission management end generates a public key and sends the public key to the application client M1, and sends a corresponding private key to the block chain. The application client M1 sends a read request carrying a public key to the blockchain, the blockchain performs matching verification on the public key according to the private key, and adds the block number of the end position block in the target blockchain, that is, the block 1006 in the read token and sends the block number to the application client under the condition that the public key is matched and valid. The application client locates the block with the block number 1006, and deduces whether the friend account existing in the account list of the current target friend relationship is a friend account G, a friend account C, a friend account D, or a friend account E according to the link relationship among the blocks. The application client M1 saves the derived target friend relationship in the storage space of the application client M1 to achieve its social purpose with the friend relationship.
It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present invention is not limited by the order of acts, as some steps may occur in other orders or concurrently in accordance with the invention. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required by the invention.
According to another aspect of the embodiments of the present invention, a friend relationship management system for implementing the friend relationship management method is further provided. As shown in fig. 8, the system includes:
an obtaining module 802, configured to obtain a read request sent by an application client, where the read request is used to request to read a target friend relationship associated with a target user account, and the target friend relationship is a friend relationship that the target user account stores in a blockchain according to a preset block data structure;
a verification module 804, configured to verify a read credential carried in the read request;
and an authorization module 806, configured to authorize the application client to read the target friend relationship in the blockchain if the read credential passes the verification.
According to the embodiment provided by the application, after the acquisition module acquires the reading request sent by the application client, the reading certificate in the reading request is verified through the verification module, and under the condition that the reading certificate is verified, the authorization module authorizes the application client to read the stored target friend relationship from the block chain, so that the exclusive barrier of the friend relationship of the application client is broken, the friend relationship can be acquired through interaction with the block chain among different application clients, the management operation times and time cost of a user on the friend relationship are saved, the purpose of simplifying the management operation of the friend relationship of the user is achieved, and the problem of high complexity of the management operation in the related technology is solved.
According to a further aspect of an embodiment of the present invention, there is also provided a computer-readable storage medium having a computer program stored thereon, wherein the computer program is arranged to perform the steps of any of the above method embodiments when executed.
Alternatively, in the present embodiment, the above-mentioned computer-readable storage medium may be configured to store a computer program for executing the steps of:
s1, a reading request sent by the application client is obtained, the reading request is used for requesting to read a target friend relationship associated with the target user account, and the target friend relationship is a friend relationship stored in a block chain by the target user account according to a preset block data structure;
s2, verifying the reading certificate carried in the reading request;
and S3, under the condition that the read certificate passes the verification, the application client is authorized to read the target friend relationship in the block chain.
Alternatively, in this embodiment, a person skilled in the art may understand that all or part of the steps in the methods of the foregoing embodiments may be implemented by a program instructing hardware associated with the terminal device, where the program may be stored in a computer-readable storage medium, and the storage medium may include: flash disks, Read-Only memories (ROMs), Random Access Memories (RAMs), magnetic or optical disks, and the like.
According to another aspect of the embodiments of the present invention, there is also provided an electronic apparatus for implementing the foregoing buddy relationship management method, as shown in fig. 9, the electronic apparatus includes a memory 902 and a processor 904, where the memory 902 stores a computer program, and the processor 904 is configured to execute the steps in any one of the foregoing method embodiments through the computer program.
Optionally, in this embodiment, the electronic apparatus may be located in at least one network device of a plurality of network devices of a computer network.
Optionally, in this embodiment, the processor may be configured to execute the following steps by a computer program:
s1, a reading request sent by the application client is obtained, the reading request is used for requesting to read a target friend relationship associated with the target user account, and the target friend relationship is a friend relationship stored in a block chain by the target user account according to a preset block data structure;
s2, verifying the reading certificate carried in the reading request;
and S3, under the condition that the read certificate passes the verification, the application client is authorized to read the target friend relationship in the block chain.
Alternatively, it can be understood by those skilled in the art that the structure shown in fig. 9 is only an illustration, and the electronic device may also be a terminal device such as a smart phone (e.g., an Android phone, an iOS phone, etc.), a tablet computer, a palm computer, a Mobile Internet Device (MID), a PAD, and the like. Fig. 9 is a diagram illustrating a structure of the electronic device. For example, the electronic device may also include more or fewer components (e.g., network interfaces, etc.) than shown in FIG. 9, or have a different configuration than shown in FIG. 9.
The memory 902 may be configured to store software programs and modules, such as program instructions and modules corresponding to the friend relationship management method and apparatus in the embodiments of the present invention, and the processor 804 executes various functional applications and data processing by operating the software programs and modules stored in the memory 902, that is, implements the friend relationship management method. The memory 902 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 902 may further include memory located remotely from the processor 904, which may be connected to the terminal over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof. The storage 902 may be specifically, but not limited to, used for storing information such as sample characteristics of the item and the target virtual resource account number. As an example, as shown in fig. 9, the aforementioned storage 902 may include, but is not limited to, an obtaining module 802, a verifying module 804 and an authorizing module 806 in the aforementioned buddy relationship management system. In addition, the friend relationship management system may further include, but is not limited to, other module units in the friend relationship management system, which is not described in this example again.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
The integrated unit in the above embodiments, if implemented in the form of a software functional unit and sold or used as a separate product, may be stored in the above computer-readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing one or more computer devices (which may be personal computers, servers, network devices, etc.) to execute all or part of the steps of the method according to the embodiments of the present invention.
In the above embodiments of the present invention, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
In the several embodiments provided in the present application, it should be understood that the disclosed client may be implemented in other manners. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one type of division of logical functions, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, units or modules, and may be in an electrical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The foregoing is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.

Claims (11)

1. A friend relationship management method is characterized in that,
the method comprises the steps of obtaining a reading request sent by an application client, wherein the reading request is used for requesting to read a target friend relationship associated with a target user account, and the target friend relationship is a friend relationship stored in a block chain by the target user account according to a preset block data structure;
verifying the reading certificate carried in the reading request;
and if the read certificate passes the verification, authorizing the application client to read the target friend relationship in the block chain.
2. The method according to claim 1, further comprising, before the obtaining the read request sent by the application client:
acquiring the target friend relationship associated with the target user account;
and storing the target friend relationship into a block body of a target block of the block chain according to a preset block data structure.
3. The method of claim 2, wherein the storing the target buddy relationship in a blockchain according to a preset blockchain data structure further comprises:
obtaining a maintenance request of the target user account for the target friend relationship, wherein the maintenance request comprises a maintenance certificate;
under the condition that the maintenance voucher passes verification, adding a block in a target block chain to store maintenance operation information contained in the maintenance request, wherein the starting block of the target block chain is the target block;
and linking the newly added block with a terminal position block on the target block chain.
4. The method of claim 3, wherein the linking the newly added block with the end position block on the target block chain comprises:
and linking the block head of the newly added block with the block head of the terminal position block on the target block chain.
5. The method of claim 4, wherein authorizing the application client to read the target buddy relationship in the blockchain comprises:
sending a reading token to the application client, so that the application client obtains all blocks contained in the target block chain according to the block numbers of the end position blocks contained in the reading token and the block chain algorithm, and reads the target friend relationship stored in the target block chain.
6. The method of claim 5, after the application client reads the target buddy relationship, further comprising:
and the application client stores the target friend relationship into a target storage address of the application client.
7. The method of claim 3, further comprising, before obtaining the target friend relationship associated with the target user account:
obtaining a saving instruction for requesting to save the target friend relationship in the block chain;
responding to the saving instruction, and distributing the target block chain for the target user account in the block chain;
and receiving and storing a reading verification certificate and a maintenance verification certificate which are generated by the authority management terminal according to the storage instruction, wherein the reading verification certificate is used for verifying the reading certificate, and the maintenance verification certificate is used for verifying the maintenance certificate.
8. The method of claim 7, further comprising, after the verifying the read credential carried in the read request:
under the condition that the read certificate is not verified, broadcasting a message that the read certificate is not verified to the authority management terminal and the application client, wherein the authority management terminal is used for generating the read certificate; determining that the application client is not allowed to read the target buddy relationship in the blockchain if the application client receives the message.
9. A buddy relationship management system, comprising:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring a reading request sent by an application client, the reading request is used for requesting to read a target friend relationship associated with a target user account, and the target friend relationship is a friend relationship stored in a block chain by the target user account according to a preset block data structure;
the verification module is used for verifying the reading certificate carried in the reading request;
and the authorization module is used for authorizing the application client to read the target friend relationship in the block chain under the condition that the read certificate passes verification.
10. A computer-readable storage medium, comprising a stored program, wherein the program when executed performs the method of any one of claims 1 to 8.
11. An electronic device comprising a memory and a processor, characterized in that the memory has stored therein a computer program, the processor being arranged to execute the method of any of claims 1 to 8 by means of the computer program.
CN202011044955.9A 2020-09-28 2020-09-28 Friend relationship management method, system, storage medium and electronic device Pending CN112131489A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011044955.9A CN112131489A (en) 2020-09-28 2020-09-28 Friend relationship management method, system, storage medium and electronic device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011044955.9A CN112131489A (en) 2020-09-28 2020-09-28 Friend relationship management method, system, storage medium and electronic device

Publications (1)

Publication Number Publication Date
CN112131489A true CN112131489A (en) 2020-12-25

Family

ID=73844415

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011044955.9A Pending CN112131489A (en) 2020-09-28 2020-09-28 Friend relationship management method, system, storage medium and electronic device

Country Status (1)

Country Link
CN (1) CN112131489A (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107579817A (en) * 2017-09-12 2018-01-12 广州广电运通金融电子股份有限公司 User ID authentication method, apparatus and system based on block chain
CN107579958A (en) * 2017-08-15 2018-01-12 中国联合网络通信集团有限公司 Data managing method, apparatus and system
CN110598386A (en) * 2019-09-27 2019-12-20 腾讯科技（深圳）有限公司 Data processing method, device and equipment based on block chain and storage medium
CN110837598A (en) * 2019-11-11 2020-02-25 腾讯科技（深圳）有限公司 Information recommendation method, device, equipment and storage medium
CN110941672A (en) * 2019-11-21 2020-03-31 腾讯科技（深圳）有限公司 Household registration management method, device, equipment and storage medium
US20200169407A1 (en) * 2019-07-31 2020-05-28 Alibaba Group Holding Limited Blockchain-based data authorization method and apparatus

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107579958A (en) * 2017-08-15 2018-01-12 中国联合网络通信集团有限公司 Data managing method, apparatus and system
CN107579817A (en) * 2017-09-12 2018-01-12 广州广电运通金融电子股份有限公司 User ID authentication method, apparatus and system based on block chain
US20200169407A1 (en) * 2019-07-31 2020-05-28 Alibaba Group Holding Limited Blockchain-based data authorization method and apparatus
CN110598386A (en) * 2019-09-27 2019-12-20 腾讯科技（深圳）有限公司 Data processing method, device and equipment based on block chain and storage medium
CN110837598A (en) * 2019-11-11 2020-02-25 腾讯科技（深圳）有限公司 Information recommendation method, device, equipment and storage medium
CN110941672A (en) * 2019-11-21 2020-03-31 腾讯科技（深圳）有限公司 Household registration management method, device, equipment and storage medium

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
曾凡太: "物联网之雾 基于雾计算的智能硬件快速反应与安全控制", 机械工业出版社, pages: 131 - 133 *

Similar Documents

Publication Publication Date Title
US11115418B2 (en) Registration and authorization method device and system
RU2620998C2 (en) Method and authentication device for unlocking administrative rights
CN107579958B (en) Data management method, device and system
CN110177124B (en) Identity authentication method based on block chain and related equipment
CN112673600B (en) Multiple security authentication system and method between mobile phone terminal and internet of things (IoT) device based on blockchain
CN112671720B (en) Token construction method, device and equipment for cloud platform resource access control
EP3777022B1 (en) Distributed access control
EP1836543A1 (en) Method and system for access control and data protection in digital memories, related digital memory and computer program product therefor
CN111654372B (en) Key management method and related device
US11050560B2 (en) Secure reusable access tokens
CN105635082A (en) Dynamic authorization method and system, authorization center, and authorization client
CN112948842A (en) Authentication method and related equipment
JP2021090151A (en) Storage system and data protection method thereof
CN105183402A (en) Data storage method
CN110334531A (en) Management method, host node, system, storage medium and the device of virtual machine key
CN111988262B (en) Authentication method, authentication device, server and storage medium
KR102501004B1 (en) Method and apparatus for managing data based on blockchain
CN108390892B (en) Control method and device for security access of remote storage system
CN114157470B (en) Token management method and device
CN112131489A (en) Friend relationship management method, system, storage medium and electronic device
CN109284622B (en) Contact information processing method and device and storage medium
CN115396209A (en) Access authorization method and device, electronic equipment and readable storage medium
KR20220162609A (en) Module and method for authenticating data transfer between a storage device and a host device
CN110958211B (en) Data processing system and method based on block chain
CN113438082A (en) Database access method, device, equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination