A court case status processing system and method thereof

Abstract

The application relates to the technical field of court informatization, and discloses a court case state processing system and a method thereof. In view of the problem that data distortion is caused by the confusion of procedural links and entity trial links in traditional case ratio calculation, and the judicial efficiency cannot be objectively reflected, the system obtains the number of effective cases S, the number of cases already concluded Y, the number of first-instance cases not concluded O, the number of second-instance cases not concluded T, the number of cases not concluded due to jurisdiction objection G and the number of cases not concluded due to service D in real time through a data interface, adopts a case number keyword combined with a flow state double determination algorithm to automatically calculate G and D, executes a formula R=(S+O+T-G-D) / (W+Y) to obtain a case ratio R, and maps the case ratio R into an interactive efficiency heat map. When the case ratio R is lower than a threshold value, a supervision reminder is triggered. The application has been deployed and run in a court, the error rate is reduced to 2%, the manual review working hours are reduced by 35%, and the application can be used for judicial trial quality and efficiency management.

Description

Technical Field

[0001] This invention relates to the field of court information technology, and in particular to a system and method for real-time processing, redundancy elimination, and performance evaluation of litigation case status in an e-government environment. Background Technology

[0002] Current court performance evaluations often use the "case ratio" as a core indicator. Traditional exhaustive or counting methods fail to distinguish between procedural stages such as jurisdictional objections and service of process and substantive trial stages, resulting in an inflated case ratio that cannot objectively reflect trial efficiency. CN107886223A discloses a general case management system, but does not disclose how to perform data cleaning based on case number keywords and the principle of procedural / substantive separation, nor does it provide a quantifiable system architecture. Summary of the Invention

[0003] The technical problem to be solved by the present invention is to provide a system and method that can automatically identify and eliminate procedurally redundant cases in the court business database, thereby outputting real and quantifiable case performance indicators.

[0004] Technical Solution Overview: Seven types of case status parameters are captured in real time through data interfaces; A dual-determination algorithm combining case number keywords and process status is used to automatically calculate G and D; The case ratio is obtained using the formula R=(S+O+T−G−D) / (W+Y) and mapped as a heat map; Two-level verification and follow-up reminders are implemented to improve data quality and review efficiency. Beneficial effects

[0005] Compared with the prior art, the present invention: By legally separating procedural and substantive hearing processes, errors are reduced by more than 20%. Through NLP keyword recognition, automated and low-manual-cost data cleaning can be achieved; Outputs a visual heatmap, supporting real-time resource scheduling and supervision. Attached Figure Description

[0006] Figure 1 System Overall Module Diagram Figure 2 Case Status Processing Flowchart Specific Implementation

[0007] [Example 1] Local server deployment method This embodiment describes how to deploy the "Court Case Status Processing System" on a high-performance server in the local computer room to achieve real-time processing of labor dispute cases of a certain city's intermediate people's court in 2023. The hardware environment is as follows: Server model: Dell PowerEdge R750; CPU: Intel Xeon Silver 4314 (16 cores and 32 threads); Memory: 64 GB DDR4; Hard disk: 2 × 2 TB SSD (RAID 1).

[0008] Operating system: CentOS 8.2; Application running environment: Docker 20.10; Database: PostgreSQL 13, used to cache case status snapshots.

[0009] Step 1: Configuration of the data interface module Connect to the "Court Comprehensive Information Management System" through the court intranet switch with a 10 Gbps fiber optic link.The data interface module pulls the case status table every 10 minutes in the form of RESTful API. The fields include: case number, current stage, closing mark, and effective date. Perform regular matching on the case number field: If the case number contains "jurisdiction" and stage = "jurisdiction objection" and hearing_date IS NULL, then include this case in G; If the case number contains "delivery" and stage = "service procedure" and receipt_flag = 0, then include this case in D.

[0010] Step 2: Operation of the calculation engine After the system starts, the calculation engine loads the snapshot data at 00:00:00 on the current day: S = 120, Y1 = 75, Y2 = 45, O = 25, T = 5, G = 3, D = 2.

[0011] Execute the formula: R = (120 + 25 + 5 - 3 - 2) / (25 + 5 + 75 + 45) = 145 / 150 ≈ 0.967.

[0012] The system compares R with the preset threshold of 0.90 and finds that 0.967 > 0.90, so no supervision is triggered.

[0013] Step 3: Visualization output The output module calls ECharts 5.4 to render the R values of each district court as a heat map, with colors ranging from dark green (R≥1.1) to red (R<0.8). The legend is synchronously embedded on the home page of the intranet portal for the hospital leaders to monitor in real time.

[0014] Step 4: Data logic verification Verification 1: S(120) is equal to Y1+Y2(120), without anomalies; Verification 2: Compare G+D(5) with O+T(30), 5 < 30, without warnings.

[0015] After running this embodiment for 30 days, compared with the traditional case number matching method, the case ratio error is reduced from 22% to 2%, and the manual review working hours are reduced by 35%.

[0016]

Embodiment 2

[0017] Hardware and network topology The private cloud is based on OpenStack Yoga and includes three control nodes, twelve computing nodes, and unified distributed storage Ceph.

[0018] The data interface module runs in the form of microservices in the Kubernetes 1.25 cluster, with each court corresponding to a Pod to achieve elastic scaling.

[0019] The message queue uses Kafka 3.2 to ensure that the case increment synchronization delay between nodes < 1 second.

[0020] Step 1: Provincial data interface Each court pushes the case status increment to the provincial Kafka topic "case_status" in real time. The data format is JSON: {"court_code":"B0101","case_no":"(2023) Jing01 Minchu 100hao","stage":"first instance","close_flag":0,"effective_date":null,"receipt_flag":1} The provincial data interface module uniformly consumes messages, calculates G and D according to the rules of Embodiment 1, and aggregates and generates provincial parameters S, O, T, Y1, and Y2.

[0021] Step 2: Distributed computing The computation engine runs as a Spark Streaming task, calculating the province-wide case ratio R_province and the court's case ratio R_court every 5 minutes. The task script completely reuses the algorithm from Example 1, only adding the partition field court_code.

[0022] Step 3: Multi-level heat map The output module renders R_court into 18 city-level heatmaps via the map service API provided by the provincial data platform; clicking on any city allows drilling down to 120 grassroots courts. Thresholds can be adjusted in real time in the management backend, and adjustment records are written to the audit log.

[0023] Step 4: Anomaly Warning If R_court < 0.8 for any primary court, the system sends a supervision instruction to the director of the court's case management office via SMS gateway; If the provincial R_province < 0.85, the system will automatically generate a "Procedural Process Optimization Suggestion Report" and send it to the email address of the Provincial High Court's Trial Management Office.

[0024] Running effect After six months of continuous operation, the error rate of cases across the province has stabilized at less than 1.5%; the average processing time for jurisdictional objections has been shortened by 4.3 days; and the average service period has been shortened by 2.7 days.

[0025] Through the above two embodiments, those skilled in the art can reproduce the present invention unambiguously in a local standalone environment or a private cloud environment and achieve the same technical effect.

Claims

1. A court case status processing system, characterized in that, include: The data interface module is configured to communicate with the court's business database in real time to obtain case status parameters within the current statistical period. These parameters include at least: the number of effective cases S, the number of concluded cases Y, the number of pending first-instance cases O, the number of pending second-instance cases T, the number of pending jurisdictional objection cases G, and the number of pending service of process cases D. The computing engine is configured to perform the following operations: R=(S+O+T−G−D) / (W+Y), where W=O+T; The output module is configured to map the case ratio R to a visual performance heatmap and trigger a supervisory reminder when R is below a set threshold.

2. The system according to claim 1, wherein, The data interface module further includes: The natural language processing submodule is configured to parse case number text. When the case number contains the character "jurisdiction" and the corresponding case has not entered the substantive trial stage, the case is counted as G; when the case number contains the character "send" and the service receipt registration has not been completed, the case is counted as D.

3. The system according to claim 1 or 2, wherein, The computing engine is also configured to perform data logic verification: If S>Y1+Y2, then mark the effective case data as abnormal and initiate the review process, where Y1 is the number of concluded cases that have only undergone the first instance trial and Y2 is the number of concluded cases that have undergone the second instance trial. If G+D>O+T, then an early warning log is generated indicating an abnormal proportion of procedural steps.

4. The system according to any one of claims 1 to 3, wherein, The visualized performance heatmap uses the administrative divisions of the court's jurisdiction as a layer and supports drill-down analysis by case type.

5. A method for handling the status of court cases, characterized in that, include: The case status parameters S, Y, O, T, G, and D are obtained in real time through the data interface. The case ratio R is calculated using the formula R=(S+O+T−G−D) / (W+Y); R is compared with a preset threshold. When R is lower than the threshold, a supervision signal is sent to the case management platform.

6. The method according to claim 5, wherein, The acquisition step further includes: The case number text is analyzed using a natural language processing model to determine the values ​​of G and D.

7. The method according to claim 5 or 6, wherein, The calculation steps are followed by: Perform logical checks on S, Y1, Y2, G, D and O, T. If the check fails, output an error message.

8. A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method according to any one of claims 5 to 7.

9. The system according to any one of claims 1 to 4, wherein, The data interface module, computing engine, and output module are integrated within the same server or deployed in a distributed manner within the court's private cloud environment.

10. The system according to any one of claims 1 to 4, wherein, The set threshold is adjusted in real time by the court administrator through the configuration interface, and the adjustment results are recorded in the audit log.

Images