Claim of priority:

[0001] This application claims priority from a NIPO application with application number 21656, filed on 10 ^th March 2021, and titled “Method for addressable data communication, processing, control, and visualization based on RF wireless communication with or without an Internet connection,” the contents of which are incorporated herein by reference in its entirety.

TECHNICAL FIELD

[0002] The present disclosure generally relates to systems and methods for wireless communication. In particular, the present disclosure relates to systems and methods for addressable data communication based on Radio Frequency (RF) wireless communication regardless of an Internet connection.

BACKGROUND

[0003] Numerous wired or wireless technologies are in use for data transmission and communication applications. For data communication, wireless technologies have been preferred for its obvious benefits and convenience. The most advantageous aspect of the wireless technology could be a user’s freedom of movement within a space in which wireless communication has been established. Specially in home appliances, electronic utility appliances, or where the user convenience is prioritized, wireless technologies have been implemented. Few examples of the wireless data communication technologies include Bluetooth, Bluetooth low energy, Zigbee, Z-wave LoRa, Wi-Fi, radio frequency and cellular technology with a private or corporate network, or internet connection.

[0004] Radio-frequency based communication is robust, reliable, accurate and efficient. Radio Frequencies refers, generally, to the frequencies that fall within the electromagnetic spectrum association with radio wave propagation. RF current creates electromagnetic fields when applied to an antenna that propagates the applied signal through space. The frequency of the RF signal is inversely proportional to the wavelength of the field. The rate of oscillation for the radio frequencies is in the range of about 3 kHz to 300 GHz. The RF spectrum is categorized into various bands and ranges depending upon on its propagation characteristics. The sub- 1 GHz frequency band in the RF spectrum have been used for long- range applications, ranging from 100 m to 20 km. The GHz frequency band that falls under short-range can only be used indoors through walls in the distance ranging from lm and 100 m or less. The long-range band, that is kHz band, allow low power long-range transmissions. The short-range band, i.e., GHz band, allow high-speed short-range transmission.

[0005] RF signals are the RF waves that have been modulated to contain data information/ command/ or message. RF communication system typically involves a transmitter-receiver pair or a transceiver for transmitting and receiving the RF signals for data transfer.

[0006] Generally, few RF-based wireless communication systems, such as microwave RF systems, fixed and mobile satellite systems, wireless network and protocols, personal communication systems, remote sensing systems, and a few emerging wireless technologies, have been applied for data communication applications.

[0007] Compared to other communication technologies, long-range wireless RF based communication technologies have several advantages. First, the data connection is enabled over a long-range while consuming low power. Second, a spread-spectrum modulation technique is used which demodulates noise easily. As a result, reliability of communication is ensured. Moreover, the long-range wireless communication technologies can be used to improve network efficiency and can be used for embedded applications because of their higher extendibility and low-cost development. Moreover, they can be apt fit for indoor and outdoor applications in smart cities, smart homes, and smart buildings.

[0008] Data communication devices transmit and receive data to and from other communication devices, respectively. When more than two devices share a common communication channel, data communication should be addressable. An address is a unique data code, which can be used to identify a device or set of devices uniquely. Many devices may receive the same data communication message. The unique ID presented with the communication message carries an identification code that defines which device or devices should respond to the received data. The uniquely addressed device decodes the received data to determine the task in the received message.

[0009] The unique IDs may belong to nodes or gateways involved in communication. As known in the general art, wireless communication is the addressable data communication between two or more nodes, and a gateway is a node that acts as a gate between two discrete networks allowing data to flow from one network to another. Each network may have one or more nodes and one or more gateways. The gateways are capable of gathering the data received from node ends.

[0010] In the existing technologies, gateways are only capable of gathering the data received from a node. The gateways cannot communicate bidirectionally with each individual node separately without Internet connection. In present applications, particularly in Internet-based IoT systems, data communication between several nodes is established through Internet connection for the data transfer. This limitation makes the system heavily dependent on the Internet connection and cloud database. Any Internet connection failure or cloud server failure could result in a total or partial system failure. This limitation affects the reliability of the data communication. Furthermore, existing systems require separate architectures for data sensing, monitoring, and devices controlling processes.

SUMMARY

[0011] Due to limitation of Internet dependability, and resulting poor data communication reliability, there is a felt requirement of providing a reliable and robust data communication system to cater long-range communication with low power consumption and no dependability on Internet connection.

[0012] The present disclosure thus discloses a system and method for addressable data communication, processing, control, and visualization based on Radio Frequency (RF) wireless communication regardless of an Internet connection. The system is based on RF wireless communication technology, and not on the Internet connectivity, thereby resulting in a reliable and robust wireless data communication system.

[0013] The system includes, but is not limited to, at least one node, at least one gateway, at least one sensor device, at least one controller device, one or more microcontrollers, at least one Central Processing Unit (CPU).

[0014] In the system, according to some embodiments, at least one controller device is configured to control an appliance. At least one sensor device is communicatively coupled to the appliance and configured to monitor the appliance. The sensor device, depending on the type of the sensor device, monitors the relevant sensing attribute. Any change in sensing values pertaining to the appliance can be identified.

[0015] According to the embodiments, at least one node is communicatively coupled to the at least one sensor device to receive sensor data. At least one node is communicatively coupled to at least one controller device. The at least one controller device is capable of controlling the appliance or any device. The at least one node having a unique address, is configured to transmit the processed the sensor data and receive data requests or commands from the at least one gateway. In one implementation, the at least one node includes a first microcontroller to generate addressable data by assigning a unique node ID to at least one of the sensor data. The first microcontroller generates a data package with addressable data. The at least node further comprises a Radio Frequency (RF) node transceiver configured to communicate the addressable data wirelessly. The RF node transceiver is capable of transmitting and receiving the sensor and controller device addressable data.

[0016] According to some embodiments, the at least one gateway is communicatively coupled to the at least one node through a bi-directional long-range and low power RF wireless communication. The at least one gateway includes an RF gateway transceiver configured to receive the addressable data. The at least one gateway further includes a second microcontroller configured to identify the at least one node based on the unique ID in the addressable data and organize the addressable data for communicating messages. The at least one gateway further includes a central processing unit configured to process the addressable data from the at least one node, provide the processed data for display on a user interface through a display device, and communicate at least one of automated command and user defined commands to the at least one node to be executed on the at least node. [0017] According to some embodiments, the first microcontroller of at least one node is configured to wirelessly communicate addressable data to the at least one gateway upon verification of any request made by the gateway or deviations from pre-defined valid range of values or reference value in the sensor data. The first microcontroller is further configured to execute the at least one of automated and user defined commands to initiate the at least one controller device to perform actions to control the appliance.

BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The foregoing and other objects, aspects, features, and advantages ofthe disclosure will become more apparent and better understood by referring to the following description taken in conjunction with the accompanying drawings, in which:

[0019] FIG. 1 is a block diagram depicting a system for addressable data communication, according to some embodiments;

[0020] FIG. 2 depicts a gateway system architecture block diagram, according to some embodiments;

[0021] FIG. 3 illustrates a gateway data packet, according to some embodiments; [0022] FIG. 4 depicts a node system architecture block diagram, according to some embodiments.

[0023] FIG. 5 illustrates the data processing and visualization process handled by the CPU in the gateway, according to some embodiments.

[0024] FIG. 6 depicts a block diagram of one implementation of the system architecture, in accordance with some embodiments.

[0025] FIG. 7 depicts a block diagram of the system architecture with user devices connected through the Internet, in accordance with some embodiments.

[0026] FIG. 8 depicts a flow diagram describing method steps, in accordance with some embodiments.

DETAILED DESCRIPTION

[0027] In various embodiments of the disclosure, non-limiting definitions of one or more terms that will be used in the document are provided below.

[0028] Hereinafter, an apparatus and various methods, to which the embodiments are applied, will be described in more detail with reference to the accompanying drawings. The suffixes “module” and “unit” of elements herein are used for the convenience of description and thus can be used interchangeably and do not have any distinguishable meanings or functions.

[0029] In the following description of the embodiments, it will be understood that, when each element is referred to as being formed “on” or “under” the other element, it can be directly “on” or “under” the other element or be indirectly formed with one or more intervening elements therebetween. In addition, it will also be understood that “on” or “under” the element may mean an upward direction and a downward direction of the element.

[0030] FIG. 1 depicts a general architecture of an addressable data communication system 100, in accordance with several embodiments. The addressable data communication system is based at least on RF wireless communication, and includes one or more nodes 101-(l-n) (alternatively referred to as node 101), at least one gateway 102 (alternatively referred to as gateway 102), at least one sensor device 106, at least one controller device 108, and an appliance 109. The system also includes a dashboard 110, and a storage device 112. The system is configured to communicate using a Radio Frequency (RF) based wireless communication between the node 101 and the gateway 102, in accordance with several embodiments. [0031] In one or more embodiments, the nodes 101-(l-n) are configured to wirelessly transmit data with an addressable unique node ID. In one implementation, the data is transmitted upon the request of the connected gateway 102. In another implementation, the data is transmitted without receiving any request from connected gateway 102. In one or more embodiments, disconnection or drift from by the appliance 120 connected to the sensor device 106 are reported to the gateway 102 from the node 101 through notifications. Such notifications are transmitted to the gateway 102 by the node 101 without receiving communication request from the gateway 102. Each node 101 may include a first microcontroller 122 and a RF node transceiver 114 (as shown for node 101-2). The first microcontroller 122 is configured to generate addressable data by assigning a unique node ID associated with the at least one node to at least one of the sensor data. The Radio Frequency (RF) node transceiver is configured to communicate the addressable data wirelessly. Although FIG. 1 illustrates the sensor device 106 and the controller device 108 as elements outside the node 101, in one or more embodiments, the sensor device 106 and the controller device 108 may be implemented as integral to the node 101.

[0032] In accordance with some embodiments, the at least one sensor device 106 and the at least one controller device 108 are connected to the node 101 and the appliance 120 separately, or together, and the one or more nodes 101-(l-n) are communicatively coupled to the at least one gateway 102 individually. The gateway 102 includes a second microcontroller 124, an RF gateway transceiver 116 and single board computer 126. The single board computer 126 may be a server, mobile device, laptop, PDA and the like. The single board computer 126 may include a processor 128. The RF communication between the node 101 and the gateway 102 is established through the RF node transceiver 114, and the RF gateway transceiver 116. The first microcontroller 122 and the second microcontroller 124 may include one or more microcontrollers.

[0033] For controlling and processing the RF signals, the single board computer 126 (also referred to as the central processing unit) collects and processes addressable data received from RF node transceiver 114. The single board computer 126 may analyze, process and organize the data obtained from the processed RF signals to be rendered for visualization. For example, the single board computer 126 may identify the RF signals pertaining to individual nodes 101-(l-n) and obtain the data from the RF signals including sensor data, status of the appliance 120, a health of node and/or the appliance 120 and such data. The single board computer 126 may store the data in the storage according to the unique node ID. The single board computer 126 may provide the data to an analytics engine for rendering visuals when requested through the dashboard 110.

[0034] Referring back to the communication between nodes and the gateway 102, the gateway 102 communicates with all the nodes separately and wirelessly, and each node 101- (1-n) communicates with the gateway 102 individually. According to few embodiments, the sensors devices 106 are configured to send sensor data to the nodes lOl-(l-n). Further, the nodes 101-(l-n) may be configured to transmit the sensor data to the gateway 102 via RF node transceiver 114. From the gateway 102, the sensing data may be stored in a storage database in real-time or otherwise, according to some embodiments. The sensing data may be processed by the second microcontroller 124. In one or more embodiments, a command or message is generated by the single board computer 126 for external controlling devices, i.e., controller device 108. The controller device 108 actuate one or more controlling means to control peripheral appliances devices connected thereof. Dashboard 110 is also connected to the single board computer/CPU 202 to enable a user to send control commands to the system.

[0035] All components connected in the system are described in more detail with respect to FIG. 1. The one or more nodes 101-(l-n) may be connected to the sensor device 106 (sometimes referred to as sensor nodes). The one or more nodes 101-(l-n) may be constructed in a layered fashion, both with respect to signal processing and network protocols, to enable use of standard tools, ease real-time operating systems issues, promote adaptability to unknown environments, simplify reconfiguration, and enable lower-power, continuously vigilant operation. The sensor device 106 may send the sensor data through one or more nodes 101-(l-n) to the gateway 102, and the sensor data may be stored at the storage database in real-time. Linkage of the gateway 102 with the storage databases enables extra resources to be brought to bear in analysis and archiving of events, and database techniques may be used to control the entire network, to enable more efficient control and design.

[0036] The sensor nodes can be of a variety of types, including very simple nodes that may, for example, serve as tags. According to some embodiments, the sensor nodes may be configured to be more compact and capable systems, and may communicate with sensor devices 106 with more reliability through RF communication system. The system may enable a wide variety of users to utilize the system with different data rate and power requirements to coexist as, for example, in wired or wireless mode home appliances. [0037] According to some embodiments, the wireless RF communication system includes at least the RF node transceiver 114 and an RF gateway transceiver 116. In another implementation, the system 100 may include a pair of RF transmitter and RF receiver at the node 101 and the gateway 102, not explicitly shown in FIG. 1. The RF transmitter may be configured for wirelessly transmitting RF signals to the RF receivers, and the term “RF receivers” may be used interchangeably with a wireless RF transmitter, a transmission terminal, a transmitter, a transmission apparatus, a transmission side, a RF transfer apparatus, etc. The RF receivers, may be configured for wirelessly receiving power from the RF transmitters, and the term “receivers” may be used interchangeably with a wireless RF reception apparatus, a wireless RF receiver, a receiver, a reception terminal, a reception side, a reception apparatus, etc.

[0038] A transmitter according to an embodiment may be configured in the form of a pad, a cradle, an Access Point (AP), a small base station or a stand, and may be of a ceiling- mounted type or a wall-mounted type. One transmitter may transfer power to a plurality of wireless RF reception apparatuses. In some examples, the wireless RF transmission unit may include an electromagnetic induction type wireless charging technology defined by the Wireless Power Consortium (WPC) and the Power Matters Alliance (PMA), which are wireless charging technology standardization organizations. The transmitter that can use protocols such as Bluetooth, near field communications, Wi-Fi, ZigBee, radio-frequency communications, cellular communications, satellite communications, and/or any other wireless communications protocol or technology capable of being understood by anyone skilled in the art, to communicate with a device at a remote location.

[0039] A receiver, according to an embodiment, may include at least one wireless power reception unit, and may wirelessly receive power from two or more transmitters at the same time. In some examples, the wireless power reception unit may include an electromagnetic- induction-type wireless charging technology that is defined by the Wireless Power Consortium (WPC) and the Power Matters Alliance (PMA), which are wireless charging technology standardization organizations.

[0040] The receiver according to the embodiment may be used in small electronic appliances, such as, for example, a mobile phone, a smart phone, a laptop computer, a digital broadcasting terminal, a Personal Digital Assistant (PDA), a Portable Multimedia Player (PMP), a navigation system, an MP3 player, an electric toothbrush, an electronic tag, a lighting apparatus, a remote controller, a float, and a wearable device such as a smart watch, without being limited thereto, and may be used in other various appliances so long as they allow the installation and battery charging of the receiver according to the embodiment. [0041] According to some embodiments, the controller device 108 may be configured to control the appliance 120 that may include peripheral devices connected to the system 100. In some implementations, the controller device 108 may be an actuator, that is configured to lock and/or unlock the engagement mechanism based on a control signal received from or otherwise transmitted by the microcontroller. In further examples, the controller device 108 may be a display, relay, solenoid valves, Light Emitting Diode (LED) indicators, audio output and such devices. As described earlier, the sensor device 106 and the controller device 108 may be controlled by the first microcontroller 122.

[0042] The first microcontroller 122 and the second microcontroller 124 may be comprised of a microprocessor, micro-controller, digital signal processor, graphics processing unit, field programmable gate array, application specific integrated circuit, system on a chip, and/or similar microelectronic circuit. The first microcontroller 122 and the second microcontroller 124 may use embedded algorithms and/or other firmware code to process the data generated by the sensors, manage power consumption, and communicate internally and externally.

[0043] Examples of long-range wireless technology may include a LoRa, WiMAX, 6L0WPAN, ultra-narrow band (UNB), or NB-IoT radio, Bluetooth, Bluetooth low energy (BLE), Zigbee, or Z-Wave can also be used for shorter range communications. The wireless communication technology can utilize and communicate with an application programming interface (API) protocol, a simple object access protocol (SOAP), a representational state transfer (REST) protocol, or another API technology.

[0044] Referring back to FIG. 1, the gateway 102 may be configured to gather, process, and visualize the received addressable data and may have the capability to send automated or user defined commands to a specific node for necessary actions. The terms dash and dashboard 110 and variations thereof, as used herein, may be used interchangeably and can be any panel and/or area of a vehicle disposed adjacent to an operator, user, and/or passenger. Dashboard 110 may include, but are not limited to, one or more control panel(s), instrument housing(s), head unit(s), indicator(s), gauge(s), meter(s), light(s), audio equipment, computer(s), screen(s), display(s), HUD unit(s), and graphical user interface(s). [0045] In some embodiments, the gateway 102 may be configured to store sensor data transmitted by the node in real-time. In one implementation, the storage device 112 may be a solid-state storage device 112. In one implementation, the storage device 112 may be a non-volatile computer-readable storage device 112 operable to permanently store computer- interpretable data. ‘Permanent storage’ as used herein may retain the stored data even when not powered. Examples of the storage include, but may not be limited to a portable computer diskette, a hard disk, a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device 112, a magnetic storage device 112, or any suitable combination of the foregoing. In another implementation, the storage device 112 may be a cloud storage connected with the appliances. Generally, uploading, access and manipulation of data stored on a cloud storage site is conducted via an HTTP, FTP or similar network connection. Examples of cloud storage service providers include Amazon Simple Storage Service, Rackspace, Windows Azure, and Iron Mountain, and Nirvanix Storage Delivery Network.

[0046] Referring back to FIG. 1, functional details pertaining to the system components described above are described in more detail herein. In some embodiments, the gateway 102 may transmit successive data request messages to all the connected node 101-(l-n) addressing individually. The data request message may include the gateway ID to identify the exact gateway 102.

[0047] In some embodiments, the nodes 101-(l-n) may identify the received message and may verify the gateway ID to confirm whether the message was originated from the connected gateway 102 and to check whether a data requesting node ID and a received node ID in the data request message match each other.

[0048] In some embodiments, if the connected gateway 102 ID and the message received node ID are matched, then the node 101 may identify the received message and determine whether it is requesting the data or assigning a command to be executed.

[0049] Upon message verification, if the node 101 identifies the received message as a data request, then the first microcontroller 122 of the node 101 may arrange the data packet(s) by including a unique node ID, data collected from the sensor device 106 (sensor or electronic device), and other necessary identification information, and then the node data packet(s) may be transmitted back to the gateway 102 by the RF node transceiver 114. The number of transmitting data packets may be calculated according to the data length.

[0050] During message verification, if the node 101 identifies the received message as a command to be executed, then the node 101 may make execute the command to initiate the controller device 108 to perform actions to control the appliance 120 by, for example, sending the execution command to the controller device 108. [0051] In some embodiments, upon receiving the data packets by the gateway 102, the received data may be processed and sorted according to their node IDs and other identification information as received by the gateway 102.

[0052] The processed data, in some embodiments, may be stored in local memory of the second microcontroller 124 and/or the single board computer 126, and displayed on a local dashboard 110, which operates without the Internet.

[0053] The node 101 may continuously perform above mentioned steps with an assigned frequency. In embodiments, if any said sensor device 106 (sensor or electronic device) deviates a pre-assigned threshold value or drifts from a normal condition, the deviations from pre-defmed valid range of values or reference value, drifting is identified and transmitted by the node 101 as a notification message. This step is being operated as an independent function without interrupting and affecting the communication steps. If the gateway 102 receives a notification message from a specific node, the gateway 102 immediately indicates the notification on the dashboard 110 and sends a command to control the specific node according to the notification message. Further custom commands can also be assigned to control nodes individually.

[0054] FIG. 2 describes the gateway 102 that includes an RF gateway transceiver 116, the second microcontroller 124, and a single board computer (SBC) 126 which acts as a central processing unit (CPU 202). As described in FIG. 1 earlier, the RF gateway transceiver 116 is communicatively coupled to the second microcontroller 124. The second microcontroller 124, according to some embodiments, is coupled to the SBC 126. According to some embodiments, the CPU 126 may be configured to perform addressable data processing and visualization operations. According to some embodiments, the second microcontroller 124 and the RF gateway transceiver 116 may be configured to communicate with all the connected nodes 101-(l-n) individually for addressable data communication. In the process of addressable data communication, the second microcontroller 124 identifies the nodes 101-(l-n), which are connected to the gateway 102 and verifies their unique node IDs upon receipt. The data packets of the addressable data are also arranged by the second microcontroller 124 when sending messages.

[0055] In accordance with one or more embodiments, the SBC includes a memory for the real-time data storage, an external display to facilitate the local dashboard 110, an optional Internet access and Publish/Subscribe messaging domain for network communication 206. The data storage facilitates history retention locally, which is useful when UAN or WAN fails. The local dashboard 110 may be built coupled to the SBC 126, which is capable of graphically visualizing the collected data. Moreover, the SBC 126 may connect to the Internet using Ethernet or Wi-Fi, which gives the ability for the users to access local storage remotely. These features are customizable and can be manipulated to facilitate the data security, availability, and system robustness requirements.

[0056] In some embodiments, a power unit 204 may be connected to power up the system components. Some examples of power unit 204 include 230V AC to 3v3, battery backup and solar power unit 204.

[0057] FIG. 3 describes data packets inclusive of identifications assigned by the microcontroller, according to some embodiments. FIG. 3 illustrates a gateway data packet 302 and a node data packet 304. The gateway data packet 302 is generated by the gateway 102. The node data packet 304 is generated by the node 101. The components of the gateway data packet 302 and the node data packet 304 are explained below.

[0058] In one embodiment, the Gateway ID may be the ID of the gateway 102 when a node receives the data packet. The Gateway ID may indicate whether the received data packet was originated from the intended gateway 102 or not.

[0059] In one or more embodiments, Node identification, referred to as Node ID, may be included into the data package. With use of Node ID, the gateway 102 is able to communicate with nodes individually, and to store and process data separately.

[0060] In one or more embodiments, Destination Identification, referred as to Destination ID, may be included in the data package. Destination ID indicates an end location of the data packet. According to some implementations, the gateway 102 may send separate data requesting messages to all the connected nodes individually. Receiving node accepts the received data packet only if the destination ID and the received node ID are matched.

[0061] In one or more embodiments, requesting identification, referred as to requesting ID, may be included in the data package. Requesting ID of the data requesting node, in one implementation, assigns IDs to the data packet based on the identity of the intended destination node.

[0062] In one or more embodiments, message identification, referred as to Message ID, may be included in the data package. Once the data package is received, the node may identify and match the message ID with the requesting node ID and the destination ID. If the requesting ID, destination ID, and the message ID match, then the node may transmit the requested data to the connected gateway 102.

[0063] In one or more embodiments, Message/Command may be included in the data package. In the default setting of the data packet in the data requesting step, the gateway 102 may assign a data requesting message to the Message/Command control information. If the gateway 102 identifies any warning message from a node, the gateway 102 either may automatically send the necessary commands to address the issues or may let the users control the connected controller device 108. In both methods, the Message/Command control information in the data packet may be used to send the necessary commands.

[0064] In one or more embodiments, sensor data and/or any message from the connected sensor device 106 may be included in the data package. The first microcontroller 122 may assign the measured values of all the connected sensor devices 106 to the respective data packets. This may allow multiple sensor data to be sent in a single data packet, which enhances bandwidth efficiency and customizability. In some implementations, other specific node identification information may be sent through the data package. The node may transmit all the specific information using this other necessary information segment, this may assist to sort the addressable data in a single data packet.

[0065] FIG. 4 describes, according to one or more embodiments, the node 101 that includes RF node transceiver 114, the first microcontroller 122, controller device 108 sensor device 106-(l-n) and power unit 204. In one embodiment, the first microcontroller 122 may receive sensor data from the connected sensor device 106-(l-n). The received sensor data may be modified by assigning a node ID (referred to as addressable data) and other necessary identification information. In one embodiment, the addressable data packets may be transmitted to the RF node transceiver 114. The RF node transceiver 114 may transfer the addressable data from the node 101 wirelessly to the gateway 102. According to one embodiment, the RF node transceiver 114 may communicate only with the intended gateway 102, and if the node 101 receives any user defined or custom commands from the connected gateway 102, the first microcontroller 122 may execute the automated command and user defined command to initiate the controller device 108 to perform actions to control the appliance 120.

[0066] As illustrated by FIG. 4, the one or more sensors, collectively referred as to sensor device 106, for providing sensing input information to the first microcontroller 122. The sensor device 106, in one implementation, may be clustered to cater a specific purpose or application. For example, first set of sensor devices 106a may include environment measuring sensors, including weather tracking data, traffic data, user health tracking data, vehicle maintenance data, or other types of data, which may provide environmental or other data to the first microcontroller^. Second set of sensor devices 106b may include agriculture attributes measuring sensors. For example, temperature sensor, a humidity sensor, a moisture sensor, a light sensor, a velocity sensor, an orientation sensor, a movement sensor, an accelerometer, an air pressure sensor, a camera and/or a microphone, and the like. Third set of sensor devices 106c may include hydrogen sulfide (FFS), nitrogen dioxide (NO2), sulfur dioxide (SO2), carbon dioxide (CO2), carbon monoxide (CO), oxygen (O2), LEL, or generally any gases, for detecting one or more gases. Each sensor device is configured to be operated within a given corresponding defined valid range of values. In one or more embodiments, the power unit 404 may be connected to power up the system components. Some examples of power unit 404 include, but are not limited to, 230V AC to 3v3, battery backup and solar power unit. The power unit 404 may be similar to power unit 202 as shown in FIG. 2.

[0067] According to some embodiments, the dashboard 110 may be coupled with the SBC 126. The dashboard 110 may be a device with a user interface enabling user to send user control command via user interface. Also, the processed signal information may be displayed in the dashboard 110 for the user to view. In one implementation, the dashboard 110 may be a device with a display and a processing unit to display data and perform computer related instructions by the user in order to send command instructions to the appliances 120 and/or peripheral devices.

[0068] In an example, a node 101 may be coupled to a visual sensor 106 such as an intelligent camera. In an example, the camera may generate a trigger in response to detection of an abnormal situation (without the request of the gateway). The node 101 may receive the sensor data from the camera and communicates the addressable data including the sensor data to the gateway 102 through a bi-directional long-range and low power RF wireless communication. The gateway 102 may communicate automated or user defined control signals to the node 101 or any other node that is coupled to controller device 108 that is further coupled to doors or other home appliances. The node 101 or any other node may execute the automated or user defined control signals to initiate the controller device 108 to perform actions to control the doors or other home appliances. System including the node 101, the gateway 102, the visual sensor 106, the controller device 108, and the appliances work with or without Internet or cloud network. In situations of failure of Internet or cloud failure, the system does not deactivate. Due to this unique feature, the system 100 may overcome Internet and cloud dependencies, which is a major drawback of existing systems. Furthermore, a separate controlling system is not required for the system as the node 101 in proposed system may handle both one or more monitoring devices and one or more controlling devices in comparison with existing systems that require a separate controlling system.

[0069] In another simplistic example, the system is connected with a printer, and if the user wants to send a print command, the user can use a dashboard 110 to send a command. In case, the printer is disconnected, a notification message may be transmitted to the dashboard 110 and displayed on the display for the user to read, and subsequently take a necessary action. Thus, the user can communicate with the system. The controller device 108, according to some embodiments, may control external peripheral devices, for example, printer, audio systems, and the like. In one implementation, the controller may be an actuator, a display, a relay, a solenoid valve, LED indicators, and the like. In an example, relay may be a node that may detect a location, control, and status monitoring device, and report such detection to a computer server. In some instances, the node may obtain information specifically identifying the location status monitoring device, along with its status. A location of the location and status monitoring device may be derived with respect to proximity of the node, or may be reported from the location and status monitoring device to the node. The identifying information may be recorded at the node for future use, or may be forwarded to a computer server for any of several purposes.

[0070] According to some embodiments, the controller device 108 may be a display. The display may refer to a portion of a physical screen used to display the output of a computer to a user. The display screen may be of a variety of types, including, but not limited to, a cathode ray tube (CRT), plasma, light-emitting diode (LED), organic LED (OLED), LEP (Light Emitting Polymer) or PLED (Polymer LED), liquid crystal display (LCD), thin film transistor (TFT) LCD, LED side-lit or back-lit LCD, combinations thereof, and the like. In various embodiments, the display screen may be integral with the electronic device. In other embodiments, the display screen may be separate from the electronic device, such as with a computer monitor or another video monitor.

[0071] According to some embodiments, the storage database is provided to store sensing data transmitted by the nodes in real-time. The aspects of the storage database of the storage device 112 are described in more detail with reference to FIG.1.

[0072] FIG. 5 illustrates a block diagram of one implementation of the system architecture, in accordance with some embodiments. The nodes 1-n may be similar to the nodes 101-(1- n) shown in FIG. 1 and gateway 102-(A-n) may be similar to the gateway 102 shown in FIG. 1. In one implementation, one or more number of gateways 102 may be interconnected using the publish or subscribe messaging domain. In another implementation, individual gateway 102 may be linked to an external centralized unit 504, which function as a broker device. The broker device may be a computer, any kind of a computing device, or specially a server can be used as the external centralized unit and it can gather, sort, and store data collected from the connected gateway 102 separately. In the case of using a server 502 as the external centralized unit, the data gathered from the connected gateway 102 can be stored in a database server. This not only gives full-fledged control over data availability with features such as remote access to the collected data through web-based applications with enforced access restrictions it also facilitates the ability to enhance data integrity and system robustness. Also, the system provides an option for external devices to be coupled with the server 502 such as a remote dashboard 510 to view the status of connected nodes and devices, and to send commands remotely.

[0073] In one or more embodiments, a wireless communication device, such as a cellular telephone, two-way radio, personal digital assistant (PDA), personal computer (PC), laptop computer, home entertainment equipment, RFID reader, RFID tag, etc. may be used as a remote dashboard 510 that communicates directly or indirectly with any centralized unit. [0074] As depicted in the FIG. 6, the separate centralized unit could be configured as an IoT-based gateway 102 by making the connected gateway 102 as a set of sub-nodes, in accordance with some embodiments. As shown in the FIG. 6, in accordance with some embodiments, there may be one or more gateways 102-A-n (from sets of nodes and gateways 662-666) coupled to the first centralized unit 606, where each gateway is communicatively coupled with one or more nodes. The centralized unit 606 is communicatively coupled to data server 602 for storing data in real-time. Information from nodes and gateways from sets of nodes and gateways 662-666) may be obtained from the centralized unit 606 and viewed through dashboard 614. In accordance with some embodiments, second gateway 102-(A-n) (from sets of nodes and gateways 668-672) is coupled to the second centralized unit 610, where each gateway is connected with one or more nodes. Also, the centralized unit 606 is communicatively coupled to data server 612 for storing data in real-time. Information from nodes and gateways from sets of nodes and gateways 668-672) may be obtained from the centralized unit 606 and viewed through dashboard 616. There may be another centralized unit 608 to which data server 602 and dashboard 618 may be coupled. FIG. 6 depicts the architecture when there may be more than one gateway 102 coupled to the first centralized unit 606 and the second centralized unit 610, respectively. More than one centralized unit (that is he central unit 606, the central unit 608 and the central unit 610) is connected to the internet 650 via wired or wireless communication protocol to establish communication between more than one centralized unit. Remote dashboards 614, 616, 618 and such remote dashboards may be connected, in some embodiments. If there is a failure of internet 650, each of the individual networks coupled to corresponding centralized units continue to function.

[0075] Furthermore, as depicted in FIG. 7, in accordance with some embodiments, first set of nodes connected to a gateway 1 102-A. The gateway 1 102-A is connected to a first local dashboard 110. Second set of nodes connected to a gateway 2 102-B. The gateway 2 102-B is connected to a second local dashboard 110. The gateway 1 102-A and the gateway 2 102-B are connected to the Internet. One or more user devices 702, such as mobile device, laptop, PDA and the like, are connected to the first and second gateways via the Internet. One or more nodes are connected to gateway 102 could directly connect to the Internet. By using these features, the described addressable data communication system could be expanded to an IoT-based addressable data communication system. The remote dashboard may be connected, in some embodiments.

[0076] FIG. 8 depicts method steps for implementing the addressable data communication unit using Radio Frequency (RF) communication, in accordance with some implementations. Method steps includes monitoring a status of appliance 120, receiving sensor data from at least one sensor device 106, generating addressable data from at least one of the sensor data, communicating the addressable data wirelessly through bi-directional long-range and low power RF wireless communication, receiving and processing the addressable data based on verifying the unique ID in the addressable data, providing the processed data for display on a dashboard 110 of a user interface, communicating at least one of an automated command and a user defined command to the at least one node to control the appliance, and executing the at least one of the automated command and the user defined command to initiate the at least one controller device 108 to perform an action to control the appliance.

[0077] At step 802, according to some embodiments, a status of appliance, for example home appliances, electronic consumer appliances and such, are monitored by at least one sensor device 106 communicatively coupled to the appliance 120. The sensor device 106 may be one or more sensors, such as temperature sensors, and may be implemented within the system. The sensor device 106 may keep monitoring the current status of such appliance. [0078] At step 804, according to some embodiments, sensor data from the at least one sensor device 106 is received by at least one sensor node. Each sensor node has a unique ID and is communicatively coupled to the at least one sensor device 106. [0079] At step 806, according to some embodiments, addressable data from the at least one of the sensor data is generated by the at least one node 101. Upon receiving the sensor data from the sensor device 106s, the at least one node 101 is configured to generate a data package with the addressable data that has to be communicated further.

[0080] At step 808, according to some embodiments, the addressable data is communicated wirelessly through a bi-directional long-range and low power RF wireless communication by the at least one node. In one implementation, the communication may be established upon receiving a request from the at least one gateway 102 having a unique ID. In another implementation, the communication may be established individually between the at least one node and the at least one gateway 102 having a unique ID without receiving a request from the at least one gateway 102.

[0081] At step 810, according to some embodiments, the addressable data is received and processed, by the at least one gateway 102, based on verifying the unique ID in the addressable data.

[0082] At step 812, according to some embodiments, the processed data is provided for display on a dashboard 110 of a user interface through a display device.

[0083] At step 814, according to some embodiments, at least one of an automated command and a user defined command to the at least one node to control the appliance is communicated by the at least one gateway 102 through the bi-directional long-range and low power RF wireless communication.

[0084] At step 816, according to some embodiments, the at least one of the automated commands and the user defined command is executed by the at least one node, based on the unique ID of the gateway 102. Upon execution, the at least one controller device 108 can initiate a step of performing an action to control the appliances.

[0085] The above-described hardware description is a non-limiting example of corresponding structure for performing the functionality described herein.

[0086] Obviously, numerous modifications and variations of the present disclosure are possible in light of the above teachings. Therefore, it is to be understood that within the scope of the appended claims, the disclosure may be practiced otherwise than as specifically described herein.