A multi-domain P2P-based government affair data sharing and exchanging system and method

Abstract

The application relates to the technical field of computers, in particular to a government affair data sharing and exchanging system and method based on a multi-domain P2P, which comprises a control plane used for maintaining basic data, defining strategies and parameters, and monitoring an execution process; a data plane used for executing the retrieval, transmission and release of data according to the strategies and parameters of the control plane; the system has the beneficial effects of improving the flexibility and reliability of the system; the separation of the control plane and the data plane realizes the standardization and configurability of the strategies; the strategy definition and parameter setting of the control plane provide explicit guidance for the transmission of the data plane, and the data plane no longer depends on the control and management node when executing the transmission task; the design ensures that the data sharing and transmission process can normally proceed even in the case of the failure of the management node, thereby guaranteeing the continuity and stability of the government affair data exchange.

Description

Technical Field

[0001] This invention relates to the field of computer technology, specifically to a government data sharing and exchange system and method based on multi-domain P2P. Background Technology

[0002] In the field of government data sharing and exchange, traditional solutions typically employ a multi-layered cascaded architecture to achieve cross-level information resource catalog services and data exchange services. While this structure meets the needs of data sharing to some extent, its inherent problems have gradually become apparent with the increase in the volume of government data and the diversification of business requirements. Specifically, due to the multi-layered and long-linked nature of the cascaded architecture, data exchange timeliness is low, and operation and maintenance become complex. For example, in a multi-layered cascaded architecture, data needs to pass through multiple intermediate nodes from the source to the destination, which not only increases data transmission latency but also raises the probability of errors, affecting the real-time performance and accuracy of the data.

[0003] To address these issues, peer-to-peer (P2P) networking technology has been introduced as a potential solution. A P2P network consists of multiple independent peer nodes interconnected, each with a unique identifier. This type of network utilizes distributed storage services to store resources, each resource also having a unique identifier. The self-organizing and self-managing characteristics of P2P networks allow nodes to flexibly join or leave the network, providing good scalability. However, when a central enrollment server is introduced to control node joining, P2P networks may encounter single points of failure; and in a fully decentralized, fully peer-to-peer network, large-scale deployment may face performance challenges.

[0004] For example, Chinese Patent Publication No. CN116781713A discloses a P2P-based government data sharing and exchange system and data acquisition method. This system includes a business system module, a data transmission control module, and a data exchange network module. The data exchange network module consists of multiple network transmission nodes, each including a P2P file system for storing configuration files for government data. Additionally, there is a municipal-level shared exchange module for communication between the business system and the network transmission nodes. However, compared to this invention, existing technologies are primarily based on a fully peer-to-peer P2P file system topology, where the network transmission nodes are the key component, interacting with the business system through municipal or provincial-level shared exchange nodes. Due to the node limit in a fully peer-to-peer network, business systems below the municipal level cannot directly become peers and need to exchange data through a higher-level shared exchange node as a proxy. Furthermore, existing technologies control resource addition through a central data transmission control module, which to some extent limits the system's flexibility and scalability.

[0005] Connector technology provides a cross-organizational framework for data sharing in the data space, allowing each organization to control how its data is shared and providing a trusted data exchange and sharing channel for data providers and consumers. However, connectors in existing technologies (e.g., IDS in Europe) typically rely on a central control module, which can lead to performance bottlenecks and single points of failure risks during large-scale deployments. Summary of the Invention

[0006] The purpose of this invention is to provide a government data sharing and exchange system and method based on multi-domain P2P, so as to solve the problems mentioned in the background art.

[0007] To achieve the above objectives, the present invention provides the following technical solution: a government data sharing and exchange system based on multi-domain P2P, the system comprising:

[0008] The control plane is used to maintain basic data, define strategies and parameters, and monitor the execution process;

[0009] The data plane performs data retrieval, transmission, and publication based on the strategies and parameters of the control plane.

[0010] Preferably, the control surface further includes:

[0011] The management center module is used for the operation and configuration of the government data sharing and exchange system under the domain-specific management system;

[0012] The approval module is used to manage the approval process for data sharing requests;

[0013] The management center module also includes a connector node control unit for managing the registration, authentication, and monitoring of connector nodes in the system; and a digital identity management unit for managing the digital identities of users and connectors.

[0014] Preferably, the data plane includes a connector module, which is used to realize data exchange and communication between nodes, and specifically includes a networking unit, a content addressing unit, a content routing unit, a security authentication unit, a transmission unit, a publishing unit, and a gateway unit;

[0015] The system also includes an application system module for specific government data provision and request, including data provider units and data requester units.

[0016] Preferably, the system adopts a multi-domain P2P topology architecture, and the connectors are set in one or more shared domains according to permissions and topics. The connector types include data users, data providers, data providers and users, data storage providers, and gateway connectors. The connectors are divided into ordinary connectors, trusted connectors, super connectors, and bootstrap connectors according to identity and permission types.

[0017] Preferably, the system configures a key pair conforming to the national cryptographic algorithm for all connectors, including a public key and a private key, for authentication and data encryption; it uses a distributed hash table to register and manage the public key, IP address, and digital identity of the connectors; it discovers and routes connectors through the ConnectorID generated based on the connector's public key; and it allows connectors to be classified and searched by setting tags, such as topic tags, industry tags, storage tags, and credit tags.

[0018] A multi-domain P2P-based government data sharing and exchange method is applied to a multi-domain P2P-based government data sharing and exchange system. The method includes the following steps:

[0019] Maintain basic data, define policies and parameters, and monitor the execution process in the control plane;

[0020] The data plane performs data retrieval, transmission, and publication based on the strategies and parameters defined in the control plane.

[0021] Preferably, the control plane management steps further include:

[0022] The operation and configuration of the government data sharing and exchange system are managed by domain through the management center module;

[0023] The approval module manages the approval process for data sharing requests, ensuring the security and compliance of data sharing.

[0024] Preferably, the connector module in the data plane execution step enables data exchange and communication between nodes, specifically including:

[0025] Constructing a multi-domain P2P network topology using networking units;

[0026] Accurate data location and routing are achieved through content addressing units and content routing units;

[0027] Use a secure authentication unit to authenticate nodes and encrypt data;

[0028] Reliable data transmission, publishing, and API access are achieved through transmission units, publishing units, and gateway units.

[0029] Preferably, the method also includes operational steps of the application system module for specific government data provision and request, including:

[0030] The data provider unit publishes data resources for other nodes to retrieve and use;

[0031] The data requesting unit requests data resources from the data providing unit and receives the returned data.

[0032] Preferably, the method further includes the following steps:

[0033] A multi-domain P2P topology architecture is adopted, and connectors are set in one or more shared domains according to permissions and topics;

[0034] Configure all connectors with key pairs conforming to Chinese cryptographic algorithms, including public and private keys, for authentication and data encryption;

[0035] Utilize distributed hash tables for the registration and management of connectors' public keys, IP addresses, and digital identities;

[0036] Connectors are discovered and routed using ConnectorIDs generated based on the connector's public key, thus determining the source and destination of data packets;

[0037] Connectors can be categorized and searched by setting tags, such as topic tags, industry tags, storage tags, and credit tags, thereby improving the efficiency and accuracy of data sharing and exchange.

[0038] Compared with the prior art, the beneficial effects of the present invention are:

[0039] 1. Improved System Flexibility and Reliability: By separating the control plane from the data plane, policies are standardized and configurable. The policy definitions and parameter settings of the control plane provide clear guidance for data plane transmission, while the data plane no longer depends on the control and management nodes when performing transmission tasks. This design ensures that data sharing and transmission can continue normally even if the management node fails, thereby guaranteeing the continuity and stability of government data exchange.

[0040] 2. Enhanced System Robustness: The system employs a domain-based management strategy, dividing the entire network into multiple domains, significantly enhancing system robustness. Each domain has an independent management node and connectors, ensuring that the operation of other domains remains unaffected when one domain experiences a failure, thus guaranteeing high availability for the entire system.

[0041] 3. Enhanced System Scalability: Domain-based management significantly increases the number of manageable nodes. Through a multi-domain approach, the system can scale to tens of thousands or even more nodes, meeting the needs of large-scale government data sharing and providing ample room for future growth in government data volume.

[0042] 4. Optimized data transmission efficiency: The introduced content addressing and routing technologies improve the efficiency of data retrieval and transmission. This content-based addressing method makes data transmission more direct and faster, reducing unnecessary network latency and data redundancy.

[0043] 5. Enhanced Data Sovereignty and Security: By strengthening the security authentication mechanism, the security and integrity of data exchange are ensured. The system's security authentication unit and digital identity management unit work together to provide strong security guarantees for data transmission.

[0044] 6. Simplified System Operation and Maintenance: Due to the separation of the control plane and data plane, system operation and maintenance become more centralized and efficient. The management center module can centrally manage policies and parameters, while data plane transmission tasks can be executed automatically, reducing the complexity and workload of operation and maintenance. Attached Figure Description

[0045] Figure 1 This is a schematic diagram of the domain P2P system of this invention;

[0046] Figure 2 This is a schematic diagram illustrating the separation of the control plane and data plane in this invention. Detailed Implementation

[0047] To make the objectives, technical solutions, and advantages of the present invention clear and complete, the embodiments of the present invention will be further described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are only some, not all, embodiments of the present invention, and are merely illustrative of the embodiments of the present invention. They are not intended to limit the embodiments of the present invention. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0048] Example 1: This invention provides a technical solution: a government data sharing and exchange system based on multi-domain P2P, the system comprising:

[0049] The control plane is used to maintain basic data, define strategies and parameters, and monitor the execution process; the control plane includes:

[0050] The management center module is used for the operation and configuration of the government data sharing and exchange system under the domain management. The management center module includes: a connector node control unit, used for the registration, authentication and monitoring of connector nodes in the system; and a digital identity management unit, used for managing the digital identities of users and connectors.

[0051] The approval module is used to manage the approval process for data sharing requests.

[0052] The data plane performs data retrieval, transmission, and publication according to the policies and parameters of the control plane; the data plane includes:

[0053] The connector module is used to enable data exchange and communication between nodes. Connectors include: data users, nodes that can only access and use data; data providers, nodes that can provide data to the network; data providers and users, nodes that can both provide and use data; data storage providers, nodes that acquire data and store copies of the data for users to use; and gateway connectors, nodes that provide an API gateway for other clients that do not have connectors installed.

[0054] Connectors are categorized by their identity and permission types: ordinary connectors, which can only access resources with the lowest possible permissions; trusted connectors, which are authenticated and trusted; super connectors, which have the highest permissions and can configure shared domains, trusted connectors, and bootstrap connectors; and bootstrap connectors, which are responsible for guiding new nodes to join the P2P domain.

[0055] The system configures each connector with a key pair conforming to the national cryptographic algorithm, including a public key and a private key, for authentication and data encryption. The system uses a distributed hash table (DHT) to register and manage the connector's public key, IP address, and digital identity. The system discovers and routes connectors through ConnectorID, which is generated based on the connector's public key and is used to determine the source and destination of data packets. The system allows connectors to be categorized and searched by setting tags, such as topic tags, industry tags, storage tags, and credit tags.

[0056] The connector module includes a networking unit, a content addressing unit, a content routing unit, a security authentication unit, a transmission unit, a publishing unit, and a gateway (API Gateway) unit.

[0057] The system includes an application system module for providing and requesting specific government data, including:

[0058] The data provider unit is responsible for publishing data resources;

[0059] The data requester unit is responsible for requesting data resources.

[0060] The system adopts a multi-domain P2P topology architecture, with connectors set in one or more shared domains according to permissions and topics.

[0061] Example 2, see attached document Figure 1 Based on Example 1, a schematic diagram of a multi-domain P2P-based government data sharing and exchange system is proposed, which includes the following modules:

[0062] Management Center:

[0063] The management center is responsible for the management and monitoring of the entire system, including strategy formulation, monitoring of the execution process, and system maintenance.

[0064] Approval Center:

[0065] The approval center is responsible for approving data sharing requests and ensuring that all data sharing requests comply with relevant policies and regulations.

[0066] Shared domain:

[0067] The shared domain proposed in this invention is a logical area divided within a multi-domain P2P system to achieve a specific data sharing purpose. Each shared domain contains a set of connectors, which can be data providers, data consumers, or both. The shared domain is designed to facilitate efficient sharing and secure exchange of data within the domain. Each shared domain can have its own management policies and security protocols, autonomously managing data sharing activities within the domain. Shared domains are independent of each other; activities within one domain do not directly affect other domains. The system can be expanded by adding new shared domains to accommodate growing data sharing needs. Shared domains can be adjusted as needed, including adding or removing connectors within the domain, or changing the domain's management policies.

[0068] Shared domain 1: contains connectors 101, 102, 201, 202, and boot connector 001.

[0069] Shared domain 2: includes connectors 203, 204, 301, 305, and boot connector 204.

[0070] Shared domain 3: includes connectors 301 and 305, and boot connector 104.

[0071] Public domain: Represents the public domain in the system, used as a default domain for all connectors.

[0072] Connector:

[0073] Connectors 101-305 represent the nodes of various data providers and data requesters in the system. They are divided into ordinary connectors, boot connectors, and storage connectors, and perform data exchange according to the data sharing and exchange strategy.

[0074] Boot connector:

[0075] Bootstrap connectors 001, 104, and 204 are bootstrap nodes set up in each shared domain, responsible for guiding new nodes to join the P2P domain and conducting initial data exchange and management.

[0076] Storage connector:

[0077] Storage connectors 103 and 205 act as local caches for shareable storage resources in a multi-domain P2P government data sharing and exchange system, providing efficient data retrieval and access services.

[0078] Storage connectors play a crucial role in multi-domain P2P government data sharing and exchange systems, acting as local caches of shareable storage resources. These connectors are distributed across different shared domains to provide efficient data retrieval and access services. In this embodiment, when connector 101 needs to query specific content, the system first uses content addressing technology to retrieve data from the nearest storage connector 103. This design reduces reliance on remote storage resources and improves the speed and efficiency of data retrieval. Through specific content routing algorithms, the system can also retrieve data from nearby storage connectors (such as 205 or 301) in other shared domains if the required data is not available in its own domain. This algorithm optimizes the data retrieval path, ensuring fast access to the required data even in cross-domain scenarios. The design of the storage connectors ensures that connectors within a domain prioritize retrieving data from their own shared domain or nearby shared domains. This strategy not only improves the speed of data access but also reduces the burden on the system's central node, thereby enhancing the stability and reliability of the entire system. By implementing this intelligent retrieval strategy based on geographic location or network topology, the system can more effectively manage and allocate data resources, optimizing the user experience.

[0079] See attached document Figure 2 As shown, this demonstrates the separation architecture of the control plane and data plane in the government data sharing system, clearly distinguishing the responsibilities of system management and data transmission.

[0080] The control plane is responsible for policy formulation, permission allocation, and system monitoring, while the data plane executes specific data exchange tasks according to the guidance of the control plane.

[0081] Example 3, based on the previous examples, proposes a multi-domain P2P-based government data sharing and exchange method, applied to a multi-domain P2P-based government data sharing and exchange system. The method includes the following steps:

[0082] The control plane maintains basic data, defines policies and parameters, and monitors the execution process; further including:

[0083] The operation and configuration of the government data sharing and exchange system are managed by domain through the management center module;

[0084] The approval process for data sharing requests is managed through an approval module to ensure the security and compliance of data sharing.

[0085] In the data plane, data retrieval, transmission, and publication are performed according to the policies and parameters defined in the control plane. The connector module in the data plane execution steps enables data exchange and communication between nodes, specifically including:

[0086] Constructing a multi-domain P2P network topology using networking units;

[0087] Accurate data location and routing are achieved through content addressing units and content routing units;

[0088] Use a secure authentication unit to authenticate nodes and encrypt data;

[0089] Reliable data transmission, publishing, and API access are achieved through transmission units, publishing units, and gateway units.

[0090] The method also includes operational steps for application system modules, used for specific government data provision and request, including:

[0091] The data provider unit publishes data resources for other nodes to retrieve and use;

[0092] The data requesting unit requests data resources from the data providing unit and receives the returned data.

[0093] The method also includes the following steps:

[0094] A multi-domain P2P topology architecture is adopted, and connectors are set in one or more shared domains according to permissions and topics;

[0095] Configure all connectors with key pairs conforming to Chinese cryptographic algorithms, including public and private keys, for authentication and data encryption;

[0096] Utilize distributed hash tables for the registration and management of connectors' public keys, IP addresses, and digital identities;

[0097] Connectors are discovered and routed using ConnectorIDs generated based on the connector's public key, thus determining the source and destination of data packets;

[0098] Connectors can be categorized and searched by setting tags, such as topic tags, industry tags, storage tags, and credit tags, thereby improving the efficiency and accuracy of data sharing and exchange.

[0099] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A government data sharing and exchange system based on multi-domain P2P, characterized in that: The system includes: The control plane is used to maintain basic data, define strategies and parameters, and monitor the execution process; The data plane performs data retrieval, transmission, and publication based on the strategies and parameters of the control plane. The control plane further includes: The management center module is used for the operation and configuration of the government data sharing and exchange system under the domain-specific management system; The approval module is used to manage the approval process for data sharing requests; The management center module also includes a connector node control unit for managing the registration, authentication, and monitoring of connector nodes in the system; and a digital identity management unit for managing the digital identities of users and connectors. The data plane includes a connector module, which is used to realize data exchange and communication between nodes. Specifically, it includes a networking unit, a content addressing unit, a content routing unit, a security authentication unit, a transmission unit, a publishing unit, and a gateway unit. The system also includes an application system module for specific government data provision and request, including data provider units and data requester units; The system adopts a multi-domain P2P topology architecture. Connectors are set in one or more shared domains according to permissions and topics. Connector types include data users, data providers, data providers and users, data storage providers, and gateway connectors. Connectors are divided into ordinary connectors, trusted connectors, super connectors, and bootstrap connectors according to identity and permission types. The system configures a key pair conforming to the national cryptographic algorithm for all connectors, including a public key and a private key, for authentication and data encryption; it uses a distributed hash table to register and manage the public key, IP address, and digital identity of connectors; it discovers and routes connectors through ConnectorID generated based on the connector's public key; and it allows connectors to be classified and searched by setting tags, such as topic tags, industry tags, storage tags, and credit tags.

2. A method for sharing and exchanging government data based on multi-domain P2P, applied to the government data sharing and exchange system based on multi-domain P2P as described in claim 1, characterized in that: The method includes the following steps: Maintain basic data, define policies and parameters, and monitor the execution process in the control plane; In the data plane, data retrieval, transmission, and publication are performed according to the strategies and parameters defined in the control plane. Control plane management steps further include: The operation and configuration of the government data sharing and exchange system are managed by domain through the management center module; The approval process for data sharing requests is managed through an approval module to ensure the security and compliance of data sharing. The connector module in the data plane execution step enables data exchange and communication between nodes, specifically including: Constructing a multi-domain P2P network topology using networking units; Accurate data location and routing are achieved through content addressing units and content routing units; Use a secure authentication unit to authenticate nodes and encrypt data; Reliable data transmission, publishing, and API access are achieved through transmission units, publishing units, and gateway units. The method also includes operational steps for application system modules, used for specific government data provision and request, including: The data provider unit publishes data resources for other nodes to retrieve and use; The data requesting unit requests data resources from the data providing unit and receives the returned data; The method also includes the following steps: A multi-domain P2P topology architecture is adopted, and connectors are set in one or more shared domains according to permissions and topics; Configure all connectors with key pairs conforming to Chinese cryptographic algorithms, including public and private keys, for authentication and data encryption; Utilize distributed hash tables for the registration and management of connectors' public keys, IP addresses, and digital identities; Connectors are discovered and routed using ConnectorIDs generated based on the connector's public key, thus determining the source and destination of data packets; Connectors can be categorized and searched by setting tags, such as topic tags, industry tags, storage tags, and credit tags, thereby improving the efficiency and accuracy of data sharing and exchange.

Images