System and Method of RFID Portals

Abstract

An RFID portal is provided for placing at an access point associated with a temporary event. The access point is controlled by a security control. The portal has a portal body erectable on at least one side of a user pathway at the access point; and an RFID reader in the portal body for reading an RFID tag issued to, and worn by, an individual user for the event that has an encoded unique UserID readable by the RFID reader. The RFID reader is located in the portal body, so as to be physically proximate to a location of the user's body where the RFID tag is worn. The RFID reader is in communication with a server which has stored a list of valid UserIDs for the event. The RFID portal also has an indicator system for receiving notification from the server that the read UserID is a valid UserID for the event and generating an indication to the security control, such that the security control permits the user to proceed along the pathway.

What is claimed is: 
     
         1 - 21 . (canceled) 
     
     
         22 . A method of processing an access transaction, comprising:
 issuing ticketing particulars to a plurality of users for an event;   associating each set of ticketing particulars with an RFID or NFC tag having a unique UserID;   providing a portal body having a first upright portion on one side of an access pathway and a second upright portion on an opposing side of the access pathway; and   providing a programmed functionality at the portal body for reading an RFID or NFC signal at 13.56 MHz frequency, such that:
 a tag that is worn or hand-held by a user is read merely by the user passing between the first and second upright portions of the portal; 
 the UserID of the tag is communicated to a server which has stored a list of valid UserIDs for the event; and 
 upon receiving notification from the server that the read UserID is a valid UserID for the event, an indication is generated on an indicator system of the portal which signals a security control to permit the user to proceed along the pathway beyond the security control. 
   
     
     
         23 . The method of  claim 22 , wherein the security control is an automatically released barrier, gate, arm or turnstile. 
     
     
         24 . The method of  claim 22 , wherein the programmed functionality is in a device, and the device is a phone mounted on or near the portal body. 
     
     
         25 . The method of  claim 22 , wherein the tag is in a phone. 
     
     
         26 . The method of  claim 22 , wherein the indicator system includes a light. 
     
     
         27 . The method of  claim 22 , wherein the indicator system includes an emitter. 
     
     
         28 . The method of  claim 22 , wherein the indicator system is in a portal head mounted on an upper portion of the portal body, having at least one screen. 
     
     
         29 . The method of  claim 22 , wherein the UserID is associated with other data stored on the server. 
     
     
         30 . The method of  claim 29 , wherein at least some of the other data is retrieved and displayed on the at least one screen when the tag is read. 
     
     
         31 . The method of  claim 29 , wherein a message related to the other data is displayed on the at least one screen when the tag is read. 
     
     
         32 . The method of  claim 29 , wherein the other data includes at least one of: an age or date of birth credential, an access or privilege credential, and a stored funds balance. 
     
     
         33 . The method of  claim 29 , wherein the other data includes a link to an account or profile of the user. 
     
     
         34 . The method of  claim 28 , wherein the at least one screen consists of a first screen facing generally away from the user, and a second screen facing generally toward the user. 
     
     
         35 . The method of  claim 34 , wherein the first screen displays an access permitted decision, and the second screen displays a welcome message. 
     
     
         36 . The method of  claim 35 , wherein the welcome message is personalized to the user. 
     
     
         37 . The method of  claim 28 , wherein the at least one screen displays an access denied message if the user does not present a tag having a UserID that is valid at the time it is read. 
     
     
         38 . The method of  claim 37 , wherein the message includes a reason. 
     
     
         39 . The method of  claim 22 , further comprising sending a timestamp of the user's entry to the server. 
     
     
         40 . The method of  claim 39 , wherein a plurality of portal bodies are provided throughout an event venue, and the server stores a continuous record of timestamps of a user's progress through the event venue. 
     
     
         41 . The method of  claim 39 , wherein the timestamps are stored together with timed records of purchases or other actions by the user during the event.