CN106339632B - A method, user equipment and system for allocating M2M device management authority - Google Patents

Abstract

The embodiment of the invention discloses a kind of methods for distributing M2M equipment management permission, has the ability for the administration authority distribution request that M2M equipment is sent to server for user equipment, so that other users equipment is likewise supplied with the administration authority of M2M equipment, to realize that multiple user equipmenies have the administration authority of M2M equipment, user experience is improved.The described method includes: the first user equipment obtains the corresponding specified application identities of second user equipment, first user equipment has the first administration authority of M2M equipment；First user equipment sends the administration authority distribution request of the M2M equipment according to the corresponding specified application identities of the second user equipment to server, so that the server binds the corresponding specified application identities of second user equipment mark corresponding with the M2M equipment, so that the second user equipment has the second administration authority of the M2M equipment.

Description

A method, user equipment and system for allocating M2M device management authority

technical field

The present invention relates to the field of communication technologies, in particular to a method, user equipment and system for allocating M2M device management authority.

Background technique

Today, machine-to-machine (M2M, machine-to-machine) devices can realize intelligent, interactive and seamless connection between people and machines through social applications. Therefore, social applications will become a very important IoT connector.

The implementation principle of the IoT is to bind the designated application identifier corresponding to the user equipment with the identifier corresponding to the M2M device, and the user equipment controls and operates the M2M device through the corresponding designated application identifier. For example, Figure 1 shows a main technical architecture of WeChat IoT, in which WeChat IoT mainly adopts the "cloud-to-cloud" technical solution, that is, the WeChat public account corresponding to the user device is bound to the device ID corresponding to the M2M device. , so that the user equipment has the management authority of the M2M equipment, and the user equipment can control and operate the M2M equipment through the WeChat public account.

However, when the user equipment has the management authority of the M2M device, the user equipment does not have the ability to send the management authority assignment request of the M2M device to the server, so that the user equipment cannot assign the additional management authority of the M2M device to other user equipment through the server, thereby affect the user experience.

SUMMARY OF THE INVENTION

Embodiments of the present invention provide a method, user equipment, and system for allocating M2M device management authority, so that the user equipment has the ability to send an M2M device management authority allocation request to a server, and then allocates the M2M equipment additional management authority through the server. For other user equipments, the other user equipments also have the management authority of the M2M equipment, so that multiple user equipments have the management authority of the M2M equipment, and the user experience is improved.

A first aspect of the present invention provides a method for allocating M2M device management authority, including:

The first user equipment obtains the designated application identifier corresponding to the second user equipment, the first user equipment has the first management authority of the M2M device, and the designated application identifier corresponding to the second user equipment is logged on the second user equipment The specified application ID corresponding to the application of ;

The first user equipment sends a management authority assignment request of the M2M device to the server according to the specified application identifier corresponding to the second user equipment, where the management authority assignment request is used to instruct the server to send the second user equipment Sending a management request of the M2M device, where the management request is used to instruct the second user equipment to send a binding request of the M2M device to the server, where the binding request is used to instruct the server to bind the M2M device to the server The specified application identifier corresponding to the second user equipment is bound with the identifier corresponding to the M2M device, and binding confirmation information is sent to the second user equipment, where the binding confirmation information is used to indicate the second user equipment Possess the second management authority of the M2M device;

Wherein, the binding request includes a designated application identifier corresponding to the second user equipment and an identifier corresponding to the M2M device.

Combined with the first aspect, in the first possible implementation manner,

The management authority assignment request and the management request include the specified application identifier corresponding to the second user equipment, the identifier corresponding to the M2M device, device management information and device binding credential information, and the corresponding identifier of the first user equipment. The designated application identifier, the identifier corresponding to the M2M device includes the designated application identifier corresponding to the M2M device and/or the device identifier corresponding to the M2M device;

The binding request further includes the device binding credential information corresponding to the M2M device.

With reference to the first possible implementation manner of the first aspect, in a second possible implementation manner, the management authority assignment request further includes authority period information corresponding to the second management authority, and the method further includes:

The first user equipment sends a permission period modification request to the server, where the permission period modification request is used to instruct the server to modify the permission period information, and send permission period modification confirmation information to the second user equipment, The authority period modification confirmation information is used to indicate that the second management authority corresponds to a new authority period;

Wherein, the permission period modification request includes the specified application identifier corresponding to the second user equipment, the identifier corresponding to the M2M device, and permission period modification information.

With reference to the first aspect or any one of the possible implementation manners of the first to second aspects of the first aspect, in a third possible implementation manner, the method further includes:

The first user equipment sends a request for canceling the management authority to the server, where the request for canceling the management authority is used to instruct the server to cancel the relationship between the specified application identification corresponding to the second user equipment and the identification corresponding to the M2M device. the binding relationship, and send confirmation information for canceling the management authority to the second user equipment, where the confirmation information for canceling the management authority is used to indicate that the second user equipment does not have the second management authority of the M2M device;

The request for canceling the management authority includes the specified application identifier corresponding to the second user equipment, the identifier corresponding to the M2M device, and management authority cancellation information.

With reference to the third possible implementation manner of the first aspect, in a fourth possible implementation manner, before the first user equipment sends the request for canceling the management authority to the server, the method further includes:

The first user equipment deletes the second management authority of the second user equipment to the M2M device, including any one of the following methods:

The first user equipment selects a rights management interface on the designated application toolbar interface corresponding to the M2M device, and deletes the second management rights of the second user equipment to the M2M device on the rights management interface ;

or,

The first user equipment selects a rights management interface in the designated application menu bar option corresponding to the M2M device, and deletes the second management rights of the second user equipment to the M2M device on the rights management interface ;

or,

The first user equipment deletes the second management authority of the M2M device by the second user equipment through a voice or text command on the designated application dialog interface corresponding to the M2M device;

or,

The first user equipment clicks the icon corresponding to the M2M device on the designated application interface corresponding to the M2M device, selects a rights management interface, and deletes the second user equipment's access to the M2M device on the rights management interface. The second management authority of the device;

or,

The first user equipment selects the rights management interface by long pressing the icon corresponding to the M2M device on the designated application interface corresponding to the M2M device, and deletes the second user equipment on the rights management interface. the second management authority of the M2M device.

With reference to the fourth possible implementation manner of the first aspect, in a fifth possible implementation manner, the acquiring, by the first user equipment, the specified application identifier corresponding to the second user equipment includes:

obtaining, by the first user equipment, a designated application identifier corresponding to the second user equipment from a designated application interface corresponding to the M2M device;

or,

The first user equipment acquires the specified application identifier corresponding to the second user equipment from the specified application dialog interface corresponding to the M2M device.

With reference to the fifth possible implementation manner of the first aspect, in a sixth possible implementation manner, before the first user equipment acquires the specified application identifier corresponding to the second user equipment, the method further includes:

the first user equipment selects the M2M device;

The first user equipment selects a user icon corresponding to the second user equipment on the management interface of the M2M device;

The first user equipment selects any application corresponding to the second user equipment as the designated application on the management interface of the user icon corresponding to the second user equipment.

A second aspect of the present invention provides a method for allocating M2M device management authority, including:

The server receives a management authority assignment request of an M2M device sent by a first user equipment, the first user equipment has the first management authority of the M2M device, and the M2M device has at least one;

The server sends a management request of the M2M device to the second user equipment according to the management authority assignment request, where the management request is used to instruct the second user equipment to send the binding request of the M2M device to the server ;

The server receives the binding request sent by the second user equipment, where the binding request includes a designated application identifier corresponding to the second user equipment and an identifier corresponding to the M2M device, and the second user equipment The designated application identifier corresponding to the device is the designated application identifier corresponding to the application logged in on the second user equipment;

The server binds the specified application identifier corresponding to the second user equipment with the identifier corresponding to the M2M device according to the binding request;

The server sends binding confirmation information to the second user equipment, where the binding confirmation information is used to indicate that the second user equipment has the second management authority of the M2M device.

With reference to the second aspect, in a first possible implementation manner, the method further includes:

The management authority assignment request and the management request include the specified application identifier corresponding to the second user equipment, the identifier corresponding to the M2M device, device management information and device binding credential information, and the corresponding identifier of the first user equipment. The designated application identifier, the identifier corresponding to the M2M device includes the designated application identifier corresponding to the M2M device and/or the device identifier corresponding to the M2M device;

The binding request further includes the device binding credential information corresponding to the M2M device.

With reference to the first possible implementation manner of the second aspect, in a second possible implementation manner, the management authority assignment request further includes authority period information corresponding to the second management authority, and the method further includes:

receiving, by the server, a request for modifying the permission period sent by the first user equipment;

The server modifies the permission term information according to the permission term modification request;

sending, by the server, authority period modification confirmation information to the second user equipment, where the authority period modification confirmation information is used to indicate that the second management authority corresponds to a new authority period;

Wherein, the management period modification request includes the specified application identifier corresponding to the second user equipment, the identifier corresponding to the M2M device, and permission period modification information.

With reference to the second aspect or any one of the first possible to second possible implementations of the second aspect, in a third possible implementation, the method further includes:

receiving, by the server, a request for canceling the management authority sent by the first user equipment;

The server modifies the permission period information according to the request for canceling the management permission;

sending, by the server, confirmation information for canceling management authority to the second user equipment, where the confirmation information for canceling management authority is used to instruct to cancel the second management authority of the second user equipment for the M2M device;

The request for canceling the management authority includes the specified application identifier corresponding to the second user equipment, the identifier corresponding to the M2M device, and management authority cancellation information.

A third aspect of the present invention provides a user equipment, including:

an acquisition module, configured to acquire a designated application identifier corresponding to the second user equipment, where the designated application identifier corresponding to the second user equipment is a designated application identifier corresponding to an application logged in on the second user equipment;

A sending module, configured to send a management authority allocation request of the M2M device to the server according to the specified application identifier corresponding to the second user equipment obtained by the obtaining module, where the management authority allocation request is used to instruct the server to The second user equipment sends a management request of the M2M device, the management request is used to instruct the second user equipment to send a binding request of the M2M device to the server, and the binding request is used to indicate the The server binds the designated application identifier corresponding to the second user equipment with the identifier corresponding to the M2M device, and sends binding confirmation information to the second user equipment, where the binding confirmation information is used to indicate the the second user equipment has the second management authority of the M2M device;

Wherein, the binding request includes a designated application identifier corresponding to the second user equipment and an identifier corresponding to the M2M device.

Combined with the third aspect, in the first possible implementation,

The management authority assignment request and the management request include the specified application identifier of the second user equipment, the identifier corresponding to the M2M device, device management information and device binding credential information, and the corresponding identifier of the first user equipment. A designated application identifier, where the identifier corresponding to the M2M device includes a designated application identifier corresponding to the M2M device and/or a device identifier corresponding to the M2M device;

The binding request further includes the device binding credential information corresponding to the M2M device.

In combination with the first possible implementation manner of the third aspect, in the second possible implementation manner,

The management authority assignment request further includes authority period information corresponding to the second management authority;

The sending module is further configured to send a permission period modification request to the server, where the permission period modification request is used to instruct the server to modify the permission period information, and send a permission period modification confirmation to the second user equipment information, the authority period modification confirmation information is used to indicate that the second management authority corresponds to a new authority period;

Wherein, the permission period modification request includes the specified application identifier corresponding to the second user equipment, the identifier corresponding to the M2M device, and permission period modification information.

With reference to the third aspect or any one of the possible implementation manners of the first to the second aspect of the third aspect, in the third possible implementation manner,

The sending module is further configured to send a request for canceling the management authority to the server, where the request for canceling the management authority is used to instruct the server to cancel the specified application identification corresponding to the second user equipment and the identification corresponding to the M2M device The binding relationship between the two, and send to the second user equipment cancellation management authority confirmation information, the management authority cancellation confirmation information is used to indicate that the second user equipment does not have the second management authority of the M2M device;

The request for canceling the management authority includes the specified application identifier corresponding to the second user equipment, the identifier corresponding to the M2M device, and management authority cancellation information.

In combination with the third possible implementation manner of the third aspect, the fourth possible implementation manner further includes:

A deletion module, configured to delete the second management authority of the second user equipment to the M2M device before the sending module sends a request for canceling the management authority to the server, including any one of the following methods:

On the designated application toolbar interface corresponding to the M2M device, select a rights management interface, and delete the second management rights of the second user equipment to the M2M device on the rights management interface;

or,

In the designated application menu bar option corresponding to the M2M device, select a rights management interface, and delete the second management rights of the second user equipment to the M2M device on the rights management interface;

or,

On the designated application dialog interface corresponding to the M2M device, delete the second management authority of the M2M device by the second user equipment through a voice or text command;

or,

Click the icon corresponding to the M2M device on the designated application interface corresponding to the M2M device, select the rights management interface, and delete the second management rights of the second user equipment to the M2M device on the rights management interface ;

or,

On the designated application interface corresponding to the M2M device, long-press the icon corresponding to the M2M device, select the rights management interface, and delete the second user equipment's second request to the M2M device on the rights management interface. Administrative rights.

In combination with the fourth possible implementation manner of the third aspect, in the fifth possible implementation manner,

The obtaining module is specifically configured to obtain the designated application identifier corresponding to the second user equipment from the designated application interface corresponding to the M2M device;

or,

The obtaining module is specifically configured to obtain the designated application identifier corresponding to the second user equipment from the designated application dialog interface corresponding to the M2M device.

With reference to the fifth possible implementation manner of the third aspect, the sixth possible implementation manner further includes:

a selection module, configured to select the M2M device before the acquisition module acquires the specified application identifier corresponding to the second user equipment;

The selection module is further configured to select a user icon corresponding to the second user equipment on the management interface of the M2M device;

The selection module is further configured to select any application corresponding to the second user equipment as a designated application on the management interface of the user icon corresponding to the second user equipment.

A fourth aspect of the present invention provides a server, comprising:

a receiving module, configured to receive a management authority assignment request of an M2M device sent by a first user equipment, where the first user equipment has the first management authority of the M2M device, and the M2M device has at least one;

A sending module, configured to send a management request of the M2M device to the second user equipment according to the management authority assignment request, where the management request is used to instruct the second user equipment to send the binding of the M2M device to the server make a request;

The receiving module is further configured to receive the binding request sent by the second user equipment, where the binding request includes a designated application identifier corresponding to the second user equipment and an identifier corresponding to the M2M device, The designated application identifier corresponding to the second user equipment is the designated application identifier corresponding to the application logged in on the second user equipment;

a binding module, configured to bind the specified application identifier corresponding to the second user equipment with the identifier corresponding to the M2M device according to the binding request;

The sending module is further configured to send binding confirmation information to the second user equipment, where the binding confirmation information is used to indicate that the second user equipment has the second management authority of the M2M device.

Combined with the fourth aspect, in the first possible implementation manner,

The management authority assignment request and the management request include the specified application identifier corresponding to the second user equipment, the identifier corresponding to the M2M device, device management information and device binding credential information, and the corresponding identifier of the first user equipment. The designated application identifier, the identifier corresponding to the M2M device includes the designated application identifier corresponding to the M2M device and/or the device identifier corresponding to the M2M device;

The binding request further includes the device binding credential information corresponding to the M2M device.

With reference to the first possible implementation manner of the fourth aspect, in a second possible implementation manner, the management authority assignment request further includes authority period information corresponding to the second management authority, and the server further includes:

The receiving module is further configured to receive a permission period modification request sent by the first user equipment;

A modification module, configured to modify the permission period information according to the permission period modification request;

The sending module is further configured to send authority period modification confirmation information to the second user equipment, where the authority period modification confirmation information is used to indicate that the second management authority corresponds to a new authority period;

Wherein, the management period modification request includes the specified application identifier corresponding to the second user equipment, the identifier corresponding to the M2M device, and permission period modification information.

With reference to the fourth aspect or any one of the possible implementation manners of the first to the second aspect of the fourth aspect, in a third possible implementation manner, the server further includes:

The receiving module is further configured to receive a request for canceling the management authority sent by the first user equipment;

a releasing module, configured to release the binding relationship between the designated application identifier corresponding to the second user equipment and the identifier corresponding to the M2M device according to the request for canceling the management authority;

The sending module is further configured to send confirmation information for cancellation of management authority to the second user equipment, where the confirmation information for cancellation of management authority is used to indicate cancellation of the second management authority of the second user equipment to the M2M device;

The request for canceling the management authority includes the specified application identifier corresponding to the second user equipment, the identifier corresponding to the M2M device, and management authority cancellation information.

A fifth aspect of the present invention provides a system, characterized in that it includes:

User equipment and servers;

The user equipment is the user equipment according to the third aspect;

The server is the server described in the fourth aspect.

By applying the above technical solutions, the first user equipment obtains the specified application identifier corresponding to the second user equipment, and the first user equipment sends the management authority assignment request of the M2M device to the server according to the specified application identifier corresponding to the second user equipment, so the The management authority assignment request is used to instruct the server to send a management request of the M2M device to the second user equipment, and the management request is used to instruct the second user equipment to send the M2M device's information to the server. A binding request, where the binding request includes a designated application identifier corresponding to the second user equipment and an identifier corresponding to the M2M device, and the binding request is used to instruct the server to associate the second user equipment with The specified application identifier of the M2M device is bound with the identifier corresponding to the M2M device, and binding confirmation information is sent to the second user equipment. Since the first user equipment has the first management authority of the M2M device, different from the prior art, in the present invention, the first user equipment has the ability to send the management authority assignment request of the M2M device to the server, and then the second user equipment is sent to the server through the server. The designated application identifier corresponding to the device is bound with the identifier corresponding to the M2M device, so that the second user equipment has the second management authority of the M2M device, thereby realizing that multiple user equipments have the management authority of the M2M device and improving user experience.

Description of drawings

1 is a schematic diagram of a technical architecture of WeChat IoT in the prior art;

2a-2b are schematic diagrams of an embodiment of WeChat IoT in the prior art;

3 is a schematic diagram of an embodiment of a method for allocating M2M device management authority in an embodiment of the present invention;

4 is a schematic diagram of another embodiment of a method for allocating M2M device management authority in an embodiment of the present invention;

5 is a schematic diagram of another embodiment of a method for allocating M2M device management authority in an embodiment of the present invention;

6 is a schematic diagram of another embodiment of a method for allocating M2M device management authority in an embodiment of the present invention;

FIG. 7 is a schematic diagram of an embodiment of a specific application scenario in an embodiment of the present invention;

8 is a schematic diagram of another embodiment of a specific application scenario in an embodiment of the present invention;

FIG. 9 is a schematic diagram of another embodiment of a specific application scenario in an embodiment of the present invention;

FIG. 10 is a schematic diagram of another embodiment of a specific application scenario in an embodiment of the present invention;

11 is a schematic diagram of another embodiment of a specific application scenario in an embodiment of the present invention;

12 is a schematic diagram of another embodiment of a specific application scenario in an embodiment of the present invention;

13 is a schematic diagram of another embodiment of a specific application scenario in an embodiment of the present invention;

14 is a schematic diagram of another embodiment of a specific application scenario in an embodiment of the present invention;

15 is a schematic diagram of another embodiment of a specific application scenario in an embodiment of the present invention;

16 is a schematic diagram of another embodiment of a specific application scenario in an embodiment of the present invention;

FIG. 17 is a schematic diagram of an embodiment of a user equipment in an embodiment of the present invention;

FIG. 18 is a schematic diagram of an embodiment of a server in an embodiment of the present invention;

19 is a schematic diagram of an embodiment of a system in an embodiment of the present invention;

FIG. 20 is a schematic structural diagram of allocating M2M device management authority in an embodiment of the present invention.

Detailed ways

Embodiments of the present invention provide a method, user equipment, and system for allocating M2M device management authority, so that the user equipment has the ability to send an M2M device management authority allocation request to a server, and then allocates the M2M equipment additional management authority through the server. For other user equipments, the other user equipments also have the management authority of the M2M equipment, thereby improving the user experience.

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, but not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative efforts shall fall within the protection scope of the present invention.

The terms "first", "second", "third", "fourth", etc. (if present) in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to Describe a particular order or sequence. It is to be understood that data so used may be interchanged under appropriate circumstances so that the embodiments described herein can be practiced in sequences other than those illustrated or described herein. Furthermore, the terms "comprising" and "having" and any variations thereof, are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those expressly listed Rather, those steps or units may include other steps or units not expressly listed or inherent to these processes, methods, products or devices.

It should be noted that the terms used in the embodiments of the present invention are only for the purpose of describing specific embodiments, and are not intended to limit the present invention. As used in the embodiments of the present invention and the appended claims, the singular forms "a," "the," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise.

The technical solution of the present invention can be applied to various communication systems, such as: Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (Wideband Code) Division Multiple Access Wireless, WCDMA), General Packet Radio Service (General Packet Radio Service, GPRS), Long Term Evolution (Long Term Evolution, LTE) and the like.

User equipment (UE, User Equipment) in this embodiment of the present invention may also be referred to as a mobile terminal (Mobile Terminal), mobile user equipment, etc. The user equipment can be a mobile terminal, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal, for example, which can be portable, pocket-sized, hand-held, computer-built-in or vehicle-mounted Mobile devices that exchange language and/or data with the radio access network.

Figures 2a-2b are an example of WeChat IoT in the prior art, in which the Codoon bracelet is a product that supports WeChat IoT, and its main function is to share and rank users' exercise data using WeChat public accounts. The device pays attention to the WeChat official account of the Codoon bracelet, so as to bind the Codoon bracelet, the user device can upload the exercise data to WeChat, and rank the users corresponding to the user device and other users according to the health data, and the user can view it through the user device. Daily sports rankings. In addition, users can view the health data of the Codoon bracelet, set a personal exercise plan, set the bracelet alarm, etc. through the WeChat public account, and use the WeChat public account to bind the Codoon bracelet, so as to control and manage the Codoon bracelet. However, , when the user wants to assign the additional management authority of the Codoon bracelet to other users, in the prior art, the user equipment does not have the ability to send a request for the allocation of the management authority of the Codoon bracelet to the server, so the user's idea cannot be realized, affecting User experience, therefore expand the discussion of the present invention:

Referring to FIG. 3, an embodiment of a method for allocating M2M device management authority in an embodiment of the present invention includes:

301. The first user equipment acquires a specified application identifier corresponding to the second user equipment;

The first user equipment has the first management authority of the M2M device, and there is at least one M2M device, wherein the first user equipment can obtain the identifier corresponding to the M2M device, and then send a binding request to the server, so that the server will A designated application identifier corresponding to a user equipment is bound with an identifier corresponding to the M2M device, so as to obtain the first management authority of the M2M device, and the first management authority of the M2M device can also be obtained in other ways, which are not specifically limited here.

In this embodiment of the present invention, the identifier corresponding to the M2M device includes a designated application identifier corresponding to the M2M device and/or a device identifier corresponding to the M2M device.

The first management authority is a main authority of the M2M device, and the user equipment with the main authority can send the management authority allocation request of the M2M device to the server, so that the management authority of the M2M device is allocated to the second user equipment through the server, so that the first A user equipment and a second user equipment also have the management authority of the M2M equipment.

The designated application identifier corresponding to the second user equipment is the designated application identifier corresponding to the application logged in on the second user equipment, for example, the designated application identifier corresponding to any social application logged in on the second user equipment .

The designated application identifier is an account or name used to identify the designated application, and may also be other symbols used to identify the designated application, which is not specifically limited here. In the present invention, the specified application identifier may be a social account or a public account of the specified application, such as a WeChat public account. Wherein, any application corresponding to the second user equipment can be used as a designated application, for example, any social application, such as: QQ, WeChat, whatsapp, line, twitter, Facebook, and so on.

302. The first user equipment sends an M2M device management authority allocation request to the server according to the specified application identifier corresponding to the second user equipment;

The management authority assignment request is used to instruct the server to send a management request of the M2M device to the second user equipment, and the management request is used to instruct the second user equipment to send the M2M device to the server The binding request, wherein the binding request includes the specified application identifier corresponding to the second user equipment and the identifier corresponding to the M2M device, and the binding request is used to instruct the server to The specified application identifier corresponding to the user equipment is bound with the identifier corresponding to the M2M device, and binding confirmation information is sent to the second user equipment, where the binding confirmation information is used to indicate that the second user equipment has all the second management authority of the M2M device.

The second management authority is an additional management authority of the M2M device. Similar to the first management authority, the second user equipment can also control and manage the M2M device through the additional management authority. However, the difference is that the second user equipment The management authority is passively acquired by the second user equipment, and the first user equipment may send a request for canceling the second management authority to the server at any time, and then cancel the second management authority through the server.

It should be noted that, in the present invention, a server may be understood as a designated application server or a service server, which may be determined according to the actual application. Among them, the designated application server can be understood as the server corresponding to the designated application (such as: WeChat server, QQ server, Facebook server and other social networking site servers, etc.), and the business server can be understood as an M2M device manufacturer that provides M2M device services and management functions Servers, such as the Gudong bracelet server.

In the embodiment of the present invention, since the first user equipment has the first management authority of the M2M device, different from the prior art, the first user equipment sends a management authority allocation request of the M2M device to the server, and the management authority allocation request uses is used to instruct the server to send a management request of the M2M device to the second user equipment, the management request is used to instruct the second user equipment to send a binding request of the M2M device to the server, the The binding request includes the designated application identifier corresponding to the second user equipment and the identifier corresponding to the M2M device, and then the server binds the designated application identifier corresponding to the second user equipment and the identifier corresponding to the M2M device, so that the first The second user equipment has the second management authority of the M2M equipment, so that multiple user equipments have the management authority of the M2M equipment, and the user experience is improved.

On the basis of the embodiment shown in FIG. 3 , referring to FIG. 4 , another embodiment of the method for allocating M2M device management authority in the embodiment of the present invention includes:

401. The first user equipment pays attention to the specified application identifier corresponding to the M2M device;

In this embodiment of the present invention, the identifier corresponding to the M2M device includes a designated application identifier corresponding to the M2M device and a device identifier corresponding to the M2M device.

The first user equipment may first obtain the designated application identifier corresponding to the M2M device, search for the designated application identifier corresponding to the M2M device on the search toolbar of the designated application through the designated application identifier corresponding to the M2M device, and then pay attention to the designated application identifier corresponding to the M2M device. App ID. For the designated application identifier, reference may be made to the definition of the designated application identifier in the embodiment shown in FIG. 3 .

402. The first user equipment enables the M2M device;

After paying attention to the designated application identifier corresponding to the M2M device, the first user equipment can further enable the M2M device by scanning the device identifier corresponding to the M2M device (such as a two-dimensional code, an identification number ID), or can also enable the M2M device in other ways. There is no specific limitation.

403. The first user equipment sends a binding request of the M2M device to the server;

In this embodiment of the present invention, the server includes a designated application server and a service server.

After enabling the M2M device, the first user equipment sends a binding request of the M2M device to the service server through the designated application service corresponding to the M2M device, where the binding request includes the designated application identifier corresponding to the first user equipment and the M2M device. The corresponding device ID.

404. The server binds the specified application identifier corresponding to the first user equipment with the device identifier corresponding to the M2M device;

After receiving the M2M device binding request sent by the first user equipment, the service server binds the designated application identifier corresponding to the first user equipment and the device identifier corresponding to the M2M device.

405. The server sends the binding confirmation information of the M2M device to the first user equipment;

After the service server binds the designated application identifier corresponding to the first user equipment with the device identifier corresponding to the M2M device, the service server sends the binding confirmation information of the M2M device to the first user equipment through the designated application server.

406. The first user equipment acquires the first management authority of the M2M device;

The first user equipment receives the binding confirmation information sent by the designated application server, and thus has the first management authority of the M2M device.

407. The first user equipment acquires a specified application identifier corresponding to the second user equipment;

After the first user equipment has the first management authority of the M2M device, the first user equipment pre-allocates the management authority of the M2M device to the second user equipment, then the first user equipment first obtains the corresponding designated application identifier of the second user equipment, so the The designated application identifier corresponding to the second user equipment is the designated application identifier corresponding to the application logged in on the second user equipment.

In some optional embodiments, the first user equipment acquires the specified application identifier corresponding to the second user equipment from the specified application interface corresponding to the M2M device, for example: the first user equipment is in the corresponding M2M device. On the input toolbar of the social public account interface, select the second user equipment, and receive the designated application identifier corresponding to the second user equipment; or, the first user equipment from the designated application dialog interface corresponding to the M2M device. Acquiring the designated application identifier corresponding to the second user equipment, for example: the first user equipment selects the second user equipment in the designated application dialog box corresponding to the M2M device, and receives the designated application identifier corresponding to the second user equipment. The specific acquisition method may be determined according to the actual situation, and is not specifically limited here.

In addition, before the first user equipment acquires the designated application identifier corresponding to the second user equipment, the designated application corresponding to the second user equipment also needs to be determined, specifically: the first user equipment selects the M2M device; the first user equipment On the management interface of the M2M device, select a user icon corresponding to the second user equipment, for example, the icon indicates a user whose first user equipment has pre-assigned the management authority of the M2M device; the first user equipment is in the second user equipment Any application corresponding to the second user equipment is selected as the designated application on the management interface of the corresponding user icon.

408. The first user equipment sends a management authority assignment request of the M2M device to the server;

The first user equipment sends a management authority assignment request of the M2M device to the specified application server according to the specified application identifier of the second user equipment, where the management authority assignment request is used to instruct the specified application server to send the specified application server to the second user equipment. Management request for M2M devices.

The management authority assignment request includes a designated application identifier corresponding to the second user equipment, an identifier corresponding to the M2M device, device management information and device binding credential information, and a designated application identifier corresponding to the first user equipment.

The identifier corresponding to the M2M device includes a designated application identifier corresponding to the M2M device and a device identifier corresponding to the M2M device.

In the embodiment of the present invention, the device identification is a two-dimensional code used to identify the M2M device, the identification number, the model, the production date, the manufacturer information, the production batch, etc., which are the identification features of the M2M device. The device management information includes icon information for displaying the management interface corresponding to the M2M device and function table information corresponding to the management interface. The user equipment with management authority can control and manage the M2M equipment through the equipment management information.

The device binding credential information is the information that is verified according to the binding request before the server binds the designated application identifier corresponding to the second user device and the identifier corresponding to the M2M device. For example, the server can authorize the second user through the obtained device binding credential information. device binding request, and then bind the designated application identifier of the second user equipment with the identifier corresponding to the M2M device. Optionally, the server may verify the binding request of the second user according to the device binding credential information and the specified application identifier corresponding to the first user's device.

The server can perform verification through the device binding credential information, and only after the verification is passed can it be determined to bind the designated application identifier of the second user equipment with the device identifier corresponding to the M2M device.

409. The server sends a management request of the M2M device to the second user equipment;

The designated application server receives the management authority assignment request of the M2M device sent by the first user equipment, and further sends the management request of the M2M device to the second user equipment, where the management request includes the designated application identifier corresponding to the second user equipment. The identifier corresponding to the M2M device, device management information and device binding credential information, and the designated application identifier corresponding to the first user equipment, and the management request is used to instruct the second user equipment to send the designated application server. The binding request of the M2M device described above.

410. The second user equipment determines whether to pay attention to the designated application identifier corresponding to the M2M device, if yes, execute step 411, if not, execute step 412;

The second user equipment receives the management request of the M2M device sent by the designated application server, and further determines whether it has paid attention to the designated application identifier corresponding to the M2M device.

411. The second user equipment sends indication information on a designated application interface corresponding to M2M;

If the second user equipment has paid attention to the designated application identifier corresponding to the M2M device, the second user equipment sends indication information on the designated application interface corresponding to the M2M device, where the indication information is used to instruct the second user equipment to accept the management request .

412. The second user equipment sends indication information on the system display interface;

If the second user equipment does not pay attention to the designated application identifier corresponding to the M2M device, the second user equipment sends indication information on the system display interface. The system is a system corresponding to the second user equipment, for example, the second user equipment is an Android (Android) system. It should be noted that, if the second user equipment does not pay attention to the designated application identifier corresponding to the M2M device, the indication information sent by the second user equipment on the system display interface further includes instructing the second user equipment to accept the designated application identifier corresponding to the M2M device. request for attention.

413. The second user equipment sends a binding request of the M2M device to the server;

After the second user equipment accepts the management request through the indication information, the second user equipment sends an M2M device binding request to the service server through the designated application server, where the binding request is used to instruct the service server to bind the second user equipment to the service server. The corresponding designated application identifier is bound with the device identifier corresponding to the M2M device, and binding confirmation information is sent to the second user equipment, where the binding confirmation information is used to indicate that the second user equipment has the The second management authority of the M2M device.

The binding request includes a specified application identifier corresponding to the second user equipment, a device identifier corresponding to the M2M device, and device binding credential information.

It can be understood that, when the second user equipment sends a binding request of the M2M device to the service server through the designated application server corresponding to the M2M device, the service server binds the designated application identifier corresponding to the second user equipment and the device identifier corresponding to the M2M device. Certainly.

414. The server binds the specified application identifier corresponding to the second user equipment with the device identifier corresponding to the M2M device;

The service server receives the binding request of the M2M device, and can verify through the device binding credential information in the binding request, and further binds the designated application identifier corresponding to the second user equipment with the device identifier corresponding to the M2M device after the verification is passed.

415. The server sends the binding confirmation information of the M2M device to the second user equipment;

After binding the designated application identifier corresponding to the second user equipment with the device identifier corresponding to the M2M device, the service server further sends the binding confirmation information of the M2M device to the second user equipment through the designated application server.

416. The second user equipment acquires the second management authority of the M2M device, and displays binding confirmation information on the corresponding designated application interface.

The second user equipment receives the binding confirmation information of the M2M device, so as to have the second management authority of the M2M device, and the second user equipment generates a designated application interface corresponding to the M2M device according to the binding confirmation information, and generates the specified application interface corresponding to the M2M device in the The binding confirmation information is displayed on the designated application interface corresponding to the M2M device.

In some optional embodiments, the management authority assignment request further includes authority period information corresponding to the second management authority. For example, the permission period is half a year, one month, etc. The permission period may be set by the user through the first user equipment, or may be set by default on the first user equipment, which is not specifically limited here.

In some optional embodiments, the first user equipment sends a permission period modification request to the service server through a designated application server, where the permission period modification request is used to instruct the service server to modify the permission period information, and send the permission period modification request to the service server through the specified application server. The designated application server sends permission period modification confirmation information to the second user equipment, where the authority period modification confirmation information is used to indicate that the second management authority corresponds to a new authority period;

Wherein, the permission period modification request includes the specified application identifier corresponding to the second user equipment, the device identifier corresponding to the M2M device, and permission period modification information.

In some optional embodiments, the first user equipment sends a management authority cancellation request to the service server through a designated application server, where the management authority cancellation request is used to instruct the service server to cancel the second user equipment The binding relationship between the corresponding designated application identifier and the device identifier corresponding to the M2M device, and sending confirmation information for canceling the management authority to the second user equipment through the designated application server, where the confirmation information for canceling the management authority is used to indicate The second user equipment does not have the second management authority of the M2M device;

The request for canceling the management authority includes the specified application identifier corresponding to the second user equipment, the device identifier corresponding to the M2M device, and management authority cancellation information.

In addition, before the first user equipment sends a request for canceling the management authority to the designated application server, the first user equipment deletes the second management authority of the second user equipment to the M2M device, including any one of the following methods:

The first user equipment selects a rights management interface on the designated application toolbar interface corresponding to the M2M device, and deletes the second management rights of the second user equipment to the M2M device on the rights management interface Or, the first user equipment selects a rights management interface in the designated application menu bar option corresponding to the M2M device, and deletes the first user equipment's first access to the M2M device on the rights management interface. 2. Management authority; or, the first user equipment deletes the second management authority of the M2M device by the second user equipment through a voice or text command on the designated application dialog interface corresponding to the M2M device; or , the first user equipment clicks the icon corresponding to the M2M device on the designated application interface corresponding to the M2M device, selects a rights management interface, and deletes the second user equipment on the rights management interface. The second management authority of the M2M device; or, the first user equipment selects the authority management interface by long-pressing the icon corresponding to the M2M device on the designated application interface corresponding to the M2M device, and selects the authority management interface on the authority management interface. above, delete the second management authority of the second user equipment to the M2M device. There are many ways for the first user equipment to delete the second management authority of the second user equipment to the M2M device, which is not specifically limited here.

In some optional embodiments, the service server sends information that the permission period expires to the second user equipment through the designated application server, prompting the second user equipment that the second user equipment no longer has the second management permission.

It should be noted that, in this embodiment of the present invention, there may be one or more second user equipments, and one or more M2M devices. When there are multiple M2M devices, a list corresponding to the M2M devices is formed, and the specific allocation The method for managing authority of the M2M device is the same as the steps in the embodiment of the present invention, and details are not repeated here.

In the embodiment of the present invention, the first user equipment has the first management authority of the M2M device. Different from the prior art, in the present invention, the first user equipment can send the management authority assignment of the M2M device to the service server by specifying the application server. request, the management authority assignment request is used to instruct the server to send a management request of the M2M device to the second user equipment, and the management request is used to instruct the second user equipment to send the server to the server The binding request of the M2M device, the binding request includes the designated application identifier corresponding to the second user equipment and the device identifier corresponding to the M2M device, and then the service server associates the designated application identifier corresponding to the second user equipment with the M2M device. The device identifiers corresponding to the devices are bound, so that the second user equipment has the second management authority of the M2M device, so that multiple user equipments have the management authority of the M2M device, and the user experience is improved. In addition, in the present invention, the first user equipment can send a request for modifying the authority period or canceling the management authority request to the service server through the designated application server, and then the service server modifies the authority period information, or the service server modifies the authority period information, In this way, the modification of the permission period and the cancellation of the management permission are realized, and the user experience is effectively improved.

In the embodiment shown in FIG. 4 , referring to FIG. 5 , another embodiment of the method for allocating M2M device management authority in the embodiment of the present invention includes:

501. The first user equipment adds an M2M device;

The first user equipment can select to add an M2M device on the specified application interface, and there are many specific adding methods, which are not specifically limited here.

502. The first user equipment enables the M2M device;

The first user equipment can enable the M2M device by scanning the QR code corresponding to the M2M device, wherein enabling the M2M device can be understood as opening the binding request interface of the M2M device, and there are many specific enabling methods, which are not specifically limited here.

503. The first user equipment sends a binding request of the M2M device to the server;

In this embodiment of the present invention, the server may be understood as a designated application server. In this embodiment of the present invention, different servers may be selected according to different types of specific designated applications. For example, the designated applications in the embodiments shown in FIG. 4 and FIG. 5 may be two different types of designated applications.

504. The server sends M2M device binding confirmation information to the first user equipment;

The designated application server receives the binding request sent by the first user equipment, binds the designated application identifier corresponding to the first user equipment and the designated application identifier corresponding to the M2M device, and then sends M2M device binding confirmation information to the first user equipment.

505. The first user equipment acquires the first management authority of the M2M device;

The first user equipment has the first management authority of the M2M device by receiving the binding confirmation information sent by the designated application server, where the first management authority is the main authority of the M2M device.

506. The first user equipment starts a designated application dialog with the M2M device;

507. The first user equipment selects a specified application corresponding to the second user equipment in the specified application dialog interface;

508. The first user equipment acquires the specified application identifier of the second user equipment;

The first user equipment pre-allocates the management authority of the M2M device to the second user equipment, then the first user equipment acquires the specified application identifier of the second user equipment according to the specified application corresponding to the second user equipment, and the second user equipment corresponds to the specified application identifier. The designated application identifier is a designated application identifier corresponding to an application logged in on the second user equipment.

In some optional embodiments, the first user equipment acquires the specified application identifier of the second user equipment from the specified application dialog interface corresponding to the M2M device, for example: the first user equipment is corresponding to the M2M device Select the second user equipment in the specified application dialog box, and receive the specified application identifier of the second user equipment. The specific acquisition method may be determined according to the actual situation, and is not specifically limited here.

509. The first user equipment sends a management authority assignment request of the M2M device to the server;

In this embodiment of the present invention, the management authority assignment request includes a designated application identifier corresponding to the second user equipment, a designated application identifier corresponding to the M2M device, device management information and device binding credential information, and the first user equipment. A designated application identifier corresponding to a user equipment.

In some optional embodiments, the management authority assignment request further includes a device identifier corresponding to the M2M device, which is not specifically limited here.

510. The server sends a management request of the M2M device to the second user equipment;

The designated application server receives the M2M device management authority assignment request sent by the first user equipment, and further sends the M2M device management request to the second user equipment.

511. The second user equipment receives the management request of the M2M device, and sends indication information on the designated application interface corresponding to the M2M.

In some optional embodiments, the second user equipment prompts and displays the specified application identifier and management request information corresponding to the M2M device in a communication dialog with the first user equipment, or displays the corresponding M2M device in the application for a new friend The specified application identifier and management request information are confirmed, and the process proceeds to step 512 .

512. The second user equipment sends a binding request of the M2M device to the server;

After the second user equipment accepts the management request through the indication information, the second user equipment sends a binding request of the M2M device to the designated application server.

The binding request includes a designated application identifier corresponding to the second user equipment and an identifier corresponding to the M2M device.

In this embodiment of the present invention, the identifier corresponding to the M2M device includes a designated application identifier corresponding to the M2M device, or includes a designated application identifier corresponding to the M2M device and a device identifier corresponding to the M2M device.

513. The server binds the designated application identifier corresponding to the second user equipment with the designated application identifier corresponding to the M2M device;

After the designated application server receives the management authority assignment request from the M2M device, the designated application server binds the designated application identifier corresponding to the second user equipment with the designated application identifier corresponding to the M2M device.

514. The server sends binding confirmation information to the second user equipment;

After binding the designated application identifier corresponding to the second user equipment with the designated application identifier corresponding to the M2M device, the designated application server further sends the binding confirmation information of the M2M device to the second user equipment.

515. The second user equipment acquires the second management authority of the M2M device.

The second user equipment receives the binding confirmation information of the M2M device sent by the designated application server, and thus has the second management authority of the M2M device.

Further, after acquiring the second management authority of the M2M device, the second user equipment displays the binding confirmation information in a designated application dialog with the first user equipment.

In some optional embodiments, the first user equipment sends a permission period modification request to the specified application server, where the permission period modification request is used to instruct the specified application server to modify the permission period information, and send the permission period modification request to the designated application server. sending, by the second user equipment, authority period modification confirmation information, where the authority period modification confirmation information is used to indicate that the second management authority corresponds to a new authority period;

Wherein, the permission period modification request includes the specified application identifier corresponding to the second user equipment, the specified application identifier corresponding to the M2M device, and permission period modification information.

In some optional embodiments, the first user equipment sends a request for canceling management rights to the designated application server, where the request for canceling management rights is used to instruct the designated application server to cancel the management rights corresponding to the second user equipment. Specify the binding relationship between the application identifier and the designated application identifier corresponding to the M2M device, and send confirmation information for canceling the management authority to the second user equipment, where the confirmation information for canceling the management authority is used to instruct the second user The device does not have the second management authority of the M2M device;

The request for canceling the management authority includes a designated application identifier corresponding to the second user equipment, a designated application identifier corresponding to the M2M device, and management authority cancellation information.

In addition, before the first user equipment sends a request for canceling the management authority to the designated application server, the first user equipment deletes the second management authority of the second user equipment to the M2M device, and the specific deletion method can refer to the diagram of the present invention The relevant content in the embodiment shown in 4 will not be repeated here.

In some optional embodiments, the designated application server sends information that the permission period expires to the second user equipment, indicating that the second user equipment no longer has the second management permission.

It should be noted that, in this embodiment of the present invention, there may be one or more second user equipments, and one or more M2M devices. When there are multiple M2M devices, a list corresponding to the M2M devices is formed, and the specific allocation The method for managing authority of the M2M device is the same as the steps in the embodiment of the present invention, and details are not repeated here.

In the embodiment of the present invention, the first user equipment has the first management authority of the M2M device. Different from the prior art, in the present invention, the first user equipment has the ability to send a management authority assignment request of the M2M device to the designated application server , the management authority assignment request is used to instruct the server to send the management request of the M2M device to the second user equipment, and the management request is used to instruct the second user equipment to send the M2M device to the server The binding request of the device, the binding request includes the designated application identifier corresponding to the second user equipment and the designated application identifier corresponding to the M2M device, and then the designated application server associates the designated application identifier corresponding to the second user equipment with the designated application identifier. The designated application identifier corresponding to the M2M device is bound, so that the second user equipment has the second management authority of the M2M device, so that multiple user equipments have the management authority of the M2M device, and the user experience is improved. In addition, in the present invention, the first user equipment can send a permission period modification request or a management permission cancellation request to the specified application server, and then the specified application server can modify the permission period information, or the specified application server can modify the permission period information, thereby Realize the modification of the permission period and the cancellation of the management permission, effectively improving the user experience.

On the basis of the foregoing embodiment, referring to FIG. 6 , another embodiment of the method for allocating M2M device management authority in the embodiment of the present invention includes:

601. The server receives an M2M device management authority allocation request sent by a first user equipment;

In this embodiment of the present invention, the server includes a designated application server or a service server. For details, refer to the server in the embodiment shown in FIG. 4 or FIG. 5 .

The first user equipment has the first management authority of the M2M device, and the M2M device has at least one.

602. The server sends a management request of the M2M device to the second user equipment according to the management authority allocation request;

The management request is used to instruct the second user equipment to send a binding request of the M2M device to the server.

603. The server receives the binding request sent by the second user equipment;

The binding request includes a designated application identifier corresponding to the second user equipment and an identifier corresponding to the M2M device, and the identifier corresponding to the M2M device includes a designated application identifier corresponding to the M2M device and a device corresponding to the M2M device. logo.

604. The server binds the specified application identifier corresponding to the second user equipment with the identifier corresponding to the M2M device according to the binding request;

The designated application identifier corresponding to the second user equipment is the designated application identifier corresponding to the application logged in on the second user equipment.

605. The server sends the binding confirmation information to the second user equipment, where the binding confirmation information is used to indicate that the second user equipment has the second management authority of the M2M device.

In some optional embodiments, both the management authority assignment request and the management request include a specified application identifier corresponding to the second user equipment, an identifier corresponding to the M2M device, device management information, and device binding Credential information and a designated application identifier corresponding to the first user equipment;

The binding request further includes the device binding credential information corresponding to the M2M device.

In some optional embodiments, the management authority assignment request further includes authority period information corresponding to the second management authority;

receiving, by the server, a request for modifying the permission period sent by the first user equipment;

The server modifies the permission term information according to the permission term modification request;

sending, by the server, authority period modification confirmation information to the second user equipment, where the authority period modification confirmation information is used to indicate that the second management authority corresponds to a new authority period;

Wherein, the management period modification request includes the specified application identifier corresponding to the second user equipment, the identifier corresponding to the M2M device, and permission period modification information.

In some optional embodiments, the server receives a request for canceling the management authority sent by the first user equipment;

The server modifies the permission period information according to the request for canceling the management permission;

sending, by the server, confirmation information for canceling management authority to the second user equipment, where the confirmation information for canceling management authority is used to instruct to cancel the second management authority of the second user equipment for the M2M device;

The request for canceling the management authority includes the specified application identifier corresponding to the second user equipment, the identifier corresponding to the M2M device, and management authority cancellation information.

It should be noted that, in this embodiment of the present invention, there may be one or more second user equipments, and one or more M2M devices. When there are multiple M2M devices, a list corresponding to the M2M devices is formed, and the specific allocation The method for managing authority of the M2M device is the same as the steps in the embodiment of the present invention, and details are not repeated here.

In the embodiment of the present invention, the server receives the management authority assignment request of the M2M device sent by the first user equipment, and the server sends the M2M equipment management request to the second user equipment according to the management authority assignment request; the management request is used to indicate the first user equipment. The second user equipment sends a binding request of the M2M device to the server, where the binding request includes a specified application identifier corresponding to the second user equipment and an identifier corresponding to the M2M device. Then the server binds the designated application identifier corresponding to the second user equipment with the identifier corresponding to the M2M device, so that the second user equipment has the second management authority of the M2M device, thereby realizing that multiple user equipments have the management of the M2M device. Permissions to improve user experience.

In combination with the above embodiments, the following describes specific application scenarios of the method for allocating M2M device management authority:

As shown in Figure 7, Xiao Ming wants to assign the management authority of the M2M device at home (such as a smart hardware device TV) to his father. The specific process is: Xiao Ming opens the TV's public account (such as WeChat public account), selects "Contact Permissions" in the input toolbar in the public account interface, and selects the user you want to authorize from "Select Contact" (such as Xiao Ming's father), further, if Xiao Ming's father does not follow the public account, he will receive the confirmation prompt message of following the public account and receiving the management authority in the system interface with Xiao Ming, and Xiao Ming's father will automatically follow the corresponding public account after confirming, And get the management authority to the TV, if Xiao Ming's father has followed the public account, he will receive the management authority reception confirmation prompt message in the communication dialog with Xiao Ming, and Xiao Ming's father will get the TV management authority after confirmation.

As shown in Figure 8, Xiao Ming wants to assign the management authority of the M2M device (such as a computer) at home to his father. The specific process is: Xiao Ming finds his father on the social application (such as: QQ) interface, further opens the QQ interface and selects "Contact Permissions", and selects the computer to be added from "My Devices". Xiao Ming's father received the confirmation message sent by Xiao Ming to receive the management permission. After Xiao Ming's father confirmed it, he immediately obtained the management permission of the home computer.

As shown in Figure 9, Xiao Ming wants to assign the management authority of the M2M device (such as a computer) at home to his father. The specific process is as follows: Xiaoming finds the computer in the "My Interface" of the social application client (such as: QQ), opens the dialog box and selects "Add Contact Permission", and selects his father from "My Contacts". After the computer receives the social application account used by Xiao Ming's father sent by Xiao Ming, it automatically sends a friend addition request to the social application account used by Xiao Ming's father.

As shown in Figure 10, Xiaoming rented a spare room in his home to Xiaoyu, and assigned the management authority of the air conditioner in the room to Xiaoyu through authorization. After a few months, Xiaoyu would move to another place. Xiaoming Take back Xiaoyu's management authority over the air conditioner in the room through the following methods.

The specific process is as follows: Xiaoming, in the options under the public account dialog box of the M2M device (for example: M2M terminal), long press "Contact Permissions" to trigger access to the "Permission Management" interface, and set the user (Xiaoyu) in the permission management column. )delete;

Or in the menu options of the public account, select "Permission Management", trigger to enter the "Permission Management" interface, and delete the user (Xiaoyu) in the permission management column.

Or in the public account, click the voice button and say "WeChat delete Xiaoyu's permissions", or use the text command "Delete Xiaoyu's permissions" to delete the user (Xiaoyu).

As shown in Figure 11, Xiaoming can also take back Xiaoyu's management rights to the air conditioner in the room in other ways:

Select the icon of the M2M device (air conditioner), select the "Permission Management" column, and delete the user (Xiaoyu) in the permission management column;

Or long press the icon of the M2M device (air conditioner) to trigger access to the "Permission Management" interface, and delete the user (Xiaoyu) in the permission management column.

Further, as shown in Figure 12, Xiaoming's friend Xiaoyu came to Xiaoming's house for two days on weekends. Xiaoming assigned the management authority of the M2M devices (such as: smart hardware device TV) to Xiaoyu and stipulated that the effective time was 2 days. .

The specific process is: Xiao Ming opens the TV's public account (such as WeChat public account), selects "Contact Permissions" in the input toolbar in the public account interface, and selects the user you want to authorize from "Select Contact" (such as Xiaoyu), and set the granted management period information. Xiaoyu clicks to receive the management permission information, and sees on the dialog interface with the M2M device that the management period granted by Xiaoming is 2 days.

Further, when Xiao Ming wants to modify Xiaoyu's management period information for the air conditioner, the specific process is shown in Figure 13:

Select the icon of the M2M device (air conditioner), select the "authority management" column, and modify the management period information in the authority management column;

Or long press the icon of the M2M device (air conditioner) to trigger access to the "authority management" interface, and modify the management period information in the authority management column.

In addition, the management period information can also be modified in other ways. The specific process is shown in Figure 14:

In the options below the M2M device public account dialog box, press and hold "Contact Permission" to trigger access to the "Permission Management" interface, and modify the management period information in the permission management column;

Or in the menu options of the public account, select "Permission Management", trigger to enter the "Permission Management" interface, and modify the management period information in the permission management column;

Or in the public account, click the voice button and say "WeChat to change the permission duration of XX to N days", N represents the number of days, XX represents Xiaoyu, or the text command "Change the permission duration of XX to N days" to modify the management Deadline information.

Further, as shown in Figure 15, Xiao Ming wants to assign the management rights of the home computer, air conditioner, TV, etc. to his father. The specific process is as follows: Find your father on the social application interface, open the interface and long press the "Add Contact Permission" option to trigger the selection of multiple M2M devices to be added from the public accounts related to the connected device. Xiao Ming's father received the management authority information sent by Xiao Ming and clicked the management authority information corresponding to each M2M device or accepted the management authority information corresponding to all M2M devices in batches, and immediately obtained the management authority of multiple devices in the home.

Further, as shown in Figure 16, Xiao Ming wants to assign the management rights of the home computer, air conditioner, TV, etc. to his father. The specific process is: find your father on the social application interface, open the interface, and trigger the selection of multiple M2M devices to be added from "My Devices" by long-pressing the "Contact Permissions" option. The father received the management authority information sent by Xiao Ming and clicked on the management authority information corresponding to each M2M device or accepted the management authority information corresponding to all M2M devices in batches, and immediately obtained the management authority for multiple devices at home.

In the embodiments of the above specific application scenarios, the allocation of management authority to M2M devices, the modification of authority period and the cancellation of management authority, and the allocation of management authority of multiple M2M devices are realized, which effectively improves user experience.

In order to facilitate better implementation of the above-mentioned related methods in the embodiments of the present invention, a related apparatus for cooperating with the above-mentioned methods is also provided below.

Referring to FIG. 17 , an embodiment of the user equipment 1700 in the embodiment of the present invention includes: an obtaining module 1701 and a sending module 1702 .

The obtaining module 1701 is configured to obtain a designated application identifier corresponding to a second user equipment, where the designated application identifier corresponding to the second user equipment is a designated application identifier corresponding to an application logged in on the second user equipment, and the first A user equipment has the first management authority of the M2M device, and the M2M device has at least one;

A sending module 1702, configured to send a management authority assignment request of the M2M device to a server according to the specified application identifier corresponding to the second user equipment obtained by the obtaining module 1701, where the management authority assignment request is used to instruct the server Sending a management request of the M2M device to the second user equipment, where the management request is used to instruct the second user equipment to send a binding request of the M2M device to the server, where the binding request is used for Instructing the server to bind the specified application identifier corresponding to the second user equipment with the identifier corresponding to the M2M device, and sending binding confirmation information to the second user equipment, where the binding confirmation information is used for Indicate that the second user equipment has the second management authority of the M2M device, wherein the binding request includes a specified application identifier corresponding to the second user equipment and an identifier corresponding to the M2M device.

In this embodiment of the present invention, the sending module sends an M2M device management authority assignment request to the server, where the management authority assignment request is used to instruct the server to send the M2M device management request to the second user equipment, the The management request is used to instruct the second user equipment to send a binding request of the M2M device to the server, where the binding request includes the specified application identifier corresponding to the second user equipment and the corresponding M2M device. identification, and then bind the designated application identification corresponding to the second user equipment with the identification corresponding to the M2M device through the server, so that the second user equipment has the second management authority of the M2M device, thereby realizing that multiple user equipment has the M2M device. Device management rights to improve user experience.

On the basis of the embodiment shown in FIG. 17 , please continue to refer to FIG. 17 , another embodiment of the user equipment in the embodiment of the present invention includes: an obtaining module and a sending module.

For the acquisition module and the transmission module, reference may be made to the acquisition module and the transmission module in the embodiment of FIG. 17 .

Further, both the management authority assignment request and the management request include the specified application identifier of the second user equipment, the identifier corresponding to the M2M device, device management information and device binding credential information, and the first user The designated application ID corresponding to the device;

The binding request further includes binding credential information corresponding to the M2M device to the device.

The management authority assignment request further includes authority period information corresponding to the second management authority;

The sending module is further configured to send a permission period modification request to the server, where the permission period modification request is used to instruct the server to modify the permission period information, and send a permission period modification confirmation to the second user equipment information, the authority period modification confirmation information is used to indicate that the second management authority corresponds to a new authority period;

Wherein, the permission period modification request includes the specified application identifier corresponding to the second user equipment, the identifier corresponding to the M2M device, and permission period modification information.

In some optional embodiments, the sending module is further configured to send a management permission cancellation request to the server, where the management permission cancellation request is used to instruct the server to cancel the specified application corresponding to the second user equipment The binding relationship between the identifier and the identifier corresponding to the M2M device, and sending confirmation information for canceling the management authority to the second user equipment, where the confirmation information for canceling the management authority is used to indicate that the second user equipment does not have all the the second management authority of the M2M device;

The request for canceling the management authority includes the specified application identifier corresponding to the second user equipment, the identifier corresponding to the M2M device, and management authority cancellation information.

In some optional embodiments, the deletion module is configured to delete the second management authority of the second user equipment to the M2M device before the sending module sends the request for canceling the management authority to the server, including any of the following a method:

On the designated application toolbar interface corresponding to the M2M device, select a rights management interface, and delete the second management rights of the second user equipment to the M2M device on the rights management interface;

or,

In the designated application menu bar option corresponding to the M2M device, select a rights management interface, and delete the second management rights of the second user equipment to the M2M device on the rights management interface;

or,

On the designated application dialog interface corresponding to the M2M device, delete the second management authority of the M2M device by the second user equipment through a voice or text command;

or,

Click the icon corresponding to the M2M device on the designated application interface corresponding to the M2M device, select the rights management interface, and delete the second management rights of the second user equipment to the M2M device on the rights management interface ;

or,

On the designated application interface corresponding to the M2M device, long-press the icon corresponding to the M2M device, select the rights management interface, and delete the second user equipment's second request to the M2M device on the rights management interface. Administrative rights.

In some optional embodiments, the obtaining module is specifically configured to obtain the specified application identifier corresponding to the second user equipment from the specified application interface corresponding to the M2M device;

or,

The obtaining module is specifically configured to obtain the designated application identifier corresponding to the second user equipment from the designated application dialog interface corresponding to the M2M device;

In some optional embodiments, the user equipment further includes: a selection module, configured to select the M2M device before the acquisition module acquires the specified application identifier corresponding to the second user equipment;

The selection module is further configured to select a user icon corresponding to the second user equipment on the management interface of the M2M device;

The selection module is further configured to select any application corresponding to the second user equipment as a designated application on the management interface of the user icon corresponding to the second user equipment.

In this embodiment of the present invention, the sending module sends an M2M device management authority assignment request to the server, where the management authority assignment request is used to instruct the server to send the M2M device management request to the second user equipment, the The management request is used to instruct the second user equipment to send a binding request of the M2M device to the server, where the binding request includes the specified application identifier corresponding to the second user equipment and the corresponding M2M device. identification, and then the server binds the designated application identification corresponding to the second user equipment with the identification corresponding to the M2M device, so that the second user equipment has the second management authority of the M2M device, so that multiple user equipments are equipped with the M2M device. management rights to improve user experience. In addition, in the present invention, the sending module sends a request to modify the authority period or cancel the management authority request to the server, and then the server modifies the authority period information, or the server modifies the authority period information, so as to realize the modification of the authority period and the management authority The cancellation can effectively improve the user experience.

On the basis of the embodiment shown in FIG. 17, referring to FIG. 18, an embodiment of the server 1800 in the embodiment of the present invention includes: a receiving module 1801, a sending module 1802, and a binding module 1803.

A receiving module 1801, configured to receive a management authority assignment request of an M2M device sent by a first user equipment, where the first user equipment has the first management authority of the M2M device, and the M2M device has at least one;

Sending module 1802, configured to send a management request of the M2M device to a second user equipment according to the management authority assignment request, where the management request is used to instruct the second user equipment to send the information of the M2M device to the server. bind request;

The receiving module 1801 is further configured to receive the binding request sent by the second user equipment, where the binding request includes a specified application identifier corresponding to the second user equipment and an identifier corresponding to the M2M device , the designated application identifier corresponding to the second user equipment is the designated application identifier corresponding to the application logged in on the second user equipment;

A binding module 1803, configured to bind the specified application identifier corresponding to the second user equipment with the identifier corresponding to the M2M device according to the binding request;

The sending module 1802 is further configured to send binding confirmation information to the second user equipment, where the binding confirmation information is used to indicate that the second user equipment has the second management authority of the M2M device.

In the embodiment of the present invention, the receiving module sends the management authority assignment request of the M2M device sent by the first user equipment, and the sending module sends the management authority request of the M2M device to the second user equipment according to the management authority assignment request, and the management request uses instructing the second user equipment to send a binding request of the M2M device to the server, where the binding request includes a designated application identifier corresponding to the second user equipment and an identifier corresponding to the M2M device, and then The binding module binds the designated application identifier corresponding to the second user equipment with the identifier corresponding to the M2M device, so that the second user equipment has the second management authority of the M2M device, so that multiple user equipments have the M2M device's second management authority. Manage permissions and improve user experience.

On the basis of the embodiment shown in FIG. 18 , with reference to FIG. 18 , another embodiment of the server in the embodiment of the present invention includes: a receiving module, a sending module, and a binding module.

For the receiving module, the sending module and the binding module, reference may be made to the receiving module, the sending module and the binding module in the embodiment shown in FIG. 18 .

Both the management authority assignment request and the management request include the specified application identifier corresponding to the second user equipment, the identifier corresponding to the M2M device, device management information and device binding credential information, and the first user equipment. The corresponding designated application identifier; the binding request also includes the device binding credential information corresponding to the M2M device.

The management authority assignment request further includes authority period information corresponding to the second management authority, and the server further includes:

The receiving module is further configured to receive a permission period modification request sent by the first user equipment;

A modification module, configured to modify the permission period information according to the permission period modification request;

The sending module is further configured to send authority period modification confirmation information to the second user equipment, where the authority period modification confirmation information is used to indicate that the second management authority corresponds to a new authority period;

Wherein, the management period modification request includes the specified application identifier corresponding to the second user equipment, the identifier corresponding to the M2M device, and permission period modification information.

In some optional embodiments, the receiving module is further configured to receive a request for canceling the management authority sent by the first user equipment;

a releasing module, configured to release the binding relationship between the designated application identifier corresponding to the second user equipment and the identifier corresponding to the M2M device according to the request for canceling the management authority;

The sending module is further configured to send confirmation information for cancellation of management authority to the second user equipment, where the confirmation information for cancellation of management authority is used to indicate cancellation of the second management authority of the second user equipment to the M2M device;

The request for canceling the management authority includes the specified application identifier corresponding to the second user equipment, the identifier corresponding to the M2M device, and management authority cancellation information.

In the embodiment of the present invention, the receiving module receives the management authority assignment request of the M2M device sent by the first application device, and the sending module sends the management authority request of the M2M device to the second user equipment according to the management authority assignment request, and the management request is used to instruct the second user equipment to send a binding request of the M2M device to the server, where the binding request includes a specified application identifier corresponding to the second user equipment and an identifier corresponding to the M2M device, Further, the binding module binds the designated application identifier corresponding to the second user equipment with the identifier corresponding to the M2M device, so that the second user equipment has the second management authority of the M2M device, thereby realizing that multiple user equipments have the M2M device. management rights to improve user experience. In addition, the modification module modifies the authority period information, or modifies the authority period information, so as to realize the modification of the authority period and the cancellation of the management authority, and effectively improve the user experience.

Further, please refer to FIG. 19 , which is a schematic diagram of an embodiment of a system 1900 in an embodiment of the present invention, including:

User equipment 1901 and server 1902;

The user equipment 1901 is the user equipment described in the embodiment of FIG. 17 ;

The server 1902 is the server in the embodiment shown in FIG. 18 .

The embodiments shown in FIGS. 17 to 18 describe the specific structures of the user equipment and the server from the perspective of functional modules. The following describes the specific structures of the user equipment and the server from the hardware perspective in conjunction with the embodiment of FIG. 20 :

The user equipment and the server involved in the embodiments of the present invention may combine two or more components, or may have different component configurations or settings, and each component may be implemented in an integrated circuit including one or more signal processing and/or application-specific integrated circuits. Hardware, software or a combination of hardware and software implementations.

Please refer to FIG. 20. FIG. 20 is a schematic structural diagram of assigning M2M management authority according to an embodiment of the present invention, including a transceiver 2001, a memory 2002, a processor 2003, and a bus 2004. The transceiver 2001, the memory 2002, and the processor 2003 are connected to all The bus 2004 is connected, where:

The transceiver 2001 is used to receive or transmit data;

The memory 2002 is used to store programs;

The processor 2003 is configured to call the program to perform the following operations:

Acquire a designated application identifier corresponding to the second user equipment, where the designated application identifier corresponding to the second user equipment is a designated application identifier corresponding to an application logged in on the second user equipment.

Further, the transceiver 2001 is configured to perform the following operations:

Send a management authority assignment request of the M2M device to the server according to the specified application identifier corresponding to the second user equipment;

Receive a management authority assignment request from an M2M device;

Send the management request of the M2M device to the second user equipment according to the management authority assignment request;

The binding request sent by the second user equipment is received.

The processor 2003 is further configured to perform the following operations:

The specified application identifier corresponding to the second user equipment and the identifier corresponding to the M2M device are bound according to the binding request.

The transceiver 2001 is further configured to perform the following operations:

Sending binding confirmation information to the second user equipment, where the binding confirmation information is used to indicate that the second user equipment has the second management authority of the M2M device.

It should be noted that, in the foregoing embodiments, the description of each embodiment has its own emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to the relevant descriptions of other embodiments. For example, for parts that are not described in detail in the embodiment shown in FIG. 20 , reference may be made to the relevant descriptions of the embodiments shown in FIGS. 3 to 6 or FIGS. 17 to 18 above.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the system, device and unit described above may refer to the corresponding process in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of units is only a logical function division. In actual implementation, there may be other division methods, for example, multiple units or components may be combined or integrated. to another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

Units described as separate components may or may not be physically separated, and components shown as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.

The integrated unit, if implemented as a software functional unit and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods of the various embodiments of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, Read-Only Memory (ROM, Read-Only Memory), Random Access Memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program codes .

Claims (23)

1. A method for assigning M2M device management rights, comprising:

a first user device acquires a designated application identifier corresponding to a second user device, wherein the first user device has a first management authority of M2M equipment, and the designated application identifier corresponding to the second user device is a designated application identifier corresponding to an application logged on the second user device;

the first user equipment sends a management authority allocation request of the M2M device to a server according to a specified application identifier corresponding to the second user equipment, the management authority allocation request is used for indicating the server to send a management request of the M2M device to the second user equipment, the management request is used for indicating the second user equipment to send a binding request of the M2M device to the server, the binding request is used for indicating the server to bind the specified application identifier corresponding to the second user equipment and the identifier corresponding to the M2M device, and binding confirmation information is sent to the second user equipment, and the binding confirmation information is used for indicating that the second user equipment has a second management authority of the M2M device;

wherein, the binding request includes a specific application identifier corresponding to the second user equipment and an identifier corresponding to the M2M device.

2. The method of claim 1,

the management authority allocation request and the management request comprise a specified application identifier corresponding to the second user equipment, an identifier corresponding to the M2M equipment, equipment management information, equipment binding credential information and a specified application identifier corresponding to the first user equipment;

the binding request further includes the device binding credential information corresponding to the M2M device.

3. The method according to claim 2, wherein the management right allocation request further includes right deadline information corresponding to the second management right, and the method further comprises:

the first user equipment sends an authority limit modification request to the server, wherein the authority limit modification request is used for indicating the server to modify the authority limit information, and sends authority limit modification confirmation information to the second user equipment, and the authority limit modification confirmation information is used for indicating that the second management authority corresponds to a new authority limit;

wherein, the permission term modification request includes a designated application identifier corresponding to the second user equipment, an identifier corresponding to the M2M device, and permission term modification information.

4. The method according to any one of claims 1 to 3, further comprising:

the first user equipment sends a management canceling permission request to the server, wherein the management canceling permission request is used for indicating the server to release the binding relationship between the designated application identifier corresponding to the second user equipment and the identifier corresponding to the M2M device, and sending management canceling permission confirmation information to the second user equipment, and the management canceling permission confirmation information is used for indicating that the second user equipment does not have the second management permission of the M2M device;

the request for canceling the management authority includes a designated application identifier corresponding to the second user equipment, an identifier corresponding to the M2M device, and management authority canceling information.

5. The method of claim 4, wherein before the first user equipment sends the request for canceling the management authority to the server, the method further comprises:

the first user equipment deletes the second management authority of the second user equipment to the M2M device, which includes any one of the following modes:

the first user equipment selects an authority management interface on a designated application toolbar interface corresponding to the M2M equipment, and deletes second management authority of the second user equipment on the M2M equipment on the authority management interface;

or,

the first user equipment selects a permission management interface in a designated application menu bar option corresponding to the M2M device, and deletes second management permission of the second user equipment to the M2M device on the permission management interface;

or,

the first user equipment deletes the second management authority of the second user equipment to the M2M equipment through a voice or word command on a specified application dialog box interface corresponding to the M2M equipment;

or,

the first user equipment clicks an icon corresponding to the M2M equipment on a designated application interface corresponding to the M2M equipment, a right management interface is selected, and second management right of the second user equipment to the M2M equipment is deleted on the right management interface;

or,

and the first user equipment selects an authority management interface by long-pressing an icon corresponding to the M2M device on a designated application interface corresponding to the M2M device, and deletes the second management authority of the second user equipment on the M2M device on the authority management interface.

6. The method of claim 5, wherein the obtaining, by the first user equipment, the designated application identifier corresponding to the second user equipment comprises:

the first user equipment acquires a specified application identifier corresponding to the second user equipment from a specified application interface corresponding to the M2M equipment;

or,

and the first user equipment acquires the specified application identifier corresponding to the second user equipment from the specified application dialog box interface corresponding to the M2M equipment.

7. The method according to claim 6, wherein before the first user equipment obtains the designated application identifier corresponding to the second user equipment, the method further comprises:

the first user device selecting the M2M device;

the first user equipment selects a user icon corresponding to the second user equipment on a management interface of the M2M equipment;

and the first user equipment selects any application corresponding to the second user equipment as a designated application on a management interface of a user icon corresponding to the second user equipment.

8. A method for assigning M2M device management rights, comprising:

a server receives a management authority distribution request of an M2M device sent by a first user device, wherein the first user device has a first management authority of the M2M device;

the server sends a management request of the M2M device to a second user device according to the management authority allocation request, wherein the management request is used for indicating the second user device to send a binding request of the M2M device to the server;

the server receives the binding request sent by the second user equipment, wherein the binding request comprises a specified application identifier corresponding to the second user equipment and an identifier corresponding to the M2M device, and the specified application identifier corresponding to the second user equipment is a specified application identifier corresponding to an application logged on the second user equipment;

the server binds the specified application identifier corresponding to the second user equipment with the identifier corresponding to the M2M equipment according to the binding request;

and the server sends binding confirmation information to the second user equipment, wherein the binding confirmation information is used for indicating that the second user equipment has the second management authority of the M2M equipment.

9. The method of claim 8, further comprising:

the management authority allocation request and the management request comprise a specified application identifier corresponding to the second user equipment, an identifier corresponding to the M2M equipment, equipment management information, equipment binding credential information and a specified application identifier corresponding to the first user equipment;

the binding request further includes the device binding credential information corresponding to the M2M device.

10. The method according to claim 9, wherein the management right allocation request further includes right deadline information corresponding to the second management right, and the method further comprises:

the server receives a permission deadline modification request sent by the first user equipment;

the server modifies the authority limit information according to the authority limit modification request;

the server sends permission term modification confirmation information to the second user equipment, wherein the permission term modification confirmation information is used for indicating that the second management permission corresponds to a new permission term;

wherein, the permission term modification request includes a designated application identifier corresponding to the second user equipment, an identifier corresponding to the M2M device, and permission term modification information.

11. The method according to any one of claims 8 to 10, further comprising:

the server receives a request for canceling the management authority sent by the first user equipment;

the server modifies the authority limit information according to the management authority canceling request;

the server sends cancellation management authority confirmation information to the second user equipment, wherein the cancellation management authority confirmation information is used for indicating that the second management authority of the second user equipment to the M2M equipment is cancelled;

the request for canceling the management authority includes a designated application identifier corresponding to the second user equipment, an identifier corresponding to the M2M device, and management authority canceling information.

12. A user device, comprising:

the acquisition module is used for acquiring a designated application identifier corresponding to second user equipment, wherein the designated application identifier corresponding to the second user equipment is a designated application identifier corresponding to an application logged on the second user equipment;

a sending module, configured to send a management permission allocation request of an M2M device to a server according to the designated application identifier corresponding to the second user device obtained by the obtaining module, where the management permission allocation request is used to instruct the server to send a management request of the M2M device to the second user device, the management request is used to instruct the second user device to send a binding request of the M2M device to the server, the binding request is used to instruct the server to bind the designated application identifier corresponding to the second user device and the identifier corresponding to the M2M device, and send binding confirmation information to the second user device, and the binding confirmation information is used to instruct the second user device to have a second management permission of the M2M device;

wherein, the binding request includes a specific application identifier corresponding to the second user equipment and an identifier corresponding to the M2M device.

13. The user equipment of claim 12,

the management authority allocation request and the management request comprise a specified application identifier corresponding to the second user equipment, an identifier corresponding to the M2M equipment, equipment management information, equipment binding credential information and a specified application identifier corresponding to the first user equipment;

the binding request further includes the device binding credential information corresponding to the M2M device.

14. The user equipment of claim 13,

the management authority allocation request also comprises authority limit information corresponding to the second management authority;

the sending module is further configured to send a permission term modification request to the server, where the permission term modification request is used to instruct the server to modify the permission term information, and send permission term modification confirmation information to the second user equipment, where the permission term modification confirmation information is used to instruct the second management permission to correspond to a new permission term;

wherein, the permission term modification request includes a designated application identifier corresponding to the second user equipment, an identifier corresponding to the M2M device, and permission term modification information.

15. The user equipment according to any of claims 12 to 14,

the sending module is further configured to send a request for canceling management permission to the server, where the request for canceling management permission is used to instruct the server to release a binding relationship between a designated application identifier corresponding to the second user equipment and an identifier corresponding to the M2M device, and send information for confirming cancellation management permission to the second user equipment, where the information for confirming cancellation management permission is used to instruct the second user equipment not to have a second management permission of the M2M device;

the request for canceling the management authority includes a designated application identifier corresponding to the second user equipment, an identifier corresponding to the M2M device, and management authority canceling information.

16. The user equipment of claim 15, further comprising:

a deleting module, configured to delete the second management permission of the second user device to the M2M device before the sending module sends the request for canceling the management permission to the server, where the deleting module includes any one of the following manners:

selecting a right management interface on a designated application toolbar interface corresponding to the M2M device, and deleting a second management right of the second user device to the M2M device on the right management interface;

or,

selecting a right management interface in a designated application menu bar option corresponding to the M2M device, and deleting a second management right of the second user device to the M2M device on the right management interface;

or,

deleting the second management authority of the second user equipment to the M2M equipment through a voice or word command on a specified application dialog box interface corresponding to the M2M equipment;

or,

clicking an icon corresponding to the M2M device on a designated application interface corresponding to the M2M device, selecting a right management interface, and deleting a second management right of the second user device to the M2M device on the right management interface;

or,

and selecting an authority management interface by long-pressing an icon corresponding to the M2M device on a designated application interface corresponding to the M2M device, and deleting the second management authority of the second user equipment to the M2M device on the authority management interface.

17. The user equipment of claim 16,

the obtaining module is specifically configured to obtain a specified application identifier corresponding to the second user equipment from a specified application interface corresponding to the M2M device;

or,

the obtaining module is specifically configured to obtain the specified application identifier corresponding to the second user equipment from the specified application dialog interface corresponding to the M2M device.

18. The user equipment of claim 17, further comprising:

a selecting module, configured to select the M2M device before the obtaining module obtains the specified application identifier corresponding to the second user equipment;

the selection module is further configured to select a user icon corresponding to the second user equipment on a management interface of the M2M device;

the selection module is further configured to select any one of the applications corresponding to the second user equipment as a designated application on a management interface of a user icon corresponding to the second user equipment.

19. A server, comprising:

a receiving module, configured to receive a management authority allocation request of an M2M device sent by a first user device, where the first user device has a first management authority of the M2M device;

a sending module, configured to send a management request of the M2M device to a second user device according to the management permission allocation request, where the management request is used to instruct the second user device to send a binding request of the M2M device to the server;

the receiving module is further configured to receive the binding request sent by the second user equipment, where the binding request includes an application identifier corresponding to the second user equipment and an identifier corresponding to the M2M device, and the application identifier corresponding to the second user equipment is an application identifier corresponding to an application logged on the second user equipment;

a binding module, configured to bind, according to the binding request, the specified application identifier corresponding to the second user equipment and the identifier corresponding to the M2M device;

the sending module is further configured to send binding confirmation information to the second user equipment, where the binding confirmation information is used to indicate that the second user equipment has the second management authority of the M2M device.

20. The server according to claim 19,

the management authority allocation request and the management request comprise a specified application identifier corresponding to the second user equipment, an identifier corresponding to the M2M equipment, equipment management information, equipment binding credential information and a specified application identifier corresponding to the first user equipment;

the binding request further includes the device binding credential information corresponding to the M2M device.

21. The server according to claim 20, wherein the management right allocation request further includes right duration information corresponding to the second management right, and the server further includes:

the receiving module is further configured to receive an authority deadline modification request sent by the first user equipment;

the modification module is used for modifying the authority limit information according to the authority limit modification request;

the sending module is further configured to send permission term modification confirmation information to the second user equipment, where the permission term modification confirmation information is used to indicate that the second management permission corresponds to a new permission term;

wherein, the permission term modification request includes a designated application identifier corresponding to the second user equipment, an identifier corresponding to the M2M device, and permission term modification information.

22. A server according to any one of claims 19 to 21, further comprising:

the receiving module is further configured to receive a request for canceling management permission sent by the first user equipment;

a removing module, configured to remove, according to the request for canceling management authority, a binding relationship between a specified application identifier corresponding to the second user equipment and an identifier corresponding to the M2M device;

the sending module is further configured to send cancellation management authority confirmation information to the second user equipment, where the cancellation management authority confirmation information is used to indicate that a second management authority of the second user equipment to the M2M device is cancelled;

the request for canceling the management authority includes a designated application identifier corresponding to the second user equipment, an identifier corresponding to the M2M device, and management authority canceling information.

23. A system, comprising:

a user device and a server;

the user equipment of any one of claims 12 to 18;

the server according to any of claims 19 to 22.