Network interface-based administrative law enforcement agency examination management system and method

Abstract

The present application relates to the field of administrative law enforcement informationization and administrative management data processing technology, discloses an administrative law enforcement organ examination management system and method based on network docking, comprising: registering an administrative law enforcement business source system and locking necessary data fields for examination, generating a source system registration list and a data field correspondence table; generating an interface handshake record before business data packet transmission, generating an event unique abstract code and an interface original record index; forming a case file handling node sequence according to the case file type, extracting the law enforcement behavior benchmark time and the source system record time; combining the same type of historical synchronous delay record to calculate the case file data time sequence credibility value, positioning the abnormal handling node list, generating a case file automatic collection mark and encapsulating the organ examination case file record, and finally generating an administrative law enforcement organ network docking examination management electronic account book. The present application is used for collecting and processing cross-source system case file data and generating an evidence catalog.

Description

Technical Field

[0001] This invention relates to the field of information technology for administrative law enforcement and data processing for administrative management; more specifically, it relates to a network-connected performance evaluation management system and method for administrative law enforcement agencies. Background Technology

[0002] In the construction of administrative law enforcement information systems, law enforcement case data is typically distributed across mobile data collection terminals, case file processing systems, document systems, public disclosure systems, supervision platforms, and data exchange platforms. When aggregating this data, the performance evaluation management system faces challenges such as interface calls, batch synchronization, offline caching, data entry supplementation, data element version differences, system time offsets, and duplicate pushes across multiple platforms. For system maintenance and data governance personnel, conventional processing methods typically include field mandatory validation, format validation, interface return status checks, case file quantity statistics, document material comparison, and manual spot checks. These methods can identify issues such as empty fields, format errors, interface failures, or missing materials. However, they often lack a unified processing flow for performance evaluation management purposes regarding the correspondence between the time of the processing node, the time recorded in the source system, and the time received by the center.

[0003] In a cross-system data access environment, the processing nodes of the same case file, such as inspection, notification, decision, delivery, and case closure, may originate from different business source systems. The time maintenance methods, interface submission methods, batch task cycles, and log storage methods of each source system are inconsistent. When network transmission queuing, centralized uploading after terminal offline, source system time offsets, and document supplementation or secondary modifications occur simultaneously, judging whether a case file is suitable for inclusion in the assessment data scope solely based on the central reception time or a single business time can easily confuse normal transmission delays with time anomalies caused by supplementation. For the assessment management system, this affects the formation of the list of admissible case files and increases the scope of manual review.

[0004] Existing data exchange platforms focus more on interface reachability, message format, field mapping, and the completion of exchange tasks; existing case file management systems focus more on document completeness, process node flow, and business status closure; existing performance evaluation and statistics modules focus more on quantity, proportion, completion status, and manual inspection conclusions. While these systems can each fulfill their respective responsibilities, a processing method oriented towards network-connected environments is still needed before case file data enters the performance evaluation and management ledger. This method would jointly process source system registration, interface handshake records, data field correspondences, processing node sequences, source system record times, law enforcement behavior benchmark times, and historical synchronization delay records. The processing results would then be converted into an automatically credible case file directory, a case file directory requiring manual verification, and an evidence directory of abnormal processing nodes. This would allow the performance evaluation and management process to rely on specific access systems, interface records, and case file processing nodes, rather than solely on manual judgment or single statistical results. Summary of the Invention

[0005] This invention provides an administrative law enforcement agency performance evaluation management system and method based on network connectivity, which solves the technical problems mentioned in the background art.

[0006] This invention provides the following solution: Firstly, a network-based assessment and management method for administrative law enforcement agencies, applied to an assessment and management system connected to the administrative law enforcement business source system via network, includes: Register the network interface objects and lock the necessary data fields for assessment, and generate a source system registration list and a data field correspondence table; Before the transmission of business data packets, an interface handshake record is generated, and an event unique digest code and an interface original record index are generated based on the data field correspondence table. Construct a sequence of case handling nodes based on case file type, and extract the base time of law enforcement behavior and the source system record time for each handling node; Based on the interface handshake record, the law enforcement behavior reference time, the source system record time, and similar historical synchronization delay records, calculate the case file data time sequence reliability value, node upload delay anomaly value, and central correction record time; The list of abnormal processing nodes is located based on the abnormal upload delay value of the node, the central correction record time, and the chronological order of the case file processing node sequence; Based on the time-series reliability value of the case file data and the list of abnormal processing nodes, an automatic acceptance mark for the case file is generated, and the case file record for agency assessment is encapsulated. Based on the aforementioned agency assessment case records, an electronic ledger for administrative law enforcement agency network-connected assessment management is generated.

[0007] Preferably, the network interface objects are registered and the necessary data fields for assessment are locked, generating a source system registration list and a data field correspondence table, including: Each accessed administrative law enforcement business source system is registered as a unique source system record, forming the source system registration list; The following data fields are locked as necessary data fields for the assessment: agency identifier, case file identifier, case file type, processing node type, document type, source system record time, central system reception time, interface request identifier, data element version, original document digest code, and interface response status. Read the source system identifier, data element version, and processing node type enumeration, compare the data element version with the preset administrative law enforcement data element correspondence rules, and obtain the data field correspondence table; Discard fields that are not part of the required data fields for the assessment, and reject data packets that lack agency identifiers, case file identifiers, processing node types, or source system record times from being added to the database.

[0008] Preferably, an interface handshake record is generated before the transmission of business data packets, and an event unique digest code and an interface original record index are generated based on the data field correspondence table, including: Before uploading, batch exchanging, or synchronizing files in the source system, a four-time-point interface handshake is performed, and the source system sending time, central system receiving time, central system response time, and source system confirmation time are recorded to obtain the interface handshake record; The interface request identifier, the central system receiving time, the interface response status, and the interface handshake record are associated as the interface original record index; Extract the necessary data fields for the assessment according to the data field correspondence table and construct standard event records; The standard event records are sorted by field name and converted to a uniform format to generate a unique digest code for the event. The event unique digest code is compared with the existing event unique digest codes in the event digest code registration table. Events with the same digest code are treated as duplicate data, and events with different digest codes are used as input for constructing the case file processing node sequence.

[0009] Preferably, a case file processing node sequence is constructed based on the case file type, and the base time of the law enforcement action and the source system record time of each processing node are extracted, including: The case file processing node template is loaded according to the case file type. The case file processing node template includes at least two processing node types from administrative inspection, order to rectify, penalty notice, penalty decision, service of process and case closure. The processing node type corresponding to the unique digest code of the event is matched one by one with the template node to form the case file processing node sequence, and the source system identifier is bound to each processing node; The baseline time of the law enforcement action is extracted in the order of trusted timestamp of electronic signature, collection time of evidence collection device of mobile law enforcement terminal, and first generation time of document business of source system; The time of occurrence of the processing node recorded by the accessed administrative law enforcement business source system shall be used as the recording time of the source system; For processing nodes where the benchmark time of the law enforcement action cannot be extracted, a marker indicating a missing benchmark time for the law enforcement action is generated.

[0010] Preferably, the calculation of the case file data time-series reliability value, node upload delay anomaly value, and central correction record time includes: Estimate the source system clock correction amount and the source system one-way transmission delay based on the interface handshake record; The source system recording time is corrected to the center correction recording time using the source system clock correction amount; Obtain the same type of historical synchronization delay records from the same source system, the same processing node type, the same data element version, and the historical case file processing nodes that have been reviewed, and generate historical synchronization delay baseline values ​​and historical synchronization delay fluctuation values. Based on the central correction record time, the law enforcement behavior reference time, the source system one-way transmission delay, the historical synchronization delay reference value, and the historical synchronization delay fluctuation value, the node upload delay anomaly value is calculated; The percentage of processing nodes in reverse order is calculated based on the central correction record time of adjacent processing nodes; The case file data time-series reliability value is generated based on the node upload delay anomaly value and the reverse order ratio of the processing nodes. Determine the number of case file processing stages.

[0011] Preferably, the list of abnormal processing nodes includes: Read the abnormal values ​​of node upload delays and the time of the center correction record for each processing node within the same case file; Based on the abnormal upload delay values ​​of each processing node within the same case file, generate a case file delay abnormality judgment value. When the abnormal value of the node upload delay of a processing node exceeds the abnormal value of the case file delay judgment, or when the center correction record time of a processing node that is later in the order is earlier than the center correction record time of the adjacent and earlier processing node, the processing node is written into the abnormal processing node list. Write the processing nodes with missing benchmark time markers for the aforementioned law enforcement actions into the list of abnormal processing nodes; The same processing node is recorded only once, and the processing nodes in the abnormal processing node list are bound with the event unique digest code, the source system identifier and the interface original record index.

[0012] Preferably, the automatic acceptance mark for the case file is generated and the agency's assessment case file record is encapsulated, including: Read the historical case files of the same administrative law enforcement agency, the same data element version, and that have been reviewed, and generate an automatic acceptance threshold for the agency based on the temporal reliability value of the case file data in the historical case file set; When the current case file has any of the following conditions: the abnormal processing node list is not empty, the base time of the law enforcement action is missing, the interface handshake record corresponding to the current case file is missing, or the number of processing nodes in the case file is not greater than one, the case file will be automatically marked as requiring manual verification. When the temporal reliability value of the case file data in the current case file reaches or exceeds the automatic acceptance threshold of the agency and the list of abnormal processing nodes is empty, the case file is marked as automatically acceptable. The case file identifier, agency identifier, case file data time sequence reliability value, abnormal processing node list, case file automatic acceptance mark, and interface original record index are encapsulated into the agency assessment case file record.

[0013] Preferably, generating the electronic ledger for the network-connected assessment and management of the administrative law enforcement agency includes: The assessment case records of the aforementioned agencies are sorted according to their agency identifiers; The records of the agency assessment files marked as automatically accreditable are written into the list of automatically accreditable files. The case files automatically marked as agency assessment case files requiring manual verification are added to the case file directory requiring manual verification. Expand the non-empty list of abnormal processing nodes into an abnormal processing node evidence directory, which includes a case file identifier, processing node type, source system identifier, event unique digest code, and interface original record index. The electronic ledger for network-connected assessment and management of the administrative law enforcement agency is converted to a unified format text and a ledger verification digest code is generated. The ledger verification digest code, generation time, data element version, and the source system registration list are written into the ledger cover.

[0014] Secondly, the administrative law enforcement agency performance evaluation and management system, based on network connectivity, is connected to the administrative law enforcement business source system via the network, including: The network connection registration module is used to register network connection objects, lock the necessary data fields for assessment, and generate a source system registration list and a data field correspondence table; The interface record generation module is used to generate interface handshake records before the transmission of business data packets, and generate event unique digest codes and interface original record indexes based on the data field correspondence table. The case file node processing module is used to construct a sequence of case file processing nodes based on the case file type, and extract the base time of law enforcement behavior and the time recorded by the source system for each processing node. The time-series reliability processing module is used to calculate the case file data time-series reliability value, node upload delay anomaly value, and central correction record time based on the interface handshake record, the law enforcement behavior reference time, the source system record time, and similar historical synchronization delay records. An abnormal node location module is used to locate a list of abnormal processing nodes based on the abnormal value of the node upload delay, the time of the central correction record, and the chronological order of the case file processing node sequence. The case file acceptance processing module is used to generate automatic case file acceptance tags based on the case file data time sequence reliability value and the abnormal handling node list, and to encapsulate the agency assessment case file records; The electronic ledger generation module is used to generate an electronic ledger for the online assessment and management of administrative law enforcement agencies based on the agency's assessment case file records.

[0015] Compared with existing technologies, the beneficial effects include: By registering the accessed administrative law enforcement business source systems, locking the necessary data fields for assessment, forming interface handshake records before business data packet transmission, using unique event digest codes for duplicate data identification, generating case file processing node sequences according to case file types, and combining the benchmark time of law enforcement behavior, the record time of the source system, and similar historical synchronization delay records to generate a reliable value for the case file data time sequence, the assessment management system can uniformly handle interface transmission delays, source system time offsets, node upload delays, reversed processing node sequences, and missing benchmark times before the case file data enters the assessment ledger. Compared with methods that rely solely on field completeness, reporting quantity, or manual spot checks, this invention can locate anomalies to specific processing nodes and corresponding interface original record indexes, forming an automatically credible case file directory, a case file directory requiring manual verification, and an evidence directory of abnormal processing nodes. This provides administrative law enforcement agencies with electronic ledger data that is verifiable in source, traceable in node, and distinguishable in directory for assessment management. Attached Figure Description

[0016] Figure 1 This is a schematic diagram of the composition of the network-connected administrative law enforcement agency performance evaluation and management system of the present invention; Figure 2 This is a flowchart illustrating the administrative law enforcement agency performance evaluation and management method based on network connectivity according to the present invention. Figure 3 This is a data flow diagram illustrating the case file data time-series processing and abnormal handling node location of the present invention. Detailed Implementation

[0017] The subject matter described herein will now be discussed with reference to exemplary embodiments. It should be understood that these embodiments are discussed only to enable those skilled in the art to better understand and implement the subject matter described herein, and changes may be made to the function and arrangement of the elements discussed without departing from the scope of this specification. Various processes or components may be omitted, substituted, or added as needed in the examples. Furthermore, features described in some examples may be combined in other examples.

[0018] The following combination Figure 1 , Figure 2 and Figure 3 This paper describes a network-based performance evaluation management system and methodology for administrative law enforcement agencies. All components, processing steps, and data objects are indicated with corresponding reference numerals in the accompanying drawings. Figure 1This is used to represent the network connection structure between the performance management system 100 and the administrative law enforcement business source system 200. Figure 2 This is used to describe the steps and procedures of the assessment and management methods for administrative law enforcement agencies based on network connectivity. Figure 3 The data stream used to represent the calculation and anomaly location of the case file processing node sequence 186 by the case file data time sequence processing unit 400.

[0019] Figure 1 The performance evaluation management system 100 includes a processor 101, a memory 102, a communication interface 103, a network connection registration module 110, an interface record generation module 120, a case file node processing module 130, a time-series reliable processing module 140, an anomaly node location module 150, a case file acceptance processing module 160, and an electronic ledger generation module 170. The processor 101 calls programs stored in the memory 102, causing the network connection registration module 110, interface record generation module 120, case file node processing module 130, time-series reliable processing module 140, anomaly node location module 150, case file acceptance processing module 160, and electronic ledger generation module 170 to perform corresponding processing. The communication interface 103 interacts with the administrative law enforcement business source system 200 via a network connection channel 300. The administrative law enforcement business source system 200 includes at least one of a mobile acquisition terminal 210, a case file processing system 220, a document system 230, a public disclosure system 240, a supervision platform 250, and a data exchange platform 260.

[0020] Figure 2 In this module, S100 corresponds to the network connection registration module 110, outputting the source system registration list 181 and the data field correspondence table 182; S200 corresponds to the interface record generation module 120, outputting the interface handshake record 183, the event unique digest code 184, and the interface original record index 185; S300 corresponds to the case file node processing module 130, outputting the case file processing node sequence 186, the law enforcement behavior benchmark time 187, and the source system record time 188; S400 corresponds to the time sequence reliability processing module 140, outputting the case file data time sequence reliability value 189, the node upload delay anomaly value 190, and the center correction record time 191; S500 corresponds to the abnormal node location module 150, outputting the abnormal processing node list 192; S600 corresponds to the case file acceptance processing module 160, outputting the case file automatic acceptance mark 193 and the agency assessment case file record 194; S700 corresponds to the electronic ledger generation module 170, outputting the administrative law enforcement agency network connection assessment management electronic ledger 180.

[0021] Figure 3In the case file data timing processing unit 400, the handshake record 183, the law enforcement behavior reference time 187, the source system record time 188, and the similar historical synchronization delay record 195 are received. This generates the source system clock correction amount 196, the source system one-way transmission delay 197, the historical synchronization delay reference value 198, the historical synchronization delay fluctuation value 199, the node upload delay anomaly value 190, the central correction record time 191, the reverse order percentage of processing nodes 201, the missing mark of the law enforcement behavior reference time 202, the case file delay anomaly judgment value 203, and the abnormal processing node evidence catalog 204. The abnormal processing node evidence catalog 204 is formed by expanding the abnormal processing node list 192 and inherits the event unique digest code 184, the source system identifier, and the interface original record index 185.

[0022] It should be noted that all time values ​​involved in the calculation are uniformly converted to a continuous numerical representation starting from the same standard epoch. The historical synchronization delay baseline value 198 defaults to 300, the historical synchronization delay fluctuation value 199 defaults to 120, and the smoothing parameter... The value is 0.001, and all values ​​are calculated using the same numerical caliber as the time values. The numerical dimensions are automatically matched during the calculation process, and the relevant technical personnel can directly complete the calculation and comparison of all time series parameters based on this unified caliber.

[0023] It should be noted that "reviewed" means that the corresponding historical case file or historical processing node has been manually verified and the data has been confirmed to be true and valid. The review is completed by operators with law enforcement data verification authority. Data that has passed the review is marked as reviewed and stored in the historical database. The same historical synchronization delay record 195 and the collection of historical case files of the agency are only selected from the data marked as reviewed. The sample collection is completed by reading the status identifier corresponding to the data during the selection process.

[0024] It should be noted that a valid processing node refers to a processing node that simultaneously meets three conditions: the processing node type successfully matches the case file processing node template, the source system records the time field 188 as non-empty, and the event unique digest code 184 is successfully generated and not judged as duplicate data. Processing nodes that do not simultaneously meet the above three conditions are not included in the case file processing node sequence 186. When the number of valid processing nodes in the case file is 0, it is determined that no valid processing node has been formed and will not enter the subsequent case file data time sequence reliability value 189 calculation process.

[0025] Example 1: like Figure 1 and Figure 2As shown, the network connection registration module 110 executes S100, registers the network connection object, locks the necessary data fields for assessment, and generates a source system registration list 181 and a data field correspondence table 182. When the administrative law enforcement business source system 200 connects for the first time, the network connection registration module 110 receives the source system identifier, data element version, processing node type enumeration, connection protocol type, and interface authentication information submitted by the administrative law enforcement business source system 200, registers each connected administrative law enforcement business source system 200 as a unique source system record, and writes the unique source system record into the source system registration list 181.

[0026] The source system registration list 181 includes at least the source system identifier, source system name, affiliated agency identifier, access time, data element version, enumeration of processing node types, and connection protocol type. The source system registration list 181 is stored in an append-only manner. When the access information of the administrative law enforcement business source system 200 changes, the network connection registration module 110 adds a change record while maintaining the traceability of the original source system records.

[0027] The network connection registration module 110 locks the agency identifier, case file identifier, case file type, processing node type, document type, source system record time, central system reception time, interface request identifier, data element version, original document digest code, and interface response status as necessary data fields for assessment. These necessary data fields are configured in the field configuration table, corresponding to the field name, data type, length constraint, whether it is required, and validation rules. The central system reception time is generated by the assessment management system 100, and the interface response status is written by the assessment management system 100 after processing the business data packet.

[0028] The data field mapping table 182 is generated by the network connection registration module 110 based on the source system identifier, data element version, and processing node type. The preset administrative law enforcement data element mapping rules include standard field names, data type conversion rules, enumeration mapping rules, time format conversion rules, and default value rules. The network connection registration module 110 compares the data element versions submitted by the administrative law enforcement business source system 200 with the preset administrative law enforcement data element mapping rules, establishes mapping relationships for source system fields that can be mapped to the necessary assessment data fields, and writes the mapping relationships into the data field mapping table 182.

[0029] In the pre-defined administrative law enforcement data element correspondence rules, standard field names correspond one-to-one with the necessary data fields for assessment. The data type conversion rules uniformly convert string, numeric, and date fields from the source system into the system's standard data types. The enumeration correspondence rules pre-configure standard enumeration values ​​for six types of processing nodes: administrative inspection, order to rectify, penalty notice, penalty decision, delivery, and case closure, as well as standard enumeration values ​​for document types corresponding to each processing node. Enumeration values ​​submitted by different source systems are matched to the corresponding standard enumeration values ​​through a pre-defined mapping table. The time format conversion rules uniformly convert various source time formats to the RFC3339 format. The default value rules configure system default fill values ​​for non-mandatory fields. When the data field correspondence table 182 is generated, each field submitted by the source system is compared with the standard field. If a match is found, a mapping relationship is established and written into the data field correspondence table 182.

[0030] The specific validation rules for essential data fields include: validating the format and non-emptiness of the agency identifier and case file identifier fields; verifying whether the processing node type and document type fields fall within the range of standard enumerated values; validating whether the source system record time field conforms to the RFC3339 format and is within the valid time range; validating the generation sequence of the central system receiving time field; validating whether the interface response status field takes the standard values ​​of success, failure, or pending processing; and validating whether the length of the original document digest codeword conforms to the output length of the corresponding algorithm. Fields that fail validation are processed according to the corresponding rules, and data packets that fail the validation of core fields are rejected from being entered into the database.

[0031] When a business data packet enters the performance evaluation management system 100, the network connection registration module 110 extracts the field content corresponding to the necessary performance evaluation data fields based on the data field correspondence table 182. For fields that are not necessary performance evaluation data fields, the network connection registration module 110 discards the field. For data packets lacking agency identifiers, case file identifiers, processing node types, or source system record times, the network connection registration module 110 rejects the data packet from being added to the database. For data packets lacking interface request identifiers, data element versions, original document digest codes, central system reception times, or interface response status, the network connection registration module 110 processes them according to the generation source or verification rules of the corresponding fields; if these cannot be corrected, the case file acceptance processing module 160 subsequently determines the corresponding case file automatic acceptance mark 193 as requiring manual verification.

[0032] The default field correction rules are as follows: When the interface request identifier field is missing, the assessment management system 100 will automatically generate a globally unique string identifier and fill it into the corresponding field when the data packet is received; when the data element version field is missing, the latest data element version registered by the corresponding source system will be used by default to fill it in; when the original document digest code field is missing, it will be calculated and filled in using the SHA-256 algorithm consistent with the event unique digest code 184 based on the document content in the data packet; the central system receiving time will be automatically generated by the assessment management system 100 when the data packet is received; the interface response status field will be automatically written by the assessment management system 100 after the data packet processing is completed; if the above fields still cannot obtain a valid value after correction, it will be judged as a correction failure.

[0033] Example 2: like Figure 1 and Figure 2 As shown, the interface record generation module 120 executes S200, generating an interface handshake record 183 before the transmission of business data packets, and generating an event unique digest code 184 and an interface original record index 185 based on the data field correspondence table 182. Before uploading, batch exchanging, or synchronizing files, the administrative law enforcement business source system 200 performs a four-time-point interface handshake with the assessment management system 100 through the network connection channel 300. The four-time-point interface handshake includes the source system sending time, the central system receiving time, the central system response time, and the source system confirmation time.

[0034] The complete interaction process of the four-time-point interface handshake is as follows: The administrative law enforcement business source system 200 initiates a handshake request and records the sending time of the source system, and sends this time value to the assessment management system 100 along with the handshake request message; After receiving the handshake request, the assessment management system 100 records the receiving time of the central system, generates a handshake response message after processing, records the response time of the central system, and returns the receiving time and response time of the central system to the administrative law enforcement business source system 200 along with the response message; After receiving the response, the administrative law enforcement business source system 200 records the confirmation time of the source system, completing a single handshake interaction; The handshake is triggered before each batch of business data is uploaded, and the timeout for a single handshake is set to 5000 seconds. After the timeout, it will automatically retry up to 3 times. If the retry fails, it is determined that the handshake is missing; The business data packet and the corresponding handshake record are bound and associated with the source system identifier and the session identifier of the same batch.

[0035] The rationality verification of the four-time interface handshake adopts the time sequence relationship within the same system. For the administrative law enforcement business source system 200, the source system's sending time should be earlier than the source system's confirmation time; for the assessment management system 100, the central system's receiving time should be earlier than the central system's response time. The cross-system offset between the source system's sending time, the central system's receiving time, the central system's response time, and the source system's confirmation time is not used as the absolute sequence verification basis before correction, but is incorporated into the calculation of the source system's clock correction amount 196 and the source system's one-way transmission delay 197.

[0036] After completing the four-timepoint interface handshake, the interface record generation module 120 binds the source system's sending time, the central system's receiving time, the central system's response time, the source system's acknowledgment time, and the source system's identifier to generate an interface handshake record 183. When the business data packet arrives at the assessment management system 100, the interface record generation module 120 extracts the interface request identifier, the central system's receiving time, and the interface response status, and associates these with the corresponding interface handshake record 183 to form an interface raw record index 185. The interface raw record index 185 may also include the source system's IP address, receiving port information, and the business data packet length.

[0037] The interface record generation module 120 extracts the necessary data fields for assessment according to the data field correspondence table 182 and constructs a standard event record. The standard event record includes a stable set of fields for generating the unique event digest code 184 and a set of interface fields associated with the original interface record index 185. The stable set of fields for generating the unique event digest code 184 includes the agency identifier, case file identifier, case file type, processing node type, document type, source system record time, data element version, and original document digest code. The interface request identifier, central system reception time, and interface response status are not used as digest input fields for the unique event digest code 184; they are only entered into the original interface record index 185.

[0038] The stable sorting rule for field names is uniquely determined to be arranged in a fixed order according to the agency identifier, case file identifier, case file type, processing node type, document type, source system record time, data element version, and original document digest code. The interface record generation module 120 sorts the stable field set used for generating the event unique digest code 184 according to this fixed order and performs a unified format conversion. The unified format conversion includes converting string fields to UTF-8 encoding, converting time fields to RFC3339 format, converting enumeration fields to system standard enumeration values, and handling whitespace characters according to preset rules. The stable field set after unified format conversion is serialized using JSONCanonicalizationScheme, and then the digest value is calculated using SHA-256 to obtain the event unique digest code 184. The event unique digest code 184 is represented by 64 lowercase hexadecimal characters.

[0039] The default rules for handling whitespace characters are as follows: remove all leading and trailing spaces, tabs, newlines, and carriage returns from the field content; replace consecutive whitespace characters in the middle of the field content with a single half-width space; convert full-width spaces to half-width spaces before performing the above processing; the processed field content then participates in subsequent JSON serialization and digest calculation to ensure that field content with the same semantics generates consistent serialization results.

[0040] The interface original record index 185 is stored in a list structure. Each index uses the event unique digest code 184 as the primary key and is associated with the corresponding source system identifier, case file identifier, processing node type, central system receiving time, interface response status, and interface request identifier set. When a duplicate event is detected, the interface request identifier corresponding to the event is appended to the end of the interface request identifier set of the corresponding index. Before appending, it is automatically checked whether the same identifier already exists in the set. If it does, the appending is skipped to ensure that there are no duplicate identifiers in the set. All interface request records of the same event can be traced and queried through the interface original record index 185.

[0041] The interface record generation module 120 compares the unique event digest code 184 with the existing unique event digest codes 184 in the event digest code registration table. Events with matching digest codes are treated as duplicate data, and the interface record generation module 120 adds the corresponding interface request identifier to the interface original record index 185, without using the event as input for constructing the case file processing node sequence 186. Events with inconsistent digest codes are used as input for constructing the case file processing node sequence 186.

[0042] Example 3: like Figure 1 and Figure 2As shown, the case file node processing module 130 executes S300, constructs a case file processing node sequence 186 based on the case file type, and extracts the base time of the enforcement action 187 and the source system record time 188 for each processing node. The case file node processing module 130 loads the case file processing node template according to the case file type. The case file processing node template includes at least two processing node types from administrative inspection, order to rectify, penalty notice, penalty decision, service of process, and case closure.

[0043] The case file processing node templates are configured according to the case file type. For administrative penalty case files, the processing node templates are in the following order: administrative inspection, order to rectify, penalty notice, penalty decision, service of process, and case closure. For administrative enforcement case files, the processing node templates are in the following order: administrative inspection, enforcement notice, enforcement decision, service of process, and case closure. For administrative inspection case files, the processing node templates are in the following order: administrative inspection, order to rectify, and case closure. After reading the case file type of the current case file, the case file node processing module 130 loads the processing node template of the corresponding type, matches the processing node type of the event one by one, and if the match is successful, writes it into the case file processing node sequence 186 according to the template order.

[0044] The case file node processing module 130 reads the processing node type corresponding to the event unique digest code 184 and matches the processing node type with the template nodes in the case file processing node template one by one. Upon successful matching, the case file node processing module 130 writes the processing node into the case file processing node sequence 186 and binds the processing node with the source system identifier, event unique digest code 184, interface original record index 185, source system record time 188, document type, and original document digest code. The case file processing node sequence 186 is organized according to the order of the case file processing node templates; when multiple processing nodes exist for the same processing node type, they are organized according to the order of the central system's receiving time.

[0045] The specific rules for extracting the benchmark time 187 for law enforcement actions are as follows: First, read the trusted timestamp of the electronic signature attached to the document corresponding to the processing node, and verify the electronic signature through the built-in trusted root certificate. If the verification is successful and the timestamp has not been tampered with, the time value corresponding to the timestamp is used as the benchmark time 187 for law enforcement actions. If there is no verifiable trusted timestamp of the electronic signature, read the device collection time field in the metadata of the evidence collection file of the corresponding mobile law enforcement terminal. This field is an extended collection field of the necessary data fields for assessment. If it is verified to be natively generated by the terminal and has not been tampered with, it is used as the benchmark time 187 for law enforcement actions. If neither of the above two exists, extract the business time corresponding to the first generation of the document from the document generation log of the source system. This time is uploaded synchronously with the extended field of the business data packet. If it is verified to be valid, it is used as the benchmark time 187 for law enforcement actions. If no valid time value can be obtained after the above three levels of extraction, a missing benchmark time 202 for law enforcement actions is generated.

[0046] The case file node processing module 130 extracts the law enforcement action benchmark time 187 in the following order: trusted timestamp of electronic signature, collection time of evidence-gathering device of mobile law enforcement terminal, and first document generation time of source system. If the trusted timestamp of electronic signature exists and is verified, the case file node processing module 130 uses the time value corresponding to the trusted timestamp of electronic signature as the law enforcement action benchmark time 187; if there is no available trusted timestamp of electronic signature but there is a collection time of evidence-gathering device of mobile law enforcement terminal, the case file node processing module 130 uses the collection time of evidence-gathering device of mobile law enforcement terminal as the law enforcement action benchmark time 187; if neither of the above exists but the first document generation time of source system can be obtained, the case file node processing module 130 uses the first document generation time of source system as the law enforcement action benchmark time 187.

[0047] When there are multiple processing nodes of the same processing node type, they are first sorted in ascending order according to the time of receipt by the central system. When the central system receipt times of multiple nodes are exactly the same, they are further sorted in ascending order according to the lexicographical order of the unique event digest code 184 to ensure that the node order is uniquely determined and to avoid uncertainty in the sorting result due to the same time, which would affect the consistency of the calculation of the reverse order ratio of subsequent processing nodes and the location of abnormal nodes.

[0048] The source system records time 188, which is written into the business data packet after the administrative law enforcement business source system 200 records the occurrence time of the processing node. The case file node processing module 130 does not modify the original field content of the source system record time 188, and provides the source system record time 188 to the time sequence reliable processing module 140 for central correction of the record time 191 calculation. For processing nodes where the benchmark time 187 of the law enforcement behavior cannot be extracted, the case file node processing module 130 generates a benchmark time missing flag 202 for the law enforcement behavior and binds the benchmark time missing flag 202 to the corresponding processing node.

[0049] When no valid processing node is formed in the case file processing node sequence 186, the case file node processing module 130 does not enter the calculation of the case file data time series reliability value 189, and hands over the corresponding case file to the case file acceptance processing module 160 to determine that it needs to be manually verified. When only one valid processing node is formed in the case file processing node sequence 186, the case file node processing module 130 records the number of case file processing nodes as 1, and the time series reliability processing module 140 processes it according to the single node rule in S400.

[0050] Example 4: like Figure 1 , Figure 2 and Figure 3As shown, the time-series reliability processing module 140 executes S400, calculating the case file data time-series reliability value 189, the node upload delay anomaly value 190, and the center correction record time 191 based on the interface handshake record 183, the law enforcement behavior reference time 187, the source system record time 188, and the similar historical synchronization delay record 195. Before calculation, the case file data time-series processing unit 400 converts the time values ​​involved in the formula in the interface handshake record 183, the law enforcement behavior reference time 187, and the source system record time 188 into a unified format so that they participate in the calculation with the same computable data type.

[0051] The median is calculated using the same lower median rule: when the sample size is odd, the middle value of the sorted sample is taken as the median; when the sample size is even, the lower median is taken as the middle value of the sorted sample. The median is the sample value of 1 / 2 digits. The total sample size; the median absolute deviation is calculated using the following formula: ; All calculations involving the median and median absolute deviation shall uniformly follow the above-mentioned median value determination rules.

[0052] The timing-based trusted processing module 140 maintains a set of 183 interface handshake records for each source system identifier. Interface handshake record collection The minimum calculable sample size is 3 records. When the number of valid interface handshake records 183 in the set is less than 3, it is determined that the calculation conditions are not met, and the source system clock correction amount 196 and the source system one-way transmission delay 197 are not generated; Interface handshake record set A rolling update mechanism is adopted, which only retains the valid handshake records of the corresponding source system within the last 7 days. New interface handshake records 183 are automatically appended to the end of the set after they are generated. Interface handshake records 183 that are out of time range are automatically removed from the set, ensuring that the set data always reflects the latest clock and network latency status of the source system.

[0053] When the interface handshake record 183 is missing, or When there is no interface handshake record 183 available for median calculation, the timing reliability processing module 140 does not generate the source system clock correction amount 196 and the source system one-way transmission delay 197, and hands over the corresponding case file to the case file acceptance processing module 160 to determine that it needs to be manually verified.

[0054] when When the calculation conditions are met, the timing reliability processing module 140 estimates the source system clock correction amount 196 and the source system one-way transmission delay 197 based on the interface handshake record 183. Indicates the source system identifier. This indicates that the interface handshake record 183 is in The serial number in Indicates source system identifier The corresponding interface handshake record set 183, Indicates the first The source system's sending time is recorded in the interface handshake record 183. Indicates the first The central system receiving time is recorded in the interface handshake record 183. Indicates the first The central system response time is recorded in the interface handshake record 183. Indicates the first The source system confirmation time is recorded in the interface handshake record 183. This indicates that the source system clock correction amount is 196. This indicates a one-way transmission delay of 197 in the source system.

[0055] The timing reliability processing module 140 uses the source system clock correction amount 196 to correct the source system recording time 188 to the center correction recording time 191. Indicates case file identification, Indicates the case file The sequence number of the processing node. Indicates the case file No. The source system record time for each processing node is 188. Indicates the case file No. The source system identifier corresponding to each processing node Indicates the case file No. The central calibration record time for each processing node is 191.

[0056] The time-series reliable processing module 140 retrieves similar historical synchronization delay records 195 from historical case processing nodes that are from the same source system, have the same processing node type, the same data element version, and have been reviewed. To avoid overlapping variable meanings, Indicates the case file No. The processing node type corresponding to each processing node. Indicates source system identifier Processing node types And the set of 195 historical synchronization delay records of the same type under the corresponding data element version.

[0057] The selection rules for historical synchronization delay record 195 are as follows: From the reviewed historical case file database, historical processing node data with consistent source system identifiers, consistent processing node types, and consistent data element versions are selected. The time range is limited to records within 90 days prior to the current time. Historical nodes marked as abnormal data are automatically excluded during the selection process. When the number of valid records obtained from the selection is greater than or equal to 100, the historical synchronization delay baseline value 198 and the historical synchronization delay fluctuation value 199 are calculated using actual samples. If there are fewer than 100 records, the default values ​​are used directly for calculation.

[0058] When the calculation conditions are met for similar historical synchronization delay record 195, the time-series reliable processing module 140 generates a historical synchronization delay baseline value 198 and a historical synchronization delay fluctuation value 199. This indicates the historical file identifier in historical synchronous delay record 195 of the same type. Representing historical files The benchmark time for enforcement actions at the corresponding processing nodes is 187. Representing historical files The corresponding processing node's central calibration record time is 191. This indicates a historical synchronization delay baseline value of 198. This indicates a historical synchronization delay fluctuation value of 199. When the number of similar historical synchronization delay records (195) is less than 100, the historical synchronization delay baseline value (198) defaults to 300, and the historical synchronization delay fluctuation value (199) defaults to 120.

[0059] The scenario where default values ​​cannot be obtained specifically refers to the following: the corresponding source system and processing node type do not have a default historical synchronization delay baseline value of 198 and a historical synchronization delay fluctuation value of 199 configured in the system, and the number of similar historical synchronization delay records 195 is 0, making it impossible to calculate through samples or read default values. In this scenario, the corresponding case file is directly determined to require manual verification and will not enter the subsequent automatic acceptance and judgment process to ensure that all calculation steps have legal numerical inputs and avoid calculation anomalies.

[0060] The time-series reliable processing module 140 calculates the node upload delay anomaly 190 based on the central correction record time 191, the law enforcement behavior reference time 187, the source system one-way transmission delay 197, the historical synchronization delay reference value 198, and the historical synchronization delay fluctuation value 199. Indicates the case file No. The node upload latency anomaly value of 190 was observed at the processing node. Indicates the case file No. The benchmark time for enforcement actions at each processing node is 187. The value is 0.001, used to keep the denominator computable when the historical synchronization delay fluctuation value 199 is 0, and to use the same calculation method as the historical synchronization delay fluctuation value 199. For processing nodes with the law enforcement behavior benchmark time missing marker 202, the node upload delay anomaly value 190 is set to 100.

[0061] The time-series reliable processing module 140 calculates the reverse-order percentage of processing nodes 201 based on the center correction record time 191 of adjacent processing nodes. Indicates the case file The number of case file processing nodes, This indicates an indicator function that returns 1 if the condition is true and 0 if the condition is false. Indicates the case file The percentage of processing nodes in reverse order is 201. When the number of processing nodes is 1, the percentage of processing nodes in reverse order is set to 1. When the number of processing nodes is 0, the percentage of processing nodes in reverse order is not calculated, and the corresponding case file is handed over to the case file acceptance and processing module 160 to be determined as requiring manual verification.

[0062] The time-series reliable processing module 140 generates a case file data time-series reliable value of 189 based on the node upload delay anomaly value of 190 and the reverse order ratio of processing nodes of 201. Indicates the case file The case file data time-series reliability value is 189. The smaller the node upload delay anomaly value 190 and the smaller the percentage of reverse-order processing nodes 201, the higher the case file data time-series reliability value 189. After the time-series reliability processing module 140 completes the calculation of the case file data time-series reliability value 189, it determines the number of case file processing nodes and provides the case file data time-series reliability value 189, node upload delay anomaly value 190, center correction record time 191, percentage of reverse-order processing nodes 201, and missing enforcement behavior benchmark time marker 202 to the abnormal node location module 150.

[0063] Example 5: like Figure 1 , Figure 2 and Figure 3As shown, the abnormal node location module 150 executes S500, locating the abnormal processing node list 192 based on the node upload delay anomaly value 190, the central correction record time 191, and the order of the case file processing node sequence 186. The abnormal node location module 150 reads the node upload delay anomaly value 190 and the central correction record time 191 of each processing node within the same case file, and generates a delay anomaly judgment value 203 within the case file. Indicates the case file The set of processing node sequence numbers, This represents the function for calculating the absolute median deviation. Indicates the case file The case file delay anomaly judgment value is 203. When the number of case file processing nodes is less than 3, the case file delay anomaly judgment value 203 is fixed at 3.

[0064] The abnormal node location module 150 traverses the case file processing node sequence 186. When the node upload delay anomaly value 190 of a processing node exceeds the case file delay anomaly judgment value 203, the abnormal node location module 150 writes the processing node into the abnormal processing node list 192. When the center correction record time 191 of a later processing node is earlier than the center correction record time 191 of the adjacent and earlier processing node, the abnormal node location module 150 writes the later processing node into the abnormal processing node list 192. When a processing node has a missing law enforcement action reference time marker 202, the abnormal node location module 150 writes the processing node into the abnormal processing node list 192.

[0065] The deduplication process for the abnormal processing node list 192 uses the unique event digest code 184 as the sole criterion. It iterates through all nodes in the abnormal processing node list 192. If multiple nodes correspond to the same unique event digest code 184, only one record is retained, and all abnormal reason identifiers corresponding to that node are merged. After deduplication, each processing node in the abnormal processing node list 192 appears only once and carries all abnormal type information triggered by that node, ensuring that the result of the abnormal processing node list 192 is unique and the abnormal information is complete.

[0066] The abnormal node location module 150 performs deduplication on the abnormal processing node list 192, ensuring that each processing node is recorded only once. The abnormal node location module 150 binds the processing nodes in the abnormal processing node list 192 with the event unique digest code 184, the source system identifier, and the interface original record index 185. The abnormal processing node list 192 is subsequently expanded by the electronic ledger generation module 170 to form the abnormal processing node evidence catalog 204.

[0067] Example 6: like Figure 1 and Figure 2 As shown, the case file acceptance processing module 160 executes S600, generating an automatic case file acceptance marker 193 based on the case file data time-series reliability value 189 and the abnormal handling node list 192, and encapsulating the agency assessment case file record 194. The case file acceptance processing module 160 reads a set of historical case files from the same administrative law enforcement agency, using the same data element version, and that have already been reviewed, and generates an automatic agency acceptance threshold based on the case file data time-series reliability value 189 in the historical case file set. Indicates the identity of an administrative law enforcement agency. Indicator of administrative law enforcement agency logo The historical case file collection corresponding to the data meta version, This represents the threshold for automatic acceptance by the relevant authorities. When the number of historical case files is less than 50, the automatic acceptance threshold is set to 0.8 by default. If the calculated automatic acceptance threshold is less than 0, it is treated as 0; if the calculated automatic acceptance threshold is greater than 1, it is treated as 1.

[0068] The case file acceptance and processing module 160 checks whether the current case file has any of the following conditions: the abnormal processing node list 192 is not empty; the law enforcement action benchmark time is missing marker 202; the interface handshake record corresponding to the current case file is missing 183; the number of case file processing nodes is not more than one; no valid processing node has been formed; or the similar historical synchronization delay records 195 are insufficient and the default value cannot be obtained. If any of these conditions exist, the case file acceptance and processing module 160 determines that the case file automatic acceptance marker 193 requires manual verification.

[0069] When the case file's data time-series reliability value 189 reaches or exceeds the automatic acceptance threshold of the agency, and the abnormal processing node list 192 is empty, and there is no missing law enforcement action benchmark time marker 202, and the interface handshake record 183 corresponding to the current case file is not missing, and the number of case file processing nodes is greater than one, the case file acceptance processing module 160 determines the case file automatic acceptance marker 193 as automatically acceptable. When the current case file does not meet the conditions for automatic acceptance, the case file acceptance processing module 160 determines the case file automatic acceptance marker 193 as requiring manual verification.

[0070] The case file acceptance processing module 160 encapsulates the case file identifier, agency identifier, case file data time sequence reliability value 189, abnormal processing node list 192, automatic case file acceptance mark 193, and interface original record index 185 into an agency assessment case file record 194. The agency assessment case file record 194 maintains a traceable relationship with the source system registration list 181, data field correspondence table 182, event unique digest code 184, and case file processing node sequence 186.

[0071] The traceability relationship between the agency assessment case file record 194 and the source system registration list 181, data field correspondence table 182, event unique digest code 184, and case file processing node sequence 186 is achieved through foreign key association. The agency assessment case file record 194 stores related fields such as source system identifier, data element version number, event unique digest code 184, and case file identifier. Through the corresponding fields, the source system registration information in the source system registration list 181, the field mapping information in the data field correspondence table 182, the original event information corresponding to the event unique digest code 184, and the node details information in the case file processing node sequence 186 can be retrieved and matched respectively. All related queries are completed through field matching to ensure that the data in the whole chain can be traced forward and verified backward.

[0072] Example 7: like Figure 1 and Figure 2 As shown, the electronic ledger generation module 170 executes S700 to generate the administrative law enforcement agency network-connected assessment management electronic ledger 180 based on the agency assessment case file records 194. The electronic ledger generation module 170 sorts the agency assessment case file records 194 according to the agency identifier, and the agency assessment case file records 194 under the same agency identifier are sorted according to the case file data time sequence reliability value 189.

[0073] The electronic ledger generation module 170 writes the automatically accepted case file marker 193 (marked as automatically accepted agency assessment case file record 194) into the automatically accepted case file directory, and writes the automatically accepted case file marker 193 (marked as requiring manual verification agency assessment case file record 194) into the manual verification case file directory. The electronic ledger generation module 170 expands the non-empty abnormal handling node list 192 into an abnormal handling node evidence directory 204. The abnormal handling node evidence directory 204 includes a case file identifier, handling node type, source system identifier, event unique digest code 184, and interface original record index 185.

[0074] The specific rules for unified format text conversion are as follows: all directory, record, and list data to be converted are uniformly converted to UTF-8 encoded JSON format. Before conversion, all field names are sorted in a preset fixed order, and field values ​​are output in the standard format of the corresponding data type. Date fields are uniformly formatted according to RFC3339, string fields are uniformly delimited by removing leading and trailing whitespace, and numeric fields are uniformly formatted as decimal floating-point. The converted JSON text is output in a compact format with no extra spaces or line breaks, ensuring that data with the same content outputs completely consistent text results after conversion.

[0075] When generating the ledger verification digest code, the system first performs a uniform format text conversion on each part of the content in a preset fixed order: source system registration list 181, agency assessment case file record 194, automatically accreditable case file directory, case file directory requiring manual verification, and abnormal handling node evidence directory 204. All the converted text content is then concatenated into a complete string in sequence, and the SHA-256 algorithm is used to calculate the digest value of the complete string. The final digest value is output in 64-bit lowercase hexadecimal character format, which is the ledger verification digest code. The verification digest codes generated for the same ledger content are completely identical and can be used for ledger integrity and anti-tampering verification.

[0076] The electronic ledger generation module 170 performs a unified format text conversion on the electronic ledger 180 for network-connected assessment and management of administrative law enforcement agencies and generates a ledger verification digest code. The ledger verification digest code is calculated by converting the automatically accepted case file directory, the case file directory requiring manual verification, the abnormal handling node evidence directory 204, the agency assessment case file record 194, and the source system registration list 181 into a unified format text in a preset order. The electronic ledger generation module 170 writes the ledger verification digest code, generation time, data element version, and source system registration list 181 into the ledger cover, forming the electronic ledger 180 for network-connected assessment and management of administrative law enforcement agencies.

[0077] Example 8: like Figure 1 As shown, the network connection registration module 110 includes source system registration processing, assessment necessary data field locking processing, data field correspondence table 182 generation processing, and data packet entry verification processing. The output of the network connection registration module 110 enters the interface record generation module 120 and the electronic ledger generation module 170.

[0078] The interface record generation module 120 includes interface handshake record generation processing 183, interface original record index association processing 185, standard event record construction processing, event unique digest code generation processing 184, and duplicate data identification processing. The output of the interface record generation module 120 enters the case file node processing module 130 and the electronic ledger generation module 170.

[0079] The case file node processing module 130 includes case file processing node template loading processing, processing node type matching processing, case file processing node sequence 186 construction processing, law enforcement behavior reference time 187 extraction processing, source system record time 188 extraction processing, and law enforcement behavior reference time missing marker 202 generation processing. The output of the case file node processing module 130 enters the time sequence reliability processing module 140.

[0080] The time-series reliability processing module 140 includes the following processing steps: source system clock correction amount 196 calculation and processing, source system one-way transmission delay 197 calculation and processing, central correction record time 191 calculation and processing, similar historical synchronization delay record reading 195 reading and processing, historical synchronization delay benchmark value 198 generation and processing, historical synchronization delay fluctuation value 199 generation and processing, node upload delay anomaly value 190 calculation and processing, processing of reverse order ratio of processing nodes 201 calculation and processing, and case file data time-series reliability value 189 generation and processing. The output of the time-series reliability processing module 140 enters the abnormal node location module 150 and the case file acceptance processing module 160.

[0081] The abnormal node location module 150 includes the generation and processing of case file delay anomaly judgment values ​​203, comparison and processing of node upload delay anomaly values ​​190, reverse order judgment and processing of central correction record time 191, identification and processing of missing law enforcement behavior benchmark time markers 202, deduplication processing of abnormal handling node list 192, and binding processing of abnormal handling node list 192. The output of the abnormal node location module 150 enters the case file acceptance processing module 160 and the electronic ledger generation module 170.

[0082] The case file acceptance processing module 160 includes automatic acceptance threshold generation processing, automatic acceptance judgment processing, manual verification judgment processing, automatic acceptance tag generation processing (193), and case file recording encapsulation processing (194). The output of the case file acceptance processing module 160 enters the electronic ledger generation module 170.

[0083] The electronic ledger generation module 170 includes automatic processing for generating case file catalogs, processing for generating case file catalogs requiring manual verification, processing for generating evidence catalogs for abnormal handling nodes (204), processing for generating ledger verification digest codes, and processing for generating ledger covers. The electronic ledger generation module 170 ultimately outputs the electronic ledger 180 for online assessment and management by administrative law enforcement agencies.

[0084] Data transfer between modules is achieved through synchronous calls combined with database transfer. After the upstream module completes its processing, it writes the result data to the corresponding database table and sends a processing trigger signal to the downstream module. Upon receiving the trigger signal, the downstream module reads the result data written by the upstream module and starts its own processing flow. The data processing triggering timing adopts an event-driven model. When a single business data packet arrives, it triggers the full-link processing of the corresponding single case file. At a fixed time every day, it triggers batch historical data statistics and core parameter updates. If an exception occurs during processing, it automatically retryes up to 2 times. If the retry fails, it is marked as abnormal data and transferred to the manual processing queue to ensure stable and controllable data flow.

[0085] The source system clock correction value 196 and the source system one-way transmission delay 197 adopt a real-time update mechanism. After each valid four-time point interface handshake is completed, the corresponding source system interface handshake record set 183 is automatically updated, and the corresponding parameters are recalculated. The historical synchronization delay benchmark value 198 and the historical synchronization delay fluctuation value 199 adopt a daily timed update mechanism. Every morning, the system automatically counts the same historical data from the past 90 days and recalculates the corresponding parameters. The automatic acceptance threshold of the agency adopts a weekly timed update mechanism. Every Monday morning, the system automatically counts the reviewed historical case data from the past 180 days of the corresponding agency and recalculates the threshold. When all parameter updates fail, the most recently calculated parameter value is automatically used, and an abnormal alarm is generated to ensure uninterrupted system operation.

[0086] Specifically, in a complete data flow, the administrative law enforcement business source system 200 initiates a four-time-point interface handshake to the assessment management system 100 through the network connection channel 300, and the interface record generation module 120 generates an interface handshake record 183. After the business data packet arrives, the network connection registration module 110 extracts the necessary assessment data fields according to the data field correspondence table 182, and the interface record generation module 120 generates an interface original record index 185 and an event unique digest code 184. When the event unique digest code 184 does not match the event digest code registration table, the corresponding event enters the case file node processing module 130.

[0087] The case file node processing module 130 loads the case file processing node template according to the case file type, writes the processing node type into the case file processing node sequence 186, and extracts the law enforcement behavior benchmark time 187 in the order of electronic signature trusted timestamp, mobile law enforcement terminal evidence collection device acquisition time, and the time when the source system first generates the document business, while retaining the source system record time 188. The time sequence trusted processing module 140 calculates the source system clock correction amount 196 and the source system one-way transmission delay 197 according to the interface handshake record 183, generates the center correction record time 191 according to the source system record time 188, and generates the historical synchronization delay benchmark value 198 and the historical synchronization delay fluctuation value 199 by combining the similar historical synchronization delay record 195.

[0088] The time-series reliability processing module 140 further calculates the node upload delay anomaly value 190, the reverse order ratio of processing nodes 201, and the case file data time-series reliability value 189. The anomaly node location module 150 generates an anomaly processing node list 192 based on the node upload delay anomaly value 190, the central correction record time 191, the sequence of case file processing nodes 186, and the missing enforcement action benchmark time marker 202. The case file acceptance processing module 160 generates an automatic case file acceptance marker 193 based on the case file data time-series reliability value 189, the anomaly processing node list 192, and the agency's automatic acceptance threshold, and encapsulates the agency's assessment case file record 194. The electronic ledger generation module 170 forms an electronic ledger 180 for the administrative law enforcement agency's network-connected assessment management based on the agency's assessment case file record 194.

[0089] The embodiments of this example have been described above. However, this example is not limited to the specific implementation methods described above. The specific implementation methods described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms based on the guidance of this example, and all of them are within the protection scope of this example.

Claims

1. A network-based performance evaluation and management method for administrative law enforcement agencies, applied to a performance evaluation and management system connected to the administrative law enforcement business source system via a network, characterized in that: include: Register the network interface objects and lock the necessary data fields for assessment, and generate a source system registration list and a data field correspondence table; Before the transmission of business data packets, an interface handshake record is generated, and an event unique digest code and an interface original record index are generated based on the data field correspondence table. Construct a sequence of case handling nodes based on case file type, and extract the base time of law enforcement behavior and the source system record time for each handling node; Based on the interface handshake record, the law enforcement behavior reference time, the source system record time, and similar historical synchronization delay records, calculate the case file data time sequence reliability value, node upload delay anomaly value, and central correction record time; The list of abnormal processing nodes is located based on the abnormal upload delay value of the node, the time of the central correction record, and the chronological order of the case file processing node sequence; Based on the time-series reliability value of the case file data and the list of abnormal processing nodes, an automatic acceptance mark for the case file is generated, and the case file record for agency assessment is encapsulated. Based on the aforementioned agency assessment case records, an electronic ledger for administrative law enforcement agency network-connected assessment management is generated.

2. The method for performance evaluation and management of administrative law enforcement agencies based on network connectivity as described in claim 1, characterized in that, Register the network interface targets and identify the necessary data fields for assessment, generating a source system registration list and a data field mapping table, including: Each accessed administrative law enforcement business source system is registered as a unique source system record, forming the source system registration list; The following data fields are locked as necessary data fields for the assessment: agency identifier, case file identifier, case file type, processing node type, document type, source system record time, central system reception time, interface request identifier, data element version, original document digest code, and interface response status. Read the source system identifier, data element version, and processing node type enumeration, compare the data element version with the preset administrative law enforcement data element correspondence rules, and obtain the data field correspondence table; Discard fields that are not part of the required data fields for the assessment, and reject data packets that lack agency identifiers, case file identifiers, processing node types, or source system record times from being added to the database.

3. The method for performance evaluation and management of administrative law enforcement agencies based on network connectivity as described in claim 2, characterized in that, Before the transmission of business data packets, an interface handshake record is generated, and an event unique digest code and an interface original record index are generated based on the data field correspondence table, including: Before uploading, batch exchanging, or synchronizing files in the source system, a four-time-point interface handshake is performed, and the source system sending time, central system receiving time, central system response time, and source system confirmation time are recorded to obtain the interface handshake record; The interface request identifier, the central system receiving time, the interface response status, and the interface handshake record are associated as the interface original record index; Extract the necessary data fields for the assessment according to the data field correspondence table and construct standard event records; The standard event records are sorted by field name and converted to a uniform format to generate a unique digest code for the event. The event unique digest code is compared with the existing event unique digest codes in the event digest code registration table. Events with the same digest code are treated as duplicate data, and events with different digest codes are used as input for constructing the case file processing node sequence.

4. The method for performance evaluation and management of administrative law enforcement agencies based on network connectivity as described in claim 3, characterized in that, Construct a sequence of case handling nodes based on case file type, and extract the baseline time of law enforcement actions and the source system record time for each handling node, including: The case file processing node template is loaded according to the case file type. The case file processing node template includes at least two processing node types from administrative inspection, order to rectify, penalty notice, penalty decision, service of process and case closure. The processing node type corresponding to the unique digest code of the event is matched one by one with the template node to form the case file processing node sequence, and the source system identifier is bound to each processing node; The baseline time of the law enforcement action is extracted in the order of trusted timestamp of electronic signature, collection time of evidence collection device of mobile law enforcement terminal, and first generation time of document business of source system; The time of occurrence of the processing node recorded by the accessed administrative law enforcement business source system shall be used as the recording time of the source system; For processing nodes where the benchmark time of the law enforcement action cannot be extracted, a marker indicating a missing benchmark time for the law enforcement action is generated.

5. The method for performance evaluation and management of administrative law enforcement agencies based on network connectivity as described in claim 4, characterized in that, Calculate the case file data time-series reliability value, node upload delay anomalies, and central correction record time, including: Estimate the source system clock correction amount and the source system one-way transmission delay based on the interface handshake record; The source system recording time is corrected to the center correction recording time using the source system clock correction amount; Obtain the same type of historical synchronization delay records from the same source system, the same processing node type, the same data element version, and the historical case file processing nodes that have been reviewed, and generate historical synchronization delay baseline values ​​and historical synchronization delay fluctuation values. Based on the central correction record time, the law enforcement behavior reference time, the source system one-way transmission delay, the historical synchronization delay reference value, and the historical synchronization delay fluctuation value, the node upload delay anomaly value is calculated; The percentage of processing nodes in reverse order is calculated based on the central correction record time of adjacent processing nodes; The case file data time-series reliability value is generated based on the node upload delay anomaly value and the reverse order ratio of the processing nodes. Determine the number of case file processing stages.

6. The method for performance evaluation and management of administrative law enforcement agencies based on network connectivity as described in claim 5, characterized in that, The list of abnormal processing nodes includes: Read the abnormal values ​​of node upload delays and the time of the center correction record for each processing node within the same case file; Based on the abnormal upload delay values ​​of each processing node within the same case file, generate a case file delay abnormality judgment value. When the abnormal value of the node upload delay of a processing node exceeds the abnormal value of the case file delay judgment, or when the center correction record time of a processing node that is later in the order is earlier than the center correction record time of the adjacent and earlier processing node, the processing node is written into the abnormal processing node list. Write the processing nodes with missing benchmark time markers for the aforementioned law enforcement actions into the list of abnormal processing nodes; The same processing node is recorded only once, and the processing nodes in the abnormal processing node list are bound with the event unique digest code, the source system identifier and the interface original record index.

7. The method for performance evaluation and management of administrative law enforcement agencies based on network connectivity as described in claim 6, characterized in that, Generate case files with automatic acceptance tags and encapsulate agency assessment case file records, including: Read the historical case files of the same administrative law enforcement agency, the same data element version, and that have been reviewed, and generate an automatic acceptance threshold for the agency based on the temporal reliability value of the case file data in the historical case file set; When the current case file has any of the following conditions: the abnormal processing node list is not empty, the base time of the law enforcement action is missing, the interface handshake record corresponding to the current case file is missing, or the number of processing nodes in the case file is not greater than one, the case file will be automatically marked as requiring manual verification. When the temporal reliability value of the case file data in the current case file reaches or exceeds the automatic acceptance threshold of the agency and the list of abnormal processing nodes is empty, the case file is marked as automatically acceptable. The case file identifier, agency identifier, case file data time sequence reliability value, abnormal processing node list, case file automatic acceptance mark, and interface original record index are encapsulated into the agency assessment case file record.

8. The method for performance evaluation and management of administrative law enforcement agencies based on network connectivity as described in claim 7, characterized in that, Generate the electronic ledger for the network-connected assessment and management of the administrative law enforcement agency, including: The assessment case records of the aforementioned agencies are sorted according to their agency identifiers; The records of the agency assessment files marked as automatically accreditable are written into the list of automatically accreditable files. The case files automatically marked as agency assessment case files requiring manual verification are added to the case file directory requiring manual verification. Expand the non-empty list of abnormal processing nodes into an abnormal processing node evidence directory, which includes a case file identifier, processing node type, source system identifier, event unique digest code, and interface original record index. The electronic ledger for network-connected assessment and management of the administrative law enforcement agency is converted to a unified format text and a ledger verification digest code is generated. The ledger verification digest code, generation time, data element version, and the source system registration list are written into the ledger cover.

9. A network-connected administrative law enforcement agency performance evaluation and management system, which is network-connected to the administrative law enforcement business source system, characterized in that: include: The network connection registration module is used to register network connection objects, lock the necessary data fields for assessment, and generate a source system registration list and a data field correspondence table; The interface record generation module is used to generate interface handshake records before the transmission of business data packets, and generate event unique digest codes and interface original record indexes based on the data field correspondence table. The case file node processing module is used to construct a sequence of case file processing nodes based on the case file type, and extract the base time of law enforcement behavior and the time recorded by the source system for each processing node. The time-series reliability processing module is used to calculate the case file data time-series reliability value, node upload delay anomaly value, and central correction record time based on the interface handshake record, the law enforcement behavior reference time, the source system record time, and similar historical synchronization delay records. An abnormal node location module is used to locate a list of abnormal processing nodes based on the abnormal value of the node upload delay, the time of the central correction record, and the chronological order of the case file processing node sequence. The case file acceptance processing module is used to generate automatic case file acceptance tags based on the case file data time sequence reliability value and the abnormal handling node list, and to encapsulate the agency assessment case file records; The electronic ledger generation module is used to generate an electronic ledger for the online assessment and management of administrative law enforcement agencies based on the agency's assessment case file records.

Images