Remote monitoring operation and maintenance management system suitable for traffic monitoring equipment

Abstract

The application discloses a remote monitoring operation and maintenance management system suitable for traffic monitoring equipment, relates to the technical field of operation and maintenance management, and comprises a law enforcement docking module, an authority control module, a compliance verification module, a segmented storage module, a two-way anchoring module and a hierarchical traceability module. The application constructs the remote monitoring operation and maintenance management system comprising the law enforcement docking module, the authority control module, the compliance verification module, the segmented storage module, the two-way anchoring module and the hierarchical traceability module, realizes closed-loop control of directional data interaction of serial operation of each module along a data flow conversion time sequence, and compared with the mode that each operation module is loosely associated and data flow conversion is not standardized in the prior art, can improve compliance and process closed-loop of traffic monitoring operation and maintenance, and therefore can solve the technical problems that the existing traffic monitoring operation and maintenance system is disconnected with law enforcement and judicial business, operation and maintenance operation has no clear process control, data flow conversion is disordered, operation and maintenance behavior is not compliant, and the effectiveness of law enforcement evidence cannot be guaranteed.

Description

Technical Field

[0001] This invention relates to the field of operation and maintenance management technology, and in particular to a remote monitoring and operation and maintenance management system applicable to traffic monitoring equipment. Background Technology

[0002] The remote monitoring and maintenance management system collects equipment status, operating data, and environmental parameters in real time to achieve centralized monitoring of distributed equipment, automatic fault early warning, and remote diagnosis and treatment. This significantly reduces on-site inspections and manual intervention, improves maintenance efficiency and response speed, and optimizes maintenance strategies based on historical data analysis to reduce the risk of unplanned downtime and ensure stable, efficient, and safe system operation.

[0003] Currently, the existing remote monitoring and maintenance management system suffers from loosely interconnected functional modules, unstandardized data flow, and lack of standardized and compliant integration with law enforcement and judicial platforms. Furthermore, its access control is chaotic and incompatible with the traffic law enforcement system. Compliance verification for maintenance operations is lax, the evidence storage model is simplistic, and maintenance records are disconnected from law enforcement evidence. This affects the compliance of maintenance activities, the security of stored data, and the validity of law enforcement evidence, making it difficult to meet the needs of compliant maintenance and judicial support in traffic law enforcement scenarios.

[0004] Therefore, a remote monitoring and maintenance management system suitable for traffic monitoring equipment is proposed to solve the above problems. Summary of the Invention

[0005] The main objective of this invention is to provide a remote monitoring and maintenance management system suitable for traffic monitoring equipment, in order to solve the problems mentioned in the background above.

[0006] To achieve the above objectives, the technical solution adopted by this invention is: a remote monitoring and maintenance management system for traffic monitoring equipment, the system comprising an enforcement docking module, an access control module, a compliance verification module, a segmented evidence storage module, a two-way anchoring module, and a hierarchical traceability module, wherein:

[0007] The law enforcement docking module is used to achieve standardized and compliant docking between the system and external law enforcement and judicial platforms, and to complete the synchronization of law enforcement-related data, the receipt of business instructions and the feedback of processing results.

[0008] The access control module is used to construct hierarchical and normalized access rules that are compatible with the traffic law enforcement system based on the legal law enforcement information synchronized by the law enforcement docking module, and to implement closed-loop management of the entire lifecycle of operation and maintenance permissions.

[0009] The compliance verification module is used to perform progressive compliance verification throughout the entire operation and maintenance process, intercept non-compliant operations, and retain corresponding operation records.

[0010] The segmented evidence storage module is used to build a segmented, tamper-proof evidence storage system specifically for traffic law enforcement scenarios, and to perform judicial-level evidence storage control for core operation and maintenance.

[0011] The two-way anchoring module is used to realize a two-way anchoring closed loop between operation and maintenance and traffic law enforcement evidence chain, and to match the corresponding operation and maintenance compliance support data for law enforcement evidence;

[0012] The hierarchical traceability module is used to perform hierarchical permission traceability of on-chain evidence storage and control the scope of access to the stored evidence content.

[0013] Preferably, when the law enforcement docking module performs standardized and compliant docking between the implementation system and external law enforcement and judicial platforms, and completes the synchronization of law enforcement-related data, receipt of business instructions, and feedback of processing results, it is specifically used for:

[0014] Encrypted connection was completed with the comprehensive traffic law enforcement management platform through the national government service standard interface, synchronizing the statutory law enforcement information of the law enforcement entities;

[0015] Receive enforcement instructions issued by the traffic enforcement integrated management platform and retain an immutable record of the entire instruction process;

[0016] The processing results of business instructions are reported back to the traffic law enforcement integrated management platform.

[0017] Preferably, when the law enforcement docking module performs standardized and compliant docking between the implementation system and external law enforcement and judicial platforms, and completes the synchronization of law enforcement-related data, receipt of business instructions, and feedback of processing results, it is specifically used for:

[0018] The government compliance hotline is used to complete the encrypted connection with the judicial evidence storage platform, and push the corresponding law enforcement evidence-bound device operation compliance report and on-chain evidence storage verification information.

[0019] Complete the same-source filing for judicial-level evidence preservation and simultaneously receive the filing feedback results from the judicial evidence preservation platform;

[0020] The on-chain evidence verification information, equipment operation compliance reports and law enforcement videos for the corresponding time period are bound together to form an inseparable law enforcement evidence package, and the evidence package is archived and stored simultaneously.

[0021] The equipment operation compliance report is generated by comparing equipment operation data with the compliance baseline and is linked to the equipment status verification document with corresponding law enforcement evidence.

[0022] The on-chain evidence verification information is stored within the consortium blockchain and serves as a unique identifier for verifying the authenticity of the evidence content and tracing the source of the data.

[0023] The law enforcement evidence package is an integrated evidence collection formed by binding and packaging law enforcement videos, on-chain evidence verification information, and equipment operation compliance reports.

[0024] Preferably, when the access control module executes the statutory law enforcement information synchronized by the law enforcement docking module, constructs hierarchical and normalized access rules adapted to the traffic law enforcement system, and performs closed-loop management of the entire lifecycle of operation and maintenance permissions, it is specifically used for:

[0025] The hierarchical and normalized permission rules are permission control rules that match the hierarchical architecture of traffic law enforcement, take effect uniformly across devices, and are decoupled from hardware devices and communication protocols.

[0026] Based on the degree of impact on the validity of traffic law enforcement evidence, all operation and maintenance operations are divided into core operation and maintenance operations and general operation and maintenance operations. Core operation and maintenance operations are those that can directly change the scope, parameters, and operating status of the equipment for law enforcement collection, and directly affect the validity of law enforcement evidence. General operation and maintenance operations are those that do not change the equipment's law enforcement collection capabilities and do not affect the validity of law enforcement evidence, such as status query and record viewing.

[0027] Set corresponding entry thresholds for core operation and maintenance operations and general operation and maintenance operations;

[0028] Based on the legal information of law enforcement entities synchronized by the law enforcement docking module, a hierarchical authority system corresponding one-to-one with the traffic law enforcement system is constructed.

[0029] Operational control rules are set up for different law enforcement scenarios to implement closed-loop control of the entire process of operation and maintenance permissions, from application, approval, effectiveness, modification to revocation.

[0030] Preferably, when the compliance verification module performs progressive compliance verification throughout the entire operation and maintenance process, intercepts non-compliant operations, and retains corresponding operation records, it is specifically used for:

[0031] Progressive compliance verification is a serial, step-by-step verification mechanism that proceeds sequentially through three fixed stages: operation initiation, approval, and execution.

[0032] Perform permission compliance verification on the entity initiating the operation and maintenance, block operation requests that do not comply with the permission rules, and retain complete records;

[0033] For core operation and maintenance operations, a dual-person, dual-position approval and qualification verification is performed, and operation requests that do not comply with the approval rules are rejected and complete records are kept.

[0034] Based on the preset equipment compliance baseline, compliance verification is performed on the operation and maintenance operations, blocking operation requests that exceed the compliance baseline and retaining complete records;

[0035] The intercepted and rejected non-compliant operation records are simultaneously pushed to the segmented evidence storage module;

[0036] The equipment compliance baseline is a unified control basis that pre-sets and limits the legal configuration parameters of traffic monitoring equipment in accordance with traffic law enforcement regulations.

[0037] Preferably, when the segmented evidence storage module executes the construction of a segmented, tamper-proof evidence storage system specifically for traffic law enforcement scenarios and performs judicial-level evidence storage control for core operation and maintenance, it is specifically used for:

[0038] The segmented, tamper-proof evidence storage system is an evidence storage architecture built on a consortium blockchain, with differentiated storage rules based on operation and maintenance types, and fixed, unchangeable written data.

[0039] A dedicated consortium blockchain evidence storage node cluster for traffic law enforcement scenarios has been established. This cluster is jointly operated and maintained by multiple government departments and is dedicated to carrying out traffic law enforcement evidence storage business.

[0040] Encrypted communication is established with the system via a dedicated government compliance line to ensure the immutable storage of on-chain data.

[0041] Provides end-to-end traceability management services for on-chain evidence storage content.

[0042] Preferably, when the segmented evidence storage module executes the construction of a segmented, tamper-proof evidence storage system specifically for traffic law enforcement scenarios and performs judicial-level evidence storage control for core operation and maintenance, it is specifically used for:

[0043] Differentiated segmented evidence storage is implemented for core operation and maintenance operations and general operation and maintenance operations, and mandatory on-chain evidence storage is implemented for core operation and maintenance operations that pass the full-process compliance verification.

[0044] Perform local encrypted logging for routine maintenance operations and control access permissions for locally stored content;

[0045] Receive non-compliant operation records pushed by the compliance verification module, and enforce on-chain storage of evidence for the violation operation records.

[0046] Preferably, when the two-way anchoring module executes a two-way anchoring closed loop to realize the operation and maintenance operation and traffic law enforcement evidence chain, and matches the corresponding operation and maintenance compliance support data for law enforcement evidence, it is specifically used for:

[0047] The two-way anchoring closed loop is a two-way association mechanism consisting of the positive association of operation and maintenance operations with video key frames and the reverse verification of law enforcement evidence matching operation and maintenance records.

[0048] Encrypted communication is established with the traffic monitoring front-end equipment cluster through the legally recognized national standard protocol to execute the issuance of operation and maintenance instructions, the transmission of equipment status, and the extraction of law enforcement key frames.

[0049] The statutory national standard protocol is a unified national communication protocol in the field of public safety video surveillance, used for data interaction between front-end monitoring equipment and the platform;

[0050] Enforcement keyframes are standardized, independently encoded video frames collected by traffic monitoring equipment within a fixed time period before and after maintenance operations.

[0051] Perform positive anchoring operations to complete the binding and on-chaining of operation and maintenance operations with law enforcement key frames;

[0052] Perform reverse anchoring operations to complete the verification of operational compliance and the generation of equipment operation compliance reports for the corresponding time period of law enforcement evidence.

[0053] Preferably, when the hierarchical traceability module performs hierarchical permission traceability for on-chain evidence storage and controls the scope of access to stored evidence content, it is specifically used for:

[0054] Establish a tiered access control system that matches the traffic law enforcement system, and clearly define the operational boundaries and evidence retrieval scope corresponding to different access levels;

[0055] The hierarchical access permission system corresponds to three types of users: judicial, law enforcement audit, and daily operation and maintenance, and divides the access scope into a multi-level permission architecture.

[0056] Perform permission compliance checks on evidence retrieval requests, intercept cross-permission retrieval requests, and retain corresponding complete records;

[0057] Intercepted cross-permission retrieval request records are synchronously pushed to the segmented evidence storage module to complete on-chain evidence storage.

[0058] Preferably, when the hierarchical traceability module performs hierarchical permission traceability for on-chain evidence storage and controls the scope of access to stored evidence content, it is specifically used for:

[0059] For evidence retrieval requests that have passed permission verification, output the evidence content within the corresponding range according to the permission level of the requesting subject;

[0060] Output compliance reports and audit reports that meet the requirements of the regulations for requesting entities with the corresponding permissions;

[0061] Retain the entire access record of all evidence retrieval requests to achieve closed-loop control of access behavior.

[0062] The present invention has the following beneficial effects:

[0063] 1. This invention constructs an integrated remote monitoring and maintenance management system that includes an enforcement docking module, an access control module, a compliance verification module, a segmented evidence storage module, a two-way anchoring module, and a hierarchical traceability module. This system enables closed-loop control of each module operating sequentially along the data flow timeline and interacting with targeted data. Compared with the loosely connected operation and maintenance modules and the lack of standardized data flow in existing technologies, this system can improve the compliance and closed-loop nature of traffic monitoring operation and maintenance. Therefore, it can solve the technical problems of existing traffic monitoring operation and maintenance systems being disconnected from law enforcement and judicial operations, lacking clear process control for operation and maintenance, and having disordered data flow, resulting in non-compliant operation and maintenance behavior and the inability to guarantee the validity of law enforcement evidence.

[0064] 2. This invention achieves standardized and compliant connection with external law enforcement and judicial platforms through an enforcement docking module. Combined with a two-way anchoring module, it completes two-way anchoring between operation and maintenance and traffic enforcement evidence chains. Simultaneously, it relies on a segmented evidence storage module to construct a differentiated and tamper-proof evidence storage system. Compared with the existing technology where operation and maintenance are not related to law enforcement evidence and the evidence storage mode is singular, this invention can improve the traceability of operation and maintenance and the legality of law enforcement evidence. Therefore, it can solve the technical problems of existing traffic monitoring operation and maintenance systems where operation and maintenance records are disconnected from law enforcement evidence, the stored evidence cannot provide effective support for law enforcement, and disputes over the validity of law enforcement evidence are likely to occur.

[0065] 3. This invention constructs hierarchical and normalized permission rules adapted to the traffic law enforcement system through an access control module, and realizes hierarchical access control traceability for on-chain evidence storage through a hierarchical traceability module. Combined with the progressive serial verification mechanism of the compliance verification module, compared with the existing technology's mode of access control not matching the law enforcement system, lack of hierarchical restrictions on evidence retrieval, and loose compliance verification, it can improve the accuracy of access control and the security of evidence storage data. Therefore, it can solve the technical problems of chaotic access configuration, easy unauthorized access to evidence storage data, and ineffective interception of non-compliant operations in the existing traffic monitoring and maintenance system, leading to data leakage and non-compliant operation and maintenance behavior. Attached Figure Description

[0066] Figure 1 This is a schematic diagram of the remote monitoring and maintenance management system architecture of the present invention;

[0067] Figure 2 This is a flowchart illustrating the law enforcement integration module of the present invention;

[0068] Figure 3 This is a flowchart illustrating the access control module of the present invention. Detailed Implementation

[0069] To make the technical means, creative features, objectives and effects of this invention easier to understand, the invention will be further described below in conjunction with specific embodiments.

[0070] Example 1, please refer to Figure 1 As shown: A remote monitoring and maintenance management system for traffic monitoring equipment. The system includes an enforcement docking module, an access control module, a compliance verification module, a segmented evidence storage module, a two-way anchoring module, and a hierarchical traceability module, among which:

[0071] The law enforcement docking module is used to achieve standardized and compliant docking between the system and external law enforcement and judicial platforms, and to complete the synchronization of law enforcement-related data, the receipt of business instructions and the feedback of processing results.

[0072] The access control module is used to construct hierarchical and normalized access rules that are compatible with the traffic law enforcement system based on the legal law enforcement information synchronized by the law enforcement docking module, and to implement closed-loop management of the entire lifecycle of operation and maintenance permissions.

[0073] The compliance verification module is used to perform progressive compliance verification throughout the entire operation and maintenance process, intercept non-compliant operations, and retain corresponding operation records.

[0074] The segmented evidence storage module is used to build a segmented, tamper-proof evidence storage system specifically for traffic law enforcement scenarios, and to perform judicial-level evidence storage control for core operation and maintenance.

[0075] The two-way anchoring module is used to realize a two-way anchoring closed loop between operation and maintenance and traffic law enforcement evidence chain, and to match the corresponding operation and maintenance compliance support data for law enforcement evidence;

[0076] The hierarchical traceability module is used to perform hierarchical permission traceability of on-chain evidence storage and control the scope of access to the stored evidence content.

[0077] Furthermore, the various functional modules within this system operate in series according to a fixed time sequence of data flow. The modules interact with each other through a standardized internal communication interface, and all cross-module data transmissions follow fixed interaction rules to form a complete closed-loop data flow. There is no data input without a source or data output without a destination.

[0078] The law enforcement docking module is set as the only authorized data interaction entry point between the system and external law enforcement and judicial platforms. The law enforcement docking module completes the receiving, legality verification and targeted distribution of external data. The legal law enforcement information obtained by the law enforcement docking module can only be pushed to the access control module and must not be distributed to other unauthorized modules.

[0079] The access control module generates access rules based on the legally mandated enforcement information synchronized by the enforcement docking module. The access rules generated by the access control module can only be pushed to the compliance verification module, serving as the sole legal basis for the compliance verification module to carry out its verification work.

[0080] After the compliance verification module completes the full-process verification of operation and maintenance, it will push the operation and maintenance execution instructions that pass the verification to the two-way anchoring module, and push the non-compliant operation records that fail the verification to the segmented evidence storage module.

[0081] After completing the command interaction with the traffic monitoring front-end equipment, the two-way anchoring module will push the generated operation and maintenance data and law enforcement evidence binding data to the segmented evidence storage module, and push the generated equipment operation compliance report to the law enforcement docking module.

[0082] After the segmented evidence storage module completes the differentiated storage of all operation records, the full amount of evidence storage data stored within it can only be retrieved and verified through the hierarchical traceability module, and direct access permissions are not granted to other modules.

[0083] The tiered traceability module uses the permission rules synchronized from the permission control module as the sole basis for permission verification. All evidence retrieval operation records generated by the tiered traceability module are synchronously pushed to the segmented evidence storage module for retention.

[0084] The system is deployed within a security domain that meets the security management requirements of the public security information network and the government extranet. The system's operating environment is physically isolated from the Internet to avoid the risk of data leakage and tampering caused by unauthorized network access.

[0085] Example 2, please refer to Figure 2 As shown: Based on Embodiment 1, the law enforcement docking module, when performing standardized and compliant docking between the system and external law enforcement and judicial platforms, and completing the synchronization of law enforcement-related data, receiving business instructions, and providing feedback on processing results, is specifically used for:

[0086] Encrypted connection was completed with the comprehensive traffic law enforcement management platform through the national government service standard interface, synchronizing the statutory law enforcement information of the law enforcement entities;

[0087] Receive enforcement instructions issued by the traffic enforcement integrated management platform and retain an immutable record of the entire instruction process;

[0088] The processing results of business instructions are reported back to the traffic law enforcement integrated management platform.

[0089] The law enforcement integration module, in executing standardized and compliant integration between the system and external law enforcement and judicial platforms, and completing the synchronization of law enforcement-related data, receipt of business instructions, and feedback of processing results, is specifically used for:

[0090] The government compliance hotline is used to complete the encrypted connection with the judicial evidence storage platform, and push the corresponding law enforcement evidence-bound device operation compliance report and on-chain evidence storage verification information.

[0091] Complete the same-source filing for judicial-level evidence preservation and simultaneously receive the filing feedback results from the judicial evidence preservation platform;

[0092] The on-chain evidence verification information, equipment operation compliance reports and law enforcement videos for the corresponding time period are bound together to form an inseparable law enforcement evidence package, and the evidence package is archived and stored simultaneously.

[0093] The equipment operation compliance report is generated by comparing equipment operation data with the compliance baseline and is linked to the equipment status verification document with corresponding law enforcement evidence.

[0094] The on-chain evidence verification information is stored within the consortium blockchain and serves as a unique identifier for verifying the authenticity of the evidence content and tracing the source of the data.

[0095] The law enforcement evidence package is an integrated evidence collection formed by binding and packaging law enforcement videos, on-chain evidence verification information, and equipment operation compliance reports.

[0096] Furthermore, all docking operations between the law enforcement docking module and external platforms strictly follow a fixed process of first completing two-way identity verification and then conducting data interaction. All interactive data has a clear source and destination, forming a complete closed-loop data flow.

[0097] When the law enforcement docking module synchronizes data with the traffic law enforcement integrated management platform, it first completes two-way identity verification with the traffic law enforcement integrated management platform through the national government service standard interface. The basis for identity verification is the compliant digital certificate issued by the government platform to this system. If the law enforcement docking module fails the verification, it directly interrupts the communication connection with the corresponding platform and does not carry out any data interaction.

[0098] After the law enforcement docking module completes the identity verification, it receives encrypted data packets pushed by the traffic law enforcement integrated management platform. The received encrypted data packets are decrypted, their integrity is verified, and their source legality is verified in sequence. Invalid data that fails the verification is removed, and valid data that passes the verification is parsed and cleaned to extract core fields such as the legal law enforcement qualifications, legal jurisdiction, and job responsibilities of the law enforcement entity, forming a standardized legal law enforcement information dataset.

[0099] The law enforcement docking module will ultimately push the standardized legal law enforcement information dataset to the access control module, while encrypting and storing the original data packets and synchronization process records locally. The retention period complies with the legal requirements for public security administrative data management.

[0100] When the law enforcement docking module receives business instructions from the traffic law enforcement integrated management platform, it first performs a dual verification of the legality and completeness of the instruction source. Instructions that fail the verification are directly rejected and a complete rejection record is retained. Instructions that pass the verification are distributed according to the instruction type. Among them, instructions for retrieving, archiving, and providing judicial evidence are distributed to the two-way anchoring module, and instructions for updating law enforcement entity information are distributed to the access control module.

[0101] After receiving the instruction processing results returned by the corresponding module, the law enforcement docking module performs standardized encapsulation and encryption of the processing results and feeds them back to the traffic law enforcement integrated management platform. At the same time, it retains an immutable record of the entire process of instruction reception, distribution, processing and feedback.

[0102] When the law enforcement docking module docks with the judicial evidence storage platform, if the communication link is abnormally disconnected, the link reconnection mechanism will be automatically triggered. During the reconnection process, the data to be transmitted is encrypted and temporarily cached to ensure that the data is not lost or omitted.

[0103] When the law enforcement docking module receives a filing failure result from the judicial evidence storage platform, it automatically triggers a retry mechanism, retains complete failure reasons and retry records, and generates an abnormal alarm. The alarm is simultaneously pushed to the system administrator and the corresponding law enforcement supervision department to ensure that all data completes compliant filing.

[0104] Example 3, please refer to Figure 3 As shown: Based on Embodiment 1, when the access control module executes the legally mandated enforcement information synchronized by the enforcement docking module, constructs hierarchical and normalized access rules adapted to the traffic enforcement system, and performs closed-loop management of the entire lifecycle of operation and maintenance permissions, it is specifically used for:

[0105] The hierarchical and normalized permission rules are permission control rules that match the hierarchical architecture of traffic law enforcement, take effect uniformly across devices, and are decoupled from hardware devices and communication protocols.

[0106] Based on the degree of impact on the validity of traffic law enforcement evidence, all operation and maintenance operations are divided into core operation and maintenance operations and general operation and maintenance operations. Core operation and maintenance operations are those that can directly change the scope, parameters, and operating status of the equipment for law enforcement collection, and directly affect the validity of law enforcement evidence. General operation and maintenance operations are those that do not change the equipment's law enforcement collection capabilities and do not affect the validity of law enforcement evidence, such as status query and record viewing.

[0107] Set corresponding entry thresholds for core operation and maintenance operations and general operation and maintenance operations;

[0108] Based on the legal information of law enforcement entities synchronized by the law enforcement docking module, a hierarchical authority system corresponding one-to-one with the traffic law enforcement system is constructed.

[0109] Operational control rules are set up for different law enforcement scenarios to implement closed-loop control of the entire process of operation and maintenance permissions, from application, approval, effectiveness, modification to revocation.

[0110] Furthermore, all operations carried out by the access control module use the legally valid law enforcement information synchronized by the law enforcement docking module as the sole legitimate data source, without setting up other external data input points, to ensure that the generated access rules are fully compatible with the legal traffic law enforcement system.

[0111] After receiving the standardized legal law enforcement information dataset pushed by the law enforcement docking module, the access control module first classifies and stores the dataset, establishes a one-to-one mapping relationship between law enforcement entities, qualification levels, jurisdiction, and job responsibilities, and forms a basic access control database.

[0112] When the law enforcement docking module synchronizes and updates the information of law enforcement entities, the access control module automatically synchronizes and updates the basic access database and the access rules of the corresponding entities to ensure that the access rules and legally mandated law enforcement information are kept in real time.

[0113] When an operations and maintenance entity initiates an operations and maintenance operation request through the system, the access control module automatically matches the operation type with the entity's access threshold to complete the pre-verification. Requests that fail the pre-verification are directly blocked and do not proceed to the next process, while requests that pass the pre-verification are pushed to the compliance verification module.

[0114] When constructing a hierarchical permission system, the permission control module achieves complete decoupling between permission rules and hardware devices through an abstract device adaptation layer. The abstract device adaptation layer has a built-in standardized permission control interface and protocol conversion engine. The upper-level permission rules are only bound to the jurisdiction and job responsibilities of the law enforcement entity, and are not associated with the manufacturer, model, or communication protocol of the specific traffic monitoring front-end equipment.

[0115] For traffic monitoring front-end devices from different manufacturers and with different communication protocols, the access control module completes protocol conversion through standardized driver plugins. The unified access rules at the upper layer are uniformly implemented at the adaptation layer, eliminating the need to configure permissions for individual devices. This enables the permissions of the same law enforcement entity to be uniformly effective and centrally managed across all traffic monitoring front-end devices within its legal jurisdiction.

[0116] In the process of implementing closed-loop management of operation and maintenance permissions throughout the entire lifecycle, fixed permissions are strongly bound to the validity period of the qualifications of law enforcement entities. An early warning is automatically triggered before the qualification expires, and the corresponding permissions are automatically frozen on the day the qualification expires. After the freeze, all operation applications are directly blocked. When temporary permissions expire, the permissions are automatically revoked and the temporary account is cancelled. Permission change information is synchronized to the compliance verification module in real time. All operations from permission application to revocation are recorded in a complete and tamper-proof manner.

[0117] Example 4, please refer to Figure 1As shown: Based on Embodiment 1, the compliance verification module, when performing progressive compliance verification throughout the entire operation and maintenance process, intercepting non-compliant operations and retaining corresponding operation records, is specifically used for:

[0118] Progressive compliance verification is a serial, step-by-step verification mechanism that proceeds sequentially through three fixed stages: operation initiation, approval, and execution.

[0119] Perform permission compliance verification on the entity initiating the operation and maintenance, block operation requests that do not comply with the permission rules, and retain complete records;

[0120] For core operation and maintenance operations, a dual-person, dual-position approval and qualification verification is performed, and operation requests that do not comply with the approval rules are rejected and complete records are kept.

[0121] Based on the preset equipment compliance baseline, compliance verification is performed on the operation and maintenance operations, blocking operation requests that exceed the compliance baseline and retaining complete records;

[0122] The intercepted and rejected non-compliant operation records are simultaneously pushed to the segmented evidence storage module;

[0123] The equipment compliance baseline is a unified control basis that pre-sets and limits the legal configuration parameters of traffic monitoring equipment in accordance with traffic law enforcement regulations.

[0124] Furthermore, the compliance verification module relies solely on the permission rules synchronized by the permission control module and the preset device compliance baseline. No other custom verification rule entry points are set. The progressive compliance verification adopts a strict serial execution logic. Operations that fail the previous level verification will terminate the process directly and will not be allowed to enter the next level verification stage. There is no verification bypass throughout the process, eliminating the possibility of the verification process being circumvented.

[0125] Before initiating the verification process, the compliance verification module receives permission rules, entry thresholds, and control requirements pushed by the access control module in real time, and simultaneously updates the device compliance baseline regularly to ensure that the verification basis is consistent with the latest rules.

[0126] After the compliance verification module completes the first-level compliance verification, only applications that pass the verification can proceed to the second-level approval compliance verification stage. General operation and maintenance operations do not need to enter the approval verification stage.

[0127] During the second-level dual-person, dual-position approval verification process of the compliance verification module, the approval process adopts a serial dual-signature mechanism. Only after the previous approver approves the application can it be pushed to the next approver. If any approver rejects the application, the approval entity's qualifications do not meet the requirements, or the approval process is not completed within the time limit, the compliance verification module will determine that the verification has failed, directly reject the operation application, and retain a complete record.

[0128] After the compliance verification module completes the third-level content compliance verification, the verified operations generate standardized operation and maintenance execution instructions, which are then pushed to the two-way anchoring module.

[0129] The compliance verification module encrypts and pushes all non-compliant operation records that are blocked or rejected in real time to the segmented evidence storage module after generation using government compliance encryption. The entire process record of operations that pass verification is simultaneously pushed to the segmented evidence storage module for retention, ensuring that all operations have complete and traceable records.

[0130] Example 5, please refer to Figure 1 As shown: Based on Embodiment 1, the segmented evidence storage module, when constructing a segmented, tamper-proof evidence storage system specifically for traffic enforcement scenarios and performing judicial-level evidence storage control for core operation and maintenance, is specifically used for:

[0131] The segmented, tamper-proof evidence storage system is an evidence storage architecture built on a consortium blockchain, with differentiated storage rules based on operation and maintenance types, and fixed, unchangeable written data.

[0132] A dedicated consortium blockchain evidence storage node cluster for traffic law enforcement scenarios has been established. This cluster is jointly operated and maintained by multiple government departments and is dedicated to carrying out traffic law enforcement evidence storage business.

[0133] Encrypted communication is established with the system via a dedicated government compliance line to ensure the immutable storage of on-chain data.

[0134] Provides end-to-end traceability management services for on-chain evidence storage content.

[0135] The segmented evidence storage module, when constructing a segmented, tamper-proof evidence storage system specifically for traffic enforcement scenarios and performing judicial-level evidence storage control for core operational and maintenance tasks, is specifically used for:

[0136] Differentiated segmented evidence storage is implemented for core operation and maintenance operations and general operation and maintenance operations, and mandatory on-chain evidence storage is implemented for core operation and maintenance operations that pass the full-process compliance verification.

[0137] Perform local encrypted logging for routine maintenance operations and control access permissions for locally stored content;

[0138] Receive non-compliant operation records pushed by the compliance verification module, and enforce on-chain storage of evidence for the violation operation records.

[0139] Furthermore, the data input source for the segmented evidence storage module is various operation records, binding data, and access logs pushed by the compliance verification module, the two-way anchoring module, and the hierarchical traceability module. All data is stored differently according to preset rules to form a complete evidence storage data stream.

[0140] The consortium blockchain evidence storage node cluster, built using a segmented evidence storage module, is jointly operated and maintained by traffic management departments, judicial administration departments, law enforcement supervision departments, and government data management departments as consensus nodes. No single node has the authority to modify or delete data. The nodes use a consensus mechanism that conforms to government regulations to complete data synchronization and confirmation, ensuring that all data written to the blockchain cannot be tampered with or deleted after being written, and has legal judicial effect.

[0141] The evidence storage node cluster connects to the system via a government compliance dedicated line, and all on-chain data transmission adopts government compliance encryption methods to ensure the security and compliance of the data transmission process.

[0142] After receiving the data to be stored, the segmented evidence storage module first classifies and determines the data into three categories: core operation and maintenance data, general operation and maintenance data, and data of violations. The corresponding evidence storage regulations are then executed according to the different categories.

[0143] For core operation and maintenance data and all data of violations, the segmented evidence storage module enforces on-chain evidence storage. First, the data is standardized and packaged, and a unique data identifier, timestamp and identity verification information are added. After completing government compliance encryption and digital signature, the data is pushed to the node cluster. Then, after the data is confirmed by the consensus of the node cluster, it is written into the block to complete the on-chain storage. At the same time, the corresponding on-chain evidence storage verification information is generated and sent back to the system for retention.

[0144] For general operation and maintenance data, the segmented evidence storage module performs local encryption and record keeping without on-chain evidence storage. After data encryption is completed using government-compliant encryption methods, it is stored in a local encrypted database. Only entities with corresponding permissions can view it, and the retention period complies with the legal and regulatory requirements for log management of public security information networks.

[0145] When the segmented evidence storage module receives a request for on-chain evidence storage that fails, it automatically triggers a retry mechanism. Each retry retains a complete log, and a compliance alarm is generated for retry failures. The alarm is simultaneously pushed to law enforcement and supervision departments and node administrators. At the same time, the data to be uploaded to the chain is encrypted and solidified locally and cannot be deleted until the on-chain upload is successful, ensuring that all data to be uploaded to the chain is compliantly stored.

[0146] Example 6, please refer to Figure 1 As shown: Based on Embodiment 1, the two-way anchoring module, when executing the two-way anchoring closed loop to realize the operation and maintenance operation and traffic law enforcement evidence chain, and matching the corresponding operation and maintenance compliance support data for law enforcement evidence, is specifically used for:

[0147] The two-way anchoring closed loop is a two-way association mechanism consisting of the positive association of operation and maintenance operations with video key frames and the reverse verification of law enforcement evidence matching operation and maintenance records.

[0148] Encrypted communication is established with the traffic monitoring front-end equipment cluster through the legally recognized national standard protocol to execute the issuance of operation and maintenance instructions, the transmission of equipment status, and the extraction of law enforcement key frames.

[0149] The statutory national standard protocol is a unified national communication protocol in the field of public safety video surveillance, used for data interaction between front-end monitoring equipment and the platform;

[0150] Enforcement keyframes are standardized, independently encoded video frames collected by traffic monitoring equipment within a fixed time period before and after maintenance operations.

[0151] Perform positive anchoring operations to complete the binding and on-chaining of operation and maintenance operations with law enforcement key frames;

[0152] Perform reverse anchoring operations to complete the verification of operational compliance and the generation of equipment operation compliance reports for the corresponding time period of law enforcement evidence.

[0153] Furthermore, the data input sources for the two-way anchoring module are the operation and maintenance execution instructions pushed by the compliance verification module, the law enforcement business instructions forwarded by the law enforcement docking module, and the device status and video stream data returned by the traffic monitoring front-end equipment. The data output destinations are the segmented evidence storage module and the law enforcement docking module, forming two complete closed-loop data flows: forward anchoring and reverse anchoring.

[0154] When the bidirectional anchoring module connects with the traffic monitoring front-end equipment cluster, it first establishes an encrypted communication connection with the traffic monitoring front-end equipment through the legal national standard protocol to complete device identity verification, registration and keep-alive, and status synchronization. For vendor-owned protocol devices that do not support the national standard protocol, the protocol conversion is completed through the abstract device adaptation layer in the permission control module to achieve standardized connection without replacing existing hardware devices.

[0155] The bidirectional anchoring module uses a standardized communication link to complete the issuance of operation and maintenance instructions, the return of equipment execution results, the real-time synchronization of equipment operating status, the retrieval of law enforcement video streams and the extraction of key frames. All interactions with the traffic monitoring front-end equipment are fully recorded.

[0156] When the bidirectional anchoring module performs a positive anchoring operation, it first receives the operation and maintenance execution instruction pushed by the compliance verification module. Then, it sends the instruction to the corresponding traffic monitoring front-end device through the national standard protocol, monitors the device's execution status in real time, and after receiving the successful execution result returned by the device, it automatically extracts the standardized video stream within a fixed time period before and after the operation and within the device's statutory working hours. It extracts independently coded keyframes that conform to the national standard specifications from the video stream to form a keyframe sequence. Finally, it uniquely binds the core operation and maintenance operation process record, the device execution result, and the keyframe sequence to generate an indivisible associated dataset, which is pushed to the segmented evidence storage module to complete the on-chain evidence storage. It receives the returned on-chain evidence storage verification information to complete the positive anchoring closed-loop confirmation.

[0157] When the bidirectional anchoring module fails to extract keyframes, a retry mechanism is automatically triggered. If the retry fails, an exception alarm is generated, a complete failure record is stored, and the record is pushed to the segmented evidence storage module.

[0158] When the two-way anchoring module performs reverse anchoring operations, it first receives the law enforcement business instructions forwarded by the law enforcement docking module, then parses the device information, corresponding time period, and instruction type in the instructions. Next, it retrieves the full amount of stored evidence content for the corresponding device and time period from the node cluster of the segmented evidence storage module to complete the compliance verification of the device's operating status. Finally, based on the verification results, it generates a device operation compliance report that is uniquely bound to the corresponding law enforcement evidence. The report clearly marks compliant or non-compliant items, attaches the corresponding on-chain evidence storage verification information, complies with the requirements of judicial document norms, and pushes the generated report to the law enforcement docking module to complete the same-source archiving, retaining a complete record of the entire reverse anchoring process, forming a reverse anchoring closed loop.

[0159] Example 7, please refer to Figure 1 As shown: Based on Embodiment 1, the hierarchical tracing module, when performing hierarchical permission tracing of on-chain evidence storage and controlling the scope of retrieval of stored evidence content, is specifically used for:

[0160] Establish a tiered access control system that matches the traffic law enforcement system, and clearly define the operational boundaries and evidence retrieval scope corresponding to different access levels;

[0161] The hierarchical access permission system corresponds to three types of users: judicial, law enforcement audit, and daily operation and maintenance, and divides the access scope into a multi-level permission architecture.

[0162] Perform permission compliance checks on evidence retrieval requests, intercept cross-permission retrieval requests, and retain corresponding complete records;

[0163] Intercepted cross-permission retrieval request records are synchronously pushed to the segmented evidence storage module to complete on-chain evidence storage.

[0164] The hierarchical tracing module, when performing hierarchical permission tracing of on-chain evidence storage and controlling the scope of access to stored evidence content, is specifically used for:

[0165] For evidence retrieval requests that have passed permission verification, output the evidence content within the corresponding range according to the permission level of the requesting subject;

[0166] Output compliance reports and audit reports that meet the requirements of the regulations for requesting entities with the corresponding permissions;

[0167] Retain the entire access record of all evidence retrieval requests to achieve closed-loop control of access behavior.

[0168] Furthermore, the basis for the permission verification by the hierarchical traceability module comes from the permission rules synchronized by the permission control module. The only channel for obtaining evidence data is the segmented evidence storage module. All retrieval operations strictly follow the fixed process of first completing permission verification and then outputting data, forming a complete data flow for evidence storage retrieval and traceability control.

[0169] The hierarchical access permission system set up by the hierarchical traceability module is synchronized in real time with the hierarchical access permission system of the access control module. When the permissions of the law enforcement entity change, the hierarchical traceability module automatically updates the evidence storage access permissions of the corresponding entity to ensure that the access rules are consistent throughout the process.

[0170] The hierarchical access permission architecture clearly corresponds to three types of users: judicial, law enforcement audit, and daily operation and maintenance. It defines fixed operation boundaries and evidence retrieval scope for each type of user, and users without the necessary permissions are prohibited from accessing any evidence data.

[0171] After receiving a request for evidence retrieval, the hierarchical traceability module first verifies the identity and qualifications of the requesting entity, extracts the requesting entity's permission level, jurisdiction, and retrieval scope, and then compares it with the preset rules of the hierarchical access permission system to verify whether the requesting entity has the corresponding access permission and whether the retrieval scope is within the permission's allowed boundaries. If all comparison items meet the requirements, the verification is deemed successful, and the process proceeds to the subsequent data retrieval process. If any comparison item fails to meet the requirements, the verification is deemed unsuccessful, and the cross-permission retrieval request is directly intercepted. A complete interception record is generated synchronously and pushed to the segmented evidence storage module in real time to complete the on-chain evidence storage.

[0172] The hierarchical traceability module retrieves the corresponding range of stored evidence content from the segmented evidence storage module according to the permission level of the requesting subject for requests that have passed the permission verification. It prohibits the output of stored evidence data that exceeds the permission range. Among them, the judicial verification permission can output the full amount of stored evidence content and the compliance report that meets the legal requirements of judicial evidence storage management. The law enforcement audit permission can output the full amount of stored evidence records and the law enforcement audit report within the jurisdiction. The daily operation and maintenance permission can only output the basic operation logs within the corresponding permission range.

[0173] The hierarchical traceability module adds corresponding permission identifiers to the output reports and evidence, prohibiting unauthorized forwarding and dissemination.

[0174] The hierarchical traceability module generates complete access records for all operations involving evidence retrieval and data output. After the access records are encrypted and stored in compliance with government regulations, they are simultaneously pushed to the segmented evidence storage module for retention. All access records are tamper-proof and cannot be deleted. The retention period complies with the legal requirements for government data auditing, thus achieving compliance and controllability of the entire process of accessing evidence data.

[0175] The foregoing has shown and described the basic principles, main features, and advantages of the present invention. Those skilled in the art should understand that the present invention is not limited to the above embodiments. The embodiments and descriptions in the specification are merely illustrative of the principles of the invention. Various changes and modifications can be made to the invention without departing from its spirit and scope, and all such changes and modifications fall within the scope of the present invention as claimed. The scope of protection of this invention is defined by the appended claims and their equivalents.

Claims

1. A remote monitoring and maintenance management system for traffic monitoring equipment, characterized in that, The system includes an enforcement docking module, an access control module, a compliance verification module, a segmented evidence storage module, a two-way anchoring module, and a hierarchical traceability module, wherein: The law enforcement docking module is used to achieve standardized and compliant docking between the system and external law enforcement and judicial platforms, and to complete the synchronization of law enforcement-related data, the receipt of business instructions and the feedback of processing results. The access control module is used to construct hierarchical and normalized access rules that are compatible with the traffic law enforcement system based on the legal law enforcement information synchronized by the law enforcement docking module, and to implement closed-loop management of the entire lifecycle of operation and maintenance permissions. The compliance verification module is used to perform progressive compliance verification throughout the entire operation and maintenance process, intercept non-compliant operations, and retain corresponding operation records. The segmented evidence storage module is used to build a segmented, tamper-proof evidence storage system specifically for traffic law enforcement scenarios, and to perform judicial-level evidence storage control for core operation and maintenance. The two-way anchoring module is used to realize a two-way anchoring closed loop between operation and maintenance and traffic law enforcement evidence chain, and to match the corresponding operation and maintenance compliance support data for law enforcement evidence; The hierarchical traceability module is used to perform hierarchical permission traceability of on-chain evidence storage and control the scope of access to the stored evidence content.

2. The remote monitoring and maintenance management system for traffic monitoring equipment according to claim 1, characterized in that, The law enforcement docking module, when performing standardized and compliant docking between the system and external law enforcement and judicial platforms, and synchronizing law enforcement-related data, receiving business instructions, and providing feedback on processing results, is specifically used for: Encrypted connection was completed with the comprehensive traffic law enforcement management platform through the national government service standard interface, synchronizing the statutory law enforcement information of the law enforcement entities; Receive enforcement instructions issued by the traffic enforcement integrated management platform and retain an immutable record of the entire instruction process; The processing results of business instructions are reported back to the traffic law enforcement integrated management platform.

3. The remote monitoring and maintenance management system for traffic monitoring equipment according to claim 1, characterized in that, The law enforcement docking module, when performing standardized and compliant docking between the system and external law enforcement and judicial platforms, and synchronizing law enforcement-related data, receiving business instructions, and providing feedback on processing results, is specifically used for: The government compliance hotline is used to complete the encrypted connection with the judicial evidence storage platform, and push the corresponding law enforcement evidence-bound device operation compliance report and on-chain evidence storage verification information. Complete the same-source filing for judicial-level evidence preservation and simultaneously receive the filing feedback results from the judicial evidence preservation platform; The on-chain evidence verification information, equipment operation compliance reports and law enforcement videos for the corresponding time period are bound together to form an inseparable law enforcement evidence package, and the evidence package is archived and stored simultaneously. The equipment operation compliance report is generated by comparing equipment operation data with the compliance baseline and is linked to the equipment status verification document with corresponding law enforcement evidence. The on-chain evidence verification information is stored within the consortium blockchain and serves as a unique identifier for verifying the authenticity of the evidence content and tracing the source of the data. The law enforcement evidence package is an integrated evidence collection formed by binding and packaging law enforcement videos, on-chain evidence verification information, and equipment operation compliance reports.

4. The remote monitoring and maintenance management system for traffic monitoring equipment according to claim 1, characterized in that, The access control module, when executing the legal enforcement information synchronized by the enforcement docking module, constructing hierarchical and normalized access rules adapted to the traffic enforcement system, and performing closed-loop management of the entire lifecycle of operation and maintenance permissions, is specifically used for: The hierarchical and normalized permission rules are permission control rules that match the hierarchical architecture of traffic law enforcement, take effect uniformly across devices, and are decoupled from hardware devices and communication protocols. Based on the degree of impact on the validity of traffic law enforcement evidence, all operation and maintenance operations are divided into core operation and maintenance operations and general operation and maintenance operations. Core operation and maintenance operations are those that can directly change the scope, parameters, and operating status of the equipment for law enforcement collection, and directly affect the validity of law enforcement evidence. General operation and maintenance operations are those that do not change the equipment's law enforcement collection capabilities and do not affect the validity of law enforcement evidence, such as status query and record viewing. Set corresponding entry thresholds for core operation and maintenance operations and general operation and maintenance operations; Based on the legal information of law enforcement entities synchronized by the law enforcement docking module, a hierarchical authority system corresponding one-to-one with the traffic law enforcement system is constructed. Operational control rules are set up for different law enforcement scenarios to implement closed-loop control of the entire process of operation and maintenance permissions, from application, approval, effectiveness, modification to revocation.

5. The remote monitoring and maintenance management system for traffic monitoring equipment according to claim 1, characterized in that, The compliance verification module, when performing progressive compliance verification throughout the entire operation and maintenance process, intercepting non-compliant operations and retaining corresponding operation records, is specifically used for: Progressive compliance verification is a serial, step-by-step verification mechanism that proceeds sequentially through three fixed stages: operation initiation, approval, and execution. Perform permission compliance verification on the entity initiating the operation and maintenance, block operation requests that do not comply with the permission rules, and retain complete records; For core operation and maintenance operations, a dual-person, dual-position approval and qualification verification is performed, and operation requests that do not comply with the approval rules are rejected and complete records are kept. Based on the preset equipment compliance baseline, compliance verification is performed on the operation and maintenance operations, blocking operation requests that exceed the compliance baseline and retaining complete records; The intercepted and rejected non-compliant operation records are simultaneously pushed to the segmented evidence storage module; The equipment compliance baseline is a unified control basis that pre-sets and limits the legal configuration parameters of traffic monitoring equipment in accordance with traffic law enforcement regulations.

6. The remote monitoring and maintenance management system for traffic monitoring equipment according to claim 1, characterized in that, The segmented evidence storage module, when executing the construction of a segmented, tamper-proof evidence storage system specifically for traffic law enforcement scenarios and performing judicial-level evidence storage control for core operation and maintenance, is specifically used for: The segmented, tamper-proof evidence storage system is an evidence storage architecture built on a consortium blockchain, with differentiated storage rules based on operation and maintenance types, and fixed, unchangeable written data. A dedicated consortium blockchain evidence storage node cluster for traffic law enforcement scenarios has been established. This cluster is jointly operated and maintained by multiple government departments and is dedicated to carrying out traffic law enforcement evidence storage business. Encrypted communication is established with the system via a dedicated government compliance line to ensure the immutable storage of on-chain data. Provides end-to-end traceability management services for on-chain evidence storage content.

7. The remote monitoring and maintenance management system for traffic monitoring equipment according to claim 1, characterized in that, The segmented evidence storage module, when executing the construction of a segmented, tamper-proof evidence storage system specifically for traffic law enforcement scenarios and performing judicial-level evidence storage control for core operation and maintenance, is specifically used for: Differentiated segmented evidence storage is implemented for core operation and maintenance operations and general operation and maintenance operations, and mandatory on-chain evidence storage is implemented for core operation and maintenance operations that pass the full-process compliance verification. Perform local encrypted logging for routine maintenance operations and control access permissions for locally stored content; Receive non-compliant operation records pushed by the compliance verification module, and enforce on-chain storage of evidence for the violation operation records.

8. The remote monitoring and maintenance management system for traffic monitoring equipment according to claim 1, characterized in that, The bidirectional anchoring module, when executing the bidirectional anchoring closed loop to realize the chain of evidence between operation and maintenance and traffic law enforcement, and matching the corresponding operation and maintenance compliance support data for law enforcement evidence, is specifically used for: The two-way anchoring closed loop is a two-way association mechanism consisting of the positive association of video key frames bound to operation and maintenance operations and the reverse verification of operation and maintenance records by matching law enforcement evidence; Encrypted communication is established with the traffic monitoring front-end equipment cluster through the legally recognized national standard protocol to execute the issuance of operation and maintenance instructions, the transmission of equipment status, and the extraction of law enforcement key frames. The statutory national standard protocol is a unified national communication protocol in the field of public safety video surveillance, used for data interaction between front-end monitoring equipment and the platform; Enforcement keyframes are standardized, independently encoded video frames collected by traffic monitoring equipment within a fixed time period before and after maintenance operations. Perform positive anchoring operations to complete the binding and on-chaining of operation and maintenance operations with law enforcement key frames; Perform reverse anchoring operations to complete the verification of operational compliance and the generation of equipment operation compliance reports for the corresponding time period of law enforcement evidence.

9. The remote monitoring and maintenance management system for traffic monitoring equipment according to claim 1, characterized in that, The hierarchical tracing module, when performing hierarchical permission tracing of on-chain evidence storage and controlling the scope of access to stored evidence content, is specifically used for: Establish a tiered access control system that matches the traffic law enforcement system, and clearly define the operational boundaries and evidence retrieval scope corresponding to different access levels; The hierarchical access permission system corresponds to three types of users: judicial, law enforcement audit, and daily operation and maintenance, and divides the access scope into a multi-level permission architecture. Perform permission compliance checks on evidence retrieval requests, intercept cross-permission retrieval requests, and retain corresponding complete records; Intercepted cross-permission retrieval request records are synchronously pushed to the segmented evidence storage module to complete on-chain evidence storage.

10. The remote monitoring and maintenance management system for traffic monitoring equipment according to claim 9, characterized in that, The hierarchical tracing module, when performing hierarchical permission tracing of on-chain evidence storage and controlling the scope of access to stored evidence content, is specifically used for: For evidence retrieval requests that have passed permission verification, output the evidence content within the corresponding range according to the permission level of the requesting subject; Output compliance reports and audit reports that meet the requirements of the regulations for requesting entities with the corresponding permissions; Retain the entire access record of all evidence retrieval requests to achieve closed-loop control of access behavior.

Images