EP2649776A1 - Procédé pour la gestion d'entités asynchrones - Google Patents

Procédé pour la gestion d'entités asynchrones

Info

Publication number
EP2649776A1
EP2649776A1 EP11784646.9A EP11784646A EP2649776A1 EP 2649776 A1 EP2649776 A1 EP 2649776A1 EP 11784646 A EP11784646 A EP 11784646A EP 2649776 A1 EP2649776 A1 EP 2649776A1
Authority
EP
European Patent Office
Prior art keywords
application
message
nfc
sending
secure element
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.)
Withdrawn
Application number
EP11784646.9A
Other languages
German (de)
English (en)
Inventor
Christophe Foesser
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Thales DIS France SA
Original Assignee
Gemalto SA
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Gemalto SA filed Critical Gemalto SA
Priority to EP11784646.9A priority Critical patent/EP2649776A1/fr
Publication of EP2649776A1 publication Critical patent/EP2649776A1/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/72409—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories
    • H04M1/72412—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories using two-way short-range wireless interfaces
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2250/00—Details of telephonic subscriber devices
    • H04M2250/04—Details of telephonic subscriber devices including near field communication means, e.g. RFID
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices

Definitions

  • the present invention relates to methods of managing asynchronous entities. It relates particularly to methods for optimizing communication between two asynchronous entities which are embedded in a secure element .
  • Secure elements may provide several services like crypto services, SIM features, or any applications which may be embedded in a smart card for example.
  • the NFC (Near Field Communication) technology is based on the exchanging of data via a magnetic field.
  • Two NFC devices may communicate thanks to an inductive coupling in a field frequency equal to 13.56 MHz.
  • the IS014443 and ISO18092 standards provide modulation technologies and communication protocols which may be used in NFC domain.
  • Secure elements are small machines comprising a memory, a microprocessor and an operating system for computing treatments. Secure elements are intended to connect - either in contact or contactless mode - a device which may provides power and a user interface.
  • secure elements comprise a plurality of memories of different types. For example, they may comprise memory of RAM, ROM, EEPROM or Flash type. Secure elements have limited computing resources.
  • smart cards are secure elements.
  • a secure element may comprise a NFC application.
  • a secure element may comprise a SimToolKit (STK) engine able to manage STK commands as described in ETSI GSM 11.14 standard.
  • STK SimToolKit
  • a mobile phone may have NFC features allowing a NFC reader to access a NFC application embedded in a SIM card.
  • a SIM card may comprise a SimToolKit (STK) engine, an application depending on the STK engine and a NFC application.
  • STK SimToolKit
  • An application depending on the STK engine is an application that uses the STK engine features. For example, such an application may exchange data with the mobile phone through commands sent to the STK engine. Thus the application depends on the STK engine for exchanging data with the mobile phone.
  • STK SimToolKit
  • An application depending on the STK engine is an application that uses the STK engine features. For example, such an application may exchange data with the mobile phone through commands sent to the STK engine. Thus the application depends on the STK engine for exchanging data with the mobile phone.
  • There is a difficulty for exchanging data between an application depending on the STK engine and a NFC application This difficulty is due to the fact that the STK engine and a NFC application operate under different schemes. These two schemes are
  • the NFC application may be started at any time while the SimToolKit engine can perform a treatment only when it has received a message from the mobile phone.
  • Possible messages are defined in the ETSI TS 102 223 v7.0 and upper standard.
  • the Status message may be used.
  • the SIM card when a NFC application embedded in a SIM card is triggered by an external NFC reader, the SIM card must wait for the receipt of a Status message which allows the processing of the display of data on the mobile phone display.
  • the sending of Status messages is managed in polling mode. In general, a Status message is sent every 6 to 30 seconds. So it may take up to 11 seconds before the data sent by the NFC application is displayed on the mobile phone.
  • An object of the invention is to solve the above mentioned technical problem.
  • the object of the present invention is a method for managing the communication between first and second asynchronous entities embedded in a secure element.
  • the first entity is a first NFC application.
  • the secure element comprises a web server and a SimToolkit engine.
  • the secure element is connected to a telecom equipment which comprises a NFC controller.
  • the second entity is dependent on the SimToolkit engine.
  • the method comprises the steps of:
  • the second message may be directly sent from the second application to the web server .
  • the telecom equipment may comprise a web browser and the second application may request the web browser to send the second message to the web server .
  • the second application may have no Graphical User Interface.
  • the second application may be a midlet
  • the first entity may be a NFC applet
  • the first message may contain a HCI Event Transaction.
  • the sending of the first message may be triggered by the receipt of a third message sent by a NFC reader.
  • the sending of the first message may be triggered by the receipt of a third message generated by a component embedded either into the secure element or into the telecom equipment.
  • Another object of the invention is a telecom equipment comprising a NFC controller and a secure element.
  • the secure element is connected to the telecom equipment.
  • the secure element comprises a web server, a SimToolkit engine, a first NFC application and an entity dependent on the SimToolkit engine.
  • the entity and the first NFC application are asynchronous.
  • the telecom equipment comprises a second application.
  • the first NFC application is capable of sending a first message to the second application through the NFC controller in order to request the sending of a second message to the web server.
  • the second application is adapted to initiate the sending of the second message to the web server by using the Bearer Independent Protocol (also named BIP) in response to the receipt of the first message.
  • BIP Bearer Independent Protocol
  • the first NFC application may be able to send the first message through the Single Wire Protocol (also named SWP) .
  • SWP Single Wire Protocol
  • the second application may be a midlet
  • the first entity may be a NFC applet
  • the first message may contain a HCI Event Transaction.
  • FIG. 1 depicts schematically a first example of a system comprising a mobile phone and a SIM card according to the invention wherein a direct call is performed;
  • Figure 2 is a second example of a system comprising a NFC reader, a mobile phone and a smart card according to the invention wherein a direct call is performed, and
  • FIG. 3 is an example of a system comprising a mobile phone and a smart card according to the invention wherein an indirect call is performed.
  • a NFC controller is a hardware module also named ContactLess Front-end chip (CLF) .
  • the invention may apply to any types of devices comprising a NFC controller and a secure element and which are able to manage the Bearer Independent Protocol (also named BIP) as defined in ETSI TS 102 223 v7.0 and upper standard.
  • BIP Bearer Independent Protocol
  • These devices may be portable devices like mobile phones, Electronic Funds Transfer Terminals for payment or Personal Digital Assistant (PDA) equipped with communication means.
  • PDA Personal Digital Assistant
  • These devices may also be fixed devices like smart poster as known as tag.
  • These devices may also be telecom equipments used in Machine- To-Machine (M2M) domain.
  • Figure 1 shows an example of a system comprising a
  • Figure 1 also shows a step sequence for managing the communication between a NFC application and a STK application through a direct call according to the invention.
  • the NFC reader RD is a NFC device working in reader mode.
  • the NFC reader RD has its own antenna AN2.
  • the mobile phone MP comprises an antenna AN, a NFC controller NC, a secure element SC, a display DI, a Java virtual machine VM, an application NMI and an application manager AM.
  • the secure element SC is connected to the mobile phone MP either in contact or wireless mode.
  • the secure element SC is a Universal Integrated Circuit Card (UICC) .
  • the secure element may be a SIM card, a USIM card or any personal security token.
  • the secure element SC may be a Secure Digital (SD) card, a miniSD card, a microSD card or a smart card.
  • SD Secure Digital
  • the application NMI is a Midlet which relies on the Java virtual machine VM.
  • the Midlet is a J2ME application which uses the MIDP 2.x as defined in SUN Mobile Information Device Profile for JavaTM 2 Micro Edition Version 2.1 for example.
  • the application manager 7AM controls the activities of the Midlets within the Java ME environment on the mobile phone MP. The application manager 7AM can select which Midlet is active at a given time by starting and by pausing it individually.
  • the NFC controller NC and the secure element SC are linked by a single wire link (not drawn at Figure 1) .
  • This single wire link allows a communication in contact mode between the NFC controller NC and the secure element SC.
  • both the NFC controller NC and the secure element SC use the Single Wire Protocol (SWP) as defined by the TS 102.613.
  • SWP Single Wire Protocol
  • NFC application means an application which is able to communicate with a NFC controller.
  • the secure element SC comprises a NFC application NAP that is intended to communicate with the NFC reader RD through a contactless protocol.
  • the used contactless protocol may be compliant with IS014443, ISO18092 or IS015693 standards.
  • the used contactless protocol may also comply with proprietary specifications.
  • the two applications SA and NAP may form a Transport application which provides access to a public transport network or a Payment application. These two applications may also be in various domains like electronic ticketing, gaming, e-wallet, debit/credit payment card, electronic keys for accessing a car/a house / a room, etc.
  • the NFC reader RD comprises a reader-part application (not drawn) which is intended to communicate with the application NAP.
  • the secure element SC comprises a web server WS .
  • the web server WS comprise an application Wl which may be implemented as a Servlet.
  • the web server WS may be a Smart Card Web Server (SCWS) as defined by OMA-TS Smartcard Web Server VI .0 standard.
  • SCWS Smart Card Web Server
  • the secure element SC comprises a SimToolkit (STK) engine and a STK application SA.
  • STK application SA is an application depending on the STK engine SE . In other words, when running, the STK application SA needs to access services of the STK engine SE .
  • the application NAP comprises a means ME1 able to send a message Ml to the application NMI through the NFC controller NC .
  • the message Ml requests the sending of a second message M2 to the web server WS .
  • the message Ml is conveyed from the secure element SC to the controller NC via the single wire link.
  • the application NMI comprises a means ME2 able to initiate the sending of the message M2 targeting the web server WS via the Bearer Independent Protocol (BIP) .
  • the means ME2 is adapted to initiate the sending of the message M2 in response to the receipt of the message Ml .
  • Figure 1 shows an example of step sequence for managing the communication between the application NAP and the STK engine SE according to the invention.
  • Both the application NAP and the STK application SA are asynchronous. This is due to the fact that the application NAP depends on the STK engine SE and that the STK engine SE and the application NAP behave in asynchronous ways.
  • the application NAP is triggered by an event.
  • the application NAP received a data emitted by the NFC reader RD at step SI.
  • This emitted data is routed through the NFC controller NC to the secure element SC.
  • the receipt of this emitted data in the secure element SC is the event that triggers the application NAP.
  • the application NAP sends a data to be displayed on the mobile phone display DI .
  • This data is sent by the application NAP to the STK application SA.
  • the STK application SA sends a message to the STK engine SE for requesting the display of data on the mobile phone display DI .
  • the STK engine SE should wait for several seconds without the invention .
  • the means ME1 sends a message Ml which targeted the application NMI.
  • the message Ml is routed through the NFC controller NC to the application NMI.
  • the message Ml may contain the "HCI Event Transaction" as defined by ETSI TS 102 705 V9.0 and upper standard.
  • the message Ml may be transmitted by the controller NC to the application manager AM via the baseband modem (not drawn) of the mobile phone MP. Then the application manager AM launches the application NMI and provides the application NMI with the message Ml. This launching may be implemented trough the Push registry mechanism as defined by the SUN JSR257 specification. Thus the message Ml may be transported through several forms between the means ME1 and the application NMI.
  • step S5 the means ME2 of the application NMI sends a message M2 to the web server WS through a local communication network based on a BIP channel.
  • the use of the local communication network based on BIP channel activates the STK engine SE .
  • the sending of the message M2 is triggered by the receipt of the message Ml.
  • This embodiment corresponds to a direct call performed by the application NMI.
  • the direct call i.e. the direct sending of the message M2
  • the direct call may be done either by sending a request to the web server WS .
  • the direct call may also be performed by sending a request to the application Wl of the web server WS thanks to the J2ME standard network API .
  • the message M2 is sent to the web server WS which further forwards the message M2 to the application Wl .
  • the means ME2 may send the following network request
  • HTTP HyperText Transfer Protocol : / / 127.0.0.1 : 3516/1rigger
  • This request is used for generating the message M2 to be sent to the server WS .
  • the application Wl may receive a message containing the following item: "GET HTTP 1.1 /trigger”.
  • the application Wl may have no computing treatment.
  • the main role of the application Wl is to be a target that allows starting the STK engine SE thanks to the sending of a request targeting the application Wl .
  • the invention takes advantage of the sending of a message targeting a web application and initiated by the application NMI . Whatever the further execution of theses two applications, the message sending generates the activation of the STK engine SE .
  • the STK engine SE has been started in the secure element SC.
  • the STK engine SE may send a message to the mobile phone in order to have the relevant data displayed on the mobile phone display DI .
  • GUI graphical user interface
  • the invention takes advantage of the very short execution time of the steps S4 and S5.
  • the STK engine is activated in a nearly real time way.
  • the NAP is triggered by the receipt of a data emitted by the NFC reader RD at step SI.
  • the application NAP may be triggered by any kind of event.
  • the application NAP may be triggered by the receipt of a message coming from a component embedded in the secure element SC itself.
  • the secure element SC may comprises a sensor able to send a message to the application NAP.
  • the embedded component may be a sensor able to measure the light, a motion, a temperature, a magnetic field, the gravity, the humidity, a vibration, the pressure, an electrical field, a sound, and any other physical aspects of the external environment
  • the application NAP may be triggered by the receipt of a message coming from a component embedded in the device MP.
  • the embedded component may be a sensor as described above.
  • the embedded component may send a message to the secure element SC via the NFC controller NC in order to take advantage of the existing interface between the secure element SC and the controller NC .
  • the embedded component may send a message to the secure element SC via an USB controller which is embedded in the telecom equipment MP.
  • the application SA may be included into the application NAP.
  • the application SA may be included into the application Wl .
  • the STK application SA may send the display request to the STK engine SE after the application Wl has been triggered by the message M2. In other words steps S4 and S5 may occur before the step S3.
  • the device MP may have no web browser.
  • application Wl can be a default web server WS application.
  • Figure 2 shows another example of a system comprising a NFC reader RD, a mobile phone MP2 and a secure element SC2 according to the invention.
  • Figure 2 also shows another step sequence for managing the communication between a NFC application and a Web server application through a direct call according to the invention.
  • the NFC reader RD is a reader similar to the one described at Figure 1.
  • the mobile phone MP2 is similar to the mobile phone MP of the Figure 1 with one difference:
  • the mobile phone MP2 comprises a web browser BR.
  • the secure element SC2 may be connected to the mobile phone MP2 either in wire or wireless mode.
  • the secure element SC2 is a
  • the secure element SC2 may be a SIM card, a USIM card, a Secure Digital (SD) card, a miniSD card, a microSD card, a smart card or any personal security token.
  • SIM SIM
  • USIM USIM
  • SD Secure Digital
  • miniSD miniSD
  • microSD microSD
  • smart card any personal security token.
  • the NFC controller NC and the secure element SC2 are linked by a single wire link (not drawn) .
  • This single wire link allows a communication in contact mode between the NFC controller NC and the secure element
  • both the NFC controller NC and the secure element SC2 use the Single Wire Protocol (SWP) .
  • SWP Single Wire Protocol
  • the secure element SC2 comprises a NFC application NAP that is intended to communicate with the NFC reader RD through a contactless protocol.
  • the application NAP may be a payment application for example.
  • the secure element SC2 comprises a web server WS .
  • the web server WS comprises two applications Wl and W2. These applications may be implemented as SCWS servlets.
  • the web server WS may be a Smart
  • SCWS Card Web Server
  • the secure element SC2 comprises a SimToolkit engine SE .
  • the application W2 is an application depending on the STK engine SE . For instance, the application W2 needs the STK engine for displaying a text on the mobile phone display DI .
  • the application NAP comprises a means ME1 able to send a message Ml to the application NMI through the NFC controller NC .
  • the message Ml requests the sending of a second message M2 to the web server WS .
  • the message Ml is conveyed from the secure element SC2 to the controller NC via the single wire link.
  • the application NMI comprises a means ME2 able to initiate the sending of the message M2 targeting the web server WS via the Bearer Independent Protocol
  • the means ME2 is adapted to initiate the sending of the message M2 in response to the receipt of the message Ml .
  • Figure 2 shows an example of step sequence for managing the communication between the application NAP and the application W2 according to the invention.
  • the application NAP and the application W2 are asynchronous.
  • both the application NAP and the STK engine SE are asynchronous.
  • the application NAP is triggered by an event.
  • the application NAP received a data emitted by the NFC reader RD at step SI.
  • This emitted data is routed through the NFC controller NC to the secure element SC2.
  • the receipt of this emitted data in the secure element SC2 is the event that triggers the application NAP.
  • the application NAP sends a data to be displayed on the mobile phone display DI .
  • This data is sent by the application NAP to the application W2.
  • the application W2 sends a message to the STK engine SE for requesting the display of data on the mobile phone display DI .
  • the means ME1 sends a message Ml which targeted the application NMI .
  • the message Ml is routed through the NFC controller NC to the application NMI .
  • the three steps S2B, S3B and S4 may occur in any order .
  • the means ME2 of the application NMI sends a message M2 to the web server WS through a local communication network based on a BIP channel.
  • the use of the local communication network based on BIP channel activates the STK engine SE .
  • the sending of the message M2 is triggered by the receipt of the message Ml .
  • This embodiment corresponds to a direct call performed by the application NMI .
  • the direct call may be done by sending a request to the web server WS .
  • the direct call may also be performed by sending a request to the application Wl of the web server WS thanks to the J2ME standard network API .
  • the message M2 is sent to the web server WS which further forwards the message M2 to the application Wl .
  • the application Wl may have no computing treatment.
  • the main role of the application Wl is to be a target that allows starting the STK engine SE thanks to the sending of a request targeting the application Wl .
  • the application Wl can be a default web server WS application.
  • the STK engine SE has been started in the secure element SC2.
  • the STK engine SE may send a message to launch the browser BR.
  • the browser BR sends a request to the application W2 in order to get the data to be displayed at step S7.
  • the application W2 send the relevant data to the browser at step S8.
  • the browser BR displays the data on the screen DI of the mobile phone MP2 at step S9.
  • Figure 3 shows another example of a system comprising a NFC reader RD, a mobile phone MP2 and a secure element SC2 according to the invention.
  • Figure 3 also shows another step sequence for managing the communication between a NFC application and a Web server application through an indirect call according to the invention.
  • the NFC reader RD is a reader similar to the one described at Figure 1.
  • the mobile phone MP2 is similar to the mobile phone MP of the Figure 1 with one difference:
  • the mobile phone MP2 comprises a web browser BR.
  • the secure element SC2 is a Universal Integrated Circuit Card (UICC) of USIM type.
  • the NFC controller NC and the secure element SC2 are linked by a single wire link (not drawn) and communicate according to the Single Wire Protocol.
  • the secure element SC2 comprises a NFC application NAP that is intended to communicate with the NFC reader RD through a contactless protocol.
  • the application NAP may be an Identity application for example.
  • the secure element SC2 comprises a web server WS .
  • the web server WS comprises two applications Wl and W2.
  • the secure element SC2 comprises a SimToolkit (STK) engine SE .
  • STK SimToolkit
  • the application W2 is an application depending on the STK engine SE .
  • the application W2 uses the STK engine services through a BIP channel for returning the requested data to be displayed on the mobile phone display DI .
  • the application NAP comprises a means ME1 able to send a message Ml to the application NMI through the NFC controller NC .
  • the message Ml requests the sending of a second message M2 to the web server WS .
  • the application NMI comprises a means ME2 able to initiate the sending of the message M2 targeting the web server WS via the Bearer Independent Protocol (BIP) .
  • the means ME2 is adapted to send a message to the browser BR in response to the receipt of the message Ml.
  • the message sent to the browser BR requests the sending of the message M2 to the web server WS .
  • Figure 3 shows an example of step sequence for managing the communication between the application NAP and the application W2 according to the invention. Both the applications NAP and W2 are asynchronous.
  • the means ME2 of the application NMI uses a system call for launching the browser BR.
  • the system call aiming at launching the browser BR is triggered by the receipt of the message Ml .
  • the browser BR sends the message M2 to the web server WS through a local communication network based on a BIP channel.
  • the use of the local communication network based on BIP channel activates the STK engine SE .
  • This embodiment corresponds to an indirect call performed by the application NMI since the browser acts as an intermediary component.
  • the indirect call may be done by sending a first request to the browser BR.
  • the browser BR sends a second request to the web server WS .
  • the second request may target either the application Wl or the application W2.
  • the means ME2 may contain the following request: platformRequest ("HTTP : //127.0.0.1 : 3516/DisplayResult”) ; .
  • the message sent by the application NMI triggers the system browser BR.
  • the browser BR use the URL which is provided by the message of step S5B. This URL corresponds to an access to the application Wl .
  • the STK engine SE has been started in the secure element SC2. Further treatments may be performed by the application NAP and may lead to data exchange with the mobile phone MP2 elements via the STK engine SE .
  • the applications Wl and W2 may be merged in a single application.
  • the application NMI is not necessarily a midlet.
  • the application NMI may be any type of application capable of sending a message to either the browser BR or to the web server WS .
  • the application manager AM has been described for the example of midlets. Depending on the operating system framework, the application manager may be optional.
  • the invention applies whatever the type of operating system of the device connected to the secure element.
  • the invention is well-suited for cell phones using iOS ® for Iphone ®, Android OS ®, Symbian OS ®, Bada Mobile OS ®, Blackberry OS ® and Windows phone ®.
  • An advantage of the invention is to allow a NFC device to keep unchanged the polling mode of the Status messages. Since the frequency of the Status messages may be kept at a low rate, the communication means is not stressed. In addition, the invention allows removing superfluous status messages which reduce the communication bandwidth.
  • the invention provides a solution which is independent from the Status messages management scheme.
  • the application is not limited by design constraints related to the management of
  • the activation of the STK engine SE allows to unlock the display of data.
  • the mechanism of the invention may also be used for establishing a remote connection from the secure element to a distant server through the mobile phone.
  • the secure element may act as a client when establishing the connection.
  • the mechanism of the invention may also be used for launching a targeted application into the telecom equipment.
  • the mechanism of the invention may also be used for generating a sound or another event into the telecom equipment.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Human Computer Interaction (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention se rapporte à un procédé adapté pour gérer la communication entre des première et seconde entités asynchrones incorporées dans un élément sécurisé. La première entité est une application NFC. L'élément sécurisé comprend un serveur et un moteur STK, et est connecté d'autre part à un équipement de télécommunications comprenant un contrôleur NFC. La seconde entité dépend du moteur STK. Le procédé selon l'invention comprend les étapes consistant : - à envoyer un premier message, de la première entité à une seconde application comprise dans l'équipement de télécommunications, le premier message étant envoyé via le contrôleur NFC et sollicitant l'envoi d'un second message au serveur; - et, en réponse à la réception du premier message, à envoyer le second message au serveur via le BIP, dans le but d'activer le moteur STK, l'envoi du second message étant initié par la seconde application.
EP11784646.9A 2010-12-06 2011-11-15 Procédé pour la gestion d'entités asynchrones Withdrawn EP2649776A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP11784646.9A EP2649776A1 (fr) 2010-12-06 2011-11-15 Procédé pour la gestion d'entités asynchrones

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
EP10306354A EP2461551A1 (fr) 2010-12-06 2010-12-06 Procédé de gestion d'entités asynchrones
PCT/EP2011/070183 WO2012076301A1 (fr) 2010-12-06 2011-11-15 Procédé pour la gestion d'entités asynchrones
EP11784646.9A EP2649776A1 (fr) 2010-12-06 2011-11-15 Procédé pour la gestion d'entités asynchrones

Publications (1)

Publication Number Publication Date
EP2649776A1 true EP2649776A1 (fr) 2013-10-16

Family

ID=43945367

Family Applications (2)

Application Number Title Priority Date Filing Date
EP10306354A Withdrawn EP2461551A1 (fr) 2010-12-06 2010-12-06 Procédé de gestion d'entités asynchrones
EP11784646.9A Withdrawn EP2649776A1 (fr) 2010-12-06 2011-11-15 Procédé pour la gestion d'entités asynchrones

Family Applications Before (1)

Application Number Title Priority Date Filing Date
EP10306354A Withdrawn EP2461551A1 (fr) 2010-12-06 2010-12-06 Procédé de gestion d'entités asynchrones

Country Status (3)

Country Link
EP (2) EP2461551A1 (fr)
CN (1) CN103229492B (fr)
WO (1) WO2012076301A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104184699B (zh) 2013-05-21 2018-06-22 ***股份有限公司 安全性信息交互***、设备和方法
CN106550351B (zh) * 2015-09-22 2020-07-07 联芯科技有限公司 传输bip协议数据的方法及所适用的移动设备

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080121687A1 (en) * 2006-11-28 2008-05-29 Motorola, Inc. Method and system for detecting an end of transaction for contactless transactions on a mobile device
CN100580613C (zh) * 2008-01-30 2010-01-13 上海华虹集成电路有限责任公司 Nfc控制芯片与sim卡芯片间的连接与通讯方法
CN101887617B (zh) * 2010-07-13 2012-10-10 武汉天喻信息产业股份有限公司 一种用于移动支付的数据通道建立方法及***

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO2012076301A1 *

Also Published As

Publication number Publication date
CN103229492B (zh) 2015-01-14
WO2012076301A1 (fr) 2012-06-14
EP2461551A1 (fr) 2012-06-06
CN103229492A (zh) 2013-07-31

Similar Documents

Publication Publication Date Title
US8811896B2 (en) Non-volatile memory for contactless systems
Monteiro et al. A secure NFC application for credit transfer among mobile phones
US8861733B2 (en) Method of personalizing a NFC chipset
Reveilhac et al. Promising secure element alternatives for NFC technology
US20160360352A1 (en) Priority based routing of data on an electronic device
US9544020B2 (en) NFC negotiated pairing
RU2008116103A (ru) Устройство, система и способ сокращения времени взаимодействия при бесконтактной транзакции
KR20100040692A (ko) 스마트 카드 기반 애플릿 설치 시스템 및 그 방법
EP2645266A1 (fr) Dispositif mobile, système de transaction comprenant le dispositif mobile et procédé de transmission de signaux dans un dispositif mobile
CN105592403B (zh) 一种基于nfc的通信装置和方法
US20130273846A1 (en) Communication system
US9924302B2 (en) Mobile communication device and cloud-based computer system
Umar et al. Performance variation in host-based card emulation compared to a hardware security element
US20130179499A1 (en) Method, apparatus and system for displaying radio frequency identification application information
KR20050096930A (ko) 스마트카드와 서버 사이의 통신
US8083140B1 (en) System and method of over-the-air provisioning
EP2355368A1 (fr) Composant de télécommunication, système de communication sans fil et procédé pour coupler un dispositif de télécommunication mobile cellulaire à un terminal NFC
EP2177922A1 (fr) Procédé de test d'un document d'identité électronique et dispositif correspondant.
EP2461551A1 (fr) Procédé de gestion d'entités asynchrones
Roland et al. Comparison of the usability and security of NFC's different operating modes in mobile devices.
KR20170126543A (ko) 뱅킹앱을 이용한 브랜드캐시 자동충전 제공 방법
Urien et al. Securing NFC mobile services with cloud of secure elements (CoSE)
EP2632180A1 (fr) Procédé d'échange de données entre deux dispositifs mobiles
TWI539319B (zh) Security Information Exchange System, Equipment and Method Based on Secure Carrier Active Command
Lerner Mobile Technology and Security

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20130708

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

DAX Request for extension of the european patent (deleted)
GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

INTG Intention to grant announced

Effective date: 20141118

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20150331