Automated service-based order processing
A system and method provide efficient, secure and fast automation of order processing. The method includes initiating an order by wirelessly receiving data from a personal digital key (PDK). The method also includes receiving a biometric input and confirming the initiation of the order by authenticating the biometric input. In response to authenticating the biometric input, the order is processed. In another embodiment, the method of further includes automatically initiating an order completion by wirelessly receiving data from a PDK. The method further includes receiving a biometric input and confirming the order completion by authenticating the biometric input. In response to authenticating the biometric input, the order is completed. In yet another embodiment, the method further includes processing rewards based on the order.
Latest Proxense, LLC Patents:
- Linked account system using personal digital key (PDK-LAS)
- Secure element as a digital pocket
- Proximity-based healthcare management system with automatic access to private information
- Implementation of a proximity-based system for object tracking and automatic application initialization
- Proximity-sensor supporting multiple application services
This application claims the benefit of U.S. Patent Application No. 61/043,326, entitled “Automated Service-Based Order Processing (Prox Order)” filed Apr. 8, 2008 and U.S. Patent Application No. 61/102,983, entitled “Automated Service-Based Order Processing (Prox Order)” filed Oct. 6, 2008, the entire contents of which are all herein incorporated by reference.
BACKGROUND OF THE INVENTION1. Field of Art
The disclosure generally relates to the field of electronic order processing, and more specifically, to automated order processing using biometric verification.
2. Description of the Related Art
Optimizing sales transactions is one of the many challenges faced by various merchants. Ensuring these processes are secure, efficient and simple is important to merchants, providers, users and consumers alike. Conventionally, technologies such as magnetic cards (e.g., credit cards, debit cards, ATM cards, and employee badges) have been used in attempt to address these needs. More recently, various contactless cards or tokens requiring placement near compatible readers have been used.
Further, in serviced-based transactions, such as those that would occur at STARBUCKS™, MCDONALDS™, or QUIZNOS™, the transaction may be further delayed during the ordering process due to the various steps involved in processing and completing the transaction. The transaction may be even further delayed due to the fact that, oftentimes, customers customize or change their orders from what is regularly offered. Also, many of these merchants have increased in popularity over the years, leading to increasing number of customers visiting such merchants. The combination of the currently technologies for completing and processing these service-based transactions, coupled with the increase in number of customers frequenting the merchants' establishments leads to longer wait times for a transaction to process and complete. A new technology is needed that provides highly reliable, safe, efficient automation for order processing.
BRIEF SUMMARY OF THE INVENTIONA system and method provide efficient, secure and fast automation of order processing. A system for automated electronic order processing, including a customer interface device for wirelessly receiving data from a personal digital key (PDK) and a transactions server, adapted for communication with the customer interface device for initiating an order in response to wirelessly receiving the data from the PDK and processing the order. In one embodiment, the system also includes a merchant interface device, adapted to communicate with the transactions server, for wirelessly receiving data from a personal digital key (PDK). The transactions server is adapted for communication with the merchant interface device and for initiating an order completion. In one embodiment, the system also includes a reader, adapted to communicate with the transaction server, for automatically uploading data from the PDK and receiving biometric input from a user.
The method includes initiating an order by wirelessly receiving data from a personal digital key (PDK). The method also includes receiving a biometric input and confirming the initiation of the order by authenticating the biometric input. In response to authenticating the biometric input, the order is processed. In another embodiment, the method of further includes automatically initiating an order completion by wirelessly receiving data from a PDK. The method further includes receiving a biometric input and confirming the order completion by authenticating the biometric input. In response to authenticating the biometric input, the order is completed. In yet another embodiment, the method further includes processing rewards based on the order.
The features and advantages described in the specification are not all inclusive and, in particular, many additional features and advantages will be apparent to one of ordinary skill in the art in view of the drawings, specification, and claims. Moreover, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes, and may not have been selected to delineate or circumscribe the disclosed subject matter.
The disclosed embodiments have other advantages and features which will be more readily apparent from the detailed description, the appended claims, and the accompanying figures (or drawings). A brief introduction of the figures is below.
Figure (FIG.) 1 is a high level block diagram illustrating a system for automated service-based order processing according to one embodiment of the invention.
The figures depict various embodiments of the present invention for purposes of illustration only. One skilled in the art will readily recognize from the following discussion that alternative embodiments of the structures and methods illustrated herein may be employed without departing from the principles of the invention described herein.
DETAILED DESCRIPTION OF THE EMBODIMENTSThe Figures (FIGS.) and the following description relate to preferred embodiments by way of illustration only. It should be noted that from the following discussion, alternative embodiments of the structures and methods disclosed herein will be readily recognized as viable alternatives that may be employed without departing from the principles of what is claimed.
Reference will now be made in detail to several embodiments, examples of which are illustrated in the accompanying figures. It is noted that wherever practicable similar or like reference numbers may be used in the figures and may indicate similar or like functionality. The figures depict embodiments of the disclosed system (or method) for purposes of illustration only. One skilled in the art will readily recognize from the following description that alternative embodiments of the structures and methods illustrated herein may be employed without departing from the principles described herein.
The system 100 addresses applications where it is important to ensure a specific individual is authorized to perform a given transaction. A transaction as used herein can include executing a purchase or financial dealing, enabling access to physical and/or digital items, verifying identification or personal information or executing other tasks where it is important to authenticate an individual for use. Generally, the reader 108 wirelessly receives information stored in the PDK 102 that uniquely identifies the PDK 102 and the individual carrying the PDK 102. The reader 108 can also receive a biometric input 104 from the individual. Based on the received information, the reader 108 determines if the transaction should be authorized. Beneficially, the system 100 provides comprehensive authentication without the need for PINs or passwords. Moreover, personal biometric information need not be stored in any local or remote storage database and is only stored on the user's own PDK. Furthermore, in one embodiment, purchase transactions can be efficiently completed without requiring the use of physical credit cards, tokens or other user action beyond initiating the transaction.
The credibility of the system 100 is ensured by the use of the PDK 102 that stores trusted information. The PDK 102 is a compact, portable uniquely identifiable wireless device typically carried by an individual. The PDK 102 stores digital information in a tamper-proof format that uniquely associates the PDK 102 with an individual. Example embodiments of PDKs are described in more detail in U.S. patent application Ser. No. 11/292,330 entitled “Personal Digital Key And Receiver/Decoder Circuit System And Method;” U.S. patent application Ser. No. 11/620,581 entitled “Wireless Network Synchronization Of Cells And Client Devices On A Network;” and U.S. patent application Ser. No. 11/620,577 entitled “Dynamic Real-Time Tiered Client Access”, the entire contents of which are all incorporated herein by reference.
To establish the trust, credibility and confidence of the authentication system, information stored in the PDK 102 is acquired by a process that is trusted, audited and easily verified. The process is ensured by a trusted third-party system, referred to herein as a Notary that administers the acquisition and storage of information in the PDK 102 according to defined security protocols. In one embodiment, the Notary is a system and/or a trusted individual that witnesses the acquisition and storage either in person or remotely. In another embodiment, the Notary comprises trusted hardware that administers the initialization process by an automated system. Thus, once initialized by the trusted process, the PDK 102 can prove that the information it stores is that of the individual. Example embodiments of the initialization process are described in U.S. patent application Ser. No. 11/744,832 (Attorney Docket No. 25000-12784), entitled “Personal Digital Key Initialization and Registration For Secure Transaction”, the entire contents of which are incorporated herein by reference.
The reader 108 wirelessly communicates with the PDK 102 when the PDK 102 is within a proximity zone of the reader 108. The proximity zone can be, for example, several meters in radius and can be adjusted dynamically by the reader 108. Example embodiments of a reader with a dynamically adjustable proximity zone are described in U.S. patent application No. 11/620,600 (Attorney Docket No. 25000-12199), filed Jan. 5, 2007, entitled “Dynamic Cell Size Variation Via Wireless Link Parameter Adjustment”, the entire contents of which are incorporated herein by reference. Thus, in contrast to many conventional RF ID devices, the reader 108 can detect and communicate with the PDK 102 without requiring the owner to remove the PDK 102 from his/her pocket, wallet, purse, etc. Also, in contrast to many conventional RFID devices, the reader 108 and PDK 102 are designed to operate in a dense client environment - not on a one-by-one reader to client-held device basis. Example embodiments of a reader that provides dense, coordinated system operation is described in U.S. patent application Ser. No. 11/620,581 (Attorney Docket No. 25000-12194), filed Jan. 5, 2007, entitled “Wireless Network Synchronization Of Cells And Client Devices On A Network”, the entire contents of which are incorporated herein by reference. Generally, the reader 108 receives uniquely identifying information from the PDK 102 and initiates an authentication process for the individual carrying the PDK 102. In one embodiment, the reader 108 is adapted to receive a biometric input 104 from the individual. The biometric input 104 comprises a representation of physical or behavioral characteristics unique to the individual. For example, the biometric input 104 can include a fingerprint, a palm print, a retinal scan, an iris scan, a photograph, a signature, a voice sample or any other biometric information such as DNA, RNA or their derivatives that can uniquely identify the individual. The reader 108 compares the biometric input 104 to information received from the PDK 102 to determine if a transaction should be authorized. Alternatively, the biometric input 104 can be obtained by a biometric reader on the PDK 102 and transmitted to the reader 108 for authentication. In an additional alternative embodiment, some or all of the authentication process can be performed by the PDK 102 instead of the reader 108.
The reader 108 is further communicatively coupled to the network 110 in order to receive and/or transmit information to remote databases for remote authentication. In an alternative embodiment, the reader 108 includes a non-volatile data storage that can be synchronized with one or more remote databases 112 or registries 114-116. Such an embodiment relaxes the requirement for a continuous connection to the network 110 and allows the reader 108 to operate in a standalone mode and for the local data storage to be updated when a connection is available. For example, a standalone reader 108 can periodically download updated registry entries and perform authentication locally without any remote lookup.
The customer interface devices 120 facilitate in the process of automated order processing. In one embodiment, the customer interface device 120 allows a customer to initiate an order by simply providing a biometric sample. In one embodiment, a customer can initiate an order via the customer interface device 120 with a simple finger swipe. In another embodiment, the customer can initiate, complete and pay for the order by simply providing a biometric sample, such as a finger swipe. In yet another embodiment, the customer need only confirm and/or select his or her order by providing a biometric sample, such as a finger swipe. More details describing the components and functionality of the customer interface device 120 is provided below with reference to
The merchant interface device 130 allows customers to automatically and securely complete order transactions with a simple step of providing a biometric sample. In one embodiment, the merchant interface device 130 allows customers to automatically and securely complete order transactions with a simple swipe of the finger. In another embodiment, the merchant interface device 130 displays customers' orders to be prepared by the merchant. In one embodiment, the customers' orders are displayed in a list in order of when the order what placed. More details describing the components and functionality of the merchant interface device 130 is provided below with reference to
The transactions server 140 includes software or routines for automating the process of entering and fulfilling an order. The transactions server 140 facilitates automatic order processing and payment procedures. The transactions server 140 is coupled to and adapted to communicate with the customer interface device 120, the merchant interface device 130 and the reader 108 via the network 110. The transaction server 140 is also coupled to the registries 114-116 for payment information and verification. More details describing the components and functionality of the transactions server 140 is provided below with reference to
The network 110 provides communication between the reader 108, customer interface device 120, merchant interface device 130, transactions server 140 and the validation database 112, central registry 114 and one or more private registries 116. In alternative embodiments, one or more of these connections may not be present or different or additional network connections may be present. In one embodiment, the network 110 uses standard communications technologies and/or protocols. Thus, the network 110 can include links using technologies such as Ethernet, 802.11, 802.16, integrated services digital network (ISDN), digital subscriber line (DSL), asynchronous transfer mode (ATM), etc. Similarly, the networking protocols used on the network 110 can include the transmission control protocol/Internet protocol (TCP/IP), the hypertext transport protocol (HTTP), the simple mail transfer protocol (SMTP), the file transfer protocol (FTP), etc. The data exchanged over the network 110 can be represented using technologies and/or formats including the hypertext markup language (HTML), the extensible markup language (XML), etc. In addition, all or some of links can be encrypted using conventional encryption technologies such as the secure sockets layer (SSL), Secure HTTP and/or virtual private networks (VPNs). In another embodiment, the entities can use custom and/or dedicated data communications technologies instead of, or in addition to, the ones described above.
The validation database 112 stores additional information that may be used for authorizing a transaction to be processed at the reader 108. For example, in purchase transactions, the validation database 112 is a credit card validation database that is separate from the merchant providing the sale. Alternatively, a different database may be used to validate different types of purchasing means such as a debit card, ATM card or bank account number.
The registries 114-116 are securely-accessible databases coupled to the network 110 that store, among other items, PDK, Notary, and reader information. In one embodiment, the registries 114-116 do not store biometric information. Information stored in the registries can be accessed by the reader 108 via the network 110 for use in the authentication process. There are two basic types of registries illustrated: private registries 116 and the central registry 114. Private registries 116 are generally established and administered by their controlling entities (e.g., a merchant, business authority, or other entity administering authentication). Private registries 116 can be custom configured to meet the specialized and independent needs of each controlling entity. The central registry 114 is a single highly-secured, centrally-located database administered by a trusted third-party organization. In one embodiment, all PDKs 102 are registered with the central registry 114 and may be optionally registered with one or more selected private registries 116. In some embodiments, these registries 114-116 are financial databases for payment processing. In such embodiments, registries 114-116 are financial databases of credit card companies such as AMERICAN EXPRESS™, VISA™ or MASTERCARD™. In alternative embodiments, a different number or different types of registries may be coupled to the network 110.
Turning now to
The memory 210 can be a read-only memory, a once-programmable memory, a read/write memory or any combination of memory types including physical access secured and tamperproof memories. The memory 210 typically stores a unique PDK ID 212 and one or more profiles 220. The PDK ID 212 comprises a public section and a private section of information, each of which can be used for identification and authentication. In one embodiment, the PDK ID 212 is stored in a read-only format that cannot be changed subsequent to manufacture. The PDK ID 212 is used as an identifying feature of a PDK 102 and distinguishes between PDKs 102 in private 116 or Central 114 registry entries. The PDK ID 212 can also be used in basic PDK authentication to ensure that the PDK 102 is a valid device. In one embodiment, the memory 210 also stores a purchase log 290. The purchase log 290 keeps track of the customer's purchases for at a particular merchant's establishment. The data contained in the purchase log 290 can later be used to determine rewards.
The profile fields 220 can be initially empty at the time of manufacture but can be written to by authorized individuals (e.g., a Notary) and/or hardware (e.g., a Programmer). In one embodiment, each profile 220 comprises a profile history 222 and profile data 230. Many different types of profiles 220 are possible. A biometric profile, for example, includes profile data 230 representing physical and/or behavioral information that can uniquely identify the PDK owner. A PDK 102 can store multiple biometric profiles, each comprising a different type of biometric information. In one embodiment, the biometric profile 220 comprises biometric information transformed by a mathematical operation, algorithm, or hash that represents the complete biometric information (e.g., a complete fingerprint scan). In one embodiment, a mathematical hash is a “one-way” operation such that there is no practical way to re-compute or recover the complete biometric information from the biometric profile. This both reduces the amount of data to be stored and adds an additional layer of protection to the user's personal biometric information. In one embodiment, the PDK 102 also stores one or more biometric profile “samples” associated with each biometric profile. The biometric profile sample is a subset of the complete profile that can be used for quick comparisons of biometric data. In one embodiment, the profile samples can be transmitted over a public communication channel or transmitted with a reduced level of encryption while the full biometric profiles are only transmitted over secure channels. In the case of fingerprint authentication, for example, the biometric profile sample may represent only a small portion area of the full fingerprint image. In another embodiment, the fingerprint profile sample is data that describes an arc of one or more lines of the fingerprint. In yet another embodiment, the fingerprint profile sample can be data representing color information of the fingerprint.
In another embodiment, the stored profiles 220 include a PIN profile that stores one or more PINs or passwords associated with the PDK owner. Here, the number or password stored in the PIN profile can be compared against an input provided by the user at the point of transaction to authenticate the user. In one embodiment, a PIN profile sample is also stored with the PIN profile that comprises a subset of the full PIN. For example, a PIN profile sample can be only the first two numbers of the PIN that can be used to quickly compare the stored PIN profile to a PIN obtained at the point of transaction.
In yet another embodiment, the PDK 102 stores a picture profile that includes one or more pictures of the PDK owner. In a picture profile authentication, the picture stored in the PDK 102 is transmitted to a display at the point of transaction to allow an administrator (e.g., a clerk or security guard) to confirm or reject the identity of the individual requesting the transaction. In another embodiment, an image is captured of the individual at the point of transaction and compared to the picture profile by an automated image analysis means. Furthermore, picture profiles could be used along with other personal identification information, for example, in place of conventional passports or drivers licenses to authenticate the identity of an individual and allow for remote identification of individuals. For example, a police officer following a vehicle could obtain an image and identity of the driver while still maintaining a safe distance from the vehicle. In the hospitality industry, a host could greet a guest at the door of a hotel, casino or restaurant and easily recognize the guest by obtaining the guest's picture profile as he/she enters.
In another embodiment, the PDK 102 stores purchase information for participating merchants. The PDK 102 also stores regularly ordered items for a particular merchant. In some embodiments, the regularly ordered items are stored as the customer's favorites.
A registry or database profile typically stores information associating the user with a registry. The registry profile can be used to determine if the individual is associated with the controlling entity for that registry and if different types of transactions are authorized for the individual. A registry profile can further include additional user information for use with the registry. For example, a private registry profile associated with a particular merchant may include a credit card number that the user has selected as a default for that merchant. In one embodiment, a profile can further include spending limits that limits the amount of purchases a user can make with a particular vendor or using a particular profile.
A profile can further include personal identification information such as name, address, phone number, etc., bank information, credit/debit card information, or membership information. This information can be useful for certain types of transactions. For example, with purchases that require delivery, a PDK 102 can automatically transmit address information to the reader 108 at the point of transaction. In one embodiment, a profile can store multiple addresses. At the point of transaction, the reader 108 displays the address options and allows the user to select which address to use.
Generally, some types of profile information (e.g., a biometric profile) can only be acquired during a trusted initialization process that is administered by a trusted Notary. In one embodiment, other secure information such as credit card information is also stored to the PDK in the presence of a Notary. Alternatively, certain types of low-risk information can be added by the user without a Notary, such as, for example a change of address. In another embodiment, once an initial profile has been stored to the PDK 102, a user can add information to the PDK 102 using a Programmer without a Notary through self-authentication. For example, in one embodiment, a PDK 102 that has a stored biometric profile can be “unlocked” by providing a matching biometric input. Then, once unlocked, the user can add additional profiles, credit cards, personal information, etc. to the PDK 102. In another embodiment, the user can make copies of the PDK 102 or move profiles from one PDK 102 to another once the PDK 102 is unlocked.
The profile history 222 includes a programmer ID field 224, a Notary ID 226, and a site ID field 228. The profile history 222 relates to the specific hardware, Notary, and site used at the time the profile data was created and stored to the PDK. Typically each profile 220 stores its specific profile history 222 along with the profile data 230. The profile history 222 can be recalled for auditing purposes at a later time to ensure the credibility of the stored data. In one embodiment, transaction history can also be stored to the PDK memory 210. Here, the PDK 102 stores information associated with any transactions made with the PDK 102 such as the name of the merchant, the purchase amount, credit card used, etc.
The PDK 102 also includes a programmer I/O 240 that provides an interface to a trusted Programmer (not shown). The Programmer comprises trusted hardware that is used to program the memory 210 of the PDK 102. An example embodiment of a Programmer is described in U.S. patent application Ser. No. 11/744,832 (Attorney Docket No. 25000-12784) entitled “Personal Digital Key Initialization and Registration For Secure Transaction”, the entire contents of which are incorporated herein by reference. The programmer I/O 240 can be, for example, a USB interface, serial interface, parallel interface, or any other direct or wireless link for transferring information between the PDK 102 and the Programmer. When coupled to the Programmer, the programmer I/O 240 receives initialization data, registration data or other information to be stored in the memory 210.
The control logic 250 coordinates between functions of the PDK 102. In one embodiment, the control logic 250 facilitates the flow of information between the programmer I/O 240, transceiver 260 and memory 210. The control logic 250 can further process data received from the memories 210, programmer I/O 240 and transceiver 260. Note that the control logic 250 is merely a grouping of control functions in a central architecture, and in other embodiments, the control functions can be distributed between the different modules of the PDK 102. The operation of the control logic will be understood to those skilled in the art based on the description below corresponding to
The transceiver 260 is a wireless transmitter and receiver for wirelessly communicating with a reader 108 or other wireless device. The transceiver 260 can send and receive data as modulated electromagnetic signals. Moreover, the data can be encrypted by the transceiver 260 and transmitted over a secure link. Further, the transceiver 260 can actively send connection requests, or can passively detect connection requests from another wireless source. In one embodiment, the transceiver 260 is used in place of a separate programmer I/O 240 and is used to wirelessly communicate with the Programmer for programming. In one embodiment, the transceiver 260 is adapted to communicate over a range of up to around 5 meters.
Optionally, a PDK 102 can also include a built in biometric reader (not shown) to acquire a biometric input from the user. The biometric input can be used to unlock the PDK 102 for profile updates, or for various types of authentication. For example, in one embodiment, a biometric input is received by the PDK 102 and compared to stored biometric information. Then, if the user is authenticated, the PDK 102 can indicate to the Reader 108 that the user is authenticated and transmit additional information (e.g., a credit card number) needed to complete a transaction.
The biometric capture module 292 comprises a scan pad to capture scan data from a user's fingerprint (e.g., a digital or analog representation of the fingerprint). Other embodiments of the biometric capture module 292 includes retinal scanners, iris scanners, facial scanner, palm scanners, DNA/RNA analyzers, signature analyzers, cameras, microphones, and voice analyzers to capture other identifying biometric data. Using the biometric data, validation module 294 determines whether the user's fingerprint, or other biometric data, matches the stored biometric data from enrollment. Conventional techniques for comparing fingerprints can be used. For example, the unique pattern of ridges and valleys of the fingerprints can be compared. A statistical model can be used to determine comparison results. Validation module 294 can send comparison results to control logic 250 of the PDK 102.
In other embodiments, validation module 294 is configured to capture biometric data for other human characteristics. For example, a digital image of a retina, iris, and/or handwriting sample can be captured. In another example, a microphone captures a voice sample.
Persistent storage 298 persistently stores biometric data from one or more users which can be provided according to specific implementations. In one embodiment, at least some of persistent storage 298 is a memory element that can be written to once but cannot subsequently be altered. Persistent storage 298 can include, for example, a ROM element, a flash memory element, or any other type of non-volatile storage element. Persistent storage 298 is itself, and stores data in, a tamper-proof format to prevent any changes to the stored data. Tamper-proofing increases reliability of authentication because it does not allow any changes to biometric data (i.e., allows reads of stored data, but not writes to store new data or modify existing data). Furthermore, data can be stored in an encrypted form.
In one embodiment, persistent storage 298 also stores the code that is provided by the PDK 102 responsive to successful verification of the user. Further, in some embodiments persistent storage 298 stores other data utilized during the operation of PDK 102. For example, persistent storage 298 can store encryption/decryption keys utilized to establish secure communications links.
An example embodiment of PDK with a biometric reader is described in U.S. patent application Ser. No. 11/314,199 (Attorney Docket No. 25000-11062) to John Giobbi, et al., entitled “Biometric Personal Data Key (PDK) Authentication”, the entire contents of which are incorporated herein by reference.
Turning now to
The RDC 304 provides the wireless interface to the PDK 102. Generally, the RDC 304 wirelessly receives data from the PDK 102 in an encrypted format and decodes the encrypted data for processing by the processor 306. An example embodiment of an RDC is described in U.S. patent application Ser. No. 11/292,330 entitled “Personal Digital Key And Receiver/Decoder Circuit System And Method”, the entire contents of which are incorporated herein by reference. Encrypting data transmitted between the PDK 102 and Reader 108 minimizes the possibility of eavesdropping or other fraudulent activity. In one embodiment, the RDC 304 is also configured to transmit and receive certain types of information in an unencrypted, or public, format.
The biometric reader 302 receives and processes the biometric input 104 from an individual at the point of transaction. In one embodiment, the biometric reader 302 is a fingerprint scanner. Here, the biometric reader 302 includes an image capture device adapted to capture the unique pattern of ridges and valleys in a fingerprint also known as minutiae. Other embodiments of biometric readers 302 include retinal scanners, iris scanners, facial scanner, palm scanners, DNA/RNA analyzers, signature analyzers, cameras, microphones, and voice analyzers. Furthermore, the Reader 108 can include multiple biometric readers 302 of different types. In one embodiment, the biometric reader 302 automatically computes mathematical representations or hashes of the scanned data that can be compared to the mathematically processed biometric profile information stored in the PDK 102.
The processor 306 can be any general-purpose processor for implementing a number of processing tasks. Generally, the processor 306 processes data received by the Reader 108 or data to be transmitted by the Reader 108. For example, a biometric input 104 received by the biometric reader 302 can be processed and compared to the biometric profile 220 received from the PDK 102 in order to determine if a transaction should be authorized. In different embodiments, processing tasks can be performed within each individual module or can be distributed between local processors and a central processor. The processor 306 further includes a working memory for use in various processes such as performing the method of
The network interface 308 is a wired or wireless communication link between the Reader 108 and one or more external databases such as, for example, a validation database 112, the Central Registry 114 or a private registry 116. For example, in one type of authentication, information is received from the PDK 102 at the RDC 304, processed by the processor 306, and transmitted to an external database 112-116 through the network interface 308. The network interface 308 can also receive data sent through the network 110 for local processing by the Reader 108. In one embodiment, the network interface 308 provides a connection to a remote system administrator to configure the Reader 108 according to various control settings.
The I/O port 312 provides a general input and output interface to the Reader 108. The I/O port 312 may be coupled to any variety of input devices to receive inputs such as a numerical or alphabetic input from a keypad, control settings, menu selections, confirmations, and so on. Outputs can include, for example, status LEDs, an LCD, or other display that provides instructions, menus or control options to a user.
The credit card terminal I/O 310 optionally provides an interface to an existing credit card terminal 314. In embodiments including the credit card terminal I/O 310, the Reader 108 supplements existing hardware and acts in conjunction with a conventional credit card terminal 314. In an alternative embodiment, the functions of an external credit card terminal 314 are instead built into the Reader 108. Here, a Reader 108 can completely replace an existing credit card terminal 314.
In one embodiment, a Reader 108 is adapted to detect and prevent fraudulent use of PDKs that are lost, stolen, revoked, expired or otherwise invalid. For example, the Reader 108 can download lists of invalid PDKs 102 from a remote database and block these PDKs 102 from use with the Reader 108. Furthermore, in one embodiment, the Reader 108 can update the blocked list and/or send updates to remote registries 114-116 or remote Readers 108 upon detecting a fraudulently used PDK 102. For example, if a biometric input 104 is received by the Reader 108 that does not match the biometric profile received from the PDK 102, the Reader 108 can obtain the PDK ID 212 and add it to a list of blocked PDKs. In another embodiment, upon detecting fraudulent use, the Reader 108 can send a signal to the PDK 102 that instructs the PDK 102 to deactivate itself. The deactivation period can be, for example, a fixed period of time, or until the rightful owner requests re-activation of the PDK 102. In yet another embodiment, the Reader 108 can send a signal instructing the fraudulently obtained PDK 102 to send beacon signals indicating that the PDK 102 is a stolen device. Here, a stolen PDK 102 can be tracked, located and recovered by monitoring the beacon signals. In one embodiment, the Reader 108 stores biometric or other identifying information from an individual that attempts to fraudulently use a PDK 102 so that the individual's identity can be determined.
Generally, the Reader 108 is configured to implement at least one type of authentication prior to enabling a transaction. In many cases, multiple layers of authentication are used. A first layer of authentication, referred to herein as “device authentication”, begins any time a PDK 102 moves within range of a Reader 108. In device authentication, the Reader 108 and the PDK 102 each ensure that the other is valid based on the device characteristics, independent of any profiles stored in the PDK 102. In some configurations, when fast and simple authentication is desirable, only device authentication is required to initiate the transaction. For example, a Reader 108 may be configured to use only device authentication for low cost purchases under a predefined amount (e.g., $25). The configuration is also useful in other types of low risk transactions where speed is preferred over additional layers of authentication.
Other configurations of the Reader 108 require one or more additional layers of authentication, referred to herein as “profile authentication” based on one or more profiles stored in the PDK 102. Profile authentication can include, for example, a biometric authentication, a PIN authentication, a photo authentication, a registry authentication, etc. or any combination of the above authentication types. Profile authentications are useful when a more exhaustive authentication process is desired, for example, for high purchase transactions or for enabling access to classified assets.
The memory 406 includes an automated order application 430 and a rewards presentation application 436. In one embodiment, the automated order application 430 enables the customer interface device 120A to communicate with the transactions server 140. In another embodiment, the automated order application 430 processes information and data received from the readers 420 and various modules and servers of the transactions server 140. The rewards presentation application 436 is adapted to communicate with the rewards processing module 1412 of the transactions server 140 to display the status of the customer's rewards on the display 418 of the customer interface device 120A. More details describing the functionality of these applications 430, 436 is provided below with reference to
The storage device 408 is any device capable of holding data, like a hard drive, compact disk read-only memory (CD-ROM), DVD, or a solid-state memory device. The memory 406 holds instructions and data used by the processor 402. The pointing device 414 may be a mouse, track ball, or other type of pointing device, and is used in combination with the keyboard 410 to input data into the customer interface device 120A. The graphics adapter 412 displays images and other information on the display 418. The network adapter 416 couples the customer interface device 120A to a local or wide area network.
As is known in the art, a customer interface device 120A can have different and/or other components than those shown in
As is known in the art, the customer interface device 120A is adapted to execute computer program modules for providing functionality described herein. As used herein, the term “module” refers to computer program logic utilized to provide the specified functionality. Thus, a module can be implemented in hardware, firmware, and/or software. In one embodiment, program modules are stored on the storage device 408, loaded into the memory 406, and executed by the processor 402.
Embodiments of the entities described herein can include other and/or different modules than the ones described here. In addition, the functionality attributed to the modules can be performed by other or different modules in other embodiments. Moreover, this description occasionally omits the term “module” for purposes of clarity and convenience.
The memory 406 in
As shown in
The memory 506 includes an order completion application 530 and a rewards presentation application 532. In one embodiment, the order completion application 530 enables the merchant interface device 130A to communicate with the transactions server 140. In another embodiment, the order completion application 530 processes information and data received from the readers 520 and various modules and servers transactions server 140. The rewards presentation application 532 is adapted to communicate with the rewards processing module 1412 of the transaction server 140 in order to present the status of a customer's rewards on the display 518 of the merchant interface device 130A. More details describing the functionality of these applications 530, 532 is provided below with reference to
The storage device 508 is any device capable of holding data, like a hard drive, compact disk read-only memory (CD-ROM), DVD, or a solid-state memory device. The memory 506 holds instructions and data used by the processor 502. The pointing device 514 may be a mouse, track ball, or other type of pointing device, and is used in combination with the keyboard 510 to input data into the merchant interface device 130A. The graphics adapter 512 displays images and other information on the display 518. The network adapter 516 couples the merchant interface device 130A to a local or wide area network.
As is known in the art, a merchant interface device 130A can have different and/or other components than those shown in
As is known in the art, the merchant interface device 130A is adapted to execute computer program modules for providing functionality described herein. As used herein, the term “module” refers to computer program logic utilized to provide the specified functionality. Thus, a module can be implemented in hardware, firmware, and/or software. In one embodiment, program modules are stored on the storage device 508, loaded into the memory 506, and executed by the processor 502.
As shown in
Embodiments of the entities described herein can include other and/or different modules than the ones described here. In addition, the functionality attributed to the modules can be performed by other or different modules in other embodiments. Moreover, this description occasionally omits the term “module” for purposes of clarity and convenience.
In step 604, a device authentication is performed. Here, the Reader 108 establishes if the PDK 102 is a valid device and PDK 102 establishes if the Reader 108 is valid. Furthermore, device authentication determines if the PDK is capable of providing the type of authentication required by the Reader 108.
An example embodiment of a method for performing 604 device authentication is illustrated in
Turning back to
The method next determines 610 whether profile authentication is required based on the configuration of the Reader 108, the type of transaction desired or by request of a merchant or other administrator. If the Reader 108 configuration does not require a profile authentication in addition to the PDK authentication, then the Reader 108 proceeds to complete the transaction for the PDK 102. If the Reader 108 does require profile authentication, the profile authentication is performed 612 as will be described below with references to
Turning now to
In a first configuration, a trigger is required to continue the process because of the type of authentication being used. For example, in biometric authentication, the authentication process cannot continue until the Reader detects a biometric contact and receives biometric information. It is noted that biometric contact is not limited to physical contact and can be, for example, the touch of a finger to a fingerprint scanner, the positioning of a face in front of a facial or retinal scanner, the receipt of a signature, the detection of a voice, the receipt of a DNA sample, RNA sample, or derivatives or any other action that permits the Reader 108 to begin acquiring the biometric input 104. By supplying the biometric contact, the user indicates that the authentication and transaction process should proceed. For example, a PDK holder that wants to make a withdrawal from an Automated Teller Machine (ATM) equipped with a Reader 108 initiates the withdrawal by touching a finger to the Reader 108. The ATM then begins the transaction process for the withdrawal.
In a second configuration, some other user action is required as a trigger to proceed with the transaction even if the authentication process itself doesn't necessarily require any input. This can be used for many purchasing transactions to ensure that the purchase is not executed until intent to purchase is clear. For example, a Reader 108 at a gas station can be configured to trigger the transaction when a customer begins dispensing gas. At a supermarket, a Reader 108 can be configured to trigger the transaction when items are scanned at a checkout counter.
In a third configuration, no trigger is used and the Reader 108 automatically completes the remaining authentication/transaction with no explicit action by the user. This configuration is appropriate in situations where the mere presence of a PDK 102 within range of the Reader 108 is by itself a clear indication of the PDK owner's desire to complete a transaction. For example, a Reader 108 can be positioned inside the entrance to a venue hosting an event (e.g., a sporting event, a concert, or a movie). When a PDK owner walks through the entrance, the Reader 108 detects the PDK 102 within range, authenticates the user, and executes a transaction to purchase an electronic ticket for the event. In another embodiment, the electronic ticket can be purchased in advance, and the Reader 108 can confirm that the user is a ticket holder upon entering the venue. Other examples scenarios where this configuration is useful include boarding a transportation vehicle (e.g., a train, bus, airplane or boat), entering a hotel room, or accessing secure facilities or other assets. Thus, if no trigger is required, the process next performs 814 the requested profile authentication tests.
If a trigger is required, the Reader monitors 810 its inputs (e.g., a biometric reader, key pad, etc.) and checks for the detection 812 of a trigger. If the required trigger is detected, the process continues to perform 814 one or more profile authentication test.
Referring first to
Furthermore, in one embodiment, scanning 904 also includes obtaining a biometric input sample from the biometric input according to the same function used to compute the biometric profile sample stored in the PDK 102. Optionally, the Reader 108 receives 908 a biometric profile sample from the PDK 102 and determines 910 if the biometric profile sample matches the biometric input sample. If the biometric profile sample does not match the input sample computed from the scan, the profile is determined to be invalid 918. If the biometric profile sample matches, the full biometric profile 912 is received from the PDK 102 to determine 914 if the full biometric profile 912 matches the complete biometric input 104. If the profile 912 matches the scan, the profile 912 is determined to be valid 920, otherwise the profile 912 is invalid 918. It is noted that in one embodiment, steps 908 and 910 are skipped and only a full comparison is performed.
It will be apparent to one of ordinary skill that in alternative embodiments, some of the steps in the biometric profile authentication process can be performed by the PDK 102 instead of the Reader 108 or by an external system coupled to the Reader 108. For example, in one embodiment, the biometric input 104 can be scanned 904 using a biometric reader built into the PDK 102. Furthermore, in one embodiment, the steps of computing the mathematical representation or hash of the biometric input 104 and/or the steps of comparing the biometric input 104 to the biometric profile can be performed by the PDK 102, by the Reader 108, by an external system coupled to the Reader 108, or by any combination of the devices. In one embodiment, at least some of the information is transmitted back and forth between the PDK 102 and the Reader 108 throughout the authentication process. For example, the biometric input 104 can be acquired by the PDK 102, and transmitted to the Reader 108, altered by the Reader 108, and sent back to the PDK 102 for comparison. Other variations of information exchange and processing are possible without departing from the scope of the invention. The transfer of data between the PDK 102 and the Reader 108 and/or sharing of processing can provide can further contribute to ensuring the legitimacy of each device.
As illustrated, the accumulated PDK data 1130 includes one or more differentiation metrics from each valid PDK 102 within range of the Reader 108. The differentiation metrics can include any information that can be used by the Reader 108 to determine which PDK 102 should be associated with the authentication and/or transaction request. According to various embodiments, differentiation metrics can include one or more of distance metrics 1132, location metrics 1134 and duration metrics 1136.
In one embodiment, a distance metric 1132 indicates the relative distance of a PDK 102 to the Reader 108. This information is useful given that a PDK 102 having the shortest distance to the Reader 108 is generally more likely to be associated with a received authentication trigger (e.g., a biometric input, a PIN input or a transaction request). The distance metrics 1132 can include, for example, bit error rates, packet error rates and/or signal strength of the PDKs 102. These communication measurements can be obtained using a number of conventional techniques that will be apparent to those of ordinary skill in the art. Generally, lower error rates and high signal strength indicate the PDK 102 is closer to the Reader 108.
Location metrics 1134 can be used to determine a location of a PDK 102 and to track movement of a PDK 102 throughout an area. This information can be useful in determining the intent of the PDK holder to execute a transaction. For example, a PDK holder that moves in a direct path towards a cashier and then stops in the vicinity of the cashier is likely ready to make a purchase (or may be waiting in line to make a purchase). On the other hand, if the PDK moves back and forth from the vicinity of a cashier, that PDK holder is likely to be browsing and not ready to make a purchase. Examples of systems for determining location metrics are described in more detail below with reference to
The differentiation metrics can also include duration metrics 1136 that tracks the relative duration a PDK 102 remains within the proximity zone 1002. Generally, the PDK 102 with the longest time duration within the proximity zone 1002 is most likely to be associated with the authentication request. For example, if the Reader 108 is busy processing a purchasing transaction at a cashier and another PDK 102 has a long duration within the proximity zone 1002, it is likely that the user is waiting in line to make a purchase. In one embodiment, the Reader 108 tracks duration 1136 by starting a timer associated with a PDK 102 when the PDK 102 enters the proximity zone 1002 and resetting the time to zero when the PDK exists. As another example, the Reader 108 tracks the duration when a PDK of a doctor enters the proximity zone of a patient's room. A long duration of the doctor's PDK within the proximity zone can provide evidence that the doctor is spending an adequate amount of time examining the patient. On the other hand, a short duration of the doctor's PDK within the proximity zone can provide evidence that the doctor just merely stopped by and did not perform any thorough examination. This information is useful in monitoring patient treatment and provider performance to help ensure quality patient care.
In one embodiment, the Reader 108 can also receive and buffer profile samples 1138 prior to the start of a profile authentication instead of during the authentication process as described in
Because profile samples 1138 only comprise a subset of the profile information, in one embodiment, the samples can be safely transmitted over a public channel without needing any encryption. In another embodiment, the profile samples 1138 are transmitted with at least some level of encryption. In yet another embodiment, some of the data is transmitted over a public communication channel and additional data is transmitted over a secure communication channel. In different configurations, other types of profile information can be accumulated in advance. For example, in one embodiment, a photograph from a picture profile can be obtained by the Reader 102 during the data accumulation phase 1102. By accumulating the profile sample 1138 or other additional information in advance, the Reader 108 can complete the authentication process more quickly because it does not wait to receive the information during authentication. This efficiency becomes increasingly important as the number of PDKs 102 within the proximity zone 1002 at the time of the transaction becomes larger.
The PDK accumulation phase 1102 continues until a trigger (e.g., detection of a biometric input) is detected 1104 to initiate a profile authentication process. If a biometric input is received, for example, the Reader 108 computes a mathematical representation or hash of the input that can be compared to a biometric profile and computes one or more input samples from the biometric input. It is noted that in alternative embodiments, the process can continue without any trigger. For example, in one embodiment, the transaction can be initiated when a PDK 102 reaches a predefined distance from the Reader 108 or when the PDK 102 remains within the proximity zone 1002 for a predetermined length of time.
The process then computes a differentiation decision 1106 to determine which PDK 102a-d should be associated with the authentication. In one embodiment, the Reader 108 computes a differentiation result for each PDK using one or more of the accumulated data fields 1130. For example, in one embodiment, the differentiation result is computed as a linear combination of weighted values representing one or more of the differentiation metrics. In another embodiment, a more complex function is used. The differentiation results of each PDK 102 are compared and a PDK 102 is selected that is most likely to be associated with the transaction.
In another embodiment, for example, in a photo authentication, the differentiation decision can be made manually by a clerk, security guard, or other administrator that provides a manual input 1112. In such an embodiment, a photograph from one or more PDKs 102 within the proximity zone 1002 can be presented to the clerk, security guard, or other administrator on a display and he/she can select which individual to associate with the transaction. In yet another configuration, the decision is made automatically by the Reader 108 but the clerk is given the option to override the decision.
An authentication test 1108 is initiated for the selected PDK 102. The authentication test 908 can include one or more of the processes illustrated in
If the authentication test 1108 indicates a valid profile, the transaction is completed 1110 for the matching PDK 102. If the authentication test 1108 determines the profile is invalid, a new differentiation decision 1106 is made to determine the next mostly likely PDK 102 to be associated with the transaction. The process repeats until a valid profile is found or all the PDKs 102 are determined to be invalid.
Turning now to
Another embodiment of location tracking is illustrated in
The PDK initialization module 1402 includes software or routines for initializing a PDK for use in the system 100. In one embodiment, the PDK initialization module 1402 is adapted to communicate with the customer interface device 150 via the network 110. In another embodiment, the PDK initialization module 1402 is adapted to communicate with the merchant interface device 130 via the network 110. The PDK initialization module 1402 facilitates the uploading of new customer information, such as biometric information and profile information, including payment information, to a new PDK. The PDK initialization module 1402 sends verification data to the merchant interface device 130. The PDK initialization module 1402 is also coupled to the customer database 1410 and sends some of the new customer information, such as profile information and payment information to the customer database 1410 for storage therein. More details describing the process performed by the PDK initialization module 1402 is provided below with reference to
The data update module 1404 includes software or routines for updating PDK 102 data to the customer database 1410. The data update module 1404 is adapted to communicate with the reader 108 via the network 110 and is coupled to the customer database 1410. The data update module 1404 receives PDK 102 information, including customer information, from the reader 108 and uploads new PDK 102 information to the customer database 1410. The data update module 1404 facilitates the maintenance of current PDK information within the system 100. More details describing the process performed by the data update module 1404 is provided below with reference to
The order processing module 1406 includes software or routines for automating the process of entering customer orders in system 100. The order processing module 1406 is adapted to communicate with the customer interface device 120 via the network 110 and is coupled to the order completion module 1408, customer database 1410 and rewards processing module 1412. The order processing module 1406 processes data received from the customer interface device 120 and obtains data from the customer's PDK in order to process the orders. In some embodiments, the order processing module 1406 obtains data from the customer database 1410 in order to process the orders. The order processing module 1406 also sends order information to the rewards processing module 1412 in order to enable the determination of customer rewards based on order activity. The order processing module 1406 also sends order information to the order completion module 1408 in order to complete such orders. More details describing the process performed by the order processing module 1406 is provided below with reference to
The order completion module 1408 includes software or routines for automating the process of completing customer orders in system 100. The order completion module 1408 is adapted to communicate with the merchant interface device 130 via the network 110 and is coupled to the order processing module 1406 and customer database 1408. In some embodiments, the order completion module 1408 is adapted to communicate with the customer interface device 120. In one embodiment, the order completion module 1408 is also coupled to the rewards processing module 1412. The order completion module 1406 receives confirmed order information from the order processing module 1406 and sends completed order information to be displayed in the merchant interface device 130. In one embodiment, the order completion module 1406 receives confirmed order information from the order processing module 1406 and sends completed order information to be displayed in the customer interface device 120. In one embodiment, the order completion module 1408 sends order information to the rewards processing module 1412 in order to enable the determination of customer rewards based on order completion activity. More details describing the process performed by the order completion module 1408 is provided below with reference to
The customer database 1410 is coupled to and adapted to communicate with the PDK initialization module 1402, the data update module 1404, the order processing module 1406, the order completion module 1408 and the rewards processing module 1412. The customer database 1410 stores PDK 102 information as well as customer information associated with the PDKs 102. In one embodiment, the customer database 1410 is adapted to communicate with the validation database 112 and registries 114, 116a, 116b. In such embodiments, data from the customer database 1410 is replicated to the validation database 112 and registries 114, 116a, 116b to ensure maintenance of current customer information within the system 1 00.
The rewards processing module 1412 includes software or routines for processing and recording customer activity for the purposes of determining customer rewards. The rewards processing module 1412 is coupled to the order processing module 1406, the order completion module 1408 and the customer database 1410. The rewards processing module 1412 receives order information from the order processing module 1406 and determines customer rewards based on order activity. In one embodiment, the rewards processing module 1412 receives order information from the order completion module 1408 and determines customer rewards based on order completion activity. The rewards processing module 1412 sends reward information to the customer database 1014 to be stored therein. More details describing the process performed by the rewards processing module 1412 is provided below with reference to
Embodiments of the entities described herein can include other and/or different modules than the ones described here. In addition, the functionality attributed to the modules can be performed by other or different modules in other embodiments. Moreover, this description occasionally omits the term “module” for purposes of clarity and convenience
The reader 108 then reads the customer's information from the PDK 102, such as customer name and favorite orders, and sends it to the transactions server 140. The data update module 1404 of the transaction server 140 uploads 1504 current PDK information received from the reader 108 to the customer database 1410 of the transactions server 140. Connection is then established 1506 between the reader 420 of the customer interface device 120 and the customer's PDK 102 and the customer's PDK 102 is authenticated 1506 be the reader 420. The order processing module 1406 obtains the customer information from the customer's PDK and processes 1508 the customer's order. In some embodiments, the rewards processing module 1412 processes 1510 rewards based on the customer's order. The processed order is sent to the order completion module 1408 and the transaction is completed 1512. In some embodiments, the customer's PDK establishes another connection between the reader 520 of the merchant interface device 130 in order to complete the order. More details describing the specific steps of this general process 1500 is provided below with reference to
In some embodiments, a customer can add or edit information with the process described above. For example, if a customer receives a gift card for a particular merchant, the customer can add the information detailing the merchant associated with the gift card and the amount of the gift card and that information is loaded onto the customer's PDK 102 for later use at the merchant's establishment. Connection is established 1601 between the reader 420 and the customer's PDK 102 and the customer's PDK 102 is authenticated. Optionally, biometric sample is requested 1602. A sample is received via the reader 420 of the customer interface device 120C. The customer interface device 120C then requests 1606 customer profile information. During this step 1606, the customer can edit already-existing information. The customer interface device 120C receives 1608 the customer profile information via the input devices of the customer interface device 120C, such as the keyboard 410, pointing device 414 and/or display 418. Next, the customer interface device 120C requests 1610 payment information, such as a credit card number, debit card number, or gift card authorization number, along with other identifying and authorization information of the customer's payment method. During this step 1610, the gift card information is entered. The customer interface device 120C receives 1612 the payment information via the reader 420, keyboard 410, pointing device 414 and/or display 418 of the customer interface device 120C. Once all the data is received, the information update application 450 verifies 1614 the data and uploads the information, including the gift card information, to the customer's PDK 102. The PDK 102 is re-initialized 1616 with current information and ready to be used.
In step 1704, a device authentication is performed. Here, the Reader 108 establishes if the PDK 102 is a valid device and PDK 102 establishes if the Reader 108 is valid. Furthermore, device authentication determines if the PDK is capable of providing the type of authentication required by the Reader 108. An example embodiment of a method for performing 604 device authentication is illustrated in
Turning now to
The process begins with the Reader 420 of the customer interface device 120 sending 1804 out a beacon signal to start the proximity authentication process. The beacon signal is preferably repeatedly sent such as at a periodic interval. The PDK 102 monitors 1802 for a beacon signal from any Reader 420 in range. If there is no such signal then the PDK 102 is outside the proximity range of any Reader 420. Once the PDK 102 detects a beacon, the PDK 102 responds by sending information to set up a secure communication channel. This process has been described above with reference to
It should be noted that the biometric authentication described above is performed without the requirement of an external database containing biometric data to be searched. The security of maintaining all biometric data to be searched within the user-owned and carried PDK 102 is apparent, as is the vastly improved speed in searching only those immediately surrounding PDK's for a match. Additionally, it will be noticed that in order to complete the transaction, the person possessing the PDK 102 containing the secure data must provide the Reader 420 with a scan (or sample) of biologically identifying material. The importance of the foregoing to the tracking and apprehension of anyone fraudulently attempting to use another person's PDK will be understood by those skilled in the art, as well as extensions of this technology to act as an aid in law enforcement in the detection, tracking and retrieval of lost, stolen or fraudulently obtained PDK's.
Next, once biometric authentication is established, the transaction is initiated 1818 and order processing is performed 1820. Turning now to
Turning back to
The process begins with the reader 520 of the merchant interface device 130 sending 2004 out a beacon signal to start the proximity authentication process. The beacon signal is preferably repeatedly sent such as at a periodic interval. The PDK 102 monitors 2002 for a beacon signal from any reader 520 in range. If there is no such signal then the PDK 102 is outside the proximity range of any reader 520. Once the PDK 102 detects a beacon, the PDK 102 responds by sending information to set up a secure communication channel. This process has been described above with reference to
After step 2010, the method continues with the user positioning 2012 his body for a biometric read. In one embodiment, this is swiping his finger over a reader 108. For the other type of biometric scanning, the user need only perform the affirmative act of allowing his body to be scanned such as for a retinal, face, palm, DNA analysis etc. Once the user has performed then inputting step 2012, the Reader 520 receives 2014 the biometric input. In this embodiment, the biometric reader is part of Reader 520 so receipt is automatic. However, where the biometric reader is on the PDK 102, the PDK 102 wirelessly transmits the biometric input to the Reader 520 that in turn receives it. Biometric authentication is then performed 2016 according to the various embodiments illustrated in
It should be noted that the biometric authentication described above is performed without the requirement of an external database containing biometric data to be searched. The security of maintaining all biometric data to be searched within the user-owned and carried PDK 102 is apparent, as is the vastly improved speed in searching only those immediately surrounding PDK's for a match. Additionally, it will be noticed that in order to complete the transaction, the person possessing the PDK 102 containing the secure data must provide the Reader 420 with a scan (or sample) of biologically identifying material. The importance of the foregoing to the tracking and apprehension of anyone fraudulently attempting to use another person's PDK will be understood by those skilled in the art, as well as extensions of this technology to act as an aid in law enforcement in the detection, tracking and retrieval of lost, stolen or fraudulently obtained PDK's. Next, once biometric authentication is established, the order completion may be performed 2020 by the order completion module 1408 of the transactions server 140.
Once the transaction is completed 2020 the order completion module 1408 of the transactions server 140 sends 2022 the transaction status to the merchant interface device 130 and the merchant interface device 130 presents 2024 the transaction status on the display 518 of the merchant interface device 130. For example, the display 518 of the merchant interface device 130 may display “Order Complete. Thank you,” or “Order Approved. Thank you.” indicating that the order completion process has been approved and completed and the customer can receive their order. Finally, the customer's PDK 102 receives 2026 and stores that transaction status.
According to one embodiment, order processing and order completion is performed by the customer interface device 120. In such embodiments, steps 1802 to 1820 remain the same. After step 1820, since connection is already established and authentication is already performed, the order completed by the order completion module 1408 of the transactions server 140 sends 2022 the transaction status to the customer interface device 120 and the transaction status is displayed 2024 on the display 418 of the customer interface device 120. The customer's PDK receives 2026 and stores the transaction status.
In some embodiments, biometric input is not required. In such embodiments, another form of confirmation may be required, such as selecting “Yes” to continue to process the order or asking a merchant to “confirm” that the identity of the customer.
Turning to
The method continues with the user positioning 2120 his body for a biometric read. In one embodiment, this is swiping his finger over a reader 108. In an embodiment where biometric input is not required, the transaction server 140 requests confirmation and the request is displayed on the customer interface device 120. Once the user has performed then inputting step 2021, the Reader 420 receives 2122 the biometric input. In this embodiment, the biometric reader is part of Reader 420 so receipt is automatic. However, where the biometric reader is on the PDK 102, the PDK 102 wirelessly transmits the biometric input to the Reader 420 that in turn receives it. Biometric authentication is then performed 1816 according to the various embodiments illustrated in
Next, once biometric authentication is established, order completion is performed 2020 and the transaction status is sent 2128 to the customer interface device 120. Once the transaction status is sent 2128, the customer interface device 120 presents 2130 the transaction status on the display 418 of the customer interface device 120. For example, the display 418 of the customer interface device 120 may display “Order Complete. Thank you,” or “Order Complete. Please Proceed to Register,” indicating that the order entry process has been completed and the customer can proceed to the next step of completing and receiving their order. Finally, the customer's PDK 102 receives 2132 and stored that transaction status.
In one embodiment, the rewards processing module 1412 determines the appropriate reward to apply by referring to a look-up table (not shown). For example, the look-up table may have a list of items eligible for specific rewards and if the customer has purchased a certain item on the table, that specific reward is applied.
The order in which the steps of the methods of the present invention are performed is purely illustrative in nature. The steps can be performed in any order or in parallel, unless otherwise indicated by the present disclosure. The methods of the present invention may be performed in hardware, firmware, software, or any combination thereof operating on a single computer or multiple computers of any type. Software embodying the present invention may comprise computer instructions in any form (e.g., source code, object code, interpreted code, etc.) stored in any computer-readable storage medium (e.g., a ROM, a RAM, a magnetic media, a compact disc, a DVD, etc.). Such software may also be in the form of an electrical data signal embodied in a carrier wave propagating on a conductive medium or in the form of light pulses that propagate through an optical fiber.
While particular embodiments of the present invention have been shown and described, it will be apparent to those skilled in the art that changes and modifications may be made without departing from this invention in its broader aspect.
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 embodiments may be described using the expression “coupled” and “connected” along with their derivatives. It should be understood that these terms are not intended as synonyms for each other. For example, some embodiments may be described using the term “connected” to indicate that two or more elements are in direct physical or electrical contact with each other. In another example, some embodiments may be described using the term “coupled” to indicate that two or more elements are in direct physical or electrical contact. The term “coupled,” however, may also mean that two or more elements are not in direct contact with each other, but yet still co-operate or interact with each other. The embodiments are not limited in this context.
As used herein, the terms “comprises,” “comprising,” “includes,” “including,” “has,” “having” or any other variation thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, article, or apparatus that comprises a list of elements is not necessarily limited to only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Further, unless expressly stated to the contrary, “or” refers to an inclusive or and not to an exclusive or. For example, a condition A or B is satisfied by any one of the following: A is true (or present) and B is false (or not present), A is false (or not present) and B is true (or present), and both A and B are true (or present).
In addition, use of the “a” or “an” are employed to describe elements and components of the embodiments herein. This is done merely for convenience and to give a general sense of the invention. This description should be read to include one or at least one and the singular also includes the plural unless it is obvious that it is meant otherwise
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 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 can be specially constructed for the required purposes, or it can comprise a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program can 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 modules presented herein are not inherently related to any particular computer or other apparatus. Various general-purpose systems can be used with programs in accordance with the teachings herein, or it may prove convenient to construct more specialized apparatuses to perform the method steps. The required structure for a variety of these systems will appear from the description below. 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 can be used to implement the teachings of the invention as described herein. Furthermore, as will be apparent to one of ordinary skill in the relevant art, the modules, features, attributes, methodologies, and other aspects of the invention can be implemented as software, hardware, firmware or any combination of the three. Of course, wherever a component of the present invention is implemented as software, the component can be implemented as a standalone program, as part of a larger program, as a plurality of separate programs, as a statically or dynamically linked library, as a kernel loadable module, as a device driver, and/or in every and any other way known now or in the future to those of skill in the art of computer programming. Additionally, the present invention is in no way limited to implementation in any specific operating system or environment.
It will be understood by those skilled in the relevant art that the above-described implementations are merely exemplary, and many changes can be made without departing from the true spirit and scope of the present invention.
Upon reading this disclosure, those of skill in the art will appreciate still additional alternative structural and functional designs for a system and a process for automating order processing through the disclosed principles herein. Thus, while particular embodiments and applications have been illustrated and described, it is to be understood that the disclosed embodiments are not limited to the precise construction and components disclosed herein. Various modifications, changes and variations, which will be apparent to those skilled in the art, may be made in the arrangement, operation and details of the method and apparatus disclosed herein without departing from the spirit and scope defined in the appended claims.
Claims
1. A method executable by at least one processor of at least one computer for electronic order processing, the method comprising:
- receiving an input that a personal digital key is within a predetermined range, the predetermined range associated with a physical location of a merchant, the personal digital key associated with a first user and integrated into a mobile computing and communication device;
- wirelessly receiving a set of data including biometric data of the first user from the personal digital key;
- authenticating the personal digital key based on the received set of data;
- authenticating a first biometric sample provided by the first user against the received set of data;
- responsive to authenticating the first biometric sample provided by the first user against the received set of data, receiving, from the personal digital key within the predetermined range associated with the physical location of the merchant, a favorite order associated with the merchant, the favorite order stored on the personal digital key;
- determining an initial order based on the favorite order;
- causing presentation, on a display of the mobile computing and communication device, of the initial order;
- causing presentation, on the display of the mobile computing and communication device, of a prompt to confirm the initial order;
- authenticating a second biometric sample provided by the first user against the received set of data;
- responsive to authenticating the second biometric sample provided by the first user against the received set of data, receiving, from the mobile computing and communication device, a communication confirming intent to complete an order of the initial order; and
- subsequent to receiving the communication confirming intent to complete the order of the initial order, fulfilling the order.
2. The method of claim 1, comprising processing rewards based on the order.
3. The method of claim 2, wherein processing the rewards further comprises maintaining a rewards count.
4. The method of claim 1, comprising sending the order for display.
5. The method of claim 1, further comprising:
- subsequent to authenticating the second biometric sample against the received set of data, receiving payment information.
6. The method of claim 1, comprising sending the order for display on a merchant interface device.
7. The method of claim 1, wherein fulfilling the order includes receiving a payment selection.
8. The method of claim 1, comprising storing the favorite order from the personal digital key, including customer information in a customer database.
9. The method of claim 1, wherein the first biometric sample provided by the first user comprises at least one of a fingerprint scan, a retinal scan, an iris scan, a facial scan, a palm scan, a DNA analysis, a signature analysis, and a voice analysis.
10. The method of claim 1, comprising establishing a secure communication channel between the personal digital key and a reader, and wherein a profile is sent from the personal digital key to the reader.
11. The method of claim 1, wherein the second biometric sample provided by the first user comprises at least one of a fingerprint scan, a retinal scan, an iris scan, a facial scan, a palm scan, a DNA analysis, a signature analysis, and a voice analysis.
12. The method of claim 1, further comprising:
- displaying a request for the second biometric sample on a customer interface device.
13. The method of claim 1, further comprising:
- displaying a request for the first biometric sample on the mobile computing and communication device.
14. The method of claim 1, wherein the first biometric sample is received and authenticated at the personal digital key.
15. The method of claim 1, further comprising:
- displaying a request for the second biometric sample on the mobile computing and communication device.
16. The method of claim 1, wherein receiving the communication confirming the intent to complete the order comprises:
- accumulating one or more metrics while the personal digital key is within the predetermined range, the one or more metrics describing a location of the personal digital key within the predetermined range over time;
- determining a path of the personal digital key within the predetermined range based on the one or more metrics accumulated; and
- determining based on the path of the personal digital key that the first user intends to complete the order.
17. A system for electronic order processing, the system comprising:
- one or more processors;
- a memory including instructions that, when executed by the one or more processors, causes the system to:
- receive an input that a personal digital key is within a predetermined range, the predetermined range associated with a physical location of a merchant, the personal digital key associated with a first user and integrated into a mobile computing and communication device;
- wirelessly receive a set of data including biometric data of the first user from the personal digital key;
- authenticate the personal digital key based on the received set of data;
- authenticate a first biometric sample provided by the first user against the received set of data;
- responsive to authenticating the first biometric sample provided by the first user against the received set of data, receive, from the personal digital key within the predetermined range associated with the physical location of the merchant, a favorite order associated with the merchant, the favorite order stored on the personal digital key;
- determine an initial order based on the favorite order;
- cause presentation, on a display of the mobile computing and communication device, of the initial order;
- cause presentation, on the display of the mobile computing and communication device, of a prompt to confirm the initial order;
- authenticate a second biometric sample provided by the first user against the received set of data;
- responsive to authenticating the second biometric sample provided by the first user against the received set of data, receive, from the mobile computing and communication device, a communication confirming intent to complete an order of the initial order; and
- subsequent to receiving the communication confirming intent to complete the order of the initial order, fulfill the order.
18. The system of claim 17, wherein the instructions, when executed by the one or more processors, further cause the system to process rewards based on the order.
19. The system of claim 18, wherein to process the rewards, the instructions, when executed by the one or more processors, further cause the system to maintain a rewards count.
20. The system of claim 17, wherein the instructions, when executed by the one or more processors, further cause the system to send the order for display on a merchant interface device.
| 3665313 | May 1972 | Trent |
| 3739329 | June 1973 | Lester |
| 3761883 | September 1973 | Alvarez et al. |
| 3906166 | September 1975 | Cooper et al. |
| 4101873 | July 18, 1978 | Anderson et al. |
| 4430705 | February 7, 1984 | Cannavino et al. |
| 4476469 | October 9, 1984 | Lander |
| 4598272 | July 1, 1986 | Cox |
| 4661821 | April 28, 1987 | Smith |
| 4759060 | July 19, 1988 | Hayashi et al. |
| 4814742 | March 21, 1989 | Morita et al. |
| 4871997 | October 3, 1989 | Adriaenssens et al. |
| 4993068 | February 12, 1991 | Piosenka et al. |
| 5043702 | August 27, 1991 | Kuo |
| 5187352 | February 16, 1993 | Blair et al. |
| 5224164 | June 29, 1993 | Elsner |
| 5296641 | March 22, 1994 | Stelzel |
| 5307349 | April 26, 1994 | Shloss et al. |
| 5317572 | May 31, 1994 | Satoh |
| 5325285 | June 28, 1994 | Araki |
| 5392287 | February 21, 1995 | Tiedemann, Jr. et al. |
| 5392433 | February 21, 1995 | Hammersley et al. |
| 5410588 | April 25, 1995 | Ito |
| 5416780 | May 16, 1995 | Patel |
| 5422632 | June 6, 1995 | Bucholtz et al. |
| 5428684 | June 27, 1995 | Akiyama et al. |
| 5450489 | September 12, 1995 | Ostrover et al. |
| 5473690 | December 5, 1995 | Grimonprez et al. |
| 5481265 | January 2, 1996 | Russell |
| 5506863 | April 9, 1996 | Meidan et al. |
| 5517502 | May 14, 1996 | Bestler et al. |
| 5541583 | July 30, 1996 | Mandelbaum |
| 5544321 | August 6, 1996 | Theimer et al. |
| 5552776 | September 3, 1996 | Wade et al. |
| 5563947 | October 8, 1996 | Kikinis |
| 5589838 | December 31, 1996 | McEwan |
| 5594227 | January 14, 1997 | Deo |
| 5598474 | January 28, 1997 | Johnson |
| 5611050 | March 11, 1997 | Theimer et al. |
| 5619251 | April 8, 1997 | Kuroiwa et al. |
| 5623552 | April 22, 1997 | Lane |
| 5629980 | May 13, 1997 | Stefik et al. |
| 5644354 | July 1, 1997 | Thompson et al. |
| 5666412 | September 9, 1997 | Handelman et al. |
| 5689529 | November 18, 1997 | Johnson |
| 5692049 | November 25, 1997 | Johnson et al. |
| 5719387 | February 17, 1998 | Fujioka |
| 5729237 | March 17, 1998 | Webb |
| 5760705 | June 2, 1998 | Glessner et al. |
| 5760744 | June 2, 1998 | Sauer |
| 5773954 | June 30, 1998 | VanHorn |
| 5784464 | July 21, 1998 | Akiyama et al. |
| 5799085 | August 25, 1998 | Shona |
| 5821854 | October 13, 1998 | Dorinski et al. |
| 5825876 | October 20, 1998 | Peterson, Jr. |
| 5835595 | November 10, 1998 | Fraser et al. |
| 5838306 | November 17, 1998 | O'Connor et al. |
| 5854891 | December 29, 1998 | Postlewaite et al. |
| 5857020 | January 5, 1999 | Peterson, Jr. |
| 5886634 | March 23, 1999 | Muhme |
| 5892825 | April 6, 1999 | Mages et al. |
| 5892900 | April 6, 1999 | Ginter et al. |
| 5894551 | April 13, 1999 | Huggins et al. |
| 5898880 | April 27, 1999 | Ryu |
| 5910776 | June 8, 1999 | Black |
| 5917913 | June 29, 1999 | Wang |
| 5923757 | July 13, 1999 | Hocker et al. |
| 5928327 | July 27, 1999 | Wang et al. |
| 5991399 | November 23, 1999 | Graunke et al. |
| 5991749 | November 23, 1999 | Morrill, Jr. |
| 6016476 | January 18, 2000 | Maes et al. |
| 6018739 | January 25, 2000 | McCoy et al. |
| 6025780 | February 15, 2000 | Bowers et al. |
| 6035038 | March 7, 2000 | Campinos et al. |
| 6035329 | March 7, 2000 | Mages et al. |
| 6038334 | March 14, 2000 | Hamid |
| 6038666 | March 14, 2000 | Hsu et al. |
| 6040786 | March 21, 2000 | Fujioka |
| 6041410 | March 21, 2000 | Hsu et al. |
| 6042006 | March 28, 2000 | Van Tilburg et al. |
| 6055314 | April 25, 2000 | Spies et al. |
| 6068184 | May 30, 2000 | Barnett |
| 6070796 | June 6, 2000 | Sirbu |
| 6076164 | June 13, 2000 | Tanaka et al. |
| 6088450 | July 11, 2000 | Davis et al. |
| 6088730 | July 11, 2000 | Kato et al. |
| 6104290 | August 15, 2000 | Naguleswaran |
| 6104334 | August 15, 2000 | Allport |
| 6110041 | August 29, 2000 | Walker et al. |
| 6121544 | September 19, 2000 | Petsinger |
| 6134283 | October 17, 2000 | Sands et al. |
| 6137480 | October 24, 2000 | Shintani |
| 6138010 | October 24, 2000 | Rabe et al. |
| 6148142 | November 14, 2000 | Anderson |
| 6148210 | November 14, 2000 | Elwin et al. |
| 6161179 | December 12, 2000 | Seidel |
| 6177887 | January 23, 2001 | Jerome |
| 6185316 | February 6, 2001 | Buffam |
| 6189105 | February 13, 2001 | Lopes |
| 6209089 | March 27, 2001 | Selitrennikoff et al. |
| 6219109 | April 17, 2001 | Raynesford et al. |
| 6219439 | April 17, 2001 | Burger |
| 6219553 | April 17, 2001 | Panasik |
| 6237848 | May 29, 2001 | Everett |
| 6240076 | May 29, 2001 | Kanerva et al. |
| 6247130 | June 12, 2001 | Fritsch |
| 6249869 | June 19, 2001 | Drupsteen et al. |
| 6256737 | July 3, 2001 | Bianco et al. |
| 6266415 | July 24, 2001 | Campinos et al. |
| 6270011 | August 7, 2001 | Gottfried |
| 6279111 | August 21, 2001 | Jensenworth et al. |
| 6279146 | August 21, 2001 | Evans et al. |
| 6295057 | September 25, 2001 | Rosin et al. |
| 6307471 | October 23, 2001 | Xydis |
| 6325285 | December 4, 2001 | Baratelli |
| 6336121 | January 1, 2002 | Lyson et al. |
| 6336142 | January 1, 2002 | Kato et al. |
| 6343280 | January 29, 2002 | Clark |
| 6345347 | February 5, 2002 | Biran |
| 6363485 | March 26, 2002 | Adams et al. |
| 6367019 | April 2, 2002 | Ansell et al. |
| 6369693 | April 9, 2002 | Gibson |
| 6370376 | April 9, 2002 | Sheath |
| 6381029 | April 30, 2002 | Tipirneni |
| 6381747 | April 30, 2002 | Wonfor et al. |
| 6385596 | May 7, 2002 | Wiser et al. |
| 6392664 | May 21, 2002 | White et al. |
| 6397387 | May 28, 2002 | Rosin et al. |
| 6401059 | June 4, 2002 | Shen et al. |
| 6411307 | June 25, 2002 | Rosin et al. |
| 6424249 | July 23, 2002 | Houvener |
| 6424715 | July 23, 2002 | Saito |
| 6425084 | July 23, 2002 | Rallis et al. |
| 6434403 | August 13, 2002 | Ausems et al. |
| 6434535 | August 13, 2002 | Kupka et al. |
| 6446004 | September 3, 2002 | Cao et al. |
| 6446130 | September 3, 2002 | Grapes et al. |
| 6463534 | October 8, 2002 | Geiger et al. |
| 6480101 | November 12, 2002 | Kelly et al. |
| 6480188 | November 12, 2002 | Horsley |
| 6484182 | November 19, 2002 | Dunphy et al. |
| 6484260 | November 19, 2002 | Scott et al. |
| 6484946 | November 26, 2002 | Matsumoto et al. |
| 6487663 | November 26, 2002 | Jaisimha et al. |
| 6490443 | December 3, 2002 | Freeny, Jr. |
| 6510350 | January 21, 2003 | Steen, III et al. |
| 6522253 | February 18, 2003 | Saltus |
| 6523113 | February 18, 2003 | Wehrenberg |
| 6529949 | March 4, 2003 | Getsin et al. |
| 6546418 | April 8, 2003 | Schena et al. |
| 6550011 | April 15, 2003 | Sims, III |
| 6563465 | May 13, 2003 | Frecska |
| 6563805 | May 13, 2003 | Ma et al. |
| 6564380 | May 13, 2003 | Murphy |
| 6577238 | June 10, 2003 | Whitesmith et al. |
| 6593887 | July 15, 2003 | Luk et al. |
| 6597680 | July 22, 2003 | Lindskog et al. |
| 6607136 | August 19, 2003 | Atsmon et al. |
| 6628302 | September 30, 2003 | White et al. |
| 6632992 | October 14, 2003 | Hasegawa |
| 6633981 | October 14, 2003 | Davis |
| 6645077 | November 11, 2003 | Rowe |
| 6647417 | November 11, 2003 | Hunter et al. |
| 6657538 | December 2, 2003 | Ritter |
| 6658566 | December 2, 2003 | Hazard |
| 6667684 | December 23, 2003 | Waggamon et al. |
| 6669096 | December 30, 2003 | Saphar et al. |
| 6671808 | December 30, 2003 | Abbott et al. |
| 6683954 | January 27, 2004 | Searle |
| 6697944 | February 24, 2004 | Jones et al. |
| 6709333 | March 23, 2004 | Bradford et al. |
| 6711464 | March 23, 2004 | Yap et al. |
| 6714168 | March 30, 2004 | Berenbaum |
| 6715246 | April 6, 2004 | Frecska et al. |
| 6728397 | April 27, 2004 | McNeal |
| 6737955 | May 18, 2004 | Ghabra et al. |
| 6758394 | July 6, 2004 | Maskatiya et al. |
| 6771969 | August 3, 2004 | Chinoy et al. |
| 6775655 | August 10, 2004 | Peinado et al. |
| 6785474 | August 31, 2004 | Hirt et al. |
| 6788640 | September 7, 2004 | Celeste |
| 6788924 | September 7, 2004 | Knutson et al. |
| 6795425 | September 21, 2004 | Raith |
| 6804825 | October 12, 2004 | White et al. |
| 6806887 | October 19, 2004 | Chernock et al. |
| 6839542 | January 4, 2005 | Sibecas et al. |
| 6850147 | February 1, 2005 | Prokoski et al. |
| 6853988 | February 8, 2005 | Dickinson et al. |
| 6859812 | February 22, 2005 | Poynor |
| 6861980 | March 1, 2005 | Rowitch et al. |
| 6873975 | March 29, 2005 | Hatakeyama et al. |
| 6879567 | April 12, 2005 | Callaway et al. |
| 6879966 | April 12, 2005 | Lapsley et al. |
| 6886741 | May 3, 2005 | Salveson |
| 6889067 | May 3, 2005 | Willey |
| 6891822 | May 10, 2005 | Gubbi et al. |
| 6892307 | May 10, 2005 | Wood et al. |
| 6930643 | August 16, 2005 | Byrne et al. |
| 6947003 | September 20, 2005 | Huor |
| 6950941 | September 27, 2005 | Lee et al. |
| 6957086 | October 18, 2005 | Bahl et al. |
| 6961858 | November 1, 2005 | Fransdonk |
| 6963270 | November 8, 2005 | Gallagher, III et al. |
| 6963971 | November 8, 2005 | Bush et al. |
| 6973576 | December 6, 2005 | Giobbi |
| 6975202 | December 13, 2005 | Rodriguez et al. |
| 6980087 | December 27, 2005 | Zukowksi |
| 6983882 | January 10, 2006 | Cassone |
| 6999032 | February 14, 2006 | Pakray et al. |
| 7012503 | March 14, 2006 | Nielsen |
| 7020635 | March 28, 2006 | Hamilton et al. |
| 7031945 | April 18, 2006 | Donner |
| 7049963 | May 23, 2006 | Waterhouse et al. |
| 7055171 | May 30, 2006 | Martin et al. |
| 7058806 | June 6, 2006 | Smeets et al. |
| 7061380 | June 13, 2006 | Orlando et al. |
| 7068623 | June 27, 2006 | Barany et al. |
| 7072900 | July 4, 2006 | Sweitzer et al. |
| 7079079 | July 18, 2006 | Jo et al. |
| 7080049 | July 18, 2006 | Truitt et al. |
| 7082415 | July 25, 2006 | Robinson et al. |
| 7090126 | August 15, 2006 | Kelly et al. |
| 7090128 | August 15, 2006 | Farley et al. |
| 7100053 | August 29, 2006 | Brown et al. |
| 7107455 | September 12, 2006 | Merkin |
| 7107462 | September 12, 2006 | Fransdonk |
| 7111789 | September 26, 2006 | Rajasekaran et al. |
| 7112138 | September 26, 2006 | Hedrick et al. |
| 7119659 | October 10, 2006 | Bonaile et al. |
| 7123149 | October 17, 2006 | Nowak et al. |
| 7130668 | October 31, 2006 | Chang et al. |
| 7131139 | October 31, 2006 | Meier |
| 7137008 | November 14, 2006 | Hamid et al. |
| 7137012 | November 14, 2006 | Kamibayashi et al. |
| 7139914 | November 21, 2006 | Arnouse |
| 7150045 | December 12, 2006 | Koelle et al. |
| 7155416 | December 26, 2006 | Shatford |
| 7159114 | January 2, 2007 | Zajkowksi et al. |
| 7159765 | January 9, 2007 | Frerking |
| 7167987 | January 23, 2007 | Angelo |
| 7168089 | January 23, 2007 | Nguyen et al. |
| 7176797 | February 13, 2007 | Zai et al. |
| 7191466 | March 13, 2007 | Hamid et al. |
| 7209955 | April 24, 2007 | Major et al. |
| 7218944 | May 15, 2007 | Cromer et al. |
| 7225161 | May 29, 2007 | Lam et al. |
| 7230908 | June 12, 2007 | Vanderaar et al. |
| 7231068 | June 12, 2007 | Tibor |
| 7231451 | June 12, 2007 | Law et al. |
| 7242923 | July 10, 2007 | Perera et al. |
| 7249177 | July 24, 2007 | Miller |
| 7272723 | September 18, 2007 | Abbott et al. |
| 7277737 | October 2, 2007 | Vollmer et al. |
| 7278025 | October 2, 2007 | Saito et al. |
| 7283650 | October 16, 2007 | Sharma et al. |
| 7295119 | November 13, 2007 | Rappaport et al. |
| 7305560 | December 4, 2007 | Giobbi |
| 7310042 | December 18, 2007 | Seifert |
| 7314164 | January 1, 2008 | Bonalle et al. |
| 7317799 | January 8, 2008 | Hammersmith et al. |
| 7319395 | January 15, 2008 | Puzio et al. |
| 7330108 | February 12, 2008 | Thomas |
| 7333002 | February 19, 2008 | Bixler et al. |
| 7333615 | February 19, 2008 | Jarboe et al. |
| 7336181 | February 26, 2008 | Nowak et al. |
| 7336182 | February 26, 2008 | Baranowski et al. |
| 7337326 | February 26, 2008 | Palmer et al. |
| 7341181 | March 11, 2008 | Bonalle et al. |
| 7342503 | March 11, 2008 | Light et al. |
| 7349557 | March 25, 2008 | Tibor |
| 7356393 | April 8, 2008 | Schlatre et al. |
| 7356706 | April 8, 2008 | Scheurich |
| 7361919 | April 22, 2008 | Setlak |
| 7363494 | April 22, 2008 | Brainard et al. |
| 7370366 | May 6, 2008 | Lacan et al. |
| 7378939 | May 27, 2008 | Sengupta et al. |
| 7380202 | May 27, 2008 | Lindhorst et al. |
| 7382799 | June 3, 2008 | Young et al. |
| 7387235 | June 17, 2008 | Gilbert et al. |
| 7401731 | July 22, 2008 | Pletz et al. |
| 7424134 | September 9, 2008 | Chou |
| 7437330 | October 14, 2008 | Robinson et al. |
| 7447911 | November 4, 2008 | Chou et al. |
| 7448087 | November 4, 2008 | Ohmori et al. |
| 7458510 | December 2, 2008 | Zhou |
| 7460836 | December 2, 2008 | Smith et al. |
| 7461444 | December 9, 2008 | Deaett et al. |
| 7464053 | December 9, 2008 | Pylant |
| 7464059 | December 9, 2008 | Robinson et al. |
| 7466232 | December 16, 2008 | Neuwirth |
| 7472280 | December 30, 2008 | Giobbi |
| 7512806 | March 31, 2009 | Lemke |
| 7525413 | April 28, 2009 | Jung et al. |
| 7529944 | May 5, 2009 | Hamid |
| 7533809 | May 19, 2009 | Robinson et al. |
| 7545312 | June 9, 2009 | Kiang et al. |
| 7565329 | July 21, 2009 | Lapsley et al. |
| 7573382 | August 11, 2009 | Choubey et al. |
| 7573841 | August 11, 2009 | Lee et al. |
| 7574734 | August 11, 2009 | Fedronic et al. |
| 7583238 | September 1, 2009 | Cassen et al. |
| 7583643 | September 1, 2009 | Smith et al. |
| 7587502 | September 8, 2009 | Crawford et al. |
| 7587611 | September 8, 2009 | Johnson et al. |
| 7594611 | September 29, 2009 | Arrington, III |
| 7595765 | September 29, 2009 | Hirsch et al. |
| 7603564 | October 13, 2009 | Adachi |
| 7606733 | October 20, 2009 | Shmueli et al. |
| 7617523 | November 10, 2009 | Das et al. |
| 7620184 | November 17, 2009 | Marque Pucheu |
| 7624073 | November 24, 2009 | Robinson et al. |
| 7624417 | November 24, 2009 | Dua |
| 7640273 | December 29, 2009 | Wallmeier et al. |
| 7644443 | January 5, 2010 | Matsuyama et al. |
| 7646307 | January 12, 2010 | Plocher et al. |
| 7652892 | January 26, 2010 | Shiu et al. |
| 7676380 | March 9, 2010 | Graves et al. |
| 7689005 | March 30, 2010 | Wang et al. |
| 7706896 | April 27, 2010 | Music et al. |
| 7711152 | May 4, 2010 | Davida et al. |
| 7711586 | May 4, 2010 | Aggarwal et al. |
| 7715593 | May 11, 2010 | Adams et al. |
| 7724713 | May 25, 2010 | Del Prado Pavon et al. |
| 7724717 | May 25, 2010 | Porras et al. |
| 7724720 | May 25, 2010 | Korpela et al. |
| 7764236 | July 27, 2010 | Hill et al. |
| 7765164 | July 27, 2010 | Robinson et al. |
| 7765181 | July 27, 2010 | Thomas et al. |
| 7773754 | August 10, 2010 | Buer et al. |
| 7774613 | August 10, 2010 | Lemke |
| 7780082 | August 24, 2010 | Handa et al. |
| 7796551 | September 14, 2010 | Machiraju et al. |
| 7813822 | October 12, 2010 | Hoffberg |
| 7865448 | January 4, 2011 | Pizarro |
| 7865937 | January 4, 2011 | White et al. |
| 7883417 | February 8, 2011 | Bruzzese et al. |
| 7904718 | March 8, 2011 | Giobbi et al. |
| 7943868 | May 17, 2011 | Anders et al. |
| 7957536 | June 7, 2011 | Nolte |
| 7961078 | June 14, 2011 | Reynolds et al. |
| 7984064 | July 19, 2011 | Fusari |
| 7996514 | August 9, 2011 | Baumert et al. |
| 8026821 | September 27, 2011 | Reeder et al. |
| 8036152 | October 11, 2011 | Brown et al. |
| 8077041 | December 13, 2011 | Stern et al. |
| 8081215 | December 20, 2011 | Kuo et al. |
| 8082160 | December 20, 2011 | Collins, Jr. et al. |
| 8089354 | January 3, 2012 | Perkins |
| 8112066 | February 7, 2012 | Ben Ayed |
| 8125624 | February 28, 2012 | Jones et al. |
| 8135624 | March 13, 2012 | Ramalingam et al. |
| 8171528 | May 1, 2012 | Brown |
| 8193923 | June 5, 2012 | Rork et al. |
| 8200980 | June 12, 2012 | Robinson et al. |
| 8215552 | July 10, 2012 | Rambadt |
| 8248263 | August 21, 2012 | Shervey et al. |
| 8258942 | September 4, 2012 | Lanzone et al. |
| 8294554 | October 23, 2012 | Shoarinejad et al. |
| 8296573 | October 23, 2012 | Bolle et al. |
| 8307414 | November 6, 2012 | Zerfos et al. |
| 8325011 | December 4, 2012 | Butler et al. |
| 8340672 | December 25, 2012 | Brown et al. |
| 8352730 | January 8, 2013 | Giobbi |
| 8373562 | February 12, 2013 | Heinze et al. |
| 8378925 | February 19, 2013 | Chiaki |
| 8387124 | February 26, 2013 | Smetters |
| 8390456 | March 5, 2013 | Puleston et al. |
| 8395484 | March 12, 2013 | Fullerton |
| 8410906 | April 2, 2013 | Dacus et al. |
| 8421606 | April 16, 2013 | Collins, Jr. et al. |
| 8424079 | April 16, 2013 | Adams et al. |
| 8432262 | April 30, 2013 | Talty et al. |
| 8433919 | April 30, 2013 | Giobbi et al. |
| 8448858 | May 28, 2013 | Kundu et al. |
| 8473748 | June 25, 2013 | Sampas |
| 8484696 | July 9, 2013 | Gatto et al. |
| 8494576 | July 23, 2013 | Bye et al. |
| 8508336 | August 13, 2013 | Giobbi et al. |
| 8511555 | August 20, 2013 | Babcock et al. |
| 8519823 | August 27, 2013 | Rinkes |
| 8522019 | August 27, 2013 | Michaelis |
| 8558699 | October 15, 2013 | Butler et al. |
| 8572391 | October 29, 2013 | Golan et al. |
| 8577091 | November 5, 2013 | Ivanov et al. |
| 8646042 | February 4, 2014 | Brown |
| 8678273 | March 25, 2014 | McNeal |
| 8717346 | May 6, 2014 | Claessen |
| 8738925 | May 27, 2014 | Park et al. |
| 8799574 | August 5, 2014 | Corda |
| 8856539 | October 7, 2014 | Weiss |
| 8914477 | December 16, 2014 | Gammon |
| 8918854 | December 23, 2014 | Giobbi |
| 8931698 | January 13, 2015 | Ishikawa et al. |
| 8979646 | March 17, 2015 | Moser et al. |
| 9037140 | May 19, 2015 | Brown |
| 9049188 | June 2, 2015 | Brown |
| 9165233 | October 20, 2015 | Testanero |
| 9189788 | November 17, 2015 | Robinson et al. |
| 9230399 | January 5, 2016 | Yacenda |
| 9235700 | January 12, 2016 | Brown |
| 9276914 | March 1, 2016 | Woodward et al. |
| 9305312 | April 5, 2016 | Kountotsis et al. |
| 9405898 | August 2, 2016 | Giobbi |
| 9418205 | August 16, 2016 | Giobbi |
| 9542542 | January 10, 2017 | Giobbi et al. |
| 9679289 | June 13, 2017 | Brown |
| 9830504 | November 28, 2017 | Masood et al. |
| 9892250 | February 13, 2018 | Giobbi |
| 10073960 | September 11, 2018 | Brown |
| 10110385 | October 23, 2018 | Rush et al. |
| 10455533 | October 22, 2019 | Brown |
| 10817964 | October 27, 2020 | Guillama et al. |
| 20010021950 | September 13, 2001 | Hawley et al. |
| 20010024428 | September 27, 2001 | Onouchi |
| 20010026619 | October 4, 2001 | Howard, Jr. et al. |
| 20010027121 | October 4, 2001 | Boesen |
| 20010027439 | October 4, 2001 | Holtzman et al. |
| 20010044337 | November 22, 2001 | Rowe et al. |
| 20020004783 | January 10, 2002 | Paltenghe et al. |
| 20020007456 | January 17, 2002 | Peinado et al. |
| 20020010679 | January 24, 2002 | Felsher |
| 20020013772 | January 31, 2002 | Peinado |
| 20020014954 | February 7, 2002 | Fitzgibbon et al. |
| 20020015494 | February 7, 2002 | Nagai et al. |
| 20020019811 | February 14, 2002 | Lapsley et al. |
| 20020022455 | February 21, 2002 | Salokannel et al. |
| 20020023032 | February 21, 2002 | Pearson et al. |
| 20020023217 | February 21, 2002 | Wheeler et al. |
| 20020026424 | February 28, 2002 | Akashi |
| 20020037732 | March 28, 2002 | Gous et al. |
| 20020052193 | May 2, 2002 | Chetty |
| 20020055908 | May 9, 2002 | Di Giorgio et al. |
| 20020056043 | May 9, 2002 | Glass |
| 20020059114 | May 16, 2002 | Cockrill et al. |
| 20020062249 | May 23, 2002 | Iannacci |
| 20020068605 | June 6, 2002 | Stanley |
| 20020069364 | June 6, 2002 | Dosch |
| 20020071559 | June 13, 2002 | Christensen et al. |
| 20020073042 | June 13, 2002 | Maritzen et al. |
| 20020080969 | June 27, 2002 | Giobbi |
| 20020083178 | June 27, 2002 | Brothers |
| 20020083318 | June 27, 2002 | Larose |
| 20020086690 | July 4, 2002 | Takahashi et al. |
| 20020089890 | July 11, 2002 | Fibranz et al. |
| 20020091646 | July 11, 2002 | Lake et al. |
| 20020095586 | July 18, 2002 | Doyle et al. |
| 20020095587 | July 18, 2002 | Doyle et al. |
| 20020097876 | July 25, 2002 | Harrison |
| 20020098888 | July 25, 2002 | Rowe et al. |
| 20020100798 | August 1, 2002 | Farrugia et al. |
| 20020103027 | August 1, 2002 | Rowe et al. |
| 20020103881 | August 1, 2002 | Granade et al. |
| 20020104006 | August 1, 2002 | Boate et al. |
| 20020104019 | August 1, 2002 | Chatani et al. |
| 20020105918 | August 8, 2002 | Yamada et al. |
| 20020108049 | August 8, 2002 | Xu et al. |
| 20020109580 | August 15, 2002 | Shreve et al. |
| 20020111919 | August 15, 2002 | Weller et al. |
| 20020112183 | August 15, 2002 | Baird et al. |
| 20020116615 | August 22, 2002 | Nguyen et al. |
| 20020124251 | September 5, 2002 | Hunter et al. |
| 20020128017 | September 12, 2002 | Virtanen |
| 20020129262 | September 12, 2002 | Kutaragi et al. |
| 20020138438 | September 26, 2002 | Bardwell |
| 20020138767 | September 26, 2002 | Hamid et al. |
| 20020140542 | October 3, 2002 | Prokoski et al. |
| 20020141586 | October 3, 2002 | Margalit et al. |
| 20020143623 | October 3, 2002 | Dayley |
| 20020143655 | October 3, 2002 | Elston |
| 20020144116 | October 3, 2002 | Giobbi |
| 20020144117 | October 3, 2002 | Faigle |
| 20020147653 | October 10, 2002 | Shmueli et al. |
| 20020148892 | October 17, 2002 | Bardwell |
| 20020150282 | October 17, 2002 | Kinsella |
| 20020152391 | October 17, 2002 | Willins et al. |
| 20020153996 | October 24, 2002 | Chan et al. |
| 20020158121 | October 31, 2002 | Stanford-Clark |
| 20020158750 | October 31, 2002 | Almalik |
| 20020158765 | October 31, 2002 | Pape et al. |
| 20020160820 | October 31, 2002 | Winkler |
| 20020174348 | November 21, 2002 | Ting |
| 20020177460 | November 28, 2002 | Beasley et al. |
| 20020178063 | November 28, 2002 | Gravelle et al. |
| 20020184208 | December 5, 2002 | Kato |
| 20020187746 | December 12, 2002 | Cheng et al. |
| 20020191816 | December 19, 2002 | Matzen et al. |
| 20020196963 | December 26, 2002 | Bardwell |
| 20020199120 | December 26, 2002 | Schmidt |
| 20030022701 | January 30, 2003 | Gupta |
| 20030034877 | February 20, 2003 | Miller et al. |
| 20030036416 | February 20, 2003 | Pattabiraman et al. |
| 20030036425 | February 20, 2003 | Kaminkow et al. |
| 20030046228 | March 6, 2003 | Berney |
| 20030046237 | March 6, 2003 | Uberti |
| 20030046552 | March 6, 2003 | Hamid |
| 20030048174 | March 13, 2003 | Stevens et al. |
| 20030051173 | March 13, 2003 | Krueger |
| 20030054868 | March 20, 2003 | Paulsen et al. |
| 20030054881 | March 20, 2003 | Hedrick et al. |
| 20030055689 | March 20, 2003 | Block et al. |
| 20030061172 | March 27, 2003 | Robinson |
| 20030063619 | April 3, 2003 | Montano et al. |
| 20030079133 | April 24, 2003 | Breiter |
| 20030087601 | May 8, 2003 | Agam et al. |
| 20030088441 | May 8, 2003 | McNerney |
| 20030105719 | June 5, 2003 | Berger et al. |
| 20030109274 | June 12, 2003 | Budka et al. |
| 20030115351 | June 19, 2003 | Giobbi |
| 20030115474 | June 19, 2003 | Khan et al. |
| 20030117969 | June 26, 2003 | Koo et al. |
| 20030117980 | June 26, 2003 | Kim et al. |
| 20030120934 | June 26, 2003 | Ortiz |
| 20030127511 | July 10, 2003 | Kelly et al. |
| 20030128866 | July 10, 2003 | McNeal |
| 20030137404 | July 24, 2003 | Bonneau, Jr. et al. |
| 20030139190 | July 24, 2003 | Steelberg et al. |
| 20030146835 | August 7, 2003 | Carter |
| 20030149744 | August 7, 2003 | Bierre et al. |
| 20030156742 | August 21, 2003 | Witt et al. |
| 20030159040 | August 21, 2003 | Hashimoto et al. |
| 20030163388 | August 28, 2003 | Beane |
| 20030167207 | September 4, 2003 | Berardi et al. |
| 20030169697 | September 11, 2003 | Suzuki et al. |
| 20030172028 | September 11, 2003 | Abell et al. |
| 20030172037 | September 11, 2003 | Jung et al. |
| 20030174839 | September 18, 2003 | Yamagata et al. |
| 20030176218 | September 18, 2003 | LeMay et al. |
| 20030177102 | September 18, 2003 | Robinson |
| 20030186739 | October 2, 2003 | Paulsen et al. |
| 20030195842 | October 16, 2003 | Reece |
| 20030199267 | October 23, 2003 | Iwasa et al. |
| 20030204526 | October 30, 2003 | Salehi-Had |
| 20030213840 | November 20, 2003 | Livingston et al. |
| 20030223394 | December 4, 2003 | Parantainen et al. |
| 20030225703 | December 4, 2003 | Angel |
| 20030226031 | December 4, 2003 | Proudler et al. |
| 20030233458 | December 18, 2003 | Kwon et al. |
| 20040002347 | January 1, 2004 | Hoctor et al. |
| 20040015403 | January 22, 2004 | Moskowitz |
| 20040022384 | February 5, 2004 | Flores et al. |
| 20040029620 | February 12, 2004 | Karaoguz |
| 20040029635 | February 12, 2004 | Giobbi |
| 20040030764 | February 12, 2004 | Birk et al. |
| 20040030894 | February 12, 2004 | Labrou et al. |
| 20040035644 | February 26, 2004 | Ford |
| 20040039909 | February 26, 2004 | Cheng |
| 20040048570 | March 11, 2004 | Oba et al. |
| 20040048609 | March 11, 2004 | Kosaka |
| 20040059682 | March 25, 2004 | Hasumi et al. |
| 20040059912 | March 25, 2004 | Zizzi |
| 20040064728 | April 1, 2004 | Scheurich |
| 20040068656 | April 8, 2004 | Lu |
| 20040073792 | April 15, 2004 | Noble et al. |
| 20040081127 | April 29, 2004 | Gardner et al. |
| 20040082385 | April 29, 2004 | Silva et al. |
| 20040090345 | May 13, 2004 | Hitt |
| 20040098597 | May 20, 2004 | Giobbi |
| 20040114563 | June 17, 2004 | Shvodian |
| 20040117644 | June 17, 2004 | Colvin |
| 20040123106 | June 24, 2004 | D'Angelo et al. |
| 20040123127 | June 24, 2004 | Teicher et al. |
| 20040127277 | July 1, 2004 | Walker et al. |
| 20040128162 | July 1, 2004 | Schlotterbeck et al. |
| 20040128389 | July 1, 2004 | Kopchik |
| 20040128500 | July 1, 2004 | Cihula et al. |
| 20040128508 | July 1, 2004 | Wheeler et al. |
| 20040128519 | July 1, 2004 | Klinger et al. |
| 20040129787 | July 8, 2004 | Saito et al. |
| 20040132432 | July 8, 2004 | Moores et al. |
| 20040137912 | July 15, 2004 | Lin |
| 20040158746 | August 12, 2004 | Hu et al. |
| 20040166875 | August 26, 2004 | Jenkins et al. |
| 20040167465 | August 26, 2004 | Mihai et al. |
| 20040181695 | September 16, 2004 | Walker |
| 20040193925 | September 30, 2004 | Safriel |
| 20040194133 | September 30, 2004 | Ikeda et al. |
| 20040203566 | October 14, 2004 | Leung |
| 20040203923 | October 14, 2004 | Mullen |
| 20040208139 | October 21, 2004 | Iwamura |
| 20040209690 | October 21, 2004 | Bruzzese et al. |
| 20040209692 | October 21, 2004 | Schober et al. |
| 20040214582 | October 28, 2004 | Lan et al. |
| 20040215615 | October 28, 2004 | Larsson et al. |
| 20040217859 | November 4, 2004 | Pucci et al. |
| 20040218581 | November 4, 2004 | Cattaneo |
| 20040222877 | November 11, 2004 | Teramura et al. |
| 20040230488 | November 18, 2004 | Beenau et al. |
| 20040230809 | November 18, 2004 | Lowensohn et al. |
| 20040234117 | November 25, 2004 | Tibor |
| 20040243519 | December 2, 2004 | Perttila et al. |
| 20040246103 | December 9, 2004 | Zukowski |
| 20040246950 | December 9, 2004 | Parker et al. |
| 20040250074 | December 9, 2004 | Kilian-Kehr |
| 20040252012 | December 16, 2004 | Beenau et al. |
| 20040252659 | December 16, 2004 | Yun et al. |
| 20040253996 | December 16, 2004 | Chen et al. |
| 20040254837 | December 16, 2004 | Roshkoff |
| 20040255139 | December 16, 2004 | Giobbi |
| 20040255145 | December 16, 2004 | Chow |
| 20050001028 | January 6, 2005 | Zuili |
| 20050002028 | January 6, 2005 | Kasapi et al. |
| 20050005136 | January 6, 2005 | Chen et al. |
| 20050006452 | January 13, 2005 | Aupperle et al. |
| 20050009517 | January 13, 2005 | Maes |
| 20050021561 | January 27, 2005 | Noonan |
| 20050025093 | February 3, 2005 | Yun et al. |
| 20050028168 | February 3, 2005 | Marcjan |
| 20050035897 | February 17, 2005 | Perl et al. |
| 20050039027 | February 17, 2005 | Shapiro |
| 20050040961 | February 24, 2005 | Tuttle |
| 20050044372 | February 24, 2005 | Aull et al. |
| 20050044387 | February 24, 2005 | Ozolins |
| 20050047386 | March 3, 2005 | Yi |
| 20050049013 | March 3, 2005 | Chang et al. |
| 20050050208 | March 3, 2005 | Chatani |
| 20050050324 | March 3, 2005 | Corbett et al. |
| 20050054431 | March 10, 2005 | Walker et al. |
| 20050055242 | March 10, 2005 | Bello et al. |
| 20050055244 | March 10, 2005 | Mullan et al. |
| 20050058292 | March 17, 2005 | Diorio et al. |
| 20050074126 | April 7, 2005 | Stanko |
| 20050076242 | April 7, 2005 | Breuer |
| 20050081040 | April 14, 2005 | Johnson et al. |
| 20050084137 | April 21, 2005 | Kim et al. |
| 20050086115 | April 21, 2005 | Pearson |
| 20050086515 | April 21, 2005 | Paris |
| 20050089000 | April 28, 2005 | Bae et al. |
| 20050090200 | April 28, 2005 | Karaoguz et al. |
| 20050091338 | April 28, 2005 | de la Huerga |
| 20050091553 | April 28, 2005 | Chien et al. |
| 20050094657 | May 5, 2005 | Sung et al. |
| 20050097037 | May 5, 2005 | Tibor |
| 20050105600 | May 19, 2005 | Culum et al. |
| 20050105734 | May 19, 2005 | Buer et al. |
| 20050108164 | May 19, 2005 | Salafia, III et al. |
| 20050109836 | May 26, 2005 | Ben-Aissa |
| 20050109841 | May 26, 2005 | Ryan et al. |
| 20050113070 | May 26, 2005 | Okabe |
| 20050114149 | May 26, 2005 | Rodriguez et al. |
| 20050114150 | May 26, 2005 | Franklin |
| 20050116020 | June 2, 2005 | Smolucha et al. |
| 20050117530 | June 2, 2005 | Abraham et al. |
| 20050119979 | June 2, 2005 | Murashita et al. |
| 20050124294 | June 9, 2005 | Wentink |
| 20050125258 | June 9, 2005 | Yellin et al. |
| 20050137977 | June 23, 2005 | Wankmueller |
| 20050138390 | June 23, 2005 | Adams et al. |
| 20050138576 | June 23, 2005 | Baumert et al. |
| 20050139656 | June 30, 2005 | Arnouse |
| 20050141451 | June 30, 2005 | Yoon et al. |
| 20050152394 | July 14, 2005 | Cho |
| 20050154897 | July 14, 2005 | Holloway et al. |
| 20050161503 | July 28, 2005 | Remery et al. |
| 20050165684 | July 28, 2005 | Jensen et al. |
| 20050166063 | July 28, 2005 | Zyh-Ming |
| 20050167482 | August 4, 2005 | Ramachandran et al. |
| 20050169292 | August 4, 2005 | Young |
| 20050177716 | August 11, 2005 | Ginter et al. |
| 20050180385 | August 18, 2005 | Jeong et al. |
| 20050182661 | August 18, 2005 | Allard et al. |
| 20050182975 | August 18, 2005 | Guo et al. |
| 20050187792 | August 25, 2005 | Harper |
| 20050192748 | September 1, 2005 | Andric et al. |
| 20050195975 | September 8, 2005 | Kawakita |
| 20050200453 | September 15, 2005 | Turner et al. |
| 20050201389 | September 15, 2005 | Shimanuki et al. |
| 20050203682 | September 15, 2005 | Omino et al. |
| 20050203844 | September 15, 2005 | Ferguson et al. |
| 20050210270 | September 22, 2005 | Rohatgi et al. |
| 20050212657 | September 29, 2005 | Simon |
| 20050215233 | September 29, 2005 | Perera et al. |
| 20050216313 | September 29, 2005 | Claud et al. |
| 20050216639 | September 29, 2005 | Sparer et al. |
| 20050218215 | October 6, 2005 | Lauden |
| 20050220046 | October 6, 2005 | Falck et al. |
| 20050221869 | October 6, 2005 | Liu et al. |
| 20050229007 | October 13, 2005 | Bolle et al. |
| 20050229240 | October 13, 2005 | Nanba |
| 20050242921 | November 3, 2005 | Zimmerman et al. |
| 20050243787 | November 3, 2005 | Hong et al. |
| 20050249385 | November 10, 2005 | Kondo et al. |
| 20050251688 | November 10, 2005 | Nanvati et al. |
| 20050253683 | November 17, 2005 | Lowe |
| 20050257102 | November 17, 2005 | Moyer et al. |
| 20050264416 | December 1, 2005 | Maurer |
| 20050268111 | December 1, 2005 | Markham |
| 20050269401 | December 8, 2005 | Spitzer et al. |
| 20050272403 | December 8, 2005 | Ryu et al. |
| 20050281320 | December 22, 2005 | Neugebauer |
| 20050282558 | December 22, 2005 | Choi et al. |
| 20050284932 | December 29, 2005 | Sukeda et al. |
| 20050287985 | December 29, 2005 | Balfanz et al. |
| 20050288069 | December 29, 2005 | Arunan et al. |
| 20050289473 | December 29, 2005 | Gustafson et al. |
| 20060001525 | January 5, 2006 | Nitzan et al. |
| 20060014430 | January 19, 2006 | Liang et al. |
| 20060022042 | February 2, 2006 | Smets et al. |
| 20060022046 | February 2, 2006 | Iwamura |
| 20060022800 | February 2, 2006 | Krishna et al. |
| 20060025180 | February 2, 2006 | Rajkotia et al. |
| 20060026673 | February 2, 2006 | Tsuchida |
| 20060030279 | February 9, 2006 | Leabman |
| 20060030353 | February 9, 2006 | Jun |
| 20060034250 | February 16, 2006 | Kim et al. |
| 20060041746 | February 23, 2006 | Kirkup et al. |
| 20060046664 | March 2, 2006 | Paradiso et al. |
| 20060058102 | March 16, 2006 | Nguyen et al. |
| 20060063575 | March 23, 2006 | Gatto et al. |
| 20060069814 | March 30, 2006 | Abraham et al. |
| 20060072586 | April 6, 2006 | Callaway, Jr. et al. |
| 20060074713 | April 6, 2006 | Conry et al. |
| 20060076401 | April 13, 2006 | Frerking |
| 20060078176 | April 13, 2006 | Abiko et al. |
| 20060087407 | April 27, 2006 | Stewart et al. |
| 20060089138 | April 27, 2006 | Smith et al. |
| 20060097949 | May 11, 2006 | Luebke et al. |
| 20060110012 | May 25, 2006 | Ritter |
| 20060111955 | May 25, 2006 | Winter et al. |
| 20060113381 | June 1, 2006 | Hochstein et al. |
| 20060116935 | June 1, 2006 | Evans |
| 20060117013 | June 1, 2006 | Wada |
| 20060120287 | June 8, 2006 | Foti et al. |
| 20060129838 | June 15, 2006 | Chen et al. |
| 20060136728 | June 22, 2006 | Gentry et al. |
| 20060136742 | June 22, 2006 | Giobbi |
| 20060143441 | June 29, 2006 | Giobbi |
| 20060144943 | July 6, 2006 | Kim |
| 20060156027 | July 13, 2006 | Blake |
| 20060158308 | July 20, 2006 | McMullen et al. |
| 20060163349 | July 27, 2006 | Neugebauer |
| 20060165060 | July 27, 2006 | Dua |
| 20060169771 | August 3, 2006 | Brookner |
| 20060170530 | August 3, 2006 | Nwosu et al. |
| 20060170565 | August 3, 2006 | Husak et al. |
| 20060172700 | August 3, 2006 | Wu |
| 20060173846 | August 3, 2006 | Omae et al. |
| 20060173991 | August 3, 2006 | Piikivi |
| 20060183426 | August 17, 2006 | Graves et al. |
| 20060183462 | August 17, 2006 | Kolehmainen |
| 20060184795 | August 17, 2006 | Doradla et al. |
| 20060185005 | August 17, 2006 | Graves et al. |
| 20060187029 | August 24, 2006 | Thomas |
| 20060190348 | August 24, 2006 | Ofer et al. |
| 20060190413 | August 24, 2006 | Harper |
| 20060194598 | August 31, 2006 | Kim et al. |
| 20060195576 | August 31, 2006 | Rinne et al. |
| 20060198337 | September 7, 2006 | Hoang et al. |
| 20060200467 | September 7, 2006 | Ohmori et al. |
| 20060205408 | September 14, 2006 | Nakagawa et al. |
| 20060208066 | September 21, 2006 | Finn et al. |
| 20060208853 | September 21, 2006 | Kung et al. |
| 20060222042 | October 5, 2006 | Teramura et al. |
| 20060226950 | October 12, 2006 | Kanou et al. |
| 20060229909 | October 12, 2006 | Kaila et al. |
| 20060236373 | October 19, 2006 | Graves et al. |
| 20060237528 | October 26, 2006 | Bishop et al. |
| 20060238305 | October 26, 2006 | Loving et al. |
| 20060268891 | November 30, 2006 | Heidari-Bateni et al. |
| 20060273176 | December 7, 2006 | Audebert et al. |
| 20060274711 | December 7, 2006 | Nelson, Jr. et al. |
| 20060279412 | December 14, 2006 | Holland et al. |
| 20060286969 | December 21, 2006 | Talmor et al. |
| 20060288095 | December 21, 2006 | Torok et al. |
| 20060288233 | December 21, 2006 | Kozlay |
| 20060290580 | December 28, 2006 | Noro et al. |
| 20060293925 | December 28, 2006 | Flom |
| 20060294388 | December 28, 2006 | Abraham et al. |
| 20070003111 | January 4, 2007 | Awatsu et al. |
| 20070005403 | January 4, 2007 | Kennedy et al. |
| 20070007331 | January 11, 2007 | Jasper |
| 20070008070 | January 11, 2007 | Friedrich |
| 20070008916 | January 11, 2007 | Haugli et al. |
| 20070011724 | January 11, 2007 | Gonzalez et al. |
| 20070016800 | January 18, 2007 | Spottswood et al. |
| 20070019845 | January 25, 2007 | Kato |
| 20070029381 | February 8, 2007 | Braiman |
| 20070032225 | February 8, 2007 | Konicek et al. |
| 20070032288 | February 8, 2007 | Nelson et al. |
| 20070033072 | February 8, 2007 | Bildirici |
| 20070033150 | February 8, 2007 | Nwosu |
| 20070036396 | February 15, 2007 | Sugita et al. |
| 20070038751 | February 15, 2007 | Jorgensen |
| 20070043594 | February 22, 2007 | Lavergne |
| 20070050259 | March 1, 2007 | Wesley |
| 20070050398 | March 1, 2007 | Mochizuki |
| 20070051794 | March 8, 2007 | Glanz et al. |
| 20070051798 | March 8, 2007 | Kawai et al. |
| 20070055630 | March 8, 2007 | Gauthier et al. |
| 20070060095 | March 15, 2007 | Subrahmanya et al. |
| 20070060319 | March 15, 2007 | Block et al. |
| 20070064742 | March 22, 2007 | Shvodian |
| 20070069852 | March 29, 2007 | Mo et al. |
| 20070070040 | March 29, 2007 | Chen et al. |
| 20070072636 | March 29, 2007 | Worfolk et al. |
| 20070073553 | March 29, 2007 | Flinn et al. |
| 20070084523 | April 19, 2007 | McLean et al. |
| 20070084913 | April 19, 2007 | Weston |
| 20070087682 | April 19, 2007 | DaCosta |
| 20070087834 | April 19, 2007 | Moser et al. |
| 20070100507 | May 3, 2007 | Simon |
| 20070100939 | May 3, 2007 | Bagley et al. |
| 20070109117 | May 17, 2007 | Heitzmann et al. |
| 20070112676 | May 17, 2007 | Kontio et al. |
| 20070118891 | May 24, 2007 | Buer |
| 20070120643 | May 31, 2007 | Jiunn-Chung |
| 20070132586 | June 14, 2007 | Plocher et al. |
| 20070133478 | June 14, 2007 | Armbruster et al. |
| 20070136407 | June 14, 2007 | Rudelic |
| 20070142032 | June 21, 2007 | Balsillie |
| 20070152826 | July 5, 2007 | August et al. |
| 20070156850 | July 5, 2007 | Corrion |
| 20070157249 | July 5, 2007 | Cordray et al. |
| 20070158411 | July 12, 2007 | Krieg, Jr. |
| 20070159301 | July 12, 2007 | Hirt et al. |
| 20070159994 | July 12, 2007 | Brown et al. |
| 20070164847 | July 19, 2007 | Crawford et al. |
| 20070169121 | July 19, 2007 | Hunt et al. |
| 20070174809 | July 26, 2007 | Brown et al. |
| 20070176756 | August 2, 2007 | Friedrich |
| 20070176778 | August 2, 2007 | Ando et al. |
| 20070180047 | August 2, 2007 | Dong et al. |
| 20070187266 | August 16, 2007 | Porter et al. |
| 20070192601 | August 16, 2007 | Spain et al. |
| 20070194882 | August 23, 2007 | Yokota et al. |
| 20070198436 | August 23, 2007 | Weiss |
| 20070204078 | August 30, 2007 | Boccon-Gibod et al. |
| 20070205860 | September 6, 2007 | Jones et al. |
| 20070205861 | September 6, 2007 | Nair et al. |
| 20070213048 | September 13, 2007 | Trauberg |
| 20070214492 | September 13, 2007 | Gopi et al. |
| 20070218921 | September 20, 2007 | Lee et al. |
| 20070219926 | September 20, 2007 | Korn |
| 20070220272 | September 20, 2007 | Campisi et al. |
| 20070229268 | October 4, 2007 | Swan et al. |
| 20070245157 | October 18, 2007 | Giobbi et al. |
| 20070245158 | October 18, 2007 | Giobbi |
| 20070247366 | October 25, 2007 | Smith et al. |
| 20070258626 | November 8, 2007 | Reiner |
| 20070260883 | November 8, 2007 | Giobbi |
| 20070260888 | November 8, 2007 | Giobbi et al. |
| 20070266257 | November 15, 2007 | Camaisa et al. |
| 20070268862 | November 22, 2007 | Singh et al. |
| 20070271194 | November 22, 2007 | Walker et al. |
| 20070271433 | November 22, 2007 | Takemura |
| 20070277044 | November 29, 2007 | Graf et al. |
| 20070280509 | December 6, 2007 | Owen et al. |
| 20070285212 | December 13, 2007 | Rotzoll |
| 20070285238 | December 13, 2007 | Batra |
| 20070288263 | December 13, 2007 | Rodgers |
| 20070288752 | December 13, 2007 | Chan |
| 20070293155 | December 20, 2007 | Liao et al. |
| 20070294755 | December 20, 2007 | Dadhia et al. |
| 20070296544 | December 27, 2007 | Beenau et al. |
| 20080001783 | January 3, 2008 | Cargonja et al. |
| 20080005432 | January 3, 2008 | Kagawa |
| 20080008359 | January 10, 2008 | Beenau et al. |
| 20080011842 | January 17, 2008 | Curry et al. |
| 20080012685 | January 17, 2008 | Friedrich et al. |
| 20080012767 | January 17, 2008 | Caliri et al. |
| 20080016004 | January 17, 2008 | Kurasaki et al. |
| 20080019578 | January 24, 2008 | Saito et al. |
| 20080028227 | January 31, 2008 | Sakurai |
| 20080028453 | January 31, 2008 | Nguyen et al. |
| 20080040609 | February 14, 2008 | Giobbi |
| 20080046366 | February 21, 2008 | Bemmel et al. |
| 20080046715 | February 21, 2008 | Balazs et al. |
| 20080049700 | February 28, 2008 | Shah et al. |
| 20080061941 | March 13, 2008 | Fischer et al. |
| 20080071577 | March 20, 2008 | Highley |
| 20080072063 | March 20, 2008 | Takahashi et al. |
| 20080088475 | April 17, 2008 | Martin |
| 20080090548 | April 17, 2008 | Ramalingam |
| 20080095359 | April 24, 2008 | Schreyer et al. |
| 20080107089 | May 8, 2008 | Larsson et al. |
| 20080109895 | May 8, 2008 | Janevski |
| 20080111752 | May 15, 2008 | Lindackers et al. |
| 20080127176 | May 29, 2008 | Lee et al. |
| 20080129450 | June 5, 2008 | Riegebauer |
| 20080148351 | June 19, 2008 | Bhatia et al. |
| 20080149705 | June 26, 2008 | Giobbi et al. |
| 20080150678 | June 26, 2008 | Giobbi et al. |
| 20080156866 | July 3, 2008 | McNeal |
| 20080164997 | July 10, 2008 | Aritsuka et al. |
| 20080169909 | July 17, 2008 | Park et al. |
| 20080186166 | August 7, 2008 | Zhou et al. |
| 20080188308 | August 7, 2008 | Shepherd et al. |
| 20080195863 | August 14, 2008 | Kennedy |
| 20080201768 | August 21, 2008 | Koo et al. |
| 20080203107 | August 28, 2008 | Conley et al. |
| 20080209571 | August 28, 2008 | Bhaskar et al. |
| 20080218416 | September 11, 2008 | Handy et al. |
| 20080222701 | September 11, 2008 | Saaranen et al. |
| 20080223918 | September 18, 2008 | Williams et al. |
| 20080228524 | September 18, 2008 | Brown |
| 20080235144 | September 25, 2008 | Phillips |
| 20080238625 | October 2, 2008 | Rofougaran et al. |
| 20080250388 | October 9, 2008 | Meyer et al. |
| 20080251579 | October 16, 2008 | Larsen |
| 20080278325 | November 13, 2008 | Zimman et al. |
| 20080289030 | November 20, 2008 | Poplett |
| 20080289032 | November 20, 2008 | Aoki et al. |
| 20080303637 | December 11, 2008 | Gelbman et al. |
| 20080313728 | December 18, 2008 | Pandrangi et al. |
| 20080314971 | December 25, 2008 | Faith et al. |
| 20080316045 | December 25, 2008 | Sriharto et al. |
| 20090002134 | January 1, 2009 | McAllister |
| 20090013191 | January 8, 2009 | Popowski |
| 20090016573 | January 15, 2009 | McAfee, II et al. |
| 20090024584 | January 22, 2009 | Dharap et al. |
| 20090033464 | February 5, 2009 | Friedrich |
| 20090033485 | February 5, 2009 | Naeve et al. |
| 20090036164 | February 5, 2009 | Rowley |
| 20090041309 | February 12, 2009 | Kim et al. |
| 20090045916 | February 19, 2009 | Nitzan et al. |
| 20090052389 | February 26, 2009 | Qin et al. |
| 20090070146 | March 12, 2009 | Haider et al. |
| 20090076849 | March 19, 2009 | Diller |
| 20090081996 | March 26, 2009 | Duggal et al. |
| 20090096580 | April 16, 2009 | Paananen |
| 20090125401 | May 14, 2009 | Beenau |
| 20090140045 | June 4, 2009 | Evans |
| 20090157512 | June 18, 2009 | King |
| 20090176566 | July 9, 2009 | Kelly |
| 20090177495 | July 9, 2009 | Abousy et al. |
| 20090199206 | August 6, 2009 | Finkenzeller et al. |
| 20090237245 | September 24, 2009 | Brinton et al. |
| 20090237253 | September 24, 2009 | Neuwirth |
| 20090239667 | September 24, 2009 | Rowe et al. |
| 20090253516 | October 8, 2009 | Hartmann et al. |
| 20090254971 | October 8, 2009 | Herz et al. |
| 20090264712 | October 22, 2009 | Baldus et al. |
| 20090310514 | December 17, 2009 | Jeon et al. |
| 20090313689 | December 17, 2009 | Nystrom et al. |
| 20090319788 | December 24, 2009 | Zick et al. |
| 20090320118 | December 24, 2009 | Muller et al. |
| 20090322510 | December 31, 2009 | Berger et al. |
| 20090328182 | December 31, 2009 | Malakapalli et al. |
| 20100005526 | January 7, 2010 | Tsuji et al. |
| 20100007498 | January 14, 2010 | Jackson |
| 20100022308 | January 28, 2010 | Hartmann et al. |
| 20100023074 | January 28, 2010 | Powers et al. |
| 20100037255 | February 11, 2010 | Sheehan et al. |
| 20100062743 | March 11, 2010 | Jonsson |
| 20100077214 | March 25, 2010 | Jogand-Coulomb et al. |
| 20100117794 | May 13, 2010 | Adams et al. |
| 20100134257 | June 3, 2010 | Puleston et al. |
| 20100169442 | July 1, 2010 | Liu et al. |
| 20100169964 | July 1, 2010 | Liu et al. |
| 20100172567 | July 8, 2010 | Prokoski |
| 20100174911 | July 8, 2010 | Isshiki |
| 20100188226 | July 29, 2010 | Seder et al. |
| 20100214100 | August 26, 2010 | Page |
| 20100277283 | November 4, 2010 | Burkart et al. |
| 20100277286 | November 4, 2010 | Burkart et al. |
| 20100291896 | November 18, 2010 | Corda |
| 20100305843 | December 2, 2010 | Yan et al. |
| 20100328033 | December 30, 2010 | Kamei |
| 20110072034 | March 24, 2011 | Sly et al. |
| 20110072132 | March 24, 2011 | Shafer et al. |
| 20110082735 | April 7, 2011 | Kannan et al. |
| 20110085287 | April 14, 2011 | Ebrom et al. |
| 20110091136 | April 21, 2011 | Danch et al. |
| 20110116358 | May 19, 2011 | Li et al. |
| 20110126188 | May 26, 2011 | Bernstein et al. |
| 20110227740 | September 22, 2011 | Wohltjen |
| 20110238517 | September 29, 2011 | Ramalingam et al. |
| 20110246790 | October 6, 2011 | Koh et al. |
| 20110266348 | November 3, 2011 | Denniston, Jr. |
| 20110307599 | December 15, 2011 | Saretto et al. |
| 20120028609 | February 2, 2012 | Hruska |
| 20120030006 | February 2, 2012 | Yoder et al. |
| 20120069776 | March 22, 2012 | Caldwell et al. |
| 20120086571 | April 12, 2012 | Scalisi et al. |
| 20120182123 | July 19, 2012 | Butler et al. |
| 20120212322 | August 23, 2012 | Idsoe |
| 20120226451 | September 6, 2012 | Bacot et al. |
| 20120226565 | September 6, 2012 | Drozd |
| 20120226907 | September 6, 2012 | Hohberger et al. |
| 20120226990 | September 6, 2012 | Hohberger et al. |
| 20120238287 | September 20, 2012 | Scherzer |
| 20120278188 | November 1, 2012 | Attar et al. |
| 20120310720 | December 6, 2012 | Balsan et al. |
| 20130019295 | January 17, 2013 | Park et al. |
| 20130019323 | January 17, 2013 | Arvidsson et al. |
| 20130044111 | February 21, 2013 | VanGilder et al. |
| 20130111543 | May 2, 2013 | Brown et al. |
| 20130135082 | May 30, 2013 | Xian et al. |
| 20130179201 | July 11, 2013 | Fuerstenberg et al. |
| 20130276140 | October 17, 2013 | Coffing et al. |
| 20130331063 | December 12, 2013 | Cormier et al. |
| 20140074696 | March 13, 2014 | Glaser |
| 20140147018 | May 29, 2014 | Argue et al. |
| 20140266604 | September 18, 2014 | Masood et al. |
| 20140266713 | September 18, 2014 | Sehgal et al. |
| 20150039451 | February 5, 2015 | Bonfiglio |
| 20150294293 | October 15, 2015 | Signarsson |
| 20150310385 | October 29, 2015 | King et al. |
| 20150310440 | October 29, 2015 | Hynes et al. |
| 20160210614 | July 21, 2016 | Hall |
| 20160300236 | October 13, 2016 | Wiley et al. |
| 20170085564 | March 23, 2017 | Giobbi et al. |
| 20170091548 | March 30, 2017 | Agrawal et al. |
| 20180322718 | November 8, 2018 | Qian et al. |
| 20180357475 | December 13, 2018 | Honda et al. |
| 20190172281 | June 6, 2019 | Einberg et al. |
| 20190260724 | August 22, 2019 | Hefetz et al. |
| H10-49604 | February 1998 | JP |
| 00/62505 | October 2000 | WO |
| 01/22724 | March 2001 | WO |
| 01/35334 | May 2001 | WO |
| 01/75876 | October 2001 | WO |
| 01/77790 | October 2001 | WO |
| 2004/010774 | February 2004 | WO |
| 2004/038563 | May 2004 | WO |
| 2005/031663 | April 2005 | WO |
| 2005/050450 | June 2005 | WO |
| 2005/086802 | September 2005 | WO |
| 2007/087558 | August 2007 | WO |
- White, “How Computers Work”, Millennium Edition, 1999, Que Corporation, Indianapolis, IN, all pages.
- Derfler, “How Networks Work,” Bestseller Edition, 1996, Ziff-Davis Press, Emeryville, CA, all pages.
- Gralla, “How the Internet Works,” Millennium Edition, 1999, Que Corporation, Indianapolis, IN, all pages.
- Muller, “Desktop Encyclopedia of the Internet,” 1999, Artech House Inc., Norwood, MA, all pages.
- Giobbi, John, Specification of U.S. Appl. No. 60/824,758, all pages.
- PCT International Search Report and Written Opinion, PCT/US2009/039943, dated Jun. 1, 2009, 9 pages.
- Nilsson et al., “Match-on-Card for Java Cards,” Precise Biometrics, white paper, Apr. 2004, retrieved from www.ibia.org/membersadmin/whitepapers/pdf/17/Precise%20Match-on-Card%20for%20Java%20Cards.pdf on Jan. 7, 2007, 5 pgs.
- Noore, “Highly Robust Biometric Smart Card Design.” IEEE Transactions on Consumer Electronics, vol. 46, No. 4, Nov. 2000, pp. 1059-1063.
- Nordin, “Match-on-Card Technology,” Precise Biometrics, white paper, Apr. 2004, retrieved from www.ibia.org/membersadmin/whitepapers/pdf/17/Precise%20Match-on-Card%20technology.pdf on Jan. 7, 2007, 7 pgs.
- Paget, “The Security Behind Secure Extranets,” Enterprise Systems Journal, vol. 14, No. 12, Dec. 1999, 4 pgs.
- Pash, “Automate proximity and location-based computer actions,” Jun. 5, 2007, retrieved from http://lifehacker.com/265822/automate-proximity-and-location+based-computer-actions on or before Oct. 11, 2011, 3 pgs.
- Pope et al., “Oasis Digital Signature Services: Digital Signing without the Headaches,” IEEE Internet Computing, vol. 10, Sep./Oct. 2006, pp. 81-84.
- Saflink Corporation, “SAFModule™: A Look Into Strong Authentication,” white paper, retrieved from www.ibia.org/membersadmin/whitepapers/pdf/6/SAFmod_WP.pdf on Jan. 7, 2007, 8 pgs.
- Sapsford, “E-Business: Sound Waves Could Help Ease Web-Fraud Woes,” Wall Street Journal, Aug. 14, 2000, p. B1.
- Singh et al. “A Constraint-Based Biometric Scheme on ATM and Swiping Machine.” 2016 International Conference on Computational Techniques in Information and Communication Technologies (ICCTICT), Mar. 11, 2016, pp. 74-79.
- Smart Card Alliance, “Contactless Technology for Secure Physical Access: Technology and Standards Choices,” Smart Card Alliance, Oct. 2002, pp. 1-48.
- Smart Card Alliance, “Alliance Activities: Publications: Identity: Identity Management Systems, Smart Cards and Privacy,” 1997-2007, retrieved from www.smartcardalliance.org/pages/publications-identity on Jan. 7, 2007, 3 pgs.
- SplashID, “SplashID—Secure Password Manager for PDAs and Smartphones,” Mar. 8, 2007, retrieved from http://www.splashdata.com/splashid/ via http://www.archive.org/ on or before Oct. 11, 2011, 2 pgs.
- Srivastava, “Is internet security a major issue with respect to the slow acceptance rate of digital signatures,” Jan. 2, 2005, Computer Law & Security Report, pp. 392-404.
- Thomson Multimedia, “Thomson multimedia unveils copy protection proposal designed to provide additional layer of digital content security,” retrieved from www.thompson-multimedia.com/gb/06/c01/010530.htm on Mar. 4, 2002, May 30, 2001, 2 pgs.
- Unixhelp, “What is a file?” Apr. 30, 1998, retrieved from unixhelp.ed.ac.uk/editors/whatisafile.html.accessed Mar. 11, 2010 via http://waybackmachine.org/19980615000000*/http://unixhelp.ed.ac.uk/editors/whatisafile.html on Mar. 11, 2011, 1 pg.
- Vainio, “Bluetooth Security,” Helsinki University of Technology, May 25, 2000, 17 pgs.
- Van Winkle, “Bluetooth: The King of Connectivity,” Laptop Buyer's Guide and Handbook, Jan. 2000, pp. 148-153.
- Wade, “Using Fingerprints to Make Payments at POS Slowly Gaining Popularity,” Credit Union Journal, International Biometric Group, Apr. 21, 2003, retrieved from http://www.biometricgroup.com/in_the_news/04.21.03.html on Jan. 7, 2007, 3 pgs.
- Wallace, “The Internet Unplugged,” InformationWeek, vol. 765, No. 22, Dec. 13, 1999, pp. 22-24.
- Weber, “In the Age of Napster, Protecting Copyright is a Digital Arms Race,” Wall Street Journal, Eastern ed., Jul. 24, 2000, p. B1.
- Yoshida, “Content protection plan targets wireless home networks,” EE Times, Jan. 11, 2002, retrieved from www.eetimes.com/story/OEG20020111S0060 on Mar. 4, 2002, 2 pgs.
- Anonymous, “Applying Biometrics to Door Access,” Security Magazine, Sep. 26, 2002, retrieved from http://www. securitymagazine.com/CDA/Articles/Technologies/3ae610eaa34d8010VgnVCM100000f932a8c0_ on Jan. 7, 2007, 5 pgs.
- Anonymous, “Firecrest Shows How Truly Commercially-Minded Companies Will Exploit the Internet,” Computergram International, Jan. 18, 1996, 2 pgs.
- Anonymous, “IEEE 802.15.4-2006—Wikipedia, the free encyclopedia,” Wikipedia, last modified Mar. 21, 2009, retrieved from http://en.wikipedia.org/wiki/IEEE_802.15.4-2006 on Apr. 30, 2009, 5 pgs.
- Antonoff, “Visiting Video Valley,” Sound & Vision, Nov. 2001, pp. 116, 118-119.
- Apple et al., “Smart Card Setup Guide,” 2006, downloaded from http://manuals.info.apple.com/en_US/Smart_Card_Setup_Guide.pdf on or before May 3, 2012, 16 pgs.
- Balanis, “Antenna Theory: A Review,” Jan. 1992, Proceedings of the IEEE, vol. 80, No. 1, p. 13.
- Beaufour, “Personal Servers as Digital Keys,” Proceedings of the Second IEEE Annual Conference on Pervasive Computing and Communications (PERCOM'04), Mar. 14-17, 2004, pp. 319-328.
- Biopay, LLC, “Frequently Asked Questions (FAQs) About BioPay,” retrieved from http://www.biopay.com/faqs-lowes.asp on Jan. 7, 2007, 5 pgs.
- BlueProximity, “BlueProximity—Leave it—it's locked, come back, it's back too . . . ” Aug. 26, 2007, retrieved from http://blueproximity.sourceforge.net/ via http://www.archive.org/ on or before Oct. 11, 2011, 1 pg.
- Bluetooth Sig, Inc. “Bluetooth,” www.bluetoothcom, Jun. 1, 2000, 8 pgs.
- Bluetooth Sig, Inc., “Say Hello to Bluetooth,” retrieved from www.bluetooth.com, at least as early as Jan. 14, 2005, 4 pgs.
- Blum, “Digital Rights Management May Solve the Napster ‘Problem,’” Technology Investor, Oct. 2000, pp. 24-27.
- Bohrsatom et al., “Automatically unlock PC when entering proximity,” Dec. 7, 2005, retrieved from http://salling.com/forums/viewtopic.php?t=3190 on or before Oct. 11, 2011, 3 pgs.
- Brown, “Techniques for Privacy and Authentication in Personal Communication Systems,” Personal Communications, IEEE, Aug. 1995, vol. 2, No. 4, pp. 6-10.
- Chen et al. “On Enhancing Biometric Authentication with Data Protection.” KES2000. Fourth International Conference on Knowledge-Based Intelligent Engineering Systems and Allied Technologies. Proceedings (Cat. No. 00TH8516), vol. 1, Aug. 1, 2000, pp. 249-252.
- Cisco Systems, Inc., “Antenna Patterns and Their Meaning,” 1992-2007, p. 10.
- Costa, “Imation USB 2.0 Micro Hard Drive,” Nov. 22, 2005, retrieved from http://www.pcmag.com/article2/0,2817,1892209,00.asp on or before Oct. 11, 2011, 2 pgs.
- Dagan, “Power over Ethernet (PoE) Midspan—The Smart Path to Providign Power for IP Telephony,” Product Manager, Systems, Aug. 2005, Power Dsine Inc., 28 pgs.
- Dai et al., “Toward Blockchain-Based Accounting and Assurance”, 2017, Journal of Information Systems, pp. 5-21.
- Debow, “Credit/Debit Debuts in Midwest Smart Card Test,” Computers in Banking, vol. 6, No. 11, Nov. 1989, pp. 10-13.
- Dennis, “Digital Passports Need Not Infringe Civil Liberties,” Newsbytes, NA, Dec. 2, 1999, 2 pgs.
- Farouk et al., “Authentication Mechanisms in Grid Computing Environment: Comparative Study,” IEEE, Oct. 2012, p. 1-6.
- Fasca, “S3, Via Formalize Agreement,” Electronic News, The Circuit, 45(45, Nov. 8, 1999), p. 20.
- Govindan et al. “Real Time Security Management Using RFID, Biometric and Smart Messages.” 2009 3rd International Conference on Anti-Counterfeiting, Security, and Identification in Communication, Aug. 20, 2009, pp. 282-285.
- Hendron, “File Security, Keychains, Encryptioin, and More with Mac OS X (10.3+)” Apr. 4, 2005, downloaded from http://www.johnhendron.net/documents/OSX_Security.pdf on or before May 3, 2012, 30 pgs.
- International Search Report and Written Opinion for International Application No. PCT/US04/38124, dated Apr. 7, 2005, 10 pgs.
- International Search Report and Written Opinion for International Application No. PCT/US05/07535, dated Dec. 6, 2005, 6 pgs.
- International Search Report and Written Opinion for International Application No. PCT/US05/43447, dated Feb. 22, 2007, 7 pgs.
- International Search Report and Written Opinion for International Application No. PCT/US05/46843, dated Mar. 1, 2007, 10 pgs.
- International Search Report and Written Opinion for International Application No. PCT/US07/00349, dated Mar. 19, 2008, 10 pgs.
- International Search Report and Written Opinion for International Application No. PCT/US07/11102, dated Oct. 3, 2008, 11 pgs.
- International Search Report and Written Opinion for International Application No. PCT/US07/11103, dated Apr. 23, 2008, 9 pgs.
- International Search Report and Written Opinion for International Application No. PCT/US07/11104, dated Jun. 26, 2008, 9 pgs.
- International Search Report and Written Opinion for International Application No. PCT/US07/11105, dated Oct. 20, 2008, 10 pgs.
- International Search Report and Written Opinion for International Application No. PCT/US08/83060, dated Dec. 29, 2008, 9 pgs.
- International Search Report and Written Opinion for International Application No. PCT/US08/87835, dated Feb. 11, 2009, 8 pgs.
- International Search Report and Written Opinion for International Application No. PCT/US09/34095, dated Mar. 25, 2009, 11 pgs.
- International Search Report and Written Opinion for International Application No. PCT/US2014/037609, dated Dec. 9, 2014, 13 pgs.
- Jeyaprakash et al. “Secured Smart Card Using Palm Vein Biometric On-Card-Process.” 2008 International Conference on Convergence and Hybrid Information Technology, 2008, pp. 548-551.
- Katz et al., “Smart Cards and Biometrics in Privacy-Sensitive Secure Personal Identification System,” May 2002, Smart Card Alliance, p. 1-29.
- Kontzer, “Thomson Bets on Smart Cards for Video Encryption,” InformationWeek, Jun. 7, 2001, retrieved from www.informationweek.com/story/IWK2001060730013 on Mar. 4, 2002, 1 pg.
- Lake, “Downloading for Dollars: Who said buying music off the Net would be easy?,” Sound & Vision, Nov. 2000, pp. 137-138.
- Lee et al., “Effects of dielectric superstrates on a two-layer electromagnetically coupled patch antenna,” Antennas and Propagation Society International Symposium, Jun. 1989, AP-S. Digest, vol. 2, pp. 26-30, found at http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=1347.
- Lewis, “Sony and Visa in On-Line Entertainment Venture,” New York Times, vol. 145, Thurs. Ed., Nov. 16, 1995, 1 pg.
- Liu et al., “A Practical Guide to Biometric Security Technology, ” IT Pro, vol. 3, No. 1, Jan./Feb. 2001, pp. 27-32.
- McIver et al., “Identification and Verification Working Together,” Bioscrypt, White Paper: Identification and Verification Working Together, Aug. 27, 2004, retrieved from www.ibia.org/membersadmin/whitepapers/pdf/15/Identification%20and%20Verification%20Working%20Together.pdf on Jan. 7, 2007, 5 pgs.
- Micronas, “Micronas and Thomson Multimedia Showcase a New Copy Protection System that Will Drive the Future of Digital Television,” Jan. 8, 2002, retrieved from www.micronas.com/press/pressreleases/printer.php?ID=192 on Mar. 4, 2002, 3 pgs.
- National Criminal Justice Reference Service, “Antenna Types,” Dec. 11, 2006, online at http://ncjrs.gov/pdfffiles1/nij/185030b.pdf, retrieved from http://web.archive.org/web/*/http://www.ncjrs.gov/pdffiles1/nij/185030b.pdf on Jan. 12, 2011, 1 pg.
- Nel et al., “Generation of Keys for use with the Digital Signature Standard (DSS),” Communications and Signal Processing, Proceedings of the 1993 IEEE South African Symposium, Aug. 6, 1993, pp. 6-11.
- Nerd Vittles, “magicJack: Could It Be the Asterisk Killer?” Aug. 1, 2007, retrieved from http://nerdvittles.com/index.php?p=187 on or before Oct. 11, 2011, 2 pgs.
- IEEE Computer Society, “IEEE Std 802.15.4™—Part 15.4: Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications for Low-Rate Wireless Personal Area Networks (LR-WPANs),” The Institute of Electrical and Electronics Engineers, Inc., New York, NY, Oct. 1, 2003, 679 pgs.
- International Search Report received for PCT Patent Application No. PCT/US2001/049916, dated Apr. 25, 2002, 1 page.
- Smart Cards and Biometrics White Paper: Smart Card Alliance, May 2002, [online] [Retrieved on Jan. 7, 2007] Retrieved from the Internet<URL:http://www.securitymanagement.com/librarylsmartcard_faqte- ch0802.pdf>, 7 pages.
Type: Grant
Filed: Apr 8, 2009
Date of Patent: Sep 14, 2021
Patent Publication Number: 20090254448
Assignee: Proxense, LLC (Bend, OR)
Inventor: John J. Giobbi (Bend, OR)
Primary Examiner: Jacob C. Coppola
Application Number: 12/420,277
International Classification: G06Q 20/40 (20120101); G06Q 20/42 (20120101); G06Q 20/32 (20120101); G06K 9/00 (20060101); G06Q 30/06 (20120101); G06Q 30/02 (20120101);
