Scanning equipment control process management method based on custom protocol

Abstract

The invention relates to the technical field of electronics, in particular to a scanning equipment control process management method based on a custom protocol. According to the method provided by the invention, a secure communication bridge between a Web environment and local hardware is established through interaction between a custom protocol and an operating system registry; a driver and an API interface matched with a configuration file are dynamically loaded by using a local plug-in, so that multi-model scanning equipment is compatible, and the hardware adaptation and maintenance complexity is reduced; original data is converted into standardized data, an atomized transactional data processing pipeline is constructed, and the integrity and traceability of cryopreservation tube information are ensured; finally, a visual interface is dynamically analyzed and rendered based on a Web client, real-time mapping of cryopreservation tube layout is achieved, and operation intuition, sample searching efficiency and user experience are improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of electronics, in particular to a scanning device control flow management method based on a custom protocol. BACKGROUND

[0002] In biomedical research and clinical applications, cryotubes are widely used for storing cells, tissues, and other biological samples. To efficiently manage and track these samples, cryotube scanning technology has emerged. This technology identifies cryotubes through barcodes or QR codes and uses scanners to quickly read the information, thereby achieving automated management of samples. However, with the development of technology, some challenges have also emerged, affecting its widespread application.

[0003] Currently, many laboratories and medical institutions use specific software systems to manage sample data, but these systems often require operation through a web interface. When the scanner reads the barcode or QR code on the cryotube, if it cannot directly trigger the corresponding web operation, it will result in low efficiency of data entry. In addition, compatibility issues between different systems and compatibility issues between scanning devices and different software systems also make this process complex, increasing the difficulty of user operation. SUMMARY

[0004] Therefore, the purpose of the present application is to provide a scanning device control flow management method based on a custom protocol.

[0005] In a first aspect, the embodiments of the present application provide a scanning device control flow management method based on a custom protocol, which comprises: In response to a scanning instruction triggering event, a custom protocol request containing user credentials is constructed to call a custom protocol through an operating system registry; A local plug-in process is started by the custom protocol, device identifiers in a preset configuration file are parsed, and a matching scanning device driver and API interface are dynamically loaded; The loaded scanning device driver controls the physical scanning device to perform scanning operations, and obtains raw data containing cryotube barcode and location information; The raw data is converted into standardized data containing barcode fields and location coordinate fields; The standardized data is dynamically parsed in the Web client and a cryotube location visualization interface is rendered.

[0006] In combination with the first aspect, the step of constructing a custom protocol request containing user credentials comprises: An initial custom protocol request is constructed according to protocol parameter construction rules; Encrypted user credentials are embedded in the protocol header of the custom protocol request.

[0007] In conjunction with the first aspect, the steps of controlling the physical scanning device to perform scanning operations through the loaded scanning device driver include: Based on the device model code in the configuration file, load the corresponding dynamic link library file from the preset driver library.

[0008] In conjunction with the first aspect, after the step of converting the raw data into standardized data containing barcode and location coordinate fields, the following steps are also included: In response to timed polling events, monitor the change status of scanning tasks in the database; If a status update is detected, the status change information is sent back to the web client via a WebSocket connection or a timed polling connection to update the display interface.

[0009] In conjunction with the first aspect, if a state update is detected, the step of sending the state change information back to the web client via a WebSocket connection or a periodic polling connection includes: When new scanned data is written to the database, the WebSocket server is proactively triggered to broadcast a data update event to subscribed web clients.

[0010] In conjunction with the first aspect, the steps for obtaining raw data containing cryopreservation tube barcodes and location information include: The barcode of the cryopreservation tube is identified by the identification device of the physical scanning equipment, and the physical location of the cryopreservation tube is mapped into two-dimensional coordinate system data by the positioning sensor of the physical scanning equipment.

[0011] In conjunction with the first aspect, the steps of dynamically parsing standardized data and rendering a visualization interface of cryopreservation tube locations on the web client also include: The status of cryopreservation tubes is dynamically marked in the gridded interface based on location coordinate data.

[0012] Secondly, this application provides a scanning device control process management device based on a custom protocol, the device comprising: The building module is used to construct a custom protocol request containing user credentials in response to a scan command trigger event, so as to invoke the custom protocol through the operating system registry; The parsing module is used to start the local plugin process by a custom protocol, parse the device identifier in the preset configuration file, and dynamically load the matching scanned device driver and API interface; The acquisition module is used to control the physical scanning device to perform scanning operations through the loaded scanning device driver, and to acquire raw data containing the barcode and location information of the cryopreservation tube; The conversion module is used to convert raw data into standardized data that includes barcode fields and location coordinate fields; The display module is used to dynamically parse standardized data and render a visualization interface of cryopreservation tube locations on the web client.

[0013] Thirdly, this application provides an electronic device, which includes a memory and a processor. The memory stores a computer program, and the processor runs the computer program to cause the electronic device to perform the above-described method.

[0014] Fourthly, this application provides a storage medium storing computer program instructions, which are read and executed by a processor to perform the above-described method.

[0015] The embodiments of the present invention bring the following beneficial effects: The scanning device control flow management method based on a custom protocol provided in this application includes: responding to a scanning command trigger event, constructing a custom protocol request containing user credentials to call the custom protocol through the operating system registry; starting a local plug-in process by the custom protocol, parsing the device identifier in the preset configuration file, and dynamically loading the matching scanning device driver and API interface; controlling the physical scanning device to perform scanning operations through the loaded scanning device driver to obtain raw data containing cryopreservation tube barcodes and location information; converting the raw data into standardized data containing barcode fields and location coordinate fields; and dynamically parsing the standardized data and rendering a cryopreservation tube location visualization interface on a web client.

[0016] The method provided in this application establishes a secure communication bridge between the web environment and local hardware by interacting with the operating system registry through a custom protocol; it dynamically loads the driver and API interface matched by the configuration file using a local plugin, making it compatible with multiple scanning devices and reducing the complexity of hardware adaptation and maintenance; it converts raw data into standardized data and constructs an atomic transactional data processing pipeline to ensure the integrity and traceability of cryopreservation tube information; finally, it dynamically parses and renders a visual interface based on a web client to achieve real-time mapping of the cryopreservation tube layout, improving operational intuitiveness, sample search efficiency, and user experience.

[0017] Other features and advantages of the invention will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the invention. The objects and other advantages of the invention are realized and obtained in accordance with the structures particularly pointed out in the description, claims and drawings.

[0018] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0019] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0020] Figure 1 A schematic diagram of the scanning device control process management method based on a custom protocol provided in an embodiment of the present invention; Figure 2 A schematic diagram of the structure of a scanning device control process management device based on a custom protocol provided in an embodiment of the present invention; Figure 3 This is a schematic diagram of the electronic device structure provided in an embodiment of the present invention.

[0021] Figure label: 10 - Construction module, 20 - Parsing module, 30 - Acquisition module, 40 - Conversion module, 50 - Display module; 130 - Processor, 131 - Memory, 132 - Bus, 133 - Communication interface. Detailed Implementation

[0022] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0023] To facilitate understanding of this embodiment, the technical terms used in this application will be briefly introduced below.

[0024] Cryopreservation tubes are containers specifically designed for the cryopreservation of biological samples, commonly used in medical and biological research and biobanks. These tubes are designed to maintain the stability and integrity of samples at extremely low temperatures, such as -80°C or lower. Cryopreservation tubes can store a wide variety of biological materials, including but not limited to cells, tissues, blood, DNA, RNA, and other biomolecules, and are an indispensable tool in modern biomedical research and applications.

[0025] After introducing the technical terms used in this application, the application scenarios and design concepts of the embodiments of this application will be briefly described below.

[0026] When a scanner reads a barcode or QR code on a cryopreservation tube, if the corresponding webpage operation cannot be triggered directly, data entry efficiency will be low. Furthermore, compatibility issues between different systems and between the scanning device and different software systems also complicate the process and increase the difficulty of operation for users.

[0027] Based on this, this application provides a scanning device control process management method based on a custom protocol.

[0028] Example 1 This application provides a scanning device control process management method based on a custom protocol, combined with Figure 1 As shown, the method includes: S110, in response to a scan command trigger event, constructs a custom protocol request containing user credentials to invoke the custom protocol through the operating system registry.

[0029] The S120 starts a local plugin process using a custom protocol, parses the device identifier in the preset configuration file, and dynamically loads the matching scanned device driver and API interface.

[0030] S130 controls the physical scanning device to perform scanning operations through the loaded scanning device driver, and obtains raw data containing the barcode and location information of the cryopreservation tube.

[0031] S140 converts the raw data into standardized data that includes barcode and location coordinate fields.

[0032] S150, The standardized data is dynamically parsed on the Web client and a visualization interface of the cryopreservation tube location is rendered.

[0033] This solution establishes a secure communication bridge between the web environment and local hardware at the operating system level by constructing a custom protocol request containing user credentials and calling the operating system registry. This effectively isolates browser sandbox restrictions and verifies the legitimacy of operations. Furthermore, by dynamically loading drivers and API interfaces matching the configuration file through a local plugin, compatibility with multiple scanning device models can be achieved simply by extending the configuration file, significantly reducing the complexity of hardware adaptation and system maintenance. Next, after the driver controls the device to acquire raw data, it converts it into standardized data, constructing an atomic transactional data processing pipeline to ensure the integrity and traceability of cryopreservation tube barcodes and location information. Finally, based on the web client, the standardized data is dynamically parsed and a visual interface is rendered, achieving precise mapping of the cryopreservation tube storage layout. This improves operational intuitiveness, sample retrieval efficiency, and user experience. In addition, all operations in this application that isolate browser sandbox restrictions are carried out in compliance with laws and regulations.

[0034] The scanning command can originate from a web interface interaction triggered by the operator clicking the scan button in the browser's database management module, or from a remote command received from a mobile terminal via a wireless network protocol. Both methods can effectively drive the scanning device to perform corresponding operations, enabling flexible and diverse task triggering methods. In practical applications, the appropriate method can be selected based on specific circumstances; this is merely an example and not a limitation.

[0035] In conjunction with the first aspect, step S110 involves constructing a custom protocol request containing user credentials, specifically including: Construct an initial custom protocol request based on the protocol parameter construction rules.

[0036] Embed encrypted user credentials in the protocol header of a custom protocol request.

[0037] By registering the "scanner-plugin: / / " protocol in the operating system registry, a channel is established for triggering local operations from the web client. When the browser initiates a call to this protocol, the operating system launches the specified local plugin process to handle the request, thereby enabling cross-environment communication.

[0038] When constructing the initial custom protocol request, embed necessary information, such as user credentials, into the request to enable authentication and ensure that the local plugin only responds to the operation instructions of legitimate users.

[0039] In this way, the operating system registry configuration provides the protocol call path, while the introduction of user credentials in the protocol request endows the request itself with security and identifiability. This ensures that the entire process can be correctly routed and pass permission verification to prevent unauthorized access or accidental triggering. It guarantees that only authorized users can trigger subsequent operations. Simultaneously, by carrying device identifiers and operation type parameters in the protocol request, step S120 executes the local plugin process to accurately call the corresponding driver and API interface, achieving a secure and efficient scan task startup process.

[0040] Understandably, prior to step S120, the following steps are also included: S1201, Receive protocol call request.

[0041] S1202, parse the protocol call request and verify the validity of the instruction parameters carried in the protocol call request.

[0042] S1203, if effective, launch the local plugin to load the matching scanning device driver and API interface.

[0043] S1204, if invalid, returns a message indicating an error in the instruction parameters.

[0044] Understandably, the process begins by receiving a custom protocol request ("scanner-plugin: / / ") triggered by the web client or a client application. This request contains user credentials, device identification, and operation instructions. Next, the system parses the parameters in the protocol request, including but not limited to the encryption token (user credentials), device ID, and operation type, verifying the validity of the user's identity, the correctness of the parameter format, and the matching of permissions to ensure the request source is legitimate and trustworthy. If verification passes, the corresponding local plugin process is started. At this point, the plugin further loads the driver and API interface matching the target device, preparing to execute specific operations (such as starting a scanning task). If verification fails, or parameters are missing or incorrectly formatted, subsequent operations are not executed, and a clear error message is returned to the calling client, such as "invalid token," "device not found," or "operation not supported," to facilitate troubleshooting.

[0045] This constitutes a security control mechanism from receiving the protocol request to processing it, ensuring that only verified and correctly structured requests can proceed to the subsequent execution stage, thereby improving the overall security and stability of the system. In conjunction with the first aspect, step S130, which controls the physical scanning device to perform scanning operations by loading the scanning device driver, specifically includes: Based on the device model code in the configuration file corresponding to the scanned device driver, load the corresponding dynamic link library file from the preset driver library.

[0046] Before performing the scanning operation, the configuration file (such as XML, JSON, etc.) is read first to extract the model code of the current target scanning device (e.g., manufacturer + model, such as Scanner_A100). Then, based on this device model code, the corresponding driver information (e.g., dynamic link library name, driver path, API interface specification, etc.) is searched in the local preset driver configuration table or mapping relationship.

[0047] Subsequently, based on the device model code parsed from the configuration file, the system locates the matching driver and loads its dynamic link library into the memory space of the current process. This "on-demand loading" method improves the system's flexibility and scalability, supporting later adaptation to new devices by updating the driver library. Each driver typically provides a set of standard API interfaces. After loading the driver, the system further loads the wrapper libraries for these API interfaces (which may be C / C++ header files, Java JAR files, .NET DLLs, etc.).

[0048] After loading the driver and API interface encapsulation libraries, the system calls the initialization function provided by the driver to configure necessary parameters for the device (such as resolution, scan area, color mode, etc.). Then, it calls commands such as "Start Scan," and the driver translates the commands into specific protocols that the device can recognize (such as SCSI, TWAIN, USB protocols, etc.), triggering the physical scan action.

[0049] After scanning is complete, the driver is responsible for receiving the raw data stream returned by the physical scanning device. In this embodiment, the physical scanning device is used to scan the barcode of the cryopreservation tube, and the corresponding data stream is raw data containing the cryopreservation tube barcode and location information.

[0050] After scanning, the original image data or the text content recognized by OCR is standardized, such as unifying the resolution, converting the format (e.g., JPEG / PNG), and extracting structured metadata (e.g., scanning time, device number, user ID, etc.). In this embodiment, it is uniformly converted into JSON format.

[0051] It is understandable that these standardized data and related information are stored in a backend database (relational databases such as MySQL and PostgreSQL, or document databases such as MongoDB) to facilitate subsequent querying, archiving, and analysis.

[0052] In conjunction with the first aspect, after step S140, the following also includes: S141, responding to a timed polling trigger event, monitors the change status of scan tasks in the database.

[0053] Among them, "timed polling trigger event" refers to the front end (web client) automatically sending HTTP requests to the back end at a set time interval (e.g., once every 2 seconds). It can be understood that this time interval can be a fixed value or dynamically adjusted according to system load or task status, and is not limited here.

[0054] Upon receiving a polling request, the system queries the database records related to the scanning task. Typically, the database contains a field (such as status) indicating the task's current status (e.g., in progress, completed, failed, etc.). If a change in the task status is detected, it is marked as "status updated." This ensures that the front-end can periodically obtain the latest status, preventing interface display lag.

[0055] S142, if a state update is detected, the state change information is sent back to the Web client via a WebSocket connection or a timed polling connection to update the display interface.

[0056] After the backend reads the task status from the database, it compares it with the status previously returned to the frontend. If they are different, it means that a status change has occurred; if they are the same, it means that no status change has occurred.

[0057] If a WebSocket connection (full-duplex communication) is established between the front-end and back-end, the back-end can proactively push state change information without waiting for the next polling, offering strong real-time performance and adapting well to scenarios sensitive to state updates. If no WebSocket connection is established, the traditional HTTP short connection method is used for state retrieval, with the front-end periodically initiating requests and the back-end returning the latest state information in each request. This embodiment provides a choice between two communication mechanisms, balancing real-time performance and compatibility, and enhancing the system's flexibility and robustness.

[0058] After receiving the status change data, the web client typically transmits structured data in JSON format. The front-end parses this data and updates the task status indicators on the interface (such as progress bars, status labels, etc.) to ensure that users always see the accurate task execution status, thereby improving user experience and interaction efficiency.

[0059] In conjunction with the first aspect, step S142 also includes: When new scanned data is written to the database, the WebSocket server is proactively triggered to broadcast a data update event to subscribed web clients.

[0060] Monitoring changes in the database utilizes the publish / subscribe mechanism of the WebSocket protocol, pushing updated information to all front-end user interfaces that have subscribed to the data update event. This allows multiple clients to receive data updates simultaneously, achieving real-time performance, reducing the latency associated with traditional polling methods, and thus improving system responsiveness and user experience.

[0061] In conjunction with the first aspect, step S130 obtains raw data containing the cryopreservation tube barcode and location information, specifically including: The barcode of the cryopreservation tube is identified by the identification device of the physical scanning equipment, and the physical location of the cryopreservation tube is mapped into two-dimensional coordinate system data by the positioning sensor of the physical scanning equipment.

[0062] This method can not only accurately record the specific location of each cryovial, but also ensure synchronous information positioning in the software system, thereby improving the efficiency of biological sample storage and management.

[0063] In conjunction with the first aspect, step S150 also includes: S151, parse the standardized data to obtain the location coordinate data of the cryopreservation tube.

[0064] S152, based on a preset mapping relationship, dynamically marks the status of cryopreservation tubes in a gridded interface according to location coordinate data.

[0065] After the local plugin is launched by building a custom protocol based on steps S110-S140 to drive the physical scanning device to scan the cryovials, the raw data obtained from the scan is standardized and fed back to the web client. The web client parses the standardized data and reads the location coordinate data from the relevant information of the cryovial. Subsequently, based on the pre-stored correspondence between the actual physical location of the cryovial and the virtual location of the gridded interface, the status of each cryovial is accurately displayed on the interface through this mapping, which helps to improve the visualization and operational efficiency of cryovial management.

[0066] Secondly, embodiments of this application also provide a scanning device control process management device based on a custom protocol, combined with Figure 2 As shown, the device includes: a construction module 10, a parsing module 20, an acquisition module 30, a conversion module 40, and a display module 50.

[0067] Module 10 is used to construct a custom protocol request containing user credentials in response to a scan command trigger event, so as to invoke the custom protocol through the operating system registry.

[0068] The parsing module 20 is used to start a local plugin process by a custom protocol, parse the device identifier in the preset configuration file, and dynamically load the matching scan device driver and API interface.

[0069] The acquisition module 30 is used to control the physical scanning device to perform scanning operations through the loaded scanning device driver, and to acquire raw data containing the barcode and location information of the cryopreservation tube.

[0070] The conversion module 40 is used to convert the raw data into standardized data that includes barcode fields and location coordinate fields.

[0071] Display module 50 is used to dynamically parse standardized data and render a visualization interface of cryopreservation tube location on the web client.

[0072] In conjunction with the second aspect, the construction module 10 includes: a request construction module and an encryption module.

[0073] The request building module is used to build an initial custom protocol request based on the protocol parameter building rules.

[0074] The encryption module is used to embed encrypted user credentials in the protocol header of a custom protocol request.

[0075] In conjunction with the second aspect, module 30 includes: loading the module.

[0076] The loading module is used to load the corresponding dynamic link library file from the preset driver library according to the device model code in the configuration file.

[0077] In conjunction with the second aspect, the conversion module 40 includes a monitoring module and a change module.

[0078] The monitoring module is used to monitor the change status of scanning tasks in the database in response to timed polling trigger events.

[0079] The change module is used to send the state change information back to the web client via a WebSocket connection or a timed polling connection when a state update is detected, so as to update the display interface.

[0080] In conjunction with the second aspect, the change module includes: the active triggering module.

[0081] The active trigger module is used to actively trigger the WebSocket server to broadcast a data update event to subscribed Web clients when new scan data is written to the database.

[0082] In conjunction with the second aspect, the acquisition module 30 includes: a mapping module.

[0083] The mapping module is used to identify the barcode of the cryopreservation tube through the identification device of the physical scanning device, and to map the physical position of the cryopreservation tube into two-dimensional coordinate system data through the positioning sensor of the physical scanning device.

[0084] In conjunction with the second aspect, the display module 50 also includes a dynamic marking module.

[0085] The dynamic marking module is used to dynamically mark the status of cryopreservation tubes in the gridded interface based on location coordinate data.

[0086] Thirdly, embodiments of this application provide an electronic device, combined with Figure 3 As shown, the electronic device includes a memory 131 and a processor 130. The memory 131 stores a computer program, and the processor 130 runs the computer program to make the electronic device perform the above-described method.

[0087] Furthermore, combined Figure 3 The electronic device shown also includes a bus 132 and a communication interface 133, with the processor 130, the communication interface 133 and the memory 131 connected via the bus 132.

[0088] The memory 131 may include high-speed random access memory (RAM) and may also include non-volatile memory, such as at least one disk storage device. Communication between this system network element and at least one other network element is achieved through at least one communication interface 133 (which can be wired or wireless), such as the Internet, wide area network, local area network, metropolitan area network, etc. The bus 132 may be an ISA bus, PCI bus, or EISA bus, etc. The bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 3 The symbol is represented by a single double-headed arrow, but this does not mean that there is only one bus or one type of bus.

[0089] Processor 130 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method can be completed by the integrated logic circuitry in the hardware of processor 130 or by instructions in software form. Processor 130 may be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this invention. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this invention can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software module can reside in a mature storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory 131, and processor 130 reads the information in memory 131 and, in conjunction with its hardware, completes the steps of the method described in the foregoing embodiments.

[0090] Fourthly, embodiments of this application provide a storage medium storing computer program instructions, which are read and executed by a processor to perform the above-described method.

[0091] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the system and apparatus described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0092] Furthermore, in the description of the embodiments of the present invention, unless otherwise explicitly specified and limited, the terms "installation," "connection," and "linking" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection of two components. Those skilled in the art can understand the specific meaning of the above terms in the present invention based on the specific circumstances.

[0093] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, essentially, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0094] In the description of this invention, it should be noted that the terms "center," "upper," "lower," "left," "right," "vertical," "horizontal," "inner," and "outer," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are used only for the convenience of describing the invention and for simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on the invention. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and should not be construed as indicating or implying relative importance.

[0095] Finally, it should be noted that the above embodiments are merely specific implementations of the present invention, used to illustrate the technical solutions of the present invention, and not to limit it. The scope of protection of the present invention is not limited thereto. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments within the technical scope disclosed in the present invention, or make equivalent substitutions for some of the technical features; and these modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be covered within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for managing the control flow of a scanning device based on a custom protocol, characterized in that, The method includes: In response to a scan command trigger event, a custom protocol request containing user credentials is constructed to invoke the custom protocol via the operating system registry; The local plugin process is started by the custom protocol, the device identifier in the preset configuration file is parsed, and the matching scanning device driver and API interface are dynamically loaded. The loaded scanning device driver controls the physical scanning device to perform scanning operations and obtain raw data containing the barcode and location information of the cryopreservation tube; Convert the raw data into standardized data that includes barcode and location coordinate fields; The standardized data is dynamically parsed on the web client, and a visualization interface of the cryopreservation tube location is rendered.

2. The method according to claim 1, characterized in that, The steps for constructing a custom protocol request containing user credentials include: Construct an initial custom protocol request based on the protocol parameter construction rules; An encrypted user credential is embedded in the protocol header of the custom protocol request.

3. The method according to claim 1, characterized in that, The steps of controlling the physical scanning device to perform scanning operations by loading the scanning device driver include: Based on the device model code in the configuration file, load the corresponding dynamic link library file from the preset driver library.

4. The method according to claim 1, characterized in that, After converting the raw data into standardized data that includes barcode and location coordinate fields, the process also includes: In response to timed polling events, monitor the change status of scanning tasks in the database; If a status update is detected, the status change information is sent back to the web client via a WebSocket connection or a timed polling connection to update the display interface.

5. The method according to claim 4, characterized in that, If a state update is detected, the step of sending the state change information back to the web client via a WebSocket connection or a timed polling connection includes: When new scanned data is written to the database, the WebSocket server is proactively triggered to broadcast a data update event to subscribed web clients.

6. The method according to claim 1, characterized in that, The steps for obtaining raw data containing cryopreservation tube barcodes and location information include: The barcode of the cryopreservation tube is identified by the identification device of the physical scanning equipment, and the physical position of the cryopreservation tube is mapped into two-dimensional coordinate system data by the positioning sensor of the physical scanning equipment.

7. The method according to claim 1, characterized in that, The steps of dynamically parsing JSON data and rendering a visualization interface of cryopreservation location on a web client also include: The status of cryopreservation tubes is dynamically marked in the gridded interface based on location coordinate data.

8. A scanning device control process management device based on a custom protocol, characterized in that, The device includes: A building module is used to construct a custom protocol request containing user credentials in response to a scan command trigger event, so as to invoke the custom protocol through the operating system registry; The parsing module is used to start a local plugin process by the custom protocol, parse the device identifier in the preset configuration file, and dynamically load the matching scanned device driver and API interface. The acquisition module is used to control the physical scanning device to perform scanning operations through the loaded scanning device driver to acquire raw data containing the cryopreservation tube barcode and location information; The conversion module is used to convert raw data into standardized data that includes barcode fields and location coordinate fields; The display module is used to dynamically parse the standardized data and render a visualization interface of the cryopreservation tube location on the web client.

9. An electronic device, characterized in that, The electronic device includes a memory and a processor, the memory storing a computer program and the processor running the computer program to cause the electronic device to perform the method of any one of claims 1 to 7.

10. A storage medium, characterized in that, The storage medium stores computer program instructions, which, when read and executed by a processor, perform the method described in any one of claims 1 to 7.

Images