AUTOMATIC PROVISIONING OF AN M2M DEVICE HAVING A WIFI INTERFACE

• US 20130094444A1
• Filed: 10/12/2012
• Published: 04/18/2013
• Est. Priority Date: 10/13/2011
• Status: Abandoned Application

• Current Assignee: Applied Communication Sciences (Perspecta, Inc.)
• Original Assignee: Applied Communication Sciences (Perspecta, Inc.)
• Inventors: Lai, Ming-Yee, Chee, Dana, Makaya, Christian, Lin, Fuchun Joseph, Hori, Kenji, Yoshihara, Kiyohito
• Application Number:
  US13/650,701
• Publication Number:
  US 20130094444A1
• Time in Patent Office: Days
• US Class Current: 370/328
• 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]
• CPC Class Codes: H04W 8/02 Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
• CPC Class Codes: H04W 8/265 for initial activation of new user
• CPC Class Codes: H04W 84/18 Self-organising networks, e.g. ad-hoc networks or sensor networks

Abstract

A method for automatically provisioning a WiFi-equipped machine-to-machine (M2M) device is disclosed. A WiFi M2M gateway identifies a WiFi network identifier broadcast by a powered-on M2M device in WiFi ad hoc mode through a scanning procedure and joins the ad hoc network defined by the M2M device. The WiFi M2M gateway obtains device information (e.g., MAC address) of the M2M device. The WiFi M2M gateway transmits a command to the M2M device to switch from ad hoc mode to infrastructure mode. The WiFi M2M gateway registers the M2M device with an M2M server associated with a service provider based on the device information of the M2M device. The WiFi M2M gateway receives a fully qualified domain name (FQDN) associated with the M2M device from the M2M server.

Claims

1. A computer-implemented method for automatically provisioning a machine-to-machine (M2M) device, comprising the steps of:

identifying, by a scanning procedure of a WiFi M2M gateway, a WiFi network identifier being broadcast by a M2M device initially set in an ad hoc mode;

joining a WiFi ad hoc network set by the M2M device;

obtaining device information from the M2M device over a WiFi connection;

transmitting a command to the M2M device to switch from the ad hoc mode to an infrastructure mode;

storing the device information of the M2M device in a gateway device database (GDD);

registering the M2M device with an M2M server associated with a service provider based on the device information; and

receiving a fully qualified domain name (FQDN) associated with the M2M device from the M2M server.

2. The method of claim 1, wherein the WiFi M2M gateway maintains at least one other connection in ad hoc mode after switching the M2M device from ad hoc mode to infrastructure mode when provisioning new M2M devices and servicing provisioned M2M devices concurrently in the same gateway area is required.

3. The method of claim 1, wherein the obtaining device information is at least one of a name, an IP address, and a MAC address of the M2M device.

4. The method of claim 3, wherein the name is employed when the M2M device includes a Web server to enable remote access to the M2M device via a Web client.

5. The method of claim 3, wherein the name is a user login name, a password, or both.

6. The method of claim 3, wherein the IP address is in one of IPv4 format or IPv6 format.

7. The method of claim 1, wherein registering the M2M device with an M2M server associated with a service provider based on the device information of the M2M device comprises creating a Device Management (DM) message with the device information of the M2M device as a payload and transmitting the DM message to the M2M server.

8. The method of claim 1, wherein the device information is stored in the GDD during provisioning time to facilitate a fast response for at least one of retrieving or updating device information in a gateway area.

9. A computer-implemented method for automatically provisioning a machine-to-machine (M2M) device, comprising the steps of:

receiving, by a M2M server associated with a service provider, device information of an M2M device from a WiFi M2M gateway;

registering the device information in a server device database (SDD);

transmitting a message with the device information of the M2M device as a payload to a domain name server (DNS);

receiving a fully qualified domain name (FDQN) associated with the M2M device from the DNS; and

transmitting the FDQN to the WiFi M2M gateway.

10. The method of claim 9, further comprising provisioning a special DNS record for NAT tunneling in the DNS for obtaining the FQDN to enable communication with a M2M device behind a CPE gateway with network address translation (NAT).

11. The method of claim 9, further comprising provisioning a regular record in the DNS to map the FQDN for a M2M device without network address translation (NAT).

12. The method of claim 9, wherein the device information stored in the SDD at the service provider network during provisioning time is kept in sync with that in the GDD, which is used to facilitate a fast response for at least one of retrieving or updating device information in a gateway area.

13. A computer system, comprising:

a memory;

a processing device, coupled to the memory; and

an operating system hosted by the computer system, having access to the memory and use of the processor, the operating system configured to;

identify, by a scanning procedure, a WiFi network identifier being broadcast by a M2M device initially set in an ad hoc mode;

join a WiFi ad hoc network set by the M2M device;

obtain device information from the M2M device over a WiFi connection;

transmit a command to the M2M device to switch from the ad hoc mode to an infrastructure mode;

store the device information of the M2M device in a gateway device database (GDD);

register the M2M device with an M2M server associated with a service provider based on the device information; and

receive a fully qualified domain name (FQDN) associated with the M2M device from the M2M server.

14. The system of claim 13, wherein the operating system maintains at least one other connection in ad hoc mode after switching the M2M device from ad hoc mode to infrastructure mode when provisioning new M2M devices and servicing provisioned M2M devices concurrently in the same gateway area is required.

15. The system of claim 13, wherein the device information is stored in the GDD during provisioning time to facilitate a fast response for at least one of retrieving or updating device information in a gateway area.

16. A computer system, comprising:

a memory;

a processing device, coupled to the memory; and

an operating system hosted by the computer system, having access to the memory and use of the processor, the operating system configured to;

receive device information of an M2M device from a WiFi M2M gateway;

register the device information in a server device database (SDD);

transmit a message with the device information as a payload to a domain name server (DNS);

receive a fully qualified domain name (FDQN) associated with the M2M device from the DNS; and

transmit the FDQN to the WiFi M2M gateway.

17. The system of claim 16, further comprising provisioning a special DNS record for NAT tunneling in the DNS for obtaining the FQDN to enable communication with a M2M device behind a CPE gateway with network address translation (NAT).

18. The system of claim 16, further comprising provisioning a regular record in the DNS to map the FQDN for a M2M device without network address translation (NAT).

19. The system of claim 16, wherein the device information stored in the SDD during provisioning time is kept sync with that in the GDD, which is used to facilitate a fast response for at least one of retrieving or updating device information in a gateway area.