Information sharing method and device, equipment and storage medium

Abstract

The embodiment of the invention provides an information sharing method and device, equipment and a storage medium, and the method comprises the steps: monitoring an information change event on a first block chain where a monitoring node is located according to the monitoring node on at least one first block chain; wherein the information change event comprises an information addition sub-event, an information modification sub-event aiming at the existing information and an information deletion sub-event aiming at the existing information; when the information change event is monitored, obtaining a change parameter corresponding to the information change event from a target first block chain generating the information change event; the change parameter comprises a change type and change information; the change type comprises addition, modification and deletion; uploading the change parameter to a second block chain; wherein the first block chain corresponds to the first object; the second block chain corresponds to a second object; the first object and the second object have an affiliation relationship.

Description

Technical Field

[0001] The present disclosure relates to the field of data processing technology, and in particular to an information sharing method, device, equipment and storage medium. Background Art

[0002] For a group company with many subsidiaries, it is usually necessary to uniformly manage the customer resources of the group company and its subsidiaries. Although the subsidiaries and the group company share the same customer management system, they each have independent customer information and need to use refined permissions to manage these customer resources. A unified system is needed to integrate and manage customer data while ensuring the security and compliance of customer data.

[0003] At present, due to the problems of inconsistent customer information and information specifications in the customer systems of different subsidiaries, in order to complete customer sharing, the subsidiary customer system needs to call the shared customer system interface to upload shared customer information. The operation is relatively cumbersome and is prone to problems such as untimely sharing and shared customer information not meeting specifications. Summary of the invention

[0004] The embodiments of the present disclosure provide an information sharing method, apparatus, device and storage medium to solve the problems in the related technology that different subsidiaries have their own customer systems with inconsistent customer information and inconsistent information specifications, which results in the need for subsidiaries to share customers and call the shared customer system interface to upload shared customer information. The operation is cumbersome and is prone to problems such as untimely sharing and shared customer information not meeting specifications.

[0005] In a first aspect, an embodiment of the present disclosure provides an information sharing method, the method comprising: According to at least one listening node on the first blockchain, monitoring the information change event on the first blockchain where the listening node is located; wherein the information change event includes an information addition sub-event, an information modification sub-event for existing information, and an information deletion sub-event for existing information; When an information change event is monitored, the change parameters corresponding to the information change event are obtained from the target first blockchain that generates the information change event; the change parameters include the change type and the change information; the change type includes addition, modification, and deletion; The changed parameters are uploaded to a second blockchain; wherein the first blockchain corresponds to a first object; the second blockchain corresponds to a second object; and the first object and the second object have a subordinate relationship.

[0006] In a second aspect, an embodiment of the present disclosure provides an information sharing device, the device comprising: A monitoring module, configured to monitor, according to at least one monitoring node on the first blockchain, information change events on the first blockchain where the monitoring node is located; wherein the information change event includes an information addition sub-event, an information modification sub-event for existing information, and an information deletion sub-event for existing information; An acquisition module, configured to acquire, when an information change event is monitored, change parameters corresponding to the information change event from the target first blockchain generating the information change event; the change parameters include a change type and change information; the change type includes addition, modification, and deletion; An uploading module is used to upload the changed parameters to a second blockchain; wherein the first blockchain corresponds to a first object; the second blockchain corresponds to a second object; and there is a subordinate relationship between the first object and the second object.

[0007] In a third aspect, an embodiment of the present disclosure provides an information sharing device, comprising: a processor; and a memory configured to store computer-executable instructions, wherein the computer-executable instructions, when executed, enable the processor to implement the steps of the method described in the first aspect above.

[0008] In a fourth aspect, an embodiment of the present disclosure provides a computer-readable storage medium, wherein the computer-readable storage medium is used to store computer-executable instructions, and the computer-executable instructions implement the steps of the method described in the first aspect when executed by a processor.

[0009] In a fifth aspect, an embodiment of the present disclosure provides a computer program product, wherein the computer program product includes a computer program, and when the computer program is executed by a processor, the steps of the method described in the first aspect are implemented.

[0010] At least one of the above technical solutions provided by the embodiments of the present invention can achieve the following technical effects: In an embodiment of the present invention, the information change event on the first blockchain where the listening node is located can be monitored according to the listening node on at least one first blockchain; wherein the information change event may include an information addition sub-event, an information modification sub-event for existing information, and an information deletion sub-event for existing information. When the information change event is monitored, the change parameters corresponding to the information change event can be obtained from the target first blockchain that generates the information change event, wherein the change parameters may include a change type and change information, and the change type may include addition, modification, and deletion, and then the change parameters may be uploaded to the second blockchain, wherein the first blockchain corresponds to the first object, and the second blockchain corresponds to the second object, and the first object and the second object may have a subordinate relationship.

[0011] As can be seen from the above-mentioned embodiments of the invention, the embodiments of the present invention can determine whether an information change event occurs on the first blockchain where the listening node is located, that is, whether the information on the first blockchain where the listening node is located has changed, through the listening node on the first blockchain, and when the information change event is listened to, that is, when the information change is listened to, the change parameters corresponding to the information change event are obtained, that is, which data has been changed and how these data have been changed specifically, and then the obtained change parameters can be uploaded to the second blockchain. Since the second object corresponding to the second blockchain has a subordinate relationship with the first object corresponding to the first blockchain, after uploading the obtained change parameters to the second blockchain, the information change occurring in the first blockchain where the information change event is located can be known by the second object, that is, it can be shared with the second object. Since the automatic and rapid sharing of information changes can be realized, it can effectively solve the problems in the related technology that the customer systems owned by different subsidiaries have inconsistent customer information and inconsistent information specifications, resulting in the need to call the shared customer system interface to upload shared customer information, which is cumbersome to operate and prone to problems such as untimely sharing and non-compliance of shared customer information with specifications. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] In order to more clearly illustrate one or more embodiments of the present disclosure or the technical solutions in the prior art, the drawings required for use in the embodiments or the prior art descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present disclosure. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative labor. Figure 1 One of the flow charts of the information sharing method provided by one embodiment of the present invention; Figure 2 A second flowchart of an information sharing method provided by an embodiment of the present invention; Figure 3 A third flowchart of an information sharing method provided by an embodiment of the present invention; Figure 4 A schematic diagram of the module composition of an information sharing device 400 provided in one embodiment of the present invention; Figure 5 A schematic diagram of the hardware structure of an information sharing device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0013] In order to make the technical parties in this technical field better understand the technical aspects of one or more embodiments of the present disclosure, and to make the purpose, technical solutions and advantages of the present invention clearer, the technical solutions of the present invention will be clearly and completely described below in combination with the specific embodiments of the present invention and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0014] The technical solutions provided by various embodiments of the present invention are described in detail below in conjunction with the accompanying drawings.

[0015] See also Figure 1 , Figure 1 One of the flow charts of the information sharing method provided by one embodiment of the present invention is as follows: Figure 1 As shown, the method comprises the following steps: Step 102: According to at least one listening node on the first blockchain, information change events on the first blockchain where the listening node is located are monitored; wherein the information change event includes an information addition sub-event, an information modification sub-event for existing information, and an information deletion sub-event for existing information.

[0016] Step 104: When an information change event is monitored, obtain change parameters corresponding to the information change event from the target first blockchain that generates the information change event; the change parameters include the change type and the change information; the change type includes addition, modification, and deletion.

[0017] Step 106: Upload the changed parameters to the second blockchain; wherein the first blockchain corresponds to the first object; the second blockchain corresponds to the second object; and there is a subordinate relationship between the first object and the second object.

[0018] In an embodiment of the present invention, a monitoring node may be provided on the first blockchain. Through at least one monitoring node provided on the first blockchain, information change events on the first blockchain where the monitoring node is located may be monitored.

[0019] In one embodiment, the information change event may include an information addition sub-event, an information modification sub-event for existing information, and an information deletion sub-event for existing information.

[0020] In the embodiment of the present invention, the change information corresponding to the information change event may be user information.

[0021] In one embodiment of the present invention, when monitoring the information change event on the first blockchain where the monitoring node is located, the information change event of the target information on the first blockchain where the monitoring node is located can be monitored. The information identifier of the target information is unique on the first blockchain where the target information is located. The information identifier of the target information can be determined based on the identity information in the target information, and the identity information includes at least one of the following: name, certificate type, and certificate number.

[0022] In one example, when the change information corresponding to the information change event is user information, the information identifier of the above-mentioned target information can be used to identify the user corresponding to the user information, and the information identifier of the target information is unique on the first blockchain where the target information is located. Correspondingly, the user corresponding to the user information identified by it is unique on the first blockchain, that is, the user information of the same user on the first blockchain can only correspond to the user, and the user information corresponding to the same user also has only one and the same information identifier.

[0023] In one example, when the first blockchain changes information, it can only change the information with unique information identification. In order to ensure the uniqueness of the information identification, this example can calculate the identity information in the information stored in the first blockchain through a preset algorithm, such as the keccak256 digest algorithm, to obtain a unique information identification for each stored information, such as a token ID.

[0024] In one example, when information needs to be changed, the first blockchain can determine the information identifier corresponding to the information that needs to be changed based on the identity information of the information that needs to be changed, and then determine whether there is an information identifier that is the same as the information identifier in the information identifiers of each stored information in the first blockchain based on the information identifier. If there is an identical information identifier, the first blockchain can obtain the change type corresponding to the changed information, wherein the change type can be determined based on the change type identifier passed in by the user or application of the changed information when changing the information. If the acquired change type is addition, the first blockchain will refuse service, that is, it will refuse the information change; if the acquired change type is modification or deletion, the information will be changed according to the change type; if there is no identical information identifier, if the change type is addition, the first blockchain will call the pre-set file creation contract to pass in the corresponding data; if the change type is modification or deletion, the first blockchain will refuse service and return an error message.

[0025] In an embodiment of the present invention, the change parameters corresponding to the information change event may include, in addition to the change type and change information, the blockchain identifier of the target first blockchain where the information change event corresponding to the change parameter is located, and the information identifier of the target information corresponding to the change parameter.

[0026] In this solution, when obtaining the change parameters corresponding to the information change event from the target first blockchain that generates the information change event, the change parameters corresponding to the information change event can be obtained through the message contract event generated by the information change event on the target first blockchain. When the information change event triggers the generation of a message contract event, the change parameters corresponding to the information change event can be passed into the message contract event, and the message contract event can be generated according to a pre-set contract event template after being triggered by the information change event.

[0027] In an embodiment of the present invention, the first blockchain can pre-set a contract event template, for example, setting the existing ERC721 contract template as a contract event template. When an information change event occurs, that is, when the information is changed, a message contract event can be triggered on the first blockchain, and the change parameters corresponding to the information change event can also be passed into the message contract event at this time, and the message contract event is generated according to the pre-set contract event template.

[0028] In one example, when the change type corresponding to the change parameter is addition or deletion, the information identifier of the change information and the change type can be passed into the message contract to generate a corresponding message contract event; when the change type corresponding to the change parameter is modification, the information identifier of the change information, the change type, and the change information can be passed into the message contract to generate a corresponding message contract event.

[0029] In an embodiment of the present invention, after obtaining the change parameters corresponding to the information change event from the target first blockchain where the information change event is generated, the change parameters can be uploaded to the second blockchain.

[0030] In the embodiment of the present invention, after monitoring the information change event, the information identifier, operation type, change information, and blockchain identifier of the first blockchain where the change information is located corresponding to the information change event can be obtained. Then, the verification contract of the second blockchain can be called by routing to upload the above change parameters.

[0031] In one example, the monitoring message returned by the monitoring node on the first blockchain can be used to determine that the information change event has been monitored, and the above-mentioned change parameters can be obtained through the monitoring message.

[0032] In one embodiment of the present invention, when there is an information identifier that is the same as the information identifier of the target information corresponding to the change parameter in the information identifier set corresponding to the second blockchain, the change parameter can be uploaded to the second blockchain, wherein the information identifier set corresponding to the second blockchain can be determined based on the identity information in the information stored in the second blockchain.

[0033] In an embodiment of the present invention, the second blockchain may correspond to an information identification list, which may include information identifications of various information stored in the second blockchain. When the second blockchain obtains the change parameter, it may determine whether the corresponding information identification list contains the same information identification according to the information identification of the change information in the change parameter, and when it is determined that there is the same information identification, it may determine that the change information is information that can be shared with the second object according to the subordinate relationship between the second object corresponding to the second blockchain and the first object corresponding to the first blockchain. Among them, the first object may be subordinate to the second object.

[0034] In an embodiment of the present invention, when there is an information identifier that is the same as the information identifier of the target information corresponding to the change parameter in the information identifier set corresponding to the second blockchain, the change type of the change parameter can be obtained. When the change type is an increase, after uploading the change parameter to the second blockchain, when an information acquisition event triggered by the blockchain identifier extraction operation of the first blockchain on the second blockchain is detected, the designated information identifier corresponding to the information acquisition event and the blockchain identifier of the designated first blockchain can be obtained, wherein the information identifier set corresponding to the second blockchain includes each information identifier and the corresponding relationship between the blockchain identifier of the first blockchain where the information corresponding to each information identifier is located, and the blockchain identifier extraction operation of the first blockchain is triggered when the second blockchain adds the change information corresponding to the change parameter to the information identifier set corresponding to the second blockchain, and is used to extract the blockchain identifier of the first blockchain corresponding to the information identifier of the change information corresponding to the change parameter from the information identifier set. Then, according to the information reading event, the information corresponding to the designated information identifier is obtained from the first blockchain corresponding to the blockchain identifier of the designated first blockchain, and the information corresponding to the information identifier corresponding to the acquired information acquisition event is sent to the second blockchain, so that the second blockchain performs information merging on the information corresponding to the acquired designated information identifier.

[0035] The above embodiments of the present invention can be applied to monitoring facilities, which may include monitoring contracts deployed by each first blockchain, and monitoring tools such as wecross tools. The present invention is described in detail below: 1. The first blockchain In an embodiment of the present invention, the first blockchain may include a blockchain node for storing information, such as user information, and a monitoring node responsible for monitoring information change events.

[0036] In one example, the first object corresponding to the first blockchain may be each subsidiary under a group head office, in which case the first blockchain may be each subsidiary chain. In an embodiment of the present invention, each subsidiary chain may be deployed in each department and project within each subsidiary, and may be responsible for storing the private customer information of the subsidiary. The user or subsidiary customer management system may connect to the blockchain node of the subsidiary chain by using the administrator CA (Certificate Authority), and may maintain the information on the chain and manage the chain nodes by calling the customer information management contract. Other application systems may connect to each node through the user CA, and may call the customer information management contract to read or manage the subsidiary user information, and such customer information will not be synchronized to other subsidiary chains, nor will it be read by other subsidiaries.

[0037] 2. Monitoring tools In an embodiment of the present invention, the monitoring tool can be responsible for monitoring the contract events generated by the addition, modification, and deletion of the on-chain information in each first blockchain, actively reading the shared information after the on-chain event is triggered, and uploading the shared information to the second blockchain by calling the on-chain contract (addition, modification, deletion contract) in the second blockchain.

[0038] 3. Second blockchain In one example, the second object corresponding to the second blockchain can be a group company. The second blockchain can be deployed in the group company and can include nodes of each subsidiary chain. Shared information can be shared to each node under its jurisdiction. Group company users and group customer management systems can access customer information management and subsidiary chain node management through the administrator CA. Each subsidiary user and application system can manage customer information through the user CA.

[0039] When the same customers exist in each subsidiary chain, local automatic verification can be implemented, and cross-chain data access, modification, addition, merging, deletion and other operations on the remote shared chain can be realized in each subsidiary chain. Whether it is the information of the same user can be verified based on the information identifier.

[0040] See also Figure 2 , which can be a schematic diagram of an architecture of an embodiment of the present invention, wherein the first blockchain can be Figure 2 The second blockchain is the China Property Insurance customer sub-chain, the health insurance customer sub-chain, and the life insurance customer sub-chain. Figure 2 The group customer chain in Figure 2It can be seen that corresponding monitoring nodes can be set on each first blockchain, and the monitoring facilities can monitor whether information changes occur on the first blockchain through the monitoring nodes. In addition to the monitoring nodes, each first blockchain also has an information storage node, which can store the customer information of the corresponding business system and accept information access and information changes of the corresponding business system. The group customer chain can store the customer information of the group shared customer management system and accept information access and information changes of the group shared customer management system.

[0041] To implement the above architecture, you can perform the following construction operations: Deployment of the second blockchain: The fisco bcos 2.x version can be used to deploy the second blockchain. The CA certificate certified by the cryptographic bureau can be used as the root certificate for node generation group, and the setup script provided by fisco bcos is used to configure the pbft (Practical Byzantine Fault Tolerance) consensus mechanism to generate all the nodes required for the entire second blockchain, initialize all nodes into the second blockchain, and configure the certificates of each sub-institution that needs to be generated. After each node and the second blockchain are generated, the node program is distributed to different servers for deployment, the chain certificate private key is retained, and the node containing the institution certificate without the chain certificate private key is issued to the first object corresponding to each first blockchain. The first object can use the institution certificate private key to generate a node certificate. In addition, it is necessary to ensure that the number of nodes configured for each first blockchain is not less than 4 to ensure complete consensus between the nodes of each first object.

[0042] Deployment of the first blockchain: connect nodes through institutional certificates and add a new group (the first blockchain), and add nodes distributed to the organization to the group. Then, each subordinate node can generate a dedicated chain account through SDK (Software Development Kit), and users can access the chain and call the contract at the same time.

[0043] Build the first blockchain functional contract: inherit the ERC721 contract template to implement the information contract. As a data storage contract, the contract can store information elements and set up element attributes, including but not limited to customer information such as name, ID card, mobile phone number, email, etc., and implement the information destruction method. Then, build the parameter verification contract of the first blockchain. The contract should implement parameter verification, information addressing functions, and call the information management contract function, and can realize query, addition, modification, deletion and other functions as an information contract. Add a trigger message event method to the contract and pass the information to the method. These contracts can provide data operation entries for various applications and users to operate.

[0044] Build the second blockchain function contract: Build the contract on the second blockchain in the same way. The second blockchain contract can have certain differences in the content of stored information from the first blockchain contract to better meet the characteristics of shared information. When building the parameter verification contract of the second blockchain, the contract should implement the parameter verification function; receipt judgment function (if it is a new receipt call: call the information merging function to splice different first object information; call the information contract function to add); call the customer information addressing function, call the information contract function; the internal attribute of the corresponding relationship between the information identifier and the blockchain identifier of the first blockchain, which is used to store the information identifier transmitted by the first blockchain and record the blockchain identifier of the source first blockchain; realize information identifier comparison, second object attribute comparison; information merging function.

[0045] In addition, a second blockchain information reading contract can be built, which can address the corresponding user information based on the incoming information identifier or encrypted identity information and return it.

[0046] Cross-chain tool deployment: Build the wecross cross-chain tool, which can access the first blockchain and the second blockchain through certificates respectively, deploy the monitoring event contract on each first blockchain, and realize wecross's monitoring of each first blockchain.

[0047] Permission setting: The second object can connect to the node through the chain certificate, and by setting the permission for calling each functional contract on the second blockchain, only the second object customer has read permission, and cancels the write permission; the first object can connect to the node through the institutional certificate, and by setting the permission for calling each functional contract on the first blockchain, the corresponding first object has read and write permissions on the first blockchain.

[0048] Below Figure 3 As shown, taking the first blockchain as the subsidiary customer chain, the second blockchain as the group company shared customer chain, and the change information as customer information as an example, the sharing process of change information is introduced in detail by combining the first blockchain, the monitoring tool and the second blockchain: First, customer information is encrypted to ensure the security of customer information on the chain. The Group will use SM2 (EllipticCurve Public Key Cryptography Algorithm) to generate a pair of public and private keys, and distribute SM2 public keys to each application or user that needs to upload customer information.

[0049] When the subsidiary's users or applications need to operate customer information, such as adding, modifying, or deleting, they can first perform SM2 encryption on each customer attribute information locally using the distributed public key.

[0050] Then, the subsidiary customer chain can perform customer uniqueness authentication to ensure that there is only one customer on the chain. The external application or user calls the verification contract on the subsidiary customer chain and passes in the customer information encrypted by SM2 according to the parameter verification contract input format, and also passes in the add / modify / delete operation flag attribute. The parameter verification contract will verify the parameters. If the parameters that do not meet the specifications are verified, it will fail and return an error message; if the parameters meet the verification rules, the subsequent steps will be carried out. The parameter verification contract can calculate a unique token Id for the three elements of the customer's identity information (name, certificate type, and certificate number) through the keccak256 digest algorithm, and address it according to the token Id. If the same token Id can be found, the operation flag attribute is judged; if it is an increase, the service is denied and an error message is returned; if the same token Id is not found, and the operation is an increase, the file creation contract is called and the corresponding parameters are passed in; if it is a modification or deletion, an error message is returned.

[0051] The subsidiary customer chain changes the subsidiary customer information. If it is a modification or deletion operation, the corresponding customer data is read according to the tokenId. According to the operation identifier, the customer management contract is called again. The customer management contract will operate according to the passed parameters. If it is an addition, the new customer information will be minted; if it is a modification, the original customer information will be addressed and the new parameters will be overwritten; if it is a deletion, the original customer information will be addressed and the destruction method in the customer information contract will be called. When the customer management contract operation is completed, the message contract is called according to different types. If it is an addition or deletion, the token Id and the operation type are passed to the message contract; if it is a modification, the token Id, the operation type and the customer information are passed to the message contract at the same time.

[0052] The cross-chain tool makes cross-chain calls and transmits the information triggered by the subsidiary chain to the group shared chain. When the wecross tool listens to the triggered message, it can read the token ID, operation type, customer information and chain address of the triggering message in the message and call the verification contract of the group shared customer chain through routing to upload the shared customer to the chain.

[0053] The group shared customer chain can perform parameter verification to identify whether it is a shared customer, and extract and merge data to automatically identify group customers. After receiving the call, the parameter verification contract of the group shared customer chain obtains the uploaded token Id, operation type, customer information and source chain address, and then determines the operation type: If the operation type is add, compare the token ID with the internal token ID list. If there is a duplicate, it is determined that the customer exists in multiple subsidiaries and is a group-shared customer: Add the token Id passed in this time to the corresponding relationship between the compared token Id and the subsidiary chain, and take out the existing subsidiary chain address and the chain address of this time, trigger the event message, and pass in the customer information token Id and chain address information to be read. When the wecross tool listens to the message triggered by the group shared chain, it uses the token Id to call the customer information reading contract of different subsidiary customer chains according to the chain address, reads the customer information, adds a receipt mark, and calls back the parameter verification contract of the group shared chain. After the group shared chain parameter verification contract obtains the receipt message, it merges multiple customer information. After the merger is completed, call the customer management contract of the group shared chain and pass in the token Id and the newly added customer information.

[0054] If the operation type is modification, compare the token Id with the token Id list of the internal mapping attribute. If it exists, the customer is a group shared customer. Call the customer management contract and pass in the token Id and the changed customer information.

[0055] If the operation type is delete, compare the token Id with the token Id list of the internal mapping attribute. If it exists, it is determined to be a group shared customer. If there is only a single subsidiary customer chain address in the list, delete the corresponding relationship, call the customer management contract and pass the token Id and the operation type of deletion to the customer management contract; if there are multiple subsidiary customer chain addresses in the list, delete the subsidiary customer chain address passed in this time in the mapping relationship, and do no other processing.

[0056] Then, the customer information of the group shared customer chain is changed. The customer information that has passed the judgment process will perform data changes on the group shared chain in this step: if it is newly created, the new customer information will be minted; if it is modified, the original customer information will be addressed and the new parameters will be overwritten; if it is deleted, the original customer information will be addressed and the destruction method in the customer information contract will be called.

[0057] The steps for reading the group's shared customer device can be as follows: When the user or application of a subsidiary needs to read the shared customer / subsidiary private customer information, the three elements of customer information should be obtained first, and SM2 encryption or token Id should be used directly as a parameter to call the customer reading contract of the group's shared customer chain; if the three elements are encrypted, the customer reading contract uses the keccak256 digest algorithm to superimpose the three elements of the customer's identity information to calculate a unique token Id; if the token Id is directly passed in, no summary processing is performed. According to the token Id, the corresponding group shared customer information is addressed. If the corresponding customer is found, the customer information is read and returned; if the corresponding customer is not found, an error is returned. After the application system or user obtains the customer information, it must use the private key assigned by the group to decrypt it to obtain the real customer information.

[0058] In an embodiment of the present invention, the information change event on the first blockchain where the listening node is located can be monitored according to the listening node on at least one first blockchain; wherein the information change event may include an information addition sub-event, an information modification sub-event for existing information, and an information deletion sub-event for existing information. When the information change event is monitored, the change parameters corresponding to the information change event can be obtained from the target first blockchain that generates the information change event, wherein the change parameters may include a change type and change information, and the change type may include addition, modification, and deletion, and then the change parameters may be uploaded to the second blockchain, wherein the first blockchain corresponds to the first object, and the second blockchain corresponds to the second object, and the first object and the second object may have a subordinate relationship.

[0059] As can be seen from the above-mentioned embodiments of the invention, the embodiments of the present invention can determine whether an information change event occurs on the first blockchain where the listening node is located, that is, whether the information on the first blockchain where the listening node is located has changed, through the listening node on the first blockchain, and when the information change event is listened to, that is, when the information change is listened to, the change parameters corresponding to the information change event are obtained, that is, which data has been changed and how these data have been changed specifically, and then the obtained change parameters can be uploaded to the second blockchain. Since the second object corresponding to the second blockchain has a subordinate relationship with the first object corresponding to the first blockchain, after uploading the obtained change parameters to the second blockchain, the information change occurring in the first blockchain where the information change event is located can be known by the second object, that is, it can be shared with the second object. Since the automatic and rapid sharing of information changes can be realized, it can effectively solve the problems in the related technology that the customer systems owned by different subsidiaries have inconsistent customer information and inconsistent information specifications, resulting in the need to call the shared customer system interface to upload shared customer information, which is cumbersome to operate and prone to problems such as untimely sharing and non-compliance of shared customer information with specifications.

[0060] Corresponding to the above information sharing method, an embodiment of the present invention further provides an information sharing device, Figure 4 A schematic diagram of the module composition of the information sharing device 400 provided in an embodiment of the present invention is shown in FIG. Figure 4 As shown, the information sharing device 400 includes: A monitoring module 401 is used to monitor, according to at least one monitoring node on the first blockchain, information change events on the first blockchain where the monitoring node is located; wherein the information change event includes an information addition sub-event, an information modification sub-event for existing information, and an information deletion sub-event for existing information; The acquisition module 402 is used to acquire, when an information change event is monitored, change parameters corresponding to the information change event from the target first blockchain generating the information change event; the change parameters include the change type and the change information; the change type includes addition, modification, and deletion; The upload module 403 is used to upload the changed parameters to the second blockchain; wherein the first blockchain corresponds to the first object; the second blockchain corresponds to the second object; and there is a subordinate relationship between the first object and the second object.

[0061] Optionally, the monitoring module 401 is used to: Monitor the information change event of the target information on the first blockchain where the monitoring node is located; wherein the information identifier of the target information is unique on the first blockchain where the target information is located; the information identifier of the target information is determined according to the identity information in the target information, and the identity information includes at least one of the following: name, certificate type, and certificate number.

[0062] Optionally, the change parameter also includes the blockchain identifier of the target first blockchain where the information change event corresponding to the change parameter is located, and the information identifier of the target information corresponding to the change parameter.

[0063] Optionally, the obtaining module 402 is used to: The message contract event is triggered by the information change event on the target first blockchain to obtain the change parameters corresponding to the information change event; wherein, when the information change event triggers the generation of the message contract event, the change parameters corresponding to the information change event are passed into the message contract event; the message contract event is triggered by the information change event and generated according to a pre-set contract event template.

[0064] Optionally, the upload module 403 is used to: When there is an information identifier in the information identifier set corresponding to the second blockchain that is identical to the information identifier of the target information corresponding to the change parameter, the change parameter is uploaded to the second blockchain; wherein the information identifier set corresponding to the second blockchain is determined based on the identity information in the information stored in the second blockchain.

[0065] Optionally, when the change type of the change parameter is increase, the device further includes ( Figure 4 not shown): The detection module 404 is used to obtain the designated information identifier corresponding to the information acquisition event and the blockchain identifier of the designated first blockchain when an information acquisition event is detected on the second blockchain, which is triggered by the blockchain identifier extraction operation of the first blockchain; wherein the information identifier set corresponding to the second blockchain includes each information identifier and the corresponding relationship between the blockchain identifier of the first blockchain where the information corresponding to each information identifier is located; the blockchain identifier extraction operation of the first blockchain is triggered when the second blockchain adds the change information corresponding to the change parameter to the information identifier set corresponding to the second blockchain, and is used to extract the blockchain identifier of the first blockchain corresponding to the information identifier of the change information corresponding to the change parameter from the information identifier set; A reading module 405 is used to obtain information corresponding to the specified information identifier from the first blockchain corresponding to the blockchain identifier of the specified first blockchain according to the information reading event; The merging module 405 is used to send the information corresponding to the information identifier corresponding to the information acquisition event to the second blockchain, so that the second blockchain merges the information corresponding to the specified information identifier.

[0066] Optionally, the second acquisition module 703 is used to: In an embodiment of the present invention, the information change event on the first blockchain where the listening node is located can be monitored according to the listening node on at least one first blockchain; wherein the information change event may include an information addition sub-event, an information modification sub-event for existing information, and an information deletion sub-event for existing information. When the information change event is monitored, the change parameters corresponding to the information change event can be obtained from the target first blockchain that generates the information change event, wherein the change parameters may include a change type and change information, and the change type may include addition, modification, and deletion, and then the change parameters may be uploaded to the second blockchain, wherein the first blockchain corresponds to the first object, and the second blockchain corresponds to the second object, and the first object and the second object may have a subordinate relationship.

[0067] As can be seen from the above-mentioned embodiments of the invention, the embodiments of the present invention can determine whether an information change event occurs on the first blockchain where the listening node is located, that is, whether the information on the first blockchain where the listening node is located has changed, through the listening node on the first blockchain, and when the information change event is listened to, that is, when the information change is listened to, the change parameters corresponding to the information change event are obtained, that is, which data has been changed and how these data have been changed specifically, and then the obtained change parameters can be uploaded to the second blockchain. Since the second object corresponding to the second blockchain has a subordinate relationship with the first object corresponding to the first blockchain, after uploading the obtained change parameters to the second blockchain, the information change occurring in the first blockchain where the information change event is located can be known by the second object, that is, it can be shared with the second object. Since the automatic and rapid sharing of information changes can be realized, it can effectively solve the problems in the related technology that the customer systems owned by different subsidiaries have inconsistent customer information and inconsistent information specifications, resulting in the need to call the shared customer system interface to upload shared customer information, which is cumbersome to operate and prone to problems such as untimely sharing and non-compliance of shared customer information with specifications.

[0068] Corresponding to the above information sharing method, an embodiment of the present invention further provides an information sharing device, Figure 5 A schematic diagram of the hardware structure of an information sharing device provided by an embodiment of the present invention.

[0069] The information sharing device may be a terminal device or a server for sharing information provided in the above embodiments.

[0070] The information sharing device may have relatively large differences due to different configurations or performances, and may include one or more processors 501 and memory 502, and the memory 502 may store one or more storage applications or data. Among them, the memory 502 may be a short-term storage or a persistent storage. The application stored in the memory 502 may include one or more modules (not shown in the figure), and each module may include a series of computer executable instructions in the information sharing device. Furthermore, the processor 501 may be configured to communicate with the memory 502 and execute a series of computer executable instructions in the memory 502 on the information sharing device. The information sharing device may also include one or more power supplies 503, one or more wired or wireless network interfaces 504, one or more input and output interfaces 505, and one or more keyboards 506.

[0071] Specifically in this embodiment, the information sharing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer executable instructions in the information sharing device, and is configured to be executed by one or more processors.

[0072] In an embodiment of the present invention, the information change event on the first blockchain where the listening node is located can be monitored according to the listening node on at least one first blockchain; wherein the information change event may include an information addition sub-event, an information modification sub-event for existing information, and an information deletion sub-event for existing information. When the information change event is monitored, the change parameters corresponding to the information change event can be obtained from the target first blockchain that generates the information change event, wherein the change parameters may include a change type and change information, and the change type may include addition, modification, and deletion, and then the change parameters may be uploaded to the second blockchain, wherein the first blockchain corresponds to the first object, and the second blockchain corresponds to the second object, and the first object and the second object may have a subordinate relationship.

[0073] As can be seen from the above-mentioned embodiments of the invention, the embodiments of the present invention can determine whether an information change event occurs on the first blockchain where the listening node is located, that is, whether the information on the first blockchain where the listening node is located has changed, through the listening node on the first blockchain, and when the information change event is listened to, that is, when the information change is listened to, the change parameters corresponding to the information change event are obtained, that is, which data has been changed and how these data have been changed specifically, and then the obtained change parameters can be uploaded to the second blockchain. Since the second object corresponding to the second blockchain has a subordinate relationship with the first object corresponding to the first blockchain, after uploading the obtained change parameters to the second blockchain, the information change occurring in the first blockchain where the information change event is located can be known by the second object, that is, it can be shared with the second object. Since the automatic and rapid sharing of information changes can be realized, it can effectively solve the problems in the related technology that the customer systems owned by different subsidiaries have inconsistent customer information and inconsistent information specifications, resulting in the need to call the shared customer system interface to upload shared customer information, which is cumbersome to operate and prone to problems such as untimely sharing and non-compliance of shared customer information with specifications.

[0074] Another embodiment of the present disclosure further provides a computer-readable storage medium, wherein the computer-readable storage medium is used to store computer-executable instructions, and the computer-executable instructions implement the above process when executed by a processor.

[0075] The storage medium in the embodiment of the present disclosure can implement each process of the above-mentioned information sharing method embodiment and achieve the same effect and function, which will not be repeated here.

[0076] Another embodiment of the present disclosure further provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the above process is implemented.

[0077] The computer program product in the embodiment of the present disclosure can implement each process of the above-mentioned information sharing method embodiment and achieve the same effects and functions, which will not be repeated here.

[0078] In various embodiments of the present disclosure, the computer-readable storage medium includes a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0079] In the 1990s, it was very clear whether the improvement of a technology was hardware improvement (for example, improvement of the circuit structure of diodes, transistors, switches, etc.) or software improvement (improvement of the method flow). However, with the development of technology, many improvements of the method flow today can be regarded as direct improvements of the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that the improvement of a method flow cannot be implemented with a hardware entity module. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is such an integrated circuit whose logical function is determined by the user's programming of the device. Designers can "integrate" a digital system on a PLD by programming themselves, without having to ask chip manufacturers to design and make dedicated integrated circuit chips. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented by "logic compiler" software, which is similar to the software compiler used when developing and writing programs, and the original code before compilation must also be written in a specific programming language, which is called hardware description language (HDL). There is not only one kind of HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that it is only necessary to program the method flow slightly in the above-mentioned hardware description languages ​​and program it into the integrated circuit, and then it is easy to obtain the hardware circuit that implements the logic method flow.

[0080] The controller may be implemented in any suitable manner, for example, the controller may take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (e.g., software or firmware) executable by the (micro)processor, a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, and the memory controller may also be implemented as part of the control logic of the memory. It is also known to those skilled in the art that, in addition to implementing the controller in a purely computer-readable program code manner, the controller may be implemented in the form of a logic gate, a switch, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, such a controller may be considered as a hardware component, and the devices for implementing various functions included therein may also be considered as structures within the hardware component. Or even, the devices for implementing various functions may be considered as both software modules for implementing the method and structures within the hardware component.

[0081] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0082] For the convenience of description, the above devices are described in terms of functions and are divided into various units. Of course, when implementing the embodiments of the present disclosure, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0083] It should be understood by those skilled in the art that one or more embodiments of the present disclosure may be provided as a method, system or computer program product. Therefore, one or more embodiments of the present disclosure may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, one or more embodiments of the present disclosure may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0084] The present disclosure is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present disclosure. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of the processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0085] These computer program instructions may also be stored in a computer readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0086] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0087] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0088] One or more embodiments of the present disclosure may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. One or more embodiments of the present disclosure may also be practiced in distributed computing environments in which tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0089] Each embodiment in the present disclosure is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0090] The above description is only an embodiment of the present disclosure and is not intended to limit the present disclosure. For those skilled in the art, the present disclosure may have various modifications and variations. Any modification, equivalent substitution, improvement, etc. made within the spirit and principle of the present disclosure shall be included in the scope of the claims of the present disclosure.

Claims

1. An information sharing method, characterized in that: The method comprises: According to at least one listening node on the first blockchain, monitoring the information change event on the first blockchain where the listening node is located; wherein the information change event includes an information addition sub-event, an information modification sub-event for existing information, and an information deletion sub-event for existing information; When an information change event is monitored, the change parameters corresponding to the information change event are obtained from the target first blockchain that generates the information change event; the change parameters include the change type and the change information; the change type includes addition, modification, and deletion; The changed parameters are uploaded to a second blockchain; wherein the first blockchain corresponds to a first object; the second blockchain corresponds to a second object; and the first object and the second object have a subordinate relationship.

2. The method according to claim 1, characterized in that The monitoring of the information change event on the first blockchain where the monitoring node is located includes: Monitor the information change event of the target information on the first blockchain where the monitoring node is located; wherein the information identifier of the target information is unique on the first blockchain where the target information is located; the information identifier of the target information is determined according to the identity information in the target information, and the identity information includes at least one of the following: name, certificate type, and certificate number.

3. The method according to claim 2, characterized in that The change parameter also includes the blockchain identifier of the target first blockchain where the information change event corresponding to the change parameter is located, and the information identifier of the target information corresponding to the change parameter.

4. The method according to claim 3, characterized in that The step of obtaining, from the target first blockchain generating the information change event, a change parameter corresponding to the information change event, includes: The message contract event is triggered by the information change event on the target first blockchain to obtain the change parameters corresponding to the information change event; wherein, when the information change event triggers the generation of the message contract event, the change parameters corresponding to the information change event are passed into the message contract event; the message contract event is triggered by the information change event and generated according to a pre-set contract event template.

5. The method according to claim 3, characterized in that: The uploading of the changed parameters to the second blockchain includes: When there is an information identifier in the information identifier set corresponding to the second blockchain that is identical to the information identifier of the target information corresponding to the change parameter, the change parameter is uploaded to the second blockchain; wherein the information identifier set corresponding to the second blockchain is determined based on the identity information in the information stored in the second blockchain.

6. The method according to claim 5, characterized in that When the change type of the change parameter is increase, after uploading the change parameter to the second blockchain, the method further includes: When an information acquisition event triggered by a blockchain identifier extraction operation of the first blockchain is detected on the second blockchain, a designated information identifier corresponding to the information acquisition event and a blockchain identifier of the designated first blockchain are acquired; wherein the information identifier set corresponding to the second blockchain includes each information identifier and a corresponding relationship between the blockchain identifier of the first blockchain where the information corresponding to each information identifier is located; the blockchain identifier extraction operation of the first blockchain is triggered when the second blockchain adds the change information corresponding to the change parameter to the information identifier set corresponding to the second blockchain, and is used to extract the blockchain identifier of the first blockchain corresponding to the information identifier of the change information corresponding to the change parameter from the information identifier set; According to the information reading event, obtaining information corresponding to the specified information identifier from the first blockchain corresponding to the blockchain identifier of the specified first blockchain; The information corresponding to the obtained designated information identifier is sent to the second blockchain, so that the second blockchain merges the information corresponding to the obtained designated information identifier.

7. An information sharing device, characterized in that: The device comprises: A monitoring module, configured to monitor, according to at least one monitoring node on the first blockchain, information change events on the first blockchain where the monitoring node is located; wherein the information change event includes an information addition sub-event, an information modification sub-event for existing information, and an information deletion sub-event for existing information; An acquisition module, configured to acquire, when an information change event is monitored, change parameters corresponding to the information change event from the target first blockchain generating the information change event; the change parameters include a change type and change information; the change type includes addition, modification, and deletion; An uploading module is used to upload the changed parameters to a second blockchain; wherein the first blockchain corresponds to a first object; the second blockchain corresponds to a second object; and there is a subordinate relationship between the first object and the second object.

8. An information sharing device, characterized in that: include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program implements the steps of the method according to any one of claims 1 to 6 when executed by the processor.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium is used to store computer-executable instructions, and when the computer-executable instructions are executed by a processor, the steps of the method described in any one of claims 1 to 6 are implemented.

10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images