Data processing method, device, equipment and storage medium for device management

Abstract

The present application discloses a data processing method, apparatus, device and storage medium for device management. The method includes: in response to a data processing instruction for a specified device, determining the type of the specified device and the usage requirement information for the specified device; determining the corresponding usage verification logic according to the type and usage requirement information; verifying the verification data according to the usage verification logic; when the verification result indicates a pass, generating consent information for the usage requirement information. The embodiments of the present application can be applied to various scenarios such as cloud technology, artificial intelligence, smart transportation, and assisted driving. The present application combines device type and usage requirements to perform fine-grained device usage management, which improves the efficiency and security of device management and the convenience of device use.

Description

Technical Field

[0001] The present application relates to the field of Internet communication technology, and in particular to a data processing method, apparatus, device and storage medium for device management. Background Art

[0002] With the rapid development of society and economy, the number of devices owned by entities represented by enterprises, universities, and research institutions has gradually increased, and therefore the equipment they own needs to be managed. In related technologies, equipment management mainly relies on manual work, such as manually recording equipment information. Even if an equipment management platform is introduced, equipment information is often entered manually. Such equipment management solutions have problems such as complex operations and cumbersome approval procedures in actual applications, which affects the efficiency of equipment management. Summary of the invention

[0003] In order to solve the problem of low efficiency of device management when the prior art is applied to device management, the present application provides a data processing method, apparatus, device and storage medium for device management:

[0004] According to a first aspect of the present application, a data processing method for device management is provided, the method comprising:

[0005] In response to a data processing instruction for a designated device, determining a type of the designated device and usage requirement information for the designated device;

[0006] Determine corresponding usage verification logic according to the type and the usage requirement information;

[0007] Verifying the data to be verified according to the usage verification logic; wherein the data to be verified is used to indicate at least one of the following: the designated device and an object associated with the use of the designated device, the data to be verified is provided by a target data provider, and the target data provider includes at least one determined from the designated device and the object based on the usage verification logic;

[0008] When the verification result indicates pass, consent information for the usage requirement information is generated.

[0009] According to a second aspect of the present application, a data processing apparatus for device management is provided, the apparatus comprising:

[0010] A response module: used for responding to a data processing instruction for a specified device, determining the type of the specified device and usage requirement information for the specified device;

[0011] Logic determination module: used to determine the corresponding usage verification logic according to the type and the usage requirement information;

[0012] Verification module: used for verifying the data to be verified according to the usage verification logic; wherein the data to be verified is used to indicate at least one of the following: the designated device and an object associated with the use of the designated device, the data to be verified is provided by a target data provider, and the target data provider includes at least one determined from the designated device and the object based on the usage verification logic;

[0013] A consent information generation module is used to generate consent information for the usage requirement information when the verification result indicates a pass.

[0014] According to a third aspect of the present application, an electronic device is provided, comprising a processor and a memory, wherein the memory stores at least one instruction or at least one program, and the at least one instruction or the at least one program is loaded and executed by the processor to implement the data processing method for device management as described in the first aspect.

[0015] According to the fourth aspect of the present application, a computer-readable storage medium is provided, in which at least one instruction or at least one program is stored, and the at least one instruction or the at least one program is loaded and executed by a processor to implement the data processing method for device management as described in the first aspect.

[0016] According to a fifth aspect of the present application, a computer program product or a computer program is provided, the computer program product or the computer program comprising computer instructions, the computer instructions being stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the data processing method for device management as described in the first aspect.

[0017] The data processing method, device, equipment and storage medium for device management provided by the present application have the following technical effects:

[0018] This application responds to the data processing instruction for the specified device, determines the type of the specified device and the usage requirement information for the specified device; then, determines the corresponding usage verification logic according to the type and usage requirement information; further, verifies the data to be verified according to the usage verification logic; finally, when the verification result indicates a pass, generates consent information for the usage requirement information. This application combines the device type and usage requirements to perform fine-grained device usage management, which improves the efficiency, security and convenience of device management. The corresponding usage verification logic is determined by using the type of the specified device and the usage requirement information for the specified device, and the data to be verified is determined by using the usage verification logic, which enriches the usage verification logic and the data to be verified in different device usage scenarios, and improves the efficiency and adaptability of device usage management. In this way, the status of related equipment can be effectively monitored, and the risks of equipment loss, equipment theft, and equipment being used in violation of regulations can be reduced, thereby improving the security of the equipment itself. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the technical solutions and advantages in the embodiments of the present application or the prior art, the drawings required for use in the embodiments or the prior art descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0020] Figure 1 is a schematic diagram of an application environment provided by an embodiment of the present application;

[0021] Figure 2 It is a flowchart of a data processing method for device management provided by an embodiment of the present application;

[0022] Figure 3 This is a flowchart of determining the corresponding usage verification logic according to the type and usage requirement information provided by the embodiment of the present application;

[0023] Figure 4 This is a schematic diagram of a process for determining the first type of verification information provided in an embodiment of the present application;

[0024] Figure 5 It is a schematic diagram of the use scenarios of various devices provided in the embodiments of the present application;

[0025] Figure 6 It is a schematic diagram of the architecture of the device management system provided in the embodiment of the present application;

[0026] Figure 7 is a schematic diagram of an overview of a device management system provided in an embodiment of the present application;

[0027] Figure 8 is a schematic diagram of the architecture of a mobile terminal provided in an embodiment of the present application;

[0028] Fig. 9 It is a schematic diagram of the architecture and application of the radio frequency identification technology provided by the embodiment of the present application;

[0029] Fig.10 It is a schematic diagram of verification requirements of different devices in different device usage scenarios provided by an embodiment of the present application;

[0030] Fig.11 It is a schematic diagram of the technical solutions related to the functional modules in the enterprise equipment management system provided by the embodiment of the present application;

[0031] Figure 12-14 This is a diagram of an administrator side interface of an enterprise device management system provided by an embodiment of the present application;

[0032] Figure 15-17 This is a diagram of an employee side interface of an enterprise equipment management system provided by an embodiment of the present application;

[0033] Fig.18 It is a block diagram of a data processing device for device management provided by an embodiment of the present application;

[0034] Fig.19 It is a structural schematic diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0035] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0036] It should be noted that the terms "including" and "having" and any variations thereof in the specification and claims of this application and the above-mentioned drawings are intended to cover non-exclusive inclusions. For example, a process, method, system, product or server that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0037] Before further describing the embodiments of the present application in detail, the nouns and terms involved in the embodiments of the present application are explained. The nouns and terms involved in the embodiments of the present application are subject to the following interpretations.

[0038] Raspberry Pi: Raspberry Pi, which is designed for learning computer programming education), is a microcomputer the size of a credit card.

[0039] OCR (Optical Character Recognition): Optical character recognition.

[0040] RFID (Radio Frequency Identification): Radio Frequency Identification.

[0041] Gateway: Gateway.

[0042] RPC (Remote Procedure Call): Remote procedure call.

[0043] ffmpeg (Fast Forward Mpeg): It is a set of open source computer programs that can be used to record, convert digital audio and video, and convert them into streams.

[0044] OpenCV: It is a cross-platform computer vision and machine learning software library.

[0045] DBN (Deep Belief Network): Deep Belief Network.

[0046] CNN (Convolutional Neural Networks): Convolutional Neural Networks.

[0047] CTPN algorithm: a text detection algorithm.

[0048] CRNN (Convolutional Recurrent Neural Network): Convolutional Recurrent Neural Network.

[0049] R-CNN (Region-CNN) algorithm: an algorithm that applies deep learning to object detection.

[0050] LSTM (Long Short-Term Memory): Long short-term memory network.

[0051] CTC (Connectionist Temporal Classification) algorithm: It is an algorithm commonly used in speech recognition, text recognition and other fields to solve the problem of different lengths of input and output sequences and inability to align them.

[0052] Redis (Remote Dictionary Server): remote dictionary service.

[0053] Docker: An open source application container engine.

[0054] K8s: Full name Kubernetes, is an open source system for automatically deploying, scaling, and managing containerized applications. The system aims to provide a "platform for automatically deploying, scaling, and running application containers across host clusters." It supports a range of container tools, including Docker.

[0055] JavaScript: A lightweight, interpreted or just-in-time compiled programming language with a function-first approach.

[0056] Vue: It is a progressive JavaScript framework for building user interfaces.

[0057] Spring MVC: It is a "Model-View-Controller" framework for the Web layer.

[0058] HTTP (Hyper Text Transfer Protocol): Hypertext Transfer Protocol.

[0059] Nginx: is a high-performance HTTP and reverse proxy web server

[0060] Slotted ALOHA algorithm: It is a commonly used anti-collision algorithm in RFID systems.

[0061] See also Figure 1 , Figure 1 It is a schematic diagram of an application environment provided by an embodiment of the present application, and the application environment may include a client 10 and a server 20. The client 10 and the server 20 may be directly or indirectly connected via wired or wireless communication. Relevant objects (such as users, simulators) may send data processing instructions for a specified device to the server 20 via the client 10. The server 20 determines the type of the specified device and the usage requirement information for the specified device based on the received data processing instructions; then determines the corresponding usage verification logic based on the type and the usage requirement information; and then verifies the verification data according to the usage verification logic. If the verification result indicates a pass, then generates consent information for the usage requirement information. It should be noted that Figure 1 Just an example.

[0062] The client 10 may be a physical device such as a smart phone, a computer (such as a desktop computer, a tablet computer, a laptop computer), an augmented reality (AR) / virtual reality (VR) device, a digital assistant, an intelligent voice interaction device (such as an intelligent speaker), an intelligent wearable device, an intelligent home appliance, a vehicle-mounted terminal, etc., or may be software running in a physical device, such as a computer program. The operating system corresponding to the client 10 may be an Android system (Android system), an iOS system (a mobile operating system developed by Apple), a Linux system (an operating system), a Microsoft Windows system (Microsoft Windows operating system), etc.

[0063] The server end 20 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. The server can include a network communication unit, a processor, a memory, etc. The server end can provide background services for the corresponding client.

[0064] In practical applications, the client 10 and the server 20 can be used to build a device management system. The device management system can be used to manage devices owned by enterprises, universities, research institutions, etc. The devices managed by the device management system can be physical devices, which can be smart phones, computers (such as desktop computers, tablet computers, laptops), augmented reality / virtual reality devices, digital assistants, intelligent voice interaction devices (such as smart speakers), smart wearable devices, smart home appliances, vehicle terminals, physical servers, etc.

[0065] The data processing scheme for device management provided in the embodiment of the present application can be used in the technology of computer vision (CV). Computer vision is a science that studies how to make machines "see". To put it more concretely, it refers to the use of cameras and computers to replace human eyes to identify and measure targets, and further do graphic processing to make computer processing into images that are more suitable for human eye observation or transmission to instrument detection. As a scientific discipline, computer vision studies related theories and technologies, and attempts to establish an artificial intelligence system that can obtain information from images or multidimensional data. Computer vision technology generally includes image processing, image recognition, image semantic understanding, image retrieval, OCR, video processing, video semantic understanding, video content / behavior recognition, three-dimensional object reconstruction, 3D technology, virtual reality, augmented reality, synchronous positioning and map construction, automatic driving, smart transportation and other technologies, as well as common biometric recognition technologies such as face recognition and fingerprint recognition.

[0066] It should be noted that for the data to be verified that is associated with user information, when the embodiments of the present application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards of relevant countries and regions.

[0067] The following describes a specific embodiment of a data processing method for device management in the present application. Figure 2 It is a flow chart of a data processing method for device management provided by an embodiment of the present application. The present application provides method operation steps as described in the embodiment or flow chart, but more or fewer operation steps may be included based on conventional or non-creative labor. The order of steps listed in the embodiment is only one way of executing the steps among many orders, and does not represent the only execution order. When the actual system or product is executed, it can be executed in sequence or in parallel according to the method shown in the embodiment or the accompanying drawings (for example, in a parallel processor or multi-threaded processing environment). The data processing method for device management provided by an embodiment of the present invention can be executed independently by the client, can be executed independently by the server, or can be executed by the interaction between the client and the server. Specifically, Figure 2 As shown, the method may include:

[0068] S201: In response to a data processing instruction for a designated device, determining the type of the designated device and usage requirement information for the designated device;

[0069] In an embodiment of the present application, in response to a data processing instruction for a specified device, a client or a server determines the type of the specified device and the usage requirement information for the specified device. The data processing instruction may carry a device identifier indicating the specified device, and the client or the server may determine the specified device according to the device identifier indicating the specified device, and then determine the type of the specified device based on the preset device type information. The preset device type information records the type of each device in the device pool, wherein the device pool is composed of a plurality of managed devices. The type of each device in the device pool may be determined based on at least one classification rule, and accordingly, each device in the device pool may have at least one type, and the type of the specified device may also have at least one type. The at least one classification rule may include a classification rule indicating the manufacturer of the device, a classification rule indicating the service life of the device, a classification rule indicating the frequency of use of the device, a classification rule indicating the unit price of the device, and the like. The data processing instruction may carry the usage requirement information for the specified device, and the client or the server may determine the usage requirement information for the specified device by reading the data processing instruction. The usage requirement information may indicate borrowing, returning, lending, and use outside the preset range (take-out), wherein borrowing may also be subdivided into ordinary borrowing and renewal.

[0070] The designated device can be a specific device or a specific type of device. For the former, the device identifier can be a more targeted device number; for the latter, the device identifier can be a device name or device model with a certain degree of distinction. Of course, the designated device can also be a specific number of devices.

[0071] Exemplarily, in order to ensure the effectiveness of the equipment inventory, the designated device in the return scenario is a specific device. Of course, the designated device can also be a specific device. In the ordinary borrowing scenario, the designated device can be a specific device (several) or a specific type of device. Further, taking the enterprise equipment management system as an example, employees can select the equipment to be borrowed in the warehouse, and then, while carrying the equipment to be borrowed, the employee triggers the generation of data processing instructions through the terminal interface set at the door of the warehouse (the terminal belongs to the enterprise equipment management system). At this time, the designated device is the equipment to be borrowed, and the designated device is a specific device (several). After the system agrees, the employee takes the equipment to be borrowed out of the warehouse for use. Employees can also select the equipment to be borrowed through the interface of the application installed on the smart phone (the application belongs to the enterprise equipment management system) to trigger the generation of data processing instructions. The equipment to be borrowed can be a specific device (several) or a specific type of equipment. Correspondingly, the designated device can be a specific device (several) or a specific type of equipment. After the system agrees, employees can go to the equipment pick-up point to pick up the equipment to be borrowed.

[0072] In actual applications, for enterprise equipment management, the equipment managed by the enterprise equipment management system is generally public equipment. The types of equipment can be divided into important equipment types and ordinary (general) equipment types. Equipment belonging to the important equipment type can be a new model development and testing machine. Whether the equipment belongs to the important equipment type or the ordinary equipment type can be determined by comprehensive consideration of the importance and confidentiality of the equipment. Figure 12-14 The administrator side interface of the enterprise equipment management system is shown. Fig.12 The home page interface is shown. Fig.13 The interface of the device list is shown. Fig.14 Shows the interface for modifying device information. Figure 15-17 The employee side interface diagram of the enterprise equipment management system is shown. Fig.15 The interface of the device list is shown. Fig.16 An interface showing detailed information about the device. Fig.17 An interface related to a device borrowing scenario is shown.

[0073] S202: Determine corresponding usage verification logic according to the type and the usage requirement information;

[0074] In an embodiment of the present application, the client or server determines the corresponding use verification logic according to the type and use requirement information. The embodiment of the present application provides different use verification logics for different device use scenarios. It can be understood that the device use scenario is obtained based on the two elements of device type and use requirement, and different combinations of device type and use requirement indicate different device use scenarios. Introducing different use verification logics for different device use scenarios can improve the fine-grainedness and flexibility of device use management, and can avoid the security risks and inefficiency brought by the use verification logic. For example, if a use verification logic for the scenario of taking important equipment is used, the verification links involved in the use verification logic may be more, so it is too troublesome for the scenario of returning ordinary equipment; on the contrary, if a use verification logic for the scenario of returning ordinary equipment is used, the verification links involved in the use verification logic may be less, so there are security risks for the scenario of taking important equipment. For the use verification logic, it needs to indicate the composition of the data to be verified, and when there are at least two data to be verified, it is also necessary to indicate the verification order. At the same time, it also needs to indicate the condition of "the verification result indicates pass".

[0075] The following will take usage requirement information as the starting point to introduce the usage verification logic corresponding to different device usage scenarios:

[0076] 1) Use demand information to indicate borrowing or returning:

[0077] When the usage requirement information indicates borrowing or returning, determining the type of the designated device and the usage requirement information for the designated device includes: determining the object level of the designated object, the type of the designated device and the usage requirement information for the designated device; wherein the designated object is an object that is using or applying to use the designated device.

[0078] Correspondingly, such as Figure 3 As shown, the determining of the corresponding usage verification logic according to the type and the usage requirement information includes:

[0079] S301: Determine, according to the object level and the type of the specified object, first type of verification information indicating the scope of the object involved in the data to be verified;

[0080] S302: Determine, according to the type and the usage requirement information, second type verification information indicating data items involved in the data to be verified;

[0081] S303: Obtain corresponding usage verification logic based on the first type of verification information and the second type of verification information.

[0082] The “type of the designated device” and “the usage requirement information for the designated device” can refer to the relevant records in the aforementioned step S201, and will not be repeated here. The designated object is the object that is using or applying to use the designated device. When the usage requirement information indicates borrowing, the designated object is the object that applies to use the designated device, that is, the object that is to have the right to use the designated object. When the usage requirement information indicates return, the designated object is the object that is using the designated device, that is, the object that is to lose the right to use the designated object. The designated object can be determined according to the object identifier carried by the data processing instruction. The object level of the designated object can be determined based on preset object level information. The preset object level information records the object level of each object in the object pool, where the object pool is composed of multiple objects with the right to use the device service. The object level of each object in the object pool can be determined based on a preset grading rule, and the object level of the designated object can be one of the first level, the second level, ..., and the N level, where N can be greater than or equal to 2 and the N level is lower than the N-1 level. For enterprise equipment management, the object here can indicate an employee or an employee account, such as an employee account in an enterprise equipment management system. Accordingly, the object level can be determined based on factors such as the employee's position, post, and job within the enterprise.

[0083] For the use verification logic, one of its functions is to indicate the composition of the data to be verified. Here, when determining the use verification logic, it is refined from the perspective of the composition of the data to be verified. The object range involved in the data to be verified is determined by the object level of the specified object and the type of the specified device, and the data items involved in the data to be verified are determined by the type of the specified device and the use requirement information for the specified device. The embodiment of the present application combines the object level of the specified object and the type of the specified device to determine the contribution object of the data to be verified. It may not be limited to the specified object itself, and may be selected or even not selected from the objects (including the specified object) that have an association relationship with the use of the specified device, thereby improving the scene adaptability of determining the contribution object of the data to be verified. Combining the type of the specified device and the use requirement information for the specified device to determine the contribution data items of the data to be verified, it can be used to clarify the data items in which the contribution object participates, and it can also clarify the data items in which the specified device participates, further improving the composition granularity of the data to be verified so as to facilitate expansion for the use scenario of the newly added device. Generally speaking, when the contribution object is not selected from the object that has an association relationship with the use of the specified device, the contribution data item does not involve the participation of the object.

[0084] In an exemplary embodiment, Figure 4 As shown, when the usage requirement information indicates borrowing, the first type of verification information indicating the scope of objects involved in the data to be verified is determined according to the object level and the type of the specified object, including:

[0085] S401: According to a first preset rule, determining whether the object level of the specified object matches the belonging type;

[0086] S402: When the object level of the specified object does not match the belonging type, determine the associated object corresponding to the specified object, and generate a first type of verification information for the specified object and the associated object; wherein, the object level of the specified object does not match the belonging type indicates that the object level of the specified object is lower than the lower limit of the object level corresponding to the belonging type, and the object level of the associated object is higher than the object level of the specified object.

[0087] The first preset rule records at least one matching object level-equipment type relationship. If the object level of the specified object and the type of the specified equipment satisfy any one of the relationships in the first preset rule, then the object level of the specified object matches the type of the specified equipment, otherwise they do not match. Exemplarily, for enterprise equipment management, if the matching object level-equipment type relationship indicates level two and ordinary equipment types, then it means that level two is the lower limit of the level for independent borrowing of ordinary equipment, and only employees above level two can independently borrow ordinary equipment, that is, employees below level three cannot independently borrow ordinary equipment. If the matching object level-equipment type relationship indicates level one and important equipment types, then it means that level one is the lower limit of the level for independent borrowing of important equipment, and only level one employees can independently borrow important equipment, that is, employees below level two cannot independently borrow important equipment.

[0088] When the object level of the specified object does not match the type of the specified device, the embodiment of the present application determines the specified object and the associated object from the objects that have an associated relationship with the use of the specified device as the contributing objects of the data to be verified, while focusing on the specified object itself, introducing the associated object with an object level higher than the specified object, and flexibly and effectively introducing assistance for the specified object to realize the borrowing of the specified device. Of course, when the object level of the specified object matches the type of the specified device, it is no longer necessary to determine the associated object corresponding to the specified object, and directly generate the first type of verification information for the specified object.

[0089] In addition, since the aforementioned step S201 mentions that "each device in the device pool may have at least one type, and the specified device may also have at least one type", it can be understood that the M classification rules correspond to a device type set respectively, that is, M device type sets. The first preset rule can be determined based on the M device type sets. When there are at least two types of the specified device, there may be at least two candidate relationships in the first preset rule. If at least two candidate relationships are satisfied, the object level of the specified object matches the type of the specified device, otherwise it does not match. This can improve the security of device management.

[0090] In an exemplary embodiment, determining the second type of verification information indicating the data items involved in the data to be verified based on the type and the usage requirement information may include the following steps: determining the second type of verification information matching the type based on a second preset rule; wherein the second preset rule records preset data items to be verified corresponding to different device types, and the preset data items to be verified include device label items related to the specified device and specified identity data items, and the specified identity data items indicate an object that has an association relationship with the use of the specified device.

[0091] The second preset rule records at least one matching device type-preset data item to be verified relationship. When the type of the specified device is known, the same device type can be determined in the second preset rule, and then the preset data item to be verified corresponding to the same device type can be determined, thereby obtaining the second type of verification information. The second preset rule can be used to quickly determine the contributing data items of the data to be verified, thereby improving the efficiency of the determination of the verification logic. It should be noted that, for "the preset data items to be verified include device label items related to the specified device and specified identity data items", it can be understood that under one relationship, it is clarified whether the device label item related to the specified device exists, and if it exists, it can be further clarified which type of label it is; and, under one relationship, it is clarified whether the identity data item exists, and if it exists, it can be further clarified what the specified identity data is, such as hand shape, fingerprint, face shape, iris, retina, pulse, signature, voice, walking gait and other biometric data, as well as the triggered instruction data. Further, the specified identity data can also cover objects that have an associated relationship with the use of the specified device, that is, to provide preferred identity data for global objects. The final composition of the data to be verified is a combination of the matching results of the aforementioned contribution objects and the "preferred identity data of the global object", as well as the "device tag items related to the specified device".

[0092] In addition, since the aforementioned step S201 mentions that "each device in the device pool may have at least one type, and the specified device may also have at least one type", it can be understood that the M classification rules correspond to a device type set, that is, M device type sets. The second preset rule can be determined based on the M device type sets. When there are at least two types of the specified device, at least two relationships in the second preset rule can be hit. If the preset data items to be verified indicated by at least two relationships are different, their union can be taken as the second type of verification information to improve the security of device management.

[0093] 2) Use demand information to indicate loan:

[0094] When the usage requirement information indicates lending, the determining of the corresponding usage verification logic according to the belonging type and the usage requirement information may include the following steps: first, determining a first object and a second object, and generating a third type of verification information for the first object and the second object; wherein the first object is an object that is using the designated device, and the second object is an object that applies to use the designated device, and the third type of verification information indicates a range of objects involved in the data to be verified; then, determining a fourth type of verification information matching the belonging type based on a second preset rule; wherein the second preset rule records preset data items to be verified corresponding to different device types, and the preset data items to be verified include device label items related to the designated device and specified identity data items, and the specified identity data items indicate objects that have an association relationship with the use of the designated device; further, obtaining the corresponding usage verification logic based on the third type of verification information and the fourth type of verification information.

[0095] Compared to the one object involved in borrowing and returning, lending involves two objects, including a first object that is using the designated device and a second object that applies to use the designated device. The first object is the object that is to lose the right to use the designated object, that is, the lender. The second object is the object that is to have the right to use the designated object, that is, the borrower. Please refer to the relevant records of "first type of verification information" in "1) Usage demand information indicates borrowing or returning". Here, considering the scenario characteristics of the loaned device, the first object and the second object are determined from the objects that have an association with the use of the designated device as the contributing objects of the data to be verified, which is more scenario-adaptive. Compared with only the lender or the borrower as the contributing object of the data to be verified, this can better ensure the security of equipment management. If only the lender is the contributing object of the data to be verified, there may be a situation where the borrower has the right to use the damaged device without knowing it. At the same time, you can refer to the relevant records of "second type of verification information" and "second preset rules" in "1) usage demand information indicating borrowing or returning" to realize the determination of the contribution data items of the data to be verified, and together with the contribution objects of different dimensions, ensure the scenario adaptability of the verification logic.

[0096] 3) Usage requirement information indicates use outside the preset range (take-away):

[0097] When the usage requirement information indicates usage outside a preset range, determining the corresponding usage verification logic based on the belonging type and the usage requirement information may include the following steps: first, determining a management object, and generating a fifth type of verification information for the management object; wherein the management object is an object having the device management authority, and the fifth type of verification information indicates the range of objects involved in the data to be verified; then, determining a sixth type of verification information matching the belonging type based on a second preset rule; wherein the second preset rule records preset data items to be verified corresponding to different device types, and the preset data items to be verified include device label items related to the specified device and specified identity data items, and the specified identity data items indicate objects that have an association with the use of the specified device; further, obtaining the corresponding usage verification logic based on the fifth type of verification information and the sixth type of verification information.

[0098] Generally speaking, the use of equipment needs to be limited within a preset range, so that the safety of the equipment can be maintained more effectively. Therefore, considering the security risks that may be caused by use outside the preset range, the management object is determined here from the objects that have an associated relationship with the use of the specified device as the contributing object of the data to be verified. As an object with device management authority, the management object's feedback on whether a specific device can be taken out is more timely and flexible. Please refer to the relevant records of "first type of verification information", "second type of verification information" and "second preset rule" in "1) Usage demand information indicating borrowing or returning". The embodiment of the present application provides a more fine-grained method for determining the use verification logic for the scenario of taking out devices, which can provide reliable protection for the security of device management.

[0099] S203: Verify the data to be verified according to the usage verification logic; wherein the data to be verified is used to indicate at least one of the following: the designated device and an object associated with the use of the designated device, and the data to be verified is provided by a target data provider, and the target data provider includes at least one determined from the designated device and the object based on the usage verification logic;

[0100] In an embodiment of the present application, the client or server verifies the data to be verified according to the use verification logic. Combined with the record in the aforementioned step S203, one of the functions of the use verification logic is to indicate the composition of the data to be verified and to indicate the target data provider that provides the data to be verified. Then, the use verification logic can be used to guide the specified object and / or the object associated with the use of the specified device to provide the data to be verified, that is, based on the use verification logic, at least one is determined as the target data provider from the specified device and the object associated with the use of the specified device. Exemplarily, if the use verification logic indicates that the composition of the data to be verified requires the facial data of object A and indicates that object A is the target data provider, then object A can be guided to provide the corresponding facial data. The provided facial data may be ideal data that meets the requirements (data that matches the standard facial data of object A pre-stored on the client or server), or it may be defective data that does not meet the requirements (such as facial data of object A that is blocked by the existence of object A), or even irrelevant data that does not meet the requirements (such as facial data of object B).

[0101] In an exemplary embodiment, when the usage verification logic indicates that the data to be verified is the return information of the device tag corresponding to the specified device, and there are currently multiple device tags to be verified, the multiple device tags to be verified respectively correspond to different devices. Before verifying the data to be verified according to the usage verification logic, the method also includes the following steps: using a preset time slot algorithm to obtain the return information of the device tag and the return information corresponding to the multiple device tags to be verified, so as to verify the relevant return information.

[0102] Considering the possible tag collision problem in the scenario where the device tag and multiple device tags to be tested coexist, a preset time slot algorithm can be used to capture the return information of these tags, so as to ensure that the return information of these tags is effectively captured, thereby improving the efficiency and security of device management. Exemplarily, the device tag and the device tag to be tested can be RFID tags, or even tear-proof RFID tags (which can improve the reliability of device data) and positioning RFID tags (which can be used for important equipment). In some equipment usage scenarios, the composition of the data to be verified can be only the return information of the device tag. Taking the enterprise equipment management system as an example, 1) employees can select the designated equipment to be borrowed in the warehouse, and then the employees can use the terminal set at the door of the warehouse to perform tag identification to realize equipment borrowing while carrying the designated equipment. The terminal can use the time slot ALOHA algorithm to first send a specified frame length (that is, the number of time slots) to send instructions. These tags randomly select a time slot within the frame length range to respond to the instruction and return an information packet. Among them, the time slot in which only one tag returns an information packet is called a successful time slot; the time slot in which no tag returns an information packet is called an empty time slot; the time slot in which at least two tags return an information packet is called a collision time slot, and the tags that collide will continue to try in the next frame. The time slot ALOHA algorithm also indicates that the number of these tags should be estimated based on the feedback of the previous frame (i.e., the number of observed collision time slots, the number of empty time slots, and the number of successful time slots), and the frame length should be updated accordingly. Accordingly, the terminal sends instructions with the updated frame length until all tags in the terminal's working area are identified. 2) The administrator can carry the terminal and use the terminal to conduct an inventory of equipment in the warehouse and an inventory of equipment within a preset range that limits the use of equipment. At this time, the process of using the terminal to conduct an inventory of equipment can refer to the content of the time slot ALOHA algorithm in 1) above.

[0103] S204: When the verification result indicates pass, generate consent information for the usage requirement information.

[0104] In an embodiment of the present application, when the verification result indicates a pass, the client or server generates consent information for the usage requirement information. In combination with the device usage scenario in the aforementioned step S202, when the usage requirement information indicates borrowing, consent to borrow information is generated so that the specified object has the right to use the specified object. When the usage requirement information indicates return, consent to return information is generated so that the specified object no longer has the right to use the specified object. When the usage requirement information indicates lending, consent to lending information is generated so that the first object no longer has the right to use the specified object and the second object has the right to use the specified object. When the usage requirement information indicates use outside the preset scope, consent to use outside the preset scope information is generated so that the specified object has the right to use the specified object outside the preset scope.

[0105] In practical applications, please refer to Figure 5 , for enterprise equipment management systems:

[0106] 1) In the equipment borrowing scenario

[0107] 1.1) If Level 2 employee A applies to borrow common device 1, and Level 2 matches the common device type, then the contribution object of the data to be verified is Level 2 employee A; at the same time, through "borrowing" and "common device type", it is determined that the contribution data item of the data to be verified is the device tag item related to common device 1. Correspondingly, the data to be verified is the return information of the device tag of common device 1. If the terminal affiliated to the enterprise equipment management system recognizes the device tag of common device 1, Level 2 employee A successfully borrows common device 1.

[0108] 1.2) If the second-level employee A applies to borrow important equipment 2, and the second level does not match the important equipment type, then the contribution objects of the data to be verified are the second-level employee A and the first-level employee B (the superior of the second-level employee A); at the same time, through "borrowing" and "important equipment type", it is determined that the contribution data items of the data to be verified are the equipment label items related to the important equipment 2 and the specified identity data items. Correspondingly, the data to be verified are the return information of the equipment label of the important equipment 2, the instruction data triggered by the first-level employee B (for the application for borrowing important equipment 2 sent by the second-level employee A), and the face data of the second-level employee A. If the instruction data triggered by the first-level employee B indicates confirmation (agreement), and the face data provided by the second-level employee A matches the pre-stored standard face data, and the terminal affiliated to the enterprise equipment management system recognizes the equipment label of the important equipment 2, then the second-level employee A successfully borrows the important equipment 2, and the first-level employee B and the second-level employee A are jointly responsible for the important equipment 2 during the borrowing period. It should be noted that if the instruction data triggered by the first-level employee B indicates non-confirmation (agreement), then there is no need to verify the face data and equipment label. In other words, only if the instruction data triggered by the first-level employee B indicates confirmation (agreement), the second-level employee A can go to the warehouse to borrow important equipment 2. In this process, the terminal set at the warehouse door can be used for tag recognition and face recognition.

[0109] 1.3) If first-level employee B applies to borrow important equipment 2, and the first level matches the type of important equipment, then the contributing object of the data to be verified is first-level employee B; at the same time, through "borrowing" and "important equipment type", it is determined that the contributing data items of the data to be verified are the equipment label items related to important equipment 2 and the specified identity data items. Correspondingly, the data to be verified is the return information of the equipment label of important equipment 2, and the facial data of first-level employee B. If the facial data provided by first-level employee B matches the pre-stored standard facial data, and the terminal belonging to the enterprise equipment management system recognizes the equipment label of important equipment 2, then first-level employee B successfully borrows important equipment 2. In addition, the process of first-level employee B applying to borrow ordinary equipment 1 can refer to 1.1) and will not be repeated.

[0110] 1.4) Renewal: The borrowing period of ordinary equipment is generally longer than that of important equipment. If the borrowing period is about to expire, you can apply for renewal. You can directly apply for renewal of ordinary equipment online. For renewal of important equipment, you need to return the equipment first, and then the administrator will check the equipment, and then (assuming that the equipment is not damaged, etc.) renew the loan through the above-mentioned process of applying for borrowing important equipment.

[0111] 2) In the device return scenario

[0112] 2.1) Combined with 1.1), if the second-level employee A applies to return the common device 1, if the terminal belonging to the enterprise equipment management system recognizes the device tag of the common device 1, the second-level employee A successfully returns the common device 1.

[0113] 2.2) Combined with 1.2), if the second-level employee A applies to return the important equipment 2, if the facial data provided by the second-level employee A matches the pre-stored standard facial data, and the terminal belonging to the enterprise equipment management system recognizes the device tag of the important equipment 2, then the second-level employee A successfully returns the important equipment 2, and the system sends a notification to the first-level employee B that the important equipment 2 has been returned.

[0114] 2.3) Combined with 1.3), if the first-level employee B applies to return the important equipment 2, if the facial data provided by the first-level employee B matches the pre-stored standard facial data, and the terminal affiliated with the enterprise equipment management system recognizes the device tag of the important equipment 2, then the first-level employee B successfully returns the important equipment 2. In addition, the process of the first-level employee B applying to return the ordinary equipment 1 can refer to 2.1), which will not be repeated.

[0115] 2.4) Abnormal appeal: When the borrower returns the equipment, he / she needs to fill in the equipment status, whether it is damaged, etc. If the equipment is damaged, the reason for the damage needs to be filled in. For consumable equipment with a scrapping time limit, if the equipment is damaged or cannot be used when the borrower returns it because it is outside the scrapping time limit, then the borrower does not need to bear compensation liability. At the same time, when borrowing equipment, the borrower also needs to fill in the equipment status, whether it is damaged, etc. If the equipment is found to be damaged, it is necessary to file a complaint with the administrator in time. The administrator needs to investigate the cause of the damage to see if it is caused by management negligence or the previous borrower did not report the return of the equipment truthfully.

[0116] 3) In the equipment loan scenario

[0117] 3.1) If Level 2 employee C applies to borrow common equipment 1 from Level 2 employee A, the contribution object of the data to be verified is Level 2 employee A; at the same time, the contribution data item of the data to be verified is determined to be a specified identity data item through "borrowing" and "common equipment type". Correspondingly, the data to be verified is the instruction data triggered by Level 2 employee A (for the application to borrow common equipment 1 sent by Level 2 employee C). If the instruction data triggered by Level 2 employee A indicates confirmation (agreement), Level 2 employee C successfully borrows common equipment 1.

[0118] 3.2) If Level 2 employee C applies to borrow important equipment 2 from Level 2 employee A, then the contributing objects of the data to be verified are Level 2 employee A, Level 1 employee B, Level 2 employee C, and Level 1 employee D (Level 2 employee C's superior); at the same time, through "borrowing" and "important equipment type", it is determined that the contributing data items of the data to be verified are designated identity data items. Correspondingly, the data to be verified are the instruction data triggered by Level 2 employee A (for the application to borrow important equipment 2 sent by Level 2 employee C), the instruction data triggered by Level 1 employee B (for the application to borrow important equipment 2 sent by Level 2 employee A), the instruction data triggered by Level 1 employee D (for the application to borrow important equipment 2 sent by Level 2 employee C), the facial data of Level 2 employee A, and the facial data of Level 2 employee C. If the instruction data triggered by the second-level employee A, the first-level employee B, and the first-level employee D indicates confirmation (agreement), the facial data provided by the second-level employee A matches the pre-stored standard facial data and the facial data provided by the second-level employee C matches the pre-stored standard facial data, then the second-level employee C successfully borrows the important equipment 2, and the first-level employee D and the second-level employee C are jointly responsible for the important equipment 2 during the borrowing period.

[0119] In addition, the process of lending ordinary equipment between employees (including between first-level employees and between first-level employees and second-level employees) can refer to 3.1), which will not be repeated here. For the process of lending important equipment between employees, 3.2) can be used as a reference. The borrower and lender need to provide facial data; if the lender and / or borrower is a second-level employee, their superiors need to intervene.

[0120] 4) In the device take-away scenario

[0121] 4.1) If Level 2 employee A applies to bring in general device 1, the contributing object of the data to be verified is the administrator; at the same time, through "bring in" and "general device type", it is determined that the contributing data item of the data to be verified is a designated identity data item. Correspondingly, the data to be verified is the instruction data triggered by the administrator (for the application sent by Level 2 employee A to bring in general device 1). If the instruction data triggered by the administrator indicates confirmation (agreement), Level 2 employee A successfully brings in general device 1.

[0122] 4.2) If the second-level employee A applies to take away important equipment 2, then the contributing object of the data to be verified is the administrator; at the same time, the contributing data item of the data to be verified is determined to be a designated identity data item through "take away" and "important equipment type". Correspondingly, the data to be verified is the instruction data triggered by the administrator (for the application sent by the second-level employee A to take away important equipment 2), and the facial data of the second-level employee A. If the instruction data triggered by the administrator indicates confirmation (agreement), and the facial data provided by the second-level employee A matches the pre-stored standard facial data, then the second-level employee A successfully takes away the important equipment 2, and the system sends a notification to the first-level employee B that the important equipment 2 has been taken away.

[0123] It should be noted that if the verification result indicates failure, and the system detects that the relevant employees forcibly borrow, return, lend, or take away the relevant equipment, the system will trigger an alarm. Fig.10 The verification requirements of different devices in different device usage scenarios are shown, where general devices can correspond to the above-mentioned ordinary devices.

[0124] It can be seen from the technical solution provided by the above embodiment of the present application that the embodiment of the present application responds to the data processing instruction for the specified device, determines the type of the specified device and the usage requirement information for the specified device; then, determines the corresponding usage verification logic according to the type and the usage requirement information; further, verifies the data to be verified according to the usage verification logic; finally, when the verification result indicates a pass, generates consent information for the usage requirement information. The present application performs fine-grained device usage management based on the device type and usage requirements, thereby improving the efficiency, security and convenience of device management. The corresponding usage verification logic is determined by using the type of the specified device and the usage requirement information for the specified device, and the data to be verified is determined by using the usage verification logic, which realizes the enrichment of the usage verification logic and the data to be verified in different device usage scenarios, and improves the efficiency and adaptability of device usage management. In this way, the status of the relevant equipment can be effectively monitored, and the risks of equipment loss, equipment theft, and equipment being used in violation of regulations can be reduced, thereby improving the security protection of the equipment itself.

[0125] The present application also provides a data processing device for device management, such as Fig.18 As shown, the data processing device 180 for device management includes:

[0126] Responding module 1801: used to respond to a data processing instruction for a designated device and determine the type of the designated device and usage requirement information for the designated device;

[0127] Logic determination module 1802: used to determine corresponding usage verification logic according to the type and the usage requirement information;

[0128] Verification module 1803: used to verify the data to be verified according to the usage verification logic; wherein the data to be verified is used to indicate at least one of the following: the designated device and an object associated with the use of the designated device, the data to be verified is provided by a target data provider, and the target data provider includes at least one determined from the designated device and the object based on the usage verification logic;

[0129] The consent information generating module 1804 is used to generate consent information for the usage requirement information when the verification result indicates pass.

[0130] It should be noted that the device in the device embodiment and the method embodiment are based on the same inventive concept.

[0131] The present application also provides a data processing system for device management. Figure 6 , 7, the front end of the system uses the Vue framework. The back end of the system uses Spring MVC, and adds the API (application programming interface) Gateway for interface authentication, etc. At the same time, the corresponding access services can be implemented according to business functions. The system uses Nginx for load balancing. The server uses the MySQL (relational database management system) master-slave database, and uses cluster caching and distributed storage, and encapsulates it as a Docker container and deploys it on a cloud server. In addition, the system uses aspect-oriented programming to implement logging and permission control functions.

[0132] The system also includes a mobile terminal composed of an RFID reader and a Raspberry Pi, which can be seen in Figure 8 It can be used for label identification of equipment entry, inventory, exit, borrowing, return, take-out, etc., and can also be used for access control of the system. Taking the enterprise equipment management system as an example, Fig.11 The technical solutions related to each functional module of the system are shown. The access control at the entrances and exits of companies, warehouses, etc. can be equipped with cameras, RFID readers and writers, and alarms. If information authentication is not performed or the information authentication is incorrect at any link, an alarm will be triggered. After the device is lent out, the device information will be bound to the borrower's identity information, and the binding information will be updated in real time as the device is lent out. The access control can perform RFID scanning and face recognition on employees and their devices to complete the identity authentication of the binding information. Once the authentication fails, an alarm will be triggered. Furthermore, when the borrower needs to take the device out of the company, he needs to submit a take-out application to the administrator in the system, and only after the administrator agrees can the information authentication be performed at the access control. If the administrator does not agree, even if the identity authentication is passed, an alarm will be caused due to unsatisfied permissions.

[0133] In order to reduce the burden of administrators when receiving and entering a large amount of information about incoming equipment, the system's OCR device can be used. It uses OCR technology, and can scan incoming equipment through the OCR device to identify the label information on the incoming equipment (such as manufacturer labels), and automatically extract the key information and enter it into the system database. At the same time, the system uses the key information to generate RFID tags for incoming equipment. The main work of the administrator includes equipment entry, equipment inventory, equipment outbound, fine processing, complaint processing, etc. The administrator enters and registers the incoming equipment and attaches RFID tags to it. Each device is given a unique ID number to ensure the uniqueness of the device and facilitate regular inventory. At the same time, the device-related information will be uploaded to the device background management system synchronously. After the information is registered, the administrator needs to store the incoming equipment. The administrator needs to regularly inventory the equipment in the warehouse to confirm whether the number of equipment is correct and whether the equipment is obviously damaged. The administrator needs to read and write the RFID tag on each device and enter the equipment information into the background. The system automatically compares the number of equipment in the warehouse and the number of borrowed equipment to see if they are consistent with the total number of equipment at the time of entry. If there is any inconsistency, the system will pop up a reminder and the administrator will conduct further verification. When the administrator takes inventory of important equipment, in addition to counting the number of equipment, he / she needs to conduct a detailed verification of the damage of the equipment. If any abnormality is found, he / she needs to report it in time. At the same time, if necessary, the equipment in the borrowed state needs to be directly checked at the borrower to ensure that the equipment is not damaged or leaked. If the borrower fails to return the equipment within the specified period, or the equipment is damaged when it is returned, the administrator needs to require the borrower to compensate and pay a fine according to the situation. The administrator needs to handle the complaints of equipment abnormalities raised by employees in a timely manner, investigate the damage of equipment, replenish consumable equipment, and determine the fine. If important equipment is not returned on time or is damaged when it is returned, the punishment will be increased and the amount of fines will increase. At the same time, if the important equipment is borrowed by a low-level user, the low-level user and the high-level user who agrees to the borrowing application will be punished together. When equipment needs to be shipped out, the administrator is responsible for counting the equipment, confirming the quantity and quality of the equipment shipped out, demagnetizing the RFID tags, and deleting the equipment details from the equipment background management system, retaining only basic information for future inquiries.

[0134] In addition, the system also involves image preprocessing (such as using CNN algorithm), text detection (such as using CTPN algorithm, R-CNN algorithm, bidirectional LSTM algorithm), text recognition (such as using CRNN algorithm, CNN algorithm, bidirectional LSTM algorithm, CTC algorithm), face recognition (such as DBN algorithm), RFID (see Fig. 9 ) and other technologies.

[0135] The data processing system for device management provided in the embodiment of the present application can be regarded as a highly reliable, high-quality, and high-performance device management system that combines device classification, permission classification, online system and access control, and simplifies the administrator's work in a hardware manner. The system has 1) scalability: the system is completed by many independent functional components and hardware. The link of components is realized through fixed interface definition, and the connection of hardware is realized through assembly. This makes the change of a component or hardware have the least impact on other components, making the maintenance of the system simple and flexible. In addition, new functions can be selectively developed and added according to actual conditions to reduce the workload of daily maintenance. In addition, as business needs change, the system needs to be partially changed, and only related components or hardware need to be modified or added. The components or hardware of other functional parts do not need any changes, which greatly improves the scalability and flexibility of the system; 2) high efficiency performance: the system separates the database, different functional modules correspond to different databases or tables, and then a certain page or function is hashed into a smaller database according to a certain strategy. At the same time, Redis cluster cache, Nginx proxy server, and cloud database RDS (relational database service) are used, so that the performance of the system can be improved at a low cost and has good scalability; 3) reliability: the reliability of the system is improved by the functional independence of components and hardware. The failure of a component and hardware will not affect the normal operation of other functional components, and the repair of a faulty component and hardware will not interrupt the normal use of other system functions. In addition, multiple deployments of components and hardware can be used to reduce the system's vulnerability to losses caused by machine or network failures and improve the system's fault tolerance. 4) Security: 4.1) System security: Use host reinforcement methods to reinforce the host; timely back up and encrypt important system files to ensure the security of system files; strictly control permissions to strengthen access control to the host; log analysis to detect anomalies in a timely manner; 4.2) Network security: Divide security subnets; customize network security testing to achieve continuous security; 4.3) Data encryption: Use data encryption technology to protect system security and prevent data loss and malicious data monitoring.

[0136] An embodiment of the present application provides an electronic device, which includes a processor and a memory, wherein the memory stores at least one instruction or at least one program, and the at least one instruction or the at least one program is loaded and executed by the processor to implement a data processing method for device management as provided in the above method embodiment.

[0137] Further, Fig.19 A hardware structure diagram of an electronic device for implementing the data processing method for device management provided in the embodiment of the present application is shown. The electronic device may participate in or include the data processing device for device management provided in the embodiment of the present application. Fig.19As shown, the electronic device 190 may include one or more (shown as 1902a, 1902b, ..., 1902n in the figure) processors 1902 (the processor 1902 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 1904 for storing data, and a transmission device 1906 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the I / O interface), a network interface, a power supply and / or a camera. It can be understood by those skilled in the art that Fig.19 The structure shown is only for illustration and does not limit the structure of the above electronic device. Fig.19 More or fewer components as shown, or with Fig.19 Different configurations shown.

[0138] It should be noted that the one or more processors 1902 and / or other data processing circuits described above may generally be referred to herein as "data processing circuits". The data processing circuits may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuit may be a single independent processing module, or may be incorporated in whole or in part into any of the other components in the electronic device 190 (or mobile device). As described in the embodiments of the present application, the data processing circuit acts as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0139] The memory 1904 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the data processing method for device management described in the embodiment of the present application. The processor 1902 executes various functional applications and data processing by running the software programs and modules stored in the memory 1904, that is, realizing the above-mentioned data processing method for device management. The memory 1904 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 1904 may further include a memory remotely arranged relative to the processor 1902, and these remote memories may be connected to the electronic device 190 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0140] The transmission device 1906 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the electronic device 190. In one example, the transmission device 1906 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one embodiment, the transmission device 1906 can be a radio frequency (Radio Frequency, RF) module, which is used to communicate with the Internet wirelessly.

[0141] The display may be, for example, a touch screen liquid crystal display (LCD) that may enable a user to interact with a user interface of the electronic device 190 (or mobile device).

[0142] An embodiment of the present application also provides a computer-readable storage medium, which can be set in an electronic device to store at least one instruction or at least one program related to a data processing method for device management in a method embodiment. The at least one instruction or the at least one program is loaded and executed by the processor to implement the data processing method for device management provided in the above method embodiment.

[0143] Optionally, in this embodiment, the storage medium may be located in at least one of the multiple network servers of the computer network. Optionally, in this embodiment, the storage medium may include, but is not limited to, various media that can store program codes, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk.

[0144] It should be noted that the above-mentioned sequence of the embodiments of the present application is for description only and does not represent the advantages and disadvantages of the embodiments. The above-mentioned specific embodiments of the present application are described. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0145] Each embodiment in this application is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device and electronic device embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments.

[0146] A person skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware or by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a disk or an optical disk, etc.

[0147] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application should be included in the protection scope of the present application.

Claims

1. A data processing method for device management, characterized in that: The method comprises: In response to a data processing instruction for a designated device, determining a type of the designated device and usage requirement information for the designated device; Determine corresponding usage verification logic according to the type and the usage requirement information; Verifying the data to be verified according to the usage verification logic; wherein the data to be verified is used to indicate at least one of the following: the designated device and an object associated with the use of the designated device, the data to be verified is provided by a target data provider, and the target data provider includes at least one determined from the designated device and the object based on the usage verification logic; When the verification result indicates passing, generating consent information for the usage requirement information; The determining of the corresponding usage verification logic according to the type and the usage requirement information includes: When the usage requirement information indicates borrowing or returning, first type verification information indicating the scope of the object involved in the data to be verified is determined according to the object level of the designated object and the belonging type, the designated object being an object that is using or applying to use the designated device; second type verification information indicating the data items involved in the data to be verified is determined according to the belonging type and the usage requirement information; corresponding usage verification logic is obtained based on the first type verification information and the second type verification information; When the usage requirement information indicates loaning, a first object and a second object are determined, and third-type verification information for the first object and the second object is generated, wherein the first object is an object that is using the designated device, and the second object is an object that applies to use the designated device, and the third-type verification information indicates a range of objects involved in the data to be verified; based on a second preset rule, a fourth-type verification information matching the type to which it belongs is determined, wherein the second preset rule records preset data items to be verified corresponding to different device types, wherein the preset data items to be verified include device label items related to the designated device and designated identity-type data items, wherein the designated identity-type data items indicate an object that has an associated relationship with the use of the designated device; corresponding usage verification logic is obtained based on the third-type verification information and the fourth-type verification information; When the usage requirement information indicates usage outside the preset scope, a management object is determined, and fifth type of verification information is generated for the management object, wherein the management object is an object having the device management authority, and the fifth type of verification information indicates the scope of objects involved in the data to be verified; based on the second preset rule, sixth type of verification information matching the type is determined; and corresponding usage verification logic is obtained based on the fifth type of verification information and the sixth type of verification information.

2. The method according to claim 1, characterized in that: When the usage requirement information indicates borrowing or returning, the determining the type of the designated device and the usage requirement information for the designated device includes: The object level of the designated object, the type of the designated device, and usage requirement information for the designated device are determined.

3. The method according to claim 2, characterized in that When the usage requirement information indicates borrowing, the first type of verification information indicating the scope of objects involved in the data to be verified is determined according to the object level and the type of the specified object, including: According to a first preset rule, determining whether the object level of the specified object matches the belonging type; When the object level of the specified object does not match the belonging type, determine the associated object corresponding to the specified object, and generate a first type of verification information for the specified object and the associated object; wherein, the object level of the specified object does not match the belonging type indicates that the object level of the specified object is lower than the lower limit of the object level corresponding to the belonging type, and the object level of the associated object is higher than the object level of the specified object.

4. The method according to claim 2 or 3, characterized in that: The determining, according to the type and the usage requirement information, the second type of verification information indicating the data items involved in the data to be verified includes: A second type of verification information matching the type is determined based on the second preset rule.

5. The method according to claim 2, characterized in that: The generating of consent information for the usage requirement information includes: When the usage requirement information indicates borrowing, generating borrowing consent information so that the designated object has the right to use the designated device; or When the usage requirement information indicates return, return consent information is generated so that the designated object no longer has the use authority for the designated device.

6. The method according to claim 1, characterized in that When the usage verification logic indicates that the data to be verified is the return information of the device tag corresponding to the specified device, and there are currently multiple device tags to be verified, the multiple device tags to be verified correspond to different devices respectively, before verifying the data to be verified according to the usage verification logic, the method further includes: The return information of the device tag and the return information respectively corresponding to the plurality of device tags to be inspected are acquired by using a preset time slot algorithm to verify the return information.

7. A data processing device for device management, characterized in that: The device comprises: A response module: used for responding to a data processing instruction for a specified device, determining the type of the specified device and usage requirement information for the specified device; Logic determination module: used to determine the corresponding usage verification logic according to the type and the usage requirement information; Verification module: used for verifying the data to be verified according to the usage verification logic; wherein the data to be verified is used to indicate at least one of the following: the designated device and an object associated with the use of the designated device, the data to be verified is provided by a target data provider, and the target data provider includes at least one determined from the designated device and the object based on the usage verification logic; A consent information generation module: used for generating consent information for the usage requirement information when the verification result indicates a pass; The logic determination module is configured to: determine, when the usage requirement information indicates borrowing or returning, first type of verification information indicating the scope of objects involved in the data to be verified according to the object level of the designated object and the belonging type, wherein the designated object is an object that is using or applying to use the designated device; determine second type of verification information indicating data items involved in the data to be verified according to the belonging type and the usage requirement information; and obtain corresponding usage verification logic based on the first type of verification information and the second type of verification information; When the usage requirement information indicates loaning, a first object and a second object are determined, and third-type verification information for the first object and the second object is generated, wherein the first object is an object that is using the designated device, and the second object is an object that applies to use the designated device, and the third-type verification information indicates a range of objects involved in the data to be verified; based on a second preset rule, a fourth-type verification information matching the type to which it belongs is determined, wherein the second preset rule records preset data items to be verified corresponding to different device types, wherein the preset data items to be verified include device label items related to the designated device and designated identity-type data items, wherein the designated identity-type data items indicate an object that has an associated relationship with the use of the designated device; corresponding usage verification logic is obtained based on the third-type verification information and the fourth-type verification information; When the usage requirement information indicates usage outside the preset scope, a management object is determined, and fifth type of verification information is generated for the management object, wherein the management object is an object having the device management authority, and the fifth type of verification information indicates the scope of objects involved in the data to be verified; based on the second preset rule, sixth type of verification information matching the type is determined; and corresponding usage verification logic is obtained based on the fifth type of verification information and the sixth type of verification information.

8. The device according to claim 7, characterized in that When the usage requirement information indicates borrowing or returning, determining the type of the designated device and the usage requirement information for the designated device includes: determining the object level of the designated object, the type of the designated device and the usage requirement information for the designated device.

9. The device according to claim 8, characterized in that When the usage requirement information indicates borrowing, the first type of verification information indicating the scope of objects involved in the data to be verified is determined based on the object level of the designated object and the belonging type, including: judging whether the object level of the designated object matches the belonging type according to a first preset rule; when the object level of the designated object does not match the belonging type, determining the associated object corresponding to the designated object, and generating the first type of verification information for the designated object and the associated object; wherein, the mismatch between the object level of the designated object and the belonging type indicates that the object level of the designated object is lower than the lower limit of the object level corresponding to the belonging type, and the object level of the associated object is higher than the object level of the designated object.

10. The device according to claim 8 or 9, characterized in that The determining, according to the belonging type and the usage requirement information, the second type of verification information indicating the data items involved in the data to be verified includes: determining the second type of verification information matching the belonging type based on the second preset rule.

11. The device according to claim 8, characterized in that The generating of the consent information for the usage requirement information includes: when the usage requirement information indicates borrowing, generating the consent to borrow information so that the designated object has the usage right for the designated device; or, when the usage requirement information indicates returning, generating the consent to return information so that the designated object no longer has the usage right for the designated device.

12. The device according to claim 7, characterized in that When the usage verification logic indicates that the data to be verified is the return information of the device tag corresponding to the specified device, and there are currently multiple device tags to be verified, the multiple device tags to be verified respectively correspond to different devices, and the device is also used to: use a preset time slot algorithm to obtain the return information of the device tag and the return information corresponding to the multiple device tags to be verified, so as to verify the relevant return information.

13. An electronic device, characterized in that: The electronic device includes a processor and a memory, wherein the memory stores at least one instruction or at least one program, and the at least one instruction or the at least one program is loaded and executed by the processor to implement the data processing method for device management as described in any one of claims 1-6.

14. A computer-readable storage medium, characterized in that: The storage medium stores at least one instruction or at least one program, and the at least one instruction or the at least one program is loaded and executed by the processor to implement the data processing method for device management according to any one of claims 1 to 6.

15. A computer program product, characterized in that The computer program product includes at least one instruction or at least one program, and the at least one instruction or the at least one program is loaded and executed by a processor to implement the data processing method for device management according to any one of claims 1 to 6.

Images