Patent Description:
Security systems are generally used at user stations, such as residential and commercial properties, to detect unauthorised entry at the station and to alert a security service provider, normally operating from a central backend, thereby to protect property at the station from theft as well as to provide personal protection.

The known security systems utilise a local controller at the station. The controller comprises a plurality of inputs which are connected to a plurality of intrusion sensors which are distributed at the station. When one of the intrusion sensors senses an intrusion, an alarm is activated by the controller. An intrusion message is transmitted by the local controller from the user station to the remote central backend via a conventional telephone line utilising a connection typically referred to as a "tip and ring" connection. Alternatively, a Global System for Mobile Communications (GSM) modem is utilised to transmit the intrusion message to the backend. These GSM modems may be jammed by intruders and the telephone line may be compromised.

Furthermore, these local controllers and associated equipment need to be installed and programmed at the user station. This installation process is technical and therefore a skilled technician or relevant expert is generally required to perform the installation, which may be both inconvenient to and expensive for the user. Hence, these known security systems may not be suitable for at least some applications.

Accordingly, it is an object of the present invention to provide a security device, a security system and a method of protecting a user station with which the applicant believes the aforementioned problems may at least be alleviated or which may provide a useful alternative for the known systems and/or devices.

<CIT> relates to an IoT child tracking security system, which comprises loT security devices communicatively coupled to a local IoT hub. <CIT> relates to a security system which comprises a control panel and wireless external sensors within a secured area.

<CIT> relates to a method and apparatus for monitoring operational parameters in an loT device with external sensors and actuators.

According to the invention there is provided a security device as defined in claim <NUM> of the following claims.

The Internet of things (IoT) is known in the art and comprises a network of things. These things typically comprise at least one of associated electronics, software, sensors and actuators. The things all have network connectivity, enabling them to connect and exchange data with one another and/or with a central backend over the Internet. Preferably, each thing forming part of the loT network is uniquely identifiable in the loT network. The loT network typically comprises network dedicated loT high sites.

Hence, the security device may be assigned a unique identification number (ID) for use in communications via the network.

The sensor element may comprise any one of a) an intrusion sensor, such as any one of: a passive infrared sensor, a contact sensor for a door or window, photoelectric beam, a panic button or other operable button, a magnetic lock sensor, a strike lock sensor; and b) another sensor, such as a temperature sensor, a smoke sensor, a water or moisture sensor/detector etc. These sensors may be normally open or normally closed sensors.

The first message may be an intrusion message comprising data derived from a signal from an intrusion sensor, alternatively the first message may be a warning message comprising data derived from a signal from at least one of the other sensors, such as a temperature sensor, a smoke sensor, a water or moisture sensor etc..

The security device may comprise a local power supply, preferably in the form of a replaceable battery, providing an output voltage. The battery may be rechargeable. The power supply is preferably dedicated and local to the security device.

The processor may be configured to incorporate, into the first message, data relating to a current output voltage of the battery.

The security device may comprise a position determining device.

The position determining device may be configured to generate position data and the processor may be configured to incorporate in the first message the position data.

The security device may comprise an loT receiver for receiving a second message, such as an instruction or command message, from the cloud-based controller via the loT network.

The loT transmitter and loT receiver may be combined in an loT transceiver.

At least the sensor element, processor, transmitter and power supply are housed in a single housing for the security device. The housing may be dedicated to the security device. Preferably, all of the sensor element, processor, transmitter, receiver, position determining device and power supply are housed in the single housing.

The security device is hence self-contained and portable between different locations.

The invention also provides a security system as defined by claim <NUM> of the following claims.

The at least one security device may be as defined above.

The cloud-based controller may be configured to perform at least some of the control functions which are conventionally associated with a local controller or control box of a conventional security system.

The security system may be associated with a first user station, the at least one security device may, in use, be deployed at the first user station and the cloud-based controller may be hosted at a remote central backend.

The cloud-based controller may be hosted on at least one server at the backend. The backend may be housed at a single physical site or may be distributed over a plurality of distributed physical sites.

The security system may comprise a terminal which is associated with the first user station, the terminal being configurable to be in communication with the cloud-based controller and may be user operable to configure settings of the cloud-based controller. The terminal may be in the form of a mobile device, such as a smartphone, comprising a processor, an associated memory arrangement and a display.

The system may comprise a computer application program (app) which is stored in the memory arrangement and, in use, is executed by the processor to present a user interface (UI) on the display of the terminal, and in response to commands entered via the UI to configure the settings of or to program the cloud-based controller.

The system may comprise a plurality of the security devices, which may be located in distributed locations at the first user station.

Each of the plurality of security devices may be configured independently to communicate via its respective IoT transmitter or transceiver with the cloud-based controller.

Furthermore, any one of the plurality of security devices may be configured to communicate via its respective loT transmitter or transceiver with any other one or more of the plurality of security devices.

The backend may host a respective cloud-based controller for each of a plurality of distributed user stations, each respective cloud-based controller forming part of a respective security system as defined above.

The backend may comprise a database which comprises data associated with the user stations, including data relating to the unique ID's of the security devices.

The invention further provides a method of protecting a user station as defined in claim <NUM> of the following claims.

The invention will now further be described, by way of example only, with reference to the accompanying diagrams wherein:.

According to a third aspect of the invention there is provided a method of protecting a user station, the method comprising:.

An example embodiment of a security system is generally designated by the reference numeral <NUM> and an example embodiment of a self-contained security device is generally designated by the reference numeral <NUM> in <FIG> and <FIG>.

The self-contained security device <NUM> comprises a sensor element <NUM> and a processor <NUM> connected to the sensor element <NUM> for generating a first message in response to a signal from the sensor element <NUM>. An Internet of things (loT) transmitter <NUM> is connected to the processor <NUM> for transmitting the first message to a cloud-based controller <NUM> via an loT communications path <NUM> provided by an IoT network. The cloud-based controller <NUM> is preferably hosted at a remote central backend <NUM>. The security device <NUM> further comprises an IoT receiver. The loT transmitter and the loT receiver may be combined in an IoT transceiver <NUM>.

The self-contained security device <NUM> comprises a local power supply, preferably in the form of a replaceable battery <NUM> which provides an output voltage. The battery <NUM> may be rechargeable. The security device <NUM> also comprises a position determining device <NUM> which is configured to generate position data and the processor <NUM> is configured to incorporate the position data into the first message.

The sensor element <NUM> may comprise any one of: a) an intrusion sensor, such as a passive infrared sensor, a contact sensor for a door or window, photoelectric beam, a panic button or other operable button, a magnetic lock sensor, a strike lock sensor; and b) another sensor, such as a temperature sensor, a smoke sensor, a water or moisture sensor/detector etc. These sensors may be normally open or normally closed sensors.

The first message may be an intrusion message comprising data derived from a signal from an intrusion sensor, alternatively the first message may be a warning message comprising data derived from a signal from at least one of the temperature sensor, smoke sensor, water or moisture sensor etc..

In <FIG> is shown the security system <NUM> which comprises a plurality of security devices <NUM> to <NUM>. The security devices <NUM> to <NUM>. n are similar to one another. The central backend <NUM> is in communication with each of the security devices <NUM> to <NUM>. n individually via the loT communications path <NUM> and via the Internet <NUM>. The loT communications path <NUM> comprises at least one loT high site <NUM> which is connected to the Internet <NUM> via an loT network switch <NUM>.

The loT transceiver <NUM> is preferably a narrow-band type transceiver which transmits the first message via the loT communications path <NUM>. The loT communications path <NUM> is preferably provided by an loT network for example one of the networks which are marketed under the trademarks 'SIGFOX"™ or "LoRaWAN"™ which respectively provides a Low-power Wide-area network (LPWAN). The loT network switch <NUM> enables connection to the Internet <NUM> and a webserver (not shown) performs a signal exchange step between the Internet <NUM> and the backend <NUM>.

The security system <NUM> is associated with a first user station <NUM>, where the security devices <NUM> to <NUM>. n are deployed in distributed locations at the first user station <NUM>. Further similar security systems may be provided for further user stations <NUM> to <NUM>.

The cloud-based controller <NUM> is preferably hosted on a server <NUM> at the remote central backend <NUM>. The backend <NUM> may be housed at a single physical site or may be distributed over a plurality of distributed physical sites. The backend <NUM> hosts a respective cloud-based controller <NUM> to <NUM>. m associated with the respective security systems at each of the plurality of distributed user stations <NUM> to <NUM>. The systems associated with the user stations <NUM> to <NUM>. m are similar and hence the system <NUM> associated user station <NUM> only will be described in further detail below.

The security system <NUM> further comprises a terminal which is associated with the first user station <NUM>. The terminal is configurable to be in communication with the cloud-based controller <NUM>. The terminal is user operable to configure settings of the cloud-based controller <NUM> via the Internet <NUM>. The terminal is preferably in the form of a mobile device <NUM> of a user <NUM>, the mobile device <NUM> comprising a processor, an associated memory arrangement and a display (shown in <FIG>). The system <NUM> still further comprises a computer application program (app) which is stored in the mobile device memory arrangement and, in use, is executed by the mobile device's processor to present a user interface (UI) <NUM> on the display of the terminal, and in response to commands entered via the UI <NUM> to configure the settings of the cloud-based controller <NUM>. Hence, the user <NUM> is enabled to control the security devices <NUM> to <NUM>. n via the loT communications path <NUM>.

Any one of the plurality of security devices <NUM> to <NUM>. n may be configured to communicate via its respective IoT transmitter or transceiver <NUM> with any other one or more of the other security devices <NUM> to <NUM>. n at the user station <NUM>.

In <FIG> is shown the security device <NUM> in more detail. The position determining device <NUM> is preferably in the form of a Global Positioning System (GPS) device or a Russian Global Navigation Satellite System (GLONASS) device or any other position determining device for determining the position of the security device <NUM> utilizing satellites <NUM> (shown in <FIG>) in known manner. The sensor element <NUM>, processor <NUM>, transmitter or transceiver <NUM>, position determining device <NUM> and power supply <NUM> may be housed in a single sensor device housing <NUM> (shown in <FIG>). The security device <NUM> is hence self-contained and portable or transportable between different locations at user station <NUM> or between user stations <NUM> to <NUM>.

The processor <NUM> is configured to incorporate the position data into the first message, in the form of an intrusion message, which is transmitted to the backend <NUM> via the loT communications path <NUM>. The position data may be incorporated into the intrusion message repetitively or only at certain predetermined time intervals. A clock (not shown) may be utilised in determining the time intervals. Alternatively, the position data may be transmitted by the loT transceiver <NUM> in a so-called "heartbeat message" for example every <NUM> minutes or at any other suitable time. The "heartbeat message" may in addition comprise data relating to a current output voltage of the battery <NUM> and data relating to a unique identification (ID) number <NUM> of the security device <NUM> which uniquely identifies the device on the loT network <NUM>. The data relating to the unique ID of the security device <NUM> is preferably pre-stored into a memory arrangement <NUM> associated with the security device <NUM>. The user <NUM> may for example be alerted of a low battery voltage of one of the security devices <NUM> via the app on the mobile device <NUM>.

In <FIG> is shown the mobile device <NUM> of the user <NUM> in more detail. The user <NUM> is prompted by the app to register at the backend <NUM>, each of the security devices <NUM> to <NUM>. n which are associated with the user station <NUM> of the user <NUM>.

Referring again to <FIG>, the backend <NUM> comprises the cloud-based controller <NUM> which is hosted by the server <NUM>. The backend <NUM> also comprises a database <NUM>. The above registration by the user via the UI <NUM> on mobile device <NUM> involves entering into and storing of data relating to the user <NUM>, data relating to the user station <NUM> and data relating to the unique ID's of the first user station's associated security devices <NUM> to <NUM>. n on database <NUM> at backend <NUM>. The registration process may comprise scanning a code associated with each respective security device <NUM> to <NUM>. n such as a bar code or a "OR code"™ when the user <NUM> is logged into a user account via the app. It will be appreciated that a plurality of users <NUM> to <NUM>. m may be registered in this manner at the backend <NUM>, for respective user stations <NUM> to <NUM>.

In use, the user <NUM> purchases one or more of the security devices <NUM> to <NUM>. n, installs them at the user station <NUM> and registers them at the backend <NUM>. Referring to <FIG>, the user is enabled to configure settings of the cloud-based controller <NUM> via the UI <NUM>. Hence, the user <NUM> is enabled to control the security devices <NUM> to <NUM>. n via the app and via the loT communications path <NUM>. The user <NUM> may utilise the UI <NUM> to assign each of the security devices <NUM> an appropriate name, for example kitchen <NUM>, bedroom <NUM>, garage <NUM>, driveway <NUM>, etc. The user <NUM> is also enabled to activate or deactivate (by-pass) each of the security devices <NUM> to <NUM>. n individually via the UI <NUM>. Some of the security devices <NUM> to <NUM>. n may also be grouped together, for example security devices <NUM> to <NUM> may be assigned to the kitchen <NUM>, security devices <NUM> to <NUM> to the bedroom <NUM> etc. A user may use buttons <NUM>, <NUM> and <NUM> on the UI <NUM> to cause the cloud-based controller <NUM> to operate in a user selectable ARM mode, a DISARM mode and a STAY mode, subject to the user bypass selections referred to above.

The backend <NUM> may also be configured to alert the user <NUM> via the app when one of the security devices <NUM> to <NUM>. n is activated or when the GPS device <NUM> provides position data indicating that the security device <NUM> is located outside a geographical coverage area of an operator of the backend <NUM>.

It will be appreciated that there are many variations in detail on the security device, security system, and associated method without departing from the scope and spirit of this disclosure.

The system <NUM> provides multiple redundancies and robustness in that when one of the security devices such as security device <NUM> has limited or no connectivity to the loT network <NUM>, the respective device is enabled to transmit the intrusion message to one of the other security devices <NUM> to <NUM>. n which device then forwards the intrusion message to the backend <NUM> via the loT communications path <NUM>.

Apart from a first message in the form of an intrusion message, the above other sensors may output signals which may be used to generate a first signal in the form of a warning message. For example, leaks of a water heater (also referred to as a "geyser") may be monitored utilising a water detector. In this case, the processor <NUM> may be configured, in the event of a water leak, to transmit to the backend <NUM> via the loT communications path <NUM>, a warning or other message comprising data relating to a detected leak and position data. It will be appreciated that these other messages may comprise data associated with any of the other sensors, with or without position data.

Claim 1:
A security system (<NUM>) comprising:
- at least one security device (<NUM>) at a first user station (<NUM>), the at least one security device comprising:
o a portable housing (<NUM>);
o a local power supply (<NUM>) for providing an output voltage;
o a sensor element (<NUM>);
∘ a processor (<NUM>) connected to the sensor element for generating an intrusion message in response to a signal from the sensor element; and
∘ an Internet of things transmitter (<NUM>) connected to the processor, the Internet of things transmitter (<NUM>) being a narrow-band transmitter configured to transmit the intrusion message directly to a high site (<NUM>) of an Internet of things communications path (<NUM>) provided by a Low-power Wide-area Internet of things network comprising the high site and which high site is connected to the Internet (<NUM>) via an Internet of things network switch (<NUM>);
∘ the sensor element (<NUM>), the processor (<NUM>), the Internet of things transmitter (<NUM>) and the local power supply (<NUM>) being housed in the portable housing (<NUM>), so that the at least one security device is self-contained and portable;
- a cloud-based controller (<NUM>) for the security system which is connected to the Internet and hosted on a server (<NUM>) at a remote central backend (<NUM>) and which is in data communication with the at least one security device via the Internet of things communications path for receiving from the at least one security device the intrusion message; and
- a terminal (<NUM>) which is associated with the first user station and which terminal is configurable to be in communication with the cloud-based controller and operable to configure settings of the cloud-based controller, to cause the cloud-based controller to act on the intrusion message in accordance with the settings which are pre-stored on the cloud-based controller.