Field of the Invention
The present invention relates to generating and authenticating passwords that include encoded information such as an expiry date or time period.
Description of the Related Art
Passwords are often used to selectively permit access to a resource, machine, vehicle, building, or the like. In many situations, it is desirable to provide such access for a limited period of time. For example, a device may be installed in a vehicle to selectively disable the vehicle if the owner or lessee fails to make payments; in such a device, a password may be provided that expires after a period of time, requiring the owner or lessee to obtain a new password each time he or she makes a payment on the vehicle. As an another example, a time-limited password may be provided to allow an individual to use a software application for a trial period, after which a payment may be required. As another example, a password may grant access to a restricted area of a building for a limited period of time, after which the password expires and can no longer be used to obtain access. In all of these situations, it is desired to provide a password that expires after some predetermined period of time or upon occurrence of some event.
In order for such a time-limited password scheme to function properly, it is useful to communicate the password expiry date to the authentication mechanism, so that the authentication mechanism can determine whether an entered password is still valid. For example, the expiry date for each password can be stored in a database that the authentication mechanism accesses when a password is entered. The authentication mechanism can look up the appropriate record in the database, based on the entered password, or a user identifier or other database lookup key. Then, in addition to verifying the authenticity of the password, the authentication mechanism can determine whether or not the password has expired, and grant or deny access to the resource accordingly.
Such a scheme presumes that the authentication mechanism has some means for accessing a database or other dynamic information repository in which expiry dates can be stored. In many cases, such access is undesirable, impractical, or impossible. The authentication mechanism may be implemented in a device that has no reliable network access, such as a vehicle, or a lock on a remote building. Alternatively, there may be a need for high reliability and/or speed that would be compromised if the system were required to rely on a network connection or other means for database access.
What is needed is a scheme for implementing passwords having expiry dates, without requiring that the authentication mechanism have access to a database or other source of expiry dates. What is further needed is a scheme for encoding the expiry date of a password within the password itself, without compromising the security or effectiveness of the password. What is further needed is a scheme for encoding an expiry date (or similar information) in a manner that does not unduly lengthen the password so as to make it difficult for a user to remember or enter.
What is further needed is a scheme for encoding identifiers or other information-carrying data items in passwords, without unduly lengthening the passwords and without unduly increasing the burden on a user. What is further needed is a scheme for encoding such information in a password reliably. What is further needed is a scheme that provides some assurance of accuracy and authenticity in the encoded information, and that reduces the possibility of tampering.
According to the techniques of the present invention, an authentication mechanism is provided that is capable of determining whether a password has expired without referring to a database or other information repository.
In addition, in one embodiment the invention provides a technique for encoding additional information in a password without unduly lengthening the password, so that the additional information can be extracted from the password when the user provides the password for authentication purposes. Thus, the password serves as an information-carrying data item as well as acting as an authentication mechanism. For example, it may be useful to encode, in a password, information specifying an access level, or specifying a warning period before password expiry, or the like.
A password generator provides a password to a user, for allowing time-limited use of a resource. The password may be communicated to the user via telephone, secure e-mail, secure postal delivery, or the like.
The user enters the password at an authentication terminal or input device, in order to gain access to the resource. In one aspect, the present invention is implemented using an infrared (IR) remote device for inputting a password. The user enters the password on a keypad on the remote device, and the remote device transmits the user-entered password to a receiver that includes or is coupled to an authentication mechanism. Alternatively, the user can enter the password using a keypad or other input device directly connected to the authentication mechanism.
The authentication mechanism determines whether the entered password is valid and unexpired; if so, it allows access to the resource. For example, the receiver and authentication mechanism may be coupled to the ignition mechanism of a vehicle, so as to disable the vehicle unless the user enters a valid, unexpired password. In one embodiment, the authentication mechanism extracts additional information from the entered password, and performs additional actions or provides feedback according to the additional information. For example, a warning period may be encoded in the password, in which case the authentication mechanism (or some other component) determines whether to display a warning to the user that the password will soon expire. Other information may also be encoded in the password.
In one aspect, the present invention avoids the need to transmit sensitive information across unsecured communication channels. Data used for password authentication and validation is independently generated at the password generator and at the authentication mechanism. The authentication mechanism and the password generator each include an internal clock that is capable of supplying the current date. Where time and date stamps are used as part of the authentication and validation mechanism, tolerances are provided to account for possible discrepancies between internal clocks.
In one aspect, a password is generated as follows. A password generator forms a data packet that includes data to be encoded in the password (for example, the number of days before password expiry, the number of warning days, and the like). The password generator obtains a date stamp from its internal clock, and retrieves or generates a secret key, which can be static or dynamic. The data packet, secret key, and date stamp are combined to form a string. A hash function is applied to the string, to generate a checksum. The checksum is combined with the data packet to generate a password, which is provided to the user.
In one aspect, after a user enters a password, the password is authenticated as follows. The checksum and the data packet are extracted from the password. The data packet is parsed to obtain the encoded data. The authentication mechanism independently retrieves or generates the secret key that was used to generate the password, and also independently obtains a date stamp from an internal clock. The extracted checksum is verified by combining the extracted data packet with the secret key and with the date stamp to generate a string, and by applying the hash function to the string to generate a verification checksum. The verification checksum is compared with the extracted checksum to determine whether the password is authentic.
In one aspect, if the checksums do not match, the authentication steps are repeated using different date stamps that fall within a predefined range of the current date stamp. Thus, the invention accounts for discrepancies between the internal clock of the password generator and that of the authentication mechanism.
The authentication mechanism uses the encoded password expiry data to determine whether the password is unexpired. If the password is authentic and unexpired, the authentication mechanism grants access; otherwise, it denies access.
The present invention provides a mechanism for providing time-limited passwords and for encoding other types of information in passwords. In one embodiment, the present invention is implemented in a device for tracking and enforcing vehicle payments, so as to provide passwords that permit use of a vehicle for a limited time, and that expire after the limited time so that the vehicle can no longer be used unless a new password is entered. New passwords are issued when vehicle payment is timely made, so that the time-limited password acts as a payment enforcement mechanism. Installation of a device employing the techniques of the present invention provides credit-challenged users with an opportunity to buy or lease a vehicle, and further provides auto dealers and financial institutions strong leverage over late and skipped payments.
Although, for illustrative purposes, the following description sets forth the invention in the context of a vehicle payment tracking and enforcement system, one skilled in the art will recognize that the techniques of the present invention can be applied in many other contexts, devices, and environments. In general, the present invention can be implemented whenever it is desirable to encode an expiry date or other information in a password, without unduly lengthening the password and without compromising security or burdening the user.
In one embodiment, the techniques of the present invention are used to enable or disable a vehicle according to whether an entered password is authentic and further according to whether the password has expired. Accordingly, the invention is implemented, in one embodiment, in a password authentication device installed in a vehicle being sold, leased, or rented. The device is connected to the vehicle's starter circuitry. Auditory warnings, such as beeps, are given before a payment is due; if a payment is not received, the unit prevents the vehicle from being started. Thus, users who fail to pay their car payments on time are unable to drive their vehicles.
When a password is authenticated, and when it is determined to be unexpired, the onboard device provides a closed relay path to the starter solenoid in order to allow the user to start the vehicle. In some embodiments, the system also includes added security features to foil jump-starts and other starts attempted without using the ignition key.
Referring now to
In one embodiment, infrared (IR) sensor 112 is coupled to authentication device 102 to receive IR signals received from a remote control device 103. Each time user 104 makes a payment, password generator 107, located at an operations center 110, generates a new password 106, using techniques described in more detail below. As described below, password generator 107 makes use of secret key 109, to generate passwords 106. The new password 106 is provided to user 104 (for example via telephone, or via a secure Internet website, secure email or the like). User 104 enters password 106 via numeric keys on remote control device 103, in order to enable vehicle 111 to be started.
Each password 106 allows use of vehicle 111 for a length of time, possibly including a grace period. Once this time period has expired, user 104 is required to enter a new password 106, which he or she receives upon making timely payment. In some embodiments, password 106 entry is not required every time vehicle 111 is started, but is required when a payment is due or on some periodic basis. As described in more detail below, each password 106 carries expiry date information, and optionally carries additional information such as a warning period, device identifier, and the like.
In one embodiment, password generator 107 generates an initial password 106 to be issued to user 104 when he or she takes possession of vehicle 111. Then, when the vehicle 111 dealer (or other payee) receives a vehicle payment, password generator 107 generates and issues a new password 106 carrying new expiry date information to reflect the fact that payment has been made. In one embodiment, a dealer, payee, operator, or other individual interacting with operations center 110 can specify an expiry date, warning period, or the like; in another embodiment such parameters are set automatically. Password generator 107 can have an associated user interface (not shown) to allow an operator or other individual to set parameters and otherwise interact with generator 107. In one embodiment, password generator 107 is implemented as a software application, such as a Microsoft Access-based application running on a conventional personal computer. In another embodiment, password generator 107 is implemented as a web-based application accessible by a dealer, payee, or other individual.
In one embodiment, according to the techniques described below, a warning time period is encoded in password 106. When authentication device 102 determines that password 106 has not yet expired, but that the current date is within the warning time period of the password expiry date, device 102 outputs an alert, such as for example a distinctive 10-second tone that is sounded when user 104 starts vehicle 111.
In one embodiment, the warning time period is not encoded in password 106, but is derived from the number of days the password is valid. For example, if password 106 is valid for 30 to 90 days, the warning function is activated when there are 5 days remaining before expiry; the warning function continues through the grace period (if any) or until payment is received (in which case a new password 111 is issued). If password 106 is valid for 10 to 29 days, the warning function is activated when there are 3 days remaining. If password 106 is valid for less than 10 days, the warning function is activated when 15% of the validity period remains. Other schemes for configuring the length of the warning period and/or the grace period are also possible.
Additional features, while not essential characteristics of the present invention, can also be incorporated in the functionality of device 102.
In one embodiment, device 102 includes an audio transducer (not shown) in order to provide user 104 with auditory feedback, such as a beep, that indicates a correct remote control key entry and operating mode. This component can also be used to provide other types of auditory feedback. In one embodiment, a visual indicator such as an LED can be provided instead of or in addition to the auditory device.
In one embodiment, the payee (such as the dealer or lessor of the vehicle) transmits password 106 directly to device 102 when a payment is made. Such transmission can take place, for example, via wireless pager or other onboard wireless connection device (not shown in
Interaction Diagram
Referring now to
Authentication device 102, in one embodiment, includes hardware and firmware for authenticating received passwords 106 and extracting encoded data therefrom. Authentication device 102 is electrically coupled to physical ignition switch 201 and to starter circuitry 101, so that device 102 is able to selectively enable or disable starter circuitry 101 as appropriate. In one embodiment, authentication device 102 is equipped to receive pager messages 203 from pager 202 and/or infrared messages 204 from IR remote device 103. Messages 203 and 204 contain, for example, passwords 106 to be authenticated, whether provided by user 104 or by operations center 110 directly. In one embodiment IR sensor 112 is included to receive IR messages 204 and provide such messages 204 to device 102.
In one embodiment, device 102 has access to key 109 (or to a key generation mechanism that operates deterministically) and clock 105, which are used as described below to authenticate passwords 106. In one embodiment, device 102 includes or is connected to speaker 205 (and/or other output device, such as an LED or display screen, not shown) for providing auditory and/or other feedback to user 104, to indicate for example whether a password 106 has been authenticated and/or whether a warning period is in effect.
In one embodiment, pager 202 receives messages from a central server, located for example at operations center 110. Pager 202 sends these messages 203 to a component of device 102 such as a PIC® microcontroller (available from Microchip Technology Inc. of Chandler, Ariz.) via a Universal Asynchronous Receiver/Transmitter (UART) connection. Handshaking is done with Request to Send (RTS) and Clear to Send (CTS) lines, according to an interface such as provided in a FLEX™ Telemetry messaging receiver (TMR1F), available from Davis-comms (S) Pte. Ltd. of Singapore.
In one embodiment, user 104 enters passwords via a keypad on IR remote device 103. Remote device 103 transmits, to IR sensor 112, an IR message 204 containing the entered password. In one embodiment, IR remote device 103 uses a Holtek HT6221/HT6222 or compatible encoder, available from Holtek Semiconductor, Inc., of Taiwan. IR sensor 112 is implemented, in one embodiment, using a receiver such as the TSOP1238 IR Receiver, available from Vishay Intertechnology, Inc. of Malvern, Pa.
Referring now to
In one embodiment, audio handler 302 is provided for generating audio tones to be played on speaker 205.
In one embodiment, the various components depicted in
Referring now to
One skilled in the art will recognize that messages 204 can take any form and be organized according to any desired protocol. For example, in one embodiment, messages 204 received from IR remote 103 include a function (for example, one character) and a payload (for example, any number of characters). The function indicates a command or type of operation that is desired, and the payload carries additional data for performing the command (such as password data).
In one embodiment, the payload portion of IR remote message 204 includes password 106, as described in more detail below.
Password Generation and Authentication
Referring again to
Referring also to
Password generator 107 then retrieves or generates 502 a secret key, for example a four-digit secret key. The key can be static or dynamic, according to well known techniques of key generation.
In one embodiment, multiple secret keys 109 are provided for authenticating passwords 106. The total number of keys 109 is m×n where m is the number of key 109 sets and n is the device ID modulo n, where each device 102 has a unique device ID. For example, m can be 5 and n can be 11. The particular key 109 to be used when generating or authenticating a particular password 106 is determined by selecting a key set using the current key set (plus one for IR messages produced by operations center 110), and selecting an entry within the key set by taking the remainder of the device ID divided by n.
Password generator 107 combines 503 the data packet, secret key, and a current time stamp, to generate a string. The time stamp can be in any form, and can represent the current date and/or time at any desired level of granularity; for example, in one embodiment the time stamp is a five-digit integer indicating the number of days since some fixed date. For example, if the fixed date is Dec. 31, 2001, the time stamp for Jan. 1, 2002 is 00001, for Jan. 31, 2002 is 00031, Jun. 1, 2003 is 00151, Jan. 1, 2003 is 00366 and for Mar. 1, 2003 is 00366+00031+00028=00425.
In one embodiment, the string also includes a unit identifier (for example, a four-digit number) that is unique to the particular device 102, resulting in a different password for each individual device 102.
Password generator 107 applies 504 a hash function to the string, to generate a checksum, which in one embodiment is a 4-digit code. Password generator 107 then adds 505 the data packet to the checksum, to generate a value (S), which in one embodiment is 5 digits in length. Password generator 107 then appends 506 the checksum to value S, to generate a password, which in one embodiment is 9 digits in length.
In one embodiment, password 106 has the following structure:
Referring now to
A user-entered password 106 is received, for example at IR sensor 112. In one embodiment, message 204 contains password 106. Authentication device 102 splits password 106 into two components, designated herein as S and checksum. In one embodiment, S is 5 digits in length and checksum is 4 digits in length.
Device 102 subtracts 603 checksum from S, to obtain a data packet. Device 102 then parses 604 the data packet to obtain the encoded information. Depending on the particular application and context, any type of data can be encoded. For example, encoded data may indicate expiry information for password 106 (how many days the password is effective), the number of warning days to provide, the number of emergency starts to allow, and the like.
In one embodiment, after the checksum is subtracted from the S, the data contains the following structure:
Next, device 102 verifies the authenticity of the extracted checksum. Device 102 obtains or generates 605 a secret key 109, using for example the same techniques that were performed by password generator 107 in step 502 of
In one embodiment, device 102 derives the checksum by applying a hash function to the following:
The verification checksum obtained in step 607 is compared with the checksum obtained in step 602. If they do not match, in one embodiment access is denied (for example, starter circuitry 101 is disabled). In another embodiment, to account for the fact that time stamps may not exactly match, verification steps 606 through 608 are repeated using other time stamps within a specified tolerance range of the current time stamp. For example, steps 606 through 608 may be repeated using time stamps ranging from (a) two days in the past or the date of the most recent authenticated message, whichever is later, to (b) five days in the future. One skilled in the art will recognize that any tolerance range can be used. The tolerance range effectively makes allowance for various confounding effects such as possibility that the message may not have been entered immediately, or that the battery that provides power to device 102 has been disconnected for a short period of time since the last valid password 106 was received. In one embodiment, password 106 is validated only if the matching time stamp is greater than that of the most recent valid password 106, so as to minimize the possibility of fraud or of unauthorized multiple uses of the same password 106.
Thus, in embodiments wherein a tolerance range is in effect, device 102 first determines 614 whether any time stamps within the tolerance range have not yet been tried. If all time stamps within the range have been tried without finding a match, device 102 denies access 615 (for example, by disabling starter circuitry 101). If one or more time stamps have not yet been tried, device 102 chooses 616 one of the remaining time stamps within the range and repeats steps 606 through 608.
If, in step 608, the checksums match, device 102 checks 609 whether password 106 has expired, for example by checking an expiration date encoded within password 106 against the current date. In one embodiment, this check is performed before the authentication steps 605 through 608, so that the authentication steps are omitted if password 106 has expired. In another embodiment, password 106 expiry is not checked.
If password 106 has expired 610, device 102 denies access 615 (for example, by disabling starter circuitry 101). If password 106 has not expired 610 (or if password 106 expiry is not checked), device 102 grants access 613 (for example, by enabling starter circuitry 101). In one embodiment, if password 106 has not expired 610, device checks 611 whether a warning period is in effect (for example, by referring to a warning period encoded in password 106); if so, device 102 issues 612 a warning, for example by causing speaker 205 to emit a distinctive tone.
In one embodiment, operations center 110 and device 102 each generate checksums independently (in step 504 and step 607, respectively), so that password authentication can be performed without transmitting the checksum across an unsecured communication channel.
In one embodiment, operations center 110 and device 102 each use time stamps that are independently determined, so that time stamp data need not be encoded in password 106 or otherwise transmitted among the components of the system. Operations center 110 determines its time stamp from internal clock 108, while device 102 uses its own internal clock 105. As described above, in one embodiment the method of the present invention takes into account the possibility of a discrepancy between clocks 108 and 105.
In one embodiment, operations center 110 and device 102 each obtain or generate secret key 109 independently, so as to avoid transmitting key 109 across an unsecured communication channel. In one embodiment, a different key 109 is provided for each device 102, so that operations center 110 maintains an array or database of keys 109 for various devices 102.
As depicted above, in one embodiment authentication device 102 is equipped to receive password 106 sent via pager message 203 and received from pager 202. In one embodiment, the same password encoding, decoding, and authentication techniques are applied regardless of the medium of transport for password 106.
Hash Function
In one embodiment, the hash function used in steps 504 and 607 is a one-way secret function that cannot easily be reverse-engineered. Such one-way hash functions are well known in the art.
In one embodiment, checksums for steps 504 and 607 are generated using the following hash function, expressed in ANSI-C:
This algorithm is a non-invertible hash function that uses the non-linearity of composed multiplication, shifting and exclusive-or for security in the tradition of the Tiny Encryption Algorithm (TEA) or the Helix encryption algorithm. This algorithm can also be implemented efficiently on microcontrollers, according to techniques that are well known in the art. One skilled in the art will recognize that other types of hash functions may also be used without departing from the essential characteristics of the present invention.
In the above description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the invention. It will be apparent, however, to one skilled in the art that the invention can be practiced without these specific details. In other instances, structures and devices are shown in block diagram form in order to avoid obscuring the invention.
Reference in the specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the invention. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment.
Some portions of the detailed description are presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of steps leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.
It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the discussion, it is appreciated that throughout the description, discussions utilizing terms such as “processing” or “computing” or “calculating” or “determining” or “displaying” or the like, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system's memories or registers or other such information storage, transmission or display devices.
The present invention also relates to an apparatus for performing the operations herein. This apparatus may be specially constructed for the required purposes, or it may comprise a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a computer readable storage medium, such as, but is not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, and magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, or any type of media suitable for storing electronic instructions, and each coupled to a computer system bus.
The algorithms and displays presented herein are not inherently related to any particular computer, network of computers, or other apparatus. Various general-purpose systems may be used with programs in accordance with the teachings herein, or it may prove convenient to construct a more specialized apparatus to perform the required method steps. The required structure for a variety of these systems appears from the description. In addition, the present invention is not described with reference to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings of the invention as described herein.
As will be understood by those familiar with the art, the invention may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. For example, the particular architectures depicted above are merely exemplary of one implementation of the present invention. The functional elements and method steps described above are provided as illustrative examples of one technique for implementing the invention; one skilled in the art will recognize that many other implementations are possible without departing from the present invention as recited in the claims. Likewise, the particular capitalization or naming of the modules, protocols, features, attributes, or any other aspect is not mandatory or significant, and the mechanisms that implement the invention or its features may have different names or formats. In addition, the present invention may be implemented as a method, process, user interface, computer program product, system, apparatus, or any combination thereof. Accordingly, the disclosure of the present invention is intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the following claims.
This application claims priority to, and is a continuation of, U.S. patent application Ser. No. 12/631,493, filed Dec. 4, 2009, titled “Encoding a Validity Period In a Password”. The Ser. No. 12/631,493 application claimed priority to U.S. patent application Ser. No. 10/856,968 (now U.S. Pat. No. 7,650,509), filed May 28, 2004, titled “Encoding Data in a Password”. The Ser. No. 10/856,968 application claimed priority to U.S. Provisional Application Ser. No. 60/539,892, filed Jan. 28, 2004, titled “Tracking and Enforcing Vehicle Payments.” All of the above-listed applications are incorporated by reference herein as if reproduced fully below.
Number | Name | Date | Kind |
---|---|---|---|
4335370 | Scalley et al. | Jun 1982 | A |
4592443 | Simon | Jun 1986 | A |
4624578 | Green | Nov 1986 | A |
4688026 | Scribner et al. | Aug 1987 | A |
4700296 | Palmer, Jr. et al. | Oct 1987 | A |
4736294 | Gill et al. | Apr 1988 | A |
4738333 | Collier et al. | Apr 1988 | A |
4800590 | Vaughan | Jan 1989 | A |
5014206 | Scribner et al. | May 1991 | A |
5132968 | Cephus | Jul 1992 | A |
5228083 | Lozowick et al. | Jul 1993 | A |
5359528 | Haendel et al. | Oct 1994 | A |
5426415 | Prachar et al. | Jun 1995 | A |
5490200 | Snyder et al. | Feb 1996 | A |
5495531 | Smiedt | Feb 1996 | A |
5510780 | Norris et al. | Apr 1996 | A |
5619573 | Brinkmeyer et al. | Apr 1997 | A |
5673318 | Bellare et al. | Sep 1997 | A |
5708712 | Brinkmeyer et al. | Jan 1998 | A |
5775290 | Staerzi et al. | Jul 1998 | A |
5797134 | McMillan et al. | Aug 1998 | A |
5818725 | McNamara et al. | Oct 1998 | A |
5819869 | Horton | Oct 1998 | A |
5857024 | Nishino | Jan 1999 | A |
5898391 | Jefferies et al. | Apr 1999 | A |
5917405 | Joao | Jun 1999 | A |
5928291 | Jenkins et al. | Jul 1999 | A |
5940812 | Tengel et al. | Aug 1999 | A |
5969633 | Rosler | Oct 1999 | A |
5970143 | Schneier et al. | Oct 1999 | A |
5970481 | Westerlage | Oct 1999 | A |
6025774 | Forbes | Feb 2000 | A |
6026922 | Horton | Feb 2000 | A |
6032258 | Godoroja et al. | Feb 2000 | A |
6064971 | McMillan et al. | May 2000 | A |
6088143 | Bang | Jul 2000 | A |
6088799 | Morgan | Jul 2000 | A |
6130621 | Weiss | Oct 2000 | A |
6157317 | Walker | Dec 2000 | A |
6185307 | Johnson, Jr. | Feb 2001 | B1 |
6195648 | Simon et al. | Feb 2001 | B1 |
6225890 | Murphy | May 2001 | B1 |
6232874 | Murphy | May 2001 | B1 |
6233566 | Levine et al. | May 2001 | B1 |
6249217 | Forbes | Jun 2001 | B1 |
6249227 | Brady et al. | Jun 2001 | B1 |
6278936 | Jones | Aug 2001 | B1 |
6353776 | Rohrl | Mar 2002 | B1 |
6370649 | Angelo et al. | Apr 2002 | B1 |
6380848 | Weigl et al. | Apr 2002 | B1 |
6401204 | Euchner et al. | Jun 2002 | B1 |
6429773 | Schuyler | Aug 2002 | B1 |
6489897 | Simon | Dec 2002 | B2 |
6587739 | Abrams et al. | Jul 2003 | B1 |
6601175 | Arnold et al. | Jul 2003 | B1 |
6611201 | Bishop et al. | Aug 2003 | B1 |
6611686 | Smith et al. | Aug 2003 | B1 |
6615186 | Kolls | Sep 2003 | B1 |
6665613 | Duvall | Dec 2003 | B2 |
6691232 | Wood | Feb 2004 | B1 |
6693517 | McCarthy et al. | Feb 2004 | B2 |
6714859 | Jones | Mar 2004 | B2 |
6717527 | Simon | Apr 2004 | B2 |
6741927 | Jones | May 2004 | B2 |
6804606 | Jones | Oct 2004 | B2 |
6812829 | Flick | Nov 2004 | B1 |
6816089 | Flick | Nov 2004 | B2 |
6816090 | Teckchandani et al. | Nov 2004 | B2 |
6828692 | Simon | Dec 2004 | B2 |
6868386 | Henderson et al. | Mar 2005 | B1 |
6870467 | Simon | Mar 2005 | B2 |
6873824 | Flick | Mar 2005 | B2 |
6888495 | Flick | May 2005 | B2 |
6917853 | Chirnomas | Jul 2005 | B2 |
6924750 | Flick | Aug 2005 | B2 |
6950807 | Brock | Sep 2005 | B2 |
6952645 | Jones | Oct 2005 | B1 |
6961001 | Chang et al. | Nov 2005 | B1 |
6972667 | Flick | Dec 2005 | B2 |
6985583 | Brainard et al. | Jan 2006 | B1 |
6993658 | Engberg et al. | Jan 2006 | B1 |
7005960 | Flick | Feb 2006 | B2 |
7015830 | Flick | Mar 2006 | B2 |
7020798 | Meng et al. | Mar 2006 | B2 |
7031826 | Flick | Apr 2006 | B2 |
7031835 | Flick | Apr 2006 | B2 |
7039811 | Ito | May 2006 | B2 |
7053823 | Cervinka et al. | May 2006 | B2 |
7061137 | Flick | Jun 2006 | B2 |
7091822 | Flick et al. | Aug 2006 | B2 |
7103368 | Teshima | Sep 2006 | B2 |
7123128 | Mullet et al. | Oct 2006 | B2 |
7124088 | Bauer et al. | Oct 2006 | B2 |
7133685 | Hose et al. | Nov 2006 | B2 |
7142089 | Yamagishi | Nov 2006 | B2 |
7149623 | Flick | Dec 2006 | B2 |
7205679 | Flick | Apr 2007 | B2 |
7224083 | Flick | May 2007 | B2 |
7228417 | Roskind | Jun 2007 | B2 |
7266507 | Simon et al. | Sep 2007 | B2 |
7292152 | Torkkola et al. | Nov 2007 | B2 |
7299890 | Mobley et al. | Nov 2007 | B2 |
7310618 | Libman | Dec 2007 | B2 |
7323982 | Staton et al. | Jan 2008 | B2 |
7327250 | Harvey | Feb 2008 | B2 |
7379805 | Olsen, III et al. | May 2008 | B2 |
7389916 | Chirnomas | Jun 2008 | B2 |
7427924 | Ferrone et al. | Sep 2008 | B2 |
7542921 | Hildreth | Jun 2009 | B1 |
7561102 | Duvall | Jul 2009 | B2 |
7814005 | Imrey et al. | Oct 2010 | B2 |
7818254 | Ma | Oct 2010 | B1 |
7823681 | Crespo et al. | Nov 2010 | B2 |
7873455 | Arshad et al. | Jan 2011 | B2 |
7877269 | Bauer et al. | Jan 2011 | B2 |
7904332 | Merkley | Mar 2011 | B1 |
7930211 | Crolley | Apr 2011 | B2 |
8018329 | Morgan et al. | Sep 2011 | B2 |
8086523 | Palmer | Dec 2011 | B1 |
8095394 | Nowak et al. | Jan 2012 | B2 |
8140358 | Ling et al. | Mar 2012 | B1 |
8217772 | Morgan et al. | Jul 2012 | B2 |
8325025 | Morgan et al. | Dec 2012 | B2 |
8344894 | Szczerba et al. | Jan 2013 | B2 |
8370027 | Pettersson et al. | Feb 2013 | B2 |
8370925 | Childress et al. | Feb 2013 | B2 |
8510556 | Cao et al. | Aug 2013 | B2 |
8630768 | McClellan et al. | Jan 2014 | B2 |
8754751 | Piccoli | Jun 2014 | B1 |
8841987 | Stanfield et al. | Sep 2014 | B1 |
8653956 | Berkobin et al. | Dec 2014 | B2 |
9002536 | Hatton | Apr 2015 | B2 |
20010034577 | Grounds et al. | Oct 2001 | A1 |
20010040503 | Bishop | Nov 2001 | A1 |
20020019055 | Brown | Feb 2002 | A1 |
20020091473 | Gardner et al. | Jul 2002 | A1 |
20020120371 | Levian et al. | Aug 2002 | A1 |
20020120374 | Douros | Aug 2002 | A1 |
20020193926 | Katagishi et al. | Dec 2002 | A1 |
20030036823 | Mahvi | Feb 2003 | A1 |
20030095046 | Borugian | May 2003 | A1 |
20030101120 | Tilton | May 2003 | A1 |
20030151501 | Teckchandani et al. | Aug 2003 | A1 |
20030191583 | Uhlmann et al. | Oct 2003 | A1 |
20030231550 | McFarlane | Dec 2003 | A1 |
20040088345 | Zellner et al. | May 2004 | A1 |
20040153362 | Bauer et al. | Aug 2004 | A1 |
20040176978 | Simon et al. | Sep 2004 | A1 |
20040177034 | Simon et al. | Sep 2004 | A1 |
20040203974 | Seibel et al. | Oct 2004 | A1 |
20040204795 | Harvey et al. | Oct 2004 | A1 |
20040239510 | Karsten | Dec 2004 | A1 |
20050017855 | Harvey | Jan 2005 | A1 |
20050024203 | Wolfe | Feb 2005 | A1 |
20050030184 | Victor | Feb 2005 | A1 |
20050033483 | Simon et al. | Feb 2005 | A1 |
20050128080 | Hall et al. | Jun 2005 | A1 |
20050134438 | Simon | Jun 2005 | A1 |
20050162016 | Simon | Jul 2005 | A1 |
20050200453 | Turner et al. | Sep 2005 | A1 |
20050212656 | Denison | Sep 2005 | A1 |
20050231323 | Underdahl et al. | Oct 2005 | A1 |
20050270178 | Ioli | Dec 2005 | A1 |
20060028431 | Leong | Feb 2006 | A1 |
20060059109 | Grimes | Mar 2006 | A1 |
20060080599 | Dubinsky | Apr 2006 | A1 |
20060100944 | Reddin et al. | May 2006 | A1 |
20060108417 | Simon | May 2006 | A1 |
20060111822 | Simon | May 2006 | A1 |
20060122748 | Nou | Jun 2006 | A1 |
20060136314 | Simon | Jun 2006 | A1 |
20070010922 | Buckley | Jan 2007 | A1 |
20070021100 | Haave et al. | Jan 2007 | A1 |
20070038351 | Larschan et al. | Feb 2007 | A1 |
20070082614 | Mock | Apr 2007 | A1 |
20070139189 | Helmig | Jun 2007 | A1 |
20070146146 | Kopf et al. | Jun 2007 | A1 |
20070176771 | Doyle | Aug 2007 | A1 |
20070179692 | Smith et al. | Aug 2007 | A1 |
20070185728 | Schwarz et al. | Aug 2007 | A1 |
20070194881 | Schwarz et al. | Aug 2007 | A1 |
20070222588 | Wolfe | Sep 2007 | A1 |
20070224939 | Jung et al. | Sep 2007 | A1 |
20070285207 | Bates | Dec 2007 | A1 |
20070288271 | Klinkhammer | Dec 2007 | A1 |
20070299567 | Simon et al. | Dec 2007 | A1 |
20080042814 | Hurwitz et al. | Feb 2008 | A1 |
20080109378 | Papadimitriou | May 2008 | A1 |
20080114541 | Shintani et al. | May 2008 | A1 |
20080150683 | Mikan et al. | Jun 2008 | A1 |
20080162034 | Breen | Jul 2008 | A1 |
20080221743 | Schwarz et al. | Sep 2008 | A1 |
20080223646 | White | Sep 2008 | A1 |
20080231446 | Cresto | Sep 2008 | A1 |
20080243558 | Gupte | Oct 2008 | A1 |
20080245598 | Gratz et al. | Oct 2008 | A1 |
20080255722 | McClellan et al. | Oct 2008 | A1 |
20080294302 | Basir | Nov 2008 | A1 |
20090043409 | Ota | Feb 2009 | A1 |
20090051510 | Follmer et al. | Feb 2009 | A1 |
20090182216 | Roushey, III et al. | Jul 2009 | A1 |
20090234770 | Simon | Sep 2009 | A1 |
20090237249 | Bielas | Sep 2009 | A1 |
20090248222 | McGarry et al. | Oct 2009 | A1 |
20090284359 | Huang et al. | Nov 2009 | A1 |
20090284367 | Pfafman et al. | Nov 2009 | A1 |
20090295537 | Lane et al. | Dec 2009 | A1 |
20100030586 | Taylor et al. | Feb 2010 | A1 |
20100045452 | Periwai | Feb 2010 | A1 |
20100063850 | Daniel | Mar 2010 | A1 |
20100075655 | Howarter et al. | Mar 2010 | A1 |
20100090826 | Moran et al. | Apr 2010 | A1 |
20100148947 | Morgan et al. | Jun 2010 | A1 |
20100238009 | Cook et al. | Sep 2010 | A1 |
20100268402 | Schwarz et al. | Oct 2010 | A1 |
20100312691 | Johnson, Jr. | Dec 2010 | A1 |
20110040630 | Weiss | Feb 2011 | A1 |
20110050407 | Schoenfeld et al. | Mar 2011 | A1 |
20110057800 | Sofer | Mar 2011 | A1 |
20110084820 | Walter et al. | Apr 2011 | A1 |
20110148626 | Acevedo | Jun 2011 | A1 |
20110153143 | O'Neil et al. | Jun 2011 | A1 |
20110210867 | Benedikt | Sep 2011 | A1 |
20110270779 | Showalter | Nov 2011 | A1 |
20120066011 | Ichien et al. | Mar 2012 | A1 |
20120068858 | Fredkin | Mar 2012 | A1 |
20120068886 | Torres | Mar 2012 | A1 |
20120089423 | Tamir et al. | Apr 2012 | A1 |
20120098678 | Rathmacher et al. | Apr 2012 | A1 |
20120158356 | Prochaska et al. | Jun 2012 | A1 |
20120203441 | Higgins et al. | Aug 2012 | A1 |
20120212353 | Fung et al. | Aug 2012 | A1 |
20120221216 | Chauncey et al. | Aug 2012 | A1 |
20130018677 | Chevrette | Jan 2013 | A1 |
20130074107 | Hyde et al. | Mar 2013 | A1 |
20130074111 | Hyde et al. | Mar 2013 | A1 |
20130074112 | Hyde et al. | Mar 2013 | A1 |
20130074115 | Hyde et al. | Mar 2013 | A1 |
20130127617 | Baade et al. | Mar 2013 | A1 |
20130099892 | Tucker et al. | Apr 2013 | A1 |
20130138460 | Schumann et al. | May 2013 | A1 |
20130141252 | Ricci | Jun 2013 | A1 |
20130144460 | Ricci | Jun 2013 | A1 |
20130144461 | Ricci | Jun 2013 | A1 |
20130144469 | Ricci | Jun 2013 | A1 |
20130144770 | Boling et al. | Jun 2013 | A1 |
20130144771 | Boling et al. | Jun 2013 | A1 |
20130144805 | Boling et al. | Jun 2013 | A1 |
20130204455 | Chia et al. | Aug 2013 | A1 |
20130133389 | Weiss | Dec 2013 | A1 |
20140191858 | Morgan et al. | Jul 2014 | A1 |
20140225724 | Rankin et al. | Aug 2014 | A1 |
20140358896 | Camacho et al. | Dec 2014 | A1 |
20160090923 | Al Salah | Mar 2016 | A1 |
Number | Date | Country |
---|---|---|
1557807 | Jul 2005 | EP |
1020040073816 | Aug 2004 | KR |
9616845 | Jun 1996 | WO |
2007092272 | Aug 2007 | WO |
2007092287 | Aug 2007 | WO |
2010068438 | Jun 2010 | WO |
2010062899 | Jun 2010 | WO |
2012097441 | Jul 2012 | WO |
Entry |
---|
Microchip Technology Inc, “KEELOQ Code Hopping Encoder”, HCS301, 2001, pp. 1-26. |
Fogerson, R. et al. “Qualitative Detection of Opiates in Sweat by EIA and GC-MS.” Journal of Analytical Toxicology; Oct. 6, 1997. vol. 21, No. 6, pp. 451-458(8) (Abstract). |
De La Torre, R. et al. “Usefulness of Sweat Testing for the Detection of Cannabis Smoke.” 2004 American Association for Clinical Chemistry, Inc., 29th Arnold O. Beckman Conference; Apr. 12-13, 2011; San Diego, CA. |
On Time Payment Protection Systems, printed Jan. 2, 2004 from www.ontime-pps.com/how.html. |
Aircept Products, printed Jan. 2, 2004 from www.aircept.com/products.html. |
How PayTeck Works, printed Jan. 2, 2004 from www.payteck.cc/aboutpayteck.html. |
Article: “Pager Lets You Locate Your Car, Unlock and Start It”, published Dec. 10, 1997 in USA Today. |
Article: “Electronic Keys Keep Tabs on Late Payers”, published Sep. 22, 1997 in Nonprime Auto News. |
Article: “PASSTEC Device Safely Prevents Vehicles from Starting”, published Jul. 19, 1999 in Used Car News. |
Payment Clock Disabler advertisement, published May 18, 1998. |
Secure Your Credit & Secure Your Investment (PayTeck advertisement); printed Jan. 2, 2004 from www.payteck.cc. |
iMetrik Company Information, printed Dec. 21, 2006 from imetrik.com. |
About C-CHIP Technologies, printed Dec. 21, 2006 from www.c-chip.com. |
Hi-tech tools to solve traditional problems, printed Dec. 26, 2006 from www.c-chip.com. |
C-Chip Technologies' Products: Credit Chip 100, Credit Chip 100C, Credit Chip 200, printed Dec. 21, 2006 from www.c-chip.com. |
The Credit Chip 100, printed Dec. 21, 2006 from www.c-chip.com. |
Credit Chip 200G Series and The Credit Chip 200G Series, C-Chip Technologies Corp., date unknown. |
C-Chip Technologies User Guide, C-Chip Technologies Corp., date unknown. |
EEC-EN0F204RK Panasonic Electronic Components | P14164CT-ND | DigiKey. Web. Accessed Feb. 13, 2013. www.digikey.com/product-detail/en/EEC-EN0F204RK/P14164CT-ND/1937322. |
Number | Date | Country | |
---|---|---|---|
20140136057 A1 | May 2014 | US |
Number | Date | Country | |
---|---|---|---|
60539892 | Jan 2004 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12631493 | Dec 2009 | US |
Child | 14159568 | US | |
Parent | 10856968 | May 2004 | US |
Child | 12631493 | US |