GB2483368A - Venue entry system and method - Google Patents

Abstract

An apparatus and method for identifying a potential venue patron, the apparatus comprises a processor device 110 coupled to an acquisition device 120, a first database 130 and a display 112. The processor device 110 receives raw identification data from the acquisition device 120 and processes this raw data to identify data indicative of an identification element presented by the venue patron. The processor 110 retrieves one or more patron records from the first database 130 based upon the processed data and displays the patron records on the display 112. The acquisition device 120 may be a scanner or reader for driverâ s licenses, passports, photo identification cards, proof of age cards, magnetic stripe cards or smart cards. The patron records are indicative of a candidate patron selectable by an operator for identifying the venue patron. The operator may decide to allow or refuse entry based upon the patron record. One or more predetermined elements of the patron records from the first local database are synchronised with a second remote database. The patron records and identification data may be shared with other venues or the police or marketing companies. The venue may be a nightclub, bar, pub or casino.

Description

METHOD AND APPARATUS FOR IDENTIFYING A VENUE PATRON

FIELD OF THE INVENTION

The present invention relates to data acquisition and in particular to data acquisition for identifying a person.

The invention has been developed primarily for use as a method and apparatus for identifying a venue patron and will be described hereinafter with reference to this application. However, it will be appreciated that the invention is not limited to this

parUcular field of use.

BACKGROUND OF THE INVENTION

Any discussion of the prior ait throughout the specification should in no way be considered as an admission that such prior art is widely known or forms part of the

common general knowledge in the field.

Many forms of identification cards, including photo identification cards, are available.

These forms of identification are typically issued at various times and by different Is administration/organisation depaitments. This can result in a variation in the nature of data presented by each identification card, and variations in the data presented by each identification card resulting from the time issuance.

There is a need to identify and verify a holder of an identification card, irrespective of the identification card presented.

OBJECT OF THE INVENTION

It is an object of the present invention to overcome or ameliorate at least one of the disadvantages of the prior art, or to provide a useful alternative.

It is an object of the invention in its preferred form to provide a method and apparatus for identifying a venue patron.

SUMMARY OF THE INVENTION

According to an aspect of the invention there is provided an apparatus for identifying a venue patron, the apparatus comprising: an acquisition device adapted to receive an identification element, the acquisition device adapted being further adapted to acquire raw identification data indicative of the identification element; a processor device coupled to the acquisition device; a processor device being adapted to process the raw identification data to identification data indicative of the identification element; the processor further coupled to a database for retrieving one or more patron records for identifying a venue patron.

According to an aspect of the invention there is provided a processor apparatus for identifying a venue patron, the apparatus comprising: a processor device coupled to the acquisition device and a local database; a processor device being adapted receives raw identification data from the acquisition device; and processes this raw identification data to identification data indicative of an identification element; the processor further adapted to retrieve one or more patron records for identifying a venue patron.

Preferable, the processor device is coupled to a display element for displaying one or more patron record, each indicative of candidate patron selectable by an operator.

Preferably, the processor device is further adapted to retrieve any incident details related to the patron record for an identified presenting patron. More preferably, the incident data is presented on the display element, thereby enabling an operator to assess the patron. Most preferably, if despite a patron has been identified with one or more associated incidents recorded, the patron is granted entry to the venue, the processor maintains a watch count for indicating a number of times entry to a venue has been allowed to the patron without further incident.

Preferably, the database is a venue local database. More preferably, the local database is updated with data acquired from other venues. Most preferably, the database is synchronised with a remote database for updating data acquired from other venues.

Preferably, a remote database is synchronised with the local database, and can be accessed for providing a marketing campaign. More preferably, a patron membership registration can authorise access to a marketer. Most preferably, a membership registration can be associated with one or more venues.

According to an aspect of the invention there is provided a user access interface for a processor device, the processor device being adapted to identify venue patron, the processor device being coupleable to database having one or more patron records; the interface comprising: a control program adapted to: receive first identification data from an acquisition device; process the first identification data to second identification data indicative of an identification element; retrieve one or more patron records for identifying a venue patron.

According to an aspect of the invention there is provided a method of identifying a venue patron, the method comprising the steps of: (a) presenting an identification element to an acquisition device; (b) acquiring raw identification data indicative of the identification element; (c) processing raw identification data to present identification data indicative of the identification element; (d) interrogating a database to retrieve one or more patron records, being potential matches within the database, each patron record having verification data; and (e) displaying verification data to a display element for verifying the patron.

According to a further aspect of the invention there is provided a computer program product stored on a computer usable medium, the computer program product adapted to provide a method of identifying a venue patron as herein described.

According to a further aspect of the invention there is provided a computer readable medium for operation with a processor device, the computer readable medium comprising computer code for executing a method a method of identifying a venue patron as herein described.

According to a further aspect of the invention there is provided a computer program product stored on a computer usable medium, the computer program product adapted to provide a user access interface for a computer device, the computer device being adapted to receive data indicative of an identification element, the computer device s being coupleable to database having one or more records indicative of registered patrons; the computer program product comprising: computer readable program means for providing a method of identifying a venue patron as herein described.

According to an aspect of the invention there is provided an apparatus for collecting and maintaining a database of registered patrons, the apparatus comprising: an acquisition device adapted to receive an identification element, the acquisition device adapted being further adapted to acquire a first identification data indicative of the identification element; a processor device coupled to the acquisition device; a processor device being adapted to process the first identification data to a second identification data indicative of the identification element; the processor further coupled to a first database for retrieving one or more patron records for identifying a venue patron; wherein, if a presenting patron is verified against a first patron record, the second identification data is used to update the first patron record stored in the database; and wherein, if a presenting patron is not verified against the one or more retrieved patron records, the second identification data is used to create the first patron record stored in the first database.

Preferably, the first database is synchronised with a remote database. More preferably, the remote database is further synchronised with a plurality of venue local database. Most preferably, the remote database can be accessed for providing (or distributing) a marketing campaign.

BRIEF DESCRIPTION OF THE DRAWINGS

A preferred embodiment of the invention will now be described, by way of example only, with reference to the accompanying drawings in which: FIG. 1 is a schematic view of an apparatus for identifying a patron to a venue according to the invention; FIG. 2 is a schematic view of an apparatus for identifying a patron to a venue according to the invention, shown coupled to a data network; FIG. 3 is a schematic view of an apparatus for identifying a patron to a venue according to the invention, shown coupled to a data network; FIG. 4A is a schematic view of a display element according to the invention, shown displaying identification data indicative of a patron record; FIG. 4B is a schematic view of a display element according to the invention, shown displaying a watch list; FIG. 5A is a schematic view of an identification element, shown in the form of a drivers licence; FIG. 5B is a schematic view of an identification element, shown in the form of a passport; FIG. 5C is a schematic view of an identification element, shown in the form of a smart card; FIG. 6A is a flowchart to a method of identifying a patron to a venue; FIG. 6B is a flowchart to a method of identifying a patron to a venue; FIG. 7 is a flowchart to a method of identifying a patron to a venue, shown adding incident data; FIG. 8A is a schematic view of an embodiment synchronisation configuration; FIG. 8B is a schematic view of an embodiment synchronisation configuration; FIG. 8C is a schematic view of an embodiment synchronisation configuration; FIG. 9 is a schematic view of membership patron data maintained / synchronised with a remote database server; FIG. 10 is a schematic view of a member database synchronised with a remote database server, a campaign parameter and a campaign script; FIG. nA is a schematic view of an apparatus in which a marketing campaign can be retrieved by, or transmitted to, a patron access device; and, FIG. iiB is a schematic view of an apparatus in which a marketing campaign can be retrieved by, or transmitted to, a patron access device.

S

S..... * S

S

S..... * .

S

S. S*** * S

S

S. .s** * S * * * *** *.. * .

PREFERRED EMBODIMENT OF THE INVENTION

FIG. 1 shows an example apparatus 100 for identifying a patron to a venue 101. The apparatus comprising a processor (or equivalently computing) device 110 coupled to an acquisition device 120 and database 130. It would be appreciated that a patron can include any person presenting for entry to a venue, being a first or subsequent visit.

The acquisition device 120 is typically adapted to receive and identification element in the form of an identification card. The acquisition device 120 is therefore typically in the form of any one or more devices selected from the set comprising: an optical scanner, a magnetic stripe card reader, a smart card reader. However, it would be appreciated that the apparatus can include a finger print scanner, or iris scanner or electronic signature pad for providing additional identification or verification.

The database 130 comprises one or more patron records, each indicative of a registered patron to a venue. The database 130 is typically configured as a local database to a venue.

is The processor device 110 is fuither coupled to a display element 112 for displaying data indicative of an identified patron, and an input element for reviewing, amending or selecting data indicative of the patron.

It would be appreciated that the apparatus 100 can be used for identifying a patron at a plurality of venues. In particular, the apparatus can be suitable for venues employing a method of security wherein patrons are evaluated prior to entry. This form of security is typically employed at venues wherein proof of age may be required, such as hotels, bars and gambling venues.

An identification element 122 can be presented to the acquisition device for acquiring or retrieving raw identification data relevant to the identification element, and purportedly indicative of a patron presenting the identification element at the venue.

By way of example, an identification element can be in the form of any one of the set comprising: a photo identification card, a driver's licence, a proof of age card, a passport, a magnetic stripe card, and a smart card.

The acquisition device 120 can acquire or receive raw identification data from the identification element 122, and transmit the identification data to the processor device 110. The processor device further comprises a computer program product stored on a computer usable medium for processing the data retrieved or acquired by the acquisition device, determine identification data indicative of the identification element, interrogating the database 130, retrieving verification data indicative of a s patron record, displaying verification data to the display element 112 for verifying the patron.

Typically, the processor device typically segments the identification image data to retrieve a presented photograph, a name, age or date of birth, and address recorded on the identification element. The name and date of birth can then be used to interrogate the local database to retrieve one or more patron records. If a new identification element is presented, data extracted from the identification element can be added to the patron record and stored in the database.

The verification data can further include one or more incident data related to the patron record retrieved. The incident data related to a patron record may include: details of disruptive behaviour, alcohol problems, and gambling problems. By way of example, the incident data can be entered and related to a patron record by any one or more of: an authorised device operator, a venue manager, a certified security personnel, an authorised third party, and/or the patron. It would be appreciated that a patron may also elect to record incident data against their record to voluntarily restrict their access to particular venue or types of venues.

Identification data acquired from the identification element can be used to identify potential matches within the database. A computer program product can include a match module for generating a list of potential matched patron records. This module typically interrogates the database based on a search parameter comprising one or more data elements within the identification data. For example, search parameters acquired from the identification element can include any one or more of: the name; date of birth; and/or a unique serial/reference number. A list of potential patron records within the database, having the search parameters, can be generated. While there is typically only one patron record in the list, if more than one patron record in the list, data indicative of each candidate can be displayed on the display element for selection by an operator. It would be appreciated that, by including a photograph (or image data) of each registered patron in the database, the operator would be able to quickly verify if any of the candidate patron records correspond to the presenting patron.

In an embodiment, wherein a photo identification card is presented by a patron, the computer program product is adapted to retrieve acquired raw image identification data indicative of the identification element, classify the type of identification element, and segment and extract relevant identification data. The relevant identification data can include a segmented photograph data acquired from the identification element and personal details such as names, date of birth, address, serial numbers. Personal details can be obtained through optical character recognition of the raw image identification data.

The database may relate further identification information associated with each registered user. This data may have been acquired, or provided, during previous visits to a venue. By way of example only, data relating to a patron may include: name, date of birth, address, telephone numbers, email addresses, height, and various demographic information such as gender, race, age, and disabilities.

Acquired information data can also be used to update and/or further complete the patron record. One or more acquired photographs of a patron can be related to a single patron record and stored in the database, additional serial numbers indicative of each identification element can also be recorded, and missing data fields within the patron record such as an address can be populated.

The acquisition device is in data communication with the processor device. The computer program product processes raw identification data acquired by the data acquisition device. The apparatus may further include a security module for restricting access to authorised users only.

It would be appreciated that the acquisition device may be activated manually or automatically upon placement of an identification element. The presence of an identification element can automatically commence processing by the acquisition device and processor device.

The acquisition device can be adapted to read information data from one or more forms of identification elements, the identification data being embedded in a medium, for example a visual medium. It will be appreciated that other mediums can be used, including any one or more of: a magnetic medium, an electrical medium, an optical medium or a visual medium.

The acquisition device can include an optical scanner (or photograph scanner), which can receive a photographic identification element (for example a drivers licence). The optical scanner may also function as a barcode scanner (including a traditional barcode, a 2D barcode, or a 3D barcode). The computer program product can process the image data from the optical scanner acquisition device and decode and/or segment information data indicative of the respective identification element.

For example the software computer program product may include an optical character recognition (OCR) module for acquiring textural information from the identification element. The computer program software product can first identify the type of identification element, thereby segmenting known regions of the identification element.

A driver's licence may be presented to an optical scanner acquisition device. The acquisition device may automatically or manually commence scanning the identification element to provide raw image identification data. This image data is then processed by the computer program product to extract relevant identification data, including textual information and/or a photograph and/or a barcode. For example, textual information may be segmented to include the licensee's name, address, date of birth and licence number. An operator may be prompted to enter further relevant identification data indicative of the presenting patron. The operator may be prompted by queries presented on the display element, wherein the operator enters further data through a keyboard and/or touch screen and/or other means.

In an embodiment data communication between the acquisition device and processor device may include universal serial bus (USB), Bluetooth, and maybe wireless and/or a wired communication. In one embodiment the apparatus, and/or the acquisition device, may be portable and wireless. The acquisition device may include a display element, thereby enabling handheld operation. The apparatus may include a display element, a printer, a keyboard, a mouse, and/or other devices known in the art.

The apparatus may include a digital camera or video capture device, for enabling a photograph to be added to a patron data record, if a photo id is not presented when creating an initial record, or can be used to add a photograph if not initially stored with the patron record.

By way of example only, if a presenting patron has been identified (or verified) in the light of a patron record, the database can be interrogated to retrieve any incident details related to the patron record, revealing (or presenting) any known incidents associated with a particular patron, thereby enabling an operator to assess the patron.

In an embodiment, the associated incident details can be presented in an ordered list based on relevancy to a particular venue. For example, a venue serving alcohol may be interested in restricting access to patrons having alcohol related incidents or associated behavioural incidents recorded, whereas a gambling venue may place a higher priority on restricting access to patrons having a recorded gambling addiction incident. Retrieved incident data can be retrieved when retrieving the patron record data or as a separate step database retrieval, for example, after a patron has been identified (or verified).

In an embodiment, when a patron has been identified with one or more associated incidents recorded, a licence security person or manager may select to either refuse or allow entry to the patron. If, despite a relevant incident being recorded, the patron is granted entry, a watch count can be maintained (and stored in the database) indicating a number of times entry has been allowed to the patron without further incident. This watch count can also be displayed to assist a licence security person or manager in selecting to either refuse or allow entry to the patron.

By way of example, if a patron is allowed entry despite a relevant incident being recorded, the display element can display a list of all watched patrons currently allowed entry to the venue. A photograph of each of these patrons may also be available or displayed for easy reference, as best shown in FIG. 4B.

A method to expire features recorded against a patron can be implemented based on a time period or completion of a predetermined number of watched visits.

By way of example only, if a presenting patron has not been identified against any patron record, a new patron record can be created using the acquired identification data. Further data may be requested and added when creating a new patron record.

A membership form may also be provided for requesting further patron information and/or authority to use the information for marketing purposes.

The local database can maintain records of patrons to the venue. A patron may then become a member, wherein membership data is further added to the patron record.

A plurality of venues can be associated to provide a joint membership (for example providing a discount scheme across one or more venues) to affiliated membership. In this example database records for patrons must be shared as a combined membership is available to all affiliated venues.

In an embodiment, once a patron has been identified and verified, a registration card can be also printed. A paper based registration card can be printed and stored for maintaining a record of a patron staying at or visiting a venue. Additional data can be collected from the patron and stored on the registration card and/or local database.

This is particularly useful in venues such as hotels where a registration card is printed and retained for each hotel patron. The registration card can include a photograph of is the patron.

In an embodiment a venue report may be generated to identify patrons that have visited the venue over a selected time period. For example a law enforcement specific report may be generated to provide a list of patrons, the time they entered the venue and an associated photograph of the patron. The report may be provided in a paper form or electronically provided such as on a USB memory device.

FIG. 2 shows the apparatus 100 can be coupled to a remote server device 210 using a data network 220. The remote server device includes a remote database server module 212 for synchronising and/or backing up patron records.

An authorised third party server device 230 can also include a third party database module 232 for maintaining a database comprising one or more patron records. The third party server device can synchronise or update patron records maintained by the remote server device.

By way of example, the third party server device 230 can be associated with another registered venue, or an authorised law enforcement agency (for example police and marshals), or an authorised government organisation (for example missing persons), or an authorised public organisation (such as alcoholics anonymous or gambling anonymous or medical alert). Patron records can then be synchronised or uploaded to a venue local database when a subsequent venue synchronisation procedure is undertaken.

It will be appreciated that privacy and or security requirement may restrict specific data elements from being synchronised with some venues.

An embodiment remote server device 210 can include a web server module 214 for presenting a user interface for accessing authorised functions, such as targeted marketing campaigns to patrons indicated by selected patron records maintained by the database server module. A third party access device 240 can be coupled to the data network for communicating with the remote server device, for example via a user interface presented by the web server module.

FIG. 3 shows that a target device 310, 320 can be coupled to the data network for receiving a communication from either the processor device 110 of remote server device 210. By way of example, a target computing device 310 can be adapted to receive an email message 312 and a target telephonic device 320 can be adapted to receive a short message service (SMS) communication 322. It would be appreciated that other communications can be used, including: instant messaging, tweeting, social network messaging, email, short message service, facsimile, and generated voice call.

By way of example, a communication can be transmitted manually or automatically by a processing device in response to a patron being identified. A communication may be sent to a third party associated with (or identified by) the patron record. If a patron presenting to a venue serving alcohol and is identified as being a registered alcoholic, then a registered councillor (or sponsor) may be contacted. If a patron presenting to a gambling venue and is identified as having a registered gambling problem, then a registered councillor (or sponsor) may be contacted. If a patron presenting to a venue serving food and is identified as having a medical alert for an allergy, then a message may be sent to a venue booking system to record the patrons allergy against any restaurant booking. If a patron presenting to a venue is identified as having a police alert issued, then a message may be sent to a police emergency contact.

By way of example, a communication can be transmitted manually or automatically by a remote server device in response to a venue (or registered third party) requesting a marketing campaign to patrons belonging to a specified set -for example a venue, or a multi-venue membership.

FIG. 4A shows an embodiment display configuration that can be presented on the display element 112. This display configuration includes information retrieved from a patron record, including: > a patron name 41o; > one or more patron photographs 412; > apatrondateofbirth42o; > one or more incident entries 430; > other relevant data 440, including a patron address.

The incident entry related to a patron record may include: details of disruptive behaviour, alcohol problems, and gambling problems. Each of the one or more is incident entries 430 can include a description of the incident 432 and a watch count 434.

A user interface 450 can be presented to enable an operator to select possible course of action, including: > reporting the patron record is not indicative of the presenting patron; > confirming a presenting patron, and allowing entry; > confirming a presenting patron, but denying entry; FIG. 4B shows an embodiment watch display configuration that can be presented on the display element 112.

By way of example, if a patron is allowed entry despite a relevant incident being recorded, the display element can display a list of all watched patrons 6o, 6i currently allowed entry to the venue. Each watch patron display segment 6o, 6i can include, one or more photographs 412 of the patron, the patron name 410, and one or more incident entries 430.

In an embodiment, the associated incident entries can be presented in an ordered list based on relevancy to a particular venue.

It will be appreciated that this apparatus both identifies potential issues associated with a presented patron, and further presents the incident details. The display data can include one or more issues by displaying a list of incidents (or alarms) previously recorded against the patron. The displayed list can be graded or categorised based on relevance to a particular venue. A watch category identifying the number of counts a patron has been allowed entry to a venue in spite of a relevant concern/alarm record can be maintained against a patron and or each incident.

An acquisition device is adapted to acquire or receive identification data from the identification element, and transmit the identification data to the processor device.

The acquisition device can include any one or more of the following: an optical scanner, a magnetic strip card reader, a smart card reader.

In an embodiment, for a photo identity card identification element, an optical scanner acquisition device can be used to obtain image identification data indicative of the identification element. This image identification data can be processed by the computing device (and computer program product), such that the type of identification element can be recognised and the image identification data processed and segmented to relevant identification data fields.

In an embodiment, for a secure electronic storage card identity card identification element, a card reader acquisition device can directly retrieve identification data.

It will be appreciated that many identification elements have further authentication data that can be used to authenticate the identification element. This authentication data is typically duplicate data stored in an alternate form such as a barcode, which can be compared or verified against other data presented by the identification element.

The acquisition device can be adapted to further retrieve authentication data for authentication by the computing device (and computer program product).

It will be appreciated that the acquisition device can be adapted to acquire or receive identification data from a plurality of different forms of identification elements.

The acquisition device enables a plurality of identification element forms to be presented. Upon presenting a new, previously non-presented identification element, relevant identification data is retrieved and determined such that a sufficient record key can be obtained to identify a patron record within the database. Upon s confirmation that the patron has been accurately identified, new identification data indicative of the previously non-presented identification element is retained by the database.

FIG. 5A through FIG. 5C show a plurality of possible identification elements that can be presented to the acquisition device, including a photographic identification element in the form of a drivers licence 500 or a passpoit 501 and a magnetic stripe card or smart card 503. The identification element can belong to an approved set of identification elements, such as a divers licence (for example a New South Wales drivers licence) or a proof of age identification card (for example a New South Wales Photo Card).

By way of example, a photo identification element can include any one or more of the following: > an issuing authority 510 of the identification element; > a photograph 520 of the identification element owner; > a name 530 of the identification element owner; > an address 532 of the identification element owner > a serial number 534 of the identification element; > date of birth 536 of the identification element owner It will be appreciated that, once the identification element is classified, the location of the relevant information data can be determined.

The processor device further comprises a computer program product stored on a computer usable medium for processing the data retrieved or acquired by the acquisition device, determine identification data indicative of the identification element, interrogating the database, retrieving verification data indicative of a patron record, displaying verification data to the display element for verifying the patron.

It will also be appreciated that identification data can be securely stored on a magnetic stripe card or smart card 502. The acquisition device can retrieve the identification data 560 from the card. Further authentication data may be printed or embossed on the card, including an issuing authority 510 of the identification element, and other S relevant identification data 550.

As the database typically maintains a photograph identification of the patron, in an example embodiment, a membership card can be provided to the patron such that, upon presenting the membership card to the acquisition device, the relevant patron record can be retrieved from the database -thereby enabling the displaying of one or more respective photographs of the patron for identification or verification. The database can also maintain data indicating that a patron has accepted or rejected membership to the venue.

FIG. 6A shows a flowchart 6oo for a method of identifying a patron to a venue. The method comprises the steps of: STEP 6io: presenting an identification element to an acquisition device; STEP 612: acquiring raw identification data indicative of the identification element; STEP 614: processing raw identification data to present identification data indicative of the identification element; STEP 6i6: interrogating a database to retrieve one or more patron records, being potential matches within the database, each patron record having verification data; and STEP 618: displaying verification data to a display element for verifying the patron (for example, as shown in FIG. 4A).

The verification data can further include one or more incident data related to the patron record retrieved.

Upon displaying an identified/verified patron and operator can be presented with one or more options.

FIG. 6B shows a flowchart 6o for a method of identifying a patron to a venue. The method comprises the steps of: STEP 660: verifying the patron record is indicative of the presenting patron; STEP 662: if no corresponding patron record is stored in the database, adding acquired indentation data to a new patron record and storing the patron record in the database; upon adding a new patron record an operator can elect to grant or deny the presenting patron access to the venue; STEP 664: if a corresponding patron record is presented and the presenting patron being verified; an operator can identify if incident data has been associated with the patron record; STEP 666: if incident data has not been associated with the patron record, an operator can elect to grant or deny the presenting patron access to the venue; STEP 670: if incident data has been associated with the patron record, an operator can elect to grant or deny the presenting patron access to the venue; STEP 672: in the light of incident data being associated with the patron record, the operator can elect to deny the presenting patron access to the venue; STEP 674: in the light of incident data being associated with the patron record, the operator can elect to grant the presenting patron access to the venue; and STEP 676: if, in the light of incident data being associated with the patron record the operator is electing to grant the presenting patron access to the venue, the patron can be placed on a watch list (for example, as shown in FIG. 4B).

Each patron record can be associated with one or more associated incidents recorded, a licence security person or manager may select to either refuse or allow entry to the patron. If a patron has been granted entry and an incident involving the patron occurs, an incident data can be recorded and associated against the patron record.

Upon interrogating a database using information data acquired from the identification element, a patron record can be found, further information provided by the identification element may be stored in relation to the patron record. If no patron record can be identified, a new patron record may be generated using the identification information obtained from the identification element, and/or any further information provided by an operator. If a plurality of records were found to s match information data available from the information, the operator is prompted to select the corresponding patron record based on information stored in respect of each matched patron. When an operator identifies the selected patron, or identifies no match, a patron record can be updated and/or created.

FIG. 7 shows a flowchart 700 for a method of identifying a patron to a venue schematic, and associating incident data to a patron record. The method comprises the steps of: STEP 71o: retrieving one or more recent patrons granted access to a venue; STEP 712: confirming a patron responsible for an incident; STEP 714: enter, storing and associating incident data with the patron record in the database; and STEP 716: synchronise the patron records with an external database.

By way of example, when a patron is ejected from a venue, it is possible to review patrons previously granted entry to the venue by viewing photographs. Once the ejected patron is identified, an incident can be added against the patron record. The type of incident added to the patron record may necessitate that two or more authorised managers or security officers must first verify the incident before it is recorded. Alternatively if the patron identification element is obtained, their data record may be retrieved by rescanning the identification element and then associating the incident.

Protocols may be implemented for relating incident data to a patron. For example, relating incident data to a patron may require: confirmation by two or more authorised operators/people, or undergo a predetermined review process. By way of example, Incident data can be related to a patron for a predetermined time, and/or may be challenged by the patron under a review process. It would be appreciated that a authorised operator can be verified and/or authenticated by providing a login-password pair, or completing any other verification/authentication process. Each authorised operator can be uniquely identified, for example by a unique user name or number.

It will be appreciated that, for other associated venues to have access to incident data relating to one venue, at least a portion of the patron record must be synchronised and made available across each associated venue. Synchronisation of the local database central/remote database may be manual or automatic.

It will be further appreciated that, for other third parties to have access to a portion of patron data acquired by a venue, without enabling access to a venue local database, at least a portion of the patron record must be synchronised and made available to a remote database server.

FIG. 8A through FIG. 8C show a schematic view of optional synchronisation configurations.

FIG. 8A shows a venue local database 8io can comprise a plurality of patron records Sii. Each patron record being related (or associated) with a key 812 and one or more identification elements 813. One or more patron records can be synchronised with a remote database 850. The remote database can comprise a plurality of patron records 8i. Each patron record being related (or associated) with a key 852 and one or more identification elements 853. It will be appreciated that the remote database can be configured (either physically or logically) as one or more databases (for example 86o and 870).

In an embodiment, all patron data can be synchronised to maintain a repository of all registered patrons in one or more associated venues. However, in addressing privacy concerns, it may be appropriate to only synchronise relevant data between selected one or more venues. To achieve this, one or more databases may be maintained to maintain relevant relations between registered patrons and particular venues.

In an embodiment, patron data records can be synchronised with a remote database and/or other venues. To address security and privacy concerns associated with synchronising data a number of configurations are available, including any one or more of the following: > synchronise patron data having associated incident data; > synchronise patron data having an associated membership involving one or more venues; > synchronise patron data, associating a venue identifier for new data acquired by the venue, which is not made available to other venues; In an example, only patron data having associated incident data and/or is associated with a membership involving one or more venues is synchronised. The data synchronised may be restricted to all available patron data having associated incident data; and a selected portion of patron data associated with a membership involving one or more venues. A membership can include any agreed association between one or more venues, typically for marketing purposes.

Patron record data, not associated with incident data, may be maintained by the local venue (or other affiliated venues). For example, patron data may be shared amongst affiliated venues for which a patron has approved or accepted terms for a membership scheme.

The patron database record may be further synchronised with third party databases (for example a database of registered gambling addicts, a database of registered alcoholics, a database of registered medical alert, a database of people of interest to law enforcement such as missing or wanted). Typically this involves importing data to a remote server database, adding new patron records for people not yet identified, or identifying a corresponding patron record, and relating incident data provided by the third party database. Alternatively, a third party may communicate directly with the remote server device for adding a new patron records for people not yet identified (or identifying a corresponding patron record) and relating relevant incident data. The data added to the remote database can be made available to the local venue, and synchronised with the local database.

Inconsistencies are typically the result of incorrect data being provided, an incorrect patron record being indentified. Database inconstancies can be flagged for a manager to review before data is accepted. It would be appreciated that by maintaining a photographic identification record, an operator may be less likely to miss identifying a patron.

It is preferred that multiple records for a single patron be substantially avoided. This is particularly of relevance when acquiring new data of a patron, when visiting a venue or when synchronising databases with other venues or a remote database. The initial database record may have been generated using a different form of identification element and bought into the current database via a synchronisation process. Various synchronisation processes will be discussed further below.

Referring to FIG. 8A, patron record data 8i1 maintained in the local database 8io is identified by a key 812. Selected patron data can be synchronised 88i with a remote database 850, wherein a corresponding patron record 86i can be uniquely identified by a remote key 862.

It will be appreciated that the local database can push' (or transmit) new patron records to the remote database server. If a corresponding patron record already exists on the remote database, then the remote database server can extract any updated data from the pushed patron record.

For a patron record added to a local database, and the patron record is programmed for synchronisation with the remote database, the remote database can be interrogated for a corresponding patron record: > if no potential matches exists, then a new patron record can be added to the

remote database populating selected data fields;

> if one or more potential matches exist, then the potential matches can be reviewed further (manually or automatically) to determine a corresponding patron record, or otherwise; > if a corresponding patron record is confirmed, or a new record added, then the local and remote data records are synchronised -at least for selected data elements.

For a patron record added to a remote database, and the patron record is programmed for synchronisation with the venue local database, the local database can be interrogated for a corresponding patron record: > if no potential matches exists, then a new patron record can be added to the

local database populating selected data fields;

> if one or more potential matches exist, then the potential matches can be reviewed further (manually or automatically) to determine a corresponding patron record, or otherwise; > if a corresponding patron record is confirmed, or a new record added, then the local and remote data records are synchronised -at least for selected data elements.

Patron records typically programmed for synchronisation include patron records associated with incident data or a membership authorisation. The venue may further provide sanitised patron record data to a remote database, which can be used for producing marketing reports and/or analysis.

Data synchronisation can be contained within one or more databases (either physically or logically). For example, patron records associated with incident data can be maintained/synchronised 8th via first database 86o and patrons associated with a membership can be maintained/synchronised 882 via a second database 870.

However, it would be appreciated that a logical distinction between data records can be maintained by asserting one or more relationships to the record and/or one or

more associate data fields.

A database can be provided as a single database or a plurality of distributed databases, being local or remote.

FIG. 8B shows a database 820 (for example another venue local database) being synchronised with a remote patron database 850. Typically this involves synchronising data 883 with the remote server database, adding new patron records for people not yet identified, or identifying a corresponding patron record, and relating incident data provided by the third party database. The data added to the remote database can be made available to the local venue, and synchronised 88i with the local database.

FIG. 8C shows a database 820 (for example another venue local database) being synchronised with one or more remote patron database 8o,86o. Typically this involves synchronising data 883,884 with the remote server database, adding new patron records for people not yet identified, or identifying a corresponding patron record, and relating incident data provided by the third party database. The data added to the remote database can be made available to the local venue, and synchrornsed 881,882 with the local database.

Synchronising of specific data record elements can be restricted. For example: > if a patron record is related with a membership associated with a venue, then member related data may be syiichronised with the remote server and associated venues; > if a patron record is related to incident data, then available identification data and incident data may be syncbronised with the remote server and all venues.

Referring to FIG. 9, in an embodiment, patron data 910 associated with a membership io can be maintained/synchronised 915 by the remote database server database 920.

A registered member to a venue may also provide contact details including telephone, mobile and/or email addresses. This can be used by affiliated venues having access to synchronised records from a venue to provide marketing material to members.

Typically membership data is only retained by one venue. However, affiliated memberships can enable data to be shared/synchronised across a number of venues.

One or more venue local database can be synchronised with a single remote database, which can be accessed for providing a marketing campaign. A patron membership registration can authorise access for a marketer to transmit to the patron a marketing campaign associated with a venue for which the patron has membership. A single membership registration can be associated with one or more venues. Similarly, a patron may have a plurality of separate memberships.

Access can be enabled for authorised marketers and marketing campaigns. By way of example, marketers and/or marketing campaigns may be authorised only for selected * . (or associated) memberships groups. An authorised marketer can access a user * * .75 interface 930 to schedule marketing campaigns targeted to selected members of a membership group. The marketing campaign scheduled against each member is typically recorded in the database. A marketing dispatch module 940 can then * interrogate the database for scheduled marketing campaigns and initiate communicating the marketing script to the targeted member.

** S*.� * S

S

S..... S a

Referring to FIG. 10, creating a marketing campaign a marketer (for example a venue or authorised third party) can create a campaign parameters 1022 and campaign script 1024. The campaign parameter can be submitted 1026 to a user interface 1030 for interrogating the database 1010 and identffijing a target subset of members 1040 s for the particular marketing campaign. A marketing dispatch module 1050 can retrieve contact details for the targeted members, used in combination with a submitted campaign script 1028, to provide targeted campaign marketing io6o to each selected member. It would be appreciated that as the member database may be synchronised with a remote database server, the campaign parameters and campaign script may be provided by a third party provided access to the membership database.

In an embodiment, members to a venue may be entitled to a gift/prize based on a pre-determined parameter. Predetermined parameters can include a specified number of visits to a venue or number of products purchased.

The database can be further used to provide management reports, typically not containing personal information, but reporting peak times, general demographic profiles of patrons, and registered member loyalty/attendances.

Referring to FIG. nA and FIG. iiB, a marketing campaign can be retrieved by, or transmitted to, a patron access device 1110,1112 (for example a third party access device).

A registered member to a venue can provide contact details including telephone, mobile and/or email addresses. This can be used by affiliated venues having access to synchronised records from a venue to provide, or enable access to, marketing material.

A remote server device 210 can include a server module 1120 for enabling access to (or transmitting) one or more marketing campaigns. For example, a marketing campaign can be presented/retrieved 1130,1132 (or transmitted 1130, 1132).

A patron access device 1110, 1112 can be in the form of a mobile phone, personal digital assistant, netbook, iPhone or iPad etc, which can be coupled to the data network 220 for communicating with the remote server device 210 for retrieving, or receiving, one or more marketing campaigns.

For example, one or more marketing campaigns can be accessed by a prospective patron through: > a user interface presented by the web sewer module, thereby presenting (or enabling access to) one or more marketing campaigns (for example 1130, 1132); > an application executed by a patron access device that retrieves one or more marketing campaigns (for example 1130, 1132) from the remote server device for presenting a catalogue of the one or more marketing campaigns; > receiving one or more emails (for example 1140), each indicative of one or more marketing campaigns; and > receiving one or more short message service (SMS) communications (for example 1142), each indicative of one or more marketing campaigns.

It would be appreciated that a patron access device can: receive, or retrieve, one or more marketing campaigns for maintaining a local catalogue of one or more current marketing campaigns; and/or access an remote server interface that presents one or more current marketing campaigns.

An application can be included on an access device for retrieving, maintaining and presenting a catalogue of one or more current campaigns being offered by venues. The data indicative of one or more current campaigns can be retrieved automatically or manually initiated.

Access to a marketing campaign can, for example, be restricted to: targeted/selected patrons; or registered members of a corresponding venue; or registered members of any affiliated venue; or any patron having a membership record. Alternatively, unrestricted retrieval (or access to) a marketing campaign can be provided to any third party device, thereby providing a centralised public availability (or access) to one or more current marketing campaigns.

It would be further appreciated that other communications can be used, including: instant messaging, tweeting, social network messaging, email, short message service, facsimile, and generated voice call.

It will be appreciated that the illustrated method and apparatus can be used in identifying patron presenting to a venue.

Unless specifically stated otherwise, as apparent from the following discussions, it is appreciated that throughout the specification discussions utilising terms such as "processing", "computing", "calculating", "determining" or the like, refer to the action and/or processes of a computer or computing system, or similar electronic computing s device, that manipulate and/or transform data represented as physical, such as electronic, quantities into other data similarly represented as physical quantities.

In a similar manner, the term "processor" may refer to any device or portion of a device that processes electronic data, e.g., from registers and/or memory to transform that electronic data into other electronic data that, e.g., may be stored in registers and/or memory. A "processing system", or equivalently: "computer", "computing machine" or a "computing platform" may include one or more processors.

Thus, one example is a typical processing system that includes one or more processors.

Each processor may include one or more of a CPU, a graphics processing unit, and a programmable DSP unit. The processing system further may include a memory subsystem including main RA1VI and/or a static RAM, and/or ROM. A bus subsystem may be included for communicating between the components. The processing system further may be a distributed processing system with processors coupled by a network.

If the processing system requires a display, such a display may be included, e.g., an liquid crystal display (LCD) or a cathode ray tube (CRT) display. If manual data entry is required, the processing system also includes an input device such as one or more of an alphanumeric input unit such as a keyboard, a pointing control device such as a mouse, and so forth. The term memory unit as used herein, if clear from the context and unless explicitly stated otherwise, also encompasses a storage system such as a disk drive unit. The processing system in some configurations may include a sound output device, and a network interface device. The memory subsystem thus includes a computer-readable carrier medium that carries computer-readable code (e.g., software) including a set of instructions to cause performing, when executed by one or more processors, one of more of the methods described herein.

In alternative embodiments, the one or more processors operate as a standalone device or may be connected, e.g., networked to other processor(s), in a networked deployment, the one or more processors may operate in the capacity of a server or a client machine in server-client network environment, or as a peer machine in a peer-to-peer or distributed network environment. The one or more processors may form a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine.

Note that while some diagrams only show a single processor and a single memory that carries the computer-readable code, those in the art will understand that many of the components described above are included, but not explicitly shown or described in order not to obscure the inventive aspect. For example, while only a single processor "processing system" is illustrated, the term "processing system" shall also be taken to include any collection of processors that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.

Methodologies described herein are, in one embodiment, performable by one or more processors that accept computer-readable (also called machine-readable) code containing a set of instructions that when executed by one or more of the processors carry out at least one of the methods described herein. Any processor capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken are included. A computer-readable carrier medium may form, or be included in, a computer program product. The computer readable medium comprises computer code for executing a method as herein described. Note that when the method includes several elements, e.g., several steps, no ordering of such elements is implied, unless specifically stated. The software may reside in the hard disk, or may also reside, completely or at least partially, within the RAM and/or within the processor during execution thereof by the computer system. Thus, the memory and the processor also constitute computer-readable carrier medium carrying computer-readable code.

Thus, one embodiment of each of the methods described herein is in the form of a computer-readable carrier medium carrying a set of instructions, e.g., a computer program that are for execution on one or more processors, e.g., one or more processors that are part of whatever the device is. Thus, as will be appreciated by those skilled in the art, embodiments of the present invention may be embodied as a method, an apparatus such as a special purpose apparatus, an apparatus such as a data processing system, or a computer-readable carrier medium, e.g., a computer program product. The computer-readable carrier medium carries computer readable code including a set of instructions that when executed on one or more processors cause the a processor or processors to implement a method. Accordingly, aspects of the present invention may take the form of a method, an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware s aspects. Furthermore, the present invention may take the form of carrier medium (e.g., a computer program product on a computer-readable storage medium) carrying computer-readable program code embodied in the medium.

It will be understood that the steps of methods discussed are performed in one embodiment by an appropriate processor (or processors) of a processing (i.e., computer) system executing instructions (computer-readable code) stored in storage.

It will also be understood that the invention is not limited to any particular implementation or programming technique and that the invention may be implemented using any appropriate techniques for implementing the functionality described herein. The invention is not limited to any particular programming language or operating system.

Furthermore, some of the embodiments are described herein as a method or combination of elements of a method that can be implemented by a processor of a processing system (or computer) or by other means of carrying out the function. Thus, a processor with the necessary instructions for carrying out such a method or element of a method forms a means for carrying out the method or element of a method.

Furthermore, an element described herein of an apparatus embodiment is an example of a means for carrying out the function performed by the element for the purpose of carrying out the invention.

The software (or computer program) may further be transmitted or received over a network via a network interface device. While the carrier medium is shown in an exemplary embodiment to be a single medium, the term "carrier medium" should be taken to include a single medium or multiple media (e.g., a centralised or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term "carrier medium" shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by one or more of the processors and that cause the one or more processors to perform any one or more of the methodologies of the present invention. A carrier medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. Non-volatile media includes, for example, optical, magnetic disks, and magneto-optical disks. Volatile media includes dynamic memory, such as main memory. Transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise a bus subsystem. Transmission media also may also s take the form of acoustic or light waves, such as those generated during radio wave and infrared data communications. For example, the term "carrier medium" shall accordingly be taken to included, but not be limited to, solid-state memories, a computer product embodied in optical and magnetic media, a medium bearing a propagated signal detectable by at least one processor of one or more processors and representing a set of instructions that when executed implement a method, a carrier wave bearing a propagated signal detectable by at least one processor of the one or more processors and representing the set of instructions a propagated signal and representing the set of instructions, and a transmission medium in a network bearing a propagated signal detectable by at least one processor of the one or more processors and representing the set of instructions.

Reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention.

Thus, appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment, but may. Furthermore, the particular features, structures or characteristics may be combined in any suitable manner, as would be apparent to one of ordinary skill in the art from this disclosure, in one or more embodiments.

Similarly it should be appreciated that in the above description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. This method of disclosure, however, is not to be interpreted as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, any claims following the Detailed Description are hereby expressly incorporated into this Detailed Description, with each claim standing on its own as a separate embodiment of this invention.

Furthermore, while some embodiments described herein include some but not other features included in other embodiments, combinations of features of different embodiments are meant to be within the scope of the invention, and form different embodiments, as would be understood by those in the art. For example, in the following claims, any of the claimed embodiments can be used in any combination.

In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. In other instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this

description.

Thus, while there has been described what are believed to be the preferred embodiments of the invention, those skilled in the art will recognise that other and further modifications may be made thereto without departing from the spirit of the invention, and it is intended to claim all such changes and modifications as fall within the scope of the invention. For example, any formulas given above are merely representative of procedures that may be used. Functionality may be added or deleted from the block diagrams and operations may be interchanged among functional blocks. Steps may be added or deleted to methods described within the scope of the present invention.

Any one of the terms "comprising", "comprised of' or "which comprises" is an open term that means including at least the elements/features that follow, but not excluding others. Thus, the term comprising, when used in the claims, should not be interpreted as being limitative to the means or elements or steps listed thereafter. For example, the scope of the expression a device comprising A and B should not be limited to devices consisting only of elements A and B. Any one of the terms including or which includes or that includes as used herein is also an open term that also means including at least the elements/features that follow the term, but not excluding others. Thus, including is synonymous with and means comprising.

Similarly, it is to be noticed that the term "coupled", when used in the claims, should not be interpreted as being limitative to direct connections only. The terms "coupled" and "connected", along with their derivatives, may be used. It should be understood that these terms are not intended as synonyms for each other. Thus, the scope of the s expression a device A coupled to a device B should not be limited to devices or systems wherein an output of device A is directly connected to an input of device B. It means that there exists a path between an output of A and an input of B which may be a path including other devices or means. "Coupled" may mean that two or more elements are either in direct physical or electrical contact, or that two or more elements are not in direct contact with each other but yet still co-operate or interact with each other.

As used herein, unless otherwise specified, the use of the ordinal adjectives "first", "second", "third", etc., to describe a common object, merely indicate that different instances of like objects are being referred to, and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.

Although the invention has been described with reference to specific examples, it will be appreciated by those skilled in the art that the invention may be embodied in many other forms.

It will be appreciated that an embodiment of the invention can consist essentially of features disclosed herein. Alternatively, an embodiment of the invention can consist of features disclosed herein. The invention illustratively disclosed herein suitably may be practiced in the absence of any element which is not specifically disclosed herein.

Claims (20)

1. CLAIMS1. An apparatus for identifying a venue patron, the apparatus comprising: a processor device coupled to an acquisition device and a first database; the processor device adapted receive raw identification data from the acquisition device, and processes this raw identification data to identify data indicative of an identification element presented by the venue patron; the processor further adapted to retrieve one or more patron records from the first database; and the processor device being coupled to a display element for displaying one or more patron record, each indicative of a candidate patron selectable by an operator for identifying the venue patron.
2. 2. The apparatus according to any one of the preceding claims, wherein: the acquisition device is adapted to receive the identification element, the acquisition device being further adapted to acquire raw identification data indicative of the identification element; the identification element is a photo identification card; and the raw identification data is image data.
3. 3. The apparatus according to any one of the preceding claims, wherein: if the venue patron is verified against a first patron record, the identification data is used to update the first patron record stored in the first database; and if the venue patron is not verified against the one or more retrieved patron records, the identification data is used to create the first patron record stored in the first database.
4. 4. The apparatus according to any one of the preceding claims, wherein: the processor device is further adapted to retrieve incident details associated with a selected patron record from the first database, the incident data is presented on a display element to thereby enable an operator to assess the venue patron.
5. 5. The apparatus according to claim 4, wherein, if despite a patron having been identified with one or more associated incidents recorded, the patron is granted entry to the venue, the processor maintains a watch count for indicating a number of times entry to a venue has been allowed to the patron without further incident.
6. 6. The apparatus according to any one of the preceding claims, wherein: the processor device is adapted to maintain a watch count indicative of a number of times entry to a venue has been allowed to the venue patron without further incident; the watch count being stored in the first database; and the first database is synchronised with a remote database; and the remote database is further synchronised with a plurality of other venue associated databases.
7. 7. The apparatus according to any one of the preceding claims, wherein: a patron record includes an alert element being indicative of a watch alert; wherein, if the patron is verified against a patron record having a alert element indicating a watch alert, a communication is sent to a third party associated with the alert element.
8. 8. The apparatus according to claim 7, wherein the alert element indicating a patron being associated with a watch alert that includes any one or more selected from the set comprising: a registered gambling addict; a registered alcoholic; a registered medical alert; a registered missing person; a person of interest to law enforcement; an incident detail; and a watch count.
9. 9. The apparatus according to any one of the preceding claims, wherein the first database is a venue local database that is synchronised with a remote database for updating data acquired from other venues.
10. 10. The apparatus according to any one of the preceding claims, wherein a remote database is synchronised with the first database, and can be accessed for providing a marketing campaign.
11. 11. The apparatus according to claim 10, wherein, the remote database can maintain membership data indicative of a patron membership registration associated with one or more venues, the membership data can include authorisation for access by a marketer.
12. 12. The apparatus according to any one of the preceding claims, wherein one or more predetermined elements of the patron records from the first database are synchronised with a second database.
13. 13. The apparatus according to claim 12, wherein: the first database is a venue local database and the second database is a remote database; the first database being synchronised with the second database, such that first predetermined elements of the first database are updated with remotely obtained respective predetermined elements of the second database, and such that second predetermined elements of the second database are updated with locally obtained respective predetermined elements.
14. 14. The apparatus according to any one of claims 12 to 13, wherein: a patron record includes a membership element being indicative of membership registration for authorising access to a marketer; wherein the second database, being synchronised with the first database, is accessible for providing a marketing campaign to patrons associated with the membership element indicating membership registration.
15. 15. The apparatus according to any one of the preceding claims, the apparatus being adapted to collect and maintain a database of registered patrons; wherein, if a presenting patron is verified against a first patron record, the second identification data is used to update the first patron record stored in the database; and wherein, if a presenting patron is not verified against the one or more retrieved patron records, the second identification data is used to create the first patron record stored in the first database.
16. 16. An apparatus for identifying a venue patron, substantially as herein described with reference to any one of the embodiments of the invention illustrated in the accompanying drawings and/or examples.
17. 17. A method of identifying a venue patron using an apparatus according to any one of the preceding claims, the method comprising the steps of: (a) presenting an identification element to an acquisition device; (b) acquiring raw identification data indicative of the identification element; (c) processing raw identification data to present identification data indicative of the identification element; (d) interrogating a database to retrieve one or more patron records, being potential matches within the database, each patron record having verification data; and (e) displaying verification data to a display element for verifying the patron.
18. i8. A method according to claim 17, further comprising the step of synchronising the first database with a remote database.
19. 19. A method of identifying a venue patron, substantially as herein described with reference to any one of the embodiments of the invention illustrated in the accompanying drawings and/or examples.
20. 20. A user access interface for an apparatus according to any one of claims 1 to i6, the apparatus being adapted to identify venue patron, the apparatus being coupleable to database having one or more patron records; the interface comprising: a control program adapted to: receive first identification data from an acquisition device; process the first identification data to second identification data indicative of an identification element; and retrieve one or more patron records for identifying a venue patron.