Gateway using resource directory
A system and method for allowing legacy devices to be discovered on a DotDot network is disclosed. The system includes a gateway device to interface between DotDot devices and legacy devices. In some embodiments, the gateway device has a plurality of network interfaces to communicate with these legacy devices. The gateway device discovers the legacy devices that it can communicate with. The gateway device then presents information about these legacy devices in a Resource Directory. In some embodiments, the Resource Directory is maintained within the gateway device. In other embodiments, the gateway device utilizes a Resource Directory that exists on the DotDot network.
1. A gateway device, comprising:
a DotDot network interface in communication with a DotDot network;
a secondary network interface;
a processing unit and a memory device, where the memory device comprises instructions, which when executed by the processing unit, allow the gateway device to:
create a virtual device, the virtual device having a different IPv6 address than the gateway;
communicate with a legacy sleepy device on the secondary network interface;
obtain data from the legacy sleepy device; and
post the data from the legacy sleepy device in a Resource Directory, wherein the Resource Directory is a mechanism defined by CoAP (Constrained Application Protocol) to allow for discovery of devices on the DotDot network, and
wherein the Resource Directory is disposed on the virtual device.
2. The gateway device of claim 1 , wherein a plurality of legacy sleepy devices is accessible via the secondary network interface, and the gateway device posts data from each of the plurality of the legacy sleepy devices in the Resource Directory.
3. The gateway device of claim 1 , wherein the gateway device obtains updated data from the legacy sleepy device and updates the data in the Resource Directory.
4. The gateway device of claim 1 , further comprising instructions, which when executed by the processing unit, allow the gateway device to:
store the data in a format that is defined for a Resource Directory.
5. A gateway device, comprising:
a DotDot network interface in communication with a DotDot network;
a secondary network interface;
a processing unit and a memory device, where the memory device comprises instructions, which when executed by the processing unit, allow the gateway device to:
create a virtual device, the virtual device having a different IPv6 address than the gateway;
indicate to DotDot devices via the DotDot interface that a Resource Directory is disposed on the virtual device, wherein the Resource Directory is a mechanism defined by CoAP (Constrained Application Protocol) to allow for discovery of devices on the DotDot network;
receive data from a legacy sleepy device on the secondary network interface; and
return the data from the legacy sleepy device to a DotDot device in response to a query of the Resource Directory.
6. The gateway device of claim 5 , wherein the secondary network utilizes a ZIGBEE® protocol.
7. The gateway device of claim 1 , wherein the secondary network utilizes a ZIGBEE® protocol.
8. The gateway device of claim 5 , wherein the gateway device stores the data received from the legacy sleepy device in the Resource Directory.
9. The gateway device of claim 8 , wherein a plurality of legacy sleepy devices is accessible via the secondary network interface, and the gateway device stores data from each of the plurality of the legacy sleepy devices in the Resource Directory.
10. The gateway device of claim 5 , wherein the gateway device receives updated data from the legacy sleepy device and updates the data in the Resource Directory.
11. The gateway device of claim 5 , further comprising instructions, which when executed by the processing unit, allow the gateway device to:
store the data in a format that is defined for a Resource Directory.