GB2546484A

GB2546484A - Monitoring system

Info

Publication number: GB2546484A
Application number: GB1600814.6A
Authority: GB
Inventors: De Cock Jacques
Original assignee: Peritempo Ltd
Current assignee: Peritempo Ltd
Priority date: 2016-01-15
Filing date: 2016-01-15
Publication date: 2017-07-26
Also published as: GB201600814D0; WO2017122029A1

Abstract

Attendance management system comprising a database for storing a registree e.g. student profile including a mobile device identifier, and a registrant mobile device to scan a local area to detect mobile devices present and obtain their identifiers. The identifier is compared against profiles in the database to determine attendance status of an attendee corresponding to the device and store in the database. The database may be stored on a server remote from the registrant device, and the device arranged to transmit the obtained identifier to the database. The mobile identifier may be a unique ID code relating to a network interface of the mobile device. The registrant device may provide information on its location while scanning. The registrant device may receive from the database information relating to expected registrees, so that information obtained from detected devices may be compared to this to determine if any expected device has not been detected, and provide to the registrant a notification of any registree whose device has not been detected. The system may also allow manual input if a registree whose device has not been detected is in fact present.

Description

Monitoring system

The present invention relates to monitoring attendance and presence. In particular, the present invention provides a system and method for monitoring, recording and managing attendance and presence.

Monitoring whether a person is in attendance, or present, at a particular place and/or time is common across many industries, for example in the work place or in education, where it is often a legal requirement that student attendance be monitored. Previously, a common approach used in education has been to read out the names of the people expected to be present from a register, or similar list, and to record each person as being present if an affirmative answer is received, or absent if not. This approach is time consuming, particularly when a large number of students are present, and attendance recordal may reduce the time left available for the lesson or lecture. A more efficient system for monitoring the attendance or presence of a person is therefore desirable.

According to an aspect of the invention, there is provided an attendance management system, comprising: a database for storing a profile for a registree, which profile includes a mobile device identifier for a mobile device associated with said registree; a registrant mobile device arranged to scan a local area to detect any mobile devices present and to obtain a mobile device identifier for each mobile device detected; whereby the mobile device identifier can be compared against registree profiles stored in the database such that an attendance status of a registree corresponding to the mobile device can be determined and stored in the database based on the comparison.

According to another aspect of the invention, there is provided a method of monitoring attendance, comprising: scanning, using a mobile device used by a registrant, the local area to detect the presence of any other mobile devices; obtaining the mobile device identifier for each mobile device detected; and comparing the mobile device identifier against known profiles, such that an attendance status of a registree corresponding to the mobile device can be determined and stored in the database based on the comparison.

Optionally, the database may be stored on a server remote from the registrant mobile device and the registrant mobile device is arranged to transmit the obtained mobile device identifier to the remotely stored database.

Optionally, the mobile identifier may be a unique identification code relating to a network interface of the mobile device.

Optionally, the mobile identifier may be a unique identification code assigned to a Bluetooth interface on the mobile device, and wherein the attendance management mobile application is arranged to scan for other mobile devices using Bluetooth.

Optionally, the mobile identifier may be a unique identification code assigned to a Wi-Fi interface on the mobile device, and wherein the attendance management mobile application is arranged to scan for other mobile devices on a local area network / Wi-Fi.

Optionally, the registrant mobile device may be arranged to provide information on its location while scanning.

Optionally, the registrant mobile device may be arranged to receive from the database information relating to expected registrees, to compare the mobile device identifiers obtained from the detected mobile devices to the information received from the database to determine if any expected mobile devices have not been detected, and to provide a notification to the registrant of any registree whose mobile device has not been detected.

Optionally, the registrant mobile device may be further arranged to receive an input from the registrant to indicate that a registree whose mobile device has not been identified is present, and to update the database to confirm attendance of the registree.

Optionally, the registrant mobile device may be arranged to store mobile device identifier information obtained from detected registree mobile device(s) when a network connection is not available, and to transmit the stored information to the database when connected to the network again.

Optionally, the registrant mobile device may comprise an attendance management mobile application arranged to control the registrant mobile device to function as described above.

Optionally, the method may further comprise storing a profile for a registree in a database, which profile includes a mobile device identifier for a mobile device associated with said registree, whereby the mobile device identifier can be compared against known registree profiles stored in the database.

The invention provides a system and method for monitoring attendance at an event simply by detecting the presence of a mobile device associated with a registree (e.g. an attendee) via its unique mobile device identifier. By detecting a unique mobile device identifier assigned to a registree’s mobile device, the registree can be identified by the system without the registree needing to have any specific software (often referred to as an “application” in relation to mobile devices) installed on their mobile device.

Furthermore, by enabling a registrant device to be able to scan for mobile devices in its vicinity, the registration system can be used in any location, rather than relying on specialist equipment that has a fixed location, such as a classroom. It also allows new or temporary registrants (for example, a supply teacher in a school) to use their own mobile devices to perform the attendance check, thereby avoiding the need to familiarise themselves with any specialist hardware.

According to another aspect of the invention, there is provided a computer program and a computer programme product for performing the above-described method. The computer program product may comprise software code adapted, when executed on a data processing apparatus, to perform any of the methods described herein, including any or all of their component steps.

The invention also provides a computer program and a computer program product comprising software code which, when executed on a data processing apparatus, comprises any of the apparatus features described herein.

The invention also provides a computer program and a computer program product having an operating system which supports a computer program for carrying out any of the methods described herein and/or for embodying any of the apparatus features described herein.

The invention also provides a computer readable medium having stored thereon the computer program as aforesaid.

The invention also provides a signal carrying the computer program as aforesaid, and a method of transmitting such a signal.

Furthermore, features implemented in hardware may be implemented in software, and vice versa. Any reference to software and hardware features herein should be construed accordingly.

The registree mobile device may be a cell (or ‘smart’) phone, a PDA, an audio player, a digital camera, a portable electronic game, a tablet device, a Bluetooth tag, or a Bluetooth-enabled watch, for example.

The registrant mobile device is preferably a mobile computing device. Alternatively, the registrant mobile device may be an unmanned / automated sensor device.

As used herein, the term “attendance” may also be used to refer to a person’s “presence” being monitored, for example in class, the workplace or at an event, and vice versa.

As used herein, the term “application” or “app” preferably connotes a self-contained program or piece of software designed to fulfil a particular purpose; the term preferably includes a software application, especially as downloaded by a user to a mobile device.

As used herein, the term “mobile device” preferably connotes a portable electronic device, and includes cell or smart phones, PDAs, audio players, digital cameras, portable games, tablet devices, watches and Bluetooth tags, for example.

As used herein, the term “registree” preferably connotes a person who is registered, such as a student in class, for example. As used herein, the term “registrant” preferably connotes a person who registers something, such as the attendance of a student in class, for example.

As used herein, the term “MAC address” is an abbreviation for “media access control address”, which is a unique identifier, assigned to network interfaces for communications on the physical network segment. MAC addresses are used as a network address for most IEEE 802 network technologies, including Ethernet and Wi-Fi.

As used herein, the term “Wi-Fi” preferably connotes a local wireless computer networking technology defined by the IEEE 802.11 standards.

As used herein, the term “UUID” is an abbreviation for “Universally unique identifier”, which is a used in mobile devices for uniquely identifying the device via its Bluetooth.

As used herein, the term “Bluetooth” preferably connotes a wireless technology standard for exchanging data over short distances, previously standardised in the IEEE 802.15.1 set of standards.

Any feature in one aspect of the invention may be applied to other aspects of the invention, in any appropriate combination. Any system feature as described herein may also be provided as a method feature, and vice versa. As used herein, means plus function features may be expressed alternatively in terms of their corresponding structure.

Furthermore, any, some and/or all features in one aspect can be applied to any, some and/or all features in any other aspect, in any appropriate combination.

It should also be appreciated that particular combinations of the various features described and defined in any aspects of the invention can be implemented and/or supplied and/or used independently.

An embodiment of the present invention will now be described, by way of example only and with reference to the accompanying drawings, in which:

Figure 1 shows an overview of a system according to the present invention;

Figure 2 shows an example of unique (MAC address) identifiers assigned to a mobile device; Figure 3 illustrates a flow chart of a registration process;

Figure 4 illustrates a registration process; and Figure 5 illustrates an attendance capturing process.

Overview

Figure 1 shows an embodiment of an attendance management system 100. A database 110 is provided, which is accessible via a network. The network may be the local area network of the location in which the event is being held, with the database 110 being stored locally on a server 120 at that location. The network may instead be a mobile (or cellular) network, or a distributed (‘internet’) network, with the database 110 being stored at a location remote from the event, or in ‘the cloud’. Optionally, the server 120 is further connected, preferably via the network, to an administrator workstation 170 to facilitate administrative control.

The database 110 is arranged to store a profile for each registree 130 whose attendance is to be managed. Each profile should include at least the identity of the registree 130 and a unique mobile device identifier assigned to a mobile device 140 that is associated with (e.g. used and/or carried by) the registree 130. The unique mobile identifier may be a universally unique identifier (UUID) or media access control (“MAC”) address, for example. The registree profile may include additional data about the registree 130, such as their date of birth, timetable of expected locations/classes and previously recorded attendance data, as required. A mobile device 150 for use by a registrant 160 is also provided. The registrant mobile device 150 is arranged to scan a local area to detect other mobile devices 140 in the vicinity (or ‘local area’). The local area may be of up to 10m radius from the mobile device 150, for example, depending on the power of the detecting signal emitted by the registrant mobile device 150.

Both the registrant mobile device 150 and the registree(s) mobile device(s) 140 should have at least one of Bluetooth or Wi-Fi capability, wherein the registrant mobile device 150 may be arranged to provide ‘hotspot’ functionality to allow the registree(s) device(s) 140 to connect to it. Preferably, the registrant mobile device 150 has both Bluetooth and Wi-Fi capability, so that it can detect both UUID and MAC addresses.

Generally, every mobile device 140 that has Bluetooth and/or Wi-Fi capability is assigned one or more unique mobile device identifier(s), which identify the respective network interface, such as the Bluetooth or Wi-Fi interface, installed in the mobile device 140. The unique identifier for a Bluetooth interface in a mobile device is a ‘UUID’, which is simply a 128-bit value. The unique identifier for a Wi-Fi interface in a mobile device is a MAC address, which is formed of six groups of two hexadecimal digits that act as a unique network address. The UUID or MAC address assigned to a device network interface is a permanent and globally unique identification of that particular interface.

Figure 2 shows an example of a settings screen on a mobile device 140, illustrating the unique identifier information assigned to that mobile device 140. As can be seen, the mobile device 140 has both Bluetooth and Wi-Fi capability, with both the UUID of the Bluetooth network interface and the MAC address of its Wi-Fi network interface being provided.

Attendance management system

As shown in Figure 4, the database may be populated during a registration event, where each attendee creates a profile and provides the unique mobile device identifier of a mobile device 140 associated with them. In the example shown, the registree mobile devices 140 may be registered via the registrant mobile device 150.

When Bluetooth is enabled on the registrant mobile device 150, it discovers any Bluetooth-enabled mobile devices in range. A pairing request is sent by the registrant mobile device 150 to the registree mobile device 140. The registree 130 has to accept the request on their mobile device 140. While pairing, the registrant mobile device 150 collects the required unique identifier data from the registree device 140.

Alternatively, the registrant mobile device 150 activates a Wi-Fi hotspot, to which the registree mobile device 140 has to be connected. While connecting, the registrant mobile device 150 collects the required unique identifier data from the registree device 140. Registering using WiFi may also enable the registrant mobile device 150 to obtain further data, including the MAC address and device model, for example.

To ensure that their attendance can be recorded, when present at a subsequent event, each registree 130 should ensure that the mobile device identifier assigned to their mobile device 140 can be detected. For example, the mobile device 140 may have Bluetooth or Wi-Fi capability, which should be enabled.

As shown in Figure 5, the registrant mobile device 150 scans the vicinity (i.e. a local area) for other mobile devices 140 and detects the mobile device identifiers of any enabled’ mobile devices 140 in range.

The detected mobile device identifiers are compared to the mobile device identifiers stored on the database 110, and when a match is detected the registree associated with the detected mobile device identifier is recorded as having attended (or been ‘present’).

If the registrant mobile device 150 detects a mobile device identifier that does not match any profile stored on the database 110, the unknown mobile device identifier can be added to the database 110 and a new profile created. This is a simple way to create profiles for new attendees on the database 110, who have not already registered.

Similarly, the registrant mobile device 150 may alert the registrant 160 to the fact that an unexpected mobile device 140 has been detected, so that the registrant can take the necessary action to remove an unwanted attendee.

If the registrant mobile device 150 does not detect the mobile device identifier of a registree 130 that is expected to be present at a particular event, that registree 130 is recorded as having been absent at that event on the database 110. The registrant mobile device 150 may be configured to alert the registrant 160 to the fact that one or more expected mobile device identifiers have not been detected, preferably providing the registrant with information on the identity of the registree 130. The registrant 160 may then visually scan the registrees 130, to confirm whether the expected registree 130 is actually present but has not activated their mobile device, or have forgotten their mobile device, for example.

Attendance management application

An attendance management application (“the App”) may be installed on the mobile device 150 of the registrant 160, wherein the App is capable of interfacing with the Bluetooth and/or Wi-Fi capability of the registrant mobile device 150, as follows.

When being used to record the attendance status of a registree 130 (for example in a class or lecture), the registrant 160 activates the App on his or her mobile device 150. The App causes the mobile device 150 to scan the vicinity to identify any Bluetooth and/or Wi-Fi enabled mobile devices 140 via their unique mobile device identifiers.

The App is operable to access the database 110, via the network, and to compare on the registrant mobile device 150 any detected mobile device identifiers against the profiles stored on the database 110 to determine an attendance status. Alternatively, the App can send the detected mobile device identifiers, via the network, to the attendance management server 120 to be compared against profiles stored on the database 110 remotely. Data relating to the mobile device identifiers may be stored locally on the registrant mobile device 150 until it can connect with the network, should a connection be temporarily unavailable. Optionally, the App updates a cloud-based database via the internet, to which it which can connect via Wi-Fi or a cellular network.

To detect Wi-Fi enabled registree mobile devices 140 in the vicinity of the registrant mobile device 150, the App may access a wireless local area network (WLAN) in the vicinity of the registrant mobile device 150. The local network can then be scanned for any other mobile devices 140 that may be connected to it, and their unique mobile device identifiers can be acquired. The identifiers are preferably the MAC address assigned to the WiFi network interface installed in each mobile device 140.

The mobile device identifier of each device 140 detected by the App is sent to the server 120 where it is compared against the profiles stored in the database 110. Based on the comparison, a profile of a registree 130 associated the detected mobile device 140 can be identified and the matched registree 130 can be recorded as present at the event (e.g. at class).

The database 110 may also contain the expected location of each registree 130 at a particular time - for example his or her timetable and the location of each scheduled event (e.g. each class or lesson). If the identifier of a mobile device 140 associated with a registree 130 is not detected by the App on a registrant’s mobile device 150 at the expected time and/or location, then that registree 130 can be recorded as being absent in the database 110. The registrant mobile device 150 may also have location capability for determining the location of the registrant 160. Location capability, such as GPS for example, should of course be activated on the device when required for these features.

Alternatively, if the mobile device 140 of a registree 130, who is expected at an event, is not detected, the system may be configured to notify the registrant 160 via the App on their mobile device 150. If the registree 130 is in fact present, but his or her mobile device 140 is not present or is not activated, then the registrant 160 can override the App and send the registree attendance status to the database 110 via the App, to mark the registree 130 as present. This feature can help prevent malfunctions or misuse of a registree mobile device 140 resulting in the registree 130 being incorrectly recorded as being absent.

An attendance record can be kept for each registree 130 using the information that is saved on the database 110. This record can be accessed by an administrator 170 connected to the network in order to analyse the attendance of the registree 130. Data obtained from a registree mobile device 140 may include the following: UUID, MAC address, device type, device name, and device model. Similarly, data that may be obtained from the registrant mobile device 150 may include the following: location, UUID and MAC address.

The database 110 can be accessed, via the network, by multiple mobile devices 150 of different registrants 160, at the same time. This allows the attendance of more than one registree 130 in multiple locations to be recorded substantially simultaneously.

It will be understood that the present invention has been described above purely by way of examples, and modifications of detail can be made within the scope of the invention.

Claims

1. An attendance management system, comprising: a database for storing a profile for a registree, which profile includes a mobile device identifier for a mobile device associated with said registree; a registrant mobile device arranged to scan a local area to detect any mobile devices present and to obtain a mobile device identifier for each mobile device detected; whereby the mobile device identifier can be compared against registree profiles stored in the database such that an attendance status of a registree corresponding to the mobile device can be determined and stored in the database based on the comparison.

2. A system according to Claim 1, wherein the database is stored on a server remote from the registrant mobile device and the registrant mobile device is arranged to transmit the obtained mobile device identifier to the remotely stored database.

3. A system according to Claim 1 or 2, wherein the mobile identifier is a unique identification code relating to a network interface of the mobile device.

4. A system according to any preceding claim, wherein the mobile identifier is a unique identification code assigned to a Bluetooth interface on the mobile device, and wherein the attendance management mobile application is arranged to scan for other mobile devices using Bluetooth.

5. A system according to any of Claims 1 to 3, wherein the mobile identifier is a unique identification code assigned to a Wi-Fi interface on the mobile device, and wherein the attendance management mobile application is arranged to scan for other mobile devices on a local area network / Wi-Fi.

6. A system according to any preceding claim, wherein the registrant mobile device is arranged to provide information on its location while scanning.

7. A system according to any preceding claim, wherein the registrant mobile device is arranged to receive from the database information relating to expected registrees, to compare the mobile device identifiers obtained from the detected mobile devices to the information received from the database to determine if any expected mobile devices have not been detected, and to provide a notification to the registrant of any registree whose mobile device has not been detected.

8. A system according to Claim 7, wherein the registrant mobile device is further arranged to receive an input from the registrant to indicate that a registree whose mobile device has not been identified is present, and to update the database to confirm attendance of the registree.

9. A system according to any of Claims 2 to 8, wherein the registrant mobile device is arranged to store mobile device identifier information obtained from detected registree mobile device(s) when a network connection is not available, and to transmit the stored information to the database when connected to the network again.

10. A system according to any preceding claim, wherein the registrant mobile device comprises an attendance management mobile application arranged to control the registrant mobile device to function as described in any of Claims 1 to 9.

11. A method of monitoring attendance, comprising: scanning, using a mobile device used by a registrant, the local area to detect the presence of any other mobile devices; obtaining the mobile device identifier for each mobile device detected; and comparing the mobile device identifier against known profiles, such that an attendance status of a registree corresponding to the mobile device can be determined and stored in the database based on the comparison.

12. A method according to Claim 11, further comprising storing in a database a profile for a registree, which profile includes a mobile device identifier for a mobile device associated with said registree, whereby the mobile device identifier can be compared against known registree profiles stored in the database.

13. A computer programme product for performing the method of Claim 11 or 12.

14. A system substantially as described herein with reference to the accompanying drawings.

15. A method substantially as described herein with reference to the accompanying drawings.