|Publication number||US7991158 B2|
|Application number||US 11/895,637|
|Publication date||Aug 2, 2011|
|Filing date||Aug 24, 2007|
|Priority date||Dec 13, 2006|
|Also published as||US20080279381|
|Publication number||11895637, 895637, US 7991158 B2, US 7991158B2, US-B2-7991158, US7991158 B2, US7991158B2|
|Inventors||Siva G. Narendra, Prabhakar Tadepalli, Thomas N. Spitzer, Asoke Talukder|
|Original Assignee||Tyfone, Inc.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (192), Non-Patent Citations (2), Referenced by (40), Classifications (10), Legal Events (3)|
|External Links: USPTO, USPTO Assignment, Espacenet|
Benefit is claimed under 35 U.S.C. 119(e) to U.S. Provisional Application Ser. No. 60/874,578, entitled “Secure Messaging” by Narendra et al., filed Dec. 13, 2006, which is herein incorporated in its entirety by reference for all purposes.
The present invention relates generally to electronic devices, and more specifically to electronic devices that perform messaging.
Mobile devices typically communicate using a control channel and a traffic channel. For example, as shown in
Typically, secure mobile communications are accomplished using secure data packets over the traffic channel. For example, in a typical secure data exchange, a call is set-up using the control channel, and secure data is exchanged using the traffic channel. The data is typically secured using a standard secure protocol, such as those available under TCP/IP.
Most modern wireless mobile devices such as cellular telephones are capable of secure communications over the traffic channel; however, many wireless carriers require that users subscribe to “data services” in order to use the data capabilities of the mobile device. This is problematic for a third party application provider that desires to implement secure communications to/from a mobile device, since mobile device users may have to subscribe to additional services in order to enjoy the benefits of the third party application.
In the following detailed description, reference is made to the accompanying drawings that show, by way of illustration, various embodiments of an invention. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention. It is to be understood that the various embodiments of the invention, although different, are not necessarily mutually exclusive. For example, a particular feature, structure, or characteristic described in connection with one embodiment may be implemented within other embodiments without departing from the spirit and scope of the invention. In addition, it is to be understood that the location or arrangement of individual elements within each disclosed embodiment may be modified without departing from the spirit and scope of the invention. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the present invention is defined only by the appended claims, appropriately interpreted, along with the full range of equivalents to which the claims are entitled. In the drawings, like numerals refer to the same or similar functionality throughout the several views.
The various embodiments of the present invention relate generally to secure mobile transactions. For example, various embodiments relate to secure authentication and messaging for mobile online transactions for (1) enabling secure access to a client mobile device including a mobile phone and (2) to enable secure transactions using text messaging/SMS to/from a client mobile device such as a mobile phone. Note that the secure access component is applicable to any client device, and is not limited to devices that are mobile.
Various embodiments include (1) a token card for enabling secure access and (2) client and gateway protocols to enable secure transactions using text/SMS messaging. The token card is a tamper evident component that has the ability to communicate to a client device via one of several standard I/O protocols including memory card protocols or high speed interface protocols such as universal serial bus (USB). The token may also store information internally to enable secure storage, secure authentication, and secure information exchange. The server protocol software in conjunction with the client enables synchronized cryptography functions for secure text messaging/SMS.
Mobile device 210 may be any device capable of messaging over a control channel. For example, mobile device 210 may be a cellular telephone, a smartphone, a personal digital assistant (PDA), a laptop computer, a desktop computer, or any other device capable of short message communications. Although the various embodiments are described with reference to SMS communications, the invention is not so limited. For example, the secure messaging embodiments of the present invention are applicable in other short messaging scenarios such as instant messaging and text messaging.
Token 220 is a device that interfaces with mobile device 210, and that may hold encryption/decryption information to enable secure messaging. Token 220 may also include a processing element and memory. Token 220 may be involved with authentication, encryption, decryption, and the like. Token 220 may be temporarily couple to mobile device 210. Various token embodiments and their functions are described further below. In some embodiments, token 220 is not included, and the token functions described herein are either omitted or included in mobile device 210.
Network 230 may be any type of network capable of passing secure messaging communications on an out-of-band signaling channel. For example, a signaling channel within network 230 may be a physically separate channel that physically separates control information from voice/data, or the signaling channel may be a logically separate channel that shares a physical medium with the voice/data. In some embodiments, the signaling channel is implemented using a signaling system 7 (SS7) protocol. Further, network 230 may include signaling system 7 (SS7) infrastructure components such as signal switching points (SSPs), signal transfer points (STPs), and signal control points (SCPs).
Server 240 may be any type of system capable of secure messaging communications. For example, server 240 may function as a signal switching point (SSP) or a signal end point (SEP) in an SS7 network. In some embodiments, server 240 may communicate with one mobile device at a time. In other embodiments, server 240 may communicate with multiple mobile devices using secure messaging. For example, server 240 may engage in multiple secure communications sessions simultaneously.
In operation, mobile device 210 encrypts data to produce an encrypted message. The encrypted message is then mapped to a series of characters that are compatible with the messaging protocol in use, resulting in a secure messaging payload. For example, in SMS embodiments, the resulting SMS message holds a secure payload. In some embodiments, token 220 includes information necessary for the mobile device to encrypt/decrypt the SMS messages. For example, encryption/decryption keys or seeds may be maintained in token 220. In these embodiments, secure messaging requires token 220 to be mated to mobile device 210. In other embodiments, mobile device 210 maintains the encryption/decryption keys or seeds, and token 220 is not included.
Mobile device 210 includes add-on slot 212. Add-on slot 212 is a slot capable of accepting token 220. For example, add-on slot 210 may have physical dimensions compatible with token 220, and may have a communications interface that operates using a protocol compatible with token 220. In some embodiments of the present invention, add-on slot 212 is a memory card slot designed to accept and communicate with memory cards. As used herein, the term “memory card slot” refers to any add-on slot capable of accepting a card having memory accessible by a mobile device such as that shown in
In some embodiments, add-on slot 212 is a universal serial bus (USB) connector. In these embodiments, token 220 includes a mating USB connector. The various embodiments of the present invention are not limited by the type of connection between token 220 and mobile device 210. For example, the connection between token 220 and mobile device 210 may be any wired or wireless connection.
Secure authentication protocol 300 includes “activation access” and “post-activation access.” The activation access is performed when a user authenticates for the first time in order to “activate” the secure messaging platform. Post-activation access is performed for subsequent authentications. The left column of
The client protocol software may start up when a token is connected to the client device. For example, a token may be delivered to a user, and the user may then insert the token into an add-on slot in the client. The client may automatically start the client protocol software, or the user may independently start the client protocol software. In some embodiments, the client protocol software is resident on the token, and when the token is first inserted in the add-on slot, the software is installed on the client device. The client protocol software begins the activation process at 310. At 310, a user enters an activation code, and at 320 the token verifies the activation code. If the activation code is entered incorrectly more than a certain number of times, no additional code entry will be allowed. If a correct activation code has been entered, the user is prompted to enter a password or personal identification number (PIN).
In some embodiments, the activation process at 310 may ask a user for identifying information known by a server. For example, a user may be prompted for a zip code or mother's maiden name. This identifying information may then be transmitted to a server for validation. Further, in some embodiments, the activation code may be transmitted to a server for verification, rather (or in addition to) the token verifying the activation code.
At 340, the token collects and stores the user selected password/PIN and identifying information corresponding to the mobile device. For example, the token may store the user selected password/PIN, the phone number (if applicable) of the mobile device, and an ID number that identifies the mobile device (phone ID number in cell phone embodiments). Identifying information may also include High Speed Switching Network (HSSN), SA Number, and/or international mobile equipment identity (IMEI). At this stage, activation access is successful, and the mobile device communicates to the server (240,
Post-activation access is performed each time a user wishes to authenticate to the messaging platform to send or receive secure messages. At 350, the user enters the password/PIN that was stored in the token at 340. At 360, the token verifies the password/PIN entered by the user. The token may also verify the stored phone number and phone ID against the phone number and phone ID of the mobile device with which it is communicating. The phone number and phone ID are checked in embodiments that authenticate a user to a token/mobile device pair.
If the password/PIN is entered incorrectly more than a certain number of times, the token will require the user to re-perform the activation process. If the password/PIN is entered correctly, then the token allows access to user data stored thereon. This may include encryption/decryption keys, seeds used to generate encryption/decryption keys, or any other data or software stored on the token.
After successful post-activation access (authentication), the client software makes token data available to the user on the mobile device display. In some embodiments, the user may not interface directly with user data stored on the token. For example, the client software may include application software that utilizes secure messaging, and the user may only interact with the application software. Encryption, decryption, character mapping, and other secure messaging components to may or may not be visible to the user.
As described above, once the PIN is entered, the token and the mobile device are “married.” Both the token and the server are aware of the parameters defining the mobile device/token marriage. The parameters defining the marriage may include the token ID, mobile device ID, phone carrier ID, or any other identifying information. After marriage, when the user enters a PIN, the token will check to make sure that the marriage parameters are valid before validating the PIN. If any of the marriage parameters are invalid, access is denied, and re-activation becomes necessary. For example, if the token is coupled to a different mobile device, access is denied and re-activation becomes necessary. Likewise, if a communications carrier has changed, access is denied and re-activation becomes necessary.
The various embodiments described with reference to
A message authentication code (MAC) may be determined from either the clear text or the cipher text. In some embodiments, determining the MAC may be as simple as computing parity bits on the clear text before encryption. In these embodiments, the MAC may be encrypted along with the clear text. In other embodiments, determining the MAC may include the use of a hashing function on the cipher text. In these embodiments, the MAC may be along with the cipher text.
At 430, the cipher text is shown with the message authentication code. The message authentication code may be part of the cipher text, or may be appended to the cipher text in the clear. The cipher text with MAC at 430 represents a secure payload to be in included in a message. In some embodiments, the cipher text may contain octets with binary combinations that are not “legal” in a messaging environment. For example, the octet “01111111” may be used as a marker in a message environment, and may not be available as a data character. Similarly, a messaging environment may only allow seven bit characters, and some may only allow a subset of all possible seven bit characters.
The secure payload is encoded to produce a text/SMS compatible payload at 440. In some embodiments, a mapping is performed from binary cipher text to messaging-compatible characters. The text/SMS compatible payload may then be included in a message that is transmitted in a mobile device control channel.
At 510, a text/SMS compatible message is received. This received message corresponds to the message transmitted at the end of the data flow in
The received message is decoded to produce the received cipher text and MAC at 520. This corresponds to the inverse of the encoding operation performed in
A calculated message authentication code (CMAC) is determined from the received clear text 530 at 560. The CMAC and RMAC can then be compared to determine if the message has been received correctly. In some embodiments, cipher text 550 is regenerated from the received clear text 530, and a CMAC is then calculated from the regenerated cipher text. This may be performed for embodiments in which the RMAC was calculated from the cipher text on the transmitting side.
At 610, a user authenticates to the client. If this is a first time use, both activation and post-activation authentications will take place. If this is not a first time use, then a user may authenticate using just the post-activation access. See
At 620, cryptography key components are read from the token to client software. The cryptography key components may include one or more seed values and/or indices from which one or more cryptography keys are derived. For example, if variables “a” and “b” are stored in the token as seeds, and “c” is stored in the token as an index, a cryptography key may be generated from “(a+c)2+b2”. The foregoing seed/index is provided as an example, and the various embodiments of the invention are not so limited.
At 630, the cryptography key (Ki) is generated from the key components read from the token; the clear text is composed; and a secure text/SMS message is created (see
On acknowledgment of successful transmission, the client updates the cryptography key components to be stored in the token so that the next key generated at the client will be Ki+1. At 644, the server verifies if the originating client phone number and/or ID number is valid. If invalid, then the server may ignore the message. The server selects the appropriate cryptography key components, and generates key Ki. In some embodiments, the server maintains communications with multiple clients, and maintains a database with different cryptography key components for each client. The server may use the phone number and/or the phone ID to retrieve cryptography key components corresponding to the client device that originated the message.
The server recovers the clear text and RMAC, and calculates a CMAC described above with reference to
At 646, the server transmits the secure text/SMS response message and receives acknowledgment of a successful transmission. As described above with reference to 640, an acknowledgment of successful transmission does not necessarily indicate that the client has received the secure text/SMS response. At 650, upon successful acknowledgment, the server updates the cryptography key components so that the next key generated at the server will be Ki+2.
At 672, the client receives the secure text/SMS response and verifies that the originating server is valid, and ignores the message if the originating server is invalid. At 674 an optional authentication process takes place. This may be necessary if the authentication from 610 is no longer valid. At 676, the cryptography key components are read from the token to the client software, and 678, the key Ki+1 is generated and used to recover clear text from the received text/SMS message response. A CMAC is calculated and compared with the received RMAC. If they match, then the key components are updated at 680 so that the next key to be used at the client is Ki+2.
As shown in
At 710, the appropriate cryptography key components are selected depending on the destination client. The cryptography key (Kj) is generated from the key components corresponding to the destination client; the clear text is composed; and a secure text/SMS message is created (see
On acknowledgment of successful transmission, the server updates the cryptography key components so that the next key generated at the server will be Kj+1. At 742, the client verifies if the originating server phone number and/or ID number is valid. If invalid, then the client may ignore the message. At 744, a user authenticates to the client. If this is a first time use, both activation and post-activation authentications will take place. If this is not a first time use, then a user may authenticate using just the post-activation access. See
The client reads the cryptography key components from the token at 746, and generates key Kj at 748. The client recovers the clear text and RMAC, and calculates a CMAC described above with reference to
At 760, the client transmits the secure text/SMS response message and receives acknowledgment of a successful transmission. As described above with reference to 720, an acknowledgment of successful transmission does not necessarily indicate that the server has received the secure text/SMS response. At 770, upon successful acknowledgment, the client updates the cryptography key components so that the next key generated at the client will be Kj+2.
At 780, the server receives the secure text/SMS response and verifies that the originating client is valid, and ignores the message if the originating client is invalid. The appropriate cryptography key components are selected and the key Kj+1 is generated. The key Kj+1 is used to recover clear text from the received text/SMS message response. A CMAC is calculated and compared with the received RMAC. If they match, then the key components are updated so that the next key to be used at the server is Kj+2.
Each client token has an originally programmed key component set capable of generating Ki, Kj, and Kref. The server has the knowledge of the same key components. Kref is not used for any standard query or response. The initial key Ki, and subsequent keys, Ki+1, Ki+2, . . . are used for query or response in client originated query-response cycles. The initial key Kj, and subsequent keys, Kj+1, Kj+2, . . . are used for query or response in client originated query-response cycles. is the one that can be generated mathematically with the next increment of the key component that generates Kref.
When an incoming message does not generate CMAC=RMAC, then the receiving device increments to the next few and/or decrements to the previous few keys to determine if it can generate CMAC=RMAC. If that works, then the recipient can understand the query or the response.
If incrementing or decrementing by a few key increments is unsuccessful, then the receiving device uses Kref to see if it can generate CMAC equal to RMAC. If this works, then the sender has just sent to the receiver a new initial key, Ki, encrypted using Kref. In some embodiments, only the server may reset the key. In these embodiments:
1) if the receiving device is a client device, then the client has just received from the server a new initial key, Ki, for synchronization encrypted using Kref.
2) if the receiving device is the server, then it has just received from the client a request to send a new initial key, Ki, for synchronization encrypted using Kref.
If using Kref does not generate CMAC=RMAC, then it is up to the receiving device to initiate the resynchronization of the client-server with a new initial key Ki. In embodiments that allow either the client or the server to reset the key, the receiving device generates a new initial key, Kj, encrypts the new key using Kref, and sends it off to the sending device. In embodiments that only allow the server to reset the key:
1) if the receiving device is a client device, the client needs to send a request to the server to generate a new initial key. This request is sent by encrypting using Kref.
2) if the receiving device is the server, then the server needs to send to the client a new generated initial key. This information is sent by encrypting using Kref.
Using a fixed reference key Kref known by both the client and server allows for key resynchronization at any time. As long as keys go out of sync at random intervals, the use of a fixed key to resynchronize has little to no negative effect on overall link security.
In some embodiments, separate reference key components are maintained to avoid possible synchronization due to simultaneous client and server originated queries. For example, separate sets of key components may be maintained to generate the reference key (Kiref), and key component increments to generate (Ki, Ki+1, Ki+2 . . . ) for client originated queries; and separate sets of key components may be maintained to generate the reference key (Kjref), and key component increments to generate (Kj, Kj+1, Kj+2 . . . ) for server originated queries. In these embodiments, resynchronization of key components needed to generate both Ki and Kj can be handled just by the server and/or client in any predetermined combination. The resynchronization of the components needed to generate either Ki or Kj will always be encrypted using Kiref or Kjref depending on whether it is originated from the client or the server, respectively. When resynchronization components are being sent between the client and the server, not all key components necessary to generate the key increments will be transmitted over the air. In some embodiments, at least one of the key components shall be kept constant and not transmitted over the air.
Processor 930 may be any processing element suitable to communicate with memory 910 and mobile device interface 940.
Memory 910 is shown having token software 912 and application software 914. In some embodiments, token 900 is sold or distributed having both token software 912 and application software 914 in memory 910. For example, memory 910 may be nonvolatile memory having token software 912 for execution by processor 930. Also for example, memory 910 may have application software 914 meant to be installed on a device other than token 900. Application software 914 may include drivers, user interface software, secure messaging software, or any other software that may be installed on a device other than token 900.
Application software 914 may operate in any of multiple languages on multiple operating systems. For example, application software 914 may provide a user interface in any regional language. Also for example, application software 914 may run on any operating system (OS).
Memory 910 also includes cryptography components KEYref 916, KEYi 918, and KEYj 920. Cryptography components KEYref 916, KEYi 918, and KEYj 920, may include key components for generating Kref, Ki, and Kj, respectively. In some embodiments, separate cryptography components are maintained for Kiref, and Kiref, as described above with reference to
Mobile device interface 940 is an interface that allows token 900 to communicate with a mobile device. Mobile device interface 940 may be any wired or wireless interface. For example, in some embodiments, mobile device interface 940 may be compatible with an add-on slot in a mobile device. Also in some embodiments, mobile device interface 940 may be a universal serial bus (USB) interface.
In operation, token 900 may perform method embodiments of the present invention while processor 930 executes token software 912. For example, token 900 may perform authentication or activation methods, and may also perform operations with the various key components, such as providing key components to a mobile device or updating key components. Token 900 may perform any suitable method embodiments described herein.
Token issuer 1010 also supplies user 1024 with activation code 1030. In some embodiments, the activation code 1030 is supplied separately from token 1020, and in other embodiments, the activation code is supplied concurrently with the token. For example, the activation code may be mailed (post or email) separate from the delivery of the token. Also for example, token 1020 and activation code 1030 may be simultaneously delivered personally to a user, as in the case of a user visiting a store or kiosk to obtain the token. The user uses the activation code to authenticate to the secure messaging platform formed by the combination of token 1020 and mobile device 1040.
System 1100 includes activation component 1110, authentication component 1120, SMS encryption component 1130, SMS decryption component 1140, character mapping component 1150, MAC generation component 1160, MAC comparison component 1170, key recovery component 1180, and key increment component 1190.
Activation component 1110 and authentication component 1120 perform the activation access and post-activation access described above with reference to
The following paragraphs provide further disclosure of various invention embodiments. Each embodiment is fully defined by the recitation of the corresponding paragraph, and no other elements are to be considered essential for that particular embodiment. The embodiments include:
an interface capable of communicating with a mobile device; and
an activation component to collect and store identifying information corresponding to the mobile device upon successful activation.
means for coupling to a mobile device;
means for encrypting short message service (SMS) messages.
providing a user with a token compatible with an interface in a mobile device, the token having software installable on the mobile device to allow encrypted short message service (SMS) communications; and
providing the user with an activation code to allow access to functionality provided by the token.
reading cryptography key components;
generating a cryptography key from the cryptography key components;
encrypting a message using the cryptography key to create an encrypted message; and
formatting the encrypted message into a short message service (SMS) text message.
receiving an acknowledgement of successful transmission of the SMS text message; and
updating the cryptography key components.
receiving a short message service (SMS) message;
reading cryptography key components;
generating a cryptography key from the cryptography key components; and
decrypting the SMS message using the cryptography key.
when the RMAC and CMAC do not match, updating the cryptography key components, generating a new cryptography key from the updated cryptography key components, decrypting the SMS message using the new cryptography key, computing a new CMAC, and comparing the new CMAC and RMAC.
checking an identification of an originating device; and
ignoring the SMS message if the identification is incorrect.
composing a response message;
reading second cryptography key components;
generating a second cryptography key from the cryptography key components;
encrypting the response message using the second cryptography key to form an encrypted response message; and
formatting the encrypted response message into an SMS compatible format.
prompting a user for an authentication code to allow access to a secure messaging platform including a plurality of components;
verifying the authentication code;
storing identifying information for the plurality of components; and
prompting the user for password to be used for subsequent authentications.
prompting the user for the password;
verifying the password;
retrieving identifying information of a mobile device currently in use; and
comparing the identifying information of the mobile device currently in use against stored identifying information.
Although the present invention has been described in conjunction with certain embodiments, it is to be understood that modifications and variations may be resorted to without departing from the spirit and scope of the invention as those skilled in the art readily understand. Such modifications and variations are considered to be within the scope of the invention and the appended claims.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US4701601||Apr 26, 1985||Oct 20, 1987||Visa International Service Association||Transaction card with magnetic stripe emulator|
|US4786791||Feb 10, 1987||Nov 22, 1988||Gateway Technology||Data processing apparatus with portable card having magnetic strip simulator|
|US4791283||Jun 3, 1986||Dec 13, 1988||Intellicard International, Inc.||Transaction card magnetic stripe emulator|
|US5574273||Jun 13, 1994||Nov 12, 1996||Hitachi Maxell, Ltd.||Non-contact system parallel data transfer system|
|US5585787||May 2, 1994||Dec 17, 1996||Wallerstein; Robert S.||Programmable credit card|
|US5700037||Jan 16, 1996||Dec 23, 1997||Keller; John A.||Security improved card|
|US5710421||Mar 25, 1996||Jan 20, 1998||Tokai-Rika-Denki-Seisakusho Kabushiki Kaisha||IC card|
|US5834756||Jun 3, 1996||Nov 10, 1998||Motorola, Inc.||Magnetically communicative card|
|US5909491 *||Nov 6, 1996||Jun 1, 1999||Nokia Mobile Phones Limited||Method for sending a secure message in a telecommunications system|
|US5952641||Nov 21, 1996||Sep 14, 1999||C-Sam S.A.||Security device for controlling the access to a personal computer or to a computer terminal|
|US5955961||Sep 25, 1996||Sep 21, 1999||Wallerstein; Robert S.||Programmable transaction card|
|US6016476||Jan 16, 1998||Jan 18, 2000||International Business Machines Corporation||Portable information and transaction processing system and method utilizing biometric authorization and digital certificate security|
|US6021944||Oct 17, 1997||Feb 8, 2000||Hewlett-Packard Company||Transaction terminal for electronic purse transactions and the like|
|US6039260||Jun 23, 1999||Mar 21, 2000||Smartdiskette Gmbh||Intelligent cassette emulator device|
|US6068184||Apr 27, 1998||May 30, 2000||Barnett; Donald A.||Security card and system for use thereof|
|US6182891||Aug 9, 1999||Feb 6, 2001||Ntt Data Communications Systems Corporation||Electronic bankbook, and processing system for financial transaction information using electronic bankbook|
|US6189786||Dec 30, 1999||Feb 20, 2001||Hitachi, Ltd.||Portable terminal device with stackable IC card slot opening|
|US6206293||Dec 1, 1997||Mar 27, 2001||Motorola, Inc.||Magnetically communicative card|
|US6219439||Jul 9, 1999||Apr 17, 2001||Paul M. Burger||Biometric authentication system|
|US6223984||Jun 6, 1997||May 1, 2001||Cybermark, Inc.||Distinct smart card reader having wiegand, magnetic strip and bar code types emulation output|
|US6250557||Aug 25, 1998||Jun 26, 2001||Telefonaktiebolaget Lm Ericsson (Publ)||Methods and arrangements for a smart card wallet and uses thereof|
|US6315195||May 11, 1998||Nov 13, 2001||Diebold, Incorporated||Transaction apparatus and method|
|US6402029||Sep 18, 2000||Jun 11, 2002||E-Micro Corporation||Method and apparatus for combining data for multiple magnetic stripe cards or other sources|
|US6481623||Jun 12, 2000||Nov 19, 2002||Privicom, Inc.||Card reader for transmission of data by sound|
|US6568600||Jan 19, 2000||May 27, 2003||Bull Cp8||Chip card equipped with a loop antenna, and associated micromodule|
|US6588660||Sep 29, 2000||Jul 8, 2003||Hewlett-Packard Development Company, L.P.||Passive contactless smartcard security system|
|US6592044||May 15, 2000||Jul 15, 2003||Jacob Y. Wong||Anonymous electronic card for generating personal coupons useful in commercial and security transactions|
|US6594759||Dec 29, 1998||Jul 15, 2003||Esignx Corporation||Authorization firmware for conducting transactions with an electronic transaction system and methods therefor|
|US6598031||Jul 31, 2000||Jul 22, 2003||Edi Secure Lllp||Apparatus and method for routing encrypted transaction card identifying data through a public telephone network|
|US6607127||Sep 18, 2001||Aug 19, 2003||Jacob Y. Wong||Magnetic stripe bridge|
|US6609654||Sep 21, 2000||Aug 26, 2003||Privasys, Inc.||Method for allowing a user to customize use of a payment card that generates a different payment card number for multiple transactions|
|US6631849||Dec 6, 2000||Oct 14, 2003||Bank One, Delaware, National Association||Selectable multi-purpose card|
|US6636833||Jan 22, 1999||Oct 21, 2003||Obis Patents Ltd.||Credit card system and method|
|US6669487||Apr 28, 2000||Dec 30, 2003||Hitachi, Ltd.||IC card|
|US6705520||Nov 15, 1999||Mar 16, 2004||Satyan G. Pitroda||Point of sale adapter for electronic transaction device|
|US6712277||Dec 5, 2001||Mar 30, 2004||Hewlett-Packard Development Company, L.P.||Multiple interface memory card|
|US6715679||Sep 8, 1999||Apr 6, 2004||At&T Corp.||Universal magnetic stripe card|
|US6721196||Jun 19, 2000||Apr 13, 2004||Giesecke & Devrient Gmbh||Semiconductor memory chip module|
|US6764005||Aug 15, 2001||Jul 20, 2004||Cooper J Carl||Universal credit card apparatus and method|
|US6769607||Jun 6, 2000||Aug 3, 2004||Satyan G. Pitroda||Point of sale and display adapter for electronic transaction device|
|US6805288||Sep 21, 2001||Oct 19, 2004||Larry Routhenstein||Method for generating customer secure card numbers subject to use restrictions by an electronic card|
|US6811082||Nov 2, 2001||Nov 2, 2004||Jacob Y. Wong||Advanced magnetic stripe bridge (AMSB)|
|US6836843||Jun 29, 2001||Dec 28, 2004||Hewlett-Packard Development Company, L.P.||Access control through secure channel using personal identification system|
|US6857566||Nov 25, 2002||Feb 22, 2005||Mastercard International||Method and system for conducting transactions using a payment card with two technologies|
|US6882900||Sep 27, 2000||Apr 19, 2005||Gilbarco Inc.||Fuel dispensing and retail system for providing customer selected guidelines and limitations|
|US6883718||Feb 27, 2004||Apr 26, 2005||Imation Corp.||Credit card sized memory card with host connector|
|US6905072||Oct 17, 2003||Jun 14, 2005||Diebold, Incorporated||Apparatus and method of transmitting transaction signature|
|US6907123 *||Dec 21, 2000||Jun 14, 2005||Cisco Technology, Inc.||Secure voice communication system|
|US6908030||Oct 31, 2001||Jun 21, 2005||Arcot Systems, Inc.||One-time credit card number generator and single round-trip authentication|
|US6925568 *||Jul 12, 2000||Aug 2, 2005||Sonera Oyj||Method and system for the processing of messages in a telecommunication system|
|US7059520||Mar 17, 2005||Jun 13, 2006||Joel Shtesl||Universal credit card integrated with cellular telephone|
|US7333062||Sep 15, 2005||Feb 19, 2008||Motorola, Inc.||Wireless communication device with integrated antenna|
|US7581678||Feb 22, 2005||Sep 1, 2009||Tyfone, Inc.||Electronic transaction card|
|US7828214||Aug 11, 2009||Nov 9, 2010||Tyfone, Inc.||Mobile phone with electronic transaction card|
|US20010002035||Nov 29, 2000||May 31, 2001||Georges Kayanakis||Contactless or hybrid contact-contactless smart card designed to limit the risks of fraud|
|US20010006902||Dec 28, 2000||Jul 5, 2001||Takafumi Ito||IC card with radio interface function, antenna module and data processing apparatus using the IC card|
|US20010013551||Apr 5, 2001||Aug 16, 2001||Diebold, Incorporated||Portable automated banking apparatus and system|
|US20020007434||Jul 8, 1999||Jan 17, 2002||Giovanni Campardo||Non-volatile memory capable of autonomously executing a program|
|US20020043566||Jul 13, 2001||Apr 18, 2002||Alan Goodman||Transaction card and method for reducing frauds|
|US20020044043||Jun 18, 2001||Apr 18, 2002||John Chaco||Patient care and communication system|
|US20020095588||May 11, 2001||Jul 18, 2002||Satoshi Shigematsu||Authentication token and authentication system|
|US20020096570||Jan 25, 2001||Jul 25, 2002||Wong Jacob Y.||Card with a dynamic embossing apparatus|
|US20020099665||Oct 1, 2001||Jul 25, 2002||Burger Todd O.||Portable electronic authorization system and method|
|US20020130187||May 13, 2002||Sep 19, 2002||Berg Jon N.||System for card to card transfer of secure data|
|US20020138422||Dec 7, 2000||Sep 26, 2002||Takeshi Natsuno||Electronic commerce contracts mediating method and mobile communication network|
|US20020138735||Feb 21, 2002||Sep 26, 2002||Felt Edward P.||System and method for message encryption and signing in a transaction processing system|
|US20020139849||Jan 17, 2002||Oct 3, 2002||Gangi Frank J.||Method and apparatus for associating identification and personal data for multiple magnetic stripe cards or other sources|
|US20020148892||Feb 22, 2002||Oct 17, 2002||Biometric Security Card, Inc.||Biometric identification system using biometric images and personal identification number stored on a magnetic stripe and associated methods|
|US20020153424||Apr 19, 2001||Oct 24, 2002||Chuan Li||Method and apparatus of secure credit card transaction|
|US20020158747||Apr 26, 2001||Oct 31, 2002||Mcgregor Christopher M.||Bio-metric smart card, bio-metric smart card reader and method of use|
|US20020178124||May 22, 2001||Nov 28, 2002||Lewis Shawn Michael||Credit card verification system|
|US20020180584||Dec 19, 2001||Dec 5, 2002||Audlem, Ltd.||Bio-metric smart card, bio-metric smart card reader, and method of use|
|US20020186845||Jun 11, 2001||Dec 12, 2002||Santanu Dutta||Method and apparatus for remotely disabling and enabling access to secure transaction functions of a mobile terminal|
|US20030028481||Jun 4, 2002||Feb 6, 2003||Orbis Patents, Ltd.||Credit card system and method|
|US20030052168||Sep 18, 2001||Mar 20, 2003||Wong Jacob Y.||Magnetic Stripe bridge|
|US20030057278||Nov 2, 2001||Mar 27, 2003||Wong Jacob Y.||Advanced magnetic stripe bridge (AMSB)|
|US20030061168||Sep 21, 2001||Mar 27, 2003||Larry Routhenstein||Method for generating customer secure card numbers|
|US20030080183||Oct 31, 2001||May 1, 2003||Sanguthevar Rajasekaran||One-time credit card number generator and single round-trip authentication|
|US20030115126||Oct 31, 2002||Jun 19, 2003||Pitroda Satyan G.||System and methods for servicing electronic transactions|
|US20030159050||May 6, 2002||Aug 21, 2003||Alexander Gantman||System and method for acoustic two factor authentication|
|US20030200180||May 14, 2003||Oct 23, 2003||Frank Phelan||Money card system, method and apparatus|
|US20030220876||Mar 19, 2003||Nov 27, 2003||Burger Todd O.||Portable electronic authorization system and method|
|US20030231550||Jun 13, 2002||Dec 18, 2003||General Motors Corporation||Personalized key system for a mobile vehicle|
|US20040030660||Jul 3, 2003||Feb 12, 2004||Will Shatford||Biometric based authentication system with random generated PIN|
|US20040035942||Dec 7, 2001||Feb 26, 2004||Silverman Martin S.||Dynamic virtual magnetic stripe|
|US20040050930||Sep 17, 2002||Mar 18, 2004||Bernard Rowe||Smart card with onboard authentication facility|
|US20040058705||Dec 21, 2001||Mar 25, 2004||Russell Morgan||Secure point-of-sale cellular telephone docking module system|
|US20040064612||Sep 26, 2002||Apr 1, 2004||Sandisk Corporation||Method and system for using a memory card protocol inside a bus protocol|
|US20040077372||Mar 7, 2001||Apr 22, 2004||Halpern John W.||Mobile phone communications system with increased functionality|
|US20040087339||Oct 28, 2003||May 6, 2004||Scott Goldthwaite||Mobile communication device equipped with a magnetic stripe reader|
|US20040094624||Dec 19, 2002||May 20, 2004||Vivotech, Inc.||Adaptor for magnetic stripe card reader|
|US20040133787||Oct 7, 2003||Jul 8, 2004||Innovation Connection Corporation||System, method and apparatus for enabling transactions using a biometrically enabled programmable magnetic stripe|
|US20040188519||Mar 31, 2003||Sep 30, 2004||Kepler, Ltd. A Hong Kong Corporation||Personal biometric authentication and authorization device|
|US20040199469||Mar 21, 2003||Oct 7, 2004||Barillova Katrina A.||Biometric transaction system and method|
|US20040243806||Mar 4, 2003||Dec 2, 2004||Mckinley Tyler J.||Digital watermarking security systems|
|US20040251303||May 28, 2004||Dec 16, 2004||Cooper J. Carl||Universal credit card apparatus and method|
|US20040255145||Mar 31, 2004||Dec 16, 2004||Jerry Chow||Memory protection systems and methods for writable memory|
|US20050006462||Jul 10, 2004||Jan 13, 2005||Rouille David W.||Security system|
|US20050017068||Jan 6, 2004||Jan 27, 2005||Zalewski Thomas W.||System and method of making payments using an electronic device cover with embedded transponder|
|US20050022002||Jun 25, 2004||Jan 27, 2005||Poisner David I.||Protected configuration space in a protected environment|
|US20050029349||Sep 14, 2004||Feb 10, 2005||Mcgregor Christopher M.||Bio-metric smart card, bio-metric smart card reader, and method of use|
|US20050038736||Jun 24, 2004||Feb 17, 2005||Saunders Peter D.||System and method for transmitting track 1/track 2 formatted information via Radio Frequency|
|US20050039027||Jul 25, 2003||Feb 17, 2005||Shapiro Michael F.||Universal, biometric, self-authenticating identity computer having multiple communication ports|
|US20050044044||Sep 29, 2004||Feb 24, 2005||Chameleon Network, Inc.||Portable electronic authorization system and method|
|US20050050367||Sep 30, 2004||Mar 3, 2005||Chameleon Network, Inc.||Portable electronic authorization system and method|
|US20050060586||Sep 30, 2004||Mar 17, 2005||Chameleon Network, Inc.||Portable electronic authorization system and method|
|US20050071282||Dec 31, 2003||Mar 31, 2005||Lu Hongqian Karen||System and method for preventing identity theft using a secure computing device|
|US20050077349||Dec 14, 2004||Apr 14, 2005||American Express Travel Related Services Company, Inc.||Method and system for facilitating a transaction using a transponder|
|US20050092830||Dec 15, 2004||May 5, 2005||George Blossom||Selectable multi-purpose card|
|US20050108096||Oct 20, 2004||May 19, 2005||Chameleon Network Inc.||Portable electronic authorization system and method|
|US20050109838||Oct 8, 2004||May 26, 2005||James Linlor||Point-of-sale billing via hand-held devices|
|US20050116026||Nov 12, 2004||Jun 2, 2005||Chameleon Network, Inc.||Portable electronic authorization system and method|
|US20050121512||Jan 6, 2005||Jun 9, 2005||John Wankmueller||Method and system for conducting transactions using a payment card with two technologies|
|US20050122209||Dec 3, 2003||Jun 9, 2005||Black Gerald R.||Security authentication method and system|
|US20050127164||Jun 25, 2004||Jun 16, 2005||John Wankmueller||Method and system for conducting a transaction using a proximity device and an identifier|
|US20050127166||Dec 14, 2004||Jun 16, 2005||Matsushita Electric Industrial Co., Ltd.||Secure device and information processing apparatus|
|US20050133606||Dec 17, 2003||Jun 23, 2005||Brown Kerry D.||Programmable magnetic data storage card|
|US20050136964 *||Dec 22, 2003||Jun 23, 2005||Le Saint Eric F.||Intelligent remote device|
|US20050168339||Jan 28, 2005||Aug 4, 2005||Semiconductor Energy Laboratory Co., Ltd.||ID label, ID tag, and ID card|
|US20050177724||Jan 14, 2005||Aug 11, 2005||Valiuddin Ali||Authentication system and method|
|US20050197859||Jan 16, 2004||Sep 8, 2005||Wilson James C.||Portable electronic data storage and retreival system for group data|
|US20050212657||Feb 24, 2005||Sep 29, 2005||Rudy Simon||Identity verification system with self-authenticating card|
|US20050224589||Apr 5, 2005||Oct 13, 2005||Electronics And Telecommunications Research Institute||SD memory card for extension of function|
|US20050240778||Apr 26, 2004||Oct 27, 2005||E-Smart Technologies, Inc., A Nevada Corporation||Smart card for passport, electronic passport, and method, system, and apparatus for authenticating person holding smart card or electronic passport|
|US20050258245||Mar 7, 2005||Nov 24, 2005||Bates Peter K||Radio frequency fobs and methods of using the same|
|US20050268058||May 27, 2004||Dec 1, 2005||Microsoft Corporation||Alternative methods in memory protection|
|US20060011731||Jul 19, 2004||Jan 19, 2006||Gemplus||Durable plastic mini card and method for testing its durability|
|US20060027655||Jul 15, 2005||Feb 9, 2006||Patrick Smets||Method and system for conducting contactless payment card transactions|
|US20060124755||Oct 28, 2005||Jun 15, 2006||Takafumi Ito||Card-shaped memory device incorporating IC card function, adapter for the same and host device|
|US20060169778||Mar 20, 2006||Aug 3, 2006||Chung Kevin K||Electronic voting apparatus, system and method|
|US20060186209||Feb 22, 2005||Aug 24, 2006||Tyfone, Inc.||Electronic transaction card|
|US20060226217||Apr 7, 2005||Oct 12, 2006||Tyfone, Inc.||Sleeve for electronic transaction card|
|US20070076877 *||Sep 30, 2005||Apr 5, 2007||Sony Ericsson Mobile Communications Ab||Shared key encryption using long keypads|
|US20070145135||Dec 28, 2005||Jun 28, 2007||Fabrice Jogand-Coulomb||Methods used in a nested memory system with near field communications capability|
|US20070145152||Dec 28, 2005||Jun 28, 2007||Fabrice Jogand-Coulomb||Nested memory system with near field communications capability|
|US20070257797||Apr 14, 2005||Nov 8, 2007||Arjowiggins Security||Structure Including an Electronic Device, in Particular for Fabricating a Security Document or a Document of Value|
|US20070293202||May 25, 2007||Dec 20, 2007||Celltrust Corporation||Secure mobile information management system and method|
|US20080214111||Feb 27, 2008||Sep 4, 2008||Celltrust Corporation||Lost phone alarm system and method|
|US20080244208||Aug 24, 2007||Oct 2, 2008||Narendra Siva G||Memory card hidden command protocol|
|US20080279381||Aug 24, 2007||Nov 13, 2008||Narendra Siva G||Secure messaging|
|US20090065571||Sep 5, 2008||Mar 12, 2009||Devicefidelity, Inc.||Selectively switching antennas of transaction cards|
|US20090065572||Sep 8, 2008||Mar 12, 2009||Devicefidelity, Inc.||Wirelessly executing transactions with different enterprises|
|US20090069049||Sep 5, 2008||Mar 12, 2009||Devicefidelity, Inc.||Interfacing transaction cards with host devices|
|US20090069050||Sep 12, 2008||Mar 12, 2009||Devicefidelity, Inc.||Updating mobile devices with additional elements|
|US20090069051||Sep 12, 2008||Mar 12, 2009||Devicefidelity, Inc.||Wirelessly accessing broadband services using intelligent covers|
|US20090069052||Sep 12, 2008||Mar 12, 2009||Devicefidelity, Inc.||Receiving broadcast signals using intelligent covers for mobile devices|
|US20090070272||Sep 11, 2008||Mar 12, 2009||Devicefidelity, Inc.||Wirelessly executing financial transactions|
|US20090070691||Sep 5, 2008||Mar 12, 2009||Devicefidelity, Inc.||Presenting web pages through mobile host devices|
|US20090070861||Sep 12, 2008||Mar 12, 2009||Devicefidelity, Inc.||Wirelessly accessing broadband services using intelligent cards|
|US20090108063||Nov 17, 2008||Apr 30, 2009||Deepak Jain||Wirelessly Communicating Radio Frequency Signals|
|US20090152361||Dec 14, 2007||Jun 18, 2009||Narendra Siva G||Memory card based contactless devices|
|US20090199283||Sep 12, 2008||Aug 6, 2009||Devicefidelity, Inc.||Wirelessly receiving broadcast signals using intelligent cards|
|US20090265552||Mar 30, 2009||Oct 22, 2009||Celltrust Corporation||Systems and methods for secure short messaging service and multimedia messaging service|
|US20090298540||Aug 11, 2009||Dec 3, 2009||Tyfone, Inc.||Electronic transaction card|
|US20100033307||Aug 8, 2008||Feb 11, 2010||Narendra Siva G||Small rfid card with integrated inductive element|
|US20100033310||Aug 8, 2008||Feb 11, 2010||Narendra Siva G||Power negotation for small rfid card|
|US20100213265||Feb 23, 2010||Aug 26, 2010||Tyfone, Inc.||Contactless device with miniaturized antenna|
|US20110053644||Nov 8, 2010||Mar 3, 2011||Tyfone, Inc.||Mobile device with transaction card in add-on slot|
|US20110073663||Dec 3, 2010||Mar 31, 2011||Tyfone, Inc.||Memory card compatible financial transaction card|
|US20110073665||Dec 8, 2010||Mar 31, 2011||Tyfone, Inc.||Electronic transaction card powered by mobile device|
|US20110077052||Dec 8, 2010||Mar 31, 2011||Tyfone, Inc.||Provisioning electronic transaction card in mobile device|
|DE3632294A1||Sep 23, 1986||Apr 7, 1988||Siemens Ag||Operating unit for smart cards (chip cards)|
|DE10054890A1||Nov 6, 2000||Apr 25, 2002||Bernd Schneider||Mobile universal data terminal with insertion and head parts has at least one card reading unit in one or more insertion slots with different arrangements for reading different chip card types|
|EP161060A1||Title not available|
|EP0818757A2||Jul 11, 1997||Jan 14, 1998||AT&T Corp.||Universal Authentication device for use over telephone lines|
|EP1014290A2||Nov 26, 1999||Jun 28, 2000||Nokia Mobile Phones Ltd.||Data card holder and reader therefor|
|EP1117068A1||Aug 30, 1999||Jul 18, 2001||C. Media Co. Ltd.||Noncontact ic medium and system using the same|
|EP1178450A2||Oct 25, 1995||Feb 6, 2002||Behruz Vazvan||Real time tele-payment system|
|EP1189465A1||Sep 19, 2000||Mar 20, 2002||Sony International (Europe) GmbH||Mobile terminal with removable memory having SIM card function|
|EP1291748A2||Aug 23, 2002||Mar 12, 2003||Alcatel||Electronic device capable of wirelessly transmitting a password that can be used to unlock/lock a password protected electronic device|
|GB2316908A||Title not available|
|TWI336449B||Title not available|
|WO03/077473A1||Title not available|
|WO2000/14678A1||Title not available|
|WO2098/12674A2||Title not available|
|WO1996026500A1||Jan 11, 1996||Aug 29, 1996||Garry Peek||A magnetic stripe card simulation means, system and method|
|WO2001088659A3||May 15, 2001||Apr 18, 2002||Privasys||Electronic cards capable of being read by a magnetic stripe reader and methods for their use|
|WO2003029942A2||Oct 1, 2002||Apr 10, 2003||Chameleon Network, Inc.||Portable electronic authorization device and associated method|
|WO2003081519A2||Mar 19, 2003||Oct 2, 2003||Chameleon Network Inc.||Portable electronic authorization system and method|
|WO2004012352A1||Jul 24, 2003||Feb 5, 2004||Way Systems, Inc.||Mobile device equipped with a contactless smart card reader/writer|
|WO2004095169A2||Apr 19, 2004||Nov 4, 2004||Josef Osterweil||Method and system for data writing/reading onto/from and emulating a magnetic stripe|
|WO2005027030A1||Sep 9, 2004||Mar 24, 2005||Human Technologies, Inc.||Magnetic stripe generating device, authentication device, authentication system and magnetic stripe generating method|
|WO2005119607A2||Jun 3, 2005||Dec 15, 2005||Tyfone, Inc.||System and method for securing financial transactions|
|WO2005119607A3||Jun 3, 2005||May 4, 2006||Siva G Narendra||System and method for securing financial transactions|
|WO2005119608A1||Jun 3, 2005||Dec 15, 2005||Tyfone, Inc.||System and method for securing financial transactions|
|WO2006091709A2||Feb 21, 2006||Aug 31, 2006||Tyfone, Inc.||Electronic transaction card|
|WO2006091709A3||Feb 21, 2006||Dec 21, 2006||Tyfone Inc||Electronic transaction card|
|WO2006108184A1||Apr 7, 2006||Oct 12, 2006||Tyfone, Inc.||Sleeve for electronic transaction card|
|WO2007011937A2||Jul 18, 2006||Jan 25, 2007||Tyfone, Inc.||Electronic stripe cards|
|WO2008121566A1||Mar 20, 2008||Oct 9, 2008||Tyfone, Inc.||Memory card hidden command protocol|
|WO2009147548A2||May 14, 2009||Dec 10, 2009||Nxp B.V.||Method for storing nfc applications in a secure memory device|
|WO2010099093A1||Feb 23, 2010||Sep 2, 2010||Tyfone, Inc.||Contactless device with miniaturized antenna|
|1||Lee, Youbok "Anntenna Circuit Design for RFID Applications", Lee, Youbok; "Anntenna Circuit Design For RFID Applications", Microchip, AN710, 2003 Microchip Technology Inc., 50 pages, (2003).|
|2||PCT Search Report, Application: PCT/US2006/006361; 13 pgs, 2006.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US8072331||Apr 7, 2011||Dec 6, 2011||Tyfone, Inc.||Mobile payment device|
|US8083145||May 24, 2011||Dec 27, 2011||Tyfone, Inc.||Provisioning an add-on apparatus with smartcard circuity for enabling transactions|
|US8091786||May 24, 2011||Jan 10, 2012||Tyfone, Inc.||Add-on card with smartcard circuitry powered by a mobile device|
|US8136732||Jul 15, 2011||Mar 20, 2012||Tyfone, Inc.||Electronic transaction card with contactless interface|
|US8231061||Feb 23, 2010||Jul 31, 2012||Tyfone, Inc||Contactless device with miniaturized antenna|
|US8408463||Feb 9, 2012||Apr 2, 2013||Tyfone, Inc.||Mobile device add-on apparatus for financial transactions|
|US8410936||Dec 5, 2011||Apr 2, 2013||Tyfone, Inc.||Contactless card that receives power from host device|
|US8451122||Mar 1, 2011||May 28, 2013||Tyfone, Inc.||Smartcard performance enhancement circuits and systems|
|US8457308 *||Jun 11, 2009||Jun 4, 2013||Chi Mei Communications Systems, Inc.||Communication system and method for protecting messages between two mobile phones|
|US8474718||Mar 21, 2012||Jul 2, 2013||Tyfone, Inc.||Method for provisioning an apparatus connected contactless to a mobile device|
|US8544076 *||Nov 11, 2010||Sep 24, 2013||Blackberry Limited||Using a trusted token and push for validating the request for single sign on|
|US8573494||Nov 27, 2011||Nov 5, 2013||Tyfone, Inc.||Apparatus for secure financial transactions|
|US8635452 *||Aug 12, 2009||Jan 21, 2014||Nxp B.V.||Method for generating a cipher-based message authentication code|
|US8814053||Oct 22, 2012||Aug 26, 2014||Tyfone, Inc.||Mobile payment device with small inductive device powered by a host device|
|US8866614||Apr 26, 2013||Oct 21, 2014||Tyfone, Inc.||Active circuit for RFID|
|US8875228||Oct 16, 2012||Oct 28, 2014||Jvl Ventures, Llc||Systems, methods, and computer program products for managing secure elements|
|US8937549||Aug 15, 2014||Jan 20, 2015||Tyfone, Inc.||Enhanced integrated circuit with smartcard controller|
|US9004361||Aug 22, 2012||Apr 14, 2015||Tyfone, Inc.||Wearable device transaction system|
|US9092708||Apr 7, 2015||Jul 28, 2015||Tyfone, Inc.||Wearable device with time-varying magnetic field|
|US9104887||Oct 16, 2012||Aug 11, 2015||Google Inc.||Systems, methods, and computer program products for interfacing multiple service provider trusted service managers and secure elements|
|US9117152||Oct 17, 2014||Aug 25, 2015||Tyfone, Inc.||13.56 MHz enhancement circuit for smartmx smartcard controller|
|US9122965||Oct 17, 2014||Sep 1, 2015||Tyfone, Inc.||13.56 MHz enhancement circuit for smartcard controller|
|US9202156||Jun 23, 2015||Dec 1, 2015||Tyfone, Inc.||Mobile device with time-varying magnetic field|
|US9208423||Aug 23, 2015||Dec 8, 2015||Tyfone, Inc.||Mobile device with time-varying magnetic field and single transaction account numbers|
|US9251453||Sep 27, 2015||Feb 2, 2016||Tyfone, Inc.||Wearable device with time-varying magnetic field and single transaction account numbers|
|US9286049||Mar 24, 2014||Mar 15, 2016||Google Inc.||Systems, methods, and computer program products for managing service installation|
|US9292345||Jul 7, 2014||Mar 22, 2016||Google Inc.||Systems, methods, and computer program products for processing sets of instructions for mobile devices|
|US9311491||Sep 17, 2014||Apr 12, 2016||Google Inc.||Systems, methods, and computer program products for securely managing data on a secure element|
|US9323945||Sep 16, 2014||Apr 26, 2016||Google Inc.||Systems, methods, and computer program products for managing secure elements|
|US9390359||Nov 14, 2014||Jul 12, 2016||Tyfone, Inc.||Mobile device with a contactless smartcard device and active load modulation|
|US9408075||Jun 16, 2014||Aug 2, 2016||Google Inc.||Systems, methods, and computer program products for processing a request relating to a mobile communication device|
|US9479571||Sep 17, 2013||Oct 25, 2016||Google Inc.||Systems, methods, and computer program products for interfacing multiple service provider trusted service managers and secure elements|
|US9483722||Oct 17, 2014||Nov 1, 2016||Tyfone, Inc.||Amplifier and transmission solution for 13.56MHz radio coupled to smartcard controller|
|US9489608||Oct 17, 2014||Nov 8, 2016||Tyfone, Inc.||Amplifier and transmission solution for 13.56MHz radio coupled to smartmx smartcard controller|
|US9495558||Mar 25, 2014||Nov 15, 2016||Google Inc.||Systems, methods, and computer program products for managing access control|
|US9497021||Aug 27, 2010||Nov 15, 2016||Nxp B.V.||Device for generating a message authentication code for authenticating a message|
|US20100054463 *||Jun 11, 2009||Mar 4, 2010||Chi Mei Communication Systems, Inc.||Communication system and method for protecting messages between two mobile phones|
|US20110138182 *||Aug 12, 2009||Jun 9, 2011||Nxp B.V.||Method for Generating a Cipher-based Message Authentication Code|
|US20110180610 *||Apr 7, 2011||Jul 28, 2011||Tyfone, Inc.||Mobile payment device|
|US20110283347 *||Nov 11, 2010||Nov 17, 2011||Mahesh Babubhai Bhuta||Using a trusted token and push for validating the request for single sign on|
|U.S. Classification||380/260, 380/262|
|International Classification||H04L9/12, H04L9/00|
|Cooperative Classification||H04L9/3242, H04L9/3234, H04L2209/56, H04L9/0891, H04L2209/80|
|Jul 16, 2008||AS||Assignment|
Owner name: TYFONE, INC., OREGON
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:NARENDRA, SIVA G.;TADEPALLI, PRABHAKAR;SPITZER, THOMAS N.;AND OTHERS;REEL/FRAME:021245/0061;SIGNING DATES FROM 20071108 TO 20071120
Owner name: TYFONE, INC., OREGON
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:NARENDRA, SIVA G.;TADEPALLI, PRABHAKAR;SPITZER, THOMAS N.;AND OTHERS;SIGNING DATES FROM 20071108 TO 20071120;REEL/FRAME:021245/0061
|Dec 10, 2014||FPAY||Fee payment|
Year of fee payment: 4
|May 15, 2015||AS||Assignment|
Owner name: RPX CORPORATION, CALIFORNIA
Free format text: SECURITY INTEREST;ASSIGNOR:TYFONE, INC.;REEL/FRAME:035685/0760
Effective date: 20150515