Trusted data space interconnection and intercommunication method, system and device

Abstract

The embodiment of the invention discloses a trusted data space interconnection and intercommunication method, system and device, and the method comprises the steps: receiving a registration request sent by a query node in an external trusted data space; initiating a legality verification request of the external trusted data space to the supervision platform through the local data market; when the validity verification of the external trusted data space is passed, the local data market initiates a validity verification request for the query node to the data market in the external trusted data space according to the general protocol, and when the validity verification of the query node is passed, the information of the query node is added to the local trusted data space; a registration success notification is sent to the query node; and receiving a data query request of the query node, matching target data in the local database according to the data query request, encrypting the target data and sending the encrypted target data to the query node. The data collaboration capability is improved, the data utilization rate is improved, and the security in the data transmission process is ensured.

Description

Technical Field

[0001] The present invention relates to the field of privacy computing, and in particular to a trusted data space interconnection method, system and device. Background Art

[0002] Trusted data spaces are becoming more and more active in China, mainly to solve data security issues in the process of data circulation. However, communication between members of different data spaces is not allowed at this stage, that is, there is no reasonable and compliant solution to enable interaction between data spaces. For example, the trusted data space of the automotive industry includes information from various automobile companies, which can be used to share data among them. But if automobile company A wants specific information about an accessory, there is no way to query it in this data space. At this time, it is necessary to query the information of the accessory in the trusted data space of the corresponding retail industry. However, the existing technology cannot complete the data interconnection and interoperability of two trusted data spaces.

[0003] There is currently no effective solution to the above problems in the prior art. Summary of the invention

[0004] To solve the above problems, the present invention provides a method, system and device for interconnecting and interoperating trusted data spaces, which realizes the legitimacy verification of external trusted data spaces through the interaction between the local data market and the regulatory platform; realizes the legitimacy verification and registration of nodes through the interaction between the local data market and the data market of the external trusted data space; after completing the registration, standardizes the data query and transmission process through a unified protocol to ensure the security and compliance of data in cross-space circulation, so as to solve the problem that different trusted data spaces cannot be interconnected in the prior art.

[0005] To achieve the above-mentioned purpose, the present invention provides a method for interconnecting and interoperating trusted data spaces, comprising: receiving a registration request sent by a query node in an external trusted data space; wherein, the query node sends the registration request according to a general protocol after querying the address information of the target data space from the regulatory platform; initiating a request for legitimacy verification of the external trusted data space to the regulatory platform through the local data market and receiving a verification notification; wherein, the data market serves as a centralized node for managing the information of other nodes in the trusted data space to which it belongs; when the legitimacy verification of the external trusted data space passes, the local data market initiates a request for legitimacy verification of the query node to the data market in the external trusted data space according to the general protocol, and when the legitimacy verification of the query node passes, the information of the query node is added to the local trusted data space, and a registration success notification is sent to the query node; receiving a data query request from the query node, matching the target data in the local database according to the data query request, encrypting the target data and sending it to the query node.

[0006] Further optionally, the general protocol includes: a message header, a message body and a message trailer; the message header includes: a protocol version number field, a sender identification field, a receiver identification field and a message sequence number field; the message body includes: a query node ID field, a data space ID field to which the query node belongs and a data field sent by the query node; the message trailer includes: a check field, a signature field and an end flag field.

[0007] Further optionally, before receiving the registration request sent by the query node in the external trusted data space, it includes: each trusted data space submits a registration application to the supervision platform; after successful registration, the registration information and address information of the trusted data space is stored in the supervision platform.

[0008] Further optionally, initiating a request for legitimacy verification of the external trusted data space to the regulatory platform through the local data market and receiving a verification notification, includes: sending an identifier of the external trusted data space to the regulatory platform; receiving a verification notification of the external trusted data space returned by the regulatory platform, if the registration status in the verification notification is registered, it is considered that the legitimacy verification of the trusted data space has been passed; otherwise, the legitimacy verification of the trusted data space has not been passed; wherein, the registration status is obtained by the regulatory platform after matching the identifier with the local registration information base.

[0009] On the other hand, the present invention provides a trusted data space interconnection system, including: a registration request receiving module, used to receive a registration request sent by a query node in an external trusted data space; wherein the query node sends the registration request according to a general protocol after querying the address information of the target data space from the regulatory platform; a trusted data space verification module, used to initiate a legitimacy verification request for the external trusted data space to the regulatory platform through its own data market; wherein the data market, as a centralized node, is used to manage the information of other nodes in its trusted data space; a query node verification module, used to initiate a legitimacy verification request for the query node to the data market in the external trusted data space according to a general protocol when the legitimacy verification of the external trusted data space passes, and when the legitimacy verification of the query node passes, the information of the query node is added to the own trusted data space, and a registration success notification is sent to the query node; a data transmission module, used to receive a data query request from the query node, match the target data in the local database according to the data query request, encrypt the target data and send it to the query node.

[0010] Further optionally, the general protocol includes: a message header, a message body and a message trailer; the message header includes: a protocol version number field, a sender identification field, a receiver identification field and a message sequence number field; the message body includes: a query node ID field, a data space ID field to which the query node belongs and a data field sent by the query node; the message trailer includes: a check field, a signature field and an end flag field.

[0011] Further optionally, the system also includes: an application submission module, which is used for each trusted data space to submit a registration application to the supervision platform; and a data storage module, which is used to store the registration information and address information of the trusted data space in the supervision platform after successful registration.

[0012] Further optionally, the trusted data space verification module includes: an identifier sending submodule, used to send the identifier of the external trusted data space to the regulatory platform; a registration information comparison submodule, used to receive the verification notification of the external trusted data space returned by the regulatory platform, if the registration status in the verification notification is registered, it is considered that the legitimacy verification of the trusted data space has been passed; otherwise, the legitimacy verification of the trusted data space has not been passed; wherein, the registration status is obtained by the regulatory platform after matching the identifier with the local registration information library based on the identifier.

[0013] On the other hand, the present invention also provides a trusted data space interconnection and intercommunication device, including the above-mentioned trusted data space interconnection and intercommunication system.

[0014] On the other hand, the present invention also provides a computer-readable storage medium having a computer program stored thereon, which implements the above-mentioned trusted data space interconnection method when executed by a processor.

[0015] The above technical solution has the following beneficial effects: by connecting different data spaces through a common protocol, cross-domain and cross-organizational data sharing and collaboration can be realized, greatly improving the efficiency of data utilization; through a legitimacy verification mechanism, it ensures that external trusted data spaces and query nodes participating in interconnection are all registered and verified trusted entities, eliminating unauthorized data access from the source and improving the security of data interaction. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0017] Figure 1is a flow chart of a trusted data space interconnection method provided by an embodiment of the present invention;

[0018] Figure 2 is a flow chart of a trusted data space registration method provided by an embodiment of the present invention;

[0019] Figure 3 is a flow chart of a trusted data space verification method provided by an embodiment of the present invention;

[0020] Figure 4 It is a structural diagram of a trusted data space interconnection and intercommunication system provided by an embodiment of the present invention;

[0021] Figure 5 is a schematic diagram of the structure of a module for trusted data space registration provided by an embodiment of the present invention;

[0022] Figure 6 It is a structural diagram of a trusted data space verification module provided by an embodiment of the present invention.

[0023] Figure numerals: 100 - registration request receiving module; 200 - trusted data space verification module; 2001 - identifier sending submodule; 2002 - registration information comparison submodule; 300 - query node verification module; 400 - data transmission module; 500 - application submission module; 600 - data storage module. DETAILED DESCRIPTION

[0024] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. 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 creative work are within the scope of protection of the present invention.

[0025] In order to solve the problem that different trusted data spaces cannot communicate with each other in the prior art, an embodiment of the present invention provides a trusted data space interconnection method. Figure 1 is a flow chart of a trusted data space interconnection method provided by an embodiment of the present invention, such as Figure 1 As shown, the method includes:

[0026] S1. Receive a registration request sent by a query node in an external trusted data space; wherein the query node queries the regulatory platform for address information of the target data space and then sends the registration request according to a general protocol;

[0027] If a connector A2 in the trusted data space A wants to query the data in the trusted data space B, then at this time, the connector A2 is the query node, and for the data space B, the trusted data space A is the external trusted data space.

[0028] Query node A2 determines the trusted data space B where the data to be queried is located according to the query requirements, and sends a request to the supervision platform for the address information of the trusted data space B. After the supervision platform obtains the address information locally, it returns it to the query node A2. The query node A2 can then send a registration request to the trusted data space B according to the address information. The registration request is sent through a general protocol.

[0029] After receiving the registration request, the trusted data space B can proceed to the next registration operation.

[0030] The above-mentioned connector refers to a software program deployed in the space of data providers and demanders, which is used to realize data exchange and control of data usage during the process.

[0031] The trusted data space can be oriented towards data element circulation scenarios and provide security protection technical capabilities in the data exchange process, such as data usage policies, log audits, data markets, etc.; corresponding security policies can also be selected to allow data to be used in accordance with the constraints of the corresponding policies during the exchange process between providers and demanders, while providing corresponding log audit capabilities to help customers understand the operational process of data in the exchange and circulation process.

[0032] The supervision platform is a government supervision platform that can query relevant information of registered trusted data spaces.

[0033] S2. Initiate a request for legality verification of the external trusted data space to the regulatory platform through the data market of the party and receive the verification notification; the data market acts as a centralized node to manage the information of other nodes in the trusted data space;

[0034] The local data market B1 of the trusted data space B extracts the identifier of the external trusted data space A from the registration request, and constructs a legitimacy verification request based on it, and sends it to the regulatory platform through a general protocol.

[0035] The transmission process of the legitimacy verification request adopts a secure encryption protocol to ensure the integrity and security of the message.

[0036] The above-mentioned data market exists in every trusted data space. The data market is also a connector, which can be regarded as a centralized connector for managing other connectors in the trusted data space of the party, such as providing data search, asset labeling, demand matching, contract negotiation, data subscription and other functions to help consumers find valuable data quickly and efficiently.

[0037] S3. When the legitimacy verification of the external trusted data space is passed, the local data market initiates a legitimacy verification request for the query node to the data market in the external trusted data space according to the general protocol. When the legitimacy verification of the query node is passed, the information of the query node is added to the local trusted data space, and a registration success notification is sent to the query node;

[0038] After receiving the legality verification request, the regulatory platform will perform legality verification locally. If the legality verification passes, a notification will be sent back to the data market B1. If not, a notification of failed verification will be sent back to the data market B1. After receiving the notification of failed verification, the data market B1 will send a registration failure notification to the external trusted data space A.

[0039] When the legitimacy verification of the external trusted data space is passed, the data market B1 can send a query node verification request to its data market A1 according to the address information of the external trusted data space in the registration request.

[0040] Specifically, the local data market can add the query node identifier and request content to the request, and send the verification request to the external trusted data space A through the general protocol. After receiving the request, the data market A1 of the external trusted data space A verifies the legal status of the query node A2 through the data market. If the verification is legal, a verification pass notification is sent to the trusted data space B; if the verification is illegal, a registration failure notification is directly sent to the query node A2.

[0041] After receiving the notification that the node legitimacy verification has passed, the trusted data space B adds the information of the query node A2 (connector ID, name, registration time, etc.) to the trusted data space B, and sends a notification of successful registration to the query node A2 in the external data space A. At this point, the query node A2 can query data from the connector in the trusted data space B.

[0042] S4. Receive a data query request from a query node, match target data in a local database according to the data query request, encrypt the target data and send it to the query node.

[0043] Query node A2 sends a data query request to trusted data space B through a universal protocol. The data market of trusted data space B notifies the corresponding connector to perform a local data query based on the data query request. After the target data is queried, the target data is encrypted and sent to query node A2.

[0044] As an optional implementation, the general protocol includes:

[0045] Message header, message body and message trailer;

[0046] The message header includes: a protocol version number field, a sender identification field, a receiver identification field, and a message sequence number field;

[0047] The message body includes: a query node ID field, a data space ID field to which the query node belongs, and a data field sent by the query node;

[0048] The message tail includes: a checksum field, a signature field, and an end flag field.

[0049] This embodiment defines a set of trusted data space information exchange protocols TAX (TAX), which aims to provide a standardized electronic communication protocol between trusted data spaces. The TAX protocol consists of three parts: a message header, a message body, and a message trailer. The message header and the message trailer contain some necessary information, such as: TAX version number, sender, receiver, message sequence number, etc. The message body includes: connector ID, data space ID to which the connector belongs, data sent by the connector, etc. Each field of the TAX message has a unique identifier (Tag) and a corresponding value (Value). The identifier and the value are connected with an equal sign (=), and the values ​​are separated by a vertical bar (|). The following is an example of a TAX protocol:

[0050] 8=TAX.4.2|35=Logon|49=SENDER|56=TARGET|34=ec9cbec3-4cde-4518-a760-0ea47ac71daa|52=20240508-10:15:30.123|;

[0051] 8=TAX.4.2: 8 represents the TAX protocol version number. The value of the version number is TAX4.2, which means that the TAX protocol version 4.2 is used.

[0052] 35=Logon: 35 is the message type. Logon means this is a login request.

[0053] 49=SENDER: 49 represents the sender identifier field, indicating that the sender identifier is "SENDER";

[0054] 56=TARGET: 56 represents the target identifier field, indicating that the target identifier is "TARGET";

[0055] 34=ec9cbec3-4cde-4518-a760-0ea47ac71daa: 34 indicates the sender’s ID information, and ec9cbec3-4cde-4518-a760-0ea47ac71daa indicates the specific ID value;

[0056] 52=20240508-10:15:30.123: This is the timestamp field, indicating that the timestamp of the message is "2023-05-0810:15:30.123".

[0057] As an optional implementation, Figure 2 is a flow chart of a trusted data space registration method provided by an embodiment of the present invention. Figure 2 As shown, before receiving the registration request sent by the query node in the external trusted data space, it includes:

[0058] S5. Each trusted data space submits a registration application to the regulatory platform;

[0059] S6. After successful registration, the registration information and address information of the trusted data space will be stored in the supervision platform.

[0060] Before starting the interconnection function, each trusted data space needs to submit a registration application to the regulatory platform, which includes data space identifier, space description, address information, registration time, etc. After receiving the application, the regulatory platform verifies the authenticity and legality of the application content to ensure that the registered data space meets the relevant compliance requirements.

[0061] After successful registration, the regulatory platform stores the registration information and address information of the trusted data space in its local registration information database and generates a unique registration identifier for each registered data space. This registration information is used in subsequent data space verification and data exchange processes to ensure that the interconnected data spaces are legal and credible entities.

[0062] As an optional implementation, Figure 3 is a flow chart of a trusted data space verification method provided by an embodiment of the present invention. Figure 3 As shown, through the local data market, a request for legality verification of the external trusted data space is initiated to the regulatory platform and a verification notification is received, including:

[0063] S201. Sending an identifier of the external trusted data space to the supervision platform;

[0064] S202. Receive the verification notification of the external trusted data space returned by the regulatory platform. If the registration status in the verification notification is registered, it is considered that the legitimacy verification of the trusted data space has been passed; otherwise, the legitimacy verification of the trusted data space has not been passed. Among them, the registration status is obtained by the regulatory platform after matching the identifier with the local registration information library based on the identifier.

[0065] After receiving the registration request from the external trusted data space, the local data market in the trusted data space B extracts the identifier of the external trusted data space A from it, and sends the identifier to the regulatory platform through the general protocol to request verification of the legitimacy of the external trusted data space.

[0066] The regulatory platform matches the received identifier with its locally stored registration information library to determine the legal registration status of the external trusted data space. If the match is successful and the registration status is "registered", the external trusted data space is judged to have passed the legality verification of the trusted data space; if the match fails or the registration status is "unregistered", the external trusted data space is judged to have failed the legality verification, and the corresponding verification result is returned to the data market of trusted data space B.

[0067] Among them, the registration status is generated by the regulatory platform after matching the identifier of the external trusted data space with the identifier of its local registration information base, and generating status information of legality verification based on the matching result.

[0068] The following is a specific embodiment:

[0069] If query node A2 in trusted data space A wants to query data in trusted data space B, it needs to send a registration request to trusted data space B. Query node A2 first sends an address query request for trusted data space B to the regulatory platform. After the regulatory platform searches for the corresponding address information locally, it sends it to trusted data space A. After query node A2 receives the address information, it sends a registration request to trusted data space B according to the address information in accordance with the general protocol. After trusted data space B receives the registration request, data market B1 sends a legality verification request to the regulatory platform. After the regulatory platform performs legality verification locally, it sends the verification result to data market B1. Data market B1 receives the verification result. If the verification fails, it sends a registration failure notification to query node A2. If it passes, it initiates a node verification request to data market A1 in trusted data space A. Data market A1 verifies query node A2. If the verification fails, a registration failure notification is sent to query node A2. If the verification passes, data market B1 is notified. Data market B1 adds the information of query node A2 to trusted data space B and sends a registration success notification to query node A2. At this time, query node A2 can query data in trusted data space B. For example, query node A2 can query data in node B2 in trusted data space B.

[0070] As an optional implementation, the embodiment of the present invention further provides a trusted data space interconnection system. Figure 4 is a schematic diagram of the structure of the trusted data space interconnection system provided by an embodiment of the present invention, such as Figure 4As shown, the system includes:

[0071] The registration request receiving module 100 is used to receive a registration request sent by a query node in an external trusted data space; wherein the query node sends a registration request according to a general protocol after querying the address information of the target data space from the supervision platform;

[0072] If a connector A2 in the trusted data space A wants to query the data in the trusted data space B, then at this time, the connector A2 is the query node, and for the data space B, the trusted data space A is the external trusted data space.

[0073] Query node A2 determines the trusted data space B where the data to be queried is located according to the query requirements, and sends a request to the supervision platform for the address information of the trusted data space B. After the supervision platform obtains the address information locally, it returns it to the query node A2. The query node A2 can then send a registration request to the trusted data space B according to the address information. The registration request is sent through a general protocol.

[0074] After receiving the registration request, the trusted data space B can proceed to the next registration operation.

[0075] The above-mentioned connector refers to a software program deployed in the space of data providers and demanders, which is used to realize data exchange and control of data usage during the process.

[0076] The trusted data space can be oriented towards data element circulation scenarios and provide security protection technical capabilities in the data exchange process, such as data usage policies, log audits, data markets, etc.; corresponding security policies can also be selected to allow data to be used in accordance with the constraints of the corresponding policies during the exchange process between providers and demanders, while providing corresponding log audit capabilities to help customers understand the operational process of data in the exchange and circulation process.

[0077] The supervision platform is a government supervision platform that can query relevant information of registered trusted data spaces.

[0078] The trusted data space verification module 200 is used to initiate a request for legality verification of the external trusted data space to the regulatory platform through the local data market; wherein the data market acts as a centralized node to manage the information of other nodes in the trusted data space;

[0079] The local data market B1 of the trusted data space B extracts the identifier of the external trusted data space A from the registration request, and constructs a legitimacy verification request based on it, and sends it to the regulatory platform through a general protocol.

[0080] The transmission process of the legitimacy verification request adopts a secure encryption protocol to ensure the integrity and security of the message.

[0081] The above-mentioned data market exists in every trusted data space. The data market is also a connector, which can be regarded as a centralized connector for managing other connectors in the trusted data space of the party, such as providing data search, asset labeling, demand matching, contract negotiation, data subscription and other functions to help consumers find valuable data quickly and efficiently.

[0082] The query node verification module 300 is used for initiating a query node legitimacy verification request to the data market in the external trusted data space according to the general protocol when the legitimacy verification of the external trusted data space passes. When the legitimacy verification of the query node passes, the query node information is added to the local trusted data space, and a registration success notification is sent to the query node.

[0083] After receiving the legality verification request, the regulatory platform will perform legality verification locally. If the legality verification passes, a notification will be sent back to the data market B1. If not, a notification of failed verification will be sent back to the data market B1. After receiving the notification of failed verification, the data market B1 will send a registration failure notification to the external trusted data space A.

[0084] When the legitimacy verification of the external trusted data space is passed, the data market B1 can send a query node verification request to its data market A1 according to the address information of the external trusted data space in the registration request.

[0085] Specifically, the local data market can add the query node identifier and request content to the request, and send the verification request to the external trusted data space A through the general protocol. After receiving the request, the data market A1 of the external trusted data space A verifies the legal status of the query node A2 through the data market. If the verification is legal, a verification pass notification is sent to the trusted data space B; if the verification is illegal, a registration failure notification is directly sent to the query node A2.

[0086] After receiving the notification that the node legitimacy verification has passed, the trusted data space B adds the information of the query node A2 (connector ID, name, registration time, etc.) to the trusted data space B, and sends a notification of successful registration to the query node A2 in the external data space A. At this point, the query node A2 can query data from the connector in the trusted data space B.

[0087] The data transmission module 400 is used to receive a data query request from a query node, match target data in a local database according to the data query request, encrypt the target data and send it to the query node.

[0088] Query node A2 sends a data query request to trusted data space B through a universal protocol. The data market of trusted data space B notifies the corresponding connector to perform a local data query based on the data query request. After the target data is queried, the target data is encrypted and sent to query node A2.

[0089] As an optional implementation, the general protocol includes:

[0090] Message header, message body and message trailer;

[0091] The message header includes: a protocol version number field, a sender identification field, a receiver identification field, and a message sequence number field;

[0092] The message body includes: a query node ID field, a data space ID field to which the query node belongs, and a data field sent by the query node;

[0093] The message tail includes: a checksum field, a signature field, and an end flag field.

[0094] This embodiment defines a set of trusted data space information exchange protocols TAX (TAX), which aims to provide a standardized electronic communication protocol between trusted data spaces. The TAX protocol consists of three parts: a message header, a message body, and a message trailer. The message header and the message trailer contain some necessary information, such as: TAX version number, sender, receiver, message sequence number, etc. The message body includes: connector ID, data space ID to which the connector belongs, data sent by the connector, etc. Each field of the TAX message has a unique identifier (Tag) and a corresponding value (Value). The identifier and the value are connected with an equal sign (=), and the values ​​are separated by a vertical bar (|). The following is an example of a TAX protocol:

[0095] 8=TAX.4.2|35=Logon|49=SENDER|56=TARGET|34=ec9cbec3-4cde-4518-a760-0ea47ac71daa|52=20240508-10:15:30.123|;

[0096] 8=TAX.4.2: 8 represents the TAX protocol version number. The value of the version number is TAX4.2, which means that the TAX protocol version 4.2 is used.

[0097] 35=Logon: 35 is the message type. Logon means this is a login request.

[0098] 49=SENDER: 49 represents the sender identifier field, indicating that the sender identifier is "SENDER";

[0099] 56=TARGET: 56 represents the target identifier field, indicating that the target identifier is "TARGET";

[0100] 34=ec9cbec3-4cde-4518-a760-0ea47ac71daa: 34 indicates the sender’s ID information, and ec9cbec3-4cde-4518-a760-0ea47ac71daa indicates the specific ID value;

[0101] 52=20240508-10:15:30.123: This is the timestamp field, indicating that the timestamp of the message is "2023-05-0810:15:30.123".

[0102] As an optional implementation, Figure 5 is a schematic diagram of the structure of a module for trustworthy data space registration provided by an embodiment of the present invention, such as Figure 5 As shown, the system also includes:

[0103] Application submission module 500, used for each trusted data space to submit a registration application to the supervision platform;

[0104] The data storage module 600 is used to store the registration information and address information of the trusted data space in the supervision platform after successful registration.

[0105] Before starting the interconnection function, each trusted data space needs to submit a registration application to the regulatory platform, which includes data space identifier, space description, address information, registration time, etc. After receiving the application, the regulatory platform verifies the authenticity and legality of the application content to ensure that the registered data space meets the relevant compliance requirements.

[0106] After successful registration, the regulatory platform stores the registration information and address information of the trusted data space in its local registration information database and generates a unique registration identifier for each registered data space. This registration information is used in subsequent data space verification and data exchange processes to ensure that the interconnected data spaces are legal and credible entities.

[0107] As an optional implementation, Figure 6 is a schematic diagram of the structure of a trusted data space verification module provided by an embodiment of the present invention. Figure 6 As shown, the trusted data space verification module includes:

[0108] The identifier sending submodule 2001 is used to send the identifier of the external trusted data space to the supervision platform;

[0109] The registration information comparison submodule 2002 is used to receive the verification notification of the external trusted data space returned by the supervision platform. If the registration status in the verification notification is registered, it is considered that the legitimacy verification of the trusted data space has been passed; otherwise, it fails the legitimacy verification of the trusted data space; wherein, the registration status is obtained by the supervision platform after matching the identifier with the local registration information library based on the identifier.

[0110] After receiving the registration request from the external trusted data space, the local data market in the trusted data space B extracts the identifier of the external trusted data space A from it, and sends the identifier to the regulatory platform through the general protocol to request verification of the legitimacy of the external trusted data space.

[0111] The regulatory platform matches the received identifier with its locally stored registration information library to determine the legal registration status of the external trusted data space. If the match is successful and the registration status is "registered", the external trusted data space is judged to have passed the legality verification of the trusted data space; if the match fails or the registration status is "unregistered", the external trusted data space is judged to have failed the legality verification, and the corresponding verification result is returned to the data market of trusted data space B.

[0112] Among them, the registration status is generated by the regulatory platform after matching the identifier of the external trusted data space with the identifier of its local registration information base, and generating status information of legality verification based on the matching result.

[0113] An embodiment of the present invention further provides a trusted data space interconnection and intercommunication device, including the above-mentioned trusted data space interconnection and intercommunication system.

[0114] An embodiment of the present invention further provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the above-mentioned trusted data space interconnection method is implemented.

[0115] The above storage media include but are not limited to: CDs, floppy disks, hard disks, erasable memory, etc.

[0116] The above technical solution has the following beneficial effects: by connecting different data spaces through a common protocol, cross-domain and cross-organizational data sharing and collaboration can be realized, greatly improving the efficiency of data utilization; through a legitimacy verification mechanism, it ensures that external trusted data spaces and query nodes participating in interconnection are all registered and verified trusted entities, eliminating unauthorized data access from the source and improving the security of data interaction.

[0117] The specific implementation methods of the above invention further illustrate the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above content is only the specific implementation methods of the present invention and is not intended to limit the protection scope of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the protection scope of the present invention.

Claims

1. A trusted data space interconnection method, characterized in that: include: Receiving a registration request sent by a query node in an external trusted data space; wherein the query node sends the registration request according to a general protocol after querying the regulatory platform for address information of the target data space; Initiate a request for verification of the legitimacy of the external trusted data space to the regulatory platform through the data market of the party and receive a verification notification; wherein the data market acts as a centralized node to manage the information of other nodes in the trusted data space; When the legitimacy verification of the external trusted data space is passed, the local data market initiates a legitimacy verification request for the query node to the data market in the external trusted data space according to the general protocol. When the legitimacy verification of the query node is passed, the information of the query node is added to the local trusted data space, and a registration success notification is sent to the query node; A data query request from the query node is received, target data is matched in a local database according to the data query request, and the target data is encrypted and sent to the query node.

2. The trusted data space interconnection method according to claim 1, characterized in that: The general protocol includes: Message header, message body and message trailer; The message header includes: a protocol version number field, a sender identification field, a receiver identification field and a message sequence number field; The message body includes: a query node ID field, a data space ID field to which the query node belongs, and a data field sent by the query node; The message tail includes: a check field, a signature field and an end flag field.

3. The trusted data space interconnection method according to claim 1, characterized in that: Before receiving the registration request sent by the query node in the external trusted data space, the method includes: Each trusted data space submits a registration application to the regulatory platform; After successful registration, the registration information and address information of the trusted data space will be stored in the supervision platform.

4. The trusted data space interconnection method according to claim 1, characterized in that: The initiating a request for verification of the legitimacy of the external trusted data space to the regulatory platform through the local data market and receiving a verification notification includes: Sending an identifier of the external trusted data space to the supervision platform; Receive the verification notification of the external trusted data space returned by the supervision platform. If the registration status in the verification notification is registered, it is considered that the legitimacy verification of the trusted data space has been passed; otherwise, it fails the legitimacy verification of the trusted data space. The registration status is obtained by the supervision platform after matching the identifier with the local registration information base based on the identifier.

5. A trusted data space interconnection system, characterized in that: include: A registration request receiving module, used to receive a registration request sent by a query node in an external trusted data space; wherein the query node sends the registration request according to a general protocol after querying the regulatory platform for the address information of the target data space; A trusted data space verification module is used to initiate a request for legitimacy verification of the external trusted data space to the regulatory platform through the local data market; wherein the data market acts as a centralized node to manage the information of other nodes in the trusted data space; A query node verification module, which is used for initiating a query node legitimacy verification request to the data market in the external trusted data space according to the general protocol when the legitimacy verification of the external trusted data space passes. When the legitimacy verification of the query node passes, the information of the query node is added to the local trusted data space, and a registration success notification is sent to the query node; The data transmission module is used to receive the data query request of the query node, match the target data in the local database according to the data query request, encrypt the target data and send it to the query node.

6. The trusted data space interconnection system according to claim 5, characterized in that: The general protocol includes: Message header, message body and message trailer; The message header includes: a protocol version number field, a sender identification field, a receiver identification field and a message sequence number field; The message body includes: a query node ID field, a data space ID field to which the query node belongs, and a data field sent by the query node; The message tail includes: a check field, a signature field and an end flag field.

7. The trusted data space interconnection system according to claim 5, characterized in that: Also includes: The application submission module is used by each trusted data space to submit registration applications to the regulatory platform; The data storage module is used to store the registration information and address information of the trusted data space in the supervision platform after successful registration.

8. The trusted data space interconnection system according to claim 5, characterized in that: The trusted data space verification module includes: An identifier sending submodule, used for sending the identifier of the external trusted data space to the supervision platform; The registration information comparison submodule is used to receive the verification notification of the external trusted data space returned by the supervision platform. If the registration status in the verification notification is registered, it is considered that the legitimacy verification of the trusted data space has been passed; otherwise, the legitimacy verification of the trusted data space has not been passed. The registration status is obtained by the supervision platform after matching the identifier with the local registration information library based on the identifier.

9. A trusted data space interconnection device, characterized in that: It comprises a trusted data space interconnection system as described in any one of claims 5 to 8.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the trusted data space interconnection method as described in any one of claims 1 to 4 is implemented.

Images