Equipment management method and related device

Abstract

The invention provides a device management method and a related device, and the method comprises the steps that a background server obtains target two-dimensional code information sent by a terminal device, and the target two-dimensional code information is information obtained by scanning a plurality of target two-dimensional codes through a scanning interface of the terminal device by a user account; the plurality of target two-dimensional codes are arranged on the plurality of target devices in a one-to-one correspondence manner; the background server determines use times corresponding to the multiple target devices according to the target two-dimensional code information; if the use times corresponding to the multiple target devices respectively meet the use safety requirement, the background server generates use verification codes used for using the multiple target devices and sends the use verification codes to the terminal device; if the number of use times corresponding to at least one target device in the multiple target devices does not meet the use safety requirement, the background server does not generate the use verification code. Through the method, the management cost is reduced, and the management efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of equipment, and more specifically, to an equipment management method and related apparatus. Background Technology

[0002] In related technologies, passive surgical instruments typically require manual operation by the surgeon. For some complex procedures or instruments, the high level of skill and clinical experience required for operation, coupled with a long learning curve, limits the clinical application of these instruments. Surgical assistance systems, however, can remotely operate the actuators to drive passive surgical instruments, freeing surgeons from manual operation, lowering the surgical threshold, and protecting them from radiation exposure—making it a highly advanced surgical method.

[0003] During surgery using a surgical assistance system, the equipment used by the system needs to be managed. In related technologies, the equipment is usually managed manually, which results in high management costs and low management efficiency. Summary of the Invention

[0004] This application provides at least one device management method and related apparatus. Through the interaction between the terminal device and the backend server, it can ensure that the user obtains the verification code when the number of times the device is used meets the security requirements. In other words, it can realize the automatic management of multiple devices in the surgical assistance system, reduce management costs and improve management efficiency.

[0005] In a first aspect, this application provides a device management method, including:

[0006] The backend server obtains the target QR code information sent by the terminal device. The target QR code information is obtained by the user account scanning multiple target QR codes through the scanning interface of the terminal device. The multiple target QR codes are set one-to-one on multiple target devices.

[0007] The backend server determines the number of uses for each of the multiple target devices based on the target QR code information.

[0008] If the number of uses for each of the multiple target devices meets the security requirements, the backend server generates a verification code for using the multiple target devices and sends the verification code to the terminal device.

[0009] If the number of uses for at least one of the target devices does not meet the security requirements, the backend server will not generate the usage verification code.

[0010] Secondly, this application also provides a device management method, including:

[0011] In response to the user account scanning multiple target QR codes on the terminal device's scanning interface, the terminal device obtains the target QR code information corresponding to the multiple target QR codes, and the multiple target QR codes are set on the multiple target devices one by one.

[0012] The terminal device sends the target QR code information to the backend server;

[0013] If the number of uses for each of the multiple target devices determined by the backend server based on the target QR code information meets the usage security requirements, the terminal device receives the usage verification code generated and sent by the backend server for using the multiple target devices.

[0014] Thirdly, this application also provides an equipment management device, comprising:

[0015] The acquisition unit is used by the backend server to acquire the target QR code information sent by the terminal device. The target QR code information is obtained by the user account scanning multiple target QR codes through the scanning interface of the terminal device. The multiple target QR codes are set one-to-one on the multiple target devices.

[0016] The determination unit is used by the backend server to determine the number of times each of the multiple target devices is used, based on the target QR code information.

[0017] The generation unit is used to generate a usage verification code for using multiple target devices if the number of uses for each target device meets the usage security requirements, and then send the usage verification code to the terminal device; if the number of uses for at least one of the target devices does not meet the usage security requirements, the backend server does not generate a usage verification code.

[0018] Fourthly, this application also provides an equipment management device, comprising:

[0019] The obtaining unit is used to respond to the scanning operation of the user account to scan multiple target QR codes on the scanning interface of the terminal device. The terminal device obtains the target QR code information corresponding to the multiple target QR codes, and the multiple target QR codes are set on the multiple target devices one by one.

[0020] The sending unit is used by the terminal device to send the target QR code information to the backend server.

[0021] The receiving unit is used to receive a usage verification code generated and sent by the backend server for using multiple target devices if the number of uses corresponding to the multiple target devices determined by the backend server based on the target QR code information all meet the usage security requirements.

[0022] Fifthly, embodiments of this application provide a device management system, which includes a backend server and a terminal device. The backend server is used to execute the methods described above, and the terminal device is used to execute the methods described above.

[0023] Sixthly, this application also provides an electronic device, including: a processor, a memory, and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor communicates with the memory via the bus, and the machine-readable instructions, when executed by the processor, perform the methods described above.

[0024] In a seventh aspect, this application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, performs the methods described in the foregoing aspects.

[0025] Eighthly, this application also provides a computer program product, including a computer program that, when run by a processor, executes the methods described above.

[0026] In summary, this application provides a device management method and related apparatus, comprising: a backend server acquiring target QR code information sent by a terminal device, wherein the target QR code information is obtained by a user account scanning multiple target QR codes through the scanning interface of the terminal device, and the multiple target QR codes are set one-to-one on multiple target devices; the backend server determining the number of times each of the multiple target devices is used based on the target QR code information; if the number of times each of the multiple target devices is used meets the security requirements, the backend server generates a usage verification code for using the multiple target devices and sends the usage verification code to the terminal device; if the number of times at least one of the multiple target devices is used does not meet the security requirements, the backend server does not generate a usage verification code. Through the above method, the interaction between the terminal device and the backend server ensures that the user obtains the usage verification code when the number of times each of the multiple devices is used meets the security requirements, thus enabling automatic management of multiple devices in a surgical assistance system, reducing management costs, and improving management efficiency.

[0027] Other advantages of this application will be explained in more detail in conjunction with the following description and figures.

[0028] It should be understood that the above description is merely an overview of the technical solution of this application, so as to enable a general understanding of the technical means of this application and to implement it in accordance with the contents of the specification. In order to make the above and other objects, features and advantages of this application more apparent and understandable, specific embodiments of this application are illustrated below. Attached Figure Description

[0029] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly described below. The accompanying drawings are incorporated in and constitute a part of this specification. These drawings illustrate embodiments conforming to this application and are used together with the specification to explain the technical solutions of this application. It should be understood that the drawings only illustrate certain embodiments of this application and should not be considered as a limitation on the scope of protection. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort. Furthermore, the same reference numerals denote the same components throughout the drawings. In the drawings:

[0030] Figure 1 A flowchart illustrating a device management method provided in this application embodiment;

[0031] Figure 2 A device structure diagram of an equipment management device provided in an embodiment of this application;

[0032] Figure 3 A device structure diagram of another device management device provided in the embodiments of this application;

[0033] Figure 4 This is a system architecture diagram of an equipment management system provided in an embodiment of this application. Detailed Implementation

[0034] Exemplary embodiments of this application will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of this application are shown in the drawings, it should be understood that this application can be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided to enable a more thorough understanding of this application and to fully convey the scope of this application to those skilled in the art.

[0035] In the description of embodiments of this application, it should be understood that terms such as “comprising” or “having” are intended to indicate the presence of the disclosed features, figures, steps, behaviors, components, portions or combinations thereof in this specification, and do not exclude the possibility of the presence of one or more other features, figures, steps, behaviors, components, portions or combinations thereof.

[0036] Unless otherwise stated, " / " means "or". For example, A / B can mean A or B. In this article, "and / or" is merely a way of describing the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A alone, A and B at the same time, and B alone.

[0037] The terms "first," "second," etc., are used only for ease of description to distinguish identical or similar technical features and should not be construed as indicating or implying the relative importance or number of these technical features. Therefore, a feature defined by "first," "second," etc., may explicitly or implicitly include one or more of that feature. In the description of embodiments of this application, unless otherwise stated, the term "multiple" means two or more.

[0038] During surgery using a surgical assistance system, the equipment used by the system needs to be managed. In related technologies, the equipment is usually managed manually, which results in high management costs and low management efficiency.

[0039] In view of this, this application provides a device management method and related apparatus. Through the interaction between the terminal device and the back-end server, it can ensure that the user obtains the verification code when the number of times the device is used meets the security requirements. In other words, it can realize the automatic management of multiple devices in the surgical assistance system, reduce management costs and improve management efficiency.

[0040] The device management method provided in this application can be implemented using a computer device, which can be a terminal device or a server. The server can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services. Terminal devices include, but are not limited to, mobile phones, computers, intelligent voice interaction devices, smart home appliances, vehicle terminals, and aircraft. Terminal devices and servers can be directly or indirectly connected via wired or wireless communication, and this application does not impose any limitations on this connection.

[0041] It is understood that in the specific embodiments of this application, data related to user information ****** is involved. When the above embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0042] The device management method provided in this application will be described below through method embodiments, such as... Figure 1 As shown, Figure 1 This application provides a flowchart of a device management method, illustrated using a computer device as the terminal device and a backend server. The method includes:

[0043] S101, In response to the user account scanning multiple target QR codes on the terminal device's scanning interface, the terminal device obtains the target QR code information corresponding to the multiple target QR codes.

[0044] A target QR code is a QR code set on a target device, which is a device that needs to be managed during the corresponding surgical procedure through a surgical assistance system.

[0045] Since multiple target devices are usually required to complete the corresponding surgery through the surgical assistance system, this application will use multiple target QR codes. Each target QR code is set on a corresponding target device. For example, when the surgical assistance system requires three target devices to complete the surgery, each of the three target devices will be set with a corresponding target QR code.

[0046] In this application, a user account refers to the account corresponding to a user who needs to obtain and use verification codes to access multiple target devices; a terminal device refers to a device with scanning capabilities; a scanning interface refers to the interface on the terminal device used for scanning QR codes; and a scanning operation refers to the operation of a user account scanning multiple target QR codes on the scanning interface of the terminal device. In the actual application of this application, the scanning interface can be configured with multiple scanning components corresponding to multiple target devices, or it can be configured with only one scanning component for multiple target devices; no limitation is made here.

[0047] When multiple target QR codes are set one-to-one on multiple target devices, in response to the user account scanning the multiple target QR codes on the terminal device's scanning interface, the terminal device can obtain the target QR code information corresponding to the multiple target QR codes. The target QR code information refers to the information obtained for the multiple target devices by scanning the multiple target QR codes.

[0048] S102. The terminal device sends the target QR code information to the backend server.

[0049] In S101, after the terminal device obtains the target QR code information corresponding to multiple target QR codes, the terminal device can send the target QR code information to the backend server. The backend server refers to the server that can process the target QR code information to generate and send the verification code, so that the backend server can perform relevant processing on the target QR code to obtain the corresponding verification code.

[0050] S103. The backend server obtains the target QR code information sent by the terminal device.

[0051] In S102, after the terminal device sends the target QR code information to the backend server, the backend server can obtain the target QR code information sent by the terminal device.

[0052] S104. The backend server determines the number of times each of the multiple target devices is used based on the target QR code information.

[0053] After the backend server in S103 obtains the target QR code information, since the target QR code information refers to the information obtained by scanning multiple target QR codes for multiple target devices, the backend server can determine the number of times each target device is used based on the target QR code information. The number of times a target device has been used refers to the number of times the target device has been used.

[0054] S105. If the number of uses corresponding to multiple target devices all meet the usage security requirements, the backend server generates a usage verification code for using multiple target devices and sends the usage verification code to the terminal device.

[0055] If the number of uses for any of the multiple target devices does not meet the security requirements, the backend server will not generate a verification code.

[0056] After determining the number of times each of the multiple target devices is used in S104, in order to ensure safe use, it is necessary to judge the number of times each of the multiple target devices is used.

[0057] If the usage counts for each of the multiple target devices meet the usage security requirements, where the usage security requirement means that the usage count of the corresponding target device does not exceed the maximum usage count, the backend server can generate a usage verification code for using the multiple target devices. The usage verification code can include one or more of numbers, uppercase and lowercase letters, and symbols, without any limitation, and send the usage verification code to the terminal device so that the relevant user can use the multiple target devices by using the verification code.

[0058] If the number of uses of at least one of the target devices does not meet the security requirements, it means that at least one of the target devices has a number of uses greater than the maximum number of uses. In this case, the backend server may not generate a verification code, thereby preventing the use of the target device that does not meet the security requirements and ensuring the security of the target device.

[0059] It should be noted that in the actual application of this application, the corresponding safety requirements for different target devices can be the same or different. For example, for target device A, the safety requirement for target device A can be that the number of times target device A is used is no more than 10 times. At the same time, for target device B, the safety requirement for target device B can also be that the number of times target device B is used is no more than 10 times.

[0060] S106. The terminal device receives the usage verification code sent by the backend server.

[0061] After the backend server generates the verification code in S105, the terminal device can receive the verification code sent by the backend server.

[0062] In one possible implementation, the backend server in S104 determines the number of uses for each of the multiple target devices based on the target QR code information, including:

[0063] The backend server determines the device identifier corresponding to each of the multiple target devices based on the target QR code information;

[0064] The backend server determines the number of times each target device is used based on the device identifiers corresponding to each target device and the pre-stored correspondence between the device identifiers and the number of times each device is used.

[0065] Specifically, device identification can be used to identify the corresponding device. For example, device identification can be a unique device identification (UDI) for medical devices.

[0066] The backend server can first determine the device identifiers corresponding to multiple target devices based on the target QR code information. In this application, in order to reliably manage the target devices, each target device has a corresponding device identifier.

[0067] After determining the device identifiers corresponding to multiple target devices, the backend server can directly determine the usage counts for each target device based on the device identifiers corresponding to the multiple target devices and the pre-stored correspondence between the device identifiers corresponding to the multiple devices and the usage counts.

[0068] In one possible implementation, in order to manage the device, in response to a device addition operation by an administrator account or manufacturer account on the device management interface of the backend server, the backend server determines the device identifier and device type information of the device to be added, and stores the device identifier and device type information of the device to be added together. The device type information includes the device type and the corresponding security requirements for the device type.

[0069] Specifically, the device management interface refers to the interface displayed on the backend server used for managing devices.

[0070] The administrator account refers to the account that can access all interfaces on the backend server, and the manufacturer account refers to the account that can access the device management interface on the backend server. It should be noted that the aforementioned user account refers to the account that can access the scanning interface of the terminal device. That is, in this application, the administrator account, manufacturer account and user account have different permissions.

[0071] Since the security requirements for devices of different types may vary, in this embodiment, in response to the device addition operation of the administrator account or manufacturer account on the device management interface of the backend server, the backend server can determine the device identifier and device type information of the device to be added. The device type information may include the device type and the corresponding security requirements.

[0072] After determining the device identifier and device type information of the device to be added, the backend server can associate and store the device identifier and device type information of the device to be added. Since the device type information includes the usage security requirements corresponding to the device type, the backend server stores the usage security requirements of the device during the process of adding the device.

[0073] In one possible implementation, in order to enable device type management, in response to the administrator account's device type management interface on the backend server, the backend server determines the device type information and device identification rules of the device type to be processed, and stores the device type information and device identification rules of the device type to be processed together. The device identification rules include the generation rules of the device identifier.

[0074] Specifically, the device type management interface refers to the interface displayed on the backend server used to manage device types. The administrator account is the account that can access all interfaces on the backend server.

[0075] In order to enable device type management, in this embodiment, in response to the administrator account's device type management interface on the backend server, the backend server can determine the device type information and device identification rules of the device type to be processed. The device type information may include the device type and the corresponding security requirements, and the device identification rules may include the rules for generating the device identification.

[0076] After determining the device type information and device identification rules for the device type to be processed, the backend server can associate and store the device type information and device identification rules for the device type to be processed. Since the device type information includes the usage security requirements corresponding to the device type and the device identification rules include the generation rules of the device identification, the backend server manages the usage security requirements and device identification generation rules corresponding to different device types during the process of managing device types, thereby realizing differentiated management of devices of different device types.

[0077] In one possible implementation, in order to enable the creation of device identification rules, in response to the administrator account's device identification rule creation operation on the device identification rule interface of the backend server, the backend server creates the device identification rule corresponding to the device identification rule creation operation.

[0078] Specifically, the device identification rules interface refers to the interface displayed on the backend server used to manage device identification rules. The administrator account is the account that can access all interfaces on the backend server.

[0079] In response to the administrator account's device identification rule creation operation on the device identification rule interface of the backend server, the backend server can create the device identification rule corresponding to the device identification rule creation operation. For example, when the device identification is a UDI code, different device identification rules can specify which bits to extract from the UDI code.

[0080] In one possible implementation, in order to maintain the manufacturer information of the equipment, in response to the manufacturer management operation of the administrator account on the manufacturer management interface of the backend server, the backend server stores the manufacturer identifier in the device identifier as associated with the corresponding manufacturer.

[0081] Specifically, the manufacturer's management interface refers to the interface displayed on the backend server used to manage the equipment. The administrator account is the account that can access all interfaces on the backend server.

[0082] In response to the administrator account's manufacturer management operations on the manufacturer management interface of the backend server, the backend server can associate and store the manufacturer identifier in the device identifier with the corresponding manufacturer name. For example, when the device identifier is a UDI code, the backend server can associate and store the manufacturer identification code in the UDI code with the manufacturer name so that the manufacturer information can be correctly identified through the UDI code.

[0083] In one possible implementation, in order to better manage user accounts using the device, in response to the administrator account's use of verification code grouping operation on the backend server's verification code grouping interface, the backend server determines at least one verification code grouping and the user account corresponding to each verification code grouping, and stores each verification code grouping and its corresponding user account in the at least one verification code grouping.

[0084] Specifically, the CAPTCHA grouping interface refers to the interface displayed on the backend server used for creating and managing CAPTCHA groups. The administrator account is the account that can access all interfaces on the backend server.

[0085] In response to the administrator account's use of CAPTCHA grouping operations on the backend server's CAPTCHA grouping interface, the backend server can identify at least one CAPTCHA group and the user account corresponding to each CAPTCHA group, and associate and store each CAPTCHA group and its corresponding user account in the at least one CAPTCHA group. This means that CAPTCHA groups and their corresponding user accounts can be bound together to enable better management of user accounts on the device.

[0086] In one possible implementation, when the verification code group is bound to the corresponding user account, the backend server in S103 obtains the target QR code information sent by the terminal device, including:

[0087] The backend server obtains the target QR code information and user account information sent by the terminal. The user account information is the information corresponding to the user account logged in when scanning multiple target QR codes through the terminal's scanning interface.

[0088] The backend server in S105 generates usage verification codes for use with multiple target devices, including:

[0089] In response to the administrator account's operation of generating a verification code group for the verification code management interface of the backend server, the backend server determines the target verification code group corresponding to the user account information based on the user account information and the user accounts corresponding to multiple pre-stored verification code groups.

[0090] The backend server generates the verification code corresponding to the target group.

[0091] Specifically, when the verification code group is bound to the corresponding user account, the backend server can obtain not only the target QR code information sent by the terminal, but also the user account information. The user account information is the information of the user account that logged in when scanning multiple target QR codes through the terminal's scanning interface.

[0092] The CAPTCHA management interface refers to the interface displayed on the backend server used to manage the use of CAPTCHAs by group. An administrator account is an account that can access all interfaces on the backend server.

[0093] After the backend server determines the user account information, in response to the administrator account's operation of generating verification code groups for the verification code management interface on the backend server, the backend server can first determine the target verification code group corresponding to the user account information based on the user account information and the user accounts corresponding to multiple pre-stored verification code groups, and then generate the verification code corresponding to the target verification code group. In other words, the backend server can generate a verification code corresponding to the user account information.

[0094] In one possible implementation, in order to manage information related to user accounts obtaining and using verification codes, the method further includes the following after sending the verification code to the terminal device:

[0095] The backend server determines the associated information corresponding to the verification code and displays the associated information on the verification code usage record interface of the backend server. The associated information includes the time when the verification code was obtained and the corresponding multiple target devices.

[0096] Specifically, the verification code record interface refers to the interface displayed on the backend server that shows the associated information related to the use of verification codes.

[0097] After sending the verification code to the terminal device, the backend server can determine the associated information corresponding to the verification code. The associated information may include the time when the verification code was obtained and the corresponding multiple target devices. After determining the associated information of the verification code, the associated information corresponding to the verification code can be displayed on the verification code record interface of the backend server.

[0098] In one possible implementation, to ensure the security of device use, in response to user management operations performed by the administrator account on the user management interface of the backend server, the backend server will associate and store the authorized user account and authorized user information.

[0099] Specifically, the user management interface refers to the interface displayed on the backend server used to manage user accounts.

[0100] In response to user management operations performed by the administrator account on the user management interface of the backend server, the backend server can associate and store authorized user accounts and authorized user information to prevent unauthorized accounts from obtaining and using verification codes, thus ensuring the security of device use.

[0101] In one possible implementation, in response to a user account's login operation on the terminal device's login interface, the user account is confirmed to be logged in, and the terminal device's scanning interface is displayed to the user account.

[0102] Specifically, the login interface refers to the interface displayed on the terminal device for user account login. In this embodiment, the login method on the login interface can be a variety of login methods such as mobile phone number login or username and password login, and is not limited here.

[0103] In response to a user account's login operation on the terminal device's login interface, the terminal device can confirm the user account is logged in and display the terminal device's scanning interface to the user account.

[0104] In one possible implementation, for a surgical assistance system for treating mitral valve, multiple target devices may include a delivery catheter adapter, a guiding catheter adapter, and a cannula adapter. When multiple target devices include a delivery catheter adapter, a guiding catheter adapter, and a cannula adapter, the safety requirement for each adapter may be no more than 10 uses.

[0105] In summary, this application provides a device management method, comprising: a backend server acquiring target QR code information sent by a terminal device, wherein the target QR code information is obtained by a user account scanning multiple target QR codes through the scanning interface of the terminal device, and the multiple target QR codes are set one-to-one on multiple target devices; the backend server determining the usage count corresponding to each of the multiple target devices based on the target QR code information; if the usage count corresponding to each of the multiple target devices meets the usage security requirements, the backend server generates a usage verification code for using the multiple target devices and sends the usage verification code to the terminal device; if the usage count corresponding to at least one of the multiple target devices does not meet the usage security requirements, the backend server does not generate a usage verification code. Through the above method, the interaction between the terminal device and the backend server ensures that the user obtains the usage verification code when the usage count of multiple devices meets the usage security requirements, thus enabling automatic management of multiple devices in a surgical assistance system, reducing management costs, and improving management efficiency.

[0106] In the description of this specification, references to terms such as "some possible implementations," "some implementations," "example," "specific example," or "some examples" indicate that a specific feature, structure, material, or characteristic described in connection with that implementation or example is included in at least one implementation or example of this application, and the aforementioned terms do not necessarily refer to the same implementation or example. Furthermore, the described specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more implementations or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different implementations or examples described in this specification, as well as the features of different implementations or examples.

[0107] The method flowcharts for embodiments of this application describe certain operations as different steps performed in a certain order. Such flowcharts are illustrative and not restrictive. Some steps described herein may be grouped together and performed in a single operation, or some steps may be divided into multiple sub-steps, and some steps may be performed in an order different from that shown herein. The various steps shown in the flowcharts may be implemented in any way by any circuit structure and / or tangible mechanism (e.g., by software running on a computer device, hardware (e.g., logic functions implemented by a processor or chip), and / or any combination thereof).

[0108] Those skilled in the art will understand that in the methods described in the above specific embodiments, the order in which the steps are written does not imply a strict execution order, and the specific execution order of each step should be determined by its function and possible internal logic.

[0109] Based on the foregoing Figure 1 , Figure 2 This application provides a device structure diagram of a device management apparatus 200, which includes:

[0110] The acquisition unit 201 is used by the backend server to acquire the target QR code information sent by the terminal device. The target QR code information is the information obtained by the user account scanning multiple target QR codes through the scanning interface of the terminal device. The multiple target QR codes are set one-to-one on the multiple target devices.

[0111] The determining unit 202 is used by the backend server to determine the number of times each of the multiple target devices is used based on the target QR code information;

[0112] The generation unit 203 is configured to, if the number of uses corresponding to multiple target devices all meet the usage security requirements, generate a usage verification code for using multiple target devices and send the usage verification code to the terminal device; if the number of uses corresponding to at least one of the multiple target devices does not meet the usage security requirements, the backend server does not generate a usage verification code.

[0113] In one possible implementation, the determining unit 202 is used for:

[0114] The backend server determines the device identifiers corresponding to the multiple target devices based on the target QR code information.

[0115] The backend server determines the number of times each target device is used based on the device identifiers corresponding to each target device and the pre-stored correspondence between the device identifiers and the number of times each device is used.

[0116] In one possible implementation, the determining unit 202 is further configured to:

[0117] In response to a device addition operation performed by an administrator account or manufacturer account on the device management interface of the backend server, the backend server determines the device identifier and device type information of the device to be added, and stores the device identifier and device type information together. The device type information includes the device type and the corresponding usage security requirements.

[0118] In one possible implementation, the determining unit 202 is further configured to:

[0119] In response to the administrator account's device type management interface on the backend server, the backend server determines the device type information and device identification rules of the device type to be processed, and stores the device type information and device identification rules of the device type to be processed together. The device identification rules include the generation rules of the device identifier.

[0120] In one possible implementation, the device management device 200 further includes a creation unit for:

[0121] In response to the administrator account's device identification rule creation operation on the device identification rule interface of the backend server, the backend server creates the device identification rule corresponding to the device identification rule creation operation.

[0122] In one possible implementation, the device management device 200 further includes a storage unit for:

[0123] In response to the administrator account's manufacturer management operations on the manufacturer management interface of the backend server, the backend server will associate and store the manufacturer identifier in the device identifier with the corresponding manufacturer name.

[0124] In one possible implementation, the determining unit 202 is further configured to:

[0125] In response to the administrator account's use of CAPTCHA grouping on the backend server, the backend server determines at least one CAPTCHA group and the user account corresponding to each CAPTCHA group, and stores each CAPTCHA group and its corresponding user account in the at least one CAPTCHA group.

[0126] In one possible implementation, the acquisition unit 201 is used for:

[0127] The backend server obtains the target QR code information and user account information sent by the terminal. The user account information is the information corresponding to the user account logged in when scanning multiple target QR codes through the terminal's scanning interface.

[0128] Generation unit 203, used for

[0129] In response to the administrator account's operation of generating a verification code group for the verification code management interface of the backend server, the backend server determines the target verification code group corresponding to the user account information based on the user account information and the user accounts corresponding to multiple pre-stored verification code groups.

[0130] The backend server generates the verification code corresponding to the target group.

[0131] In one possible implementation, the determining unit 202 is further configured to:

[0132] After sending the verification code to the terminal device, the backend server determines the associated information corresponding to the verification code and displays the associated information on the verification code usage record interface of the backend server. The associated information includes the time when the verification code was obtained and the corresponding multiple target devices.

[0133] In one possible implementation, the storage unit is also used for:

[0134] In response to user management operations performed by the administrator account on the user management interface of the backend server, the backend server will associate and store the authorized user account and authorized user information.

[0135] In one possible implementation, the multiple target devices include a delivery conduit adapter, a guide tube adapter, and a cannula adapter.

[0136] It should be noted that the apparatus in the embodiments of this application can implement each process of the aforementioned method and achieve the same effect and function, which will not be elaborated here.

[0137] Based on the foregoing Figure 1 , Figure 3 This application provides another device management device structural diagram, the device management device 300 includes:

[0138] Unit 301 is used to respond to the scanning operation of the user account scanning multiple target QR codes on the scanning interface of the terminal device. The terminal device obtains the target QR code information corresponding to the multiple target QR codes, and the multiple target QR codes are set on the multiple target devices one by one.

[0139] Sending unit 302 is used for the terminal device to send target QR code information to the backend server;

[0140] The receiving unit 303 is used to receive a usage verification code generated and sent by the backend server for using multiple target devices if the number of uses corresponding to the multiple target devices determined by the backend server based on the target QR code information all meet the usage security requirements.

[0141] In one possible implementation, the device management device 300 further includes a determining unit for:

[0142] In response to a user account's login operation on the terminal device's login interface, the terminal device confirms the user account is logged in and displays the terminal device's scanning interface to the user account.

[0143] It should be noted that the apparatus in the embodiments of this application can implement each process of the aforementioned method and achieve the same effect and function, which will not be elaborated here.

[0144] In the foregoing Figure 1 Based on the corresponding embodiments, Figure 4 The present application provides a system architecture diagram of a device management system 400, which includes a backend server 401 and a terminal device 402. The backend server 401 is used to execute the method of the aforementioned method embodiment, and the terminal device 402 is used to execute the method of the aforementioned method embodiment.

[0145] Therefore, the backend server obtains the target QR code information sent by the terminal device. This target QR code information is obtained by the user account scanning multiple target QR codes through the terminal device's scanning interface. Each target QR code is uniquely set on a different target device. Based on the target QR code information, the backend server determines the number of times each target device can be used. If the number of uses for each target device meets the security requirements, the backend server generates a verification code for using the multiple target devices and sends it to the terminal device. If the number of uses for at least one target device does not meet the security requirements, the backend server does not generate a verification code. Through this method, the interaction between the terminal device and the backend server ensures that the user obtains a verification code only when the number of uses for multiple devices meets the security requirements. This enables automated management of multiple devices in the surgical assistance system, reducing management costs and improving management efficiency.

[0146] This application also provides an electronic device, including a processor, a memory, and a bus. The memory stores machine-readable instructions executable by the processor. When the electronic device is running, the processor communicates with the memory via the bus. When the machine-readable instructions are executed by the processor, the following processing is performed:

[0147] The backend server obtains the target QR code information sent by the terminal device. The target QR code information is obtained by the user account scanning multiple target QR codes through the scanning interface of the terminal device. The multiple target QR codes are set one-to-one on multiple target devices.

[0148] The backend server determines the number of uses for each of the multiple target devices based on the target QR code information.

[0149] If the number of uses for each of the multiple target devices meets the security requirements, the backend server generates a verification code for using the multiple target devices and sends the verification code to the terminal device.

[0150] If the number of uses for at least one of the target devices does not meet the security requirements, the backend server will not generate the usage verification code.

[0151] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the method provided in the above embodiments. The storage medium can be either volatile or non-volatile computer-readable storage.

[0152] This application also provides a computer program product, including a computer program, which carries program code. The instructions included in the program code can be used to execute the methods provided in the above embodiments. For details, please refer to the above method embodiments, which will not be repeated here.

[0153] The various embodiments in this application are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on its differences from other embodiments. In particular, the descriptions of the apparatus, device, and computer-readable storage medium embodiments are simplified because they are substantially similar to the method embodiments; relevant details can be found in the descriptions of the method embodiments.

[0154] The apparatus, device, and computer-readable storage medium provided in the embodiments of this application correspond one-to-one with the method. Therefore, the apparatus, device, and computer-readable storage medium also have similar beneficial technical effects as their corresponding methods. Since the beneficial technical effects of the method have been described in detail above, the beneficial technical effects of the apparatus, device, and computer-readable storage medium will not be repeated here.

[0155] While the spirit and principles of this application have been described above with reference to several specific embodiments, it should be understood that this application is not limited to the disclosed specific embodiments, and the division of aspects does not imply that features in these aspects cannot be combined. This application is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

Claims

1. A method for managing equipment, characterized in that, include: The backend server obtains target QR code information sent by the terminal device. The target QR code information is obtained by the user account scanning multiple target QR codes through the scanning interface of the terminal device. The multiple target QR codes are set one-to-one on multiple target devices. The backend server determines the number of times each of the multiple target devices is used based on the target QR code information. If the number of uses corresponding to the multiple target devices all meet the usage security requirements, the backend server generates a usage verification code for using the multiple target devices and sends the usage verification code to the terminal device. If the number of uses for at least one of the multiple target devices does not meet the security requirements, the backend server will not generate the usage verification code.

2. The method according to claim 1, characterized in that, The backend server determines the number of uses for each of the multiple target devices based on the target QR code information, including: The backend server determines the device identifiers corresponding to the multiple target devices based on the target QR code information. The backend server determines the number of times each of the multiple target devices is used based on the device identifiers corresponding to the multiple target devices and the pre-stored correspondence between the device identifiers and the number of times each of the multiple devices is used.

3. The method according to claim 2, characterized in that, The method further includes: In response to a device addition operation performed by an administrator account or manufacturer account on the device management interface of the backend server, the backend server determines the device identifier and device type information of the device to be added, and stores the device identifier and device type information of the device to be added together. The device type information includes the device type and the corresponding security requirements for the device type.

4. The method according to claim 3, characterized in that, The method further includes: In response to an administrator account's device type processing operation on the device type management interface of the backend server, the backend server determines the device type information and device identification rules of the device type to be processed, and stores the device type information and device identification rules of the device type to be processed in association. The device identification rules include the generation rules of the device identifier.

5. The method according to claim 4, characterized in that, The method further includes: In response to the administrator account's device identification rule creation operation on the device identification rule interface of the backend server, the backend server creates the device identification rule corresponding to the device identification rule creation operation.

6. The method according to claim 2, characterized in that, The method further includes: In response to the administrator account's manufacturer management operation on the manufacturer management interface of the backend server, the backend server associates and stores the manufacturer identifier in the device identifier with the corresponding manufacturer name.

7. The method according to claim 1, characterized in that, The method further includes: In response to an administrator account's use of a verification code group on the backend server's verification code group interface, the backend server determines at least one verification code group and a user account corresponding to each verification code group, and stores each verification code group and its corresponding user account in association.

8. The method according to claim 7, characterized in that, The backend server obtains the target QR code information sent by the terminal, including: The backend server obtains the target QR code information and user account information sent by the terminal. The user account information is the information corresponding to the user account logged in when scanning the multiple target QR codes through the scanning interface of the terminal. The backend server generates a usage verification code for using the multiple target devices, including: In response to the administrator account's operation of generating a verification code group for the verification code management interface of the backend server, the backend server determines the target verification code group corresponding to the user account information based on the user account information and the user accounts corresponding to multiple pre-stored verification code groups. The backend server generates the verification code corresponding to the target verification code group.

9. The method according to claim 1, characterized in that, After sending the usage verification code to the terminal device, the method further includes: The backend server determines the associated information corresponding to the verification code used, and displays the associated information corresponding to the verification code used on the verification code usage record interface of the backend server. The associated information includes the acquisition time of the verification code used and the corresponding multiple target devices.

10. The method according to claim 1, characterized in that, The method further includes: In response to user management operations performed by the administrator account on the user management interface of the backend server, the backend server will associate and store the authorized user account and authorized user information.

11. The method according to any one of claims 1-10, characterized in that, The plurality of target devices include a delivery conduit adapter, a guide tube adapter, and a cannula adapter.

12. A method for managing equipment, characterized in that, include: In response to a user account scanning multiple target QR codes on a terminal device's scanning interface, the terminal device obtains target QR code information corresponding to the multiple target QR codes, and the multiple target QR codes are set on the multiple target devices one by one. The terminal device sends the target QR code information to the backend server; If the number of uses corresponding to the multiple target devices determined by the backend server based on the target QR code information all meet the usage security requirements, the terminal device receives the usage verification code generated and sent by the backend server for using the multiple target devices.

13. The method according to claim 12, characterized in that, The method further includes: In response to a user account's login operation on the terminal device's login interface, the terminal device confirms that the user account is logged in and displays the terminal device's scanning interface to the user account.

14. An equipment management device, characterized in that, include: The acquisition unit is used by the backend server to acquire target QR code information sent by the terminal device. The target QR code information is information obtained by the user account scanning multiple target QR codes through the scanning interface of the terminal device. The multiple target QR codes are set one-to-one on multiple target devices. A determining unit is used by the backend server to determine the number of times each of the multiple target devices is used, based on the target QR code information. The generation unit is configured to, if the number of uses corresponding to the plurality of target devices all meet the usage security requirements, generate a usage verification code for using the plurality of target devices and send the usage verification code to the terminal device; if the number of uses corresponding to at least one of the plurality of target devices does not meet the usage security requirements, the backend server does not generate the usage verification code.

15. An equipment management device, characterized in that, include: The unit is used to respond to the scanning operation of the user account scanning multiple target QR codes on the scanning interface of the terminal device, wherein the terminal device obtains the target QR code information corresponding to the multiple target QR codes, and the multiple target QR codes are set on the multiple target devices one by one. A sending unit is used for the terminal device to send the target QR code information to the backend server; The receiving unit is configured to receive a usage verification code generated and sent by the backend server for using the multiple target devices if the number of uses corresponding to the multiple target devices determined by the backend server based on the target QR code information all meet the usage security requirements.

16. An equipment management system, characterized in that, The system includes a backend server and a terminal device, wherein the backend server is used to execute the method according to any one of claims 1-11, and the terminal device is used to execute the method according to any one of claims 12-13.

17. An electronic device, characterized in that, include: The device includes a processor, a memory, and a bus, wherein the memory stores machine-readable instructions executable by the processor, and the processor communicates with the memory via the bus when the electronic device is in operation. When the machine-readable instructions are executed by the processor, they are used to perform the method described in any one of claims 1-11, or to perform the method described in any one of claims 12-13.

18. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, performs the method as described in any one of claims 1-11, or performs the method as described in any one of claims 12-13.

19. A computer program product, characterized in that, It includes a computer program that, when run by a processor, performs the method according to any one of claims 1-11, or performs the method according to any one of claims 12-13.

Images