Predictive battery warnings for an electronic locking device
US-2016116510-A1 · Apr 28, 2016 · US
US2016156604A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2016156604-A1 |
| Application number | US-201514887972-A |
| Country | US |
| Kind code | A1 |
| Filing date | Oct 20, 2015 |
| Priority date | Dec 1, 2014 |
| Publication date | Jun 2, 2016 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A method of managing a device is provided. The method includes registering execution authorization information regarding a function provided by a first device, receiving a request for determining whether a second device that requests execution of a function provided by the cloud server has authorization to perform the function provided by the first device from the first device, authenticating whether the second device has authorization for performing a function provided by the first device, and transmitting a result of the authentication to the first device.
Opening claim text (preview).
What is claimed is: 1 . A method, performed by a cloud server, of managing a device, the method comprising: registering execution authorization information regarding a function provided by a first device; receiving from the first device, a request for determining whether a second device that requests execution of the function provided by the first device has authorization to perform the function provided by the first device; authenticating whether the second device has the authorization to perform the function provided by the first device; and transmitting a result of the authentication to the first device. 2 . The method of claim 1 , wherein, in the receiving of the request, authentication information regarding the second device, which is received by the first device from the second device, is also received by the cloud server. 3 . The method of claim 1 , wherein the first device provides a plurality of functions, and wherein a function selected by the second device from among the plurality of functions provided by the first device is authenticated. 4 . The method of claim 1 , wherein the authenticating comprises: transmitting, if the second device has no authorization to perform the function provided by the first device, an authorization determination request to a device of an administrator of the first device; and receiving an authentication determination result from the device of the administrator of the cloud server. 5 . The method of claim 1 , wherein the authenticating of whether the second device has the authorization to perform the function provided by the first device comprises determining whether the second device has authorization to perform the function provided by the first device by comparing authentication information regarding the second device included in the received authentication request to the registered execution authorization information regarding the first device. 6 . The method of claim 5 , further comprising: deleting, if it is determined that the second device has authorization to perform the function provided by the first device, information corresponding to the authentication information regarding the second device in the registered execution authorization information regarding the first device. 7 . The method of claim 1 , further comprising: receiving an input of an administrator of the first device and deleting the registered execution authorization information regarding the first device. 8 . The method of claim 1 , wherein the registering of the execution authorization information regarding the first device comprises: receiving execution authorization information and access information regarding the first device; determining whether to register the received execution authorization information based on the access information; and registering the execution authorization information based on a result of the determination. 9 . A cloud server comprising: a controller configured to register execution authorization information regarding a first device; and a communication unit configured to: receive, from the first device, a request for authenticating whether a second device that requests execution of a function provided by the first device has authorization to perform the function provided by the first device, and transmit a result of the authentication to the first device. 10 . The cloud server of claim 9 , wherein the communication unit is further configured to receive authentication information regarding the second device received by the first device from the second device. 11 . The cloud server of claim 9 , wherein the first device provides a plurality of functions, and wherein the controller is further configured to authenticate a function selected by the second device from among the plurality of functions provided by the first device. 12 . The cloud server of claim 9 , wherein, if the second device has no authorization to perform the function provided by the first device, the controller is further configured to control transmission of an authorization determination request to a device of an administrator of the first device, and wherein the communication unit is further configured to receive an authentication determination result from the device of the administrator of the cloud server. 13 . The cloud server of claim 9 , wherein the controller is further configured to determine whether the second device has authorization to perform the function provided by the first device by comparing authentication information regarding the second device included in the received authentication request to the registered execution authorization information regarding the first device. 14 . The cloud server of claim 13 , wherein, if it is determined that the second device has authorization to perform the function provided by the first device, the controller is further configured to delete information corresponding to the authentication information regarding the second device in the registered execution authorization information regarding the first device. 15 . The cloud server of claim 9 , wherein the controller is further configured to: receive an input of an administrator of the first device, and delete the registered execution authorization information regarding the first device. 16 . The cloud server of claim 9 , wherein the controller is further configured to: receive execution authorization information and access information regarding the first device, determine whether to register the received execution authorization information based on the access information, and register the execution authorization information based on a result of the determination. 17 . At least one non-transitory computer-readable recording medium for storing a computer program configured to be readable by at least one processor for instructing the at least one processor to execute a computer process for performing the method of claim 1 .
Access control comprising means for the enrolment of users · CPC title
for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32) · CPC title
With time considerations, e.g. temporary activation, valid time window or time limitations · CPC title
operated by interacting with a central unit · CPC title
Access control lists [ACL] · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.