TECHNIQUES FOR THE DEPLOYMENT AND MANAGEMENT OF NETWORK CONNECTED DEVICES

• US 20160087933A1
• Filed: 12/01/2015
• Published: 03/24/2016
• Est. Priority Date: 09/25/2006
• Status: Active Grant

• Current Assignee: remot3.it, Inc.
• Original Assignee: Weaved, Inc.
• Inventors: Johnson, Michael W., Koyama, Ryo, Smith, Michael J.S.
• Granted Patent: US 9,712,486 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/9566 URL specific, e.g. using aliases, detecting broken or misspelled links
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: H04L 2101/345 containing wildcard characters
• CPC Class Codes: H04L 2101/35 containing special prefixes
• CPC Class Codes: H04L 2101/604 Address structures or formats
• CPC Class Codes: H04L 41/08 Configuration management of networks or network elements address allocation H04L61/50
• CPC Class Codes: H04L 41/0803 Configuration setting
• CPC Class Codes: H04L 47/125 by balancing the load, e.g. traffic engineering
• CPC Class Codes: H04L 61/301 Name conversion
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 61/4555 Directories for electronic mail or instant messaging
• CPC Class Codes: H04L 63/0281 Proxies
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/105 Multiple levels of security
• CPC Class Codes: H04L 67/025 for remote control or remote monitoring of applications
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04W 12/02 Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
• CPC Class Codes: H04W 12/35 Protecting application or service provisioning, e.g. securing SIM application provisioning
• CPC Class Codes: H04W 12/50 : Secure pairing of devices
• CPC Class Codes: H04W 4/50 : Service provisioning or reconfiguring
• CPC Class Codes: H04W 4/70 : Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Abstract

A method, system, and computer program product for Internet of Things (IoT) network-connected devices. Embodiments include methods and systems for registering one or more listener devices (e.g., mobile phones or tablets, etc.) to receive messages from one or more notification devices (e.g., web cameras, etc.). A notification server is selected from among multiple notification servers to receive notification messages from the notification devices and then to forward (e.g., through a push service, etc.) portions of or variations of the notification messages to the listener devices. In some embodiments, the selection of the notification server is based on load balancing between the multiple notification servers and/or push servers. In some embodiments, the selection of a notification server and/or push server is based on a provisioning file.

Claims

1. A method comprising:

receiving, using a network, a message from a first device connected to the network, wherein the message comprises a first URL containing a fractional subdomain portion in a fractional subdomain position;

parsing the fractional subdomain portion into a plurality of tokens comprising at least a first token and a second token;

generating a second URL, wherein the second URL comprises at least one wildcard character in the fractional subdomain position and at least one of the plurality of tokens in the fractional subdomain position;

using the second URL to configure the first device by establishing a connection between a first computing platform and the first device;

communicating one or more messages over the connection wherein at least a portion of the one or more messages comprise a provisioning file;

authenticating at least one aspect of the provisioning file;

decrypting at least one aspect of the provisioning file;

receiving from the first device a first URL comprising a first top level domain, a first domain name, and at least one first subdomain; and

mapping the first URL to a second URL comprising a second top level domain, a second domain name, and at least one second subdomain, wherein the second URL is associated with a set of one or more target devices and the second URL is different than the first URL

selecting a notification server from a plurality of notification servers to receive a notification message that is sent from the first device;

registering at least one notification device to receive messages from the notification server;

receiving the notification message at the notification server; and

forwarding the notification message from the notification server to the notification device.

2. The method of claim 1, further comprising:

presenting a user interface on a display terminal, wherein the user interface includes one or more first fields for user entry of a first device type, and wherein the user interface includes one or more second fields for user entry of a second device type;

recognizing the first device type to associate one or more aspects of the first device type;

configuring a domain name service server using at least one aspect of the first device type;

recognizing the second device type to associate one or more aspects of the second device type; and

configuring the domain name service server using at least one aspect of the second device type, wherein the domain name service server is operable to initiate network communication between a first device instance of a device of the first device type and a second device instance of a device of the second device type.

3. The method of claim 1, further comprising:

determining a routing of at least one notification message to load balance at least some of the plurality of notification servers.

4. The method of claim 1, further comprising:

creating an internet connection between the first device and the set of one or more target devices, wherein the internet connection enables the first device and the set of one or more target devices to exchange information.

5. The method of claim 1, wherein the first top level domain is formed as portion1.portion2.

6. The method of claim 5 wherein the portion2 is at least one of, “

com”

, “

net”

, “

tv”

, and “

co”

.

7. The method of claim 5 wherein the portion1 is formed as subportion1.subportion2.

8. The method of claim 7 wherein the subportion1 or the subportion2 is a company name.

9. The method of claim 7 wherein the subportion1 or the subportion2 is automatically generated.

10. The method of claim 1, wherein the first device is associated with a user.

11. The method of claim 1, wherein an address associated with the first device is unknown.

12. The method of claim 1, further comprising linking the first device to an account.

13. The method of claim 12, wherein the account is associated with a service.

14. The method of claim 13, further comprising re-configuring the first device utilizing the service.

15. The method of claim 13, wherein the service performs communication with the first device without processing an Internet Protocol (IP) address associated with the first device.

16. The method of claim 13, further comprising identifying the first device connected to the network utilizing a unique identifier associated with the device.

17. The method of claim 13, wherein communication between the service and device includes a protocol that updates configuration information of the first device.

18. The method of claim 13, wherein the first device is re-configured using an interface associated with the service.

19. The method of claim 18, wherein a website associated with the service includes the interface.

20. The method of claim 1, wherein the one or more messages comprises two or more portions.