WO2021140506A1

WO2021140506A1 - A control system

Info

Publication number: WO2021140506A1
Application number: PCT/IL2021/050015
Authority: WO
Inventors: Ohad Amir
Original assignee: Essence Security International ESI Ltd
Current assignee: Essence Security International ESI Ltd
Priority date: 2020-01-06
Filing date: 2021-01-05
Publication date: 2021-07-15
Anticipated expiration: 2022-07-06
Also published as: GB202000117D0

Abstract

Disclosed is a method (300) of authorising an action for controlling an electrical device in a premises (19) using a mobile device, comprising: reading (344), by the mobile device (10), an RFID tag (12a) installed at a fixed location on the premises (19), to obtain RFID tag identification information (346); and transmitting (348), by the mobile device, an authorisation request to a remote server (18), wherein the authorisation request comprises mobile device identification information and causes the server to carry out an authorisation process using the mobile device identification information to provide an authorised action, wherein the authorised action is associated with the RFID tag; and, transmitting the authorised action to a controller at the premises, wherein the controller is configured to control the electrical device to carry out the action upon receiving the action.

Description

A CONTROL SYSTEM

TECHNICAL FIELD

This invention relates to a control system and associated method for authorising an action for controlling an electrical device in a premises. In particular, though not exclusively, the systems and methods described herein relate to security and door access systems.

BACKGROUND

Known security systems and door access systems may require a user to interact with some form of interface on the exterior of a premises prior to entering the premises so that an alarm might be disarmed and/or a door unlocked or unlatched. Corresponding actions may be required when exiting the property.

Such interfaces come in different forms and may include intercoms which are serviced by people inside the building, keypads for entering a passcode and key fobs which provide a passive electronic key, to name but a few. More recent developments have seen security systems controlled using software, e.g. applications, on mobile devices in which a user can open an application and engage with the system when approaching or at an entrance of the premises.

The present invention seeks to provide an improved security system and/or door access system which reduces the need for user interaction and increases the security of the system.

In addition to the above, the present invention also seeks to provide, more generally, an improved method and system for controlling electrical devices within a premises. Such electrical devices may form part of a security or access system, or may relate to a home automation system or other electrical device which are desirably controlled from the exterior of a building or other premises, or a part thereof.

SUMMARY OF THE INVENTION

The present invention provides a method and system for authorising an action for controlling an electrical device in a premises using a mobile device according to the appended claims. Disclosed herein are various methods and systems relating to the same.

Disclosed herein according to a first aspect is a method of authorising an action for controlling an electrical device in a premises using a mobile device. The method may comprise: reading, by the mobile device, an RFID tag installed at a fixed location on the premises, to obtain RFID tag identification information; and transmitting, by the mobile device, an authorisation request to a remote server, wherein the authorisation request comprises mobile device identification information and causes the server to carry out an authorisation process using the mobile device identification information to provide an authorised action, wherein the authorised action is associated with the RFID tag; and, transmitting the authorised action to a controller at the premises, wherein the controller is configured to control the electrical device to carry out the action upon receiving the action.

Providing an RFID tag which is read by a mobile device provides a convenient way of engaging with a control system. Because the mobile device is the reader, the RFID tags can be passive meaning no power supply is required by the RFID tag. This makes installation simpler.

Providing a separate server and controller as part of this system provides more versatility in the system.

The mobile device identification information may comprise user identification information for a user logged onto the mobile device. Providing user identification information allows a user to be authorised rather than the mobile device itself. This allows an authorised user to have multiple devices, potentially without the need to register all of the devices.

The mobile device identification information comprises an identifier for the mobile device which is unique to the mobile device. Providing a device identifier allows a mobile device to be shared amongst authorised users.

Carrying out the authorisation process may comprise querying a register of authorised mobile devices or mobile device users using the mobile device identification information.

The user identification information may be associated with one or more mobile devices.

The register may comprise a plurality of users. Each user of the plurality of users may associated with user specific authorised actions. Providing users with specific authorised actions allows different users reading the same RFID tag to have different default actions associated with them. This may include restricting certain actions, such as limited access within the premises, or preferential actions, such as initiating certain home automations devices, for example, switching on particular lights.

The plurality of users may comprise at least one master user. The users may include one or more user groups of user accounts. The method may further comprise: providing a notification on a master user device and/or displaying one or more user-selectable options for a master user to select. The master user may have oversight or control of the control system so as to receive notifications of relating to other users who have read the RFID tag. The master user device may be a master user mobile device. The user-selectable options on the master user device may include one or more of: an authorisation approval; an authorisation rejection; an action request to activate one or more of the electrical devices at the premises.

The notification on the master user device may comprise a user identifier associated with the mobile device identification information and/or the action for authorisation and/or one or more authorised actions which have been transmitted to the controller.

The authorisation process may comprise receiving an authorisation confirmation from a master user. The master user may be able to override or accept requests and/or actions which have not been previously authorised.

The authorisation request may further comprise the RFID tag identification information and/or an action upon which the authorised action is based. Providing the RFID tag identification information and/or action, allows the action in relation to an RFID tag to be predetermined and possibly pre-programmed into the RFID tag for convenience and the minimisation of installing RFID tags.

The mobile device may a mobile phone. The step of reading the RFID tag may comprise communicating with the RFID tag using a near field communication protocol. NFC communications are widely available on mobile phones and a convenient way of having a user engage with the system.

The method may further comprise: the mobile device transmitting a request to a controller to carry out the authorised action following an affirmation of the authorisation request. The method may further comprise: the mobile device transmitting a request to the server to carry out the authorised action following affirmation of the authorisation request.

The method may further comprise: the mobile device receiving a request from the server to carry out the authorised action following affirmation of the authorisation request. The authorised action may relate to an action which is carried out at the mobile device. The authorised action may be to open an application on the mobile device or display one or more user-selectable options for a user of the mobile device. The app may be one in which a user of the mobile device can initiate a further action within the premises. Thus, the electrical devices may comprise the mobile device.

The action may relate to the control of a security system of the premises and/or a door access system. The action may be one or more of: arming or disarming a security system associated with the fixed location; and controlling an electrical device within the premises.

The electrical device may comprise one or more of: an audio system; a video system; an actuator for operating a door or gate of the premises; and a lighting system. The actuator may be configured to open, close, lock and/or unlock the door or gate. The user identification information may comprise an association between a user- determined action and the RFID tag identification information.

The RFID tag may be configured to transmit an RFID tag stored action to the reader upon reading.

The method may further comprise: the mobile device configuring the RFID tag with the RFID tag stored action. Providing a configurable predetermined action in the RFID tag provides flexibility in the system. The RFID tag identification information may be associated with a pre determined action stored in a memory of the RFID tag, mobile device or server.

Also disclosed, in a second aspect, is a method of authorising an action for controlling an electrical device within a premises using a server, comprising: receiving, from a mobile device, an authorisation request comprising: mobile device identification information; carrying out an authorisation process to determine whether the mobile device or a mobile device user is authorised to carry out an authorised action, wherein the authorised action is associated with an RFID tag located at a fixed location on the premises; and transmitting an authorised action request to a controller instructing the controller to issue a command to an electrical device to carry out the authorised action.

Providing a server to receive and carry out the authorisation process and forward this to a controller to carry out the location provides versatility in the system. This is particularly so where the server is a remote server and capable of managing different premises and user groups. It is also advantageous where the control system utilises push (or other) notifications which are managed by the server.

The authorisation request may further comprise RFID tag identification information and/or the action for authorising. Carrying out the authorisation process may comprise querying a register of authorised mobile devices or mobile device users using the mobile device identification information. The mobile device identification information may comprise user identification information for a user logged onto the mobile device. The mobile device identification information may comprise an identifier for the mobile device which is unique to the mobile device.

The user identification information is registered for one or more mobile devices. The register may comprise a plurality of users. Each of the users of the plurality of users may be associated with user specific authorised actions. The plurality of users may comprise at least one master user. The method may further comprise: providing a notification on a master user device and/or display one or more user- selectable options for a master user to select.

The master user device may be a master user mobile device. The user-selectable options on the master user device may include one or more of: an authorisation approval; an authorisation rejection; an action request to activate one or more of the electrical devices at the premises.

The notification on the master user device may comprise a user identifier associated with the mobile device identification information and/or the action for authorisation and/or one or more authorised actions which have been transmitted to the controller. The authorisation process comprises receiving an authorisation confirmation from a master user.

The method may further comprise: determining the action using at least one of: the RFID tag identification information and the mobile device identification information. The method may further comprise: obtaining, by the server, an RFID tag register comprising RFID tag identification information for a plurality of RFID tags.

The method may further comprise: receiving, from the mobile device, a request to carry out the action.

Also disclosed, according to a third aspect, is a method of authorising an action for controlling an electrical device in a premises using a mobile device and server, comprising: the mobile device: reading an RFID tag installed at a fixed location on a premises, to obtain RFID tag identification information; and transmitting an authorisation request to the server, instructing the server to carry out an authorisation process before the action is initiated and wherein the authorisation request comprises mobile device identification information; and the server: receiving the authorisation request; carrying out the authorisation process to determine whether the mobile device is authorised to carry out the action wherein the action is associated with the RFID tag; and transmitting an action request to a controller at the premises instructing the electrical device to carry out the action following affirmation of the authorisation request.

The action request may be associated with one or more of: arming or disarming a security system associated with the fixed location; and controlling an electrical device within the premises. The action may be determined on the basis of the RFID tag which is read and/or the mobile device used for the reading.

Also described, according to a fourth aspect, is a system for authorising an action for controlling an electrical device in a premises using a mobile device, comprising: at least one RFID tag for locating at a fixed location at a premises, wherein the RFID tag comprises a data store which is configured to store RFID tag identification information; and a server configured to receive an action request in response to an RFID reader, which is configured to read the RFID tag identification information at the fixed location, reading the RFID tag identification information; and, a controller configured to receive an authorised action request from the server, the controller being configured to cause the authorisation action to be executed by the electrical device.

The system may further comprise a plurality of RFID tags located at one or more fixed locations at the premises. The or each RFID tag may be located proximate to an entrance of the premises.

The system may further comprise: a security system, wherein the action relates to the control of the security system. The action may comprise arming or disarming the security system.

The system may further comprise one or more electrical devices, wherein the action relates to controlling one of the one or more electrical devices. The one or more electrical device may comprise one or more of: an audio system, a video system; an actuator for opening, closing, locking or unlocking a door or gate of the premises; the RFID reader or a mobile device; and a lighting system. The mobile device may be that of the RFID reader, user or a master user.

The system may further comprise the RFID reader. The RFID reader may be a mobile device. The mobile device may be a mobile phone.

The RFID tag may comprise an adhesive for adhering the RFID tag to the fixed location. Providing an adhesive backing makes the installation of the RFID tag straightforward and user- friendly, particularly for a lay person.

The system may further comprise the premise at which the RFID tags are installed.

Also disclosed according to a fifth aspect is a computer program that, when read by one or more electronic processors, causes performance of any of the methods disclosed herein.

Also disclosed is at least one non-transitory storage medium comprising electronic-processor readable code that, when read by one or more electronic processors, cause performance of any of the methods disclosed herein.

Also disclosed is a mobile device configured to carry out any of the method steps relating to the mobile device disclosed herein.

Also disclosed is a server configured to carry out any of the methods disclosed herein.

Disclosed herein and according to a sixth aspect, there is a method of authorising an action for controlling an electrical device in a premises using a mobile device, comprising: reading, by the mobile device, an RFID tag installed at a fixed location on the premises, to obtain RFID tag identification information; and transmitting, by the mobile device, an authorisation request to a server, wherein the authorisation request comprises mobile device identification information and causes the server to carry out an authorisation process using the mobile device identification information before an action is initiated, wherein the action is associated with the RFID tag and wherein the RFID tag identification information is unique to that RFID tag.

Also disclosed herein and according to a seventh aspect is a method of authorising an action for controlling an electrical device within a premises using a server, comprising: receiving, from a mobile device, an authorisation request comprising: mobile device identification information and RFID identification information from an RFID tag located at a fixed location on the premises, wherein the RFID identification information is unique to the RFID tag; determine whether the mobile device or a mobile device user is authorised to carry out an authorised action, wherein the authorised action is associated with the RFID tag; and transmitting an authorised action request to a controller instructing the controller to issue a command to an electrical device to carry out the authorised action.

The RFID identification information may be associated with a plurality of users, each of the plurality of users having a different authorised action for the RFID tag.

The method may further comprise populating a register with one or more RFID tag entries, each of the RFID tag entries being associated with the RFID identification information from one or more RFID tags; and associating a plurality of users with each of the RFID tags in the register, wherein each user of the plurality of users is associated with a different authorised action.

The authorised action request is associated with one or more of: arming or disarming a security system associated with the fixed location; and controlling an electrical device within the premises.

Also disclosed, according to an eight aspect, is a system for authorising an action for controlling an electrical device in a premises using a mobile device, comprising: at least one RFID tag for locating at a fixed location at a premises, wherein the RFID tag comprises a data store which is configured to store RFID tag identification information, wherein RFID tag identification information is unique to that RFID tag; and a server configured to receive the RFID tag identification information from a mobile device which is configured to read the RFID tag identification information at the fixed location; and, a controller configured to receiving an authorised action request from the server, the controller being configured to cause the authorisation action to be executed by the electrical device.

The server may comprise a register, the register comprising the RFID tag identification information for one or more RFID tags and an associated authorised user and/or authorised action for the RFID tag identification information for each of the one or more of the RFID tags. Each RFID tag may be associated with a plurality of authorised users and at least one authorised action for each of the plurality of authorised users, wherein the at least one authorised action is different for different users.

The register may be amendable by a user such that the authorised user and/or authorised action for each RFID tag of the one or more RFID tags may be configurable.

The authorised action may comprise one or more of: arming or disarming a security system associated with the fixed location; and controlling an electrical device within the premises.

Also disclosed herein, according to a ninth aspect is an RFID tag for use with a system for authorising an action for controlling an electrical device in a premises using a mobile device, wherein the RFID tag comprises unique identification information which is associated with one or more authorised actions and/or one or more authorised users.

The unique identifier may comprise: a hardware ID or a serial number. The unique identification may be write protected in a memory of the RFID tag, such that it cannot be erased or re-written at the premises.

Also disclosed herein according to a tenth aspect, is an RFID tag for use with a system for authorising an action for controlling an electrical device in a premises using a mobile device, wherein the RFID tag comprises a predetermined action, wherein the predetermined action is write protected to prevent the action being rewritten.

Also disclosed is at least one non-transitory storage medium comprising one or more registers, each of the one or more registers comprising RFID tag identification information corresponding to one or more RFID tags, wherein each of the one or more RFID tags is associated with a plurality of authorised users and at least one authorised action for each of the plurality of authorised users, wherein the at least one authorised action is different for different users.

Disclosed herein, according to an eleventh aspect is a method of authorising an action for controlling an electrical device within a premises using a server, comprising: receiving, from a mobile device, an authorisation request comprising mobile device identification information; determine whether the mobile device or a mobile device user is authorised to carry out an authorised action, wherein the authorised action is associated with an RFID tag located at a fixed location on the premises; and, transmitting a notification to a user in relation to the authorisation request and/or the authorised action.

The notification may be one or more of: an authorisation request; an authorised action; a status change in the one or more electrical devices, an action selection; an authorisation rejection; and, an authorisation acceptance. The user may be the user of the mobile device. The user may not the user of the mobile device. The user may be a master user. The skilled person will appreciate that except where mutually exclusive, a feature described in relation to any one of the aspects, examples or embodiments described herein may be applied to any other aspect, example, embodiment or feature. Further, the description of any aspect, example or feature may form part of or the entirety of an embodiment of the invention. Any of the examples described herein may be an example which embodies the invention defined by the claims and thus an embodiment of the invention.

As used herein, except where the context requires otherwise, the terms “comprises”, “includes”, “has”, and grammatical variants of these terms, are not intended to be exhaustive. They are intended to allow for the possibility of further additives, components, integers or steps.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS The invention will now be described, by way of example only, with reference to the accompanying drawings, in which:

Fig. 1 shows a schematic representation of a control system;

Fig. 2 shows a schematic representation of an alternative control system;

Fig. 3 shows a method of operating a control system from the perspective of a mobile reader;

Fig. 4 shows a method of operating a control system from the perspective of a server;

Fig. 5 shows a flow diagram showing some operational steps of a control system;

Fig. 6 shows a flow diagram showing some operational steps for an alternative control system;

Fig. 7 shows a flow diagram showing some operational steps for a yet further alternative control system;

Fig. 8 shows a method of operating a notification system as part of a control method; and Fig. 9 shows a method of operating a control system using a unique identifier.

DETAILED DESCRIPTION OF THE EMBODIMENTS

The present disclosure is concerned with providing a convenient method of controlling access to (or other aspects of) a premises using a mobile device, such as a mobile phone. The mobile device is used as a reader to read one or more RFID tags which are located at strategic locations around a premises, such as building entry points and/or one or more parts of the building. Providing passive RFID tags which are read by a mobile device allows a user to approach a premises and engage with an access control or security system without having to interact with an interface of the mobile device. Thus, the mobile device can be configured to read the RFID tag and use information associated with the RFID tag to initiate an action request.

Using the mobile device as a reader and using information associated with RFID tags allows a convenient control system to be provided which can optionally be readily configured by a user for a particular premises and according to specific user requirements, both of which can vary tremendously from application to application. Thus, a user or owner of a premises may install a plurality of task specific passive RFID tags at desired locations at a premises and allow a mobile device which is associated a user to initiate that action upon reading the RFID tag. Alternatively or additionally, a user or owner of a premises may be able to configure the system such that the RFID tag is associated with the location such that user specific actions are carried out when a given user reads the RFID tag at that location.

Such a system provides an improved control system which is relatively inexpensive to install and configure.

In contrast to the above, prior art systems generally require some form of user interface engagement with a mobile device, or involve installed active/powered RFID reading devices which are costly to install and maintain.

Figure 1 shows a schematic representation of a control system 100 comprising: a mobile device 10; a premises 19; one or more RFID tags 12a-d located at predetermined locations around and/or in the premises 19; a server 18; a controller 14; and one or more electrical devices 16a- 16c. The elements shown as dashed lines are optional elements of the system. Thus, the system may comprise a single RFID tag 12a, a mobile device 10, a controller 14, a single electrical device 16a and a premises 19 and not require the use of a server. The arrows generally show a transmission of data from one entity to another.

The control system 100 may be an access system, a security system and/or a home- automation system, for example. Thus, the control system 100 may be configured such that a user carrying a mobile device 10 can control one or more electrical devices 16a-c which relate to aspects of an access system, a security system and/or a home automation system, for example. It will be appreciated that by home automation, it is meant that the one or more electrical device 16a-c within the system 100 may relate to one or more audio/visual, lighting devices or other remotely controlled device within the premises 19. It will also be appreciated that the control system 100 may be employed in other applications not covered by security, access or home automation systems.

The premises 19 may comprise a building. The building may be a dwelling such as a house, an apartment or block of apartments, for example. The premises 19 may comprise a commercial or industrial building such as an office, storage facility, shop, factory, restaurant or other public amenity building, for example. The premises 19 may include the grounds which surround the building such as a garden, driveway, or car park, and may include one or more outbuildings. Thus, the premises 19 may be defined as the curtilage of a property which includes the grounds and any buildings therein in some examples, or be restricted to one or more buildings in other examples.

A security system may be installed at the premises such that the premises 19 may comprise a security system. The security system may be a conventional security system in many respects and may comprise one or more of: a door access system; an alarm beacon or sounder; a motion detector for detecting the presence of an intruder or user of the premises 19; a security camera; a sensor(s) for detecting opening of a respective door/window and, a break-glass detector, for example. The door access system may comprise, for example, one or more remotely operated locks or latches which allow a user to unlock and/or open a door without physically engaging with the door, for example, by using a mechanical key or handle. The door access system may comprise one or more electrically controlled locks, which may employ magnetic or motor-driven latches, for example.

The premises 19 may include one or more RFID tags 12a-d provided at one or more locations on the premises. As shown in Figure 1, there are four RFID tags 12a-d distributed between three separate locations, with RFID tag 12a and 12b being at a common location, ‘location V . The locations may include entry points to a building or part thereof, such as a doorway or vehicular garage for example, or entry points to the curtilage such as a pedestrian or vehicular gate.

The actions initiated by the system 100 may be location specific. For example, a first RFID tag 12a provided at a first door entry point at location 1 may be read and result in an action of unlocking the door at the first door entry point and/or switching on a light or camera at that location, for example. An action in relation to a second RFID tag 12c provided at a second door entry point at location 2, may result in the door at the second door entry point being unlocked.

As noted above, a first door entry point may include two RFID tags 12a, b, each of which may be associated with a different action. The predetermined actions will be application specific but may, for a security system, include: ‘arm security system’ and ‘disarm security system’ and/or arm/disarm a part of the security monitoring that is associated with the first door entry point. Thus, a user can read the ‘arm’ RFID tag 12a when leaving the building, or ‘disarm’ RFID tag 12b when entering the building. Other examples of task specific RFID tags may include ‘lock’ and ‘unlock’ for an access system, or ‘activate’ or ‘deactivate’ select devices as part of a home automation system. An advantage of the exemplary system and method described herein, is that providing different passive RFID tags 12a-d which can be configured to provide predetermined generic actions or location specific actions, allows a user or premises owner to install different RFID tags at different locations to best suit that premises or a user group associated therewith. It will be appreciated that the system and method described herein also allows the premises to be segregated into zones or areas. Each of the zones or areas may have specific user access rights and/or dedicated RFID tags associated with them, such as restricted locations within a commercial building or sub-dwellings within a communal residential block, for example.

The mobile device 10, may be any suitable mobile device 10 which can be configured to read the one or more RFID tags 12a-d. The mobile device 10 may be: a mobile phone, such as a: smart phone; a tablet; a wearable device such as a smart watch; laptop; or, any other electronic device which a user may carry on their person when entering or exiting the premises 19.

The mobile device 10 may include mobile device identification information which can be used to verify that the mobile device 10, or the user thereof, is authorised to carry out a requested action and/or action associated with an RFID tag 12a-d. The mobile device identification information may include information linking the mobile device 10 to a user. The mobile device identification information may include an encrypted key or other suitable identifier which is associated with the user and/or user credentials of the mobile device 10 such as a username and password. Thus, the authorised actions which are permitted for that user or mobile device 10 can be initiated once the mobile device identification information is received and verified. It will be appreciated that the mobile device may be one of a plurality of devices which an authorised user may use to read an RFID tag 12a-d. Further, it will be appreciated that various users may have access to a common mobile device 10. Hence, in some examples, the mobile device identification information may include both mobile device credentials and user credentials.

The mobile device credentials may include a serial number or other unique number which may relate to a piece of installed software or hardware. Alternatively, or additionally, the mobile device 10 may comprise a security token that is issued to the mobile device 10 when the app is installed or a system installed and/or commissioned. Hence, the mobile device identifier may be something stored in a memory, such as an EEPROM.

The mobile device 10 may be configured so as to require a user to unlock the mobile device 10 using one or more mobile device 10 security features prior to the transmission of an authorisation request and/or reading of the RFID tag 12a-d. The security features may comprise well-known features currently used on mobile devices such as login information including one or more of a username, password and security key, or biometric sensors such as facial, iris or fingerprint recognition sensors. Restricting the transmission of the mobile device identification information to instances where the mobile device 10 has been unlocked by an authorised user using suitable security measures may prevent access by unauthorised users who have obtained the mobile device in illegitimately.

The mobile device 10 may be configured to read the RFID tag 12a-d and, upon or after reading, transmit an authorisation request to an authorisation module. The authorisation request may comprise the mobile device identification information and cause the authorisation module to carry out an authorisation process using the mobile device identification information before an action is initiated.

Upon successfully executing the authorisation process and verifying the mobile device 10 and/or user, an action may be initiated with one or more the electrical devices 16a-c. The authorisation module may be server 18 based, or provided as part of a system controller 14 which may be remotely located or located within the premises 19 respectively. Providing the authorisation module as part of a server may be advantageous where: multiple premises or user groups require access, and/or where push notifications relating to the activity or status of the system are desirable. These advantages are explained in more detail below.

The mobile device 10 is configured to communicate with an RFID tag 12a-d wirelessly as is known in the art. The communication between the RFID tag 12a-d and mobile device 10 may comprise any suitable RFID transmission frequency and/or communication protocol.

The choice of the RFID transmission frequency or communication protocol may be determined or selected according to a desired read range, that is, a maximum distance for the reading to be reliably performed. In some examples, it may be advantageous to have a user undergo a defined action or carry out a specific gesture such as offering the mobile device 10 up to the RFID tag 12a-d for a predetermined length of time or by swiping the RFID tag 12a-d in a similar manner to a conventional passive door access key fob. Providing an affirmative action from the user of the mobile device 10, such as a presenting or swiping the mobile device 10 in relation to the RFID tag 12a-d, may help avoid accidental authorisation requests and may help reduce power consumption. It may also allow multiple RFID tags 12a-d to be located in a common location.

The read range of the mobile device 10 may be less than 10cm or less than 4cm, for example. In some examples, the read range may be greater than 3cm and less than 10cm, greater than 10cm and less than lm, greater than lm or less than 10m, or any combination of these ranges. The mobile device 10 may be configured to read the RFID tag 12a-d using different transmission frequencies and/or using different communication protocols so that a single mobile device may be configured to work with different types of RFID tags allow the range to be selected as required. In some examples, the mobile device 10 may be configured to read the RFID tag 12a-d using a near field communications, NFC, protocol which is a well-known protocol and typically operates in the range of around 10cm or less, or in some implementations, around 4cm or less.

Reading of the one or more RFID tags 12a-d may provide the mobile device 10 with information relating to the RFID tags 12a-d which can be used to inform the mobile device 10 and/or the server 18 and/or controller 14 what action is required from the electrical devices 16a-c. Thus, for example, an RFID tag 12a may be associated with a particular location and/or a predetermined action which causes a predetermined response from one or more of the electrical devices 16a-c when a request is successfully processed by the system.

In some examples, the mobile device 10 may be configured to open an application on the mobile device 10 in response to reading the RFID tag 12a-d, or display a push notification to the, or another, user. Alternatively, or additionally, the mobile device 10 may be configured to open an application or display a notification to a user of the mobile device 10 upon an authorisation request being approved. The application and/or push notification may be configured to initiate an interaction with the user or with another user. For example, the application and/or push notification may provide a number of possible actions from which a user can select, such as arm/disarm or lock/unlock. Other users may include any other individual or organisation who have an interest in activity associated with the control system or the status of the control system. For example, another user may comprise a security service or personnel responsible for the premises 19, or an owner of the property who wishes to have a monitoring service to understand the comings and goings of family members, employees, tenants, visitors or other people to property.

The RFID tags 12a-d may be passive and may include RFID tag identification information which relates to the location where they are installed and/or a predetermined action for transmission to the mobile device 10 upon being read. For example, an RFID tag 12a-d may be configured to transmit a desired action to the reader such as ‘arm’ or a ‘disarm’ such that, when the RFID tag 12a-d in question is read, the mobile device 10 can relay for arming or disarming a component of the system, such as one or more security aspects of the server 18 or controller 14 of the premises 19, which is subsequently armed or disarmed. Other actions may include locking or unlocking a door, latching or unlatching a door, activating or deactivating a camera, lighting or audio/visual equipment, amongst others. Providing pre-programmed actions is advantageous as it reduces the configuration required for the system during installation. Further, it also allows the RFID tag 12a-d to be clearly marked such that a user operating the mobile device 10 can select an action by sight alone and avoid any further interaction with the mobile device 10 to initiate a particular action. Alternatively or additionally, the RFID tag identification information may relate simply to an identification number which can be assigned to a particular location or action within the system, the assignment being recorded in the memory of the mobile device, server and/or controller.

The RFID tag 12a-d may be configured to be installed by an end user and may, for example, comprise one or more features for attaching the RFID tag 12a-d to a wall or other suitable support structure at the desired installation location. In one example, the RFID tags 12a-d may be provided with a suitable adhesive backing by which an end user can adhere the RFID tag 12a-d to at an appropriate location.

Providing passive or battery-powered RFID tags 12a-d enables them to be readily installed by an end user without any need to route wiring for powering or communication. Additionally, the system may be configured as required for a particular premises or purpose, and/or may utilize a range of pre-configured RFID tags for different locations and actions to simplify set-up and/or offer greater control each over the systems functionality. Further the use of passive tags can reduce the size and cost of the goods, and can improve reliability and/or reduce any need for servicing.

The RFID tag 12a-d may be reconfigurable such that the RFID tag 12a-d can be updated after being installed at the predetermined location of the premises 19. Reconfiguring the RFID tag 12a-d may include assigning new identification information or actions to the RFID tag 12a-d or simply updating the tag 12a-d to improve security or the like.

As noted above, the communication between the RFID tag 12a-d and mobile device 10 may comprise any suitable RFID transmission frequency or protocol, known in the art. Thus, the RFID tags 12a-d may be arranged to communicate on a particular transmission frequency or using a particular communication protocol, and RFID tags 12a-c allocated may be configured to communicate on the same or different transmission frequencies or protocols so as, for example, to allow different actions to be initiated by different types of mobile devices 10 which support different communication protocols.

Providing installable RFID tags 12a-d as part of a control system 100 for a premises 19 allows the system to be readily and inexpensively configured such that control of various electrical devices 16a-c can be accomplished without a user having to interact with their mobile device 10. Further, the system 100 can be highly configurable by using task specific passive RFID tags 12a- d.

Each “RFID tag” 12a-d may, in some embodiments, be provided by an NFC device that is operable to act, at minimum, as a tag. The installed NFC device(s) may optionally also be operable as a reader, but such reader functionalities are not utilised by the installed NFC device in the described embodiments. The one or more electrical devices 16a-c may be arranged within the premises 19 and may be configured to be controlled by the controller 14. The controller 14 may be a generic controller 14 which is configurable or programmable to allow for control of the electrical devices 16a-c or may be task specific. The controller 14 may comprise a single controller, or be a distributed controller comprising plurality of task specific controllers, each of which are configured to control different aspects of the system 100. Thus, there may be a task specific controller associated with the security system such as a security system control hub, as is known in the art. Additionally or alternatively, the controller 14 may comprise a task specific controller associated with a door access control system, as also known in the art. Further task specific controllers may relate to other equipment such as audio/visual equipment or lighting equipment.

The control of the electrical devices 16a-c may be caused by an action request initiated by a mobile device 10 reading one or more RFID tag 12a-d. The action may be transmitted to the controller 14 or determined by the controller 14 on the basis of the mobile device 10 identification information and/or information associated with the read RFID tag 12a-d.

The connection between the controller 14 and the mobile device 10 will be wireless and achieved using conventional wireless transmission technology. Thus, the mobile device 10 may communicate with the controller 14 via the internet, a wide area network, a wireless local area network, or short range wireless communications using known standards and/or protocols, such as TCP/IP, WiFi (RTM) or Bluetooth (RTM), for example. The controller 14 may be connected to each of the electrical devices 16a-c via any suitable network such as a wide area or local area network, or short range wireless communications which may be achieved wirelessly or may be via wired connections, as known in the art. The controller 14 or parts thereof may be located within the premises 19. For example, in some embodiments the controller 14 is a control hub installed at the premises. The control hub may more specifically communicate with the electrical devices 16a- c using a wireless personal area network (WPAN). In some embodiments the WPAN may be a low-rate wireless personal area network (LR-WPAN), which may operate in accordance with IEEE 802.15.4.

The server 18 may be configured to receive information from the mobile device 10 and determine whether the mobile device 10 is authorised to request or initiate an action on the basis of the mobile device identification information and RFID tag 12a-d which has been read. The server may further be configured to obtain an action which is to be carried out as a result of the mobile device reading a given RFID tag 12a-d. The action may be one or more of: predetermined by the RFID tag 12a-d; predetermined based on the user credentials of the mobile device 10 or mobile device identification information; and, selected by a user of the mobile device 10 using the mobile device 10. The selection of an action and/or communication of an action to the controller 14 may be carried out by the server 18. The action may be pre-assigned on the basis of the mobile device 10 and/or RFID tag 12a-d, or may be transmitted to the server 18 by the mobile device 10.

The server 18 may be configured to initiate the action once the authorisation request has been approved. In some embodiments this is achieved by the server 18 transmitting one or more action requests to the controller 14. In response, one or more actions may be performed by the controller 14 and/or or by one of the electrical devices 16a-c under its control.

The server 18 may be a conventional server and may be located remotely from the premises 19. The server 18 may be cloud based, for example. The server 18 may be a single device or a plurality of distributed devices. The mobile device 10 may communicate with the server 18 using any suitable network such as the Internet or other wide area network or a local area network, for example. Thus, the mobile device 10 may communicate via the wide area network using broadband mobile or via a wireless connection to an access point at the premises 19, using WiFi, for example.

In addition to carrying out one or more of an authorisation request and obtaining and communicating an action to the controller 14, the server 18 may be configured to carry out other tasks associated with the premises 19. For example, the server 19 may be configured to provide security system functionality such as monitoring activity at the premises 19 via a security system and/or security system controller 14. This may comprise receiving data from the controller 14 relating to the security of the premises 19 and contacting responders and/or users when the security of the premises is breached and an alarm triggered.

Further, the server may be configured to manage user accounts. In some examples, the system 100, controller 14, RFID tag 12a-d or an electrical device 16a-c may be associated with one or more users or user groups. Further, each of the users and/or user groups may be associated with one or more premises 19. Each of the user groups may include one or more master users. The server 18, may be configured to associate different permissions for different users or members of the user groups and communicate the status of the system and/or changes in the system to the one or more master users. Thus, a master user may registered with a server as being a master user for each one of a plurality of premises and may be determined to provide an authentication or permission.

It will be appreciated from the above description that the server is located remotely from the premises and accessible by various premises via a common network. In contrast, the controller is a local controller located at the premises and in some embodiments is without the facility to be directly contactable by different premises. The electrical devices 16a-c may relate to access control equipment for the premises 19, a security system for the premises 19, or other systems or equipment which are desirable for a user to activate or deactivate when entering (or exiting) the premises 19. Such electrical devices 16a-c may relate to audio visual equipment, lighting devices, an alarm beacon or sounder, one or more locks, and/or door-opening mechanisms for example. As will be appreciated from the description herein, other kind of electrical devices may also be used.

Figure 2 provides a more detailed view of a control system 200. The control system of Figure 2 may include similar features to the control system described in connection with Figure 1 and the description of some corresponding features may not be repeated below for the sake of brevity.

Figure 2 shows a control system 200. The control system 200 may comprise: a mobile device 210; an RFID tag 212; a controller 214; electrical devices 216a-n; and a server 218 that is accessible via a network 220.

The mobile device 210 may include one or more antenna 226 for external wireless communications and data transmissions; a display screen comprising a user interface 228 with which a user can interact with the mobile device 210 to receive data or input data relevant to the control system; one or more applications 230 which may be configured to receive inputs or provide outputs which are associated with the control system and control of the electrical devices 216a-n; a reader application 233 for controlling the reading the RFID tag 212; a processor 229; a data store 232 which may store instructions which, when executed by the processor cause the performance of the method steps relevant to the mobile device 210; and a user profile 232.

As noted above, the mobile device 210 may be any mobile computing device which is carried by a user when exiting or entering a premises. In the case of Figure 2, the mobile device 210 is assumed to be a mobile phone in the form of a conventional smart phone which comprises conventional hardware and software to allow voice and text communications and data connections via various wireless communication channels such as mobile broadband, wireless local area networks, and short range wireless technologies such as near field communications and Bluetooth (RTM), for example. The mobile device 210 is also configured to store and operate other applications, ‘apps’, as known in the art.

The display screen may be a conventional touch screen which is configured to receive touch inputs from a user so as to allow the selection of a screen items such as menus or buttons. The screen items may be provided as part of the user interface 228 which may include options for a user to select, as part of an application or a notification, provided on screen without a user request or action other than reading the RFID tag 16a-d. The notification may be a push notification and may be provided as an on-screen dialogue box or a dropdown menu.

The user profile 231, which may also be referred to as user identification information, may include one or more user credentials which allow a user to be identified. The user credentials may include a username or other identifier and possibly one or more passwords, for example, so that the user can be securely identified. The user profile 231 may also include a current status of the user and/or whether, for example, they are logged in to the phone when the RFID tag 216a-n was read.

The presence of the user profile 231, including their log-in state, may be used, in some embodiments, to determine whether the user who has control of the mobile device 210 has the necessary authorisation associated with a given action request. For example, the control system, e.g. the server 218, may receive an authorisation request from the mobile device 210 which relates to an action for disarming a security system or unlocking an entrance door. As part of the authorisation request process, the server 218 may be configured to establish who a currently logged in user is, and whether this user has permission to initiate the requested action. Thus, the user profile, or data associated with the user profile, may be transmitted to the server as part of an authorisation request, following a reading of the RFID tag 216a-n.

Providing the user profile 231 may also allow a user to be validated for a mobile device 210 which is not known to the system. Thus, instead of authorising an action on the basis of the mobile device 210, it may be preferable to authorise an action using only the user credentials. Thus, an authorisation request may include mobile device identification information which comprises the user credentials including a username or password, for example.

It will be appreciated that reference to a user profile or user credentials may include data relating to the user profile or user credential. Thus, the actual username or password of a user may not be transmitted as part of an authorisation request, but data relating to the user may be transmitted once local security checks have been carried out on the mobile device and the user identity confirmed.

In some embodiments, the user profile may be stored in the server, with the stored user profile including a unique identifier for one or more mobile devices and/or an identifier of software serial numbers to which the user access on the mobile device. The unique identifier may for example be a hardware identifier of the mobile device, e.g. MAC address. The software serial number may be unique to each instance of a software application installation. In such embodiments, the server may identify the associated user of the mobile device based on the received unique identifier associated with the mobile device. The use of user profiles may optionally be used to provide different levels premises access and/or control over different sets of electrical devices 216a-n, dependent on the user.

In some examples, the users may form part of a user group or a user account. The users may be provided with different permissions for different controllers and/or different premises. Thus, for example, a first user account may include ‘Userl’ and ‘User2’ which have authorisation for actions in relation to a first controller. ‘Userl’ may additionally have authorisation for actions in relation to a second controller, as may a User3. At a further premises, a second user account may comprise ‘Userl’ and ‘User5’ who are authorised for actions in relation to a third controller, and a ‘User4’ who is authorised for actions in relation to a fourth controller. It will be appreciated that other combinations of users, controllers and premises may be possible.

The applications may be task specific applications. There may be one or more of: a security system application, a door access application, a home automation application and a RFID tag reader application. Any of these applications may be combined in a single application. Thus, there may be a security system app that is configured to read the RFID tag 216 and issue an authorisation request to the control system, e.g. the server 218, accordingly. Alternatively, the RFID reader application may be a separate application or a service of the mobile device’s operating system.

The data store 232 may comprise one or more memories present in the mobile device 210. The one or more memories may comprise a non-transitory computer readable storage medium comprising computer readable instructions that, when read a processor of a mobile phone, configure the mobile phone to carry out the methods described herein. The computer readable instructions may comprise executable code relating to the one or more applications, for example.

Thus, the data store 232 may comprise one or more computer programs which, when executed by the mobile device 210, cause the performance of the methods described herein. The memory may comprise: volatile memory, for example, one or more dynamic random access (DRAM) modules and/or static random access memory (SRAM) modules; and/or non-volatile memory, for example, one or more read only memory (ROM) modules, which for example may comprise a Flash memory and/or other electrically erasable programmable read-only memory (EEPROM) device. In other embodiments the data store may be separate from the mobile device 210. For example, it may be located in a memory component of a remote server or a portable memory device such as a memory card, e.g. SD card or microSD (RTM). Alternatively, the data store may be distributed amongst a plurality of devices, for example, partly on the mobile device 210 and partly remotely).

The processor 229 may be a conventional mobile device processor which may include one or more microprocessors executed in hardware or software, for example. The processor may include at least one microprocessor and may comprise a single core processor, may comprise multiple processor cores (such as a dual core processor or a quad core processor), or may comprise a plurality of processors (at least one of which may comprise multiple processor cores). In various examples, the processor may comprise: control circuitry; and/or processor circuitry; and/or at least one application specific integrated circuit (ASIC); and/or at least one field programmable gate array (FPGA); and/or single or multi-processor architectures; and/or sequential/parallel architectures; and/or at least one programmable logic controllers (PLCs); and/or at least one microprocessor; and/or at least one microcontroller; and/or a central processing unit (CPU); and/or a graphics processing unit (GPU), and/or transceiver(s) to perform the methods.

As described above in connection with Figure 1, the mobile device 210 may be configured to be a reader so as to read the passive RFID tag 212 using any suitable communication protocol. The mobile device 210 of Figure 2 is shown as using a near field communication, NFC, protocol as is well known in the art. The use of NFC is convenient due to its prevalence on conventional mobile phones and other portable computing devices but is particularly advantageous to the present disclosure due to the mobile device 210 requiring a close proximity engagement with the RFID tag 212. The RFID tag is therefore, in this embodiment, provided by an NFC device. This means that a plurality of RFID tags 212, each with predefined tasks (e.g. arm/disarm), can be located relatively closely together at a strategic location on the property, whilst allowing a user to select a particular action by swiping/presenting the mobile device 210 at only one of the RFID tags 212.

The RFID tag 212 may be conventional and may comprise: a data store 222, an antenna 224 for communicating via a corresponding antenna 226 in the mobile device 210 and a processor 223.

In some examples, the RFID tag 212 may be configured to be re -programmable, as described above. Thus, the mobile device 210 may be configured to carry out a read/write function. Reconfiguring the RFID tag 212 may comprise changing a predetermined action associated with the RFID tag 212, for example.

The RFID tags 12a-d, 212, described herein may include unique identification information comprising, for example, a hardware ID or a serial number. The unique identification may be fixed such that it cannot be erased or re-written in the field. In this way, no two RFID tags 12a-d, 212 from a given system, or any other, will have the same ID meaning each can be uniquely identifiable. Each unique ID may be placed on the authorisation register 239 together with a user, an action, or user specific action, for that RFID tag ID. The controller 214 may be a generic controller configured to control the operation of the electrical devices 216a-n, or may be task specific. Hence, although the controller 214 is a single item in the example shown in Figure 2, it is possible for the controller 214 to comprise a plurality of task specific controllers. Hence, there may be a first controller which is configured to control a security system or a door entry system. The controller may comprise a further controller for which is configured to control one or more of the electrical devices used for audio or visual equipment or lighting, for example. Other controllers will be apparent to the skilled person.

The controller 214 or the sub-controllers thereof, may be collocated within a common location or housing within the premises, or may be distributed throughout.

The controller 214 may comprise any suitable circuitry to cause performance of the methods described herein and as illustrated in the drawings.

In various examples, the controller 214 may comprise at least one processor. For example, the controller may comprise: control circuitry; and/or processor circuitry; and/or at least one application specific integrated circuit (ASIC); and/or at least one field programmable gate array (FPGA); and/or single or multi-processor architectures; and/or sequential/parallel architectures; and/or at least one programmable logic controllers (PLCs); and/or at least one microprocessor; and/or at least one microcontroller; and/or a central processing unit (CPU); and/or a graphics processing unit (GPU), and/or transceiver(s) to perform the methods.

The controller may also comprise at least one memory that is separate from the processor(s) and/or partly or wholly integrated onto a common chip(s) with the processor(s). The at least one memory may store code that, when read by the processor(s), causes performance of any of the methods described herein, and/or as illustrated in in the drawings. For example, the memory may comprise: volatile memory, for example, one or more dynamic random access (DRAM) modules and/or static random access memory (SRAM) modules; and/or non-volatile memory, for example, one or more read only memory (ROM) modules, which for example may comprise a Flash memory and/or other electrically erasable programmable read-only memory (EEPROM) device. The code may for example be software, firmware, or hardware description language (HDL) or may be any combination of these or any other form of code for one or more processors that is known by a person skilled in the art.

The electrical devices 216a-n may comprise any number and are shown in Figure 2 as including up to n electrical devices, where n may be any integer. The electrical devices 216a-n may be any electrical device which forms part of the control system which is controllable via an initial reading of the RFID tag 212 with the mobile device 210. The electrical devices 216a-n may be operable in response to commands received from the controller 214. Thus, in use, the controller 214 may receive an action request from a mobile device 210 or server 218, and may issue a corresponding command to given electrical device 216a-n, accordingly. The electrical devices 216a-n are referred to as electrical devices in that they are electrically responsive or operated and will typically include one or more electronic circuit, actuator, sensor or transducer.

As noted above in connection with Figure 1, the server 218 may be conventional and may include one or more processors and one or more memory. The server 218 may be located remotely from the premises 19 and be connected to via the network 220. The server 218 may be utilised to serve a plurality of premises 19, and/or a plurality of controllers/control hubs and/or a plurality of users or user accounts at one or more of the plurality of the premises. Hence, the server 218 may be in communication with and accessible from different premises 19 via the network 220. However, for the sake of simplicity, only one premises 19 is referred to in the following description.

The server 218 may comprise: a data store 238 comprising a register 239; an action module 240; and an authorisation module 242.

The register 239 may comprise data relating to one or more mobile devices 210; mobile device users; one or more of the RFID tags 212 and one or more actions which are authorised for the listed mobile device 210 or user. The register 239 may be referred to as an RFID tag register.

Information may be extracted from the register 239 by one or more of the authentication module 242 or action module 240.

In one example, the register 239 comprises a list of the users and/or mobile devices 210 registered for the system and the actions which those users and/or mobile devices 210 are permitted to make following an authorisation request or action request. The list of users and/or mobile devices 210 may correspond to the mobile device identification information which is received from the mobile device 210 as part of an authorisation request. Thus, a first user, ‘user G, may be associated with one or more mobile devices 210 and be recorded as having permission to access a premises via one or more entrances, as determined RFID tags 212 listed against that user, for example.

In addition, the register 239 may record a number of user preferences in relation to certain electrical devices in the premises 19. Hence, if a user wishes to have a particular arrangement of lighting provided when entering the premises 19, this can be recorded within the register 239.

The register 239 may be populated during the configuration of the system using a suitable input device. The input device may be provided by one of the controllers 214, or may be achieved using an application on a mobile device 210 or a user terminal of the server 218 or similar. Thus, a mobile device 210 may include a control system application which includes a configuration setting where users and permitted and/or preferred actions are recorded for each of users in relation to each of the RFID tags 212.

The authorisation module 242 may receive an authorisation request from a mobile device 210. The authorisation request may comprise mobile device identification information which may include an identifier for the mobile device and/or a user of the mobile device 210. The authorisation module 242 may use this information to assess whether the mobile device 210 and/or user is authorised to carry out an action in relation to the RFID tag which has been read prior to the transmission of the authorisation request from the mobile device 210. The authorisation module 242 may read the register to make a determination as to whether the mobile device 210 and/or user has the necessary permission.

The action which is to be undertaken by the system may not have been determined or selected at the time when the authorisation request is transmitted. In some examples, the action may be predetermined and encoded in the authorisation request as a result of the type or location of the RFID tag 212 which was read. In other examples, an action request may be transmitted from the mobile device 210 following successful authorisation request. The action request may be based on one or more selections made on the mobile device 210, either prior to the reading of the RFID tag 212, for example as a default setting, or in response to a user selecting an action once authorised to do so. In other examples, the action may be limited to a default action for a location and a user. The default action may be stored within the register 239.

The action module 240 may receive a request for an action to be carried out. The action module 240 may determine whether the requested action is authorised by the requesting user, for example, by referring to the register, and, upon a positive determination, forward the request to the controller 214, or directly to the electrical device 216a-n where possible, so as to cause the action to be carried out.

It will be appreciated that any of the authorisation module 242, action module 240 and data store 238 including the register 239 may be incorporated in the controller 214, particularly where a server is not present in the system 200.

The present disclosure provides methods and systems for authorising an action for controlling an electrical device in a premises using a mobile device. A method of authorising an action for controlling an electrical device in a premises using a mobile device may comprise: reading an RFID tag installed at a fixed location on the premises using a mobile device. The mobile device may read the RFID tag to obtain RFID tag identification information. The mobile device may subsequently transmit an authorisation request to an authorisation module. The authorisation request may comprise mobile device identification information and cause the server to carry out an authorisation process before an action is initiated. The action may be associated with the RFID tag which was read.

In some examples, the method may be executed using a server based system in which the mobile device 10 transmits information to a server which then processes the information. The information may relate to an authorisation request or an action request. Figures 3 and 4 show respective methods from the perspective of the mobile device and server respectively.

Figure 3 shows a method 300 of authorising an action for controlling an electrical device 16a-c in a premises 19 using a mobile device 10. The method may comprise: reading 344, by the mobile device 10, an RFID tag 12a installed at a fixed location on the premises 19, to obtain RFID tag identification information 346; and transmitting 348, by the mobile device 10, an authorisation request to a server 18 and/or controller 14. The authorisation request may comprise mobile device identification information and cause the server and/or controller to carry out an authorisation process using the mobile device identification information before an action is initiated. The authorisation request may additionally comprise RFID tag identification information, wherein the RFID tag identification information is associated with the RFID tag.

Figure 4 shows a method 400 of authorising an action for controlling an electrical device 16a-c within a premises 19 using a server 18, comprising: receiving 450, from a mobile device, an authorisation request comprising mobile device identification information; carrying out an authorisation process 452 to determine whether the mobile device is authorised to carry out an action wherein the action is associated with an RFID tag located at a fixed location on the premises; and transmitting an action request 454 instructing a device to carry out the action following affirmation of the authorisation request. The authorisation request may additionally comprise RFID tag identification information, wherein the RFID tag identification information is associated with the RFID tag.

Figure 5 shows a method flow diagram including some of the operational steps of a control system. The control system may be that described in Figures 1 and 2, for example. Thus, there is shown the separate entities of the control system comprising: an RFID tag 512; a mobile device 510; a server 518; a controller 514 and an electrical device 516. Each of the elements of the system may be similar to the corresponding features described above. The module 516, may be taken to have the features of the electrical devices 16, 216.

In a first step, the mobile device 510 may be activated so as to be put in a read ready state in which the mobile device can read the RFID tag 512 when presented to the RFID tag 512. The read ready state may be established as a default state such that a read application programme is constantly active in the background. This may be achieved using a specific control system app, or as part of the operating system. For example, the operating system, or other reader software, may be in permanent standby as an NFC reader. Alternatively, the read ready state may be activated by a user logging into the mobile device using one or more of a password, key code or biometric data.

Once in a read ready state, a user may place the mobile device 510 within a read distance of the RFID tag 512 which is to be read. As described above, this distance may be application specific, but in the case of a near field communication, will require the mobile device 510 to be placed within a few centimetres of the RFID tag, by hand. Thus, it will be appreciated that the RFID tag 512 may be installed by a user at a convenient height and location to allow an easy presentation of the mobile device 510.

Once in the correct position, data can be read from the data store of the RFID tag 512. The data may include identification information for the RFID tag 512, such as an identification number and possibly a location identifier and/or a predetermined action. Following a successful reading of the RFID tag 512, a user may be provided with an audible or visual indication that a successful reading has been achieved such that the mobile device 510 can be removed from the proximity of the RFID tag 512 and stowed away or viewed in anticipation of a follow-on prompt, initiated either from the mobile device 510 itself or from the server 518, once the device has been authorised.

The mobile device 510 may then transmit the mobile device identification information and, optionally, the RFID tag identification information, to the server 518. As noted above, the mobile device identification information may include one or more identifiers relating to the mobile device 510 or the user of the mobile device such that the system can determine whether the person operating the mobile device is authorised to carry out an action. The action may or may not be determined at this point, either on the basis of the RFID tag 512 including a default action, that is, being a task specific RFID tag 512, or on the basis of the mobile device transmitting a default action when transmitting the mobile device identification information.

The transmission of the mobile device identification information may constitute an authorisation request.

The mobile device identification information and RFID identification information may be received by the server 518 and a comparison made with a register of existing mobile device identification information for different mobile devices and/or users who are permitted to carry out an action in relation to the RFID tag 512 which has been read. The comparison provides a determination of whether the authorisation request can be granted.

Where the RFID identification information is not sent with the mobile device identification information, it will be appreciated that some associated action may be sent with the authorisation request. That is, in some examples it is possible that the mobile device is configured to determine the location of the RFID tag 512 from RFID tag identification information and select an appropriate action for that location and/or RFID tag, in which case there is no requirement to send the RFID identification information. Alternatively, the RFID tag 512 may mandate a particular action. Hence, in some instances, the mobile device 510 may only transmit the mobile device identification information and an action to the server 518. This is shown in Figure 6.

Once granted, the server 518 may instruct a controller 514 to execute a requested action, if already known. The controller 514 may provide a corresponding action to the one or more devices 516 which may then carry out the requested action.

It will be appreciated that where an authorisation request is not successful, the server 518 may be configured to return a notification to the mobile device 510 for display to the user, or take no further action.

If no action has been requested or is not known to the server 518 at the time of the authorisation request, the server 518 may await an action or take steps to seek an action. In doing so, the server 518 may provide a notification to the mobile device 510 confirming that the authorisation request has been successful and await an action to be issued from the mobile device 510.

Upon receiving a notification from the server 518 that the authorisation request has been successful, the mobile device 510 may initiate one of the following responses: open one or more applications on the mobile device 510 to instigate a response and action selection from the user; provide the user with a notification relating to the authorisation thereby prompting a follow-on action from the user, or, send a default action to the server 518. The default action may be determined on the basis of the RFID tag 512 location or a predetermined action assigned to the RFID tag 512.

The one or more applications may be task specific applications from which a user can select an action. For example, the application may be a security application which provides the options of ‘arm’ and ‘disarm’ in the form of virtual buttons which can be pressed by a user to trigger a corresponding action request to be transmitted. The notification presented to the user may be in the form of a conventional push notification which is displayed on screen without the need for starting an app and may provide similar options with which a user can respond with the selection of an appropriate action.

The ability of the system to initiate an action on the basis of a user reading the RFID tag 512 without further interaction saves time for the user and power. In the alternative prior art examples, a user may have been required to open an app upon approaching the premises, or location thereof, and select an action to disarm an alarm or the like. According to some of the methods described herein, there is no requirement to open an app on the mobile device. Where an action is to be selected, this may be achieved using a push notification which is under the control of the server. Thus, the user can select the action more readily and without having to engage with the phone unnecessarily.

In one example, the action may be predetermined based on the mobile device identification information and/or the RFID tag identification information, and/or the current status of the system (for example, the system may be configured to toggle between a lock/unlock status when an action request is authorised). In another example, an action may be performed and a pop-up dialogue box from a push notification informs the user that an action is done. In a further example, various action options may be displayed as a pop-up dialogue box from which one of the options may be selected.

This may be in response to a push notification from the server, the server response being in response to the initial information sent from the mobile device. The options may include the selection of an action for one or more electrical devices, or to open an app on the mobile device to allow more low level or non-standard response. Each of these examples requires less interaction from the user and power from the mobile device than prior art systems which require the opening of an app to engage with the control system.

As noted above, Figure 6 shows a flow diagram which generally corresponds to the flow diagram of Figure 5 and includes a tag 812, mobile device 810, server 818, controller 814 and electrical device 816. The method steps differ from Figure 5 in that the mobile device 810 provides an action request with the mobile device identification information when transmitting the authorisation request. The action is shown as being transmitted from the RFID tag 812 when read, however, this need not be the case and the action may be selected by a user of the mobile device 810 from a predetermined list of displayed possible actions for that RFID tag 812, or may be a default action which is determined on the basis of the RFID tag identification information. The server 818 may receive the authorisation request and action request and transmit the latter to the controller if the authorisation request is granted, without further engagement with the mobile device or user.

Figure 7 represents an alternative operational flow diagram for a control system in which the mobile device 910 is provided with notifications and updates as to the status of the system. The system may comprise: a mobile device 910; one or more RFID tags 912; a server 918; a controller 914; and, one or more devices 916. The system may also optionally include a responder 917, which is described in more detail below.

The communications between the mobile device 910, RFID tag 912, server 918, controller 914 and electrical device 916 may be the same as any of the corresponding communications described above. Thus, the mobile device 919 may read the RFID tag 912 and transmit an authorisation request and/or an action request to the server 918 which may execute the authorisation request and action requests, accordingly.

In addition to this, the server 918 may be configured to provide status updates to the mobile device 910. The status updates may relate to one or more requested actions. Thus, when the action request relates to an arm or disarm command for an alarm system, a notification may be provided to the mobile device 910 to confirm that the action has been successfully executed. Thus, following an action command being delivered to the electrical device 916, a status update may be provided to the controller 914 from the electrical device 916, and this may be relayed to the server 918. It will be appreciated that controller 914 or server 918 may not require a confirmatory notification from the electrical device 916 or controller 914, as the case may be, and may simply provide the confirmatory notification to the mobile device 910 once the action command has been issued.

It will be appreciated that this disclosure provides a control system for a premises which requires less interaction from a user. As described above, the control system may comprise a security and/or door access system. Such a system may form part of a larger security system for the premises which monitors and raises an alarm when one or more security devices is triggered.

Thus, the server 918 may also provide periodic or event based notifications to the mobile device 910. The system may be configured to provide periodic or event based notifications as a result of an action request resulting from reading an RFID tag 912 when, for example, a user exits the premises and arms the security system.

The security system may be a responder system in which an agency can be notified in the event of an alarm, for example. The server 918 may provide the notification to the responder service as part of a broader security system.

As noted above, the control system(s) described herein may configured to send notifications in relation to the control system. The notifications may be push notifications which are sent to a user of the mobile device and/or another user. The other user may be a user with some of interest or responsibility in the premises with a need to be provided with information in relation to the activity occurring at the premises.

The notifications may be visual and/or audible. Thus, the notifications may comprise dialogue boxes or drop down menus on a user interface of the mobile device or other computer interface. Additionally or alternatively, the notification may include an audible alarm such as a siren or ‘beep’ to confirm the status of the system, for example.

The user who receives the notifications may be the person logged into the mobile device reading the RFID tag, or a property owner, family member, carer, employer or contractor responsible for the security of the premises or personnel entering and exiting the property. Other examples of notifiable users may exist. The users, other than those of the mobile device reading the RFID tag, may be referred to as master users in this disclosure in the sense that they have a supervisory function, rather than being required to read an RFID tags directly with their own mobile device to receive a notification.

The notifications provided to the user, or master user, may be any which could be useful in the operation or supervision of the control system. Thus, the notification may relate to: an authorisation request; an authorised action; a status change or update in the one or more of the requests; and, a status change or update in one of the electrical devices.

The status changes or updates in relation to the requests may be a notification that a request has been made and/or that a response is pending. Alternatively, the notification in relation to the requests may include a confirmation that a request, such as an authorisation request, has been successful and that the authorised action is pending, for example. The status change or update in relation to the electrical devices may include a confirmation that a security system is armed/disarmed, or that a door is locked/unlocked. It will be appreciated that other examples will exist.

Additionally or alternatively, the notification may provide user-selectable options which the user, or master user, may select. Such actions may be to: open an app on a mobile device or other computing device or interface; accept or reject an authorisation request; accept or reject an authorised action; or to instruct an action of one or more of the electrical devices. The action of one or more of the electrical device may include: sounding or silencing an alarm; opening/closing and/or locking/unlocking a door; arming/disarming a security system; or, initiating a video or audio recording, for example.

The notifications may be provided by the server or the controller 214. As noted above, the controller may be located local to the premises whereas the server 218 is generally remote and connected to by the system via an external network 220. As such, the server 218 may be employed to manage control systems for several premises 19. Providing a server 218 based notification system is advantageous as the server 218 may be configured to manage notifications for one or more users operating across one or more premises 19. For example, a master user may require an oversight of activity at a plurality or premises and notifications from each premises 19 accordingly.

Providing a server based notification system makes this possible, in contrast to a controller 214 based system which only has oversight of the premises 19 in which it is located. Providing a server based notification system may also reduce number of notification licences or certificates required. Figure 8 shows a method 1000 of operating a notification system as part of a control system. The method 1000 relates to the authorising an action for controlling an electrical device 216a-n within a premises 19 using a server 218. The method 1000 comprises receiving 1056, from a mobile device 210, an authorisation request. The authorisation request may be made in a similar way to the methods described above and may comprise the inclusion of mobile device identification information which is indicative of a user logged into a mobile device and/or of the mobile device itself. The authorisation request may also include RFID identification information and possibly an action which is to be authorised, both of which are discussed above.

Once the authorisation request is received, the server 218 may then determine 1058 whether the mobile device 210, or a mobile device user, is authorised to carry out an authorised action, for example, by carrying out an authorisation process, as discussed above. As with the previously described examples, the authorised action may be associated with an RFID tag located at a fixed location on the premises 19 and relate to a location specific action, such as locking or unlocking a door, or arming or disarming an alarm system, for example.

Once an authorisation request has been received, a notification may be transmitted 1060 to a user in relation to the authorisation request and/or the authorised action. As noted above, the user may be simply provided with information, or required to select a response. The user may be master user, or the user logged into the requesting mobile device. In some embodiments, it is possible for a user or master user to may be sent user identification information in relation to a device or user of a device that read that RFID tag when the reading device or user of the reading device is not pre-registered in a list of authorization users which may be held in the register. That way a device/user that was has not been set up at the server may still be used to request an action, provided it is authorized by an authorized user or master user

As noted above, the RFID tags may provide the mobile device with information in relation to the RFID tag when it is read by the mobile device. The RFID identification information may include information relating to the location of the RFID tag, a predetermined, preassigned task and/or an identifier which can be assigned within the system, by the server for example, to one or more users and/or one or more actions. Hence, an RFID tag may be recorded in the system as being associated with: a specific action, such as ‘arm’ or ‘disarm’; one or more authorised users and/or mobile devices; or a combination of the two.

The RFID identification information may include an identifier which is unique to a specific RFID tag. The identifier may relate to a hardware components which form part of tag and which include unique serial numbers. Thus, the identifier may be a hardware identification number or tag serial number. The identifier may be fixed such that it cannot be altered during use or by a user or installer of the RFID tag or control system. Hence, where the identifier is stored in a memory, the memory may be write protected, for example.

Providing a unique identifier is advantageous as it allows the identifier to be assigned to different purposes within the system. Hence, for example, an RFID tag with the identity of ‘tagl234’, may be assigned to different users within a register of RFID tags and associated authorised actions within the system. As the users and actions associated with the RFID tag are associated using a unique identifier, all that is required is for the server to be passed the identifier and the mobile device identification information (which may relate to the user or mobile device itself). Optionally encryption or security protocols may be carried out by the mobile device when reading the tag. However, it may be preferred in some embodiments not to use such encryption or security protocols for reading the tag, and this may be facilitated by having authorization being based at least in part on the mobile device identification information. This may make the reading of the RFID tags quicker and more efficient, whilst allowing the server, which would typically be better resourced, carry out any computation required for security checks.

Assigning users and authorised actions against each of the RFID tags also allows different users to be authorised for different actions for each of the RFID tags. Hence, a first user, ‘Userl’ may, for example, be a property owner and may be permitted to: access all areas of the premises when entering via a particular entrance; disarm an alarm system; and, enable functionality of preferred home automation devices. A second user, ‘User2’ may be a staff member who may have restricted access beyond the entrance resulting in only a select number of doors unlocking within the property and a different selection of home automation capability. Additionally or alternatively, the property owner may wish to record activity at the premises when ‘User2’ is present and so may choose to activate one or more security cameras or the like when ‘User2’ uses their mobile device to read an RFID tag.

Thus, with reference to Figures 1 and 2, the present disclosure provides a system for authorising an action for controlling an electrical device in a premises using a mobile device, comprising: at least one RFID tag 12a-d for locating at a fixed location at a premises, wherein the RFID tag comprises a data store 222 which is configured to store RFID tag identification information, wherein RFID tag identification information is unique to that RFID tag. The server 18 may be configured to receive the RFID tag identification information from the mobile device 10 which is configured to read the RFID tag identification information at the fixed location.

Further, the controller 14 may be configured to receive an authorised action request from the server, the controller being configured to cause the authorisation action to be executed by the electrical device. The assignment of users and/or actions to an RFID tag may be achieved using a suitable register which is configurable to record a desired matrix of users, actions, and RFID tags/locations. The register may be configured by an installer or user of the system using, for example, a mobile device application. The register may be updated as required, either to add or delete users and/or actions, or update the permissions and/or actions in relation each user. The register may be recalled as part of the authorisation process in response to an authorisation request or action request from a mobile device following a reading of an RFID tag.

Figure 9 shows a method 1100 of authorising an action for controlling an electrical device within a premises using a server. The method 1100 comprising: receiving 1162, from a mobile device, an authorisation request which comprises RFID identification information from an RFID tag located at a fixed location on the premises, wherein the RFID identification information is unique to the RFID tag. A determination is then made as to whether the mobile device or a mobile device user is authorised to carry out an authorised action in relation to the associated with the RFID tag. If the authorisation request is successful, an authorisation request can be transmitted 1164 to a controller instructing the controller to issue a command to an electrical device to carry out the authorised action.

The register may be stored centrally in the server, for example register 239 in the server 218 of Figure 2. This may be advantageous where a register covers multiple premises and/or user groups. Alternatively, a local register may be located at the premises 19, for example, as part of the controller 14. Thus, the server 218 or controller 214 may comprise a non-transitory storage medium comprising one or more registers, each of the one or more registers comprising RFID tag identification information corresponding to one or more RFID tags, wherein, within the register, each of the one or more RFID tags is associated with a plurality of authorised users and at least one authorised action for each of the plurality of authorised users, wherein the at least one authorised action is different for different users.

As with previous embodiments, the requested action which is attributed to each user may be associated with one or more of: arming or disarming a security system associated with the fixed location; and controlling an electrical device within the premises.

In the claims that follow, any reference numerals included within the claims are included merely to aid understanding of the invention with reference to one or more of the exemplary embodiments disclosed herein. The reference numerals do not limit the claims in anyway. It will be understood that the invention is not limited to the examples and embodiments above-described and various modifications and improvements can be made without departing from the concepts described herein. Except where mutually exclusive, any of the features may be employed separately or in combination with any other features and the disclosure extends to and includes all combinations and sub-combinations of one or more features described herein.

Claims

WHAT IS CLAIMED IS:

1. A method (300) of authorising an action for controlling an electrical device in a premises (19) using a mobile device, comprising: reading (344), by the mobile device (10), an RFID tag (12a) installed at a fixed location on the premises (19), to obtain RFID tag identification information (346); and transmitting (348), by the mobile device, an authorisation request to a remote server (18), wherein the authorisation request comprises mobile device identification information and causes the server to carry out an authorisation process using the mobile device identification information to provide an authorised action, wherein the authorised action is associated with the RFID tag; and, transmitting the authorised action to a controller at the premises, wherein the controller is configured to control the electrical device to carry out the action upon receiving the action.

2. The method of claim 1, wherein the mobile device identification information comprises user identification information for a user logged onto the mobile device and/or an identifier for the mobile device which is unique to the mobile device.

3. The method of any preceding claim, wherein carrying out the authorisation process comprises querying a register (239) of authorised mobile devices or mobile device users using the mobile device identification information and, optionally, the register comprises a plurality of users, wherein each user of the plurality of users is associated with user specific authorised actions.

4. The method of claim 3, wherein the plurality of users comprises at least one master user and, optionally, providing a notification on a master user device and/or displaying one or more user-selectable options for a master user to select.

5. The method of claim 4, wherein the user-selectable options on the master user device include one or more of: an authorisation approval; an authorisation rejection; an action request to activate one or more of the electrical devices at the premises and, optionally, wherein the notification on the master user device comprises: a user identifier associated with the mobile device identification information and/or the action for authorisation and/or one or more authorised actions which have been transmitted to the controller.

6. The method of claims 4 or 5, wherein the authorisation process comprises receiving an authorisation confirmation from a master user.

7. The method of any preceding claim, wherein the authorisation request further comprises RFID tag identification information.

8. The method of claim 7, wherein the authorised action is to open an application on the mobile device or display one or more user-selectable options for a user of the mobile device.

9. The method of any preceding claim, wherein the electrical device comprises one or more of: an audio system; a video system; an actuator configured to open, close, lock and/or unlock a door or gate; a lighting system; and, the mobile device.

10. The method of any of claims 7 to 9 when dependent of claim 2, wherein the user identification information comprises an association between a user-determined action and the RFID tag identification information.

11. The method of any of claims 7 to 10, wherein the RFID tag identification information is associated with a pre-determined action stored in a memory of the RFID tag, mobile device or server, or the authorisation request comprises an action upon which the authorised action is based.

12. A method (400) of authorising an action for controlling an electrical device within a premises using a server, comprising: receiving (450), from a mobile device, an authorisation request comprising: mobile device identification information; carrying out an authorisation process (452) to determine whether the mobile device or a mobile device user is authorised to carry out an authorised action, wherein the authorised action is associated with an RFID tag located at a fixed location on the premises; and transmitting an authorised action request (454) to a controller instructing the controller to issue a command to an electrical device to carry out the authorised action.

13. The method of any of preceding claim, further comprising: obtaining, by the server, an RFID tag register comprising RFID tag identification information for a plurality of RFID tags.

14. The method of claims 12 or 13, wherein the RFID tag identification information is unique to that RFID tag.

15. The method according to claim 14, wherein the RFID identification information is associated with a plurality of users, each of the plurality of users having a different authorised action for the unique RFID tag identification information.

16. The method of any preceding claim, further comprising: transmitting, by the server, a notification to a user in relation to the authorisation request and/or the authorised action.

17. The method of claim 16, wherein the notification is one or more of: an authorisation request; an authorised action; a status change in the one or more electrical devices, an action selection; an authorisation rejection; and, an authorisation acceptance.

18. A system (100) for authorising an action for controlling an electrical device in a premises using a mobile device, comprising: at least one RFID tag (12a-d) for locating at a fixed location at a premises, wherein the RFID tag comprises a data store (222) which is configured to store RFID tag identification information; and a server (18) configured to receive an action request in response to an RFID reader, which is configured to read the RFID tag identification information at the fixed location, reading the RFID tag identification information; and, a controller (14) configured to receive an authorised action request from the server, the controller being configured to cause the authorisation action to be executed by the electrical device.

19. The system of claim 18, further comprising the premises and a plurality of RFID tags located at one or more fixed locations at the premises.

20. The system of claims 18 or 19, wherein the or each RFID tag is located proximate to an entrance of the premises.

21. The system of any of claims 18 to 20, wherein the system further comprises one or more electrical devices, wherein the action relates to controlling one of the one or more electrical devices and, optionally, wherein the one or more electrical devices comprises one or more of: an audio system, a video system; an actuator for opening, closing, locking or unlocking a door or gate of the premises; a lighting system or the RFID reader.

22. The system of any of claims 18 to 21, wherein the RFID tag comprises an adhesive for adhering the RFID tag to the fixed location.

23. The system of any of claims 18 to 22, wherein the server comprises a register, the register comprising the RFID tag identification information for one or more RFID tags and an associated authorised user and/or authorised action for the RFID tag identification information for each of the one or more of the RFID tags, wherein the register is amendable by a user such that the authorised user and/or authorised action for each RFID tag of the one or more RFID tags is configurable.

24. A mobile device configured to carry out the method according to any of claims 1 to 11 and/or a server configured to carry out the method according to any of claims 12 to 17.