WO2018203301A1

WO2018203301A1 - An internet of things architecture for controlling devices and objects

Info

Publication number: WO2018203301A1
Application number: PCT/IB2018/053126
Authority: WO
Inventors: Derek Graham; Peter Manley; Durai RAMACHANDIRAN
Original assignee: ClearOne Inc
Current assignee: ClearOne Inc
Priority date: 2017-05-04
Filing date: 2018-05-04
Publication date: 2018-11-08
Anticipated expiration: 2019-11-04

Abstract

This disclosure describes a system that controls devices within the loT architecture that includes a user device (104) with a user control interface, and includes an loT device (116) with an input device (108) that allows the user device to identify, link, and control the loT device. Further included is a first linking connection (106) that links the input device of the loT device with the user device, the first linking connection includes one or more security control attributes. And the user device on linking with the loT device can discover one or more controllable attributes directly from the loT device; the user device uses an individual controllable attribute to connect to the loT device using a second linking connection with a higher communication bandwidth; the user device will automatically retrieve the remote control application from the loT device; and the user control interface controls the loT device.

Description

Title of the Invention

AN INTERNET OF THINGS ARCHITECTURE FOR CONTROLLING DEVICES AND

OBJECTS

Cross Reference To Related Applications

[01] This application claims priority and the benefits of the earlier filed Provisional Application USAN 62501648, filed 05/04/2017, which is incorporated by reference for all purposes into this specification.

Technical Field

[02] This disclosure relates to controlling devices and objects. More specifically, this disclosure relates to an Internet of Things architecture for controlling devices and objects.

Background Art

[03] Current methodologies define a manual mapping of hardware/software interfaces between a device and a control interface. More specifically, current methods to control an installed device using a mobile device require prior knowledge about how to connect to the device and how to obtain and possibly configure the software that must control it.

[04] The current methods of installed device control using a mobile app require the following knowledge and/or steps:

a. The user must know that the installed device can be controlled by an App.

b. The user must find, download, and install the app on their mobile device.

c. The user must know which wireless network to connect to for installed device control.

d The user must have the correct credentials to connect to the wireless network. e The user must launch the installed device control app and possibly initiate an installed device discovery step. f. The user must know which installed device they need to connect to, and select that device from the list of available devices.

g. The user probably needs to perform an authentication step prior to getting

access to the installed device to control it.

h. The user might need to set up control parameters in the control application to properly control a specific device.

[05] An objective of this disclosure is to enable a mobile device to control an installed device as easily as a tabletop dialer or a touchscreen built-in to the installed device. As described further in this disclosure, device control could be as simple as following these steps:

a. The user places their mobile device on or near an NFC-enabled cradle that

enables a control application to be downloaded and configured to enable control of the installed device.

b. The user controls the installed device (for example, they dial the phone) c. And optionally, the control application automatically removes itself from the

mobile device's memory after use

[06] This disclosure illustrates a single hardware control interface to interact with a wide variety of controllable objects by automatically establishing a wireless communication link with a device or object and then obtain sufficient information either directly from the device or object to allow a user to interact with and control the device or object directly.

[07] The system described in this disclosure can be applied to stand-alone devices or networked objects and fits well in the broader Internet of Things (loT) architecture for interconnected devices.

[08] This disclosure has these advantages over the prior art:

a. Easier control system provisioning. For example, a control interface may be set up by an integrator without complex programming of multiple control devices. b. Lower maintenance costs. The control interface is updated automatically when the controllable device or object is updated. Separate control system updates are not required.

c. Lower control system costs. The control interface may be developed using

standard hardware/operating systems.

d. Lower device costs. The target device cost may be reduced by having only

backend network interface and/or near field device communication link and higher bandwidth communication link to the control interface.

[09] One example that can use this disclosure is where a corporation has several conference rooms, each including an installed group audio conferencing system, such as a ClearOne Converge Pro 2 audio system. Some rooms may also include a video conferencing end point. Each room may contain one or more control systems, which must be manually provisioned to control attributes of the communication device. Using this disclosure, each controllable device would be linked with an automatically discoverable wireless technology, such as iBeacon or an NFC link. If iBeacon were used, a user device, such as a Smart Phone or tablet, would sense the iBeacon in the room and use the token broadcast to lookup the required application and/or control information directly through the audio system or through a backend server. The user device would then connect to and authenticate with the loT device/object to it. If a NFC sensor were used, the user would bring the user device within range of the NFC sensor (which could be built into a mobile device cradle), which would (optionally) exchange sufficient information to establish a second, higher bandwidth and greater range communication link and would then push device specific control information and/or software to the user device, allowing specific attributes of the room to be controlled.

[10] With a telephone interface, these attributes may include volume and mute controls, device capabilities, identification information, telephony interface, contact information, etc. With a video conferencing endpoint, the controllable attributes may also include video controls, such as participant layout and placement, application sharing, white boarding, media streaming controls, document camera controls, etc.

[1 1] This disclosure extends to a large variety of loT devices. Some examples include:

Manufacturing equipment - dedicated control panels may be eliminated. Smart tablet interfaces can be used by technicians to control multiple types of equipment, reducing equipment and training costs.

Automobile maintenance - When a car is brought in for maintenance, the technician brings up information from the cars diagnostic system by touching a Smart Tablet to a Near Field communications device embedded in the car. The tablet establishes a Bluetooth or Wi-Fi link with the car's diagnostic system and can pull up the car's diagnostic information for that specific car model.

Automated food/drink dispenser - A drink dispenser is set up at movie

theaters/restaurants. The user touches the Near Field sensor on the machine with his Smart Phone/Tablet. The user is presented with an interface to select a desired food or drink item specific to that machine. The Smart Phone also carries credit/debit card information so the transaction may be completed. Once the Smart Phone is removed, the transaction is completed.

Airline boarding pass printer - Instead of having screens at airports, a user touches a Near Field Communication Interface with their Smart Phone and an interface is presented which allows the user to print their boarding pass or check bags, etc.

Home Automation - Upon arriving home, the user touches his Smart

Phone/Tablet to a Near Field Communication Interface and is presented with controls specific to the location. [12] Embodiments described in this disclosure use Near Field Communication (NFC) and similar technologies for authentication, communication, and connection. More information about NFC and similar technologies are found in these patents: USPN 7657255, USPN 8060012, and USPN 8352323, all which are incorporated by reference for all purposes into this disclosure.

Summary of Invention

[13] This disclosure describes a system and method of an embodiment of an invention that controls devices and objects within the Internet of Things (loT) architecture. This embodiment of the apparatus/system includes a user device with a user control interface. In addition, this embodiment includes an loT device that performs a function, where the loT device uses an input device that allows the user device to identify, link, and control the loT device using the user control interface of the user device. The embodiment additional includes a first linking connection that links the input device of the loT device with the user device, the first linking connection also includes one or more security control attributes. This embodiment further provides that the user device on linking with the loT device can discover one or more controllable attributes of the loT device directly from the loT device; the user device uses an individual controllable attribute to determine whether it can connect to the loT device using a second linking connection with a higher communication bandwidth, if a second linking connection is available, then the user device connects to the loT device using the second linking connection; the user device will automatically retrieve the loT device remote control application from the loT device through the appropriate linking connection; and the user control interface of the user device controls the loT device through the remote control application executing on the user device.

[14] The above embodiment of the disclosure may include one or more of these additional embodiments that may be combined in any and all combinations with the above embodiment. One embodiment of the invention describes where the first linking connection uses a NFC handshaking protocol. One embodiment of the invention describes where the first linking connection uses a NFC connection in peer-to-peer mode. One embodiment of the invention describes where the controllable attribute is an NFC tag. One embodiment of the invention describes where the user control device uses the NFC connection handover to switch the NFC connection to the higher speed connection of the second linking mechanism. One embodiment of the invention describes where the input device is an NFC enabled cradle. One embodiment of the invention describes where the loT device remote control application will automatically delete itself from the memory of the user control device after the loT device remote control application use is completed. And one embodiment of the invention describes where the loT device remote control application will automatically delete itself from the memory of the user control device after the loT device remote control application after a period of inactivity.

[15] In addition, this disclosure describes a system and method of an embodiment of an invention that controls devices and objects within the Internet of Things (loT) architecture. This embodiment of the apparatus/system includes a user device with a user control interface. In addition, this embodiment includes an loT device that performs a function, where the loT device uses an input device that allows the user device to identify, link, and control the loT device using the user control interface of the user device. The embodiment additional includes a first means for a linking connection that links the input device of the loT device with the user device, the first linking means also includes one or more security control attributes. This embodiment further provides that the user device on linking with the loT device can discover one or more controllable attributes of the loT device directly from the loT device; the user device uses an individual controllable attribute to determine whether it can connect to the loT device using a second means for a linking connection with a higher communication bandwidth, if a second linking means is available, then the user device connects to the loT device using the second linking connection; the user device will automatically retrieve the loT device remote control application from the loT device through the appropriate linking means; and the user control interface of the user device controls the loT device through the remote control application executing on the user device. [16] The above embodiment of the disclosure may include one or more of these additional embodiments that may be combined in any and all combinations with the above embodiment. One embodiment of the invention describes where the first linking means uses a NFC handshaking protocol. One embodiment of the invention describes where the first linking means uses a NFC connection in peer-to-peer mode. One embodiment of the invention describes where the controllable attribute is an NFC tag. One embodiment of the invention describes where the user control device uses the NFC connection handover to switch the NFC connection to the higher speed connection of the second linking means. One embodiment of the invention describes where the input device is an NFC enabled cradle. One embodiment of the invention describes where the loT device remote control application will automatically delete itself from the memory of the user control device after the loT device remote control application use is completed. And one embodiment of the invention describes where the loT device remote control application will automatically delete itself from the memory of the user control device after the loT device remote control application after a period of inactivity.

[17] The present disclosure further describes an apparatus and method of an embodiment of the invention as further described. Other and further aspects and features of the disclosure will be evident from reading the following detailed description of the embodiments, which should illustrate, not limit, the present disclosure.

Brief Description of Drawings

[18] To further aid in understanding the disclosure, the attached drawings help illustrate specific features and embodiments of the disclosure and the following is a brief description of the attached drawings:

[19] FIG. 1 A illustrates an embodiment of the disclosure.

[20] FIG. 1 B illustrates another embodiment of the disclosure.

[21] FIG. 2 illustrates an embodiment of a user device.

[22] FIG. 3 illustrates an embodiment of a user input device.

[23] FIG. 4 illustrates an embodiment of an installed device.

[24] FIG. 5 illustrates the workflow of an embodiment of the disclosure

Disclosure of Embodiments

[25] The present disclosure describes an Internet of Things (loT) architecture for controlling devices and objects. The disclosed embodiments are intended to describe aspects of the disclosure in sufficient detail to enable those skilled in the art to practice the invention. Other embodiments may be utilized and changes may be made without departing from the scope of the disclosure. The following detailed description is not to be taken in a limiting sense, and the scope of the present invention is defined only by the included claims.

[26] Furthermore, specific implementations shown and described are only examples and should not be construed as the only way to implement or partition the present disclosure into functional elements unless specified otherwise herein. It will be readily apparent to one of ordinary skill in the art that the various embodiments of the present disclosure may be practiced by numerous other partitioning solutions.

[27] In the following description, elements, circuits, and functions may be shown in block diagram form in order not to obscure the present disclosure in unnecessary detail. Additionally, block definitions and partitioning of logic between various blocks is exemplary of a specific implementation. It will be readily apparent to one of ordinary skill in the art that the present disclosure may be practiced by numerous other partitioning solutions. Those of ordinary skill in the art would understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof. Some drawings may illustrate signals as a single signal for clarity of presentation and description. It will be understood by a person of ordinary skill in the art that the signal may represent a bus of signals, wherein the bus may have a variety of bit widths and the present disclosure may be implemented on any number of data signals including a single data signal.

[28] The various illustrative functional units includes logical blocks, modules, and circuits described in connection with the embodiments in this disclosure so as to more particularly emphasize their implementation independence. The functional units may be implemented or performed with a general purpose processor, a special purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described. A general purpose processor may be a microprocessor, any conventional processor, controller, microcontroller, or state machine. A general purpose processor may be considered a special purpose processor while the general purpose processor is configured to fetch and execute instructions (e.g., software code) stored on a computer readable medium such as any type of memory, storage, and/or storage devices. A processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[29] In addition, the various illustrative functional units previously described above may include software or programs such as computer readable instructions that may be described in terms of a process that may be depicted as a flowchart, a flow diagram, a structure diagram, or a block diagram. The process may describe operational acts as a sequential process, many of these acts can be performed in another sequence, in parallel, or substantially concurrently. Further, the order of the acts may be rearranged. In addition, the software may comprise one or more objects, agents, threads, lines of code, subroutines, separate software applications, two or more lines of code or other suitable software structures operating in one or more software applications or on one or more processors. The software may be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices.

[30] Elements described may include multiple instances of the same element. These elements may be generically indicated by a numerical designator (e.g. 1 10) and specifically indicated by the numerical indicator followed by an alphabetic designator (e.g., 11 OA) or a numeric indicator preceded by a "dash" (e.g., 1 10-1 ). For ease of following the description, for the most part element number indicators begin with the number of the drawing on which the elements are introduced or most fully discussed. For example, where feasible elements in FIG. 3 are designated with a format of 3xx, where 3 indicates FIG. 3 and xx designates the unique element.

[31] It should be understood that any reference to an element herein using a designation such as "first," "second," and so forth does not limit the quantity or order of those elements, unless such limitation is explicitly stated. Rather, these designations may be used herein as a convenient method of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second element does not mean that only two elements may be employed or that the first element must precede the second element in some manner. In addition, unless stated otherwise, a set of elements may comprise one or more elements.

[32] Reference throughout this specification to "one embodiment", "an embodiment" or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrases "one embodiment", "an embodiment" and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment.

[33] This disclosure describes a system where devices or objects can be identified, linked, and controlled from user device such as a smart phone, tablet, or other user device with a user control interface. Upon linking, the user device can discover the controllable attributes of the device/object either directly from the device/object, or from a central database, either locally or on the internet, containing information about that specific device/object. The linking connection also includes security control attributes that may include device and/or user authentication. Using this linking connection, the device/object integrates a wireless technology that allows the user device to automatically create a communication link to the device/object that could include one or more existing communication protocols that include NFC, iBeacon, Bluetooth, WIFI, or the like as described or developed in the future.

[34] Once the user device is connected loT device, the user device will automatically retrieve the loT device remote control application from the loT device through the appropriate linking connection. The remote control application may be a binary application designed specifically for the control interface (such as Android or iOS), or may include an applet or interactive markup language script (e.g. Java or HTML), which runs within the context of an existing application on the user device.

[35] One embodiment may provide that the remote control application need not be permanently stored in memory of the user device. It may be stored only if it is needed, or kept in an application cache and removed automatically after a period of inactivity, that prevents unnecessary use of the user device's memory resources and also relieving the user from having to manually manage potentially many applications for different user devices and loT devices. [36] FIG. 1A illustrates an embodiment 100 of the disclosure. A user 102 with a user control device 104 connects to an input device 108 through a linking connection by placing user device 104 near or in close proximity to the input device 108. The user device 104 can be for example, a mobile phone, a tablet, a smart watch or some other type of user device. The user device 104 incorporates some type of user control interface such as a graphical user interface as part of its operating system. The input device 108 can be for example an NFC device such as an NFC cradle or an NFC reader, an iBeacon device, a Bluetooth device, a WI-FI device, or some other type of device suitable for receiving information from the user device 104. The communication or linking connection 106 between user device 104 and input device 108 can be for example, Bluetooth, WIFI, NFC, or some other type of suitable communication medium or protocol. One embodiment of the disclosure uses an NFC connection with the NFC handshaking protocol. Another embodiment of disclosure uses an NFC connection in peer-to-peer mode. In one embodiment, the first linking connection will authenticate user device 104 to connect with input device 108 using one or more security control attributes. The security control attributes can include user authentication, device authentication, biometric authentication using fingerprints or faces such as Touch ID and Face ID by Apple. The security control attributes can be handled through the user device 104 and/or input device 108. In other embodiments a backend authentication server either on the local LAN or WAN or through the Internet maybe used.

[37] The input device 108 can be connected to a network 1 10 that could be for example a LAN and/or a WAN that uses some type of networking protocol such as TCP/IP, a serial or parallel communication link such as USB, RS-232, RS-422, or some other type of communication protocol in use now or developed in the future, that establishes a connection that connects the input device 108 to some type of network for communicating with other devices or even the Internet 1 12. In one embodiment the input device 108 can be coupled directly to or even incorporated into an loT device 1 16. In one embodiment, the user input device 108 connects to the Internet 1 12 through network 1 10. In another embodiment, the input device 108 can connect through the Internet 1 12 to a backend authentication system such as an internet server 1 14 for authentication services for connecting the user device 104 to other devices on the network such as Internet of Things devices 1 16, 1 18, 120, and/or 122. In other embodiments, the input device 108 connects directly other devices on the network such as loT devices 116, 1 18, 120, and/or 122 without requiring the use of an authentication server. In various embodiments of this disclosure, the Internet of Things devices 1 16, 1 18, 120, and/or 122 could be a local control system 1 16 that could be for example a local server, a local conferencing control system, or a home control system, or other internet connected devices, conferencing devices, lights, home appliances, or similar devices.

[38] During the setup of the first linking connection 106, the user device 104 discovers one or more controllable attributes about one or more loT devices such as loT device 1 16 directly from the loT device 1 16 itself. In one embodiment, one controllable attribute could be an NFC tag that contains information about setup and control of the loT device 1 16. Another controllable attribute could be an NFC tag that further includes information that describes that a remote control software application available for download from the loT device 1 16 to the user device 104. In another embodiment, the remote control software application could be downloadable from an internet server 1 14. The user device 104 uses another of controllable attributes to determine whether it can connect to the loT device 1 16 using a second linking connection with a higher bandwidth. In one embodiment, the second linking process uses the NFC connection handover to switch the NFC connection (the first linking connection) to a high speed connection such as Bluetooth or even WIFI. If the second linking connection is available, then the user device connects to the loT device 1 16 using the higher bandwidth connection. The user control device will automatically retrieve the loT device remote control application from the loT device 1 16 through the appropriate linking connection. In one embodiment, the user device 104 will automatically retrieve the remote control application from a local server through the appropriate linking connection. In another embodiment, the user control device will automatically retrieve the remote control application from an internet server 1 14 through the appropriate linking connection.

[39] The user can use the user control interface of the user device 104 to control the loT device 1 16 through the remote control application executing on the user device 104. In one embodiment, the loT device remote control application will automatically delete itself from the memory of the user device 104 after the loT device remote control application use is completed. And in another embodiment, the loT device remote control application will automatically delete itself from the memory of the user device 104 after the loT device remote control application after a period of inactivity.

[40] FIG. 1 B illustrates an embodiment 150 of the disclosure. A user 152 with a user device 154 connects to an input device 158 through a linking connection by placing user device 154 near or in close proximity to the input device 158. The user device 154 can be an iPhone with user control interface as part of its operating system. The input device 158 can be for example an NFC device such as an NFC cradle or an NFC reader for receiving information from the user device 154. The communication or linking connection156 between user device 154 and input device 158 uses an NFC connection with the NFC handshaking protocol. Another embodiment of disclosure uses an NFC connection in peer-to-peer mode. In one embodiment, the first linking connection will authenticate user device 154 to connect with input device 158 using one or more security control attributes. The security control attributes can include user authentication, device authentication, biometric authentication using fingerprints or faces such as Touch ID and Face ID by Apple. The security control attributes can be handled through the user device 154 and/or input device 158. In other embodiments a backend authentication server either on the local LAN or WAN or through the Internet maybe used.

[41] The input device 158 connects to network 160 that uses the TCP/IP communication protocol in use now or developed in the future, that establishes a connection that connects the input device 158 to other devices on the local network 160 and to the Internet 162. In one embodiment the input device 158 can be coupled directly to or even incorporated into an loT device 166. In one embodiment, loT device 166 can be a professional audio device such as the Converge Pro by ClearOne.

[42] During the setup of the first linking connection 156, the user device 154 discovers one or more controllable attributes about the professional audio device 166 directly from the loT device 166 itself. In one embodiment, one controllable attribute could be an NFC tag that contains information about setup and control of the professional audio device 166. Another controllable attribute could be an NFC tag that further includes information that describes that a remote control software application available for download from the professional audio device 166 to the user device 152. The user device 154 uses another of the controllable attributes to determine whether it can connect to the professional audio device 166 using a second linking mechanism with a higher bandwidth. In one embodiment, the second linking process uses the NFC connection handover to switch the NFC connection (the first linking connection) to a high speed connection such as WIFI. If the second linking connection is available, then the user device 154 connects to the professional audio device 166 using the higher bandwidth connection. The user device 154 will automatically retrieve the loT device remote control application from the professional audio device 166 through the appropriate linking connection. In one embodiment, the user control device will automatically retrieve the remote control application from a local server through the appropriate linking connection. [43] The user can use the user control interface of the user device 154 to control the professional audio device 166 through the remote control application executing on the user device 154. In one embodiment, the loT device remote control application will automatically delete itself from the memory of the user device 152 after the loT device remote control application use is completed. And in another embodiment, the loT device remote control application will automatically delete itself from the memory of the user device 152 after the loT device remote control application after a period of inactivity.

[44] FIG. 2 illustrates an embodiment of a user device 200. The user device 200 includes a user interface 202 such as commonly found in smart phones, tablets, smart watches, that incorporates some type of user control interface such as a graphical user interface as part of its operating system, and includes a touch screen, a touch pad, a display, a keyboard, a mouse, etc., or something similar as described or developed in the future for use in user input. The user device 200 further includes one or more processors 204 with one or more different types of local storage 206 that are typically found in user devices 200. The user device 200 includes a variety of connectivity interfaces that may include NFC 208, Bluetooth 210, WIFI 212, and other types of connectivity 214 that may include USB, Ethernet, or the like as described or developed in the future.

[45] FIG. 3 illustrates an embodiment of an input device 300 that could be an NFC device such as an NFC cradle or an NFC reader, an iBeacon device, a Bluetooth device, a WI-FI device, or some other type of device suitable for receiving information from a user device. One embodiment of the input device 300 could include a user interface 302 such as commonly found in smart phones, tablets, smart watches, that incorporates some type of user control interface such as a graphical user interface as part of its operating system, and includes a touch screen, a touch pad, a display, a keyboard, a mouse, etc., or something similar as described or developed in the future for use in user input. Another embodiment of the input device could include a user interface 302 that included an NFC cradle or an NFC reader for receiving information from another device. The input device 300 further includes one or more processors 304 with one or more different types of local storage 306 that are typically found in device interface bridge 300. The device interface bridge 300 includes a variety of connectivity interfaces that may include NFC 308, Bluetooth 310, WIFI 312, and other types of connectivity 314 that may include USB, Ethernet, or the like as described or developed in the future.

[46] FIG. 4 illustrates an embodiment of an Internet of Things (loT) device 400 that could be a local control system such as a local server, a local conferencing control system, or a home control system, or other internet connected devices, conferencing devices, lights, home appliances, or similar devices. In one embodiment, loT device 400 can be a professional audio device such as the Converge Pro by ClearOne. The loT device 400 may include a user interface 402 such as commonly found in smart phones, tablets, smart watches, or it could comprise a touch screen, a touch pad, a display, a keyboard, a mouse, etc., or something similar as described or developed in the future for use in user input. The loT device 400 further includes one or more processors 404 with one or more different types of local storage 406 that are typically found in loT devices 400. The loT device 400 includes a variety of connectivity interfaces that may include NFC 408, Bluetooth 410, WIFI 412, and other types of connectivity 414 that may include USB, Ethernet, or the like as described or developed in the future.

[47] FIG. 5 illustrates the workflow of one embodiment of the disclosure when a user initiates the system workflow 500 to control an Internet of Things (loT) architecture type of device. The workflow follows the initiation of a connection of an embodiment as previously described. At step 502, the user 102 places user device 104 near the input device 108. In one embodiment, the user device 104 could be a smartphone. In another embodiment, input device 108 could be an NFC cradle. As a result of the close proximity between the two devices, the first linking connection initiates to connect user device 104 with input device 108. In one embodiment, the first linking connection uses the NFC handshaking protocol for connecting the two devices. In another embodiment, first linking connection uses the NFC connection in peer to peer mode to connect the two devices. If configured, the control inference discovery process will authenticate the user device 104 to connect with input device 108 using one or more security control attributes. At step 504, the user device 104 discovers one or more controllable attributes about the loT device 1 16 directly from the loT device itself. In one embodiment, one controllable attribute could be an NFC tag that contains information about setup and control of the loT device 1 16. Another controllable attribute could be an NFC tag that further includes information that describes that a remote control software application is available for download from the loT device 1 16 to the user device 104. In another embodiment, the remote control software application could be downloadable from an internet server 1 14. At step 506, the user device 104 uses one of the controllable attributes to determine whether it can connect to the loT device 1 16 using a second linking mechanism with a higher bandwidth. In one embodiment, the second linking process uses the NFC connection handover to switch the NFC connection (the first linking connection) to a high speed connection such as Bluetooth or even WIFI. At step 508, if the second linking connection is available, then the user device 104 connects to the loT device 116 using the higher bandwidth connection. At step 510, the user device 104 will automatically retrieve the loT device remote control application from the loT device 116 through the appropriate linking connection. In one embodiment, the user device 104 will automatically retrieve the remote control application from a local server such as 1 18 - 120 through the appropriate linking connection. In another embodiment, the user device 104 will automatically retrieve the remote control application from an internet server 1 14 through the appropriate linking connection. And at step 512, the user can use the user control interface of the user device 104 to control the loT device 1 16 through the remote control application executing on the user device 104. In one embodiment, the loT device remote control application will automatically delete itself from the memory of the user device 102 after the loT device remote control application use is completed. And in another embodiment, the loT device remote control application will automatically delete itself from the memory of the user device 102 after the loT device remote control application after a period of inactivity.

[48] While the present disclosure has been described regarding certain illustrated and described embodiments, those of ordinary skill in the art will recognize and appreciate that the present invention is not so limited. Rather, many additions, deletions, and modifications to the illustrated and described embodiments may be made without departing from the scope of the invention as claimed along with their legal equivalents. In addition, features from one embodiment may be combined with features of another embodiment while still being encompassed within the scope of the invention as contemplated by the inventor. The disclosure of the present invention is exemplary only, with the true scope of the present invention being determined by the included claims.

Claims

We claim the following invention:

Claim 1 A system that controls devices and objects within the Internet of Things (loT) architecture, comprising:

a user device with a user control interface;

an loT device that performs a function, where the loT device uses an input device that allows the user device to identify, link, and control the loT device using the user control interface of the user device; and

a first linking connection that links the input device of the loT device with the user device, the first linking connection also includes one or more security control attributes; where:

the user device on linking with the loT device can discover one or more controllable attributes of the loT device directly from the loT device;

the user device uses an individual controllable attribute to determine whether it can connect to the loT device using a second linking connection with a higher communication bandwidth, if a second linking connection is available, then the user device connects to the loT device using the second linking connection; the user device will automatically retrieve the loT device remote control application from the loT device through the appropriate linking connection; and the user control interface of the user device controls the loT device through the remote control application executing on the user device.

Claim 2 The claim of claim 1 where the first linking connection uses a NFC handshaking protocol. Claim 3 The claim of claim 1 where the first linking connection uses a NFC connection in peer-to-peer mode.

Claim 4 The claim of claim 1 where the controllable attribute is an NFC tag.

Claim 5 The claim of claim 1 where the user device uses the NFC connection handover to switch the NFC connection to the higher speed connection of the second linking connection.

Claim 6 The claim of claim 1 where the input device is an NFC enabled cradle.

Claim 7 The claim of claim 1 where the loT device remote control application will automatically delete itself from the memory of the user control device after the loT device remote control application use is completed.

Claim 8 The claim of claim 1 where the loT device remote control application will automatically delete itself from the memory of the user control device after the loT device remote control application after a period of inactivity.

Claim 9 A method to manufacture a system that controls devices and objects within the Internet of Things (loT) architecture, comprising:

providing a user device with a user control interface;

providing an loT device that performs a function, where the loT device uses an input device that allows the user device to identify, link, and control the loT device using the user control interface of the user device; and

providing a first linking connection that links the input device of the loT device with the user device, the first linking connection also includes one or more security control attributes;

where: the user device on linking with the loT device can discover one or more controllable attributes of the loT device directly from the loT device;

Claim 10 The claim of claim 9 the first linking connection uses a NFC handshaking protocol.

Claim 1 1 The claim of claim 9 where the first linking connection uses a NFC connection in peer-to-peer mode. Claim 12 The claim of claim 9 where the controllable attribute is an NFC tag.

Claim 13 The claim of claim 9 where the user device uses the NFC connection handover to switch the NFC connection to the higher speed connection of the second linking connection.

Claim 14 The claim of claim 9 where the input device is an NFC enabled cradle. Claim 15 The claim of claim 9 where the loT device remote control application will automatically delete itself from the memory of the user control device after the loT device remote control application use is completed. Claim 16 The claim of claim 9 where the loT device remote control application will automatically delete itself from the memory of the user control device after the loT device remote control application after a period of inactivity.

Claim 17 A method to use a system that controls devices and objects within the Internet of Things (loT) architecture, comprising:

providing a user device with a user control interface;

linking the input device of the loT device with the user device with a first linking connection, the first linking connection also includes one or more security control attributes;

where:

Claim 18 The claim of claim 17 where the first linking connection uses a NFC handshaking protocol. Claim 19 The claim of claim 17 where the first linking connection uses a NFC connection in peer-to-peer mode.

Claim 20 The claim of claim 17 where the controllable attribute is an NFC tag.

Claim 21 The claim of claim 17 where the user device uses the NFC connection handover to switch the NFC connection to the higher speed connection of the second linking connection.

Claim 22 The claim of claim 17 where the input device is an NFC enabled cradle.

Claim 23 The claim of claim 17 where the loT device remote control application will automatically delete itself from the memory of the user control device after the loT device remote control application use is completed.

Claim 24 The claim of claim 17 where the loT device remote control application will automatically delete itself from the memory of the user control device after the loT device remote control application after a period of inactivity.

Claim 25 A non-transitory program storage device readable by a computing device that tangibly embodies a program of instructions executable by the computing device to perform a method to use a system that controls devices and objects within the Internet of Things (loT) architecture, comprising:

providing a user device with a user control interface;

linking the input device of the loT device with the user device with a first linking connection, the first linking connection also includes one or more security control attributes; where:

Claim 26 The claim of claim 25 where the first linking connection uses a NFC handshaking protocol.

Claim 27 The claim of claim 25 where the first linking connection uses a NFC connection in peer-to-peer mode.

Claim 28 The claim of claim 25 where the controllable attribute is an NFC tag.

Claim 29 The claim of claim 25 where the user device uses the NFC connection handover to switch the NFC connection to the higher speed connection of the second linking connection. Claim 30 The claim of claim 25 where the input device is an NFC enabled cradle.

Claim 31 The claim of claim 25 where the loT device remote control application will automatically delete itself from the memory of the user control device after the loT device remote control application use is completed. Claim 32 The claim of claim 25 where the loT device remote control application will automatically delete itself from the memory of the user control device after the loT device remote control application after a period of inactivity.