Abstract:
The present device aggregates all kinds of contactless services such as credit card, loyalty card, micro-payment, discount card, transport card, access control, e-ticket, parking, etc. An NFC (Near Field Communication) device comprises a host CPU, a memory, a GPRS modem controlled by the CPU to access Internet, a SIM holder, an antenna and a battery. The NFC device is shaped as a credit card and it also includes a touch-screen, able to implement technical functionalities to operate contactless services, visualize his ticket/coupon and consult the latest transaction, a secure element to store and execute the contactless applications, and a ST controller connected to Host CPU and to the SE.

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
       [0001]    This application is a Continuation-in-Part of U.S. patent application Ser. No. 14/358,525, filed on May 15, 2014, which is a U.S. National Phase Entry of International Application No. PCT/EP2012/072784, filed on Nov. 15, 2012, which claims priority to French Patent Application Serial No. 11/03456, filed on Nov. 15, 2011, all of which are incorporated by reference herein. 
     
    
     BACKGROUND 
       [0002]    The invention relates to a NFC (Near Field Communication) device shaped as a credit card with a touch-screen able to implement technical functionalities and a connection system of NFC devices. 
         [0003]    NFC technology development in the mobile communication field is growing up with the integration of contactless radio frequency identification and interconnectivity. The functions of card reader, induction card and peer-to-peer are integrated in a single chip. NFC technology involves also identification and data exchanges with compatible devices within short distance by inductive coupling of radio frequency. In particular, the NFC mobile phone allows the short distance wireless communication and achieves a plurality of functions: electronic payment, tag reading, tickets system and data download. 
       SUMMARY 
       [0004]    The problem is the aggregation of the more and more functions and their compatibility. The goal of this device is to aggregate all kind of contactless services such as credit card, loyalty card, micro-payment, discount card, transport card, access control, e-ticket, parking, etc. The NFC device according to the invention is defined with combinations of particular features of claims  1  to  10  and the connection system with the combination of particular features of claim  11 . 
         [0005]    The device is connected to mobile Internet through a GPRS connection, which let user receives e-coupon and e-ticket “over the air”, top-up (recharge) an e-wallet or extends validity of an e-transport or e-parking card without having to queue at the cashier. The touch-screen lets the user operate the service, visualize his ticket/coupon, consult the latest transaction, and so on. The NFC device has a secure element SE to store the contactless application. The Secure Element is a smartcard like a microcontroller that stores and executes application called Cardlet. Each Cardlet implements the contactless service. 
         [0006]    Through the mobile Internet connectivity, NFC devices are connected to a backend server. The backend server is used to manage application download on the NFC device and on the secure element. Through the backend server, when a new user subscribes a service, the contactless application is downloaded to the SE and the user interface is downloaded to the NFC device of the new subscriber. 
         [0007]    The device is powered on a rechargeable battery. But it can still operate when the battery is empty (battery off mode), Beijing powered-up by the magnetic induction field issued from the POS. In that mode, the screen and GPRS connection is not functional, but contactless transaction can still be done. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0008]      FIG. 1  describes the main device&#39;s functionalities of an example of a NFC device according to the invention; 
           [0009]      FIG. 2  describes the power on/off life cycle of the NFC device example; 
       
    
    
       [0010]    The layout cut of the NFC device example is illustrated in  FIG. 3 ; and 
         [0011]    The software stack design of the same example is showed in the  FIG. 4 . 
       DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS 
       [0012]    As shown in  FIG. 1 , an example of NFC device according to the invention is built around a CPU/MCU  12  with NAND flash memory and RAM  13 . The touch-screen  10  is made of a color LCD display and an associated Touch-Panel. The device has Internet access through a GSM/GPRS modem  11 . The GPRS modem is controlled with the CPU  12 . GPRS Modem  11  is connected to CPU/MCU  12 , and it can be powered on/off by CPU/MCU&#39;s GPIO. A SIM/miniSIM holder  110  will receive the SIM needed to GPRS/3G communication. 
         [0013]    The NFC device is powered with NFC FrontEnd Controller  21 . The NFC FrontEnd Controller  21  is connected to Host CPU/MCU  12 . NFC FrontEnd Controller  21  is then connected to a Secure Element  16 . 
         [0014]    The NFC Device received NFC radio-frequency thought an Antenna  17  designed as a external board, or as a wire wrapped and embedded into the device case. A specific power management module powers up the NFC part. In order to take advantage of the battery off mode, the SE  16  power pin is connected to a pin of the NFC FrontEnd Controller  21 . The NFC FrontEnd Controller  21  is connected to the battery in order to have the NFC feature available event if the device is power off. 
         [0015]    In order to let host CPU/MCU  12  access the SE  16  directly, the device uses a dedicated chip, a SC Reader  14 . The SC reader  14  is connected to the SE  16  with a standard ISO 7816 connection, and to the host CPU/MCU  12 . As the SC reader  14  is a generic micro-controller, a special firmware is designed to interface the Host CPU/MCU  12 . 
         [0016]    The NFC device is powered by a battery and recharged from a USB connector. A LED indicates when the device is charging and when full charge level is reached. The hardware provides battery charge level information. 
         [0017]    The  FIG. 2  describes an example of the NFC device&#39;s power on/off life cycle. A two states button  21  located on the top (or on the side) of the device powers on/off &amp; lock/unlock the device. The life cycle is described in  FIG. 2 . 
         [0018]    The device layout cut is illustrated in  FIG. 3 . It comprises:
       a LCD/TP layer  31 , connected to   a Printed Circuit Board (PCB) motherboard  32 , connected to   a NFC antenna  33  and to a battery  34 , and   the GSM antenna  17  connected to the PCB motherboard  32 .       
 
         [0023]    The device size is credit card format (85 mm×54 mm) and fits cabling and the above mentioned chips/feature. The device is running a custom software. The high level software stack design is showed in the  FIG. 4 . 
         [0024]    The NFC stack is broken into two subcomponents:
       a HCl layer  41 , which implements the protocol related to NFC Front-End controller.   a NFC Forum specification layer with a card emulation  42 , NDEF Emulation  43  and peer-to-peer module  44 . This layer implements NFC Forum specification.
 
This last layer provides specific Apis  45  to let service application control/access NFC feature of the NFC Front-End controller.
       
 
         [0027]    The application layer consists in two kinds of components:
       service applications  46  that implements a given service, like e-wallet, e-coupon wallet, etc.;   Service Application Manager SAM  47  that manages Service Application running on the board.
 
SC Reader Firmware  48  interfaces the host CPU/MCU with the SE through an ISO7816 connection. SC Reader Driver  49  provides API to interface Application Layer with SC reader through the SC Reader Firmware  48 .
       
 
         [0030]    Service Apps are under management of SAM-Home-Screen  47  (Service App manager). Service Apps are started or deleted through SAM  47 . SAM is started at device startup and is always running in the background. User cannot close/kill/terminate SAM. 
         [0031]    SAM Maintain a list of Service Application installed on the device and show a “cover flow” with all Service App&#39;s icons. SAM lets the user browse all Service App Icon and launch/starts the selected Service App. SAM monitors running Service App and bring itself to front end when running Service App is terminated. (SAM always remains on the background). 
         [0032]    Service App can register to SAM for NFC Activity. Service App will give the AID of the Card application they are related to. When POS will send data to that Card Application SAM will start the associated Service App. SAM supports read/write Smart Poster feature. When user “tap” a smart poster, SAM will pop-up a dialog and performs the actions associated with the tag. 
         [0033]    Tag associated actions are:
       Trigger Service App launch;   Trigger Service App download;   Trigger Service App content download;   Download and render a predefined simple XML format to display text and image;   Send HTTP notification to the server.       
 
         [0039]    The technical problem is that, the portable communication devices, generally known as smartphones, contains a secure element with a key or other encryption information determined by the manufacturer. The users of third party applications want or need to ensure the payment data and other credentials by another security control, which is different from the secure element. 
         [0040]    As disclosed in the published patent application US20120124394 (which is incorporated by reference herein), a virtual secure element is used in order to fulfill the desire of uses for the third party application. This virtual secure element can be located on any memory accessible to the communication device and is managed by a card management system. This card management system tracks the issuers of all cards, coupon, access control and ticket data stored in the virtual secure memory as well as secure element in the payment subsystem. This means that the virtual secure memory knows the key of the secure element and has access to the internal data of the secure element. This imposes a potential danger to the security of system, since there is a possibility to invade the secure element via the virtual secure element. 
         [0041]    In order to solve this problem, the patent application US20120124394 discloses that the virtual secure element may also be secured using a key or other encryption information that is stored in the secure element. In this case, in order to access the data stored within the virtual secure element, the card management system would need to access and obtain the key from the secure element. Again, in this embodiment, the card management system also has access to the internal data of secure element. 
         [0042]    It is important to find a method without necessity to access the internal data of the secure element. In addition, the key of the secure element is an inherent element from the manufacturer. For certain third party, e.g. a bank, it needs to have an independent key, which is not accessible by the manufacturer. Thus, the invention in the present patent application enables the joint use of internal secure element (SE) and external secure module, like service app manager (SAM) or cards in the same module. So these two levels of secure elements guarantee the security of an application jointly. 
         [0043]    As illustrated in the  FIG. 1 , in order to let host CPU access the security element directly, the device uses a dedicated chip, a security card reader, which has its owner key and is connected directly to the security element with a standard ISO connection. As the security card reader is a generic micro-controller, a special firmware is designed to interface the host CPU. The security card reader can activate and deactivate the security element. Furthermore, the SC reader can verify the active/non-active status of the security element without access of the inherent content and data in the security element. 
         [0044]    In this sense there is a double level of security: the internal security by the secure element and the external security by the SC reader. The keys in the SC reader and keys in the SE belong to two different identifies. Firstly, the SE contains its inherent keys, which are set by the manufacturer and responsible for the internal security of the smartphone device. Then the SC reader contains another keys, which are held only by the user, e.g. bank. For the payment and transaction, the bank verifies the key in the SC reader. 
         [0045]    At the first level, these two keys are independent in their functions in controlling the identification and access to this device. At the second level, the SC reader is an external control to operate the SE in the sense that the SC reader can activate and deactivate the SE without reading, verifying or modifying the content inside the SE. 
         [0046]    As illustrated in the  FIG. 4 , the application layer consists in two kinds of components: service applications that implements a give service and service application managers SAM that manages series application running on the board. SC reader firmware interfaces the host CPU/MCU with the SE through an ISO connection. SC reader driver provides API to interface application layer with SC reader through the SC reader firmware. Thus, the SE can activate and deactivate the SAM. 
         [0047]    The security element can realize the authentication of the keys of the SAM, and diversification of symmetric keys of the SAM. Meanwhile, the SAM can contain the key for the payment, and the bank transaction data. A list of possible application examples is given below: 
         [0048]    1. Deploying SAM Access and Securing the SAM Access at the Same Time. 
         [0000]    Banks or transport companies normally use SAM to secure the transactions with credit cards or transport cards. The accesses to those SAMs are usually controlled with a code. However storing the code on the applications of the file system in the host operation device is unsecure, it is easily to be decrypted. The usage of an internal secure element to activate and to deactivate the SAM enables Security. 
         [0049]    2. Securing Device and Device Connectivity without Comprising SAM. 
         [0000]    When an operator has deployed a payment/transportation scheme with its SAM, he still needs to cypher the communications between the devices. However, because the SAM contains the keys, this can be done with the use of the internal secure element and hence without the need to give access to the SAM. 
         [0050]    3. Verify the Authenticity of Applications and Binary. 
         [0000]    When deploying business applications on a mobile terminal, one is limited by the security of the operating system, e.g. android. The internal secure element is used to sign the applications binary in order to ensure the security of the application. 
         [0051]    4. Creating Dual Applications 
         [0000]    Although deploying applications on a terminal is limited by the security of the operation system, a duplet application type can improve the security. This duplet application type consists of a couple of applications, one stored on the operating system (e.g. android) as an apk and the other on the internal secure element as a javacard application, with the business logic programmed in the secure element javacard application. 
         [0052]    5. Identifying Hardware 
         [0000]    When transaction are made on a terminal, it is essential to identify in an secure way the hardware of the host making the transaction, like MAC/IMEI/Serial numbers/uuid are easily changeable. The internal security element enables to identify securely a device. In addition, the security element can identify the unique mutual ID, the private and public key for the communication with a platform. Furthermore, the SE can sign the communication, the application.