Abstract: A system and method monitor skier behavior. An identifier is read from a lift access product when the lift access product is in the vicinity of a lift boarding area and a scan record containing the identifier, location information of the lift boarding area and a time stamp if generated. The scan record is processed to generate a location event record that is stored within a location database. The location database is processed to determine skier behavior based upon the location event records.

Abstract: A system and method monitor skier behavior. An identifier is read from a lift access product when the lift access product is in the vicinity of a lift boarding area and a scan record containing the identifier, location information of the lift boarding area and a time stamp if generated. The scan record is processed to generate a location event record that is stored within a location database. The location database is processed to determine skier behavior based upon the location event records.

Abstract: A system and method monitor skier behavior. An identifier is read from a lift access product when the lift access product is in the vicinity of a lift boarding area and a scan record containing the identifier, location information of the lift boarding area and a time stamp if generated. The scan record is processed to generate a location event record that is stored within a location database. The location database is processed to determine skier behavior based upon the location event records.

Abstract: A system and method monitor skier behavior. An identifier is read from a lift access product when the lift access product is in the vicinity of a lift boarding area and a scan record containing the identifier, location information of the lift boarding area and a time stamp if generated. The scan record is processed to generate a location event record that is stored within a location database. The location database is processed to determine skier behavior based upon the location event records.

Abstract: A system and method monitor skier behavior. An identifier is read from a lift access product when the lift access product is in the vicinity of a lift boarding area and a scan record containing the identifier, location information of the lift boarding area and a time stamp if generated. The scan record is processed to generate a location event record that is stored within a location database. The location database is processed to determine skier behavior based upon the location event records.

Abstract: A system and method monitor skier behavior. An identifier is read from a lift access product when the lift access product is in the vicinity of a lift boarding area and a scan record containing the identifier, location information of the lift boarding area and a time stamp if generated. The scan record is processed to generate a location event record that is stored within a location database. The location database is processed to determine skier behavior based upon the location event records.

Abstract: A system and method monitor skier behavior. An identifier is read from a lift access product when the lift access product is in the vicinity of a lift boarding area and a scan record containing the identifier, location information of the lift boarding area and a time stamp if generated. The scan record is processed to generate a location event record that is stored within a location database. The location database is processed to determine skier behavior based upon the location event records.

Abstract: A system and method monitor skier behavior. An identifier is read from a lift access product when the lift access product is in the vicinity of a lift boarding area and a scan record containing the identifier, location information of the lift boarding area and a time stamp if generated. The scan record is processed to generate a location event record that is stored within a location database. The location database is processed to determine skier behavior based upon the location event records.

Abstract: A method for determining validity of an RFID tag. The method includes probing the tag using a series of tag commands to trigger a corresponding series of tag responses, comparing the tag responses to tag reference data stored in a database, and repeating the probing and comparing operations to determine whether or not the tag is valid.

Abstract: A method for provisioning security for an RFID tag. Initially, a random new tag ID is generated, and a new master key is generated based on an existing master key. Encrypted user data to be placed on the tag is generated utilizing the new tag ID as an IV and the new master key as input to an encryption algorithm. The new tag ID and the encrypted user data are then written to the tag.

Abstract: A method for optimizing communication between an RFID reader and an RFID tag. Initially, an RFID tag is detected, and the tag type is passively determined. An optimization goal is then selected. An optimal parameter set for communicating with the tag, based on the tag type and the optimization goal is then determined. The reader is then reconfigured using the optimal parameter set to communicate with the tag.

Abstract: A method for creating an enhanced RFID tag. A longer range RFID tag and a relatively shorter range credential are proximately co-located in the same container. The longer range RFID tag is cryptographically bound to the shorter range credential by storing, on the longer range tag, signed data which includes indicia of the shorter range tag. The longer range RFID tag requires authorization via an authentication server to grant access to data stored in the enhanced RFID tag.

Abstract: A method for generating and using a consumable RFID tag in a system including a plurality of RFID tag readers communicatively coupled in a network in which the tag includes rewritable tag memory. Data is stored in the tag memory, including a sequence number, a UID, and an ownership ID. The data is signed with a key to generate signed content. Each time the tag is read by one of the readers in the network, the signature and sequence number in the tag memory are validated by comparing signed content stored in the tag with signature data stored in said one of the readers; a new sequence number is stored in the tag memory; contents of the tag memory, including the new sequence number and the ownership ID, are signed with a key to generate new signed content; and the new signed content is written to the tag memory.

Abstract: A system for communicating a message securely between a sender and a receiver. The sender provides a key server with a string specifying the receiver. The key server obtains a message key and a particular envelope encryption key corresponding with a particular envelope decryption key, encrypts the message key with the envelope encryption key (creating the envelope), and provides the envelope to the sender-client. The sender-client encrypts the message with the message key and provides it and the envelope to the receiver. The receiver-client receives these and asks an authentication server for the envelope decryption key. The authentication server obtains the envelope decryption key and provides it to the receiver. The receiver then decrypts the envelope with the envelope decryption key, to get the message key, and decrypts the message.

Abstract: A federated authentication service technology (10) for authenticating a subject (20) residing in a subject domain (12) on a network to a server application (38) residing in a server domain (18), wherein an authentication mechanism (32) residing in an authentication domain (16) affects the service provided by the server application (38). A client (22), which may be integrated non-human instances of the subject (20), authenticates the subject (20) and a protocol proxy (34) mediates with the authentication mechanism (32) to obtain a name assertion which the client can use to access the server application (38). When multiple authentication mechanisms (32) are available, an optional agent (24), mechanism resolution process (26) and mechanism repository (28), all residing in an agent domain (14), may be used to resolve to one suitable authentication mechanism (32).