CA3027034A1

CA3027034A1 - Personal point of sale

Info

Publication number: CA3027034A1
Application number: CA3027034A
Authority: CA
Inventors: Malcolm LYNE; David L. Dekozan; Kay Paetzold
Original assignee: Cubic Corp
Current assignee: Cubic Corp
Priority date: 2016-06-28
Filing date: 2017-05-30
Publication date: 2018-01-04
Also published as: WO2018004925A1; AU2017289738A1; EP3475902A1

Abstract

Embodiments provided herein include techniques for enabling a mobile device to communicate with smart media in a manner that can sidestep the secure element of the mobile deviceand the costs associated with it. The mobile device can communicate with the smart media using near-field communication (NFC) by creating an encrypted connection with a remote computer while bypassing a secure element of the mobile device. This allows the mobile device to provide point-of-sale (POS) functionality by reading and/or writing to the smart media, without compromising the security of the smart media. Embodiments may further enable the server to provide authentication information to a third party based on the communication between the smart media and the server.

Description

PERSONAL POINT OF SALE
BACKGROUND
[0001] Many mobile devices are natively equipped to communicate using Near-Field Communication (NFC). Other mobile devices may become NFC-enabled with the use of accessories, such as a sleeve, dongle, and the like. Such NFC-enabled mobile devices may further come with a secure element with which the mobile device may utilize encrypted communications, enabling the mobile device to read smart cards, radio-frequency identification (RFID) tags, and other smart media, and/or replace them altogether.

[0002] The use of the secure element in this manner, however, typically is not free. There can be costs related to encrypted channels, licensed technologies, and other features of the secure element. These costs can ultimately prevent a user from utilizing the NFC
functionality of a mobile device that takes advantage of the secure element in this manner.
BRIEF SUMMARY

[0003] Embodiments provided herein include techniques for enabling a mobile device to communicate with a smart media in a manner that can sidestep the secure element of the mobile device--and the costs associated with it. The mobile device can communicate with the smart media using near-field communication (NFC) by creating an encrypted connection with a remote computer while bypassing a secure element of the mobile device. This allows the mobile device to provide point-of-sale (POS) functionality by reading and writing to the smart media, without compromising the security of the smart media.

[0004] An example method for enabling a mobile device to communicate with a smart media, according to the disclosure, includes providing a user interface with the mobile device where the user interface operable to receive user input, receiving, with the mobile device, the user input, and reading information from the smart media with the mobile device. The method also includes establishing a secure communications link between the mobile device and a remote computer.
Establishing the secure communications link can include providing at least a portion of the information from the smart media. The method further includes receiving encrypted data from the remote computer via the secure communications link, and communicating the encrypted data to the smart media.

5 [0005] The example method for enabling the mobile device to communicate with the smart media can also include one or more of the following features. Communicating the encrypted data to the smart media can include writing the encrypted data without using a secure element of the mobile device. Communicating the encrypted data to the smart media can include communicating with the smart media wirelessly using Near-Field Communications (NFC).
Reading the information from the smart media can be based on the user input.
The smart media can include at least one of a contactless smart card, a credit card, a debit card, or a radio-frequency identification (RFID) tag. The smart media can be physically attached to the mobile device. The smart media can be adhesively coupled with the mobile device.
Communicating the encrypted data to the smart media can include changing a value stored in a memory of the smart media. The value can be used to track usage related to a transit system.
Providing the at least a portion of the information from the smart media can include providing an identifier of the smart media. The user input can include at least one of login information, payment source information, payment amount information, or an indication of a product or service for purchase.
.. [0006] An example non-transitory computer-readable medium having instructions embedded thereon enabling a mobile device to communicate with a smart media, according to the disclosure, can include instructions with computer-executable code for providing a user interface with the mobile device where the user interface is operable to receive user input, receiving the user input, reading information from the smart media, and establishing a secure communications link between the mobile device and a remote computer. Establishing the secure communications link can include providing at least a portion of the information from the smart media. The instructions can also include computer-executable code for receiving encrypted data from the remote computer, and communicating the encrypted data to the smart media.
[0007] The example non-transitory computer-readable medium can also include one or more of the following features. Code for communicating the encrypted data to the smart media can include code for writing the encrypted data without using a secure element of the mobile device.
The smart media can comprise at least one of a contactless smart card, a credit card, a debit card, or a radio-frequency identification (RFID) tag. The computer-executable code for providing the user interface can include computer-executable code for displaying a graphical user interface on a display of the mobile device. Providing the at least a portion of the information from the smart media can include providing an identifier of the smart media. The computer-executable code for receiving the user input can include computer-executable code for receiving at least one of login information, payment source information, payment amount information, or a product or service for purchase.
[0008] Another example method for enabling a mobile device to communicate with a smart media, according to the disclosure, can include receiving, from a mobile device, identifying information regarding the smart media, determining, with a computer, an encryption key based on the identifying information, and establishing a secure communications link between the computer and a mobile device. The secure communications link can be established, based on at least a portion of information read from the smart media by the mobile device.
The method can also include communicating encrypted data to the mobile device, via the secure communications link, to be written on the smart media.
[0009] The example method for enabling the mobile device to communicate with the smart media can include one or more of the following features. Determining the encryption key can include communicating with an external encryption engine. Encrypted data can include a value used to track usage related to a transit system. The encrypted data can include an indication that a ticket related to the smart media is no longer valid. The method can further include receiving, from the mobile device at least one of login information, payment source information, payment amount information, or an indication of a product or service for purchase. The method can also include identifying a user account related to either or both of the smart media or the mobile device.
[0010] Numerous benefits are achieved over conventional techniques. For example, a user can update smart media using a personal mobile device, without the need to visit a specialized terminal or user services counter. By bypassing the secure element and utilizing smart media, techniques disclosed can help users avoid costs associated with the secure element. Moreover, certain smart media, such as stickers, can be coupled directly to the mobile device, providing essentially the same functionality as the secure element, without incurring the costs. Allowing individual users to reload their own smart media also allows a distributor or transit agency to reduce the cost of maintaining its own distribution network. These and other embodiments, along with many of its advantages and features, are described in more detail in conjunction with the text below and attached figures.

BRIEF DESCRIPTION OF THE DRAWINGS
[0011] A further understanding of the nature and advantages of various embodiments may be realized by reference to the following figures. In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If only the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label.
[0012] FIGS. 1A and 1B are simplified hardware block diagrams of embodiments of a system for enabling a mobile device to communicate with smart media.
[0013] FIG. 2 is a simplified software block diagram a system for enabling a mobile device to communicate with the smart media, according to one embodiment in a transit system context.
[0014] FIG. 3 is a flowchart representing a method for enabling a mobile device to communicate data to be written on a smart media, such as a contactless smart card, according to one embodiment.
[0015] FIG. 4 is a flowchart representing a method for method for enabling a mobile device to communicate with a smart media, which can be performed by a computer, according to one embodiment.
[0016] FIG. 5 simplified block diagram providing an illustration of how authenticating the smart media (and/or the holder of the smart media) for non-transit applications can be done using components described herein, according to one embodiment.
[0017] FIG. 6 is a flow diagram illustrating a method for enabling an electronic device to communicate with a smart media, according to one embodiment.
DETAILED DESCRIPTION
[0018] For the purposes of explanation, the ensuing numerous provides specific details are set forth in order to provide a thorough understanding of various embodiments. It will be apparent, however, to one skilled in the art that various embodiments may be practiced without some of these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments. In other instances, well-known structures and devices are shown in block diagram form.
[0019] Embodiments provided herein include techniques for enabling a mobile device such as mobile phones, smart phones, tablet computers, personal media players, laptop computers, and other portable electronic devices, to securely communicate with smart media including, but not limited to, smart cards radio-frequency identification (RFID) tags, credit cards, debit cards, tickets, and the like. The smart media¨in any physical form (card, ticket, RFID, etc.)¨can include a memory with information such as a unique identifier (e.g., card number, serial number, etc.) and/or other information such as an electronic purse (cash), one or more products (e.g., passes), an origin and/or destination, validity parameters, and/or individual tickets, depending on the application in which the smart media is used (transit, transportation, event ticketing, etc.).
The mobile device can communicate with the smart media using near-field communication (NFC) by creating an encrypted connection with a remote computer while bypassing a secure element of the mobile device. This allows the mobile device to read and write to the smart media using standard protocols (e.g., ISO 14443) and Internet connectivity via standard networks (e.g. Wi-Fi 802.11, 3G, 4G, and the like), without compromising the security of the smart media.
[0020] In some embodiments, the ability to read and/or write to smart media can include formatting and/or initializing the smart media. For example, using the techniques described herein below to read and/or write to the smart media, a mobile device may be utilized to initialize a smart media for use. In so doing, the smart media may be formatted, and encryption keys may be written to the smart media. Such functionality can facilitate the distribution of such smart media because the smart media would not have to be pre-encoded prior to delivery. Moreover, such encoding could help ensure the smart media receives the most recent formatting and/or security key(s).
[0021] Because techniques provided herein enable a mobile device to read from and write to smart media, the mobile device to function as a personal point-of-sale (POS) device to a user.
The POS device can conduct point-of-sale transactions such as the sale of a product or service, ticket validation (e.g., debit a value from the smart media and/or cancel a ticket), and the like.
For example, a user may use the mobile device to both purchase a product and update the smart media accordingly to reflect the purchase.

[0022] FIG. lA is a simplified hardware block diagram of a first embodiment 100-1 of a system for enabling a mobile device 120-1 to communicate with the smart media.
In this embodiment, the mobile device 120-1 utilizes native NFC capabilities to read and write to a contactless smart card 105 (or other smart media). It will be understood that the first embodiment 100-1 is provided as an example. Other embodiments of an IC 100 may include more, less, and/or different components, depending on desired functionality.
[0023] In this first embodiment 100-1, the mobile device 120-1 can include an NFC
transceiver with modulation 126 and demodulation 128 circuitry enabling the mobile device 120-1 to establish a contactless communication link 117 with a contactless smart card 105 via an NFC antenna 122. The contactless smart card 105 (and/or other smart media) can include an antenna loop 115 and circuitry 112 to store information and communicate via contactless communication link 117. In some embodiments, the contactless smart card 105 and/or other smart media can communicate using ISO 14443 standards, and may be induction and/or battery powered.
[0024] The mobile device 120-1 also can include a secure element 130. In certain applications, the secure element 130 can be utilized to emulate cards, RFID
tags, and/or other smart media with card emulation 133, communicating information via the NFC
transceiver 125.
The secure element 130 can offer encrypted communications and secure channels to help keep sensitive information (e.g., credit card and/or other account information, personal data, etc.) from being compromised. However, as indicated above, it can cost a user to utilize the secure element in this manner. Thus, embodiments can bypass the secure element 130 to allow a user to use a contactless smart card 105 (and/or other smart media) and avoid the costs associated with the secure element 130. As described in more detail below, communication with the smart media can still be encrypted by, for example, a central computer host 175, in which case the mobile device 120-1 can simply relay encrypted information between the contactless smart card 105 and the central computer host 175. That said, some embodiments may utilize the secure element 130.
[0025] In this first embodiment 100-1, the mobile device 120-1 includes other components, such as a central processing unit (CPU) 140, input device(s) 135, and subscriber identity module (SIM) card 145. Among other things, the SIM card 145 can be used to identify the mobile device 120-1 and/or a related user to the central computer host 175. Input device(s) 135 can be utilized to enable a user to provide input in any of a variety of ways. For example, the input

6 device(s) 135 can include a touch screen, button(s), microphone, camera, and the like. In some embodiments, depending on the model of the mobile device 120-1 and mobile carrier network 160, the secure element 130 may be present as either embedded in the mobile phone hardware and/or firmware, embedded in the subscriber identity module (SIM) card 145, and/or included in a separate form factor, such as micro SD card.
[0026] The CPU 140 can be used to process information and coordinate the functionality of the various components of the mobile device 120-1. The CPU 140 can include one or more general-purpose processors and/or one or more special-purpose processors (such as digital signal processing chips, graphics acceleration processors, microprocessors, and/or the like). The CPU
may be configured to execute one or more computer programs stored, for example, on a computer-readable storage medium (not shown), or memory, such as a disk drive, a drive array, an optical storage device, a solid-state storage device, such as a random access memory ("RAM"), and/or a read-only memory ("ROM"), which can be programmable, flash-updateable, and/or the like. Such storage devices may be configured to implement any appropriate data stores, including without limitation, various file systems, database structures, and/or the like.
Moreover, the computer-readable storage medium can be removable, incorporated into the mobile device 120-1, and/or communicatively coupled with the mobile device 120-1 via a communication interface.
[0027] The mobile device 120-1 can communicate with one or more communication networks via one or more antenna(s) 150. Such communication networks can include a mobile carrier network (e.g., cell phone service via cell phone tower 155), the Internet 170 (via Wi-Fi access point 165), and/or other networks. In the first embodiment 100-1 of FIG. 1A, the mobile device is able to gain access to the Internet 170 via either or both of a Wi-Fi access point 165 or a mobile carrier network 160. The Internet 170, in turn, provides the mobile device 120-1 access to the central computer host 175. In other embodiments, other forms of wireless and/or wired communication can be utilized, depending on desired functionality.
[0028] The central computer host 175 can comprise one or more computers configured to manage and/or update smart media, such as the contactless smart card 105. To this end, it can manage and/or access one or more encryption key(s) associated with each smart media. In some embodiments, such as the first embodiment 100-1 of FIG. 1A, encryption keys may be stored

7 externally in an encryption engine 180 such as a separate computer and/or a specialized encryption hardware.
[0029] In this first embodiment 100-1, the contactless smart card 105 can be written to as follows. A user may bring contactless smart card 105 within a range of the mobile device 120-1 sufficient to activate the contactless smart card 105 and start an initial communication between the mobile device 120-1 and the contactless smart card 105. The user may activate a software application executed by the mobile device 120-1 before doing so. The software application can, for example, enable a user to perform various point-of-sale transactions such as load value to the electronic purse, purchase a product and/or validate a ticket, deliver an electronic benefit (e.g., debit a card and/or inactivate or cancel a ticket, inactivate and/or cancel the card, deliver a monthly employer transit benefit, etc.), in which data of the contactless smart card 105 is to be updated accordingly. In some embodiments, the software application can perform functions that do not necessarily result in updating a value on the card. For example, the software application can perform enforcement actions in which a value and/or other information is read from a card to ensure fare compliance. To complete a transaction involving reading and/or writing to the contactless smart card 105, the software application can prompt the user to bring contactless smart card 105 within a range of the mobile device 120-1 (e.g., tap the contactless smart card 105 to the mobile device 120-1).
[0030] During the initial communication, the mobile device 120-1 can read certain unsecure information from the contactless smart card 105, such as a serial, card, and/or account number; a name of a user associated with the contactless smart card 105; and the like.
The mobile device 120-1 then can connect with the central computer host 175 via the Internet 170, using a data connection provided by the mobile carrier network 160, Wi-Fi access point 165, and/or another communication means with the Internet. In some embodiments, the user may input identifying information (e.g., login ID, password, etc.) using input device(s) 135, which can be used to establish an authenticated connection with the central computer host 175.
[0031] Using the serial number and/or other information provided by the mobile device 120-1, the central computer host can then establish a secure communications link with the mobile device. Information communicated via the secure communications link can be encrypted using one or more encryption keys associated with the contactless smart card 105.
The encryption may

8 take place in the central computer host using locally stored keys 175 and/or take place in the external encryption engine 180.
[0032] The encrypted information from the central computer host 175 can be sent to the contactless smart card 105 and used to update secure information of the contactless smart card 105. The mobile device 120-1 may not have encryption keys to decrypt the encrypted information. Instead the mobile device 120-1 can write to the contactless smart card by transparently passing the encrypted information along to the contactless smart card, bypassing the secure element 130 and simply modulating the encrypted information with the NFC
transceiver 125 in accordance with related NFC protocols. The contactless smart card 105 can then update secure information stored in memory using the encrypted information. The contactless smart card 105 can then communicate to the mobile device 120-1 and/or central computer host 175 using encrypted and/or non-encrypted data to indicate whether the memory has been successfully (or unsuccessfully) updated.
[0033] FIG. 1B is a simplified hardware block diagram of a second embodiment 100-2 of a system for enabling a mobile device 120-1 to communicate with the smart media.
The second embodiment 100-2 of FIG. 1B is similar to the first embodiment 100-1 of FIG.
1A. Here, however, a second mobile device 120-2 without native NFC capability is used.
Instead, the mobile device 120-2 is given NFC capabilities by an external NFC module 190, such as a mobile device sleeve or dongle, which includes some or all of the NFC-related components.
[0034] The mobile device 120-2 and external NFC module 190 can be communicatively coupled using respective input/output (I/0) connectors 193. The mobile device's I/O connector 193-2 can include a generic or specialized interface, such as a serial port, mini universal serial port (USB), parallel port, and the like, and the external NFC module's I/O
connector 193-1 can include a port configured to communicate with the mobile device's I/0 connector 193-2.
[0035] It will be understood that the embodiments provided in FIGS. 1A and 1B, as well as other embodiments detailed herein, are provided as non-limiting examples, that may not include every component for each embodiment. The external NFC module, for example, may include a processing unit, memory, and/or other subcomponents. The contactless smart card 105 can be replaced with any of a variety of smart media, including credit and/or debit cards, RFID tags, and the like. Moreover, the smart media may be physically attached to the mobile device 120 and/or external NFC module 190 (e.g., as a sticker or other item adhesively coupled to the mobile

9 device). The central computer host 175 and/or encryption engine 180 may be a cloud-based and/or networked system of computers. Embodiments may also include using card emulation 133 in addition or as an alternative to smart media, and/or the user of an external card reader in addition or as an alternative to the external NFC module 190. A person of ordinary skill in the art will recognize many additions, substitutions, and other variations.
[0036] FIG. 2 is a simplified software block diagram a system 200 for enabling a mobile device to communicate with the smart media, according to one embodiment in a transit system context. That said, the components depicted in FIG. 2 may be implemented in a variety of combinations of hardware and software, some of which (such as the contactless smart card 210, mobile device 220, and central computer 250) may correspond with components depicted in FIGS. 1A and/or 1B. As with other figures provided herein, the system 200 shown in FIG. 2 is provided as a non-limiting example.
[0037] In this system 200, the contactless smart card 210 can include an RF
interface 203, controller 207, memory controller 205 memory 215, and encryption engine 213.
The encryption engine 213 can store, generate, and/or manage one or more encryption key(s) to help ensure sensitive information stored in memory 215 is not communicated via the RF
interface 203 without proper encryption. The memory can store information such as a value, counter, product, and the like, that may be used in one or more of a variety of applications, such as transit fare, event ticketing, payment systems, etc. Different blocks of memory may be encrypted with different keys and have different access conditions. Furthermore, components of the contactless smart card 210 can further ensure that only authorized entities are provided read and/or write access to memory 215.
[0038] Mobile device 220 can include memory 227, communication interface 225, point-of-sale (POS) application 235, secure device identification 237, and user interface 238, each of which can communicate with, be integrated into, and/or be managed by mobile operating system (OS) 230. In some embodiments, such as those in which an external NFC module 270 is not utilized, the mobile device can include an RF interface 223. The mobile OS 230 and/or other applications can be stored in memory 227 and executed by the mobile device, for example, upon device startup or upon receiving certain user input and/or detecting other triggering events.
[0039] The POS application 235 can be an application executed by the mobile device 220 with which the user may initiate various point-of-sale functions related to the contactless smart card 210. In a transit context, for example, such functions can include purchasing a new product or service (e.g., a 20-ride pass, month-long pass, etc.) and/or validating a ticket (e.g., debiting a card and canceling a ticket). The POS application 235 can be evoked by user input (e.g., pressing a link of a user interface 238 shown on a touchscreen display of the mobile device 220) and/or when the mobile device 220 detects the contactless smart card 210. The POS
application 235 also can receive input, such as a login ID, password, and/or other identifier, to send to a central computer 250, which may be used to identify a user and/or establish a secure connection between the mobile device 220 and the central computer 250.
[0040] The operation of POS application 235 may vary, depending on desired functionality.
For example, a user may execute the POS application 235 on a personal mobile device 220 to initiate point-of-sale functions related to a contactless smart card 210.
Additionally or alternatively, the POS application 235 may be used by an agent and/or vender to initiate point-of-sale functions related to the contactless smart card 210 of a customer. In either case, and in other scenarios, the secure device identification 237 (which can be related to a SIM
card 145 of FIGS.
1A and 1B) can identify the mobile device 220 to the back-end system 240 for tracking and/or login purposes. In some embodiments, the POS application 235 can be a client program that communicatively connects with a server program executed by the central computer 250. In some embodiments, the POS application may be a browser-based program that enables users to initiate point-of-sale functions via a web portal.
[0041] The RF interface 223 of the mobile device 220 can include an NFC
transceiver and/or antenna that enables the mobile device 220 to communicate with the contactless smart card 210.
Additionally or alternatively, as shown in FIG. 1B, NFC and/or other wireless functionality may be provided by an external NFC module 270. In embodiments in which an external NFC module 270 is utilized, the mobile device 220 can include an external NFC module library 239, enabling the mobile operating system 230 to communicate with and/or manage any of a variety of external NFC modules 270, which can be manufactured by third parties. The external NFC
module library 239 can communicate with the external NFC module via an I/O expansion module 233 of the mobile device 220.
[0042] In addition to the central computer 250, the back-end system 240 can include a variety of additional components, depending on desired functionality. Components can include an external encryption engine 245 (which may have a master key, as indicated), one or more terminal computer(s) 247, connection to a banking system 253, and fare collection software 260 that communicates with a user database and hotlists 263, fare tables 265, and/or card database 267. Terminal computer(s) 247 can be any of a variety of machines or devices (computers, vending machines, etc.) that can provide point-of-sale and/or other functionality related to the .. transit system. As discussed earlier, components shown in FIG. 2 may be utilized in a transit system, but components may vary depending on application. A person having ordinary skill in the art will recognize many substitutions, alterations, and variations.
[0043] The mobile device 220 can communicate with the back-end system 240 via respective communication interfaces 225 and 243. As indicated previously, the central computer 250 can utilize information from the mobile device 220 to identify the mobile device 220 and/or a user associated with the mobile device 220. For example, a transit system may be an account-based system in which users can create accounts that are maintained by fare collection software 260 and stored in the user database and hotlists 263. An account-based system can enable the transit system to store payment information (e.g., credit card information, bank account, transit benefit account) associated with a user in the card database 267 and/or user database and hotlists 263.
In this manner, the mobile device 220 may not need to communicate payment information to the central computer 250. Rather, the central computer 250 can use payment information stored in the card database 267 and associated with a user in the user database and hotlists 263 and/or user database and hotlists 263 to pay for a product or service requested by a user using the mobile device 220.
[0044] The back-end system can process payments by utilizing a connection to a banking system 253. Payments may be processed periodically in batches, or may be processed in real- or near-real time. Moreover, the central computer 250 can communicate information to the mobile device 220 indicating whether a payment was successfully made. Depending on the product or service requested by a user via the mobile device 220, the central computer 250 can gather information from the fare tables 265 (e.g., to calculate a fare) and/or card database (e.g., to verify and/or authenticate a contactless smart card) via the fare collection software 260 to calculate an amount of payment and/or a value to add, deduct, or write to the contactless smart card 210.
[0045] What is written to the contactless smart card 210 can vary, depending on desired functionality. For example, in addition or as an alternative to the account-based system described above, the system can provide for writing one or more secure token(s) to the contactless smart card 210 (or other smart media) without requiring the need for separate fare payment. With regards to bank cards, such as credit and/or debit cards, this information may be written to a scratch pad (i.e., unused portion of memory) of the bank card, thereby enabling the bank card to be utilized as a fare token, ticket, and/or other media, depending on the application.
[0046] FIG. 3 is a flowchart representing a method 300 for enabling a mobile device to communicate data to a smart media, such as a contactless smart card, according to one embodiment. The method, which can be executed by the mobile device, can begin at block 310, where a user interface is provided, where the user interface is operable to receive a user input.
As discussed previously, the user interface can include a graphical user interface on a display of the mobile device. User input may be received in any of a variety of ways, depending on desired functionality and hardware capabilities of the device. For example, user input can be received via buttons, a keypad, touchscreen, microphone, camera, motion sensors, and the like.
[0047] At block 320, the user input is received. User input can include any of a variety of information, such as login information, payment source information (e.g., credit card information, debit card information, etc.), payment amount information, an indication of a product or service for purchase, and the like. The user input may also indicate and/or depend on a desired point-of-sale transaction the user wishes to make on the mobile device.
[0048] At block 330, information is read from the smart media. The information read from the smart media can include a card number, serial number, and/or other identifier, which may be used to help identify the smart media to a central computer. The information read from the smart media may be data that is not encrypted and/or secured, and therefore accessible to the mobile device without the user of encryption keys. The information read from the card may also depend on the input received from the user. For example, an indication that a certain point-of-sale transaction is desired may cause the mobile device to read a serial number from the smart media to provide to a central computer.
[0049] At block 340, at least a portion of the information is provided to establish a secure communication link with a remote computer. For example, the mobile device may provide a unique manufacturer serial number or other identifier of the smart media to a remote computer.
The remote computer can then use a card database, encryption engine, and/or the like to determine one or more encryption key(s) to use to establish a secure communications link. Other information, such as user login information, mobile device identification information, etc., may also be used to establish the secure communications link.
[0050] At block 350, encrypted data is received via the secure communications link. As indicated previously, the mobile device may not decrypt the encrypted data.
Instead, at block 360, the encrypted data may be written to the smart media. The mobile device may do so by simply sending the encrypted data to the smart media with no decryption. In so doing, the mobile device may bypass a secure element. Bypassing the secure element may be done by utilizing a specific operating system procedure, which may depend on the mobile device.
[0051] FIG. 4 is a flowchart representing a method 400 for method for enabling a mobile device to communicate with a smart media, which can be performed by a computer of a back-end system (such as the centralized computer host 175 of FIGS. 1A and 1B, and/or the central computer 250 of FIG. 2). The method 400 of FIG. 4 can be performed, for example, by a computer in communication with a mobile device performing the method 300 of FIG. 3.
[0052] At block 410, identifying information regarding the smart media is received. The identifying information can include a card number, serial number, and/or other identifier of the smart media. Additionally or alternatively, identifying information can include user identification information, such as a username, password, account ID, discount status (senior), transit balance, etc. The information can be verified against data in a database or otherwise stored in a memory, local to or remote from the computer. Other information, such as login information, payment source information, payment amount information, and/or an indication of a product or service to purchase, may also be received.
[0053] At block 420, an encryption key is determined. In some embodiments, the encryption key can be determined by utilizing, for example, a lookup table that associates identifying information regarding the smart media with an encryption key. In some embodiments, determining the encryption key may include communicating with an external encryption engine.
As indicated previously, a master key and/or multiple encryption keys may be used. The keys can be diversified, based on the serial number of the smart card and the master key.
[0054] At block 430, a secure communications link is established. The secure communications link, which can be established between the computer and the mobile device, can be based on at least a portion of information read from the smart media by the mobile device.
For example, encryption of the secure communications link can utilize an encryption key associated with an identifier read from the smart media.
[0055] At block 440, encrypted data is communicated via the secure communication link. The encrypted data can include any of a variety of data, which can be written to the smart media. For example, the encrypted data can include a value (e.g., a counter, monetary value, credit value, etc.) used to track the smart media's usage in a transit system. Additionally or alternatively, for ticket validation, such encrypted data can include an indication that a ticket related to the smart media has been used and/or is otherwise no longer valid.
[0056] It should be appreciated that the specific steps illustrated in FIGS. 3-4 provide example flowcharts illustrating embodiments of methods for enabling a mobile device to communicate with a smart media. Alternative embodiments may include alterations to the embodiments shown. For example, alternative embodiments may include reading and/or writing information to and/or from the smart media at different times. Furthermore, additional features may be added or removed depending on the particular applications. One of ordinary skill in the art would recognize many variations, modifications, and alternatives.
[0057] Techniques described herein above for establishing a communication link between the contactless smart card and a remote computer may further be utilized for authenticating the smart media (and/or the holder of the smart media) for non-transit applications, such as loyalty programs and/or other applications in which authentication of a contactless smart card can be utilized for any of a variety of functions.
[0058] FIG. 5 is a simplified block diagram providing an illustration of how this can be utilized using components described herein. Here, components include a contactless smartcard 105, mobile device 120, Internet 170, and central host computer 175, all of which are similar to corresponding components illustrated in FIGS. 1A, 1B, and 2. Additionally, however, FIG. 5 includes a third party system 510 that is also connected to the Internet 170.
It should be known that additional or alternative networks, other than the Internet 170, may be utilized depending on desired functionality. Moreover, embodiments may substitute a mobile device 120 with another electronic device, which may or may not be "mobile."
[0059] As indicated previously, the contactless smartcard 105, mobile device 120, and central host computer 175, can be utilized as described herein above to establish a connection between the contactless smartcard 105 and the central host computer 17. In so doing, the central host computer 175 may validate and/or authenticate the contactless smartcard 105 and provide authentication information to the third party system 510. The third party system 510 can be an application or server maintained by a third party that may include a database that logs authentication information provided to the third party system 510 by the central host computer 175. Depending on desired functionality, the third-party can utilize this authentication information in any of a variety of ways.
[0060] Loyalty programs are an example of how a third party may utilize the authentication provided by the central host computer 175. For example, the third-party system 510 may be a backend server of a coffee shop chain that, due to an agreement between the third-party and a transit system, may provide loyalty points for users of the transit system. In this example, the contactless smartcard 105 may serve as a transit fare media with which a user can gain access to services (e.g., transit rides) in the transit system. If a user enters a coffee shop of the third party's coffee shop chain, techniques herein can be utilized to establish a secure link between the contactless smartcard 105 and the central host computer 175. Here, the mobile device 120 may be a point-of-sale (POS) unit within the coffee shop. The central host computer 175 can authenticate the contactless smartcard 105 and provide details of this authentication to the third party system 510. The third-party system 510 can then credit an account of the user with loyalty points in accordance with a loyalty program of the third party based upon business rules and .. algorithms that are determined by that loyalty program. Additionally or alternatively, the central host computer 175 can provide the mobile device 120 (the POS) or other device maintained by the third party with information regarding the authentication. This may enable the mobile device 120 to provide rewards to the user while the user is performing a transaction at the POS.
[0061] In another example, the contactless smartcard 105 may be authenticated by a central host computer 175 to serve as a library card where the third party system 510 is a server maintained by library. In this example, the contactless smartcard 105, once authenticated, can serve as a library card. When the contactless smartcard 105 is presented at a mobile device 120 (e.g., a checkout terminal at the library), the central host computer 175 may provide user information (e.g., a name and/or account identifier) to the third party system 510, which can then link transactions made by the contactless smartcard 105 to an account maintained by the library.

[0062] These techniques may be utilized in other applications as well. In addition to loyalty and library programs, for example, these techniques may be utilized to authenticate users in student programs, senior programs, other ticket-based venues (concerts, sporting events, etc.), or any other program in which authentication can be utilized.
[0063] The information provided by the central host computer 175 could include any of a variety of data, depending on desired functionality. This authentication information can be determined by business rules implemented by the central host computer 175.
These business rules may be determined by the third party and may be triggered based on data provided by the mobile device, a determined location of the mobile device, an application executed by the mobile device, as the like. In some embodiments, for example, the central host computer 175 may simply indicate that the contactless smartcard 105 is valid or active. The authentication may further include additional information such as user identification information, whether the contactless smartcard 105 has been used in the transit system within a certain time period, a frequency of use, a type of transit product associated with the contactless smartcard 105 or a corresponding user's account, a location of use, and the like.
[0064] FIG. 6 is a flow diagram illustrating a method 600 for enabling an electronic device to communicate with a smart media, according to one embodiment. Any or all of the functions illustrated in the method 600 can be performed, for example, by a central host computer 175. As with other figures provided herein, FIG. 6 is not meant to be limiting. A
person having ordinary skill in the art will recognize alternative embodiments may implement variations to the embodiment illustrated in FIG. 6.
[0065] The method can begin at block 610, by receiving information read from the smart media by the electronic device, the information including identifying information regarding the smart media. Information read from the smart media may include any of a variety of identifying information, such as an account number, a user identification code, an ID
number or serial number of the smart media, or the like. As indicated previously, initial information received from the smart media may not be encrypted.
[0066] At block 620, a secure communications link between the electronic device and the server is established. This can be done using the techniques described previously herein. For example, it may involve determining an encryption key so that communication between the smart media and the server can be secure. As noted previously, the electronic device may not decrypt this communication, but may instead simply pass the encrypted communication between the smart media and the server.
[0067] The functionality at block 630 involves conducting a transaction between the server and the smart media via the secure communications link. Such a transaction can include any transaction previously described herein in other embodiments. This transaction may involve writing encrypted data to the smart media, reading additional information from the smart media, and/or other functions.
[0068] The functionality at block 640 involves determining a third party related to the transaction. The server may make this determination based on information received from the electronic device and/or the smart media. For example, the electronic device may provide information indicative of a managing entity, a location, a transaction type, and/or other type of information with which a third party may be identified. Additionally or alternatively, the smart media itself may provide information such as an identification code, name, or other data, which may be read from the smart card by the electronic device and provided to a server.
[0069] This information may be used to determine relevant business rules related to the third party. These business rules can include rules that may be specific to the third party such as, for example, an indication of what authentication information to send to the third party, a device or devices to which the information is to be sent, protocols and/or other technical information related to the sending of data, and the like.
[0070] At block 650, in response to determining the third party related to the transaction, authentication information is sent to a device associated with the third party. As indicated previously, the device may be the electronic device facilitating the communication between the smart media and the server, or it may be a separate device, such as a server or other third-party system, as described previously.
[0071] Embodiments may implement any of a variety of additional or alternative features, depending on desired functionality. For example, some embodiments may include communicating encrypted data to the smart media via the secure communications link by writing the encrypted data such that a secure element of the mobile device is not used. In some embodiments, the authentication information may comprise an indication that the smart media is valid or active, and/or one or more of user identification information, an indication of when the smart media was last used in a transit system, a frequency of use of the smart media, a type of transit product associated with the smart media or a corresponding user's account, or a location of use of the smart media, or any combination thereof.
[0072] In the foregoing description, for the purposes of illustration, methods were described in a particular order. It should be appreciated that in alternate embodiments, the methods may be performed in a different order than that described. It should also be appreciated that the methods described above may be performed by hardware components and/or may be embodied in sequences of machine-readable instructions, such as programming code, which may be used to cause a machine, such as a general-purpose or special-purpose processor or logic circuits programmed with the instructions to perform the methods. These machine-readable and/or computer-readable instructions may be stored on one or more non-transitory storage mediums, such as CD-ROMs or other type of optical disks, floppy diskettes, ROMs, RAMs, EPROMs, EEPROMs, magnetic or optical cards, flash memory, or other types of machine-readable storage mediums suitable for storing electronic instructions.
.. [0073] With this understanding, embodiments may be implemented by hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof.
When implemented in software, firmware, middleware or microcode, the program code or code segments to perform the necessary tasks may be stored in a machine-readable storage medium, such as those described above. A processor(s) may perform the necessary tasks.
[0074] Embodiments provided herein are examples only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the embodiments will provide those skilled in the art with an enabling description for implementing one or more embodiments. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosed systems and methods as set forth in the appended claims.
[0075] While illustrative and presently preferred embodiments of the disclosed systems, methods, and devices have been described in detail herein, it is to be understood that the inventive concepts may be otherwise variously embodied and employed, and that the appended claims are intended to be construed to include such variations, except as limited by the prior art.

Claims

WHAT IS CLAIMED IS:

1. A method for enabling an electronic device to communicate with a smart media, the method comprising:
receiving, with a server, information read from the smart media by the electronic device, the information including identifying information regarding the smart media;
establishing a secure communications link between the electronic device and the server;
conducting a transaction between the server and the smart media via the secure communications link;
determining, with the server, a third party related to the transaction; and in response to determining the third party related to the transaction, sending, from the server, authentication information to a device associated with the third party.

2. The method for enabling the electronic device to communicate with the smart media of claim 1, further comprising communicating encrypted data to the smart media via the secure communications link by writing the encrypted data such that a secure element of the mobile device is not used.

3. The method for enabling the electronic device to communicate with the smart media of claim 1, wherein authentication information comprises an indication that the smart media is valid or active.

4. The method for enabling the electronic device to communicate with the smart media of claim 1, wherein the authentication information comprises one or more of:
user identification information, an indication of when the smart media was last used in a transit system, an indication of where the smart media was last used in a transit system, an indication of how the smart media was last used in a transit system, a frequency of use of the smart media, a type of transit product associated with the smart media or a corresponding user's account, or a location of use of the smart media, or any combination thereof.

5. The method for enabling the electronic device to communicate with the smart media of claim 1, wherein the device associated with the third party is the electronic device.

6. The method for enabling the electronic device to communicate with the smart media of claim 1, wherein determining, with the server, the third party related to the transaction is based on information provided by the electronic device.

7. A non-transitory computer-readable medium having instructions embedded thereon for enabling an electronic device to communicate with a smart media, the instructions including computer-executable code for:
receiving information read from the smart media by the electronic device, the information including identifying information regarding the smart media;
establishing a secure communications link between the electronic device and a server;
conducting a transaction between the server and the smart media via the secure communications link;
determining a third party related to the transaction; and in response to determining the third party related to the transaction, sending authentication information to a device associated with the third party.

8. The non-transitory computer-readable medium of claim 7, wherein the instructions further comprise computer code for communicating encrypted data to the smart media via the secure communications link by writing the encrypted data such that a secure element of the mobile device is not used.

9. The non-transitory computer-readable medium of claim 7, wherein the instructions further comprise computer code for providing authentication information comprising an indication that the smart media is valid or active.

10. The non-transitory computer-readable medium of claim 7, wherein the instructions further comprise computer code for providing authentication information comprising one or more of:
user identification information, an indication of when the smart media was last used in a transit system, an indication of where the smart media was last used in a transit system, an indication of how the smart media was last used in a transit system, a frequency of use of the smart media, a type of transit product associated with the smart media or a corresponding user's account, or a location of use of the smart media, or any combination thereof.

11. The non-transitory computer-readable medium of claim 7, wherein the instructions further comprise computer code for determining the third party related to the transaction based on information provided by the electronic device.

12. A server for enabling an electronic device to communicate with a smart media, the server comprising:
a communications interface; and a processing unit communicatively coupled with the communications interface and configured to cause the server to:
receive, via the communications interface, information read from the smart media by the electronic device, the information including identifying information regarding the smart media;
establish, via the communications interface, a secure communications link between the electronic device and the server;
conduct a transaction between the server and the smart media via the secure communications link;
determine a third party related to the transaction; and in response to determining the third party related to the transaction, send, via the communications interface, authentication information to a device associated with the third party.

13. The server for enabling the electronic device to communicate with the smart media of claim 12, wherein the processing unit is further configured to cause the server to communicate encrypted data to the smart media via the secure communications link by writing the encrypted data such that a secure element of the mobile device is not used.

14. The server for enabling the electronic device to communicate with the smart media of claim 12, wherein the processing unit is further configured to include, in the authentication information, an indication that the smart media is valid or active.

15. The server for enabling the electronic device to communicate with the smart media of claim 12, wherein the processing unit is further configured to include, in the authentication information, one or more of:
user identification information, an indication of when the smart media was last used in a transit system, an indication of where the smart media was last used in a transit system, an indication of how the smart media was last used in a transit system, a frequency of use of the smart media, a type of transit product associated with the smart media or a corresponding user's account, or a location of use of the smart media, or any combination thereof.

16. The server for enabling the electronic device to communicate with the smart media of claim 12, wherein the processing unit is further configured to cause the server to base the determination of the third party related to the transaction on information provided by the electronic device.