IP Library Granted Patent US 9,584,482
Granted Patent B2
US 9,584,482 · App. 14/636,926 · Granted Feb 28, 2017

Access control lists for private networks of system agnostic connected devices

Inventors: Gregory Burns (Seattle, WA); Joshua Dickenson Hershberg (Beit Shemesh, IL); Phil Tien Nguyen (San Diego, CA); Fruma Adina Geffen (Beit Shemesh, IL)
Assignee: Qualcomm Connected Experiences, Inc.
H04L63/0272G06F21/629H04L12/6418H04L12/66H04L63/101H04L67/12G06F8/61G06F2221/2141H04L63/108H04W84/22
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,584,482
App. No.
14/636,926
Granted
Feb 28, 2017
Kind
B2
Abstract

The disclosure relates to using a control service to control external access to APIs of IoT devices on a private network. An external application can request access to an API, and in response, the control service can monitor broadcasts from the IoT devices indicating what APIs they have available. If a match exists, the control service can request user authorization to allow the requested access. The user can grant or deny the requested access, and place limitations on the authorized access. The control service uses this information to open a connection between the requesting application and the IoT device having the requested API, and via this connection, the requesting application can access and control the device running the requested API.

Claims (35)

1. A system for securing access to internet-of-things (IoT) devices on a private network, the system comprising:

a first IoT device on a private network having one or more APIs;

a gateway device coupled to the private network and to a public network and configured to receive API requests over the public network;

one or more IoT services on the gateway device for managing the API requests;

a control service on the gateway device for matching one of the one or more APIs on the first IoT device with the one or more APIs requested by the IoT service; and

a configuration module configured to prompt a user to allow the one or more IoT services to have access to the one of the one or more APIs on the first IoT device, and upon authorization from the user, allowing authorized IoT services to access the API, and where the user does not provide authorization, then precluding a denied IoT service from accessing the API, wherein the configuration module is further configured to prompt the user to allow the IoT service to have access to a new API that becomes available on a second IoT device that joins the private network or that becomes available on the first IoT device.

2. The system of claim 1 , wherein the control service is distributed between the gateway device and a user device, the user device being on the public network.

3. The system of claim 1 , wherein the gateway device is an access point between the private and public networks.

4. The system of claim 1 , wherein the gateway device is distinct from an access point between the private and public networks.

5. The system of claim 1 , wherein the control service is on the public network and the configuration module is on the private network.

6. The system of claim 1 , wherein one of the one or more IoT services provides access to the first IoT device for an IoT control application on the public network.

7. A method for securing access to internet-of-things (IoT) devices on a private network, the method comprising:

precluding access to a private network;

receiving a request to access an API on the private network from an IoT service on a public network;

determining matches between the API requested by the IoT service and available APIs on IoT devices on the private network;

prompting a user to allow the IoT service to have access to the APIs on the IoT devices that are the same as the API requested by the IoT service and upon receiving authorization from the user, allowing the IoT service to access the APIs, and where the user does not provide authorization, then precluding a denied IoT service from accessing the APIs on the IoT devices that are the same as the API requested by the IoT service; and

prompting the user to allow the IoT service to have access to a new API that becomes available on a new IoT device that joins the private network.

8. The method of claim 7 , wherein, the IoT service makes the request from a gateway device coupled between the private and public networks.

9. The method of claim 7 , wherein, the IoT service makes the request from a user device on the private network.

10. The method of claim 7 , wherein, the IoT service makes the request from one of the IoT devices on the private network.

11. The method of claim 7 , further comprising, when there is more than one match between the available APIs and the API requested by the IoT service, prompting the user to select one or more of the available APIs matching the requested API.

12. A system for securing access to internet-of-things (IoT) devices on a private network, the system comprising:

means for precluding access to a private network;

means for receiving a request to access an API on the private network from an IoT service on a public network;

means for determining matches between the API requested by the IoT service and available APIs on IoT devices on the private network; and

means for prompting a user to allow the IoT service to have access to the APIs on the IoT devices that are the same as the API requested by the IoT service and upon receiving authorization from the user, allowing the IoT service to access the APIs, and where the user does not provide authorization, then precluding a denied IoT service from accessing the APIs on the IoT devices that are the same as the API requested by the IoT service; and

means for prompting the user to allow the IoT service to have access to a new API that becomes available on a new IoT device that joins the private network.

13. The system of claim 7 , wherein, the IoT service makes the request from a gateway device coupled between the private and public networks.

14. The system of claim 7 , wherein, the IoT service makes the request from a user device on the private network.

15. The system of claim 7 , wherein, the IoT service makes the request from one of the IoT devices on the private network.

16. The system of claim 7 , further comprising, when there is more than one match between the available APIs and the API requested by the IoT service, prompting the user to select one or more of the available APIs matching the requested API.

17. The system of claim 1 , wherein the configuration application is further configured to request and receive authorization from a user to allow the IoT service to have access to the first IoT device for a period of time selected by the user.

18. The system of claim 17 , wherein the authorization includes one or more recurring, but limited, periods of time.

19. The method of claim 7 , further comprising requesting and receiving authorization from a user to allow the IoT service to have access to the APIs on the IoT devices that are the same as the API requested by the IoT service for a period of time selected by the user.

20. The method of claim 19 , wherein the authorization includes one or more recurring, but limited, periods of time.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 19, 2016
From: BURNS, GREGORY; HERSHBERG, JOSHUA DICKENSON; NGUYEN, PHIL TIEN; GEFFEN, FRUMA ADINA
To: QUALCOMM CONNECTED EXPERIENCES, INC.
Reel/Frame 038312/0719 →
Continuity (3)
Provisional Application 61947408 · Mar 3, 2014
Provisional Application 62026024 · Jul 17, 2014
Related Publication 20150249672A1 · Sep 3, 2015