CN106339632B

CN106339632B - A kind of method, user equipment and system for distributing M2M equipment management permission

Info

Publication number: CN106339632B
Application number: CN201510404339.2A
Authority: CN
Inventors: 于小博; 龙水平
Original assignee: Huawei Device Dongguan Co Ltd
Current assignee: Huawei Device Co Ltd
Priority date: 2015-07-10
Filing date: 2015-07-10
Publication date: 2019-04-26
Anticipated expiration: 2035-07-10
Also published as: WO2017008705A1; CN106339632A

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

Method, user equipment and system for distributing M2M equipment management authority

Technical Field

The invention relates to the technical field of communication, in particular to a method, user equipment and a system for distributing M2M equipment management authority.

Background

Nowadays, machine-to-machine (M2M) devices can realize intelligent and interactive seamless connection between people and machines through social applications, and therefore, the social applications become very important internet-of-things connectors.

The principle of implementing the internet of things is to bind a specified application identifier corresponding to the user equipment with an identifier corresponding to the M2M device, and the user equipment controls and operates the M2M device through the corresponding specified application identifier. For example, fig. 1 is a main technical architecture of a wechat internet of things, where the wechat internet of things mainly adopts a technical scheme of "cloud to cloud", that is, a wechat public account corresponding to a user equipment is bound with an equipment identifier corresponding to an M2M equipment, so that the user equipment has a 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 device is provided with the management authority of the M2M device, the user device is not provided with the capability of sending a management authority allocation request of the M2M device to the server, so that the user device cannot allocate additional management authority of the M2M device to other user devices through the server, thereby affecting the user experience.

Disclosure of Invention

The embodiment of the invention provides a method, user equipment and a system for distributing management authority of M2M equipment, which are used for enabling the user equipment to have the capacity of sending a management authority distribution request of the M2M equipment to a server, and further enabling the additional management authority of the M2M equipment to be distributed to other user equipment through the server, so that the other user equipment also has the management authority of the M2M equipment, a plurality of user equipment can have the management authority of the M2M equipment, and user experience is improved.

The invention provides a method for distributing M2M device management authority, which comprises the following steps:

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.

With reference to the first aspect, in a first possible implementation manner,

the management authority allocation request and the management request comprise a designated application identifier corresponding to the second user equipment, an identifier corresponding to the M2M device, device management information, device binding credential information, and a designated application identifier corresponding to the first user equipment, wherein the identifier corresponding to the M2M device comprises 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.

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

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.

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

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.

With reference to the third possible implementation manner of the first aspect, in a fourth possible implementation manner, before the sending, by the first user equipment, the request to cancel 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, 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.

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

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.

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

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.

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

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, and at least one M2M device is provided;

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.

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

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

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;

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

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

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;

A third aspect of the present invention provides a user equipment, 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 the 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;

With reference to the third aspect, in a first possible implementation manner,

the management authority allocation request and the management request comprise a designated application identifier of the second user equipment, an identifier corresponding to the M2M device, device management information, device binding credential information, and a designated application identifier corresponding to the first user equipment, wherein the identifier corresponding to the M2M device comprises a designated application identifier corresponding to the M2M device and/or a device identifier corresponding to the M2M device;

With reference to the first possible implementation manner of the third aspect, in a second possible implementation manner,

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;

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

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;

With reference to the third possible implementation manner of the third aspect, in a fourth possible implementation manner, the method further includes:

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.

With reference to the fourth possible implementation manner of the third aspect, in a fifth possible implementation manner,

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.

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

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.

A fourth aspect of the present invention provides 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, and at least one of the M2M devices is provided;

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.

With reference to the fourth aspect, in a first possible implementation manner,

With reference to the first possible implementation manner of the fourth aspect, in a second possible implementation manner, the management authority allocation request further includes authority limit information corresponding to the second management authority, 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;

With reference to the fourth aspect or any one of the first to the second possible implementation manners 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 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;

A fifth aspect of the present invention provides a system, comprising:

a user device and a server;

the user equipment is as in the third aspect;

the server is as in the fourth aspect.

By applying the technical scheme, the first user equipment acquires the specified application identifier corresponding to the second user equipment, the first user equipment sends the management authority allocation request of the M2M equipment to the server according to the specified application identifier corresponding to the second user equipment, the management authority allocation request is used for instructing the server to send a management request of the M2M device to the second user device, the management request is used for instructing the second user equipment to send a binding request of the M2M device to the server, the binding request includes the specified application identifier corresponding to the second user equipment and the identifier corresponding to the M2M device, 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. Because the first user equipment has the first management authority of the M2M device, different from the prior art, the first user equipment has the capability of sending a management authority distribution request of the M2M device to the server, and further the server binds the specified 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 a plurality of user equipment have the management authority of the M2M device and improving user experience.

Drawings

FIG. 1 is a diagram of a prior art architecture of WeChat physical association;

FIGS. 2a-2b are schematic diagrams of an embodiment of a prior art WeChat physical link;

FIG. 3 is a diagram of an embodiment of a method for assigning M2M device management rights in an embodiment of the present invention;

FIG. 4 is a diagram illustrating another embodiment of a method for assigning M2M device management rights in an embodiment of the present invention;

FIG. 5 is a diagram of another embodiment of a method for assigning M2M device management rights in an embodiment of the present invention;

FIG. 6 is a diagram of another embodiment of a method for assigning M2M device management rights in an embodiment of the present invention;

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

FIG. 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;

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

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

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

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

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

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

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

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

FIG. 19 is a schematic diagram of one embodiment of a system in accordance with embodiments of the present invention;

fig. 20 is a schematic structural diagram of assigning M2M device management authority in the embodiment of the present invention.

Detailed Description

The embodiment of the invention provides a method, user equipment and a system for distributing management authority of an M2M device, which are used for enabling the user equipment to have the capability of sending a management authority distribution request of the M2M device to a server, and further enabling the additional management authority of the M2M device to be distributed to other user equipment through the server, so that the other user equipment also has the management authority of the M2M device, and user experience is improved.

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The terms "first," "second," "third," "fourth," and the like in the description and in the claims, as well as in the drawings, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that the embodiments described herein may be practiced otherwise than as specifically illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

It is to be understood that the terminology used in the embodiments of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the examples of the present invention and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

The technical scheme of the 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 (WCDMA), General Packet Radio Service (GPRS), Long Term Evolution (LTE), and the like.

User Equipment (UE) in the embodiments of the present invention, which may also be referred to as a mobile terminal (mobile terminal), a mobile User Equipment, and the like, may communicate with one or more core networks through a Radio Access Network (for example, RAN), and the User Equipment may be a mobile terminal, such as a mobile phone (or referred to as a "cellular" phone) and a computer having the mobile terminal, for example, a portable, pocket, handheld, computer-embedded, or vehicle-mounted mobile device, which exchanges language and/or data with the Radio Access Network.

Fig. 2a-2b are examples of a slightly trusted internet of things in the prior art, where the gudgeon bracelet is a product supporting slightly trusted internet of things, and its main function is to share and rank the motion data of a user by using a slightly trusted public account, and a user device focuses on the slightly trusted public account of the gudgeon bracelet, so as to bind the gudgeon bracelet, and the user device can upload the motion data to the slightly trusted user, and rank the user corresponding to the user device and other users according to the health data, and the user can view the daily motion ranking through the user device. In addition, a user can check health data of the gudong bracelet through a WeChat public account, set a personal exercise plan, set a bracelet alarm and the like, and bind the gudong bracelet by using the WeChat public account, so that the gudong bracelet is controlled and managed, however, when the user wants to allocate the additional management authority of the gudong bracelet to other users, in the prior art, the user equipment does not have the capability of sending a management authority allocation request of the gudong bracelet to a server, so that the idea of the user cannot be realized, the user experience is influenced, and therefore, the discussion of the invention is developed:

referring to fig. 3, an embodiment of a method for assigning M2M device management permissions according to an embodiment of the present invention includes:

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

the first user equipment has a first management authority of M2M equipment, and at least one of the M2M equipment is provided, where the first user equipment may further send a binding request to the server by obtaining an identifier corresponding to the M2M equipment, so that the server binds a specified application identifier corresponding to the first user equipment with the identifier corresponding to the M2M equipment, thereby obtaining the first management authority of the M2M equipment, and may also obtain the first management authority of the M2M equipment in other manners, which is not specifically limited herein.

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

The first management authority is a master authority of the M2M device, and the user device with the master authority can send a 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 device through the server, and the first user device and the second user device also have the management authority of the M2M device.

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

The specific application identifier is an account or a name, etc. for identifying the specific application, or may be other symbols for identifying the specific application, which is not specifically limited herein. In the present invention, the specific application identifier may be a social account or a public account of the specific application, such as a wechat public account. Any application corresponding to the second user equipment may be used as a designated application, such as any social application, for example: QQ, WeChat, whatcapp, line, twitter, facebook, etc.

302. The first user equipment sends a management authority distribution request of the M2M equipment to the server according to the appointed application identification corresponding to the second user equipment;

the management authority allocation request is used for instructing the server to send a management request of the M2M device to the second user device, the management request is used for instructing the second user device to send a binding request of the M2M device to the server, wherein the binding request includes a specified application identifier corresponding to the second user device and an identifier corresponding to the M2M device, the binding request is used for instructing the server to bind the specified application identifier corresponding to the second user device and the identifier corresponding to the M2M device, and binding confirmation information is sent to the second user device, and the binding confirmation information is used for instructing the second user device to have a second management authority of the M2M device.

The second management authority is an additional management authority of the M2M device, and the second user device can also control and manage the M2M device through the additional management authority, which is the same as the first management authority, but the difference is that the second management authority is passively acquired by the second user device, and the first user device can send a request for canceling the second management authority to the server at any time, so that the server cancels the second management authority.

It should be noted that, in the present invention, a server may be understood as a specific application server or a specific service server, which may be specific to an actual application. The designated application server may be understood as a server corresponding to the designated application (e.g., a wechat server, a QQ server, a facebook server, or some other social networking server), and the service server may be understood as an M2M device vendor server providing an M2M device service and a management function, such as a cordong bracelet server.

In the embodiment of the present invention, since a first user device has a first management right of an M2M device, different from the prior art, the first user device sends a management right allocation request of an M2M device to a server, where the management right allocation request is used to instruct the server to send a management request of the M2M device to a 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 includes a specified application identifier corresponding to the second user device and an identifier corresponding to the M2M device, and further the server binds the specified application identifier corresponding to the second user device and the identifier corresponding to the M2M device, so that the second user device has a second management right of the M2M device, thereby realizing that a plurality of user devices all have the management right of the M2M device, the user experience is improved.

Referring to fig. 4, based on the embodiment shown in fig. 3, another embodiment of the method for assigning M2M device management authority according to the embodiment of the present invention includes:

401. the first user equipment pays attention to the designated application identifier corresponding to the M2M equipment;

in the embodiment of the present invention, the identifier corresponding to the M2M device includes a specified 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 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 focus on the designated application identifier corresponding to the M2M device. The specified application identification may refer to the definition of the specified application identification in the embodiment shown in fig. 3.

402. The first user device enables an M2M device;

after the first user device focuses on the designated application identifier corresponding to the M2M device, the M2M device may be further enabled by scanning the device identifier (for example, a two-dimensional code, an ID number ID) corresponding to the M2M device, or the M2M device may be enabled by other manners, which is not limited herein.

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

in the embodiment of the invention, the server comprises a designated application server and a service server.

After the first user equipment enables the M2M device, a binding request of the M2M device is sent to a service server through a specified application service corresponding to the M2M device, where the binding request includes a specified application identifier corresponding to the first user equipment and a device identifier corresponding to the M2M device.

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

after receiving a binding request of the M2M device sent by the first user device, the service server binds the specified application identifier corresponding to the first user device and the device identifier corresponding to the M2M device.

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

after the service server binds the specified application identifier corresponding to the first user equipment and the device identifier corresponding to the M2M device, the service server sends binding confirmation information of the M2M device to the first user equipment through the specified application server.

406. The method comprises the steps that a first user device obtains a first management authority of an M2M device;

the first user device receives the binding acknowledgement message sent by the designated application server, thereby possessing the first management authority of the M2M device.

407. The first user equipment acquires a designated 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 allocates the management authority of the M2M device to the second user equipment in advance, and then the first user equipment first acquires a corresponding designated application identifier of 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 on the second user equipment.

In some optional embodiments, the first user equipment obtains a specified application identifier corresponding to the second user equipment from a specified application interface corresponding to the M2M device, such as: the method comprises the steps that a first user device selects a second user device on an input toolbar of a social public account interface corresponding to an M2M device, and receives a designated application identifier corresponding to the second user device; or, the first user equipment obtains a specified application identifier corresponding to the second user equipment from a specified application dialog interface corresponding to the M2M device, for example: the first user equipment selects the second user equipment in the specified application dialog box corresponding to the M2M device, and receives the specified application identification corresponding to the second user equipment. The specific acquisition method may be determined according to actual conditions, and is not specifically limited herein.

In addition, before the first user equipment obtains the designated application identifier corresponding to the second user equipment, it is further required to determine the designated application corresponding to the second user equipment, specifically: 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, for example, the icon indicates a user of the first user equipment for pre-allocating management authority 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.

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

the first user equipment sends a management authority allocation request of the M2M device to a specified application server according to a specified application identifier of the second user equipment, wherein the management authority allocation request is used for indicating the specified application server to send a management request of the M2M device to the second user equipment.

The management authority allocation request includes an application identifier corresponding to the second user equipment, an identifier corresponding to the M2M device, device management information, device binding credential information, and an 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 identifier is a two-dimensional code for identifying the M2M device, an identification number, a model number, a production date, manufacturer information, a production lot, and the like, and is a marking feature of the M2M device. The device management information includes management interface graphic information for displaying the M2M device and function table information corresponding to the management interface. The user device having the management authority can manipulate and manage the M2M device through the device management information.

Before the server binds the designated application identifier corresponding to the second user equipment and the identifier corresponding to the M2M device, the device binding credential information is verified according to the binding request, for example, the server may authorize the binding request of the second user equipment through the obtained device binding credential information, and then bind the designated application identifier of the second user equipment and 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 device.

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

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

the method comprises the steps that a specified application server receives a management authority distribution request of an M2M device sent by a first user device, and further sends a management request of the M2M device to a second user device, wherein the management request comprises a specified application identifier corresponding to the second user device, an identifier corresponding to the M2M device, device management information, device binding credential information and a specified application identifier corresponding to the first user device, and the management request is used for indicating the second user device to send a binding request of the M2M device to the specified application server.

410. The second user equipment judges whether to pay attention to the designated application identifier corresponding to the M2M equipment, if so, step 411 is executed, and if not, step 412 is executed;

the second user equipment receives the management request of the M2M device sent by the designated application server, and further determines whether the second user equipment has paid attention to the designated application identifier corresponding to the M2M device, if yes, step 411 is executed, and if no, step 412 is executed.

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

and if the second user equipment pays attention to the designated application identifier corresponding to the M2M equipment, the second user equipment sends indication information on the designated application interface corresponding to the M2M, wherein the indication information is used for indicating the second user equipment to accept the management request.

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

and if the second user equipment does not pay attention to the designated application identifier corresponding to the M2M equipment, the second user equipment sends indication information on a 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 an attention request indicating that the second user equipment accepts the designated application identifier corresponding to the M2M device.

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

after the second user equipment receives the management request through the indication information, the second user equipment sends a binding request of the M2M device to a service server through a specified application server, wherein the binding request is used for indicating the service server to bind a specified application identifier corresponding to the second user equipment with a device identifier corresponding to the M2M device, and sending binding confirmation information 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.

The binding request includes a designated 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, 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, and then the service server binds the designated application identifier corresponding to the second user equipment and the device identifier corresponding to the M2M device.

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

and the service server receives the binding request of the M2M device, can verify through the device binding certificate information in the binding request, and further binds the specified application identifier corresponding to the second user device 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 device;

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

416. And the second user equipment acquires the second management authority of the M2M equipment and displays the binding confirmation information on the corresponding specified application interface.

And the second user equipment receives the binding confirmation information of the M2M device, so that the second management authority of the M2M device is possessed, generates a specified application interface corresponding to the M2M device according to the binding confirmation information, and displays the binding confirmation information on the specified application interface corresponding to the M2M device.

In some optional embodiments, the management authority allocation request further includes authority limit information corresponding to the second management authority. Such as: the authority limit is half a year, a month, etc., and the authority limit may be set by the user through the first user equipment, or may be set by default for the first user equipment, and is not specifically limited herein.

In some optional embodiments, the first user equipment sends a permission term modification request to a service server through a designated application server, where the permission term modification request is used to instruct the service server to modify the permission term information, and sends permission term modification confirmation information to the second user equipment through the designated application server, 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, a device identifier corresponding to the M2M device, and permission term modification information.

In some optional embodiments, the first user equipment sends a request for canceling management authority to the service server through a designated application server, where the request for canceling management authority is used to instruct the service server to release the binding relationship between the designated application identifier corresponding to the second user equipment and the device identifier corresponding to the M2M device, and sends a confirmation message for canceling management authority to the second user equipment through the designated application server, where the confirmation message for canceling management authority is used to instruct the second user equipment not to 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 device identifier corresponding to the M2M device, and management authority canceling information.

In addition, before the first user equipment sends the request for canceling the management authority to the specified application server, 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 right management interface in a designated application menu bar option corresponding to the M2M device, and deletes the second management right of the second user equipment to the M2M device on the right 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 device on a designated application interface corresponding to the M2M device, selects a right management interface, and deletes the second management right of the second user equipment to the M2M device on the right management interface; or, 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. There are various ways for the first user device to delete the second management authority of the second user device to the M2M device, and this is not limited in detail here.

In some optional embodiments, the service server prompts that the second user equipment no longer has the second management authority by specifying that the application server sends the information that the authority limit expires to the second user equipment.

It should be noted that, in the embodiment of the present invention, one or more second user devices may be used, and one or more M2M devices may also be used, and when there are multiple M2M devices, a list corresponding to the M2M devices is formed, and the method for specifically allocating M2M device management permissions is the steps in the embodiment of the present invention, and is not described herein again.

In the embodiment of the present invention, a first user equipment has a first management right of an M2M device, and different from the prior art, in the present invention, the first user equipment can send a management right allocation request of an M2M device to a service server through a designated application server, where the management right allocation request is used to instruct the server to send a management request of the M2M device to a 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 binding request includes a designated application identifier corresponding to the second user equipment and a device identifier corresponding to the M2M device, and the service server binds the designated application identifier corresponding to the second user equipment and the device identifier corresponding to the M2M device, so that the second user equipment has a second management right of the M2M device, therefore, a plurality of user devices all have the management authority of the M2M device, and user experience is improved. In addition, the first user equipment can send an authority limit modification request or a management authority cancellation request to the service server through the appointed application server, and then the service server modifies the authority limit information or modifies the authority limit information, so that the modification of the authority limit and the cancellation of the management authority 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 may add the M2M device by selecting it on a specific application interface, and the specific adding manner is various and is not limited herein.

502. The first user device enables an M2M device;

the first user device may enable the M2M device by scanning the two-dimensional code corresponding to the M2M device, where enabling the M2M device may be understood as opening a binding request interface of the M2M device, and the specific enabling manner is various and is not limited herein.

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

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

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

the appointed application server receives the binding request sent by the first user equipment, binds the appointed application identification corresponding to the first user equipment with the appointed application identification corresponding to the M2M equipment, and further sends M2M equipment binding confirmation information to the first user equipment.

505. The method comprises the steps that a first user device obtains a first management authority of an M2M device;

the first user device receives the binding confirmation information sent by the designated application server, so that the first user device has a first management authority of the M2M device, wherein the first management authority is a master authority of the M2M device.

506. The first user device initiates a specified application dialog with the M2M device;

507. the first user equipment selects a designated application corresponding to the second user equipment on a designated application dialog box interface;

508. the method comprises the steps that a first user device obtains a designated application identifier of a second user device;

the first user equipment allocates the management authority of the M2M device to the second user equipment in advance, and then the first user equipment acquires the designated application identifier of the second user equipment according to the designated application corresponding to the second user equipment, where the designated application identifier corresponding to the second user equipment is the designated application identifier corresponding to the application logged on the second user equipment.

In some optional embodiments, the first user equipment obtains 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 device selects the second user device in the designated application dialog box corresponding to the M2M device and receives the designated application identification for the second user device. The specific acquisition method may be determined according to actual conditions, and is not specifically limited herein.

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

in this embodiment of the present invention, the management authority allocation request includes a specific application identifier corresponding to the second user equipment, a specific application identifier, device management information, and device binding credential information corresponding to the M2M device, and a specific application identifier corresponding to the first user equipment.

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

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

the appointed application server receives the management authority distribution request of the M2M device sent by the first user device, and further sends the management request of the M2M device to the second user device.

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

In some optional embodiments, the second user device prompts and displays the designated application identifier and the management request information corresponding to the M2M device in the communication dialog box with the first user device, or displays the designated application identifier and the management request information corresponding to the M2M device in the application of the new friend, and proceeds to step 512 after confirmation.

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

after the second user equipment receives the management request through the indication information, the second user equipment sends a binding request of the M2M device to the specified application server.

The binding request includes a specific 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 specified application identifier corresponding to the M2M device, or includes a specified application identifier corresponding to the M2M device and a device identifier corresponding to the M2M device.

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

and after receiving the management authority allocation request of the M2M device, the designated application server binds the designated application identifier corresponding to the second user device with the designated application identifier corresponding to the M2M device.

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

and after the designated application server binds the designated application identifier corresponding to the second user equipment with the designated application identifier corresponding to the M2M equipment, further sending binding confirmation information of the M2M equipment to the second user equipment.

515. The second user device obtains a second management right of the M2M device.

The second user device receives the binding acknowledgement information of the M2M device transmitted from the designated application server, thereby possessing the second management authority of the M2M device.

Further, after the second user device acquires the second management authority of the M2M device, the binding confirmation information is displayed in a specified application dialog box with the first user device.

In some optional embodiments, the first user equipment sends a permission term modification request to the specified application server, where the permission term modification request is used to instruct the specified application server to modify the permission term information, and sends 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;

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

In some optional embodiments, the first user device sends a request for canceling management authority to the designated application server, where the request for canceling management authority is used to instruct the designated application server to release the binding relationship between the designated application identifier corresponding to the second user device and the designated application identifier corresponding to the M2M device, and sends a confirmation message for canceling management authority to the second user device, where the confirmation message for canceling management authority is used to instruct the second user device not to 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 canceling information.

In addition, before the first user equipment sends the request for canceling the management permission to the specified application server, the first user equipment deletes the second management permission of the second user equipment to the M2M device, and a specific deletion manner may refer to relevant contents in the embodiment shown in fig. 4 of the present invention, which is not described herein again.

In some optional embodiments, the designated application server sends information of the expiry of the permission period to the second user equipment, and prompts that the second user equipment does not possess the second management permission any more.

In the embodiment of the present invention, a first user equipment has a first management authority of an M2M device, and different from the prior art, in the present invention, the first user equipment has a capability of sending a management authority allocation request of an M2M device to a specified application server, where the management authority allocation request is used to instruct the server to send a management request of the M2M device to a 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 binding request includes a specified application identifier corresponding to the second user equipment and a specified application identifier corresponding to the M2M device, and the specified application server binds the specified application identifier corresponding to the second user equipment and the specified application identifier corresponding to the M2M device, so that the second user equipment has a second management authority of the M2M device, therefore, a plurality of user devices all have the management authority of the M2M device, and user experience is improved. In addition, the first user equipment can send an authority limit modification request or a management authority cancellation request to the appointed application server, and then the appointed application server modifies the authority limit information or modifies the authority limit information, so that the modification of the authority limit and the cancellation of the management authority are realized, and the user experience is effectively improved.

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

601. the server receives a management authority distribution request of the M2M device sent by the first user device;

in the embodiment of the invention, the server comprises a designated application server or a service server. In particular, reference may be made to the server in the embodiment shown in fig. 4 or fig. 5.

The first user device is provided with a first administrative authority for the M2M devices, at least one of the M2M devices.

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

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

603. The server receives a binding request sent by 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 identifier corresponding to the M2M device.

604. 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 specified application identifier corresponding to the second user equipment is the specified application identifier corresponding to the application logged on the second user equipment.

605. 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.

In some optional embodiments, the management permission allocation request and the management request both include a specific application identifier corresponding to the second user device, an identifier corresponding to the M2M device, device management information, device binding credential information, and a specific application identifier corresponding to the first user device;

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

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

In the embodiment of the invention, a server receives a management authority distribution request of an M2M device sent by a first user device, and sends a management request of an M2M device to a second user device according to the management authority distribution request; the management request is used for instructing 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. And 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 a plurality of user equipment all have the management authority of the M2M device, and improving user experience.

With reference to the foregoing embodiments, the following describes specific application scenario embodiments of the method for assigning M2M device management permissions:

as shown in fig. 7, xiaoming wants to assign the management authority of M2M device (such as smart hardware device tv) in home to its father. The specific process is as follows: the method comprises the steps that Xiaoming opens a public account (such as a WeChat public number) of a television, selects 'contact authority' from an input toolbar in a public account interface, selects a user (such as the Xiaoming father) who wants to be authorized from 'select the contact', further, if the Xiaoming father does not pay attention to the public account, receives public account attention and management authority receiving confirmation prompt information in a system interface with the Xiaoming, the Xiaoming father automatically pays attention to the corresponding public account after confirmation and obtains management authority of the television, if the Xiaoming father pays attention to the public account, receives management authority receiving confirmation prompt information in a communication dialog box with the Xiaoming, and the Xiaoming father obtains the management authority of the television after confirmation.

As shown in fig. 8, xiaoming wants to assign the management authority of M2M device (e.g. computer) in home to its father. The specific process is as follows: xiaoming finds own father on a social application (such as QQ) interface, further opens the QQ interface, selects 'contact authority', and selects a computer to be added from 'my equipment'. The Xiaoming father receives the management authority receiving confirmation prompt message sent by the Xiaoming father, and the Xiaoming father immediately obtains the management authority of the computer at home after confirmation.

As shown in fig. 9, xiaoming wants to assign the management authority of M2M device (e.g. computer) in home to its father. The specific process is as follows: xiaoming finds a computer in a social application client (such as QQ) My interface, opens a dialog box, selects 'Add contact Authority', and selects a parent from 'My contacts'. The computer automatically sends a friend adding request to the social application account number used by the Mingmen father after receiving the social application account number used by the Mingmen father sent by the Mingmen, and the Mingmen father obtains the management authority of the computer at home after receiving the request of adding friends from the computer.

As shown in fig. 10, xiaoming leases an empty room in a home to a xiaoyu, and assigns the management authority of the air conditioner in the room to the xiaoyu in an authorized manner, and after several months, the xiaoyu needs to move to other places to live, and the xiaoming recovers the management authority of the air conditioner in the room by the xiaoyu as follows.

The specific process is as follows: xiaoming presses 'contact authority' for a long time in an option below a public account dialog box of an M2M device (such as an M2M terminal), triggers to enter an 'authority management' interface, and deletes a user (Xiaoyu) in an authority management column;

or selecting 'authority management' in the menu options of the public account, triggering to enter an 'authority management' interface, and deleting the user (little universe) in the authority management column.

Or in the public account, clicking a voice button and saying 'WeChat deletes the authority of the Xiaoyu', or deleting the user (Xiaoyu) by a word command 'deleting the authority of the Xiaoyu'.

As shown in fig. 11, xiaoming can also receive the management authority of xiaoyu on the air conditioner in the room through other ways:

select the icon of the M2M device (air conditioner), select the "rights management" field, and delete the user (little space) in the rights management field;

or long-pressing an icon of the M2M device (air conditioner) triggers entering an authority management interface and deleting the user (Xiaoyu) in the authority management column.

Further, as shown in FIG. 12, the Xiaoming friend Xiaoyu weekend lives in Xiaoming's home for two days, and Xiaoming assigns the management authority of the M2M device (e.g., smart hardware device television) in home to Xiaoyu and specifies the valid time to be 2 days.

The specific process is as follows: xiaoming opens the public account (such as WeChat public number) of the television, selects 'contact authority' in an input toolbar in a public account interface, selects a user (such as Xiaoyu) to be authorized from 'select contact', and sets granted management term information. The Xiaoyu clicks to receive the management authority information and sees the management term granted by Xiaoming on the dialog interface with the M2M device as 2 days.

Further, when the god wants to modify the management deadline information of the god for the air conditioner, the specific flow is as shown in fig. 13:

selecting an icon of an M2M device (air conditioner), selecting a "rights management" field, and modifying the management term information in the rights management field;

or long-pressing an icon of the M2M device (air conditioner) triggers entering a 'authority management' interface and modifying the management term information in the authority management column.

In addition, the management deadline information may also be modified in other ways, and a specific flow is shown in fig. 14:

pressing down the 'contact authority' in an option below an M2M device public account dialog box, triggering to enter an 'authority management' interface, and modifying the management term information in an authority management column;

or selecting 'authority management' from menu options of public accounts, triggering to enter an 'authority management' interface, and modifying the management term information in an authority management column;

or in the public account, clicking a voice button and saying that the permission duration of XX is changed to be N days by WeChat, N represents the number of days, XX represents the Xiaoyu, or a word command that the permission duration of XX is changed to be N days modifies the management deadline information.

Further, as shown in fig. 15, the xiao will assign the administrative authority of the home computer, air conditioner, tv, etc. to their father. The specific process is as follows: finding the father of the user on the social application interface, opening the interface, and triggering to select a plurality of M2M devices to be added from public numbers related to the connected devices by pressing the option of 'adding contact authority' for a long time. And the father of Xiaoming receives the management authority information sent by the Xiaoming and clicks the management authority information corresponding to each M2M device or receives the management authority information corresponding to all the M2M devices in batches, so that the management authority of a plurality of devices in the house is obtained immediately.

Further, as shown in fig. 16, the inventor wants to assign the management authorities of the home computer, the air conditioner, the television, and the like to their father together. The specific process is as follows: finding the father of the user on the social application interface, opening the interface, and triggering to select a plurality of M2M devices to be added from My devices by pressing the contact authority option for a long time. And the father receives the management authority information sent by the Xiaoming and clicks the management authority information corresponding to each M2M device or receives the management authority information corresponding to all the M2M devices in batches, and then acquires the management authority of a plurality of devices at home.

In the embodiment of the specific application scenario, the management authority of the M2M device is distributed, the authority limit is modified, the management authority is cancelled, and the management authorities of the M2M devices are distributed, so that the user experience is effectively improved.

To facilitate a better understanding of the above-described related methods of embodiments of the present invention, the following also provides related apparatus for cooperating with the above-described methods.

Referring to fig. 17, an embodiment of a user equipment 1700 according to an embodiment of the present invention includes: an acquisition module 1701 and a sending module 1702.

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

a sending module 1702, configured to send a management authority allocation request of the M2M device to a server according to the specified application identifier corresponding to the second user device obtained by the obtaining module 1701, the management authority allocation request is used for instructing the server to send a management request of the M2M device to the second user device, the management request is used for instructing the second user equipment to send a binding request of the M2M device to the server, 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 transmitting binding confirmation information to the second user equipment, the binding confirmation information indicating that the second user equipment has the second management authority of the M2M device, the binding request includes a specific application identifier corresponding to the second user equipment and an identifier corresponding to the M2M device.

In this embodiment of the present invention, a sending module sends a management authority allocation request of an M2M device to a server, where the management authority allocation request is used to instruct the server to send a management request of the M2M device to a second user device, and the management request is used to instruct the second user device 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 device and an identifier corresponding to the M2M device, and further, the server binds the specified application identifier corresponding to the second user device and the identifier corresponding to the M2M device, so that the second user device has the second management authority of the M2M device, and thus, multiple user devices all have the management authority of the M2M device, and user experience is improved.

With continuing reference to fig. 17 on the basis of the embodiment shown in fig. 17, another embodiment of the ue in the embodiment of the present invention includes: the device comprises an acquisition module and a sending module.

The acquiring module and the sending module can refer to the acquiring module and the sending module in the embodiment of fig. 17.

Further, the management authority allocation request and the management request both include a specified application identifier of the second user equipment, an identifier corresponding to the M2M device, device management information, device binding credential information, and a specified application identifier corresponding to the first user equipment;

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

In some optional embodiments, the deleting module is configured to delete the second management permission of the second user equipment to the M2M device before the sending module sends the request for canceling the management permission to the server, and includes any one of the following manners:

or,

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

or,

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

in some optional embodiments, the user equipment further comprises: a selecting module, configured to select the M2M device before the obtaining module obtains the specified application identifier corresponding to the second user equipment;

In this embodiment of the present invention, a sending module sends a management authority allocation request of an M2M device to a server, where the management authority allocation request is used to instruct the server to send a management request of the M2M device to a second user device, and the management request is used to instruct the second user device 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 device and an identifier corresponding to the M2M device, and then the server binds the specified application identifier corresponding to the second user device and the identifier corresponding to the M2M device, so that the second user device has the second management authority of the M2M device, thereby implementing that a plurality of user devices all have the management authority of the M2M device, and improving user experience. In addition, the sending module sends an authority limit modification request or a management authority cancellation request to the server, and then the server modifies the authority limit information or modifies the authority limit information, so that the modification of the authority limit and the cancellation of the management authority are realized, and the user experience is effectively improved.

Referring to fig. 18, based on the embodiment shown in fig. 17, an embodiment of the server 1800 according to 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 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, and at least one of the M2M devices is provided;

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

the receiving module 1801 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 1803, 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 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, a management authority allocation request of an M2M device sent by a first user device is received, a sending module sends a management request of the M2M device to a second user device according to the management authority allocation request, where the management request is used to instruct the second user device to send a binding request of the M2M device to a server, and the binding request includes a designated application identifier corresponding to the second user device and an identifier corresponding to the M2M device, and then the binding module binds the designated application identifier corresponding to the second user device and the identifier corresponding to the M2M device, so that the second user device has a second management authority of the M2M device, thereby implementing that a plurality of user devices all have the management authority of the M2M device, and improving user experience.

With further reference to fig. 18 on the basis of the embodiment shown in fig. 18, another embodiment of the server according to the embodiment of the present invention includes: the device comprises a receiving module, a sending module and a binding module.

The receiving module, the sending module and the binding module can refer to the receiving module, the sending module and the binding module in the embodiment shown in fig. 18.

The management authority allocation request and the management request both include a specified application identifier corresponding to the second user equipment, an identifier corresponding to the M2M device, device management information, device 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.

The management authority allocation request further includes authority limit information corresponding to the second management authority, and the server further includes:

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

In the embodiment of the present invention, a receiving module receives a management authority allocation request of an M2M device sent by a first application device, a sending module sends a management request of the M2M device to a second user device according to the management authority allocation request, where the management request is used to instruct the second user device to send a binding request of the M2M device to a server, and the binding request includes a designated application identifier corresponding to the second user device and an identifier corresponding to the M2M device, and then the binding module binds the designated application identifier corresponding to the second user device and the identifier corresponding to the M2M device, so that the second user device has a second management authority of the M2M device, thereby implementing that a plurality of user devices all have the management authority of the M2M device, and improving user experience. In addition, the modification module modifies the authority limit information or modifies the authority limit information, so that the modification of the authority limit and the cancellation of the management authority are realized, and the user experience is effectively improved.

Further, referring to fig. 19, an embodiment of a system 1900 according to the present invention is shown, which includes:

user device 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 fig. 17 to 18 describe the specific structures of the user equipment and the server from the perspective of functional modules, and the following describes the specific structures of the user equipment and the server from the perspective of hardware in conjunction with the embodiment of fig. 20:

embodiments of the present invention relate to a user device and a server that may combine two or more components or may have different configurations or arrangements of components, each of which may be implemented in hardware, software, or a combination of hardware and software including one or more signal processing and/or application specific integrated circuits.

Referring 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, where the transceiver 2001, the memory 2002 and the processor 2003 are connected to the bus 2004, where:

the transceiver 2001 is used for receiving or transmitting data;

the memory 2002 is used for storing programs;

the processor 2003 is configured to invoke the program to perform the following operations:

and 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 the application logged on the second user equipment.

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

sending a management authority distribution request of the M2M device to a server according to the designated application identifier corresponding to the second user device;

receiving a management authority allocation request of an M2M device;

sending a management request of the M2M device to a second user device according to the management authority allocation request;

and receiving the binding request sent by the second user equipment.

Processor 2003 is also configured to perform the following operations:

and binding the specified application identifier corresponding to the second user equipment with the identifier corresponding to the M2M equipment 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, wherein the binding confirmation information is used for indicating that the second user equipment has the second management authority of the M2M device.

It should be noted that, in the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments. For example, the portions that are not described in detail in the embodiment shown in fig. 20 may be referred to the related description of the embodiments shown in fig. 3 to 6 or fig. 17 to 18.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, a division of a unit is merely a logical division, and an actual implementation may have another division, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

Units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

Claims

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

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;

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:

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

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:

or,

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:

or,

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;

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;

9. The method of claim 8, further comprising:

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:

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

12. A user device, comprising:

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;

13. The user equipment of claim 12,

14. The user equipment of claim 13,

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

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

or,

17. The user equipment of claim 16,

or,

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

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;

20. The server according to claim 19,

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:

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

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.