WO2016206082A1

WO2016206082A1 - Terminal apparatus management method and device

Info

Publication number: WO2016206082A1
Application number: PCT/CN2015/082476
Authority: WO
Inventors: 陈志军; 高建平
Original assignee: 宇龙计算机通信科技(深圳)有限公司
Priority date: 2015-06-26
Filing date: 2015-06-26
Publication date: 2016-12-29

Abstract

A terminal apparatus management method and device. The method comprises: receiving a request for binding a target terminal apparatus and transmitted by a user (S101); upon detecting that a state of the target terminal apparatus is a sharing initiation state, binding the user and the target terminal apparatus (S102); when a current binding state of the target terminal apparatus satisfies a first preset condition, allocating a first role for the user (S103, S104); and when the current binding state of the target terminal apparatus does not satisfy the first preset condition, allocating a second role for the user (S104, S105), wherein only the first role has a permission for managing the target terminal apparatus. The method manages the permission of the terminal apparatus, and addresses the problem of a disorder of the terminal apparatus management permission.

Description

Terminal device management method and device

Technical field

The present application relates to the field of terminal device management technologies, and in particular, to a terminal device management method and device.

Background technique

Google started with the acquisition of terminal hardware items, and Apple first took the platform hardware. Under their call, home appliance companies, terminal hardware manufacturers, and Internet giants have entered the terminal hardware platform strategy. In 2013, it was called the first year of terminal hardware explosion. At one time, terminal hardware products emerged in an endless stream, such as air conditioners, refrigerators, and monitoring equipment.

That is to say, with the endless emergence of terminal hardware products, terminal devices play an increasingly important role in people's daily life and production applications. If effective authority management cannot be performed on terminal devices, the management rights of terminal devices are often disordered. problem.

Summary of the invention

In view of this, the present application provides a terminal device management method and apparatus, which avoids the problem of disordered management authority of the terminal device by managing rights of the terminal device.

In order to achieve the above objective, the technical solution provided by the embodiment of the present invention is as follows:

A terminal device management method includes:

Receiving a request sent by the user to bind the target terminal device;

Binding the user to the target terminal device when detecting that the state of the target terminal device is a sharing open state;

Determining whether the current binding state of the target terminal device meets a first preset condition, where the binding state includes the number of currently bound users of the target terminal device;

If yes, assign the first role to the user; if not, assign the second role to the user, wherein only the first role has the right to manage the target terminal device.

Preferably, the method further includes:

Receiving a device sharing request sent by the target user as the first role, where the device sharing request includes the first to-be-shared device information and the first to-be-shared user information;

Determining, by the first to-be-shared device information, each first to-be-shared device, where the first to-be The sharing device is a target terminal device bound to the target user;

Determining, according to the first to-be-shared user information, each first to-be-shared user;

For each of the first to-be-shared users, they are respectively bound to each of the first to-be-shared devices, and are assigned a second role.

Preferably, the method further includes:

Receiving, by the target user, a first to-be-shared user addition request corresponding to the device sharing request, where the first to-be-shared user addition request includes second to-be-shared user information;

Determining, according to the second to-be-shared user information, each second to-be-shared user;

For each of the second to-be-shared users, they are respectively bound to each of the first to-be-shared devices, and are assigned a second role.

Preferably, the method further includes:

Receiving a to-be-shared user deletion request corresponding to the device sharing request sent by the target user, where the to-be-shared user deletion request includes the first to-be-deleted user information;

Determining, according to the first to-be-deleted user information, the first to-be-removed user, the first to-be-deleted user being the first to-be-shared user or the second to-be-shared user;

And for each of the first to-be-deleted users, respectively, unbinding each of the first to-be-shared devices.

Preferably, the method further includes:

And receiving, by the target user, a to-be-shared device addition request corresponding to the device sharing request, where the to-be-shared device addition request includes second to-be-shared device information;

Determining, according to the second to-be-shared device information, the second to-be-shared device, where the second to-be-shared device is a target terminal device that is bound to the target user;

For each of the first to-be-shared users, they are respectively bound to each of the second to-be-shared devices, and are assigned a second role.

Preferably, the method further includes:

Receiving a to-be-shared device deletion request corresponding to the device sharing request sent by the target user, where the to-be-shared device deletion request includes first to-be-deleted device information;

Determining, according to the first information to be deleted, the first to be deleted device, where the first to be deleted device is the first to be shared device or the second to be shared device;

For each of the first to-be-deleted devices, each of the first to-be-shared users is unbound.

Preferably, the method further includes:

Receiving, by the target user, a first timing deletion request corresponding to the device sharing request, where the first timing deletion request includes second user information to be deleted;

Determining, according to the second to-be-deleted user information, each second to-be-deleted user, where the second to-be-deleted user is the first to-be-shared user;

When it is detected that the binding time of the second to-be-deleted user and the first to-be-shared device exceeds a preset first threshold, the second to-be-deleted user is shared with each of the first to-be-reviewed users. The device is unbound.

Preferably, the method further includes:

Receiving, by the target user, a second timing deletion request corresponding to the device sharing request, where the second timing deletion request includes second device information to be deleted;

Determining, according to the second information to be deleted, the second device to be deleted, where the second device to be deleted is the first device to be shared;

When it is detected that the binding time of the second to-be-deleted device and the first to-be-shared user exceeds a preset second threshold, the second to-be-deleted device is shared with each of the first to-be-disabled devices. User unbind.

Preferably, the method further includes:

Receiving, by the target user, a third timing deletion request corresponding to the device sharing request;

Detecting a time interval between a current time and a request to share the device;

When the time interval exceeds the preset third threshold, each of the first to-be-shared users is decoupled from each of the first to-be-shared devices.

Preferably, the method further includes:

Receiving, by the first to-be-shared user, a second to-be-shared user addition request corresponding to the device sharing request, where the second to-be-shared user addition request includes third to-be-shared user information;

Determining, according to the third to-be-shared user information, each third to-be-shared user, when the second to-be-shared user addition request meets the second preset condition;

For each of the third to-be-shared users, they are respectively bound to each of the first to-be-shared devices, and are assigned a second role.

Preferably, the method further includes:

And disconnecting the user from the target terminal device in response to receiving a request to release the target terminal device binding sent by the user of the first role or the second role.

A terminal device management device includes:

a request receiving unit, configured to receive a request sent by the user to bind the target terminal device;

a binding unit, configured to bind the user to the target terminal device when detecting that the state of the target terminal device is a sharing open state;

a determining unit, configured to determine whether the current binding state of the target terminal device meets a first preset condition, where the binding state includes the number of currently bound users of the target terminal device;

a role assignment unit, configured to allocate a first role to the user when the current binding state of the target terminal device meets the first preset condition; and when the current binding state of the target terminal device does not satisfy the first pre- When the condition is set, the user is assigned a second role, wherein only the first role has the right to manage the target terminal device.

The present invention provides a terminal device management method and apparatus, by receiving a request of a binding target terminal device sent by a user, and binding the user to the target terminal device when detecting that the state of the target terminal device is a sharing open state; Assigning a first role to the user when the current binding state of the target terminal device meets the first preset condition; and assigning the second role to the user when the current binding state of the target terminal device does not satisfy the first preset condition (where Only the first role has the authority to manage the target terminal device, and the rights management of the terminal device is realized, thereby avoiding the problem that the terminal device management authority is disordered.

DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are only It is an embodiment of the present invention, and those skilled in the art can obtain other drawings according to the provided drawings without any creative work.

1 is a flowchart of a method for managing a terminal device according to Embodiment 1 of the present application;

FIG. 2 is another terminal device tube provided on the basis of FIG. 1 above according to Embodiment 1 of the present application; Method flow chart;

FIG. 3 is a schematic structural diagram of a terminal device management apparatus according to Embodiment 2 of the present application.

detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, but not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

Embodiment 1:

FIG. 1 is a flowchart of a terminal device management method according to Embodiment 1 of the present application.

As shown in Figure 1, the method includes:

S101. Receive a request for binding a target terminal device sent by a user.

In the embodiment of the present application, preferably, when the user needs to operate a certain terminal device, the user terminal first needs to send a request for binding the target terminal device (the target terminal device here is a certain terminal device that the user needs to operate).

In the embodiment of the present application, preferably, the operation target terminal device includes using the target terminal device, managing and using the target terminal device, and the like.

Specifically, the using the terminal device includes: the terminal device sends the alarm information to the user (eg, when the camera monitors the entry of the person, sends the corresponding alarm information to the user who uses the camera), and the linkage between the terminal devices (eg, the camera and the camera) When the sounder is used by the user at the same time, when the camera monitors the entry of the person, an alarm message can be sent to the buzzer to control the buzzer alarm).

The above is only a preferred mode of the embodiment of the present application, and the inventor can arbitrarily set the manner of operating the target terminal device according to his own needs, which is not limited herein.

S102. Bind the user to the target terminal device when detecting that the state of the target terminal device is the sharing open state.

In the embodiment of the present application, after receiving the request of the binding target terminal device sent by the user, it is required to detect whether the state of the target terminal device is the sharing-on state, and when the state of the target terminal device is the sharing-on state. , the user is bound to the target terminal device.

Further, in the embodiment of the present application, preferably, when the detected target terminal device is When the status is shared off, the execution is stopped, which means that the user fails to bind to the target terminal device.

The above is only a preferred mode of the embodiment of the present application. The inventor can arbitrarily set the state of the target terminal device according to the needs of the user, such as the status of the shared inquiry, which is not limited herein.

In the embodiment of the present application, preferably, when the state of the target terminal device is the sharing query state, it is required to query whether the target terminal device can be bound by the user, and when yes, bind the user to the target terminal device; When no, the execution is stopped, which means that the user fails to bind to the target terminal device.

S103, determining whether the current binding state of the target terminal device meets the first preset condition; when satisfied, step S104 is performed; when not satisfied, step S105 is performed;

In the embodiment of the present application, after the user is bound to the target terminal device, it is required to determine whether the current binding state of the target terminal device meets the first preset condition, where the binding state includes the current target device. The number of users that have been bound.

Specifically, in the embodiment of the present application, after the user is bound to the target terminal device, the number of users bound to the current target terminal device is calculated, and the number of users bound on the current target terminal device is At 1 o'clock, it is determined that the current binding state of the target terminal device meets the first preset condition, and then step S104 is performed; when the number of users bound on the current target terminal device is greater than 1, the current binding of the target terminal device is determined. The state does not satisfy the first preset condition, and then step S105 is performed.

The above is only a preferred mode of the embodiment of the present application. The inventor can arbitrarily set the specific content of the current binding state of the target terminal device according to the needs of the user, and determine whether the current binding state of the target terminal device meets the first preset condition. The way is not limited here.

S104. Assign a first role to the user.

In the embodiment of the present application, preferably, when the user needs to operate the target terminal device, the user needs to be bound to the target terminal device, and after the user is assigned the corresponding role, the user can operate the terminal device.

In the embodiment of the present application, preferably, when the current binding state of the target terminal device meets the first preset condition, the first role is assigned to the user, that is, the user needs to operate the target as the first role. Terminal Equipment.

S105. Assign a second role to the user.

In the embodiment of the present application, preferably, when the current binding state of the target terminal device does not satisfy the first preset condition, the second role is assigned to the user, that is, the user needs to operate the identity as the second role. Target terminal device.

In the embodiment of the present application, preferably, the difference between the first role and the second role is that only the first role has the right to manage the target terminal device.

In the embodiment of the present application, preferably, the first role and the second role have the right to use the target terminal device. The above is only the preferred mode of the embodiment of the present application, and the inventor can arbitrarily set the first role according to his own needs. The common authority with the second role, but it is necessary to ensure that only the first role has the right to manage the target terminal device, that is, the user with only the first role has the management of the target terminal device. Permissions.

The present application provides a terminal device management method, by receiving a request from a user to bind a target terminal device; and when detecting that the state of the target terminal device is a sharing open state, binding the user to the target terminal device; and when the target When the current binding state of the terminal device meets the first preset condition, the first role is assigned to the user; when the current binding state of the target terminal device does not satisfy the first preset condition, the second role is assigned to the user (where only The first role has the right to manage the rights of the target terminal device, and the rights management of the terminal device is realized, thereby avoiding the problem that the terminal device management authority is disordered.

In the embodiment of the present application, preferably, when there is no user as the first role corresponding to the target terminal device, the status of the target terminal device (eg, sharing open state, sharing closed state, etc.) is determined by the target terminal. The device itself controls; when there is a user who is the first role corresponding to the target terminal device, the state of the target terminal device is controlled by the user who is the first role corresponding to the target terminal device.

The above is only a preferred mode of the embodiment of the present application, and the inventor can arbitrarily set the controller of the state of the target terminal device according to his own needs, and the control time, which is not limited herein.

Further, on the basis of the terminal device management method shown in FIG. 1 provided in the first embodiment of the present application, another terminal device management method is further included, as shown in FIG. 2 .

As shown in Figure 2, the method includes:

S201: Receive a device sharing request sent by a target user that is the first role, where the device sharing request includes the first to-be-shared device information and the first to-be-shared user information.

In the embodiment of the present application, preferably, the user can be bound to several terminal devices by using the terminal device management method shown in FIG. 1 above, and a first role is assigned to each terminal device to enable the user. The management of the corresponding terminal device is implemented by the identity of the first role.

In the embodiment of the present application, preferably, when the user is bound to the target terminal device and assigned the first role, the user can share the target terminal device to other users.

Specifically, on the basis of the terminal device management method shown in FIG. 1 provided by the embodiment of the present application, the method further includes: receiving a device sharing request sent by a user who is the first role, and the user who is the first role may The target sharing user includes the first to-be-shared device information and the first to-be-shared user information.

S202: Determine, by using the first to-be-shared device information, the first to-be-shared device, where the first to-be-shared device is a target terminal device that is bound to the target user;

Specifically, in the embodiment of the present application, the first to-be-shared device information in the device sharing request sent by the target user that is received as the first role is determined, and each of the first to-be-shared devices is determined, and the determined each to be shared. The device is a target terminal device that is bound to the target user.

S203. Determine, according to the first to-be-shared user information, each first to-be-shared user.

S204. Bind each of the first to-be-shared devices to each of the first to-be-shared devices, and assign a second role to them.

In the embodiment of the present application, preferably, for each first to-be-shared user, the following process is performed: binding the first to-be-shared user to each first to-be-shared device, and the first to-be-shared user is bound After the device to be shared is configured, the first to-be-shared user is assigned a second role, so that the user manages the device to be shared with the second role by the identity of the second role.

In the embodiment of the present application, the user who is the second role has the same management authority as the user of the device to be shared, and is not described here.

In the embodiment of the present application, the application scenario in which the target user performs device sharing may be: the target user establishes a sharing group, and the first to-be-shared device and the first to-be-shared user are pulled into the sharing group, and the confirmation button is clicked. The device sharing request is sent by the target user, and the device sharing request includes the first device information to be shared (the first device to be shared device is pulled into the sharing group). The first to-be-shared device determines) and the first to-be-shared user information (the first to-be-shared user information is determined by the first to-be-shared user that is pulled into the sharing group), and further passes through the terminal device as shown in FIG. 2 The management method can implement the sharing process of the terminal device, that is, sharing each of the first to-be-shared devices in the sharing group to each of the first to-be-shared users in the sharing group.

The present application further provides a terminal device management method as shown in FIG. 2 on the basis of the terminal device management method shown in FIG. 1 provided above, so that the target user as the first role can share the terminal device bound thereto. To the corresponding user, the flexibility of the terminal device management method provided by the embodiment of the present application is effectively increased.

Further, the terminal device management method provided by the embodiment of the present application further includes: receiving, by the target user, a first to-be-shared user addition request corresponding to the device sharing request, where the first to-be-shared user addition request includes the second The user information to be shared is determined; and each of the second to-be-shared users is determined according to the second to-be-shared user information; and, for each second to-be-shared user, each of the first to-be-shared devices is separately bound and Assign a second role.

In the embodiment of the present application, after the target user shares the first to-be-shared device to each of the first to-be-shared users, the user may also need to add other users to share the first ones on the basis of the device sharing. The device to be shared, in this case, the target user needs to send a first to-be-shared user addition request corresponding to the device sharing request, where the first to-be-shared user addition request includes the second to-be-shared user information, and the second to-be-shared user The user information may determine each of the second to-be-shared users, and then perform the following process for each second to-be-shared user. The process includes: binding the second to-be-shared user to each of the first to-be-shared devices, and each time After the second to-be-shared user is bound to the first to-be-shared device, the second to-be-shared user is assigned a second role corresponding to the first to-be-shared device, so that the second to-be-shared user can pass the second role. The identity of the first to-be-shared device is managed to share the first to-be-shared device with each of the first to-be-shared users. The second object of the user to be shared.

Further, the terminal device management method provided by the embodiment of the present application further includes: receiving a to-be-shared user deletion request corresponding to the device sharing request sent by the target user, where the to-be-shared user deletion request includes the first to-be-deleted user information And, according to the first user information to be deleted Determining each of the first to-be-shared users, and the first to-be-removed user is the first to-be-shared user or the second to-be-shared user; and, for each of the first to-be-deleted users, respectively, unbinding each of the first to-be-shared devices set.

In the embodiment of the present application, after the target user shares the first to-be-shared device with each of the first to-be-shared user and the second to-be-shared user, there may be a situation that the first device to be shared is not shared. Providing a user to be shared by the first user to be shared and the second user to be shared, wherein the target user needs to send a user to be shared request corresponding to the device sharing request, and the to-be-shared user deletion request includes the first to be deleted. The user information may be determined according to the first to-be-deleted user information, and the following process is performed for each of the first to-be-deleted users. The process includes: the first to-be-deleted user and each first to-be-deleted The sharing device is unbound, and the first to-be-removed user cannot be managed to share the first to-be-shared device with the second to-be-shared device. User's purpose.

Further, in the terminal device management method provided by the embodiment of the present application, the method further includes: receiving a device to be shared device request corresponding to the device sharing request sent by the target user, where the device to be shared device includes the second device to be shared device And determining, according to the second to-be-shared device information, the second to-be-shared device, the second to-be-shared device being the target terminal device bound to the target user; and, for each of the first to-be-shared users, respectively The second to-be-shared device is bound and assigned a second role.

In the embodiment of the present application, after the target users share the first to-be-shared devices to each of the first to-be-shared users, the other users may be bound to the target users based on the sharing of the devices. The target terminal device is shared with each of the first to-be-shared users. The target user needs to send a device to be shared request corresponding to the device sharing request, and the device to be shared device includes the second device to be shared. The second to-be-shared device information may be used to determine the second to-be-shared device, and the following process is performed for each of the first to-be-shared users. The process includes: binding the first to-be-shared user to each second to-be-shared device. And each time the first to-be-shared user is bound to the second to-be-shared device, the second role corresponding to the second to-be-shared device is allocated to the first to-be-shared user, so that the first to-be-shared user utilizes the first Two The identity of the role is managed by the second to-be-shared device. The second device to be shared is shared with each of the first to-be-shared users.

Further, in the terminal device management method provided by the embodiment of the present application, the method further includes: receiving a to-be-shared device deletion request corresponding to the device sharing request sent by the target user, where the to-be-shared device deletion request includes the first to-be-deleted device information And determining, according to the first to-be-deleted device information, the first to-be-deleted device is the first to-be-shared device or the second to-be-shared device; and, for each of the first to-be-deleted devices, respectively Each first share to be shared is unbound.

In the embodiment of the present application, after the target user shares the first to-be-shared device to each of the first to-be-shared users, the first to-be-shared device or the second device to be shared may not be shared. For the first to be shared user, the target user needs to send a device to be shared request corresponding to the device sharing request, and the to-be-shared device deletion request includes the first device to be deleted, according to the first device to be deleted. The information may be determined by each of the first to be deleted devices, and the following process is performed for each of the first to be deleted devices. The process includes: unbinding the first to-be-deleted device with each first to-be-shared user, and unbinding each The first to-be-shared user cannot manage the first to-be-discarded device in the identity of the second role, so as to achieve the purpose of not sharing the first to-be-deleted device with each of the first to-be-shared users.

Further, the terminal device management method provided by the embodiment of the present application further includes: receiving a first timing deletion request that is sent by the target user and corresponding to the device sharing request, where the first timing deletion request includes the second to-be-deleted user information. And determining, according to the second to-be-deleted user information, the second to-be-removed user, the second to-be-deleted user being the first to-be-shared user; and detecting the binding time of the second to-be-deleted user and the first to-be-shared device When the preset first threshold is exceeded, the second to-be-disconnected user is decoupled from each of the first to-be-shared devices.

In the embodiment of the present application, after the target user shares the first to-be-shared device to each of the first to-be-shared users, there may be a situation that the first user to be shared is periodically deleted. The target user needs to send the first timer corresponding to the device sharing request. In addition to the request, the first timing deletion request includes the second to-be-deleted user information, and each second to-be-deleted user is determined according to the second to-be-deleted user information, and then the following process is performed for each second to-be-deleted user (the process includes: When the binding time of the second to-be-removed user and the first to-be-shared device exceeds a preset first threshold, the second to-be-deleted user is unbounded from each of the first to-be-shared devices, The deleting user can no longer manage each of the first to-be-shared devices in the identity of the second role, so as to delete the second to-be-deleted user periodically, and not share the first to-be-shared device with the second to-be-deleted user.

Further, the terminal device management method provided by the embodiment of the present application further includes: receiving a second timing deletion request that is sent by the target user and corresponding to the device sharing request, where the second timing deletion request includes the second to-be-deleted device information. And determining, according to the second to-be-deleted device information, the second device to be deleted, the second to-be-deleted device being the first device to be shared; and detecting the binding time of the second device to be deleted and the first user to be shared When the second threshold is exceeded, the second to-be-deleted device is decoupled from each of the first to-be-shared users.

In the embodiment of the present application, after the target user shares the first to-be-shared device to each of the first to-be-shared users, there may be a situation that the first device to be shared is periodically deleted. The target user needs to send a second timing deletion request corresponding to the device sharing request, where the second timing deletion request includes the second to-be-deleted device information, and the second to-be-deleted device is determined according to the second to-be-deleted device information, and then The second to-be-deleted device performs the following process: the process includes: when it is detected that the binding time of the second to-be-deleted device and the first to-be-shared user exceeds a preset second threshold, the second to-be-deleted device and each first The shared user is unbound, and the first to-be-shared user can no longer manage the second to-be-deleted device by the second role. The purpose of each first share to be shared.

Further, in a terminal device management method provided by the embodiment of the present application, the method further includes: receiving a third timing deletion request that is sent by the target user and corresponding to the device sharing request; and detecting a time when the current time and the receiving device share the request And, when the time interval exceeds the preset third threshold, each of the first to-be-shared users is decoupled from each of the first to-be-shared devices.

In the embodiment of the present application, after the target user shares the first to-be-shared device with each of the first to-be-shared users, there may be a situation that the sharing is cancelled periodically. At this time, the target user needs to send And a third timing deletion request corresponding to the device sharing request, and detecting a current time (the current time here, that is, a time when the third timing deletion request is received) and a time interval for sharing the request with the receiving device; and, when the time interval exceeds the pre- When the third threshold is set, each of the first to-be-shared users is de-bound to each of the first to-be-shared devices, so that each of the first to-be-shared users cannot be managed as the second role. The purpose of the device to be shared.

Further, the terminal device management method provided by the embodiment of the present application further includes: receiving a second to-be-shared user addition request corresponding to the device sharing request sent by the first to-be-shared user, and the second to-be-shared user adding request The third to-be-shared user information is included; and when the second to-be-shared user addition request satisfies the second preset condition, each third to-be-shared user is determined according to the third to-be-shared user information; and, for each third to-be-shared The user binds each of them to each of the first to-be-shared devices and assigns a second role to them.

In the embodiment of the present application, after the target user shares the first to-be-shared device to each of the first to-be-shared users, there may be a situation in which the first to-be-shared user needs to be the first one. The device to be shared is shared with a user. In this case, the first to-be-shared user needs to send a second to-be-shared user addition request corresponding to the device sharing request, and the second to-be-shared user addition request includes the third to-be-shared user information. After receiving the request to add to the second to-be-shared user, and the third to-be-shared user addition request satisfies the second preset condition, the third to-be-shared user may be determined according to the third to-be-shared user information, and for each The third to-be-shared user performs the following process. The process includes: binding the third to-be-shared user to each of the first to-be-shared devices, and each time the third to-be-shared user is bound to the first to-be-shared device, The third to-be-shared user allocates a second role corresponding to the first to-be-shared device, so that the third to-be-shared user manages the first to-be-subscribed by using the identity of the second role. The device is configured to share the first to-be-shared device with the third to-be-shared user.

In the embodiment of the present application, preferably, the second preset condition includes: the second to-be-shared user addition request is allowed by the target user, that is, only after the second to-be-shared user addition request is confirmed by the target user, Each third shared user to be shared in the user add request can be divided into Enjoy each of the first devices to be shared.

The above is only a preferred mode of the embodiment of the present application, and the inventor can arbitrarily set the specific expression of the second preset condition according to his own needs, which is not limited herein.

Further, in a terminal device management method provided by the embodiment of the present application, the method further includes: responding to the request for releasing the target terminal device binding sent by the user who is the first role or the second role, and the user and the target terminal The device is unbound.

In the embodiment of the present application, after the target user shares the first to-be-shared device to each of the first to-be-shared users, there may be a situation in which the user who is the first role (the target user) Or the user who is the second role needs to release the binding with the target terminal device. At this time, the user who is the first role or the second role needs to send a request to release the binding of the target terminal device, and then receive and release the request. After the request of the target terminal device is bound, responding to the request, and unbinding the user with the target terminal device, so that the user who is the first role can no longer manage the target terminal device as the identity of the first role, and The user of the second role can no longer manage the target terminal device as the second role.

Further, in the embodiment of the present application, preferably, after the user who is the first role is unbound from the target terminal device, the user who is the second role that is shared by the target terminal device cannot be The identity of the second role manages the target terminal device.

The above is only a preferred mode of the embodiment of the present application. The inventor can arbitrarily set other processing modes after the user who is the first role or the user of the second role is unbound from the target terminal device according to the needs of the present application, which is not limited herein. .

The terminal device management method provided by the embodiment of the present application is more clear and complete, and is convenient for those skilled in the art to understand.

As shown in Figure 3, the device comprises:

The request receiving unit 1 is configured to receive a request of the binding target terminal device sent by the user;

The binding unit 2 is configured to: when detecting that the state of the target terminal device is a sharing open state, Bind the user to the target terminal device;

The determining unit 3 is configured to determine whether the current binding state of the target terminal device meets the first preset condition, where the binding state includes the number of users currently bound by the target terminal device;

a role assignment unit 4, configured to allocate a first role to the user when the current binding state of the target terminal device meets the first preset condition; and when the current binding state of the target terminal device does not satisfy the first When the condition is preset, the user is assigned a second role, wherein only the first role has the right to manage the target terminal device.

The present application provides a terminal device management apparatus, by receiving a request of a binding target terminal device sent by a user, and binding the user to the target terminal device when detecting that the state of the target terminal device is a sharing open state; and when the target When the current binding state of the terminal device meets the first preset condition, the first role is assigned to the user; when the current binding state of the target terminal device does not satisfy the first preset condition, the second role is assigned to the user (where only The first role has the right to manage the rights of the target terminal device, and the rights management of the terminal device is realized, thereby avoiding the problem that the terminal device management authority is disordered.

The various embodiments in the present specification are described in a progressive manner, and each embodiment focuses on differences from other embodiments, and the same similar parts between the various embodiments may be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part.

The above is only a preferred embodiment of the present application, so that those skilled in the art can understand or implement the present application. Various modifications to these embodiments are obvious to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the application. Therefore, the application is not limited to the embodiments shown herein, but is to be accorded the broadest scope of the principles and novel features disclosed herein.

Claims

A terminal device management method, comprising:

Receiving a request sent by the user to bind the target terminal device;

Binding the user to the target terminal device when detecting that the state of the target terminal device is a sharing open state;

Determining whether the current binding state of the target terminal device meets a first preset condition, where the binding state includes the number of currently bound users of the target terminal device;

If yes, assign the first role to the user; if not, assign the second role to the user, wherein only the first role has the right to manage the target terminal device.
The method of claim 1 further comprising:

Receiving a device sharing request sent by the target user as the first role, where the device sharing request includes the first to-be-shared device information and the first to-be-shared user information;

Determining, by the first to-be-shared device information, the first to-be-shared device, where the first to-be-shared device is a target terminal device that is bound to the target user;

Determining, according to the first to-be-shared user information, each first to-be-shared user;

For each of the first to-be-shared users, they are respectively bound to each of the first to-be-shared devices, and are assigned a second role.
The method of claim 2, further comprising:

Receiving, by the target user, a first to-be-shared user addition request corresponding to the device sharing request, where the first to-be-shared user addition request includes second to-be-shared user information;

Determining, according to the second to-be-shared user information, each second to-be-shared user;

For each of the second to-be-shared users, they are respectively bound to each of the first to-be-shared devices, and are assigned a second role.
The method of claim 3, further comprising:

Receiving a to-be-shared user deletion request corresponding to the device sharing request sent by the target user, where the to-be-shared user deletion request includes the first to-be-deleted user information;

Determining, according to the first to-be-deleted user information, the first to-be-removed user, the first to-be-deleted user being the first to-be-shared user or the second to-be-shared user;

For each of the first to-be-deleted users, respectively, and each of the first to-be-shared devices Unbind.
The method of claim 2, further comprising:

And receiving, by the target user, a to-be-shared device addition request corresponding to the device sharing request, where the to-be-shared device addition request includes second to-be-shared device information;

Determining, according to the second to-be-shared device information, the second to-be-shared device, where the second to-be-shared device is a target terminal device that is bound to the target user;

For each of the first to-be-shared users, they are respectively bound to each of the second to-be-shared devices, and are assigned a second role.
The method of claim 5, further comprising:

Receiving a to-be-shared device deletion request corresponding to the device sharing request sent by the target user, where the to-be-shared device deletion request includes first to-be-deleted device information;

Determining, according to the first information to be deleted, the first to be deleted device, where the first to be deleted device is the first to be shared device or the second to be shared device;

For each of the first to-be-deleted devices, each of the first to-be-shared users is unbound.
The method of claim 2, further comprising:

Receiving, by the target user, a first timing deletion request corresponding to the device sharing request, where the first timing deletion request includes second user information to be deleted;

Determining, according to the second to-be-deleted user information, each second to-be-deleted user, where the second to-be-deleted user is the first to-be-shared user;

When it is detected that the binding time of the second to-be-deleted user and the first to-be-shared device exceeds a preset first threshold, the second to-be-deleted user is shared with each of the first to-be-reviewed users. The device is unbound.
The method of claim 7 further comprising:

Receiving, by the target user, a second timing deletion request corresponding to the device sharing request, where the second timing deletion request includes second device information to be deleted;

Determining, according to the second information to be deleted, the second device to be deleted, where the second device to be deleted is the first device to be shared;

When it is detected that the binding time of the second to-be-deleted device and the first to-be-shared user exceeds When the second threshold is preset, it is debinding to each of the first to-be-shared users for the second to-be-deleted device.
The method of claim 2, further comprising:

Receiving, by the target user, a third timing deletion request corresponding to the device sharing request;

Detecting a time interval between a current time and a request to share the device;

When the time interval exceeds the preset third threshold, each of the first to-be-shared users is decoupled from each of the first to-be-shared devices.
The method of claim 2, further comprising:

Receiving, by the first to-be-shared user, a second to-be-shared user addition request corresponding to the device sharing request, where the second to-be-shared user addition request includes third to-be-shared user information;

Determining, according to the third to-be-shared user information, each third to-be-shared user, when the second to-be-shared user addition request meets the second preset condition;

For each of the third to-be-shared users, they are respectively bound to each of the first to-be-shared devices, and are assigned a second role.
The method of claim 2, further comprising:

And disconnecting the user from the target terminal device in response to receiving a request to release the target terminal device binding sent by the user of the first role or the second role.
A terminal device management device, comprising:

a request receiving unit, configured to receive a request sent by the user to bind the target terminal device;

a binding unit, configured to bind the user to the target terminal device when detecting that the state of the target terminal device is a sharing open state;

a determining unit, configured to determine whether the current binding state of the target terminal device meets a first preset condition, where the binding state includes the number of currently bound users of the target terminal device;

a role assignment unit, configured to allocate a first role to the user when the current binding state of the target terminal device meets the first preset condition; and when the current binding state of the target terminal device does not satisfy the first pre- When the condition is set, the user is assigned a second role, wherein only the first role has the right to manage the target terminal device.