SYSTEMS AND METHODS FOR PROVIDING IOT SERVICES

• US 20160205106A1
• Filed: 01/12/2015
• Published: 07/14/2016
• Est. Priority Date: 01/12/2015
• Status: Abandoned Application

• Current Assignee: VeriSign, Inc.
• Original Assignee: VeriSign, Inc.
• Inventors: Yacoub, Souheil Ben, Piccand, Regis, Schonfeld, Daniel, James, Stephen Daniel, Fregly, Andrew
• Application Number:
  US14/595,190
• Publication Number:
  US 20160205106A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 2101/35 containing special prefixes
• CPC Class Codes: H04L 51/046 Interoperability with other network applications or services
• CPC Class Codes: H04L 61/3025 Domain name generation or assignment
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 61/5007 Internet protocol [IP] addresses
• CPC Class Codes: H04L 63/0442 wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30
• CPC Class Codes: H04L 63/101 Access control lists [ACL]
• CPC Class Codes: H04L 63/126 the source of the received data
• CPC Class Codes: H04L 9/3247 involving digital signatures
• CPC Class Codes: H04W 12/041 Key generation or derivation
• CPC Class Codes: H04W 12/0433 Key management protocols
• CPC Class Codes: H04W 12/108 Source integrity
• CPC Class Codes: H04W 4/70 Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Abstract

Provided is a method for subscribing to a data feed from an internet of things (“IoT”) device. The method comprises obtaining, by a subscribe application program interface (“API”) of a container, a subscription request to subscribe to the data feed from a requestor, wherein the container is operable to provide one or more services to an internet of things (“IoT”) device through one or more application programming interfaces (“APIs”), wherein subscription request is associated with data stored in one or more domain name system (“DNS”) records; determining that the subscription request is permissible based on a list of approved requestors; and providing the data feed to the requestor, wherein the requestor is another container or another IoT device.

Claims

1. A method for subscribing to a data feed from an internet of things (“

IoT”

) device, the method comprising;

obtaining, by a subscribe application program interface (“

API”

) of a container, a subscription request to subscribe to the data feed from a requestor, wherein the container is operable to provide one or more services to an internet of things (“

IoT”

) device through one or more application programming interfaces (“

APIs”

), wherein subscription request is associated with data stored in one or more domain name system (“

DNS”

) records;

determining that the subscription request is permissible based on a list of approved requestors; and

providing the data feed to the requestor, wherein the requestor is another container or another IoT device.

2. The method of claim 1, wherein the one or more services comprise a message bus service operable to receive and provide message to requestor or another requestor, a data service operable to process data received from the IoT device, a data transformer service operable to transform data from the IoT device from one state to another state, and an administrative service operable to maintain information on valid users of the data feed.

3. The method of claim 1, wherein the data feed to provided to the requestor on a predetermined schedule.

4. The method of claim 1, wherein the data feed is obtained by the requestor on a predetermined schedule.

5. A method for registering a container with a domain name system (“

DNS”

), comprising;

creating a container, wherein the container is operable to provide one or more services to an internet of things (“

IoT”

) device through one or more application programming interfaces (“

APIs”

);

providing a registration request to register the container to a registration server of the DNS, wherein the registration request comprises an unique identifier for the container; and

obtaining an internet protocol (“

IP”

) address and a domain name associated with the unique identifier for the container from the registration server.

6. The method of claim 5, wherein the one or more services comprises one or more of:

a registry server, a data service, a DNS server service, and a messaging service.

7. The method of claim 5, wherein the one or more APIs comprise an account API, a crawler API, a consume API, a publish API.

8. The method of claim 6, wherein the data service comprises one or more of:

a data transformer, a data aggregator, a data average.

9. The method of claim 5, further comprising providing a public key of an asymmetric key pair associated with the container to the DNS.

10. The method of claim 5, further comprising:

obtaining a subscription request from a requestor for a data feed managed by the container;

determining that the subscription request from the requestor is permissible based on a record of permissible requestors;

providing the data feed to the requestor.

11. The method of claim 10, wherein the requestor is another container or another IoT device.

12. The method of claim 10, further comprising obtaining a data feed from the IoT device.

13. The method of claim 7, wherein the crawler API is operable to communicate with other containers.

14. A method for subscribing to a container, the method comprising:

registering a first and a second internet of things (“

IoT”

) device with the container, wherein the container is operable to provide one or more services to the IoT device through one or more application programming interfaces (“

APIs”

);

obtaining a first data feed from the first IoT device;

obtaining a second data feed from the second IoT device;

obtaining a request for the second data feed to subscribe to the first data feed;

obtaining a subscription request from the second IoT device, wherein the subscription request is digitally signed using a private key associated with the second IoT device;

obtaining an answer to the subscription request from the first IoT device;

adding the first data feed to the second data feed based on the answer; and

obtaining a subscription acknowledgement from the first IoT.

15. The method of claim 14, further comprising providing metadata associated to the first and/or second IoT device to another container.

16. A method for creating a verified data stream, the method comprising:

generating, by an IoT device, a public/private key pair;

transforming an identifier of the IoT device into a qualified name;

providing the public key to be published in a DNSSEC secured zone under the qualified name; and

generating a data stream including a message that is digitally signed using the private key, wherein the message includes a feed identifier and a payload.

17. A method for authenticating a data stream, the method comprising:

obtaining a message from a container, wherein the message is digitally signed using a private key of an IoT device that created the message, wherein the message includes a feed identifier and a payload, and wherein the container is operable to provide one or more services to the IoT device through one or more application programming interfaces (“

APIs”

);

extracting the feed identifier from the message,

transforming the feed identifier into a device identifier;

transforming the device identifier into a qualified name;

obtaining, from a DNS record, a public key associated with the private key; and

authenticating the message using the public key.

18. A method for searching for IoT devices, the method comprising:

obtaining, at a DNS resolver from a requestor, a DNS query for an IP address of an IoT device;

determining, by the DNS resolver, that the DNS query is intended for resolution via a search engine instead of a DNS server based on a characteristic of the DNS query;

forming a search query based on the DNS query for submission to a search engine;

providing the search query to the search engine; and

creating a transient IP from which results from the search engine are retrievable by the requestor.

19. The method of claim 18, wherein the DNS resolver is a DNS stub resolver or a DNS recursive name server.

20. The method of claim 18, further comprising providing a result to the requestor, wherein the result comprises one or more DNS matching DNS records that are identified by the search engine based on a domain name of the requestor.