Transferable ownership tokens for discrete, identifiable devices
A mobile device that includes an ownership token application program receives user input indicative of a first authentication factor associated with an ownership token bound to an Internet of Things (IoT) device. Responsive to detecting the IoT device in close proximity, the mobile device may obtain a second authentication factor and an IoT device identifier from the IoT device. The mobile device may then provide the obtained factors as authenticating credentials to a token server via a trust application program interface (API). After the server authenticates the mobile device, the server may send the token to the mobile device thereby transferring ownership rights, including access rights, to recipient. The application program and/or the trust API may be configured for one-time access wherein, after the token has been transferred to the mobile device. The discrete electronic device may comprise an Internet of Things (IoT device) that supports wireless, near field communication.
1. A mobile device, comprising:
a central processing unit (CPU);
a mobile communication module; and
a non-transitory computer readable medium, comprising processor executable program instructions for an ownership token application that, when executed, causes the CPU to perform operations comprising:
responsive to receiving user input indicative of a first authentication factor associated with an ownership token bound to an Internet of Things (IoT) device, configuring the mobile device to participate in a wireless, near field transfer of authentication data from the IoT device to the mobile device;
responding to a trigger event by receiving, from the IoT device, additional authentication data associated with the ownership token, wherein the trigger event occurs when the mobile device and the IoT device are brought into close proximity and wherein the additional authentication information includes a second authentication factor and an IoT identifier associated with the ownership token;
providing, to a server communicatively coupled to an ownership token database, authentication credentials to authenticate the mobile device to the server, wherein the authentication credentials include the first authentication factor, the second authentication factor, and the IoT identifier; and
receiving the ownership token from the server.
2. The mobile device of claim 1 , wherein the providing of authentication credentials to authenticate the mobile device comprises establishing communication with the server via an application programming interface (API) exposed to the mobile device by the server.
3. The mobile device of claim 2 , wherein the API is unavailable to the ownership token application after the mobile device receives the ownership token.
4. The mobile device of claim 1 , wherein the IoT device comprises: an embedded controller, a wireless transceiver, and non-volatile storage sufficient to store the IoT identifier.
5. The mobile device of claim 4 , wherein the wireless transceiver comprises a near field communication transceiver.
6. The mobile device of claim 1 , wherein the ownership token enables the mobile device to gain access to configuration settings, communication resources, and input/output (I/O) ports of the IoT device.
7. A method, comprising:
responsive to receiving, by an ownership token application program of a mobile device, user input indicative of a first authentication factor associated with an ownership token bound to an Internet of Things (IoT) device, configuring the mobile device to participate in a wireless, near field transfer of authentication data from the IoT device to the mobile device;
responding to a trigger event by receiving, from the IoT device, additional authentication data associated with the ownership token, wherein the trigger event occurs when the mobile device and the IoT device are brought into close proximity and wherein the additional authentication data includes a second authentication factor and an IoT identifier associated with the device ownership token;
providing, to a server communicatively coupled to an ownership token database, authentication credentials to authenticate the mobile device to the server, wherein the authentication credentials include the first authentication factor, the second authentication factor, and the IoT identifier; and
receiving the ownership token from the server.
8. The method of claim 7 , wherein the providing of authentication credentials to authenticate the mobile device comprises establishing communication with the server via an application programming interface (API) exposed to the mobile device by the server.
9. The method of claim 8 , wherein the API is unavailable to the mobile device after the mobile device receives the ownership token.
10. The method of claim 7 , wherein the IoT device includes: an embedded controller, a wireless transceiver, and non-volatile storage sufficient to store a device identifier.
11. The method of claim 10 , wherein the wireless transceiver comprises a near field communication transceiver.
12. The method of claim 7 , wherein the IoT device comprises a device selected from: a home router and a digital camera.
13. The method of claim 7 , wherein the ownership token enables the mobile device to gain access to configuration settings, communication resources, and I/O ports of the IoT device.
14. A non-transitory computer readable medium, including processor executable program instructions, wherein the instructions, when executed, cause a processor to perform operations, wherein the operations comprise:
responsive to receiving, from a mobile device, user input indicative of a first authentication factor associated with an ownership token bound to an Internet of Things (IoT) device, configuring the mobile device to participate in a wireless, near field transfer of additional authentication data from the IoT device to the mobile device;
responding to a trigger event by receiving, from the IoT device, the additional authentication data, wherein the trigger event occurs when the mobile device and the IoT device brought into close proximity and wherein the additional authentication data includes a second authentication factor and an IoT identifier associated with the ownership token;
providing, to a server communicatively coupled to an ownership token database, authentication credentials to authenticate the mobile device to the server, wherein the authentication credentials include the first authentication factor, the second authentication factor, and the IoT identifier; and
receiving the ownership token from the server.
15. The non-transitory computer readable medium of claim 14 , wherein the providing of authentication credentials to authenticate the mobile device comprises establishing communication with the server via an application programming interface (API) exposed to the mobile device by the server.
16. The non-transitory computer readable medium of claim 15 , wherein the API comprises a single use API, wherein the single use API becomes unavailable to the mobile device after the ownership token is successfully transferred to the mobile device.
17. The non-transitory computer readable medium of claim 14 , wherein the IoT device comprises: an embedded controller, a wireless transceiver, and non-volatile storage sufficient to store the IoT identifier and wherein the wireless transceiver comprises a near field communication transceiver.
18. The non-transitory computer readable medium of claim 14 , wherein the ownership token enables the mobile device to gain access to configuration settings, communication resources, and input/output (I/O) ports of the IoT device.
19. The non-transitory computer readable medium of claim 14 , wherein the trigger event occurs when the mobile device is tapped against the IoT device.
20. The non-transitory computer readable medium of claim 14 , wherein the trigger event occurs when the mobile device is brought into near field proximity with to the IoT device.