CN112988254A

CN112988254A - Method, device and equipment for managing hardware equipment

Info

Publication number: CN112988254A
Application number: CN201911200509.XA
Authority: CN
Inventors: 胡腾; 楼宏微; 刘俊; 李斌; 赵东
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2019-11-29
Filing date: 2019-11-29
Publication date: 2021-06-18
Anticipated expiration: 2039-11-29
Also published as: CN112988254B

Abstract

The application discloses a method, a device and equipment for managing hardware equipment, and belongs to the technical field of internet. The method comprises the following steps: acquiring a target device identifier of a device to be bound; acquiring a target enterprise identifier corresponding to a management account currently logged in by a management terminal; sending a binding request carrying the target enterprise identifier and the target device identifier to a server, wherein the binding request is used for indicating the server to determine a plurality of target account identifiers corresponding to the target enterprise identifier based on a pre-stored corresponding relationship between the enterprise identifier and the account identifier, determine a target device control applet corresponding to the target device identifier based on a pre-stored corresponding relationship between the device identifier and the device control applet, and add the target device control applet to an applet list of a target account corresponding to each target account identifier. By adopting the method and the device, the staff in the enterprise can use the equipment more conveniently.

Description

Method, device and equipment for managing hardware equipment

Technical Field

The present application relates to the field of internet technologies, and in particular, to a method, an apparatus, and a device for managing hardware devices.

Background

With the development of the internet of things and scientific technology, more and more hardware devices are used by enterprises, such as printers, attendance machines and the like, and the use of the hardware devices greatly improves the working efficiency of enterprise employees.

In the prior art, a provider of a hardware device may write a corresponding operation program for the hardware device, and a user may download the operation program to a terminal, and operate and manage the corresponding hardware device through the terminal.

In the process of implementing the present application, the inventor finds that the prior art has at least the following problems:

when the types of hardware devices used in an enterprise become various, employees in the enterprise need to download corresponding operation application programs according to each type of hardware device, so that the use of the hardware devices by the employees becomes more complicated.

Disclosure of Invention

The embodiment of the application provides a method, a device and equipment for managing hardware equipment, and can solve the problem that when the number of hardware equipment in an enterprise is increased, the use of the hardware equipment in the enterprise by staff in the enterprise becomes more complicated. The technical scheme is as follows:

in one aspect, a method for managing hardware devices is provided, and is applied to a management terminal, and the method includes:

acquiring a target device identifier of a device to be bound;

acquiring a target enterprise identifier corresponding to a management account currently logged in by a management terminal;

sending a binding request carrying the target enterprise identifier and the target device identifier to a server, wherein the binding request is used for indicating the server to determine a plurality of target account identifiers corresponding to the target enterprise identifier based on a pre-stored corresponding relationship between the enterprise identifier and the account identifier, determine a target device control applet corresponding to the target device identifier based on a pre-stored corresponding relationship between the device identifier and the device control applet, and add the target device control applet to an applet list of a target account corresponding to each target account identifier.

Optionally, before sending the binding request carrying the target enterprise identifier and the target device identifier to the server, the method further includes:

acquiring a plurality of department identifications corresponding to the target enterprise identification;

displaying a permission setting page, wherein the permission setting page comprises options corresponding to each department identifier;

determining at least one target department identifier selected in the permission setting page;

the sending the binding request carrying the target enterprise identifier and the target device identifier to the server includes:

and sending a binding request carrying the target enterprise identifier, the target equipment identifier and the at least one target department identifier to a server.

Optionally, after sending the binding request carrying the target enterprise identifier and the target device identifier to the server, the method further includes:

receiving an applet selection list sent by the receiving server, wherein the applet selection list comprises identifiers of a plurality of equipment control applets;

displaying the applet selection list;

determining the identifier of the selected target equipment control small program in the small program selection list;

and sending the identification of the target equipment control small program to the server.

In another aspect, a method for managing hardware devices is provided, and is applied to a server, and the method includes:

receiving a binding request sent by a management terminal, wherein the binding request carries a target enterprise identifier and a target equipment identifier;

determining a plurality of target account identifications corresponding to the target enterprise identifications based on the corresponding relation between the enterprise identifications and the account identifications stored in advance;

determining a target device control applet corresponding to the target device identification based on a corresponding relation between pre-stored device identification and the device control applet, and adding the identification of the target device control applet to an applet list of an account corresponding to each target account identification;

when receiving an applet list request sent by a terminal for logging in any target account, sending the applet list of any target account to the terminal, and when receiving an applet acquisition request which is sent by the terminal and carries an identifier of a target equipment control applet, sending the target equipment control applet to the terminal.

Optionally, the binding request further carries at least one target department identifier;

the determining a plurality of target account identifications corresponding to the target enterprise identification based on the pre-stored corresponding relationship between the enterprise identification and the account identification includes:

and determining a plurality of target account identifications corresponding to the target enterprise identification and the at least one target department identification based on the corresponding relation among the enterprise identifications, the department identifications and the account identifications which are stored in advance.

Optionally, the determining, based on a correspondence between a pre-stored device identifier and a device control applet, a target device control applet corresponding to the target device identifier, and adding the identifier of the target device control applet to an applet list of an account corresponding to each target account identifier includes:

determining a plurality of equipment control small programs corresponding to the target equipment identification based on the corresponding relation between the pre-stored equipment identification and the equipment control small programs;

sending an applet selection list to the management terminal, wherein the applet selection list comprises an identifier of each device control applet;

receiving an identifier of a target equipment control small program sent by the management terminal;

and adding the identification of the target equipment control applet into an applet list of an account corresponding to each target account identification.

Optionally, after determining a plurality of target account ids corresponding to the target enterprise id based on a pre-stored correspondence between the enterprise id and the account id, the method further includes:

correspondingly adding the target equipment identification and the target account identifications into a control binding relation between the equipment identification and the account identification;

when a control message carrying the target account identifier and the target device identifier is received, determining whether the target account identifier corresponds to the target device identifier in the control binding relationship;

and if the target account identifier corresponds to the target device identifier in the control binding relationship, sending the control message to a device corresponding to the target device identifier.

In another aspect, an apparatus for managing hardware devices is provided, where the apparatus is applied to a management terminal, and the apparatus includes:

the device comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is configured to acquire a target device identifier of a device to be bound;

the second acquisition module is configured to acquire a target enterprise identifier corresponding to a management account currently logged in by the management terminal;

a first sending module, configured to send a binding request carrying the target enterprise identifier and the target device identifier to a server, where the binding request is used to instruct the server to determine multiple target account identifiers corresponding to the target enterprise identifier based on a pre-stored correspondence between an enterprise identifier and an account identifier, determine a target device control applet corresponding to the target device identifier based on a pre-stored correspondence between a device identifier and a device control applet, and add the target device control applet to an applet list of a target account corresponding to each target account identifier.

Optionally, the apparatus further comprises a determining sub-module configured to:

the first transmitting module is configured to:

Optionally, the first sending module further includes a first sending submodule configured to:

displaying the applet selection list;

In another aspect, an apparatus for managing hardware devices is provided, and is applied to a server, the apparatus includes:

the system comprises a receiving module, a sending module and a receiving module, wherein the receiving module is configured to receive a binding request sent by a management terminal, and the binding request carries a target enterprise identifier and a target equipment identifier;

the determining module is configured to determine a plurality of target account identifications corresponding to the target enterprise identifications based on a pre-stored corresponding relationship between the enterprise identifications and the account identifications;

the adding module is configured to determine a target device control applet corresponding to the target device identification based on a corresponding relation between a pre-stored device identification and the device control applet, and add the identification of the target device control applet to an applet list of an account corresponding to each target account identification;

the second sending module is configured to send the applet list of any target account to a terminal when receiving an applet list request sent by the terminal for logging in any target account, and send the target device control applet to the terminal when receiving an applet obtaining request which is sent by the terminal and carries an identifier of the target device control applet.

Optionally, the binding request further carries at least one target department identifier, and the determining module is configured to:

Optionally, the adding module is configured to:

Optionally, the apparatus further includes a second sending sub-module:

In yet another aspect, a computer device is provided, which includes a processor and a memory, where at least one instruction is stored, and is loaded and executed by the processor to implement the operations performed by the method for managing a hardware device as described above.

In yet another aspect, a computer-readable storage medium is provided, in which at least one instruction is stored, and the at least one instruction is loaded and executed by a processor to implement the operations performed by the method for managing a hardware device as described above.

The technical scheme provided by the embodiment of the application has the following beneficial effects:

binding information for binding the equipment and the enterprise is sent to the server through a management terminal in the enterprise, the server can add the small program of the control equipment corresponding to the equipment into a small program list of an account of the enterprise staff, then the small program list is sent to the terminal of the enterprise staff, and the enterprise staff can select the small program of the control equipment to control the equipment in the enterprise through the small program list of the terminal. Therefore, the staff in the enterprise does not need to download the corresponding operation application program according to each hardware device, and the staff in the enterprise can use the device more conveniently.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

FIG. 1 is a schematic illustration of an implementation environment provided by an embodiment of the present application;

FIG. 2 is a flowchart illustrating a device provider terminal registering a hardware device with a server according to an embodiment of the present disclosure;

FIG. 3 is a flowchart of a method for managing hardware devices according to an embodiment of the present disclosure;

FIG. 4 is a flowchart of a method for managing hardware devices according to an embodiment of the present disclosure;

FIG. 5 is a flowchart of a method for managing hardware devices according to an embodiment of the present disclosure;

FIG. 6 is a schematic diagram of a program page in a method for managing hardware devices according to an embodiment of the present application;

FIG. 7 is a schematic diagram of a program page in a method for managing hardware devices according to an embodiment of the present application;

FIG. 8 is a schematic diagram of a program page in a method for managing hardware devices according to an embodiment of the present application;

fig. 9 is a flowchart of establishing a binding relationship between a hardware device and an account identifier according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of an apparatus for managing a hardware device according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of an apparatus for managing a hardware device according to an embodiment of the present application;

FIG. 12 is a schematic structural diagram of a computer device according to an embodiment of the present disclosure;

fig. 13 is a schematic structural diagram of a server according to an embodiment of the present application.

Detailed Description

To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

Fig. 1 is a schematic diagram of an implementation environment provided by an embodiment of the present application. Referring to fig. 1, the embodiment of the present application can manage and use different devices through the same application, for example, an enterprise application for enterprise office. The method and the device can be realized by three parts, namely a management server, a device provider terminal and a management terminal. The management server can complete the functions of storing enterprise information, equipment information, binding relationship between enterprises and equipment and the like, and is responsible for communication between various terminals and hardware; the equipment provider terminal can provide the equipment information of the hardware equipment for the server and provide the small program for operating the hardware equipment; the management terminal can provide the server with functions of enterprise information, binding information of enterprises and equipment and the like; in addition, the hardware device may have a network connection function, and may establish a network connection with the server and the management terminal, for example, a printer, an attendance machine, a projector, and the like. The equipment provider terminal and the management terminal have a communication function, can be connected to the Internet, and can be a mobile phone, a tablet personal computer, intelligent wearable equipment, a desktop computer, a notebook computer and the like. The server may establish communication with the terminal. The server may be a single server or a server group, and if the server is a single server, the server may be responsible for all processing in the following scheme, and if the server is a server group, different servers in the server group may be respectively responsible for different processing in the following scheme, and the specific processing allocation condition may be arbitrarily set by a technician according to actual needs, and is not described herein again.

Fig. 2 is a flowchart illustrating a device provider terminal registering a hardware device in a server according to an embodiment of the present disclosure, and as shown in fig. 2, a device provider may send device information for providing the hardware device to the server through a service provider application installed in the device provider terminal or through a website of the device provider. For example, the device information such as the name, model, device code, etc. of the device is uploaded to the server, wherein the device code can be registered in batch in advance through a service provider application program, and the server receives the device information uploaded by the device provider terminal, generates a corresponding device key, and then transmits the device key to the device provider terminal.

When the device provider terminal receives the device key sent by the server, a technician may write the device code and the device key corresponding to the hardware device into a corresponding connection program for subsequent binding and connection of the hardware device and the management terminal. The device provider may provide the corresponding device code to an enterprise purchasing the hardware device when the hardware device is shipped from a factory, for example, the device code of the hardware device is written in a use instruction book of the hardware device, or a two-dimensional code image containing the device code is printed on the hardware device. In addition, the equipment provider terminal can upload an equipment control applet corresponding to the hardware equipment to the server, so that the management terminal can control and operate the hardware equipment.

In addition, the application terminal can be further included in the embodiment of the application, the application terminal can be used for operating and using hardware devices by staff inside an enterprise, an enterprise application program for using the hardware devices can be installed in the application terminal, staff inside the enterprise can log in staff accounts of the enterprise in the enterprise application program, an applet list can be set in the enterprise application program, the applet list includes device control applets of various hardware devices, and the staff can control corresponding hardware devices through corresponding device control applets in the enterprise application program.

Fig. 3 is a flowchart of a method for managing hardware devices, which is applied to a management terminal according to an embodiment of the present application. The management terminal can be provided with an enterprise application program for equipment management, and an administrator of an enterprise can bind the management account of the enterprise and the on-equipment by logging in the management account of the enterprise at the terminal, so that the management of the hardware equipment is realized. In addition, an administrator of the enterprise may manage the hardware device at the terminal through a management website corresponding to the enterprise application.

Referring to fig. 3, the method comprises the steps of:

step 301, obtaining a target device identifier of a device to be bound.

Step 302, acquiring a target enterprise identifier corresponding to a management account currently logged in by the management terminal.

Step 303, sending a binding request carrying the target enterprise identifier and the target device identifier to the server.

The binding request is used for indicating the server to determine a plurality of target account identifications corresponding to the target enterprise identification based on the corresponding relation between the enterprise identification and the account identification stored in advance, determine a target device control applet corresponding to the target device identification based on the corresponding relation between the device identification stored in advance and the device control applet, and add the target device control applet to an applet list of a target account corresponding to each target account identification.

Fig. 4 is a flowchart of a method for managing a hardware device, which is used for a server according to an embodiment of the present application. The server may be a background server corresponding to the enterprise application program and the service provider application program, and may establish network connection with the management terminal, the application terminal, and the device provider terminal, as shown in fig. 4, where the method includes the following steps:

step 401, receiving a binding request sent by a management terminal, where the binding request carries a target enterprise identifier and a target device identifier.

Step 402, determining a plurality of target account identifications corresponding to the target enterprise identification based on the pre-stored corresponding relationship between the enterprise identification and the account identification.

Step 403, determining a target device control applet corresponding to the target device identifier based on the correspondence between the pre-stored device identifier and the device control applet, and adding the identifier of the target device control applet to the applet list of the account corresponding to each target account identifier.

Step 404, when receiving an applet list request sent by a terminal for any target account login, sending the applet list of any target account to the terminal, and when receiving an applet obtaining request carrying an identifier of a target device control applet sent by the terminal, sending the target device control applet to the terminal.

Fig. 5 is a flowchart of a method for managing a hardware device according to an embodiment of the present application, and referring to fig. 5, the embodiment includes:

step 501, the management terminal obtains a target device identifier of a device to be bound.

In implementation, the target device identifier of the device may be a device code corresponding to the hardware device, and before the management terminal establishes a binding relationship with the hardware device, the device code corresponding to the hardware device needs to be acquired first. An enterprise application program in the management terminal may be provided with an equipment adding control, when an administrator of an enterprise clicks the equipment adding control, the enterprise may enter an adding page, as shown in fig. 6, different adding options are set in the adding page, and the administrator may complete adding with equipment by inputting equipment codes manually; or the Bluetooth is connected with the hardware equipment, and the hardware equipment can send the corresponding equipment code to the management terminal; or the target device identifier can be obtained by scanning the two-dimensional code carried on the hardware device in a scanning mode, so as to obtain the corresponding device code.

Step 502, acquiring a target enterprise identifier corresponding to a management account currently logged in by the management terminal.

In implementation, the target enterprise identifier may be an enterprise code corresponding to an enterprise, where the enterprise code may be an enterprise code obtained when an administrator of the enterprise registers the enterprise in an enterprise application program, each enterprise corresponds to a unique enterprise code, and when an administrator of the enterprise logs in a management account at a management terminal, the management terminal may obtain the management account and correspond to the enterprise code.

Step 503, the management terminal sends a binding request carrying the target enterprise identifier and the target device identifier to the server.

In implementation, when step 501 is executed, the enterprise application may enter a binding page, a binding option is set in the binding page, and after the administrator clicks the binding option, the management terminal may send a binding request of the hardware device to the server, where the binding request carries the device code obtained in step 501 and the enterprise identifier obtained in step 502.

Optionally, the administrator may set the usage right of the internal enterprise employee to the hardware device, and the corresponding process is as follows: acquiring a plurality of department identifications corresponding to the target enterprise identification; displaying a permission setting page, wherein the permission setting page comprises options corresponding to each department identifier; determining at least one target department identifier selected in the permission setting page; and sending a binding request carrying the target enterprise identifier, the target equipment identifier and at least one target department identifier to a server.

The employee in the enterprise can log in an employee account in an enterprise application program in the application terminal, wherein the employee account corresponds to the department identifier and the enterprise identifier of the employee. The department identifiers can be set by management accounts logged in by managers of enterprises through enterprise application programs, one enterprise identifier corresponds to at least one department identifier, and each department identifier corresponds to at least one account identifier.

In implementation, a binding page of the enterprise application program may further be provided with a permission setting option, as shown in fig. 7, before a manager sends a binding request of the hardware device, the manager further clicks the permission setting option, after the manager clicks the permission setting option, the enterprise application program may display a management page in which department identifiers of each department inside the enterprise are displayed, and the manager may select a corresponding department identifier to complete setting of the use permission of the hardware device by employees of each department inside the enterprise. Wherein the selected department identification may use a hardware device. After the administrator completes setting the use permission of the hardware device for the employees of each department inside the enterprise, the administrator can return to the binding page and click on my binding controls in the binding page, and after the administrator clicks on the binding controls, the management terminal can send a binding request of the hardware device to the server, wherein the binding request carries the device code acquired in step 501, the enterprise identifier acquired in step 502 and the department identifier inside the enterprise.

In addition, after the manager completes the binding of the hardware equipment, the manager can set the use authority of the staff of each department to each hardware equipment in the enterprise. The enterprise application program is provided with an equipment identification list, wherein the equipment identification list comprises all hardware equipment bound in an enterprise, a manager can click corresponding equipment identification to set the use permission of the hardware equipment, after the manager clicks the corresponding equipment identification, the enterprise application program can display a management page, department identifications of all departments in the enterprise are displayed in the management page, and the manager can select the corresponding department identifications to complete the setting of the use permission of the hardware equipment of employees of all the departments in the enterprise. Wherein the selected department identification may use a hardware device.

Alternatively, the administrator may select a device control applet for controlling the hardware device for the employee within the enterprise, and the corresponding process may be as follows: receiving an applet selection list sent by a server, wherein the applet selection list comprises identifiers of a plurality of equipment control applets; displaying an applet selection list; determining the identifier of the target equipment control small program selected in the small program selection list; an identification of the target device control applet is sent to the server.

In implementation, an applet selection option may also be set in the binding page of the enterprise application program, as shown in fig. 8, after a manager sends a binding request of the hardware device, the manager may further click the applet selection option, and after the manager clicks the applet selection option, the enterprise application program may display an applet selection list, where the applet selection list is sent by the server and displays identifiers of all device control applets capable of controlling the current bound hardware device, the manager may click an identifier of a corresponding device control applet to select a device control applet for controlling the hardware device, and the management terminal may send the selected control applet identifier to the device control server.

Step 504, the server receives the binding request sent by the management terminal, and determines that the binding request carries the target enterprise identifier and the target device identifier.

Corresponding to the above alternative scheme that the manager can configure the use right of the hardware device for the employee inside the enterprise in step 503, the process of step 504 may also be as follows: the binding request also carries at least one target department identifier; and determining a plurality of target account identifications corresponding to the target enterprise identification and at least one target department identification based on the corresponding relation among the enterprise identifications, the department identifications and the account identifications which are stored in advance.

In implementation, the server stores the corresponding relationship between the enterprise identifier, the department identifier and the account identifier. After receiving the binding request sent by the management terminal, the server determines an account identifier corresponding to the department identifier carried in the binding request according to the corresponding relationship among the enterprise identifier, the department identifier and the account identifier stored in the server, establishes a binding relationship between the hardware device and the determined account identifier, and stores the binding relationship in the server. Fig. 9 is a flowchart of establishing a binding relationship between a hardware device and an account identifier, where as shown in fig. 9, a management terminal establishes a binding relationship with a hardware device through a device code and a device key of the hardware device, and after the binding relationship is successfully established, a server determines an account identifier corresponding to a department identifier carried in a binding request according to a stored correspondence between an enterprise identifier, a department identifier, and an account identifier, and establishes a binding relationship between the hardware device and the determined account identifier.

Step 505, the server determines a plurality of target account identifications corresponding to the target enterprise identification based on the pre-stored correspondence between the enterprise identification and the account identification.

In implementation, after the server receives the binding request sent by the receiving management terminal, the server determines a plurality of account identifiers corresponding to the enterprise identifier carried in the binding request according to the correspondence between the enterprise identifier and the account identifier stored before.

Optionally, after determining a plurality of account identifiers corresponding to the enterprise identifier carried in the binding request, step 505 may further perform the following operations: correspondingly adding the equipment identifier and the target account identifiers into the control binding relationship between the equipment identifier and the account identifier; when receiving a control message carrying a target account identifier and a target device identifier, determining whether the target account identifier corresponds to the target device identifier in a control binding relationship; and if the target account identifier corresponds to the target equipment identifier in the control binding relationship, sending the control message to equipment corresponding to the target equipment identifier.

In implementation, after determining that the enterprise identifier carried in the binding request corresponds to the plurality of account identifiers, the device identifier and the plurality of account identifiers carried in the binding request are added to a control binding relationship between the device identifier and the account identifier, where the control binding relationship may be in the form of a binding list, one account identifier may correspond to the plurality of device identifiers, and one device identifier may also correspond to the plurality of account identifiers. After the server receives a control instruction for the hardware device sent by the application terminal, whether the account identifier and the target device identifier carried in the control instruction correspond to each other in the control binding relationship is judged according to the account identifier and the target device identifier carried in the control instruction and the previously stored control binding relationship. And if the account identifier carried in the control instruction corresponds to the target equipment identifier in the control binding relationship, sending the control message to the hardware equipment corresponding to the equipment identifier carried in the control instruction, so that the hardware equipment completes the control instruction sent by the enterprise application terminal.

Step 506, the server determines the target device control applet corresponding to the target device identifier based on the pre-stored correspondence between the device identifier and the device control applet, and adds the identifier of the target device control applet to the applet list of the account corresponding to each target account identifier.

In implementation, the server correspondingly stores the device identifier and the markup of the device control applet according to the device control applet uploaded by the device provider terminal and used for controlling the hardware device, after receiving the binding request, the server can determine the identifier of the device control applet corresponding to the device identifier according to the pre-stored corresponding relationship between the device identifier and the identifier of the device control applet and the device identifier carried in the binding request, determine the account identifier corresponding to the enterprise identifier carried in the binding request according to the enterprise identifier carried in the binding request and the pre-stored corresponding relationship between the enterprise identifier and the account identifier in the server, and then add the determined identifier of the device control applet into the applet list of the account corresponding to the determined account identifier.

Optionally, corresponding to the step 503 where the manager selects a device control applet for controlling the hardware device for the employee in the enterprise, the corresponding step 506 may be performed as follows: determining a plurality of equipment control small programs corresponding to the target equipment identification based on the corresponding relation between the pre-stored equipment identification and the equipment control small programs; sending an applet selection list to a management terminal, wherein the applet selection list comprises an identifier of each device control applet; receiving an identifier of a target equipment control small program sent by a management terminal; and adding the identification of the control applet of the target equipment to an applet list of an account corresponding to each target account identification.

In implementation, the server stores the corresponding relationship between the device identifier and the device control applet identifier in advance, and when a plurality of control applets of the control device are provided, the server may store the plurality of device control applet identifiers corresponding to the device identifier in a list form. When the server receives a binding request carrying the device identifier, the server may determine, according to a pre-stored applet selection list corresponding to each device identifier, an applet selection list corresponding to the device identifier carried in the binding request, where the applet list includes a device control applet for controlling the hardware device corresponding to the device identifier carried in the binding request. And sending an applet selection list to the management terminal, receiving the identifier of the device control applet selected by the management terminal after the management terminal selects the identifier of the device control applet in the applet selection list, and adding the identifier of the device control applet selected by the management terminal into the applet list of the account corresponding to the determined account identifier.

And 507, when receiving an applet list request sent by a terminal for logging in any target account, sending the applet list of any target account to the terminal, and when receiving an applet acquisition request which is sent by the terminal and carries an identifier of a target equipment control applet, sending the target equipment control applet to the terminal.

The terminal may be an application terminal operated by an employee in an enterprise, and an account of the employee of the enterprise is logged in the application terminal.

In implementation, when starting an enterprise application program of an application terminal, an employee in an enterprise may request an applet list from a server, where the applet list request carries an account identifier, and when the server sends an applet list corresponding to the account identifier to the application terminal according to the account identifier carried in the applet list request. In addition, employees in the enterprise select the applet identifiers in the applet list through the enterprise application program of the application terminal and send an applet acquiring request to the server, wherein the applet acquiring request carries the identifiers of the selected device control applets, and the server sends the device control applets corresponding to the identifiers of the device control applets to the application terminal according to the identifiers of the device control applets.

According to the method and the device, the binding information of the binding between the device and the enterprise is sent to the server through the management terminal in the enterprise, the server can add the small program of the control device corresponding to the device into the small program list of the account of the enterprise staff, then the small program list is sent to the terminal of the enterprise staff, and the enterprise staff can select the small program of the control device to control the device in the enterprise through the small program list of the terminal. Therefore, the staff in the enterprise does not need to download the corresponding operation application program according to each hardware device, and the staff in the enterprise can use the device more conveniently.

All the above optional technical solutions may be combined arbitrarily to form the optional embodiments of the present disclosure, and are not described herein again.

An embodiment of the present application provides an apparatus for managing hardware devices, where the apparatus may be a management terminal in the foregoing embodiment, and as shown in fig. 10, the apparatus includes:

a first obtaining module 1010 configured to obtain a target device identifier of a device to be bound;

a second obtaining module 1020 configured to obtain a target enterprise identifier corresponding to a management account currently logged in by the management terminal;

a first sending module 1030 configured to send a binding request carrying the target enterprise identifier and the target device identifier to a server, where the binding request is used to instruct the server to determine multiple target account identifiers corresponding to the target enterprise identifier based on a correspondence between pre-stored enterprise identifiers and account identifiers, determine a target device control applet corresponding to the target device identifier based on a correspondence between pre-stored device identifiers and device control applets, and add the target device control applet to an applet list of a target account corresponding to each target account identifier.

the first transmitting module 1030 is configured to:

Optionally, the sending module 1030 further includes a first sending submodule configured to:

displaying the applet selection list;

An embodiment of the present application provides an apparatus for managing hardware devices, where the apparatus may be a server in the foregoing embodiment, and as shown in fig. 11, the apparatus includes:

a receiving module 1110, configured to receive a binding request sent by a management terminal, where the binding request carries a target enterprise identifier and a target device identifier;

a determining module 1120, configured to determine, based on a pre-stored correspondence between the enterprise identities and the account identities, a plurality of target account identities corresponding to the target enterprise identities;

an adding module 1130, configured to determine a target device control applet corresponding to the target device identifier based on a correspondence between a pre-stored device identifier and a device control applet, and add the identifier of the target device control applet to an applet list of an account corresponding to each target account identifier;

a second sending module 1140, configured to send the applet list of any target account to any terminal when receiving an applet list request sent by the terminal in which the target account is logged, and send the target device control applet to the terminal when receiving an applet obtaining request carrying an identifier of the target device control applet sent by the terminal.

Optionally, the binding request further carries at least one target department identifier, and the determining module 1120 is configured to:

Optionally, the adding module 1130 is configured to:

Optionally, the apparatus further includes a second sending sub-module:

It should be noted that: in the apparatus for managing hardware devices provided in the foregoing embodiments, when managing hardware devices, only the division of the functional modules is illustrated, and in practical applications, the above functions may be distributed by different functional modules according to needs, that is, the internal structure of the apparatus is divided into different functional modules, so as to complete all or part of the functions described above. In addition, the apparatus for managing hardware devices and the method embodiment for managing hardware devices provided in the foregoing embodiments belong to the same concept, and specific implementation processes thereof are detailed in the method embodiment and are not described herein again.

Fig. 12 shows a block diagram of a computer device provided in an exemplary embodiment of the present application. The computer device may be a terminal 1200, and the terminal 1200 may be: a smart phone, a tablet computer, an MP3 player (Moving Picture Experts Group Audio Layer III, motion video Experts compression standard Audio Layer 3), an MP4 player (Moving Picture Experts Group Audio Layer IV, motion video Experts compression standard Audio Layer 4), a notebook computer, or a desktop computer. Terminal 1200 may also be referred to by other names such as user equipment, portable terminal, laptop terminal, desktop terminal, and so forth.

In general, terminal 1200 includes: a processor 1201 and a memory 1202.

The processor 1201 may include one or more processing cores, such as a 4-core processor, an 8-core processor, or the like. The processor 1201 may be implemented in at least one hardware form of a DSP (Digital Signal Processing), an FPGA (Field-Programmable Gate Array), and a PLA (Programmable Logic Array). The processor 1201 may also include a main processor and a coprocessor, where the main processor is a processor for Processing data in an awake state, and is also called a Central Processing Unit (CPU); a coprocessor is a low power processor for processing data in a standby state. In some embodiments, the processor 1201 may be integrated with a GPU (Graphics Processing Unit) that is responsible for rendering and drawing content that the display screen needs to display. In some embodiments, the processor 1201 may further include an AI (Artificial Intelligence) processor for processing a computing operation related to machine learning.

Memory 1202 may include one or more computer-readable storage media, which may be non-transitory. Memory 1202 may also include high-speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In some embodiments, a non-transitory computer readable storage medium in memory 1202 is used to store at least one instruction for execution by processor 1201 to implement a method of managing a hardware device as provided by method embodiments herein.

In some embodiments, the terminal 1200 may further optionally include: a peripheral interface 1203 and at least one peripheral. The processor 1201, memory 1202, and peripheral interface 1203 may be connected by a bus or signal line. Various peripheral devices may be connected to peripheral interface 1203 via a bus, signal line, or circuit board. Specifically, the peripheral device includes: at least one of radio frequency circuitry 1204, touch display 1205, camera 1206, audio circuitry 1207, pointing component 1208, and power source 1209.

The peripheral interface 1203 may be used to connect at least one peripheral associated with I/O (Input/Output) to the processor 1201 and the memory 1202. In some embodiments, the processor 1201, memory 1202, and peripheral interface 1203 are integrated on the same chip or circuit board; in some other embodiments, any one or two of the processor 1201, the memory 1202 and the peripheral device interface 1203 may be implemented on a separate chip or circuit board, which is not limited in this embodiment.

The Radio Frequency circuit 1204 is used for receiving and transmitting RF (Radio Frequency) signals, also called electromagnetic signals. The radio frequency circuit 1204 communicates with a communication network and other communication devices by electromagnetic signals. The radio frequency circuit 1204 converts an electric signal into an electromagnetic signal to transmit, or converts a received electromagnetic signal into an electric signal. Optionally, the radio frequency circuit 1204 comprises: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a subscriber identity module card, and so forth. The radio frequency circuit 1204 may communicate with other terminals through at least one wireless communication protocol. The wireless communication protocols include, but are not limited to: metropolitan area networks, various generation mobile communication networks (2G, 3G, 4G, and 5G), Wireless local area networks, and/or WiFi (Wireless Fidelity) networks. In some embodiments, the rf circuit 1204 may further include NFC (Near Field Communication) related circuits, which are not limited in this application.

The display screen 1205 is used to display a UI (User Interface). The UI may include graphics, text, icons, video, and any combination thereof. When the display screen 1205 is a touch display screen, the display screen 1205 also has the ability to acquire touch signals on or over the surface of the display screen 1205. The touch signal may be input to the processor 1201 as a control signal for processing. At this point, the display 1205 may also be used to provide virtual buttons and/or a virtual keyboard, also referred to as soft buttons and/or a soft keyboard. In some embodiments, the display 1205 may be one, providing the front panel of the terminal 1200; in other embodiments, the display 1205 can be at least two, respectively disposed on different surfaces of the terminal 1200 or in a folded design; in still other embodiments, the display 1205 may be a flexible display disposed on a curved surface or on a folded surface of the terminal 1200. Even further, the display screen 1205 may be arranged in a non-rectangular irregular figure, i.e., a shaped screen. The Display panel 1205 can be made of LCD (Liquid Crystal Display), OLED (Organic Light-Emitting Diode), or other materials.

Camera assembly 1206 is used to capture images or video. Optionally, camera assembly 1206 includes a front camera and a rear camera. Generally, a front camera is disposed at a front panel of the terminal, and a rear camera is disposed at a rear surface of the terminal. In some embodiments, the number of the rear cameras is at least two, and each rear camera is any one of a main camera, a depth-of-field camera, a wide-angle camera and a telephoto camera, so that the main camera and the depth-of-field camera are fused to realize a background blurring function, and the main camera and the wide-angle camera are fused to realize panoramic shooting and VR (Virtual Reality) shooting functions or other fusion shooting functions. In some embodiments, camera assembly 1206 may also include a flash. The flash lamp can be a monochrome temperature flash lamp or a bicolor temperature flash lamp. The double-color-temperature flash lamp is a combination of a warm-light flash lamp and a cold-light flash lamp, and can be used for light compensation at different color temperatures.

The audio circuitry 1207 may include a microphone and a speaker. The microphone is used for collecting sound waves of a user and the environment, converting the sound waves into electric signals, and inputting the electric signals into the processor 1201 for processing or inputting the electric signals into the radio frequency circuit 1204 to achieve voice communication. For stereo capture or noise reduction purposes, multiple microphones may be provided at different locations of terminal 1200. The microphone may also be an array microphone or an omni-directional pick-up microphone. The speaker is used to convert electrical signals from the processor 1201 or the radio frequency circuit 1204 into sound waves. The loudspeaker can be a traditional film loudspeaker or a piezoelectric ceramic loudspeaker. When the speaker is a piezoelectric ceramic speaker, the speaker can be used for purposes such as converting an electric signal into a sound wave audible to a human being, or converting an electric signal into a sound wave inaudible to a human being to measure a distance. In some embodiments, the audio circuitry 1207 may also include a headphone jack.

The positioning component 1208 is configured to locate a current geographic Location of the terminal 1200 to implement navigation or LBS (Location Based Service). The Positioning component 1208 can be a Positioning component based on the united states GPS (Global Positioning System), the chinese beidou System, the russian graves System, or the european union galileo System.

The power supply 1209 is used to provide power to various components within the terminal 1200. The power source 1209 may be alternating current, direct current, disposable or rechargeable. When the power source 1209 includes a rechargeable battery, the rechargeable battery may support wired or wireless charging. The rechargeable battery may also be used to support fast charge technology.

In some embodiments, terminal 1200 also includes one or more sensors 1210. The one or more sensors 1210 include, but are not limited to: acceleration sensor 1211, gyro sensor 1212, pressure sensor 1213, fingerprint sensor 1214, optical sensor 1215, and proximity sensor 1216.

The acceleration sensor 1211 can detect magnitudes of accelerations on three coordinate axes of the coordinate system established with the terminal 1200. For example, the acceleration sensor 1211 may be used to detect components of the gravitational acceleration in three coordinate axes. The processor 1201 may control the touch display 1205 to display the user interface in a landscape view or a portrait view according to the gravitational acceleration signal collected by the acceleration sensor 1211. The acceleration sensor 1211 may also be used for acquisition of motion data of a game or a user.

The gyro sensor 1212 may detect a body direction and a rotation angle of the terminal 1200, and the gyro sensor 1212 may collect a 3D motion of the user on the terminal 1200 in cooperation with the acceleration sensor 1211. The processor 1201 can implement the following functions according to the data collected by the gyro sensor 1212: motion sensing (such as changing the UI according to a user's tilting operation), image stabilization at the time of photographing, game control, and inertial navigation.

Pressure sensors 1213 may be disposed on a side bezel of terminal 1200 and/or an underlying layer of touch display 1205. When the pressure sensor 1213 is disposed on the side frame of the terminal 1200, the user's holding signal of the terminal 1200 can be detected, and the processor 1201 performs left-right hand recognition or shortcut operation according to the holding signal collected by the pressure sensor 1213. When the pressure sensor 1213 is disposed at a lower layer of the touch display screen 1205, the processor 1201 controls the operability control on the UI interface according to the pressure operation of the user on the touch display screen 1205. The operability control comprises at least one of a button control, a scroll bar control, an icon control and a menu control.

The fingerprint sensor 1214 is used for collecting a fingerprint of the user, and the processor 1201 identifies the user according to the fingerprint collected by the fingerprint sensor 1214, or the fingerprint sensor 1214 identifies the user according to the collected fingerprint. When the user identity is identified as a trusted identity, the processor 1201 authorizes the user to perform relevant sensitive operations, including unlocking a screen, viewing encrypted information, downloading software, paying, changing settings, and the like. The fingerprint sensor 1214 may be provided on the front, back, or side of the terminal 1200. When a physical button or vendor Logo is provided on the terminal 1200, the fingerprint sensor 1214 may be integrated with the physical button or vendor Logo.

The optical sensor 1215 is used to collect the ambient light intensity. In one embodiment, the processor 1201 may control the display brightness of the touch display 1205 according to the ambient light intensity collected by the optical sensor 1215. Specifically, when the ambient light intensity is high, the display brightness of the touch display panel 1205 is increased; when the ambient light intensity is low, the display brightness of the touch display panel 1205 is turned down. In another embodiment, processor 1201 may also dynamically adjust the camera head 1206 shooting parameters based on the ambient light intensity collected by optical sensor 1215.

A proximity sensor 1216, also known as a distance sensor, is typically disposed on the front panel of the terminal 1200. The proximity sensor 1216 is used to collect a distance between the user and the front surface of the terminal 1200. In one embodiment, when the proximity sensor 1216 detects that the distance between the user and the front surface of the terminal 1200 gradually decreases, the processor 1201 controls the touch display 1205 to switch from the bright screen state to the dark screen state; when the proximity sensor 1216 detects that the distance between the user and the front surface of the terminal 1200 gradually becomes larger, the processor 1201 controls the touch display 1205 to switch from the breath screen state to the bright screen state.

Those skilled in the art will appreciate that the configuration shown in fig. 12 is not intended to be limiting of terminal 1200 and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components may be used.

Fig. 13 is a schematic structural diagram of a server 1300 according to an embodiment of the present application, where the server 1300 may generate a relatively large difference due to different configurations or performances, and may include one or more processors (CPUs) 1301 and one or more memories 1302, where the memory 1302 stores at least one instruction, and the at least one instruction is loaded and executed by the processor 1301 to implement the methods provided by the foregoing method embodiments. Of course, the server may also have components such as a wired or wireless network interface, a keyboard, and an input/output interface, so as to perform input/output, and the server may also include other components for implementing the functions of the device, which are not described herein again.

In an exemplary embodiment, a computer-readable storage medium, such as a memory, including instructions executable by a processor in a terminal to perform the method of managing hardware devices of the above embodiments is also provided. The computer readable storage medium may be non-transitory. For example, the computer-readable storage medium may be a ROM (Read-Only Memory), a RAM (Random Access Memory), a magnetic tape, a floppy disk, an optical data storage device, and the like.

It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.

The above description is only exemplary of the present application and should not be taken as limiting, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims

1. A method of managing hardware devices, the method comprising:

acquiring a target device identifier of a device to be bound;

2. The method of claim 1, wherein before sending the binding request carrying the target enterprise identity and the target device identity to the server, the method further comprises:

3. The method of claim 1, wherein after sending the binding request carrying the target enterprise identity and the target device identity to the server, further comprising:

displaying the applet selection list;

4. A method of managing hardware devices, the method comprising:

5. The method of claim 4, wherein the binding request further carries at least one target department identifier;

6. The method according to claim 4, wherein the determining a target device control applet corresponding to the target device identifier based on a pre-stored correspondence between the device identifier and the device control applet, and adding the identifier of the target device control applet to an applet list of an account corresponding to each target account identifier comprises:

7. The method according to claim 4, wherein after determining a plurality of target account ids corresponding to the target enterprise id based on the pre-stored correspondence between the enterprise id and the account ids, the method further comprises:

8. An apparatus for managing hardware devices, the apparatus comprising:

9. An apparatus for managing hardware devices, the apparatus comprising:

the determining module is configured to determine a target device control applet corresponding to the target device identification based on a corresponding relation between a pre-stored device identification and a device control applet, and add the identification of the target device control applet to an applet list of an account corresponding to each target account identification;

the adding module is configured to determine a device control applet corresponding to the target device identification, and add the identification of the device control applet to an applet list of an account corresponding to each target account identification;

10. A computer device comprising a processor and a memory, the memory having stored therein at least one instruction that is loaded and executed by the processor to perform operations performed by a method of managing hardware devices of any of claims 1 to 7.