US20140223510A1 - System and method for providing diverse secure data communication permissions to trusted applications on a portable communication device - Google Patents
System and method for providing diverse secure data communication permissions to trusted applications on a portable communication device Download PDFInfo
- Publication number
- US20140223510A1 US20140223510A1 US14/250,720 US201414250720A US2014223510A1 US 20140223510 A1 US20140223510 A1 US 20140223510A1 US 201414250720 A US201414250720 A US 201414250720A US 2014223510 A1 US2014223510 A1 US 2014223510A1
- Authority
- US
- United States
- Prior art keywords
- permissions
- credentials
- secure element
- application
- commands
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/322—Aspects of commerce using mobile devices [M-devices]
- G06Q20/3226—Use of secure elements separate from M-devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
- G06F21/34—User authentication involving the use of external additional devices, e.g. dongles or smart cards
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/70—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer
- G06F21/71—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure computing or processing of information
- G06F21/74—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure computing or processing of information operating in dual or compartmented mode, i.e. at least one secure mode
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/20—Point-of-sale [POS] network systems
- G06Q20/204—Point-of-sale [POS] network systems comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
- G06Q20/356—Aspects of software for card payments
- G06Q20/3567—Software being in the reader
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
- G06Q20/357—Cards having a plurality of specified features
- G06Q20/3574—Multiple applications on card
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0807—Network architectures or network communication protocols for network security for authentication of entities using tickets, e.g. Kerberos
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/20—Network architectures or network communication protocols for network security for managing network security; network security policies in general
Definitions
- the present invention relates generally to the use of secure data to complete a wireless transaction, and more particularly to a system and method for providing diverse secure data communication functionality to a plurality of trusted applications on a portable communication device.
- RFID which stands for radio-frequency identification
- RFID uses electromagnetic waves to exchange data between a terminal and some object for the purpose of identification.
- companies have been trying to use RFIDs to supported by cellular telephones to implement an electronic payment product (i.e. credit and/or debit card).
- electronic payment product i.e. credit and/or debit card.
- basic RFID technology raises a number of security concerns that have prompted modifications of the basic technology. Still, widespread adoption of RFID as a mechanism for electronic payments has been slow.
- NFC Near Field Communication
- NFC waves are only transmitted over a short-range (on the order of a few inches) and at high-frequencies.
- NFC devices are already being used to make payments at point of sale devices.
- NFC is an open standard (see, e.g. ISO/IEC 18092) specifying modulation schemes, coding, transfer speeds and RF interface.
- ISO/IEC 18092 open standard
- Card issuers are interested in facilitating the option to pay for application usage and ecommerce using their credit/debit card products. Notwithstanding their self-interest in enabling third party applications to access their financial products, the card issuers may have serious security concerns about broad distribution of security protocols. Similarly, the third party developers may not be interested in developing financial product subroutines. Accordingly, there is a need in the industry for an electronic wallet that is accessible by third party programs to facilitate the payment of charges associated with the use of those programs. The application accessible electronic wallet may also be used via direct access by the consumer to the mobile application.
- the present invention relates to a system for providing first and second trusted applications diverse permission to communicate via a secure element associated with a portable communication device.
- the system comprises a first digital identifier and a first digital token operably associated with the first trusted application; a second digital identifier and a second digital token operably associated with the second trusted application; a card services module disposed on the portable communication device to provide an application programming interface; and a secure data table electronically associated with the card services module, the secure data table including a first entry pairing the first digital identifier with the first digital token and a second entry pairing the second digital identifier with the second digital token, the first entry further including a first set of permissions and the second entry further including a second set of permissions.
- the card services module issues one or more commands to the secure element based on a first action requested by the first trusted application in conjunction with the presentation of the first digital token only if the one or more commands will not violate the first set of permissions.
- the card services module issues one or more commands to the secure element based on a second action requested by the second trusted application in conjunction with the presentation of the second digital token only if the one or more commands will not violate the second set of permissions.
- the present invention also relates to a method of providing first and second trusted applications diverse permission to communicate via a secure element associated with a portable communication device.
- a first set of permissions is assigned to the first trusted application; a second set of permissions is assigned to the second trusted application.
- the method also comprises requesting from the first trusted application that a card services module operably associated with the secure element implement a first action; and issuing one or more commands to the secure element based on the first action requested by the first trusted application only if the one or more commands will not violate the first set of permissions.
- FIG. 1 a illustrates the diagnostic agent installed in the end user's portable communication device asking whether she would like diagnostics performed following a failed attempt to use her device to conduct a secure payment transaction at a point of sale;
- FIG. 1 b illustrates the operable interconnections between the end user's smartphone and various subsystems, including the system management back end;
- FIG. 2 is a block diagram illustrating some of the logical blocks within a portable communication device that may be relevant to the present system
- FIG. 3 is a block diagram illustrating the logical blocks within the system management back end.
- FIG. 4 is a block diagram illustrating further detail of the “OpenWallet” block of FIG. 2 that may be relevant to the present system.
- FIGS. 4A , 4 B, 4 C and 4 D are illustrations of various screens from an exemplary wallet user interface 410 that may be deployed on a smart phone.
- FIG. 5 is a block diagram illustrating the operable interconnections between the end user's smartphone, the control server, and the issuer server.
- FIG. 6 is a block diagram of one potential implementation of a system underlying the grant of permission for one of the third party apps 200 to view, select and/or change secure data stored in the payment subsystem.
- the present invention provides a system and method that can be utilized with a variety of different portable communication devices, including but not limited to PDA's, cellular phones, smart phones, laptops, tablet computers, and other mobile devices that include cellular voice and data service as well as preferable access to consumer downloadable applications.
- portable communication device could be an iPhone, Motorola RAZR or DROID; however, the present invention is preferably platform and device independent.
- the portable communication device technology platform may be Microsoft Windows Mobile, Microsoft Windows Phone 7, Palm OS, RIM Blackberry OS, Apple OS, Android OS, Symbian, Java or any other technology platform.
- the present invention has been generally described in accordance with features and interfaces that are optimized for a smart phone utilizing a generalized platform, although one skilled in the art would understand that all such features and interfaces may also be used and adapted for any other platform and/or device.
- the portable communication device includes one or more short proximity electromagnetic communication devices, such as an NFC, RFID, or Bluetooth transceiver. It is presently preferred to use an NFC baseband that is Compliant with NFC IP 1 standards (www.nfcforum.org), which provides standard functions like peer-to-peer data exchange, reader-writer mode (i.e. harvesting of information from RFID tags), and contactless card emulation (per the NFC IP 1 and ISO 14443 standards) when paired with a secure element on the portable communication device and presented in front of a “contactless payment reader” (see below at point of sale).
- NFC IP 1 www.nfcforum.org
- reader-writer mode i.e. harvesting of information from RFID tags
- contactless card emulation per the NFC IP 1 and ISO 14443 standards
- the NFC IP 1 standards are simply the presently preferred example, which could be exported—in whole or in part—for use in association with any other proximity communication standard. It is further preferred that the portable communication device include an NFC/RFID antenna (conformed to NFC IP 1 and ISO 14443 standards) to enable near field communications. However, as would be understood in the art NFC/RFID communications may be accomplished albeit over even shorter ranges and potential read problems.
- the portable communication device also includes a mobile network interface to establish and manage wireless communications with a mobile network operator.
- the mobile network interface uses one or more communication protocols and technologies including, but not limited to, global system for mobile communication (GSM), 3G, 4G, code division multiple access (CDMA), time division multiple access (TDMA), user datagram protocol (UDP), transmission control protocol/Internet protocol (TCP/IP), SMS, general packet radio service (GPRS), WAP, ultra wide band (UWB), IEEE 802.16 Worldwide Interoperability for Microwave Access (WiMax), SIP/RTP, or any of a variety of other wireless communication protocols to communicate with the mobile network of a mobile network operator.
- GSM global system for mobile communication
- 3G 3G, 4G
- CDMA code division multiple access
- TDMA time division multiple access
- UDP user datagram protocol
- TCP/IP transmission control protocol/Internet protocol
- SMS general packet radio service
- GPRS general packet radio service
- WAP ultra wide band
- WiMax IEEE 802.16 Worldwide Intero
- the mobile network interface may include as a transceiver, transceiving device, or network interface card (NIC). It is contemplated that the mobile network interface and short proximity electromagnetic communication device could share a transceiver or transceiving device, as would be understood in the art by those having the present specification, figures, and claims before them.
- NIC network interface card
- the portable communication device further includes a user interface that provides some means for the consumer to receive information as well as to input information or otherwise respond to the received information.
- this user interface may include a microphone, an audio speaker, a haptic interface, a graphical display, and a keypad, keyboard, pointing device and/or touch screen.
- the portable communication device may further include a location transceiver that can determine the physical coordinates of device on the surface of the Earth typically as a function of its latitude, longitude and altitude.
- This location transceiver preferably uses GPS technology, so it may be referred to herein as a GPS transceiver; however, it should be understood that the location transceiver can additionally (or alternatively) employ other geo-positioning mechanisms, including, but not limited to, triangulation, assisted GPS (AGPS), E-OTD, CI, SAI, ETA, BSS or the like, to determine the physical location of the portable communication device on the surface of the Earth.
- AGPS assisted GPS
- E-OTD E-OTD
- CI CI
- SAI ETA
- BSS BSS
- the portable communication device will also include a microprocessor and mass memory.
- the mass memory may include ROM, RAM as well as one or more removable memory cards.
- the mass memory provides storage for computer readable instructions and other data, including a basic input/output system (“BIOS”) and an operating system for controlling the operation of the portable communication device.
- BIOS basic input/output system
- the portable communication device will also include a device identification memory dedicated to identify the device, such as a SIM card.
- SIM cards contain the unique serial number of the device (ESN), an internationally unique number of the mobile user (IMSI), security authentication and ciphering information, temporary information related to the local network, a list of the services the user has access to and two passwords (PIN for usual use and PUK for unlocking).
- ESN unique serial number of the device
- IMSI internationally unique number of the mobile user
- each portable communication device is thought to have two subsystems: (1) a “wireless subsystem” that enables communication and other data applications as has become commonplace with users of cellular telephones today, and (2) the “secure transactional subsystem” which may also be known as the “payment subsystem”. It is contemplated that this secure transactional subsystem will preferably include a Secure Element, similar (if not identical) to that described as part of the Global Platform 2.1.X, 2.2, or 2.2.X (www.globalplatform.org).
- the secure element has been implemented as a specialized, separate physical memory used for industry common practice of storing payment card track data used with industry common point of sale; additionally, other secure credentials that can be stored in the secure element include employment badge credentials (enterprise access controls), hotel and other card-based access systems and transit credentials.
- Each of the portable communications devices is connected to at least one mobile network operator.
- the mobile network operator generally provides physical infrastructure that supports the wireless communication services, data applications and the secure transactional subsystem via a plurality of cell towers that communicate with a plurality of portable communication devices within each cell tower's associated cell.
- the cell towers may be in operable communication with the logical network of the mobile network operator, POTS, and the Internet to convey the communications and data within the mobile network operator's own logical network as well as to external networks including those of other mobile network operators.
- the mobile network operators generally provide support for one or more communication protocols and technologies including, but not limited to, global system for mobile communication (GSM), 3G, 4G, code division multiple access (CDMA), time division multiple access (TDMA), user datagram protocol (UDP), transmission control protocol/Internet protocol (TCP/IP), SMS, general packet radio service (GPRS), WAP, ultra wide band (UWB), IEEE 802.16 Worldwide Interoperability for Microwave Access (WiMax), SIP/RTP, or any of a variety of other wireless communication protocols to communicate with the portable communication devices.
- GSM global system for mobile communication
- 3G 3G
- 4G code division multiple access
- TDMA time division multiple access
- UDP user datagram protocol
- TCP/IP transmission control protocol/Internet protocol
- SMS general packet radio service
- GPRS general packet radio service
- WAP ultra wide band
- WiMax Worldwide Interoperability for Microwave Access
- SIP/RTP Worldwide Interoperability for Microwave Access
- Standard at merchants today is an Internet Protocol connected payment system that allows for transaction processing of debit, credit, prepay and gift products of banks and merchant service providers.
- a magnetic stripe enabled card at the magnetic reader of a Point of Sale Terminal
- the card data is transferred to the point of sale equipment and used to confirm funds by the issuing bank.
- This point of sale equipment has begun to include contactless card readers as accessories that allow for the payment card data to be presented over an RF interface, in lieu of the magnetic reader.
- the data is transferred to the reader through the RF interface by the ISO 14443 standard and proprietary payment applications like PayPass and Paywave, which transmit the contactless card data from a card and in the future a mobile device that includes a Payment Subsystem.
- a retailer's point of sale device 75 may be connected to a network via a wireless or wired connection.
- This point of sale network may include the Internet in addition to local area networks (LANs), wide area networks (WANs), direct connections, such as through a universal serial bus (USB) port, other forms of computer-readable media, or any combination thereof.
- LANs local area networks
- WANs wide area networks
- USB universal serial bus
- a router acts as a link between LANs, enabling messages to be sent from one to another.
- communication links within LANs typically include twisted wire pair or coaxial cable
- communication links between networks may utilize analog telephone lines, full or fractional dedicated digital lines including T1, T2, T3, and T4, Integrated Services Digital Networks (ISDNs), Digital Subscriber Lines (DSLs), wireless links including satellite links, or other communications links known to those skilled in the art.
- ISDNs Integrated Services Digital Networks
- DSLs Digital Subscriber Lines
- remote computers and other related electronic devices could be remotely connected to either LANs or WANs via a modem and temporary telephone link.
- the point of sale network may utilize any communication method that allows information to travel between the point of sale devices and financial services providers for the purpose of validating, authorizing and ultimately capturing financial transactions at the point of sale for payment via the same financial service providers.
- the system includes a secure transactional subsystem.
- the secure transactional subsystem includes the secure element and associated device software for communication to management and provisioning systems as well as the customer facing interface for use and management of secure data stored in the secure element.
- the secure transactional subsystem will conform, where appropriate, to an international standard, such as the standard defined in Global Platform 2.1.X or 2.2.
- the system includes a system management back end. As shown in FIG. 1 b , the system management back end 300 is connected to the retail subsystem, the secure transactional subsystem and to a plurality of portable communication devices via the infrastructure of at least one mobile network operator.
- the system management back end has a server operably communicating with one or more client devices.
- the server is also in operable communication with the retailer subsystem, secure transactional subsystem, and one or more portable communication devices.
- the server is also in operable communication with the retailer subsystem, secure transactional subsystem, and one or more portable communication devices.
- the communications include data and voice channels. Any type of voice channel may be used in association with the present invention, including but not limited to VoIP.
- the server may comprise one or more general-purpose computers that implement the procedures and functions needed to run the system back office in serial or in parallel on the same computer or across a local or wide area network distributed on a plurality of computers and may even be located “in the cloud” (preferably subject to the provision of sufficient security).
- the computer(s) comprising the server may be controlled by Linux, Windows®, Windows CE, Unix, or a Java® based operating system, to name a few.
- the system management back end server is operably associated with mass memory that stores program code and data.
- Data may include one or more databases, text, spreadsheet, folder, file, or the like, that may be configured to maintain and store a knowledge base, user identifiers (ESN, IMSI, PIN, telephone number, email/IM address, billing information, or the like).
- the system management back end server supports a case management system to provide call traffic connectivity and distribution across the client computers in the customer care center.
- the case management system is a contact/case management system distributed by Contactual, Inc. of Redwood City, Calif.
- the Contactual system is a standard CRM system for a VoIP-based customer care call center that also provides flexibility to handle care issues with simultaneous payments and cellular-related care concerns.
- Salesforce Saalesforce.com, inc. of San Francisco, Calif.
- Novo Novo Solutions, Inc. of Virginia Beach, Va.
- Each client computer associated with the system management back end server has a network interface device, graphical user interface, and voice communication capabilities that match the voice channel(s) supported by the client care center server, such as VoIP.
- Each client computer can request status of both the cellular and secure transactional subsystems of a portable communication device. This status may include the contents of the soft memory and core performance of portable communication device, the NFC components: baseband, NFC antenna, secure element status and identification.
- each portable communication device 50 may contain one or more third party applications 200 (e.g. selected by the consumer), OpenWallet 100 , payment libraries 110 , secure element 120 , NFC Baseband, a payment subsystem 150 (i.e. secure data store 115 and secure element 120 ), and diagnostic agent 170 .
- OpenWallet 100 is a computer application that allows the consumer to see all credentials (e.g., card, coupon, access control and ticket data) stored in the device 50 (preferably in payment subsystem 150 ).
- OpenWallet 100 would also preferably track the issuers of all the credentials stored in the portable communication device's payment subsystem 150 and determine on an application-by-application basis whether that third party application should have permissions to view, select and/or change the credentials stored in the payment subsystem. In this manner, OpenWallet 100 also prevents unauthorized applications from accessing data stored in the payment subsystem 150 , which they do not currently have permission to access.
- the payment libraries 110 are used by OpenWallet 100 to manage (and perform housekeeping tasks on) the secure element 120 , interface with the system management back end, and perform over-the-air (OTA) provisioning via data communication transceiver (including its SMS channel), on the device 50 . It is contemplated that the OTA data communications will be encrypted in some manner and an encryption key will be deployed in card services module 420 .
- the payment subsystem 150 may be used to store credentials such as payment card, coupon, access control and ticket data (e.g. transportation, concert). Some of these payment types may be added to the payment subsystem by different applications 200 for use by those applications. In this manner, other third party applications (not shown) may be precluded from accessing the payment subsystem 150 .
- the secure data store 115 provides secured storage on the portable communication device 50 .
- Various levels of security may be provided depending upon the nature of the data intended for storage in secure data store 115 .
- secure data store 115 may simply be password-protected at the operating system level of device 50 .
- the password may be a simple alphanumeric or hexadecimal code that is stored somewhere on the device 50 .
- the data in secure data store 115 is preferably encrypted.
- the secure data store 115 will be set up as a virtual secure element in the manner disclosed in the co-pending patent application (owned by the assignee of the present application) entitled “System and Method for Providing A Virtual Secure Element on a Portable Communication Device” filed contemporaneously herewith and hereby incorporated by reference.
- OpenWallet 100 preferably removes the complexity involved in the storage, maintenance and use of credentials such as card, coupon, ticket, access control data from one or multiple sources or issuers in association with the payment subsystem 150 . OpenWallet 100 also preferably enforces access control to the data stored in the payment subsystem 150 and the functions allowed by each application. In one approach, OpenWallet 100 verifies the author/issuer of each third party application stored on the portable communication device 50 . This verification may be accomplished by accessing a local authorization database of permitted (i.e., trusted) applications (see FIG. 6 ).
- card services module 420 access and/or manipulate data stored in the payment subsystem 150 and/or meta data repository 125 (which stores, among other things, card image data and any embossed card data).
- an application 200 or wallet user interface 410 needs to interact with the payment subsystem 150 it does so by passing a digital identifier (such as its Issuer ID or App ID), a digital token (i.e., Compile ID or Secret Token ID), the desired action, and any associated arguments needed for the action to the card services module 420 .
- Card services module 420 verifies the digital identifier-digital token pair matches trusted application data in the secure data table ( FIG. 6 ), and then would issue the one or more commands necessary to execute the desired action.
- a digital identifier such as its Issuer ID or App ID
- a digital token i.e., Compile ID or Secret Token ID
- Card services module 420 verifies the digital identifier-digital token pair matches trusted application data in the secure data table ( FIG. 6 ), and then would issue the one or more commands necessary to execute the desired action.
- the potential actions that may be used by applications 200 or wallet user interface 410 are those associated with:
- FIG. 4 illustrates further detail of the “OpenWallet” block of FIG. 2 .
- the functions of “OpenWallet” 100 can be integrated into a single dedicated module that provides a user interface that is closely coupled to the card services.
- the capabilities and functionality of OpenWallet 100 may be distributed between a Wallet User Interface 410 and a Card Services Module 420 . The distributed approach would allow applications to have direct access to the Card Services Module 420 without having to use the user interface provided by Wallet User Interface 410 .
- the Card Services Module 420 may be configured to track the issuer of all card, coupon, access and ticket data stored in the payment subsystem 150 of the portable communication device 50 and determine on an application-by-application basis whether an application should have permissions to view, select, use and/or change secure data stored in the payment subsystem.
- the wallet user interface 410 provides a user interface through which a user may register, provision, access and/or use the information securely stored in association with the card services module 420 relating to the user's credentials. Because the wallet user interface 410 is separated from the card services module 420 , the user may elect to use one of the third party applications 200 to manage information in the Card Services Module 420 .
- metadata such as credential logos (e.g.
- affinity images e.g. AA Advantage® and United Mileage Plus®
- affinity images e.g. AA Advantage® and United Mileage Plus®
- this metadata can be shared across applications, the storage needed to implement secured transaction may be minimized.
- FIGS. 4A , 4 B, 4 C and 4 D Various screen shots of one exemplary wallet user interface 410 that may be deployed on a smart phone are shown in FIGS. 4A , 4 B, 4 C and 4 D. Among other things these figures illustrate the functionality of registering, provisioning, access and/or using information securely stored in association with the card services module 420 .
- FIG. 4A depicts that the wallet can hold various credentials such as cards, coupons, tickets and more.
- FIG. 4A further depicts that multiple cards may be stored in the wallet 100 .
- FIG. 4D upon selecting the VISA® card from the screen illustrated in FIG. 4A , the wallet user interface opens another screen that provides an interface for the user to initiate a secure NFC payment transaction. As also depicted, the user interface may show balance and available credit information.
- FIG. 5 illustrates one exemplary system architecture that may be utilized to provision credentials in the system.
- the user's portable communication device 50 is configured to communicate with a control server and an issuer adapter.
- the control server (which may alternatively be known as a Card Application Management System) is configured to validate a user's credentials. For example, if the user wishes to store information relating to a credit card in the secure element 120 of their mobile device 50 , they would input their credit card information via a user interface displayed on their portable device 50 .
- the user interface may be generated by wallet user interface 410 or a trusted third party application 200 supported by OpenWallet 100 .
- FIGS. 4A and 4B illustrate the provisioning of a “Charge-It Card” into the wallet using one exemplary wallet user interface 410 that may be deployed on a smart phone.
- the card services module 420 preferably transmits the first six digits of the identified credit card (commonly referred to as the Bank Identification Number or BIN) to the control server, which then validates the card issuer's compliance rules and facilitates a direct key exchange between the OpenWallet 100 (or Card Services Module 420 ) on the user's mobile device 50 and the appropriate issuer server in an encrypted fashion as was previously known in the art.
- the Issuer Server authenticates the user, executes issuer rules and then initiate the personalization process.
- the Issuer Server is preferably a server operated by the issuer of the credentials that the user is seeking to provision.
- the issuer server may verify the user, for example by providing a series of verification questions based on user information previously provided to the issuer (see FIG. 4B ).
- the issuer server passes the full 16 digit credit card number to the secure element 120 via the card services module 420 .
- the issuer server may also pass metadata, such as information relating to the look and design of the selected credit card to the application memory 125 .
- the issuer adapter would notify the control server about the completion of the transaction.
- FIG. 4C following provisioning the wallet user interface 410 would include the Charge-It Card, which the user could select using user interface techniques that are well-known in the art of smart phone user interfaces.
- OpenWallet 100 verifies the trusted status of any third party application 200 before that application is allowed access to the secure element 120 (or secure data store 115 and even preferably the meta data repository 125 ) on the portable communication device 50 to view, select and/or change secure data stored in the payment subsystem 150 .
- this verification may be accomplished by accessing a local authorization database of permitted or trusted applications.
- the local authorization database in cooperates with a remote authorization database associated with one or more servers associated with system management back end 300 .
- FIG. 6 is a block diagram of one potential implementation of one potential combination local and remote authorization databases to enhance security of the card services module 420 , secure element 120 , and payment subsystem 150 .
- a User A/C Registry (or User Account Registry) may be associated with the server (or otherwise deployed in the cloud).
- the User A/C Registry may store the identification of the secure element 120 disposed in each user's portable device 50 . Entries in the User Account Registry may be added for each user at any point in the process.
- the “Issuer Registry” database is a database of approved Issuers.
- the Issuer ID is unique for each type of credential.
- each credential type would have its own Issuer ID (e.g. I-BofA-II).
- the Issuer ID as between multiple types of credentials would have some common elements, so as to indicated that the credentials are at least related (e.g. I-BofA-I). In this way applications from same issuer can share data with the other application of the same “extended” issuer.
- card services module 420 can be simplified by requiring even the wallet user interface 410 (which “ships with the system”) to have an Issuer ID (and as well as an Application ID and Compile token).
- the “Application Registry” is a database of applications (mostly third party) that have pre-approved by an operating system provider. Like the User A/C Registry, the “Application Registry” and “Issuer Registry” database are maintained on the server side (or otherwise in the cloud) in operable association with OpenIssuance (see FIG. 3 ). As would be understood by those of ordinary skill in the art having the present specification before them, the various registries may be implemented in separate databases or one unified database. At initiation of a wallet 100 and preferably at substantially regular time-intervals thereafter (e.g., daily), the data stored in the Application Registry of Open Issuance (see, FIG. 3 ) is distributed to devices with the wallet to be stored locally.
- substantially regular time-intervals thereafter e.g., daily
- the Application Registry may include, among other information, an Application ID (“App ID”), an Issuer ID, and a Compile ID or token.
- the Compile ID is a global constant generated for each application by one or more processes associated with Open Issuance ( FIG. 3 ) during the qualification process for the particular application 200 .
- the Compile token is included or otherwise associated with the application.
- This Compile token is preferably generated by a pseudo-random number generator local to the device that uses a pre-determined seed, such as the Application ID, Compile ID, Issuer ID or some combination thereof.
- the Compile ID (a digital token) and Application ID (a digital identifier) associated with the third party application may be matched against the Compile ID and Application ID pairs stored in the Card Services Registry stored on the device 50 (see FIG. 6 ).
- the same Compile and Application ID pairs are transmitted to other devices 50 associated with the system, as well.
- a Secret Token ID is preferably generated on the device 50 by a pseudo-random number generator (such as the one associated with the Secure Element 120 and then stored in association with the Compile ID/Application ID pair in the Card Services Registry on the device 50 .
- the Compile ID may be pre-selected and used to seed the random number generator. It should be understood that one or more pieces of other predetermined data associated with the card services registry could be preselected as the seed instead.
- the card services Registry is preferably stored in secure memory (rather than the secure element 120 because secure element 120 has limited real estate) and the Card Services Registry is preferably further encrypted using standard encryption techniques.
- the Secret Token ID is also embedded in or otherwise associated with the application 200 on the device 50 in place of the Compile ID that was distributed with the application.
- the third party may launch and may prompt the user to opt-in to provide access to the issuer-specific credential needed for the validated (or trusted) application.
- the embedded Secret Token and/or Application ID are compared to the data in the Card Services Registry on the device. If there is match, the application is trusted and can access the payment subsystem 150 via card services module 420 . In this manner, it can be seen that applications 200 or wallet user interface 410 may also be removed from the Card Services Registry and thus would be disabled from accessing the payment subsystem and possibly the application, altogether.
- Card services module 420 also preferably uses the trusted application verification step to determine the appropriate level of subsystem access allowed for each application 200 .
- one application 200 a may be authorized to access and display all of the data contained in the payment subsystem 150
- another third party application 200 x may be only authorized to access and display a subset of the data contained in the payment subsystem 150 .
- an application may be permitted only to send a payment or transaction requests to OpenWallet 100 , but may not itself be permitted to access any of the data contained in the payment subsystem 150 .
- assignment of permissions to the application can be thought of as follows:
- Credentials Credentials Read 0 0 or 1 0 or 1 0 or 1 Write 0 0 or 1 0 or 1 0 or 1 Delete 0 0 or 1 0 or 1 0 or 1 Activate/Deactivate 0 0 or 1 0 or 1 0 or 1 Download Credential 0 0 or 1 0 or 1 0 or 1
- permission can be used to form 4 hexadecimal number in the order shown above from most to least significant figure.
- the I-BofA-II issuer has permission level 11111, which can be thought to expand to 0001 0001 0001 0001 0001.
- the I-BofA-II application can read, write, delete, activate/deactivate, and download its own credentials but not the extended issuer credentials let alone all credentials. If BofA had another issuer code (e.g. I-BofA-I), then that would be an extended Issuer application. So, if the permission level of the application associated with Issuer ID “I-BofA-II” was set to 0010 0001 0001 0010 0001 (or 21121 hexadecimal) then the application would be able to read and activate/deactivate the credentials associated with both issuer IDs.
- the wallet user interface 410 may be given a permission level of 44444 (i.e. 0100 0100 0100 0100 0100 0100).
- the wallet user interface 410 can read, write, delete, activate/deactivate, and download all credentials.
- these are merely examples of potential permissions that can be granted to applications, other permissions are contemplated.
- some applications may have the ability to read extended issuer credentials, but only write, delete, activate and download the application's own credentials (e.g. 21111, which expands to 0010 0001 0001 0001 0001).
- an application may only be given activate/deactivate and download rights (e.g. 0000 0000 0000 0001 0001 or 00011 in hexadecimal).
- an application may be disabled—without being deleted from the trusted application database or Card Service Registry—by setting all rights to zero.
Abstract
Description
- This application is a continuation of U.S. application Ser. No. 13/279,200, filed on Oct. 21, 2011, entitled “System and Method for Providing Diverse Secure Data Communication Permissions to Trusted Applications on a Portable Communication Device,” which claims priority to U.S. Provisional Patent Application No. 61/414,847, filed on Nov. 17, 2010, entitled “System and Method for Providing Secure Data Communication Functionality to a Variety of Applications on a Portable Communication Device.” The content of each of which is incorporated herein by reference in its entirety.
- The present invention relates generally to the use of secure data to complete a wireless transaction, and more particularly to a system and method for providing diverse secure data communication functionality to a plurality of trusted applications on a portable communication device.
- Wireless transactions using RFID-based proximity cards are fairly common place. For instance, many workers use RFID keycards to gain access to their workplace and drivers use RFID passes to pay tolls at highway speeds. RFID, which stands for radio-frequency identification, uses electromagnetic waves to exchange data between a terminal and some object for the purpose of identification. More recently, companies have been trying to use RFIDs to supported by cellular telephones to implement an electronic payment product (i.e. credit and/or debit card). However, basic RFID technology raises a number of security concerns that have prompted modifications of the basic technology. Still, widespread adoption of RFID as a mechanism for electronic payments has been slow.
- Near Field Communication (NFC) is another technology that uses electromagnetic waves to exchange data. NFC waves are only transmitted over a short-range (on the order of a few inches) and at high-frequencies. NFC devices are already being used to make payments at point of sale devices. NFC is an open standard (see, e.g. ISO/IEC 18092) specifying modulation schemes, coding, transfer speeds and RF interface. There has been wider adoption of NFC as a communication platform because it provides better security for financial transactions and access control. Other short distance communication protocols are known and may gain acceptance for use in supporting financial transactions and access control.
- Many applications have been developed for use in association with portable communications devices. Some of these applications would benefit from having access to electronic funds to facilitate the consumer's consummation of a electronic transactions via those applications, such as the purchase of goods over the Internet. Still other applications have no purpose if they cannot access the secure data subsystem of the portable communication device.
- Card issuers are interested in facilitating the option to pay for application usage and ecommerce using their credit/debit card products. Notwithstanding their self-interest in enabling third party applications to access their financial products, the card issuers may have serious security concerns about broad distribution of security protocols. Similarly, the third party developers may not be interested in developing financial product subroutines. Accordingly, there is a need in the industry for an electronic wallet that is accessible by third party programs to facilitate the payment of charges associated with the use of those programs. The application accessible electronic wallet may also be used via direct access by the consumer to the mobile application.
- Accordingly, the present invention seeks to provide one or more solutions to the foregoing problems and related problems as would be understood by those of ordinary skill in the art having the present specification before them. These and other objects and advantages of the present disclosure will be apparent to those of ordinary skill in the art having the present drawings, specifications, and claims before them. It is intended that all such additional systems, methods, features, and advantages be included within this description, be within the scope of the disclosure, and be protected by the accompanying claims.
- The present invention relates to a system for providing first and second trusted applications diverse permission to communicate via a secure element associated with a portable communication device. The system comprises a first digital identifier and a first digital token operably associated with the first trusted application; a second digital identifier and a second digital token operably associated with the second trusted application; a card services module disposed on the portable communication device to provide an application programming interface; and a secure data table electronically associated with the card services module, the secure data table including a first entry pairing the first digital identifier with the first digital token and a second entry pairing the second digital identifier with the second digital token, the first entry further including a first set of permissions and the second entry further including a second set of permissions. The card services module issues one or more commands to the secure element based on a first action requested by the first trusted application in conjunction with the presentation of the first digital token only if the one or more commands will not violate the first set of permissions. The card services module issues one or more commands to the secure element based on a second action requested by the second trusted application in conjunction with the presentation of the second digital token only if the one or more commands will not violate the second set of permissions.
- The present invention also relates to a method of providing first and second trusted applications diverse permission to communicate via a secure element associated with a portable communication device. A first set of permissions is assigned to the first trusted application; a second set of permissions is assigned to the second trusted application. The method also comprises requesting from the first trusted application that a card services module operably associated with the secure element implement a first action; and issuing one or more commands to the secure element based on the first action requested by the first trusted application only if the one or more commands will not violate the first set of permissions.
- For a better understanding of the present disclosure, non-limiting and non-exhaustive embodiments are described in reference to the following drawings. In the drawings, like reference numerals refer to like parts through all the various figures unless otherwise specified.
-
FIG. 1 a illustrates the diagnostic agent installed in the end user's portable communication device asking whether she would like diagnostics performed following a failed attempt to use her device to conduct a secure payment transaction at a point of sale; -
FIG. 1 b illustrates the operable interconnections between the end user's smartphone and various subsystems, including the system management back end; -
FIG. 2 is a block diagram illustrating some of the logical blocks within a portable communication device that may be relevant to the present system; -
FIG. 3 is a block diagram illustrating the logical blocks within the system management back end. -
FIG. 4 is a block diagram illustrating further detail of the “OpenWallet” block ofFIG. 2 that may be relevant to the present system. -
FIGS. 4A , 4B, 4C and 4D are illustrations of various screens from an exemplarywallet user interface 410 that may be deployed on a smart phone. -
FIG. 5 is a block diagram illustrating the operable interconnections between the end user's smartphone, the control server, and the issuer server. -
FIG. 6 is a block diagram of one potential implementation of a system underlying the grant of permission for one of thethird party apps 200 to view, select and/or change secure data stored in the payment subsystem. - The present invention now will be described more fully hereinafter with reference to the accompanying drawings, which form a part hereof, and which show, by way of illustration, specific exemplary embodiments by which the invention may be practiced. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Among other things, the present invention may be embodied as methods or devices. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. The following detailed description is, therefore, not to be taken in a limiting sense.
- The present invention provides a system and method that can be utilized with a variety of different portable communication devices, including but not limited to PDA's, cellular phones, smart phones, laptops, tablet computers, and other mobile devices that include cellular voice and data service as well as preferable access to consumer downloadable applications. One such portable communication device could be an iPhone, Motorola RAZR or DROID; however, the present invention is preferably platform and device independent. For example, the portable communication device technology platform may be Microsoft Windows Mobile, Microsoft Windows Phone 7, Palm OS, RIM Blackberry OS, Apple OS, Android OS, Symbian, Java or any other technology platform. For purposes of this disclosure, the present invention has been generally described in accordance with features and interfaces that are optimized for a smart phone utilizing a generalized platform, although one skilled in the art would understand that all such features and interfaces may also be used and adapted for any other platform and/or device.
- The portable communication device includes one or more short proximity electromagnetic communication devices, such as an NFC, RFID, or Bluetooth transceiver. It is presently preferred to use an NFC baseband that is Compliant with
NFC IP 1 standards (www.nfcforum.org), which provides standard functions like peer-to-peer data exchange, reader-writer mode (i.e. harvesting of information from RFID tags), and contactless card emulation (per theNFC IP 1 and ISO 14443 standards) when paired with a secure element on the portable communication device and presented in front of a “contactless payment reader” (see below at point of sale). As would be understood in the art by those having the present specification, figures, and claims before them, the NFCIP 1 standards are simply the presently preferred example, which could be exported—in whole or in part—for use in association with any other proximity communication standard. It is further preferred that the portable communication device include an NFC/RFID antenna (conformed to NFC IP 1 and ISO 14443 standards) to enable near field communications. However, as would be understood in the art NFC/RFID communications may be accomplished albeit over even shorter ranges and potential read problems. - The portable communication device also includes a mobile network interface to establish and manage wireless communications with a mobile network operator. The mobile network interface uses one or more communication protocols and technologies including, but not limited to, global system for mobile communication (GSM), 3G, 4G, code division multiple access (CDMA), time division multiple access (TDMA), user datagram protocol (UDP), transmission control protocol/Internet protocol (TCP/IP), SMS, general packet radio service (GPRS), WAP, ultra wide band (UWB), IEEE 802.16 Worldwide Interoperability for Microwave Access (WiMax), SIP/RTP, or any of a variety of other wireless communication protocols to communicate with the mobile network of a mobile network operator. Accordingly, the mobile network interface may include as a transceiver, transceiving device, or network interface card (NIC). It is contemplated that the mobile network interface and short proximity electromagnetic communication device could share a transceiver or transceiving device, as would be understood in the art by those having the present specification, figures, and claims before them.
- The portable communication device further includes a user interface that provides some means for the consumer to receive information as well as to input information or otherwise respond to the received information. As is presently understood (without intending to limit the present disclosure thereto) this user interface may include a microphone, an audio speaker, a haptic interface, a graphical display, and a keypad, keyboard, pointing device and/or touch screen. As would be understood in the art by those having the present specification, figures, and claims before them, the portable communication device may further include a location transceiver that can determine the physical coordinates of device on the surface of the Earth typically as a function of its latitude, longitude and altitude. This location transceiver preferably uses GPS technology, so it may be referred to herein as a GPS transceiver; however, it should be understood that the location transceiver can additionally (or alternatively) employ other geo-positioning mechanisms, including, but not limited to, triangulation, assisted GPS (AGPS), E-OTD, CI, SAI, ETA, BSS or the like, to determine the physical location of the portable communication device on the surface of the Earth.
- The portable communication device will also include a microprocessor and mass memory. The mass memory may include ROM, RAM as well as one or more removable memory cards. The mass memory provides storage for computer readable instructions and other data, including a basic input/output system (“BIOS”) and an operating system for controlling the operation of the portable communication device. The portable communication device will also include a device identification memory dedicated to identify the device, such as a SIM card. As is generally understood, SIM cards contain the unique serial number of the device (ESN), an internationally unique number of the mobile user (IMSI), security authentication and ciphering information, temporary information related to the local network, a list of the services the user has access to and two passwords (PIN for usual use and PUK for unlocking). As would be understood in the art by those having the present specification, figures, and claims before them, other information may be maintained in the device identification memory depending upon the type of device, its primary network type, home mobile network operator, etc.
- In the present invention each portable communication device is thought to have two subsystems: (1) a “wireless subsystem” that enables communication and other data applications as has become commonplace with users of cellular telephones today, and (2) the “secure transactional subsystem” which may also be known as the “payment subsystem”. It is contemplated that this secure transactional subsystem will preferably include a Secure Element, similar (if not identical) to that described as part of the Global Platform 2.1.X, 2.2, or 2.2.X (www.globalplatform.org). The secure element has been implemented as a specialized, separate physical memory used for industry common practice of storing payment card track data used with industry common point of sale; additionally, other secure credentials that can be stored in the secure element include employment badge credentials (enterprise access controls), hotel and other card-based access systems and transit credentials.
- Each of the portable communications devices is connected to at least one mobile network operator. The mobile network operator generally provides physical infrastructure that supports the wireless communication services, data applications and the secure transactional subsystem via a plurality of cell towers that communicate with a plurality of portable communication devices within each cell tower's associated cell. In turn, the cell towers may be in operable communication with the logical network of the mobile network operator, POTS, and the Internet to convey the communications and data within the mobile network operator's own logical network as well as to external networks including those of other mobile network operators. The mobile network operators generally provide support for one or more communication protocols and technologies including, but not limited to, global system for mobile communication (GSM), 3G, 4G, code division multiple access (CDMA), time division multiple access (TDMA), user datagram protocol (UDP), transmission control protocol/Internet protocol (TCP/IP), SMS, general packet radio service (GPRS), WAP, ultra wide band (UWB), IEEE 802.16 Worldwide Interoperability for Microwave Access (WiMax), SIP/RTP, or any of a variety of other wireless communication protocols to communicate with the portable communication devices.
- Standard at merchants today is an Internet Protocol connected payment system that allows for transaction processing of debit, credit, prepay and gift products of banks and merchant service providers. By swiping a magnetic stripe enabled card at the magnetic reader of a Point of Sale Terminal, the card data is transferred to the point of sale equipment and used to confirm funds by the issuing bank. This point of sale equipment has begun to include contactless card readers as accessories that allow for the payment card data to be presented over an RF interface, in lieu of the magnetic reader. The data is transferred to the reader through the RF interface by the ISO 14443 standard and proprietary payment applications like PayPass and Paywave, which transmit the contactless card data from a card and in the future a mobile device that includes a Payment Subsystem.
- A retailer's point of
sale device 75 may be connected to a network via a wireless or wired connection. This point of sale network may include the Internet in addition to local area networks (LANs), wide area networks (WANs), direct connections, such as through a universal serial bus (USB) port, other forms of computer-readable media, or any combination thereof. On an interconnected set of LANs, including those based on differing architectures and protocols, a router acts as a link between LANs, enabling messages to be sent from one to another. In addition, communication links within LANs typically include twisted wire pair or coaxial cable, while communication links between networks may utilize analog telephone lines, full or fractional dedicated digital lines including T1, T2, T3, and T4, Integrated Services Digital Networks (ISDNs), Digital Subscriber Lines (DSLs), wireless links including satellite links, or other communications links known to those skilled in the art. Furthermore, remote computers and other related electronic devices could be remotely connected to either LANs or WANs via a modem and temporary telephone link. In essence, the point of sale network may utilize any communication method that allows information to travel between the point of sale devices and financial services providers for the purpose of validating, authorizing and ultimately capturing financial transactions at the point of sale for payment via the same financial service providers. - The system includes a secure transactional subsystem. The secure transactional subsystem includes the secure element and associated device software for communication to management and provisioning systems as well as the customer facing interface for use and management of secure data stored in the secure element. Preferably the secure transactional subsystem will conform, where appropriate, to an international standard, such as the standard defined in Global Platform 2.1.X or 2.2.
- System Management Back End
- The system includes a system management back end. As shown in
FIG. 1 b, the system managementback end 300 is connected to the retail subsystem, the secure transactional subsystem and to a plurality of portable communication devices via the infrastructure of at least one mobile network operator. The system management back end has a server operably communicating with one or more client devices. The server is also in operable communication with the retailer subsystem, secure transactional subsystem, and one or more portable communication devices. The server is also in operable communication with the retailer subsystem, secure transactional subsystem, and one or more portable communication devices. The communications include data and voice channels. Any type of voice channel may be used in association with the present invention, including but not limited to VoIP. - The server may comprise one or more general-purpose computers that implement the procedures and functions needed to run the system back office in serial or in parallel on the same computer or across a local or wide area network distributed on a plurality of computers and may even be located “in the cloud” (preferably subject to the provision of sufficient security). The computer(s) comprising the server may be controlled by Linux, Windows®, Windows CE, Unix, or a Java® based operating system, to name a few. The system management back end server is operably associated with mass memory that stores program code and data. Data may include one or more databases, text, spreadsheet, folder, file, or the like, that may be configured to maintain and store a knowledge base, user identifiers (ESN, IMSI, PIN, telephone number, email/IM address, billing information, or the like).
- The system management back end server supports a case management system to provide call traffic connectivity and distribution across the client computers in the customer care center. In a preferred approach using VoIP voice channel connectivity, the case management system is a contact/case management system distributed by Contactual, Inc. of Redwood City, Calif. The Contactual system is a standard CRM system for a VoIP-based customer care call center that also provides flexibility to handle care issues with simultaneous payments and cellular-related care concerns. As would be understood by one of ordinary skill in the art having the present specification, drawings and claims before them other case management systems may be utilized within the present invention such as Salesforce (Salesforce.com, inc. of San Francisco, Calif.) and Novo (Novo Solutions, Inc. of Virginia Beach, Va.).
- Each client computer associated with the system management back end server has a network interface device, graphical user interface, and voice communication capabilities that match the voice channel(s) supported by the client care center server, such as VoIP. Each client computer can request status of both the cellular and secure transactional subsystems of a portable communication device. This status may include the contents of the soft memory and core performance of portable communication device, the NFC components: baseband, NFC antenna, secure element status and identification.
- As shown in
FIG. 2 , eachportable communication device 50 may contain one or more third party applications 200 (e.g. selected by the consumer),OpenWallet 100,payment libraries 110,secure element 120, NFC Baseband, a payment subsystem 150 (i.e.secure data store 115 and secure element 120), anddiagnostic agent 170.OpenWallet 100 is a computer application that allows the consumer to see all credentials (e.g., card, coupon, access control and ticket data) stored in the device 50 (preferably in payment subsystem 150).OpenWallet 100 would also preferably track the issuers of all the credentials stored in the portable communication device'spayment subsystem 150 and determine on an application-by-application basis whether that third party application should have permissions to view, select and/or change the credentials stored in the payment subsystem. In this manner,OpenWallet 100 also prevents unauthorized applications from accessing data stored in thepayment subsystem 150, which they do not currently have permission to access. - The
payment libraries 110 are used byOpenWallet 100 to manage (and perform housekeeping tasks on) thesecure element 120, interface with the system management back end, and perform over-the-air (OTA) provisioning via data communication transceiver (including its SMS channel), on thedevice 50. It is contemplated that the OTA data communications will be encrypted in some manner and an encryption key will be deployed incard services module 420. Thepayment subsystem 150 may be used to store credentials such as payment card, coupon, access control and ticket data (e.g. transportation, concert). Some of these payment types may be added to the payment subsystem bydifferent applications 200 for use by those applications. In this manner, other third party applications (not shown) may be precluded from accessing thepayment subsystem 150. - The
secure data store 115 provides secured storage on theportable communication device 50. Various levels of security may be provided depending upon the nature of the data intended for storage insecure data store 115. For instance,secure data store 115 may simply be password-protected at the operating system level ofdevice 50. As is known in these operating systems, the password may be a simple alphanumeric or hexadecimal code that is stored somewhere on thedevice 50. Alternatively, the data insecure data store 115 is preferably encrypted. More likely, however, thesecure data store 115 will be set up as a virtual secure element in the manner disclosed in the co-pending patent application (owned by the assignee of the present application) entitled “System and Method for Providing A Virtual Secure Element on a Portable Communication Device” filed contemporaneously herewith and hereby incorporated by reference. -
OpenWallet 100 preferably removes the complexity involved in the storage, maintenance and use of credentials such as card, coupon, ticket, access control data from one or multiple sources or issuers in association with thepayment subsystem 150.OpenWallet 100 also preferably enforces access control to the data stored in thepayment subsystem 150 and the functions allowed by each application. In one approach,OpenWallet 100 verifies the author/issuer of each third party application stored on theportable communication device 50. This verification may be accomplished by accessing a local authorization database of permitted (i.e., trusted) applications (seeFIG. 6 ). Under this approach, only applications that are signed with a known Issuer ID and the correctly associated Compile ID are allowed bycard services module 420 to access and/or manipulate data stored in thepayment subsystem 150 and/or meta data repository 125 (which stores, among other things, card image data and any embossed card data). - In other words, when an
application 200 orwallet user interface 410 needs to interact with thepayment subsystem 150 it does so by passing a digital identifier (such as its Issuer ID or App ID), a digital token (i.e., Compile ID or Secret Token ID), the desired action, and any associated arguments needed for the action to thecard services module 420.Card services module 420 verifies the digital identifier-digital token pair matches trusted application data in the secure data table (FIG. 6 ), and then would issue the one or more commands necessary to execute the desired action. Among the potential actions that may be used byapplications 200 orwallet user interface 410 are those associated with: -
- a. wallet management (e.g. setting, resetting or enabling wallet passcodes; get URL of OTA server; over-the-air registry provisioning; setting payment timing; increasing payment timing; set default card; list issuers, list supported credentials; set display sequence of credentials; set credential storage priority; create categories/folders; associate credentials with categories; memory audit; determine SE for storage of credential; get Offers; update wallet status)
- b. credential management (e.g. add credential; view credential detail; delete credential; activate credential (for redemption/payment); deactivate credential; search credentials; list credential capability; set default credential; lock/unlock credential; require passcode access; get credential image; set access passcode)
- c. Secure Element (SE) Management (e.g. get credential; update credential; update meta data; delete credential; wallet lock/unlock; SE lock/unlock)
- d. Personalization (e.g. add credential; delete credential; suspend/unsuspend credential; notification for issuer metadata update; notification for card metadata update)
-
FIG. 4 illustrates further detail of the “OpenWallet” block ofFIG. 2 . As shown, the functions of “OpenWallet” 100 can be integrated into a single dedicated module that provides a user interface that is closely coupled to the card services. In another embodiment illustrated inFIG. 4 , the capabilities and functionality ofOpenWallet 100 may be distributed between aWallet User Interface 410 and aCard Services Module 420. The distributed approach would allow applications to have direct access to theCard Services Module 420 without having to use the user interface provided byWallet User Interface 410. TheCard Services Module 420 may be configured to track the issuer of all card, coupon, access and ticket data stored in thepayment subsystem 150 of theportable communication device 50 and determine on an application-by-application basis whether an application should have permissions to view, select, use and/or change secure data stored in the payment subsystem. Thewallet user interface 410 provides a user interface through which a user may register, provision, access and/or use the information securely stored in association with thecard services module 420 relating to the user's credentials. Because thewallet user interface 410 is separated from thecard services module 420, the user may elect to use one of thethird party applications 200 to manage information in theCard Services Module 420. As further shown inFIG. 4 , metadata (such as credential logos (e.g. Amtrak®, MasterCard®, TicketMaster®, and Visa®) and affinity images (e.g. AA Advantage® and United Mileage Plus®)) may be stored inmemory 125 for use by thethird party apps 200 orwallet user interface 410 in rendering a more friendly user experience. As this metadata can be shared across applications, the storage needed to implement secured transaction may be minimized. - Various screen shots of one exemplary
wallet user interface 410 that may be deployed on a smart phone are shown inFIGS. 4A , 4B, 4C and 4D. Among other things these figures illustrate the functionality of registering, provisioning, access and/or using information securely stored in association with thecard services module 420.FIG. 4A depicts that the wallet can hold various credentials such as cards, coupons, tickets and more.FIG. 4A further depicts that multiple cards may be stored in thewallet 100. As shown inFIG. 4D , upon selecting the VISA® card from the screen illustrated inFIG. 4A , the wallet user interface opens another screen that provides an interface for the user to initiate a secure NFC payment transaction. As also depicted, the user interface may show balance and available credit information. - Credential Provisioning
-
FIG. 5 illustrates one exemplary system architecture that may be utilized to provision credentials in the system. As shown, the user'sportable communication device 50 is configured to communicate with a control server and an issuer adapter. The control server (which may alternatively be known as a Card Application Management System) is configured to validate a user's credentials. For example, if the user wishes to store information relating to a credit card in thesecure element 120 of theirmobile device 50, they would input their credit card information via a user interface displayed on theirportable device 50. - The user interface may be generated by
wallet user interface 410 or a trustedthird party application 200 supported byOpenWallet 100. As an example,FIGS. 4A and 4B , illustrate the provisioning of a “Charge-It Card” into the wallet using one exemplarywallet user interface 410 that may be deployed on a smart phone. Underlying either user interface, thecard services module 420 preferably transmits the first six digits of the identified credit card (commonly referred to as the Bank Identification Number or BIN) to the control server, which then validates the card issuer's compliance rules and facilitates a direct key exchange between the OpenWallet 100 (or Card Services Module 420) on the user'smobile device 50 and the appropriate issuer server in an encrypted fashion as was previously known in the art. - Various approaches to the direct key exchange may be facilitated by a variety of off-the-shelf solutions provided by entities including, but not limited to, Gemalto N.V. (Amsterdam, The Netherlands), Giesecke & Devrient (Munich, Germany), SK C&C (Korea)(Corefire), or VIVOtech Inc. of Santa Clara, Calif. (ViVoTech Issuer Server). The Issuer Server authenticates the user, executes issuer rules and then initiate the personalization process. The Issuer Server is preferably a server operated by the issuer of the credentials that the user is seeking to provision. The issuer server may verify the user, for example by providing a series of verification questions based on user information previously provided to the issuer (see
FIG. 4B ). Once verified, the issuer server passes the full 16 digit credit card number to thesecure element 120 via thecard services module 420. The issuer server may also pass metadata, such as information relating to the look and design of the selected credit card to theapplication memory 125. On completion, the issuer adapter would notify the control server about the completion of the transaction. As shown inFIG. 4C , following provisioning thewallet user interface 410 would include the Charge-It Card, which the user could select using user interface techniques that are well-known in the art of smart phone user interfaces. - Validating Third Party Applications
- As noted above,
OpenWallet 100 verifies the trusted status of anythird party application 200 before that application is allowed access to the secure element 120 (orsecure data store 115 and even preferably the meta data repository 125) on theportable communication device 50 to view, select and/or change secure data stored in thepayment subsystem 150. In one approach noted above, this verification may be accomplished by accessing a local authorization database of permitted or trusted applications. In a preferred approach, the local authorization database in cooperates with a remote authorization database associated with one or more servers associated with system managementback end 300. -
FIG. 6 is a block diagram of one potential implementation of one potential combination local and remote authorization databases to enhance security of thecard services module 420,secure element 120, andpayment subsystem 150. As shown inFIG. 6 , a User A/C Registry (or User Account Registry) may be associated with the server (or otherwise deployed in the cloud). The User A/C Registry may store the identification of thesecure element 120 disposed in each user'sportable device 50. Entries in the User Account Registry may be added for each user at any point in the process. - The “Issuer Registry” database is a database of approved Issuers. The Issuer ID is unique for each type of credential. In other words, if a bank has multiple types of credentials (e.g. debit cards, credit cards, affinity cards, etc.) each credential type would have its own Issuer ID (e.g. I-BofA-II). In a preferred approach, the Issuer ID as between multiple types of credentials would have some common elements, so as to indicated that the credentials are at least related (e.g. I-BofA-I). In this way applications from same issuer can share data with the other application of the same “extended” issuer. In a preferred approach,
card services module 420 can be simplified by requiring even the wallet user interface 410 (which “ships with the system”) to have an Issuer ID (and as well as an Application ID and Compile token). - The “Application Registry” is a database of applications (mostly third party) that have pre-approved by an operating system provider. Like the User A/C Registry, the “Application Registry” and “Issuer Registry” database are maintained on the server side (or otherwise in the cloud) in operable association with OpenIssuance (see
FIG. 3 ). As would be understood by those of ordinary skill in the art having the present specification before them, the various registries may be implemented in separate databases or one unified database. At initiation of awallet 100 and preferably at substantially regular time-intervals thereafter (e.g., daily), the data stored in the Application Registry of Open Issuance (see,FIG. 3 ) is distributed to devices with the wallet to be stored locally. - As shown in
FIG. 6 , the Application Registry may include, among other information, an Application ID (“App ID”), an Issuer ID, and a Compile ID or token. The Compile ID is a global constant generated for each application by one or more processes associated with Open Issuance (FIG. 3 ) during the qualification process for theparticular application 200. After it is generated by a particularcard services module 420 on aunique device 50, the Compile token is included or otherwise associated with the application. This Compile token is preferably generated by a pseudo-random number generator local to the device that uses a pre-determined seed, such as the Application ID, Compile ID, Issuer ID or some combination thereof. - When the user seeks to qualify a third party application with the
card services module 420 on adevice 50, the Compile ID (a digital token) and Application ID (a digital identifier) associated with the third party application may be matched against the Compile ID and Application ID pairs stored in the Card Services Registry stored on the device 50 (seeFIG. 6 ). As should be understood by those skilled in the art having the present specification before them, the same Compile and Application ID pairs are transmitted toother devices 50 associated with the system, as well. If the Compile ID/Application ID pair matches one of the pair-stored in the Card Services Registry on the device, a Secret Token ID is preferably generated on thedevice 50 by a pseudo-random number generator (such as the one associated with theSecure Element 120 and then stored in association with the Compile ID/Application ID pair in the Card Services Registry on thedevice 50. In some instances, the Compile ID may be pre-selected and used to seed the random number generator. It should be understood that one or more pieces of other predetermined data associated with the card services registry could be preselected as the seed instead. The card services Registry is preferably stored in secure memory (rather than thesecure element 120 becausesecure element 120 has limited real estate) and the Card Services Registry is preferably further encrypted using standard encryption techniques. The Secret Token ID is also embedded in or otherwise associated with theapplication 200 on thedevice 50 in place of the Compile ID that was distributed with the application. - After the application has been loaded into the Card Services Registry (and the secret token embedded in the application), the third party may launch and may prompt the user to opt-in to provide access to the issuer-specific credential needed for the validated (or trusted) application. In each subsequent launch of the third party trusted application, the embedded Secret Token and/or Application ID are compared to the data in the Card Services Registry on the device. If there is match, the application is trusted and can access the
payment subsystem 150 viacard services module 420. In this manner, it can be seen thatapplications 200 orwallet user interface 410 may also be removed from the Card Services Registry and thus would be disabled from accessing the payment subsystem and possibly the application, altogether. -
Card services module 420 also preferably uses the trusted application verification step to determine the appropriate level of subsystem access allowed for eachapplication 200. For example, in one embodiment, one application 200 a may be authorized to access and display all of the data contained in thepayment subsystem 150, where another third party application 200 x may be only authorized to access and display a subset of the data contained in thepayment subsystem 150. In yet another embodiment, an application may be permitted only to send a payment or transaction requests toOpenWallet 100, but may not itself be permitted to access any of the data contained in thepayment subsystem 150. In one approach, assignment of permissions to the application can be thought of as follows: -
Extended All Issuer Own Reserved Credentials Credentials Credentials Read 0 0 or 1 0 or 1 0 or 1 Write 0 0 or 1 0 or 1 0 or 1 Delete 0 0 or 1 0 or 1 0 or 1 Activate/Deactivate 0 0 or 1 0 or 1 0 or 1 Download Credential 0 0 or 1 0 or 1 0 or 1
These permission can be used to form 4 hexadecimal number in the order shown above from most to least significant figure. As shown in the example Card Services Registry ofFIG. 6 , the I-BofA-II issuer haspermission level 11111, which can be thought to expand to 0001 0001 0001 0001 0001. In other words, the I-BofA-II application can read, write, delete, activate/deactivate, and download its own credentials but not the extended issuer credentials let alone all credentials. If BofA had another issuer code (e.g. I-BofA-I), then that would be an extended Issuer application. So, if the permission level of the application associated with Issuer ID “I-BofA-II” was set to 0010 0001 0001 0010 0001 (or 21121 hexadecimal) then the application would be able to read and activate/deactivate the credentials associated with both issuer IDs. In yet another example, thewallet user interface 410 may be given a permission level of 44444 (i.e. 0100 0100 0100 0100 0100). In other words, thewallet user interface 410 can read, write, delete, activate/deactivate, and download all credentials. As would be understood by those of ordinary skill in the art, these are merely examples of potential permissions that can be granted to applications, other permissions are contemplated. For instance, some applications may have the ability to read extended issuer credentials, but only write, delete, activate and download the application's own credentials (e.g. 21111, which expands to 0010 0001 0001 0001 0001). In yet another example, an application may only be given activate/deactivate and download rights (e.g. 0000 0000 0000 0001 0001 or 00011 in hexadecimal). In yet another example, an application may be disabled—without being deleted from the trusted application database or Card Service Registry—by setting all rights to zero. - The foregoing description and drawings merely explain and illustrate the invention and the invention is not limited thereto. While the specification is described in relation to certain implementation or embodiments, many details are set forth for the purpose of illustration. Thus, the foregoing merely illustrates the principles of the invention. For example, the invention may have other specific forms without departing from its spirit or essential characteristic. The described arrangements are illustrative and not restrictive. To those skilled in the art, the invention is susceptible to additional implementations or embodiments and certain of these details described in this application may be varied considerably without departing from the basic principles of the invention. It will thus be appreciated that those skilled in the art will be able to devise various arrangements which, although not explicitly described or shown herein, embody the principles of the invention and, thus, within its scope and spirit.
Claims (15)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/250,720 US20140223510A1 (en) | 2010-11-17 | 2014-04-11 | System and method for providing diverse secure data communication permissions to trusted applications on a portable communication device |
US14/987,507 US10515352B2 (en) | 2010-11-17 | 2016-01-04 | System and method for providing diverse secure data communication permissions to trusted applications on a portable communication device |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US41484710P | 2010-11-17 | 2010-11-17 | |
US13/279,200 US20120124659A1 (en) | 2010-11-17 | 2011-10-21 | System and Method for Providing Diverse Secure Data Communication Permissions to Trusted Applications on a Portable Communication Device |
US14/250,720 US20140223510A1 (en) | 2010-11-17 | 2014-04-11 | System and method for providing diverse secure data communication permissions to trusted applications on a portable communication device |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/279,200 Continuation US20120124659A1 (en) | 2010-11-17 | 2011-10-21 | System and Method for Providing Diverse Secure Data Communication Permissions to Trusted Applications on a Portable Communication Device |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/987,507 Continuation US10515352B2 (en) | 2010-11-17 | 2016-01-04 | System and method for providing diverse secure data communication permissions to trusted applications on a portable communication device |
Publications (1)
Publication Number | Publication Date |
---|---|
US20140223510A1 true US20140223510A1 (en) | 2014-08-07 |
Family
ID=46049077
Family Applications (5)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/279,184 Active 2032-07-11 US8745716B2 (en) | 2010-11-17 | 2011-10-21 | System and method for providing secure data communication functionality to a variety of applications on a portable communication device |
US13/279,200 Abandoned US20120124659A1 (en) | 2010-11-17 | 2011-10-21 | System and Method for Providing Diverse Secure Data Communication Permissions to Trusted Applications on a Portable Communication Device |
US14/250,720 Abandoned US20140223510A1 (en) | 2010-11-17 | 2014-04-11 | System and method for providing diverse secure data communication permissions to trusted applications on a portable communication device |
US14/293,688 Active 2031-11-30 US9607298B2 (en) | 2010-11-17 | 2014-06-02 | System and method for providing secure data communication functionality to a variety of applications on a portable communication device |
US14/987,507 Active 2033-03-01 US10515352B2 (en) | 2010-11-17 | 2016-01-04 | System and method for providing diverse secure data communication permissions to trusted applications on a portable communication device |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/279,184 Active 2032-07-11 US8745716B2 (en) | 2010-11-17 | 2011-10-21 | System and method for providing secure data communication functionality to a variety of applications on a portable communication device |
US13/279,200 Abandoned US20120124659A1 (en) | 2010-11-17 | 2011-10-21 | System and Method for Providing Diverse Secure Data Communication Permissions to Trusted Applications on a Portable Communication Device |
Family Applications After (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/293,688 Active 2031-11-30 US9607298B2 (en) | 2010-11-17 | 2014-06-02 | System and method for providing secure data communication functionality to a variety of applications on a portable communication device |
US14/987,507 Active 2033-03-01 US10515352B2 (en) | 2010-11-17 | 2016-01-04 | System and method for providing diverse secure data communication permissions to trusted applications on a portable communication device |
Country Status (6)
Country | Link |
---|---|
US (5) | US8745716B2 (en) |
EP (2) | EP3438812B1 (en) |
CA (1) | CA2818541A1 (en) |
ES (1) | ES2919336T3 (en) |
PT (1) | PT2641162T (en) |
WO (1) | WO2012068290A2 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110326266A (en) * | 2017-09-18 | 2019-10-11 | 华为技术有限公司 | A kind of method and device of data processing |
Families Citing this family (67)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10045327B2 (en) * | 2007-01-17 | 2018-08-07 | Eagency, Inc. | Mobile communication device monitoring systems and methods |
US20100114768A1 (en) | 2008-10-31 | 2010-05-06 | Wachovia Corporation | Payment vehicle with on and off function |
US10867298B1 (en) | 2008-10-31 | 2020-12-15 | Wells Fargo Bank, N.A. | Payment vehicle with on and off function |
CA2775237C (en) | 2011-04-27 | 2015-07-07 | Perspecsys Inc. | System and method of sort-order preserving tokenization |
US20130054473A1 (en) * | 2011-08-23 | 2013-02-28 | Htc Corporation | Secure Payment Method, Mobile Device and Secure Payment System |
US20130067232A1 (en) * | 2011-09-09 | 2013-03-14 | Kai Chung CHEUNG | METHOD AND SYSTEM FOR CREDENTIAL MANAGEMENT AND DATA ENCRYPTION FOR iOS BASED DEVICES |
US8811895B2 (en) | 2011-10-28 | 2014-08-19 | Sequent Software Inc. | System and method for presentation of multiple NFC credentials during a single NFC transaction |
US9923986B2 (en) | 2011-12-30 | 2018-03-20 | Mozido Corfire—Korea, Ltd. | Master TSM |
US9818098B2 (en) * | 2012-03-20 | 2017-11-14 | First Data Corporation | Systems and methods for facilitating payments via a peer-to-peer protocol |
US9223961B1 (en) | 2012-04-04 | 2015-12-29 | Symantec Corporation | Systems and methods for performing security analyses of applications configured for cloud-based platforms |
US8918387B1 (en) * | 2012-04-04 | 2014-12-23 | Symantec Corporation | Systems and methods for classifying applications configured for cloud-based platforms |
US20150172925A1 (en) * | 2012-04-26 | 2015-06-18 | Tapani Antero Leppanen | Method and Apparatus for Wireless Network Access Parameter Sharing |
US9357332B2 (en) * | 2012-06-08 | 2016-05-31 | Broadcom Corporation | Near field communication application identification routing in card emulation |
US10212158B2 (en) | 2012-06-29 | 2019-02-19 | Apple Inc. | Automatic association of authentication credentials with biometrics |
US9959539B2 (en) | 2012-06-29 | 2018-05-01 | Apple Inc. | Continual authorization for secured functions |
US9143498B2 (en) | 2012-08-30 | 2015-09-22 | Aerohive Networks, Inc. | Internetwork authentication |
US10475024B1 (en) | 2012-10-15 | 2019-11-12 | Square, Inc. | Secure smart card transactions |
CA2825751A1 (en) * | 2012-11-05 | 2014-05-05 | Sequent Software Inc. | System and method for increasing security in internet transactions |
US9762679B2 (en) | 2013-03-15 | 2017-09-12 | Aerohive Networks, Inc. | Providing stateless network services |
US9769056B2 (en) | 2013-03-15 | 2017-09-19 | Aerohive Networks, Inc. | Gateway using multicast to unicast conversion |
US9317704B2 (en) * | 2013-06-12 | 2016-04-19 | Sequent Software, Inc. | System and method for initially establishing and periodically confirming trust in a software application |
US10331866B2 (en) | 2013-09-06 | 2019-06-25 | Apple Inc. | User verification for changing a setting of an electronic device |
US20150073998A1 (en) | 2013-09-09 | 2015-03-12 | Apple Inc. | Use of a Biometric Image in Online Commerce |
US9106642B1 (en) * | 2013-09-11 | 2015-08-11 | Amazon Technologies, Inc. | Synchronizing authentication sessions between applications |
KR20150032970A (en) * | 2013-09-23 | 2015-04-01 | 삼성전자주식회사 | Storage unit for offering security function and method thereof |
WO2015082946A2 (en) * | 2013-12-07 | 2015-06-11 | Vilmos András | Procedure for the remote management of secure elements and communication device for carrying out such procedure |
US10305893B2 (en) | 2013-12-27 | 2019-05-28 | Trapezoid, Inc. | System and method for hardware-based trust control management |
US9258331B2 (en) | 2013-12-27 | 2016-02-09 | Trapezoid, Inc. | System and method for hardware-based trust control management |
US20150220931A1 (en) | 2014-01-31 | 2015-08-06 | Apple Inc. | Use of a Biometric Image for Authorization |
AU2015218275B2 (en) | 2014-02-14 | 2019-05-02 | Intertrust Technologies Corporation | Network security systems and methods |
EP2950229B1 (en) * | 2014-05-28 | 2018-09-12 | Nxp B.V. | Method for facilitating transactions, computer program product and mobile device |
US10546293B2 (en) | 2014-05-29 | 2020-01-28 | Apple Inc. | Apparatuses and methods for using a random authorization number to provide enhanced security for a secure element |
US9760740B1 (en) | 2014-06-23 | 2017-09-12 | Square, Inc. | Terminal case with integrated dual reader stack |
US9344455B2 (en) * | 2014-07-30 | 2016-05-17 | Motorola Solutions, Inc. | Apparatus and method for sharing a hardware security module interface in a collaborative network |
US10108947B2 (en) * | 2014-07-31 | 2018-10-23 | Square, Inc. | Smart card reader with public key index on host device |
US10154082B2 (en) * | 2014-08-12 | 2018-12-11 | Danal Inc. | Providing customer information obtained from a carrier system to a client device |
US9992619B2 (en) | 2014-08-12 | 2018-06-05 | Aerohive Networks, Inc. | Network device based proximity beacon locating |
US9773232B1 (en) | 2014-08-20 | 2017-09-26 | Square, Inc. | Payment without account creation |
US9401912B2 (en) * | 2014-10-13 | 2016-07-26 | Netiq Corporation | Late binding authentication |
FR3028122A1 (en) * | 2014-11-05 | 2016-05-06 | Orange | SYSTEM FOR SECURING EXCHANGES BETWEEN A COMMUNICATING OBJECT AND A SERVICE PLATFORM |
US10753982B2 (en) | 2014-12-09 | 2020-08-25 | Square, Inc. | Monitoring battery health of a battery used in a device |
WO2016106277A2 (en) | 2014-12-22 | 2016-06-30 | Capital One Services, LLC. | A system, method and apparatus for reprogramming a transaction card |
US9609541B2 (en) | 2014-12-31 | 2017-03-28 | Motorola Solutions, Inc. | Method and apparatus for device collaboration via a hybrid network |
US11429975B1 (en) | 2015-03-27 | 2022-08-30 | Wells Fargo Bank, N.A. | Token management system |
WO2016182272A1 (en) * | 2015-05-08 | 2016-11-17 | Samsung Electronics Co., Ltd. | Terminal device and method for protecting information thereof |
US11170364B1 (en) | 2015-07-31 | 2021-11-09 | Wells Fargo Bank, N.A. | Connected payment card systems and methods |
US11424931B2 (en) * | 2016-01-27 | 2022-08-23 | Blackberry Limited | Trusted execution environment |
FR3051059A1 (en) * | 2016-05-09 | 2017-11-10 | Orange | METHOD AND DEVICE FOR INSTALLATION UNDER DOUBLE CONTROL OF A CONFIGURATION RULE OF A SIM-BOOKED BOARD |
US11886611B1 (en) | 2016-07-01 | 2024-01-30 | Wells Fargo Bank, N.A. | Control tower for virtual rewards currency |
US10992679B1 (en) | 2016-07-01 | 2021-04-27 | Wells Fargo Bank, N.A. | Access control tower |
US11935020B1 (en) | 2016-07-01 | 2024-03-19 | Wells Fargo Bank, N.A. | Control tower for prospective transactions |
US11386223B1 (en) | 2016-07-01 | 2022-07-12 | Wells Fargo Bank, N.A. | Access control tower |
US11615402B1 (en) * | 2016-07-01 | 2023-03-28 | Wells Fargo Bank, N.A. | Access control tower |
US10783517B2 (en) | 2016-12-30 | 2020-09-22 | Square, Inc. | Third-party access to secure hardware |
US10762495B2 (en) * | 2016-12-30 | 2020-09-01 | Square, Inc. | Third-party access to secure hardware |
CN108629186A (en) * | 2017-03-23 | 2018-10-09 | 惠尔丰(中国)信息系统有限公司 | A kind of embedded-type security applied to Android system pays POS machine and method |
US11556936B1 (en) | 2017-04-25 | 2023-01-17 | Wells Fargo Bank, N.A. | System and method for card control |
US11062388B1 (en) | 2017-07-06 | 2021-07-13 | Wells Fargo Bank, N.A | Data control tower |
US11188887B1 (en) | 2017-11-20 | 2021-11-30 | Wells Fargo Bank, N.A. | Systems and methods for payment information access management |
US11734416B2 (en) * | 2018-04-27 | 2023-08-22 | Huawei Technologies Co., Ltd. | Construct general trusted application for a plurality of applications |
US11861595B2 (en) * | 2018-12-19 | 2024-01-02 | Jpmorgan Chase Bank , N.A. | Systems and methods for generation and use of a device wallet identifier |
US11343256B2 (en) | 2019-09-05 | 2022-05-24 | The Toronto-Dominion Bank | Systems and methods for controlling third-party access of a protected data resource |
US11888972B2 (en) | 2020-02-26 | 2024-01-30 | Red Hat, Inc. | Split security for trusted execution environments |
US11630683B2 (en) | 2020-02-26 | 2023-04-18 | Red Hat, Inc. | Low latency launch for trusted execution environments |
US11620411B2 (en) | 2020-03-24 | 2023-04-04 | Red Hat, Inc. | Elastic launch for trusted execution environments |
US10992606B1 (en) | 2020-09-04 | 2021-04-27 | Wells Fargo Bank, N.A. | Synchronous interfacing with unaffiliated networked systems to alter functionality of sets of electronic assets |
US11546338B1 (en) | 2021-01-05 | 2023-01-03 | Wells Fargo Bank, N.A. | Digital account controls portal and protocols for federated and non-federated systems and devices |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060165060A1 (en) * | 2005-01-21 | 2006-07-27 | Robin Dua | Method and apparatus for managing credentials through a wireless network |
US20110087610A1 (en) * | 2009-10-13 | 2011-04-14 | Asif Batada | Global secure service provider directory |
Family Cites Families (40)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3053527B2 (en) | 1993-07-30 | 2000-06-19 | インターナショナル・ビジネス・マシーンズ・コーポレイション | Method and apparatus for validating a password, method and apparatus for generating and preliminary validating a password, method and apparatus for controlling access to resources using an authentication code |
US6298440B1 (en) | 1994-04-22 | 2001-10-02 | Microsoft Corporation | Method and system for providing multiple entry point code resources |
US6330670B1 (en) | 1998-10-26 | 2001-12-11 | Microsoft Corporation | Digital rights management operating system |
US6470450B1 (en) * | 1998-12-23 | 2002-10-22 | Entrust Technologies Limited | Method and apparatus for controlling application access to limited access based data |
US7953671B2 (en) | 1999-08-31 | 2011-05-31 | American Express Travel Related Services Company, Inc. | Methods and apparatus for conducting electronic transactions |
EP1277162A4 (en) | 2000-02-18 | 2008-02-20 | Vasco Data Security Inc | Field programmable smart card terminal and token device |
US20030037237A1 (en) | 2001-04-09 | 2003-02-20 | Jean-Paul Abgrall | Systems and methods for computer device authentication |
US20040143550A1 (en) | 2002-12-19 | 2004-07-22 | International Business Machines Corporation | Cellular electronic wallet device and method |
US7761374B2 (en) | 2003-08-18 | 2010-07-20 | Visa International Service Association | Method and system for generating a dynamic verification value |
US7165727B2 (en) * | 2004-02-24 | 2007-01-23 | Sun Microsystems, Inc. | Method and apparatus for installing an application onto a smart card |
US7140549B2 (en) | 2004-02-24 | 2006-11-28 | Sun Microsystems, Inc. | Method and apparatus for selecting a desired application on a smart card |
US7014107B2 (en) * | 2004-07-20 | 2006-03-21 | Irek Singer | Wireless payment processing system |
US7665667B2 (en) | 2004-10-09 | 2010-02-23 | Gemalto Inc. | System and method for updating access control mechanisms |
US8639629B1 (en) | 2005-02-02 | 2014-01-28 | Nexus Payments, LLC | System and method for accessing an online user account registry via a thin-client unique user code |
TWI283122B (en) | 2005-11-29 | 2007-06-21 | Benq Corp | Method for securing a near field communication device of a mobile phone |
US8352323B2 (en) | 2007-11-30 | 2013-01-08 | Blaze Mobile, Inc. | Conducting an online payment transaction using an NFC enabled mobile communication device |
US20070192840A1 (en) | 2006-02-10 | 2007-08-16 | Lauri Pesonen | Mobile communication terminal |
US7907896B2 (en) | 2006-04-28 | 2011-03-15 | Motorola Mobility, Inc. | Mobile commerce method and device |
EP2060101B1 (en) * | 2006-09-07 | 2018-02-07 | Nokia Technologies Oy | Managing information relating to secure module applications |
US8225093B2 (en) * | 2006-12-05 | 2012-07-17 | Qualcomm Incorporated | Providing secure inter-application communication for a mobile operating environment |
US20080162353A1 (en) * | 2006-12-27 | 2008-07-03 | Spansion Llc | Personal digital rights management agent-server |
US8370913B2 (en) | 2007-03-16 | 2013-02-05 | Apple Inc. | Policy-based auditing of identity credential disclosure by a secure token service |
US8667285B2 (en) | 2007-05-31 | 2014-03-04 | Vasco Data Security, Inc. | Remote authentication and transaction signatures |
JP4403433B2 (en) | 2007-08-23 | 2010-01-27 | ソニー株式会社 | Electronic wallet device, communication method and program |
US8887270B2 (en) | 2007-11-12 | 2014-11-11 | Micron Technology, Inc. | Smart storage device |
US20090198618A1 (en) | 2008-01-15 | 2009-08-06 | Yuen Wah Eva Chan | Device and method for loading managing and using smartcard authentication token and digital certificates in e-commerce |
US8060413B2 (en) | 2008-03-14 | 2011-11-15 | Research In Motion Limited | System and method for making electronic payments from a wireless mobile device |
AU2009249272B2 (en) | 2008-05-18 | 2014-11-20 | Google Llc | Secured electronic transaction system |
WO2010011055A2 (en) | 2008-07-20 | 2010-01-28 | Samsung Electronics Co., Ltd. | Method and system for managing multiple applications in near field communication |
EP2324445B1 (en) | 2008-08-20 | 2019-03-20 | Xcard Holdings, LLC | Secure smart card system |
US20100153721A1 (en) | 2008-12-12 | 2010-06-17 | Anders Mellqvist | Portable Electronic Devices, Systems, Methods and Computer Program Products for Accessing Remote Secure Elements |
US9325721B2 (en) * | 2009-03-23 | 2016-04-26 | International Business Machines Corporation | Restricting access to objects created by privileged commands |
US9135424B2 (en) | 2009-05-29 | 2015-09-15 | Paypal, Inc. | Secure identity binding (SIB) |
US8484728B2 (en) * | 2009-06-03 | 2013-07-09 | Apple Inc. | Managing securely installed applications |
US20110313870A1 (en) | 2009-10-13 | 2011-12-22 | Skycore LLC, | Initiating and Enabling Secure Contactless Transactions and Services with a Mobile Device |
WO2011084963A2 (en) | 2010-01-05 | 2011-07-14 | Iota, Inc. | Mobile communications resource management system |
US9009790B2 (en) * | 2010-09-11 | 2015-04-14 | At&T Intellectual Property I, L.P. | Association of multiple public user identifiers to disparate applications in an end-user's device |
US20120095852A1 (en) | 2010-10-15 | 2012-04-19 | John Bauer | Method and system for electronic wallet access |
US8533796B1 (en) | 2011-03-16 | 2013-09-10 | Google Inc. | Providing application programs with access to secured resources |
US9955348B2 (en) * | 2012-09-12 | 2018-04-24 | Lg Electronics Inc. | Method and device for requesting for specific right acquisition on specific resource in wireless communication system |
-
2011
- 2011-10-21 US US13/279,184 patent/US8745716B2/en active Active
- 2011-10-21 US US13/279,200 patent/US20120124659A1/en not_active Abandoned
- 2011-11-16 PT PT11841802T patent/PT2641162T/en unknown
- 2011-11-16 EP EP18189625.9A patent/EP3438812B1/en active Active
- 2011-11-16 EP EP11841802.9A patent/EP2641162B1/en active Active
- 2011-11-16 ES ES18189625T patent/ES2919336T3/en active Active
- 2011-11-16 WO PCT/US2011/061050 patent/WO2012068290A2/en active Application Filing
- 2011-11-16 CA CA2818541A patent/CA2818541A1/en not_active Abandoned
-
2014
- 2014-04-11 US US14/250,720 patent/US20140223510A1/en not_active Abandoned
- 2014-06-02 US US14/293,688 patent/US9607298B2/en active Active
-
2016
- 2016-01-04 US US14/987,507 patent/US10515352B2/en active Active
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060165060A1 (en) * | 2005-01-21 | 2006-07-27 | Robin Dua | Method and apparatus for managing credentials through a wireless network |
US20110087610A1 (en) * | 2009-10-13 | 2011-04-14 | Asif Batada | Global secure service provider directory |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110326266A (en) * | 2017-09-18 | 2019-10-11 | 华为技术有限公司 | A kind of method and device of data processing |
US11552807B2 (en) | 2017-09-18 | 2023-01-10 | Huawei Technologies Co., Ltd. | Data processing method and apparatus |
Also Published As
Publication number | Publication date |
---|---|
US20120124659A1 (en) | 2012-05-17 |
EP3438812B1 (en) | 2022-05-04 |
EP3438812A1 (en) | 2019-02-06 |
CA2818541A1 (en) | 2012-05-24 |
EP2641162B1 (en) | 2018-08-29 |
US8745716B2 (en) | 2014-06-03 |
US20140289119A1 (en) | 2014-09-25 |
PT2641162T (en) | 2018-12-05 |
WO2012068290A3 (en) | 2013-05-30 |
US20160224961A1 (en) | 2016-08-04 |
US10515352B2 (en) | 2019-12-24 |
ES2919336T3 (en) | 2022-07-26 |
US20120124658A1 (en) | 2012-05-17 |
EP2641162A4 (en) | 2014-08-06 |
WO2012068290A2 (en) | 2012-05-24 |
US9607298B2 (en) | 2017-03-28 |
EP2641162A2 (en) | 2013-09-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10515352B2 (en) | System and method for providing diverse secure data communication permissions to trusted applications on a portable communication device | |
US20220358484A1 (en) | System and Method for Dynamic Temporary Payment Authorization in a Portable Communication Device | |
US10496832B2 (en) | System and method for initially establishing and periodically confirming trust in a software application | |
US20120123868A1 (en) | System and Method for Physical-World Based Dynamic Contactless Data Emulation in a Portable Communication Device | |
US20180174131A1 (en) | System and method for one-time payment authorization in a portable communication device | |
US20120159612A1 (en) | System for Storing One or More Passwords in a Secure Element | |
US9123041B2 (en) | System and method for presentation of multiple NFC credentials during a single NFC transaction | |
AU2014360806A1 (en) | System and method for dynamic temporary payment authorization in a portable communication device | |
WO2013130651A2 (en) | System for storing one or more passwords in a secure element |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: COMERICA BANK, MICHIGAN Free format text: SECURITY INTEREST;ASSIGNOR:SEQUENT SOFTWARE LLC;REEL/FRAME:034477/0111 Effective date: 20130212 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: SEQUENT SOFTWARE INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:COMERICA BANK;REEL/FRAME:049437/0802 Effective date: 20190611 |
|
AS | Assignment |
Owner name: TIS INC., JAPAN Free format text: SECURITY INTEREST;ASSIGNORS:SEQUENT SOFTWARE INC.;GFA WORLDWIDE, INC.;REEL/FRAME:049623/0638 Effective date: 20190626 |
|
AS | Assignment |
Owner name: TIS INC., JAPAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SEQUENT SOFTWARE, INC.;REEL/FRAME:064105/0348 Effective date: 20230329 |