SYSTEM AND METHOD FOR MANAGING OTA PROVISIONING APPLICATIONS THROUGH USE OF PROFILES AND DATA PREPARATION

• US 20120174189A1
• Filed: 12/02/2011
• Published: 07/05/2012
• Est. Priority Date: 12/30/2010
• Status: Active Grant

• Current Assignee: Mozido Corfire-Korea Limited
• Original Assignee: SK C&C Company Limited (SK Inc.)
• Inventors: LIM, Jaemin, KWON, Daeman, KIM, Donghyun, JEON, Byungkwon
• Granted Patent: US 9,191,813 B2
• Time in Patent Office: Days
• US Class Current: 726/3
• CPC Class Codes: G06F 21/34 involving the use of external additional devices, e.g. dongles or smart cards
• CPC Class Codes: G06F 21/35 communicating wirelessly
• CPC Class Codes: G06F 21/57 Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
• CPC Class Codes: G06F 21/88 Detecting or preventing theft or loss
• CPC Class Codes: G06F 2221/2153 Using hardware token as a secondary aspect
• CPC Class Codes: G06Q 20/3227 using secure elements embedded in M-devices
• CPC Class Codes: G06Q 20/3263 characterised by activation or deactivation of payment capabilities
• CPC Class Codes: G06Q 20/354 Card activation or deactivation
• CPC Class Codes: G06Q 20/355 Personalisation of cards for use
• CPC Class Codes: G06Q 20/363 with the personal data of a user
• CPC Class Codes: H04L 63/067 using one-time keys cryptographic mechanisms or cryptographic arrangements for generation of one-time passwords H04L9/0863
• CPC Class Codes: H04W 12/04 Key management, e.g. using generic bootstrapping architecture [GBA]
• CPC Class Codes: H04W 12/06 Authentication
• CPC Class Codes: H04W 12/068 using credential vaults, e.g. password manager applications or one time password [OTP] applications
• CPC Class Codes: H04W 12/086 using security domains
• CPC Class Codes: H04W 12/35 Protecting application or service provisioning, e.g. securing SIM application provisioning
• CPC Class Codes: H04W 12/71 Hardware identity
• CPC Class Codes: H04W 12/72 Subscriber identity
• CPC Class Codes: H04W 4/50 Service provisioning or reconfiguring
• CPC Class Codes: H04W 4/80 Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication

Abstract

A method using a non-transitory processor for providing an application product including receiving an application profile, a key profile, a secure element (SE) profile, and a mobile terminal profile; establishing a link between the received profiles, in which the link is established for assembling the application product; and applying a limitation to the application product, in which the applied limitation determines whether the application product is accessible to a user. A method using a non-transitory processor for data preparation in a Trusted Service Manager (TSM) including receiving data from a service provider, in which the received data is in a Data Grouping Identifier (DGI) format or a raw data format; and processing the data using at least one of a logical data preparation and a physical data preparation.

Claims

1. A method using a non-transitory processor for providing an application product, comprising:

receiving at least one of an application profile, a load file profile, a secure element (SE) profile, and a mobile terminal profile;

establishing a link between the received profiles, wherein the link is established for assembling the application product; and

applying a limitation to the application product, wherein the applied limitation determines whether the application product is accessible to a user.

2. The method of claim 1, wherein the application profile describes a smart card application as metadata for creating an instance of the application.

3. The method of claim 1, wherein the load file profile describes one or more load files that make up an application code.

4. The method of claim 1, wherein the mobile terminal profile describes attributes of a mobile terminal comprising, Near Field Communication (NFC) capability, supported SE types and over-the-air (OTA) channel support.

5. The method of claim 1, further comprising:

receiving a key profile;

receiving a key; and

establishing a link between the key profile and the key.

6. The method of claim 1, wherein the application product comprises at least one of a product name, a logo, a product group, a SE type, a security domain application identifier (AID), and an instance AID.

7. The method of claim 6, wherein the key profile describes key information as metadata for creating an instance of a key.

8. The method of claim 1, wherein applying the limitation to the application product comprises applying a technological limitation, wherein the technological limitation is applied in response to a determination of a technological incompatibility being present between at least one of a mobile terminal, an operating system of the mobile terminal, and a SE type.

9. The method of claim 1, wherein applying the limitation to the application product comprises applying a business rule limitation, wherein the business limitation is applied in response to a determination of a business incompatibility between one or more service providers.

10. The method of claim 9, wherein the service providers comprise at least one of a financial institution, a mobile network operator, a handset manufacturer, and a card manufacturer.

11. The method of claim 1, wherein applying the limitation to the application product comprises applying a certification limitation, wherein the certification limitation is applied in response to a determination that the application product is not certified by a financial institution.

12. The method of claim 11, wherein financial institution is a credit card issuer or a debit card issuer.

13. The method of claim 1, wherein establishing a link between the received profiles for assembling the application product comprises establishing a link for the application product with a dependent application product.

14. A method using a non-transitory processor for data preparation in a Trusted Service Manager (TSM) comprising:

receiving data from a service provider, wherein the received data is in a Data Grouping Identifier (DGI) format or a raw data format; and

processing the data using at least one of a logical data preparation and a physical data preparation.

15. A method of claim 14, wherein the service provider is a financial institution, a mobile network operator, a handset manufacturer, or a card manufacturer.

16. A method of claim 14, wherein the logical data preparation and the physical data preparation are executed for the data in a raw data format.

17. A method of claim 14, wherein logical data preparation is executed for the data in a DGI format.

18. A method using a non-transitory processor for filtering an application product, comprising:

receiving at least one of an application profile, a load file profile, a key profile, a secure element (SE) profile, and a mobile terminal profile;

receiving a key;

establishing a link between the key profile and the key;

establishing a link between the received profiles, wherein the link is established for assembling the application product;

applying a limitation to the application product, wherein the limitation is a technical limitation, a business rule limitation, or a certification limitation;

receiving mobile terminal information, wherein the mobile terminal information comprises at least one of operating system information, SE type information, hardware information, and application information stored in a mobile terminal; and

filtering the applicable application product based on the applied limitation and the mobile terminal information for displaying to a user.