Judicial data collaboration method and system based on distributed deployment

By utilizing distributed deployment and container cloud platform technologies, the problems of data silos and consistency in judicial data collaboration systems have been solved, enabling secure aggregation and collaboration of cross-departmental data and improving the intelligence and accuracy of data management.

CN118967074APending Publication Date: 2024-11-15SHANGHAI JIAOTONG UNIV
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202410244606.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-03-05
Publication Date
2024-11-15

AI Technical Summary

Technical Problem

Existing judicial data collaboration systems suffer from insufficient systematicness, intelligence, and accuracy in cross-departmental collaboration. They are characterized by data silos, inconsistent standards, inability to physically aggregate data due to data security constraints, inability to connect business processes between departments, and lack of data consistency guarantees.

Method used

A distributed deployment-based judicial data collaboration approach is adopted, which manages distributed nodes through a central hub node, uses meta-hash algorithms and multi-master node replication technology to achieve data synchronization and load balancing, and combines container cloud platform technology for deployment to achieve secure data aggregation and cross-departmental collaboration.

Benefits of technology

Under data security constraints, cross-judicial data aggregation and integration can be achieved, ensuring the consistency and security of data exchange, reducing operating and management costs, and improving the reliability and observability of data throughout its entire lifecycle.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118967074A_ABST
    Figure CN118967074A_ABST
Patent Text Reader

Abstract

The invention discloses a judicial data collaboration method and system based on distributed deployment, and relates to the technical field of big data, and the method comprises the steps: obtaining a business collaboration document, determining a target distributed node corresponding to the category of the business collaboration document according to a load balancing rule, the business collaboration document is stored in the target distributed node; and obtaining collaborative metadata corresponding to the business collaborative document, storing the collaborative metadata by a target central hub node to which the target distributed node belongs, and updating a metadata dynamic directory according to the collaborative metadata, the metadata dynamic directory stores metadata information of all collaborative metadata stored in the target central hub node; and the target central hub node sends the collaborative metadata and the updated metadata dynamic directory to other central hub nodes in the judicial data collaborative system. And intelligent management and collaboration of judicial data intelligence and precision are realized.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of big data technology, and in particular to a judicial data collaboration method and system based on distributed deployment. Background Art

[0002] With the vigorous development of the Internet and the new generation of information technology and applications, how to achieve reliable, manageable and controllable data interconnection and intelligent applications has become a world-class problem for the industrial chain, value chain and ecosystem of the digital society. It is urgent to establish a data-centric data mesh protocol stack and technical architecture to promote the transformation of cyberspace from Internet-based to data mesh-based. Data mesh technology focuses on providing a distributed data storage and management framework. Its core is to realize data virtualization and distributed processing, so that data resources stored in geographically dispersed locations can be accessed and processed as if they were stored locally. By providing a unified data access interface and data management strategy, data mesh allows users to access, analyze, share and manage distributed data sets without having to worry about the physical storage location of the data.

[0003] In the judicial field, my country is gradually deepening the research and practice of key technologies of data fusion in the data grid environment. At present, the informationization and intelligence of the judicial data field have made great progress. The domestic judicial departments have carried out the construction of data grid big data platforms and carried out preliminary customized development and application at the level of cross-departmental collaboration. For example, the judicial business collaboration support platform of the judicial administrative agency gathers 1 billion business data, realizes data collaboration, process collaboration and business collaboration, and has carried out promotion and application. This kind of cross-departmental big data collaboration platform breaks the information barriers between public security, procuratorial, judicial and other political and legal units, and significantly improves the quality and efficiency of case handling.

[0004] However, the above existing technologies are insufficient in terms of systematization, intelligence and accuracy in judicial collaboration. Data in various departments are isolated, data standards are not unified, data is not centralized, large-scale cross-departmental data cannot be physically aggregated under data security constraints, and the data aggregation and fusion mechanism of the original systems, data middle platforms and applications of various departments is missing. The business processes between departments cannot be connected, and the data consistency of cross-departmental data exchange in the process of business collaboration is not guaranteed.

[0005] Therefore, technicians in this field are committed to developing a data collaboration method and system for a judicial cloud environment. Summary of the invention

[0006] In view of the above-mentioned defects of the prior art, the technical problem to be solved by the present invention is to realize intelligent and precise management and coordination of judicial data.

[0007] To achieve the above-mentioned object, the present invention provides a judicial data collaboration method based on distributed deployment, which is applied to a judicial data collaboration system based on distributed deployment, wherein the judicial data collaboration system includes multiple central hub nodes and multiple distributed nodes managed by each central hub node, and the method includes:

[0008] Acquire a business collaboration document, determine a target distributed node corresponding to the category to which the business collaboration document belongs according to a load balancing rule, and store the business collaboration document in the target distributed node;

[0009] Acquire the collaborative metadata corresponding to the business collaborative document, the target central hub node to which the target distributed node belongs stores the collaborative metadata, and updates the metadata dynamic directory according to the collaborative metadata, the metadata dynamic directory stores the metadata information of all the collaborative metadata stored in the target central hub node;

[0010] The target central hub node sends the collaborative metadata and the updated metadata dynamic directory to other central hub nodes in the judicial data collaborative system.

[0011] In a preferred embodiment of the present invention, the method further comprises:

[0012] Acquire service registration data, the service registration data corresponding to all collaborative metadata stored in the target central hub node, and configure access permission information for each collaborative metadata;

[0013] In response to a service registration data viewing request from a user, the service registration data corresponding to the access permission is disclosed to the user according to the access permission of the user.

[0014] In a preferred embodiment of the present invention, obtaining the collaboration metadata corresponding to the business collaboration document includes:

[0015] Ingesting metadata from the business collaboration document through a command line interface or through a front-end interface;

[0016] Verify whether the acquired metadata complies with the collaborative metadata standard. When the acquired metadata complies with the collaborative metadata standard, use the acquired metadata as the collaborative metadata corresponding to the business collaborative document.

[0017] In a preferred embodiment of the present invention, the method further comprises: periodically or triggeringly performing data synchronization verification on the data stored in the multiple central hub nodes in the judicial data collaborative system;

[0018] The data synchronization check includes at least one of the following checks: consistency check, data traceability check and polling monitoring;

[0019] The consistency check includes: during the data migration process, the migration target central hub node analyzes the log record of the data change of the current central hub node, queries the relevant data record in the migration source central hub node according to the data sequence number, and compares the data content to determine whether there is a data error. When there is a data error, the data error is repaired according to the data record of the migration source central hub node;

[0020] Data traceability detection includes: recording and tracking the source, change history, transmission path, browsing and calling of data received and stored by the central hub node through annotation, tracing the entire life cycle of the data circulating in the judicial data collaborative system, and determining the reliability, accuracy and compliance of the data;

[0021] Polling monitoring includes: reading the data stored in the central hub node, and determining the data volume, real-time performance, data summary, and data lineage of the central hub node according to pre-set detection rules, and measuring and evaluating the operating status, behavior, and performance of the judicial data collaborative system.

[0022] In a preferred embodiment of the present invention, determining a target distributed node corresponding to the category to which the business collaboration document belongs according to the load balancing rule includes:

[0023] Using a meta-hash algorithm, each distributed node corresponding to the category to which the business collaboration document belongs is mapped onto a hash space ring, and a unique identifier of each distributed node or a hash value of each distributed node is used as the position of the distributed node on the hash space ring;

[0024] Create multiple virtual nodes for each distributed node, and each virtual node is evenly distributed on the hash space ring;

[0025] When the business collaboration document obtains a hash value through the hash algorithm, the first node greater than or equal to the hash value is found clockwise on the hash space ring, and this node is used as the target distributed node corresponding to the category to which the business collaboration document belongs.

[0026] In a preferred embodiment of the present invention, the method further comprises:

[0027] When the number of distributed nodes in the judicial data collaborative system changes, the mapping relationship between adjacent distributed nodes and hash space rings is adjusted using a meta-hash algorithm, and whether to migrate data is determined according to a load balancing rule;

[0028] When determining the data to be migrated, the amount of data to be migrated and the target node to be migrated are determined based on the hash algorithm;

[0029] The migrated data is migrated to the target node based on the best distance vector routing through the Border Gateway Protocol.

[0030] In a preferred embodiment of the present invention, the method further comprises:

[0031] Container cloud platform technology is used to deploy components or modules of applications or operating software in each central hub node and each distributed node in the judicial data collaborative system. The components or modules deployed at each central hub node are the same or different, and the components or modules deployed at each distributed node are the same or different.

[0032] On the other hand, the present invention also provides a judicial data collaboration system based on distributed deployment, including: multiple central hub nodes, and multiple distributed nodes managed by each central hub node; each central hub node directly communicates with all other central hub nodes;

[0033] The distributed nodes are used to store business collaboration documents corresponding to their categories;

[0034] The central hub node is used to store the collaborative metadata corresponding to the business collaborative documents of each distributed node managed, and update the metadata dynamic directory according to the collaborative metadata, and the metadata dynamic directory stores the metadata information of all collaborative metadata stored in the target central hub node;

[0035] Each central hub node sends the collaborative metadata and updated metadata dynamic directory saved by the current central hub node to other central hub nodes in the judicial data collaborative system.

[0036] The third aspect of the present application also provides a computing device, comprising: at least one processor and a memory storing a computer program; when the computer program is read and executed by the processor, the electronic device executes the above method.

[0037] The fourth aspect of the present application also provides a readable storage medium storing a computer program. When the computer program is read and executed by an electronic device, the electronic device executes the above method.

[0038] The judicial data collaboration method and system based on distributed deployment provided by the present invention have the following technical effects:

[0039] The present invention is based on the principle of physical dispersion and logical concentration, and realizes a judicial data collaboration method and system based on distributed deployment. The central hub node can be deployed in each judicial department. Each central hub node manages the corresponding multiple distributed nodes, and the data synchronization between the central hub nodes is realized through multi-master node replication technology. The original business collaboration document data used in the business collaboration process is stored in each distributed node, and the central hub node stores the metadata of the original business collaboration document data, so that the data across judicial departments can be aggregated and integrated in each department under the data security constraint. When exchanging data across judicial departments in the business collaboration process, data synchronization verification including consistency verification, data traceability detection and polling monitoring is performed. The deployment of the central hub node and the distributed nodes is realized through a distributed deployment solution based on the container cloud platform, which ensures the data security in the business collaboration process, realizes data intercommunication between the central hub nodes, improves the reliability of identity authentication, and reduces the maintenance, operation and management costs of the data throughout its life cycle.

[0040] The concept, specific structure and technical effects of the present invention will be further described below in conjunction with the accompanying drawings to fully understand the purpose, characteristics and effects of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1 It is a structural diagram of a preferred embodiment of the judicial data collaboration system based on distributed deployment according to an embodiment of the present invention;

[0042] Figure 2 It is a flow chart of a preferred embodiment of the judicial data collaboration method based on distributed deployment according to an embodiment of the present invention;

[0043] Figure 3 is a schematic diagram of a load balancing strategy used in an embodiment of the present invention;

[0044] Figure 4 is a schematic diagram of a collaborative metadata standard used in an embodiment of the present invention;

[0045] Figure 5 is a schematic diagram of collaborative metadata used in an embodiment of the present invention;

[0046] Figure 6 It is a schematic diagram of the node container set encapsulation process in the distributed deployment process based on the container cloud platform according to an embodiment of the present invention;

[0047] Figure 7 It is a schematic diagram of distributed data storage used in distributed deployment based on a container cloud platform according to an embodiment of the present invention;

[0048] Figure 8 This is a schematic diagram of the communication process within the same node in the distributed deployment of an embodiment of the present invention;

[0049] Fig. 9 The figure is a schematic diagram of the distributed deployment cross-node communication process of an embodiment of the present invention. DETAILED DESCRIPTION

[0050] The following describes the embodiments of the present invention by specific examples, and those skilled in the art can easily understand other advantages and effects of the present invention from the contents disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present invention. It should be noted that the following embodiments and features in the embodiments can be combined with each other without conflict.

[0051] It should be noted that the illustrations provided in the following embodiments are only used to illustrate the basic concept of the present invention in a schematic manner, and thus the illustrations only show components related to the present invention rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed arbitrarily, and the component layout may also be more complicated.

[0052] While some exemplary embodiments of the present invention have been described for the purpose of illustration, it should be understood that the present invention may be implemented in other ways not specifically shown in the drawings.

[0053] Figure 1 FIG. 1 is a schematic diagram of a preferred embodiment of a judicial data collaboration system based on distributed deployment according to an embodiment of the present invention. Figure 1 As shown, the judicial data collaboration system based on distributed deployment of the example of the present invention includes: multiple central hub nodes, and multiple distributed nodes managed by each central hub node; each central hub node directly communicates with all other central hub nodes;

[0054] The distributed nodes are used to store business collaboration documents corresponding to their categories;

[0055] The central hub node is used to store the collaborative metadata corresponding to the business collaborative documents of each distributed node managed, and update the metadata dynamic directory according to the collaborative metadata, and the metadata dynamic directory stores the metadata information of all collaborative metadata stored in the target central hub node;

[0056] Each central hub node sends the collaborative metadata and updated metadata dynamic directory saved by the current central hub node to other central hub nodes in the judicial data collaborative system.

[0057] In the embodiment of the present invention, each distributed node stores original business collaboration document data used in the business collaboration process, and the central hub node stores metadata of the original business collaboration document data.

[0058] In order to improve the stability of the judicial data collaboration system, the embodiment of the present invention configures central hub nodes in each judicial department, and the data synchronization between the central hub nodes adopts a multi-master node replication solution. Multi-master node replication is a database replication architecture in which there are multiple master nodes, each of which can independently process read and write requests and propagate its changes to other master nodes. This architecture allows high availability and scalability in a distributed environment while providing better performance and fault tolerance. In the embodiment of the present invention, the central hub node corresponds to the master node in the multi-master node replication solution. Multi-master node replication solves these problems by introducing multiple master nodes. Each master node has read and write permissions, can independently receive and process read and write requests from clients, and propagate changes to other master nodes.

[0059] Figure 2 The flowchart of a preferred embodiment of a judicial data collaboration method based on distributed deployment according to an embodiment of the present invention is shown below. The judicial data collaboration method based on distributed deployment is executed in an electronic device. The electronic device can be a server or a terminal device, wherein the server can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides cloud computing services. The terminal device can be a smart phone, a tablet computer, a laptop computer, a desktop computer, etc., but is not limited thereto. The terminal device and the server can be directly or indirectly connected via wired or wireless communication, and the embodiment of the present invention does not limit this. Figure 1 As shown, the judicial data collaboration method based on distributed deployment begins with step S110.

[0060] In step S110, a business collaboration document is obtained, a target distributed node corresponding to the category to which the business collaboration document belongs is determined according to a load balancing rule, and the business collaboration document is stored in the target distributed node.

[0061] In the embodiment of the present invention, the judicial data collaboration system based on distributed deployment includes two main parts: a central hub node and a distributed node. The central hub node of the distributed deployment judicial data collaboration system serves as a fusion big data center, and each distributed node stores the original business collaboration document data used in the business collaboration process. Taking the data collaboration scenario for the judicial department as an example, the central hub nodes of each institution are constructed in the court, the procuratorate and the judicial administration department, and each central hub node manages one or more distributed nodes under each institution. The distributed nodes of each institution include branches at all levels under the institution, that is, the distributed nodes of the court are deployed in the high people's courts, intermediate people's courts and grassroots people's courts, the distributed nodes of the procuratorate are deployed in the local people's procuratorates at all levels and special people's procuratorates, and the distributed nodes of the judicial administration department are deployed in the judicial departments of provinces, autonomous regions, and municipalities directly under the central government and the judicial bureaus of autonomous regions, cities, regions, autonomous prefectures, and leagues. There is only one central hub node in each institution, for example, the central hub node of the court is deployed in the Supreme People's Court, the central hub node of the procuratorate is deployed in the Supreme People's Procuratorate, and the central hub node of the judicial administration department is deployed in the Ministry of Justice.

[0062] In an embodiment of the present invention, a user (a person with data upload authority, such as a staff member of a judicial department) can upload a business collaboration document through a client or server. After obtaining the business collaboration document, since a central hub node manages the corresponding distributed nodes, the obtained business collaboration document is allocated and saved to a distributed node (target distributed node) of the corresponding category according to the load balancing rule. Taking the data collaboration scenario for the judicial department as an example, the business collaboration documents of the court are saved in the distributed nodes corresponding to the court according to the load balancing rule, the business collaboration documents of the procuratorate are saved in the distributed nodes corresponding to the procuratorate according to the load balancing rule, and the business collaboration documents of the judicial administrative department are saved in the distributed nodes corresponding to the judicial administrative department according to the load balancing rule.

[0063] In an embodiment of the present invention, distributed nodes are deployed in a container cloud platform. The container cloud platform is a cloud computing platform based on container technology, which is designed to simplify the deployment, management and expansion of applications. The deployment method of the container cloud platform packages the front-end, back-end, relational and time-series databases and all their dependencies in a lightweight, portable and scalable manner, and encapsulates them as containers. Distributed deployment refers to deploying different components or modules of an application or system on multiple computing nodes or servers to achieve resource sharing, load balancing and improved fault tolerance.

[0064] Among them, the container is a virtualization technology used to encapsulate an application and its dependencies in an isolated operating environment. The container can be regarded as an independently running environment, which contains the application and its related libraries, dependencies and configuration files. The container isolates the resources between the application and its host system and other containers, so that the application can run consistently in different environments without being affected by the underlying system. Each distributed node in the embodiment of the present invention corresponds to a node of the container cloud platform, and all nodes belong to the same containerized computer cluster. Containerized computer cluster refers to combining container technology with cluster management technology to form a cluster of multiple computers (nodes) for hosting and managing large-scale container instances. Through the containerized computer cluster, efficient container deployment, elastic scaling, load balancing and communication between containers can be achieved. Each distributed node in the containerized computer cluster deploys a container set containing multiple containers, which realizes the rapid deployment of applications.

[0065] Figure 3 The schematic diagram of the load balancing strategy used in the present invention can be operated by a controller in a special container group. The controller includes a set of rules for managing traffic and a daemon process that applies these rules. The controller has a built-in load balancing feature, and more complex load balancing rules can be formulated on this basis to meet the load balancing function and requirements of the distributed judicial data collaboration system. The controller is relied on to read the rules and then schedule traffic resources according to the route. The controller can be implemented by any service program with a reverse proxy function, running on the cluster in the form of a container group. It can communicate directly with other container groups on the cluster, allowing the user's traffic to be directly scheduled to the back-end container group through the controller. Reverse proxy is a network service architecture mode for communication between a proxy server and a client. A forward proxy is a proxy client sending a request to a server, while a reverse proxy is a proxy server receiving a request from a client, forwarding the request to a back-end server, and then returning a response to the client. After reading the routing rules, the controller converts the rules into configuration files to implement traffic scheduling according to the rules. At the same time, it will also perceive the changes in the container group corresponding to the back-end service node in real time. When the container group changes, the controller will combine the rules again to complete the dynamic update of the configuration.

[0066] In the embodiment of the present invention, determining a target distributed node corresponding to the category to which the business collaboration document belongs according to the load balancing rule includes:

[0067] Using a meta-hash algorithm, each distributed node corresponding to the category to which the business collaboration document belongs is mapped onto a hash space ring, and a unique identifier of each distributed node or a hash value of each distributed node is used as the position of the distributed node on the hash space ring;

[0068] Create multiple virtual nodes for each distributed node, and each virtual node is evenly distributed on the hash space ring;

[0069] When the business collaboration document obtains a hash value through the hash algorithm, the first node greater than or equal to the hash value is found clockwise on the hash space ring, and this node is used as the target distributed node corresponding to the category to which the business collaboration document belongs.

[0070] The judicial data collaboration method based on distributed deployment in the embodiment of the present invention also includes:

[0071] When the number of distributed nodes in the judicial data collaborative system changes, the mapping relationship between adjacent distributed nodes and hash space rings is adjusted using a meta-hash algorithm, and whether to migrate data is determined according to a load balancing rule;

[0072] When determining the data to be migrated, the amount of data to be migrated and the target node to be migrated are determined based on the hash algorithm;

[0073] The migrated data is migrated to the target node based on the best distance vector routing through the Border Gateway Protocol.

[0074] The meta-hash algorithm is an algorithm for data sharding and load balancing in distributed deployment. It solves the problem that traditional hash algorithms may cause data migration when nodes are dynamically increased or decreased, and provides an efficient way to distribute data. The meta-hash algorithm maps hash values ​​to a ring-shaped hash space. The hash space refers to the range of possible hash values ​​in the hash algorithm. In the hash algorithm, the input data is calculated by a hash function to obtain a hash value, which is usually a binary string of fixed length. The hash space is composed of these binary strings, which represents all possible hash values. The meta-hash algorithm maps each distributed node to the hash space ring, and the unique identifier of the distributed node or the hash value of the distributed node can be used as the position of the distributed node on the ring. The meta-hash algorithm creates multiple virtual nodes for each distributed node, and each virtual node is evenly distributed on the hash space ring. When the data is calculated by the hash algorithm to obtain a hash value, the first node that is greater than or equal to the hash value is found clockwise on the hash space ring, which is the distributed node to which the data belongs. Due to the existence of virtual nodes, when the number of distributed nodes changes, it is only necessary to adjust the data mapping relationship between adjacent distributed nodes without remapping all data, thereby achieving load balancing and dynamic expansion and contraction.

[0075] In step S120, the collaborative metadata corresponding to the business collaborative document is obtained, the target central hub node to which the target distributed node belongs stores the collaborative metadata, and updates the metadata dynamic directory based on the collaborative metadata. The metadata dynamic directory stores metadata information of all collaborative metadata stored in the target central hub node.

[0076] In the embodiment of the present invention, the central hub node stores metadata of the original business collaboration document data. Metadata, also known as intermediary data or relay data, is data used to describe data, mainly information describing data attributes, and is used to support functions such as indicating storage location, historical data, resource search, and file records.

[0077] In the embodiment of the present invention, obtaining the collaboration metadata corresponding to the business collaboration document in step S120 includes:

[0078] Ingesting metadata from the business collaboration document through a command line interface or through a front-end interface;

[0079] Verify whether the acquired metadata complies with the collaborative metadata standard. When the acquired metadata complies with the collaborative metadata standard, use the acquired metadata as the collaborative metadata corresponding to the business collaborative document.

[0080] In an embodiment of the present invention, the collaborative metadata corresponding to the business collaborative document can be obtained by receiving a metadata file uploaded by a user, verifying that the ingested metadata content meets the collaborative metadata standard, and then using the ingested metadata as the collaborative metadata corresponding to the business collaborative document (if the ingested metadata does not meet the collaborative metadata standard, it may be due to the lack of necessary data or other reasons. At this time, the metadata can be prompted and re-ingested, or when the necessary data is missing, the ingested metadata is supplemented according to the preset rules to make it meet the collaborative metadata standard), and business scenarios and other information are extracted from the collaborative metadata to update the metadata dynamic directory. The metadata dynamic directory is a directory structure used to store and manage data in a computer system, which is characterized by being able to dynamically adjust and change the structure and content of the directory as needed. The creation of the dynamic directory is based on multiple rules such as user input, data attributes and upload time. The directory structure is adjusted and updated according to the actual upload situation, which is more flexible and adaptable to business needs. The directory collects and manages metadata information such as data sources, field definitions and data relationships, acts as a storage database for metadata, and builds a standardized data index for storage. Each document establishes a connection between a set of keys (names of fields or attributes) and their corresponding values ​​(strings, numbers, Boolean values, dates, value groups, geographic locations or other types of data). After the index is completed, users can perform full-text search based on keywords, tags, data scenarios, data publishers, etc. Full-text search refers to the method of extracting part of the information in unstructured data, reorganizing it to make it have a certain structure, and then searching for this structured data.

[0081] The central hub node can realize metadata import, dynamic catalog generation and service registration management. Metadata import is to ingest the collaborative metadata of business collaborative documents from the data source, that is, the database of the distributed nodes of each institution. There are two main methods of ingesting metadata, namely, through the command line interface method and through the front-end interface method. On the basis of ensuring that the uploaded file format complies with the collaborative metadata standard, the method through the front-end interface means that the user logs in to the web front-end interface of the central hub node to upload files that comply with the collaborative metadata standard, and the method through the command line interface means that the user enters commands in the command line terminal through an open interface to complete the upload of metadata that complies with the collaborative metadata standard.

[0082] When developing collaborative metadata standards, it is necessary to determine the purpose, scope, and objectives of metadata, as well as the business processes and data requirements to be supported, determine the types of metadata that need to be collected and managed, develop consistent naming conventions for each element in the standard, and define the necessary attributes for each metadata type to meet the goals and needs of metadata management in order to better organize and manage metadata.

[0083] In the embodiment of the present invention, taking the data collaboration scenario for the judicial department as an example, the collaborative metadata standard may include information such as "business scenario", "publisher", "data name", "data type", "data life cycle", and "catalog field". Figure 4 shown.

[0084] like Figure 5 As shown, in the "Business Scenario" column, you need to select the corresponding business scenario name from the six items of public prosecution request, case supervision, commutation of sentence and parole, delivery for execution, compulsory medical treatment, and legal aid, and fill in "commutation of sentence and parole" in this embodiment.

[0085] In the "Publisher" column, you need to select the corresponding data publishing agency from the courts, procuratorates, and judicial administrative departments. In this embodiment, fill in "Judicial Administrative Department".

[0086] In the "Data Name" column, you need to fill in the specific name of the data collaboration content involved in the corresponding business, such as: basic case information, court hearing notice, case file, basic information of the criminal, etc. In this embodiment, fill in "Prison Admission Notice".

[0087] In the "Data Type" column, you need to fill in the data type of the business data, such as: database table, text file, video file, audio file. If multiple formats are involved, they are separated by Chinese commas. In this embodiment, fill in "Mixed Type".

[0088] In the "Data Life Cycle" column, you need to fill in the specific data involving the corresponding business process stage. In this embodiment, the full cycle is filled in.

[0089] The "Catalog Field" column may contain multiple sub-blocks, each of which corresponds to one of the collaborative data items in the collaborative content. In this embodiment, four fields, namely "Name", "Gender", "Detention Unit", and "Date of Prison Entry", are filled in.

[0090] The user interface layer of the central hub node of the embodiment of the present invention can adopt a front-end framework based on Vue and TypeScript.

[0091] Among them, Vue is a JavaScript front-end framework that builds user interfaces through componentization, allowing developers to more easily build maintainable and reusable code.

[0092] TypeScript is an open source programming language developed by Microsoft. It is a superset of JavaScript, which means that any valid JavaScript code is valid TypeScript code, but TypeScript adds static typing and some other new features to help developers build large and complex applications more easily. Static typing refers to the feature that in a programming language, the types of variables, function parameters, function return values, etc. are determined at compile time and remain unchanged at runtime. In a statically typed language, the type of a variable must be explicitly specified at the time of declaration, and its type cannot be changed in subsequent operations.

[0093] Among them, JavaScript is a scripting language widely used in web front-end development. It can be used to add interactivity and dynamism to web pages.

[0094] The user interface layer of the central hub node uses control components such as secondary encapsulation components, permission verification, and button-level permissions to build a large monitoring screen for business collaboration in the judicial environment with low code.

[0095] Secondary packaging refers to the process of repackaging and abstracting existing code or libraries in software development to provide simpler, easier-to-use, and higher-level interfaces or functions. It is a common development technique that aims to simplify the use of code and improve its reusability.

[0096] The large screen is a user interface for visualizing and monitoring data. It displays metadata, service registration data, and observability indicators stored in the central hub node through charts, graphs, tables, and other visual elements, allowing users to more easily analyze and understand the content in the platform. When users use the central hub node, the organization to which they belong will directly affect the platform content that users can access, and together with the user role, determine the user's authority to call data. The early warning notification component of the user interface layer can monitor the operation of the platform and the quality of metadata stored in the platform, and immediately notify users when data anomalies occur or exceed preset thresholds, detect problems in a timely manner, take action before the situation escalates, reduce fault recovery time, and minimize the impact and loss of abnormal data on smart judicial business collaboration.

[0097] In step S130, the target central hub node sends the collaborative metadata and the updated metadata dynamic directory to other central hub nodes in the judicial data collaborative system.

[0098] In the examples of the present invention, in order to achieve data synchronization, each central hub node can adopt an all-to-all topology. This can prevent the ring topology from affecting the data synchronization between other central hub nodes when a central hub node fails, thereby improving fault tolerance. The all-to-all topology refers to a network topology in which each node in the network can communicate directly with all other nodes. In the embodiment of the present invention, an all-to-all topology is adopted, and each central hub node is directly connected to other central hub nodes to form a fully connected network. This connection method allows any two central hub nodes to communicate directly without routing through other intermediate central hub nodes.

[0099] In addition, one of the challenges of multi-master node replication is conflict handling. Since each master node can receive write operations independently, that is, concurrent write operations on different master nodes may modify the same data, which will cause data modification conflicts. In order to solve the data modification conflict problem, in the embodiment of the present invention, according to the department to which the data is published, the central hub node through which the data write request passes is determined, that is, the write operation request of the collaborative metadata of a certain judicial department is uniformly received and executed by the central hub node of the judicial department, and other judicial departments do not have the authority to modify the collaborative metadata in the central hub node of the judicial department, thus avoiding the occurrence of asynchronous write conflicts.

[0100] The judicial data collaboration method based on distributed deployment in an embodiment of the present invention further includes:

[0101] Acquire service registration data, the service registration data corresponding to all collaborative metadata stored in the target central hub node, and configure access permission information for each collaborative metadata;

[0102] In response to a service registration data viewing request from a user, the service registration data corresponding to the access permission is disclosed to the user according to the access permission of the user.

[0103] In the embodiment of the present invention, the central hub node can realize the function of service registration management. During the specific operation, the user is required to upload the service registration data. The service registration data corresponds to the collaborative metadata one by one. The service registration data can store the distributed node information, interactive interface, interactive method and other contents of the business data corresponding to the collaborative metadata in each business unit, which is important information to support business collaboration. Unlike metadata that is open to all users, service registration data can only be viewed by authorized users. Taking the data collaboration scenario for the judicial department as an example, when a collaborative metadata is the collaborative metadata corresponding to the business collaboration document of the court, and the service registration data corresponding to this collaborative metadata is limited to the open rights to the procuratorate, the central hub node of the court and the central hub node of the procuratorate can both view the collaborative metadata and the corresponding service registration data, while the judicial central hub node can view the corresponding collaborative metadata but cannot view the service registration data.

[0104] The judicial data collaboration method based on distributed deployment in an embodiment of the present invention further includes:

[0105] Periodically or trigger-wise, perform data synchronization verification on the data stored in multiple central hub nodes in the judicial data collaboration system;

[0106] The data synchronization check includes at least one of the following checks: consistency check, data traceability check and polling monitoring;

[0107] The consistency check includes: during the data migration process, the migration target central hub node analyzes the log record of the data change of the current central hub node, queries the relevant data record in the migration source central hub node according to the data sequence number, and compares the data content to determine whether there is a data error. When there is a data error, the data error is repaired according to the data record of the migration source central hub node;

[0108] Data traceability detection includes: recording and tracking the source, change history, transmission path, browsing and calling of data received and stored by the central hub node through annotation, tracing the entire life cycle of the data circulating in the judicial data collaborative system, and determining the reliability, accuracy and compliance of the data;

[0109] Polling monitoring includes: reading the data stored in the central hub node, and determining the data volume, real-time performance, data summary, and data lineage of the central hub node according to pre-set detection rules, and measuring and evaluating the operating status, behavior, and performance of the judicial data collaborative system.

[0110] For the purpose of data quality detection, the central hub node of the embodiment of the present invention performs consistency verification, data traceability detection and automatic polling monitoring to ensure the data quality within the entire judicial data collaboration system based on distributed deployment.

[0111] The consistency check is mainly used to prevent data synchronization problems that occur during system data migration. The data migration of the central hub node includes data upload from distributed nodes to the central hub node and data replication between the central hub node and other central hub nodes. During the data migration process, data inconsistency may occur due to reasons such as some fields not being synchronized or data updates being out of order. Therefore, data consistency must be checked. The migration target database receives and parses log data about database changes, queries related data records in the source database according to the data sequence number, and compares the data content to promptly discover and repair data errors.

[0112] Data traceability detection records and tracks the source of data, change history, transmission path, browsing and calling status, etc. received and stored by the central hub node through annotation, and allows annotation and data to be transmitted together. Through data traceability, the central hub node maintenance personnel can trace the entire life cycle of the circulating data in the system, understand the reliability, accuracy and compliance of the data, and ensure the credibility of the system. The full life cycle of data refers to the entire process from data creation or acquisition to final processing and archiving, including the stages of data generation, storage, use, sharing, protection and destruction.

[0113] Polling monitoring uses a polling mechanism to periodically read observability indicators such as data volume, real-time performance, data summary, and data lineage from the data storage module. Observability indicators are indicators or metrics used to measure and evaluate the degree of observability of computing systems, applications, or services. Observability refers to the ability of the system's operating status, behavior, and performance to be effectively monitored, collected, analyzed, and understood. Data lineage refers to information that tracks and records the source, flow, and transformation process of data during the data lifecycle. It describes the data's transmission path, transformation operations, and associations at each stage, helping users understand the source, changes, and impact of data. Automatic polling monitoring automatically monitors data quality based on pre-set detection rules. The monitoring results are used to infer and estimate the state and quality of the data, and enable it to be quickly detected and located when anomalies occur. The early warning notification component of the user interface layer alerts relevant users to ensure the validity of the data and that data flow complies with the judicial process.

[0114] Before executing the judicial data collaboration method based on distributed deployment in the embodiment of the present invention, it is also necessary to:

[0115] Container cloud platform technology is used to deploy components or modules of applications or operating software in each central hub node and each distributed node in the judicial data collaborative system. The components or modules deployed at each central hub node are the same or different, and the components or modules deployed at each distributed node are the same or different.

[0116] Figure 6 The figure shows the process of encapsulating node container sets in the distributed deployment process of the container cloud platform. The containers in the container set are encapsulated with databases, back-end programs and front-end programs or projects. The operator is the system developer, the input is the development version code, and the output is the application encapsulated as a container set.

[0117] The encapsulated database is used as follows: load the container image corresponding to the decompressed tar file into the address, create a container, migrate the database from outside the container to inside the container, enter the database with administrator privileges, view the database information and create specific names required for front-end and back-end operation, and finally import the initial structured database file into the container.

[0118] The packaging process of the backend container is as follows. First, debug and build the backend application based on the framework Flask. Flask is a lightweight software tool using Python language. It provides a set of structures, patterns and tools to help developers organize and manage the code of web applications, handle HTTP data transmission protocol requests and responses, and interact with databases and other services. The framework deploys a high-performance server that communicates with the client and uses pre-derived child processes to handle concurrent requests. Write the environment configuration file required to create the container and the text file used to build the container image, place them in the root directory folder of the backend application, and use the command to package them into a container image. In the process of using the container image, it is necessary to specify the port outside the container to which the port in the container is mapped, establish the local storage mount of the log part, and enter the local server parameters. Local storage mounting is the process of connecting files or directories on the local computer to the inside of the container. It allows access to the file system on the host in the container, so that the container can read and write local files.

[0119] The static deployment of the front-end requires publishing the static files generated by the development process to the static server, combining the routing of the front-end and the server, and handling the cross-domain issues after the project is deployed. Routing refers to the process of transmitting data packets from the source address to the destination address according to specific rules or algorithms. Routing determines the path and forwarding method of data packets in the network to ensure that they can reach the destination correctly. The cross-domain problem after the project is deployed refers to the cross-domain restrictions encountered when a web page or web application loads resources (such as scripts, style sheets, fonts, images, etc.) in one domain (domain name, port, protocol combination) in a browser environment. Cross-domain restrictions are security restrictions imposed by the browser's same-origin policy. The same-origin policy requires that web pages can only interact with resources in the same domain, and cannot communicate directly with resources in other domains. The purpose of the same-origin policy is to prevent malicious scripts from obtaining users' sensitive data or performing malicious operations through cross-domain requests.

[0120] During the deployment of the container cloud platform, it is necessary to define the host name and host address of each distributed node, perform time synchronization between nodes, add bridge filtering and address forwarding functions, and pull container images. Bridge filtering is a basic function of bridge devices. It checks the source and destination MAC addresses of the data packet to decide whether to forward or discard the data packet. The address forwarding function is a function in network devices (such as routers and switches) that is used to forward received data packets from the source address to the destination address.

[0121] The container image includes control node components, API service entry components, cluster internal management control center, cluster distribution scheduler, cluster management command line tool set, load balancing components and node status manager.

[0122] A control node component refers to a node or component that is responsible for managing and controlling the entire system in a distributed deployment architecture.

[0123] The API service entry component refers to a component that serves as a unified entry point in a distributed deployment architecture to process and manage requests and responses for interface services.

[0124] A cluster is a distributed deployment architecture consisting of multiple computing nodes, which are connected through a network and share resources to achieve high performance and scalability. In order to effectively manage and coordinate the various nodes in the cluster, the cluster internal management and control center is responsible for managing and controlling the central components or nodes of the internal operation and resource management of the entire cluster.

[0125] In a distributed deployment architecture, the distribution and execution of tasks is a complex process involving multiple computing nodes, resource scheduling, task scheduling, etc. The role of the cluster distribution scheduler is to distribute and schedule tasks to ensure that tasks can be executed on appropriate computing nodes in the cluster and meet the utilization and performance requirements of system resources.

[0126] The cluster management command line toolset is a set of command line tools for managing and operating clusters. These tools provide a command line interface for performing various management tasks and operations in a cluster environment, making it easier for administrators to configure, monitor, and maintain clusters.

[0127] The load balancing component is a key component used to distribute network traffic and achieve load balancing. It is usually used in a distributed deployment architecture to distribute incoming request traffic to multiple backend servers or service instances to achieve load balancing and improve system performance, scalability, and reliability.

[0128] The node state manager is a component or service that manages and maintains the node state in a distributed deployment architecture. It tracks and monitors the state information of each node in the cluster, and manages and schedules the node state to ensure the stability and reliability of the cluster.

[0129] In the embodiment of the present invention, the distributed nodes use a distributed data storage solution, such as Figure 7 As shown;

[0130] Storage media refers to the physical media or devices used to store and persist data. It is the medium that carries data in a computer system and can be used to store various types of data, including files, programs, operating systems, etc.

[0131] Stateful workloads refer to applications or services running in a computer system that need to maintain and manage specific state information during operation. This state information may include database connections, session status, file system status, etc. Stateful workloads rely on this state data to process requests and provide consistent responses.

[0132] The distributed storage control plane refers to a set of components or functions used to manage and control distributed data storage. It is responsible for handling tasks such as metadata management, data access control, fault detection and recovery, data replication and migration of distributed data storage to ensure the reliability, performance and scalability of the storage system.

[0133] The node storage control plane refers to the control plane function located on each distributed node in the distributed data storage solution. It is responsible for managing and controlling the storage resources on the distributed nodes, processing local storage operations, and coordinating communication and data exchange with other distributed nodes.

[0134] A distributed storage engine is a core component or software library for distributed data storage, which provides the ability to store and manage large-scale data in a distributed environment. The design goal of a distributed storage engine is to achieve data distribution and redundant storage to provide data availability, persistence, and reliability, and to handle the storage and access requirements of large-scale data sets.

[0135] The distributed data storage solution manages the storage media available on each distributed node and uses the storage media to provide local or distributed persistent volumes for stateful workloads. A local volume refers to a storage medium that is directly attached to a host or server in a computer system and can only be accessed from a single distributed node. Its container group must be on the same node as the volume. The workload of local volumes is distributed and highly available. For local volumes, you can use raw partitions or subdirectories of the host path to create persistent volumes. Persistent volumes are a type of persistent storage resource independent of containers. They can be dynamically bound to containers when the containers are started, enabling containers to access and use persistent data. In the data storage solution, the distributed storage control plane provides additional tools for local volumes for monitoring, backup and recovery, disaster recovery, snapshots, and data scheduling.

[0136] Distributed persistent volumes are volumes that synchronously replicate data to multiple nodes. Unlike traditional distributed block storage volumes that store data in blocks on multiple nodes in a cluster, distributed persistent volumes store all data blocks of a volume on a certain node and replicate the entire data to other nodes in the cluster for persistence. When accessing volume data, traditional distributed block storage relies on a meta-hash algorithm to locate the node where the block is located, while distributed persistent volumes can access data from any node. Distributed persistent volumes are designed for cloud-native stateful workloads, which require large-capacity volumes that can usually be served directly from a single node without being sharded across multiple nodes. Distributed persistent volumes create microservices, where stateful workloads write data to the engine, which synchronously replicates the data to other nodes in the cluster. When the central hub node running a stateful workload container group fails, the container group will be rescheduled to another node in the cluster, using available data replicas on other nodes to provide access to the data.

[0137] The communication between the distributed nodes of the embodiment of the present invention can be composed of devices such as switches and routers, and driven by Ethernet protocols, routing protocols, and VLAN protocols. The VLAN (Virtual Local Area Network) protocol is a network protocol for virtualized local area networks. It is based on Ethernet technology and allows physically dispersed network devices to be divided into logically independent virtual networks to achieve logical isolation and flexible network management. The embodiment of the present invention uses a network plug-in that follows the scheme, and realizes the reachable routing between the nodes of the autonomous system through the border gateway protocol BGP, and selects the distance vector routing of the best route to solve the network communication and network security problems of the container cloud platform. The border gateway protocol is a standard protocol for exchanging routing information in the Internet. Autonomous system is a concept in the Internet that is used to divide and identify a group of network devices with the same routing policies and management permissions. An autonomous system can be a collection of one or more network devices that are logically regarded as a single unit and interact and communicate with other autonomous systems.

[0138] like Figure 8 As shown in the figure, the communication process of container group 1 accessing container group 2 in the distributed node, the operation subject is the network plug-in, the input is the information of container group 1 sending packets to container group 2 in the distributed node 1, and the output is the packet return information from container group 2 of the distributed node 1 to container group 1. Packet sending refers to the process of sending a data packet from the source host or router to the target host or router. Packet return refers to the process of the target device receiving a data packet and responding.

[0139] During the packet sending process, the information of container group 1 is transmitted from the wired Ethernet interface Localhost of container group 1 to Nodehost1 on the host side through the virtual network device interface, and enters the host network stack; according to the target IP 192.168.0.2, the information matches the routing rule "192.168.0.2dev Nodehost2 scope link" of container group 2 in the routing table; the information enters the container network stack of container group 2 from Nodehost2, completing the packet sending action. During the packet return process: the information of container group 2 is transmitted from the wired Ethernet interface Localhost of container group 2 to Nodehost2 on the host side through the virtual network device interface, and enters the host network stack; according to the destination IP 192.168.0.1, the information matches the routing rule "192.168.0.1dev Nodehost1 scope link" of container group 1 in the routing table; the information enters the container network stack of container group 1 from the Nodehost1 network card, completing the entire packet sending and return process.

[0140] For the explanation of routing rules, take "192.168.0.1dev Nodehost1 scope link" as an example:

[0141] In this example, there is a configuration with an IP address of 192.168.0.1, associated with a device interface named "Nodehost1", and with a scope attribute of "scope link".

[0142] 192.168.0.1: This is an IPv4 address that belongs to the private IP address range. It is usually used in internal networks and cannot be directly accessed from the public Internet. In this case,

[0143] 192.168.0.1 is the IP address of a specific device.

[0144] dev Nodehost1: This indicates that the IP address is associated with a network device interface named "Nodehost1". "dev" is short for "device" and specifies the interface name. In this case, the IP address is associated with a device interface named "Nodehost1".

[0145] Scope link: This is a scope indicator that describes the available range of an IP address. "Link" means that the IP address is only valid on the local link (local network) and can only be used for local communication. This means that the IP address can only communicate with other devices on the same network, and cannot communicate directly with external networks.

[0146] Therefore, this rule indicates that the IP address 192.168.0.1 is associated with the device interface named "Nodehost1" and that this IP address is valid only on the local link (local network) for local communication between devices.

[0147] like Fig. 9As shown in the figure, the communication process of accessing container group 2 of distributed node 2 from container group 1 of distributed node 1. During the packet sending process, the traffic of container group 1 is transmitted from the wired Ethernet interface Localhost of container group 1 to Nodehost1 on the host side through the virtual network device interface, that is, it is transmitted from the wired Ethernet interface Localhost of container group 1 to Nodehost1 on the host side, and enters the host network stack; according to the target IP, the traffic matches the routing rule of the corresponding network segment of container group 2 in the routing table, and is sent from the physical network card of distributed node 1; the traffic enters from the physical network card of node 2, and enters the container network stack of container group 2 from Nodehost2, completing the packet sending action. During the packet reply process, the traffic of container group 2 is transmitted from the wired Ethernet interface Localhost of container group 2 to Nodehost2 on the host side, and enters the host network stack; according to the target IP, the traffic matches the routing rule of the corresponding network segment of container group 1 in the routing table, and is sent from the physical network card of distributed node 2; the traffic enters from the physical network card of distributed node 1, and enters the container network stack of container group 1 from Nodehost1, completing the entire packet sending and reply process.

[0148] Compared with the "192.168.0.1dev Nodehost1 scopelink" for intra-node communication, the cross-node communication routing table adds a segment "192.168.0.2 / 26via 10.0.96.42dev physical network card proto brid".

[0149] 192.168.0.2 / 26: This is a combination of an IP address and a subnet mask, which indicates the range of a subnet. In this case, 192.168.0.2 is the network address of the subnet, and / 26 represents the subnet mask, which indicates the range of IP addresses available in the subnet.

[0150] via 10.0.96.42: This means that the IP address 10.0.96.42 is used as a gateway to access other networks. When a device wants to send a packet to a destination address that is not on the local subnet, it sends the packet to this gateway, which is responsible for forwarding the packet to the correct destination network.

[0151] dev physical NIC: This means that the IP address configuration will be applied to the physical NIC.

[0152] proto brid: refers to the type of network protocol. bird is actually the abbreviation of BIRD Internet Routing Daemon, which is a network dynamic routing protocol program.

[0153] In the specific judicial business collaboration process under specific business scenarios, there is a clear distinction between publishers and subscribers in terms of responsibilities and the use process of the distributed judicial data collaboration system.

[0154] Subscribers refer to users who need to query metadata information by using the distributed judicial data collaboration system and apply to the publisher to call business data during the judicial business collaboration process. In the process of using the central hub node, subscribers focus on specific data in the business process through the data subscription function, and track changes in metadata and service registration data corresponding to the data set. At the same time, subscribers can use the metadata query and service discovery functions provided by the distributed judicial data collaboration system to call specific judicial business collaboration data to which they have authority. They can also specify warning rules for observability indicators for specific metadata and receive alarm information returned by the platform.

[0155] Data subscription refers to the process by which a user or application subscribes to and receives updates on data provided by a specific data source or service provider. Once a subscription is established, the user or application can begin receiving data updates. Data updates can be real-time, periodic, or variable based on the update frequency of the data source.

[0156] The subscriber implements the service discovery function, which refers to the process of automatically discovering and identifying available service instances in the distributed fusion big data center system. In a judicial data collaboration system based on distributed deployment, there may be multiple service instances that provide the same service, and these instances may be dynamically deployed, expanded, or replaced. The goal of service discovery is to effectively manage and locate service instances in such an environment so that other components or services can communicate with them.

[0157] The publisher is mainly responsible for uploading and updating metadata, uploading and updating service registration data, and uploading and updating observability indicators. The publisher refers to the manager of the distributed node data storage system that stores smart judicial business collaboration data. In the process of judicial business collaboration, it is responsible for providing metadata information of stored data to the central hub of the affiliated institution and responding to the user's application for judicial business collaboration data call from the subscriber.

[0158] The entire judicial data collaboration system based on distributed deployment can adopt a decentralized identity authentication method. Decentralized identity is a new type of identity identification that is completely controlled by the owner. The personal information used for identity authentication is completely in the hands of the user himself, and no centralized third party is required to participate. Any other user cannot obtain authentication information without the user's authorization, which reduces identity fraud and attacks, improves the reliability of identity authentication, and reduces the maintenance, operation and management costs of the entire life cycle of data. Compared with traditional centralized authentication methods, decentralized identity authentication realizes data interoperability between systems. The construction of a decentralized identity authentication system is mainly divided into a basic layer and an application layer. The basic layer mainly includes decentralized identity identifiers and decentralized identity documents, and the application layer contains verifiable statements implemented through encryption algorithms and digital signature technologies.

[0159] The decentralized identifier system consists of six parts, namely the identifier itself, the resource location extension of the identifier, the identifier subject, the identifier controller, the verifiable data registry, and the decentralized identification document. The identifier itself consists of three parts, namely the scheme name, the method identifier, and the unique identifier under the method identifier. The decentralized identifier is secure, decentralized but not easy to remember, and can globally and uniquely represent a digital identity; on this basis, the resource location extension of the identifier further extends the basic decentralized identifier syntax, adding path, query and fragment information for locating resources. Uniform resource locators; is the entity identified by the decentralized identifier. This entity can be a specific person, organization or thing, or even an abstract concept; the identifier controller is a person, organization or software that can make changes to the decentralized identification document according to the definition of the decentralized identification method. The controller's modification capability is declared by the controller software using an encrypted key. A decentralized identifier may correspond to multiple controllers, and the identifier subject may be just one of the multiple controllers of the identifier. The verifiable data registry is a global key-value database used to record decentralized identifiers and return decentralized identification documents. In this virtual database, the key is the identifier itself and the value is the decentralized identification document. Commonly used verifiable data registries include distributed ledgers, decentralized file systems, peer-to-peer networks, and blockchain storage.

[0160] The purpose of a decentralized identity document is to describe the public keys, authentication protocols, and service endpoints necessary to conduct cryptographically verified interactions with identified entities. A decentralized identity document primarily contains the following: the identifier itself; a set of cryptographic materials, such as public keys, for authentication or interaction with the identifier subject; a set of cryptographic protocols for interacting with the identifier subject, such as authentication and capability delegation; a set of service endpoints that describe where and how to interact with the identifier subject; timestamps for auditing; and a JSON-LD signature for integrity verification of the decentralized identity document.

[0161] A verifiable claim is a qualification, achievement, quality, or information about an entity's background, such as name, government ID, payment provider, home address, or university degree. Such a claim describes one or more qualities, attributes, or properties of an entity, thereby establishing its existence and uniqueness. In order to make progress in the standardization and interoperability of possible high- and low-risk claims in the future, the goal of verifiable claims is to store, transmit, and receive digitally verifiable proofs of attributes. Verifiable claims are the value of establishing a decentralized identifier system, under which decentralized identifiers can be used to identify individuals, organizations, and even objects. The implementation of verifiable claims requires a complete system support. Participants in the verifiable claim system include claim issuers, claim verifiers, claim holders, and verifiable data registries in the decentralized identifier system. Verification of a verifiable claim is done by obtaining the issuer's decentralized identifier through the issuer field uniform resource locator address in the claim, and then obtaining the issuer's public key from the decentralized identification document corresponding to the decentralized identifier. The identity of the verifiable claim issuer can be verified by verifying the signature of the verifiable claim with the public key. Similarly, the method for verifying user identity is the same: the user verifies the legitimacy of his digital signature through the public key in the decentralized identification document corresponding to his own decentralized identifier.

[0162] The decentralized identity authentication verifiable statement used in the embodiment of the present invention includes the issuer, the holder, the verifier and the verifiable data registry as the participants.

[0163] The verifiable statement issuer refers to an entity that owns user data and can issue a verifiable statement. In the embodiment of the present invention, it specifically refers to a decentralized alliance jointly formed by courts, procuratorates and judicial administrative departments.

[0164] The holder of a verifiable statement is an entity that receives and holds a verifiable statement after making a request to the issuer of the verifiable statement. The verifiable statement issued by the issuer can be used repeatedly within the specified validity period. In the embodiment of the present invention, it specifically refers to users of courts, procuratorates and judicial administrative departments that use a judicial data collaboration system based on distributed deployment. During the business collaboration process, the user presents the verifiable statement to the verifier of the verifiable statement, views metadata and service information, and retrieves business data.

[0165] The verifiable claim verifier accepts the user's verifiable claim and verifies it. Depending on the department the user belongs to, different services can be provided to the type of user who presents the verifiable claim.

[0166] Maintaining a database of decentralized identities, the Verifiable Data Registry. The Verifiable Data Registry is a database where verifiers verify verifiable claims, verify users, verify the issuers of user verifiable claims, verify decentralized identities held by users, and store decentralized identities.

[0167] A verifiable statement mainly includes some metadata, namely the issuer, issue date, and expiration time; the statement part, which is one or more descriptions related to the subject; and the proof part, which is usually the digital signature of the issuer, which ensures that this verifiable statement can be verified, prevents the content of the verifiable statement from being tampered with, and verifies the issuer of the verifiable statement.

[0168] The above embodiments are merely illustrative of the principles and effects of the present invention, and are not intended to limit the present invention. Anyone familiar with the art may modify or alter the above embodiments without departing from the spirit and scope of the present invention. Therefore, all equivalent modifications or alterations made by a person of ordinary skill in the art without departing from the spirit and technical concept disclosed by the present invention shall still be covered by the claims of the present invention.

Claims

1. A judicial data collaboration method based on distributed deployment, characterized in that: Applied to a judicial data collaboration system based on distributed deployment, the judicial data collaboration system includes multiple central hub nodes and multiple distributed nodes managed by each central hub node; the method includes: Acquire a business collaboration document, determine a target distributed node corresponding to the category to which the business collaboration document belongs according to a load balancing rule, and store the business collaboration document in the target distributed node; Acquire the collaborative metadata corresponding to the business collaborative document, the target central hub node to which the target distributed node belongs stores the collaborative metadata, and updates the metadata dynamic directory according to the collaborative metadata, the metadata dynamic directory stores metadata information of all collaborative metadata stored in the target central hub node; The target central hub node sends the collaborative metadata and the updated metadata dynamic directory to other central hub nodes in the judicial data collaborative system.

2. The method according to claim 1, characterized in that Also includes: Acquire service registration data, the service registration data corresponds one-to-one with all collaborative metadata stored in the target central hub node, and configure access permission information for each collaborative metadata; In response to a service registration data viewing request from a user, the service registration data corresponding to the access permission is disclosed to the user according to the access permission of the user.

3. The method according to claim 1, characterized in that Acquire the collaboration metadata corresponding to the business collaboration document, including: Ingesting metadata from the business collaboration document through a command line interface or through a front-end interface; Verify whether the acquired metadata complies with the collaborative metadata standard. When the acquired metadata complies with the collaborative metadata standard, use the acquired metadata as the collaborative metadata corresponding to the business collaborative document.

4. The method according to claim 1, characterized in that Also includes: Periodically or trigger-wise perform data synchronization verification on the data stored in multiple central hub nodes in the judicial data collaboration system; The data synchronization check includes at least one of the following checks: consistency check, data traceability check and polling monitoring; The consistency check includes: during the data migration process, the migration target central hub node analyzes the log record of the data change of the current central hub node, queries the relevant data record in the migration source central hub node according to the data sequence number, and compares the data content to determine whether there is a data error. When there is a data error, the data error is repaired according to the data record of the migration source central hub node; The data traceability detection includes: recording and tracking the source, change history, transmission path, browsing and calling of data received and stored by the central hub node through annotation, tracing the full life cycle of the data circulating in the judicial data collaborative system, and determining the reliability, accuracy and compliance of the data; The polling monitoring includes: reading the data stored in the central hub node, and determining the data volume, real-time performance, data summary, and data lineage of the central hub node according to pre-set detection rules, and measuring and evaluating the operating status, behavior, and performance of the judicial data collaborative system.

5. The method according to claim 1, characterized in that Determining a target distributed node corresponding to the category to which the business collaboration document belongs according to the load balancing rule includes: Using a meta-hash algorithm, each distributed node corresponding to the category to which the business collaboration document belongs is mapped onto a hash space ring, and a unique identifier of each distributed node or a hash value of each distributed node is used as the position of the distributed node on the hash space ring; Create multiple virtual nodes for each distributed node, and each virtual node is evenly distributed on the hash space ring; When the business collaboration document obtains a hash value through the hash algorithm, the first node greater than or equal to the hash value is found clockwise on the hash space ring, and this node is used as the target distributed node corresponding to the category to which the business collaboration document belongs.

6. The method according to claim 5, characterized in that Also includes: When the number of distributed nodes in the judicial data collaborative system changes, the mapping relationship between adjacent distributed nodes and hash space rings is adjusted using a meta-hash algorithm, and whether to migrate data is determined according to a load balancing rule; When determining the data to be migrated, the amount of data to be migrated and the target node to be migrated are determined based on the hash algorithm; The migrated data is migrated to the target node based on the best distance vector routing through the Border Gateway Protocol.

7. The method according to claim 1, characterized in that The method also includes: Container cloud platform technology is used to deploy components or modules of applications or operating software in each central hub node and each distributed node in the judicial data collaborative system. The components or modules deployed at each central hub node are the same or different, and the components or modules deployed at each distributed node are the same or different.

8. A judicial data collaboration system based on distributed deployment, characterized in that: include: Multiple central hub nodes, and multiple distributed nodes managed by each central hub node; each central hub node communicates directly with all other central hub nodes; The distributed nodes are used to store business collaboration documents corresponding to their categories; The central hub node is used to store the collaborative metadata corresponding to the business collaborative documents of each distributed node managed, and update the metadata dynamic directory according to the collaborative metadata, and the metadata dynamic directory stores the metadata information of all collaborative metadata stored in the target central hub node; Each central hub node sends the collaborative metadata and updated metadata dynamic directory saved by the current central hub node to other central hub nodes in the judicial data collaborative system.

9. A computing device, characterized in that include: Memory; processor; as well as Computer programs; The computer program is stored in the memory and is configured to be executed by the processor to implement the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that A computer program is stored thereon; the computer program is executed by a processor to implement the method according to any one of claims 1 to 7.

Citation Information

Cited By

  • Cross-department and cross-network service data line interaction service method

    CN121166661A