A physical isolation dual-host device closed-loop management method and system

Abstract

The application provides a physical isolation double-host device closed-loop management and control method and system. The method comprises: a device lending and returning host generates an encrypted return permission two-dimensional code containing a lending and returning record number in response to a device return request; a data processing host reads and decrypts the two-dimensional code, establishes a return processing task based on the lending and returning record number, and listens to a device access event based on the return processing task, reads a physical serial number, and performs a data processing operation on the returned device after associating the task; and the data processing host generates a result two-dimensional code based on the execution result and returns it to the device lending and returning host to update the lending and returning record and the device state. The application realizes closed-loop management and control of the return task between the physically isolated double hosts through the lending and returning record number throughout the whole process of the two-dimensional code message, the processing task and the result return, effectively prevents task repeated execution, device mismatch, asynchronous callback crosstalk and failure state misrelease, and improves the reliability and data security of the intelligent cabinet device return process.

Description

Technical Field

[0001] This application relates to the fields of intelligent cabinet equipment management and control, industrial terminal collaboration, data security isolation and equipment return data processing technology. Specifically, it relates to a closed-loop management and control method and system for physically isolated dual host devices. Background Technology

[0002] The DCC smart cabinet is used for the self-service borrowing and returning of data acquisition devices such as cameras, USB flash drives, and portable hard drives, as well as post-return data processing. When returning a device, the following steps are required: user identification, slot control, device access recognition, file enumeration and watermarking, file upload or backup USB drive copying, data clearing from the device, updating borrowing and returning records, and anomaly alarms. The device borrowing and returning host is responsible for user interaction, slot control, and borrowing and returning record maintenance, while the data processing host is responsible for device access detection, file processing, and data uploading. Due to data security requirements, the two hosts are physically isolated and there is no direct network communication link between them.

[0003] Existing smart locker information storage management solutions can already realize functions such as device borrowing and returning, matching of compartments and device tags, and data transfer; existing QR code physical isolation transmission equipment can also encode source data into QR codes and transmit it across isolation channels. However, simply combining the above solutions still cannot solve the following problems in the actual operation of DCC smart lockers: First, the QR code channel is an intermittent, manually triggered channel. Each of the two hosts maintains its local state, making real-time task progress synchronization impossible. The same QR code may be scanned consecutively, causing the same return task to be repeatedly initiated. Second, if a device is not associated with a return task upon connection, the detected device may not match the task, leading to incorrect data attribution. Third, file uploads are asynchronous, and progress callbacks from earlier tasks may overwrite the current interface display, causing interface state crosstalk. Finally, without differentiation of result message types, releasing the device as if it were successful when the upload fails will lead to data management risks, and the backup USB drive may be re-occupied by new tasks before being returned, causing resource conflicts.

[0004] Therefore, existing technologies urgently need a method and system that can achieve closed-loop management of the entire process of task return, prevent task duplication and equipment mismatch, isolate asynchronous processing results, reliably distinguish between success and failure states, and control equipment release under physically isolated dual-host conditions. Summary of the Invention

[0005] The purpose of this application is to provide a closed-loop management method and system for physically isolated dual-host devices, aiming to solve the problems of repetitive execution of smart cabinet return tasks, task-device mismatch, crosstalk of asynchronous processing results, and unreliable closed-loop management of success / failure states under physically isolated dual-host conditions. By binding each return to a unique borrowing / returning record number, and making this record number permeate the permission QR code, data processing task, success result QR code, and failure alarm QR code, task-level collaboration between the borrowing / returning host and the data processing host is achieved. Limited control commands, processing parameters, and result statistics are transmitted between the two physically isolated hosts via QR codes, without transmitting any original business files. Business files in the storage medium to be returned are read to the local data processing host via USB interface using mass storage or MTP media transmission protocol. On this host, all secure processing operations, including watermarking, file archiving and uploading, and media data erasure, are independently completed. This avoids the leakage risk caused by business files being transmitted across isolated domains via optical QR codes, achieving closed-loop collaborative management of the entire task process between the two hosts while meeting physical isolation security specifications.

[0006] This application also provides a closed-loop management method for physically isolated dual-host devices, including the following steps: In response to a device return request, the device borrowing and returning host queries existing borrowing and returning records to obtain the borrowing and returning record number, and generates a return task control message based on the borrowing and returning record number and the device association information. After encrypting the return task control message, the encrypted message is encoded into a return permission QR code. The data processing host reads the return permission QR code, decodes and decrypts it, extracts the borrowing and returning record number and device association information, and establishes a return processing task based on the borrowing and returning record number; The data processing host listens for device access events based on the return processing task, reads the physical serial number of the accessed device, associates the physical serial number with the current return task, and performs data processing operations on the return device. The data processing host generates a result QR code based on the execution result of the return processing task. The result QR code contains the borrowing and returning record number and processing result information, and is read by an industrial barcode scanner and then sent back to the equipment borrowing and returning host. The device borrowing / returning host reads the result QR code and updates the corresponding borrowing / returning record and device status based on the borrowing / returning record number and processing result information.

[0007] Optionally, in the physically isolated dual-host device closed-loop management method described in this application, the device borrowing / returning host responds to the device return request by querying existing borrowing / return records to obtain a borrowing / return record number, and generates a return task control message based on the borrowing / return record number and device association information. The return task control message is then encrypted and encoded into a return permission QR code, including: The return task control message includes the borrowing / returning record number, equipment association information, upload method, and watermark type. The equipment association information includes the equipment number, equipment type, and grid number. The device borrowing and returning host uses a preset encryption key and initialization vector to encrypt the return task control message with AES, and adds a QR code recognition prefix to the encryption result before encoding it into a return permission QR code.

[0008] Optionally, in the physically isolated dual-host device closed-loop management method described in this application, the data processing host reads the return permission QR code, decodes and decrypts it, extracts the borrowing / returning record number and device association information, and establishes a return processing task based on the borrowing / returning record number, including: The data processing host performs normalization processing on the received return permission QR code, and records the normalized QR code content and its receiving timestamp; The data processing host compares the currently received QR code content with the QR code content already received within a preset time window. If the two are the same, it is determined to be a duplicate scan and the current input is ignored. The data processing host extracts the borrowing and returning record number from the return permission QR code, queries the processing status of the borrowing and returning record number in the concurrency dictionary, and if the processing status is "processing", it prohibits the creation of a new return data processing task corresponding to the borrowing and returning record number. If the borrowing and returning record number is in an unprocessed state in the concurrency dictionary, the data processing host will register the borrowing and returning record number as being processed in the concurrency dictionary, and create a return data processing task instance bound to the borrowing and returning record number based on the device association information and task parameters in the return permission QR code.

[0009] Optionally, in the physically isolated dual-host device closed-loop management method described in this application, the data processing host listens for device access events based on the return processing task, reads the physical serial number of the accessed device, associates the physical serial number with the current return task, and performs data processing operations on the return device, including: The data processing host listens for device access events on the corresponding interface based on the grid number in the return task control message; When a device is detected to be connected, the physical serial number of the currently connected device is read, and it is determined whether there is a historical physical serial number corresponding to the grid number in the local mapping. If it does not exist, the grid number will be associated with the currently read physical serial number and stored to establish a local mapping, and then the normal processing flow will be entered to perform data processing operations on the returned device. If it already exists, then perform a consistency check between the currently read physical sequence number and the historical physical sequence number corresponding to that grid number in the local mapping; If the verification is successful, proceed to the normal processing flow and perform data processing operations on the returned equipment. If the verification fails, the device ownership is determined to be abnormal, a result control message of detection failure type is generated, and the current return processing task is terminated.

[0010] Optionally, the closed-loop management method for physically isolated dual-host devices described in this application further includes: If the data processing operation for the returned device includes uploading data to the target storage location, the data processing host generates a unique upload task identifier for each upload operation; When the upload progress feedback is triggered, the data processing host will compare the upload task identifier corresponding to the upload task that triggered the feedback with the current upload task identifier; If the two do not match, the data processing host will generate a processing result control message corresponding to the upload task in the background and maintain the current progress display on the interface.

[0011] Optionally, in the physically isolated dual-host device closed-loop management method described in this application, the data processing host generates a result QR code based on the execution result of the return processing task. The result QR code includes the borrowing / returning record number and processing result information, including: When the device is successfully detected and the data processing operation for the returned device is completed and uploaded successfully, the data processing host generates a record update result QR code, which contains the borrowing and returning record number and data statistics information. When a device fails to be detected, the data processing host generates a detection failure result QR code, which contains the borrowing / returning record number, device type, and reason for failure. When the data processing result fails to be uploaded, the data processing host generates an alarm result QR code. The result QR code contains the borrowing and returning record number, the total number of data objects, the number of data objects that have been uploaded, the grid number, the upload method, and the watermark type.

[0012] Optionally, in the physically isolated dual-host device closed-loop management method described in this application, the device borrowing / returning host reads the result QR code and updates the corresponding borrowing / returning record and device status based on the borrowing / returning record number and processing result information therein, including: The equipment borrowing and returning host obtains the result QR code through the industrial barcode scanner, parses and processes the result control message, and locates the corresponding equipment management record based on the borrowing and returning record number. When the processing result is successful, the device borrowing and returning host updates the device status in the device management record to idle status, executes the device release operation, and records the return completion time; When the processing result is a detection failure, the device borrowing and returning host will update the corresponding borrowing and returning record to the return failure status, will not perform the device release operation, and will prompt the user to return the device again. When the processing result is upload failure, the device borrowing and returning host will update the corresponding borrowing and returning record to the return failure status, save the processed file statistics, generate an alarm record and send an alarm notification.

[0013] Optionally, the closed-loop management method for physically isolated dual-host devices described in this application further includes: After receiving the return task control message, the data processing host determines whether the data processing host has been configured with backup storage media and whether the backup storage media is in an idle state that is not occupied by other return processing tasks. When the backup storage medium is configured and idle, the data processing host allows the user to choose to output data to the backup storage medium. Otherwise, disable the output option for the backup storage media; After the data processing host finishes outputting the file to the backup storage medium, it generates a QR code to open the backup storage medium slot and starts the return timer. After the host obtains the QR code, it opens the corresponding compartment when the device is borrowed or returned. If the backup storage medium is returned within the preset return time and is in normal condition, the data processing host generates a confirmation QR code, and the device borrowing and returning host records the status of the backup storage medium return. If the backup storage medium is not returned within the preset return time or is in an abnormal state, the data processing host generates an abnormal alarm QR code and the device borrowing and returning host records the alarm.

[0014] Optionally, the closed-loop management method for physically isolated dual-host devices described in this application further includes: After completing the equipment release control operation, the equipment borrowing and returning host generates a return record verification message and encodes it as a QR code for display. The data processing host acquires and parses the return record verification message, extracts the borrowing and returning record number and the device release status, and compares it with the processing result of the corresponding return processing task recorded locally on the data processing host. If the two are inconsistent, the data processing host generates a consistency anomaly alarm QR code, which is obtained by the device borrowing and returning host, records the abnormal event, and triggers the manual verification process.

[0015] Secondly, this application provides a closed-loop management and control system for physically isolated dual-host devices. The system includes a memory and a processor. The memory stores a program for a closed-loop management and control method for physically isolated dual-host devices. When the program for the closed-loop management and control method for physically isolated dual-host devices is executed by the processor, it implements the following steps: The device borrowing and returning host is used to generate a return task control message in response to a device return request, encrypt the return task control message and encode it into a return permission QR code, and read the result QR code to update the borrowing and returning record and device status. The data processing host is used to read the return permission QR code, decode and decrypt it, establish a return processing task based on the borrowing and returning record number, listen for device access events, associate the physical serial number with the current return processing task, perform data processing operations on the returning device, and generate a result QR code based on the result of the data processing operation on the returning device and send it back to the device borrowing and returning host. Industrial barcode scanners are used to transmit QR codes between the equipment borrowing and returning host and the data processing host. The intelligent cabinet body and compartment lock control module are used to perform compartment opening and closing operations under the control of the equipment borrowing and returning host.

[0016] As described above, the closed-loop management method and system for physically isolated dual-host devices provided in this application aims to solve the problems of repetitive execution of smart cabinet return tasks, task and device mismatch, crosstalk of asynchronous processing results, and unreliable closed-loop management of success / failure states under physically isolated dual-host conditions. By binding each return to a unique borrowing / returning record number, and ensuring this record number permeates the permission QR code, data processing task, success result QR code, and failure alarm QR code, task-level collaboration between the borrowing / returning host and the data processing host is achieved. Limited control commands, processing parameters, and result statistics are transmitted between the two physically isolated hosts via QR codes, without transmitting any original business files. Business files in the storage medium to be returned are read to the local data processing host via USB interface using mass storage or MTP media transmission protocol. On this host, all secure processing operations, including watermarking, file archiving and uploading, and media data erasure, are independently completed. This avoids the leakage risk caused by business files being transmitted across isolated domains via optical QR codes, achieving closed-loop collaborative management of the entire task process between the two hosts while meeting physical isolation security standards.

[0017] Other features and advantages of this application will be set forth in the following description and will be apparent in part from the description or may be learned by practicing embodiments of this application. The objectives and other advantages of this application may be realized and obtained by means of the structures particularly pointed out in the written description and the accompanying drawings. Attached Figure Description

[0018] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 A flowchart illustrating the closed-loop management method for physically isolated dual-host devices provided in this application embodiment; Figure 2 This is a schematic diagram of the DCC intelligent cabinet dual-host physical isolation system architecture provided in the embodiments of this application; Figure 3 A timing diagram of QR code messages between the device borrowing / returning host and the data processing host provided in an embodiment of this application. Detailed Implementation

[0020] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. The components of the embodiments of this application described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely represents selected embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0021] It should be noted that similar reference numerals and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. Furthermore, in the description of this application, the terms "first," "second," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0022] Please refer to Figure 1 , Figure 1 This is a flowchart of a closed-loop management method for physically isolated dual-host devices according to some embodiments of this application. This closed-loop management method for physically isolated dual-host devices is used in terminal devices, such as computers and mobile terminals. The closed-loop management method for physically isolated dual-host devices includes the following steps: S11. The equipment borrowing and returning host responds to the equipment return request by querying existing borrowing and returning records to obtain the borrowing and returning record number, and generates a return task control message based on the borrowing and returning record number and the equipment association information. After encrypting the return task control message, the encrypted message is encoded into a return permission QR code. S12. The data processing host reads the return permission QR code, decodes and decrypts it, extracts the borrowing and returning record number and device association information, and establishes a return processing task based on the borrowing and returning record number. S13. The data processing host listens for device access events based on the return processing task, reads the physical serial number of the accessed device, associates the physical serial number with the current return task, and performs data processing operations on the return device. S14. The data processing host generates a result QR code based on the execution result of the return processing task. The result QR code contains the borrowing and returning record number and processing result information, and is read by an industrial barcode scanner and then sent back to the equipment borrowing and returning host. S15. The device borrowing and returning host reads the result QR code and updates the corresponding borrowing and returning record and device status based on the borrowing and returning record number and processing result information.

[0023] It should be noted that, unlike general QR code physically isolated transmission, this application binds the QR code message with the smart cabinet's return record number, device number, compartment number, upload parameters, and processing result. This allows the optical channel to participate in the specific return task control, rather than simply transparently transmitting source data. By using the borrowing / return record number to connect the permission QR code, data processing task, and result QR code, a task-level collaborative closed loop is achieved between physically isolated dual hosts.

[0024] According to an embodiment of the present invention, in response to a device return request, the device borrowing and returning host queries existing borrowing and returning records to obtain a borrowing and returning record number, and generates a return task control message based on the borrowing and returning record number and device association information. After encrypting the return task control message, the encrypted message is encoded into a return authorization QR code, including: The return task control message includes the borrowing / returning record number, equipment association information, upload method, and watermark type. The equipment association information includes the equipment number, equipment type, and grid number. The device borrowing and returning host uses a preset encryption key and initialization vector to encrypt the return task control message with AES, and adds a QR code recognition prefix to the encryption result before encoding it into a return permission QR code.

[0025] It should be noted that by employing multiple mechanisms, including AES encryption, QR code recognition prefix, short-term display, standardized QR code input, repeated scanning time window detection, and lock handling for the same borrowing and returning record number, the risk of plaintext exposure of the QR code is reduced, continuous false triggering and repeated execution of the same return task are prevented, thus improving the system's security and reliability. In this embodiment of the invention, the device borrowing and returning host queries the database to obtain the borrowing and returning record number, device number, device type (e.g., camera), and locker number (number 3), and assembles the above information together with the smart locker name, upload method (public disk upload), and watermark type (timestamp watermark) into a return task control message. The device borrowing and returning host encrypts the message using a preset AES key and initialization vector, adds a specific QR code recognition prefix (e.g., "DCC_") to the encryption result, and then encodes the encrypted content with the prefix into a return permission QR code and displays it on the screen. After the scanner of the data processing host reads the QR code, it first identifies the prefix to confirm the message type, and then calls AES decryption to restore the complete task control parameters, thereby completing the preparation work for scanning to establish the task.

[0026] According to an embodiment of the present invention, the data processing host reads the return permit QR code, decodes and decrypts it, extracts the borrowing / return record number and device association information, and establishes a return processing task based on the borrowing / return record number, including: The data processing host performs normalization processing on the received return permission QR code, and records the normalized QR code content and its receiving timestamp; The data processing host compares the currently received QR code content with the QR code content already received within a preset time window. If the two are the same, it is determined to be a duplicate scan and the current input is ignored. The data processing host extracts the borrowing and returning record number from the return permission QR code, queries the processing status of the borrowing and returning record number in the concurrency dictionary, and if the processing status is "processing", it prohibits the creation of a new return data processing task corresponding to the borrowing and returning record number. If the borrowing and returning record number is in an unprocessed state in the concurrency dictionary, the data processing host will register the borrowing and returning record number as being processed in the concurrency dictionary, and create a return data processing task instance bound to the borrowing and returning record number based on the device association information and task parameters in the return permission QR code.

[0027] It should be noted that this invention employs a dual anti-duplicate mechanism through repeated scanning time window filtering and concurrent dictionary record number state locking. When the same QR code is continuously triggered by the scanner within a preset time window, the system automatically ignores duplicate inputs; when the same borrowing / returning record number is already in a processing state, the system prohibits the creation of a second processing task. This mechanism effectively avoids the repeated execution of the same return task due to human error or continuous scanner triggering, preventing waste of system resources and confusion in task states. In this embodiment, after the data processing host scans the return permission QR code, it performs normalization processing, including URL decoding to restore special characters, identifying and removing QR code prefixes, cleaning up any possible whitespace characters, and then recording the processed QR code content and the current timestamp in a memory cache. When the same QR code is repeatedly scanned within 3 seconds due to continuous scanner triggering, the data processing host compares the newly received QR code content with the historical records within a 5-second time window in the cache. If the content is found to be completely identical, it is determined to be a duplicate scan, and subsequent inputs are automatically ignored without triggering any task operations. Simultaneously, the data processing host extracts the borrowing / returning record number from the QR code and queries the status of that record number in the concurrency dictionary. If a "processing" marker already exists, creating a second processing task for that record number is prohibited until the current task is completed and the processing marker for that record number is released. The concurrency dictionary is a concurrency-safe data structure in the data processing host's memory used to maintain the mapping relationship between "borrowing / returning record numbers" and "processing statuses." Since device returns may cause request conflicts due to repeated scanning, this dictionary uses its internal locking mechanism to ensure that queries and status changes (never processed → processing) for the same record are atomic in a multi-threaded environment. This strictly prevents the creation of multiple return processing tasks for the same borrowing / returning record number, ensuring the uniqueness of task processing and data consistency.

[0028] According to an embodiment of the present invention, the data processing host listens for device access events based on the return processing task, reads the physical serial number of the accessed device, associates the physical serial number with the current return task, and performs data processing operations on the return device, including: The data processing host listens for device access events on the corresponding interface based on the grid number in the return task control message; When a device is detected to be connected, the physical serial number of the currently connected device is read, and it is determined whether there is a historical physical serial number corresponding to the grid number in the local mapping. If it does not exist, the grid number will be associated with the currently read physical serial number and stored to establish a local mapping, and then the normal processing flow will be entered to perform data processing operations on the returned device. If it already exists, then perform a consistency check between the currently read physical sequence number and the historical physical sequence number corresponding to that grid number in the local mapping; If the verification is successful, proceed to the normal processing flow and perform data processing operations on the returned equipment. If the verification fails, the device ownership is determined to be abnormal, a result control message of detection failure type is generated, and the current return processing task is terminated.

[0029] It should be noted that this invention, through a local mapping and consistency verification mechanism between the grid number and the device's physical serial number, enables the data processing host to compare the physical serial number of the currently connected device with historical mapping records, ensuring that the physically inserted device is consistent with the device bound to the return task. When the devices do not match, processing is automatically terminated and a detection failure result is generated, physically eliminating data attribution errors caused by incorrect device insertion into the wrong grid or manual replacement, significantly improving the reliability and data security of the return process. The data processing operations for the returned devices mainly include file processing operations: Enumerate the files in the returned device and apply watermarks to images, videos, and images in office documents according to the watermark type in the return task control message. According to the upload method in the return task control message, the processed file is uploaded to the file server or backup USB drive, and a unique upload task ID is generated each time the upload is started. The upload progress interface only follows the latest upload task ID. When the upload is completed and the callback is triggered, the borrowing and returning record number corresponding to the callback task is compared with the borrowing and returning record number of the task on the current interface. If they do not match, a result QR code corresponding to the background task is generated without forcibly switching the current interface.

[0030] In this embodiment of the invention, the data processing host continuously monitors the device access event of the USB interface corresponding to the port number (No. 3) in the return task control message. When a camera device is detected to be connected, the data processing host reads the physical serial number (SN: X9K3L2P1) of the camera through the underlying interface of the operating system, and then checks whether a historical serial number record for port number 3 already exists in the local mapping. If the mapping table is empty, "port number 3" and "SN: X9K3L2P1" are associated and stored to establish a local mapping and enter the normal processing flow; if a record of "port number 3: SN: X9K3L2P1" already exists in the mapping table, the currently read serial number is compared with the historical record. If they match, the normal processing flow is entered; if the detected serial number is "SN: Y7H4M5N2" and does not match the historical record, the device ownership is determined to be abnormal, the current processing task is immediately terminated, and a detection failure QR code is generated and sent back to the device borrowing and returning host.

[0031] According to an embodiment of the present invention, it further includes: If the data processing operation for the returned device includes uploading data to the target storage location, the data processing host generates a unique upload task identifier for each upload operation; When the upload progress feedback is triggered, the data processing host will compare the upload task identifier corresponding to the upload task that triggered the feedback with the current upload task identifier; If the two do not match, the data processing host will generate a processing result control message corresponding to the upload task in the background and maintain the current progress display on the interface.

[0032] It should be noted that this invention generates an independent upload task identifier for each upload operation and compares the task identifier carried in the upload progress feedback with the task identifier on the current interface when the upload progress feedback is triggered. Only feedback that matches is allowed to update the progress display on the current interface. When they do not match, a result message is generated in the background while maintaining the current interface, effectively isolating progress callback interference between multiple asynchronous upload tasks and avoiding the interface state crosstalk problem where the callback results of old tasks overwrite the current task's interface, thus improving the user interaction experience in multi-task concurrent scenarios. Specifically, if the two do not match, it is determined that the current feedback belongs to a background asynchronous task, and a processing result control message corresponding to that background task is generated without updating the progress display on the current interface, in order to avoid interface state crosstalk between different return processing tasks.

[0033] According to an embodiment of the present invention, the data processing host generates a result QR code based on the execution result of the return processing task. The result QR code includes the borrowing / returning record number and processing result information, including: When the device is successfully detected and the data processing operation for the returned device is completed and uploaded successfully, the data processing host generates a record update result QR code, which contains the borrowing and returning record number and data statistics information. When a device fails to be detected, the data processing host generates a detection failure result QR code, which contains the borrowing / returning record number, device type, and reason for failure. When the data processing result fails to be uploaded, the data processing host generates an alarm result QR code. The result QR code contains the borrowing and returning record number, the total number of data objects, the number of data objects that have been uploaded, the grid number, the upload method, and the watermark type.

[0034] It should be noted that this invention categorizes the execution results of the return processing task into three types of QR codes: record update type (success), detection failure type, and alarm type (upload failure). This allows the device borrowing and returning host to perform differentiated device release control based on different result types—releasing the device and updating the record upon success, and not releasing the device and prompting the user to return it again upon failure. This result-type-based differentiated control mechanism avoids the data management risks of traditional solutions that still release the device according to the success process after an upload failure, achieving a reliable closed loop between success and failure states. Detection failure refers to an error at the device identity verification level where the serial number read after physical access is inconsistent with the historical grid number bound in the return record (e.g., inserted into the wrong grid). Upload failure refers to an error at the data persistence communication level where device identity verification and data processing operations have been completed, but the sending of the processing result file to the target storage location fails due to network or service anomalies.

[0035] According to an embodiment of the present invention, the device borrowing / returning host reads the result QR code and updates the corresponding borrowing / returning record and device status based on the borrowing / returning record number and processing result information therein, including: The equipment borrowing and returning host obtains the result QR code through the industrial barcode scanner, parses and processes the result control message, and locates the corresponding equipment management record based on the borrowing and returning record number. When the processing result is successful, the device borrowing and returning host updates the device status in the device management record to idle status, executes the device release operation, and records the return completion time; When the processing result is a detection failure, the device borrowing and returning host will update the corresponding borrowing and returning record to the return failure status, will not perform the device release operation, and will prompt the user to return the device again. When the processing result is upload failure, the device borrowing and returning host will update the corresponding borrowing and returning record to the return failure status, save the processed file statistics, generate an alarm record and send an alarm notification.

[0036] It should be noted that, after reading the result QR code, the device borrowing and returning host locates the corresponding device management record based on the borrowing and returning record number, and performs different operations according to the processing result type, such as updating to idle status and clearing borrowing association (success), keeping the device able to initiate return again (detection failure), and saving processed statistical information and sending alarm notification (upload failure). This ensures that the borrowing and returning record status on the device borrowing and returning host is synchronized with the task execution result on the data processing host, thus ensuring the accuracy of device release control operations and the integrity of business records.

[0037] According to an embodiment of the present invention, it further includes: After receiving the return task control message, the data processing host determines whether the data processing host has been configured with backup storage media and whether the backup storage media is in an idle state that is not occupied by other return processing tasks. When the backup storage medium is configured and idle, the data processing host allows the user to choose to output data to the backup storage medium. Otherwise, disable the output option for the backup storage media; After the data processing host finishes outputting the file to the backup storage medium, it generates a QR code to open the backup storage medium slot and starts the return timer. After the host obtains the QR code, it opens the corresponding compartment when the device is borrowed or returned. If the backup storage medium is returned within the preset return time and is in normal condition, the data processing host generates a confirmation QR code, and the device borrowing and returning host records the status of the backup storage medium return. If the backup storage medium is not returned within the preset return time or is in an abnormal state, the data processing host generates an abnormal alarm QR code and the device borrowing and returning host records the alarm.

[0038] It should be noted that this invention, through dual judgment of the backup storage medium's configuration status and idle status, disables the backup output option when the backup medium is not configured, not connected, or still in the pending return state of a previous task, thus avoiding resource conflicts caused by multiple return tasks simultaneously occupying the same backup medium. By generating an open slot QR code and starting the return timer after backup output is completed, and monitoring return, timeout, and abnormal statuses and generating corresponding QR codes to feed back to the device borrowing / returning host, a closed-loop management system for the entire lifecycle of the backup storage medium is achieved. For example, a DCC smart cabinet is configured with a backup USB flash drive as a backup media for data output. After user A completes data processing for returning the device, they select the backup USB flash drive method. The data processing host first determines whether the backup USB flash drive is configured and connected and is not currently occupied by other tasks. After confirming it is idle, copying is allowed. After copying is completed, the data processing host generates a QR code to open the backup USB flash drive slot. The device borrowing / returning host obtains this code, opens the dedicated slot, user A takes the USB flash drive, and the system simultaneously starts a 5-minute return timer. If User A returns the backup USB drive within 5 minutes, the system generates a confirmation QR code to record the return completion; if it is not returned within the time limit, the system generates a timeout alarm QR code to notify the administrator. Before User A returns the USB drive, when User B initiates a new task, the data processing host determines that the backup USB drive is still in a "pending return" occupied state and automatically disables the backup USB drive output option, which can only be re-enabled after User A returns the USB drive.

[0039] According to an embodiment of the present invention, it further includes: After completing the equipment release control operation, the equipment borrowing and returning host generates a return record verification message and encodes it as a QR code for display. The data processing host acquires and parses the return record verification message, extracts the borrowing and returning record number and the device release status, and compares it with the processing result of the corresponding return processing task recorded locally on the data processing host. If the two are inconsistent, the data processing host generates a consistency anomaly alarm QR code, which is obtained by the device borrowing and returning host, records the abnormal event, and triggers the manual verification process.

[0040] It should be noted that this invention generates a return record verification message after the device release is completed by the device borrowing / returning host and sends it back to the data processing host for comparison. This enables post-event consistency verification of the final execution result of the return task, even when both hosts are in independent maintenance states. When the device release status recorded by the device borrowing / returning host is inconsistent with the task processing result recorded by the data processing host, the system automatically generates a consistency anomaly alarm and triggers a manual verification process. This adds a fallback verification mechanism to the closed-loop control of QR code messages, further reducing the risk of data inconsistency caused by abnormal QR code transmission, missed scanning, or state drift between the two hosts, thus improving the overall fault tolerance and data reliability of the system.

[0041] Please refer to Figure 2 , Figure 2 This is a schematic diagram of the DCC intelligent cabinet dual-host physical isolation system architecture in some embodiments of this application. The present invention also discloses a closed-loop management and control system for physically isolated dual-host devices, including a memory and a processor. The memory stores a closed-loop management and control method program for physically isolated dual-host devices. When the processor executes the closed-loop management and control method program for physically isolated dual-host devices, it performs the following steps: The device borrowing and returning host is used to generate a return task control message in response to a device return request, encrypt the return task control message and encode it into a return permission QR code, and read the result QR code to update the borrowing and returning record and device status. The data processing host is used to read the return permission QR code, decode and decrypt it, establish a return processing task based on the borrowing and returning record number, listen for device access events, associate the physical serial number with the current return processing task, perform data processing operations on the returning device, and generate a result QR code based on the result of the data processing operation on the returning device and send it back to the device borrowing and returning host. Industrial barcode scanners are used to transmit QR codes between the equipment borrowing and returning host and the data processing host. The intelligent cabinet body and compartment lock control module are used to perform compartment opening and closing operations under the control of the equipment borrowing and returning host.

[0042] Figure 3 This is a timing diagram of QR code messages between the device borrowing / returning host and the data processing host in some embodiments of this application.

[0043] This invention discloses a closed-loop management method and system for physically isolated dual-host devices, aiming to solve the problems of repetitive execution of smart cabinet return tasks, task-device mismatch, crosstalk of asynchronous processing results, and unreliable closed-loop management of success / failure states under physically isolated dual-host conditions. By binding each return to a unique borrowing / returning record number, and making this record number permeate the permission QR code, data processing task, success result QR code, and failure alarm QR code, task-level collaboration between the borrowing / returning host and the data processing host is achieved. Limited control commands, processing parameters, and result statistics are transmitted between the two physically isolated hosts via QR codes, without transmitting any original business files. Business files in the storage medium to be returned are read to the local data processing host via USB interface using mass storage or MTP media transmission protocol. On this host, all security processing operations, including watermarking, file archiving and uploading, and media data erasure, are independently completed. This avoids the leakage risk caused by business files being transmitted across isolated domains via optical QR codes, achieving closed-loop collaborative management of the entire task process between the two hosts while meeting physical isolation security specifications.

[0044] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple units or components can be combined, or integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the various components shown or discussed can be through some interfaces, and the indirect coupling or communication connection between devices or units can be electrical, mechanical, or other forms.

[0045] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units. They may be located in one place or distributed across multiple network units. Some or all of the units may be selected to achieve the purpose of this embodiment according to actual needs.

[0046] In addition, in the various embodiments of the present invention, each functional unit can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the integrated unit can be implemented in hardware or in the form of hardware plus software functional units.

Claims

1. A closed-loop management and control method for physically isolated dual-host devices, characterized in that, Includes the following steps: In response to a device return request, the device borrowing and returning host queries existing borrowing and returning records to obtain the borrowing and returning record number, and generates a return task control message based on the borrowing and returning record number and the device association information. After encrypting the return task control message, the encrypted message is encoded into a return permission QR code. The data processing host reads the return permission QR code, decodes and decrypts it, extracts the borrowing and returning record number and device association information, and establishes a return processing task based on the borrowing and returning record number; The data processing host listens for device access events based on the return processing task, reads the physical serial number of the accessed device, associates the physical serial number with the current return task, and performs data processing operations on the return device. The data processing host generates a result QR code based on the execution result of the return processing task. The result QR code contains the borrowing and returning record number and processing result information, and is read by an industrial barcode scanner and then sent back to the equipment borrowing and returning host. The device borrowing / returning host reads the result QR code and updates the corresponding borrowing / returning record and device status based on the borrowing / returning record number and processing result information.

2. The closed-loop management method for physically isolated dual-host devices according to claim 1, characterized in that, The device borrowing and returning host responds to a device return request by querying existing borrowing and returning records to obtain a borrowing and returning record number, and generating a return task control message based on the borrowing and returning record number and device association information. After encrypting the return task control message, the encrypted message is encoded into a return authorization QR code, including: The return task control message includes the borrowing / returning record number, equipment association information, upload method, and watermark type. The equipment association information includes the equipment number, equipment type, and grid number. The device borrowing and returning host uses a preset encryption key and initialization vector to encrypt the return task control message with AES, and adds a QR code recognition prefix to the encryption result before encoding it into a return permission QR code.

3. The closed-loop management method for physically isolated dual-host devices according to claim 1, characterized in that, The data processing host reads and decodes the return permission QR code, extracts the borrowing / return record number and device association information, and establishes a return processing task based on the borrowing / return record number, including: The data processing host performs normalization processing on the received return permission QR code, and records the normalized QR code content and its receiving timestamp; The data processing host compares the currently received QR code content with the QR code content already received within a preset time window. If the two are the same, it is determined to be a duplicate scan and the current input is ignored. The data processing host extracts the borrowing and returning record number from the return permission QR code, queries the processing status of the borrowing and returning record number in the concurrency dictionary, and if the processing status is "processing", it prohibits the creation of a new return data processing task corresponding to the borrowing and returning record number. If the borrowing and returning record number is in an unprocessed state in the concurrency dictionary, the data processing host will register the borrowing and returning record number as being processed in the concurrency dictionary, and create a return data processing task instance bound to the borrowing and returning record number based on the device association information and task parameters in the return permission QR code.

4. The closed-loop management method for physically isolated dual-host devices according to claim 1, characterized in that, The data processing host listens for device access events based on the return processing task, reads the physical serial number of the accessed device, associates the physical serial number with the current return task, and performs data processing operations on the return device, including: The data processing host listens for device access events on the corresponding interface based on the grid number in the return task control message; When a device is detected to be connected, the physical serial number of the currently connected device is read, and it is determined whether there is a historical physical serial number corresponding to the grid number in the local mapping. If it does not exist, the grid number will be associated with the currently read physical serial number and stored to establish a local mapping, and then the normal processing flow will be entered to perform data processing operations on the returned device. If it already exists, then perform a consistency check between the currently read physical sequence number and the historical physical sequence number corresponding to that grid number in the local mapping; If the verification is successful, proceed to the normal processing flow and perform data processing operations on the returned equipment. If the verification fails, the device ownership is determined to be abnormal, a result control message of detection failure type is generated, and the current return processing task is terminated.

5. The closed-loop management method for physically isolated dual-host devices according to claim 4, characterized in that, Also includes: If the data processing operation for the returned device includes uploading data to the target storage location, the data processing host generates a unique upload task identifier for each upload operation; When the upload progress feedback is triggered, the data processing host will compare the upload task identifier corresponding to the upload task that triggered the feedback with the current upload task identifier; If the two do not match, the data processing host will generate a processing result control message corresponding to the upload task in the background and maintain the current progress display on the interface.

6. The closed-loop management method for physically isolated dual-host devices according to claim 1, characterized in that, The data processing host generates a result QR code based on the execution result of the return processing task. The result QR code contains the borrowing / return record number and processing result information, including: When the device is successfully detected and the data processing operation for the returned device is completed and uploaded successfully, the data processing host generates a record update result QR code, which contains the borrowing and returning record number and data statistics information. When a device fails to be detected, the data processing host generates a detection failure result QR code, which contains the borrowing / returning record number, device type, and reason for failure. When the data processing result fails to be uploaded, the data processing host generates an alarm result QR code. The result QR code contains the borrowing and returning record number, the total number of data objects, the number of data objects that have been uploaded, the grid number, the upload method, and the watermark type.

7. The closed-loop management method for physically isolated dual-host devices according to claim 1, characterized in that, The device borrowing / returning host reads the result QR code and updates the corresponding borrowing / returning record and device status based on the borrowing / returning record number and processing result information, including: The equipment borrowing and returning host obtains the result QR code through the industrial barcode scanner, parses and processes the result control message, and locates the corresponding equipment management record based on the borrowing and returning record number. When the processing result is successful, the device borrowing and returning host updates the device status in the device management record to idle status, executes the device release operation, and records the return completion time; When the processing result is a detection failure, the device borrowing and returning host will update the corresponding borrowing and returning record to the return failure status, will not perform the device release operation, and will prompt the user to return the device again. When the processing result is upload failure, the device borrowing and returning host will update the corresponding borrowing and returning record to the return failure status, save the processed file statistics information, generate an alarm record and send an alarm notification.

8. The closed-loop management method for physically isolated dual-host devices according to claim 1, characterized in that, Also includes: After receiving the return task control message, the data processing host determines whether the data processing host has been configured with backup storage media and whether the backup storage media is in an idle state that is not occupied by other return processing tasks. When the backup storage medium is configured and idle, the data processing host allows the user to choose to output data to the backup storage medium. Otherwise, disable the output option for the backup storage media; After the data processing host finishes outputting the file to the backup storage medium, it generates a QR code to open the backup storage medium slot and starts the return timer. After the host obtains the QR code, it opens the corresponding compartment when the device is borrowed or returned. If the backup storage medium is returned within the preset return time and is in normal condition, the data processing host generates a confirmation QR code, and the device borrowing and returning host records the status of the backup storage medium return. If the backup storage medium is not returned within the preset return time or is in an abnormal state, the data processing host generates an abnormal alarm QR code and the device borrowing and returning host records the alarm.

9. The closed-loop management method for physically isolated dual-host devices according to claim 7, characterized in that, Also includes: After completing the equipment release control operation, the equipment borrowing and returning host generates a return record verification message and encodes it as a QR code for display. The data processing host acquires and parses the return record verification message, extracts the borrowing and returning record number and the device release status, and compares it with the processing result of the corresponding return processing task recorded locally on the data processing host. If the two are inconsistent, the data processing host generates a consistency anomaly alarm QR code, which is obtained by the device borrowing and returning host, records the abnormal event, and triggers the manual verification process.

10. A physically isolated dual-host device closed-loop control system, characterized in that, include: The device borrowing and returning host is used to generate a return task control message in response to a device return request, encrypt the return task control message and encode it into a return permission QR code, and read the result QR code to update the borrowing and returning record and device status. The data processing host is used to read the return permission QR code, decode and decrypt it, establish a return processing task based on the borrowing and returning record number, listen for device access events, associate the physical serial number with the current return processing task, perform data processing operations on the returning device, and generate a result QR code based on the result of the data processing operation on the returning device and send it back to the device borrowing and returning host. Industrial barcode scanners are used to transmit QR codes between the equipment borrowing and returning host and the data processing host. The intelligent cabinet body and compartment lock control module are used to perform compartment opening and closing operations under the control of the equipment borrowing and returning host.

Images