A closed-loop method, system, equipment, and medium for digital security monitoring hazard investigation and mitigation.

By generating a hidden danger event identifier (EID) and a version number (VSN), the data is divided into multiple fragments. Combined with edge-side missing fragment bitmaps and cloud hash verification mechanisms, the problems of repeated transmission and data association in the weak network environment of mountain rail construction sites are solved, and the structured closed-loop processing of hidden danger data throughout its entire lifecycle is realized.

CN123123377APending Publication Date: 2026-11-17SICHUAN SHUDAO NEW STANDARD RAIL GRP CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611144438.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-07-30
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In the weak network environment of construction sites such as mountain railways, the existing hidden danger investigation and management platform has problems such as high failure rate of retransmission of the entire package of hidden danger attachments, lack of the same hidden danger identifier in the cloud leading to duplicate order creation, and difficulty in unifying and archiving multiple versions of rectification data.

Method used

By generating a hidden event identifier (EID) and a version number (VSN), the data is divided into multiple fragments. Combined with edge-side missing fragment bitmap retransmission, cloud hash integrity verification, and version association mechanisms, breakpoint resume transmission and data anti-duplicate verification are achieved, ensuring structured closed-loop processing of the same event throughout its entire lifecycle.

Benefits of technology

It significantly reduces duplicate traffic and transmission failure rate, achieves accurate correlation of potential data throughout its entire lifecycle, prevents system status chaos caused by network jitter, and establishes a strict technical closed-loop threshold.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123123377A_ABST
    Figure CN123123377A_ABST
Patent Text Reader

Abstract

This invention discloses a closed-loop processing method, system, device, and medium for digital security monitoring hazard investigation and management, relating to the field of network communication technology. The method includes: collecting hazard data at the edge, generating a unique hazard event identifier (EID) and version number, and segmenting the data to generate event list packets and fragment records with fragment hashes; the edge gateway creates a session table containing a confirmation bitmap based on the EID, and retransmits missing data according to the missing fragment bitmap returned from the cloud; the cloud performs hash integrity verification after all fragments are complete, and triggers the initial order creation only if the verification passes; the rectification data uses the original EID with an updated version number, is associated and archived by the cloud, and is released from the edge cache in a controlled manner after business confirmation. This invention solves the technical problems of high retransmission rate of large files and difficulty in associating multiple versions of rectification data in weak network environments, realizing structured closed-loop processing of the entire lifecycle of hazards.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of network communication technology, specifically to a closed-loop processing method, system, device, and medium for digital security monitoring, risk investigation, and mitigation. Background Technology

[0002] The statements in this section are provided only as background information in connection with this disclosure and may not constitute prior art.

[0003] Construction sites for mountain railways and similar projects are characterized by long work areas, dispersed locations, uneven network coverage, and frequent uploading of large-volume attachments. The project construction plan clearly proposes capabilities such as patrol task management, digital coding of video points, registration and verification of monitoring points, verification and access of point codes, AI event perception, and visual traceability. This means that on-site hazard data includes not only text records, but also large-volume data such as photos, videos, point codes, geographical locations, responsibility areas, and subsequent rectification attachments.

[0004] Existing hazard identification and management platforms generally adopt a workflow of "mobile terminal data collection - server reception - order creation and dispatch - manual review," lacking clear technical mechanisms for handling large file uploads, duplicate data merging, and cross-version rectification data association in weak network environments. Based on existing publicly available patents and general system solutions, dual prevention, hazard closure, and general work order platforms emphasize reporting, order dispatch, rectification, and case closure processes, but they exhibit the following significant technical deficiencies: On-site photos and videos are often uploaded as a whole. If there is a weak network or network outage, the entire packet needs to be retransmitted if there is a failure, resulting in large network transmission latency and high repetitive traffic. Cloud-based systems typically only perform duplicate checks based on the title or content field of the hazard, which cannot guarantee that the same location and the same hazard will maintain a unique business identifier when uploaded, re-uploaded, and rectified and returned multiple times. The lack of a structured underlying verification link makes it easy for duplicate order creation and status conflicts to occur due to repeated uploads or network jitter. Supplementary photos, retest data, and cancellation results after rectification are often directly overwritten as new attachments, lacking a version association mechanism based on the same hazard number, making it difficult to achieve traceable ledger archiving throughout the entire life cycle. Summary of the Invention

[0005] The purpose of this invention is to address the technical problems of high failure rates in the retransmission of complete packages of hidden danger attachments in weak network environments at construction sites such as mountain railways, duplicate order creation due to the lack of the same hidden danger identifier in the cloud, and difficulty in unifying and archiving multiple versions of rectification data. This invention provides a digital safety monitoring hidden danger investigation and management closed-loop processing method, system, equipment, and medium. Based on the Hidden Danger Event Identifier (EID), it generates event list packages and fragmented records, and combines edge-side missing fragment bitmap retransmission, cloud hash integrity verification, and version association mechanisms to achieve breakpoint resume transmission, data anti-duplicate verification, and structured closed-loop processing of the same event throughout its entire lifecycle in weak network environments.

[0006] The technical solution of the present invention is as follows: A closed-loop method for digital security monitoring hazard investigation and mitigation includes: Hazardous data is collected from the site via the endpoint. A hazard event identifier (EID) is generated using the location code, collection time slot, and local serial number. A version number (VSN) corresponding to the hazard data is also generated. Based on the number of attachments included in the hazard data, it is divided into multiple data fragments, and an event list package containing the EID, the VSN, the number of fragments, and a list digest hash is generated. A corresponding fragment hash and fragment record are generated for each data fragment, and a hash tree is constructed based on the fragment hashes of each data fragment to generate a root hash. The edge gateway receives the event list packet and the data fragment, establishes a fragment offset index table, and creates an edge session table based on the EID. The edge session table contains an acknowledgment bitmap and the current status. The edge gateway prioritizes sending the event list packet to the cloud and writes unacknowledged data fragments into the local cache queue according to the network status. After receiving the event list packet, the cloud establishes a cloud session table based on the EID and the VSN; if the data fragments subsequently received by the cloud are incomplete, a missing fragment bitmap is generated based on the arrived data fragments and returned to the edge gateway; the edge gateway retransmits the missing data fragments according to the missing fragment bitmap. Once all data shards are collected, the cloud performs integrity verification on the list summary hash and the root hash. After the integrity verification passes, the state of the cloud session table is switched to a business-processable state, thereby triggering the first order creation corresponding to the EID. For rectification data corresponding to the same EID, the edge device retains the original EID and generates a new version number. The same data transmission and integrity verification process as described above is performed through the edge gateway and the cloud. The cloud establishes an association between the new version number corresponding to the rectification data and the original version number VSN for unified ledger archiving, and returns a business confirmation receipt to the edge gateway. The edge gateway releases the corresponding data in the local cache queue only after all the confirmation bitmaps in the edge session table are confirmed as completed and the business confirmation receipt is received.

[0007] Further, an event list package containing the EID, the VSN, the number of shards, and the list digest hash is generated, and a shard record is generated for each data shard, including: Generate event manifest package ;in, Indicates the number of fragments. Represents the list digest hash; For the first Each data shard generates a shard record. ;in, This is the fragment number. This is the offset from the original attachment. This is the fragment length. The shard hash is the hash of the corresponding data shard. This is a fragmentation type identifier.

[0008] Further, an edge session table is created based on the EID, including: The edge gateway maintains an edge session table entry for each EID. ; in, This indicates the confirmation bitmap. Indicates the last sent time. Indicates the number of retries. This indicates the current state; The current status includes at least the following: receiving status, waiting for link recovery status, retrying status, service confirmed status, and archiving completed status.

[0009] Furthermore, when the edge gateway retransmits the missing data fragments according to the missing fragment bitmap, it also employs the following state machine control mechanism: If the missing fragment bitmap received by the edge gateway remains unchanged for two consecutive cycles, the current state in the edge session table is switched to the waiting link recovery state, and the retransmission of the missing fragment is suspended. When the network link is restored or a changed missing bitmap is received, the current state will be switched back to the state corresponding to fragment retransmission. If the service confirmation receipt returned by the cloud is not received after the preset retention period, a cache retention alarm will be triggered, and the data in the local cache queue will be kept from being deleted.

[0010] Furthermore, after the integrity verification passes, the state of the cloud session table is switched to a business-processable state, thereby triggering the first order creation corresponding to the EID, including: After the cloud verifies the joint hash of the event list package and the root hash of all data shards, it calls the task engine to generate a work order based on the risk source level, impact scope, and rectification time limit. When the task engine generates a work order, it calculates the task priority according to the following formula. :

[0011] in, Indicates the risk source level factor, Indicates the scope of influence factor. Indicates the rectification time limit factor; , , These represent the corresponding preset weight coefficients.

[0012] Furthermore, the cloud will associate the new version number corresponding to the rectified data with the original version number VSN for unified ledger archiving, including: Create cloud session entries in the cloud ,in For the root hash; For the rectification data, the cloud identifies the same EID and the new version number, and establishes a parent-child version association relationship between the new version number and the original version number VSN in the cloud session table; If the verification of the rectification data passes, a cancellation record is generated, and the original reported version and the rectification version are archived together in the same ledger link; if the verification fails, the new version session state under the same EID is maintained and the rectification task is reassigned.

[0013] Furthermore, the specific method for generating the EID (Emergency Identifier for Hidden Dangerous Events) on the endpoint using the location code, data collection time slot, and local serial number is as follows: The location code corresponding to the current physical location is obtained by scanning the QR code of the monitoring point; Extract the location code, and combine it with the collection time slot when the hazard data is collected and the local serial number generated on the terminal side to generate a unique hazard event identifier (EID).

[0014] This invention also proposes a closed-loop processing system for digital security monitoring, hazard investigation, and mitigation, used to implement the method described above. The system includes: The edge-side data acquisition and event encapsulation unit is used to acquire on-site hazard data, generate a hazard event identifier (EID) using the location code, acquisition time slot, and local serial number, and generate a version number (VSN) corresponding to the hazard data; divide the hazard data into multiple data fragments according to the number of attachments contained in the hazard data, and generate an event list package containing the EID, the VSN, the number of fragments, and the list digest hash; generate a corresponding fragment hash and fragment record for each data fragment, and construct a hash tree based on the fragment hash of each data fragment to generate a root hash; The edge gateway and fragment caching unit are used to receive the event list packet and the data fragment, establish a fragment offset index table, and create an edge session table based on the EID. The edge session table includes an acknowledgment bitmap and the current status. The event list packet is sent to the cloud first, and the unacknowledged data fragments are written to the local cache queue according to the network status. The missing data fragments are retransmitted according to the missing fragment bitmap returned by the cloud. The cloud access and idempotent merging unit is used to establish a cloud session table based on the EID and the VSN after receiving the event list packet; if the subsequently received data fragments are incomplete, it generates the missing fragment bitmap based on the arrived data fragments and returns it; after all the data fragments are received, it performs integrity verification on the list digest hash and the root hash and triggers the first order creation corresponding to the EID after the verification passes; and it is used to associate the new version number corresponding to the rectification data with the original version number VSN for unified ledger archiving and return a business confirmation receipt. The edge gateway and sharding cache unit are further configured to release the corresponding data in the local cache queue only after all the confirmation bitmaps in the edge session table have been confirmed as completed and the service confirmation receipt has been received.

[0015] The present invention also proposes an electronic device, comprising: At least one processor; and a memory communicatively connected to said at least one processor; The memory stores instructions that can be executed by the at least one processor, and the at least one processor executes the instructions stored in the memory to perform the method described above.

[0016] The present invention also proposes a computer-readable storage medium for storing instructions that, when executed, cause the method described above to be implemented.

[0017] Compared with existing technologies, the advantages of this invention are: 1. Significantly improves transmission success rate and reduces network load in weak network environments. By first generating an event list packet and then segmenting attachments for fragmented transmission, attachment uploads in weak network environments are transformed from traditional full packet retransmission to targeted retransmission based on "missing fragment bitmaps," significantly reducing duplicate traffic and transmission failure rate.

[0018] 2. Achieved precise correlation of hazard data throughout its entire lifecycle. By generating a unified hazard event identifier (EID), version number (VSN), and inventory summary hash, the initial reporting, weak network retransmission, rectification feedback, and closure archiving of the same hazard can all be bound to parent and child versions under a single and clear identifier system, preventing record overwriting and loss.

[0019] 3. Effectively prevents system state chaos caused by network jitter. By establishing session tables with state machine control on the edge and cloud sides, combined with the cloud-side list registration, root hash verification, and idempotent merging mechanism, duplicate order creation and business state conflicts caused by repeated uploads, network jitter, or rectification and re-upload are avoided.

[0020] 4. A rigorous technical closed-loop threshold has been established, enhancing the innovative technical substance of the solution. Setting "hash tree-based integrity verification" as a prerequisite for triggering business order creation, and setting "cloud business confirmation receipt" as a mandatory constraint for edge cache release, ensures that the risk management chain is strictly controlled by the underlying data session state, rather than simply a manual business process. Attached Figure Description

[0021] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments recorded in the embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings.

[0022] Figure 1 This is an overall structural diagram of the closed-loop system for hazard identification and mitigation provided in an embodiment of the present invention; Figure 2 This is a connection diagram showing the connection relationship between end, edge, and cloud fragmented retransmission and idempotency verification provided in an embodiment of the present invention. Figure 3 This is a flowchart illustrating the closed-loop process for hazard identification and mitigation provided in this embodiment of the invention. Figure 4 A schematic diagram of the state machine for list confirmation and fragmented data transfer provided in an embodiment of the present invention; Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention.

[0023] Explanation of reference numerals in the attached figures: 301 - End-side data acquisition and event encapsulation unit; 302 - Edge Gateway and Fragmented Cache Unit; 303 - Cloud Access and Idempotent Merging Unit; 304 - Message Delivery Unit; 305 - Visual Management Terminal. Detailed Implementation

[0024] It should be noted that relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0025] The features and performance of the present invention will be further described in detail below with reference to embodiments.

[0026] Example 1 Combination Figures 1 to 4 This embodiment provides a closed-loop processing method for digital security monitoring hazard investigation and management, which relies on, for example, Figure 1 The system architecture shown is implemented collaboratively by the end-side acquisition and event encapsulation unit 301, the edge gateway and sharding cache unit 302, the cloud access and idempotent merging unit 303, the message delivery unit 304, and the visual management terminal 305. Figure 1 The main arrow in the image indicates that after a potential incident is collected from the edge, it is cached and retransmitted through the edge gateway, then enters the cloud for verification and business invoicing, and is further output to the message delivery and visual traceability link. Figure 3 The overall processing flow of this method is given, which includes the following steps: Step S301: Event encapsulation and hazard identification generation.

[0027] In this step, hazard data is collected from the site via the terminal. A hazard event identifier (EID) is generated using the location code, collection time slot, and local serial number, and a version number (VSN) corresponding to the hazard data is also generated. Based on the number of attachments included in the hazard data, the hazard data is divided into multiple data fragments, and an event list package containing the EID, the VSN, the number of fragments, and the list digest hash is generated. A corresponding fragment hash and fragment record are generated for each data fragment, and a hash tree is constructed based on the fragment hash of each data fragment to generate a root hash.

[0028] Specifically, the end side (i.e. Figure 1 The specific method by which the end-side acquisition and event encapsulation unit 301 (e.g., an inspection terminal) generates the hidden danger event identifier EID using the point code, acquisition time slot, and local serial number is as follows: the point code corresponding to the current physical location is obtained by scanning the QR code of the monitoring point; the point code is extracted and combined with the acquisition time slot when the hidden danger data is currently acquired and the local serial number generated by the end-side unit to generate the unique hidden danger event identifier EID.

[0029] In this embodiment, taking the lack of edge protection at the bridge construction site as an example, inspection personnel scan the QR code of the monitoring point on the terminal side. The platform reads the standard code, responsibility area, and professional classification corresponding to that point. Subsequently, it collects the on-site hazard data (including on-site photos, videos, short videos, geographical location, location, timestamp, text description, hazard description, and operator information). The terminal side generates a unified EID and marks this upload as the initial version number VSN = 1.

[0030] Further, generating an event manifest package containing the EID, the VSN, the number of shards, and the manifest digest hash, and generating a shard record for each data shard, includes: generating the event manifest package. ;in, Indicates the number of fragments, Represents the hash of the list digest; for the first The data sharding generates shard records. ;in, This is the fragment number. This is the offset from the original attachment. This is the fragment length. The shard hash is the hash of the corresponding data shard. This is a segment type identifier (used to identify image or video clips).

[0031] Assuming the attachment contains 2 photos and 1 video, the client will segment it according to the preset segment size. Data is divided into shards. The endpoint is configured based on the hash of each shard. Construct a hash tree (such as a Merkle tree structure) and aggregate layer by layer to obtain the root hash. and will It is sent along with the manifest package. In this embodiment, it should be noted that, unlike existing systems that directly upload complete attachments, this invention first generates an event manifest package and fragment records that can be jointly identified by the edge and the cloud. This ensures that all subsequent retransmission, verification, and archiving processes always revolve around the same event object (EID), laying the data structure foundation for resuming transmission even when interrupted in a weak network.

[0032] Step S302: Edge-side sharding cache and index establishment.

[0033] In this step, the event list packet and the data fragment are received through the edge gateway, a fragment offset index table is established, and an edge session table is created based on the EID. The edge session table contains an acknowledgment bitmap and the current status. The edge gateway first sends the event list packet to the cloud, and writes the unacknowledged data fragments into the local cache queue according to the network status.

[0034] like Figure 2 As shown in the fragmented record and offset index node and the edge session table node, the creation of the edge session table based on the EID includes: the edge gateway maintaining an edge session table entry for each EID. ;in, This indicates the confirmation bitmap. Indicates the last sent time. Indicates the number of retries. The current state is indicated; the current state includes at least the receiving state, the waiting link recovery state, the retrying state, the service confirmation state, and the archiving completed state.

[0035] In this embodiment, it should be noted that this node link addresses the problem of maintaining the manifest packet and fragment index unchanged under weak network conditions, and only retransmitting missing fragments. If the on-site network is normal, fragments are sent in the order of the index; if the network is interrupted when sending the 5th fragment, the edge gateway (i.e., Figure 1 The edge gateway and sharding cache unit 302 in the middle write unacknowledged shards to the local cache queue and put the state machine ( The status is updated to "Waiting for link recovery". Unlike the existing whole packet retransmission method, this embodiment keeps the list packet and fragment index unchanged under weak network conditions, and only maintains the set of missing fragments that need to be retransmitted, so that caching, retry and release are strictly controlled by the session state.

[0036] Step S303: Register the list and upload missing bitmaps.

[0037] In this step, after receiving the event list packet, the cloud establishes a cloud session table based on the EID and the VSN; if the data fragments subsequently received by the cloud are incomplete, a missing fragment bitmap is generated based on the arrived data fragments and returned to the edge gateway; the edge gateway retransmits the missing data fragments according to the missing fragment bitmap.

[0038] like Figure 2 and Figure 4 As shown, when the edge gateway retransmits the missing data fragments according to the missing fragment bitmap, it also adopts the following state machine control mechanism: if the missing fragment bitmap received by the edge gateway for two consecutive cycles remains unchanged, the current state in the edge session table is switched to the waiting link recovery state, and the retransmission of missing fragments is suspended; when the network link is restored or a changed missing fragment bitmap is received, the current state is switched back to the state corresponding to the fragment retransmission; if the service confirmation receipt returned by the cloud is not received after the preset retention period, a cache retention alarm is triggered, and the data in the local cache queue is kept from being deleted.

[0039] In this embodiment, specifically, the cloud (i.e. Figure 1 The cloud access and idempotent merging unit 303 in the middle registers the event session and returns a registration success flag after receiving the list packet. For example, if cloud fragments 1 to 4 have been successfully received, but fragments 5 to 8 are lost, a missing fragment bitmap is generated. The missing fragments are identified as fragments 5 to 8 and returned to the edge gateway. After the network recovers, the edge gateway only retransmits fragments 5 to 8, and does not retransmit fragments 1 to 4. This mechanism avoids channel congestion caused by invalid retries under continuous weak network conditions, and triggers an alarm in the event of a timeout but does not directly delete the cache, thus ensuring that potentially vulnerable data will never be lost due to link jitter.

[0040] Steps S304 - S305: Integrity verification and initial order creation notification.

[0041] In this step, after all the data shards are collected, the cloud performs integrity verification on the list digest hash and the root hash; after the integrity verification passes, the state of the cloud session table is switched to the business-processable state, thereby triggering the first order creation corresponding to the EID.

[0042] Figure 4 This demonstrates the business confirmation mechanism; confirmation only occurs when the cloud verifies the manifest package digest hash. and root hash Only after the joint verification passes will the event session be switched from "verification in progress" to "business-processable". If the manifest packet of the same EID and VSN is resubmitted due to network jitter, the cloud performs idempotent merging, only updating the session status or supplementing missing attachments, without creating duplicate manifests.

[0043] Furthermore, after the integrity verification passes, the state of the cloud session table is switched to a business-processable state, thereby triggering the first order creation corresponding to the EID. This includes: after the cloud verifies the joint hash of the list digest of the event list package and the root hash of all data shards, it calls the task engine to generate a work order based on the risk source level, impact scope, rectification time limit, responsible area, and professional category; wherein, when the task engine generates a work order, it calculates the task priority according to the following formula. :

[0044] in, Indicates the risk source level factor, Indicates the scope of influence factor. Indicates the rectification time limit factor; , , These represent the corresponding preset weight coefficients.

[0045] For example, if set , , Take the weighting coefficient , , Then the calculation yields This corresponds to a major hidden danger level. At this point, after generating a work order, the message delivery unit 304 can also send notifications to the responsible person and on-duty personnel. Only after the event session completes list registration, fragment verification, and version confirmation will the task engine allow the initial work order creation, thus making "transmission integrity + version consistency" a prerequisite technical condition for entering the business closed loop. Therefore, the essential difference between this invention and ordinary breakpoint resume or general file upload is that business work order creation, version archiving, and cache clearing are all controlled by the event session state, rather than solely determined by the success or failure of file transmission. The system utilizes event sessions to implement strong dependency control between file transmission and business work order creation.

[0046] Step S306: Return and review the rectified version.

[0047] In this step, the responsible person uploads the rectification data (such as rectification photos, retest results, and explanatory text) after completing the rectification. For the rectification data corresponding to the same EID, the edge device uses the original EID and generates a new version number, and performs the same data transmission and integrity verification process as described above through the edge gateway and the cloud.

[0048] This means that the upload will still be processed according to the manifest package and fragment index, but the version number will be updated (e.g., from VSN = 1 to VSN = 2). If the fragments of the rectified version are only partially uploaded in a weak network environment, the system will still use the missing fragment bitmap return mechanism to only upload the missing fragments.

[0049] For major potential risks, the task engine can set a deadline for responsibility confirmation and a deadline for rectification completion after the initial task is created. If no responsibility confirmation is received within the first preset deadline, message delivery unit 304 automatically sends an escalation reminder to the superior. If the rectified version still has not completed hash verification and entered the review status within the second preset deadline, a review warning is triggered. Thus, the business trigger chain is built on the underlying data link status such as event session integrity, version status, and hash verification results, rather than simply manual reminder rules.

[0050] Step S307: Unified ledger archiving and controlled release of cache.

[0051] In this step, the cloud establishes an association between the new version number corresponding to the rectification data and the original version number VSN for unified ledger archiving, and returns a business confirmation receipt to the edge gateway; the edge gateway releases the corresponding data in the local cache queue only after all the confirmation bitmaps in the edge session table are confirmed as completed and after receiving the business confirmation receipt.

[0052] Specifically, the cloud platform associates the new version number corresponding to the rectification data with the original version number VSN for unified ledger archiving, including: the cloud platform establishing cloud session entries. ,in For the root hash; the It includes at least the following states: receiving, verification, business-processable, and closed-loop completion. For the rectification data, the cloud identifies the same EID and the new version number, and establishes a parent-child version association between the new version number and the original version number VSN in the cloud session table. If the verification of the rectification data passes, a cancellation record is generated, and the original reported version and the rectification version are jointly archived in the same ledger link. If the verification fails, the new version session state under the same EID is maintained and the rectification task is reassigned.

[0053] After archiving is completed, the entire process status under the same EID—from initial report, segmented re-upload, initial order creation, rectification version, review conclusion, and closure time—can be displayed through the visual management terminal 305, allowing for the tracing of the hazard lifecycle. For example... Figure 4 As shown in the business confirmation node and archive clearing node, the cache clearing on the edge side does not rely on simple timeout eviction, but must be subject to the dual constraints of integrity verification results and business closed-loop results (i.e., confirmation that all bitmaps meet the standards + arrival of cloud business receipts). This is also the core technical point that distinguishes this invention from ordinary breakpoint resume solutions at the underlying technical level. Thus, a structured and complete closed-loop processing technology chain is formed, consisting of "event encapsulation - list registration - fragmented retransmission - idempotent merging - order dispatch notification - review and cancellation - ledger archiving".

[0054] In this embodiment, it should be further explained that, as Figure 3 As shown in the diagram, the main chain arrows indicate the processing sequence of a potential hazard incident from its initial reporting to its event closure and archiving. The output of the preceding node directly constitutes the input of the following node. Figure 4 As shown, the state transition arrows in the diagram correspond to triggering conditions such as initial transmission, fragment retransmission, waiting for link recovery, receiving service confirmation, and cache clearing; the diagram clearly indicates the state machine transition process for list confirmation and fragment retransmission.

[0055] Specifically, regarding the mapping of each functional node, such as Figure 2 As shown, the endpoint includes inspection terminal / manifest package nodes, representing the entry point for on-site data collection and event encapsulation; the edge includes shard cache / offset index / session table nodes, used to segment attachments and maintain transmission status; the cloud includes manifest registration / idempotent merging nodes and task engine / ledger archiving nodes. The arrows in the diagram clearly illustrate the data flow between the endpoint, edge, and cloud layers. Meanwhile, as... Figure 4 As shown in the state machine, the event encapsulation node represents the initial state; the list sending node indicates that the edge gateway sends the list first; the cache queue node indicates that the fragments that have not yet been confirmed have entered the local cache; the fragment retransmission node indicates that only the missing fragments are retransmitted; the waiting link recovery node indicates that the retransmission is paused and the network is waiting; the service confirmation node indicates that the cloud returns the confirmation result; and the archive clearing node indicates that the edge cache is only released after the confirmation bitmap is fully confirmed and the service receipt is received.

[0056] Example 2 Based on the same inventive concept as Embodiment 1, this embodiment provides a closed-loop processing system for digital security monitoring, hazard investigation, and mitigation. Since this system is a virtual device embodiment corresponding to the method in Embodiment 1, its implementation principles and technical effects are similar to those of the method embodiment. For the sake of brevity, this section focuses on describing the functional module division of each unit.

[0057] Combination Figure 1 The diagram shown illustrates the overall structure of a closed-loop system for hazard identification and mitigation. This system primarily includes the following essential technical units: End-side data acquisition and event encapsulation unit 301: This unit is used to acquire on-site hazard data, generate a hazard event identifier (EID) using the location code, acquisition time slot, and local serial number, and generate a version number (VSN) corresponding to the hazard data; based on the number of attachments included in the hazard data, it divides the hazard data into multiple data fragments and generates an event list package containing the EID, the VSN, the number of fragments, and a list digest hash; it generates a corresponding fragment hash and fragment record for each data fragment, and constructs a hash tree based on the fragment hash of each data fragment to generate a root hash.

[0058] This unit is typically deployed on the mobile terminal devices of inspection personnel. By converting large original attachments (such as on-site photos and videos) into fragmented records and manifest packets containing hash characteristics at the edge, the traceability and tamper-proof nature of data transmission are ensured from the source, providing a basic data structure for resuming interrupted transmissions when network jitter occurs.

[0059] Edge gateway and fragment caching unit 302: This unit receives the event list packet and the data fragments, establishes a fragment offset index table, and creates an edge session table based on the EID. The edge session table includes an acknowledgment bitmap and the current status. It prioritizes sending the event list packet to the cloud and writes unacknowledged data fragments into a local cache queue according to the network status. It also retransmits missing data fragments based on the missing fragment bitmap returned by the cloud. The edge gateway and fragment caching unit is further configured to release the corresponding data in the local cache queue only after all acknowledgment bitmaps in the edge session table have been confirmed as complete and after receiving the service acknowledgment receipt.

[0060] This unit plays a core role in the system as a "weak network buffer and state control" unit. By maintaining an edge session table with state machines (such as waiting for link recovery state, retrying state, etc.), its cleanup of local cache is not only subject to time constraints, but also to the hard constraints of cloud integrity verification results and closed-loop results, thus completely solving the problem of data loss or duplicate accumulation that is easily caused by traditional weak network retransmission.

[0061] Cloud access and idempotent merging unit 303: After receiving the event list packet, it establishes a cloud session table based on the EID and the VSN; if the subsequently received data fragments are incomplete, it generates the missing fragment bitmap based on the arrived data fragments and returns it; after all the data fragments arrive, it performs integrity verification on the list digest hash and the root hash, and triggers the first order creation corresponding to the EID after the verification passes; and it associates the new version number corresponding to the rectification data with the original version number VSN for unified ledger archiving, and returns a business confirmation receipt.

[0062] This unit is deployed on a cloud server. On the one hand, it uses joint hash verification to ensure data consistency and triggers order creation based on a preset task engine priority formula; on the other hand, for the data returned after rectification, it avoids invalid order creation and version overwrite issues caused by duplicate uploads by identifying version number changes of the same EID and the parent-child version association.

[0063] Furthermore, to enhance the closed-loop processing capability of the system, as a preferred embodiment, the system may further include: Message delivery unit 304: After the cloud access and idempotency merging unit 303 triggers the order creation, it sends a notification to the corresponding responsible person and on-duty personnel; and sends an upgrade reminder when rectification is overdue or review warning is issued.

[0064] Visual management terminal 305: Used to display the entire process status of the first report, missing piece retransmission, first order creation, rectification version, review conclusion and cancellation time corresponding to the same EID, thereby realizing visual traceability of the hidden danger life cycle, responsibility chain and time consumption.

[0065] The aforementioned digital security monitoring and hidden danger investigation and management closed-loop processing system deeply integrates the business flow mechanism with the underlying hash generation, bitmap comparison and session state machine control, overcoming the limitations of relying solely on manual intervention and simple breakpoint resume, and is particularly suitable for long-term closed-loop management in mountain rail construction and operation scenarios.

[0066] Based on the same technical concept, embodiments of the present invention also provide an electronic device that can implement the closed-loop processing method for digital security monitoring hazard investigation and management provided in the above embodiments of the present invention. In one embodiment, the electronic device can be a server, a terminal device, or other electronic devices. Figure 5 As shown, the electronic device may include: At least one processor and a memory connected to the at least one processor. In this embodiment of the invention, the specific connection medium between the processor and the memory is not limited. Figure 5The example used is the connection between the processor and memory via a bus. The bus... Figure 5 The connections between other components are indicated by thick lines and are for illustrative purposes only, not as limiting information. Buses can be divided into address buses, data buses, control buses, etc., but for ease of representation, [the specific bus type is not shown here]. Figure 5 The processor is represented by a single thick line, but this does not imply that there is only one bus or one type of bus. Alternatively, a processor can also be called a controller; there are no restrictions on the name.

[0067] In this embodiment of the invention, the memory stores instructions executable by at least one processor. By executing the instructions stored in the memory, the at least one processor can perform the closed-loop processing method for digital security monitoring hazard investigation and management described above. The processor can implement... Figure 5 The functions of each module in the device shown.

[0068] The processor is the control center of the device. It can connect to various parts of the control device through various interfaces and lines. By running or executing instructions stored in memory and calling data stored in memory, it can monitor the device's various functions and process data, thereby enabling overall monitoring of the device.

[0069] In an alternative design, the processor may include one or more processing units. The processor may integrate an application processor and a modem processor, wherein the application processor primarily handles the operating system, user interface, and applications, while the modem processor primarily handles wireless communication. It is understood that the modem processor may also not be integrated into the processor. In some embodiments, the processor and memory may be implemented on the same chip; in some embodiments, they may also be implemented separately on separate chips.

[0070] The processor can be a general-purpose processor, such as a CPU, digital signal processor, application-specific integrated circuit, field-programmable gate array or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, capable of implementing or executing the methods, steps, and logic block diagrams disclosed in the embodiments of this invention. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the closed-loop processing method for digital security monitoring hazard investigation and management disclosed in the embodiments of this invention can be directly manifested as execution by a hardware processor, or execution by a combination of hardware and software modules within the processor.

[0071] Memory, as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules. Memory can include at least one type of storage medium, such as flash memory, hard disk, multimedia cards, card-type memory, random access memory (RAM), static random access memory (SRAM), programmable read-only memory (PROM), read-only memory (ROM), and electrically erasable programmable read-only memory (EPROM). Only memory (EEPROM), magnetic storage, magnetic disks, optical disks, etc. A memory is any other medium capable of carrying or storing desired program code in the form of instructions or data structures, and accessible by a computer, but is not limited thereto. The memory in embodiments of this invention can also be a circuit or any other device capable of performing storage functions for storing program instructions and / or data.

[0072] By designing and programming the processor, the code corresponding to the closed-loop processing method for digital security monitoring hazard investigation and management described in the foregoing embodiments can be embedded into the chip, enabling the chip to execute the steps of the method described in the foregoing embodiments during operation. How to design and program the processor is a technique well-known to those skilled in the art and will not be elaborated upon here.

[0073] Based on the same inventive concept, embodiments of the present invention also provide a storage medium storing computer instructions, which, when executed on a computer, cause the computer to perform a closed-loop processing method for digital security monitoring hazard investigation and management as described above.

[0074] In some alternative embodiments, the present invention also provides a method for closed-loop processing of digital security monitoring hazard investigation and management, which can also be implemented as a program product, including program code. When the program product is run on a device, the program code is used to cause the control device to perform the steps in the closed-loop processing method for digital security monitoring hazard investigation and management according to various exemplary embodiments of the present invention as described above.

[0075] It should be noted that although several units or sub-units of the apparatus have been mentioned in the detailed description above, this division is merely exemplary and not mandatory. In fact, according to embodiments of the invention, the features and functions of two or more units described above can be embodied in one unit. Conversely, the features and functions of one unit described above can be further divided and embodied by multiple units. Furthermore, although the operation of the method of the invention is described in a specific order in the drawings, this does not require or imply that these operations must be performed in that specific order, or that all the operations shown must be performed to achieve the desired result. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step, and / or one step may be broken down into multiple steps.

[0076] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can be implemented in one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROMs) containing computer-usable program code. The form of a computer program product implemented on ROM, optical memory, etc.

[0077] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a server, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0078] Program code for performing the operations of this invention can be written using any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on the user's computing device, partially on the user's device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0079] In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0080] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0081] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0082] The embodiments described above merely illustrate specific implementation methods of this application, and while the descriptions are detailed and specific, they should not be construed as limiting the scope of protection of this application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of the technical solution of this application, and these modifications and improvements all fall within the scope of protection of this application.

[0083] This background section is provided to generally present the context of the invention. The work of the currently named inventors, the work to the extent described in this background section, and aspects of this section that did not constitute prior art at the time of application are neither expressly nor impliedly acknowledged as prior art to the invention.

Claims

1. A closed-loop processing method for digital security monitoring hazard investigation and management, characterized in that, include: By collecting on-site hazard data from the terminal, a hazard event identifier (EID) is generated using the location code, collection time slot, and local serial number, and a version number (VSN) corresponding to the hazard data is also generated. Based on the number of attachments included in the hazard data, the hazard data is divided into multiple data fragments, and an event list package containing the EID, the VSN, the number of fragments, and the list digest hash is generated. For each data shard, a corresponding shard hash and shard record are generated, and a hash tree is constructed based on the shard hash of each data shard to generate a root hash; The event list packet and the data fragment are received through the edge gateway, a fragment offset index table is established, and an edge session table is created based on the EID. The edge session table contains an acknowledgment bitmap and the current status. The edge gateway first sends the event list packet to the cloud, and writes unconfirmed data fragments into the local cache queue according to the network status; After receiving the event list packet, the cloud establishes a cloud session table based on the EID and the VSN; If the data fragments subsequently received by the cloud are incomplete, a missing fragment bitmap is generated based on the data fragments that have arrived and returned to the edge gateway; The edge gateway retransmits the missing data fragments according to the missing fragment bitmap. Once all data shards are collected, the cloud performs integrity verification on the list summary hash and the root hash. After the integrity verification passes, the state of the cloud session table is switched to a business-processable state, thereby triggering the first order creation corresponding to the EID. For the rectification data corresponding to the same EID, the terminal side retains the original EID and generates a new version number, and performs the same data transmission and integrity verification process as described above through the edge gateway and the cloud. The cloud will associate the new version number corresponding to the rectification data with the original version number VSN for unified ledger archiving, and return a business confirmation receipt to the edge gateway; the edge gateway will release the corresponding data in the local cache queue only after all the confirmation bitmaps in the edge session table have been confirmed as completed and the business confirmation receipt has been received.

2. The closed-loop processing method for digital security monitoring hazard investigation and management according to claim 1, characterized in that, Generate an event manifest package containing the EID, the VSN, the number of shards, and the manifest digest hash, and generate a shard record for each data shard, including: Generate event manifest package ;in, Indicates the number of fragments. Represents the list digest hash; For the first Each data shard generates a shard record. ;in, This is the fragment number. This is the offset from the original attachment. This is the fragment length. The shard hash is the hash of the corresponding data shard. This is a fragmentation type identifier.

3. The closed-loop processing method for digital security monitoring hazard investigation and management according to claim 1, characterized in that, Creating an edge session table based on the EID includes: The edge gateway maintains an edge session table entry for each EID. ; in, This indicates the confirmation bitmap. Indicates the last sent time. Indicates the number of retries. This indicates the current state; The current status includes at least the following: receiving status, waiting for link recovery status, retrying status, service confirmed status, and archiving completed status.

4. The closed-loop processing method for digital security monitoring hazard investigation and management according to claim 3, characterized in that, When the edge gateway retransmits the missing data fragments according to the missing fragment bitmap, it also employs the following state machine control mechanism: If the missing fragment bitmap received by the edge gateway remains unchanged for two consecutive cycles, the current state in the edge session table is switched to the waiting link recovery state, and the retransmission of the missing fragment is suspended. When the network link is restored or a changed missing bitmap is received, the current state will be switched back to the state corresponding to fragment retransmission. If the service confirmation receipt returned by the cloud is not received after the preset retention period, a cache retention alarm will be triggered, and the data in the local cache queue will be kept from being deleted.

5. The closed-loop processing method for digital security monitoring hazard investigation and management according to claim 1, characterized in that, After the integrity verification passes, the state of the cloud session table is switched to a business-processable state, thereby triggering the first order creation corresponding to the EID, including: After the cloud verifies the joint hash of the event list package and the root hash of all data shards, it calls the task engine to generate a work order based on the risk source level, impact scope, and rectification time limit. When the task engine generates a work order, it calculates the task priority according to the following formula. : in, Indicates the risk source level factor, Indicates the scope of influence factor. Indicates the rectification time limit factor; , , These represent the corresponding preset weight coefficients.

6. The closed-loop processing method for digital security monitoring hazard investigation and management according to claim 1, characterized in that, The cloud will associate the new version number corresponding to the rectification data with the original version number VSN for unified ledger archiving, including: Create cloud session entries in the cloud ,in For the root hash; For the rectification data, the cloud identifies the same EID and the new version number, and establishes a parent-child version association relationship between the new version number and the original version number VSN in the cloud session table; If the verification of the rectification data passes, a cancellation record is generated, and the original reported version and the rectification version are archived together in the same ledger link; if the verification fails, the new version session state under the same EID is maintained and the rectification task is reassigned.

7. The closed-loop processing method for digital security monitoring hazard investigation and management according to claim 1, characterized in that, The specific method for generating the EID (Emergency Identifier for Hidden Dangers) on the endpoint using the location code, data collection time slot, and local serial number is as follows: The location code corresponding to the current physical location is obtained by scanning the QR code of the monitoring point; Extract the location code, and combine it with the collection time slot when the hazard data is collected and the local serial number generated on the terminal side to generate a unique hazard event identifier (EID).

8. A closed-loop processing system for digital security monitoring, hazard investigation, and mitigation, characterized in that: For implementing the method as described in any one of claims 1 to 7, the system comprises: The edge-side data acquisition and event encapsulation unit is used to acquire on-site hazard data, generate a hazard event identifier (EID) using the location code, acquisition time slot, and local serial number, and generate a version number (VSN) corresponding to the hazard data; divide the hazard data into multiple data fragments according to the number of attachments contained in the hazard data, and generate an event list package containing the EID, the VSN, the number of fragments, and the list digest hash; generate a corresponding fragment hash and fragment record for each data fragment, and construct a hash tree based on the fragment hash of each data fragment to generate a root hash; The edge gateway and fragment caching unit are used to receive the event list packet and the data fragment, establish a fragment offset index table, and create an edge session table based on the EID. The edge session table includes an acknowledgment bitmap and the current status. The event list packet is sent to the cloud first, and the unacknowledged data fragments are written to the local cache queue according to the network status. The missing data fragments are retransmitted according to the missing fragment bitmap returned by the cloud. The cloud access and idempotent merging unit is used to establish a cloud session table based on the EID and the VSN after receiving the event list packet; if the subsequently received data fragments are incomplete, it generates the missing fragment bitmap based on the arrived data fragments and returns it; after all the data fragments are received, it performs integrity verification on the list digest hash and the root hash and triggers the first order creation corresponding to the EID after the verification passes; and it is used to associate the new version number corresponding to the rectification data with the original version number VSN for unified ledger archiving and return a business confirmation receipt. The edge gateway and sharding cache unit are further configured to release the corresponding data in the local cache queue only after all the confirmation bitmaps in the edge session table have been confirmed as completed and the service confirmation receipt has been received.

9. An electronic device, characterized in that, include: At least one processor; and a memory communicatively connected to the at least one processor; The memory stores instructions that can be executed by the at least one processor. By executing the instructions stored in the memory, the at least one processor performs the closed-loop processing method for digital security monitoring hazard investigation and management as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store instructions that, when executed, enable the closed-loop processing method for digital security monitoring hazard investigation and management as described in any one of claims 1-7 to be implemented.