Internet of Things

Figure 1 illustrates an IoT system 100 in one embodiment. The IoT system 100 comprises IoT devices 102 communicatively coupled via a wide area network 104 to a server system 106 via an optional proxy server 108. The network topology of the IoT system 100 is hub-and-spoke. Each of the IoT devices 102 has a 1:1 communication channel to the server system 106 and each of the IoT devices 102 communicates with the others, if at all, via the server system 106. The optional proxy server 108 may improve the performance of the IoT system 100 by mirroring some or all of the state of the server system 106 and thus enabling the IoT devices 102 to communicate without creating bandwidth or incurring the latency of the wide area network 104. The optional proxy server 108 is typically colocated at a facility or nearby facility to where the IoT devices 102 are located.

Figure 2 illustrates an IoT system 200 in one embodiment. The IoT system 200 comprises IoT devices 202 communicatively coupled via a wide area network 204 to a server system 206 via an optional proxy server 210. The network topology of the IoT system 200 is a hybrid hub-and-spoke. One or more of the IoT devices 202 acts as a gateway device 208 providing a communication channel to the server system 206. The IoT devices 102 that are not the gateway device 208 communicate directly with the gateway device 208, or via the proxy server 210, which communicates on their behalf and on its own behalf with the server system 206. The optional proxy server 210 may improve the performance of the IoT system 200 by mirroring some or all of the state of the server system 206 and thus enabling the IoT devices 202 to communicate without creating bandwidth or incurring the latency of the wide area network 204. The optional proxy server 210 is typically colocated at a facility or nearby facility to where the IoT devices 202 are located.

Figure 3 illustrates an IoT system 300 in one embodiment. The IoT system 300 comprises IoT devices 302 communicatively coupled via a wide area network 304 to a server system 306 via an optional proxy server 310. The network topology of the IoT system 300 is a partially connected mesh network. The IoT devices 102 are organized into groups of fully connected meshes, and communicate within a mesh group without interacting with the server system 306 or proxy server 310. In other embodiments, there may be one fully connected mesh of the IoT devices 102, although this requires that each of the IoT devices 102 is in direct communication range of all of the others.

One or more of the IoT devices 302 acts as a gateway device 308 providing a communication channel to the server system 306. The IoT devices 102 that are not the gateway device 308 communicate directly with the gateway device 308, or via the proxy server 310, which communicates on their behalf and on its own behalf with the server system 306. The optional proxy server 310 may improve the performance of the IoT system 300 by mirroring some or all of the state of the server system 306 and thus enabling the IoT devices 302 to communicate without creating bandwidth or incurring the latency of the wide area network 304. The optional proxy server 310 is typically colocated at a facility or nearby facility to where the IoT devices 302 are located.

Figure 4 illustrates an IoT system 400 in one embodiment. The IoT system 400 comprises IoT devices 402 communicatively coupled via a wide area network 404 to a server system 406 via an optional proxy server 410. The network topology of the IoT system 400 is a partially connected mesh network. The IoT devices 102 are organized into groups of partially connected meshes, and communicate within a mesh group without interacting with the server system 406 or proxy server 410. This type of network topology may be found in environments in which the IoT devices 402 are spread apart and battery powered, so that they can only communicate using relatively short-range wireless communications (e.g., near-field communications). In such environments a particular one of the IoT devices 402 may only be within communication range of a nearest neightbor. 

One or more of the IoT devices 402 acts as a gateway device 408 providing a communication channel to the server system 406. The IoT devices 102 that are not the gateway device 408 communicate directly with the gateway device 408, or via the proxy server 410, which communicates on their behalf and on its own behalf with the server system 406. The optional proxy server 410 may improve the performance of the IoT system 400 by mirroring some or all of the state of the server system 406 and thus enabling the IoT devices 402 to communicate without creating bandwidth or incurring the latency of the wide area network 404. The optional proxy server 410 is typically colocated at a facility or nearby facility to where the IoT devices 402 are located.

Figure 5 illustrates an embodiment of an IoT device 500 to implement components and process steps of IoT devices described herein.

Input devices 504 comprise transducers that convert physical phenomenon into machine internal signals, typically electrical, optical or magnetic signals. Signals may also be wireless in the form of electromagnetic radiation in the radio frequency (RF) range but also potentially in the infrared or optical range. Examples of input devices 504 are keyboards which respond to touch or physical pressure from an object or proximity of an object to a surface, mice which respond to motion through space or across a plane, microphones which convert vibrations in the medium (typically air) into device signals, scanners which convert optical patterns on two or three dimensional objects into device signals. The signals from the input devices 504 are provided via various machine signal conductors (e.g., busses or network interfaces) and circuits to memory 506. 

The memory 506 is typically what is known as a first or second level memory device, providing for storage (via configuration of matter or states of matter) of signals received from the input devices 504, instructions and information for controlling operation of the CPU 502, and signals from storage devices 510. 

The memory 506 and/or the storage devices 510 may store computer-executable instructions and thus forming logic 514 that when applied to and executed by the CPU 502 implement embodiments of the processes disclosed herein.

Information stored in the memory 506 is typically directly accessible to the CPU 502 of the device. Signals input to the device cause the reconfiguration of the internal material/energy state of the memory 506, creating in essence a new machine configuration, influencing the behavior of the IoT device 500 by affecting the behavior of the CPU 502 with control signals (instructions) and data provided in conjunction with the control signals. 

Second or third level storage devices 510 may provide a slower but higher capacity machine memory capability. Examples of storage devices 510 are hard disks, optical disks, large capacity flash memories or other non-volatile memory technologies, and magnetic memories. 

The CPU 502 may cause the configuration of the memory 506 to be altered by signals in storage devices 510. In other words, the CPU 502 may cause data and instructions to be read from storage devices 510 in the memory 506 from which may then influence the operations of CPU 502 as instructions and data signals, and from which it may also be provided to the output devices 508. The CPU 502 may alter the content of the memory 506 by signaling to a machine interface of memory 506 to alter the internal configuration, and then converted signals to the storage devices 510 to alter its material internal configuration. In other words, data and instructions may be backed up from memory 506, which is often volatile, to storage devices 510, which are often non-volatile.

Output devices 508 are transducers which convert signals received from the memory 506 into physical phenomenon such as vibrations in the air, or patterns of light on a machine display, or vibrations (i.e., haptic devices) or patterns of ink or other materials (i.e., printers and 3-D printers).  

The network interface 512 receives signals from the memory 506 and converts them into electrical, optical, or wireless signals to other machines, typically via a machine network. The network interface 512 also receives signals from the machine network and converts them into electrical, optical, or wireless signals to the memory 506.

Referring to Figure 6, an IoT IoT device 600 in one embodiment comprises an antenna 602, control logic 604, wireless communication logic 606, a memory 608, a power manager 610, a battery 612, logic 616, and user interface logic 614.

The control logic 604 controls and coordinates the operation of other components as well as providing signal processing for the IoT device 600. For example control logic 604 may extract baseband signals from radio frequency signals received from the wireless communication logic 606 logic, and processes baseband signals up to radio frequency signals for communications transmitted to the wireless communication logic 606 logic. Control logic 604 may comprise a central processing unit, digital signal processor, and/or one or more controllers or combinations of these components. 

The wireless communication logic 606 may further comprise memory 608 which may be utilized by the control logic 604 to read and write instructions (commands) and data (operands for the instructions). The memory 608 may comprise logic 616 to carry out aspects of the processes disclosed herein, e.g., those aspects executed by a smart phone or other mobile device. 

A human user or operator of the IoT device 600 may utilize the user interface logic 614 to receive information from and input information to the IoT device 600. Images, video and other display information, for example, user interface optical patterns, may be output to the user interface logic 614, which may for example operate as a liquid crystal display or may utilize other optical output technology. The user interface logic 614 may also operate as a user input device, being touch sensitive where contact or close contact by a use’s finger or other device handled by the user may be detected by transducers. An area of contact or proximity to the user interface logic 614 may also be detected by transducers and this information may be supplied to the control logic 604 to affect the internal operation of the IoT device 600 and to influence control and operation of its various components. 

Audio signals may be provided to user interface logic 614 from which signals output to one and more speakers to create pressure waves in the external environment representing the audio. The IoT device 600 may convert audio phenomenon from the environment into internal electro or optical signals by operating a microphone and audio circuit (not illustrated). 

The IoT device 600 may operate on power received from a battery 612. The battery 612 capability and energy supply may be managed by a power manager 610. 

The IoT device 600 may transmit wireless signals of various types and range (e.g., cellular, GPS, WiFi, BlueTooth, and near field communication i.e. NFC). The IoT device 600 may also receive these types of wireless signals. Wireless signals are  transmitted and received using wireless communication logic 606 logic coupled to one or more antenna 602. Other forms of electromagnetic radiation may be used to interact with proximate devices, such as infrared (not illustrated).

Referring to the IoT  IoT device 700 of Figure 7, signal processing and system control 706 controls and coordinates the operation of other components as well as providing signal processing for the IoT device 700. For example signal processing and system control 706 may extract baseband signals from radio frequency signals received from the wireless communication 708 logic, and processes baseband signals up to radio frequency signals for communications transmitted to the wireless communication 708 logic. Signal processing and system control 706 may comprise a central processing unit, digital signal processor, and/or one or more controllers or combinations of these components. 

The wireless communication 708 may further comprise memory 716 which may be utilized by the signal processing and system control 706 to read and write instructions (commands) and data (operands for the instructions). 

A human user or operator of the IoT device 700 may utilize the user interface 722 to receive information from and input information to the IoT device 700. Images, video and other display information, for example, user interface optical patterns, may be output to the user interface 722, which may for example operate as a liquid crystal display or may utilize other optical output technology. The user interface 722 may also operate as a user input device, being touch sensitive where contact or close contact by a use’s finger or other device handled by the user may be detected by transducers. An area of contact or proximity to the user interface 722 may also be detected by transducers and this information may be supplied to the signal processing and system control 706 to affect the internal operation of the IoT device 700 and to influence control and operation of its various components. 

A camera 724 may interface to image processing 726 logic to record images and video from the environment. The image processing 726 may operate to provide image/video enhancement, compression, and other transformations, and from there to the signal processing and system control 706 for further processing and storage to memory 716. Images and video stored in the memory 716 may also be read by the signal processing and system control 706 and output to the user interface 722 for display to a user of the IoT device 700.

Audio signals may be provided to user interface 722 from which signals output to one and more speakers to create pressure waves in the external environment representing the audio. The IoT device 700 may convert audio phenomenon from the environment into internal electro or optical signals by operating a microphone and audio circuit (not illustrated). 

The IoT device 700 may operate on power received from a battery 720. The battery 720 capability and energy supply may be managed by a power manager 718. 

The IoT device 700 may transmit wireless signals of various types and range (e.g., cellular, WiFi, BlueTooth, and near field communication i.e. NFC). The IoT device 700 may also receive these types of wireless signals. Cellular wireless signals are  transmitted and received using wireless communication 708 logic coupled to one or more antenna 702. Shorter-range wireless signals may be transmitted and received via antenna 704 and wireless communication logic 728. Other forms of electromagnetic radiation may be used to interact with proximate devices, such as infrared (not illustrated).

The device may utilize a haptic driver 732 which controls a vibration generator 714 to cause vibrations in response to events identified by signal processing and system control 706, such as the received text messages, emails, incoming calls or other events that require the user or the device’s attention.

A subscriber identity module ( SIM 710 ) may be present in some mobile devices, especially those operated on the Global System for Mobile Communication (GSM) network. The SIM 710 stores, in machine-readable memory, personal information of a mobile service subscriber, such as the subscriber’s cell phone number, address book, text messages, and other personal data. A user of the IoT device 700 can move the SIM 710 to a different and maintain access to their personal information. A SIM 710 typically has a unique number which identifies the subscriber to the wireless network service provider.

The IoT device 700 may include an audio driver 730 including an audio encoder/decoder for encoding and decoding digital audio files or audio files stored by memory 716, SIM 710, or received in real time via  one of the antenna 702, antenna 704. The audio driver 730 is controlled by the signal processing and system control 706 and decoded audio is provided to one and more speaker 712 to create pressure waves in the external environment representing the audio.

Figure 8 illustrates a diagrammatic representation of an IoT device 800 in the form of a computer system within which a set of instructions may be executed for causing the IoT device 800 to perform any one or more of the methodologies discussed herein, according to an example embodiment. Specifically, Figure 8 shows a diagrammatic representation of the IoT device 800 in the example form of a computer system, within which instructions 808 (e.g., software, a program, an application, an applet, an app, or other executable code) for causing the IoT device 800 to perform any one or more of the methodologies discussed herein may be executed. 

The instructions 808 transform the general, non-programmed IoT device 800 into a particular IoT device 800 programmed to carry out the described and illustrated functions in the manner described.  In alternative embodiments, the IoT device 800 operates as a standalone device or may be coupled (e.g., networked) to other machines.  In a networked deployment, the IoT device 800 may operate in the capacity of a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment.  The IoT device 800 may comprise, but not be limited to, a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a PDA, an entertainment media system, a cellular telephone, a smart phone, a mobile device, a wearable device (e.g., a smart watch), a smart home device (e.g., a smart appliance), other smart devices, a web appliance, a network router, a network switch, a network bridge, or any machine capable of executing the instructions 808, sequentially or otherwise, that specify actions to be taken by the IoT device 800. 

Further, while only a single IoT device 800 is illustrated, the term “machine” shall also be taken to include a collection of machines 200 that individually or jointly execute the instructions 808 to perform any one or more of the methodologies discussed herein.

The IoT device 800 may include processors 802, memory 804, and I/O components 842, which may be configured to communicate with each other such as via a bus 844.  In an example embodiment, the processors 802 (e.g., a Central Processing Unit (CPU), a Reduced Instruction Set Computing (RISC) processor, a Complex Instruction Set Computing (CISC) processor, a Graphics Processing Unit (GPU), a Digital Signal Processor (DSP), an ASIC, a Radio-Frequency Integrated Circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, a processor 806 and a processor 810 that may execute the instructions 808.  The term “processor” is intended to include multi-core processors that may comprise two or more independent processors (sometimes referred to as “cores”) that may execute instructions contemporaneously.  Although Figure 8 shows multiple processors 802, the IoT device 800 may include a single processor with a single core, a single processor with multiple cores (e.g., a multi-core processor), multiple processors with a single core, multiple processors with multiples cores, or any combination thereof.

The memory 804 may include a main memory 812, a static memory 814, and a storage unit 816, both accessible to the processors 802 such as via the bus 844.  The main memory 804, the static memory 814, and storage unit 816 store the instructions 808 embodying any one or more of the methodologies or functions described herein.  The instructions 808 may also reside, completely or partially, within the main memory 812, within the static memory 814, within machine-readable medium 818 within the storage unit 816, within at least one of the processors 802 (e.g., within the processor’s cache memory), or any suitable combination thereof, during execution thereof by the IoT device 800. 

The I/O components 842 may include a wide variety of components to receive input, provide output, produce output, transmit information, exchange information, capture measurements, and so on.  The specific I/O components 842 that are included in a particular machine will depend on the type of machine.  For example, portable machines such as mobile phones will likely include a touch input device or other such input mechanisms, while a headless server machine will likely not include such a touch input device.  It will be appreciated that the I/O components 842 may include many other components that are not shown in Figure 8.  The I/O components 842 are grouped according to functionality merely for simplifying the following discussion and the grouping is in no way limiting.  In various example embodiments, the I/O components 842 may include output components 828 and input components 830.  The output components 828 may include visual components (e.g., a display such as a plasma display panel (PDP), a light emitting diode (LED) display, a liquid crystal display (LCD), a projector, or a cathode ray tube (CRT)), acoustic components (e.g., speakers), haptic components (e.g., a vibratory motor, resistance mechanisms), other signal generators, and so forth.  The input components 830 may include alphanumeric input components (e.g., a keyboard, a touch screen configured to receive alphanumeric input, a photo-optical keyboard, or other alphanumeric input components), point-based input components (e.g., a mouse, a touchpad, a trackball, a joystick, a motion sensor, or another pointing instrument), tactile input components (e.g., a physical button, a touch screen that provides location and/or force of touches or touch gestures, or other tactile input components), audio input components (e.g., a microphone), and the like.

In further example embodiments, the I/O components 842 may include biometric components 832, motion components 834, environmental components 836, or position components 838, among a wide array of other components.  For example, the biometric components 832 may include components to detect expressions (e.g., hand expressions, facial expressions, vocal expressions, body gestures, or eye tracking), measure biosignals (e.g., blood pressure, heart rate, body temperature, perspiration, or brain waves), identify a person (e.g., voice identification, retinal identification, facial identification, fingerprint identification, or electroencephalogram-based identification), and the like.  The motion components 834 may include acceleration sensor components (e.g., accelerometer), gravitation sensor components, rotation sensor components (e.g., gyroscope), and so forth.  The environmental components 836 may include, for example, illumination sensor components (e.g., photometer), temperature sensor components (e.g., one or more thermometers that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., barometer), acoustic sensor components (e.g., one or more microphones that detect background noise), proximity sensor components (e.g., infrared sensors that detect nearby objects), gas sensors (e.g., gas detection sensors to detection concentrations of hazardous gases for safety or to measure pollutants in the atmosphere), or other components that may provide indications, measurements, or signals corresponding to a surrounding physical environment.  The position components 838 may include location sensor components (e.g., a GPS receiver component), altitude sensor components (e.g., altimeters or barometers that detect air pressure from which altitude may be derived), orientation sensor components (e.g., magnetometers), and the like.

Communication may be implemented using a wide variety of technologies.  The I/O components 842 may include communication components 840 operable to couple the IoT device 800 to a network 820 or devices 822 via a coupling 824 and a coupling 826, respectively.  For example, the communication components 840 may include a network interface component or another suitable device to interface with the network 820.  In further examples, the communication components 840 may include wired communication components, wireless communication components, cellular communication components, Near Field Communication (NFC) components, Bluetooth^® components (e.g., Bluetooth^® Low Energy), Wi-Fi^® components, and other communication components to provide communication via other modalities.  The devices 822 may be another machine or any of a wide variety of peripheral devices (e.g., a peripheral device coupled via a USB).

Moreover, the communication components 840 may detect identifiers or include components operable to detect identifiers.  For example, the communication components 840 may include Radio Frequency Identification (RFID) tag reader components, NFC smart tag detection components, optical reader components (e.g., an optical sensor to detect one-dimensional bar codes such as Universal Product Code (UPC) bar code, multi-dimensional bar codes such as Quick Response (QR) code, Aztec code, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2D bar code, and other optical codes), or acoustic detection components (e.g., microphones to identify tagged audio signals).  In addition, a variety of information may be derived via the communication components 840, such as location via Internet Protocol (IP) geolocation, location via Wi-Fi® signal triangulation, location via detecting an NFC beacon signal that may indicate a particular location, and so forth.

EXECUTABLE INSTRUCTIONS AND MACHINE STORAGE MEDIUM

The various memories (i.e., memory 804, main memory 812, static memory 814, and/or memory of the processors 802) and/or storage unit 816 may store one or more sets of instructions and data structures (e.g., software) embodying or utilized by any one or more of the methodologies or functions described herein.  These instructions (e.g., the instructions 808), when executed by processors 802, cause various operations to implement the disclosed embodiments.