CN112988254B

CN112988254B - Method, device and equipment for managing hardware equipment

Info

Publication number: CN112988254B
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: 2023-08-22
Anticipated expiration: 2039-11-29
Also published as: CN112988254A

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; and sending a binding request carrying the target enterprise identifier and the target equipment 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 the corresponding relation between the prestored enterprise identifier and the account identifier, determine a target equipment control applet corresponding to the target equipment identifier based on the corresponding relation between the prestored equipment identifier and the equipment control applet, and add the target equipment 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 staff of the enterprises.

In the prior art, a vendor of a hardware device writes a corresponding operation program for the hardware device, and a user can download the operation program to a terminal, and operate and manage the corresponding hardware device through the terminal.

In carrying out the application, the inventors have found that the prior art has at least the following problems:

when the types of hardware devices used in the enterprise become more, staff in the enterprise need to download corresponding operation application programs according to each hardware device, so that the staff becomes more complex to use the hardware devices.

Disclosure of Invention

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

in one aspect, a method for managing a hardware device 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;

and sending a binding request carrying the target enterprise identifier and the target equipment 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 the corresponding relation between the prestored enterprise identifier and the account identifier, determine a target equipment control applet corresponding to the target equipment identifier based on the corresponding relation between the prestored equipment identifier and the equipment control applet, and add the target equipment 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 identifications;

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

determining at least one target department identification selected in the authority setting page;

The sending a binding request carrying the target enterprise identifier and the target equipment identifier to a 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 identification of the selected target device control applet in the applet selection list;

and sending the identification of the target equipment control applet to the server.

In another aspect, a method for managing a hardware device is provided, and the method is applied to a server, and 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 a corresponding relation between the prestored enterprise identifications and the account identifications;

Determining a target equipment control applet corresponding to the target equipment identifier based on a corresponding relation between the prestored equipment identifier and the equipment control applet, and adding the identifier of the target equipment control applet into an applet list of an account corresponding to each target account identifier;

and when an applet acquisition request carrying the identification of the target equipment control applet sent by the terminal is received, 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 identifications based on the corresponding relation between the prestored enterprise identifications and the account identifications comprises the following steps:

and determining a plurality of target account identifications corresponding to the target enterprise identifications and the at least one target department identification based on the corresponding relation among the prestored enterprise identifications, department identifications and account identifications.

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

Determining a plurality of equipment control applets corresponding to the target equipment identifier based on the corresponding relation between the prestored equipment identifier and the equipment control applets;

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

receiving an identification of a target equipment control applet 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 the plurality of target account identifiers corresponding to the target enterprise identifier based on the correspondence between the prestored enterprise identifier and the account identifier, the method further includes:

correspondingly adding the target equipment identifier and the plurality of target account identifiers into a control binding relation between the equipment identifier and the account identifiers;

when a control message carrying the target account identifier and the target equipment identifier is received, determining whether the target account identifier corresponds to the target equipment identifier in the 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 still another aspect, an apparatus for managing a hardware device is provided, which is applied to a management terminal, and the apparatus includes:

the first acquisition module is configured to acquire a target device identifier of the device to be bound;

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

the first sending module is configured to send a binding request carrying the target enterprise identifier and the target equipment 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 corresponding relation between the prestored enterprise identifier and the account identifier, determine a target equipment control applet corresponding to the target equipment identifier based on a corresponding relation between the prestored equipment identifier and the equipment control applet, and add the target equipment control applet to an applet list of a target account corresponding to each target account identifier.

Optionally, the apparatus further comprises a determination submodule configured to:

the first transmission module is configured to:

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

displaying the applet selection list;

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

the receiving module is configured to receive a binding request sent by the management terminal, wherein 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 the corresponding relation between the prestored enterprise identifications and the account identifications;

The adding module is configured to determine a target device control applet corresponding to the target device identifier based on a corresponding relation between the pre-stored device identifier and the 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;

the second sending module is configured to send the applet list of any target account to the terminal when receiving the applet list request sent by the terminal logged in by any target account, and send the target equipment control applet to the terminal when receiving the applet acquisition request sent by the terminal and carrying the identification of the target equipment 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 transmitting sub-module:

In yet another aspect, a computer device is provided that includes a processor and a memory having at least one instruction stored therein that is loaded and executed by the processor to perform the operations performed by the method of managing a hardware device as described above.

In yet another aspect, a computer-readable storage medium having stored therein at least one instruction loaded and executed by a processor to implement operations performed by a method of managing hardware devices as described above is provided.

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

and the server can add the applet corresponding to the equipment to the applet list of the enterprise employee account, then send the applet list to the terminal of the enterprise employee, and the enterprise employee can select the applet of the control equipment to control the equipment in the enterprise through the applet list of the terminal. Therefore, staff in the enterprise does not need to download corresponding operation application programs according to each hardware device, so that the staff in the enterprise can use the devices more conveniently.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

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

FIG. 2 is a flow chart of a device provider terminal registering a hardware device with a server in an embodiment of the present application;

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

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

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

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 a binding relationship between a hardware device and an account identifier provided by an embodiment of the present application;

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

FIG. 11 is a schematic diagram of an apparatus for managing hardware devices according to an embodiment of the present application;

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

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

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the embodiments of the present application will be described in further detail 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, embodiments of the present application may manage and use different devices through the same application, such as an enterprise application for an enterprise office. The present application can be implemented in three parts, a management server, a device provider terminal and a management terminal, respectively. The management server can finish the functions of storing enterprise information, equipment information, binding relation between enterprises and equipment and the like and is responsible for communication between the various terminals and hardware; the device provider terminal may provide the server with device information of the hardware device, and with an applet that operates the hardware device; the management terminal can provide the server with functions such as 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 can have a communication function, can be connected to the Internet, and can be a mobile phone, a tablet 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, if the server is a single server, the server may be responsible for all the processes in the following schemes, if the server is a server group, different servers in the server group may be respectively responsible for different processes in the following schemes, and specific process allocation conditions may be set by technicians according to actual requirements at will, which will not be described herein.

Fig. 2 is a flowchart of registering a hardware device by a device provider terminal in a server according to an embodiment of the present application, where as shown in fig. 2, the 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 device provider website. For example, the name, model, device code and other device information of the device are uploaded to the server, wherein the device code can be registered in batch in advance by the service provider application program, the server receives the device information uploaded by the device provider terminal, generates a corresponding device key, and then sends the device key to the device provider terminal.

When the device provider terminal receives the device key sent by the server, a technician can write the device code and the device key corresponding to the hardware device into a corresponding connection program for binding and connecting 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 leaves the factory, for example, write the device code of the hardware device in a use instruction of the hardware device, or print a two-dimensional code image containing the device code on the hardware device, etc. In addition, the device provider terminal can upload the device control applet corresponding to the control hardware device to the server for the management terminal to control and operate the hardware device.

In addition, the embodiment of the application can also comprise an application terminal, the application terminal can be used for operating and using the hardware equipment by staff in an enterprise, an enterprise application program for using the hardware equipment can be installed in the application terminal, staff in the enterprise can log in staff accounts of the enterprise in the enterprise application program, an applet list can be arranged in the enterprise application program, the applet list comprises equipment control applets of various hardware equipment, and staff can control the corresponding hardware equipment through corresponding equipment control applets in the enterprise application program.

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

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

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

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

Step 303, a binding request carrying the target enterprise identifier and the target device identifier is sent 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 identifications based on the corresponding relation between the prestored enterprise identifications and the account identifications, determine target equipment control applets corresponding to the target equipment identifications based on the corresponding relation between the prestored equipment identifications and the equipment control applets, and add the target equipment control applets into an applet list of target accounts corresponding to each target account identification.

Fig. 4 is a flowchart of a method for managing hardware devices, which is provided by an embodiment of the present application, where the method is used for a server. The server may be a background server corresponding to an enterprise application program and a service provider application program, and may establish network connection with a management terminal, an application terminal and a device provider terminal, see fig. 4, and 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 identifications based on the corresponding relation between the prestored enterprise identifications and the account identifications.

Step 403, determining a target device control applet corresponding to the target device identifier based on the corresponding relation 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.

And step 404, when receiving the applet list request sent by the terminal logged in by any target account, sending the applet list of any target account to the terminal, and when receiving the applet acquisition request carrying the identification of the 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 hardware devices according to an embodiment of the present application, referring to fig. 5, where the embodiment includes:

in 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 can be provided with a device adding control, after an administrator of the enterprise clicks the device adding control, an adding page can be entered, as shown in fig. 6, different adding options are arranged in the adding page, and the administrator can finish adding the device through manual input of a device code; or the device can be connected with the hardware device through Bluetooth, and the hardware device can send the corresponding device code to the management terminal; or the two-dimensional code carried on the hardware equipment can be scanned in a scanning mode to obtain the target equipment identification, so that the corresponding equipment code can be obtained.

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

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

In 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 executing step 501, the enterprise application may enter a binding page, where 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 manager may set the usage rights of the staff in the enterprise to the hardware device, and the corresponding processing is as follows: acquiring a plurality of department identifications corresponding to the target enterprise identifications; displaying a permission setting page, wherein the permission setting page comprises options corresponding to each department identifier; determining at least one target department identification selected in the authority 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.

Staff within an enterprise can log in an staff account of an enterprise application in an application terminal, wherein a department identification and an enterprise identification of the staff correspond to the staff account. The department identifiers can be set by a manager of the enterprise through a management account logged in by the enterprise application program, one enterprise identifier corresponds to at least one department identifier, and each department identifier corresponds to at least one account identifier.

In implementation, the binding page of the enterprise application program may further be provided with a permission setting option, as shown in fig. 7, before the manager sends the binding request of the hardware device, the manager clicks the permission setting option, after the manager clicks the permission setting option, the enterprise application program may display a management page, the management page displays department identifiers of all departments in the enterprise, and the manager may select the corresponding department identifiers to complete setting of the usage permissions of employees of all departments in the enterprise on the hardware device. Wherein the selected department identification may use a hardware device. After the administrator completes setting the usage rights of the staff of each department in the enterprise to the hardware device, the administrator may return to the binding page and click on my binding control in the binding page, and after the administrator clicks on the binding control, the administration 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, the enterprise identifier obtained in step 502, and the department identifier in the enterprise.

In addition, the manager can set the use authority of staff of each department to each hardware device in the enterprise after the binding of the hardware devices is completed. The enterprise application program is provided with a device identification list, wherein the device identification list comprises all the hardware devices bound in the enterprise, a manager can click on the corresponding device identification to set the use authority of the hardware devices, after clicking on the corresponding device 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 finish setting the use authority of staff of all departments in the enterprise on the hardware devices. Wherein the selected department identification may use a hardware device.

Alternatively, the manager may select a device control applet for controlling the hardware device for staff 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 identification of the selected target device control applet in the applet selection list; and sending the identification of the target device control applet to the server.

In an implementation, an applet selection option may be further set in a binding page of the enterprise application, as shown in fig. 8, after the manager sends a binding request of the hardware device, the manager may click on the applet selection option, after the manager clicks on the applet selection option, the enterprise application may display an applet selection list, where the applet selection list is sent by the server, and displays identifiers of all device control applets that can control the currently bound hardware device, the manager may click on the identifiers of the corresponding device control applets to select a device control applet that controls 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 equipment identifier.

Corresponding to the above alternative scheme that the manager may configure the usage rights of the hardware device for the staff in the enterprise in step 503, the processing in step 504 may further 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 identifications and at least one target department identification based on the corresponding relation among the prestored enterprise identifications, department identifications and account identifications.

In implementation, the server stores the correspondence between enterprise identifications, department identifications and account identifications. 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 between the enterprise identifier, the department identifier and the account identifier stored in the server, and 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 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 the hardware device through a device code and a device key of the hardware device, after the binding relationship is established successfully, a server determines an account identifier corresponding to a department identifier carried in a binding request according to a stored correspondence between the enterprise identifier, the department identifier and the account identifier, and establishes a binding relationship between the hardware device and the determined account identifier.

In step 505, the server determines a plurality of target account identifiers corresponding to the target enterprise identifiers based on the correspondence between the prestored enterprise identifiers and the account identifiers.

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

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

In an implementation, after determining that the enterprise identifier carried in the binding request corresponds to a plurality of account identifiers, adding the device identifier and the plurality of account identifiers carried in the binding request to a control binding relationship between the device identifier and the account identifiers, where the control binding relationship may be in a binding list form, one account identifier may correspond to a plurality of device identifiers, and one device identifier may also correspond to a plurality of account identifiers. After receiving a control instruction to the hardware device sent by the application terminal, the server judges whether the account identifier and the target device identifier carried in the control instruction correspond to each other in the control binding relationship according to the account identifier and the target device identifier carried in the control instruction and according to the control binding relationship stored previously. If the account identifier and the target device identifier carried in the control instruction correspond to each other in the control binding relationship, the control message is sent to the hardware device corresponding to the device identifier carried in the control instruction, so that the hardware device 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 correspondence between the pre-stored 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 stores the device identifier and the corresponding book of the device control applet according to the device control applet for controlling the hardware device uploaded by the device provider terminal, after the server receives the binding request, the server can determine the identifier of the device control applet corresponding to the device identifier according to the corresponding relation between the device identifier stored in advance and the identifier of the device control applet and the device identifier carried in the binding request, and 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 corresponding relation between the enterprise identifier stored in advance and the account identifier in the server, and then the determined identifier of the device control applet is added into the applet list of the account corresponding to the determined account identifier.

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

In implementation, the correspondence between the device identifier and the device control applet identifier is stored in the server in advance, and when the number of the control applets of the control device is multiple, the server may store the multiple device control applet identifiers corresponding to the device identifier in the form of a list. When the server receives the binding request carrying the device identifier, the applet selection list corresponding to the device identifier carried in the binding request can be determined according to the applet selection list corresponding to each device identifier stored in advance, wherein the applet list comprises device control applets for controlling the hardware devices corresponding to the device identifiers carried in the binding request. And after the management terminal selects the identification of the device control applet in the applet selection list, receiving the identification of the device control applet selected by the management terminal, and then adding the identification of the device control applet selected by the management terminal into the applet list of the account corresponding to the determined account identification.

Step 507, when receiving an applet list request sent by a terminal logged in by any target account, sending the applet list of any target account to the terminal, and when receiving an applet acquisition request carrying an identifier of the target device control applet sent by the terminal, sending the target device control applet to the terminal.

The terminal can be an application terminal operated by staff in the enterprise, and accounts of staff in the enterprise are logged in the application terminal.

In implementation, when an enterprise application program of the application terminal is started, staff in the enterprise can send an applet list request to the server, wherein 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, staff in the enterprise select the applet identification in the applet list through the enterprise application program of the application terminal, and send an applet acquisition request to the server, wherein the applet acquisition request carries the identification of the selected device control applet, and the server sends the device control applet corresponding to the identification of the device control applet to the application terminal according to the identification of the device control applet.

According to the embodiment of the application, binding information of binding equipment and an enterprise is sent to a server through a management terminal in the enterprise, the server can add the applet of the control equipment corresponding to the equipment into an applet list of an enterprise employee account, then the applet list is sent to a terminal of the enterprise employee, and the enterprise employee can select the applet of the control equipment to control the equipment in the enterprise through the applet list of the terminal. Therefore, staff in the enterprise does not need to download corresponding operation application programs according to each hardware device, so that the staff in the enterprise can use the devices more conveniently.

Any combination of the above-mentioned optional solutions may be adopted to form an optional embodiment of the present disclosure, which is not described herein in detail.

An embodiment of the present application provides an apparatus for managing a hardware device, where the apparatus may be a management terminal in the foregoing embodiment, as shown in fig. 10, and 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 a plurality of target account identifiers corresponding to the target enterprise identifier based on a correspondence between prestored enterprise identifiers and account identifiers, determine a target device control applet corresponding to the target device identifier based on a correspondence between prestored 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 sub-module configured to:

displaying the applet selection list;

An embodiment of the present application provides an apparatus for managing a hardware device, where the apparatus may be a server in the foregoing embodiment, as shown in fig. 11, and 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 a plurality of target account identifiers corresponding to the target enterprise identifiers based on a correspondence between prestored enterprise identifiers and account identifiers;

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 an applet list of any target account to a terminal when receiving an applet list request sent by the terminal logged in to the target account, and send the target device control applet to the terminal when receiving an applet acquisition request sent by the terminal and carrying an identifier of the target device control applet.

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 transmitting sub-module:

It should be noted that: the apparatus for managing a hardware device according to the above embodiment is only exemplified by the above division of each functional module when managing a hardware device, and in practical application, the above functional allocation may be performed by different functional modules according to needs, that is, the internal structure of the apparatus is divided into different functional modules to perform all or part of the functions described above. In addition, the apparatus for managing a hardware device and the method embodiment for managing a hardware device provided in the foregoing embodiments belong to the same concept, and specific implementation processes of the apparatus for managing a hardware device are detailed in the method embodiment, which is not described herein again.

Fig. 12 shows a block diagram of a computer device according to 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 picture expert compression standard audio plane 3), an MP4 (Moving Picture Experts Group Audio Layer IV, motion picture expert compression standard audio plane 4) player, a notebook computer, or a desktop computer. Terminal 1200 may also be referred to as a user device, portable terminal, laptop terminal, desktop terminal, etc.

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

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 DSP (Digital Signal Processing ), FPGA (Field-Programmable Gate Array, field programmable gate array), PLA (Programmable Logic Array ). The processor 1201 may also include a main processor, which is a processor for processing data in an awake state, also called a CPU (Central Processing Unit ), and a coprocessor; a coprocessor is a low-power processor for processing data in a standby state. In some embodiments, the processor 1201 may integrate a GPU (Graphics Processing Unit, image processor) for rendering and rendering of content required to be displayed by the display screen. In some embodiments, the processor 1201 may also include an AI (Artificial Intelligence ) processor for processing computing operations 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 hardware devices provided by a method embodiment of the present application.

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

The peripheral interface 1203 may be used to connect at least one peripheral device associated with an I/O (Input/Output) to the processor 1201 and the memory 1202. In some embodiments, the processor 1201, the memory 1202, and the peripheral interface 1203 are integrated on the same chip or circuit board; in some other embodiments, either or both of the processor 1201, the memory 1202, and the peripheral interface 1203 may be implemented on separate chips or circuit boards, 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 via electromagnetic signals. The radio frequency circuit 1204 converts an electrical signal into an electromagnetic signal for transmission, or converts a received electromagnetic signal into an electrical signal. Optionally, the radio frequency circuit 1204 includes: antenna systems, RF transceivers, one or more amplifiers, tuners, oscillators, digital signal processors, codec chipsets, subscriber identity module cards, and so forth. The radio frequency circuit 1204 may communicate with other terminals via at least one wireless communication protocol. The wireless communication protocol includes, but is not limited to: metropolitan area networks, various generations of mobile communication networks (2G, 3G, 4G, and 5G), wireless local area networks, and/or WiFi (Wireless Fidelity ) networks. In some embodiments, the radio frequency circuit 1204 may also include NFC (Near Field Communication ) related circuits, which the present application is not limited to.

The display 1205 is used to display a UI (User Interface). The UI may include graphics, text, icons, video, and any combination thereof. When the display 1205 is a touch display, the display 1205 also has the ability to collect touch signals at or above the surface of the display 1205. The touch signal may be input as a control signal to the processor 1201 for processing. At this time, 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 a front panel of the terminal 1200; in other embodiments, the display 1205 may 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 a folded surface of the terminal 1200. Even more, the display 1205 may be arranged in an irregular pattern that is not rectangular, i.e., a shaped screen. The display 1205 can be made of LCD (Liquid Crystal Display ), OLED (Organic Light-Emitting Diode) or other materials.

The camera assembly 1206 is used to capture images or video. Optionally, camera assembly 1206 includes a front camera and a rear camera. Typically, the front camera is disposed on the front panel of the terminal and the rear camera is disposed on the rear surface of the terminal. In some embodiments, the at least two rear cameras are any one of a main camera, a depth camera, a wide-angle camera and a tele camera, so as to realize that the main camera and the depth camera are fused to realize a background blurring function, and the main camera and the wide-angle camera are fused to realize a panoramic shooting and Virtual Reality (VR) shooting function or other fusion shooting functions. In some embodiments, camera assembly 1206 may also include a flash. The flash lamp can be a single-color temperature flash lamp or a double-color temperature flash lamp. The dual-color temperature flash lamp refers to a combination of a warm light flash lamp and a cold light flash lamp, and can be used for light compensation under 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 to the processor 1201 for processing, or inputting the electric signals to the radio frequency circuit 1204 for voice communication. For purposes of stereo acquisition or noise reduction, a plurality of microphones may be respectively disposed at different portions of the terminal 1200. The microphone may also be an array microphone or an omni-directional pickup microphone. The speaker is used to convert electrical signals from the processor 1201 or the radio frequency circuit 1204 into sound waves. The speaker may be a conventional thin film speaker or a piezoelectric ceramic speaker. When the speaker is a piezoelectric ceramic speaker, not only the electric signal can be converted into a sound wave audible to humans, but also the electric signal can be converted into a sound wave inaudible to humans for ranging and other purposes. In some embodiments, the audio circuitry 1207 may also include a headphone jack.

The positioning component 1208 is used to position the current geographic location of the terminal 1200 to enable navigation or LBS (Location Based Service, location-based services). The positioning component 1208 may be a positioning component based on the united states GPS (Global Positioning System ), the beidou system of china, the grainer system of russia, or the galileo system of the european union.

The power supply 1209 is used to power the various components in the terminal 1200. The power source 1209 may be an alternating current, a direct current, a disposable battery, or a rechargeable battery. 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, gyroscope sensor 1212, pressure sensor 1213, fingerprint sensor 1214, optical sensor 1215, and proximity sensor 1216.

The acceleration sensor 1211 may detect the 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 gravitational acceleration in three coordinate axes. The processor 1201 may control the touch display 1205 to display a user interface in a landscape view or a portrait view based on the gravitational acceleration signal acquired by the acceleration sensor 1211. The acceleration sensor 1211 may also be used for the 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 may implement the following functions based on the data collected by the gyro sensor 1212: motion sensing (e.g., changing UI according to a tilting operation by a user), image stabilization at shooting, game control, and inertial navigation.

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

The fingerprint sensor 1214 is used to collect a fingerprint of the user, and the processor 1201 identifies the identity of the user based on the fingerprint collected by the fingerprint sensor 1214, or the fingerprint sensor 1214 identifies the identity of the user based on the fingerprint collected. Upon recognizing that the user's identity is a trusted identity, the processor 1201 authorizes the user to perform relevant sensitive operations including unlocking the screen, viewing encrypted information, downloading software, paying for and changing settings, etc. The fingerprint sensor 1214 may be provided on the front, back or side of the terminal 1200. When a physical key or a vendor Logo is provided on the terminal 1200, the fingerprint sensor 1214 may be integrated with the physical key or the 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 based on the ambient light intensity collected by the optical sensor 1215. Specifically, when the intensity of the ambient light is high, the display brightness of the touch display screen 1205 is turned up; when the ambient light intensity is low, the display brightness of the touch display screen 1205 is turned down. In another embodiment, processor 1201 may also dynamically adjust the shooting parameters of camera assembly 1206 based on the intensity of ambient light collected by optical sensor 1215.

A proximity sensor 1216, also referred to as a distance sensor, is typically provided on the front panel of the terminal 1200. The proximity sensor 1216 is used to collect the distance between the user and the front of the terminal 1200. In one embodiment, when the proximity sensor 1216 detects that the distance between the user and the front face of the terminal 1200 gradually decreases, the processor 1201 controls the touch display 1205 to switch from the bright screen state to the off screen state; when the proximity sensor 1216 detects that the distance between the user and the front surface of the terminal 1200 gradually increases, the touch display 1205 is controlled by the processor 1201 to switch from the off-screen state to the on-screen state.

It will be appreciated by those skilled in the art that the structure shown in fig. 12 is not limiting and that more or fewer components than shown may be included or certain components may be combined or a different arrangement of components may be employed.

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

In an exemplary embodiment, a computer readable storage medium, such as a memory comprising instructions executable by a processor in a terminal to perform the method of managing hardware devices in the above embodiment 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 for instructing relevant hardware, where the program may be stored in a computer readable storage medium, and the storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.

The foregoing description of the preferred embodiments of the present application is not intended to limit the application, but rather, the application is to be construed as limited to the appended claims.

Claims

1. A method of managing a hardware device, the method comprising:

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

the method comprises the steps of sending a binding request carrying target enterprise identifications and target equipment identifications to a server, receiving an applet selection list sent by the server, wherein the applet selection list comprises identifications of a plurality of equipment control applets, displaying the applet selection list, determining identifications of selected target equipment control applets in the applet selection list, sending the identifications of the target equipment control applets to the server, wherein the binding request is used for indicating the server to determine a plurality of target account identifications corresponding to the target enterprise identifications based on the corresponding relation between the prestored enterprise identifications and account identifications, determining the target equipment control applets corresponding to the target equipment identifications based on the corresponding relation between the prestored equipment identifications and the equipment control applets, and adding the target equipment control applets to the applet list of target accounts corresponding to each target account identification.

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

3. A method of managing a hardware device, the method comprising:

4. A method according to claim 3, wherein the binding request further carries at least one target department identifier;

5. The method according to claim 3, wherein the determining the 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, adding the identifier of the target device control applet to the applet list of the account corresponding to each target account identifier, comprises:

6. The method according to claim 3, wherein after determining the plurality of target account identifications corresponding to the target enterprise identifications based on the correspondence between the prestored enterprise identifications and the account identifications, the method further comprises:

7. An apparatus for managing a hardware device, the apparatus comprising:

the first sending module is configured to send a binding request carrying the target enterprise identifier and the target equipment identifier to a server, receive an applet selection list sent by the server, wherein the applet selection list comprises identifiers of a plurality of equipment control applets, display the applet selection list, determine the identifier of the selected target equipment control applet in the applet selection list, send the identifier of the target equipment control applet to the 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 the corresponding relation between the prestored enterprise identifier and the account identifier, determine the target equipment control applet corresponding to the target equipment identifier based on the corresponding relation between the prestored equipment identifier and the equipment control applet, and add the target equipment control applet to the applet list of the target account corresponding to each target account identifier.

8. An apparatus for managing a hardware device, the apparatus comprising:

the determining module is configured to determine a target device control applet corresponding to the target device identifier based on a corresponding relation between the pre-stored device identifier and the 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;

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

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

10. A computer-readable storage medium having stored therein at least one instruction that is loaded and executed by a processor to implement operations performed by the method of managing hardware devices of any one of claims 1 to 6.