GB2609227A

GB2609227A - Gateway module

Info

Publication number: GB2609227A
Application number: GB2110634.9A
Authority: GB
Inventors: Owen Duffy Anthony; Hamer Malcolm
Original assignee: AXON SYSTEMS Ltd
Current assignee: AXON SYSTEMS Ltd
Priority date: 2021-07-23
Filing date: 2021-07-23
Publication date: 2023-02-01
Also published as: GB202110634D0

Abstract

A module for use in an internet of things (IoT) computing system comprising a data communication means and a data processing means configured to perform an IoT gateway function and a device controller function. The IoT gateway function is configured to receive control data from a remote computing system and communicate it to the device controller function. The device controller function converts the control data into control instructions and controls the devices by communicating the control instructions. These devices may be sensors, switches and controls associated with an HVAC system in buildings. The invention may comprise a motion sensor and a carbon dioxide sensor. It may alert when too many people are in the room (e.g. increased CO2) or switch off when no motion is detected. CO2 monitoring can be used to indirectly monitor the risk of the spread of diseases by airborne particles, as increased co2 implies stale air. It may be configured to undertake security and authentication functions on high level control data. It may be provided in a ruggedised enclosure and be mounted in/near a building vent.

Description

GATEWAY MODULE

Technical Field

The present invention relates an Internet of Things gateway module.

Background

"Internet of Things" (loT) systems are increasingly widely used as they provide a very convenient means for remotely monitoring and controlling devices and systems. In particular, loT systems allow otherwise conventional computing equipment, such as internet connected devices like personal computers, tablets, smartphones and so on, running conventional web browsing software, to provide the remote monitoring and control functionality.

loT systems can be particularly useful in certain settings, for example in settings involving the control of internal environments, such as the internal spaces of buildings. Such systems may typically comprise many systems and sub-systems which themselves comprise many devices such as sensors (such as temperature, heat, light and humidity sensors) and switches, actuators and other control equipment for heating, ventilation and air conditioning (HVAC) systems.

Conventionally, integrating loT systems into systems such as HVAC systems requires deploying substantial amounts of complicated and expensive equipment including customised data gateways for communicating data to and from remote computing systems, and the provision of customised device controllers which act as an intermediary between the devices and the data gateways. As well as the expense, these devices can consume considerable amounts of power to run the complicated data processing tasks that they undertake, so they typically need to be physically connected to the power supply of the location in which they are deployed.

It is an aim of certain embodiments of the invention to address some of these difficulties.

Summary of the Invention

In accordance with a first aspect of the invention, there is provided a module for use in an loT system, said module comprising a stand-alone device comprising a data processing means and data communication means, said data processing means configured to perform an loT gateway function and a device controller function. The loT gateway is function configured to receive, via the data communication means, control data from a computing system and communicate the control data to the device controller function. The device controller function is configured to convert the control data into control instructions and control one or more devices by communicating the control instructions, via the data communication means, to the one or more devices.

Optionally, the device controller function is configured to receive, via the data communication means, from the one or more devices, output signals and convert the output signals to output device data and communicate the output data to the loT gateway function, wherein the loT gateway function is configured to communicate, via the data communication means, the output device data to the computing system.

Optionally, the module further comprises an expansion port for connecting to the module loT device hardware.

Optionally, upon connecting of loT device hardware to the expansion port, the module is configured to operate as a loT endpoint.

Optionally, the module comprises a real-time clock enabling the device controller function to control the one or more devices in accordance with a real-time clock signal.

Optionally, the module is powered by a photovoltaic cell.

Optionally, the data communication means comprises at least a wireless data transceiver.

Optionally, the data communication means comprises at least a data port for receiving a wired data communication line of a first type.

Optionally, the module comprises a power input means for receiving power via the data port.

Optionally, the data port is an Ethernet data port.

Optionally, the data communication means comprises at least one further data port for receiving a wired data communication line of a second type.

Optionally, the at least one further data port is an RS485 data port.

Optionally, the module further comprises a daughter board connected to the expansion port, said daughter board comprising one or more sensors.

Optionally, the one or more sensors comprise a carbon dioxide sensor for detecting a level of carbon dioxide present in air in the vicinity of the sensor.

Optionally, the one or more sensors further comprise a motion detector.

Optionally, the one or more sensors further comprise an air pressure detector for detecting airflow in a vent Optionally, the module is configured to be housed in an enclosure.

Optionally, the enclosure is a 'rugged' enclosure.

Optionally, the enclosure has suitable form factor to allow mounting to a ceiling.

Optionally, the enclosure has suitable form factor to allow mounting to a vent.

Optionally, the enclosure has suitable form factor to allow mounting to a consumer unit.

Optionally, the computing system is a remote computing system.

According to a second aspect of the invention there is provided an loT system comprising the module according to the first aspect, one or more devices and a computing system, wherein the loT gateway function of the module is configured to receive, via the data communication means of the module, control data from the computing system and communicate the control data to the device controller function of the module, said device controller function configured to convert the control data into control instructions and control the one or more devices by communicating the control instructions, via the data communication means, to the one or more devices.

Optionally, the computing system is a remote computing system.

Optionally, the one or more of the devices comprise one or more further modules, further comprising an expansion port to which is connected loT device hardware and the one or more further modules operate as loT endpoints.

In accordance with certain embodiments of the invention, a gateway module is provided for use in loT systems. The gateway module is provided as a single, standalone device which incorporates both loT gateway functionality and device controller functionality. In conventional loT systems this functionality is typically distributed across several devices. Providing a modified gateway module in this way means that loT type functionality can be more easily, conveniently and cost-effectively deployed. Such a module can act as a combination of device controller and gateway, standalone gateway, and in certain embodiments can be modified to act as an loT end-point device itself.

Advantageously, in accordance with certain embodiments of the invention, the gateway module comprises an expansion port which enables the gateway module to, itself, be deployed as a device end point in an loT system.

Advantageously, in certain embodiments, such a gateway module can be adapted to implement a wall mounted, ceiling mounted or vent mounted carbon dioxide sensor which can be used to generate carbon dioxide readings which can be used to infer a level of risk in an environment of the transmission of airborne diseases.

Advantageously, in certain embodiments, such a gateway module can be configured to have a suitable form factor to allow mounting of said gateway module to a consumer unit.

Various further features and aspects of the invention are defined in the claims.

Brief Description of the Drawings

Embodiments of the present invention will now be described by way of example only with reference to the accompanying drawings where like parts are provided with corresponding reference numerals and in which: Figure 1 provides a simplified schematic diagram depicting a conventional loT system; Figure 2 provides a simplified schematic diagram depicting a loT system arranged in accordance with certain embodiments of the invention, Figure 3 provides a simplified schematic diagram depicting components of a gateway module arranged in accordance with certain embodiments of the invention; Figure 4 provides a simplified schematic diagram depicting a gateway module arranged in accordance with certain embodiments of the invention and in particular including a carbon dioxide sensor daughter board; Figure 5a provides a simplified schematic diagram depicting components of a carbon dioxide sensor daughterboard for a wall mounted carbon dioxide sensor in accordance with certain embodiments of the invention; Figure 5b provides a simplified schematic diagram depicting components of a carbon dioxide sensor daughterboard for a vent mounted carbon dioxide sensor in accordance with certain embodiments of the invention; Figure 5c provides a simplified schematic diagram depicting an example deployment of such a vent-mounted carbon dioxide monitoring unit.

Figure 5d provides a simplified schematic diagram depicting an example deployment of a vent-mounted carbon dioxide monitoring unit corresponding to that shown in Figure 5c except that a supply fan is used in place of an extract fan; Figure 6 provides a simplified schematic diagram depicting an implementation of an loT system in in accordance with an exemplary embodiment of the invention; Figure 7 provides a simplified schematic diagram depicting a plurality of gateway modules arranged in accordance with an embodiment of the invention; Figure 8 provides a simplified schematic diagram of a system arranged in accordance with an exemplary embodiment of the invention; Figure 9 provides a simplified schematic diagram depicting a ceiling mounted loT system arranged in accordance with an embodiment of the invention, and Figure 10 provides a simplified schematic diagram depicting an loT system arranged in accordance with an embodiment of the invention implemented in a consumer unit.

Detailed Description

Figure 1 provides a simplified schematic diagram of a conventional loT system 101.

The loT system 101 is distributed across a local location 102 and a remote location 103.

Located in the local location 102 is an loT gateway 104 which is connected via a data network 105 to a remote computing system 106. Further located at the local location 102 is a first device controller 107a and a second device controller 107b both of which are connected to the loT gateway 104.

The first device controller 107a is connected to a first device 108a and a second device 108b. The second device controller 107b is connected to a third device 108c and a fourth device 108d In operation, the remote computing system 106 has running thereon loT monitoring and control software. Under the control of this monitoring and control software, the remote computing system 106 generates high level control data which is communicated by the data network 105 to the loT gateway 104. This high-level control data can be input to the remote computing system 106 by an operative via an interface provided by the monitoring and control software.

The loT gateway 104 is configured to undertake security functions and authentication functions on this high-level control data and, where appropriate, communication protocol conversion functions. The loT gateway 104 is configured to then communicate control instructions corresponding to the high-level control data to the device controllers 107a, 107b.

These control instructions provide the device controllers 107a, 107b with instructions for controlling the operation of the devices 108a, 108b, 108c, 108d. Accordingly, the device controllers 107a, 107b are configured to communicate control signals to the devices 108a, 108b, 108c, 108d corresponding to the control instructions. The devices 108a, 108b, 108c, 108d then operate in accordance with the control signals.

Output signals generated by the devices 108a, 108b, 108c, 108d, for example sensor signals, are communicated from the devices 108a, 108b, 108c, 108d to the device controllers 107a, 107b. The device controllers 107a, 107b are configured to process the output signals to generate corresponding sensor data. This is typically undertaken in accordance with processing instruction provided in the control instructions. The sensor data is then communicated back to the loT gateway 104.

The loT gateway 104 then performs security and authentication functions on the sensor data and, where appropriate, communication protocol translation functions. The loT gateway 104 then communicates corresponding high level device output data to the remote computing system 106. This high-level device output data can then, for example, be accessed by an operative via the interface.

Figure 2 provides a simplified schematic diagram of modified loT system 201 arranged in accordance with certain embodiments of the invention.

The modified loT system 201 corresponds to the conventional loT system 101 described with reference to Figure 1 except that the loT gateway and device controllers are replaced by a single gateway module which incorporates functionality associated with the loT gateway and device controllers in a single device.

Specifically, the modified loT system 201 depicted in Figure 2 comprises a local location 202 (such as a building) and a remote location 203. Located in the local location 202 is a gateway module 204 which comprises an loT gateway function 205 and a device controller function 206. Connected to the gateway module 204 are a first device 207a, second device 207b, third device 207c and a fourth device 207d.

In certain embodiments, these devices may be sensors, switches and controls associated with 25 an HVAC system.

The gateway module 204 is connected via a local data network 213 and an onward data network 208 to a remote computing system 209 located in the remote location 203. The data network 208 is typically provided by the combination of telecommunications networks that together comprise the "internet" including, for example fixed line and mobile telecommunications networks. The gateway module 204 is typically equipped with data communication means for sending and receiving data via fixed (wired") data connections and wireless data connections.

In operation, in keeping with the conventional loT system 101, the remote computing system 209 has running thereon loT monitoring and control software. Under the control of this monitoring and control software, the remote computing system 209 generates high level control data which is communicated by the data network 208 to the gateway module 204. Again, in keeping with the conventional loT system 101, this high-level control data can be input to the remote computing system 209 by an operative via an interface provided by the monitoring and control software.

The gateway module 204 comprises data processing means which is configured to perform an loT gateway function 205 which undertakes operations equivalent to those performed by the loT gateway 104 in the conventional loT system 101.

Specifically, the loT gateway function 205 is configured to undertake security functions and authentication functions on the high-level control data received from the remote computing system 209 and, where appropriate, communication protocol conversion functions. The loT gateway function 205 is then configured to communicate these control instructions to the device controller function 206.

These control instructions define how the plurality of devices 207a, 207b 207c and 207d are to be controlled and how data received from the plurality of devices is to be processed and returned to the remote computing system 209.

The device controller function 206 is configured to generate and communicate control signals to the plurality of devices 207a, 207b 207c and 207d in accordance with the control instructions from the loT gateway function 205. The plurality of devices 207a, 207b 207c and 207d then operate in accordance with the control signals.

Output signals generated by plurality of devices 207a, 207b 207c and 207d, for example sensor signals, are communicated back to the gateway module 204 and are processed by the device controller function 206. Specifically, the device controller function 206 is configured to generate corresponding output device data, such as sensor data in accordance with the control instructions. This data is then communicated to the loT gateway function 205. The loT gateway function 205 then performs security and authentication functions on this device data (e.g., sensor data) and, where appropriate, communication protocol translation functions. The gateway module 204 then communicates corresponding high level device output data to the remote computing system 209 via the data network 208. This high-level device output data can then, for example, be accessed by an operative via the interface.

In certain examples, the loT gateway function 205 includes software enabling the gateway module 204 to "serve" web pages to the remote computing system 209. Correspondingly, the software running on the remote computing system 209 provides a web browser for receiving the served web pages and enabling them to be displayed via a suitable display device of the remote computing system 209. As will be understood, such an arrangement can provide the means by which the high-level control data can be communicated to the gateway module 204 from the remote computing system 209 and can also provide the means by which the high-level device data is communicated from the gateway module 204 to the remote computing system 209.

The data processing means of the gateway module 204 is configured to further implement a third party controller interface function 210.

The third party controller interface function 210 is configured to receive control instructions from a third party controller 212 located in the local location 202.

The third party controller 212 is typically provided by a conventional third party controller, for example, any building automation systems (BAS) or building management systems controllers, which support open source methods of communication such as BACnet or Modbus communication protocols. An example of such a controller is a building automation and control (BAC) PLC.

The third party controller 212 is connected to the gateway module 204 via a suitable signal line (for example an Ethernet cable). The third party controller interface function 210 is configured to enable output signals from the plurality of devices 207a, 207b 207c and 207d to be communicated to the third party controller 212 and to enable control data to be communicated from the third party controller 212 to the plurality of devices 207a, 207b 207c and 207d. The third party controller interface function 210 is configured to communicate data to and from the third party controller 212 in accordance with a suitable communication protocol such as Modbus or BACnet.

The system further comprises a local computing system 211 which can substantially correspond to the remote computing system 209 except that it is connected to the gateway module 204 via the local data network 213, which may be situated within the local location.

The local computing system 211 has running thereon loT monitoring and control software.

Under the control of this monitoring and control software, the local computing system 211 generates control instructions which are communicated, via the local data network 213, to the gateway module 204. The loT gateway function 205 is configured to communicate these control instructions to the device controller function 206 which is configured to control the plurality of devices 207a, 207b 207c and 207d in accordance with these control instructions and, where appropriate, communicate output data from the plurality of devices 207a, 207b 207c and 207d to the local computing system 211.

Data is typically communicated on the local data network 213 and the data network 208 in accordance with the TCP/IP data communication protocol. In certain examples, devices of the plurality of devices, if equipped with suitable data communication ports, can communicate data to and from the gateway module 204 via a connection to the local data network 213.

Figure 3 provides a simplified schematic diagram showing in more detail a gateway module 301 arranged in accordance with certain embodiments of the invention.

The gateway module 301 comprises a data processor 302 (provided by any suitable data processing means) connected to which is a memory 303.

The data processor 302 is further connected to a cellular network transceiver 304 (comprising a subscriber identity module 305), a first wired data port 306a of a first type, a second wired data port 306b of a second type, a first wireless data transceiver 307a of a first type and a second wireless data transceiver 307b of a second type.

The gateway module 301 further comprises a power input port 308. The data processor 302 is further connected to a real time clock module 309 and an expansion port 310.

The memory 303 has stored thereon executable instructions for implementing the loT gateway function 205, device controller function 206 and third party controller interface function 210.

The cellular network transceiver 304 enables the gateway module 301 to communicate data to and from the remote computing system 209 via a PLMN (Public Land Mobile Network cellular mobile telecommunications network).

The first wired data port 306a is typically provided by an Ethernet port (for example an RJ45 Ethernet port) and provides a means to connect to the local data network 213 as described above. This connection enables data to be communicated to the remote computing system 209 via a fixed ("wired") connection, and also enables data to be communicated to and from suitably equipped devices via the local data network 213.

The second wired data port 306b, provides a means by which data can be communicated in accordance with a further data communication protocol. For example, the second wired data port 206b may be provided by a RS 485 port enabling data to be communicated to and from the plurality of devices 207a, 207b, 207c, 207d using a suitable industrial automation data communication protocol such as BACnet over MSTP, Modbus or MQTT.

In the example depicted in Figure 3, the gateway module 301 comprises a single wired data port of the first type, and a single wired data port of the second type. However, in other embodiments, more than one (multiple) wired data ports of the first type and/or more than one (multiple) wired data ports of the second type may be provided. Further, one or more further wired data ports of further types may be provided. For example, two data ports of the first type (for example RJ45 ports) can be in included. The additional data port of the first type can be used to connect an additional gateway module which also has an additional data port of the first type thereon. In this way, multiple gateway modules can be connected in a 'daisy chain' arrangement which can reduce wiring and installation costs.

The first wireless data transceiver 307a is typically provided by a wireless transceiver configured for communicating data to and from the devices 207a, 207b, 207c, 207d in accordance with a specific low-power communication protocol, for example, the EnOcean protocol.

The second wireless data transceiver 307b is typically configured to communicate data in accordance with a wireless IP protocol such as W-Fi. Data can be communicated to and from the devices 207a, 207b, 207c, 207d (or the third party controller 212) if equipped with a corresponding transceiver (for example a Wi-Fi transceiver). The second wireless data transceiver 307b can also provide a means by which to communicate data to and from the remote computing system via a suitable wireless transceiver in the vicinity (e.g. a W-Fi transceiver in a network router) The power input port 308 provides a means for receiving power into the gateway module 301. The power input port 308 can be configured to receive power from any suitable source, for example a 24V DC source or a 24V AC source. In certain examples, the power input port 308 is configured to receive power from a "standalone" power source such as a solar power source meaning that the gateway module 301 need not be connected to a physical power supply line.

Alternatively, or additionally the power input port 308 can be configured to receive power from a physical power supply line such as a supply line connected to the mains electrical supply. In certain examples the power input port 308 is configured to receive power from an input line such as an Ethernet cable connected to the wired data port 306 (in accordance with "power over Ethernet" (PoE) techniques).

The real time clock module 309 is configured to generate a "real-time" clock signal and communicate this to the data processor 302. In this way, the data processor 302 is able, in accordance with control instructions received from the loT gateway function 205 and third party controller interface function 210, to control the devices in accordance with "real-time" clock values. For example, functions of devices can be activated and deactivated based on the time of day.

In certain examples, certain components of the gateway module 301 may be provided by a single "system-on-chip" microcontroller, such as the ESP32 developed by Espressif Systems, which includes, in an integrated package a microprocessor, memory, suitable wireless transceivers and other components. The ESP32, for example includes integrated Wi-Fi and dual-mode Bluetooth transceivers.

The expansion port 310 enables further hardware modules to be connected to, and thus incorporated in, the gateway module 301. In this way, gateway modules in accordance with embodiments of the invention can be readily modified to become standalone devices themselves.

Such hardware modules can be provided by any suitable type of hardware module, for example: environmental sensors, such as, temperature sensors, humidity sensors, and voc sensors; local display units, which can be provided by one or more visual display units (VDUs), for displaying configuration and sensor data; third party protocol interface modules, such as, OpenTherm Boiler Interface modules, M-Bus Interface modules, and cellular modules for internet connectivity without the need for VVIFI or hardwired Ethernet.

An example of such a standalone device is described further with reference to Figure 4.

Figure 4 provides a simplified schematic diagram of a gateway module 401 arranged in accordance with certain embodiments of the invention.

The gateway module 401 corresponds to the gateway module 301 described with reference to Figure 1 except that the power supply is provided by a photovoltaic power unit 402. The photovoltaic power unit 402 which generates energy from ambient light received by a photovoltaic cell 403 which is input to a capacitor 404 which provides output power for powering the gateway module 401. A back up battery 406 is provided for providing power in the event that ambient light levels are such that sufficient power cannot be generated from the photovoltaic cell.

Further connected to the expansion port 310 is a carbon dioxide sensor daughter board 405. The carbon dioxide sensor daughter board 405 comprises hardware for monitoring levels in carbon dioxide in the vicinity of the gateway module 401.

The carbon dioxide sensor daughter board 405 can be configured to monitor carbon dioxide levels in different settings.

In one example, the carbon dioxide sensor daughter board 405 can be configured so that the gateway module 401 can be deployed as a wall mounted carbon dioxide monitoring unit for monitoring levels of carbon dioxide in a particular environment, such as a room in a building where people congregate. In such an example, the gateway module 401 will be housed in a suitable housing for mounting on a wall.

Such a carbon dioxide monitoring unit can be used to indirectly monitor the risk of the spread of diseases by airborne particles in a particular environment. This is because as the number of people in a space increases, the carbon dioxide concentration increases (this is sometimes referred to as the air becoming "stale"). Moreover, a higher level of carbon dioxide implies a lower level of ventilation (which could indicate ventilation equipment failure). The higher the number of people and the lower the level the ventilation, the greater the risk of diseases spreading by airborne particles.

Figure 5a provides a simplified schematic diagram of a daughterboard arranged in this way.

With reference to Figure 5a, a daughterboard 501a is shown which is configured such that when incorporated in a gateway module of the type shown in Figure 4, the gateway module can be deployed as a wall mounted carbon dioxide monitoring unit.

The daughterboard 501a comprises a carbon dioxide sensor 502 which can be provided by any suitable sensor, for example a "Gas Sensing Solutions (GSS) COZIR-Blink-N" CO2 sensor. The daughter board further comprises a motion detector 503 which can be provided by any suitable motion detector, for example a motion sensor from the Panasonic BKMB series motion detectors.

The daughterboard 501a is configured to receive power via a powerline connected to the photovoltaic power unit 402 power supply of the gateway module 401 via a suitable connection point provided in the expansion port 310.

The carbon dioxide sensor 502 is configured to generate an output signal which is conveyed via a signal line to the data processor of the gateway module 401 via a suitable connection point provided in the expansion port 310. The output signal from the carbon dioxide sensor 502 is indicative of a detected (measured) level of carbon dioxide. The carbon dioxide sensor 502 is configured to receive control signals from the data processor via this signal line.

The motion detector 503 is configured to generate an output signal indicative of detected motion in the vicinity of the gateway module which is conveyed via a signal line to the data processor of the gateway module 401 via a suitable connection point provided in the expansion port 310. The motion detector 503 is also configured to receive control instructions from the data processor via this signal line.

When the gateway module 401 is fitted with a carbon dioxide sensor daughter board 405 of the type described with reference to Figure 5a, the device controller function 206 receives control instructions from the remote computing system 209 or the local computing system 211 to implement a carbon dioxide monitoring function (alternatively, control instructions for implementing such a carbon dioxide monitoring function can be pre-programmed into the gateway module).

In operation, for example, on receiving output data from the motion detector 503 indicative of detected motion in vicinity of the gateway module 401, the carbon dioxide monitoring function, controls the data processor 302 to generate an activation signal which is sent via the expansion port 310 to the carbon dioxide sensor 502. On receipt of the activation signal, the carbon dioxide sensor 502 is configured to begin a carbon dioxide monitoring operation and to generate, and communicate back to the data processor 302, the output signal indicative of a detected level of carbon dioxide.

The carbon dioxide monitoring function running on the data processor 302 is configured to receive the output signal from the carbon dioxide sensor 502. If the output data signal is indicative of "stale air", that is a carbon dioxide level that it is above a predetermined threshold level (set, for example, by the control instructions received from the loT gateway function 205 or third party controller interface function 210), the carbon dioxide monitoring function is configured to generate sensor data comprising a carbon dioxide alert.

This carbon dioxide alert is communicated from the carbon dioxide monitoring function to the loT gateway function 205 and/or the third party controller interface function 210. Responsive to this the loT gateway function 205 communicates a corresponding alert in the high-level device output data to the remote computing system 209 and/or the third party controller interface function 210 communicates a corresponding alert in the high-level device output data to the local computing system 211.

Responsive to receipt of such an alert, the remote computing system 209 is configured to generate a suitable warning for an operative via the interface provided by the software running on the remote computing system 209. This warning, for example in the form of the display of a warning message and/or the sounding of a warning alarm, can indicate that a dangerous number of people are congregating in the environment and remedial action should be taken (for example ensuring people leave the environment or the environment is ventilated by, for example opening a window).

An alert for an operative can be generated in the same way on the local computing system 211 Alternatively or additionally, the carbon dioxide monitoring function can be configured to facilitate the communication of the alert to a third party controller of the type described above with reference to Figure 2. For example, using known industrial control system communication techniques, the alert can be "exposed" as a data point to such a third party controller, enabling the third party controller to receive the alert and process it accordingly.

In another example, the carbon dioxide sensor daughter board 405 can be configured so that the gateway module 401 can be deployed as a vent-mounted carbon dioxide monitoring unit for monitoring levels of carbon dioxide in a vent which vents air from a particular environment, such as a room in a building where people congregate. Figure 5b provides a simplified schematic diagram of a daughterboard arranged in this way. In such an example, the gateway module 401 will be housed in a suitable 'rugged' housing for mounting to a vent (typically on the vent outer enclosure).

The daughterboard 501b for configuring the gateway module 401 as a vent mounted carbon dioxide detector corresponds to the daughterboard 501a for configuring the gateway module 401 as a wall mounted carbon dioxide detector, except that the motion detector 503 is replaced by pressure differential sensor input 504. The pressure differential sensor input 504 is configured to generate an output signal indicative of the presence or absence of flow in the vicinity of the gateway module 401. This output signal is conveyed to the gateway module 401 via a digital input, which can be provided via a "dry contact", hardwired to the gateway module 401. Alternatively, the output signal can be communicated to the gateway module 401 via a wireless digital input from a wireless field device installed in a remote location.

Further, when implemented as a vent mounted carbon dioxide sensor, sufficient power may not be available from ambient light to power the unit. Accordingly, the gateway module may be configured to receive power via a fixed line (for example, a dedicated power line or via an Ethernet cable (power over Ethernet PoE) as described above).

The pressure differential sensor input 504 is configured to receive a sensor signal from a differential pressure sensor which provides an indication of whether or not a fan operating in the vent in which the detector is mounted is working correctly.

Figure 5c provides a simplified schematic diagram depicting an example deployment of such a vent-mounted carbon dioxide monitoring unit.

A vent-mounted carbon dioxide monitoring unit 510 comprising a daughter board of the type described with reference to Figure 5b is mounted in a vent 509. The main housing of the vent-mounted carbon dioxide monitoring unit 510 is mounted on an outer enclosure of the vent 509 and a probe 505 of the carbon dioxide sensor extends into the vent 509. A pressure differential sensor 506 is connected, via a suitable signal line, to the pressure differential sensor input of the daughter board of the vent-mounted carbon dioxide monitoring unit 510. The pressure differential sensor 506 is connected to a first pressure sensor 507a located on an intake side of an extract fan 508 mounted in the vent 509, and to a second pressure sensor 507b located on an output side of the extract fan 508. The vent-mounted carbon dioxide monitoring unit 510 is mounted such that the probe 505 of the carbon dioxide sensor extends into the vent on the intake side of the extract fan 508. In normal operation, air flows in the direction of the arrows shown in Figure Sc.

In operation, the carbon dioxide sensor of the vent-mounted carbon dioxide monitoring unit 510 communicates an output signal to the data processor of the vent-mounted carbon dioxide monitoring unit 510 indicative of the level of carbon dioxide in the air being extracted from an environment.

Further, the pressure differential sensor 506 is configured to generate a sensor signal which is received by the data processor of the vent-mounted carbon dioxide monitoring unit 510 indicative of the differential pressure between the first pressure sensor 507a and second pressure sensor 507b.

The carbon dioxide monitoring function running on the data processor of the vent-mounted carbon dioxide monitoring unit 510 is configured to receive the output signal from the carbon dioxide sensor. If this is indicative of a carbon dioxide level that it is above a predetermined threshold level, the carbon dioxide monitoring function is configured to generate sensor data comprising a carbon dioxide alert which is communicated to the loT gateway function (and the third party controller interface function if the vent-mounted carbon dioxide monitoring unit 510 is connected to one or more third party controllers).

The loT gateway function then communicates a corresponding alert in the high-level device output data to the remote computing system 209 and/or local computing system 211. Correspondingly, the third party controller interface function communicates a corresponding alert to the to the one or more third party controllers if they are connected to the vent-mounted carbon dioxide monitoring unit 510.

Further, the carbon dioxide monitoring function running on the data processor of the vent-mounted carbon dioxide monitoring unit 510 is configured to receive the output signal from the pressure differential sensor 506 via the pressure differential sensor input 504. If this is indicative that the extract fan is not operating, or not operating correctly (for example by detecting a reduced pressure differential between the first pressure sensor 507a and second pressure sensor 507b), the carbon dioxide monitoring function is configured to generate sensor data comprising a potential ventilation failure alert which is communicated to the loT gateway function (and the third party controller interface function if the vent-mounted carbon dioxide monitoring unit 510 is connected to one or more third party controllers).

The loT gateway function then communicates a corresponding ventilation failure in the high-level device output data to the remote computing system 209 and/or local computing system 211. Correspondingly, the third party controller interface function communicates a corresponding ventilation failure to the one or more third party controllers if they are connected to the vent-mounted carbon dioxide monitoring unit 510.

In this way, the vent-mounted carbon dioxide monitoring unit 510 enables it to be remotely determined if the extract fan is working correctly and if not, enable remedial action to be taken (for example ensuring people leave the environment and that the ventilation system is investigated).

It will be understood that the vent-mounted carbon dioxide monitoring unit 510 can also be configured to work with a supply fan mounted in a vent where the probe 505 of the carbon dioxide sensor extends into the vent on the air output side of the supply fan.

Figure 5d provides a simplified schematic diagram depicting an example deployment of a vent-mounted carbon dioxide monitoring unit corresponding to that shown in Figure Sc except that a supply fan 511 is used in place of the extract fan 508. The supply fan 511 corresponds to the extract fan 508 in reverse orientation.

Figure 6 provides a simplified schematic diagram depicting an loT system arranged in accordance with an embodiment of the invention implemented in a location 601.

The location 601 represents a typical environment in which examples of the invention might be implemented, specifically an enclosed room in which people congregate.

Mounted on a wall of the room is a wall mounted carbon dioxide sensor 602 comprising a gateway module of the type described with reference to Figure 4 and incorporating a carbon dioxide sensor implemented as a daughter board as shown in Figure 5a.

A vent mounted carbon dioxide sensor 603 comprising a gateway module of the type described with reference to Figure 4 and incorporating a carbon dioxide sensor implemented as a daughter board as shown in Figure 5b is mounted within a ventilation shaft 604 which vents air from the location by virtue of an extractor fan 605. In other examples the extractor fan 605 and ventilation shaft 604 may be arranged as part of a heat recirculation system.

Positioned within the location 601 is a wireless access point 606 (for example a W-Fi transceiver) which is connected, via a local network 611, to a local monitoring computing system 607 (for example, via an Ethernet cable). Positioned relative to the location 601 is a base station 608 (for example of a PLMN) which is connected to a data network 609 which provides an onwards connection to a remote computing system 610.

In the event that too many people congregate in the location 601 increasing the risk beyond an acceptable level of the transmission of airborne diseases, the concentration of carbon dioxide levels in the location 601 will exceed a predetermined level which will be detected by the wall mounted carbon dioxide sensor 602 and vent mounted carbon dioxide sensor 603. The wall mounted carbon dioxide sensor 602 and vent mounted carbon dioxide sensor 603 will generate corresponding alerts which will be communicated to the local computing system 607 by the wireless access point 606 and to the remote computing system 610 via the base station 608 and the data network 609.

On receipt of such alerts, operatives of the local computing system 607 and/or remote computing system 610 may be prompted to take remedial action for example by ensuring that some or all of the people congregating in the location 601 leave the location 601. This could be achieved in any suitable way. For example, an announcement could be made over a tannoy system, an alarm/siren sounded, warning beacons illuminated and/or, in more advanced implementations, alerts sent to the mobile devices of the people in the location 601 in the form, for example of text messages, email messages, instant messaging messages and so on.

Other examples of remedial action may include, for example, the manual or automatic opening of windows or doors within the location 601 to improve ventilation or a manual or automatic increase of the speed of the extraction fan 605 to improve ventilation within the location 601.

In the event that the extraction fan 605 develops a fault (for example a fan belt snaps), this may lead to the concentration of carbon dioxide levels in the location 601 exceeding the predetermined level. In this event, the wall mounted carbon dioxide sensor 602 will generate an alert which is communicated to the local computing system 607 and remote computing system 610. However, the vent mounted carbon dioxide sensor 603 will generate a ventilation failure alert as described above which is communicated to the local computing system 607 and remote computing system 610. On receipt of such an alert, operatives of the local computing system 607 and/or remote computing system 610 may be prompted to take remedial action for example by ensuring that some or all of the people congregating in the location 601 leave the location 601 as described above and by deploying personnel to investigate the fault with the extraction fan 605. Alternatively, or additionally, back up ventilation systems could be automatically or manually activated.

For example, as shown in Figure 6, the wall mounted carbon dioxide sensor 602 and vent mounted carbon dioxide sensor 603 can be connected to a third party controller 612 which is connected to a back up system 613 (for example an auxiliary ventilation system such as actuators to open one or more windows or doors).

In the event of a ventilation failure alert (or a carbon dioxide alert) as described above, the back up system 613 can be activated by a control signal from the wall mounted carbon dioxide sensor 602 or vent mounted carbon dioxide sensor 603.

These control signals can be generated automatically at the wall mounted carbon dioxide sensor 602 or vent mounted carbon dioxide sensor 603 or generated at the local computing system 607 and/or remote computing system 610 and communicated to the wall mounted carbon dioxide sensor 602 or vent mounted carbon dioxide sensor 603.

As will be appreciated, by virtue of the fact that the wall mounted carbon dioxide sensor 602 and vent mounted carbon dioxide sensor 603 are "standalone" devices, they can be installed directly in the location 601 without any requirement for deploying any further infrastructure. In contrast, were the wall mounted carbon dioxide sensor 602 and vent mounted carbon dioxide sensor 603 implemented as devices in a conventional loT system, intermediate device controller devices and at least one loT gateway device would be required within the location 601. Moreover, as the wall mounted carbon dioxide sensor 602 can be powered by ambient light (in the event that a photovoltaic power unit is provided) or via an ethernet cable Of the power input port is adapted to receive power by ethernet), then there is no requirement to provide an independent mains power supply.

Further, if one or both of the wall mounted carbon dioxide sensor 602 and vent mounted carbon dioxide sensor 603 are provided with a real time clock module as described above, they can be operated in accordance with real-time. For example, to conserve power, they can be powered down during predetermined hours when there will be fewer or no people in the location 601, for example during the night if the location 601 is a work environment.

In the example implementation described with reference to Figure 6, the wall mounted carbon dioxide sensor 602 and vent mounted carbon dioxide sensor 603 operate as standalone devices which communicate directly with the local computing system 607 and computing system 610.

However, in certain embodiments the gateway module architecture described with reference to figure 3 can be used as a basis to build a modular loT system. Such a system comprises a plurality of gateway modules as described with reference to Figure 3, except certain gateway modules are configured as "end-point" devices (by the inclusion of hardware provided by suitable daughterboards) and which communicate with a central gateway module that acts as a device controller and loT gateway. An example of this is shown in Figure 7.

Figure 7 provides a schematic diagram of a loT system 701 arranged in accordance with an example embodiment of the invention.

A first gateway module 702 is provided which is configured to communicate data to and from a plurality of further gateway modules 703a, 703b, 703c.

Each of the further gateway modules 703a, 703b, 703c comprises a device daughter board 705 which enables each of the further gateway modules 703a, 703b, 703c to operate as an loT end-point device.

In each of the further gateway modules 703a, 703b, 703c, control instructions are communicated to the device daughter board 705, and output signals received from each device daughter board 705, by the device controller function 704. Each device controller function 704 on each of the further gateway modules 703a, 703b, 703c is configured to receive control instructions from a device controller function 706 of the first gateway module 702 and to communicate output signals from the respective device daughter boards 705 to the device controller function 706 of the first gateway module 702. The gateway function of each of the further gateway modules 703a, 703b, 703c is deactivated.

In certain examples, this 'star-type topology, with the 702 controlling the 703a, 703b, 703c is self-configured On accordance with "distributed wireless 10" techniques). In such an example, which gateway module will act as the first gateway module is automatically selected based on a variable such as signal strength. For example, out of a group of gateway modules in a given area that can wirelessly communicate data with each other, the gateway module with the best onwards connection to the rest of the data network is selected as the gateway module.

The gateway function 707 of the first gateway module 702 is configured to communicate data to and from a remote computing system as described with reference to Figure 2. Although not shown, in certain embodiments the first gateway module 702 comprises a local control function which enables data to be communicated with a local computing system, again, as described with reference to Figure 2.

Figure 8 provides a simplified schematic diagram of a system arranged in accordance with an exemplary embodiment of the invention.

The system includes an loT gateway 801 of the type described above. Specifically, the loT gateway 801 is configured to act both as a gateway and a device controller.

The loT gateway 801 is equipped with a EnOcean transceiver 802, VVi-Fi transceiver 803, 2G transceiver 804, RS 485 communication port 805 and Ethernet communication port 806.

The EnOcean transceiver 802 is configured to wirelessly communicate data to and from a plurality of EnOcean devices 807 in accordance with the EnOcean wireless communication standard.

The RS 485 communication port 805 is configured to communicate data to and from a plurality of MSTP devices 808 via a serial data communication protocol such as BACnet over MSTP.

The 1M-Fi transceiver 803 is configured to transmit and receive data in accordance with the VVi-Fi protocol and the 2G transceiver 804 is configured to transmit and receive data from a cellular telecommunications network in accordance with the 2G telecommunications standard.

The loT gateway 801 is connected via a TCP/IP data link 810 and data network 811 (for example a local IP network) to a local computing device 812. As described above, the local computing device 812 has running thereon loT monitoring and control software. Under the control of this monitoring and control software, the local computing device 812 generates control instructions which are communicated to the gateway module 204 via a suitable connection.

The data network 811 is further connected to the cloud network 813 (typically provided by telecommunications networks that form the "internet") to a remote computing device 814. As described above, the remote computing device 814 has running thereon loT monitoring and control software which enables the generation of high level control data which is communicated to the loT gateway 801 In use, the loT gateway 801 receives high-level control data from the remote computing device 814 and local computing device 812 via the cloud network 813 and data network 811. However, as will be understood, alternatively or additionally, this data can be received via the TCP/IP data link 810 by virtue of the provision of suitable Wi-Fi transceivers connected to the TCP/IP data link 810. Further, as will be understood, alternatively or additionally, this data can be received by the 2G transceiver 804 by virtue of the provision of a suitable connection to a mobile telecommunications network to the local computing device 812 and/or remote computing device 814.

As described above, the loT gateway 801 is configured to receive this high-level instruction data and convert it to control signals to communicate to the plurality of EnOcean devices 807, plurality of MSTP devices 808 and plurality of IP devices 809. The control signals are communicated to the plurality of EnOcean devices 807 from the EnOcean transceiver 802.

The control signals are sent to the plurality of MSTP devices 808 from the RS 485 communication port 805 and a suitable MSTP data link MSTP data link 815. The control signals are sent to the plurality of IP devices 809 from the Ethernet communication port 806 via suitable IP data link IP data link 816.

The system further includes a third party controller 817 which is also configured to communicate control signals to the plurality of MSTP devices 808 and plurality of IP devices 809.

Control signals from the third party controller 817 are sent to the plurality of MSTP devices 808 via a Modbus data link 818. Control signals are sent from the third party controller 817 to the plurality of IP devices 809 via the IP data link 816 and a further IP data link 819 connected to the IP data link 816.

In the example described above the 2G transceiver 804 is provided by 2G technology, however, the skilled person will understand that in other embodiments alternative technologies can be used, for example, other Cellular technologies or Low Power Wide Area Network (LPWAN) technologies such as Narrow Band Internet Of Things (NBIOT) and Cat-M1.

Figure 9 provides a simplified schematic diagram depicting an loT system arranged in accordance with an embodiment of the invention implemented in a location 900.

The location 900 represents a typical environment in which examples of the invention might be implemented, specifically an enclosed room in which people congregate.

Mounted on the ceiling of the room is a ceiling mounted carbon dioxide sensor 901 comprising a gateway module of the type described with reference to Figure 4, incorporating a carbon dioxide sensor implemented as a daughter board.

The ceiling mounted carbon dioxide sensor 901 corresponds to the wall mounted carbon dioxide sensor 602 shown in Figure 6 except that the ceiling mounted carbon dioxide sensor 901 includes the following additional hardware modules: a pressure sensor 904 configured to continually or periodically measure pressure in the location 900; a motion sensor 905 configured to continually or periodically measure motion in the location 900; a speaker 906; and LEDs 903a 903b 903c. These additional hardware modules are connected to the daughterboard and thus incorporated in the gateway module.

Positioned within the location 900 is a wireless access point 915 (for example a W-Fi transceiver) which is connected, via a local network 907, to a local computing system 902 (for example, via an Ethernet cable). Positioned relative to the location 900 is a base station 912 (for example of a PLMN) which is connected to a data network 908 which provides an onwards connection to a first remote computing system 909 and a second remote computing system 911 which has running thereon an artificial intelligence module 910 to provide machine learning and artificial intelligence analysis of data received from the ceiling mounted carbon dioxide sensor 901.

Also shown in Figure 9 is a temperature sensor 913 configured to continually or periodically measure temperature in the location 900 and a window contact sensor 914 configured to continually or periodically determine the open/closed status of the adjacent window. These sensors are auxiliary devices wirelessly connected to the carbon dioxide sensor 901.

In the event that too many people congregate in the location 900 increasing the risk beyond an acceptable level of the transmission of airborne diseases, the concentration of carbon dioxide levels in the location 900 will exceed a predetermined level which will be detected by the ceiling mounted carbon dioxide sensor 901. As a result of this detection, the pressure sensor 904 is configured generate a pressure data signal corresponding to the pressure in the location 900; the motion sensor 905 is configured to generate a motion data signal corresponding to motion detected in the location 900; the temperature sensor 913 is configured to generate a temperature data signal corresponding to the temperature in the location 900; and the window contact sensor 914 is configured to generate a window data signal corresponding to the open/closed status of the adjacent window. These signals are communicated to the processor of the ceiling mounted carbon dioxide sensor 901 either via the daughterboard or a wireless data transceiver. Upon receipt of these signals, the ceiling mounted carbon dioxide sensor 901 will generate a corresponding alert signal, which will contain information about air quality (for example CO2 levels) in the location 900 along with the associated pressure data signal; the motion data signal; the temperature data signal; and the window data signal. The alert signal will be communicated to the local computing system 902 by the wireless access point 915 and to the first remote computing system 909 and second remote computing system 911 via the base station 912 and the data network 908.

The information contained in the alert signal, such as CO2 levels, pressure, temperature, motion, and the open/closed status of the window is analysed by the artificial intelligence module 910 using artificial intelligence and machine learning techniques to infer an associated level of risk and generate analysis data that indicates appropriate remedial action. For example, the artificial intelligence module 910 can use the data associated with CO2 levels, motion, and temperature in the location 900 to infer the number of occupants in the location 900. Further, the artificial intelligence module 910 can use data associated with the pressure in the location 900 to determine whether the location 900 is in positive or negative pressure (which is important for preventing transmission of airborne disease because, for example, a negative room pressure can trap potentially harmful airborne particles). In the event that the artificial intelligence module 910 determines that there is negative air pressure in the location 900, the artificial intelligence module 910 can use data associated with the window open/closed status to determine whether opening the window will sufficiently adjust the pressure in the location 900 to result in a reduction in risk, of the transmission of airborne diseases, below a predetermined acceptable level. If so, the analysis data generated by the artificial intelligence module 910 will indicate that opening the window is an appropriate remedial action; if not, then the analysis data generated by the artificial intelligence module 910 will indicate that alternate remedial action must be taken, for example reducing the number of occupants in the location 900.

The analysis data is communicated via the data network 908 to the first remote computing system 909 which generates corresponding instructions. These instructions are communicated via the base station 912 and data network 908 to the local computing system 902. Upon receipt of the instructions, operatives of the local computing system 902 and/or remote computing system 909 may be prompted to take remedial action for example by ensuring that some or all of the people congregating in the location 900 leave the location 900.

This could be achieved in any suitable way. For example, an announcement made via the speaker 906 or visual indication provided by the LEDs 903a 903b 903c. For example, LED 903a, when illuminated, is red to indicate 002 > 1500ppm which is unsafe; LED 903b, when illuminated, is amber to indicate 1500ppm > CO2 > 900ppm which is safe but undesirable; and LED 903c, when illuminated, is green to indicate CO2 < 400ppm which is safe.

In the example described above, the sensors (such as, the pressure sensor 904, motion sensor 905, temperature sensor 913, and window contact sensor 914) are continually or periodically operating, however, the skilled person will understand that in other embodiments these sensors could be configured to, only, initiate operation in the event that CO2 levels rise above a predetermined threshold. In this way, fidelity of sensor data would be reduced but power consumption by the sensors would also be reduced. Power consumption can also be used to determine the frequency with which air quality (for example CO2 level) is measured. For example, gateway modules connected to physical power supplies could be used to continually measure air quality, whereas gateway modules using "standalone" power sources such as solar power, or battery power, could periodically measure air quality, for example by taking a 'snapshot' every 10 minutes.

Figure 10 provides a simplified schematic diagram depicting an loT system arranged in accordance with an embodiment of the invention implemented in a consumer unit.

The consumer unit 1001 includes a din rail 1002. Mounted on the din rail of the consumer unit 1001 is a consumer unit mounted gateway module 1003 of the type described with reference to Figure 4.

In the example described above the consumer unit mounted gateway module 1003 is shown mounted on the din rail 1002. However, the skilled person will understand that the consumer unit mounted gateway module 1003 can be configured to have any suitable form factor to allow mounting to the consumer unit 1001.

In the embodiments described above, for example, with reference to Figures 5c, 6, 9, and 10, gateway modules are shown in locations, such as: in a vent; on a ceiling; and in a consumer unit. The skilled person will understand that in such examples the gateway modules can be configured to be housed in suitable enclosures which can be mounted in said locations. The enclosures can be configured to have any suitable form factor to allow mounting in the respective locations. Further, these enclosures can be 'rugged' for operation in environments such as vents.

It will be understood that mountings in these examples can be achieved by any suitable means, for example, using mechanical fixings, such as bolts, screws, rivets or clips. It will also be understood that the term 'form factor' refers, broadly, to size, configuration, or physical arrangement.

In the embodiments described with reference. for example, to Figures 5a, 5b and Figure 6, gateway modules are configured to detect carbon dioxide. However, it will be understood that in other examples of the invention, additionally or alternatively, sensors for detecting other types of gases can be used.

It will be understood that certain embodiments of the gateway module can include additional data input and output components. For example, hardwired analogue or digital inputs and outputs, such as, Ethernet, Modbus and Meter Mbus, to further enhance the monitoring and control capabilities of the device.

All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and/or all of the steps of any method or process so disclosed, may be combined in any combination, except combinations where at least some of such features and/or steps are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise. Thus, unless expressly stated otherwise, each feature disclosed is one example only of a generic series of equivalent or similar features. The invention is not restricted to the details of the foregoing embodiment(s). The invention extends to any novel one, or any novel combination, of the features disclosed in this specification (including any accompanying claims, abstract and drawings), or to any novel one, or any novel combination, of the steps of any method or process so disclosed.

With respect to the use of substantially any plural and/or singular terms herein, those having skill in the art can translate from the plural to the singular and/or from the singular to the plural as is appropriate to the context and/or application. The various singular/plural permutations may be expressly set forth herein for sake of clarity.

It will be understood by those within the art that, in general, terms used herein, and especially in the appended claims are generally intended as "open" terms (e.g., the term "including" should be interpreted as "including but not limited to," the term "having" should be interpreted as "having at least," the term "includes" should be interpreted as "includes but is not limited to," etc.). It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, as an aid to understanding, the following appended claims may contain usage of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles "a" or "an" limits any particular claim containing such introduced claim recitation to embodiments containing only one such recitation, even when the same claim includes the introductory phrases "one or more" or "at least one" and indefinite articles such as "a" or "an" (e.g., "a" and/or "an" should be interpreted to mean "at least one" or "one or more"); the same holds true for the use of definite articles used to introduce claim recitations.

In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted to mean at least the recited number (e.g., the bare recitation of "two recitations," without other modifiers, means at least two recitations, or two or more recitations).

It will be appreciated that various embodiments of the present disclosure have been described herein for purposes of illustration, and that various modifications may be made without departing from the scope of the present disclosure. Accordingly, the various embodiments disclosed herein are not intended to be limiting, with the true scope being indicated by the following claims.

Claims

CLAIMS1. A module for use in an loT system, said module comprising a stand-alone device comprising a data processing means and data communication means, said data processing means configured to perform an loT gateway function and a device controller function, said loT gateway function configured to receive, via the data communication means, control data from a computing system and communicate the control data to the device controller function, said device controller function configured to convert the control data into control instructions and control one or more devices by communicating the control instructions, via the data communication means, to the one or more devices.
2. A module according to claim 1, wherein the device controller function is configured to receive, via the data communication means, from the one or more devices, output signals and convert the output signals to output device data and communicate the output data to the loT gateway function, wherein the loT gateway function is configured to communicate, via the data communication means, the output device data to the computing system.
3. A module according to claim 1 or 2, further comprising an expansion port for connecting loT device hardware to the module.
4. A module according to claim 3, wherein upon connecting of loT device hardware to the expansion port, the module is configured to operate as an loT endpoint.
5. A module according to any previous claim, wherein the module comprises a real-time clock enabling the device controller function to control the one or more devices in accordance with a real-time clock signal.
6. A module according to any previous claim, wherein the module is powered by a photovoltaic cell.
7. A module according to any previous claim, wherein the data communication means comprises at least a wireless data transceiver.
8. A module according to any previous claim, wherein the data communication means comprises at least a data port for receiving a wired data communication line of a first type.
9. A module according to claim 8, wherein the module comprises a power input means for receiving power via the data port.
10. A module according to claim 8, wherein the data port is an Ethernet data port.
11. A module according to any previous claim, wherein the data communication means comprises at least one further data port for receiving a wired data communication line of a second type.
12. A module according to claim 11, wherein the at least one further data port is an R3485 data port.
13. A module according to claim 3, further comprising a daughter board connected to the expansion port, said daughter board comprising one or more sensors.
14. A module according to claim 13, wherein the one or more sensors comprise a carbon dioxide sensor for detecting a level of carbon dioxide present in air in the vicinity of the sensor.
15. A module according to claim 14, wherein the one or more sensors further comprise a motion detector.
16. A module according to claim 14, wherein the one or more sensors further comprise an air pressure detector for detecting airflow in a vent.
17. A module according to any previous claim wherein the module is configured to be housed in an enclosure.
18. A module according to claim 17 wherein the enclosure is a 'rugged' enclosure.
19. A module according to claim 17 wherein the enclosure has suitable form factor to allow mounting to a ceiling.
20. A module according to claim 17 wherein the enclosure has suitable form factor to allow mounting to a vent.
21. A module according to claim 17 wherein the enclosure has suitable form factor to allow mounting to a consumer unit.
22. A module according to claim 1, wherein the computing system is a remote computing system.
23. An loT system comprising a module according to claim 1, one or more devices and a computing system, wherein the loT gateway function of the module is configured to receive, via the data communication means of the module, control data from the computing system and communicate the control data to the device controller function of the module, said device controller function configured to convert the control data into control instructions and control the one or more devices by communicating the control instructions, via the data communication means, to the one or more devices.
24. An loT system according to claim 23, wherein the computing system is a remote computing system.
25. An loT system according to claim 23, wherein the one or more of the devices comprises one or more further modules according to claim 4 further comprising an expansion port to 20 which is connected loT device hardware and the one or more further modules operate as loT endpoints.