EP2659445A2 - Système et procédé pour gérer un portefeuille mobile et ses authentifiants associés - Google Patents

Système et procédé pour gérer un portefeuille mobile et ses authentifiants associés

Info

Publication number
EP2659445A2
EP2659445A2 EP11852431.3A EP11852431A EP2659445A2 EP 2659445 A2 EP2659445 A2 EP 2659445A2 EP 11852431 A EP11852431 A EP 11852431A EP 2659445 A2 EP2659445 A2 EP 2659445A2
Authority
EP
European Patent Office
Prior art keywords
mobile
mobile device
information
wallet application
wma
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.)
Ceased
Application number
EP11852431.3A
Other languages
German (de)
English (en)
Other versions
EP2659445A4 (fr
Inventor
Yong Sung Kwon
Hyung Joon HONG
Ji Won Kang
Hyun Jin Kim
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.)
Mozido Corfire Korea Ltd
Original Assignee
SK C&C Co Ltd
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
Priority claimed from US13/310,091 external-priority patent/US8843125B2/en
Application filed by SK C&C Co Ltd filed Critical SK C&C Co Ltd
Publication of EP2659445A2 publication Critical patent/EP2659445A2/fr
Publication of EP2659445A4 publication Critical patent/EP2659445A4/fr
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/322—Aspects of commerce using mobile devices [M-devices]
    • G06Q20/3227—Aspects of commerce using mobile devices [M-devices] using secure elements embedded in M-devices
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/326—Payment applications installed on the mobile devices
    • G06Q20/3267—In-app payments
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
    • G06Q20/363—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes with the personal data of a user
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
    • G06Q20/367—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes involving electronic purses or money safes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/28—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP with meter at substation or with calculation of charges at terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/28—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP with meter at substation or with calculation of charges at terminal
    • H04M15/30—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP with meter at substation or with calculation of charges at terminal the meter or calculation of charges not being controlled from an exchange
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data

Definitions

  • the following description relates to management of virtual cards stored on mobile devices.
  • the SE may be a smart card chip capable of storing multiple applications, including of account specific information that may not be easily accessed by external parties.
  • the model mobile wallet application may have the same composition as a conventional wallet, which may contain payment cards, member cards, transportation cards, and loyalty cards.
  • NFC-based applications a method of providing contactless payment (NFC-based applications) through provisioning account specific information within the secure domain of the mobile device’s SE.
  • user financial credentials such as credit card numbers
  • NFC enabled Near Field Communication chipset
  • the provisioned NFC enabled device may transfer information or make payments to another NFC compatible device by coming near within a few centimeters of one another without physically contacting each other.
  • This type of technology is conventionally referred to as “contactless” technology and a payment made with this technology is referred to as “contactless” payment.
  • a contactless payment applet i.e., contactless payment virtual card
  • POS point-of-sale
  • a user may be limited to view the contactless payment applets stored in the user’s mobile device when interacting with a POS device.
  • the user may be unable to view the details related to the contactless payment applets (e.g., account number, expiration date, security code, balance and the like). Accordingly, users may be unable to effectively manage or keep track of various contactless payment applets stored in their respective mobile devices.
  • details related to the contactless payment applets e.g., account number, expiration date, security code, balance and the like. Accordingly, users may be unable to effectively manage or keep track of various contactless payment applets stored in their respective mobile devices.
  • the contactless card applets may be stored within a specific compartment, or a secured domain, of the SE to be accessed during an interaction with the POS device.
  • PPSE Payment Procedure Secure Elements
  • ID application identification
  • the user may be unable to view any account specific information stored within the SE or manage such applications with or without the use of POS equipment.
  • Another issue with the current mobile wallet application is its ability to update its information. As various service providers operate independently from one another, when an update is required by a particular service provider, each individual application is typically updated separately. Such inefficiency may dissuade users from obtaining crucial updates that may be necessary to a particular application.
  • Exemplary embodiments of the present invention provide a mobile device to store a mobile wallet application and a wallet management system (WMS) to store corresponding wallet application information.
  • Exemplary embodiments of the present invention provide a method for provisioning a wallet application, a contactless card applet, a wallet management applet (WMA), and a widget.
  • Exemplary embodiments of the present invention provide a method for synchronizing a mobile wallet application with the WMS.
  • Exemplary embodiments of the present invention provide a method for installing a wallet application in a mobile device including requesting, by the mobile device, a mobile wallet application comprising a corresponding Over-the-Air (OTA) proxy; receiving mobile wallet application installation information; installing the mobile wallet application in the mobile device; capturing mobile device information by using the OTA proxy, the mobile device information comprising secure element (SE) information; and transmitting the mobile device information for registering the installed mobile wallet application.
  • OTA Over-the-Air
  • Exemplary embodiments of the present invention provide a method for managing mobile wallet accounts installed on a mobile devices including receiving a request for a mobile wallet application from a mobile device; transmitting the mobile wallet application to the mobile device; receiving mobile device information, the mobile device information comprising SE information; and registering the mobile device and the corresponding mobile wallet application in a trusted service manager (TSM).
  • TSM trusted service manager
  • Exemplary embodiments of the present invention provide method for provisioning a contactless card applet in a mobile device comprising a mobile wallet application including activating the mobile wallet application; connecting to a TSM system; synchronizing the mobile wallet application with the TSM system; displaying a contactless card applet based on attributes of the mobile device; receiving a selection of a contactless card applet; retrieving a widget and a WMA corresponding to the contactless card applet; and provisioning the selected contactless card applet, widget, and the WMA.
  • Exemplary embodiments of the present invention provide a WMS in a non-transitory storage medium to store and manage mobile wallet account information including a wallet client management component to store and to manage a mobile wallet application; a widget management component to store and to manage widgets; a device profile management component to store mobile device information; and a rule engine to filter a widget based on the mobile device information.
  • Exemplary embodiments of the present invention provide a mobile device including a SE; a mobile wallet application to store a widget corresponding to a contactless card applet, wherein the contactless card applet is stored in the SE; a WMA corresponding to the contactless card applet, wherein WMA is stored in the SE; and an OTA proxy to provision the contactless card applet, a widget corresponding to the contactless card applet, and the WMA.
  • FIG. 1 is a system diagram of a mobile wallet application and associated integration in accordance with an exemplary embodiment of the present invention.
  • FIG. 2 is a system diagram illustrating a system and method for provisioning mobile card wallet management application along with supporting applications, mobile card widgets, contactless card applets, and related credentials in accordance with an exemplary embodiment of the present invention.
  • FIG. 3 is a system diagram illustrating a system and method for provisioning service provider specific mobile card widgets, contactless card applets, and wallet management application account information in accordance with an exemplary embodiment of the present invention.
  • FIG. 4 is a system diagram illustrating a system and method for dynamically filtering applicable mobile wallet service provider specific widgets based upon user account attributes in accordance with an exemplary embodiment of the present invention.
  • FIG. 5 is a system diagram illustrating a system and method for synchronizing mobile wallet application with the master mobile wallet configuration server to provide a most current version of the mobile wallet application in accordance with an exemplary embodiment of the present invention.
  • X, Y, and Z will be construed to mean X only, Y only, Z only, or any combination of two or more items X, Y, and Z (e.g. XYZ, XZ, YZ).
  • XYZ, XZ, YZ any combination of two or more items X, Y, and Z
  • FIG. 1 is a system diagram of a mobile wallet system and associated integration, according to an exemplary embodiment of the present invention.
  • an example system utilizing mobile wallet technology may include a mobile device 100, mobile wallet management system (WMS) 110, supporting Trusted Service Manager (TSM) system 120, Mobile Network Operator (MNO) 130, and Service Provider (SP) 140.
  • WMS mobile wallet management system
  • TSM Trusted Service Manager
  • MNO Mobile Network Operator
  • SP Service Provider
  • WMS 110 includes a wallet client management component 111, widget management component 112, device profile management component 113, user profile management component 114, data management component 115, and rule engine 116.
  • wallet client management component 111 is responsible for the wallet application itself (referred as the container), which may house the individual widgets (e.g., applications stored at the application level related to a financial institution, transportation account, and the like).
  • the wallet client management component 111 may store container specific information, including the type of wallet application and manufacturer.
  • wallet client management component 111 may recognize a user John has a mobile wallet application manufactured by Google® and has specified set of known functionalities. By managing the type of wallet application the user has on the mobile device, it may be possible to provide the same wallet application when necessary.
  • Widget management component 112 is responsible for the individual widgets stored within the wallet container. Widgets may be an application configured to interface with a user of the mobile device. In an example, widgets may refer to individual payment applications, transportation applications, and other related applications.
  • Device Profile management component 113 houses a memory to store one or more programs, such as applications, and other related information. Device Profile management component 113 may store device specific information, such as information related to the mobile device itself including type of mobile device, supporting operating system (OS), mobile service provider, and other relevant information.
  • OS operating system
  • User Profile management component 114 captures user identifying information such as name, address, birthday, phone number, and the like.
  • Data Management component 115 allows further expansion of data management services offered by a mobile WMS (e.g., transaction history, user preferences, loyalty programs, digital receipts, digital coupons and the like). Rule engine 116 may filter widgets based on information related to the mobile device. Although various components were illustrated to be included in the WMS 110, the configuration of WMS 110 is not limited thereto. The illustrated components may be included within the WMS 110 or external to the WMS 110.
  • the disclosed WMS 110 may reside within TSM system 120 or independent of the TSM system 120. For the purposes of this disclosure, it will be assumed that the WMS 110 is housed within the TSM system 120. Like the TSM system 120, WMS 110 may interact with MNO 130 to transmit and receive billing related information. Further, WMS 110 may interact with SP 140 to receive and transmit SP payment card information.
  • the TSM system 120 may refer to a third party entity positioned to consolidate various information from various service providers including, financial institutions, MNOs, handset manufacturers, and card manufacturers. As TSM system 120 may hold various information from various parties, the mobile device may interact with the TSM system individually rather than various discrete entities. Accordingly, the described TSM system 120 may act as an integration point for all of the external parties the mobile device may deal with, providing for a seamless and more efficient operation of mobile services.
  • FIG. 2 is a system diagram illustrating a system and method for installing a mobile wallet application on the mobile device and correlating wallet management applet in the SE of the mobile device in accordance with an exemplary embodiment of the present invention.
  • the mobile device 100 requests a new mobile wallet application 24.
  • a SP 140 may request installation of the mobile wallet application 24 from the TSM system 120.
  • the TSM system 120 may wait for the mobile device 100 to connect to the TSM system 120 before installing the mobile wallet application 24.
  • the TSM system 120 may install the mobile wallet application 24 directly upon connection to the mobile device 100 or wait until the user approves the request to install the mobile wallet application 24.
  • a corresponding widget representing a virtual card such as a virtual credit card, may be provisioned to reside within the respective mobile wallet application 24.
  • the widget representing the virtual card may reside within the mobile wallet application 24.
  • the TSM system 120 receives the mobile wallet application installation request and corresponding identification information and checks for duplicate records existing in the TSM system 120. If it is determined that the requesting customer is a new customer, a new record is created within the TSM system 120. If the customer information already exists, TSM system 120 may verify the existing customer and update the customer’s information, if applicable.
  • the TSM system 120 After a customer account has been created or updated, if it is determined that the mobile wallet application 24 is not installed on the mobile device 100, the TSM system 120 will confirm the mobile wallet application installation request and initiate the wallet application installation process.
  • the installation process may be initiated by transmitting a Wireless Application Protocol (WAP) message with an embedded Uniform Resource Locator (URL) to the Short Message Service (SMS) platform in step 203, which relays the message to the mobile device 100 in step 204.
  • WAP Wireless Application Protocol
  • URL Uniform Resource Locator
  • SMS Short Message Service
  • the mobile wallet application 24 may be obtained in various other ways as well and is not limited to the WAP message method as described above.
  • the mobile wallet application 24 may be downloaded directly to the requesting mobile device 100, sent to the user in a physical medium storing the application, or by other suitable methods for providing software applications.
  • the user upon receipt of the installation message from the SMS platform, may initiate the actual installation process by sending a request to the TSM system 120 in step 205.
  • TSM system 120 transmits the requested mobile wallet application 24 to mobile device 100 for installation and an accompanying over-the-air (OTA) proxy program to allow OTA provisioning in step 206.
  • OTA over-the-air
  • the mobile wallet application 24 may be launched by the requesting user in step 207. Alternatively, the mobile wallet application 24 may be launched automatically once it is downloaded. Also, in the event OTA proxy is already downloaded or installed, the mobile wallet application 24 may be downloaded independently of the OTA proxy. Although not illustrated, the accompanying OTA proxy may be included in the mobile wallet application 24.
  • the OTA proxy captures the mobile device information (e.g. International Mobile Equipment Identity (IMEI)/Mobile Equipment Identifier (MEID), Mobile Subscriber Integrated Services Digital Network Number (MSISDN)), including SE information (e.g. Card Production Life Cycle (CPLC), Card Serial Number (CSN), Card Image Number (CIN), Integrated Circuit Card Identification (ICCID)), which may be stored in a device memory component of the mobile device 100.
  • the OTA proxy may be a separate component from the mobile wallet application 24, or may be included in the mobile wallet application 24.
  • the OTA proxy sends the captured SE and mobile device information to the TSM system 120, which may house a WMS 110 (as shown in Fig. 2) or be in communication with an external WMS 110 (as shown in Fig. 1).
  • the TSM system 120 may house a WMS 110 (as shown in Fig. 2) or be in communication with an external WMS 110 (as shown in Fig. 1).
  • the WMS 110 upon receipt of the information provided by the OTA proxy, creates a Mobile identification (ID) for the installed mobile wallet application 24 in step 210.
  • ID Mobile identification
  • the WMS 110 requests TSM system 120 to provision a corresponding wallet management applet (WMA) 21 with the following information via OTA proxy: CPLC or CSN, CIN, Mobile ID and WMA personalization data.
  • WMA 21 may include both a WMA 21 container and one or more WMA 21 applets.
  • WMA 21 container may manage the information stored in the WMA 21 applets.
  • WMA 21 container may be installed in the mobile device 100 when WMA 21 applet is requested to be installed, or when the mobile wallet application is installed, or separately without regard to either the WMA 21 applet or the mobile wallet application.
  • the WMA 21 container is a software application that may reside within the SE of the mobile device 100 to manage account information related to the contactless card applet 23 (i.e. WMA 21 applet) that may be typically inaccessible by the user.
  • the SE may store one or more contactless card applets that may be used through a mobile device 100 with NFC capability, but the contactless card applets may largely be inaccessible by the user. More specifically, during a financial transaction, the NFC enabled mobile device may transmit contactless card information, which may include account specific information to a POS device to complete the transaction.
  • account specific information may include credit card number, expiration date, security code (e.g., a combination of numbers typically found on back of credit cards), personal identification number (PIN) (e.g., a combination of numbers typically used to conduct financial transactions with the user’s financial institution), and other related information.
  • security code e.g., a combination of numbers typically found on back of credit cards
  • PIN personal identification number
  • separate account information associated with the corresponding contactless card applet 23 may be provisioned into the SE as WMA 21 applets.
  • the respective account information or WMA 21 applet may be provided by duplicating the account information associated with the contactless card when the TSM system receives contactless card applets from SPs to provision into the mobile device 100.
  • SP providing the contactless card applet may provide the account related information separately to the TSM system for provisioning.
  • TSM system 120 sends a wake up message to the mobile push server (e.g. Cloud to Device Messaging (C2DM)) with a mobile device identifier to wake up OTA proxy residing in the requesting mobile device 100.
  • the mobile push server e.g. Cloud to Device Messaging (C2DM)
  • C2DM Cloud to Device Messaging
  • the mobile push server routes the received message to the mobile wallet application 24, which in turn sends the request to OTA proxy and wakes OTA proxy in step 212.
  • the OTA proxy gathers mobile device and SE specific information such as MSISDN and CIN and sends it over to TSM system 120.
  • OTA proxy gathers mobile device and SE specific information to send to TSM system 120 every time it is woken up. Alternatively, this step may be skipped and the mobile device and SE information provided in step 209 to register the mobile device 100 and the wallet application may be used.
  • TSM system 120 receives the information sent by OTA Proxy in step 213, TSM system 120 processes the information and converts the identifying information along with the request to provision WMA 21 container into Application Protocol Data Unit (APDU) commands in step 214 and sends them over to OTA proxy in step 215.
  • APDU Application Protocol Data Unit
  • OTA proxy receives the APDU commands to install WMA 21 container and relays them to the SE, which processes the APDU commands to install the requested WMA 21 container and its associated credentials. SE then responds back with the result of each command request in step 217.
  • WMA 21 container, PPSE 22, and Contactless Card Applet 23 are shown as being part of mobile device 100, an ordinarily skilled artisan understands that these elements may not be present on the SE of the mobile device 100 until they are installed.
  • OTA Proxy relays the result back to the TSM system 120 in step 218, and the TSM system 120 updates its system with the result.
  • the user may provision SP 140 specific contactless card applets 23, and its corresponding widget applications and WMA 21 applet onto mobile device 100.
  • FIG. 3 is a system diagram illustrating a method for installing a mobile widget into the mobile wallet application 24 and its corresponding contactless card applet and account information into the SE of the requesting mobile device in accordance with an exemplary embodiment of the present invention.
  • step 301 the user logs into the mobile wallet application 24 to start the mobile wallet application 24 for use.
  • the mobile wallet application 24 connects to the TSM system 120, which may house WMS 110, for synchronization in step 302.
  • TSM system 120 which may house WMS 110
  • TSM system 120 checks for any updated information made by external parties (e.g. SP 140, user by web access, TSM system 120 administrator, and/or etc.) and sends the list of waiting updates to the mobile wallet application 24 in step 303. Further, additional applications that user may be interested in may be displayed for download through dynamic filtering. The applicable applications based on user attributes will be displayed through this filtering process. A more detailed description of how this dynamic filtering works is provided below with reference to FIG. 4.
  • the mobile device user is prompted to decide whether to update the mobile wallet application 24 with the changes made at the TSM system 120, if any, in step 304.
  • the mobile device may update the mobile wallet application 24 automatically with the respective changes in step 304.
  • a request is made to the TSM system 120/WMS 110 to provision the updates and/or selected card applications in step 305. If a request to update requires updating of account specific information, such as change in account number or expiration date, the process to update the application will follow the same steps regardless of the information being updated.
  • a corresponding widget and WMA 21 applet may be programmed to be provisioned automatically.
  • the corresponding widget may reside in the mobile wallet application 24, at the application level, to provide an interface to the user.
  • the corresponding WMA 21 applet which may include account specific information of the contactless card apple (e.g. credit card number, expiration date, security code, PIN, etc.), may be provisioned into the SE.
  • TSM system 120 processes the provisioning request and sends a wake up message request to the mobile push server in step 306, and the push server proceeds to relay the request the mobile wallet application 24, which in turn sends the message to OTA proxy, thereby waking OTA proxy in step 307.
  • OTA proxy wakes up and gathers mobile device and SE specific information, such as MSISDN and CIN, and sends the collected information to TSM system 120.
  • TSM system 120 processes the received information along with the provisioning command and converts both the received information along with the provisioning command into APDU commands to send to OTA proxy in step 309.
  • the contactless card applet and the corresponding WMA 21 applet are sent to OTA proxy for provisioning into the SE.
  • the widget since the widget is provisioned at the application level and not into the SE, the widget may be provisioned through the OTA proxy or through a wireless network.
  • OTA proxy receives the APDU commands from the TSM system 120 to install requested issuer contactless applets 23 and correlating WMA 21 applet to be provisioned.
  • contactless applets 23 and correlating WMA 21 applet are provided in different domains of the same SE.
  • SE processes the APDU commands for both the contactless applet and the WMA 21 applet and sends back the result of each command request in step 311.
  • APDU commands may be processed one at a time, multiple communications may be passed back and forth between the OTA proxy and the SE.
  • OTA Proxy relays the result back to the TSM system 120 in step 312, and the TSM system 120 updates its system with the result of the request in step 313.
  • notification of the results is sent to SP 140 in step 314.
  • the mobile wallet application 24 notifies TSM system 120 of the result of the widget installation. For example, the mobile wallet application 24 will notify the TSM system 120 whether the widget installation was a success or a failure.
  • the respective mobile device 100 may access the information periodically for required updates.
  • the mobile device 100 may access the information stored in the WMA 21 applet using the mobile wallet application 24 to check for the expiration dates of the contactless card applets 23 stored within the mobile device 100 and prompt user for updates as necessary.
  • the mobile wallet application 24 may check for updates automatically.
  • the user may also gain access to the account number, security code, and corresponding expiration date as necessary to make purchases online for further utility.
  • the information stored in the WMA 21 applet may allow the mobile device 100 to check the expiration date of the contactless card applet 23 and request update when the card applet expires.
  • WMA 21 container may, however, limit amount of change requests to the WMA 21 applet as they contain account specific information. For example, the number of times expiration date may be changed with a reference time period may be limited, or changes to the credit card numbers may be prohibited.
  • WMA 21 container may prevent user from making changes directly in the WMA 21 applet but allow request for modification to the TSM system 120, which in turn will make the request to the relevant external parties. While the described process illustrates a preferred embodiment of the present invention, the amount of modification allowed by the WMA 21 container is not limited to what has been described. In some instances, WMA 21 container may allow direct modification to the account specific information as dictated by business needs.
  • FIG. 4 is a system diagram illustrating a method for dynamically filtering a list of mobile widget applications that are available for installation based upon corresponding mobile device attributes in accordance with an exemplary embodiment of the present invention.
  • step 401 the user logs into the mobile wallet application 24, which seeks to connect with the TSM system 120/WMS 110.
  • the TSM system 120 receives the connection request through a mobile gateway residing within the TSM system 120 and relays the request to a Rule Engine in TSM system 120 in step 402.
  • the TSM system 120 queries the user account in its system in step 403 for equipment information, MNO, SP accounts, and any other relevant information.
  • a filtered list of downloadable applications from the TSM system 120 may be displayed to the mobile device.
  • mobile device 100 attributes may include, without limitation, the mobile network provider of the mobile device 100 (e.g. “Sprint®,” “Verizon®”, “AT&T®”, etc.), financial institutions associated with the contactless card applets stored (e.g.
  • TSM system 120 may house a large list of available applications, including contactless card applets 23, as illustrated in FIG. 4.
  • TSM system 120 may house various applications without regard to the device capabilities, SPs’ relationship with other SPs, or other limitations that may be inherent in the business or technical environments.
  • TSM system 120 may dynamically filter the list of available applications based upon the mobile device attributes described above.
  • the applets provided by the SP may be compatible with the user mobile device or user’s MNO. Because of lack of standardization of hardware and software on mobile devices, an efficient method to filter only the relevant applets is helpful. Along with these technical limitations, many MNOs and SPs may decide not to provide their services to each other for business reasons. As the general public may not be familiar with such knowledge, an additional filtering mechanism may be provided to provide only the applicable applets to the requesting user. In an example, all of the provided limitations may be managed and applied by the Rule Engine in the TSM system 120. The Rule Engine may be housed in the TSM system 120 or may exist as an external entity, which interacts with TSM system 120 through a network.
  • the Rule Engine may be a combination of software and hardware, software to apply and manage the rules and hardware to store the relevant rules. Accordingly, by providing an active dynamic filtering mechanism at the TSM system 120 level, all of the parties involved in such transaction need to make only a general request to the TSM system 120 to access and to provide customer specific services.
  • TSM system 120 sends the list of applets to display to the mobile gateway in step 404, which relays it back to the mobile wallet application 24 in step 405.
  • FIG. 5 a system diagram is provided for synchronizing the mobile wallet application residing within the mobile device with the TSM system in accordance with an exemplary embodiment of the present invention.
  • a centralized management or storage may be beneficial to maintain a master file of the user wallet configuration.
  • step 501 multiple external parties, such as credit card service providers as illustrated in FIG. 5, may send a request for changes to be made to the user’s mobile wallet configuration directly to the TSM system 120/WMS 110, which may store the master configuration of the respective mobile wallet application 24.
  • TSM system 120 administrators and the user themselves may access the TSM system 120 via web access or any other remote access functionality.
  • a central repository allows external parties to make the necessary requests without regard to user’s mobile wallet application 24’s operating status.
  • SPs 140 may request an additional contactless card applet 23 to be provisioned to the user’s SE on their own time without regard to the mobile wallet application 24’s operating status.
  • TSM system 120 itself may recognize that the expiration date of the respective application is coming up and prompt the user to update the card for provisioning when the mobile wallet application 24 connects to the system.
  • the requesting party may be any external party to the TSM system 120.
  • step 502 when the user logs into the mobile wallet application 24, the mobile wallet application 24 checks with the TSM system 120/WMS 110 for any modifications to the wallet configuration since the last login by the user. As the mobile wallet application 24 synchronizes every time the application is logged into, the user can be sure that the user has access to the most current information during use. In addition, by limiting synchronization events to access of mobile wallet application 24, secure access to sensitive information is provided only when the user is utilizing the mobile wallet application 24. However, if desired, mobile wallet application 24 may always be in sync by automatically whenever mobile device is on and has mobile signal.
  • Any updates made in the WMS 110 while mobile wallet application 24 was offline will be prompted for the user to make the updates in step 503.
  • User may update one application at a time or all at once if such is desired. Also, the user may set the application to automatically update every change made in the TSM system 120/WMS 110 at synchronization.
  • step 504 while mobile wallet application 24 is still active, any modifications that are made in the mobile wallet application 24 itself will be updated in the WMS 110 in step 505 as synchronization is a continuous one during usage. For example, if the user changes a user preference on the mobile wallet application 24, changes to the user preference may be updated into the WMS 110 in real time. Similarly, if the mobile device 110 prompts the user to update the expiration date of the contactless applet and the user agrees, user’s request will be submitted to TSM system 120, which will process the request and route it to SP 140 for processing.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • General Business, Economics & Management (AREA)
  • Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Finance (AREA)
  • Signal Processing (AREA)
  • Telephone Function (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

La présente invention se rapporte à un procédé permettant de fournir un applet de carte sans contact dans un dispositif mobile avec une application de portefeuille mobile. Le procédé selon l'invention consiste : à activer l'application de portefeuille mobile ; à se connecter à un système de gestionnaire de services de confiance (TSM, Trusted Service Manager) ; à synchroniser l'application de portefeuille mobile par rapport au système TSM ; à afficher un applet de carte sans contact sur la base d'attributs du dispositif mobile ; à recevoir une sélection d'un applet de carte sans contact ; à retrouver un composant d'interface graphique (widget) et un applet de gestion de portefeuille (WMA, Wallet Management Applet) correspondant à l'applet de carte sans contact ; et à fournir l'applet de carte sans contact sélectionné, le composant d'interface graphique et le WMA. La présente invention se rapporte d'autre part à un système de gestion de portefeuille (WMS, Wallet Management System) dans un support de stockage non transitoire. Le système de gestion de portefeuille selon l'invention est apte à stocker et à gérer des informations de compte de portefeuille mobile comprenant un élément de gestion de client de portefeuille, un élément de gestion de composant d'interface graphique, un élément de gestion de profil de dispositif et un moteur de règles.
EP11852431.3A 2010-12-30 2011-12-20 Système et procédé pour gérer un portefeuille mobile et ses authentifiants associés Ceased EP2659445A4 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US201061428846P 2010-12-30 2010-12-30
US13/310,091 US8843125B2 (en) 2010-12-30 2011-12-02 System and method for managing mobile wallet and its related credentials
PCT/KR2011/009866 WO2012091349A2 (fr) 2010-12-30 2011-12-20 Système et procédé pour gérer un portefeuille mobile et ses authentifiants associés

Publications (2)

Publication Number Publication Date
EP2659445A2 true EP2659445A2 (fr) 2013-11-06
EP2659445A4 EP2659445A4 (fr) 2016-10-12

Family

ID=46383643

Family Applications (1)

Application Number Title Priority Date Filing Date
EP11852431.3A Ceased EP2659445A4 (fr) 2010-12-30 2011-12-20 Système et procédé pour gérer un portefeuille mobile et ses authentifiants associés

Country Status (6)

Country Link
EP (1) EP2659445A4 (fr)
KR (2) KR20130116905A (fr)
CN (1) CN103270526A (fr)
AU (1) AU2011350195A1 (fr)
SG (1) SG190987A1 (fr)
WO (1) WO2012091349A2 (fr)

Families Citing this family (68)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101572768B1 (ko) 2007-09-24 2015-11-27 애플 인크. 전자 장치 내의 내장형 인증 시스템들
US8600120B2 (en) 2008-01-03 2013-12-03 Apple Inc. Personal computing device control using face detection and recognition
US9002322B2 (en) 2011-09-29 2015-04-07 Apple Inc. Authentication with secondary approver
US8769624B2 (en) 2011-09-29 2014-07-01 Apple Inc. Access control utilizing indirect authentication
KR101515768B1 (ko) 2011-11-01 2015-04-28 제이브이엘 벤쳐스, 엘엘씨 보안 요소를 관리하기 위한 시스템, 방법 및 컴퓨터 프로그램 제품
EP2610799A1 (fr) * 2011-12-28 2013-07-03 Research In Motion Limited Dispositif de communication mobile fournissant des fonctions d'émission de carte de communication à champ proche et procédés associés
US9154903B2 (en) 2011-12-28 2015-10-06 Blackberry Limited Mobile communications device providing near field communication (NFC) card issuance features and related methods
US9563891B2 (en) 2012-07-09 2017-02-07 Google Inc. Systems, methods, and computer program products for integrating third party services with a mobile wallet
US8676709B2 (en) 2012-07-31 2014-03-18 Google Inc. Merchant category codes in a proxy card transaction
KR101793664B1 (ko) 2012-09-18 2017-11-06 구글 엘엘씨 복수의 서비스 제공자 신뢰 서비스 관리기들과 보안 요소들을 인터페이싱하기 위한 시스템들, 방법들, 및 컴퓨터 프로그램 제품들
US9947001B2 (en) * 2013-03-15 2018-04-17 Mastercard International Incorporated System and method for using multiple payment accounts using a single payment device
WO2014158331A1 (fr) * 2013-03-26 2014-10-02 Jvl Ventures, Llc Systèmes, procédés et produits de programmes informatiques permettant de gérer l'activation de portefeuilles
WO2014189569A1 (fr) 2013-05-21 2014-11-27 Jvl Ventures, Llc Systèmes, procédés et produits de programmes informatiques pour gérer des états
US9408075B2 (en) * 2013-06-17 2016-08-02 Google Inc. Systems, methods, and computer program products for processing a request relating to a mobile communication device
KR102168922B1 (ko) * 2013-06-26 2020-10-22 삼성전자 주식회사 모바일 기기 간 월렛 전송 방법 및 장치
US9898642B2 (en) 2013-09-09 2018-02-20 Apple Inc. Device, method, and graphical user interface for manipulating user interfaces based on fingerprint sensor inputs
KR102405189B1 (ko) 2013-10-30 2022-06-07 애플 인크. 관련 사용자 인터페이스 객체를 표시
CN104715368A (zh) * 2013-12-16 2015-06-17 中国移动通信集团公司 电子钱包注销方法、装置、系统和相关设备
US10003969B2 (en) 2013-12-19 2018-06-19 Google Llc Communication between mobile devices and mobile wallet architectures
US11068875B2 (en) * 2013-12-30 2021-07-20 Apple, Inc. Person-to-person payments using electronic devices
WO2015102456A1 (fr) * 2014-01-06 2015-07-09 에스케이플래닛 주식회사 Procédé de fourniture de service en utilisant un appareil de balise, et système et appareil pour celui-ci
KR20150123551A (ko) * 2014-04-25 2015-11-04 모지도코화이어코리아 유한회사 Hce를 활용한 모바일 카드 서비스 방법 및 이를 적용한 모바일 단말
CN206193906U (zh) * 2014-05-29 2017-05-24 苹果公司 电子设备
US10482461B2 (en) 2014-05-29 2019-11-19 Apple Inc. User interface for payments
US11120442B2 (en) * 2014-06-20 2021-09-14 Apple Inc. Management of reloadable credentials on an electronic device using an online resource
US10339293B2 (en) 2014-08-15 2019-07-02 Apple Inc. Authenticated device used to unlock another device
US10066959B2 (en) 2014-09-02 2018-09-04 Apple Inc. User interactions for a mapping application
US9547419B2 (en) 2014-09-02 2017-01-17 Apple Inc. Reduced size configuration interface
US20160224973A1 (en) 2015-02-01 2016-08-04 Apple Inc. User interface for payments
WO2016129863A1 (fr) 2015-02-12 2016-08-18 Samsung Electronics Co., Ltd. Procédé de traitement de paiement et dispositif électronique prenant en charge ledit procédé
US9574896B2 (en) 2015-02-13 2017-02-21 Apple Inc. Navigation user interface
EP3059918B1 (fr) * 2015-02-23 2018-12-12 Giesecke+Devrient Mobile Security GmbH Procédé pour accéder à un élément de sécurité
KR102460459B1 (ko) 2015-02-27 2022-10-28 삼성전자주식회사 전자 장치를 이용한 카드 서비스 방법 및 장치
WO2016137300A1 (fr) * 2015-02-27 2016-09-01 Samsung Electronics Co., Ltd. Dispositif électronique fournissant une fonction de paiement électronique et son procédé de fonctionnement
US10193700B2 (en) 2015-02-27 2019-01-29 Samsung Electronics Co., Ltd. Trust-zone-based end-to-end security
US11107047B2 (en) 2015-02-27 2021-08-31 Samsung Electronics Co., Ltd. Electronic device providing electronic payment function and operating method thereof
US10254911B2 (en) 2015-03-08 2019-04-09 Apple Inc. Device configuration user interface
US10878407B1 (en) * 2015-04-17 2020-12-29 Jpmorgan Chase Bank, N.A. Systems and methods for facilitating payment application provisioning and transacting
CN105590201B (zh) * 2015-04-23 2019-05-10 中国银联股份有限公司 移动支付装置及移动支付系统
US20160358133A1 (en) 2015-06-05 2016-12-08 Apple Inc. User interface for loyalty accounts and private label accounts for a wearable device
US9940637B2 (en) 2015-06-05 2018-04-10 Apple Inc. User interface for loyalty accounts and private label accounts
CN105185002B (zh) * 2015-09-09 2018-06-12 建亿通（北京）数据处理信息有限公司 移动终端、业务平台及卡片业务系统
SG10201508866SA (en) * 2015-10-27 2017-05-30 Mastercard International Inc Method for predicting purchasing behaviour of digital wallet users for wallet-based transactions
CN105631949A (zh) * 2016-03-30 2016-06-01 周勇 一种智能公共汽车收费系统
EP3247136A1 (fr) 2016-05-16 2017-11-22 Gemalto Sa Procédé d'approvisionnement d'une mini-application de justificatifs d'identité d'une application de terminal fournie par un serveur d'application et plate-forme ota correspondante
DK179186B1 (en) 2016-05-19 2018-01-15 Apple Inc REMOTE AUTHORIZATION TO CONTINUE WITH AN ACTION
CN109313759B (zh) 2016-06-11 2022-04-26 苹果公司 用于交易的用户界面
US10621581B2 (en) 2016-06-11 2020-04-14 Apple Inc. User interface for transactions
DK201670622A1 (en) 2016-06-12 2018-02-12 Apple Inc User interfaces for transactions
CN106875186B (zh) * 2016-06-20 2020-07-24 阿里巴巴集团控股有限公司 一种离线支付方法和装置
US20180068313A1 (en) 2016-09-06 2018-03-08 Apple Inc. User interfaces for stored-value accounts
US10860199B2 (en) 2016-09-23 2020-12-08 Apple Inc. Dynamically adjusting touch hysteresis based on contextual data
DK179978B1 (en) 2016-09-23 2019-11-27 Apple Inc. IMAGE DATA FOR ENHANCED USER INTERACTIONS
US10496808B2 (en) 2016-10-25 2019-12-03 Apple Inc. User interface for managing access to credentials for use in an operation
EP3616148B1 (fr) * 2017-06-02 2024-01-24 Apple Inc. Fourniture de comptes de carte sur la base d'une notification
KR102185854B1 (ko) 2017-09-09 2020-12-02 애플 인크. 생체측정 인증의 구현
EP4156129A1 (fr) 2017-09-09 2023-03-29 Apple Inc. Mise en oeuvre de l'enregistrement biométrique
CN110062016B (zh) * 2018-01-18 2023-05-09 阿里巴巴集团控股有限公司 用于可信服务管理的方法及装置
US11170085B2 (en) 2018-06-03 2021-11-09 Apple Inc. Implementation of biometric authentication
US11100349B2 (en) 2018-09-28 2021-08-24 Apple Inc. Audio assisted enrollment
US10860096B2 (en) 2018-09-28 2020-12-08 Apple Inc. Device control using gaze information
US11328352B2 (en) 2019-03-24 2022-05-10 Apple Inc. User interfaces for managing an account
US11481094B2 (en) 2019-06-01 2022-10-25 Apple Inc. User interfaces for location-related communications
US11477609B2 (en) 2019-06-01 2022-10-18 Apple Inc. User interfaces for location-related communications
US11169830B2 (en) 2019-09-29 2021-11-09 Apple Inc. Account management user interfaces
AU2020356269B2 (en) 2019-09-29 2023-04-06 Apple Inc. Account management user interfaces
DK202070633A1 (en) 2020-04-10 2021-11-12 Apple Inc User interfaces for enabling an activity
US11816194B2 (en) 2020-06-21 2023-11-14 Apple Inc. User interfaces for managing secure operations

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7822688B2 (en) * 2002-08-08 2010-10-26 Fujitsu Limited Wireless wallet
US8341088B2 (en) * 2004-06-30 2012-12-25 France Telecom Multipurpose electronic payment method and system
JP2007226684A (ja) * 2006-02-24 2007-09-06 Fujitsu Ltd サービス提供サーバ、情報端末、サービス提供方法およびサービス提供プログラム
US7469151B2 (en) * 2006-09-01 2008-12-23 Vivotech, Inc. Methods, systems and computer program products for over the air (OTA) provisioning of soft cards on devices with wireless communications capabilities
KR101000195B1 (ko) * 2007-11-15 2010-12-10 주식회사 엘지유플러스 모바일 디바이스 및 상기 모바일 디바이스의 모바일 위젯 서비스 제공 방법
US8949937B2 (en) 2008-06-24 2015-02-03 Nxp, B.V. Method of accessing applications in a secure mobile environment
AU2009302485C1 (en) * 2008-10-06 2015-10-22 Mastercard International, Inc. Systems, methods, and computer readable media for payment and non-payment virtual card transfer between mobile devices
US8725122B2 (en) * 2009-05-13 2014-05-13 First Data Corporation Systems and methods for providing trusted service management services

Also Published As

Publication number Publication date
EP2659445A4 (fr) 2016-10-12
AU2011350195A1 (en) 2013-06-20
CN103270526A (zh) 2013-08-28
WO2012091349A3 (fr) 2012-10-04
WO2012091349A2 (fr) 2012-07-05
KR20150094792A (ko) 2015-08-19
KR20130116905A (ko) 2013-10-24
SG190987A1 (en) 2013-07-31

Similar Documents

Publication Publication Date Title
WO2012091349A2 (fr) Système et procédé pour gérer un portefeuille mobile et ses authentifiants associés
US8843125B2 (en) System and method for managing mobile wallet and its related credentials
WO2012091351A2 (fr) Système et procédé pour assurer la transmission de données confidentielles en liaison radio, sur des dispositifs de communication mobiles avec des éléments sécurisés non uicc
RU2630419C2 (ru) Интегрированный мобильный доверенный менеджер услуг
EP2211480B1 (fr) Dispositif de communication sans fil pour fournir au moins un service de communication à champ proche
EP2852070B1 (fr) Dispositif de communication sans fil pour fournir au moins un service de communication à champ proche
US20130262302A1 (en) Systems, methods, and computer program products for provisioning payment accounts into mobile wallets and managing events
US9940618B2 (en) Method and apparatus for transmitting wallets between mobile devices
US9918347B2 (en) Wireless communication apparatus, information processing apparatus, communication system, and communication method
US20100275269A1 (en) Procedure for the preparation and performing of a post issuance process on a secure element
WO2012091350A2 (fr) Système et procédé pour un confinement sécurisé de données financières sensibles enregistrées dans un terminal de communication mobile
US20220286861A1 (en) Subscriber Identity Module (SIM) Remote Update Agent
CA2834625C (fr) Reseau de communication, systeme informatique, methode implantee par ordinateur et produit de programme informatique pour fournir une infrastructure a base de femtocellule pour le paiement electronique mobile
EP2816517A1 (fr) Procédé et appareil pour combiner différents types de portefeuilles sur un dispositif mobile
CN101379844A (zh) 在智能卡的控制下由无线电通信网络向移动终端传送的专有信息的使用
CN107124760B (zh) Apn信息的收集及同步方法、终端设备及存储介质
CN101867918A (zh) 实名制登记状态的获取方法和装置、以及终端
KR101561534B1 (ko) 프로파일 사용과 데이터 준비를 통한 어플리케이션 ｏｔａ 프로비저닝 관리 시스템 및 방법
CN101753590A (zh) 一种用于远程管理应用的装置和方法
CN104217331A (zh) 一种客户端前置及移动支付系统
JP2013125444A (ja) 登録手続き作業軽減システム及び仲介事業者サーバ並びにその方法及びそのプログラム

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: 20130611

AK Designated contracting states

Kind code of ref document: A2

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)
RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: MOZIDO CORFIRE - KORCA, LTD.

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: MOZIDO CORFIRE - KOREA, LTD.

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: MOZIDO CORFIRE - KOREA, LTD.

A4 Supplementary search report drawn up and despatched

Effective date: 20160909

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 8/22 20090101ALI20160905BHEP

Ipc: H04M 15/28 20060101ALI20160905BHEP

Ipc: H04M 15/30 20060101ALI20160905BHEP

Ipc: H04W 4/24 20090101ALI20160905BHEP

Ipc: H04B 5/02 20060101ALI20160905BHEP

Ipc: G06Q 20/32 20120101AFI20160905BHEP

Ipc: H04W 8/24 20090101ALI20160905BHEP

Ipc: G06Q 20/36 20120101ALI20160905BHEP

Ipc: H04W 60/00 20090101ALI20160905BHEP

17Q First examination report despatched

Effective date: 20170818

REG Reference to a national code

Ref country code: DE

Ref legal event code: R003

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

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED

18R Application refused

Effective date: 20190618