GB2461963A - Access control system and method - Google Patents

Abstract

A system for controlling access to an event, comprises a user access device 2 comprising an identifier, wherein the identifier comprises at least one of a user identifier and a device identifier, means for obtaining information concerning a user, and associating the user information with the identifier, and means for reading the identifier from the access device 6, and obtaining the associated user information in dependence upon the identifier. The user information may be a photograph of the user, biometric information, image data or a PIN. The user information may be displayed and access controlled on the basis of the user information. The system may have a central server (14, Fig 3), local servers (40, Fig 3) and at least one access control device, the central server (14) providing user information and identifiers to the relevant local server (40) for a particular event. The system may be able to authorise users, allow groups of users to exchange access authorisations, have waiting lists of users, be linked to social networking websites and have user statuses and loyalty information maintained at the central server. The user access device is preferably a RFID wristband that the user wears.

Description

Access control system and method The present invention relates to a method, and apparatus, for controlling access. The invention relates in particular to the control of access by a user to an event, location or service.

The most common method of controlling access of a user is to issue the user with a paper or other ticket. The user presents the ticket at a control point and, if the ticket is valid, the user is allowed entry to the event, location or service. However, in general, there is no check of whether the ticket is held by a user who is entitled to entry. Thus, there is little to stop a user entering with a stolen ticket. Also, ticket touting, in which a ticket is sold on by the original purchaser to another user, often via an intermediary and at an inflated price, is difficult to prevent.

An alternative method of controlling access is described in WO 2006/114613. According to WO 2006/114613 a user purchasing a ticket provides a mobile phone number and a photograph, which are stored in a database. The photograph may be taken by the user with a camera phone and provided via MMS message. A ticket identifier, usually in the form of a bar code, is sent to the mobile phone. In order to obtain entry to an event the user must display the bar code on the screen of the mobile phone, or transmit the code from their phone using Bluetooth or WiFi. The bar code is scanned by an operative using a scanner and read into a terminal, The terminal retrieves the user's photograph from the database and compares the photograph to the appearance of the user, and allows access if they match.

However, the method of WO 2006/114613 requires that a user takes their mobile phone to : .. an event, which is often inconvenient and undesirable, both for a user and for an event S..

organiser, as the user may not wish to risk their phone being lost or stolen, and the event organiser may wish to restrict photography or sound recordal. Furthermore, there is nothing 3JJ: in WO 2006/114613 that provides any way of preventing transfer of the bar code or other :" ticket identifier from one mobile phone to another, or duplicating the bar code or other ticket identifier on a plurality of mobile phones. In addition, there are circumstances in which a user may genuinely not be able to attend an event after purchasing a ticket, and may wish to transfer the ticket to another user. WO 2006/114613 does not provide any facility for validation of transfer of a ticket to another user and thus provides no less incentive for ticket touting than methods using traditional paper tickets.

In a first independent aspect of the invention there is provided a system for controlling access to an event, comprising:-a user access device comprising an identifier, wherein the identifier comprises at least one of a user identifier and a device identifier; means for obtaining information concerning a user, and associating the user information with the identifier; and means for reading the identifier from the access device, and obtaining the associated user information in dependence upon the identifier. The system may further comprise means for displaying the user information. The system may comprise means for controlling access of a user to the event in dependence upon the user information.

In another independent aspect of the invention there is provided apparatus for controlling access, comprising:-a user access device having a device identifier; means for obtaining information concerning a user, and associating the user information with the device identifier; means for reading the device identifier from the access device, and obtaining the associated user information in dependence upon the device identifier; and means for displaying the user information.

The means for obtaining the user information may comprise a user input system, for example a user input device and/or a website. The system may comprise a data processing system for associating the user information with the identifier. The data processing system may comprise a processor and optionally an associated data store. The means for reading may comprise a reader device, which may comprise a processor and a display. The means for displaying the user information may comprise the or a display included in or associated with the reader device. The access control means may comprise, for example, a barrier. * * *

The device identifier may be unique to the device. By providing an access device having a **** device identifier and/or user identifier to a user, and by associating the device identifier : *. and/or user identifier with at least one characteristic of a user, it can be ensured that S...

duplication or transfer of a ticket is made more difficult. In contrast, if ticket data such as the bar code of WO 2006/11461, is sent to an existing user device it may be difficult to prevent : transfer or duplication of that ticket data across other devices. *

S

The displayed user information may be compared with the user presenting the access device, either automatically or by an operator, and access may be provided only if the user information seems to match the user and if the user has right of access to the event, premises or other location, or service The user information usually comprises image data, for instance a photograph of the user, but may comprise or be represented by any kind of biometric data, for instance fingerprint data or iris scan data, or a user-provided Personal Identification Number, similar to that used in bank card authorisation. The unique device identifier may be provided in hardware or software. The apparatus or system may comprise storage means for storing data representative of the user information and the device identifier. The storage means may comprise at least one database.

The system may comprise a plurality of the user access devices, each having a respective identifier; a central server that comprises a data store for storing the user information and the identifiers; an event access sub-system that comprises a local server and at least one access control apparatus, wherein:-the or each access control apparatus comprises the reading means and displaying means; the remote server is configured to transmit user information and identifiers to the local server, and the local server comprises a data store for storing the user information and the identifiers; the reading means is configured to transmit a request for user information to the local server, in response to reading of the identifier from a user access device; and the local server is configured to transmit the user information.to the access control apparatus in response to the request.

The local server may be configured to select user information and identifiers for users who have authorisation to access the event, and the transmitting of user information and identifiers to the local server comprises transmitted the selected user information and identifiers to the local server. * S *

*25. The local server may be configured to monitor identifiers read by the at least one access ** control apparatus, to maintain a record of user access to the event, and to transmit the ::::. record of user access to the event to the remote server.

The system may comprise means (for example, the or a data processing system) for S...

.30: associating a user identifier, representative of the identity of the user, with the device :" identifier and/or with the user information.

The access device may be provided to a user in response to a ticket purchase by the user.

The access device may be provided to a user in response to a first ticket purchase and may be reusable for subsequent ticket purchases. The access device may be replaced if the user loses it, or it is stolen, or damaged The user information may be associated with the device identifier of the replacement device.

The access device may comprise transceiver circuitry and optionally comprises radio frequency identification (rfid) circuitry. Such rfid circuitry can be robust and easy to read, and may be read remotely, without necessarily requiring a reader device to be in physical contact with the device. The rfid circuitry may comprise circuitry having a unique rfid identifier that may be used as the device identifier.

In a further, independent aspect of the invention there is provided apparatus for controlling access, comprising:-an access device comprising rfid circuitry, the access device including an identifier; means for obtaining information concerning a user and associating the user information with the identifier; means for reading the identifier and obtaining the associated user information in dependence upon the identifier; and means for displaying the user information.

In another independent aspect there is provided an electronic ticket device comprising rfid circuitry.

The device may be a device that is wearable by a user. The device may comprise a wristband, ankleband or badge, clothing, or key-ring. The device may comprises RFID circuitry attached to another device such as a phone or other personal electronic device, or attached to a third party token or pass, such as a travel pass. * S S

The apparatus or system may further comprise means for storing authorisation data and **** associating the authorisation data with a device identifier and/or with a user identifier. The ::::. storing means may comprise a data store. The authorisation data may represent authorisation to access an event, location or service. The apparatus or system may further comprise means for reading the authorisation data associated with a device identifier and/or S...

: user in dependence on the device identifier read from the access device. Thus, it may be : determined both whether an access device is in the possession of the correct user, and whether that user is authorised to access a particular event, location or service. The user information may comprise the authorisation data.

The apparatus or system may further comprise means for transferring authorisation associated with one user and/or device identifier to another user and/or device identifier.

The transfer of authorisation may comprise, for each user and/or device identifier, modifying the authorisation data associated with the user and/or device identifier. The transfer of authorisation may be performed in response to a user request. The transferring means may comprise the or a data processing system.

In another independent aspect there is provided a system for controlling access, comprising:-storage means for storing a plurality of device or user identifiers, each identifier identifying a respective user access device or user; means for associating authorisation data with at least one of the identifiers, the authorisation data representing access authorisation; and means for subsequently transferring authorisation from one user access device or user to another user access device or user, optionally by altering the authorisation data.

The authorisation data may be associated with the device identifier directly or indirectly, for instance by mutual association with the same user identifier. The apparatus or system may comprise means (for example, the or a data processing system) for determining the number of authorisations that have been issued, optionally configured to determine whether the number of authorisations has matched or exceeded a predetermined threshold. The determining means may be configured to co-operate with the transferring means such the transfer means transfers authorisation only if the number of authorisations has matched or exceeded the threshold. The threshold may be equal to the maximum number of authorisations that are to be issued for an event. The transfer means may be configured to transfer authorisation only if an event is oversubscribed.

:. By providing for the transfer of authorisation, the method allows the transfer of access to an * event, service or location from one user to another. The apparatus or system may further comprise means for grouping users into user groups and providing transfer of authorisation : .. between users in dependence on whether the users are in the same user group.

The apparatus or system may comprise user selection means, for example a user selection *: module, for enabling user to select at least one other user to be in their user group. The : apparatus or system may comprise means for charging for transfer of authorisation between users in dependence on whether the users are in the same group. The charging means may be configured to refund a user and to charge a further user in response to transfer of authorisation from the user to the further user, optionally only if the user and the further user are not in the same user group. The charging means may be configured to transfer authorisation from the user to the further user without refund and/or without charge if the user and the further user are in the same user group.

The system may further comprise means for receiving user requests to access the event and means for maintaining a waiting list of user requests to access the event, and the transferring means is configured to transfer authorisation to a user and/or device identifier associated with a user having a user request in the waiting list.

The system may further comprise data storage means for storing user records, each user record comprising an identifier included in a respective user access device and respective user information.

Each user record may comprise respective user status data.

The transferring means may be configured to allow or disallow a transfer of authorisation from one user to another user in dependence upon the status of one or both of the users, represented by the user status data for the users.

The system may further comprise means for receiving a user request to obtain authorisation to access an event, and determining whether or not to provide authorisation in dependence upon the user status data for the user.

The user status data may comprise loyalty data.

The apparatus or system may further comprise a website and associated processing system, :. the website optionally comprising a respective webpage or other website space associated with each user. The website may comprise the or a means for receiving a user request to obtain authorisation to access an event. The website may be a ticket purchase website that : .. is configured to allow users to purchase access authorisation for events, services, or S...

locations. The website is optionally configured to allow users to post information, for instance photographs or comments, which may concern events, services, or locations. The *: method may comprise varying the price paid by a user for access to events, services or locations and/or varying the status of the user in dependence upon information posted by the user. Thus a loyalty scheme may be provided, in which prices may be varied, and in which preferential access to tickets may be provided, in dependence upon the participation of the user. The website may be configured to be a social networking website.

The website may comprise a social networking area, and access to the social networking area by a user may be dependent on the user status data for the user. The system may further comprise means for amending the loyalty data for a user in dependence upon the user's usage of the social networking area.

The user access device may be useable as a payment device, and the system may further comprise means for receiving payments from a user, means for storing payment credit data for a user representative of credit available to the user for payment using the payment device, and at least one payment terminal for reading the identifier from the access device and debiting the payment credit data associated with the identifier by a payment amount.

In another independent aspect of the invention there is provided a method of controlling access to an event, comprising:-obtaining information concerning a user, associating the user information with at least one of a user identifier and a device identifier, and storing the user information in a data store; reading at least one of the user identifier and the device identifier from a user access device, and obtaining the associated user information from the data store in dependence upon user identifier or device identifier read from the user access device; and controlling access in dependence on the user information.

The method may comprise displaying the user information, for example to an operator.

The method may further comprise transmitting user information and identifiers to a local server; storing the user information and the identifiers at the local server; transmitting a request for user information from access control apparatus to the local server in response to reading of the identifier from a user access device; and transmitting user information to the access control apparatus in response to the request. The method may further comprise transmitting the user information and identifiers to the local server from a remote server.

: ," The method may comprise selecting user information and identifiers for users who have *...

authorisation to access an event, and the transmitting of user information and identifiers to the local server may comprise transmitting the selected user information and identifiers to the * m * 3W * local server. ** * I....

* The method may further comprise monitoring identifiers that have been read, maintain a record of user access to the event, and transmitting the record of user access to the event to the remote server.

The method may further comprise storing authorisation data representing authorisation to access the event and associating the authorisation data with the device identifier and/or the user identifier. The user information may comprise the authorisation data.

The method may comprise transferring authorisation to access an event from one user to another user by modifying the authorisation data associated with each user.

The method may further comprise grouping users into user groups, and providing transfer of authorisation between users in dependence on whether the users are in the same user group.

The method may comprise enabling a user to select at least one other user to be in their user group.

The method may comprise receiving user requests to access the event, maintaining a waiting list of user requests to access the event, and transferring authorisation to a user and/or device identifier associated with a user having a user request in the waiting list.

The method may comprise storing user records, each user record comprising an identifier included in a respective user access device and respective user information. Each user record may comprise respective user status data.

The method may comprise allowing or disallowing a transfer of authorisation from one user :. to another user in dependence upon the status of one or both of the users, represented by ** the user status data for the users. *...

: .. The method may comprise receiving a user request to obtain authorisation to access an event, and determining whether or not to provide authorisation in dependence upon the user status data for the user. The user status data may comprise loyalty data.

* * ..

* .5W * ** I The method may further comprise providing a website and associated processing system, wherein the website comprises means for receiving a user request to obtain authorisation to access an event.

The website may comprise a social networking area, and access to the social networking area by a user may be dependent on the user status data for the user.

The method may comprise amending the loyalty data for a user in dependence upon the user's usage of the social networking area.

The method may further comprise receiving payments from a user, storing payment credit data for a user representative of credit available to the user for payment, and associating the payment credit data with a user identifier and/or device identifier.

The method may further comprise reading a user identifier and/or a device identifier from a user access device, obtaining payment credit data for a user associated with the user identifier and/or device identifier, and debiting the payment credit data associated with the identifier by a payment amount.

In a further independent aspect there is provided a method of controlling access, comprising:-providing a user access device having a unique device identifier to a user; obtaining user information concerning a user, and associating the user information with the device identifier; reading the device identifier from the access device, and obtaining the associated user information in dependence upon the device identifier; and displaying the user information.

In another, independent aspect of the invention there is provided a method of controlling access, comprising:-providing an access device comprising rfid circuitry to a user, the access device inc'uding an identifier; obtaining information concerning a user and associating the user information with the identifier; reading the identifier and obtaining the associated user information in dependence upon the identifier; and displaying the user information.

: , In a further independent aspect of the invention there is provided a method of controlling S...

access:-storing a plurality of device or user identifiers, each identifier identifying a respective user access device or user; associating authorisation data with at least one of the identifiers, the authorisation data representing access authorisation; and subsequently transferring authorisation from one user access device or user to another user access device or user, optionally by altering the authorisation data.

Any feature in one aspect of the invention may be applied to other aspects of the invention, in any appropriate combination. In particular, apparatus or system features may be applied to method features and vice versa.

Embodiments of the invention will now be described, by way of example only, with reference to the following figures:-Figure 1, which is a schematic diagram of a user access system; Figure 2, which is a schematic diagram showing a server included in the user access system of Figure 1 in more detail; Figure 3 is a schematic diagram of a user access system according to an alternative embodiment; Figure 4 is a schematic diagram illustrating the format of a home page of a web site of the systems of Figures 1 and 3; Figure 5 is a screen shot showing a sample order confirmation page; Figure 6 is a flow chart illustrating in overview the allocation of admissions personnel to an event; Figure 7 is a flow chart illustrating in overview set-up processes for the system prior to admission of users to an event; Figure 8 is a flow chart illustrating in overview a member search process; Figure 9 is a flowchart illustrating in overview processes performed by an administrator in sending out wristbands; Figure 10 is a flowchart illustrating in overview a quality control process; Figure 11 is a flowchart illustrating the various statuses that a wristband may have; Figure 12 is a flowchart illustrating in overview access control processes performed by an rfid reader device and operator terminal; Figure 13 is an illustration of a sequence of screens displayed on the website to enable an administrator to approve or reject photographs; and Figure 14 is a list of different categories of discussion forum provided on the website.

: s. A user access system is shown in overview in Figure 1. A user access device in the form or S...

a wristband or other token 2 including an embedded rfid chip is provided to each user 4.

Each rfid chip has a unique identifier. The system is configured to control access of a large number of users to an event, but a single user is shown in Figure 1 for clarity. a

*sss.e * In the embodiment of Figure 1 each wristband 2 comprises a stretch portion and a protective portion. The wristband 2 is suitable for wearing on, for example, a user's wrist and has a circumference of approximately 200mm, a width of approximately 15mm and a thickness of approximately 3.5mm. The protective portion has a length of approximately 30mm and consequently the stretch portion has a length of approximately 170mm when in a natural non-stretched state. The stretch portion and the protective portion are both formed of silicone rubber in the illustrated embodiment, but other materials can be used in alternative embodiments. However, the compositions of the materials used to form the stretch portion and the protective portion are different. The stretch portion is formed of a composition that when set will stretch analogous to a standard silicone wristband. The protective portion is formed of a silicone composition that when set does not readily stretch or deform. The two portions are fused together during the manufacture process and are formed to have the same width and thickness. An RFID tag including its antenna is encased inside the protective portion during the manufacture process. The RFID is communicable with RFID readers outside of the wristband. In the embodiment of Figure 1, the RFID tag is formed according to ISO 14443 A, however other kinds of REID tags may be used.

An rfid reader device 6, in communication with an operator (or self service) terminal 8 is provided at the entrance to the event. The reader device 6 is able to read the identifier from the rfid chip and to transmit the identifier to the operator terminal 8.

The operator terminal 8 is in communication with a control centre 10. The control centre comprises a control processor 12, linked to a database 14, and configured to generate a website 16. The control centre software is written using Django/Python in the embodiment of Figure 1.

In the embodiment of Figure 1, the operator terminal 8 is a Psion Workabout Pro, programmed with access control software written in C Sharp for implementing the access control and communication processes. The rfid reader device 6 comprises rfid reader technology included in the Psion Workabout Pro, or is a separate rfid reader device that is in wired or wireless communication with the Psion Workabout Pro or other operator terminal 8.

*, In advance of the event the user 4 registers on the website 16, and the wristband 2 is sent to the user 4. The user 4 also submits a photograph of themselves and other personal information, which is stored together with a user identifier as a record in the database 14.

The rfid identifier for the wristband 2 supplied to the user is also stored in the record for that The user, once registered, may purchase access to events via the website 16. If the user 4 purchases access to an event then the record for the user 4 is updated to include an access authorisation for that event. The website includes a homepage for each user, in which they can view their history of access authorisation and other purchases, view a schedule of forthcoming events for which they have purchased access authorisations or which may be of interest, and view other promotional material. The promotional material provided on a user's homepage is usually tailored for that user, based for example on previous purchases or demographic information.

At the entrance to the event, the user's wristband 2 is read by the rfid reader device 6, associated with the operator terminal 8. The operator terminal 8 transmits the rfid identifier read to the processor 12 at the control centre 10, and in response the processor 12 obtains from the database 14 user information in the form of data representing the user's photograph and authorisation data and a PIN from the user record corresponding to that identifier, and transmits the data to the operator terminal 8. An image of the user is displayed on the terminal 8 and the image is compared by the operator to the appearance of the user 4 who has presented the wristband 2. If the user's appearance matches the displayed image and, in this example, the user successfully enters the PIN the user is allowed access to the event. The data that is sent from the database, and the checks that are performed before allowing access vary depending on the requirements of an event or situation. For example, a user may not be required to enter a PIN. In another example, an event organiser can decide to operate the system allow entry if the authorisation data associated with the rfid identifier indicates that the corresponding user has authorisation to enter the event, without checking whether the person in possession of the wristband is the registered user.

A record of user access to the event is maintained by the processor 12 in the database 14.

Access data representative of device and/or user identifiers in respect of each user who is allowed (or refused) access to an event is sent by the operator terminal 8 to the processor 12 *.., and is stored in the database 14. * **

A user is able to leave and re-enter an event. The leaving of an event by a user can be ,* monitored by reading of the rfid identifier by the operator terminal 8. Usually, there is no I...

check of user information upon leaving, but the usual access procedure is repeated when the user comes to re-enter. Data concerning user departures and re-entries can also be stored *F: in the database 14. Therefore, a record of the number of people present in a venue can be *....: maintained, and can be used, for example, for safety monitoring purposes. * I

The system allows a user to transfer authorisation to access an event to another user. The conditions according to which transfer of authorisation occurs usually depend on the number of authorisations that have been issued to an event and the status of the user.

In one mode of operation, a user may be allowed to transfer authorisation to access an event only to one of a group of other users who he has identified as friends, unless the event is oversubscribed. Usually no payment is refunded by the system to the originally authorised user or demanded from the newly authorised user by the system. Instead the users, having the status of mutual friends, arrange themselves for payment, if any, in respect of the transfer of authorisation. In a variant of that mode of operation, the system also manages payment in respect of the transfer of authorisation.

If the event is oversubscribed the authorisation may be transferred instead to a user on a waiting list. In that situation the processor 12 maintains the waiting list, determines the user on the waiting list to whom authorisation should be transferred, arranges for refund of the originally authorised user and arranges for charging of the newly authorised user.

The transfer of authorisation is usually performed by amending the respective authorisation data stored in the database for each of the users.

Each user record also includes user status data. In one mode of operation, different statuses are available to users, and the functionality available to a member is dependent on the user's status.

For example, a user with full member status is authorised to obtain a wristband and is able to use all of the functionality of the system, for example the ability to purchase authorisations (also referred to as tickets) to attend events, to join or establish user groups, to join waiting lists for oversubscribed events, to transfer authorisation to attend events to other users, to 5r: participate in a loyalty scheme, and to have their own home page on the website. A user may be limited to a certain number of authorisation transfers during a predetermined period : (for example, 10 transfers per year).

A user with partial member status is registered on the system but is not able to purchase authorisations to attend events, or have such authorisations bought for them. However, they I...

: may have a home page on the website. Usually a user with partial member status is :: required to submit more information before they can obtain full member status.

A user with full member status is able to purchase more than one authorisation to attend a particular event and to offer at least some of the purchased authorisations to other users, for example by sending an e-mail invitation to the other users. The other users should have full member status in order to receive a purchased authorisation. If they do not, then they will be invited to register as full members.

The system also provides a loyalty scheme for full members, and each user record includes loyalty data representative of a loyalty score. A full member can increase their loyalty score by, for example, purchasing tickets via the system. Rewards can be provided, in dependence on a user's loyalty score, by providing the user with priority access to forthcoming events, or free or reduced price tickets to events, or free or reduced price merchandise.

The website includes a social networking site, and all full and partial members can participate in the social networking site by posting photographs, comments or messages on the site, for example concerning a past or future event. In one mode of operation, users with full member status can increase their loyalty score by participating in the social networking site. Non-members can view the social networking site but cannot participate until they register as either a full or partial member.

Each wristband may include advertising material, for example a logo or other branding.

In variants of the system, music or other audio visual content relating to events is downloaded or streamed to users who have subscribed. The content may relate to an event to which the user has authorisation to attend or which the user has attended.

In other variants, the processor is configured to implement an auction process for tickets to S...

.S' : an event, and the authorisation data of winning bidders is automatically updated to allow them access to the event. * S*

In other variants the wristband is used as a payment device within an event, for instance to pay for food, drinks or other merchandise. In such variants a user can pre-charge the wristband by making a payment to the system, for instance via a credit card. The user record on the database is credited with the payment amount. Each time a transaction takes :: place within the event the user's record is updated to reduce the reflect the payment that is required for the transaction.

The wristband can be provided as a gift, precharged with a payment amount and/or with access authorisation to a particular event pre-provided. Registration of the recipient of the gift is required before the wristband can be used.

In one mode of operation, a payment terminal is used to read the wristband in order to take payment for a purchase and the payment terminal is configured to request user information corresponding to the wristband identifier, in a similar way to that described for access control.

In some circumstances, the user information can be used to determine whether or not to proceed with a purchase. For example, a user purchase may be refused if the user information indicates that the user is under the age of eighteen or twenty one.

In further variants of the system, the access system is automatic with no operator required, for instance turnstile based, and relies on automatic matching of the user's appearance with the stored image using an image recognition and matching system and/or entry of a PIN into a keypad by the user.

Figure 2 shows the server 12 in more detail. The processor 12 includes various modules for providing different functionalities of the system as described above, including:-a network communication module 20 for communication with the operator terminal 8 via a network; a web site management module 22 for managing display and operation of the website 16; and an authorisation booking module 24 for receiving user requests for access authorisation purchases (for example via the website 16) and for updating user records in the database to reflect successful access authorisation purchases. The authorisation booking module 24 is configured to communicate with a payment authorisation module 26 in order to verify that payment has correctly been received for an access authorisation purchase. The payment authorisation module 26 is also configured to manage the crediting and debiting of payment credit data stored in a user record in response to charging of a user's account or in response 2: to purchases by a user using the wristband 2. In the illustrated embodiment, the payment authorisation module 26 is in communication with a third party payment service 28 (for : example, PayPal) which is used to administer payments.

The processor 12 also includes a data management module 30, which is configured to retrieve user information from the database 14, including authorisation data, in response to receipt of a device identifier and/or event identifier from the operator terminal 8 and to :: provide the retrieved user information to the operator terminal 8 via the network communication module 20. The data management module 30 is also configured to manage data stored in the database 20, and to maintain records of user access to each event. The data management module 30 is also able to provide data from the database upon request, for example to event promoters or a system operator, enabling analysis of event attendance or ticket purchases.

The processor 12 also includes a registration and user administration module 32, which manages the user registration process, and also manages communication with users, for example via e-mail or via automatically generated letters. The registration and user administration module also monitors the distribution of wristbands 2 to users, maintains records of the registration and wristband distribution process, and provides all other administration functions.

In the embodiment of Figure 1, the operator terminal 8 is in communication directly with the processor 12 at the control centre. An alternative embodiment is illustrated in Figure 3. In that embodiment, a local server 40 (for example, in the form of personal computer) is provided at a venue 42 for an event. Several operator terminals 8 are provided, each at one of the entrances to the venue 42. In operation, device identifier data and user information for all users who have access authorisation for an event is downloaded from the server 12 to the local server 40 in advance of the event.

The local server 40 is able to communicate with each of the operator terminals 8 via a local area network (LAN) for example a wireless LAN.

User access to the event is controlled in the same way as described for the embodiment of Figure 1. However, each of the operator terminals transmits the rfid identifiers obtained from the reading of user wristbands 2 to the local server 40 rather than to the server 12. In response, it is the local server 40 rather than the server 12 that provides the user information to the operator terminals 8. :

. The local server 40 maintains user access records representative of users who have succeeded (or failed) to gain access to the event. In some cases the user access records :.::: include records of users leaving and re-entering the venue 42. The user access records may also include time data representative of the time that each user entered (or left) the venue.

The user access records are uploaded to the server 12 for storage in the database 14, either 0s** periodically before and during the event or after the event has finished.

S.....

S

By providing local control of access at the venue 42, the need to communicate with the server 12 during the access control procedure can be avoided. The server 12 is usually remote from the venue 42 and the reliability of network communication between the operator terminals 8 and the server 12 can be lower than the reliability of communication over the LAN. In those circumstances, local control of access at the venue can be more efficient in the embodiment of Figure 3.

It will be understood that extensive data concerning users, events, ticket sales and event attendances can be built up in the database 14. That data can be provided to third parties, for example event promoters, upon request. In some cases a fee is payable to the system operator to obtain such data.

In a variant of the described embodiments, the website 16 can be branded under the brand of a particular event promoter, venue or artist, and/or can be linked to or incorporated within the existing websites of event promoters, venues or artists. Multiple websites 16 can be provided, each branded under the brand of different event promoter, venue or artist.

Although the system uses an rfid chip embedded in a wristband, any other suitable token may be used as the user access device. For instance the chip may be embedded in a card or badge instead of a wristband, or some other readable device may be used instead of an rfid chip. Any readable device having an identifier may be used as the token, and the token may have another primary use. For example, the user's credit or debit card may be used as the token. Other modifications of detail may also be made.

In one, alternative embodiment the user access device is a Mifare card.

In the embodiment described in relation to Figure 1, a device identifier is read from the wristband or other user access device. In alternative embodiments, a user identifier is stored S...

5' : on the user access device, for example during a registration process prior to providing the . user access device to the user, and the user identifier is read from the user access device as

S

well as or instead of the device identifier. * .. * * * S...

Further details concerning one embodiment are provided below, including various details and 3** functional specifications of aspects of the website, the user interaction with the website, interrogation of the token and operation of the system. It will be understood that each of the *.*S.* . . . . . . * * details and specifications below is provided by way of example only and can be varied in alternative embodiments.

The format of a home page of the website 16 in one embodiment is illustrated in overview in Figure 4. The content of the different areas of the home page is as follows:-The main menu area 50 highlights the area the user is in e.g a Gigs area. The main menue area 50 also provides a navigation bar that provides links to other pages of the website 16 as follows, from left to right:-Home I Gigs / Waitlists / People I The Vault / Forums I About. The main menu area 50 also provides a search function underneath the main menu for to provide searches for artists / venues / people.

A promotional area 52 displays the following text:-o We provide a ticket service for music events based on fairness and aimed at those music fans who go regularly to music events.

o We connect music fans with each other and let each of you share their experiences at gigs, or share opinions on artists, music or anything related to the industry o We connect artists with their fans by providing lots of up to the minute information including new releases, tour updates, professionally written reviews and loads of other interesting stuff The website 16 provides discussion forums, and the area 54 provides a list of the ten most recently added discussion forum posts, with the following data: * Forum Name * Member Name * Topic Title * first 30 characters of the post * S * S. S S...

The website 16 also provides live chat rooms and the area 56 provides a list of the ten most * ,* recently added live chat room (Live Room) submissions, with the following data: * Artist name * Venue + Town * Date * * Member name *5*SS*

S S

The footer area 58 provides linkes to an FAQ page, a Terms of Use and Policies page and a Contact Us page.

The home page also includes a logo 60, a featured artist area 62 containing information and links relating to a featured artist, and a listings area 64 that lists events for which tickets may be purchased and, in some cases, content that may be accessed.

Each of the listings area 64 and the featured artist area 62 includes links to ticket purchase pages that allow the user to purchase tickets. The ticket purchase pages can also be accessed via the main menu area 50.

The process of buying tickets for events using the embodiment is now described in more detail.

Only fully registered members with approved photographs can buy tickets. That information features prominently on all communications with partially registered members.

When a member attempts to buy tickets, or tickets are bought for them, that member must have a currently active wristband, or a wristband that is pending activation (i.e. sent out but not yet activated), If this is not the case, then a fee for a new wristband will be incurred and a new one sent to their correspondence address.

There are seven stages to the buying process via the website 16: 1. Selectagig 2. Decide who is going to the gig 3. Decide what tickets to allocate to each attendee 4. Review the basket, see summary of tickets purchased and monies due : 5. Pay for the tickets 6. Order confirmation : 7. Send out email to all going to the gig a...

Stages 2 to 6 inclusive are represented on the website by web pages corresponding to each of the stages in the process. Stage 1 begins the process. The final stage, stage 7 involves * the sending of confirmations to users and is a behind the scenes process.

S.....

The system allows an administrator to define the following parameters: * Fee for first purchase of a wristband * Replacement fee for a wristband * Postage and packaging fee for a wristband (new or replacement) These fees are then applied to each wristband which is issued.

Stage 1 When a member selects buy ticket' for an event, then navigation is straight to the Stage 2 web page. In terms of design, the artist, date and venue are displayed prominently above the navigation bar of pages corresponding to all the remaining stages Stage 2 Called "Tell us who is going" (the gig has already been chosen) The main purpose of this stage is to decide who is going, there is no other data capture required at this point, the number of tickets to be bought should be derived from the user in deciding who is going.

Design guide: the logged in member has a separate icon and tick box, which is easy to find, All remaining friends are listed, for example using an alphabetical navigation model. A checkbox is used to decide who is going to the gig.

A different icon is used for friends already going to the gig and for friends who are not fully registered. Friends that can go who have a wristband are differentiated from those who don't.

The following text is provided on a panel on the stage 2 web page:-* ..* * S * Buying Guide You are about to buy tickets fort an event. Before proceeding * ** select this checkbox to let us know you have read our Buying Policy. Have an empty check box for positive affirmation.

You are limited to X number of tickets for this event.

Pick which if your friends you want to invite to the gig and then *5SS move onto the next stage to pick the types of tickets you want * to buy.

* If you pick a friend who doesn't already have a wristband, then you will need to The following selectable buttons are provided-Next Go to stage 3 Cancel Go back to select an event. Go to the artists event page from where the event was selected Stage 3 Called "Choose Ticket Types" All the friends who are going, selected during stage two, are listed with a drop down beside them. The drop down provides a list showing the ticket type and price. Ticket types should be chosen for all members going to the gig before proceeding. There should be no default ticket type on form entry, so the user is forced to choose explicitly. Each time a user modifies the ticket types, the order is updated to give a total amount due, excluding credit card fees, for the ticket purchase.

A dynamically calculated order cost is included on this page to include tickets and any required wristbands.

A delete button is provided, which the user can use to exclude a member from coming.

The following text is provided in a panel on the stage 3 web page:-Buying Guide Some events have different tickets available for sale. Beside each of the people going to the gig, use the drop down to select a ticket type. You can choose different tickets types if * *** : you are buying for more than one member.

* When you have decided which tickets you want to buy, click the "check availability" button to see if the tickets you have asked for are available. If we have availability, then you can continue to review your order by clicking on the Next button.

From that point you will have ten minutes to conclude the order * before your order expires.

S.....

* * If we don't have any tickets left, then you can ask to go our waiting list for the event. We will only waitlist you and not your friends, so ask them all to joint the waitlist too.

The following buttons are provided on the stage three web page:-Check Check ticket availability. If the order requested is ok Availability then return a positive message "we have the tickets you have asked for" and then enable the Next button.

If a positive result is returned, block out the tickets and start the timer. The timer should then appear on this page and every other subsequent page until payment is accepted.

If there is no availability, then return a message "we are sorry, but the tickets you have asked for are not available" Next Initially disabled. Should only be enabled when the check availability button has returned a result which agrees with the members requested order.

Back Go back to reselect tickets. If an order has been blocked out (i.e. "Check Availability" has returned a positive result), unblock the tickets and tell the member. "We are now unblocking the tickets you have asked for, are you sure you want to continue?" Cancel ask for confirmation and then navigate back to the page from where Stage One was begun, probably the artist page Stage 4 Called "Payment" S...

: The page requests payment card details. Only fields which are relevant for a *...

particular selected card type are presented. Pre-populate with last used card data if * ** available. (only show last 4-5 digits of card) , plus valid to date, plus issue number, plus card type.

*:::: A card can only be used by one member S.....

* A total amount for the bill as per the calculation at stage 3 is displayed. The page can be pre-populated with any saved card data.

The following text is displayed:-"Total charged to your card is �XX.XX (excluding card processing fee)" A timer is provided on the page, which is updated on entry.

The following buttons are provided on the stage 4 web page:-Continue Validate Card and move to next stage if valid.

Otherwise popup error message saying "this is not a valid card" Update the timer.

Back Go back to reselect tickets, Stage 2. Put up a confirmation dialog box: "We are now unblocking the tickets you have asked for, are you sure you want to continue?" The following text is displayed on the stage 4 web page:-Buying Guide You can now provide us with your payment card detail. Click Continue to move to the final stage to review your final order. Only then will we take payment You can use the Back button to go back to change who is going to the gig. Clicking Back unblocks the tickets we have blocked during this process, so you risk the chance of losing the tickets if this is a high-demand event.

Stage 5 S... * S * * .

Called "Place Order" S...

This stage presents a summary of the purchase order as follows, for example:-Artist Name Date Venue Item Friends Quantity Price Service Total s. Charge per ticket Wristband Dave, 2 1.50 N/A 3.00 Steve Ticket Type You, Dave 2 �10.00 �2.00 �24.00 TicketType Steve, 3 �15.00 �2.00 �51.00 Mary,Joe I _____ Subtotal �78.00 VAT@17.5% �13.65 Total Including VAT �88.13 (SecureTrading + Bank charge) Card Processing Fee �1.38 Total �89.51 The following data are included on the same page: Billing Address: Payment Method: Title Fname Sname Card type: *)()Q()( Address Line 1 Expiry Date: mm/yy Address Line 2 Issue Number (for Maestro) Glasgow Amount �XX.XX Lanarkshire BTN: change payment method (which G12 OXE goes back a page)

UNITED KINGDOM

Email address The following text is provided on the stage 5 web page:-Buying Guide This is the summary of your order. We have quoted you the price you will pay, including a payment processing fee for your card. If you : want to change the tickets you are buying, use the Back button. * **.

S's... What fees are charged? * *. . We apply a service fee for each ticket purchased, this is shown in your order summary and can vary for different events. This service fee covers the ongoing costs of providing *:::: your wristband, the secure ticket service and the moderated web content on the website, VAT is payable on your tickets *..S.* * attherateofl7.5% * We also charge a payment processing fee of the value of your total transaction including VAT. This is to cover fees imposed on us for accepting your card payment over the internet.

The following button is provided on the stage 5 web page:-Place Order Take payment. If successful move to stage 6, II unsuccessful, display "your payment has not been successful, please check your card details from the <un Payment> page Stage 6 The stage 6 web page is also called the "Confirmation" web page The following text is displayed on the stage 6 web page:-

PRINT THIS PAGE FOR YOUR RECORDS

Thank you for your order (Header format) You will receive a confirmation email, as will any of your friends for whom you bought tickets, You will also see a record of this purchase on your website login page.

Please contact us if you have any problems with this order on <url to contact page> You have purchased tickets for <Artist Name> at <Venue Name + City> on <date>.

Doors open at <time of opening> Billing Address: Payment Method: Title Fname Sname Card type: *))( Address Line 1 Expiry Date: mm/yy : Address Line 2 Issue Number (for Maestro) Glasgow Amount �XX.XX Lanarkshire ::::. G12OXE

UNITED KINGDOM

Email address I. Peoplegoingtothegig: S.....

* Title Fname Sname (username) Ticket Type (repeat for each person on the list) A sample order confirmation page is shown in Figure 5.

Stage 7 Send emails out as follows: * Email to the Buyer * Email to the friend being purchased for Moving on from the ticket purchase process, the website 16 can also be used by an administrator or operator to create a venue record on the system. Administrators or operators are able to access web pages of the website 16 that provide administration functions if they have appropriate permissions.

The following data are captured when creating a venue: * Venue Name * Contact Address, PAF'd * Capacity * Communications facility: broadband (YIN), bandwidth (512Kb, 1Mb, 2Mb, 8Mb) * Maximum Number of entry points -should be the same as the number of handhelds, although there could be some chance of doubling up * Where a venue has multiple stages or performance locations capture for each: * Stage Name * Capacity * Promoter: First name, Surname, cell phone, desk phone, email address, correspondence address PAF'd. S...

Auto-create user logins for the event based on the number of entry points. Random alphanumeric passwords are created for each login. These passwords are changed for every : ** gig. These users names will be associated to door entry personnel at the time the gig is *...

being set up 3Q'. The system also enable admissions staff to be registered on the system. For example, all : security personal on doors will be registered on the system. Each venue will have a number of user names and corresponding passwords. These will be distributed to the different security personnel, after being associated on the system.

A data record for a member of the admissions staff is as follows:-

Field Mandatory!

Optional First Name M Surname M Gender M

DOB M

Residential Address (PAF'd) M Contact Phone Number M Email Address M Employer (could be linked if M held relationally) The system also provides for asset management services in relation to operator terminals 8, reader devices 6 and other equipment.

For example, when a new operator terminal 8 or reader device 6 is procured to use at an event, it is commissioned and asset tracked on the server 12. This wHl involve registering device-unique information with the server 12. Data to be registered includes: * Wireless and/or Ethernet MAC address * Make * Model * Operating System, version * Date/time registered * Price(exandincVAT) * Listofaddons : .. o Device Name a..

o Description

o Manufacturer * . * . o Price (ex and inc VAT) * Status: set to Available' on first registration When a device (for example an operator terminal 8 or reader device 6) is first entered on the system, it will be set to a status of available. The application should allow a user to subsequently change the status of the device to: * Allocated -allocated to a specific event * Available -either on first commissioning, or after it has been used at an event. All available devices should physically be returned to us * Out of service -when a device dies and is not to be fixed * Lost -device has been misplaced (take a description of events leading up to loss) * lnforRepair The server 12 includes an application that provides a process to allocate admissions personnel to an event. This process associates venue logins to the Admissions Personnel responsible for handling admissions. The process is illustrated in overview in the flow chart of Figure 6.

The server 12 also provides an asset management application. Each device has an auditable history of events at which it has been used at and some data on the activity at that event. Typical reports provided by the application include: Event history report * event name * date * location * promoter Device Audit Report * username(s) logged in * unsuccessful logins and device lock out * number of successfully authorised members * number of referrals ordered by referral reason *..

Inventory Report * list of devices in sort-able order, with age in weeks * devices allocated and who they are allocated to: even/promoter/door entry person * devices available * cash spent Turning now to operation of the system during an event, the high-level processes that are performed for an event so that admissions can begin are illustrated in the flow chart of Figure 7.

Turning to functions provided by the system during an event, the system provides an application for use by admissions staff to deal with members in the event of their failing to gain admission via presentation of a valid wristband for identification at the venue. The application is implemented as software installed at the operator terminal 8, or as software installed at a PC at the venue, or as software implemented at the server 12 and accessible remotely from a PC at the venue (for example, via the web site 16). The following functions are provided by the application: * Login * Search for a member based on data * Search for a member based upon wristband * Start the admissions for an event * Manage the following scenarios: o Member forgotten wristband o Member not received wristband o Member wristband not being read properly by admissions personnel o Person not a member but wants to attend the gig o Member refused entry by admissions personnel because photo is not accurate o Member refused entry because they didn't/couldn't provide their PIN when asked by admissions personnel o Member refused entry because the admissions personnel can't see a valid ticket on the system, but member insists they have paid for one, or had one bought for them * Reports on sales for the event Further details and comments concerning the functions provided by the application are listed in thefollowing table.

Login A venue-user' aka promoter will be someone at the venue with access to a PC with a browser. After logging in, a venue user will be offered different functions Navigation After login there should be a number of functions available to the venue.

Select a Gig This should bring up a list (oldest last) of events on the system for the promoter's venue Member Search The object of this function is to bring back as much information as possible about the member so that the user can answer the query quickly.

The member search page should present search criteria, or ask the user to swipe a wristband The member search process is illustrated in the flow chart of Figure 8.

The member search process is provided on a single web page or spread over three web pages.

The potential Search Criteria are: 1. Email address 2. Login name 3. Postcode and house name or house number 4. Member reference number (encrypted on the wristband) The lost of possible matching headers is as followed: 1. Surname, Forename *,SS : 2. Data of Birth 3. Email Address 4. Concatenated Address ) S. * S S S...

The information provided in the full profile is as follows: 1. Title, Surname, Forename *SSS * S. * 2. Nickname

S *.*.*

* 3. Login name 4. Billing and Correspondence addresses (both if available) 5. Member status, one of: a. Partial Member b. Full Member, photo not approved c. Full Member, photo approved d. Full Member, Wristband ordered e. Full Member, wristband packed f. Full Member, wristband activated g. Full Member, suspended 6. All financial transactions made by this member. For each transaction list the following: a. Date b. Amount c. Card used, last 5 digits d. Name on card e. Invoice list: i. Member surname, forename, ticket type and cost ii. Wristband and member intended for 1. Total levied against the card g. Event the transaction is for -Artist/Venue/DateTime 7. All financial transactions made by members which have included a purchase for this member a. Date b. Amount c. Card used, last 5 digits d. Name on card e. Invoice list: Member surname, forename, ticket type and cost ii, Wristband and member intended for f. Totallevied against the card g. Event the transaction is for -ArtistNenue/DateTime : . Manage Referral Once a member has been searched for and found, there are a number S...

of functions which are needed, these should be offered in a drop down, or some other selection box, to allow the member's query to be : handled. Each then has its own process:

S

S... S

S S

Member forgotten wristband View the wristband status. If the member has an Active Wristband, then prompt the user to Ask for debit card/credit card or driver's licence". If the identify of the member corresponds with the member record, then record the fact the user is to be admitted and issue them with a temporary wristband. Also record which type of ID was presented -Debit Card/Credit Card/Drivers Licence Return to the member search screen after issue the wristband.

2. Member not received wristband View the wristband status. If the member has an Active Wristband, then prompt the user to "Ask for debit card/credit card or driver's licence". If the identify of the member corresponds with the member record, then record the fact the user is to be admitted and issue them with a temporary wristband. Also record which type of ID was presented -Debit Card/Credit Card/Drivers Licence Return to the member search screen after issue the wristband.

3. Member wristband not being read properly by admissions personnel The desk bound promoter should perform a member search as above, but with the wristband. If there is a match and member data is brought back, ask the member for a debit/credit/drivers card. If the data is the same, then ask the member to revisit the entry queue. If wristband doesn't work, let them keep it, I...

deactivate current on system and issue with a new one (for free) * ** * * * **** 4. Person not a member but wants to attend the gig For initial gigs, we have an arrangement with the promoter about : walk ups. However for future gigs we provide the ability for the person to go through the registration process, and for a webcam to be used to take a picture and then for a person to have a wristband swiped and presented to them on the spot.

5. Member refused entry by admissions personnel because photo is not accurate.

Desk bound promoter will search for the member profile by swiping the wristband. The photograph will be viewed and the member asked for a debit/credit/drivers card. The promoter has the right to decline or accept the entry based upon the outcome.

Record which of the options is taken:' * No proof of identity. Wristband retained, member declined entry * Identify confirmed, member granted permission to enter, but their membership status is downgraded to "full registration, photo declined". The member can then attempt to provide a new photograph on next login, but cannot buy tickets for events until that photo is approved.

6. Member refused entry because they didn't provide the correct PIN when asked by admissions personnel. 3 attempts were made and the member was locked out of the event.

Deskbound promoter will search for the member by swiping their wristband. The member will be asked for a debit card/credit card/drivers licence. If the member has a ticket, and the data on the system, the photo and the debit card all agreed, then the member will be given a temporary PIN of 1234 and asked to re-*.a.

: enter, and then they have to change it on re-entry. * * ****

If the member proof of identity and photo and profile don't agree, then decline entry.

7. Member refused entry because the admissions personnel did not * S..

: pick up a valid ticket for the member, for the event they are trying to access.

Desk bound promoter searches for and views: * Email sent for confirmation Purchase transactions involving this member for this gig Secure Trading transaction Promoter uses discretion to let the member in or not.

Wristbands may be sent out to users by the system administration or by a third party (also referred to as a wristband fulfilment entity or fulfiller. The system provides a software application which allows a system administrator or fulfiller to login, swipe wristbands and associate them with welcome letters sent to registering members. This application also allow them to print off the list of people who need wristbands fulfilled.

A Quality Control process is used to ensure the envelopes are packed with the correct details, and that the wristband operates before being sent out.

At the beginning of a working shift the fulfiller runs off a report of those members needing wristbands fulfilled, this can be sorted by date and by New/Replacement. This report contains the following data in an excel spreadsheet:- 1. First name 2. Second Name 3. Correspondence Address Line 1 4. Correspondence Address Line 2 : .. 5. Correspondence Address City/Town I...

6. Correspondence Address Postcode 7. Activation Code *: 8. Date/Time of wristband order 9. New or Replacement Flag (will define which letter is sent to the member) This report should be drawn from the live database 14. The date/time is included to let the fulfiller sort data in advance of pick and pack, but will not be used on the actual welcome letter. Fulfilment users are setup on the database and be provided with a login with username and password.

The process performed by the fulfiller or administrator in sending out wristbands is illustrated in overview in the flow chart of Figure 9. The following actions are performed:- 1. The fulfiller will take the current fulfilment report and sort by date/time, it is important that wristbands are fulfilled oldest first. The remaining process deal with multiple fulfilment people picking and packing.

2. The fulfilment manager prints out the mail-merged letters and mailing labels and distributes them in batches -new and replacement letters done separately 3. The fulfilment manager allocates batches, separating new and replacement letters, within the current report to individual fulfillers for pick and pack.

4. Each fulfiller then sits with their pile of letters and mailing labels, each pile synchronised with the other.

5. The fulfiller logs into the fulfilment application and provides three items of data a. the starting Activation Code for their batch b. the number of letters in their batch c. New or Replacement From this point on they will be served with individual fulfilment records in date order, oldest first. In this way each fulfilment person will receive only those records which correspond to the letters and labels within their personal batch.

6. Repeat until the batch is finished: a. Retrieve member record from live database. Data to be fetched back is: * * * * i. First name S. * ii. Second Name *** iii. Correspondence Address Line 1 : iv. Correspondence Address Line 2 v. Correspondence Address City/Town vi. Correspondence Address Postcode **.

vii. Activation Code viii. Date/Time of wristband order b. Check onscreen member record is the same as the mailing label and the letter and check activation code is the same on screen as on the welcome letter.

c. If they are not the same, put the mailing label and letter to the side and click a "Refer" button on the customer record. This should bring back the next record in the batch, or if none left, sent a message to the fulfiller: "No records left in your batch" d. If all the data is the same on screen as on welcome letter and mailing label, pick a wristband and swipe. Store the Member ID, encrypted against a private key on the wristband. This means there will be two reference numbers on the wristband, one of the original RFID chip and the second of the keyed Member.

If this process works ok, send a message to user "RFID tag allocated to member". Write a status of packed' to the member's wristband application e. The fulfiller then packs the welcome letter and wristband in a blank envelope and then sticks the mailing label on the envelope. The envelope is placed in the outbox, or Quality Control tray.

f. The fulfiller then clicks "Next" on the screen and is served with the next record in their batch directly from the live database, if there is one. If none available then present a "No records left in your batch" message.

Once the wristbands have been packed, they are subject to a quality control process. A quality controller carries out the following actions in order to check each packed wristband against the member record:- 1. QC Fulfiller logs into the application 2. Repeat the following: a. They are presented with a screen which says "Swipe wristband to bring back member record" b. If the application brings back the member record then check the member data, **:*. welcome letter, and mailing label all agree. If everything is fine, click a "Quality Control Check Passed". Write a "Quality Control Check Passed" flag to the member's wristband application record. * A

* Ju S **..

If the member record is not pulled back, or if when it does it doesn't agree with the envelope and the letter contents, then click "Referred at Quality Control * S..

: Check" and place the letter with its contents into a referrals bin *S.S*S c. Click Next to go back to step a), or logout The quality control process is illustrated in overview in the flowchart of Figure 10. A further flowchart is provided in Figure 11 which illustrates the various status states that a wristband may have.

As mentioned above, the data stored in the database 14 can be provided to various third parties. The server 12 includes a reporting application that enables a user to obtain various reports based on data in the database 14.

For example, a tour report can be provided by the reporting application. The user provides a tour name, from a drop down and is give: * Numberofevents * Number of events sold out * Tickets sold * Tickets sold this week * Historical tickets sold by week * Percentage tickets sold * Total Tickets (sum of all capacities) An event report can also be provided by the reporting application. The user provides a specific event, either by coming in from a tour, or choosing from a list of all events, and is given a report on: * Date * Venue * date on sale * days to event * capacity S...

* production hold : ** * guests hold S...

* pre-sale allocation e pre-sale sold *:::: * full public sale * salesthisweek * sales history by week * total sales * %sold As mentioned above, the system provides the ability for a user to sell tickets or to transfer tickets to friends. Those functions are provided by a marketplace area on the website 16.

The marketplace provides a convenience service to be used by members when tickets have been purchased but are no longer desired. It is not there to allow members, or the administrator for that matter, to market and sell tickets for a higher than face value' price.

The Marketplace is accessible from the main site home page, but only full members, who 0 have registered all details and had their photograph approved, will be able/entitled to apply for tickets on a wait list.

General principles 1. The Marketplace is a collection of waitlists'. A waitlist is a queue of member requests for tickets for events for which there is currently no ticket availability. The queue is first in first out'.

(if loyalty points are used, the position in the queue may not be FIFO because it may be weighted based on loyalty value of the member, which opens up the possibility of a user buying their way into a queue with points) 2. When an event is sold out, a new waitlist should be created for that event and should appear on the marketplace. Initially the waitlist will be empty.

3. If an event is not sold out and a member wants to return his ticket, he/she can only give that ticket to one of his friends. The system does not provide a cash return to the member, but in this way the member has a chance to getting his cash back from the friend. The opportunity to transfer a ticket to a friend is referred to herein as a tickle.

A member has 4 tickles per year, timed from the anniversary of them becoming fully *: registered members (photograph approved). Each donation to a member, uses up one tickle. Once the tickles are used up, the member can only submit tickets for sale when a venue is sold out and into the waitlist for general distribution. * **

4. If an event is sold out and a member wishes to return their ticket, this can be done in two ways: a. Use up an available tickle to give the ticket to a friend, or * : b. Offer the ticket up to a waitlist. When we find another member to buy the ticket, a will a refund be made less a transfer fee. The buying member will pay the same price for the ticket as the selling member did in the first place, the ticket price does not change 5. A member can only allocate tickets to a friend if the receiving member is fully registered, with an approved photograph.

6. A member can only make a waitlist request through the Marketplace and by accessing the event's waitlist, this applies to buyers or sellers.

7. A member can only be waitlisted for one ticket per event, and that ticket must be for themselves, although they may pass it on based on rules 3 and 4.

8. A member can only have one waitlist request for any waitlist queue, but may have more than one across multiple queues.

9. Each sold out event can have its own waitlist. This means that a band on tour could have a waitlist for each gig, potentially at the same venue (but on different dates) 10. When a member purchases the last tickets available for an event, they will only be able to purchase those tickets which are remaining, and that request will not spill over' into a waitlist. If that member wants more tickets than are available, they must make a new waitlist request 11. The maximum number of tickets which can be bought by a member can be configured on an event-by-event basis. Members who then buy tickets will be restricted to buying no more than that limit.

12. Selling tickets shall have no effect on the maximum number of tickets a member can buy for an event. So, if an event has a maximum of 4 tickets, and a member buys 4, then sells his own, then the member cannot buy another one.

13. Events which are not sold out should not appear on the marketplace, only events which are sold should be there, and advertised through their waitlist 14. Every member who applies for a waitlist will have a waittist entry. When the member logs in to the site, their home page will have a section which shows the different waitlists they are on. This applies to buying and selling.

15. If a member buys a ticket from a waitlist then: a. Make sure the waitlist entry is changed from waiting' to purchased' b. Add a new ticket to the members future gigs section 16. Because a member can only have one ticket for an event, they can only return one * ** * 3u * ticket for an event. ****

17. Returning a ticket which was part of a group purchase will not cause the other tickets to be returned. * ***

: 18. The number of requests on a waitlist should not be presented as public data and should only be known to us 19. A member can cancel their waitlist request at any time -note that waitlist entries which are fulfilled should be removed from the waitlist. Members should see the waitlist entries on their home page, they should be able to cancel their request from their homepage.

20. When a member is allocated tickets from a waitlist, send an email and SMS to their mobile phone informing them of the purchase. If the purchase is not processed because of payment failure, their waitlist request will be cancelled and removed, with the member being sent an email notification describing the problem.

21. A ticket for an event has only one price. That price will be the same no matter how many times the ticket is sold then repurchased on waitlists. The price is made up of the promoter fee and a booking fee. The promoter fee is passed to the promoter and the booking fee is retained by the system operator 22. There is no system-imposed limit to the number of times a ticket can be bought and sold on a waitlist, although suspicious activity for tickets sold 3 or more times should be logged and alerted to admin.

The marketplace appears the same to all internet users, with specific functions enabled depending on whether the user is logged in or not logged in. There are further differences in function for members who are logged in, depending on whether or not they are fully or partially registered.

The marketplace home page is accessible from the home page and from the members home page, as a minimum.

The main market place web page includes various panels, and the panels display the text and content listed in the following table:-Left Panel Welcome to the Marketplace (panel header) This is a convenience service for fully registered members, it is not a free-trading service. In the Marketplace you can see events which have been sold out. As a fully registered member you can join a waitlist' for an event, and if a ticket becomes available then we will automatically sell you that ticket.

We believe our Marketplace is the fairest way managing .. : circumstances when, for whatever reason, you are unable to go to a gig and offers other members the opportunity of going in your place. For more details on how the marketplace works, see our <url buying policy>.

Information for Sellers (panel subheader) If you have bought a ticket for an event which you no longer wish to use, then you are able to do the following: * Use a fickle pass to give the ticket to a friend, you have four tickles per year available to you * If you have no tickles left you can only return a ticket via a waitlist, if the event is sold out We regret we cannot give refunds for tickets, as a ticketing service we are only acting on behalf of a promoter, who dictates any refund policy.

Information for Buyers (panel sub header) You must be a fully registered member to buy tickets for an event. Simply find the event you are interested in and click the "Join Waitlist" button. You will then be guided through the process for joining. You can cancel a waitlist request, to sell or to buy, from your home page on the site How does money change hands in the Marketplace? (subheader) Sellers (panel sub sub header) If we successfully find a buyer for your ticket, your original transaction will be refunded and then we will levy a separate handling fee of �1.50 against your card.

Buyers If you successfully buy a ticket through the Marketplace, your credit/debit card will automatically be levied. You will be charged the original price of the ticket, not an inflated price.

____________________ __________________________________________________________________________ _____

0** Content Guide All events for which there is a wait list should be listed. For each * 4S b for main panel entry in the list display: * Headline Artists or Event Name * *4 * I * * Date * Venue, Town/City * Join Waitlist Button * S I * Selecting the artist name should to the Artist's up and coming *..*S. *

gigs page When selecting the Join Waitlist button, do the following: * If the user is not logged in, present a You must join or login before joining a waitlist" * If the user is logged in and waiting for their photograph to be approved, after having completed the full registration process, then present a Please be patient, once your photo is approved, you can join this waitlist" * If the user is logged in and has not gone through the full registration data capture process, then present a message You need to complete a <url full registration> to join a waitlist.

* If the user is fully registered then begin the Join Waitlist Process A waitlist request form should be presented, but only if the browser is logged in and fully registered.

The user is able to join a waitlist and that process can be initiated from the Marketplace, or from an Artists up and coming gig list page. A web page is displayed corresponding to each stage of the process. Details of the artist, venue, data and doors open time are provided on each stage of this process.

Stage 1 of the process enables a user to join a waitlist. The panels, text and content included in the panels, and buttons provided on the webpage for stage 1 of the process are as follows:-S..

: Left hand What's happening here? (panel header) I... . . . . . Panel We will now confirm which event waitlist you want to join.

You can cancel the process at any stage.

We can't predict what tickets will become available, so for events with different ticket types, you must be prepared to accept any ticket that becomes available when you are at the head of the waitlist. This means your debit/credit card * . could be debited by the maximum price for all ticket types.

Select this box to tell us you have accepted and understood this feature of the waitlist. Enable interactive functions on remainder of page when this box is selected.

See our <url buying policy> for all the terms and conditions for joining a waitlist Main Panel Display the following: Content "You are about to join the waitlist for <name of event, location and date>. If you are successful, we will automatically deducted money from your credit/debit card.

You can cancel this waitlist request from your main profile page. Are you happy to continue? Yes or No confirmation.

Summary of ticket costs (sub header)

For each ticket type show: * Ticket type * Ticket Cost * Booking Fee * VAT (17.5% of the total of Ticket Cost and Booking Fee) * Card processing fee (1.5% of the VAT inclusive fee) * Total Cost Buttons Yes move to next stage No pop up confirmation dialog box and return to same page, or go back to the page from where the process was initiated Stage 2 of the process enables the user to configure their waitlist entry. The panels, text and content included in the panels, and buttons provided on the webpage for stage 2 of the *** process are as follows:-S...

:.:,:. Left panel What should you do here? (panel header) guide text To make this flexible for you we can let you set a minimum notice period before the start of the event. If you are still on s.

: the waitlist when the minimum notice period is encountered, we will remove your waitlist request.

Waitlists are closed 2 hours before doors opening for an event, that is the minimum waitlist period.

Data Capture Show the artist, venue, doors open time at the top of in Main Area Capture minimum notice period working back from the doors open time. Let the user do this in different ways: * Pick a date (then default to the doors open time on that date) * Pick a number of hours * Pick a number of days (always stick to the doors open time) Show the resulting date and time with the label, "Your waitlist entry will expire on dd/mmm/yyyy at XX:XX, 24 hour clock) Mobile Number. If you provide a mobile number we will send an SMS informing you of the ticket sale. We will send an email to your registered email address. An SMS notification will cost 20p. Tick a box to confirm.

Buttons Next move to next stage Cancel cancel waitlist request and go to page from where the process was initiated.

Stage 3 of the process enables a user to select a payment method in respect of the waitlist entry. The panels, text and content included in the panels, and buttons provided on the webpage for stage 3 of the process are as follows:-Left panel What should you do here? (panel header) guide text If you have already used a debit/card or credit card with us then we will default to using that one, some of those details will appear on this page for you to check. You can add e.

another credit card if you would like.

Select Confirm to post your new waitlist request with us.

Remember you can cancel your waitlist request from your home page.

: Important If we attempt to make take a payment from your card and the transaction fails, your waitlist request will be removed.

We will send a message to your mailbox if this happens.

Data Capture If the member has a card already registered, which has in Main Area made a successfully payment, then display those details, Current Card (subheader) * Card no Xxx's followed by last 5 digits * Issue Number * Valid From * Name on Card Buttons Use Different Card Reveal standard data capture for entering a new card Cancel Cancel waitlist request and go back to page the process was started from Confirm Go to next stage A member can attempt to return a ticket at any point in time. There are three scenarios: Event not sold out the member can only offer the ticket up to a friend using up a tickle in the process Event sold out if the member has a tickle available, then they can choose to use it by nominating a friend to receive, or simply offer it to the waitlist for general allocation. The tickle is not used up if the ticket is offered to the waitlist.

This process is initiated from their homepage, from their Ticket list (there is a link saying, "return ticket", or similar, beside each of their up and coming tickets). At stage 1 of the return ticket process, a pop-up confirmation box is provided that states "we are now going to help you try and return your ticket, are you sure you want to continue". Yes to continue to next stage, No to remain on same page.

* At stage 2 of the return ticket process:- * *. If the event is not sold out AND the member has no available tickles: * S S S...

Popup a dialog saying "you can't return you ticket at this point in time because the event is not sold out and you have no available tickles to transfer to a friend. Please wait until the event is sold out and then try returning it via a waitlist" S...

* If the event is not sold out AND the member has an available tick/e: Pop up a dialog saying "This event is not sold and you have an available tickle to transfer, so you can transfer this ticket to a friend. You will have to get the money from your friend yourself of course, we will not issue a refund to you directly. Are you happy to continue? If yes, then a webpage is provided that has the following panels, content and buttons:-Left panel What should you do here? (panel header) guide text You can nominate a friend who doesn't already have a ticket, and is also a fully registered member. On this page you can find and select the friend you want to receive your ticket. Choose the Confirm button to transfer ownership of your ticket Content for "Ticket Information" (Header) Main Panel Display: * Artist or Event Name * Date and Doors Open * Venue and City * Total Cost charged for ticket * Ticket Type Display a navigable list of members with different imagery for: * Friends already going (not selectable) * Friends not fully registered (not selectable) * Friends full registered and without a ticket

(selectable)

Buttons Confirm transfer ownership of ticket; remove from the . : selling member, add to the receiving member; ... send us messages to both sender and S...

receiver. Both member recent activity sections should now reflect the transfer Cancel Cancel request and go back to member home page

S

:: If the event is sold out and the member still has a tickle: Pop up a dialog saying. This event is sold out. You have an available tickle to transfer to a friend. Do you wish to use one to give this ticket to a friend or just offer it to the Marketplace for allocation to another member? If member wants to use a tickle, then reduce count by one and then follow the same process as above.

If member wants to offer to the Marketplace, a webpage is provided that has the following panels, content and buttons: Left panel What should you do here? (panel header) guide text You are about to offer this ticket to the Marketplace to try to finder a buyer. We cannot guarantee you will find a buyer, but if you do, then you will then be charged a transfer fee of �1.50 and your original purchase will be refunded to your original card.

Important If the �1.50 transfer fee is not successfully deducted from the card you give us, then your selling request will be abandoned and you will have to begin the process all over again. We will send you a message to your mailbox if this happens.

Please tick this box to indicate you have understood how the refund will work and that you accept the �1.50 selling fee.

(Ticket checkbox to enable remaining functions on this page) Content for "Ticket Information" (Header) Main Panel Display: :::: . Artist or Event Name * Date and Doors Open : .". * Venue and City * Total Cost charged for ticket * Ticket Type : Credit/Debit Card Details you purchased this ticket with (subheader) * Card no X)(X's followed by last 5 digits * Issue Number * Valid From * Name on Card Use a different card for transfer fee, checkbox. If selected, capture new card details, as per standard card data capture.

Buttons Confirm submit to waitlist (should be reflected on members recent activity section of their home page) Cancel Cancel request and go back to member home page The server 12 operates a waitlist algorithm that controls the waitlist process. Each waitlist usually has two queues, one for buyers, one for sellers. The waitlist algorithm is either a database stored procedure, or an event driven module which runs every time a new request to sell' (which should also appear in the member's home page) is added to the relevant table.

The process broadly speaking is as follows.

1) When a member adds a new bid to buy on a waitlist: Add request to bid queue 2) When a member adds a new bid to sell on a waitlist: Add request to offers queue 3) Periodically, try and match buyers with sellers across all event waitlists (for example, every ten minutes) Waitlists are closed 2 hours from doors opening for an event. When a waitlist is closed, messages are sent to members waiting for a ticket, and members waiting to sell a ticket, "itT' informing them they have not been successful. * ** ** S S...

As mentioned above, a FAQ link is made available from any page of the website. Usually the FAW link is provided in a footer: * 1. * *S *. I

..: The FAQs and corresponding answers, accessible via the FAQ link, are as follows:-What are we? We are a community of gig-goers who come together under one banner to share thehj experiences of gigs and the music they love.

It is also a ticketing service which allows you to buy tickets for music events around the country.

What is the Wristband? After you have bought your first ticket, we will post a wristband to you. Look after it because you must use your wristband every time you go to a gig.

If you lose your wristband, you will have to pay a replacement fee for a new one if you want to go to another gig.

It has all sorts of clever electronics in it which gives you quick access to gigs. It doesn't hold any personal data, but allows us to work out who you are when you appear at a gig.

What different types of registration There are two types of registration. The first is are there? when you just register as a casual user who wants to browse and access content on the website.

The second is when you register to buy tickets for gigs. You need to provide us with an electronic photograph of yourself to become fully registered.

When do I need to get a Wristband? Whenever you receive your first ticket for an event, either one you have purchased yourself, or one a friend has purchase for you, we will send you a wristband. As long as you don't lose or damage your wristband, you never need to ask us for a new one. You will be subject to a replacement fee if you ::..: need a new one, sotake care of it.

*... You use that wristband for all future events, it is like : .. a membership bracelet. *...

Why is there a Marketplace? The Marketplace is provided as a convenience service to our members and works differently for S...

buyers and sellers. The marketplace is not designed as a trading site for tickets, its there to allow you to pass tickets which you no longer have a need for onto other members in the community, that's all. It also lets us pass on tickets which only become available at the last minute to members of the service.

The Marketplace for Sellers When you have a ticket for an event and for any reason can't make it to the event, we will try and find another member for the ticket.

You also have 4 tickle passes to use every year where you can nominate a friend to receive your ticket. If you have no tickle passes left or would prefer not to use one up, then we will try find another member using the waitlist for that event.

The Marketplace for Buyers You can use the marketplace to join a wait//st for an event that is sold it. If tickets become available, we will pass these tickets to members on the waitlist, on a first come first served basis, Please see our <url marketplace policy> for details on how the marketplace works.

How do I get in touch with us? The simplest way to get in touch with us is by going to the <url Contact Us> section and filling out the electronic form.

What happens if I lose my wristband? Members who have been issued with a wristband have a "Lost Wristband" option on their personal home page -we call that the "Tickall Me" page.

::.. Selecting that link will deactivate your wristband and render it useless. No one will be able to use it : ., again. I..

We will charge a replacement fee for a new wristband, so do your best not to lose it.

* What do I do if I have not received my If you just come to the gig and go to the Referrals wristband and I need to go to a gig I desk, show us a bank card/drivers licence and we have paid for? will give you a temporary wristband for the gig.

Temporary wristbands can only be used once, so please dispose of them carefully.

How do I buy tickets for friends? You can buy tickets for your friends if they are fully registered and their photograph has been approved by us. During the ticket purchase process you first of all tell us which friends you want to buy tickets for. Remember that you will be charged the full cost of the all the tickets for your friends, and for any wristbands, if needed We'll send you a breakdown of any ticket purchase for your records.

Does the system store cookies on my computer? What is a cookie? Cookies are pieces of data which websites sometimes store on your computer to give you a better experience when using the website. You can use your browser's security settings to override any cookies which are stored on your computer.

Read our <un privacy policy> here.

What is done with my data? Your personal information will not be passed on to any third party without your express permission, unless we are obliged to do so for legal reasons.

In order to improve our service, we may include your depersonalised data (data which cannot be used to identify you) in trend analysis. This is done purely to help improve our service, the results of which may be passed to our industry partners, such as promoters who want to improve their service to the gig goer.

As a member we would also like to communicate with you about newand exciting things happening in the music industry which we hope you will be interested in. * .**

* If you do not wish to have us communicate directly with you or have your depersonalised data included in our trend analysis, please follow the Using my data" link on your login page.

Can I refund or exchange my tickets if Unfortunately we cannot refund or exchange tickets I don't want them. directly, unless the event is postponed or cancelled. Please see our <url Purchase Policy>, which you agreed to when you purchased tickets.

However we do provide the Marketplace which we provide to help people find buyers for tickets.

Please see our <un Marketplace Policy> Do I have to pay for my wristband? The first time you buy a ticket online we will charge you once-only fee of �1.50 for your wristband. You must then keep it and use it whenever you come to events.

If your first ticket is bought by for you by a friend, then your friend will pay �1.50 for your wristband, so as a good citizen, we'd recommend you to reimburse them.

If you lose your wristband, you will have to pay �5.00 for a new one. Your wristband is full of electronic wizardry and is key to making sure you get access to events quickly and securely, so please look after it.

Your wristband will be sent to the address you have nominated on your profile sethngs.

Where is my wristband sent to? When you register you provide a billing address where your credit or debut card is registered to. By default, your wristband will be sent to this address.

If you want your wristband sent to a different address, login and add a Correspondence Address in your Address Book, from your page.

Can I collect my wristband at a No, it will be delivered to the address you give us in . venue? your profile settings. If your wristband hasn't arrived I,..

before you come to an event, you can go to the organisers on the night and you'll be given a temporary wristband for that venue only. You can discard the temporary wristband after the event if you wish.

Turning to fearures of the rfid reader device 6, the device 6 can be used as a wristband checker during an event as well as for admissions. The device 6 has a mode of operation which is for general purpose, during events, where a wristband must be read and bring back the member details. This is not to be used for the purposes of admitting, but to be used for general discovery purposes where wristbands are lost and found, people need to be identified, or wristbands have gotten mixed up.

The reader device includes control software that provides the following functions:-.

Login to application User logs into application with username and password.

The login should check that this uses has permissions to use this device before passing the login.

There should be a menu which offers two options: 1. Event Admissions 2. Wristband Checker Selecting 1. Should enter the admissions process (See below). Selecting 2 should proceed to next, Loop stage Loop The device should wait in a loop which will wait for a wristband to be presented and then simply present the user profile for reading by the operator. Data to be fetched back (with formatted labels) o Photograph o Concatenated First name and Surname o Gender o DOB o Concatenated billing address * S * o Member status o List of tickets redeemed in the last week (i.e. admitted : ** to an event). Venue, Town, Artist, Date S...

o Next Ticket to be redeemed, Venue, town, Artist, Date S.',. e S S )I *5SSS

* The rfid reader device 6 is also used to control admissions. The admissions operator logs in at the operator terminal. Once successfully logged in the operator can use the reader device 6 to control admissions as follows:- * Reader reads card or wristband, interrogate for its reference number and then call a software service at the server 12 to pick up the Member profile Application on device 6 or operator terminal 8 interrogates databases for the card or wristband reference number using a software service and fetch back user profile data that includes: o Photograph o Concatenated First name and Surname o Gender o DOB o Concatenated registered address o Member status o Entitlement to enter gig -Yes or No o Booking reference o Flag to indicate if PIN should be asked for. If so, return two random digits from the PIN * Communications from card to card reader, and from device to software service may be encrypted.

Operator logon to device application, calls software service to authenticate user on the device, The device should not open for use, if the user has not been previously allocated to the event /device.

The access control processes performed by the ruid reader device 6 and operator terminal 8 are illustrated in overview in the flowchart of Figure 12.

The server 12 provides an application that offers functions to allow booking agents, artists * managers and promoters to manage the scheduling of events via the website 16. Each has a **** ***different role and will have access to different data within the system. They are each given : ..logins to the site and presented with functions using the same styled theme as the public I...

website.

*:. Role Function Manager The manager is able to create detail on their artists and view progress on ticket sales. A band manager cannot view or amend details on artists which are not within his management ownership.

Promoter This role is allowed to create information on venues and view historical and future information around ticket sales at their venues. One promoter should not be able to view or change the details on venues which are represented by different promoters Booking Agent This role can create schedules of events, tours or festivals. A booking agent cannot view events which have been created by other booking agents, but they will be able to see the global calendar for a venue as it relates to our events.

A system administrator is required to create individuals within the above roles to provide access:

Function Description

CRUD Management The following data should be managed: Management Company Name Location -a list of address. Types of address: billing, satellite, head office. Each location should have a main fixed line number Management Team and Role -list of individuals containing the following data: name, email address, mobile, land line, username, password, link to location Roles can include, Managing Director, Artist Manager, Admin, Billing CRUD Booking Agent Booking Agency Company Name Location -a list of address. Types of address: billing, satellite, head office. Each location should have a main fixed line number Booking Agent Team and Role -list of individuals containing the following data: name, email address, mobile, land line, username, password, link to location * .. Roles can include, Managing Director, Booker, Admin, Billing CRUD Promoter Promotional Company Name Location -a list of address. Types of address: billing, satellite, head office. Each location should have a main *..*** fixed line number Promotional Team and Role -list of individuals containing the following data: name, email address, mobile, land line, username, password, link to location Roles can include, Managing Director, Promoter, Admin, Billing Once these have been setup, each user should be given access to the system and presented with different functions: Manager Anyone with system access from the management team will be give the same set of functions. These functions should be available on login to the site:

Function Description

CRUD Solo Performer Data to be managed: Management Company owning the artist First Name Last Name Mobile Phone Number Email address CRUD Group Data to be managed: Management Company owning the artist Group Name List of Group members, first name, second name, email address, cell phone, role in group [yew Tour Details Tour details Jo.. * S S ** * **.* * *

Promoter * S. * S S S...

Anyone with system access from the management team will be give the same set of functions. These functions should be available on login to the site S... * SS ** *

: [ction Description

CRUD Venue Data to be managed includes: Venue Name Promoter -link to the promoter responsible for managing the venue. Note that this can change from time to time for a specific venue.

Full PAF address Map to get to the venue Performance Area. A venue must have a minimum of one performance area, but could have more than one. Data to be captured: Name

Description

Capacity Viewing area (e.g. standing, stalls) Optional list of all seat names with association to the area they are in -e.g. "Seat A2 in the Upper Area" Venue Map -Schematic of the venue showing all performance areas Venue Manager First Name Last Name Email Address Fixed Line Land Line Contact Address CRUD Festival Venue Data to be managed should include: Festival Venue Name * .S* * * * Full PAF Address * S..

Directions -Schematic Map and text descriptions to get to * .* and from the festival site. Should be in a web viewable form and the same as distributed in any printed material Total Capacity. This maybe one figure for the total site, or *:::: made up of the sum of individual performance areas.

Schematic of the festival site showing all performance S....

* areas, points of interest, routes, facilities, retail areas.

Performance Area. A festival venue must have a minimum of one performance area, but could have more than one.

Data to be captured: Name

Description

Capacity optional Viewing area (e.g. standing, stalls) Optional list of all seat names with association to the area they are in -e.g. Seat A2 in the Upper Area" Booking Agents Anyone with system access from the booking agent organisation will be give the same set of functions. These functions should be presented on login to the site.

Function Description

CRUD Event (The booking agent can create a venue or an act if one doesn't exist, and should use the same process as offered to the promoter) When creating an event the following data should be managed: Venue ID Tour Name, linked (optional) Date Doors Open time For each performance within the event: Artist name, linked * Start time * *** Duration * ** Performance Area For each area of the venue, ticket price per seat. This ticket price should include: ticket cost + booking fee net of VAT.

*:::: That price will be applied to every ticket in that ticket area, * even if the tickets are against named seats or not.

* Ticket priorities Number of tickets to be offered to the public Number of tickets to be given to management Ticket Release Schedule. This will define how tickets are L --released to the public based on a percentage of total ticket volume and dates for the release schedule. The total percentage must add up to 100%, and must only be applied to the publicly released tickets, not the management allocation. Capture: Date of release Percentage CRUD Tour Data to be managed includes: Tour Name Events created with the tour, using the above process CRUD Festival -(The booking agent should be able to create a festival venue if not done by the promoter) Data to be managed, a list of Festival Venue, linked Artist, linked Festival Performance Area, linked Start Time [End Time Tour Report Rolled Up Number of events Number of events sold out Total tickets for public sale Tickets sold Historical tickets sold by week, previous 4 weeks Percentage tickets sold * * I Total ticket revenue **** Total booking fee revenue * ** Total Promoter Revenue * * * -------.---------------Tour Report Events List of all events in a Tour with the following columns on each row: *:::: Venue + Town + Country Date Total Tickets available Total Tickets sold Historical tickets sold by week, previous 4 weeks Percentage tickets sold Totaltketrevenue rTotal booking fee revenue Total Promoter Revenue Turning to user registration processes, users are able to register via the website 16.

Registration can be partial or full. Only those members who have completed a full registration can buy or have tickets bought for them.

Considering partial registration first, the partial registration process can be launched via a Join button on the website home page A single web page is provided to capture user details. The panels, text, content and buttons provided on the web page, and the data to be captured by the web page are as follows.

Page Title Join Nowl Data to be * username captured * Password, with repeat confirmation * email address with repeat confirmation * checkbox, left deselected. "I would like to receive information by email and post, but not by telephone, from approved business partners, offering services deemed complimentary to the core service of community-based event ticketing' Guide text for What's happening now? *:::: left hand panel Join now to browse content on the website. To buy tickets, or have tickets bought for you by your friends, you must complete the full registration. Do this from your member : *. home page. We advise you to do this as soon as possible, so there are no delays when ordering tickets for your first event.

*:::: We have a number of <un Policies> attached to using the service, please review them.

Important You must activate your account from the email we send you within 24 hours.

Buttons Create Account -create the account based on the data provided, send welcome email for partially registered user.

if partial registration is confirmed, then a partial registration webpage is provided. The panels, text, content and buttons provided on the partial web page are as follows:-Guide Test Left Have a welcoming photograph with a community feel to it Panel Main Panel Welcome, your account has been activated! (Header) You are the newest member and we've already logged you in. You are ready to find and make friends, browse our website.

Important You aren't a full member yet, so you can't buy tickets and any friends you make can't buy tickets for you. You can complete the <un full registration> now, or do it at a later date from your <url personal home page>, all you need is a passport-style photograph to upload to the website.

We advise you to complete the full registration as soon as possible, so that there are no unnecessary delays when you find agig you want to goto.

Some useful links you can start to use * <url Artists> this will take you to our Artists page where you can see what gigs are up and coming * <url Live Room> this will take you to our gig ::::. archive where you can browse through gig reviews, photographs, and also contribute yourself : *** * <url forums> our members can use the S...

forum to discuss different music-related topics which and even make suggestions to improve the service * <url personal home page> this is your personal home page where you can review your ticket purchases, manage your friends, update your profile and loads of other cool stuff * <un policies> you can go here to read all the important stuff relating to the way we manage your data, terms of use for the website, rules for using the marketplace. All boring we know, but its important you read through these. We want you to understand how we operate and tell us how to provide a better service! * <url People> you can have a look at the other members and make friends.

* <url Help> here you will find a simple guide to using the system and get to understand why we think it's the best music ticketing service on the planet! tf a time limit is put on an expiring account, then the user should be able to register with the same email address and username (if it is still unique). An expiring registration web page is provided. The panels, text, content and buttons provided on the expiring registration web page are as follows:-Guide Text for What's happening now? left hand panel We are really sorry, but your account activation has expired.

Text for Centre All memberships must be activated within 24 hours. Your Panel activation expired XX minutes ago.

You will now have to apply for a new account again. Go to our <url new member link> to create a new account and this time please remember to activate within 24 hours.

You can use the same username if it's still available and provide the same email address too. * * *

::..: Our activation process is there to protect your security so please don't be too upset. * * * * ****

Turning to the full registration process, that process can be initiated in the following ways:- *1Qd. * a partial member logs into the site and on their home page they use the "Complete Full Registration" link. (link should only be present for partially registered users) * partially registered logged in member attempts to buy tickets * partially registered logged in member attempts to join a waitlist from the marketplace The full registration process is a five stage process.

At stage one of the process, a web page is displayed that requests personal information from the user. The panels, text, content and buttons provided on the web page, and data to be captured by the web page are as follows:-Data to be * title, drop down, one of Mr/Mrs/Miss/Ms/Doctor/Other captured * first name * surname * date of birth * sex * PIN, with double entry * Forgotten password question (label it' "The Question", see below) * Forgotten password question answer. Just provide a text box to type the answer, max 15 chars. Double entry confirmation.

Guide Text for What's happening now? (left panel header) left hand panel Before you can buy tickets, we need some extra details from you. We will guide you through this process, it won't take long.

You will need a passport-style photograph (.jpg, .gif, max size 5MB). This is used at the venue to verify your identity at a venue.

Buttons Next: save data and move onto screen two. Do a *::::* PAF search to populate the next screen with data : .. Cancel: don't save this data, navigate back to the Me S. page *.5S *., : At stage two of the full registration process, a web page is displayed that requests address information from the user. The panels, text, content and buttons provided on the web page, and data to be captured by the web page are as follows:-I0 Data to be * post code plus one of: captured o house number or o house name Button Find Address: takes the data above and returns from PAF service, 0, 1 matching row. Note that we should not bring back multiple flat numbers at the same house name or house number, so multiple rows should not be returned.

Data returned If there are zero rows returned, pop up a dialog box telling from PAF call the user, on dismissal return to the page with the data entered still there..

If there is one match, bring back the following data: * Street (read only) * town (read only) * county (read only) * postcode (Read only) * house no or house name (read only) (don't use PAF labels, use user-friendly street labels, like street, town etc) Present the following field to be added by the member if required: * Flat number (don't bring this back from PAF, but let the user add if required) Modified flag -if the user modifies the address served from PAF, track using this flag and keep a copy of the address prior to modification Guide text for What's happening now? (header) left hand panel We will send your wristband to your Correspondence Address. * S

The first time you buy tickets we will ask you for your : invoicing address if it's different from your correspondence S.,.

address, but we don't need it right now.

Buttons Next: save address and continue Cancel: exit without saving, ask for confirmation first.

Then navigate back to the home page At stage three of the full registration process, a web page is displayed that enables the user to upload their photograph. The panels, text, content and buttons provided on the web page are as follows:-5.

Left Hand We will accept these... (Hint Panel header) Panel list of good photos We won't accept these. . (Hint Panel header) List of bad photos Central Screen What's happening now? (sub-header) Content Please upload your photograph, to be displayed electronically to venue admissions staff when they scan your wristband at an event.

Here are three tips for taking a good photograph (sub-header) 1. <url How to make your own passport photos>, from DP challenge 2. Read the <un UK Passport Service photo guidelines (PDF, 752Kb) We reserve the right to refuse you entry to an event if your doesn't allow admissions staff to identify you, please see our <url admissions> policy> for further details.

Click this checkbox to let us know you have read and understood what's needed for a good photograph. (enable the browse file button once its clicked, only then) Upload Your Photo (subheader); field plus browse file button and then Upload button.

On selecting upload, navigate to next stage.

At stage four of the full registration process, a web page is provided that enables a user to confirm that they are happy with the uploaded photograph. The panels, text, content and *: buttons provided on that web page are as follows:-* * *1 * I...

Left Hand What's happening now? (left panel header) :,:::. Panel On the right you will see your photo that's been uploaded.

Please treat it as if you were submitting a photograph for a new passport. If you submit a photograph which can't easily identify you : or is inappropriate or offensive in any way, then we will reject it and you will not be able to buy tickets for any of our events.

We are sorry to be so insistent about this, but a good likeness of you is really important to getting into events, It is for your benefitc Tick this checkbox once you have read an understood the importance of providing a good photograph (In selecting the checkbox, enable interactive functions on rest of page) Main Screen Are you happy with this photo? (header) <plc> Important If you are happy with this photograph, and you are sure it meets our guidelines), then click "Confirm Photo" now. If you want to upload a different photo click the Back button below and submit an alternative.

Buttons Back goes back to the previous stage Confirm Photo dialog saying Are you really sure?" If Yes, then attach photo to the account and move to next stage. If No, then remain at this stage.

Also send out email confirming the full registration application At stage five of the full registration process, a summary of the registration data is provided to the user. The panels, text, content and buttons provided on the summary web page are as follows:-Left Hand What's Happening Now? (panel header) Panel Help Here's the summary of your registration information. We will now Text look at your photograph and we will let you know as soon as possible if it is approved.

Once your profile is approved, we will Iave a message in your message centre, so please keep a lookout for it by visiting regularly. We will give you a chance to upload another photo for *...

approval if this one isn't appropriate.

You can always change your profile data from your <url personal login page> Main Panel Display a summary of all data captured during this process .. : Display Data including photograph. Do not provide edit functionality.

Buttons Ok go to member home page As mentioned above, once a user is fully registered they have access to their own home page on the website. As can be seen from stage five of the registration process, once the registration process has been completed the member is immediately able to access their home page.

Various different functions are available to the user via their home page. For example, a user is able to report a lost wristband using a lost wristband web page accessible via a link from the user home page.

The functionality provided by the lost wristband web page is as follows:-

Function Description

Lost Pass This links should only be accessible for full members who have been sent a pass (wristband or other token), even if they haven't actually activated the pass.

A pass can only be reported lost after it has been activated. If the pass is subsequently reported lost, then the Lost Wristband function should be disabled, and only enabled once the member has activated a new pass.

On selecting Lost Pass, the member's pass should be deactivated from the system.

Detail: 1. User selects Lost Pass" 2. Present the following dialog a. "You are about to report your Pass lost, this will disable your pass forever from the system. Are you sure you want to do this?" b. UseaY/Ndialog: i. Yes text "Yes I want to report my Pass S...

missing" ::5:. ii. No text No, I don't want to report my Pass missing" 3. If No is selected return to the member profile page S...

: 4. If Yes is selected, pop up another dialog a. Are you positive you want to report your Pass missing, there is no going back from here, it will be disabled forever" b. YIN dialog i. Yes text "Yes, I want to report my Pass missing" ii. No text No, I don't want to report my pass missing" 5. If No is selected, return to member home page 6. If Yes is selected, then remove the pass reference from the member account and navigate back to the member home page. Change the status of the member to Full member, No Pass" this should be displayed on their home page below their approved photograph The user is also provided with wristband activation functionality via the user's home page.

The wristband activation functionality is as follows:-

Function Description

Activate Your When a member has a Wristband sent out, then a flag should be set so Pass that when the member next logs in, there is a link "Activate Wristband" which is enabled.

This link should be removed once the wristband is activated.

Each member receives a welcome letter which contains their activation code.

To activate, the user selects the link: 1. Page title: "Wristband Activation'.

Display the following text "In order to activate your Wristband you will need your welcome letter and your wristband in front of you. Ready to proceed'?'

S

a. Yes to continue :.:::. b. No to go back to the member home page 2. Page title: "Enter your Activation Code" a. Display the following text: "Please enter your Activation Code which will should be visible on your welcome letter in the space below (have a field to capture the data). Continue and Cancel buttons b. On Cancel, return to member home page c. On Continue, reconcile data entered with data stored in database.

If the same, go to next screen.

ii. If not the same, stay on the same page and display "Your activation code is not the same as we have stored on our database. Please try again." The user should be able to clear that message and then attempt to re-enter the data.

3. Page Title "Wristband Serial Number" Display "On the inside of your Wristband, there is a serial number, please enter that now" Using double entry, provide the number.

a. Continue button. If numbers are the same, then proceed to confirmation page b. If numbers are not the same, then display You have supplied two different serial numbers, try again". Remain in the same page c. Cancel button. Confirm cancellation of the process and return to the member home page 4. Page Title "Activation Confirmation" a. Display: "Congratulations, your Wristband has now been activated. We look forward to seeing you at the next gig.

Please remember to look after your Wristband, you will re-use it every time you come to one of our events, if you lose it you will be charged a replacement fee for a new one.

b. Continue button returns to the member home page. At this stage the member's status as it appears under their S...

* home page photo should be "Full Member -Active * . Wr*cfb *..

The user is also able to view a list of their recent activities via their home page, including:-*... * S* S. S

:: 1. Tickets purchased 2. Events attended 3. Forum posts 4. Reviews written 5. Photos added 6. Set lists added 7. Successful invites The user home page also includes a section that list all activity of the user relating to Waitlists, if there are any entries. If there is no waitlist activity, then that section is not displayed.

Fields for the Waitlist Activity List are as follows:- * Date (short form) * Action (see icons below) * Gig Icons are provided for the following actions:- * Joined a waitlist * Put a ticket on waitlist * Succeeded in buying a ticket on the waitlist * Waitlist expired * Left waitlist as a buyer * Removed ticket from waitlist or, left waitlist as a seller * Succeeded in Selling your ticket on the waitlist The user home page also provides a facility for a member to provide a name and e-mail address to invite members. The server 12 keeps track of successful member invites and display on member home page. Up to 5 addresses and names are allowed. *.IS

.. : As mentioned above, each user is able to submit and approve a photograph during the a...

registration process. A backend process is also provided via the website 16 that allows an : ** administrator to approve or reject photographs.

Three successive screens are displayed on the website 16 to enable the administrator to :::: approve or reject photographs. The sequence of screens is illustrated schematically in * Figure 13. The first screen (screen 1) is a login screen, the second screen (screen 2) is a *..SSa * viewing screen for viewing a list of users with photographs that are awaiting approval, and the third screen (screen 3) is a screen that enables viewing and approval or rejection of a photograph for a selected user. The data, buttons and other information provided on the three screens is as follows:-Screen 1 Data Username and Password Buttons Login Screen 2 Data This should be a list view of all the members waiting to have photos pending. The list should have the following fields: * Member ID * First Name + Second Name * Date Added * Status, one of (pending or locked (locked out by another user for approval There should be data on the list to show: * Average wait time for approval * Longest in list * Shortest in list * Total number processed * Total number of approvals * Total number of rejections The list should be ordered by the latest added, first in the list.

Buttons 1. Take Next -locks out the entry longest in the queue, fetches user profile plus photograph and then moves to next screen. Should set the photograph status to locked.

: 2. Logout -logs user out * *** * * **.* : *. Screen 3 **S.

Data View user profile and photo. This should show the member details :. to include: S. * * member ID * First name * Second name * full address * Email address * photo being offered for approval * date/time the photo was submitted for approval * length of time in queue * number of previously rejected photographs for this member Buttons 1. Reject, with YIN confirmation. Also capture the reason for rejection in a drop down: a. obscene photograph b. more than one person in the photo c. unclear picture d. not a head picture Change the member status back to "Partially Registered" (changed from Photo Approval Pending). Send "Photo Declined" message to their inbox. If the reason was for an obscene picture send the "Photo Declined Obscene" message.

2. Approve, with Y/N confirmation. Remove photo from the approval queue and send "Photo Approved" email to the member. Change their profile to "Full Member". Send a message to their inbox 3. Logout -logs user out and unlocks current record, putting it back in the approval queue Other After a photo is declined or accepted record the following information against the entry in the waiting for approval queue: * Date + time status changed from pending to declined or approved : * Username responsible for amending the status * Reason for rejection, if any : * * Email sent to the member (code will do) As mentioned above, the website 16 provides discussion forums where users can post comments. The different categories of forums provided by the website 16 are listed in Figure * 14.

S *5

The website 16 also provides for display of policies relating to aspects of uses of the website, the system, and data provided to the system.

The policies are accessible on a single web page, using tabbed navigation to move between display of different policies. The policies page can open up as a new window if selected during a ticket purchase or registration process, or any other process which is capturing data.

If simply browsing content, then the policies page can pop up in the same window.

The policies page provides the following standard text:-Header for Page: "Policies" Permanent Text (above the tabs Welcome to the website. We are obliged to put this up so for the different polices) please understand and read through the content to make sure you are aware of how we operate.

By accessing the website you are immediately bound by the Terms of Use Policy. If you buy tickets for events you are bound by the Purchase Policy. If you buy or sell tickets through the Marketplace, you are additionally bound by the Marketplace Policy. If you attend an event using a ticket bought from us you are bound by the Admissions Policy.

Make sure you review these Policies from time to time and if you have any queries about them, please tell us on our <Contact Us> page The text of the different policies, which are displayed on the policies page are provided in Appendix A below. S..

Covering letters and guidance notes may be sent to users along with their wristbands. *5**

Example templates for such letters and guidance notes are provided in Appendix B below. * S.

Alternative embodiments of the invention can be implemented as a computer program product for use with a computer system, the computer program product being, for example, a *... series of computer instructions stored on a tangible data recording medium, such as a diskette, CD-ROM, ROM, or fixed disk, or embodied in a computer data signal, the signal *S.** * being transmitted over a tangible medium or a wireless medium, for example, microwave or infrared. The series of computer instructions can constitute all or part of the functionality described above, and can also be stored in any memory device, volatile or non-volatile, such as semiconductor, magnetic, optical or other memory device.

It will also be understood by persons of ordinary skill in the art that whilst embodiments described herein implement certain functionality by means of software, that functionality could equally be implemented solely in hardware (for example by means of one or more ASICs (application specific integrated circuit)) or indeed by a mix of hardware and software.

As such, the scope of the present invention should not be interpreted as being limited only to being implemented in software.

It will be understood that the present invention has been described above purely by way of example, and modifications of detail can be made within the scope of the invention. Each feature disclosed in the description, and (where appropriate) the claims and drawings may be provided independently or in any appropriate combination. I.,. * * * * * * **. * a * a,-* .4 $ a a.. *q$. * a. a. *

SI

S

Appendix A Username and Password Access to certain areas of the Website is restricted. If you register with as a member we will allow you to choose a unique username with a password, which you will use to access member-specific content, products or services. You must ensure that the username and password are not disclosed to a third party. You accept responsibility for all activities that occur under your username and password combination.

If you contravene the Terms of the Website and other associated Policies, we reserve the right at our sole discretion to disable your username and password and to prevent you from accessing the Website for future.

Privacy policy This privacy policy describes how we use and protects any information that you give us when you use the website.

What we collect We may coilect the following information: * name * contact information including email address * demographic information such as postcode, preferences and interests * credit and debit card information for the purchasing of tickets * other information relevant to the music and live music industry ":. What we do with the information we gather ::.. We require this information to understand your needs and provide you with a better service, * L S and in particular for the following reasons: * .* *.:.. * internal record keeping * to improve our products and services.

* we may periodically send promotional email about new products offered exclusively S'S : by us, special offers or other information which we think you may find interesting using the email address which you have provided.

* from time to time, we may also use your information to contact you for market research purposes * we may use the information to customise the website according to your interests.

Security We are committed to ensuring that your information is secure. In order to prevent unauthorised access or disclosure we have put in place suitable physical, electronic and managerial procedures to safeguard and secure the information we collect online.

How we use cookies A cookie is a small file which asks permission to be placed on your computer's hard drive.

Cookies will allow the Website to respond to you as an individual. The Website can tailor its operations to your needs, likes and dislikes by gathering and remembering information about your preferences.

We use traffic log cookies to identify which pages are being used. This helps us analyse data about web page traffic and improve our website in order to tailor it to customer needs. We only use this information for statistical analysis purposes and then the data is removed from the system.

Overall, cookies help us provide you with a better website, by enabling us to monitor which pages you find useful and which you do not. A cookie in no way gives us access to your computer or any information about you, other than the data you choose to share with us.

You can choose to accept or decline cookies. Most web browsers automatically accept cookies, but you can usually modify your browser setting to decline cookies if you prefer.

Note however that this may prevent you from taking full advantage of the website.

Links to other websites Our website may contain links to enable you to visit other websites of interest easily.

However, once you have used these links to leave our site, you should note that we do not have any control over that other website. Therefore, we cannot be responsible for the protection and privacy of any information which you provide whilst visiting such sites and *...

such sites are not governed by this privacy statement. You should exercise caution and look at the privacy statement applicable to the website in question.

Controlling your personal in formation .. :You may choose to restrict the collection or use of your personal information in the following * whenever you are asked to fill in a form on the website, look for the box that you can click to indicate that you do not want the information to be used by anybody for direct marketing purposes * if you have previously agreed to us using your personal information for direct marketing purposes, you may change your mind at any time by emailing us at < Contact Us> We will not sell, distribute or lease your personal information to third parties unless we have your permission, or are required by law to do so. We may use your personal information to send you promotional information about third parties which we think you may find interesting if you tell us that you wish this to happen.

You may request details of personal information which we hold about you under the Data Protection Act 1998. A small fee will be payable. If you would like a copy of the information held on you please use the form provided in the <un Contact Us> section of the Website If you believe that any information we are holding on you is incorrect or incomplete, please email us as soon as possible, at the above address. We will promptly correct any information found to be incorrect.

Admission Policy A reusable electronic chip (Token") is provided to you when you buy tickets, or have tickets bought on your behalf, for an event. This policy covers the terms and conditions related to gaining admission to an event with your Token. The token may be in the form, for example, of a wristband or card.

Your Token is sent to you via registered delivery.

Z. When you arrive at the event and attempt to gain access, you will be asked by our :.: admissions team to present your Token for scanning. This process will bring back your member profile and ticket details to the admissions team. * ** * * * **.S

If the admissions team are able to verify your identify from your photograph and that you have a ticket allocated to your member profile, then you will be given admission to the event.

.You may be asked to additionally provide 2 random digits from your PIN, at our discretion. If ** S you must successfully provide such 2 random digits.

If the admissions personnel are unable to verify your identity from the photograph and/or PIN, you will be asked to go to the referrals queue where we will attempt to identify you using alternative means.

When you go to the referrals queue, you will be asked to provide one of the following: bank card, credit card, debit card, driver's licence or passport. No other form of identification will be accepted. If we are able to identify you from the card provided and a combination of random questions from your profile, we will admit you to the event. If this happens, your photo will be removed from our records and you can go online and provide another for approval. You will also be able to provide a new PIN, which will be asked for the next time you log on to the website.

If we are unable to identify you at the referrals queue, we reserve the right to refuse admission to the event and to retain your Tag. member account with which you were attempting to access the event will be suspended and you will lose any rights to refund.

Purchase Policy We want to make it as easy as possible for you to go to gigs which is why we use an electronic identification in a variety of different guises such as a rubber wristband or plastic card. Apart from the first time you buy a ticket for a gig, when we will send you a wristband through the post using recorded delivery, we won't have to send you tickets for events. This means you can't ever lose a ticket, unlike other paper-based ticketing solutions. Even if you lose your wristband, as long as you can identify yourself at a venue with either a bank card or a driver's licence, we will still let you into the event.

We sell tickets on behalf of promoters, venues and artists (together termed the Organisers").

That means we are subject to terms and conditions imposed on us by the Organisers of the 2g. event. There are some important points to remember: * S S S. S * *1S * S *SS.

* Unless otherwise stated at the time you buy your tickets we are unable to offer a : *. refund for a ticket unless in some special circumstances: S...

* When an event is cancelled by the Organiser, we will refund the full amount S...

: Remember that we provide a Marketplace service which allows you to either pass your ticket *,...: to a friend, or submit it onto the waitlist for that event. S *

Undelivered Wristband If you have paid for tickets for an event and your wristband is not delivered in time, simply go to the referrals desk at the venue and identify yourself with a bank card, credit card or driver's licence and we'll make sure you get into the event.

Lost Wristband If you lost a wristband you should tell us on the <un Lost wristband> link from your home page. We will then issue you a new one at a cost of �5 excluding postage and packaging.

We are sorry to have to charge you for the wristband, but they are full of interesting sophisticated technology which we Named Seats If you buy tickets for an event which requires named seats or is for a particular area of a venue, we will email those details and you can print that email off and bring with you to the event. Our door entry staff will know the specific details for your ticket in any case and will help you if you have any problems in any case. S. o * * * . *. * S S... * ** * S S *555 *SS* * S S

S

S * S

Appendix B The following welcome letter is posted to newly registered full members, along with their RFID band: <first name> <surname> Address Line 1 Address Line 2 Town/City Postcode <date letter printed> Activation Code:X)(XX)O(X)(XXX Hello <first name>, This is your welcome pack which should contain, your wristband and a set of guidelines for using your wristband to gain access to gigs. We hope you enjoy using our service and get to see many of your favourite acts.

Please look after your wristband, because you will need to wear it to our events to gain entry via our door admissions system. As a member, you do not receive a paper ticket to go to our gigs, you simply buy an electronic ticket from our website, and then wear your wristband to the gig. Venue admissions staff will swipe your wristband at the venue so you can gain access. Safe and easy! The wristband will also help us control ticket prices so that you only pay one price for a ticket.

And don't worry about the band if you lose it, none of your personal data or passwords are : .. stored on it.

SS

What Next? You must activate your wristband online: * * S S. S Go to the website using your internet browser, Login as normally with your username and password On your home profile page, you will find an "Activate Your Wristband" option, select it once by clicking with your left mouse button You will be asked to enter the reference number in your welcome letter, enter it where you are asked and click "Activate" Your band is now active. You must now bring it with you to every gig We looking forward to seeing you at your first gig. Remember once you have been to post your reviews and photos for the gig, it will help you get more priority for events in the future. *.** * * S * * S. * S * SS. * *5 * S S S... *S * SI *5 *

S S *

Replacement Wristband Letter This letter is posted to newly registered full member, along with their RFID band: logo <first name> <surname> Address Line 1 Address Line 2 Wristband Guidelines The following guidelines should help you understand more about your wristband: What if I lose my Tell us about it as soon as possible: wristband? Login as normal with your username and password On your home profile page, locate the "Lost Wristband" link, select it by clicking your left mouse button once Your band is now de-activated and it can't be used to enter a gig, by you or anyone else.

The next time you want to go to an event we will issue you with a new one, but it maybe subject to a replacement fee.

Remember that you must have a valid wristband to go to a gig.

How do I gain access to Each gig has a doors open time from when you can gain an event with my access to the venue. We advise you to turn up at the wristband venue as close to that time as possible, to make sure you get in for the start of the performance.

*e: At the venue, admissions staff will ask to see your wristband and then pass it over our mobile reader. *s.

Information about you will appear on the reader and will be * ** used to give you access to the gig. The photograph will be used to identify you and from time-to-time we will ask you for two digits from your PIN. *** * * *

Can I re-use my Yes. You can re-use your wristband every time you come * * wristband? to a gig, so don t throw it away after your first gig! What if I de-activate my Once you de-activate your wristband, it cannot be re-wristband and then find activated to your account. If you do find your band after it again, what should I deactivating it, we'd appreciate it if you either dispose of it do? safely, or hand it to us at your next gig.

What is the PIN This is a four digit number you will have provided during registration on the website. The only time you ever us this number is at a venue when you are in the process of gaining access. We will not display the PIN number to anyone, only ask you for 2 digits from that PIN. PIN with anyone else. If you do share this with another person, you are in violation of our Event Admissions policy, and your membership may be suspended.

Refer to our Events Admissions policy at the url below for further information What should I do if I If you realise you have forgotten your PIN before you go to forget my PIN at an the venue, please login to your personal home page and event? select the "Change PIN" option. You can choose a new PIN.

If you forget your PIN at the venue, then if you are able to answer a random question about your account and are able to provide us with one of the following means of identification: *..* *.. : Your photographic driver's licence (UK only) S...

Your passport Your bank or credit card :.::. we will reset your PIN number and you can view that the next time you login to the website. You will be able to gain access to the gig without providing your PIN, but must use your new PIN at future events.

Do I have to pay for a Your first wristband will have a fee of �1.50. Payment is wristband? made when you buy your first ticket, or a first ticket is bought for you by another member in the website community.

A replacement wristband will be charged at �3.00, so please try not to lose it. This will be charged the next time you buy a ticket after t is reported lost.

What If I forget my Contact the event admissions personnel at the venue on wristband when I go to the night of the gig and they will instruct you what to do.

a gig? As long as you can answer a random question about your account and can provide proof of your ID using one of the following methods, we will give you access to the event: Your photographic drivers licence (UK only) Your passport Your bank or credit card no other form of identification will be accepted If you don't bring your wristband with you to the gig, you may have to wait in a referrals queue, so please come as early as possible after doors open to make sure you can still get in to see the performance on time.

Refer to our Event Admissions Policy at the un defined in the Useful Links section of this letter.

What if I find another If you find a wristband at a gig, then please hand the member's wristband? wristband into the venue management staff, we will try to re-unite if with its owner.

If you find a wristband outside of a gig, we'd welcome you to return it to us at the next gig you go to, or dispose of it safely. *.S. * * * ** .

S * S * ** * S S **.. * 55S * S S S. * * S *

Claims (29)

1. CLAIMS1. A system for controlling access to an event, comprising:-a user access device comprising an identifier, wherein the identifier comprises at least one of a user identifier and a device identifier; means for obtaining information concerning a user, and associating the user information with the identifier; and means for reading the identifier from the access device, and obtaining the associated user information in dependence upon the identifier.
2. 2. A system according to Claim 1, further comprising means for displaying the user information.
3. 3. A system according to Claim 1 or 2, further comprising means for controlling access of a user to the event in dependence upon the user information.
4. 4. A system according to any preceding claim, wherein the user information comprises at least one of biometric data, image data, a photograph of the user, or a personal identification number.
5. 5. A system according to any preceding claim, further comprising:-a plurality of the user access devices, each having a respective identifier; a central server that comprises a data store for storing the user information and the identifiers; S...: 25 an event access sub-system that comprises a local server and at least one . access control apparatus, wherein:-*..the or each access control apparatus comprises the reading means and :.::. displaying means; the remote server is configured to transmit user information and identifiers to the local server, and the local server comprises a data store for storing the user *.SS * S* * information and the identifiers; the reading means is configured to transmit a request for user information to the local server, in response to reading of the identifier from a user access device; and the local server is configured to transmit the user information to the access control apparatus in response to the request.
6. 6. A system according to Claim 5, wherein the local server is configured to select user information and identifiers for users who have authorisation to access the event, and the transmitting of user information and identifiers to the local server comprises transmitted the selected user information and identifiers to the local server.
7. 7. A system according to Claim 5 or 6, wherein the local server is configured to monitor identifiers read by the at least one access control apparatus, to maintain a record of user access to the event, and to transmit the record of user access to the event to the remote server.
8. 8. A system according to any preceding claim, further comprising means for storing authorisation data representing authorisation to access the event and associating the authorisation data with the device identifier and/or the user identifier.
9. 9. A system according to Claim 8, wherein the user information further comprises the authorisation data.
10. 10. A system according to Claim 8 or 9, wherein the system further comprises means for transferring authorisation to access an event from one user to another user by modifying the authorisation data associated with each user.
11. 11. A system according to Claim 10, further comprising means for grouping users into user groups, wherein the transferring means is configured to provide transfer of S...*.. :25 authorisation between users in dependence on whether the users are in the same ". usergroup.
12. 12. A system according to Claim 11, further comprising user selection means for enabling a user to select at least one other user to be in their user group.

    :
13. 13. A system according to Claim 10, further comprising means for receiving user requests to access the event and means for maintaining a waiting list of user requests to access the event, and the transferring means is configured to transfer authorisation to a user and/or device identifier associated with a user having a user request in the waiting list.
14. 14. A system according to any preceding claim, further comprising data storage means for storing user records, each user record comprising an identifier included in a respective user access device and respective user information.
15. 15. A system according to Claim 14, wherein each user record further comprises respective user status data.
16. 16. A system according to any of Claims 10 to 13 as dependence upon Claim 15, wherein the transferring means is configured to allow or disallow a transfer of authorisation from one user to another user in dependence upon the status of one or both of the users, represented by the user status data for the users.
17. 17. A system according to Claim 15 or 16, further comprising means for receiving a user request to obtain authorisation to access an event, and determining whether or not to provide authorisation in dependence upon the user status data for the user.
18. 18. A system according to any of Claims 15 to 17, wherein the user status data comprises loyalty data.
19. 19. A system according to any preceding claim, further comprising a website and associated processing system, wherein the website comprises the or a means for receiving a user request to obtain authorisation to access an event.
20. 20. A system according to Claim 19, wherein the website comprises a social *.. : 25 networking area, and access to the social networking area by a user is dependent on . the user status data for the user.

    * ** .
21. 21. A system according to Claim 20 as dependent on Claim 18, wherein the system further comprises means for amending the loyalty data for a user in *::::° dependence upon the user's usage of the social networking area.
22. 22. A system according to any preceding claim, wherein the user access device is useable as a payment device, and the system further comprises means for receiving payments from a user, means for storing payment credit data for a user representative of credit available to the user for payment using the payment device, and at least one payment terminal for reading the identifier from the access device and debiting the payment credit data associated with the identifier by a payment amount.
23. 23. A system according to any preceding claim, wherein the user access device comprises rfid circuitry.
24. 24. A system according to any preceding claim, wherein the user access device is wearable by a user.
25. 25. A system according to any preceding claim, wherein the user access device comprises a wristband.
26. 26. A method of controlling access to an event, comprising: obtaining information concerning a user, associating the user information with at least one of a user identifier and a device identifier, and storing the user information in a data store; reading at least one of the user identifier and the device identifier from a user access device, and obtaining the associated user information from the data store in dependence upon user identifier or device identifier read from the user access device; and controlling access in dependence on the user information.
27. 27. A computer program product comprising computer readable instructions that are executable to perform a method according to Claim 26. *.S. * * * ** *
28. 28. A system substantially as described herein with reference to the accompanying drawings. * * * * *.*S
29. 29. A method substantially as described herein with reference to the **.*30 accompanying drawings. **I * 4