Claims:We Claim:
1. A system comprising:
a Central Controller 101 comprising at least of processing unit and a storage unit, wherein the Central Controller 101 is configured to:
communicate with a Sensor Gateway 102;
communicate with a Sensor Device 103 via a Sensor Gateway 102;
receive and transmit instructions to a mobile or a web App; and
the communication being encrypted over wired or Radio Frequency communication links.

2. The system of claim 1, wherein the Central Controller 101 comprises of single server or in high availability mode with load balancing capabilities.

3. The system of claim 1, wherein the Sensor Gateway 102 is configured to collect data from Sensor Devices 103.

4. The system of claim 1, wherein the Sensor Device 103 is an analog or digital sensor with current or voltage output.

5. The system of claim 1, wherein the Central Controller 101 is configured to connect to multiple Sensor Gateways 102; and Sensor Gateways are configured to connect to multiple Sensor Devices 103.

6. The system of claim 1, wherein the Sensor Gateway 102 is configured to carry preliminary analysis of the data received from the Sensor Device 103 and to discard anomalies and outlier data.

7. The system of claim 1, wherein the App is configured to communicate with the Central Controller 101, or with the Sensor Gateway 102 or with the Sensor Device 103.

8. The system of claim 1, wherein the Sensor Device 103 is configured send last gasp signal to the Sensor Gateway 102 before the Sensor Device 103 battery is discharged.

9. The system of claim 1, wherein the Central Controller 101 and the Sensor Gateway 102 are configured such that either of them can initiate the sync process for making the Central Controller aware of the entire state of the system at any given instance of time.

10. The system of claim 1, wherein the App is configured to add or remove Sensor Gateway 102 or Sensor Device 103 from monitoring the external parameters.

11. A method comprising:
Obtaining and analysing external parameters data within a cloud computing platform wherein at least one Sensor is connected to a Gateway, which is communicating with the Cloud computing platform.

12. The method of claim 11, wherein the Cloud computing platform instructs the gateway or the sensor.

13. The method of claim 11, wherein the App instructs the Cloud computing platform either to monitor a parameter or to discontinue monitoring of a parameter.

14. The method of claim 11, wherein all the communication between the App and Cloud computing platform is encrypted. , Description:
System and Method for Interconnecting Sensors & Devices to Intelligent Applications for Detection, Analysis and Control

Field of Invention and Use of Invention:

This invention relates to the field of communication and networking with integration of sensors and control devices to intelligent software application. The invention is related the Internet of Things (IoT) field.

The invention is used in automation of detection of climatic conditions, fluid level and weight/mass, movement of humans and non-humans. The invention uses detection and its analysis based on set of rules to control devices to affect output and to either grant or restrict access to humans or non-humans.

Prior Art and problem to be solved:

The Internet of Things is a network of sensors, control devices, software application and communication technology. The IoT involves three major steps: capturing of data via sensors, collection of data at a central server, analyzing the data, decision based on data and conveying the decision to actuators.

The IoT essentially comprises of three layers – the Sensor Layer, the Communication Layer and the Application Layer, all interacting with each other simultaneously. The Sensor Layer comprises of sensors to detect and capture the physical parameter to be monitored or controlled. The Communication Layer comprises of network Study of the prior art reveals that every invention has solved only a portion of the IoT problem focusing only on one or two of the three layers. Some of the prior art has tried to solve problems related to all the three layers but have failed to address the core issue of optimising all the three layers for effective performance of the system.

Problems with prior art:

Acceptance of a ubiquitous high speed network: The first problem with the prior art is that majority of the prior art have generally accepted presence of high speed network connecting sensor layer to application layer. Such an assumption is not valid in the rural areas of large countries such as India, China and even countries of African and South American continents. The prior art has not solved the problem of interconnection of Sensor Device with intelligent central analytical process for data analysis and decision making.
Assumption of Reliable Network: The state of art invention assumes a reliable network for connectivity between the Sensor Device and the Central Controller. This assumption does not hold true for remote locations in hilly and desert areas. The prior art has not solved the problem of unreliable network.

High power requirement of Sensor Devices: In the state of art inventions, controller devices connected to sensors for collecting data or for instructing the actuators or consumption devices are not optimized for low power consumption or for longer operation on battery power.

Transmission of entire raw data to central processing server: The controller devices connected to the sensors transmit entire raw data to the central processing server without any data massaging which causes irrelevant and unnecessary data to traverse the network.

Requirement of manual registration of devices to the service gateway: In the prior art, the large numbers of Sensor Devices are required to be registered manually with the central repository. This requirement is a huge burden and cost for the management of the Sensor Devices.

The invention described in US 8,984,113 B2 discloses the architecture of the IOT and the method for implementing the architecture. The invention does not disclose how the system shall operate in a low bandwidth and/or intermittently available communication work. The invention is silent in regards to the real world scenario where a single central server shall be controlling sensors and devices belonging to different administrative groups and requiring independent and autonomous control within its own private group. The disclosed invention does not show how the architecture is capable of handling low bandwidth communication environment.

The present invention discloses a system based on a cloud based platform wherein the Sensor Gateway 102 communicates with subordinate end devices being actuators and Sensor Device 103 which are monitored or controlled by the user application in the mobile device and where the mobile device is communicating with the central server in the cloud over the encrypted communication network.

Objects of the invention:

The principal object of this invention is to build and deploy a system comprising of sensors and end devices connected to the controllers send their data or receive instructions from the central server which is communicating with mobile devices used for monitor and control of external parameters or conditions. Another object of the invention is to optimize the deployment of the system in low bandwidth or intermittent network areas for effective monitor and control of external parameters or conditions. Further object of the invention is to utilize Sensor Device 103s and control devices powered by batteries for longer duration by use of wake up and dead or alive signals to and from the controllers. Another object of the invention is to restrict outlier or anomalous data and other irrelevant data to be sent to central server for processing.

Summary of the invention:

The problem to be solved in the present invention is to provide a system for the deployment of sensors/actuators, controllers, central processors and mobile devices connected to each other through a communication system and to provide configuration, monitoring and control of physical parameters and external conditions.

The invention is a system comprising of following entities: (i) Sensor Device 103s, (ii) Sensor Gateway 102s, (iii) end user devices or actuator based devices, (iv) controllers connected to sensors and end user devices, (v) Cloud Computing platform, (vi) communication network, (vii) Mobile Application.

The Sensor Device 103s form the lowest layer of the system. The Sensor Device 103s are connected to a Sensor Gateway 102. The Sensor Gateway 102 collects and converges all the sensor data. The Sensor Gateway 102 performs data massaging and then forwards the data to the central server in the cloud for near real time data analysis. The central server performs data analysis using pre-configured rules or using Artificial Intelligence. The central server based on the rules, carries out subsequent automatic action on the actuator devices or forwards the information to mobile device for manual intervention. The invention uses both broadband (WiFi, 4G, 3G etc) as well as narrowband (GPRS, SMS, Zigbee, Bluetooth etc) technologies for communication.

A Sensor Gateway 102 is capable of connecting up to 2^n devices, n being 8 or 16. The Sensor Gateway 102 is capable of connecting to at least one Sensor Device 103 and to an actuator device. The Sensor Gateway 102 is capable of monitoring the health of Sensor Device 103s or actuator devices by sending keep alives or receiving last gasp signal from the end devices. This mechanism helps in conserving the power consumption of the controller when the controller is battery powered.

The Sensor Gateway 102 performs data massaging of the signals received from the sensors and only forwards relevant data to the central server thereby reducing traffic bandwidth on communication network.

The Central Processor performs analysis of the data received from the sensors and either informs the mobile device or performs an action on the analysed data based on pre-configured rules or Artificial Intelligently and thereafter informs the mobile device.

The mobile device hosts a mobile app for configuration, monitoring and control of sensor and actuator devices. The mobile app is an integral component of the system. The rules for action based on analysis of data are configured from the mobile app.

Brief Description of Drawings:

Fig 1 illustrates the layers of the system – Sensor Layer, Sensor Gateway 102 Layer and Central Controller 101 Layer along with Mobile app layer;

Fig 2 is the flow diagram of Sensor Device 103 communicating with Sensor Gateway 102 according to an embodiment of the present invention;

Fig 3 illustrates the complete flow diagram of Sensor Device 103 communication with the Central Controller 101 via the Sensor Gateway 102;

Fig 4 is the flow diagram of Sensor Gateway 102 registration with Central Controller 101;

Fig 5 is the flow diagram of the mobile app or the desktop application registration and communication with the Central Controller 101;
Fig 6 is a model layout of the mobile app and the desktop application

Detailed Description:

The detailed description of the invention will be described in detail below with reference to the drawings. FIGS. 1 through 6, discussed below, and the various embodiments used to describe the principles of the present invention in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the invention. Those skilled in the art will understand that the principles of the invention may be implemented in any type of suitably arranged system.

Fig 1. Illustrates the three layers of the System.

The entire ecosystem is built up by first deploying the Central Controller 101 101. The Central Controller 101 is the heart and brain of the entire system. The Central Controller 101 is pre-configured with software and applications to register and communicate with the Sensor Gateway 102 and Sensor Device 103. It must be pointed out that condition to requirements, the Central Controller 101 may be a single Server implementation or a redundant Server implementation with load balancing and high availability. The actual physical and logical implementation of the Central Controller 101 may vary as per the requirements. The Central Controller 101 comprises of at least one storage device connected to it.

The second step in creation of the ecosystem is the deployment of Sensor Gateways 102. The Sensor Gateway 102 form the second layer in the three tier-system and are deployed as required to places where the external conditions have to be monitored. The Central Controller 101 communicates with Sensor Gateway 102 via the communication link 104. The communication link between the Central Controller 101 and the Sensor Gateway 102 may comprise of a high bandwidth IP based network, or a point-to-point link using GPRS or any radio frequency communication or may even be a dial up network.

The Sensor Gateway 102 connects the Sensor Device 103 to the Central Controller 101. The Sensor Gateway 102 is used to converge all the data coming from the Sensor Device 103. The Sensor Gateway 102 comprises of a two way communication i.e. a) with the Central Controller 101 via communication link 104 and b) with Sensor Device 103 via communication link 105.

The Sensor Gateway 102 comprises of a northbound communication link (i.e. to the Central Controller 101 and a southbound communication link to the Sensor Device 103. The Sensor Gateway 102 is configured to gather updates from the Sensor Devices 103 regarding their health status – power status, battery status, type of sensor i.e. whether a current or a voltage sensor, or a digital or an analog sensor.

Sensor Devices 103 is the third layer of the three-tiered system and comprises of an inbuilt sensor or connected to a sensor having electrical output in form of electrical voltage or current. Sensor Devices 103 are uniquely identified with an identifier, which may be a MAC address or any other proprietary address of 16/32 bits. Sensor Devices 103 are paired with the Sensor Gateway 102 using physical proximity only. The Sensor Devices 103 and the Sensor Gateway 102 comprise of pairing buttons on each of their outer physicality. To ensure strict security and no leakage of Sensor Device 103 connectivity to an unauthorized Sensor Gateway 102, the clever method of pairing the Sensor Gateway 102 with the Sensor Device 103 of physical proximity is adopted.

The Sensor Device 103 also comprises of applications running to gather the external environmental conditions and performs operations, which help with clustering, filtering, smoothening and analysing the sensor data for accuracy and validation. An individual Sensor Device 103 is configured to send trigger to the Sensor Gateway 102 based on an external event. The event may be a change in temperature, weight or flow of fluid or even a movement. Along with the external events, the Sensor Devices 103 are configured to update their power status, the health status in form of dead or alive messages. The Sensor Devices 103 may also be attached to an actuator to perform the commands as instructed by the Central Controller 101. The actuator may be a mechanical, electro-mechanical or a software-controlled device.

Fig 2 is an illustration of the communication between the Sensor Gateway 102 and Central Controller 101. The communication between Sensor Gateway 102 and Central Controller 101 is carried over an encrypted and secured northbound communication link 104. In other examples, the northbound communication link may be unencrypted and unsecured.

Sensor Gateway 102 when powered up gets connected to the network, and sends a Registration Request 201 to the Central Controller 101. The Central Controller 101 is pre-configured with the details of Sensor Gateway 102 as per client requirements. The Central Controller 101 carries the authentication and verification of the Sensor Gateway 102. The Central Controller 101 carries out authentication for every Sensor Gateway 102 powered up and connected to the communication network. The Central Controller 101 either on successful authentication or otherwise, replies with either a positive acknowledgment or a Nack. On positive authentication, the Central Controller 101 sends the required Meta Data to the Sensor Gateway 102.

The Sensor Gateway 102 forwards the updates from the Sensor Device 103, which is shown in Fig 2 as messages 203 Sensor Updates. The Sensor Gateway 102, before forwarding the updates carries out primary analysis for discarding anomalous and outlier readings from the Sensor Devices 103. This innovative feature helps in reducing the bandwidth consumption on the northbound link 104. This feature helps in a robust communication mechanism even on low and unreliable bandwidth communication links.

The Sensor Device 103 sends a Sensor Gateway 102 to Controller sync request 205, which is replied via a Ack/Nack/Meta Data 206. In an event, where the Central Controller 101 has lost communication with the Sensor Gateway 102 due to any reason such as power failure at the Sensor Gateway 102 site or loss of communication link, the Central Controller 101 sends a sync request to the Sensor Gateway 102. This mechanism helps to ensure that the Central Controller 101 knows the state of the Sensor Gateway 102 at any given instance of time.

Based on the Sensor Update, the Central Controller 101 sends an Action Request 209 to the Sensor Gateway 102. The Action Request is meant for the Sensor Device 103 or the actuator device to carry out certain actions.

Fig 3 illustrates the communication flow between the Sensor Device 103 and the Sensor Gateway 102.

One or more Sensor Device 103 may be connected to the Sensor Gateway 102. A Sensor Device 103 may be connected wirelessly or via a wired interface. The Sensor Device 103 to Sensor Gateway 102 communication is in three phases. First is the Registration Phase. During Registration, the pairing of a Sensor Device 103 with the Sensor Gateway 102 is carried out in close proximity. The pairing buttons on the Sensor Device 103 and the Sensor Gateway 102 pressed simultaneously. Thereby the Sensor Device 103 sends a Pairing Request 301 to Sensor Gateway 102. The Sensor Gateway 102 has a repository of Sensor Device 103 IDs, which are obtained from the Central Controller 101. In another embodiment, the Sensor Device 103 IDs are generated locally by the Sensor Gateway 102 and are made unique by either a prefix or a suffix.

In the normal operation phase, on the occurrence of an event, the Sensor Device 103 sends the event update to the Sensor Gateway 102. The Sensor Gateway 102 upon receipt of information from the Central Controller 101 informs the Sensor Device 103 regarding sensor actuation or update via the message 306.

The third phase of the Sensor Device 103 and Sensor Gateway 102 is the Dead/Alive or last gasp communication. The innovative feature allows for the Sensor Device 103 to send a last gasp before its battery is discharged to the Sensor Gateway 102 via message 308. The feature allows for conservation of energy at the Sensor Gateway 102 and reduction in polling cycles from the Sensor Gateway 102 to the Sensor Device 103.

Fig 4 illustrates the flow diagram of communication between the Sensor Device 103, Sensor Gateway 102 and Central Controller 101. The communication between Sensor Device 103 and Sensor Gateway 102 is similar to that of Fig 3. Fig 4 shows that in the normal operation phase, the Sensor Gateway 102 carries out the Analysis and massaging via message 405. During the Last gasp operation, the Sensor Gateway 102 forwards the Sensor Device 103 information to the Central Controller 101. Thus the Central Controller 101 is always aware of the state of every Sensor Device 103 in the system.

Fig 5 illustrates communication flow diagram between the App (Mobile or web based) and the Central Controller 101. The App sends a message 501 for registration and credential check. The Central Controller 101 validates and authenticates the App and replies with Ack/Nack/Meta Data. The communication between the Central Controller 101 and App is event triggered so as to save on bandwidth. Although, in some of the embodiments, an App may keep requesting the Central Controller 101 with a constant request for updates. The App sends a request 413 for Data Refresh from the Central Controller 101. The App has notification pushed by the Central Controller 101 and may request an action with a request 509.

Fig 6 illustrates the layout of the App on a mobile device as well as on a web page.

While this disclosure has described certain embodiments and generally associated methods, alterations and permutations of these embodiments and methods will be apparent to those skilled in the art. Accordingly, the above description of example embodiments does not define or constrain this disclosure. Other changes, substitutions, and alterations are also possible without departing from the spirit and scope of this disclosure, as defined by the following claims.