Patent Grant
11120449
1. 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.
A 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.
The 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 100.
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.
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.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3665313 | Trent | May 1972 | A |
| 3739329 | Lester | Jun 1973 | A |
| 3761883 | Alvarez et al. | Sep 1973 | A |
| 3906166 | Cooper et al. | Sep 1975 | A |
| 4101873 | Anderson et al. | Jul 1978 | A |
| 4430705 | Cannavino et al. | Feb 1984 | A |
| 4476469 | Lander | Oct 1984 | A |
| 4598272 | Cox | Jul 1986 | A |
| 4661821 | Smith | Apr 1987 | A |
| 4759060 | Hayashi et al. | Jul 1988 | A |
| 4814742 | Morita et al. | Mar 1989 | A |
| 4871997 | Adriaenssens et al. | Oct 1989 | A |
| 4993068 | Piosenka et al. | Feb 1991 | A |
| 5043702 | Kuo | Aug 1991 | A |
| 5187352 | Blair et al. | Feb 1993 | A |
| 5224164 | Elsner | Jun 1993 | A |
| 5296641 | Stelzel | Mar 1994 | A |
| 5307349 | Shloss et al. | Apr 1994 | A |
| 5317572 | Satoh | May 1994 | A |
| 5325285 | Araki | Jun 1994 | A |
| 5392287 | Tiedemann, Jr. et al. | Feb 1995 | A |
| 5392433 | Hammersley et al. | Feb 1995 | A |
| 5410588 | Ito | Apr 1995 | A |
| 5416780 | Patel | May 1995 | A |
| 5422632 | Bucholtz et al. | Jun 1995 | A |
| 5428684 | Akiyama et al. | Jun 1995 | A |
| 5450489 | Ostrover et al. | Sep 1995 | A |
| 5473690 | Grimonprez et al. | Dec 1995 | A |
| 5481265 | Russell | Jan 1996 | A |
| 5506863 | Meidan et al. | Apr 1996 | A |
| 5517502 | Bestler et al. | May 1996 | A |
| 5541583 | Mandelbaum | Jul 1996 | A |
| 5544321 | Theimer et al. | Aug 1996 | A |
| 5552776 | Wade et al. | Sep 1996 | A |
| 5563947 | Kikinis | Oct 1996 | A |
| 5589838 | McEwan | Dec 1996 | A |
| 5594227 | Deo | Jan 1997 | A |
| 5598474 | Johnson | Jan 1997 | A |
| 5611050 | Theimer et al. | Mar 1997 | A |
| 5619251 | Kuroiwa et al. | Apr 1997 | A |
| 5623552 | Lane | Apr 1997 | A |
| 5629980 | Stefik et al. | May 1997 | A |
| 5644354 | Thompson et al. | Jul 1997 | A |
| 5666412 | Handelman et al. | Sep 1997 | A |
| 5689529 | Johnson | Nov 1997 | A |
| 5692049 | Johnson et al. | Nov 1997 | A |
| 5719387 | Fujioka | Feb 1998 | A |
| 5729237 | Webb | Mar 1998 | A |
| 5760705 | Glessner et al. | Jun 1998 | A |
| 5760744 | Sauer | Jun 1998 | A |
| 5773954 | VanHorn | Jun 1998 | A |
| 5784464 | Akiyama et al. | Jul 1998 | A |
| 5799085 | Shona | Aug 1998 | A |
| 5821854 | Dorinski et al. | Oct 1998 | A |
| 5825876 | Peterson, Jr. | Oct 1998 | A |
| 5835595 | Fraser et al. | Nov 1998 | A |
| 5838306 | O'Connor et al. | Nov 1998 | A |
| 5854891 | Postlewaite et al. | Dec 1998 | A |
| 5857020 | Peterson, Jr. | Jan 1999 | A |
| 5886634 | Muhme | Mar 1999 | A |
| 5892825 | Mages et al. | Apr 1999 | A |
| 5892900 | Ginter et al. | Apr 1999 | A |
| 5894551 | Huggins et al. | Apr 1999 | A |
| 5898880 | Ryu | Apr 1999 | A |
| 5910776 | Black | Jun 1999 | A |
| 5917913 | Wang | Jun 1999 | A |
| 5923757 | Hocker et al. | Jul 1999 | A |
| 5928327 | Wang et al. | Jul 1999 | A |
| 5991399 | Graunke et al. | Nov 1999 | A |
| 5991749 | Morrill, Jr. | Nov 1999 | A |
| 6016476 | Maes et al. | Jan 2000 | A |
| 6018739 | McCoy et al. | Jan 2000 | A |
| 6025780 | Bowers et al. | Feb 2000 | A |
| 6035038 | Campinos et al. | Mar 2000 | A |
| 6035329 | Mages et al. | Mar 2000 | A |
| 6038334 | Hamid | Mar 2000 | A |
| 6038666 | Hsu et al. | Mar 2000 | A |
| 6040786 | Fujioka | Mar 2000 | A |
| 6041410 | Hsu et al. | Mar 2000 | A |
| 6042006 | Van Tilburg et al. | Mar 2000 | A |
| 6055314 | Spies et al. | Apr 2000 | A |
| 6068184 | Barnett | May 2000 | A |
| 6070796 | Sirbu | Jun 2000 | A |
| 6076164 | Tanaka et al. | Jun 2000 | A |
| 6088450 | Davis et al. | Jul 2000 | A |
| 6088730 | Kato et al. | Jul 2000 | A |
| 6104290 | Naguleswaran | Aug 2000 | A |
| 6104334 | Allport | Aug 2000 | A |
| 6110041 | Walker et al. | Aug 2000 | A |
| 6121544 | Petsinger | Sep 2000 | A |
| 6134283 | Sands et al. | Oct 2000 | A |
| 6137480 | Shintani | Oct 2000 | A |
| 6138010 | Rabe et al. | Oct 2000 | A |
| 6148142 | Anderson | Nov 2000 | A |
| 6148210 | Elwin et al. | Nov 2000 | A |
| 6161179 | Seidel | Dec 2000 | A |
| 6177887 | Jerome | Jan 2001 | B1 |
| 6185316 | Buffam | Feb 2001 | B1 |
| 6189105 | Lopes | Feb 2001 | B1 |
| 6209089 | Selitrennikoff et al. | Mar 2001 | B1 |
| 6219109 | Raynesford et al. | Apr 2001 | B1 |
| 6219439 | Burger | Apr 2001 | B1 |
| 6219553 | Panasik | Apr 2001 | B1 |
| 6237848 | Everett | May 2001 | B1 |
| 6240076 | Kanerva et al. | May 2001 | B1 |
| 6247130 | Fritsch | Jun 2001 | B1 |
| 6249869 | Drupsteen et al. | Jun 2001 | B1 |
| 6256737 | Bianco et al. | Jul 2001 | B1 |
| 6266415 | Campinos et al. | Jul 2001 | B1 |
| 6270011 | Gottfried | Aug 2001 | B1 |
| 6279111 | Jensenworth et al. | Aug 2001 | B1 |
| 6279146 | Evans et al. | Aug 2001 | B1 |
| 6295057 | Rosin et al. | Sep 2001 | B1 |
| 6307471 | Xydis | Oct 2001 | B1 |
| 6325285 | Baratelli | Dec 2001 | B1 |
| 6336121 | Lyson et al. | Jan 2002 | B1 |
| 6336142 | Kato et al. | Jan 2002 | B1 |
| 6343280 | Clark | Jan 2002 | B2 |
| 6345347 | Biran | Feb 2002 | B1 |
| 6363485 | Adams et al. | Mar 2002 | B1 |
| 6367019 | Ansell et al. | Apr 2002 | B1 |
| 6369693 | Gibson | Apr 2002 | B1 |
| 6370376 | Sheath | Apr 2002 | B1 |
| 6381029 | Tipirneni | Apr 2002 | B1 |
| 6381747 | Wonfor et al. | Apr 2002 | B1 |
| 6385596 | Wiser et al. | May 2002 | B1 |
| 6392664 | White et al. | May 2002 | B1 |
| 6397387 | Rosin et al. | May 2002 | B1 |
| 6401059 | Shen et al. | Jun 2002 | B1 |
| 6411307 | Rosin et al. | Jun 2002 | B1 |
| 6424249 | Houvener | Jul 2002 | B1 |
| 6424715 | Saito | Jul 2002 | B1 |
| 6425084 | Rallis et al. | Jul 2002 | B1 |
| 6434403 | Ausems et al. | Aug 2002 | B1 |
| 6434535 | Kupka et al. | Aug 2002 | B1 |
| 6446004 | Cao et al. | Sep 2002 | B1 |
| 6446130 | Grapes et al. | Sep 2002 | B1 |
| 6463534 | Geiger et al. | Oct 2002 | B1 |
| 6480101 | Kelly et al. | Nov 2002 | B1 |
| 6480188 | Horsley | Nov 2002 | B1 |
| 6484182 | Dunphy et al. | Nov 2002 | B1 |
| 6484260 | Scott et al. | Nov 2002 | B1 |
| 6484946 | Matsumoto et al. | Nov 2002 | B2 |
| 6487663 | Jaisimha et al. | Nov 2002 | B1 |
| 6490443 | Freeny, Jr. | Dec 2002 | B1 |
| 6510350 | Steen, III et al. | Jan 2003 | B1 |
| 6522253 | Saltus | Feb 2003 | B1 |
| 6523113 | Wehrenberg | Feb 2003 | B1 |
| 6529949 | Getsin et al. | Mar 2003 | B1 |
| 6546418 | Schena et al. | Apr 2003 | B2 |
| 6550011 | Sims, III | Apr 2003 | B1 |
| 6563465 | Frecska | May 2003 | B2 |
| 6563805 | Ma et al. | May 2003 | B1 |
| 6564380 | Murphy | May 2003 | B1 |
| 6577238 | Whitesmith et al. | Jun 2003 | B1 |
| 6593887 | Luk et al. | Jul 2003 | B2 |
| 6597680 | Lindskog et al. | Jul 2003 | B1 |
| 6607136 | Atsmon et al. | Aug 2003 | B1 |
| 6628302 | White et al. | Sep 2003 | B2 |
| 6632992 | Hasegawa | Oct 2003 | B2 |
| 6633981 | Davis | Oct 2003 | B1 |
| 6645077 | Rowe | Nov 2003 | B2 |
| 6647417 | Hunter et al. | Nov 2003 | B1 |
| 6657538 | Ritter | Dec 2003 | B1 |
| 6658566 | Hazard | Dec 2003 | B1 |
| 6667684 | Waggamon et al. | Dec 2003 | B1 |
| 6669096 | Saphar et al. | Dec 2003 | B1 |
| 6671808 | Abbott et al. | Dec 2003 | B1 |
| 6683954 | Searle | Jan 2004 | B1 |
| 6697944 | Jones et al. | Feb 2004 | B1 |
| 6709333 | Bradford et al. | Mar 2004 | B1 |
| 6711464 | Yap et al. | Mar 2004 | B1 |
| 6714168 | Berenbaum | Mar 2004 | B2 |
| 6715246 | Frecska et al. | Apr 2004 | B1 |
| 6728397 | McNeal | Apr 2004 | B2 |
| 6737955 | Ghabra et al. | May 2004 | B2 |
| 6758394 | Maskatiya et al. | Jul 2004 | B2 |
| 6771969 | Chinoy et al. | Aug 2004 | B1 |
| 6775655 | Peinado et al. | Aug 2004 | B1 |
| 6785474 | Hirt et al. | Aug 2004 | B2 |
| 6788640 | Celeste | Sep 2004 | B2 |
| 6788924 | Knutson et al. | Sep 2004 | B1 |
| 6795425 | Raith | Sep 2004 | B1 |
| 6804825 | White et al. | Oct 2004 | B1 |
| 6806887 | Chernock et al. | Oct 2004 | B2 |
| 6839542 | Sibecas et al. | Jan 2005 | B2 |
| 6850147 | Prokoski et al. | Feb 2005 | B2 |
| 6853988 | Dickinson et al. | Feb 2005 | B1 |
| 6859812 | Poynor | Feb 2005 | B1 |
| 6861980 | Rowitch et al. | Mar 2005 | B1 |
| 6873975 | Hatakeyama et al. | Mar 2005 | B1 |
| 6879567 | Callaway et al. | Apr 2005 | B2 |
| 6879966 | Lapsley et al. | Apr 2005 | B1 |
| 6886741 | Salveson | May 2005 | B1 |
| 6889067 | Willey | May 2005 | B2 |
| 6891822 | Gubbi et al. | May 2005 | B1 |
| 6892307 | Wood et al. | May 2005 | B1 |
| 6930643 | Byrne et al. | Aug 2005 | B2 |
| 6947003 | Huor | Sep 2005 | B2 |
| 6950941 | Lee et al. | Sep 2005 | B1 |
| 6957086 | Bahl et al. | Oct 2005 | B2 |
| 6961858 | Fransdonk | Nov 2005 | B2 |
| 6963270 | Gallagher, III et al. | Nov 2005 | B1 |
| 6963971 | Bush et al. | Nov 2005 | B1 |
| 6973576 | Giobbi | Dec 2005 | B2 |
| 6975202 | Rodriguez et al. | Dec 2005 | B1 |
| 6980087 | Zukowksi | Dec 2005 | B2 |
| 6983882 | Cassone | Jan 2006 | B2 |
| 6999032 | Pakray et al. | Feb 2006 | B2 |
| 7012503 | Nielsen | Mar 2006 | B2 |
| 7020635 | Hamilton et al. | Mar 2006 | B2 |
| 7031945 | Donner | Apr 2006 | B1 |
| 7049963 | Waterhouse et al. | May 2006 | B2 |
| 7055171 | Martin et al. | May 2006 | B1 |
| 7058806 | Smeets et al. | Jun 2006 | B2 |
| 7061380 | Orlando et al. | Jun 2006 | B1 |
| 7068623 | Barany et al. | Jun 2006 | B1 |
| 7072900 | Sweitzer et al. | Jul 2006 | B2 |
| 7079079 | Jo et al. | Jul 2006 | B2 |
| 7080049 | Truitt et al. | Jul 2006 | B2 |
| 7082415 | Robinson et al. | Jul 2006 | B1 |
| 7090126 | Kelly et al. | Aug 2006 | B2 |
| 7090128 | Farley et al. | Aug 2006 | B2 |
| 7100053 | Brown et al. | Aug 2006 | B1 |
| 7107455 | Merkin | Sep 2006 | B1 |
| 7107462 | Fransdonk | Sep 2006 | B2 |
| 7111789 | Rajasekaran et al. | Sep 2006 | B2 |
| 7112138 | Hedrick et al. | Sep 2006 | B2 |
| 7119659 | Bonaile et al. | Oct 2006 | B2 |
| 7123149 | Nowak et al. | Oct 2006 | B2 |
| 7130668 | Chang et al. | Oct 2006 | B2 |
| 7131139 | Meier | Oct 2006 | B1 |
| 7137008 | Hamid et al. | Nov 2006 | B1 |
| 7137012 | Kamibayashi et al. | Nov 2006 | B1 |
| 7139914 | Arnouse | Nov 2006 | B2 |
| 7150045 | Koelle et al. | Dec 2006 | B2 |
| 7155416 | Shatford | Dec 2006 | B2 |
| 7159114 | Zajkowksi et al. | Jan 2007 | B1 |
| 7159765 | Frerking | Jan 2007 | B2 |
| 7167987 | Angelo | Jan 2007 | B2 |
| 7168089 | Nguyen et al. | Jan 2007 | B2 |
| 7176797 | Zai et al. | Feb 2007 | B2 |
| 7191466 | Hamid et al. | Mar 2007 | B1 |
| 7209955 | Major et al. | Apr 2007 | B1 |
| 7218944 | Cromer et al. | May 2007 | B2 |
| 7225161 | Lam et al. | May 2007 | B2 |
| 7230908 | Vanderaar et al. | Jun 2007 | B2 |
| 7231068 | Tibor | Jun 2007 | B2 |
| 7231451 | Law et al. | Jun 2007 | B2 |
| 7242923 | Perera et al. | Jul 2007 | B2 |
| 7249177 | Miller | Jul 2007 | B1 |
| 7272723 | Abbott et al. | Sep 2007 | B1 |
| 7277737 | Vollmer et al. | Oct 2007 | B1 |
| 7278025 | Saito et al. | Oct 2007 | B2 |
| 7283650 | Sharma et al. | Oct 2007 | B1 |
| 7295119 | Rappaport et al. | Nov 2007 | B2 |
| 7305560 | Giobbi | Dec 2007 | B2 |
| 7310042 | Seifert | Dec 2007 | B2 |
| 7314164 | Bonalle et al. | Jan 2008 | B2 |
| 7317799 | Hammersmith et al. | Jan 2008 | B2 |
| 7319395 | Puzio et al. | Jan 2008 | B2 |
| 7330108 | Thomas | Feb 2008 | B2 |
| 7333002 | Bixler et al. | Feb 2008 | B2 |
| 7333615 | Jarboe et al. | Feb 2008 | B1 |
| 7336181 | Nowak et al. | Feb 2008 | B2 |
| 7336182 | Baranowski et al. | Feb 2008 | B1 |
| 7337326 | Palmer et al. | Feb 2008 | B2 |
| 7341181 | Bonalle et al. | Mar 2008 | B2 |
| 7342503 | Light et al. | Mar 2008 | B1 |
| 7349557 | Tibor | Mar 2008 | B2 |
| 7356393 | Schlatre et al. | Apr 2008 | B1 |
| 7356706 | Scheurich | Apr 2008 | B2 |
| 7361919 | Setlak | Apr 2008 | B2 |
| 7363494 | Brainard et al. | Apr 2008 | B2 |
| 7370366 | Lacan et al. | May 2008 | B2 |
| 7378939 | Sengupta et al. | May 2008 | B2 |
| 7380202 | Lindhorst et al. | May 2008 | B1 |
| 7382799 | Young et al. | Jun 2008 | B1 |
| 7387235 | Gilbert et al. | Jun 2008 | B2 |
| 7401731 | Pletz et al. | Jul 2008 | B1 |
| 7424134 | Chou | Sep 2008 | B2 |
| 7437330 | Robinson et al. | Oct 2008 | B1 |
| 7447911 | Chou et al. | Nov 2008 | B2 |
| 7448087 | Ohmori et al. | Nov 2008 | B2 |
| 7458510 | Zhou | Dec 2008 | B1 |
| 7460836 | Smith et al. | Dec 2008 | B2 |
| 7461444 | Deaett et al. | Dec 2008 | B2 |
| 7464053 | Pylant | Dec 2008 | B1 |
| 7464059 | Robinson et al. | Dec 2008 | B1 |
| 7466232 | Neuwirth | Dec 2008 | B2 |
| 7472280 | Giobbi | Dec 2008 | B2 |
| 7512806 | Lemke | Mar 2009 | B2 |
| 7525413 | Jung et al. | Apr 2009 | B2 |
| 7529944 | Hamid | May 2009 | B2 |
| 7533809 | Robinson et al. | May 2009 | B1 |
| 7545312 | Kiang et al. | Jun 2009 | B2 |
| 7565329 | Lapsley et al. | Jul 2009 | B2 |
| 7573382 | Choubey et al. | Aug 2009 | B2 |
| 7573841 | Lee et al. | Aug 2009 | B2 |
| 7574734 | Fedronic et al. | Aug 2009 | B2 |
| 7583238 | Cassen et al. | Sep 2009 | B2 |
| 7583643 | Smith et al. | Sep 2009 | B2 |
| 7587502 | Crawford et al. | Sep 2009 | B2 |
| 7587611 | Johnson et al. | Sep 2009 | B2 |
| 7594611 | Arrington, III | Sep 2009 | B1 |
| 7595765 | Hirsch et al. | Sep 2009 | B1 |
| 7603564 | Adachi | Oct 2009 | B2 |
| 7606733 | Shmueli et al. | Oct 2009 | B2 |
| 7617523 | Das et al. | Nov 2009 | B2 |
| 7620184 | Marque Pucheu | Nov 2009 | B2 |
| 7624073 | Robinson et al. | Nov 2009 | B1 |
| 7624417 | Dua | Nov 2009 | B2 |
| 7640273 | Wallmeier et al. | Dec 2009 | B2 |
| 7644443 | Matsuyama et al. | Jan 2010 | B2 |
| 7646307 | Plocher et al. | Jan 2010 | B2 |
| 7652892 | Shiu et al. | Jan 2010 | B2 |
| 7676380 | Graves et al. | Mar 2010 | B2 |
| 7689005 | Wang et al. | Mar 2010 | B2 |
| 7706896 | Music et al. | Apr 2010 | B2 |
| 7711152 | Davida et al. | May 2010 | B1 |
| 7711586 | Aggarwal et al. | May 2010 | B2 |
| 7715593 | Adams et al. | May 2010 | B1 |
| 7724713 | Del Prado Pavon et al. | May 2010 | B2 |
| 7724717 | Porras et al. | May 2010 | B2 |
| 7724720 | Korpela et al. | May 2010 | B2 |
| 7764236 | Hill et al. | Jul 2010 | B2 |
| 7765164 | Robinson et al. | Jul 2010 | B1 |
| 7765181 | Thomas et al. | Jul 2010 | B2 |
| 7773754 | Buer et al. | Aug 2010 | B2 |
| 7774613 | Lemke | Aug 2010 | B2 |
| 7780082 | Handa et al. | Aug 2010 | B2 |
| 7796551 | Machiraju et al. | Sep 2010 | B1 |
| 7813822 | Hoffberg | Oct 2010 | B1 |
| 7865448 | Pizarro | Jan 2011 | B2 |
| 7865937 | White et al. | Jan 2011 | B1 |
| 7883417 | Bruzzese et al. | Feb 2011 | B2 |
| 7904718 | Giobbi et al. | Mar 2011 | B2 |
| 7943868 | Anders et al. | May 2011 | B2 |
| 7957536 | Nolte | Jun 2011 | B2 |
| 7961078 | Reynolds et al. | Jun 2011 | B1 |
| 7984064 | Fusari | Jul 2011 | B2 |
| 7996514 | Baumert et al. | Aug 2011 | B2 |
| 8026821 | Reeder et al. | Sep 2011 | B2 |
| 8036152 | Brown et al. | Oct 2011 | B2 |
| 8077041 | Stern et al. | Dec 2011 | B2 |
| 8081215 | Kuo et al. | Dec 2011 | B2 |
| 8082160 | Collins, Jr. et al. | Dec 2011 | B2 |
| 8089354 | Perkins | Jan 2012 | B2 |
| 8112066 | Ben Ayed | Feb 2012 | B2 |
| 8125624 | Jones et al. | Feb 2012 | B2 |
| 8135624 | Ramalingam et al. | Mar 2012 | B1 |
| 8171528 | Brown | May 2012 | B1 |
| 8193923 | Rork et al. | Jun 2012 | B2 |
| 8200980 | Robinson et al. | Jun 2012 | B1 |
| 8215552 | Rambadt | Jul 2012 | B1 |
| 8248263 | Shervey et al. | Aug 2012 | B2 |
| 8258942 | Lanzone et al. | Sep 2012 | B1 |
| 8294554 | Shoarinejad et al. | Oct 2012 | B2 |
| 8296573 | Bolle et al. | Oct 2012 | B2 |
| 8307414 | Zerfos et al. | Nov 2012 | B2 |
| 8325011 | Butler et al. | Dec 2012 | B2 |
| 8340672 | Brown et al. | Dec 2012 | B2 |
| 8352730 | Giobbi | Jan 2013 | B2 |
| 8373562 | Heinze et al. | Feb 2013 | B1 |
| 8378925 | Chiaki | Feb 2013 | B2 |
| 8387124 | Smetters | Feb 2013 | B2 |
| 8390456 | Puleston et al. | Mar 2013 | B2 |
| 8395484 | Fullerton | Mar 2013 | B2 |
| 8410906 | Dacus et al. | Apr 2013 | B1 |
| 8421606 | Collins, Jr. et al. | Apr 2013 | B2 |
| 8424079 | Adams et al. | Apr 2013 | B2 |
| 8432262 | Talty et al. | Apr 2013 | B2 |
| 8433919 | Giobbi et al. | Apr 2013 | B2 |
| 8448858 | Kundu et al. | May 2013 | B1 |
| 8473748 | Sampas | Jun 2013 | B2 |
| 8484696 | Gatto et al. | Jul 2013 | B2 |
| 8494576 | Bye et al. | Jul 2013 | B1 |
| 8508336 | Giobbi et al. | Aug 2013 | B2 |
| 8511555 | Babcock et al. | Aug 2013 | B2 |
| 8519823 | Rinkes | Aug 2013 | B2 |
| 8522019 | Michaelis | Aug 2013 | B2 |
| 8558699 | Butler et al. | Oct 2013 | B2 |
| 8572391 | Golan et al. | Oct 2013 | B2 |
| 8577091 | Ivanov et al. | Nov 2013 | B2 |
| 8646042 | Brown | Feb 2014 | B1 |
| 8678273 | McNeal | Mar 2014 | B2 |
| 8717346 | Claessen | May 2014 | B2 |
| 8738925 | Park et al. | May 2014 | B1 |
| 8799574 | Corda | Aug 2014 | B2 |
| 8856539 | Weiss | Oct 2014 | B2 |
| 8914477 | Gammon | Dec 2014 | B2 |
| 8918854 | Giobbi | Dec 2014 | B1 |
| 8931698 | Ishikawa et al. | Jan 2015 | B2 |
| 8979646 | Moser et al. | Mar 2015 | B2 |
| 9037140 | Brown | May 2015 | B1 |
| 9049188 | Brown | Jun 2015 | B1 |
| 9165233 | Testanero | Oct 2015 | B2 |
| 9189788 | Robinson et al. | Nov 2015 | B1 |
| 9230399 | Yacenda | Jan 2016 | B2 |
| 9235700 | Brown | Jan 2016 | B1 |
| 9276914 | Woodward et al. | Mar 2016 | B2 |
| 9305312 | Kountotsis et al. | Apr 2016 | B2 |
| 9405898 | Giobbi | Aug 2016 | B2 |
| 9418205 | Giobbi | Aug 2016 | B2 |
| 9542542 | Giobbi et al. | Jan 2017 | B2 |
| 9679289 | Brown | Jun 2017 | B1 |
| 9830504 | Masood et al. | Nov 2017 | B2 |
| 9892250 | Giobbi | Feb 2018 | B2 |
| 10073960 | Brown | Sep 2018 | B1 |
| 10110385 | Rush et al. | Oct 2018 | B1 |
| 10455533 | Brown | Oct 2019 | B2 |
| 10817964 | Guillama et al. | Oct 2020 | B2 |
| 20010021950 | Hawley et al. | Sep 2001 | A1 |
| 20010024428 | Onouchi | Sep 2001 | A1 |
| 20010026619 | Howard, Jr. et al. | Oct 2001 | A1 |
| 20010027121 | Boesen | Oct 2001 | A1 |
| 20010027439 | Holtzman et al. | Oct 2001 | A1 |
| 20010044337 | Rowe et al. | Nov 2001 | A1 |
| 20020004783 | Paltenghe et al. | Jan 2002 | A1 |
| 20020007456 | Peinado et al. | Jan 2002 | A1 |
| 20020010679 | Felsher | Jan 2002 | A1 |
| 20020013772 | Peinado | Jan 2002 | A1 |
| 20020014954 | Fitzgibbon et al. | Feb 2002 | A1 |
| 20020015494 | Nagai et al. | Feb 2002 | A1 |
| 20020019811 | Lapsley et al. | Feb 2002 | A1 |
| 20020022455 | Salokannel et al. | Feb 2002 | A1 |
| 20020023032 | Pearson et al. | Feb 2002 | A1 |
| 20020023217 | Wheeler et al. | Feb 2002 | A1 |
| 20020026424 | Akashi | Feb 2002 | A1 |
| 20020037732 | Gous et al. | Mar 2002 | A1 |
| 20020052193 | Chetty | May 2002 | A1 |
| 20020055908 | Di Giorgio et al. | May 2002 | A1 |
| 20020056043 | Glass | May 2002 | A1 |
| 20020059114 | Cockrill et al. | May 2002 | A1 |
| 20020062249 | Iannacci | May 2002 | A1 |
| 20020068605 | Stanley | Jun 2002 | A1 |
| 20020069364 | Dosch | Jun 2002 | A1 |
| 20020071559 | Christensen et al. | Jun 2002 | A1 |
| 20020073042 | Maritzen et al. | Jun 2002 | A1 |
| 20020080969 | Giobbi | Jun 2002 | A1 |
| 20020083178 | Brothers | Jun 2002 | A1 |
| 20020083318 | Larose | Jun 2002 | A1 |
| 20020086690 | Takahashi et al. | Jul 2002 | A1 |
| 20020089890 | Fibranz et al. | Jul 2002 | A1 |
| 20020091646 | Lake et al. | Jul 2002 | A1 |
| 20020095586 | Doyle et al. | Jul 2002 | A1 |
| 20020095587 | Doyle et al. | Jul 2002 | A1 |
| 20020097876 | Harrison | Jul 2002 | A1 |
| 20020098888 | Rowe et al. | Jul 2002 | A1 |
| 20020100798 | Farrugia et al. | Aug 2002 | A1 |
| 20020103027 | Rowe et al. | Aug 2002 | A1 |
| 20020103881 | Granade et al. | Aug 2002 | A1 |
| 20020104006 | Boate et al. | Aug 2002 | A1 |
| 20020104019 | Chatani et al. | Aug 2002 | A1 |
| 20020105918 | Yamada et al. | Aug 2002 | A1 |
| 20020108049 | Xu et al. | Aug 2002 | A1 |
| 20020109580 | Shreve et al. | Aug 2002 | A1 |
| 20020111919 | Weller et al. | Aug 2002 | A1 |
| 20020112183 | Baird et al. | Aug 2002 | A1 |
| 20020116615 | Nguyen et al. | Aug 2002 | A1 |
| 20020124251 | Hunter et al. | Sep 2002 | A1 |
| 20020128017 | Virtanen | Sep 2002 | A1 |
| 20020129262 | Kutaragi et al. | Sep 2002 | A1 |
| 20020138438 | Bardwell | Sep 2002 | A1 |
| 20020138767 | Hamid et al. | Sep 2002 | A1 |
| 20020140542 | Prokoski et al. | Oct 2002 | A1 |
| 20020141586 | Margalit et al. | Oct 2002 | A1 |
| 20020143623 | Dayley | Oct 2002 | A1 |
| 20020143655 | Elston | Oct 2002 | A1 |
| 20020144116 | Giobbi | Oct 2002 | A1 |
| 20020144117 | Faigle | Oct 2002 | A1 |
| 20020147653 | Shmueli et al. | Oct 2002 | A1 |
| 20020148892 | Bardwell | Oct 2002 | A1 |
| 20020150282 | Kinsella | Oct 2002 | A1 |
| 20020152391 | Willins et al. | Oct 2002 | A1 |
| 20020153996 | Chan et al. | Oct 2002 | A1 |
| 20020158121 | Stanford-Clark | Oct 2002 | A1 |
| 20020158750 | Almalik | Oct 2002 | A1 |
| 20020158765 | Pape et al. | Oct 2002 | A1 |
| 20020160820 | Winkler | Oct 2002 | A1 |
| 20020174348 | Ting | Nov 2002 | A1 |
| 20020177460 | Beasley et al. | Nov 2002 | A1 |
| 20020178063 | Gravelle et al. | Nov 2002 | A1 |
| 20020184208 | Kato | Dec 2002 | A1 |
| 20020187746 | Cheng et al. | Dec 2002 | A1 |
| 20020191816 | Matzen et al. | Dec 2002 | A1 |
| 20020196963 | Bardwell | Dec 2002 | A1 |
| 20020199120 | Schmidt | Dec 2002 | A1 |
| 20030022701 | Gupta | Jan 2003 | A1 |
| 20030034877 | Miller et al. | Feb 2003 | A1 |
| 20030036416 | Pattabiraman et al. | Feb 2003 | A1 |
| 20030036425 | Kaminkow et al. | Feb 2003 | A1 |
| 20030046228 | Berney | Mar 2003 | A1 |
| 20030046237 | Uberti | Mar 2003 | A1 |
| 20030046552 | Hamid | Mar 2003 | A1 |
| 20030048174 | Stevens et al. | Mar 2003 | A1 |
| 20030051173 | Krueger | Mar 2003 | A1 |
| 20030054868 | Paulsen et al. | Mar 2003 | A1 |
| 20030054881 | Hedrick et al. | Mar 2003 | A1 |
| 20030055689 | Block et al. | Mar 2003 | A1 |
| 20030061172 | Robinson | Mar 2003 | A1 |
| 20030063619 | Montano et al. | Apr 2003 | A1 |
| 20030079133 | Breiter | Apr 2003 | A1 |
| 20030087601 | Agam et al. | May 2003 | A1 |
| 20030088441 | McNerney | May 2003 | A1 |
| 20030105719 | Berger et al. | Jun 2003 | A1 |
| 20030109274 | Budka et al. | Jun 2003 | A1 |
| 20030115351 | Giobbi | Jun 2003 | A1 |
| 20030115474 | Khan et al. | Jun 2003 | A1 |
| 20030117969 | Koo et al. | Jun 2003 | A1 |
| 20030117980 | Kim et al. | Jun 2003 | A1 |
| 20030120934 | Ortiz | Jun 2003 | A1 |
| 20030127511 | Kelly et al. | Jul 2003 | A1 |
| 20030128866 | McNeal | Jul 2003 | A1 |
| 20030137404 | Bonneau, Jr. et al. | Jul 2003 | A1 |
| 20030139190 | Steelberg et al. | Jul 2003 | A1 |
| 20030146835 | Carter | Aug 2003 | A1 |
| 20030149744 | Bierre et al. | Aug 2003 | A1 |
| 20030156742 | Witt et al. | Aug 2003 | A1 |
| 20030159040 | Hashimoto et al. | Aug 2003 | A1 |
| 20030163388 | Beane | Aug 2003 | A1 |
| 20030167207 | Berardi et al. | Sep 2003 | A1 |
| 20030169697 | Suzuki et al. | Sep 2003 | A1 |
| 20030172028 | Abell et al. | Sep 2003 | A1 |
| 20030172037 | Jung et al. | Sep 2003 | A1 |
| 20030174839 | Yamagata et al. | Sep 2003 | A1 |
| 20030176218 | LeMay et al. | Sep 2003 | A1 |
| 20030177102 | Robinson | Sep 2003 | A1 |
| 20030186739 | Paulsen et al. | Oct 2003 | A1 |
| 20030195842 | Reece | Oct 2003 | A1 |
| 20030199267 | Iwasa et al. | Oct 2003 | A1 |
| 20030204526 | Salehi-Had | Oct 2003 | A1 |
| 20030213840 | Livingston et al. | Nov 2003 | A1 |
| 20030223394 | Parantainen et al. | Dec 2003 | A1 |
| 20030225703 | Angel | Dec 2003 | A1 |
| 20030226031 | Proudler et al. | Dec 2003 | A1 |
| 20030233458 | Kwon et al. | Dec 2003 | A1 |
| 20040002347 | Hoctor et al. | Jan 2004 | A1 |
| 20040015403 | Moskowitz | Jan 2004 | A1 |
| 20040022384 | Flores et al. | Feb 2004 | A1 |
| 20040029620 | Karaoguz | Feb 2004 | A1 |
| 20040029635 | Giobbi | Feb 2004 | A1 |
| 20040030764 | Birk et al. | Feb 2004 | A1 |
| 20040030894 | Labrou et al. | Feb 2004 | A1 |
| 20040035644 | Ford | Feb 2004 | A1 |
| 20040039909 | Cheng | Feb 2004 | A1 |
| 20040048570 | Oba et al. | Mar 2004 | A1 |
| 20040048609 | Kosaka | Mar 2004 | A1 |
| 20040059682 | Hasumi et al. | Mar 2004 | A1 |
| 20040059912 | Zizzi | Mar 2004 | A1 |
| 20040064728 | Scheurich | Apr 2004 | A1 |
| 20040068656 | Lu | Apr 2004 | A1 |
| 20040073792 | Noble et al. | Apr 2004 | A1 |
| 20040081127 | Gardner et al. | Apr 2004 | A1 |
| 20040082385 | Silva et al. | Apr 2004 | A1 |
| 20040090345 | Hitt | May 2004 | A1 |
| 20040098597 | Giobbi | May 2004 | A1 |
| 20040114563 | Shvodian | Jun 2004 | A1 |
| 20040117644 | Colvin | Jun 2004 | A1 |
| 20040123106 | D'Angelo et al. | Jun 2004 | A1 |
| 20040123127 | Teicher et al. | Jun 2004 | A1 |
| 20040127277 | Walker et al. | Jul 2004 | A1 |
| 20040128162 | Schlotterbeck et al. | Jul 2004 | A1 |
| 20040128389 | Kopchik | Jul 2004 | A1 |
| 20040128500 | Cihula et al. | Jul 2004 | A1 |
| 20040128508 | Wheeler et al. | Jul 2004 | A1 |
| 20040128519 | Klinger et al. | Jul 2004 | A1 |
| 20040129787 | Saito et al. | Jul 2004 | A1 |
| 20040132432 | Moores et al. | Jul 2004 | A1 |
| 20040137912 | Lin | Jul 2004 | A1 |
| 20040158746 | Hu et al. | Aug 2004 | A1 |
| 20040166875 | Jenkins et al. | Aug 2004 | A1 |
| 20040167465 | Mihai et al. | Aug 2004 | A1 |
| 20040181695 | Walker | Sep 2004 | A1 |
| 20040193925 | Safriel | Sep 2004 | A1 |
| 20040194133 | Ikeda et al. | Sep 2004 | A1 |
| 20040203566 | Leung | Oct 2004 | A1 |
| 20040203923 | Mullen | Oct 2004 | A1 |
| 20040208139 | Iwamura | Oct 2004 | A1 |
| 20040209690 | Bruzzese et al. | Oct 2004 | A1 |
| 20040209692 | Schober et al. | Oct 2004 | A1 |
| 20040214582 | Lan et al. | Oct 2004 | A1 |
| 20040215615 | Larsson et al. | Oct 2004 | A1 |
| 20040217859 | Pucci et al. | Nov 2004 | A1 |
| 20040218581 | Cattaneo | Nov 2004 | A1 |
| 20040222877 | Teramura et al. | Nov 2004 | A1 |
| 20040230488 | Beenau et al. | Nov 2004 | A1 |
| 20040230809 | Lowensohn et al. | Nov 2004 | A1 |
| 20040234117 | Tibor | Nov 2004 | A1 |
| 20040243519 | Perttila et al. | Dec 2004 | A1 |
| 20040246103 | Zukowski | Dec 2004 | A1 |
| 20040246950 | Parker et al. | Dec 2004 | A1 |
| 20040250074 | Kilian-Kehr | Dec 2004 | A1 |
| 20040252012 | Beenau et al. | Dec 2004 | A1 |
| 20040252659 | Yun et al. | Dec 2004 | A1 |
| 20040253996 | Chen et al. | Dec 2004 | A1 |
| 20040254837 | Roshkoff | Dec 2004 | A1 |
| 20040255139 | Giobbi | Dec 2004 | A1 |
| 20040255145 | Chow | Dec 2004 | A1 |
| 20050001028 | Zuili | Jan 2005 | A1 |
| 20050002028 | Kasapi et al. | Jan 2005 | A1 |
| 20050005136 | Chen et al. | Jan 2005 | A1 |
| 20050006452 | Aupperle et al. | Jan 2005 | A1 |
| 20050009517 | Maes | Jan 2005 | A1 |
| 20050021561 | Noonan | Jan 2005 | A1 |
| 20050025093 | Yun et al. | Feb 2005 | A1 |
| 20050028168 | Marcjan | Feb 2005 | A1 |
| 20050035897 | Perl et al. | Feb 2005 | A1 |
| 20050039027 | Shapiro | Feb 2005 | A1 |
| 20050040961 | Tuttle | Feb 2005 | A1 |
| 20050044372 | Aull et al. | Feb 2005 | A1 |
| 20050044387 | Ozolins | Feb 2005 | A1 |
| 20050047386 | Yi | Mar 2005 | A1 |
| 20050049013 | Chang et al. | Mar 2005 | A1 |
| 20050050208 | Chatani | Mar 2005 | A1 |
| 20050050324 | Corbett et al. | Mar 2005 | A1 |
| 20050054431 | Walker et al. | Mar 2005 | A1 |
| 20050055242 | Bello et al. | Mar 2005 | A1 |
| 20050055244 | Mullan et al. | Mar 2005 | A1 |
| 20050058292 | Diorio et al. | Mar 2005 | A1 |
| 20050074126 | Stanko | Apr 2005 | A1 |
| 20050076242 | Breuer | Apr 2005 | A1 |
| 20050081040 | Johnson et al. | Apr 2005 | A1 |
| 20050084137 | Kim et al. | Apr 2005 | A1 |
| 20050086115 | Pearson | Apr 2005 | A1 |
| 20050086515 | Paris | Apr 2005 | A1 |
| 20050089000 | Bae et al. | Apr 2005 | A1 |
| 20050090200 | Karaoguz et al. | Apr 2005 | A1 |
| 20050091338 | de la Huerga | Apr 2005 | A1 |
| 20050091553 | Chien et al. | Apr 2005 | A1 |
| 20050094657 | Sung et al. | May 2005 | A1 |
| 20050097037 | Tibor | May 2005 | A1 |
| 20050105600 | Culum et al. | May 2005 | A1 |
| 20050105734 | Buer et al. | May 2005 | A1 |
| 20050108164 | Salafia, III et al. | May 2005 | A1 |
| 20050109836 | Ben-Aissa | May 2005 | A1 |
| 20050109841 | Ryan et al. | May 2005 | A1 |
| 20050113070 | Okabe | May 2005 | A1 |
| 20050114149 | Rodriguez et al. | May 2005 | A1 |
| 20050114150 | Franklin | May 2005 | A1 |
| 20050116020 | Smolucha et al. | Jun 2005 | A1 |
| 20050117530 | Abraham et al. | Jun 2005 | A1 |
| 20050119979 | Murashita et al. | Jun 2005 | A1 |
| 20050124294 | Wentink | Jun 2005 | A1 |
| 20050125258 | Yellin et al. | Jun 2005 | A1 |
| 20050137977 | Wankmueller | Jun 2005 | A1 |
| 20050138390 | Adams et al. | Jun 2005 | A1 |
| 20050138576 | Baumert et al. | Jun 2005 | A1 |
| 20050139656 | Arnouse | Jun 2005 | A1 |
| 20050141451 | Yoon et al. | Jun 2005 | A1 |
| 20050152394 | Cho | Jul 2005 | A1 |
| 20050154897 | Holloway et al. | Jul 2005 | A1 |
| 20050161503 | Remery et al. | Jul 2005 | A1 |
| 20050165684 | Jensen et al. | Jul 2005 | A1 |
| 20050166063 | Zyh-Ming | Jul 2005 | A1 |
| 20050167482 | Ramachandran et al. | Aug 2005 | A1 |
| 20050169292 | Young | Aug 2005 | A1 |
| 20050177716 | Ginter et al. | Aug 2005 | A1 |
| 20050180385 | Jeong et al. | Aug 2005 | A1 |
| 20050182661 | Allard et al. | Aug 2005 | A1 |
| 20050182975 | Guo et al. | Aug 2005 | A1 |
| 20050187792 | Harper | Aug 2005 | A1 |
| 20050192748 | Andric et al. | Sep 2005 | A1 |
| 20050195975 | Kawakita | Sep 2005 | A1 |
| 20050200453 | Turner et al. | Sep 2005 | A1 |
| 20050201389 | Shimanuki et al. | Sep 2005 | A1 |
| 20050203682 | Omino et al. | Sep 2005 | A1 |
| 20050203844 | Ferguson et al. | Sep 2005 | A1 |
| 20050210270 | Rohatgi et al. | Sep 2005 | A1 |
| 20050212657 | Simon | Sep 2005 | A1 |
| 20050215233 | Perera et al. | Sep 2005 | A1 |
| 20050216313 | Claud et al. | Sep 2005 | A1 |
| 20050216639 | Sparer et al. | Sep 2005 | A1 |
| 20050218215 | Lauden | Oct 2005 | A1 |
| 20050220046 | Falck et al. | Oct 2005 | A1 |
| 20050221869 | Liu et al. | Oct 2005 | A1 |
| 20050229007 | Bolle et al. | Oct 2005 | A1 |
| 20050229240 | Nanba | Oct 2005 | A1 |
| 20050242921 | Zimmerman et al. | Nov 2005 | A1 |
| 20050243787 | Hong et al. | Nov 2005 | A1 |
| 20050249385 | Kondo et al. | Nov 2005 | A1 |
| 20050251688 | Nanvati et al. | Nov 2005 | A1 |
| 20050253683 | Lowe | Nov 2005 | A1 |
| 20050257102 | Moyer et al. | Nov 2005 | A1 |
| 20050264416 | Maurer | Dec 2005 | A1 |
| 20050268111 | Markham | Dec 2005 | A1 |
| 20050269401 | Spitzer et al. | Dec 2005 | A1 |
| 20050272403 | Ryu et al. | Dec 2005 | A1 |
| 20050281320 | Neugebauer | Dec 2005 | A1 |
| 20050282558 | Choi et al. | Dec 2005 | A1 |
| 20050284932 | Sukeda et al. | Dec 2005 | A1 |
| 20050287985 | Balfanz et al. | Dec 2005 | A1 |
| 20050288069 | Arunan et al. | Dec 2005 | A1 |
| 20050289473 | Gustafson et al. | Dec 2005 | A1 |
| 20060001525 | Nitzan et al. | Jan 2006 | A1 |
| 20060014430 | Liang et al. | Jan 2006 | A1 |
| 20060022042 | Smets et al. | Feb 2006 | A1 |
| 20060022046 | Iwamura | Feb 2006 | A1 |
| 20060022800 | Krishna et al. | Feb 2006 | A1 |
| 20060025180 | Rajkotia et al. | Feb 2006 | A1 |
| 20060026673 | Tsuchida | Feb 2006 | A1 |
| 20060030279 | Leabman | Feb 2006 | A1 |
| 20060030353 | Jun | Feb 2006 | A1 |
| 20060034250 | Kim et al. | Feb 2006 | A1 |
| 20060041746 | Kirkup et al. | Feb 2006 | A1 |
| 20060046664 | Paradiso et al. | Mar 2006 | A1 |
| 20060058102 | Nguyen et al. | Mar 2006 | A1 |
| 20060063575 | Gatto et al. | Mar 2006 | A1 |
| 20060069814 | Abraham et al. | Mar 2006 | A1 |
| 20060072586 | Callaway, Jr. et al. | Apr 2006 | A1 |
| 20060074713 | Conry et al. | Apr 2006 | A1 |
| 20060076401 | Frerking | Apr 2006 | A1 |
| 20060078176 | Abiko et al. | Apr 2006 | A1 |
| 20060087407 | Stewart et al. | Apr 2006 | A1 |
| 20060089138 | Smith et al. | Apr 2006 | A1 |
| 20060097949 | Luebke et al. | May 2006 | A1 |
| 20060110012 | Ritter | May 2006 | A1 |
| 20060111955 | Winter et al. | May 2006 | A1 |
| 20060113381 | Hochstein et al. | Jun 2006 | A1 |
| 20060116935 | Evans | Jun 2006 | A1 |
| 20060117013 | Wada | Jun 2006 | A1 |
| 20060120287 | Foti et al. | Jun 2006 | A1 |
| 20060129838 | Chen et al. | Jun 2006 | A1 |
| 20060136728 | Gentry et al. | Jun 2006 | A1 |
| 20060136742 | Giobbi | Jun 2006 | A1 |
| 20060143441 | Giobbi | Jun 2006 | A1 |
| 20060144943 | Kim | Jul 2006 | A1 |
| 20060156027 | Blake | Jul 2006 | A1 |
| 20060158308 | McMullen et al. | Jul 2006 | A1 |
| 20060163349 | Neugebauer | Jul 2006 | A1 |
| 20060165060 | Dua | Jul 2006 | A1 |
| 20060169771 | Brookner | Aug 2006 | A1 |
| 20060170530 | Nwosu et al. | Aug 2006 | A1 |
| 20060170565 | Husak et al. | Aug 2006 | A1 |
| 20060172700 | Wu | Aug 2006 | A1 |
| 20060173846 | Omae et al. | Aug 2006 | A1 |
| 20060173991 | Piikivi | Aug 2006 | A1 |
| 20060183426 | Graves et al. | Aug 2006 | A1 |
| 20060183462 | Kolehmainen | Aug 2006 | A1 |
| 20060184795 | Doradla et al. | Aug 2006 | A1 |
| 20060185005 | Graves et al. | Aug 2006 | A1 |
| 20060187029 | Thomas | Aug 2006 | A1 |
| 20060190348 | Ofer et al. | Aug 2006 | A1 |
| 20060190413 | Harper | Aug 2006 | A1 |
| 20060194598 | Kim et al. | Aug 2006 | A1 |
| 20060195576 | Rinne et al. | Aug 2006 | A1 |
| 20060198337 | Hoang et al. | Sep 2006 | A1 |
| 20060200467 | Ohmori et al. | Sep 2006 | A1 |
| 20060205408 | Nakagawa et al. | Sep 2006 | A1 |
| 20060208066 | Finn et al. | Sep 2006 | A1 |
| 20060208853 | Kung et al. | Sep 2006 | A1 |
| 20060222042 | Teramura et al. | Oct 2006 | A1 |
| 20060226950 | Kanou et al. | Oct 2006 | A1 |
| 20060229909 | Kaila et al. | Oct 2006 | A1 |
| 20060236373 | Graves et al. | Oct 2006 | A1 |
| 20060237528 | Bishop et al. | Oct 2006 | A1 |
| 20060238305 | Loving et al. | Oct 2006 | A1 |
| 20060268891 | Heidari-Bateni et al. | Nov 2006 | A1 |
| 20060273176 | Audebert et al. | Dec 2006 | A1 |
| 20060274711 | Nelson, Jr. et al. | Dec 2006 | A1 |
| 20060279412 | Holland et al. | Dec 2006 | A1 |
| 20060286969 | Talmor et al. | Dec 2006 | A1 |
| 20060288095 | Torok et al. | Dec 2006 | A1 |
| 20060288233 | Kozlay | Dec 2006 | A1 |
| 20060290580 | Noro et al. | Dec 2006 | A1 |
| 20060293925 | Flom | Dec 2006 | A1 |
| 20060294388 | Abraham et al. | Dec 2006 | A1 |
| 20070003111 | Awatsu et al. | Jan 2007 | A1 |
| 20070005403 | Kennedy et al. | Jan 2007 | A1 |
| 20070007331 | Jasper | Jan 2007 | A1 |
| 20070008070 | Friedrich | Jan 2007 | A1 |
| 20070008916 | Haugli et al. | Jan 2007 | A1 |
| 20070011724 | Gonzalez et al. | Jan 2007 | A1 |
| 20070016800 | Spottswood et al. | Jan 2007 | A1 |
| 20070019845 | Kato | Jan 2007 | A1 |
| 20070029381 | Braiman | Feb 2007 | A1 |
| 20070032225 | Konicek et al. | Feb 2007 | A1 |
| 20070032288 | Nelson et al. | Feb 2007 | A1 |
| 20070033072 | Bildirici | Feb 2007 | A1 |
| 20070033150 | Nwosu | Feb 2007 | A1 |
| 20070036396 | Sugita et al. | Feb 2007 | A1 |
| 20070038751 | Jorgensen | Feb 2007 | A1 |
| 20070043594 | Lavergne | Feb 2007 | A1 |
| 20070050259 | Wesley | Mar 2007 | A1 |
| 20070050398 | Mochizuki | Mar 2007 | A1 |
| 20070051794 | Glanz et al. | Mar 2007 | A1 |
| 20070051798 | Kawai et al. | Mar 2007 | A1 |
| 20070055630 | Gauthier et al. | Mar 2007 | A1 |
| 20070060095 | Subrahmanya et al. | Mar 2007 | A1 |
| 20070060319 | Block et al. | Mar 2007 | A1 |
| 20070064742 | Shvodian | Mar 2007 | A1 |
| 20070069852 | Mo et al. | Mar 2007 | A1 |
| 20070070040 | Chen et al. | Mar 2007 | A1 |
| 20070072636 | Worfolk et al. | Mar 2007 | A1 |
| 20070073553 | Flinn et al. | Mar 2007 | A1 |
| 20070084523 | McLean et al. | Apr 2007 | A1 |
| 20070084913 | Weston | Apr 2007 | A1 |
| 20070087682 | DaCosta | Apr 2007 | A1 |
| 20070087834 | Moser et al. | Apr 2007 | A1 |
| 20070100507 | Simon | May 2007 | A1 |
| 20070100939 | Bagley et al. | May 2007 | A1 |
| 20070109117 | Heitzmann et al. | May 2007 | A1 |
| 20070112676 | Kontio et al. | May 2007 | A1 |
| 20070118891 | Buer | May 2007 | A1 |
| 20070120643 | Jiunn-Chung | May 2007 | A1 |
| 20070132586 | Plocher et al. | Jun 2007 | A1 |
| 20070133478 | Armbruster et al. | Jun 2007 | A1 |
| 20070136407 | Rudelic | Jun 2007 | A1 |
| 20070142032 | Balsillie | Jun 2007 | A1 |
| 20070152826 | August et al. | Jul 2007 | A1 |
| 20070156850 | Corrion | Jul 2007 | A1 |
| 20070157249 | Cordray et al. | Jul 2007 | A1 |
| 20070158411 | Krieg, Jr. | Jul 2007 | A1 |
| 20070159301 | Hirt et al. | Jul 2007 | A1 |
| 20070159994 | Brown et al. | Jul 2007 | A1 |
| 20070164847 | Crawford et al. | Jul 2007 | A1 |
| 20070169121 | Hunt et al. | Jul 2007 | A1 |
| 20070174809 | Brown et al. | Jul 2007 | A1 |
| 20070176756 | Friedrich | Aug 2007 | A1 |
| 20070176778 | Ando et al. | Aug 2007 | A1 |
| 20070180047 | Dong et al. | Aug 2007 | A1 |
| 20070187266 | Porter et al. | Aug 2007 | A1 |
| 20070192601 | Spain et al. | Aug 2007 | A1 |
| 20070194882 | Yokota et al. | Aug 2007 | A1 |
| 20070198436 | Weiss | Aug 2007 | A1 |
| 20070204078 | Boccon-Gibod et al. | Aug 2007 | A1 |
| 20070205860 | Jones et al. | Sep 2007 | A1 |
| 20070205861 | Nair et al. | Sep 2007 | A1 |
| 20070213048 | Trauberg | Sep 2007 | A1 |
| 20070214492 | Gopi et al. | Sep 2007 | A1 |
| 20070218921 | Lee et al. | Sep 2007 | A1 |
| 20070219926 | Korn | Sep 2007 | A1 |
| 20070220272 | Campisi et al. | Sep 2007 | A1 |
| 20070229268 | Swan et al. | Oct 2007 | A1 |
| 20070245157 | Giobbi et al. | Oct 2007 | A1 |
| 20070245158 | Giobbi | Oct 2007 | A1 |
| 20070247366 | Smith et al. | Oct 2007 | A1 |
| 20070258626 | Reiner | Nov 2007 | A1 |
| 20070260883 | Giobbi | Nov 2007 | A1 |
| 20070260888 | Giobbi et al. | Nov 2007 | A1 |
| 20070266257 | Camaisa et al. | Nov 2007 | A1 |
| 20070268862 | Singh et al. | Nov 2007 | A1 |
| 20070271194 | Walker et al. | Nov 2007 | A1 |
| 20070271433 | Takemura | Nov 2007 | A1 |
| 20070277044 | Graf et al. | Nov 2007 | A1 |
| 20070280509 | Owen et al. | Dec 2007 | A1 |
| 20070285212 | Rotzoll | Dec 2007 | A1 |
| 20070285238 | Batra | Dec 2007 | A1 |
| 20070288263 | Rodgers | Dec 2007 | A1 |
| 20070288752 | Chan | Dec 2007 | A1 |
| 20070293155 | Liao et al. | Dec 2007 | A1 |
| 20070294755 | Dadhia et al. | Dec 2007 | A1 |
| 20070296544 | Beenau et al. | Dec 2007 | A1 |
| 20080001783 | Cargonja et al. | Jan 2008 | A1 |
| 20080005432 | Kagawa | Jan 2008 | A1 |
| 20080008359 | Beenau et al. | Jan 2008 | A1 |
| 20080011842 | Curry et al. | Jan 2008 | A1 |
| 20080012685 | Friedrich et al. | Jan 2008 | A1 |
| 20080012767 | Caliri et al. | Jan 2008 | A1 |
| 20080016004 | Kurasaki et al. | Jan 2008 | A1 |
| 20080019578 | Saito et al. | Jan 2008 | A1 |
| 20080028227 | Sakurai | Jan 2008 | A1 |
| 20080028453 | Nguyen et al. | Jan 2008 | A1 |
| 20080040609 | Giobbi | Feb 2008 | A1 |
| 20080046366 | Bemmel et al. | Feb 2008 | A1 |
| 20080046715 | Balazs et al. | Feb 2008 | A1 |
| 20080049700 | Shah et al. | Feb 2008 | A1 |
| 20080061941 | Fischer et al. | Mar 2008 | A1 |
| 20080071577 | Highley | Mar 2008 | A1 |
| 20080072063 | Takahashi et al. | Mar 2008 | A1 |
| 20080088475 | Martin | Apr 2008 | A1 |
| 20080090548 | Ramalingam | Apr 2008 | A1 |
| 20080095359 | Schreyer et al. | Apr 2008 | A1 |
| 20080107089 | Larsson et al. | May 2008 | A1 |
| 20080109895 | Janevski | May 2008 | A1 |
| 20080111752 | Lindackers et al. | May 2008 | A1 |
| 20080127176 | Lee et al. | May 2008 | A1 |
| 20080129450 | Riegebauer | Jun 2008 | A1 |
| 20080148351 | Bhatia et al. | Jun 2008 | A1 |
| 20080149705 | Giobbi et al. | Jun 2008 | A1 |
| 20080150678 | Giobbi et al. | Jun 2008 | A1 |
| 20080156866 | McNeal | Jul 2008 | A1 |
| 20080164997 | Aritsuka et al. | Jul 2008 | A1 |
| 20080169909 | Park et al. | Jul 2008 | A1 |
| 20080186166 | Zhou et al. | Aug 2008 | A1 |
| 20080188308 | Shepherd et al. | Aug 2008 | A1 |
| 20080195863 | Kennedy | Aug 2008 | A1 |
| 20080201768 | Koo et al. | Aug 2008 | A1 |
| 20080203107 | Conley et al. | Aug 2008 | A1 |
| 20080209571 | Bhaskar et al. | Aug 2008 | A1 |
| 20080218416 | Handy et al. | Sep 2008 | A1 |
| 20080222701 | Saaranen et al. | Sep 2008 | A1 |
| 20080223918 | Williams et al. | Sep 2008 | A1 |
| 20080228524 | Brown | Sep 2008 | A1 |
| 20080235144 | Phillips | Sep 2008 | A1 |
| 20080238625 | Rofougaran et al. | Oct 2008 | A1 |
| 20080250388 | Meyer et al. | Oct 2008 | A1 |
| 20080251579 | Larsen | Oct 2008 | A1 |
| 20080278325 | Zimman et al. | Nov 2008 | A1 |
| 20080289030 | Poplett | Nov 2008 | A1 |
| 20080289032 | Aoki et al. | Nov 2008 | A1 |
| 20080303637 | Gelbman et al. | Dec 2008 | A1 |
| 20080313728 | Pandrangi et al. | Dec 2008 | A1 |
| 20080314971 | Faith et al. | Dec 2008 | A1 |
| 20080316045 | Sriharto et al. | Dec 2008 | A1 |
| 20090002134 | McAllister | Jan 2009 | A1 |
| 20090013191 | Popowski | Jan 2009 | A1 |
| 20090016573 | McAfee, II et al. | Jan 2009 | A1 |
| 20090024584 | Dharap et al. | Jan 2009 | A1 |
| 20090033464 | Friedrich | Feb 2009 | A1 |
| 20090033485 | Naeve et al. | Feb 2009 | A1 |
| 20090036164 | Rowley | Feb 2009 | A1 |
| 20090041309 | Kim et al. | Feb 2009 | A1 |
| 20090045916 | Nitzan et al. | Feb 2009 | A1 |
| 20090052389 | Qin et al. | Feb 2009 | A1 |
| 20090070146 | Haider et al. | Mar 2009 | A1 |
| 20090076849 | Diller | Mar 2009 | A1 |
| 20090081996 | Duggal et al. | Mar 2009 | A1 |
| 20090096580 | Paananen | Apr 2009 | A1 |
| 20090125401 | Beenau | May 2009 | A1 |
| 20090140045 | Evans | Jun 2009 | A1 |
| 20090157512 | King | Jun 2009 | A1 |
| 20090176566 | Kelly | Jul 2009 | A1 |
| 20090177495 | Abousy et al. | Jul 2009 | A1 |
| 20090199206 | Finkenzeller et al. | Aug 2009 | A1 |
| 20090237245 | Brinton et al. | Sep 2009 | A1 |
| 20090237253 | Neuwirth | Sep 2009 | A1 |
| 20090239667 | Rowe et al. | Sep 2009 | A1 |
| 20090253516 | Hartmann et al. | Oct 2009 | A1 |
| 20090254971 | Herz et al. | Oct 2009 | A1 |
| 20090264712 | Baldus et al. | Oct 2009 | A1 |
| 20090310514 | Jeon et al. | Dec 2009 | A1 |
| 20090313689 | Nystrom et al. | Dec 2009 | A1 |
| 20090319788 | Zick et al. | Dec 2009 | A1 |
| 20090320118 | Muller et al. | Dec 2009 | A1 |
| 20090322510 | Berger et al. | Dec 2009 | A1 |
| 20090328182 | Malakapalli et al. | Dec 2009 | A1 |
| 20100005526 | Tsuji et al. | Jan 2010 | A1 |
| 20100007498 | Jackson | Jan 2010 | A1 |
| 20100022308 | Hartmann et al. | Jan 2010 | A1 |
| 20100023074 | Powers et al. | Jan 2010 | A1 |
| 20100037255 | Sheehan et al. | Feb 2010 | A1 |
| 20100062743 | Jonsson | Mar 2010 | A1 |
| 20100077214 | Jogand-Coulomb et al. | Mar 2010 | A1 |
| 20100117794 | Adams et al. | May 2010 | A1 |
| 20100134257 | Puleston et al. | Jun 2010 | A1 |
| 20100169442 | Liu et al. | Jul 2010 | A1 |
| 20100169964 | Liu et al. | Jul 2010 | A1 |
| 20100172567 | Prokoski | Jul 2010 | A1 |
| 20100174911 | Isshiki | Jul 2010 | A1 |
| 20100188226 | Seder et al. | Jul 2010 | A1 |
| 20100214100 | Page | Aug 2010 | A1 |
| 20100277283 | Burkart et al. | Nov 2010 | A1 |
| 20100277286 | Burkart et al. | Nov 2010 | A1 |
| 20100291896 | Corda | Nov 2010 | A1 |
| 20100305843 | Yan et al. | Dec 2010 | A1 |
| 20100328033 | Kamei | Dec 2010 | A1 |
| 20110072034 | Sly et al. | Mar 2011 | A1 |
| 20110072132 | Shafer et al. | Mar 2011 | A1 |
| 20110082735 | Kannan et al. | Apr 2011 | A1 |
| 20110085287 | Ebrom et al. | Apr 2011 | A1 |
| 20110091136 | Danch et al. | Apr 2011 | A1 |
| 20110116358 | Li et al. | May 2011 | A9 |
| 20110126188 | Bernstein et al. | May 2011 | A1 |
| 20110227740 | Wohltjen | Sep 2011 | A1 |
| 20110238517 | Ramalingam et al. | Sep 2011 | A1 |
| 20110246790 | Koh et al. | Oct 2011 | A1 |
| 20110266348 | Denniston, Jr. | Nov 2011 | A1 |
| 20110307599 | Saretto et al. | Dec 2011 | A1 |
| 20120028609 | Hruska | Feb 2012 | A1 |
| 20120030006 | Yoder et al. | Feb 2012 | A1 |
| 20120069776 | Caldwell et al. | Mar 2012 | A1 |
| 20120086571 | Scalisi et al. | Apr 2012 | A1 |
| 20120182123 | Butler et al. | Jul 2012 | A1 |
| 20120212322 | Idsoe | Aug 2012 | A1 |
| 20120226451 | Bacot et al. | Sep 2012 | A1 |
| 20120226565 | Drozd | Sep 2012 | A1 |
| 20120226907 | Hohberger et al. | Sep 2012 | A1 |
| 20120226990 | Hohberger et al. | Sep 2012 | A1 |
| 20120238287 | Scherzer | Sep 2012 | A1 |
| 20120278188 | Attar et al. | Nov 2012 | A1 |
| 20120310720 | Balsan et al. | Dec 2012 | A1 |
| 20130019295 | Park et al. | Jan 2013 | A1 |
| 20130019323 | Arvidsson et al. | Jan 2013 | A1 |
| 20130044111 | VanGilder et al. | Feb 2013 | A1 |
| 20130111543 | Brown et al. | May 2013 | A1 |
| 20130135082 | Xian et al. | May 2013 | A1 |
| 20130179201 | Fuerstenberg et al. | Jul 2013 | A1 |
| 20130276140 | Coffing et al. | Oct 2013 | A1 |
| 20130331063 | Cormier et al. | Dec 2013 | A1 |
| 20140074696 | Glaser | Mar 2014 | A1 |
| 20140147018 | Argue et al. | May 2014 | A1 |
| 20140266604 | Masood et al. | Sep 2014 | A1 |
| 20140266713 | Sehgal et al. | Sep 2014 | A1 |
| 20150039451 | Bonfiglio | Feb 2015 | A1 |
| 20150294293 | Signarsson | Oct 2015 | A1 |
| 20150310385 | King et al. | Oct 2015 | A1 |
| 20150310440 | Hynes et al. | Oct 2015 | A1 |
| 20160210614 | Hall | Jul 2016 | A1 |
| 20160300236 | Wiley et al. | Oct 2016 | A1 |
| 20170085564 | Giobbi et al. | Mar 2017 | A1 |
| 20170091548 | Agrawal et al. | Mar 2017 | A1 |
| 20180322718 | Qian et al. | Nov 2018 | A1 |
| 20180357475 | Honda et al. | Dec 2018 | A1 |
| 20190172281 | Einberg et al. | Jun 2019 | A1 |
| 20190260724 | Hefetz et al. | Aug 2019 | A1 |
| Number | Date | Country |
|---|---|---|
| H10-49604 | Feb 1998 | JP |
| 0062505 | Oct 2000 | WO |
| 0122724 | Mar 2001 | WO |
| 0135334 | May 2001 | WO |
| 0175876 | Oct 2001 | WO |
| 0177790 | Oct 2001 | WO |
| 2004010774 | Feb 2004 | WO |
| 2004038563 | May 2004 | WO |
| 2005031663 | Apr 2005 | WO |
| 2005050450 | Jun 2005 | WO |
| 2005086802 | Sep 2005 | WO |
| 2007087558 | Aug 2007 | WO |
| Entry |
|---|
| 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. |
| Number | Date | Country | |
|---|---|---|---|
| 20090254448 A1 | Oct 2009 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61043326 | Apr 2008 | US | |
| 61102983 | Oct 2008 | US |
