Device management method and apparatus

Abstract

Embodiments of this specification provide a device management method and apparatus, wherein the device management method includes: in response to a device management instruction, sending a charging control instruction to a target device storage unit in a device management cabinet, wherein the device to be managed is stored in the target device storage unit; receiving an execution result generated by the target device storage unit executing the charging control instruction; determining a charging event sequence generated by the device to be managed based on the execution result; comparing the charging event sequence with the execution result; determining the storage status of the device to be managed based on the comparison result; sending the device identification and storage status of the device to be managed to a client; wherein the client generates borrowing and returning information for the device to be managed based on the device identification and storage status.

Description

Technical Field

[0001] The embodiments of this specification relate to the field of computer technology, and in particular to a device management method. Background Art

[0002] Under the "new retail" service model, service providers (retailers or merchants in practical applications) can open offline physical stores, where consumers can purchase goods directly. At the same time, service providers can also provide online stores corresponding to physical stores through online applications (apps), displaying information about goods available in physical stores to users through online stores, allowing them to place orders.

[0003] Whether it is an offline physical store or an online store, in the process of providing services to consumer users, relevant operators may need to cooperate with the use of some mobile devices. For example, when a user purchases a product in an offline store, the cashier can provide the user with a convenient and fast settlement service through a mobile POS machine. In other words, in order to provide services to consumer users, a physical store usually needs to be equipped with multiple operators to perform different tasks, and in order to ensure the normal progress of each task, each operator will be assigned a mobile device for their own task. The operator can use the assigned mobile device or even borrow the mobile device of other personnel to perform related tasks, which leads to relatively chaotic use and management of the equipment. Therefore, an effective device management method is urgently needed to solve this problem. Summary of the Invention

[0004] In view of this, embodiments of this specification provide a device management method. One or more embodiments of this specification also relate to a device management apparatus, a computing device, a computer-readable storage medium, and a computer program to address technical deficiencies in the prior art.

[0005] According to a first aspect of an embodiment of this specification, a device management method is provided, which is applied to a device to be managed, including:

[0006] In response to the device management instruction, a charging control instruction is sent to a target device storage unit in the device management cabinet, wherein the device to be managed is stored in the target device storage unit;

[0007] Receiving an execution result generated by executing the charging control instruction by the target device storage unit;

[0008] Determining a charging event sequence generated by the device to be managed based on the execution result;

[0009] Comparing the charging event sequence with the execution result, and determining the storage status of the device to be managed based on the comparison result;

[0010] The device identification and the storage status of the device to be managed are sent to the client, wherein the client generates borrowing and returning information of the device to be managed according to the device identification and the storage status.

[0011] Optionally, the sending of the charging control instruction to the target device storage unit in the device management cabinet includes:

[0012] A first Bluetooth communication link is established with a target device storage unit in the device management cabinet, and a charging control instruction is sent to the target device storage unit through the first Bluetooth communication link.

[0013] Optionally, receiving an execution result generated by executing the charging control instruction by the storage unit of the target device includes:

[0014] Receiving a first execution result generated by executing the start charging instruction by the target device storage unit; and / or,

[0015] Receiving a second execution result generated by the target device storage unit executing the disconnect charging instruction;

[0016] Accordingly, determining a charging event sequence generated by the device to be managed based on the execution result includes:

[0017] Obtaining a charging event generated by the device to be managed based on the first execution result; and / or,

[0018] Obtaining a charging disconnection event generated by the device to be managed based on the second execution result;

[0019] A charging event sequence is constructed based on event information corresponding to the charging event and / or the charging disconnection event.

[0020] Optionally, comparing the charging event sequence with the execution result, and determining the storage status of the device to be managed based on the comparison result, includes:

[0021] comparing a first event start time of a charging event in the charging event sequence with a first execution time corresponding to a start charging instruction executed by a storage unit of a target device;

[0022] If it is determined according to the comparison result that the difference between the start time of the first event and the first execution time is less than a preset time threshold, then determining that the storage status of the device to be managed is successfully placed in the storage unit of the target device; and / or,

[0023] comparing a second event start time of a disconnect charging event in the charging event sequence with a second execution time corresponding to execution of a disconnect charging instruction by a storage unit of a target device;

[0024] If it is determined according to the comparison result that the difference between the second event start time and the second execution time is greater than or equal to a preset time threshold, it is determined that the storage status of the device to be managed is not successfully placed into the target device storage unit.

[0025] Optionally, the device management method further includes:

[0026] In response to the image acquisition instruction, calling the image acquisition component to acquire an image identification code corresponding to a first device storage unit in the device management cabinet, wherein the first device storage unit is one of a plurality of device storage units in the device management cabinet;

[0027] The image identification code is parsed to obtain location information of the first device storage unit in the device management cabinet.

[0028] Optionally, the device management method further includes:

[0029] A first Bluetooth communication link is established with the first device storage unit according to the location information, and a charging control instruction is sent to the first device storage unit through the first Bluetooth communication link.

[0030] Optionally, sending the device identifier of the device to be managed and the storage status to the client includes:

[0031] The device identification and the storage status of the device to be managed are sent to a cloud service platform, wherein the cloud service platform sends the device identification and the storage status to a client.

[0032] Optionally, the device management method further includes:

[0033] A second Bluetooth communication link is established with the electromagnetic lock. The first Bluetooth communication link, the second Bluetooth communication link, the communication link between the device to be managed and the cloud service platform, and the communication link between the cloud service platform and the client together constitute a Bluetooth auxiliary link.

[0034] Optionally, the device management method further includes:

[0035] Sending the charging status information of the target device storage unit, the charging status information of the device to be managed, the lock status data of the electromagnetic lock, the device identifier and the storage status to the client via the Bluetooth auxiliary link;

[0036] Among them, the charging status information of the target device storage unit is transmitted by the target device storage unit to the device to be managed through the first Bluetooth communication link, and the lock status data is sent by the electromagnetic lock to the device to be managed through the second Bluetooth communication link. The device to be managed sends the charging status information of the target device storage unit, the charging status information of the device to be managed, the lock status data of the electromagnetic lock, the device identification and the storage status to the client through the communication link between the device and the cloud service platform, and the communication link between the cloud service platform and the client.

[0037] According to a second aspect of an embodiment of this specification, there is provided a device management apparatus, applied to a device to be managed, comprising:

[0038] a sending module configured to send a charging control instruction to a target device storage unit in the device management cabinet in response to the device management instruction, wherein the device to be managed is stored in the target device storage unit;

[0039] A receiving module configured to receive an execution result generated by the target device storage unit executing the charging control instruction;

[0040] A determination module, configured to determine a charging event sequence generated by the device to be managed based on the execution result;

[0041] a comparison module configured to compare the charging event sequence with the execution result, and determine the storage status of the device to be managed based on the comparison result;

[0042] The processing module is configured to send the device identification and the storage status of the device to be managed to the client, wherein the client generates the borrowing and returning information of the device to be managed according to the device identification and the storage status.

[0043] According to a third aspect of an embodiment of this specification, a computing device is provided, including:

[0044] memory and processor;

[0045] The memory is configured to store computer-executable instructions, and the processor is configured to execute the computer-executable instructions:

[0046] In response to the device management instruction, a charging control instruction is sent to a target device storage unit in the device management cabinet, wherein the device to be managed is stored in the target device storage unit;

[0047] Receiving an execution result generated by executing the charging control instruction by the target device storage unit;

[0048] Determining a charging event sequence generated by the device to be managed based on the execution result;

[0049] Comparing the charging event sequence with the execution result, and determining the storage status of the device to be managed based on the comparison result;

[0050] The device identification and the storage status of the device to be managed are sent to the client, wherein the client generates borrowing and returning information of the device to be managed according to the device identification and the storage status.

[0051] According to a fourth aspect of the embodiments of this specification, a computer-readable storage medium is provided, which stores computer-executable instructions, and when the instructions are executed by a processor, the steps of any one of the device management methods are implemented.

[0052] According to a fifth aspect of the embodiments of this specification, a computer program is provided, wherein when the computer program is executed in a computer, the computer is caused to execute the steps of the above-mentioned device management method.

[0053] One embodiment of the present specification sends a charging control instruction to a target device storage unit in a device management cabinet in response to a device management instruction, wherein the device to be managed is stored in the target device storage unit, receives an execution result generated by the target device storage unit executing the charging control instruction, determines a charging event sequence generated by the device to be managed based on the execution result, compares the charging event sequence with the execution result, and determines the storage status of the device to be managed based on the comparison result, and sends the device identification and the storage status of the device to be managed to a client, wherein the client generates borrowing and returning information of the device to be managed based on the device identification and the storage status.

[0054] The embodiments of this specification utilize a device management cabinet to implement daily digital management of managed devices, including storage, issuance, borrowing, returning, and charging. This avoids resource waste caused by lost managed devices and helps improve the utilization rate of managed devices. Furthermore, by transferring the location awareness function of the device storage unit where the managed device resides from the device management cabinet to the managed device, the cost of manufacturing the device management cabinet is reduced.

[0055] In addition, by controlling the charging state or disconnected charging state of the target device storage unit, the device to be managed generates a corresponding charging event sequence based on the charging event of the charging state or disconnected charging state, and then the device to be managed compares the charging event sequence with the status information (execution result) corresponding to the charging state or disconnected charging state of the aforementioned target device storage unit to determine the storage state of the device to be managed itself based on the comparison result, and then the device to be managed sends its device identification and the storage state to the client, and the client can generate the borrowing and returning information of the device to be managed based on the device identification and storage state, which is conducive to ensuring the accuracy of the generation result of the borrowing and returning information. BRIEF DESCRIPTION OF THE DRAWINGS

[0056] Figure 1 This is an architecture diagram of a device management system provided by one embodiment of this specification;

[0057] Figure 2 This is a flow chart of a device management method provided by one embodiment of this specification;

[0058] Figure 3 This is a process flow chart of a device management method provided by one embodiment of this specification;

[0059] Figure 4 This is a schematic diagram of the structure of a device management device provided by an embodiment of this specification;

[0060] Figure 5 This is a structural block diagram of a computing device provided by one embodiment of this specification. DETAILED DESCRIPTION

[0061] The following description sets forth many specific details to facilitate a thorough understanding of this specification. However, this specification can be implemented in many other ways than those described herein, and those skilled in the art can make similar generalizations without violating the scope of this specification. Therefore, this specification is not limited to the specific implementations disclosed below.

[0062] The terms used in one or more embodiments of this specification are for the purpose of describing specific embodiments only and are not intended to limit one or more embodiments of this specification. The singular forms "a," "the," and "the" used in one or more embodiments of this specification and the appended claims are also intended to include plural forms unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used in one or more embodiments of this specification refers to and includes any or all possible combinations of one or more associated listed items.

[0063] It should be understood that although the terms first, second, etc. may be used to describe various information in one or more embodiments of this specification, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of one or more embodiments of this specification, the first may also be referred to as the second, and similarly, the second may also be referred to as the first. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0064] First, the terms involved in one or more embodiments of this specification are explained.

[0065] Digital terminals are battery-powered electronic devices that have data storage and computing capabilities, are amenable to secondary development, can communicate with other devices, and have a human-machine interface. These devices, such as handheld terminals, personal digital assistants, handheld cash registers, and barcode scanners, are widely used in industries like express delivery, logistics, supermarkets, and smart manufacturing.

[0066] Terminal management cabinet: equipment and systems that provide digital terminals with management functions such as equipment borrowing and returning management, charging, status data statistics, fault reporting, and usage statistics analysis.

[0067] In this specification, a device management method is provided. This specification also relates to a device management apparatus, a computing device, and a computer-readable storage medium, which are described in detail one by one in the following embodiments.

[0068] Figure 1 The following is an architecture diagram of a device management system provided according to one embodiment of this specification, specifically including:

[0069] An equipment management cabinet, equipment to be managed, and a client, wherein the equipment management cabinet is equipped with an electromagnetic lock, the equipment to be managed is stored in a device storage unit in the equipment management cabinet, and is connected to the device storage unit via a charging cable configured in the device storage unit, and the equipment management cabinet and the client, as well as the electromagnetic lock and the client are connected via Bluetooth communication.

[0070] Specifically, the devices to be managed are digital terminals requiring device management, including but not limited to handheld terminals, personal digital assistants, handheld cash registers, and barcode scanners widely used in industries such as express delivery, logistics, supermarkets, and smart manufacturing. Device management includes but is not limited to loan and return management, charging, status data statistics, fault reporting, and usage statistics and analysis.

[0071] The client includes but is not limited to a mobile computer, a mobile computing device or a face recognition device, wherein the mobile computing device includes but is not limited to a smartphone, a tablet computer, a personal digital assistant, a laptop computer, a notebook computer, a netbook, etc., a mobile phone (e.g., a smartphone), a wearable computing device (e.g., a smart watch, smart glasses, etc.) or other types of mobile devices, or a stationary computing device such as a desktop computer or a PC.

[0072] In the equipment management system provided in the embodiments of this specification, the equipment management cabinet includes multiple equipment storage units, each of which can be used to store one or at least two devices to be managed. When a user needs to lend a device to be managed, the user can take the device to be managed out of the device storage unit, or when a user needs to return a device to be managed, the user can put the device to be managed into the device storage unit.

[0073] When a user lends or returns a device to be managed, the client needs to generate corresponding lending or returning information based on the user's lending or returning operation to record and manage the lending and returning status of the device to be managed. To ensure the accuracy of the generated lending and returning information, the embodiment of this specification can use the device to be managed to send a charging control instruction to the target device storage unit in the device management cabinet, obtain the corresponding execution result generated by the target storage unit executing the charging control instruction, and obtain the charging event sequence generated by the device to be managed based on the execution result. The charging event sequence is then compared with the execution result to determine the storage status of the device to be managed based on the comparison result. The client then generates the lending and returning information of the device to be managed based on the storage status and the device identifier of the device to be managed.

[0074] For example, after the user sends a loan request for the device to be managed to the client, the client can authenticate the user, and if the verification is passed, it can send an unlocking instruction to the electromagnetic lock, and the electromagnetic lock will unlock the equipment management cabinet. Then the user can open the door of the equipment management cabinet and take out the device to be managed from any device storage unit in the equipment management cabinet that meets the lending conditions. If the user takes out the device to be managed from the device storage unit 1, during the removal process, the user can send a charging control instruction to the device storage unit 1 through the device to be managed. The charging control instruction includes a start charging instruction and / or a disconnect charging instruction. The device storage unit 1 executes the start charging instruction or the disconnect charging instruction to charge the device to be managed, or stop charging the device to be managed, and generates a corresponding execution result. For example, at time A1, charging of the device to be managed starts, and at time A2, charging of the device to be managed stops.

[0075] The device to be managed can sense the change in the charging status of the device storage unit 2, and change its own charging status according to the change in the charging status of the device storage unit 2, and generate a corresponding charging event sequence. For example, the device storage unit 1 starts charging the device to be managed at time A1, and the device to be managed senses this change at time A3, and then starts charging at time A3; the device storage unit 1 stops charging the device to be managed at time A2, and the device to be managed senses this change at time A4, and then stops charging at time A4 (there may be a time difference between A3 and A1, and between A4 and A2).

[0076] The device to be managed receives the execution result generated by the device storage unit 1 executing the charging control instruction, and after generating a corresponding charging event sequence by sensing the charging state change result of the device storage unit 1, the execution result can be compared with the charging event sequence, and the storage state of the device to be managed can be determined according to the comparison result, and the storage state and the device identification of the device to be managed are sent to the client, wherein the storage state can be used to represent the user taking out the device to be managed from the storage unit of the target device.

[0077] After receiving the storage status and device identification, the client can generate the lending information of the device to be managed based on this information.

[0078] For another example, after the user sends a return request for the device to be managed to the client, the client can authenticate the user, and if the authentication is passed, it can send an unlocking instruction to the electromagnetic lock, and the electromagnetic lock will unlock the equipment management cabinet. Then the user can open the door of the equipment management cabinet and place the device to be managed in any device storage unit in the equipment management cabinet that meets the return conditions. If the user places the device to be managed in device storage unit 2, then after placing it, the user can send a charging control instruction to the device storage unit 2 through the device to be managed. The charging control instruction includes a start charging instruction and / or a disconnect charging instruction. The device storage unit 2 executes the start charging instruction or the disconnect charging instruction to charge the device to be managed, or stop charging the device to be managed, and generates a corresponding execution result. For example, at time A5, charging of the device to be managed starts, and at time A6, charging of the device to be managed stops.

[0079] The device to be managed can sense the change in the charging state of the device storage unit 2, and change its own charging state according to the change in the charging state of the device storage unit 2, and generate a corresponding charging event sequence. For example, the device storage unit 2 starts charging the device to be managed at time A5, and the device to be managed senses this change at time A7, and then starts charging at time A7; the device storage unit 2 stops charging the device to be managed at time A6, and the device to be managed senses this change at time A8, and then stops charging at time A8 (there may be a time difference between A5 and A7, and between A6 and A8).

[0080] The device to be managed receives the execution result generated by the device storage unit 2 executing the charging control instruction, and generates a corresponding charging event sequence by sensing the charging state change result of the device storage unit 2. The execution result can be compared with the charging event sequence, and the storage state of the device to be managed can be determined according to the comparison result. The storage state and the device identification of the device to be managed are sent to the client, wherein the storage state can be used to characterize whether the device to be managed is placed in the target device storage unit.

[0081] After receiving the storage status and device identification, the client can generate return information for the device to be managed based on this information.

[0082] In actual applications, if the client used by the user is a mobile computer or mobile computing device (such as a smart phone), the user can use the application installed in the mobile computer or mobile computing device to borrow and return the managed device. When the client authenticates the user, it can authenticate the user through the user's login information in the application; if the client used by the user is a face recognition device (such as a face recognition PAD), the user's identity can be authenticated by performing face recognition on the user. The specific method can be determined according to actual needs and is not restricted here.

[0083] In addition, the device management system provided in the embodiments of this specification also includes a cloud service platform. A communication connection is established between the managed devices and the cloud service platform, and between the cloud service platform and the client. Therefore, the managed devices can send their storage status and device identification to the cloud service platform, which then sends the storage status and device identification to the client. The cloud service platform only provides data mirroring functionality, leaving the client responsible for local computing and decision-making.

[0084] The embodiments of this specification utilize a device management cabinet to implement daily digital management of managed devices, including storage, issuance, borrowing, returning, and charging. This avoids resource waste caused by lost managed devices and helps improve the utilization rate of managed devices. Furthermore, by transferring the location awareness function of the device storage unit where the managed device resides from the device management cabinet to the managed device, the cost of manufacturing the device management cabinet is reduced.

[0085] In addition, by controlling the charging state or disconnected charging state of the target device storage unit, the device to be managed generates a corresponding charging event sequence based on the charging event of the charging state or disconnected charging state, and then the device to be managed compares the charging event sequence with the status information (execution result) corresponding to the charging state or disconnected charging state of the aforementioned target device storage unit to determine the storage state of the device to be managed itself based on the comparison result, and then the device to be managed sends its device identification and the storage state to the client, and the client can generate the borrowing and returning information of the device to be managed based on the device identification and storage state, which is conducive to ensuring the accuracy of the generation result of the borrowing and returning information.

[0086] In addition, the embodiment of this specification uses low-cost Bluetooth technology to communicate between the equipment management cabinet, the electromagnetic lock and the client, and the device to be managed can report its own storage status and device identification via Wi-Fi. The equipment management cabinet itself does not have computing and transmission capabilities, which is conducive to reducing the production cost of the equipment management cabinet.

[0087] Figure 2 A flow chart of a device management method provided according to an embodiment of this specification is shown, which specifically includes the following steps.

[0088] Step 202 : In response to the device management instruction, a charging control instruction is sent to a target device storage unit in the device management cabinet, wherein the device to be managed is stored in the target device storage unit.

[0089] The device management methods provided in the embodiments of this specification are applied to managed devices. These devices are digital terminals requiring device management, including but not limited to handheld terminals, personal digital assistants, handheld cash registers, and barcode scanners widely used in industries such as express delivery, logistics, supermarkets, and smart manufacturing. Device management includes but is not limited to loan and return management, charging, status data statistics, fault reporting, and usage statistics and analysis.

[0090] The equipment management cabinet includes multiple equipment storage units, each of which can be used to store one or at least two devices to be managed. When a user needs to lend a device to be managed, he or she can take the device to be managed out of the equipment storage unit, or when a user needs to return a device to be managed, he or she can put the device to be managed into the equipment storage unit.

[0091] When a user lends or returns a device to be managed, the client needs to generate corresponding lending or returning information according to the user's lending or returning operation to record and manage the lending and returning status of the device to be managed.

[0092] Among them, since the equipment management cabinet contains multiple equipment storage units, and each equipment storage unit is equipped with a charging cable that can be used to charge the device to be managed, after the user places the device to be managed in the equipment storage unit, the charging cable needs to be inserted into the device to be managed to ensure that the device to be managed enters the charging state. Therefore, when the client generates the borrowing and returning information of the device to be managed, it can determine whether the device to be managed is successfully borrowed or returned based on the charging status change information of the device to be managed and the charging status change information of the target device storage unit.

[0093] In addition, each equipment management cabinet is equipped with an electromagnetic lock, which can be used to control the switch of the equipment management cabinet. In actual applications, when a user needs to lend or return the equipment to be managed, the user can send an unlocking instruction to the electromagnetic lock through the client. Before sending the unlocking instruction, the client can first authenticate the user, and if the verification is passed, the unlocking instruction is sent to the electromagnetic lock, so that the electromagnetic lock unlocks the equipment management cabinet; after the unlocking is successful, the user can borrow the equipment to be managed from any equipment storage unit in the equipment management cabinet, or place the borrowed equipment to be managed in an idle equipment storage unit in the equipment management cabinet to realize the lending or returning of the equipment to be managed.

[0094] In the embodiments of this specification, before a user removes the device to be managed from the target device storage unit, since the device to be managed is connected to a charging cable configured in the target device storage unit, the device to be managed can be used to send a charging control instruction to the target device storage unit in the device management cabinet, obtain the target storage unit to execute the charging control instruction to generate a corresponding execution result, and obtain a charging event sequence generated by the device to be managed based on the execution result. The charging event sequence is then compared with the execution result to determine the storage status of the device to be managed based on the comparison result. The client then generates the loan information of the device to be managed based on the storage status and the device identification of the device to be managed. The target device storage unit is any device storage unit in the device management cabinet that meets the loan conditions.

[0095] Alternatively, when a user places the device to be managed into the target device storage unit and connects the charging cable configured in the target device storage unit to the device to be managed, the device to be managed can be used to send a charging control instruction to the target device storage unit in the device management cabinet, obtain the target storage unit to execute the charging control instruction to generate a corresponding execution result, and obtain the charging event sequence generated by the device to be managed based on the execution result. The charging event sequence is then compared with the execution result to determine the storage status of the device to be managed based on the comparison result. The client then generates the return information of the device to be managed based on the storage status and the device identification of the device to be managed. The target device storage unit is any device storage unit in the device management cabinet that meets the return conditions.

[0096] The client includes but is not limited to a mobile computer, a mobile computing device or a face recognition device, wherein the mobile computing device includes but is not limited to a smartphone, a tablet computer, a personal digital assistant, a laptop computer, a notebook computer, a netbook, etc., a mobile phone (e.g., a smartphone), a wearable computing device (e.g., a smart watch, smart glasses, etc.) or other types of mobile devices, or a stationary computing device such as a desktop computer or a PC.

[0097] In actual applications, after the user sends a loan request for the device to be managed to the client, the client can authenticate the user, and if the verification is passed, it can send an unlocking instruction to the electromagnetic lock, and the electromagnetic lock will unlock the equipment management cabinet. Then the user can open the door of the equipment management cabinet and take out the device to be managed from any device storage unit in the equipment management cabinet that meets the lending conditions. If the user takes out the device to be managed from the device storage unit 1, before taking it out, the user can send a charging control instruction to the device storage unit 1 through the device to be managed, and the device storage unit 1 in the equipment management cabinet will execute the power control instruction to generate a corresponding execution result.

[0098] After the user sends a return request for the device to be managed to the client, the client can authenticate the user, and if the verification is passed, it can send an unlocking instruction to the electromagnetic lock, and the electromagnetic lock will unlock the equipment management cabinet. Then the user can open the door of the equipment management cabinet and place the device to be managed in any device storage unit in the equipment management cabinet that meets the return conditions. If the user places the device to be managed in device storage unit 2, then after placing it, the user can send a charging control instruction to the device storage unit 2 through the device to be managed, and the device storage unit 2 in the equipment management cabinet will execute the power control instruction to generate a corresponding execution result.

[0099] During specific implementation, a charging control instruction is sent to the target device storage unit in the equipment management cabinet, specifically, a first Bluetooth communication link is established between the target device storage unit in the equipment management cabinet, and a charging control instruction is sent to the target device storage unit through the first Bluetooth communication link.

[0100] Specifically, the device to be managed may establish a Bluetooth communication link with the target device storage unit in the device management cabinet, and send a charging control instruction to the target device storage unit via the Bluetooth communication link.

[0101] Step 204: Receive an execution result generated by the target device storage unit executing the charging control instruction.

[0102] Specifically, after receiving a charging control instruction sent by the device to be managed, the target device storage unit may execute the charging control instruction and generate a corresponding execution result. The charging control instruction may include a start charging instruction and / or a stop charging instruction. The target device storage unit executes the start charging instruction or the stop charging instruction to charge or stop charging the device to be managed, and generates a corresponding execution result.

[0103] For example, if the target device storage unit receives a start charging instruction at time A1, it will start charging the managed device at time A1. If the target device storage unit receives a stop charging instruction at time A2, it will stop charging the managed device at time A2. Starting charging the managed device at time A1 and stopping charging the managed device at time A2 are the execution results generated by executing the charging control instructions.

[0104] After the target device storage unit generates the execution result, it can send it to the device to be managed. The device to be managed can use the execution result as a reference and compare its own charging state change data with the execution result to determine whether the two match.

[0105] Step 206: Determine a charging event sequence generated by the device to be managed based on the execution result.

[0106] Specifically, after the device to be managed sends the charging control instruction to the storage unit of the target device, the storage unit of the target device executes the charging control instruction and generates a corresponding execution result.

[0107] In a specific implementation, receiving an execution result generated by executing the charging control instruction by the storage unit of the target device includes:

[0108] receiving a first execution result generated by executing a start charging instruction by a storage unit of the target device; and / or,

[0109] Receiving a second execution result generated by the target device storage unit executing the disconnect charging instruction;

[0110] Accordingly, determining the charging event sequence generated by the device to be managed based on the execution result can be specifically achieved in the following manner:

[0111] Obtaining a charging event generated by the device to be managed based on the first execution result; and / or,

[0112] Obtaining a charging disconnection event generated by the device to be managed based on the second execution result;

[0113] A charging event sequence is constructed based on event information corresponding to the charging event and / or the charging disconnection event.

[0114] Specifically, the charging control instruction includes a start charging instruction and / or a disconnect charging instruction. Therefore, the target storage unit executes the charging control instruction and generates a corresponding execution result, i.e., executing the start charging instruction generates a first execution result; and / or executing the disconnect charging instruction generates a second execution result. The managed device receives the execution result generated by the target device storage unit executing the charging control instruction, i.e., receives the first execution result and / or the second execution result.

[0115] In addition, during the process of the target storage unit executing the charging control instruction, the device to be managed can sense the change in the charging state of the target storage unit, and change its own charging state according to the change in the charging state of the target device storage unit, and generate a corresponding charging event sequence. For example, the target device storage unit starts charging the device to be managed at time A1 (first execution result), and the device to be managed senses this change at time A3, and then starts charging at time A3. The corresponding charging event is that the device to be managed starts charging at time A3; the target device storage unit stops charging the device to be managed at time A2 (second execution result), and the device to be managed senses this change at time A4, and then stops charging at time A4. The corresponding disconnection charging event is that the device to be managed stops charging at time A4.

[0116] After the device to be managed generates corresponding charging events and / or charging disconnection events based on the charging state change result of the target device storage unit, a charging event sequence can be constructed based on the charging events and / or charging disconnection events.

[0117] Step 208 : Compare the charging event sequence with the execution result, and determine the storage status of the device to be managed based on the comparison result.

[0118] In a specific implementation, the charging event sequence is compared with the execution result, and the storage status of the device to be managed is determined based on the comparison result, which can be specifically achieved in the following manner:

[0119] comparing a first event start time of a charging event in the charging event sequence with a first execution time corresponding to a start charging instruction executed by a storage unit of a target device;

[0120] If it is determined according to the comparison result that the difference between the start time of the first event and the first execution time is less than a preset time threshold, then determining that the storage status of the device to be managed is successfully placed in the storage unit of the target device; and / or,

[0121] comparing a second event start time of a disconnect charging event in the charging event sequence with a second execution time corresponding to execution of a disconnect charging instruction by a storage unit of a target device;

[0122] If it is determined according to the comparison result that the difference between the second event start time and the second execution time is greater than or equal to a preset time threshold, it is determined that the storage status of the device to be managed is not successfully placed into the target device storage unit.

[0123] Specifically, the device to be managed receives the execution result generated by the target device storage unit executing the charging control instruction, and generates a corresponding charging event sequence by sensing the charging state change result of the target device storage unit. The execution result can be compared with the charging event sequence, and the storage state of the device to be managed can be determined based on the comparison result.

[0124] Among them, the first event start time of the charging event in the charging event sequence can be compared with the first execution time corresponding to the target device storage unit executing the start charging instruction. If it is determined according to the comparison result that the difference between the first event start time and the first execution time is less than the preset time threshold, it is determined that the storage status of the device to be managed is successfully placed in the target device storage unit; otherwise, it is determined that the storage status of the device to be managed is not successfully placed in the target device storage unit; and / or, the second event start time of the disconnect charging event in the charging event sequence can be compared with the second execution time corresponding to the target device storage unit executing the disconnect charging instruction, and if it is determined according to the comparison result that the difference between the second event start time and the second execution time is greater than or equal to the preset time threshold, it is determined that the storage status of the device to be managed is not successfully placed in the target device storage unit; otherwise, it is determined that the storage status of the device to be managed is successfully placed in the target device storage unit.

[0125] Continuing with the above example, the target device storage unit starts charging the device to be managed at time A5, and the device to be managed starts charging at time A7, that is, the first event start time of the charging event is A5, and the first execution time corresponding to the target device storage unit executing the start charging instruction is A7. The time A5 is compared with A7. If the difference between the two is determined to be less than the preset time threshold according to the comparison result, it is determined that the storage status of the device to be managed is successfully placed in the target device storage unit. Otherwise, it is determined that the storage status of the device to be managed is not successfully placed in the target device storage unit.

[0126] Alternatively, the target device storage unit stops charging the device to be managed at time A6, and the device to be managed stops charging at time A8, that is, the start time of the second event of the charging disconnection event is A6, and the second execution time corresponding to the target device storage unit executing the charging disconnection instruction is A8. The time A6 is compared with A8. If it is determined according to the comparison result that the difference between the two is less than the preset time threshold, it is determined that the storage status of the device to be managed is successfully placed in the target device storage unit. Otherwise, it is determined that the storage status of the device to be managed is not successfully placed in the target device storage unit.

[0127] The embodiments of this specification determine the storage status of the device to be managed by combining the charging event sequence of the device to be managed and the execution result generated by the target device storage unit executing the charging control instruction, which is conducive to ensuring the accuracy of the generated result.

[0128] Step 210: Send the device identification and the storage status of the device to be managed to the client, wherein the client generates the borrowing and returning information of the device to be managed according to the device identification and the storage status.

[0129] Specifically, after the device to be managed determines its own storage status, it may send the storage status and the device identification of the device to be managed to the client, wherein the storage status may be used to indicate whether the device to be managed is placed in the target device storage unit.

[0130] After receiving the storage status and device identification, the client can generate the borrowing and returning information of the device to be managed based on this information.

[0131] In addition, when the user places the device to be managed into the target device storage unit, the user can send an image acquisition instruction to the device to be managed, so that the device to be managed can acquire the image identification code corresponding to the target device storage unit, and determine the location information of the target device storage unit in the device management cabinet based on the identification result, and send a charging control instruction to the corresponding target device storage unit based on the location information. This can be achieved in the following ways:

[0132] In response to the image acquisition instruction, calling the image acquisition component to acquire an image identification code corresponding to a first device storage unit in the device management cabinet, wherein the first device storage unit is one of a plurality of device storage units in the device management cabinet;

[0133] The image identification code is parsed to obtain location information of the first device storage unit in the device management cabinet.

[0134] Furthermore, after determining the location information, a first Bluetooth communication link is established with the first device storage unit according to the location information, and a charging control instruction is sent to the first device storage unit through the first Bluetooth communication link.

[0135] Specifically, in order to ensure the accuracy of the generated borrowing and returning information, when the user places the device to be managed into the target device storage unit, the user can use the device to be managed to scan and identify the image identification code of the target device storage unit, so as to determine the position of the target device storage unit in the equipment management cabinet based on the identification result, thereby determining the storage location of the device to be managed, and then the device to be managed sends a charging control instruction to the first device storage unit corresponding to the location information.

[0136] For example, after the user sends a return request for the device to be managed to the client, the client can authenticate the user, and if the verification is passed, it can send an unlocking instruction to the electromagnetic lock, and the electromagnetic lock will unlock the equipment management cabinet. Then the user can open the door of the equipment management cabinet and place the device to be managed in any device storage unit in the equipment management cabinet that meets the return conditions. If the user places the device to be managed in the device storage unit 1, an image acquisition instruction can be sent to the device to be managed during the placement process, and the device to be managed can call the image acquisition component to capture the image identification code corresponding to the device storage unit 1; wherein, the image identification code includes but is not limited to a QR code, a barcode or other recognizable identification code.

[0137] After the device to be managed collects the image identification code, it can be parsed and the location information of the device storage unit 1 in the device management cabinet can be determined based on the parsing result. The device to be managed then sends a charging control instruction to the device storage unit 1 corresponding to the location information. Specifically, a first Bluetooth communication link can be established with the first device storage unit based on the location information, and a charging control instruction can be sent to the first device storage unit through the first Bluetooth communication link.

[0138] In addition, after the storage status of the device to be managed is determined, the device identification of the device to be managed and its storage status can be sent to the client through the cloud service platform. Specifically, the device identification and storage status of the device to be managed are sent to the cloud service platform, and the cloud service platform sends the device identification and storage status to the client.

[0139] In practice, a communication connection is established between the managed device and the cloud service platform, and between the cloud service platform and the client. Therefore, the managed device can send its storage status and device identification to the cloud service platform, which then sends these status and device identification to the client. The cloud service platform only provides data mirroring, leaving the client responsible for local computation and decision-making.

[0140] In addition, a second Bluetooth communication link can be established between the device to be managed and the electromagnetic lock. The first Bluetooth communication link, the second Bluetooth communication link, the communication link between the device to be managed and the cloud service platform, and the communication link between the cloud service platform and the client together constitute a Bluetooth auxiliary link.

[0141] Furthermore, the charging status information of the target device storage unit, the charging status information of the device to be managed, the lock status data of the electromagnetic lock, the device identification and the storage status may be sent to the client via the Bluetooth auxiliary link;

[0142] Among them, the charging status information of the target device storage unit is transmitted by the target device storage unit to the device to be managed through the first Bluetooth communication link, and the lock status data is sent by the electromagnetic lock to the device to be managed through the second Bluetooth communication link. The device to be managed sends the charging status information of the target device storage unit, the charging status information of the device to be managed, the lock status data of the electromagnetic lock, the device identification and the storage status to the client through the communication link between the device and the cloud service platform, and the communication link between the cloud service platform and the client.

[0143] Specifically, when the equipment management cabinet is in the unlocked state, it can detect the charging status information of each device storage unit, such as the time information of starting charging or disconnecting charging (the time point of starting charging for the device to be managed, or stopping charging for the device to be managed), and send the information to the client; in addition, after the user successfully places the device to be managed into the device storage unit, the user can send a locking instruction to the electromagnetic lock through the client. The electromagnetic lock responds to the locking instruction, locks the equipment management cabinet, and sends the lock status data of the equipment management cabinet to the device to be managed through the second Bluetooth communication link, and then the device to be managed sends the lock status data to the client.

[0144] After the client receives the charging status information of the device storage unit and the lock status data of the electromagnetic lock, it can also obtain the charging status information of the device to be managed, and generate the borrowing and returning information of the device to be managed based on this information, the storage status and the device identification of the device to be managed. The charging status information of the device to be managed can be sent to the client by the device to be managed through the cloud service platform.

[0145] One embodiment of the present specification sends a charging control instruction to a target device storage unit in a device management cabinet in response to a device management instruction, wherein the device to be managed is stored in the target device storage unit, receives an execution result generated by the target device storage unit executing the charging control instruction, determines a charging event sequence generated by the device to be managed based on the execution result, compares the charging event sequence with the execution result, and determines the storage status of the device to be managed based on the comparison result, and sends the device identification and the storage status of the device to be managed to a client, wherein the client generates borrowing and returning information of the device to be managed based on the device identification and the storage status.

[0146] The embodiments of this specification utilize a device management cabinet to implement daily digital management of managed devices, including storage, issuance, borrowing, returning, and charging. This avoids resource waste caused by lost managed devices and helps improve the utilization rate of managed devices. Furthermore, by transferring the location awareness function of the device storage unit where the managed device resides from the device management cabinet to the managed device, the cost of manufacturing the device management cabinet is reduced.

[0147] In addition, by controlling the charging state or disconnected charging state of the target device storage unit, the device to be managed generates a corresponding charging event sequence based on the charging event of the charging state or disconnected charging state, and then the device to be managed compares the charging event sequence with the status information (execution result) corresponding to the charging state or disconnected charging state of the aforementioned target device storage unit to determine the storage state of the device to be managed itself based on the comparison result, and then the device to be managed sends its device identification and the storage state to the client, and the client can generate the borrowing and returning information of the device to be managed based on the device identification and storage state, which is conducive to ensuring the accuracy of the generation result of the borrowing and returning information.

[0148] The following combined Figure 3 , taking the application of the device management method provided in this specification in the scanning device return scenario as an example, the device management method is further explained. Figure 3 A process flow chart of a device management method provided in one embodiment of this specification is shown, which specifically includes the following steps.

[0149] In step 302, the user sends a request to return the scanning device to the face recognition terminal.

[0150] Step 304: The face recognition terminal collects the user's face image and authenticates the user based on the collection result.

[0151] If the verification is successful, step 306 is executed.

[0152] Step 306: The face recognition terminal sends an unlocking instruction to the electromagnetic lock.

[0153] Specifically, the electromagnetic lock responds to the unlocking instruction and performs an unlocking operation.

[0154] In step 308 , the user opens the device management cabinet and places the code scanning device into any free device storage unit in the device management cabinet.

[0155] Specifically, after the user places the code scanning device into the device storage unit, the user needs to insert the charging cable in the device storage unit into the code scanning device to charge the code scanning device.

[0156] Step 310: The code scanning device sends a charging control instruction to the device storage unit.

[0157] Specifically, the charging control instruction includes a charging start instruction and / or a charging stop instruction.

[0158] Step 312: receiving an execution result generated by a storage unit of the device executing the charging control instruction.

[0159] Step 314: Determine a charging event sequence generated by the code scanning device based on the execution result.

[0160] Step 316: Compare the charging event sequence with the execution result, and determine the storage status of the code scanning device based on the comparison result.

[0161] After executing step 316 , the process may return to step 310 to loop through steps 310 to 316 , and the number of loops may be determined based on actual needs and is not limited here.

[0162] Step 318: Send the device identification of the code scanning device and the storage status to the client.

[0163] The client generates return information of the code scanning device according to the device identification and the storage status.

[0164] The embodiments of this specification utilize a device management cabinet to implement daily digital management of the storage, use, return, and charging of code scanning devices, thereby avoiding resource waste caused by the loss of code scanning devices and improving the utilization rate of code scanning devices. In addition, the location awareness function of the device storage unit where the code scanning device is located is transferred from the device management cabinet to the code scanning device, which helps reduce the production cost of the device management cabinet.

[0165] In addition, by controlling the charging state or disconnecting charging state of the device storage unit, the scanning device generates a corresponding charging event sequence based on the charging event of the charging state or disconnecting charging state, and then the scanning device compares the charging event sequence with the state information (execution result) corresponding to the charging state or disconnecting charging state of the aforementioned device storage unit to determine the storage state of the scanning device itself according to the comparison result, and then the scanning device sends its device identification and the storage state to the client. The client can generate the return information of the scanning device based on the device identification and storage state, which is conducive to ensuring the accuracy of the generation result of the return information.

[0166] Corresponding to the above method embodiment, this specification also provides a device management apparatus embodiment, Figure 4 FIG1 shows a schematic diagram of the structure of a device management device provided by an embodiment of this specification. Figure 4 As shown, the device includes:

[0167] The sending module 402 is configured to send a charging control instruction to a target device storage unit in the device management cabinet in response to the device management instruction, wherein the device to be managed is stored in the target device storage unit;

[0168] The receiving module 404 is configured to receive an execution result generated by the target device storage unit executing the charging control instruction;

[0169] A determination module 406 is configured to determine a charging event sequence generated by the device to be managed based on the execution result;

[0170] a comparison module 408 configured to compare the charging event sequence with the execution result, and determine the storage status of the device to be managed based on the comparison result;

[0171] The processing module 410 is configured to send the device identification and the storage status of the device to be managed to the client, wherein the client generates the borrowing and returning information of the device to be managed according to the device identification and the storage status.

[0172] Optionally, the sending module 402 is further configured to:

[0173] A first Bluetooth communication link is established with a target device storage unit in the device management cabinet, and a charging control instruction is sent to the target device storage unit through the first Bluetooth communication link.

[0174] Optionally, the receiving module 404 is further configured to:

[0175] receiving a first execution result generated by executing a start charging instruction by a storage unit of the target device; and / or,

[0176] Receiving a second execution result generated by the target device storage unit executing the disconnect charging instruction;

[0177] Accordingly, the determining module 406 is further configured to:

[0178] Obtaining a charging event generated by the device to be managed based on the first execution result; and / or,

[0179] Obtaining a charging disconnection event generated by the device to be managed based on the second execution result;

[0180] A charging event sequence is constructed based on event information corresponding to the charging event and / or the charging disconnection event.

[0181] Optionally, the comparison module 408 is further configured to:

[0182] comparing a first event start time of a charging event in the charging event sequence with a first execution time corresponding to a start charging instruction executed by a storage unit of a target device;

[0183] If it is determined according to the comparison result that the difference between the start time of the first event and the first execution time is less than a preset time threshold, then determining that the storage status of the device to be managed is successfully placed in the storage unit of the target device; and / or,

[0184] comparing a second event start time of a disconnect charging event in the charging event sequence with a second execution time corresponding to execution of a disconnect charging instruction by a storage unit of a target device;

[0185] If it is determined according to the comparison result that the difference between the second event start time and the second execution time is greater than or equal to a preset time threshold, it is determined that the storage status of the device to be managed is not successfully placed into the target device storage unit.

[0186] Optionally, the device management apparatus further includes a parsing module configured to:

[0187] In response to the image acquisition instruction, calling the image acquisition component to acquire an image identification code corresponding to a first device storage unit in the device management cabinet, wherein the first device storage unit is one of a plurality of device storage units in the device management cabinet;

[0188] The image identification code is parsed to obtain location information of the first device storage unit in the device management cabinet.

[0189] Optionally, the device management apparatus further includes a first establishing module configured to:

[0190] A first Bluetooth communication link is established with the first device storage unit according to the location information, and a charging control instruction is sent to the first device storage unit through the first Bluetooth communication link.

[0191] Optionally, the processing module 410 is further configured to:

[0192] The device identification and the storage status of the device to be managed are sent to a cloud service platform, wherein the cloud service platform sends the device identification and the storage status to a client.

[0193] Optionally, the device management apparatus further includes a second establishing module configured to:

[0194] A second Bluetooth communication link is established with the electromagnetic lock. The first Bluetooth communication link, the second Bluetooth communication link, the communication link between the device to be managed and the cloud service platform, and the communication link between the cloud service platform and the client together constitute a Bluetooth auxiliary link.

[0195] Optionally, the device management apparatus further includes a data sending module configured to:

[0196] Sending the charging status information of the target device storage unit, the charging status information of the device to be managed, the lock status data of the electromagnetic lock, the device identifier and the storage status to the client via the Bluetooth auxiliary link;

[0197] Among them, the charging status information of the target device storage unit is transmitted by the target device storage unit to the device to be managed through the first Bluetooth communication link, and the lock status data is sent by the electromagnetic lock to the device to be managed through the second Bluetooth communication link. The device to be managed sends the charging status information of the target device storage unit, the charging status information of the device to be managed, the lock status data of the electromagnetic lock, the device identification and the storage status to the client through the communication link between the device and the cloud service platform, and the communication link between the cloud service platform and the client.

[0198] The above is a schematic diagram of a device management apparatus according to this embodiment. It should be noted that the technical solution of the device management apparatus and the technical solution of the device management method described above are of the same concept. For details not described in detail in the technical solution of the device management apparatus, please refer to the description of the technical solution of the device management method described above.

[0199] Figure 5The block diagram of a computing device 500 according to one embodiment of the present disclosure is shown. Components of the computing device 500 include, but are not limited to, a memory 510 and a processor 520. The processor 520 is connected to the memory 510 via a bus 530, and a database 550 is used to store data.

[0200] The computing device 500 also includes an access device 540 that enables the computing device 500 to communicate via one or more networks 560. Examples of such networks include a public switched telephone network (PSTN), a local area network (LAN), a wide area network (WAN), a personal area network (PAN), or a combination of communication networks such as the Internet. The access device 540 may include one or more of any type of network interface (e.g., a network interface card (NIC)), whether wired or wireless, such as an IEEE 802.11 wireless local area network (WLAN) wireless interface, a Worldwide Interoperability for Microwave Access (Wi-MAX) interface, an Ethernet interface, a universal serial bus (USB) interface, a cellular network interface, a Bluetooth interface, a near field communication (NFC) interface, and the like.

[0201] In one embodiment of the present specification, the above components of the computing device 500 and Figure 5 Other components not shown in the figure may also be connected to each other, for example, via a bus. Figure 5 The computing device structure block diagram shown is for illustrative purposes only and is not intended to limit the scope of this specification. Those skilled in the art may add or replace other components as needed.

[0202] Computing device 500 can be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., a tablet computer, a personal digital assistant, a laptop computer, a notebook computer, a netbook computer, etc.), a mobile phone (e.g., a smartphone), a wearable computing device (e.g., a smartwatch, smart glasses, etc.), or other types of mobile devices, or a stationary computing device such as a desktop computer or PC. Computing device 500 can also be a mobile or stationary server.

[0203] The processor 520 is configured to execute the following computer-executable instructions, which implement the steps of the above-mentioned device management method when executed by the processor.

[0204] The above is a schematic solution of a computing device of this embodiment. It should be noted that the technical solution of the computing device and the technical solution of the above-mentioned device management method are of the same concept. For details not described in detail in the technical solution of the computing device, please refer to the description of the technical solution of the above-mentioned device management method.

[0205] An embodiment of the present specification further provides a computer-readable storage medium storing computer-executable instructions, which implement the steps of the above-mentioned device management method when executed by a processor.

[0206] The above is a schematic diagram of a computer-readable storage medium of this embodiment. It should be noted that the technical solution of the storage medium and the technical solution of the above-mentioned device management method are based on the same concept. For details not described in detail in the technical solution of the storage medium, please refer to the description of the technical solution of the above-mentioned device management method.

[0207] An embodiment of the present specification further provides a computer program, wherein when the computer program is executed in a computer, the computer is caused to execute the steps of the above-mentioned device management method.

[0208] The above is an illustrative solution of a computer program of this embodiment. It should be noted that the technical solution of the computer program and the technical solution of the above-mentioned device management method are of the same concept. For details not described in detail in the technical solution of the computer program, please refer to the description of the technical solution of the above-mentioned device management method.

[0209] The foregoing description of this specification describes specific embodiments. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0210] The computer instructions include computer program code, which may be in source code form, object code form, executable file, or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal, and software distribution medium, etc. It should be noted that the content contained in the computer-readable medium may be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electric carrier signals and telecommunication signals.

[0211] It should be noted that for the aforementioned method embodiments, for the sake of simplicity of description, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the embodiments of this specification are not limited by the order of the actions described, because according to the embodiments of this specification, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in this specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the embodiments of this specification.

[0212] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0213] The preferred embodiments disclosed above are intended only to help illustrate this specification. The optional embodiments do not exhaustively describe all details, nor do they limit the invention to the specific embodiments described. Obviously, many modifications and variations can be made based on the content of the embodiments of this specification. This specification selects and specifically describes these embodiments in order to better explain the principles and practical applications of the embodiments of this specification, so that those skilled in the art can better understand and utilize this specification. This specification is limited only by the claims and their full scope and equivalents.

Claims

1. A device management method, applied to a device to be managed, comprising: In response to the device management instruction, a charging control instruction is sent to a target device storage unit in the device management cabinet, wherein the device to be managed is stored in the target device storage unit; Receiving an execution result generated by executing the charging control instruction by the target device storage unit; Determining a charging event sequence generated by the device to be managed based on the execution result; Comparing the charging event sequence with the execution result, and determining the storage status of the device to be managed based on the comparison result, wherein comparing the charging event sequence with the execution result and determining the storage status of the device to be managed based on the comparison result includes: comparing the event start time of the target event in the charging event sequence with the execution time corresponding to the execution of the target instruction by the storage unit of the target device, and determining the storage status of the device to be managed based on the comparison result, the target event includes a charging event and a disconnect charging event, the target instruction includes a start charging instruction and a disconnect charging instruction, and the storage status includes successfully placing the device into the storage unit of the target device and unsuccessfully placing the device into the storage unit of the target device; The device identification and the storage status of the device to be managed are sent to the client, wherein the client generates borrowing and returning information of the device to be managed according to the device identification and the storage status.

2. The device management method according to claim 1, wherein the step of sending a charging control instruction to a target device storage unit in the device management cabinet comprises: A first Bluetooth communication link is established with a target device storage unit in the device management cabinet, and a charging control instruction is sent to the target device storage unit through the first Bluetooth communication link.

3. The device management method according to claim 1, wherein receiving the execution result generated by the target device storage unit executing the charging control instruction comprises: Receiving a first execution result generated by executing a start charging instruction by a storage unit of the target device; and / or, Receiving a second execution result generated by the target device storage unit executing the disconnect charging instruction; Accordingly, determining a charging event sequence generated by the device to be managed based on the execution result includes: Obtaining a charging event generated by the device to be managed based on the first execution result; and / or, Obtaining a charging disconnection event generated by the device to be managed based on the second execution result; A charging event sequence is constructed based on event information corresponding to the charging event and / or the charging disconnection event.

4. The device management method according to claim 1 or 3, wherein comparing the charging event sequence with the execution result and determining the storage status of the device to be managed based on the comparison result comprises: comparing a first event start time of a charging event in the charging event sequence with a first execution time corresponding to a start charging instruction executed by a storage unit of a target device; If it is determined according to the comparison result that the difference between the start time of the first event and the first execution time is less than a preset time threshold, determining that the storage status of the device to be managed is successfully placed in the storage unit of the target device; and / or, comparing a second event start time of a disconnect charging event in the charging event sequence with a second execution time corresponding to execution of a disconnect charging instruction by a storage unit of a target device; If it is determined according to the comparison result that the difference between the second event start time and the second execution time is greater than or equal to a preset time threshold, it is determined that the storage status of the device to be managed is not successfully placed into the target device storage unit.

5. The device management method according to claim 1, further comprising: In response to the image acquisition instruction, calling the image acquisition component to acquire an image identification code corresponding to a first device storage unit in the device management cabinet, wherein the first device storage unit is one of a plurality of device storage units in the device management cabinet; The image identification code is parsed to obtain location information of the first device storage unit in the device management cabinet.

6. The device management method according to claim 5, further comprising: A first Bluetooth communication link is established with the first device storage unit according to the location information, and a charging control instruction is sent to the first device storage unit through the first Bluetooth communication link.

7. The device management method according to claim 1, wherein the step of sending the device identification and the storage status of the device to be managed to the client comprises: The device identification and the storage status of the device to be managed are sent to a cloud service platform, wherein the cloud service platform sends the device identification and the storage status to a client.

8. The device management method according to claim 2 or 6, further comprising: A second Bluetooth communication link is established with the electromagnetic lock. The first Bluetooth communication link, the second Bluetooth communication link, the communication link between the device to be managed and the cloud service platform, and the communication link between the cloud service platform and the client together constitute a Bluetooth auxiliary link.

9. The device management method according to claim 8, further comprising: Sending the charging status information of the target device storage unit, the charging status information of the device to be managed, the lock status data of the electromagnetic lock, the device identifier and the storage status to the client via the Bluetooth auxiliary link; Among them, the charging status information of the target device storage unit is transmitted by the target device storage unit to the device to be managed through the first Bluetooth communication link, and the lock status data is sent by the electromagnetic lock to the device to be managed through the second Bluetooth communication link. The device to be managed sends the charging status information of the target device storage unit, the charging status information of the device to be managed, the lock status data of the electromagnetic lock, the device identification and the storage status to the client through the communication link between the device and the cloud service platform, and the communication link between the cloud service platform and the client.

10. A device management apparatus, applied to a device to be managed, comprising: a sending module configured to send a charging control instruction to a target device storage unit in the device management cabinet in response to the device management instruction, wherein the device to be managed is stored in the target device storage unit; A receiving module configured to receive an execution result generated by the target device storage unit executing the charging control instruction; A determination module, configured to determine a charging event sequence generated by the device to be managed based on the execution result; a comparison module configured to compare the charging event sequence with the execution result, and determine the storage status of the device to be managed based on the comparison result, wherein the comparing the charging event sequence with the execution result and determining the storage status of the device to be managed based on the comparison result comprises: comparing the event start time of the target event in the charging event sequence with the execution time corresponding to the execution of the target instruction by the storage unit of the target device, and determining the storage status of the device to be managed based on the comparison result, the target event comprises a charging event and a charging disconnect event, the target instruction comprises a charging start instruction and a charging disconnect instruction, and the storage status comprises a successful placement into the storage unit of the target device and an unsuccessful placement into the storage unit of the target device; The processing module is configured to send the device identification and the storage status of the device to be managed to the client, wherein the client generates the borrowing and returning information of the device to be managed according to the device identification and the storage status.

11. A computing device comprising: memory and processor; The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions. When the computer-executable instructions are executed by the processor, the steps of the device management method according to any one of claims 1 to 9 are implemented.

12. A computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions, when executed by a processor, implement the steps of the device management method according to any one of claims 1 to 9.

13. A computer program product, characterized in that The device comprises computer instructions, which, when executed by a processor, implement the steps of the device management method according to any one of claims 1 to 9.

Images