Attendance monitoring systems

Abstract

An attendance monitoring system (10) includes at least one registration device (16) having at least one sensor (18) to sense respective input attendee data identifying respective attendees and a communications device (14) configured to transmit to a remote storage and processing facility (16). The communications device (14) or at least one registration device (14) includes a processor and memory. The processor is configured to compare respective input attendee data with attendee data stored in said memory to determine a verification status record for the respective attendee.

Description

[0001] Field of the Invention

[0002] The invention relates to attendance monitoring systems and particularly, but not exclusively, to attendance monitoring systems for use in educational facilities such as schools and universities. Embodiments of the invention relate to AMS that monitor attendance by enabling the registration and tracking of attendees. This may include students and employees, using a range of identification methods. These methods may comprise, but are not limited to, RFID cards, NFC- enabled phones, QR codes, and biometrics such as voice, face, and fingerprint recognition. Additionally, embodiments of the system may offer registration by proximity, eliminating the need for direct user interaction. The system may provide a capability for comprehensive data collection, which subsequently transmits the data to a backend system for storage, analysis, and report generation. Embodiments of the invention may allow the optimisation of power consumption, and data storage and communication load.

[0003] Background to the Invention

[0004] Attendance monitoring has become a pressing issue in various organisations, including educational institutions and workplaces. Traditional methods of recording attendance are often time-consuming, prone to errors, and challenging to manage and analyse. Moreover, many existing systems necessitate considerable supplementary infrastructure, leading to increased costs and complexities during implementation. While there have been numerous developments in attendance monitoring systems using technologies such as RFID, NFC, and biometrics, many still grapple with issues like high implementation costs, intricate infrastructure prerequisites, and a lack of versatility in data analysis and reporting. Consequently, there is a distinct need for a more efficient, versatile, and cost-effective attendance monitoring systems to at least partially overcome the limitations of both traditional and contemporary systems, or at least provide an alternative to existing products on the market.

[0005] Summary of the Invention

[0006] The invention provides an attendance monitoring system comprising: at least one registration device comprising at least one sensor to sense respective input attendee data identifying respective attendees; and a communications device configured to transmit to a remote storage and processing facility, wherein said communications device or said at least one registration device comprises a processor and memory, said processor configured to compare said respective input attendee data with attendee data stored in said memory to determine a verification status record for the respective attendee.

[0007] Preferably said processor is configured to cause said communications device to transmit attendee enquiry data to said remote storage and processing facility when said comparison fails to match the respective input attendee data with attendee data stored in said memory and receive a verification status record for the respective attendee from said storage processing device based on said attendee enquiry data.

[0008] Preferably during a predetermined attendee registration time period, said processor is configured to limit transmissions by said communications device to said remote storage and processing facility to attendee enquiry data.

[0009] Preferably said processor is configured to provide a verification signal based on said verification status record and said at least one registration device comprises a notification unit to notify the respective attendee of their verification status based on said verification signal.

[0010] Preferably said notification unit comprises a visual display component to visually notify said verification status.

[0011] Preferably said processor is configured to cause said communications device to transmit verification status records as data sets comprising respective verification records for a plurality of attendees.

[0012] Preferably said at least one sensor comprises: i) an RFID reader; ii) an NFC reader; or iii) a biometric sensor.

[0013] Said at least one registration device is connected to said communications device by a wireless signal technology.

[0014] Some embodiments may comprise a combined registration and communications device comprising a housing arrangement that houses a said registration device and said communications device and wherein said registration device is connected with said communications device by wiring. Preferably said communications device is configured to communicate with said remote storage and processing facility via a WIFI communications protocol, a USB or an ethernet connection.

[0015] Preferably said at least one registration device and said communications device are battery powered.

[0016] The invention also provides a method of monitoring attendance at a venue, said method comprising: providing at said venue at least one registration device provided with a sensor to sense respective input attendee data identifying respective attendees; providing said at venue a communications device configured to transmit to a remote storage and processing facility that is disposed at a location remote from said venue; electronically processing said respective input attendee data at said at least one registration device or said communications device to verify the respective attendee by matching the respective attendee input data with attendee data stored in a memory provided at said at least one registration device or said communication device to determine a verification status record for the respective attendee.

[0017] Transmitting to said remote storage and processing facility by said communications device may comprise transmitting data sets comprising a plurality of said verification status records at predetermined spaced apart intervals. Said predetermined intervals may be: i) intervals of time; or ii) intervals based on accumulating a predetermined number of verification status records.

[0018] Preferably when a said respective attendee input data does not match attendee data stored in said memory, the method further comprises transmitting enquiry data based on the not matching respective attendee input data to said remote storage and processing facility by said communication device for matching with attendee data stored at said remote processing and storage facility and receiving at said communications device a verification status record based on matching said enquiry data with attendee data stored at said remote storage and processing facility.

[0019] The remote processing and storage facility may comprises: i) a laptop or desktop computer; ii) a server; or iii) a cloud storage processing and storage facility. The venue may be a class room or lecture room.

[0020] The invention also includes an attendance monitoring system comprising: at least one registration device comprising at least one sensor to sense respective input attendee data identifying respective attendees and a wireless communications unit; and a communications device local to said at least one registration device and configured to transmit to a remote storage and processing facility, wherein said wireless communications unit is configured to transmit attendee related data to said communications device and said communications device is configured to communicate the attendee related data received from said at least one registration device to said remote storage and processing facility as batched data comprising attendee related data relating to a plurality of attendees.

[0021] The at least one registration device may comprise a processor and memory and said processor is configured to compare said respective input attendee data with attendee data stored in said memory to determine an attendee verification status, said attendee related data communicated to said communications unit is said attendee verification status and said batched data comprises attendee verification status data for a plurality of attendees.

[0022] Preferably said communications device comprises a processor and memory and said processor is configured to compare said respective input attendee data with attendee data stored in said memory to determine an attendee verification status and said batched data comprises attendee verification status data for a plurality of attendees.

[0023] The attendance monitoring system may comprise a combined registration and communications device comprising a housing arrangement that houses a said registration device and said communications device and wherein said registration device is connected with said communications device by wiring.

[0024] Preferably said communications device is configured to communicate with said remote storage and processing facility via a WIFI communications protocol or a USB or ethernet connection. Preferably said at least one registration device and said communications device are battery powered.

[0025] Said at least one sensor may comprises: i) an RFID reader; ii) an NFC reader; or iii) a biometric sensor.

[0026] Discussion

[0027] The attendance monitoring systems (AMS) referred to herein offer a capability for enhanced attendance monitoring that facilitates straightforward registration and tracking of attendees using one or more of the following two methods:

[0028] 1 . By-interaction: This approach necessitates the attendee’s engagement with a registration device. It could involve tapping RFID cards (referred to as “By-card”), using NFC-enabled phones (“By-phone”), or scanning QR codes, other identification techniques, including voice, face, and fingerprint recognition.

[0029] 2. By-proximity: In this method, users are not required to undertake any explicit action to register their attendance. Attendance is documented based on data collected from the user's mobile phone, which interacts with Bluetooth emitters or other signalling devices like Wi-Fi set up in the rooms. An advanced version of this system can pinpoint a user's location within a room using triangulation techniques, akin to those found in GPS systems.

[0030] Our system prioritises the optimisation of both power consumption and data communication, removing the need for intricate and expensive supplementary infrastructure.

[0031] The AMS may comprise several primary components:

[0032] 1 . By-interaction method: a. Registration Device: This device facilitates the registration of the user's identity. These devices are battery-powered. b. Communication Hub: Serving as a conduit between the registration devices and data storage. These hubs draw power from USB ports or other external power sources.

[0033] 2. By-proximity method: a. Beacons: These include Bluetooth emitters and other signal devices such as WiFi. Their function is to broadcast signals that mobile phones detect. The data received is then relayed to the server to document attendance. These beacons are battery-powered. 3. Backend Service: Typically hosted on cloud platforms, this service provides the necessary infrastructure for data storage, management, exportation, and analysis.

[0034] 4. Mobile Application: Through this app, users can register their attendance using their phones. It plays a pivotal role in different registration methods like 'By-phone' and 'Byproximity'.

[0035] The novelty of this invention centres on the following aspects:

[0036] 1. Power Conservation: The invention drastically minimises power consumption, enabling the device to function for an extended duration on a single battery charge. Crucially, this also pertains to its connectivity with the communication hub, facilitating efficient data transfer to the backend.

[0037] 2. Data Optimisation: The invention refines the data storage and communication between devices (for instance, between the registration devices and the communication hub) and the backend. This not only diminishes power consumption but also enhances response time.

[0038] Brief Description of the Drawings

[0039] Figure 1 is a schematic representation of an attendance monitoring system;

[0040] Figure 2 is schematic representation of another attendance monitory system;

[0041] Figure 3 is a schematic representation of a registration device of the attendance monitoring system of Figure 1 ;

[0042] Figure 4 is a schematic representation of a communications hub of the attendance monitoring system of Figure 1 ;

[0043] Figure 5 is a schematic representation of a combined registration device and communications hub usable in the attendance monitoring system of Figure 1 as alternative to the registration device and communications hub shown in Figures 3 and 4;

[0044] Detailed Description

[0045] Referring to Figure 1 , an attendance monitoring system 10 comprises at least one registration device 12 and a communications device 14. The communications device 14 is configured to transmit to a remote processing and storage facility or backend service 16.

[0046] Referring to Figure 2, the at least one registration device 12 are used to collect attendee data or information. A registration device 12 comprises at least one sense unit 17 that comprises at least one sensor 18 to sense respective input attendee data identifying respective attendees. Various configurations are possible, each is tailored to gather specific forms of attendee input data such as RFID, NFC, and biometric data. Thus, the at least one sensor 18 may comprise a RFID reader, an NFC reader or a biometric sensor.

[0047] In this embodiment, the at registration device 12 comprises a processing unit 20 comprising a processor 22 and memory 24. The registration device 12 further comprises a communications unit 26 configured to transmit to the communications device 14 using a local wireless signal. In the illustrated embodiment the communications unit 26 comprises a Bluetooth communication component. Depending on the model, the Bluetooth component might utilise traditional Bluetooth protocols or Bluetooth Low Energy (BLE) to minimise power consumption. In other embodiments, the communications unit 26 may be configured to transmit to the communications device 14 by an infrared component using infrared technology such as IrDA technology or other wireless protocols such as ZigBee®or UWB ultra-wideband technology. Generally, it is preferred that the communications unit 26 employs a wireless transmission technology that requires low levels of power so that the registration device 12 can be battery powered and not require frequent replacement of or recharging of its batteries.

[0048] The registration device 12 further comprises a power unit 30 comprising one or more batteries 32 and a power regulator 34 or other power supply mechanism configured to distribute electrical power to the various components of the registration device 12 that require electrical power.

[0049] The registration device 12 further comprises a notification unit 36. The notification unit is 36 is configured to provide an indication of verification status to attendees that use the registration device 12 to record their attendance at a venue. Preferably the notification unit 36 is configured to provide visual notifications of verification status. For example, the notification unit 36 may comprise coloured lights indicating respective verification status to notify the attendee of their verification status. Thus, there might be red, amber and green to respectively notify the verification status as ‘attendance not verified or recorded’, ‘attendance recorded but not verified’ and ‘attendance verified and recorded’. Referring to Figure 4, the communications device 14 comprises a processing unit 50 comprising a processor 52 and memory 54, a communications unit 56 configured to communicate with the at least one registration device 12 and a communications unit 58 configured to communication with the backend service 16. Thus, for example, the communications unit 56 may comprise a Bluetooth component to communicate with a registration device 12 whose communication unit 26 is configured to transmit data using a Bluetooth protocol. The communications unit 58 is preferably configured to communicate with the backend service 16 by wireless transmission or using a Wi-Fi protocol or may be connected with a modem via a USB connection or an ethernet connection.

[0050] The communications device 14 further comprises a power unit 60. The power unit 60 may correspond to the power unit 30 illustrated in Figure 3, so that the communications device 14 is battery-powered. However, in the illustrated embodiment, the power unit 60 is configured to receive power from an external source by a USB connection or a mains electricity and comprises a power regulator for distributed required electrical power to the components of the communications device that require electrical power. It is advantageous that the at least one registration unit 12 is battery-powered and communicates wirelessly with the communications device 14 so that it can be positioned freely at a venue without the need to provide infrastructure such as a power supply or data connection. Thus, a plurality of registration devices 12 may be provided at a venue to allow greater flexibility and opportunity for attendees to verify their attendance. While it may be convenient to also have a battery-powered communications device 14, this is not so important as only one is needed and it does not need to be accessible by attendees. Thus, in some embodiments power supply and data communication may be by wired connections as described above.

[0051] The communications device 14 has two principal responsibilities:

[0052] 1 . Serving as an intermediary between the at least one registration device 12 and the backend service 16.

[0053] 2. Functioning as a data server to supply information to the registration devices.

[0054] The attendance monitoring system 10 may optimise power consumption and data transmission capacity through one or more of the following mechanisms:

[0055] A. Standby Mode for Devices: Both the at least one registration device 12 and the communications device 14 may remain in standby mode for most of their operational time, only becoming active when required for attendance monitoring at an event, such as a class or lecture.. The attendance monitoring system 10 may we woken from standby mode by a user input signal manually input at the at least one registration device 12 or the communications device 14. Alternatively, the communications device 14 may be configured to receive a wake-up signal from the remote storage and processing facility 16 and transmit a wake-up signal to the at least one registration device 12. In still further embodiments, events within the at least one registration device 12 may be initiated by the sense unit(s) 17. They are dispatched to the processing unit 20 when a valid form of identification is detected, such as an RFID card, an NFC-enabled mobile phone, a fingerprint, or a facial recognition. For the communication device 14, events by the need to relay data to and from the backend 16, as well as between itself and the at least one registration device 12.

[0056] B. Batch Data Communication: Data may be relayed between the at least one registration device 12 and the communications device 14 or the communications device 16 and the backend service 16 in aggregated batches or data sets, substantially reducing the communication overhead associated with each packet of information. This approach is particularly implemented when the communications device 14 forwards data to the backend service 16.

[0057] C. Internal Data Verification: Upon receiving input attendee data at the at least one registration device 12, the processing unit 20 or the processing unit in the communications device 14 cross- references this input attendee data against attendee data held in the respective memory to determine the verification status. If a match is identified, a verification signal is notification unit 36 to cause the notification unit to notify the attendee that they have been verified. In the absence of a match, the communications device 14 may transmit attendee enquiry data to the backend service 16 for further verification against attendee date held by the backend status that typically stores attendee data for a larger group of potential attendees than is held by the at least one registration device 12 or communications device 14.

[0058] D. Energy-efficient Data Transmission: Data communication between the at least one registration device 12 and the communications device 14is preferably by a low energy or power technology, such as Bluetooth and preferably by a low-power Bluetooth protocol. Thus, rather than dispatching data directly from the at least one registration device 12 to the backend service 16 using a power-intensive Wi-Fi connection, the data is first channelled to the communications device 14 through this energy-conserving protocol.

[0059] Collectively, these strategies significantly mitigate power consumption and data communication demands. As a result, there's a pronounced extension in battery longevity and a reduction in network load.

[0060] The attendance monitoring system revolves around the strategic minimisation of communication demands. By doing so, power consumption is curtailed while still ensuring that the registration devices are adequately supplied with the requisite data: Scheduled Data Communication: The device retains data and schedules its communication with the backend at predetermined intervals. These intervals can be tailored to align with specific business needs, be it after a designated number of registrations or after a set time frame.

[0061] Storage of Priority Data: Given the magnitude of target users, the device judiciously stores only the data that is most likely to be required.

[0062] The term 'most likely required data' pertains to the subset of data residing on the device that is predominantly essential for its routine operation. To illustrate, in a university with 20,000 students, not every student would frequent a specific lecture theatre. Over time, the device intelligently optimises its data storage, retaining only the details of students who are regular attendees of that particular venue. Such a strategy markedly reduces the necessity to liaise with the backend for data retrieval. This optimisation is facilitated by appending time-tags to the data, and systematically purging the oldest records when memory approaches its capacity.

[0063] Referring to Figure 5, the at least one registration device 12 and communications device 14 may be provided in a common housing arrangement 72 to form a combined registration device and communications device 74. The components of the combined registration device and communications device 74 may correspond to the those of a registration device 12 as shown in Figure 3 and a communications device 14 as shown in Figure 4, except there is no Bluetooth or other wireless signal technology for communicating between the registration device and communications device and there is only one processing unit. To avoid repetition of description, component corresponding at least substantially to components shown in Figures 3 and 4 are indicated by the same reference numerals and will not be described again. The combined registration device and communications device 74 may require external power supply (e.g., a USB). However, in the illustrated embodiment, the combined registration device and communications device 74 is shown provided with a battery-powered power unit 30. The combined registration device and communications device 74 may be used for temporary installations when, for example on field trips or using rooms at a school or university that are not usually used for events that require attendance monitoring.

[0064] Unlike registration devices and communication hubs, which gather data and liaise with the server directly, beacons adopt a distinctive approach: they facilitate a service wherein the data acquisition and communication with the server are orchestrated by the user’s mobile phone. Here's how it operates:

[0065] Beacons emit a signal at specified intervals, which is detected and recorded by the user’s mobile phone. This signal encapsulates various elements:

[0066] 1. Signal Data: This pertains to the information embedded within the signal itself, which could encompass aspects like a specific code or the current battery level. This data could be encrypted for further security.

[0067] 2. Signal Characteristics: This refers to the qualities of the received signal, like its strength. The amalgamation of these data points yields two discernible types of information:

[0068] 1. User Presence: Given that the user’s mobile phone can only detect the beacon's signal when in close proximity, any recorded signal is a testament to the user's presence in a designated room or space.

[0069] 2. Approximate User Location: The signal characteristics, such as its strength, provide insight into the gap between the beacon and the user’s mobile phone in a radial manner around the beacon. With the strategic placement of multiple beacons within a space, the system is adept at pinpointing the rough location of the mobile phone through triangulation techniques.

[0070] The structural composition of the beacon is segmented into:

[0071] 1 . Processing Unit: This encapsulates both the logic unit and memory storage.

[0072] 2. Communication Unit: Predominantly anchored by a Bluetooth communication component, its mandate is to broadcast signals at predetermined intervals. Depending on its design, it might employ conventional Bluetooth protocols or gravitate towards Bluetooth Low Energy (BLE) for enhanced power efficiency.

[0073] 3. Power Unit: Comprising a battery coupled with a power supply mechanism, it furnishes the vital energy required for the seamless operation of the device.

[0074] The backend service 16 is responsible for storing the data regardless of method of registration, as well as communicating with the communication hubs in the case of by-interaction registration.

[0075] Mobile Application

[0076] The Mobile Application serves as a personal, convenient tool for users to register their attendance. It leverages NFC technology in smartphones, allowing users to simply tap their phone on the RFID / NFC Collection Device to register attendance. The application also utilises various phone sensor data to validate user location and timing, ensuring accurate attendance registration. This feature offers a layer of redundancy in attendance tracking, further ensuring the reliability of attendance data.

[0077] The application also offers remote tracking capabilities by analysing signal RSSI from different sources, such as Wi-Fi, BLE, GSM, and GPS. This multi-faceted approach to location verification ensures accurate attendance tracking, even in complex or large environments.

[0078] In summary, the system presents a holistic, multi-faceted approach to attendance tracking, offering a high degree of accuracy, convenience, and security. Each component plays a crucial role, together creating a comprehensive solution that surpasses traditional attendance systems in versatility, user-friendliness, and robustness. The proprietary technologies and unique combination of features warrant patent protection to safeguard the significant investment and innovation embedded in this system.

[0079] Registration By-proximity

[0080] Central to our system is the avant-garde 'registration by-proximity' feature. This system offers a plethora of advantages and superior functionalities over alternative registration modalities:

[0081] 1 . Absence of User Interaction: Users simply need to activate their Bluetooth and location settings (contingent on the mobile model and OS version). Thereafter, the system, encompassing both the hardware and app, will autonomously log their attendance.

[0082] 2. Periodic Attendance Logging: Traditional registration systems typically record attendance upon entry and occasionally upon exit. However, the registration by-proximity mechanism has the capability to record attendance at predetermined or sporadic intervals, ensuring continuous presence during a session. This introduces heightened reliability; for instance, if students depart mid-session, the system diligently detects and documents this behaviour.

[0083] 3. Distributed Data Acquisition: Contrary to systems that centralise data gathering and communication through a singular hub (e.g., the communication hub), the by-proximity method leverages the user's mobile for data acquisition. This decentralisation ensures there's no ceiling to the concurrent number of users marking their attendance.

[0084] 4. Instantaneous Attendance Registration: As mobile phones facilitate parallel data collection, bottlenecks at entry points, such as queues, are eradicated.

[0085] 5. Locational Insights with Multiple Beacons: Harnessing distance calculations, triangulation, and advanced techniques underpinned by artificial intelligence and big data analytics, the system can deduce the approximate positioning of users with the aid of two or more beacons. This granular insight can be instrumental in discerning movement patterns and interpersonal interactions.

[0086] This pioneering technology is meticulously developed to verify a user's presence in a designated space or location over a sustained period, delivering unparalleled accuracy and dependability in tracking. At its core, the technology harnesses a mixture of signal sources, combined with advanced analytical methodologies, to yield an exhaustive and precise depiction of a user's whereabouts.

[0087] The key point of this innovation is the 'signal fusion algorithm'. This sophisticated algorithm amalgamates data from a plethora of signal sources, encompassing GPS, GSM, local BLE nodes, and Wi-Fi SSIDs. Such a multifaceted data fusion guarantees meticulous user tracking, even in locales characterised by intricate signal topographies or fluctuating conditions.

[0088] By contrasting individual user metrics with collective data from a broader user base, the system is adept at pinpointing trends, anomalies, and correlations. This parallel analysis bolsters the precision of the attendance monitoring, furnishing an indomitable and trusty metric of user presence and locomotion within a stipulated region.

[0089] The capability to oversee user attendance longitudinally, rather than merely at ingress points, proffers a myriad of pronounced benefits:

[0090] 1 . Accuracy & Reliability: Persistent monitoring offers a holistic picture of user attendance, mitigating the pitfalls of spurious or overlooked registrations.

[0091] 2. Insight into User Behaviour: Recording user movements over durations empowers the system to gather invaluable information on behavioural trends, like predominant active intervals, high-traffic zones, and circulation pathways. Such insights can be instrumental in refining space utilisation, marshalling resources, and strategising operations.

[0092] 3. Augmented Security: The continuous surveillance increases security measures by promptly detecting any unwarranted intrusions or atypical activities within the space.

[0093] 4. Operational Efficiency: The benefit of real-time attendance observation facilitates swift interventions and recalibrations, heightening the efficacy of operations.

[0094] 5. Adaptable Design: The system's flexibility ensures its suitability for a vast spectrum of applications. For enhanced security and reliability, the broadcasted data could be encrypted:

[0095] 1. Temporal Encryption: By incorporating the current time, down to the minute, into the broadcasted data packet, you ensure that the encryption changes dynamically. This frequent change renders any captured packets obsolete in a matter of minutes, reducing the likelihood of successful breaches. Furthermore, by synchronising the beacon's internal clock with a trusted time source (e.g., an atomic clock), you can prevent adversaries from predicting future encrypted strings.

[0096] 2. Spatial Encryption: The beacon's broadcast can also be encrypted based on its physical location, such as its assigned room number or geocoordinates. By integrating the location data with other encryption elements, the system creates a multi-layered encryption technique. This not only reinforces security but also aids in verifying the authenticity of the beacon's broadcasts, ensuring users are genuinely at the designated location.

[0097] 3.

[0098] The background service on the user’s device holds the necessary keys to decrypt the broadcast data. It verifies the location and time values match the expected meeting information to confirm the device's presence in the meeting space.

[0099] Disappearance of the beacon signals suggests the attendee has moved outside the range of the transmitters, indicating early departure. The service records this transition in attendance status.

[0100] Figure 1

[0101] Schematic of the system detailing the registration-by-interaction method. The registration by interaction requires at least one registration device. The other components include a communication hub that creates an interface between the registration device and the backend service. The communication hub also serves as memory storage to store the UIDs and UUlDs of cards and phones. However, this data can vary based on the method of registration implemented in the registration devices. Communication between the registration devices and the communication hub occurs via Bluetooth, while communication between the communication hub and the backend service is via Wi-Fi. The registration devices and communication hub are implemented using NRF and ESP chips, respectively. However, this choice of chips may vary based on the functionality and facilities implemented in different chips. Figure 2

[0102] Schematic of the system detailing the registration-by-proximity method. This consists of at least one beacon that broadcasts Bluetooth signals. The data and signal characteristics are collected by the user's mobile phone. The mobile phone then stores and communicates the data with the backend service via Wi-Fi or other communication protocols.

[0103] Figure 3

[0104] The internal structure of the registration device contains multiple components, including at least one sensing unit, a processing unit (which includes a logic unit and memory), a user notification unit (e.g., an LED or a buzzer), a Bluetooth communication unit, and a power unit (which includes a power regulator and battery). The sensing unit can be any form of registration, such as RFID, NFC, or biometrics.

[0105] Figure 4

[0106] The internal structure of the communication hub includes multiple components: Bluetooth and WiFi communication units, a processing unit (which includes logic and memory), and a power regulator. This device is powered externally via USB or other power sources.

[0107] Figure 5

[0108] The internal structure of the combined device, which consists of both the registration device and communication hub, eliminates the need for Bluetooth communication as both units are implemented in one enclosure. Power is supplied by external sources such as USB or mains electricity. Everything is implemented using the ESP chip series, although this can change and can be any Wi-Fi-enabled chip. This device requires at least one sensing unit (e.g., for both RFID and NFC) and can be used for various by-interaction registration methods.

[0109] Figure 6

[0110] The internal structure of the beacon includes a processing unit (which contains a logic unit and a memory unit), a Bluetooth communication unit, and a power unit (which includes a battery and a power regulator).

[0111] Figure 7

[0112] Diagram of the system, including the backend service and the user interface. The communication hub communicates with the backend service via Wi-Fi. A sample architecture of the backend service is shown on AWS Cloud. The implementation includes the MQTT protocol, HTTP protocol, device gateway, over-the-air updates, FreeRTOS device, data store, and Lambda functions. The backend service also provides an interface for user interaction through a web browser or a mobile app.

[0113] Figure 8

[0114] Diagram showing the amplitude of the electrical current over time. The numbers indicate the current amplitude for different states:

[0115] 1 . Zero level, when the device is off.

[0116] 2. Sleep / stand-by state.

[0117] 3. Check for any interactions, such as a card or a mobile phone.

[0118] 4. Read the card, phone, or any other registration methods used.

[0119] 5. Communication with the communication hub via Bluetooth.

[0120] 6. Communication with the backend service via Wi-Fi.

[0121] 7.

[0122] Figure 9

[0123] The initialisation procedure for the communication hub involves running and initialising multiple subsystems and defining various settings in the system. It consists of the initialisation of the logging system, Ul system, NVS, device configuration, Wi-Fi subsystem, HTTPD server, BLE subsystem, SNTP subsystem, database subsystem, and attendance registration subsystem.

[0124] Figure 10

[0125] The procedure for adding logs to the communication hub starts by checking whether the log buffer is full. If not, it stores the log and sends it to the backend service using an API call. Otherwise, it deletes the oldest log and adjusts the circular buffer's head and tail.

[0126] Figure 11

[0127] Initialisation of the NVS subsystem in the communication hub starts with checking the integrity of the configuration partition. If it is OK, it checks whether a device reset is requested. If so, it resets the device configuration partition before loading the device configuration.

[0128] Figure 12

[0129] Initialisation of the Wi-Fi subsystem in the communication hub involves setting soft AP mode parameters, setting STA mode parameters, and starting the Wi-Fi service. Subsequently, it connects to the configured AP and checks for a connection to the backend service. If not connected, it will attempt again.

[0130] Figure 13

[0131] Initialisation of the HTTPD server on the communication hub configures the server to connect to the device via a web browser. It starts the HTTP service, registers URI handlers, prepares web server files, registers web server request handlers, registers FOTA request handlers, and finally registers local API web socket request handlers.

[0132] Figure 14

[0133] This figure depicts the local API web socket request handler in the communication hub. It contains multiple conditions to identify the validity, type, and credentials of the request and whether the session has already been authenticated. Depending on these factors, it returns various responses, such as 400 or 401 errors, or creates a new session and returns a 200 code. Alternatively, it calls the API command handler.

[0134] Figure 15

[0135] This figure shows the local API web socket request handler in the communication hub, which checks the content of the request to identify the action. There are multiple possible commands: ota_update, read_all, reboot, reset, write_ap, write_credential, write_mdsn, write_reader, write_sntp, and write_sta. Depending on these commands, it performs specific actions or returns a 404 error.

[0136] Figure 16

[0137] The task of connecting to Bluetooth or BLE in the communication hub begins with checking for any disconnected nodes. If any are found, it starts the scanning process. If not, it stops scanning and rechecks.

[0138] Figure 17

[0139] The BLE GATTC events handler in the communication hub has two GATT event handlers: (1) GATTC, which is central, and (2) GATTS, which is peripheral. This handler consists of multiple conditions to determine the event type and perform an action accordingly. If no event is recognised, it logs an unhandled event.

[0140] Figure 18

[0141] Database synchronisation task in the communication hub. It begins with three conditions to indicate the connection to the Wi-Fi network, whether the date-time is synchronised, and whether the local database needs updating. Subsequently, it will request a database link from the remote API, download remote databases of RFID UIDs and NFC UUlDs, and schedule the next database update. Figure 19

[0142] The attendance registration task in the communication hub. First, it initialises attendance subsystem queues. Then it checks different conditions to determine whether it is a by-phone registration. Depending on the local database, it will return success or failure to the registration device, add attendance to the send queue, and check whether the queue limit has been exceeded.

[0143] Figure 20

[0144] Emergency shutdown procedure in the communication hub. The communication hub is externally powered. There is a chance that the power might be cut off. As some data is stored in memory, the data will be stored on the flash memory of the system, which is an NVS. It begins by indicating whether a power loss is detected. If so, it will record a log, store the data on NVS, attempt to sync the system's latest state with the remote server, and finally disable system units and wait for final discharge.

[0145] Figure 21

[0146] Firmware over-the-air (FOTA) update in the communication hub. This procedure is to update the firmware of the chip remotely. It begins by checking whether there is any scheduled update and whether it originates from the local panel. If it is from the local panel, specific actions will be performed. If not, other actions are taken. Finally, it checks if it is a security patch; if not, it schedules a restart for off-peak hours, which are usually at night.

[0147] Figure 22

[0148] The initialisation procedure for the registration device involves running and initialising multiple subsystems and defining various settings. It involves the initialisation of the Ul subsystem, ADC subsystem, RFID subsystem, BLE subsystem, NFC subsystem, and events subsystem. The system then enters sleep mode to preserve power.

[0149] Figure 23

[0150] Initialisation of the BLE subsystem in the registration device. It enables the BLE subsystem, registers services and event callbacks, creates and sets up the ADV instance, and starts advertising.

[0151] Figure 24

[0152] Initialisation of the NFC subsystem in the registration device. It enables the NFC subsystem, registers event callbacks, prepares and encodes a default NFC message, enables NFC read and write modes, and finally starts NFC emulation. Figure 25

[0153] Initialisation of the events subsystem in the registration device. It initialises the system timeout timer, Ul timer, NFC reset timer, RFID timer, and RFID set timer, and starts the RFID timer.

[0154] Figure 26

[0155] The event handling procedure in the registration device contains multiple conditions to identify the event type. Depending on the event, specific actions will be taken.

[0156] Figure 27

[0157] The RFID work in the registration device involves multiple conditions to check the state of the device, whether any RFID cards have been detected, and whether the cards are valid or have been recently registered. Depending on these conditions, different states will be set and different procedures called.

[0158] Figure 28

[0159] The BLE work in the registration device includes multiple conditions to check different states and whether communication via BLE was successful. Actions and procedures will be determined based on these conditions.

[0160] Figure 29

[0161] The BLE callback handler in the registration device examines different states and the success of return data. Depending on these factors, different states are set and tasks are performed.

[0162] Figure 30

[0163] The request_idle_state_on state in the registration device involves multiple tasks, such as stopping the system timeout timer, restarting the RFID timer, and setting the state to IDLE. Figure 31

[0164] The request_idle_state_off state in the registration device restarts the system timeout timer.

[0165] Figure 32

[0166] The NFC callback handler in the registration device includes multiple conditions to assess the state, the validity of the NFC data, and whether the NFC UUID was recently registered. Actions and states are determined accordingly.

[0167] Figure 33

[0168] The BLE callback handler in the registration device considers various states and the success of data transmission. Actions and procedures are determined based on these conditions.

[0169] Figure 34

[0170] The BLE subsystem event handler for the registration device first identifies the event type. It will then perform different tasks based on the event type and the attribute involved. If the attribute pertains to the battery level, it will read the battery level using ADC and update its value, or return the attribute value if not.

[0171] Figure 35

[0172] The initialisation procedure for the BLE Beacon involves running and initialising multiple subsystems. It includes the initialisation of the FOTA trigger subsystem, ADC subsystem, BLE subsystem, and events subsystem. The device will enter sleep mode following the initialisation. Figure 36

[0173] The BLE initialisation subsystem for the BLE beacon involves enabling the BLE subsystem, creating the advertising (ADV) instance, setting up the data, and finally starting the advertising. Figure 37

[0174] The events initialisation subsystem for the BLE beacon is designed to broadcast the voltage of the battery as data. This voltage is measured at set intervals. The device initialises the advertisement data update and battery monitor timers, then starts the advertisement and battery timers.

[0175] Figure 38

[0176] The battery monitor procedure for the BLE beacon uses an ADC to measure the battery value. This procedure encompasses measuring the battery, updating the system state, and finally restarting the battery timer.

[0177] Figure 39

[0178] The advertisement (ADV) update procedure for the BLE beacon reads the battery level from the system's states. The security token within the ADV is updated based on the date and time, which will subsequently replace all ADV data.

[0179] Glossary

[0180] Term Meaning

[0181] ADC analogue to digital converter

[0182] ADV advertisement

[0183] AMS attendance monitoring system

[0184] AP access point

[0185] API application programming interface

[0186] BLE Bluetooth low energy

[0187] DNS domain network system

[0188] ESP a chip series

[0189] FOTA firmware over-the-air

[0190] GATT generic attribute profile GATTC generic attribute profile - client

[0191] GATTS generic attribute profile - server

[0192] GPS global positioning system

[0193] GSM global system for mobile communications

[0194] HTTPD hypertext transfer protocol daemon loT internet of things

[0195] MAC medium access control mDNS multicast DNS

[0196] MQTT message queuing telemetry transport

[0197] MTU maximum transmission unit

[0198] NFC near field communication

[0199] NRF a chip series

[0200] NVS non-volatile storage

[0201] Preact a programming toolbox

[0202] QR-code quick-response code

[0203] RFID radio frequency identification

[0204] RSSI received signal strength indicator

[0205] RTOS real-time operating system

[0206] SNTP simple network time protocol

[0207] SPA single page application

[0208] SSID service set identifier

[0209] STA station

[0210] Ul user-interface

[0211] UID unique identifier

[0212] URI uniform resource identifier

[0213] UUID universal unique identifier

Claims

Claims1 . An attendance monitoring system comprising: at least one registration device comprising at least one sensor to sense respective input attendee data identifying respective attendees; and a communications device configured to transmit to a remote storage and processing facility, wherein said communications device or said at least one registration device comprises a processor and memory, said processor configured to compare said respective input attendee data with attendee data stored in said memory to determine a verification status record for the respective attendee.

2. The attendance monitoring system claimed in claim 1 , wherein said processor is configured to cause said communications device to transmit attendee enquiry data to said remote storage and processing facility when said comparison fails to match the respective input attendee data with attendee data stored in said memory and receive a verification status record for the respective attendee from said storage processing device based on said attendee enquiry data.

3. The attendance monitoring system claimed in claim 2, wherein during a predetermined attendee registration time period, said processor is configured to limit transmissions by said communications device to said remote storage and processing facility to attendee enquiry data.

4. The attendance monitoring system claimed in claim 1 , 2 or 3, wherein said processor is configured to provide a verification signal based on said verification status record and said at least one registration device comprises a notification unit to notify the respective attendee of their verification status based on said verification signal.

5. The attendance monitoring system claimed in claim 3, wherein said notification unit comprises a visual display component to visually notify said verification status.

6. The attendance monitoring system claimed in any one of the preceding claims, wherein said processor is configured to cause said communications device to transmit verification status records as data sets comprising respective verification records for a plurality of attendees.

7. The attendance monitoring system claimed in any one of the preceding claims, wherein said at least one sensor comprises: i) an RFID reader; ii) an NFC reader; or iii) a biometric sensor.

8. The attendance monitoring system claimed in any one of the preceding claims, wherein said at least one registration device is connected to said communications device by a wireless technology.

9. The attendance monitoring system claimed in any one of claims, comprising a combined registration and communications device comprising a housing arrangement that houses a said registration device and said communications device and wherein said registration device is connected with said communications device by wiring.

10. The attendance monitoring system claimed in any one of the proceeding claims, wherein said communications device is configured to communicate with said remote storage and processing facility via a WIFI communications protocol or a USB or ethernet connection.

11. The attendance monitoring system claimed in any one of the preceding claims, wherein said at least one registration device and said communications device are battery powered.

12. A method of monitoring attendance at a venue, said method comprising: providing at said venue at least one registration device provided with a sensor to sense respective input attendee data identifying respective attendees; providing said at venue a communications device configured to transmit to a remote storage and processing facility that is disposed at a location remote from said venue; electronically processing said respective input attendee data at said at least one registration device or said communications device to verify the respective attendee by matching the respective attendee input data with attendee data stored in a memory provided at said at least one registration device or said communication device to determine a verification status record for the respective attendee.

13. The method of monitoring attendance at a venue claimed in claim 12, further comprising transmitting to said remote storage and processing facility by said communications device data sets comprising a plurality of said verification status records at predetermined spaced apart intervals.

14. The method of monitoring attendance at a venue claimed in claim 13, wherein said predetermined intervals are: i) intervals of time; or ii) intervals based on accumulating a predetermined number of verification status records.

15. The method of monitoring attendance at a venue claimed in claim 12, 13 or 14, wherein a said respective attendee input data does not match attendee data stored in said memory, further comprising transmitting enquiry data based on the not matching respective attendee input data to said remote storage and processing facility by said communication device for matching with attendee data stored at said remote processing and storage facility and receiving at said communications device a verification status record based on matching said enquiry data with attendee data stored at said remote storage and processing facility.

16. The method of monitoring attendance at a venue claimed in any one of claims 12 to 15, wherein said remote processing and storage facility comprises: i) a laptop or desktop computer; ii) a server; or iii) a cloud storage processing and storage facility.

17. The method of monitoring attendance at a venue claimed in any one of claims 12 to 16, wherein said venue is a class room or lecture room.

18. An attendance monitoring system comprising: at least one registration device comprising at least one sensor to sense respective input attendee data identifying respective attendees and a wireless communications unit; and a communications device local to said at least one registration device and configured to transmit to a remote storage and processing facility, wherein said wireless communications unit is configured to transmit attendee related data to said communications device and said communications device is configured to communicatethe attendee related data received from said at least one registration device to said remote storage and processing facility as batched data comprising attendee related data relating to a plurality of attendees.

19. The attendance monitoring system claimed in claim 18, wherein said at least one registration device comprises a processor and memory and said processor is configured to compare said respective input attendee data with attendee data stored in said memory to determine an attendee verification status, said attendee related data communicated to said communications unit is said attendee verification status and said batched data comprises attendee verification status data for a plurality of attendees.

20. The attendance monitoring system claimed in claim 18, wherein said communications device comprises a processor and memory and said processor is configured to compare said respective input attendee data with attendee data stored in said memory to determine an attendee verification status and said batched data comprises attendee verification status data for a plurality of attendees.

21. The attendance monitoring system claimed in claim 18, 19 or 20, comprising a combined registration and communications device comprising a housing arrangement that houses a said registration device and said communications device and wherein said registration device is connected with said communications device by wiring.

22. The attendance monitoring system claimed in any one of claims 18 to 21 , wherein said communications device is configured to communicate with said remote storage and processing facility via a WIFI communications protocol or a USB or ethernet connection.

23. The attendance monitoring system claimed in any one of claims 18 to 22, wherein said at least one registration device and said communications device are battery powered.

24. The attendance monitoring system claimed in any one of claims 18 to 23, wherein said at least one sensor comprises: i) an RFID reader; ii) an NFC reader; or iii) a biometric sensor.

Images