GB2598139A

GB2598139A - A system and method for establishing the presence of a user at a tag device

Info

Publication number: GB2598139A
Application number: GB2013020.9A
Authority: GB
Inventors: Brigham Peter
Original assignee: Dacfon Ltd
Current assignee: Dacfon Ltd
Priority date: 2020-08-20
Filing date: 2020-08-20
Publication date: 2022-02-23
Also published as: GB202013020D0

Abstract

System for establishing the presence of a user at a stationary location tag, comprising: a tag 12 providing time dependent output; and a server 36 that receives tag data from a user, extracts the time data and stores said time data. The system may comprise multiple tags with unique IDs, the tags’ output including the tag ID. The tag device may include: a real time clock 20 where the tag output changes periodically relative thereto; and an encryption module 24 configured to encrypt clock and tag ID as a displayed image, such as a QR code 50. The tag output may comprise a URL providing an address of the server. A user reader device 32 may optically scan the tag output and communicate the tag data to the server along with a user ID, via the URL. The server may store a sequence of check-ins indicative of a, or multiple, users being present at multiple tags at various times (Figs. 5-7) in order to track the movements of the users or operate a queuing system.

Description

Title: A system and method for establishing the presence of a user at a tag device

Description of Invention

This invention relates to a system and method for establishing the presence of a user at a tag device.

In particular, the system of the invention provides a mechanism for determining the presence of a user at a remote location, in a particular time period. For example, security guards may be required to monitor a secure site, by visiting locations within the site at prescribed time intervals. A security guard on a night shift may be required to patrol a perimeter of a site, once per hour. The present system provides a way to allow a user to 'check in' by reporting their attendance at particular locations.

Another example of known 'check-in' systems is for use at a counter in a shop, where a ticketing system may be used to establish an order of customers' arrival. Similar systems are provided in medical facilities, to establish that users can be seen in order, by allocating patients to a queueing system on their arrival, and calling them in turn to see a physician.

The present invention seeks to reduce or overcome one or more of the deficiencies associated with the prior art.

According to a first aspect of the invention we provide a system for establishing the presence of a user at a tag device, including: a tag device providing a tag output containing time-dependent tag data, and a server storing data associated with the tag device, the server being configured to: receive a communication from a user comprising the tag data and a user ID, determine from the tag data a time interval during which the tag data was output from the tag device, and store a record of the user ID and determined time interval.

According to a second aspect of the invention we provide a method of 10 establishing the presence of a user at a tag device, using a system of the type including: a tag device that provides a tag output containing time-dependent tag data; and a server storing data associated with the tag device, the method including the steps of: receiving at the server a communication from a user comprising the tag data and a user ID, determining from the tag data, at the server, a time interval during which the tag data was output from the tag device, and storing at the server a record of the user ID and determined time interval.

Further features of the above aspects of the invention are described in the appended claims.

Embodiments of the invention will now be described, by way of example only, with reference to the following figures, of which: Figure 1 is a diagrammatic representation of a system according to embodiments of the invention; Figures 2 and 3 are illustrations of a tag device according to embodiments of the invention; Figures 4A and 4B are examples of a user interface provided to a user via a reader device of embodiments of the invention, Figure 4C is an example of a user interface provided via a server of embodiments of the invention, and Figures 5 to 7, 8A and 8B are illustrative examples of the records stored at the server according to embodiments of the invention, and accompanying illustrations representing the data.

With reference to Figure 1, a system 10 is provided, comprising a tag device 12 and a server 36. The tag device 12 provides a tag output 30 containing time-dependent tag data. A server 36 stores data associated with the tag device 12, for establishing a record of the presence of a user at the location of the tag device 12.

In broad terms, the server 36 is configured to receive a communication 34 that originates from a user. The communication 34 contains tag data that has been obtained by the user from the tag device 12. Since the tag output 30 of the tag device 12 changes over time, in a manner known to the server, the server 36 is operable to determine when the tag data was read from the tag device 12.

This determination is not dependent on the time of receipt of the communication 34 at the server 36, since the time information is contained within the tag data. In this way, the server 36 determines a time interval during which the tag data was output from the tag device 12, and stores a record of the determined time interval.

By time-dependent, we mean that the tag output 30 changes over time. The change to the tag output 30 is preferably periodic, and in embodiments the tag output 30 changes according to a predetermined time interval, for example, based on a value of a real-time clock 24 included within the tag device 12.

The time interval can be predefined and hard-coded, or may be adjustable according to the intended use of the system. For example, if time precision is not required, it may be sufficient to establish the data upon which the tag data was output from the tag device 12, in which case an appropriate time period may be 24 hours. At the other end of the scale, the tag output 30 may change every second, and so the time interval may be 1 second. It is envisaged that in most settings, a suitable time period is between 60 seconds and 1 hour, and may be for example 5 minutes, 10 minutes, or 30 minutes. Therefore, in some embodiments the time period may be considered to be effectively a real time reading -recording the actual time of the reading.

In embodiments, the system 10 may include multiple tag devices 12 each having a different associated tag ID 18. In this way, the server 36 may receive communications each relating to different tag devices 12, to determining the presence of a user, or multiple users, at the tag devices 12 positioned in multiple locations. Each tag device 12 has an associated tag ID 18, and the tag ID 18 is included in the tag data that is transmitted to the server 36 so that the server 36 can determine and store a record that includes information about which tag device 12 was read to generate the tag data.

The tag device 12 typically includes a microcontroller 16, configured to read the real-time clock 24, and the tag ID 18, and a battery 22 to power the unit. In embodiments, the tag device 12 may provide a power connector for connecting the device to mains power, for example, rather than requiring a battery 22. In other embodiments, the tag device 12 may include a solar-powered cell.

The microcontroller 16 is configured to provide the tag date, including the tag ID data and data from the clock to an encryption module 24 configured to encrypt this tag data as a tag output 30. In embodiments, the encryption module 24 is configured to encrypt the tag data as an image. In embodiments, the encryption module 24 encrypts the tag data as a barcode or a OR code. This encrypted tag output 30 preferably also includes a URL or other server contact information (i.e. in addition to the tag data), providing an address of the server.

The system 10 periodically changes the tag output 30 by generating a new tag output 30 using data from the clock 20. The updated tag output 30 reflects the current time interval so that at any point in time the tag output 30 effectively provides a rtimestamp' of the time it is read. In this way, a user may read the tag output from the tag device 12, which contains tag data identifying the time interval during which the tag device 12 was read. As this updates, periodically, a later reading will provide a different tag output 30, to reflect a later time period.

In embodiments, the tag data may be encrypted using a password, or one of a list of passwords, or using a hash function. The server may include an encryption key or set of encryption keys for decoding the tag data so as to establish a time interval from the tag data, when a communication 34 is received. In embodiments the server 36 may store a hash table, for reconstructing data that has been hashed prior to transmission.

As illustrated in Figures 2 and 3, in embodiments the tag device 12 is formed with a casing 42 to surround and protect its microcontroller 16 and associated electronics in a central recess 46. The casing 42 may be formed of a hard plastic material, or a suitable metal, for example. A ridge 44 is formed around the edge of the casing 42 to support a screen 26, 50, suitable for displaying the tag output 30. Securing mechanisms 48 are provided to enable the tag device 12 to be fixed in place by securement to a surface or object at a desired location. In the example shown, the securing mechanisms 48 are apertures for receiving screws or the like. In other embodiments, a flat surface for receiving a strong adhesive may be provided on the casing 42, or other alternative securing mechanisms may be used as will be apparent to the person skilled in the art.

In embodiments, in addition to the screen 26, 50, or instead of the screen 50, a transponder 28, 51 (or simply a transmitter) may be housed within the tag device 12. The transponder 28, 51 is operable to transmit a signal when prompted to a nearby device to read the tag output 30 via a non-visual transmission in this manner. For example, the transponder 28, 51 may be an RFID (Radio-frequency identification) or NEC (Near-Field Communication) transponder, operable to transmit and RFID or NEC signal.

The tag device 12 output 30 may read by a user visiting the tag device 12 location. A user carries a reader device 32 which is configured to read the tag output 30 from the tag device 12. Where the tag device 12 provides a screen 26, 50, the reader device 32 may use a camera, for example, to photograph the image displayed on the screen 26, 60. For example, where a barcode or QR code is displayed, the reader device 32 may scan the code using the device's camera. Where the tag device 12 provides a transponder 28, 51, the reader device 32 may use an appropriate communication protocol to trigger the tag output 30 from the tag device 12 using the relevant protocol (i.e. NFC or RFID, or the like). Where the tag device 12 includes a transmitter, the reader device 32 may simply receive the tag output 30.

It is envisaged that the reader device 32 may be a smart phone, including a camera and/or suitable communication protocols to receive data from the transponder 28, 51.

The reader device 32 is also operable to communicate the tag data to the server 36. In embodiments, this communication 34 from the user further includes a user ID. In this setting, when the server 36 stores the record of the determined time interval, the record includes the associated user ID. The user ID may be associated with the reader device 32. For example, where the reader device 32 is the user's smart phone, the communication 34 to the server 36 may include an IP address or MAC address identifying the smart phone, or a telephone number from which the data is communicated to the server 36 (i.e. via a suitable receiver connected to the server). Alternatively, or in addition, the user ID may be associated with the user rather than the device.

The user may have a user account that is linked to the reader device 32. For example, the reader device 32 may run an application specifically configured to read or otherwise receive tag output 30 from a tag device 12, and communicate data to the server 36. The application may require a user information to be entered by the user, and the information -or at least an identifier associated with the user's account, is communicated to the server 36.

In embodiments, the tag output 30 comprises a URL (encrypted in a OR code for example). An application running on the reader device 32 may cause the reader device 32 to extract the URL from the tag output 30, and to communicate to the server 36 via the URL. In alternative embodiments, rather than a URL, the tag output 30 may contain a telephone contact number on which to contact a receiver connected to the server 36 so as to communicate data to the server 36, or an IP address at which the server may be contacted, for example.

The server 36 provides a processor and storage media, and is configured to receive the communications 34 from the user(s), via the reader device(s) 32 -preferably via an internet connection as described. The server 36 is configured to decrypt the received data to establish the time interval at which the tag data was output. The server 36 may extract a user ID and/or a tag ID from the data received, and stored the data as a record. The server 36 further provides an application program interface 40 with which a program may interact with the stored records, to operate a connected application. The application program interface 40 may be configured to be run on a terminal coupled with the server, for example. In addition, the reader device 32 may be configured to run a corresponding user interface 52 which is communicatively coupled with the server 36, for receiving input from a user including a user ID which may include contact details, the name of the user and/or other user-related information. Figures 4A and 4B illustrate an example user interface for a reader device 32, and Figure 4C illustrates an example application program interface 40 running on a server 36, or on a terminal coupled to the server 36.

For example, the application program interface 40 may provide a time tracking system for determining the presence of a user at a specific location at which the tag device 12 is located. We explain this with reference to Figure 5.

In essence, the system 10 in this setting includes a tag device 12 marked at location A, within an area being monitored, for example. The tag output 30 contains time-dependent tag data, which changes periodically as described. A server (not shown) stores data associated with the tag device 12, and is set ou

in the table.

As a user visits the tag location A, the user reads the tag output 30 using a reader device 32. The reader device 32 establishes the address to communicate to the server 36 from the tag output (i.e. via a OR code for example), and subsequently communicates the tag data to the server 36. The server receives the communication from the user, which includes the (encrypted) tag data. The server 36 determines a time interval during which the tag data was output from the tag device 12, and subsequently stores a record of the determined time interval.

The table in Figure 5 illustrates a security guard's activity, in which the guard visits site A five times, each time scanning the tag output 30, and communicating to the server 36. The server stores 5 records of the time intervals reflected in the tag data received. In this way, the system 10 stores a record of the time intervals during which the guard was present at the tag devices 12. It is not possible to trick the system into recording a visit to the tag device 12 at that later time of communication to create the appearance that the visit happened at that later time. The server 36 determines from the tag data the time interval during which the tag output was read, and so whenever the tag data is communicated to the server 36, that time interval does not change.

Using this system 10, a security guard carrying a reader device 32 can 'check in' at various locations on a site being monitored by scanning a tag device 12 associated with that location, and the timing of the guard's presence at the tag device 12 in each location is recorded. For example, the guard may be required to visit each location between the hours of 11pm and 2am. Therefore, with an appropriate time interval set (e.g. 5 minutes, 10 minutes, 30 minutes, or an hour), the system 10 can be used to ensure that the guard visits the locations on site at appropriate times falling within the required time window.

With reference to Figure 6, the system 10 may establish the presence of a user at multiple locations, this time labelled A to E, at which multiple tag devices 12 are located, respectively, at specific time intervals. The table this time reflects the movements of the security guard between sits A to E. The records in the table are not in time order, as they may not be received in the order at which the tag devices 12 were visited. Instead, the time interval data is determined from the tag data when it is received by the server 36, and stored along with the tag ID representing the tag device 12 from which the tag output 30 was received.

In broad terms, the system 10 includes multiple tag devices 12, each tag device 12 having a unique associated tag ID 18 (A to E) and the tag data generated by the tag device 12 includes the tag ID 18. The method includes receiving at the server 36 multiple communications from the user, and each communication includes tag data from which, at the server, the tag ID is determined. The tag ID identifies a respective tag device 12 (i.e. the devices located at locations A to E) from which the tag data was read. The server 36 determines the time intervals representing the times during which the tag data was output from the tag device, and records the tag ID alongside the associated time interval With reference to Figure 7, embodiments of the system 10 are used to establish the presence of multiple users at multiple locations, at particular time intervals. In this example two users each visit a selection of sites A to E. Guard A is the user ID associated with visits to sites A, B and D, at the time intervals indicated. Records 4 and 5 relate to user ID Guard B, who visited sites E and C. Considering the case where the records are stored in order of ascending record number, the order of the records indicates that Guard A communicated the readings of the tag devices with tag IDs A, B and D prior to the Guard B communicating the readings of the tag devices with tag IDs C and E. Even so, it can be seen from the records that the reading of tag ID E occurred at the earliest time interval.

In embodiments such as this, the method of using the system 10 involves receiving at the server a communication from each user which includes a user ID, and storing a record of the determined time interval and also the user ID.

In embodiments, the system 10 may be used to establish a time sequence of multiple users being present at a tag device 12. The method of using the system 10 in this way includes the steps of receiving multiple communications from users, at the server 36, each communication including tag data and a user ID associated with the user sending the communication. The server 36 determines from each communication a time interval from its respective tag data, representing the time interval during which the tag data was output from the tag device. A record is then stored, associating the time interval with the user ID, for each communication received.

With reference to Figures 8A and 8B, an example of this type is illustrated in the form of two tables of records stored by a server. In this setting, the user ID received in each communication includes contact information for contacting that user, in the form of a telephone contact number in this case.

The system 10 is effectively being used as a queueing system, to establish the order of users scanning the tag device, which corresponds to their time of arrival at premises (such as a café, for example). The method of operating the system 10 includes identifying the "next" user in the queue, based on the stored records. Each user arrives in turn and reads the tag output of the tag device 12 (using their smartphone to read a OR code, for example). The users' smartphones connect automatically to the server via a URL stored in the QR code, and communicate the tag data to the server 36, and a respective user ID. The user ID in this example is a contact telephone number, but may also or alternatively include a registration number associated with the user, or a name.

At a terminal in the café, a staff member may run an associated application program interface 40 which displays a sequence of the records stored by the server, as shown in Figure 4C. The "next" record in the queue is identified, that being the one having the earliest associated time interval. In Figure 8A it can be seen that record #1 has the earliest associated time interval, of 10:31 (where in this example the interval period is set to one minute). The system 10 associates an identifier code with the record, and communicates the identifier code to the user associated with the next record. This may be communicated via an application interface on the user's reader device, for example. Alternatively, the system 10 may communicate the information via a text SMS message, or via any other suitable form of communication. On receipt of the information by the user, the user is able to approach the counter and provide a code to the staff member, to establish that they are indeed the next customer in the queue to be served. At that point the staff member can check that the code provided by the used matches the identifier code allocated by the system 10. Where the code is found to match, the system 10 or staff member, may mark that record as 'complete' and/or simply delete the record from the stored records. The process may be repeated, to establish the 'next' customer in sequence.

In some embodiments, the system 10 may store the records in an order determined by the time intervals associated with each record, so that the list is maintained in time-sequential order. In that way, a user may be provided with information from the server, via the program interface on their respective reader device for example, relating to their relative position in the queue (i.e. you are the fifth user in the queue).

Figure 4C illustrates an example application program interface 40, 62 for a queuing system, wherein a list of records 64 are displayed, each with an associated user ID contact telephone number. The records 64 are listed in order, sorted by the time intervals associated with each record, as previously discussed. The record identified as being the 'next' record is associated with an identifier code 56, which is communicated to the associated user via the contact details in the user ID, so as to update the displayed information on the reader device 32 of the user via a corresponding application interface (see Figures 4A and 4B). Figure 4A illustrates an example user interface 52 for a reader device 32 such as a smartphone. The user interface 52 provides an indication of the number of users ahead of the respective user in the queue, determined by the records stored on the server 36. When the user becomes the 'next' user, the user interface 52 receives the identifier code 56 from the server, associated with that respective record. The user may then present the code to a staff member at the premises operating the system 10, for example.

In some embodiments, the identifier code presented by a user may be presented to a scanner on a device for example, to read the code automatically, so as to allow the user to operate the device. In this way, a device may operate an associated queuing system to allow users access to the device. For example the identifier code may take the form of a barcode of other machine-readable code, and may be presented on a screen of the reader device 32, to be read by the scanner.

In some embodiments, and as illustrated in Figure 4A, the user interface 52 may provide options for the user to interact with and/or modify the stored records on the server 36, or with the queued records presented on the program application interface 40. The user may be presented with an option 58 to defer their position in the queue (for example, if they are not ready to take their place). Selecting this option 58 to defer the position in the queue may cause the record associated with that user to be revised so that the time interval stored in the record is altered so as to cause the relative ordering of the records to be changed. Alternatively, the record may be moved a set number of positions in the queue, so that the queue no longer strictly represents the time intervals stored in the records, so as to defer the user's position in the queue. The deferment may cause the user's position in the queue to be deferred by one position, or by 2 or more positions, for example.

In some embodiments the user interface 52 may provide a cancellation option 60 to enable a user to remove their record from the queue. This may be desirable, for example, if the user no longer wishes to participate in the queue.

Choosing the cancellation option 60 may cause the user's associated record to be removed from storage at the server, or may result in the user's record being removed from the queue displayed on the program application interface 40.

When used in this specification and claims, the terms "comprises" and "comprising" and variations thereof mean that the specified features, steps or integers are included. The terms are not to be interpreted to exclude the presence of other features, steps or components.

The features disclosed in the foregoing description, or the following claims, or the accompanying drawings, expressed in their specific forms or in terms of a means for performing the disclosed function, or a method or process for attaining the disclosed result, as appropriate, may, separately, or in any combination of such features, be utilised for realising the invention in diverse forms thereof.

Although certain example embodiments of the invention have been described, the scope of the appended claims is not intended to be limited solely to these embodiments. The claims are to be construed literally, purposively, and/or to encompass equivalents.

Claims

CLAIMS1. A system for establishing the presence of a user at a tag device, including: a tag device providing a tag output containing time-dependent tag data, and a server storing data associated with the tag device, the server being configured to: receive a communication from a user including the tag data, determine from the tag data a time interval during which the tag data was output from the tag device, and store a record of the determined time interval.
2. A system according to claim 1, including multiple tag devices each having a different associated tag ID, and wherein the tag data includes the tag ID.
3. A system according to claim 1 or claim 2, wherein the tag device includes a real time clock.
4. A system according to any preceding claim, wherein the time-dependent tag data changes periodically.
5. A system according to any preceding claim wherein the tag device includes an encryption module configured to encrypt the data forming the tag output as an image, and the tag device includes a screen that displays the image.
6. A system according to claim 5, wherein the image includes a barcode or a QR code.
7. A system according to any preceding claim, wherein the tag output includes a URL providing an address of the server.
8. A system according to any preceding claim, further including a reader device operated by the user, configured to: read the tag output from the tag device, and communicate the tag data to the server.
9. A system according to any preceding claim wherein the communication from the user to the server further includes a user ID, and wherein the stored record of the determined time interval also includes the user ID.
10. A system according to claim 9, where dependent on claim 8, wherein the user ID is either associated with the reader device, or the user ID is associated with a user account that is linked to the reader device, and the reader device is configured to communicate the user ID to the server with the tag data.
11. A system according to any one of claims 8 to 10, where dependent directly or indirectly on claim 7, wherein the reader device is configured to extract the URL from the tag output, and to communicate to the server via the URL.
12. A system according to any one of claims 8 to 11, where dependent directly or indirectly on claim 6, wherein the reader device includes a camera, and wherein the reader device is configured to scan the barcode or QR code using the camera, and automatically extract the URL from the tag output, and connect to the server using the URL.
13. A method of establishing the presence of a user at a tag device, using a system of the type including: a tag device that provides a tag output containing time-dependent tag data; and a server storing data associated with the tag device, the method including the steps of: receiving at the server a communication from a user including the tag data, determining from the tag data, at the server, a time interval during which the tag data was output from the tag device, and storing at the server a record of the determined time interval.
14. A method according to claim 13, wherein the system includes multiple tag devices, each tag device having a unique associated tag ID and the tag data including the tag ID, and wherein the step of storing a record of the determined time interval further includes storing in that record the tag ID.
15. A method according to claim 14, for establishing a time sequence of a user being present at multiple tag devices, wherein the method includes receiving at the server multiple communications from a user, each communication including tag data from which, at the server: a tag ID is determined, identifying a respective tag device from which the tag data was read, and a time interval is determined representing the time interval during which the tag data was output from the tag device, and a record of the tag ID and associated time interval is stored.
16. A method according to any one of claims 13 to 15, wherein receiving at the server a communication from a user further includes receiving a user ID, and storing a record of the determined time interval further includes storing in that record the user ID.
17. A method according to claim 16, for establishing a time sequence of multiple users being present at a tag device, wherein the method includes, at the server: receiving multiple communications from users, each communication including tag data and a user ID associated with the user sending the communication, determining from each communication a time interval from its respective tag data, representing the time interval during which the tag data was output from the tag device, and storing a record of each time interval with its associated user ID.
18. A method according to claim 17, wherein the user ID received in each communication from a user includes contact information for contacting that user, and the method further including identifying the next user, including the steps of: determining at the server from the stored records the next record in the queue, that being the one having the earliest associated time interval, communicating an identifier code to the user associated with the next record, and identifying the user associated with the next record by determining a match between a code provided by the user and the identifier code sent to the user associated with the next record.
19. A method according to claim 18, further including: on identifying the user associated with the next record, removing that record from the stored records, and subsequently, repeating the steps for identifying the next user based on the remaining stored records.