Cross-department administrative law enforcement data co-processing method and system

Abstract

The invention relates to the technical field of data processing, and discloses a cross-department administrative law enforcement data co-processing method and system, and the system comprises a business application layer module, an application support module and a data resource module. The business application layer module is used for generating law enforcement behavior data; the application support module is configured with an external data interface component and is used for querying an external authoritative database; and the data resource module is used for receiving reported data reported by a plurality of law enforcement departments and performing data management on the reported data. The method comprises the following steps: generating and reporting data; receiving and executing data governance including accuracy verification; aggregating the governance qualified data to construct a same-level administrative law enforcement database; and receiving and aggregating a plurality of same-level administrative law enforcement databases to construct an upper-level administrative law enforcement database. According to the invention, active quality verification and cross-level ordered convergence are carried out on the reported data, so that the accuracy of the data is improved, and effective collaboration and supervision of cross-department law enforcement data are realized.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, specifically to a cross-departmental administrative law enforcement data collaborative processing method and system. Background Technology

[0002] With the continuous development of information technology, the informatization of administrative law enforcement has become a key link in improving law enforcement efficiency and government governance capabilities. Currently, administrative law enforcement departments at all levels have generally established business information systems to support daily case handling, document preparation, and file management, which have improved the efficiency of law enforcement work to a certain extent.

[0003] However, in current technological practices, the construction and application of such information systems are typically carried out on a per-departmental basis, with each law enforcement agency or field operating independently. This fragmented approach results in the independent operation and lack of interconnectivity of business systems across different law enforcement areas. This situation not only severely hinders joint law enforcement or collaborative case-handling scenarios requiring the participation of multiple departments but also makes cross-departmental data sharing and business collaboration difficult to achieve.

[0004] More critically, existing business systems generally lack mechanisms for connecting and comparing data with authoritative external data sources during the data collection phase. The accuracy and authenticity of key data stored internally, such as information on law enforcement subjects and the qualifications of law enforcement personnel, cannot be effectively guaranteed, resulting in inconsistent data quality. When cross-level data aggregation is required, the data reporting process from lower-level departments to higher-level departments often relies on manual summarization or temporary interface programs. This is not only inefficient but also prone to introducing new errors during data conversion and integration, further reducing data usability. Therefore, breaking down data silos and establishing a technical solution that can ensure data quality and achieve efficient cross-departmental and cross-level data collaborative processing is a pressing technical problem that needs to be solved in this field. Summary of the Invention

[0005] To address the shortcomings of existing technologies, this invention provides a cross-departmental administrative law enforcement data collaborative processing method and system, which solves the problem that in existing technologies, administrative law enforcement data is scattered across independent systems of various departments, with inconsistent standards and a lack of quality verification, making it difficult to achieve effective cross-departmental and cross-level data collaboration and supervision.

[0006] To achieve the above objectives, the present invention provides the following technical solution: a cross-departmental administrative law enforcement data collaborative processing method and system.

[0007] The first aspect of this invention provides a cross-departmental administrative law enforcement data collaborative processing system, the system comprising: The business application layer module integrates the business systems of multiple law enforcement departments. This module is configured to execute law enforcement business processes and generate law enforcement behavior data based on preset law enforcement basis data and law enforcement subject data.

[0008] The application support module connects to the business application layer module. This module is configured with an external data interface component, which establishes communication connections with authoritative external databases and performs data query operations.

[0009] The data resource module connects to the business application layer module and the application support module. This module is configured to receive reported data from the business systems of multiple law enforcement departments. Upon receipt, the data resource module performs data governance on the reported data to produce qualified data. A specific step in this data governance is to use an external authoritative database, through an external data interface component in the application support module, to compare the fields in the reported data to verify accuracy.

[0010] In one specific implementation, the business application layer modules include: a system for sorting out laws, regulations, rules, and administrative enforcement matters; a system for managing enforcement certificates; a system for handling administrative enforcement cases; and a system for supervising administrative enforcement. The system for sorting out laws, regulations, rules, and administrative enforcement matters is responsible for managing and providing enforcement basis data to other systems. The enforcement certificate management system is responsible for managing and providing enforcement entity data. The administrative enforcement case handling system obtains enforcement basis data and enforcement entity data from the first two systems and generates reporting data containing enforcement behavior data in its business processes. The administrative enforcement supervision system receives enforcement behavior data from the administrative enforcement case handling system to perform supervision.

[0011] In one specific implementation, the external data interface component is specifically configured to perform the following operations: when receiving a query request from the administrative law enforcement case handling system containing a unique identifier of a legal entity, the component initiates a query to the external legal entity basic information database and returns the legal entity information; when receiving a query request containing a unique identifier of a natural person, the component initiates a query to the external population basic information database and returns the individual basic information.

[0012] In one specific implementation, the data resource module includes a data governance submodule and a data fusion submodule. The data governance submodule is specifically configured to perform data governance operations. The data fusion submodule is connected to the data governance submodule, and its function is to aggregate the qualified data output by the data governance submodule to construct a peer-to-peer administrative law enforcement database.

[0013] In one specific implementation, the data governance performed by the data governance submodule includes, in addition to accuracy verification, integrity verification and consistency verification. Integrity verification checks for missing required fields in the reported data based on a predefined law enforcement data model. Consistency verification checks for logical inconsistencies between data items within the reported data.

[0014] In one specific implementation, the data fusion submodule is also configured to perform upper-level data aggregation. Specifically, this submodule receives multiple peer-level administrative law enforcement databases reported by multiple lower-level supervisory departments, and aggregates these databases to construct an upper-level administrative law enforcement database.

[0015] In one specific implementation, the business application layer module further includes an enforcement disclosure system. This system is connected to the legal regulations and rules system, the enforcement certificate management system, and the administrative enforcement case handling system, respectively, to obtain enforcement basis data, enforcement subject data, and enforcement result data, and to perform public disclosure of enforcement information.

[0016] In one specific implementation, the application support module may further include at least one of an electronic seal component, a geographic information system service component, or an optical character recognition service component, to provide standardized technical support services for the business application layer module.

[0017] In one specific implementation, the system further includes a basic resource module and a user and presentation layer module. The basic resource module, data resource module, application support module, business application layer module, and user and presentation layer module are deployed in a layered manner.

[0018] A second aspect of this invention provides a cross-departmental administrative law enforcement data collaborative processing method, comprising the following steps: First, a business application layer module generates law enforcement behavior data based on preset law enforcement basis data and law enforcement subject data, and forms this law enforcement behavior data into reporting data. Next, a data resource module receives this reporting data from multiple law enforcement departments. Then, the data resource module performs data governance on the received reporting data. This data governance step includes a key operation: verifying the accuracy of the reporting data by calling an external authoritative database, thereby forming qualified data. Subsequently, the data resource module aggregates the formed qualified data to construct a peer-to-peer administrative law enforcement database. Finally, the data resource module receives multiple peer-to-peer administrative law enforcement databases reported by multiple lower-level supervisory departments, and aggregates these multiple databases to construct a higher-level administrative law enforcement database.

[0019] This invention provides a method and system for cross-departmental collaborative processing of administrative law enforcement data. It has the following beneficial effects: 1. This invention performs data governance on the data reported by various law enforcement departments by setting up a data resource module, and verifies the accuracy of the data entering the unified data warehouse by calling an external authoritative database through the application support module during the governance process. This mechanism transforms passive data reception into proactive quality verification, improving the accuracy and reliability of aggregated data from the source, and laying a solid data foundation for subsequent data sharing and supervision applications.

[0020] 2. This invention achieves close coupling between law enforcement and supervision operations through data collaboration and flow between various systems within the business application layer module. Law enforcement data generated by the administrative law enforcement case handling system can be transmitted to the administrative law enforcement supervision system in real time, enabling a shift from post-event supervision to process supervision, enhancing the timeliness and effectiveness of supervision. Simultaneously, the sharing of standardized law enforcement basis data and law enforcement entity data also standardizes the front-end case handling process.

[0021] 3. This invention, through the data fusion submodule within the data resource module, designs a hierarchical aggregation process from constructing a peer-to-peer administrative law enforcement database to converging it into a higher-level administrative law enforcement database. This process breaks down the horizontal departmental barriers and vertical hierarchical barriers in the traditional administrative system, enabling the orderly aggregation and unified storage of cross-departmental and cross-level administrative law enforcement data, thus providing the possibility for comprehensive, multi-dimensional law enforcement data analysis and macro-level decision support. Attached Figure Description

[0022] Figure 1 This is a schematic diagram of the overall system architecture of the present invention; Figure 2 This is a schematic diagram of the internal structure of the data resource module of the present invention; Figure 3 This is a schematic diagram of the internal structure of the application support module of the present invention; Figure 4 This is a schematic diagram of the internal structure and data interaction of the business application layer module of the present invention; Figure 5 This is a flowchart illustrating the overall process of the cross-departmental administrative law enforcement data collaborative processing method of the present invention. Figure 6 This is a detailed flowchart of the cross-departmental data supervision and aggregation process of the present invention. Detailed Implementation

[0023] The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on 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.

[0024] See attached document Figure 1 -Appendix Figure 6 The present invention provides a cross-departmental administrative law enforcement data collaborative processing system, comprising: a basic resource module 100, a data resource module 200, an application support module 300, a business application layer module 400, and a user and display layer module 500.

[0025] The basic resource module 100, data resource module 200, application support module 300, business application layer module 400, and user and presentation layer module 500 are deployed in a layered manner. Basic resource module 100 is at the bottom layer, providing the runtime environment for the upper-layer modules. Data resource module 200 is built on top of basic resource module 100. Application support module 300 is built on top of data resource module 200. Business application layer module 400 is built on top of application support module 300. User and presentation layer module 500 is at the top layer.

[0026] The basic resource module 100 is configured to provide the computing, storage, and network resources required for system operation. The basic resource module 100 provides the hardware and virtualization environment for the operation of the data resource module 200, application support module 300, and business application layer module 400.

[0027] The data resource module 200 is connected to the basic resource module 100 and the application support module 300. The data resource module 200 is configured to store, manage, and process administrative law enforcement data for the entire province. Specifically, the data resource module 200 is configured to store the same-level administrative law enforcement database reported by lower-level supervisory departments. and execute the parent aggregation function. In order to build a database of higher-level administrative law enforcement The convergence process can be represented by the following formula: ; in, represent A hierarchical (higher-level) database of administrative law enforcement; Representing the indivual The administrative law enforcement database reported by supervisory departments at the same level; This refers to the total number of supervisory departments at the same level that report to the database.

[0028] Application support module 300 connects to data resource module 200 and business application layer module 400. Application support module 300 is configured to provide standardized public technical components and service interfaces for business application layer module 400 to call. Specifically, application support module 300 includes: an identity authentication component, an electronic seal generation component, an electronic certificate retrieval component, a Geographic Information System (GIS) service component, an Optical Character Recognition (OCR) service component, and a standardized data interface for querying external databases.

[0029] The business application layer module 400 connects to the application support module 300 and the user and presentation layer module 500. This module is the core functional unit for executing the business logic of collaborative administrative law enforcement processing. Specifically, the business application layer module 400 includes: a system for sorting out laws, regulations, rules, and administrative law enforcement matters; a system for managing law enforcement certificates; a system for handling administrative law enforcement cases; and a system for supervising administrative law enforcement. These systems interact with each other through pre-defined data interfaces to perform internal system collaboration and data flow.

[0030] The user and presentation layer module 500 is connected to the business application layer module 400. The user and presentation layer module 500 is configured to provide a graphical user interface (GUI), receive user operation commands, and transmit the commands to the business application layer module 400. Simultaneously, this module is configured to receive data processing results from the business application layer module 400 and display the results on the user interface.

[0031] In one deployment method, the system of the present invention can be deployed on a provincial integrated government big data platform, wherein the basic resource module 100, the data resource module 200 and the application support module 300 can reuse the existing computing, storage and public component capabilities of the platform.

[0032] See attached document Figure 2 The data resource module 200 is connected between the basic resource module 100 and the application support module 300, and is configured as the center for the aggregation, governance, storage and sharing of administrative law enforcement data in the province.

[0033] Specifically, the data resource module 200 may include: a data receiving submodule 210, a data governance submodule 220, a data fusion submodule 230, a unified data warehouse 240, and a data service submodule 250.

[0034] Data receiving submodule 210 is configured with a standard data exchange interface for receiving data from multiple different law enforcement agencies. Reported data and from lower-level supervisory departments Reported administrative law enforcement database at the same level The data receiving submodule 210 performs initial parsing and verification of the received data.

[0035] The data governance submodule 220 is connected to the data receiving submodule 210. The data governance submodule 220 is configured to process the received reported data. Execute data governance functions The governance process includes data quality verification based on a pre-defined set of rules. Specifically, this submodule performs the following verifications: Accuracy verification ( ):Will Fields in the database (e.g., law enforcement officer identity information, legal entity information of law enforcement entities) and external authoritative data obtained through application support module 300 ( We will compare them to verify their accuracy.

[0036] Integrity verification ( Based on a predefined law enforcement data model, inspect Does the database contain any missing required fields?

[0037] Consistency verification ( ):examine The logical relationships between the various data items must be consistent; for example, the case completion date must not be earlier than the case filing date. Only data that passes all the above verifications is identified as qualified data. And transmit it to the data fusion submodule 230.

[0038] The data fusion submodule 230 is connected to the data governance submodule 220 and the data receiving submodule 210. This submodule is configured to perform data aggregation operations. Firstly, the data fusion submodule 230 executes peer database construction functions. Governance compliance data from multiple law enforcement agencies Aggregate to form this administrative level Administrative law enforcement database The construction process can be represented by the following formula: ; in, To pass the governance function Verified law enforcement agencies The set of indices.

[0039] Data fusion submodule 230 executes the aggregation function of the upper-level database. The received data will be from multiple lower-level administrative law enforcement databases. To aggregate and form a higher administrative level Administrative law enforcement database .

[0040] The unified data warehouse 240 is connected to the data fusion submodule 230. The unified data warehouse 240 is a structured data storage unit configured to physically store the administrative law enforcement databases at various levels generated by the data fusion submodule 230. and The data in the unified data warehouse 240 is divided according to preset subject areas to support subsequent data querying and analysis.

[0041] The data service submodule 250 connects the unified data warehouse 240 and the application support module 300. The data service submodule 250 encapsulates the data stored in the unified data warehouse 240 into standardized data service interfaces (e.g., RESTful APIs), which can be called on demand by the application support module 300 or the business application layer module 400, thereby realizing the sharing of administrative law enforcement data.

[0042] See attached document Figure 3 Application support module 300 is connected between data resource module 200 and business application layer module 400. It is configured to provide standardized and reusable common technical components and service interfaces for each business system in business application layer module 400.

[0043] Specifically, the application support module 300 may include: an identity authentication component 310, an external data interface component 320, an electronic seal component 330, an electronic certificate component 340, a geographic information system (GIS) service component 350, an optical character recognition (OCR) service component 360, and a data service interface component 370.

[0044] The identity authentication component 310 is configured to interface with an external or internal unified identity authentication system. When the business application layer module 400 (e.g., a law enforcement certificate management system or an administrative law enforcement case handling system) needs to verify the identity of law enforcement personnel or parties involved in a case, the identity authentication component 310 provides standardized verification service calls and returns the verification results to the business application layer module 400.

[0045] External data interface component 320, configured to execute external data query functions. External data interface component 320 includes an external population database. and external legal entity basic information database Pre-defined communication protocols and interface specifications. When the business application layer module 400 (e.g., the administrative law enforcement case handling system) initiates a query request (containing the query keyword key)... or When the request is received, the external data interface component 320 is responsible for encapsulating the request and sending it to the corresponding external database. or and receive the returned data. or .

[0046] The electronic seal component 330 is configured to invoke the electronic seal service upon request from the business application layer module 400. After the administrative law enforcement case handling system generates electronic law enforcement documents, the electronic seal component 330 affixes a compliant electronic seal at a designated location on the document and ensures the validity of the seal.

[0047] Electronic certificate component 340 is configured to connect to an authoritative electronic certificate repository. This component 340 provides a standard interface for administrative law enforcement systems to acquire and verify electronic certificate information related to law enforcement activities as needed during the enforcement process.

[0048] GIS service component 350 is configured to provide geographic location-related services. GIS service component 350 receives geographic coordinates or address information sent by the business application layer module 400, and provides geographic location coding, spatial query, and map rendering services to assist the administrative law enforcement case handling system in locating and analyzing law enforcement positions.

[0049] OCR service component 360 is configured to receive image files (e.g., photos of paper evidence) uploaded by business application layer module 400. OCR service component 360 calls the OCR engine to recognize text information in the image and returns the recognition result to business application layer module 400 in structured text format to support the electronic entry of paper documents.

[0050] Data service interface component 370 is connected to data service submodule 250 in data resource module 200. Data service interface component 370 is configured to convert the business application layer module 400's request for internal law enforcement data (e.g., querying historical case data) into standard query instructions for unified data warehouse 240, and obtain the returned data through data service submodule 250.

[0051] See attached document Figure 4 The business application layer module 400 is connected between the application support module 300 and the user and display layer module 500, and is configured to execute the core business logic for collaborative administrative law enforcement processing.

[0052] Specifically, the business application layer module 400 may include: a system for sorting out laws, regulations, rules and administrative law enforcement matters 410, a law enforcement certificate management system 420, an administrative law enforcement case handling system 430, an administrative law enforcement supervision system 440, and a law enforcement publicity system 450.

[0053] The Legal Regulations and Administrative Enforcement Matters Sorting System 410 is configured to perform structured management and storage of basic legal information, statutory discretionary information, and unified administrative enforcement matters (sub-items). The Legal Regulations and Administrative Enforcement Matters Sorting System 410 uses a preset data interface to process the enforcement basis data it manages. This data is provided to the Administrative Law Enforcement Case Handling System 430 and the Administrative Law Enforcement Supervision System 440 as the legal basis for case handling and supervision. The Laws, Regulations, Rules, and Administrative Law Enforcement Matters Sorting System 410 also provides this data on the legal basis for enforcement. 450 were provided to the law enforcement information disclosure system.

[0054] The Law Enforcement Credentials Management System 420 is configured to uniformly manage and maintain information on law enforcement departments and the identity, qualifications, and credentials of law enforcement personnel. The Law Enforcement Credentials Management System 420 communicates the law enforcement entity data it manages through a data interface. The system provides data to the administrative law enforcement case handling system 430 and the administrative law enforcement supervision system 440 for verifying the identity of law enforcement personnel and allocating permissions during case handling and supervision activities. The law enforcement certificate management system 420 also stores law enforcement entity data. 450 were provided to the law enforcement information disclosure system.

[0055] The Administrative Law Enforcement Case Handling System 430 is configured to execute all business processes for online case handling. When initializing the case handling process, the Administrative Law Enforcement Case Handling System 430 first calls the Laws, Regulations, Rules, and Administrative Law Enforcement Matters Review System 410 to obtain... and call the law enforcement credentials management system 420 to obtain This is to ensure the compliance of the case-handling body and the legal basis for enforcement.

[0056] During the case-handling process, the administrative law enforcement case-handling system 430 also executes external data query functions by calling the external data interface component 320 of the application support module 300. To obtain external legal entity information for case verification. and population information The administrative law enforcement case handling system 430 also calls the electronic seal component 330 and electronic certificate component 340 in the application support module 300 to generate and verify electronic law enforcement documents.

[0057] The administrative law enforcement case handling system 430 generates structured law enforcement behavior data in real time during the execution of case handling procedures. and the data The data is transmitted to the administrative law enforcement supervision system 440 in real time or near real time via a data interface. After the case handling process is completed, the administrative law enforcement case handling system 430 transmits the resulting law enforcement result data (e.g., administrative penalty decision documents) to the law enforcement publicity system 450.

[0058] The administrative law enforcement supervision system 440 is configured for real-time monitoring and post-event review of the law enforcement process. The administrative law enforcement supervision system 440 maintains a data connection with the administrative law enforcement case handling system 430, receiving law enforcement action data transmitted from it in real time. Meanwhile, the administrative law enforcement supervision system 440 also receives data from the laws, regulations, rules, and administrative law enforcement matters sorting system 410. and from the law enforcement credentials management system 420 This serves as benchmark data for oversight and review. System 440 uses this data... Law enforcement actions and , The data is compared and analyzed to perform automated monitoring and post-event review.

[0059] The law enforcement disclosure system 450 is configured to disclose law enforcement information to the public. The law enforcement disclosure system 450 receives enforcement basis data from the laws, regulations, rules, and administrative enforcement matters sorting system 410. Receive law enforcement entity data from the law enforcement certificate management system 420 The system also receives enforcement result data from the administrative law enforcement case handling system 430. The law enforcement publicity system 450 integrates and publishes the received data, and displays it to the public through the user and display layer module 500.

[0060] See attached document Figure 5 The collaborative processing method provided by the present invention performs external data collaboration and acquisition in step S100 (stage one).

[0061] Step S100 is initiated by the administrative law enforcement case handling system 430 in the business application layer module 400 during the execution of the law enforcement process. When the administrative law enforcement case handling system 430 needs to verify the basic information of the law enforcement counterpart (legal entity or natural person), the administrative law enforcement case handling system 430 generates a data query request containing query keywords. This request is sent to the application support module 300.

[0062] The external data interface component 320 in the application support module 300 receives the data query request. The external data interface component 320 calls a preset external data query function. The function It encapsulates standardized communication protocols and interface specifications for communication with one or more external authoritative databases.

[0063] In one specific implementation (obtaining legal entity information), the query keyword is the unique identifier of the legal entity. (For example, social credit code). External data interface component 320 will (External legal entity basic information database) is designated as the target database, and As a parameter, through Function to Initiate a query. External data interface component 320 receives the returned basic legal entity information. and the The data was transmitted back to the administrative law enforcement case handling system 430.

[0064] In another specific implementation (obtaining population information), the query keyword is the unique identifier of a natural person. (For example, a citizen's identification number). External data interface component 320 will... (External population database) is designated as the target database, and As a parameter, through Function to Initiate a query. Component 320 receives the returned basic personal information. and the The data was transmitted back to the administrative law enforcement case handling system (430).

[0065] The execution process of external data collaboration and acquisition step S100 can be formally expressed by the following formula: ; ; in, For the returned legal entity information, This is the basic personal information returned. The Administrative Law Enforcement Case Handling System 430 will obtain... or For use in subsequent law enforcement procedures.

[0066] See attached document Figure 5 The collaborative processing method provided by this invention performs internal system collaboration and data flow in step S200 (stage two). This step S200 is executed within the business application layer module 400, through the data interfaces between the various systems included in this module 400.

[0067] Step S200 includes: the legal regulations, rules, and administrative enforcement matters sorting system 410, which, through a data interface, manages the enforcement basis data. The data is transmitted to the administrative law enforcement case handling system 430 and the administrative law enforcement supervision system 440.

[0068] The Law Enforcement Certificate Management System 420, through a data interface, manages the data of law enforcement entities. The data is transmitted to the administrative law enforcement case handling system 430 and the administrative law enforcement supervision system 440.

[0069] Before executing the case handling procedure, the administrative law enforcement case handling system 430 first obtains information from system 410. and obtain from the law enforcement credentials management system 420 This serves as the basis for initiating the investigation. The data acquisition relationship can be represented by the following formula: ; in, This refers to the Administrative Law Enforcement Case Handling System 430. During the execution of the case handling process, the Administrative Law Enforcement Case Handling System 430 generates real-time law enforcement action data based on the business inputs it receives. This process can be represented by the following formula: ; The administrative law enforcement case handling system will generate 430 The data is transmitted to the administrative law enforcement supervision system 440 in real time or near real time via the data interface.

[0070] The administrative law enforcement supervision system 440 receives data from the administrative law enforcement case handling system 430. And obtain from the 410 system for sorting out laws, regulations, rules and administrative enforcement matters. And obtained from the law enforcement credentials management system 420 The administrative law enforcement supervision system 440 compares... and , The data is used to perform oversight and review operations. This data dependency can be represented by the following formula:

[0071] ; in, Represents the administrative law enforcement supervision system 440.

[0072] In addition, the law enforcement publicity system 450 is connected to the laws, regulations, rules and administrative enforcement matters sorting system 410, the law enforcement certificate management system 420, and the administrative law enforcement case handling system 430. The law enforcement publicity system 450 obtains information from the laws, regulations, rules and administrative enforcement matters sorting system 410. Obtained from the law enforcement certificate management system 420 Furthermore, it obtains enforcement result data from the administrative law enforcement case handling system 430 for the public disclosure of enforcement information.

[0073] See attached document Figure 6 The collaborative processing method provided by the present invention performs a cross-departmental data supervision and aggregation process in step S300 (stage three).

[0074] This step S300 specifically includes the following steps: By various law enforcement agencies ( (This refers to the collective execution of law enforcement agencies.) Each law enforcement agency... Firstly, it examines the various types of raw law enforcement data generated by its internal business systems (e.g., the administrative law enforcement case handling system 430). Collect and integrate the information. This includes data on law enforcement personnel, administrative law enforcement matters, and law enforcement actions.

[0075] This aggregation process executes internal departmental data aggregation functions. To achieve this function Multi-source heterogeneous raw data within the department ( (Integrated into standardized data packages for data type indexing) This process can be represented by the following formula: Step S310 (Departmental Data Collection): ; Step S320 (Data Reporting to the Same Level): By law enforcement agencies Enforcement. Law enforcement agencies. After completion After collection, the data is converted by executing the data reporting function. , will data packet Convert the data to meet the reporting standards. .Should Function ensures The data structure and encoding meet the requirements of the recipient.

[0076] Subsequently, law enforcement agencies Will Report to the same administrative level law enforcement supervision departments ( (This refers to a collection of law enforcement and oversight departments). The process can be represented by the following formula: ; Step S330 (Data Governance at the Same Level): This is carried out by the law enforcement and supervision department at the same level. This is executed within the data resource module 200, specifically by the data governance submodule 220. The data governance submodule 220 receives data from multiple law enforcement agencies within its jurisdiction. Reported .

[0077] Data governance submodule 220 for each Execute data governance functions This is for quality monitoring. (The function is mentioned here.) Determine data quality by executing the following validation function: Accuracy verification :Will Key information (e.g., personnel identity, legal entity information) and information accessed through the application support module 300 or The returned data is compared.

[0078] Integrity verification Based on the pre-set law enforcement data model, the inspection Does it contain all the required data items?

[0079] Consistency verification :examine Logical relationships between internal data items, for example, the case filing date cannot be later than the case closure date.

[0080] The logical judgment can be expressed by the following formula: ; Data governance submodule 220 only filters out Data that returns True from the function forms a set of qualified data for governance. Step S340 (Construction of the same-level database): This is carried out by the same-level law enforcement and supervision department. This is executed in the data resource module 200, specifically by the data fusion submodule 230. The data fusion submodule 230 processes the data generated in step S330. (i.e., all those that have passed the governance requirements) Execute the sibling database construction function .Should The function will All data in the set are aggregated (e.g., through a union operation) to form the administrative level. Administrative law enforcement database .Should It is stored in a unified data warehouse 240. The construction process can be represented by the following formula: ; in, For passing in step S330 Verified law enforcement agencies The set of indices.

[0081] Step S350 (Upper-level data aggregation): By Supervisory departments at different levels and Supervisory departments at higher levels Jointly implemented. Supervisory departments at different levels The part that was built in step S340 Report it to higher authorities. Supervisory departments at different levels In the data resource module 200, the data receiving submodule 210 receives data from all resources within its jurisdiction. indivual Databases reported by supervisory departments at different levels .

[0082] Data fusion submodule 230 executes the aggregation function of the upper-level database. , will this Aggregate the databases to form a structure Hierarchical administrative law enforcement database And store it in a unified data warehouse 240. This aggregation process can be represented by the following formula: ; By cyclically executing steps S310 to S350, this method enables the cross-departmental and cross-level aggregation and collaborative processing of administrative law enforcement data.

Claims

1. A cross-departmental administrative law enforcement data collaborative processing system, characterized in that, include: The business application layer module is configured to generate law enforcement behavior data based on preset law enforcement basis data and law enforcement subject data. The business application layer module includes business systems of multiple law enforcement departments. The application support module is configured with an external data interface component for querying authoritative external databases; The data resource module is configured to receive reported data from the business systems of the multiple law enforcement departments and perform data governance on the reported data to form qualified data. The data governance includes calling the external authoritative database through the external data interface component to verify the accuracy of the reported data.

2. The cross-departmental administrative law enforcement data collaborative processing system according to claim 1, characterized in that, The business application layer module specifically includes: A system for sorting out laws, regulations, rules, and administrative enforcement matters is configured to manage and provide the aforementioned enforcement basis data. The law enforcement credentials management system is configured to manage and provide data on the aforementioned law enforcement entities. The administrative law enforcement case handling system is configured to acquire the data on the legal basis and the data on the law enforcement entity, and generate reporting data containing the data on the law enforcement actions. An administrative law enforcement supervision system is configured to receive data on the aforementioned law enforcement actions in order to perform supervision.

3. The cross-departmental administrative law enforcement data collaborative processing system according to claim 1, characterized in that, The external data interface component is configured to: Receive a query request from the administrative law enforcement case handling system containing a unique identifier of the legal entity, and query the legal entity information from the external legal entity basic information database; In addition, it can receive query requests from the administrative law enforcement system that contain the unique identifier of the natural person, and query personal basic information from external population databases.

4. The cross-departmental administrative law enforcement data collaborative processing system according to claim 1, characterized in that, The data resource module specifically includes: The data governance submodule is configured to perform the data governance on the reported data; The data fusion submodule is configured to aggregate the qualified governance data and construct a peer-level administrative law enforcement database.

5. A cross-departmental administrative law enforcement data collaborative processing system according to claim 4, characterized in that, The data governance performed by the data governance submodule also includes: Integrity verification is used to check whether there are any missing required fields in the reported data, based on a predefined law enforcement data model. And consistency verification, used to check the logical relationships between the data items within the reported data.

6. The cross-departmental administrative law enforcement data collaborative processing system according to claim 4, characterized in that, The data fusion submodule is also configured to: Receive reports from multiple lower-level supervisory departments on multiple administrative law enforcement databases at the same level; Furthermore, the multiple administrative law enforcement databases at the same level are aggregated to construct a higher-level administrative law enforcement database.

7. A cross-departmental administrative law enforcement data collaborative processing system according to claim 2, characterized in that, The business application layer module also includes: The law enforcement disclosure system is connected to the aforementioned legal regulations and rules system, administrative law enforcement matters sorting system, law enforcement certificate management system, and administrative law enforcement case handling system. It is configured to obtain the aforementioned law enforcement basis data, law enforcement subject data, and law enforcement result data, and to publicly disclose law enforcement information.

8. The cross-departmental administrative law enforcement data collaborative processing system according to claim 1, characterized in that, The application support module also includes at least one of the following: An electronic seal component, configured to affix electronic seals to electronic law enforcement documents; Geographic Information System service components, configured to provide geographic location coding and spatial query services; An optical character recognition service component, configured to recognize text information in image files.

9. A cross-departmental administrative law enforcement data collaborative processing system according to claim 1, characterized in that, Also includes: The basic resource module is configured to provide computing, storage, and network resources; The user and presentation layer module is configured to provide a graphical user interface. The basic resource module, data resource module, application support module, business application layer module, and user and presentation layer module are deployed in a layered manner.

10. A method for cross-departmental collaborative processing of administrative law enforcement data, characterized in that, Includes the following steps: The business application layer module generates law enforcement behavior data based on preset law enforcement basis data and law enforcement subject data, and then forms the law enforcement behavior data into reporting data. The data resource module receives the reported data from multiple law enforcement agencies; The data resource module performs data governance on the received reported data. The data governance includes verifying the accuracy of the reported data by calling an external authoritative database and forming qualified data. The data resource module aggregates the qualified governance data and constructs a database of administrative law enforcement at the same level. The data resource module receives multiple administrative law enforcement databases at the same level reported by multiple lower-level supervisory departments, and aggregates the multiple administrative law enforcement databases at the same level to construct a higher-level administrative law enforcement database.

Images