WO2014077544A1 - Method for configuring profile of subscriber authenticating module embedded and installed in terminal device, and apparatus using same - Google Patents

Abstract

Disclosed are a method for configuring a profile of a subscriber authenticating module embedded and installed in a terminal device, and an apparatus using same. The subscriber authenticating module embedded and installed in the terminal device according to one aspect of the present invention includes one or more network access application related data sets and one or more profiles having unique identifiers. The present invention enables an eco-system provider such as a network service provider, an eUICC manufacturer, or a terminal manufacturer to develop an efficient and rapid eUICC and provide an eUICC service.

Description

Profile configuration method of subscriber authentication module installed in terminal device and device using same

The present invention relates to a profile configuration in a subscriber authentication module, and relates to a profile configuration method of a subscriber authentication module installed in a terminal device and an apparatus using the same.

A UICC (Universal Integrated Circuit Card) is a smart card that can be inserted into a terminal and used as a module for network connection authentication. The UICC may include Network Access Applications (NAA), which are applications for accessing various networks of operators such as Universal Subscriber Identity Module (USIM) for WCDMA / LTE network access and Subscriber Identity Module (SIM) for GSM network access. have.

For terminals requiring miniaturization and durability such as M2M (Machine to Machine) terminals, an embedded SIM (hereinafter referred to as eSIM or eUICC) that is integrally mounted when manufacturing a terminal, rather than a conventional removable UICC, has been proposed.

eUICC provides network access authentication function similar to existing detachable UICC, but due to its physical structure, eUICC should be able to handle network access of multiple operators with one UICC, and there are many issues such as eUICC opening / distribution / subscriber information security. And it is necessary to prepare a plan for this. To address this, international standardization bodies such as GSMA and ETSI are conducting standardization activities on relevant elements such as carriers, manufacturers and SIM vendors, as well as necessary elements including top-level structures.

At ETSI, a working group (WG) is in operation to establish eUICC standards. Currently, a module called profile is defined and post-organized to post personalization of applications for network access authentication functions of various operators to eUICC. Has established requirements for installation and management. In addition, the management policy and application of the profile are discussed, but the specific method is not defined yet.

As such specific details related to profile management of eUICC are not defined, there are many difficulties for eUICC card manufacturers, terminal manufacturers, and eco-system operators to develop and commercialize eUICC.

An object of the present invention for overcoming the above-described problem is to provide a profile configuration method of a subscriber authentication module that is installed embedded in the terminal device.

ETSI defines profile type and usage definition and basic data to be included. However, the details of the management data, support command interface, function, and the like of the profile type and the application method thereof have not been discussed yet.

Another object of the present invention is to provide an apparatus using the profile composition method.

In order to achieve the above object, a subscriber authentication device embedded in a terminal device according to an aspect of the present invention includes one or more profiles including a set of one or more network connection application-related data and having a unique identifier.

The network connection application related data includes one or more network connection applications and an associated connection authentication key.

The network connection application may include at least one of parameter data and a file structure for network connection.

A profile according to the present invention manages one or more of profile attribute data and profile policy rules.

In this case, the profile attribute data may include at least one of profile identifier, profile type, profile status information, network operator information, network connection application list belonging to the profile, privilege, size of profile data, profile version, and type of profile support terminal. It may include.

In addition, the profile policy rule may include one or more rules of whether profile deletion is allowed, profile state change notification, profile state change allowed, profile type change allowed, and profile initialization.

The profile may further include an interface for interfacing with an object located in or outside the subscriber authentication device.

The profile may also provide secure messaging for communication with objects located within or outside the subscriber authentication device.

The interface receives an incoming message for at least one of profile selection, the profile attribute data related management, profile state change, security authentication, profile management key management, and profile registration related management and returns a corresponding value.

According to another aspect of the present invention, a terminal device includes a subscriber authentication device including one or more profiles including a set of one or more network connection application-related data and having a unique identifier and installed in a terminal device; It includes a subscriber management module to interwork with the subscriber authentication module.

The subscriber management module transmits a change or inquiry request for profile related information to the subscriber authentication module.

The subscriber authentication module returns a response value according to the change or inquiry request to the subscriber management module.

Profile related information according to the present invention includes one or more of profile attribute data and profile policy rules.

In accordance with another aspect of the present invention, a method of configuring a profile includes configuring at least one profile including a set of at least one network connection application related data and having a unique identifier.

The method may further include receiving a change or inquiry request for profile related information from an object located in or outside the subscriber authentication apparatus.

The method may further include returning a response value according to the change or inquiry request to an object located inside or outside the subscriber authentication device.

Profiles according to the invention may manage one or more of profile attribute data and profile policy rules.

Here, the profile attribute data may include at least one of profile identifier, profile type, profile status information, network operator information, network connection application list belonging to the profile, privileges, size of profile data, profile version, and type of profile support terminal. It may include.

In addition, the profile policy rule may include one or more rules of whether profile deletion is allowed, profile state change notification, profile state change allowed, profile type change allowed, and profile initialization.

According to one embodiment of the present invention, each profile attribute data and profile policy rule may be defined as a separate elementary file under an application-specific file (ADF).

According to another embodiment of the present invention, the profile attribute data and the profile policy rule may be defined as one elementary file under a master file.

In addition, according to another embodiment of the present invention, the profile attribute data and profile policy rule may be defined as a data object template in a profile.

The present invention defines network management service providers, eUICC manufacturers, terminal manufacturers, and the like by defining contents related to profile management data, external interworking interfaces, and security features necessary for the eUICC internal management module or an external interworking device to manage profiles installed on the eUICC. It will enable efficient and fast eUICC development and service provision of eco-system operators.

1 is a diagram illustrating a connection relationship between an eUICC and a peripheral external device according to an embodiment of the present invention.

2 is a block diagram of an eUICC module according to an embodiment of the present invention.

Figure 3 shows an embodiment of a profile configuration method according to the present invention.

4 shows another embodiment of a method for constructing a profile according to the present invention.

5 shows another embodiment of a method for constructing a profile according to the present invention.

6 shows an embodiment of a profile selection method according to the present invention.

7 illustrates an embodiment of a profile attribute data or policy rule query method according to the present invention.

8 illustrates another embodiment of a profile attribute data or policy rule query method according to the present invention.

9 illustrates an embodiment of an interworking interface when adding or modifying profile attribute data and policy rules according to the present invention.

10 illustrates another embodiment of an interworking interface when adding or modifying profile attribute data and policy rule according to the present invention.

11 illustrates an embodiment of an interworking interface for changing a profile state according to the present invention.

12 illustrates an embodiment of a security authentication method with a profile and an external companion device according to the present invention.

FIG. 13 illustrates an embodiment of an interworking protocol when an external companion device sets or changes a profile management key according to the present invention.

14 illustrates an embodiment of an interworking protocol for registering profile information according to the present invention.

15 illustrates an embodiment of an interworking protocol for profile deregistration according to the present invention.

16 is a flowchart illustrating a method of configuring a profile according to an embodiment of the present invention.

As the present invention allows for various changes and numerous embodiments, particular embodiments will be illustrated in the drawings and described in detail in the written description.

However, this is not intended to limit the present invention to specific embodiments, it should be understood to include all modifications, equivalents, and substitutes included in the spirit and scope of the present invention.

The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting of the present invention. Singular expressions include plural expressions unless the context clearly indicates otherwise. In this application, the terms "comprise" or "have" are intended to indicate that there is a feature, number, step, operation, component, part, or combination thereof described in the specification, and one or more other features. It is to be understood that the present invention does not exclude the possibility of the presence or the addition of numbers, steps, operations, components, components, or a combination thereof.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art. Terms such as those defined in the commonly used dictionaries should be construed as having meanings consistent with the meanings in the context of the related art and shall not be construed in ideal or excessively formal meanings unless expressly defined in this application. Do not.

The terms to be described below are terms defined in consideration of functions in the present invention, and may be called differently according to the intention or precedent of a client, an operator, or a user. Therefore, the definition of terms should be made based on the contents throughout the specification.

The term eUICC (embedded UICC) or eSIM (embedded SIM) used in the present application is used to mean an embedded SIM (Subscriber Identity Module) that is integrally mounted when manufacturing a terminal in a meaning distinguished from an existing removable UICC.

As used herein, the term “terminal” refers to a mobile station (MS), user equipment (UE), user terminal (UT), wireless terminal, access terminal (AT), terminal, subscriber unit (Subscriber Unit). May be referred to as a subscriber station (SS), a wireless device, a wireless communication device, a wireless transmit / receive unit (WTRU), a mobile node, mobile or other terms. Various embodiments of the terminal may be photographed such as a cellular telephone, a smart phone having a wireless communication function, a personal digital assistant (PDA) having a wireless communication function, a wireless modem, a portable computer having a wireless communication function, or a digital camera having a wireless communication function. Devices, gaming devices with wireless communications capabilities, music storage and playback appliances with wireless communications capabilities, internet appliances with wireless Internet access and browsing, as well as portable units or terminals incorporating combinations of such functions. have.

In addition, the terminal may include a machine to machine (M2M) terminal, a machine type communication (MTC) terminal / device, but is not limited thereto.

In addition, each block or step described herein may represent a portion of a module, segment, or code that includes one or more executable instructions for executing a particular logical function (s). It should also be appreciated that in some embodiments, the functions noted in the blocks or steps may occur out of order. For example, it is also possible that two blocks or steps shown in succession are performed simultaneously, or that the blocks or steps are sometimes performed in the reverse order, depending on the function in question.

Hereinafter, with reference to the accompanying drawings, it will be described in detail a preferred embodiment of the present invention. In the following description of the present invention, the same reference numerals are used for the same elements in the drawings and redundant descriptions of the same elements will be omitted.

The profile on the eUICC includes a network operator's unique data, key information, and the like, and can be created and managed by a network operator or a third party delegated by the network operator. However, in managing and operating such a profile on the eUICC, a standardized interworking interface provided by the profile for the external interworking device 400 (eg, SM) or the eUICC internal management module is required. In addition, it is necessary to define the property data and policy rules that the profile can manage and provide externally.

Without these standardized interface specifications and data definitions, external devices that manage multiple profiles (e.g., subscriber management modules (SMs), etc.) or eUICC internal management modules can be optimized for each network operator's profile characteristics. As a result, many resources can be consumed for development and commercialization.

In order to solve the above problems, the present invention defines items to be basically provided according to profile types such as attribute data and policy rules, interworking interfaces, and security functions managed by the profile, and a method of applying the same and the actual method We propose various embodiments in which a profile is applied on an eUICC.

A profile according to the invention is a module comprising one or more network connection applications (including parameter data, file structures, etc. for network connection) and network connection credentials. Profiles can be accessed with unique values (IDs) on the eUICC, and the types of profiles include provisioning profiles and operator profiles.

The provisioning profile, when installed on the eUICC, provides access to the eUICC between the eUICC and the Subscription Manager-Secure Routing (SM-SR) and profile management. A profile that contains one or more network connection applications and associated network connection credentials that enable it.

An operator profile is a profile that includes one or more network connection applications and associated connection credentials.

As described above, unlike the conventional removable USIM, several profiles (operator profile or configuration profile) may exist on the eUICC.

The profile configuration method according to the present invention largely includes basic attribute data and policy rule management method of a profile, an eUICC internal or external interworking interface providing method for profile management, and a profile security method.

A first embodiment of the profile construction method according to the present invention comprises a profile including attribute data and policy rules of the profile.

At this time, the attribute data of the profile includes a profile identifier, a profile type, status information, network operator (MNO) information, a network access application (NAA) list belonging to the profile, a privilege, and profile data. Information about the size, profile version, and profile support terminal type.

In addition, the policy rules of the profile include policy rules for one or more of whether profile deletion is allowed, profile state change notification, profile state change is allowed, and profile type change is allowed.

A second embodiment of the profile configuration method according to the present invention comprises an eUICC internal or external interworking interface for profile management.

Here, the eUICC internal or external interworking interface may include an interface for selecting a profile, an interface for inquiring, adding, and modifying profile data and policy rules, an interface for changing profile state, an external profile and an eUICC external object (or an internal eUICC). Object), an interface for setting and changing a profile management key, an internal interface for registering or unregistering with eUICC when installing or deleting a profile.

A third embodiment of a profile configuration method according to the present invention includes a profile security method.

Here, the profile security method, the property data of the profile through the secure messaging (ecure messaging) with the eUICC internal or external interworking device 400, over the air (OTA), policy rule data management (for example, issuing, Profile security is performed using one or more of the following methods.

In summary, in the present invention, in order to provide the same network access function as the existing removable USIM card on the eUICC, the attribute data and policy rule data that the profiles basically manage and provide are defined.

In addition, the present invention proposes embodiments for defining an interface for interworking with an internal or external eUICC and using the interface.

In addition, the present invention defines the security functions that the profile must provide.

In addition, the present invention proposes a basic data included in the configuration profile and a data structure for managing the same.

1 is a diagram illustrating a connection relationship between an eUICC and a peripheral external device according to an embodiment of the present invention.

The eUICC 100 according to the present invention includes one or more profiles as shown in FIG. 1. As shown in FIG. 1, there may be several profiles in the eUICC, and if only a profile block is loaded, it is a loaded profile, and the installed profile is either an enabled profile 5100 or an inactive depending on the state. (disabled) in the form of a profile 5200.

The eUICC 100 may also include a Mobile Network Operator-Over The Air (MNO-OTA) 200, an MNO Core Network 300, one or more Subscription Manger-Secure Routing (SM-SR) 410, one or more SM- It may be connected with a subscription manger-data preparation (DP) 420.

The MNO-OTA 200 and the MNO core network 300 are operated by an entity that provides a communication service to customers through a mobile network, that is, a mobile network operator, and communicate with a terminal. As shown in FIG. 1, the MNO-OTA 200 provides a profile content access credentials to the eUICC 100.

The SM-SR 410 plays a role of safely performing a function of directly managing service provider profiles and configuration profiles on the eUICC. In addition, the SM-DP 420 prepares the operator profile and the configuration profile to be securely provisioned on the eUICC, for example, encrypts the profile.

The subscriber management module (SM), which is a concept of integrating the SM-SR 410 and the SM-DP 420, may be understood as a system that provides a function for securely managing profiles on an eUICC and provisioning profiles securely on an eUICC. Can be.

2 is a block diagram of an eUICC module according to an embodiment of the present invention.

The components to be described below with reference to FIG. 2 may be defined by functions that each performs as components defined by functional divisions, not physical divisions. Each of the components may be implemented in hardware and / or program code and a processing unit for performing each function, and the functions of two or more components may be included in one component and implemented.

Therefore, the names given to the components in the present embodiment are given not to physically distinguish each component, but to imply a representative function performed by each component, and according to the name of the component It should be noted that the technical spirit of the is not limited.

As shown in FIG. 2, the eUICC 100 according to an embodiment of the present invention includes a standard platform and API 120 such as a card operating system 110 and Java Cards. The eUICC 100 is also a module for supporting profiles in the Card Operating System 110 and the upper layers of the standard platform and API 120, and the profile manager 130 and the profile for installing and managing profiles. It may include a profile installer (140).

The eUICC 100 according to the present invention includes one or more profiles. Profiles can be classified into several types according to their states. When a profile block is loaded in a memory (for example, EEPROM, Flash memory, etc.) that does not change, it can be defined as a loaded profile 5300.

In addition, when a profile block is loaded and decoded by the profile installation unit 140, a necessary memory allocation is performed, and when issuance of necessary data may be defined as an installed profile. The installed profile may exist as an enable profile 5100 or a disable profile 5200 depending on the state.

Here, the active profile 5100 is a state in which network access applications (NAAs) belonging to the profile are selectable after the profile is installed. On the other hand, the inactive profile 5200 refers to a profile in which a profile is installed but network access applications (NAAs) belonging to the profile are not selectable.

The installed profile, that is, the active profile 5100 and the inactive profiles 5200 in FIG. 2, includes a content management unit 5101 and a network connection application (NAA) that provide a function of remotely managing data of the profile. Network Access Application) 5102.

The installed profile also includes a profile registry 5110 for managing profile attribute data and policy rules and a Policy Enforcement Function 5120 for performing profile related policy rules. Here, policy rules refer to an operation required to implement an eUICC management policy related to eUICC remote management.

On the other hand, the profile installation unit 140 has a key (credentials) for installing the profile instance (instance) as a module for verifying, decrypting, installing the profile data.

In addition, the profile manager 130 may include a profile block management, a profile information registry, and a profile enforcement policy.

Profile block management is a module that manages encrypted data blocks when a profile is installed, and has a key for installing, deleting, activating, and deactivating a profile.

The profile information repository manages the profile list installed in association with the profile installation unit, the NAA list of the corresponding profile, the profile state, and the profile type information.

The profile related policy execution unit manages the profile related policies and applies them.

Profile management data

Attribute data managed by a profile according to the present invention may include data as illustrated below.

Profile identifier Profile type

● Profile Status Information

● Information about the mobile network operator (MNO), the profile owner

● List of Network Access Applications (NAA) belonging to the profile

● Privilege of Profile

● Profile data size

● Profile version

● Profile Supported Terminal Type

Among these attribute data managed by the profile according to the present invention, profile identifier, profile type, and profile state information are preferably included as profile attribute data, and other attribute data may be additionally included.

In addition, the policy rule data managed by the profile according to the present invention may include one or more of the data as illustrated below.

● Allow profile deletion

● Allow profile state changes

● Notify me of profile status changes

● Whether to change profile type

● Allow profile initialization

In the manner in which the attribute data and policy rule data managed by the profile are managed in the actual profile, first, each attribute data or each policy rule data is managed in the form of an elementary file (EF). Method, and second, all attribute data and policy rule data are managed in the form of one elementary file (EF), and third, the data object template (data object template) in the profile, the value field of several Management in the form of a set of data objects).

3 to 5, each of the three methods of managing attribute data and policy rule data managed by a profile will be described.

Figure 3 shows an embodiment of a profile configuration method according to the present invention.

That is, FIG. 3 shows a preferred embodiment of a method of managing in an EF form having respective data, which is the first method. Attribute data and policy rule data may be defined in the form of EF under MF (Master File). At this time, each EF file may have a file ID of '2FXX' according to the ISO7816-4 standard.

On the other hand, if the attribute data and policy rule data are defined in the EF form under a specific application file (ADF, Application Dedicated File), each EF file is a file ID of '6FXX' according to the ISO / IEC 7816-4 standard. May have The access rights of each EF file can be defined according to the service environment of eUICC.

One embodiment of the profile type data definition among the attribute data or policy rule data of the profile according to the present embodiment is shown in the form of coded with one byte of data as shown in the second shown table of FIG. 3.

Among profile attribute data and policy rules, in particular, an embodiment of a profile privilege related data definition may also be represented in a coded form as in the last table of FIG. 3.

Profile privilege related data may have one or more of the following items.

● Default Selected: A specific profile is automatically selected on the basic logical channel after an eUICC reset.

● Service to other applications on the eUICC (Global Service): For example, in the case of a configuration profile, an operation profile may provide a service for providing external object access information.

Although embodiments of the profile type and privilege data according to the present invention have been described above, other attribute data and policy rule data other than the profile type and privilege data may also be defined in an EF form similar to the table shown in FIG. 3. . That is, the present invention does not define all the data, but may include all the definitions of the EF type that can be generally considered.

4 shows another embodiment of a method for constructing a profile according to the present invention.

Figure 4 shows a preferred embodiment of the second method of the profile configuration method according to the present invention.

Referring to the table shown in FIG. 4, it can be seen that all attribute data and policy rule data are defined and managed in one EF form.

The attribute data and policy rule data management file may be defined in the EF form under MF (Master File). The EF file may have a file ID in the form of '2FXX' according to the ISO7816-4 standard.

On the other hand, if the attribute data and policy rule data are defined in an EF format under a specific application dedicated file (ADF), the corresponding EF file is a file ID of '6FXX' according to the ISO / IEC 7816-4 standard. May have The access rights of the EF file can be defined according to the service environment of eUICC.

5 shows another embodiment of a method for constructing a profile according to the present invention.

Figure 5 shows a preferred embodiment of the third method of the profile configuration method according to the present invention.

FIG. 5 is a table illustrating object templates in the case of managing the attribute data of the profile and the policy rule data in the form of a data object template in the profile. Tag values and the like defined in the table shown in FIG. 5 are arbitrarily defined values, and forms in which each data is defined as a general Tag Length Value (TLV) data structure may be considered to conform to the structure of the present invention.

In the above, embodiments of the profile management data in the profile configuration method according to the present invention have been described with reference to FIGS. 3 to 5, and hereinafter, a profile interworking interface based on such profile management data will be described.

The interworking interface with the eUICC internal and external objects provided by the profile according to the present invention includes at least one of the commands or functions defined below.

● Profile selection (SELECT)

● Profile property data and policy rule query (READ BINARY, READ RECORD, GET DATA)

● Add / modify profile attribute data and policy rules (UPDATE BINARY, UPDATE RECORD, PUT DATA)

● Profile status query (READ BINARY, GET DATA)

● Change Profile Status (UPDATE BINARY, SET STATUS)

● Security authentication between profiles and external objects (or eUICC internal modules) (INIT UPDATE, EXTERNAL AUTHENTICATE)

● Setting / Change Profile Management Key (PUT KEY)

● Register with eUICC when installing profile (REGISTER)

● Unregister to eUICC when deleting profile (DEREGISTER)

Hereinafter, various embodiments of an interworking interface with an external interworking device and an eUICC internal module will be described with reference to the drawings.

The profile selection method, which is the first embodiment of the profile interworking interface according to the present invention, can be classified into two types. The first method is to explicitly select a specific profile by sending a "selection" command using the external companion device 400 (or eUICC internal module) profile ID, and the second method is to implicitly select a specific profile. Way.

6 shows an embodiment of a profile selection method according to the present invention.

In detail, FIG. 6 illustrates an embodiment of an interworking protocol in which the external companion device 400 selects a profile when the specific profile is explicitly selected using the profile ID.

The profile 5000 according to the present invention may support a SELECT command which is a file selection command defined in the ETSI TS 102 221 and the Global Platform standard as a command for selecting a profile. The external companion device 400 may select a specific profile through a SELECT command provided by the profile 5000 (S610). In this case, the external companion device 400 may be, for example, a device such as a terminal or an SM. Meanwhile, in the embodiment of FIG. 6, the external companion device 400 may be an eUICC internal module. In this case, the eUICC internal module may be a profile manager 130.

File control information (FCI) may be returned as response data to the file selection command S610 (S620). The file control information may include a profile ID, profile status information, profile data size, and the like. The eUICC 100 may check whether the corresponding profile is a profile installed on the eUICC through the received file control information and process the corresponding profile to be selected.

On the other hand, with respect to the manner in which a specific profile is implicitly selected, which is the second method of the method of selecting the profile 5000, the specific profile has an implicit selection privilege or is enabled in the eUICC. If only one exists, the eUICC 100 may implicitly select the profile. In this case, the external companion device 400 may implicitly select a specific profile 5000 only by resetting the eUICC 100 without transmitting an instruction for selecting the profile 5000 to the eUICC 100.

Query profile attribute data and policy rules

According to the present invention, the method for querying the above-described profile attribute data and policy rule in the external companion device 400 or the eUICC internal module may be a data management scheme, that is, whether the attribute data and policy rule data are EF files in the profile. There are two ways to distinguish between data objects.

According to the first method described below with reference to FIG. 7, when the attribute data and policy rule data are managed in the form of Elementary File (EF) inside the profile, the profile may support a command to select an EF file and read the file data. have. The external companion device 400 (or the eUICC internal module) may inquire necessary data through a command provided by the profile 5000.

7 illustrates an embodiment of a profile attribute data or policy rule query method according to the present invention.

In detail, FIG. 7 illustrates an embodiment of an interworking protocol in which the external companion device 400 inquires data when the attribute data and the policy rule are in the EF form. The profile 5000 is a command for reading data according to an EF file type and may support a READ BINARY or READ RECORD command, which is a general file reading command defined in ISO / IEC 7816-4 and ETSI 102 221.

The external companion device 400 may inquire the attribute data and the policy rule of the profile by using the READ BINARY or READ RECORD command S710 supported by the profile 5000. When the file read command is called, the profile 5000 checks the file read access condition and returns data of the corresponding file only when the access condition is satisfied (S720).

In the second method of querying profile attribute data and policy rules according to the present invention, the attribute data and policy rules are applied when they are managed in the form of data objects.

8 illustrates another embodiment of a profile attribute data or policy rule query method according to the present invention.

Specifically, FIG. 8 illustrates an embodiment of an interworking protocol in which the external companion device 400 inquires data when the attribute data and policy rule data are in the form of a data object. The profile 5000 supports a command for querying a data object, thereby providing a function for the external companion device 400 to query profile attribute data and policy rules through the command.

The profile 5000 is a command for inquiring a data object and can support a GET DATA command defined in ISO / IEC 7816-4 and a global platform. The external companion device 400 can search for attribute data through a GET DATA command. Inquire (S810). In this case, the external companion device 400 may call the GET DATA command without a parameter to query the entire profile management data. The profile 5000 checks the validity of the parameter and returns the corresponding data object or the entire data object (S820).

As in other embodiments, the external companion device 400 may be, for example, a device such as a terminal or an SM. In addition, the external interworking device 400 may be replaced with an eUICC internal module, and in this case, the eUICC internal module may be the profile manager 130.

Add / Modify Profile Attribute Data and Policy Rules

The method of adding or modifying the above-described profile attribute data and policy rule in the external companion device 400 or the eUICC internal module will be described. Adding or modifying profile attribute data and policy rule can be divided into two types according to the data management method.

In a first manner, when the attribute data and policy rule data are managed in the form of an elementary file (EF) inside the profile, the profile 5000 may support a selection of an EF file and a file update command.

9 illustrates an embodiment of an interworking interface when adding or modifying profile attribute data and policy rules according to the present invention.

Specifically, FIG. 9 illustrates an embodiment of an interworking protocol in which the external companion device 400 adds / modifies data when the attribute data and the policy rule are in the EF form.

The external companion device 400 (or the eUICC internal module) may add or modify necessary data by selecting an EF file (S910) and a command (S930) for updating file data.

The profile 5000 may support an UPDATE BINARY or UPDATE RECORD command, which is a general file update command defined in ISO / IEC 7816-4 and ETSI 102 221, as a data update command according to the type of an EF file.

The external companion device 400 may modify data of the EF file by using an UPDATE BINARY or UPDATE RECORD command provided by the profile 5000 (S930). Profile data to be modified can be set in the data field of the UPDATE BINARY command. The record number and the data to be modified can be set in the data field of the UPDATE RECORD command.

When the file update command is called, the profile checks the file update access condition and checks whether the access condition is satisfied. In addition, the profile checks that the policy does not violate a specific policy rule (for example, whether to allow the type change, whether to change the state, etc.) and if it is found to return a policy violation error (S940). If this does not violate, update the data in the file.

Meanwhile, FIG. 9 illustrates a procedure (S920) of inputting a VERIFY PIN which is an administrator authentication value (ADM) authentication command when the file update access condition is an administrator's authority. In the present invention, the file can be updated only when the administrator authentication value is normally authenticated.

10 illustrates another embodiment of an interworking interface when adding or modifying profile attribute data and policy rule according to the present invention.

Specifically, FIG. 10 illustrates an embodiment of an interworking protocol in which the external companion device 400 adds / modifies data when the attribute data and the policy rule are in the form of a data object.

In the present embodiment, the external companion device 400 may add / modify attribute data and policy rule data of a profile by using a command for updating a data object.

The profile 5000 is a command for adding / modifying data objects and may support the PUT DATA command defined in ISO / IEC 7816-4. The external companion device 400 may add / modify profile attribute data and policy rules using the PUT DATA command provided by the profile 5000 (S1010). In the data field of the PUT DATA command, one or more data objects can be updated by setting one profile data object or a data object group of a nested structure.

When the data update command is called, the profile 5000 checks the data update right condition (for example, mutual authentication through a key) to check whether the right condition is already satisfied. In addition, the profile 5000 checks whether it does not violate a specific policy rule (for example, whether to allow a type change, whether to change the state, etc.), and returns a policy violation error if it violates (S1020). If it does not violate, add / modify the data object value.

Profile status query

According to the present invention, a method of querying the state of the profile in the external companion device 400 or the eUICC internal module is similar to the embodiments of FIGS. 7 and 8, and is defined in the profile attribute data and the policy rule query interworking interface item. Profile status can be queried using the same method as the profile attribute data and policy rule data query method.

Profile state change

According to the present invention, the method of changing the state of the profile in the external companion device 400 or the eUICC internal module can be largely divided into two types.

The first method is a method of changing a specific file or data object by using the same method as described with respect to the addition and modification of profile attribute data and policy rule, as described above with reference to the embodiments illustrated in FIGS. 9 and 10. You can change the status with.

The second method of changing the state of the profile according to the present invention is a method of changing the state through a specific command for changing the state information in order to grant and manage the state information management authority separately. The profile 5000 may support an instruction for changing the state of the profile. The external companion device 400 may change the profile state by using a state change command provided by the profile.

11 illustrates an embodiment of an interworking interface for changing a profile state according to the present invention.

In detail, FIG. 11 illustrates an embodiment of an interworking protocol in which the external interworking device 400 changes a state of a profile by using a state change command provided by the profile 5000.

As a command for changing the state of the profile 5000, the SET STATUS command defined in the global platform may be supported. The external companion device 400 may change the active profile to the inactive state or change the inactive profile to the active state by using the SET STATUS command (S1110). The external companion device 400 may call the profile state change command after performing mutual authentication with the eUICC according to the security setting of the eUICC in order to change the state of the profile 5000.

When the state change command is called, the profile 5000 checks whether a policy state change allowance policy rule exists and does not violate the policy. If the policy is violated, an appropriate error is returned. If not violating the policy, the profile 5000 changes the state of the profile itself to match the state sent (active / inactive) as a parameter of the SET STATUS command. At this time, if there is a policy rule of status change notification of the profile and the value is set, the profile returns a value according to a method of notifying the status change of the profile.

According to an embodiment of the present invention, an OTA (Over The Air) method using a short message service (SMS) may be used as a method of notifying a state change of the profile 5000. When the profile 5000 notifies the status change by the OTA method using the SMS, the profile 5000 returns a success message including the value '91XX' as the status word (S1120). The terminal or the external companion device 400 reads the OTA message from the eUICC 100 and transmits the OTA message to the OTA system of the service provider MNO of the profile 5000. When the service provider receives the corresponding OTA, the service provider may check that the state of the profile 5000 of the eUICC 100 is changed.

Security authentication between profile and external interlocking device

The security authentication method between the profile and the external interworking device (or the eUICC internal module) according to the present invention may have various methods depending on the key data and the authentication method used for the security authentication. The mutual authentication method and the mutual authentication method through a certificate are mentioned.

The first method, mutual authentication using a shared key, may use a secure channel protocol '02' using a shared key defined in a global platform. Profiles may support commands to support secure authentication.

12 illustrates an embodiment of a security authentication method with a profile and an external companion device according to the present invention.

In detail, FIG. 12 illustrates an embodiment of a mutual security authentication method using a shared key between a profile and an external companion device.

Referring to FIG. 12, the profile 5000 may support INIT UPDATE and EXTERNAL AUTHENTICATE commands provided by a global platform in order to support mutual security authentication using a shared key. The external interworking device 400 performs a procedure of verifying whether the correct keys are owned by each other by using keys previously shared with each other by using an INIT UPDATE S1210 and EXTERNAL AUTHENTICATE S1230 command.

The external companion device 400 generates a random value, sets the data as an INIT UPDATE command, and transmits the data to the profile (S1210). The profile 5000 generates a session key using the shared key and returns a random value of the card and a value obtained by encrypting the random value to the external companion device 400 (S1220). The external companion device 400 also generates a session key using the shared key and verifies whether the encrypted data received from the profile is correct.

If the encrypted data is correct, the external companion device 400 encrypts the random value generated by the external companion device 400 and transmits the encrypted random value to the profile 5000 (S1230). The profile 5000 checks whether the encrypted value transmitted by the external companion device 400 is correct and returns a success / failure result (S1240).

Meanwhile, according to an embodiment of a security authentication method using a certificate between a profile and an external companion device, which is the second method, a certificate-based secure channel protocol '10' provided by a global platform may be used. The procedures and commands of the secure authentication method can follow the method defined in the global platform.

Set / Change Profile Management Key

As a method of changing the management key of the profile in the external companion device, a method of performing a separate key management command may be used. Since the management key may be only a module having a specific authority, the command may be executed after the authority verification is performed through the security authentication method described above with respect to the security authentication between the profile and the external companion device.

FIG. 13 illustrates an embodiment of an interworking protocol when an external companion device sets or changes a profile management key according to the present invention.

The profile 5000 according to the present invention provides a command for changing a management key, wherein the command may be a PUT KEY command defined in a global platform for key setting / change.

The external companion device 400 may set / change a profile management key by using a PUT KEY command provided by the profile 5000. When the profile 5000 has a security authentication scheme policy in order to obtain the authority to set / change the management key, the external companion device 400, as described above with reference to the embodiment of FIG. The authentication procedure described in the security authentication related part with the companion device 400 (or the eUICC internal module) may be previously performed.

The external companion device 400 may set a key index and new key data to be set or changed as a data field of the PUT KEY command (S1310). The profile 5000 checks whether the security policy is normally performed before the command call, so that the security policy is not violated. If the profile 5000 does not violate the security policy, the profile 5000 sets or changes new key data and transmits the result value to the external companion device 400.

Registration with eUICC during profile installation

According to the present invention, the method of registering the profile 5000 to the eUICC internal module 150 when installing the profile 5000 may include a method in which the profile uses a profile registration interface provided by the eUICC internal module 150.

The eUICC internal module 150 may collectively manage profile attribute information such as a profile list installed on the eUICC, a type / status / NAA list of each profile, and the like. The eUICC internal management module 150 according to the present invention may be, for example, the profile manager 130, the eUICC platform 120, and the like, which have been described with reference to FIG. 2.

The eUICC internal module 150 may provide a profile registration interface to obtain information of the profile. The profile 5000 may register information such as a profile identifier, a profile type, a status, a NAA list, and the like into the eUICC internal module 150 at the time when the profile 5000 is installed in the eUICC using the profile registration interface.

14 illustrates an embodiment of an interworking protocol for registering profile information according to the present invention.

In detail, FIG. 14 illustrates an embodiment of an interworking protocol in which a profile registers profile information in an eUICC internal module.

The eUICC internal management module 150 may provide a REGISTER command as an internal interface (API) for registering the profile 5000.

The profile 5000 calls the REGISTER command provided by the eUICC internal management module 150 at the time when profile installation is completed, and sends profile information (profile identifier, type, status, NAA list, etc.) to the eUICC internal management module 150. It is possible to register (S1410). When the REGISTER command is called, the eUICC internal management module 150 verifies the validity of the profile information and stores and manages it in a memory such as a data store. The eUICC internal management module 150 then returns the profile registration related result value to the profile 500 (S1420).

Meanwhile, as an example of the API for registering the profile information used in the embodiment of FIG. 14 to the eUICC internal management module 150, REGISTER (Profile ID, Profile Type, NAAs list, initial status) may be mentioned. The REGISTER command is used to register profile information in the eUICC internal management module. The parameters may include a profile identifier, a profile type, a list of NAAs belonging to the profile, and a profile state (active / inactive) at the initial installation. .

Deregistration in eUICC when deleting profile (eUICC internal interface)

According to the present invention, a method of releasing a profile from the profile registration in the eUICC internal management module when deleting a profile may include a method in which a profile uses a profile deregistration interface provided by the eUICC internal management module.

The eUICC internal management module 150 may integrally manage profile information installed on the eUICC. The eUICC internal management module 150 may provide a profile deregistration interface to delete information of a registered profile.

15 illustrates an embodiment of an interworking protocol for profile deregistration according to the present invention.

In detail, FIG. 15 illustrates an embodiment of an interworking protocol in which a profile requests a profile deregistration to an eUICC internal management module.

The eUICC internal management module 150 may provide a DEREGISTER command as an internal interface for deregistering a profile.

The profile 5000 may request to deregister the profile by calling the DEREGISTER command provided by the eUICC internal management module 150 at the start of the profile deletion procedure (S1510). When the DEREGISTER command is called, the eUICC internal management module 150 deletes the profile management information after checking whether the profile for which registration is requested is a registered profile identifier. The eUICC internal management module 150 then returns the profile deregistration related result value to the profile 5000 (S1520).

An example of an API for deregistering a profile used in the embodiment of FIG. 15 with the eUICC internal management module 150 may include DEREGISTER (Profile ID), and deregistering a profile with the eUICC internal management module. Can be used. The parameter of the DEREGISTER command may include a profile identifier.

Profile security properties

Profile according to the present invention ensures the confidentiality (confidentiality) and integrity (integrity) of the command APDU (Application Protocol Data Unit) exchanged with the external interworking device and the eUICC internal management module.

A profile according to the present invention uses a secure channel as a way to guarantee the confidentiality and integrity of the command APDU. The secure channel generation method performs security authentication as defined in the security authentication related part between the profile and the external interworking device (or the eUICC internal module) as described in the embodiment of FIG. 12, and sets the security level when the security authentication is successfully performed. And session key generation is complete.

The profile and the external interworking device may ensure the confidentiality and integrity of the command APDU by generating the data encryption and data authentication code (MAC) of the command through the generated session key and adding it to the APDU.

Command security message method through secure channel is performed by external interworking device (or eUICC internal management module) with specific authority in eUICC management policy such as changing profile status, adding / modifying profile attribute data and policy rule, setting / changing profile management key. Applicable only when performing a possible interface.

Profiles according to the present invention also support remote management of profile attribute data and policy rule changes, profile state changes, and the like via Over The Air (OTA).

The key for the secure channel and the OTA management function of the profile according to the invention is managed separately and securely. In addition, each key can be changed to a new key by the profile owner according to the method of setting or changing the profile management key as described in the embodiment of FIG. 13.

In this case, the profile owner may be, for example, a network service provider (MNO), a subscriber manager module, or the like.

16 is a flowchart illustrating a method of configuring a profile according to an embodiment of the present invention.

The profile configuration method according to the present invention illustrated in FIG. 16 may be mainly performed by a subscriber authentication module installed in a terminal device, for example, an eUICC.

The profile configuration method according to the present invention largely comprises the steps of installing one or more profiles (S1610), registering the installed profile (S1620), receiving a change or inquiry request for the installed one or more profiles (S1630), changing Alternatively, the method may include performing an operation according to the inquiry request (S1640), and returning a response value of the operation for the change or inquiry request (S1650). Here, one or more profiles may be distinguished by a unique identifier.

On the other hand, receiving a change or inquiry request for the installed one or more profiles (S1630) specifically, for example, receiving a profile state change request (S1631), receiving a profile deletion request (S1632), attributes Receiving a data or policy rule change request (S1633), receiving a property data or policy rule inquiry request (S1634), and receiving a profile management key change request (S1635).

Here, the change or inquiry request for the profile represents only a part of various embodiments that may be considered according to the profile interworking interface according to the present invention, and there may be various profile attribute data or policy rule-related change or inquiry requests. It should be understood.

In addition, performing the operation according to the change or inquiry request (S1640), the step of changing the requested profile state to active or inactive (S1641), the step of deleting the requested profile (S1642), the attributes of the requested profile Changing the data or policy (S1643), providing information on the requested data (S1644), and changing the requested profile management key (S1645).

Each of the detailed steps listed above is illustrated only as an example only for convenience, and may be reversed, and the steps of receiving a request (S1631, S1632, S1633, S1634, and S1635) are combined into one step. It may be configured.

According to the above embodiments, the method for constructing a profile according to the present invention including the above-described steps, operation sequences, and instructions may be implemented as computer-readable program code on a computer-readable recording medium.

Computer-readable recording media include all types of recording devices that store data that can be read by a computer system. For example, there are ROM, RAM, CD-ROM, DVD-ROM, Blu-ray, magnetic tape, floppy disk, optical data storage, and the like, and also include those implemented in the form of a carrier wave (eg, transmission over the Internet). .

The computer readable recording medium can also be distributed over network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion. And, the functional program code for carrying out the technical idea of the present invention can be easily inferred by programmers in the technical field to which the present invention belongs.

As described above, the present invention relates to a function that a profile must basically provide in order to manage profiles installed on an eUICC by an eUICC internal management module or an external interworking device, and relates to profile management data, an external interworking interface, and a security feature. Contains the content.

By defining the property data and policy rules managed by the profile by default, the external interlocking device and the eUICC internal management module can inquire basic information of the profile, modify the necessary information, and synchronize data between the eUICC internal data and the external management system. It is possible. In addition, by defining profile policy rules and defining how they are performed, profile owners (e.g., network service providers, etc.) can assign policy rules necessary for profile management, and how the profile itself can enforce policies. Suggesting.

In addition, in the present invention, by defining the interworking interface that the profile can provide, the minimum interface required to manage the profile is standardized, so that the external interworking system or the eUICC internal interworking device managing the profile acquires the profile information or the information. And a method for modifying the state and the like.

Finally, the present invention proposes a method in which the proposed management function can be performed in a secure environment by defining security characteristics of a profile.

By standardizing the profile data, interface, and security characteristics as described above, it is possible to efficiently and quickly eUICC development and service provision of eco-system operators such as network service providers, eUICC manufacturers, and terminal manufacturers.

Although described above with reference to various embodiments, those skilled in the art can be variously modified and changed within the scope of the present invention without departing from the spirit and scope of the invention described in the claims below. I can understand.

Claims (23)

1. A subscriber authentication device installed in a terminal device,

   Subscriber authentication device comprising a set of one or more network connection application-related data and includes one or more profiles having a unique identifier.
2. The method according to claim 1,

   The network connection application related data,

   And at least one network connection application and associated connection authentication key.
3. The method according to claim 2,

   And the network connection application comprises at least one of parameter data and file structure for network connection.
4. The method according to claim 1,

   And the profile comprises a profile storage unit for managing profile attribute data.
5. The method according to claim 1,

   And the profile comprises a policy execution unit that executes a profile related policy rule.
6. The method according to claim 4,

   The profile attribute data is

   And at least one of a profile identifier, a profile type, profile status information, network operator information, a list of network connection applications belonging to the profile, a privilege, a size of profile data, a profile version, and a type of a profile support terminal.
7. The method according to claim 5,

   The profile policy rule,

   And at least one rule among whether profile deletion is allowed, profile state change notification, profile state change is allowed, profile type change is allowed, and profile initialization is allowed.
8. The method according to claim 1,

   And the profile further comprises an interface for interfacing with an object located in or external to the subscriber authentication device.
9. The method according to claim 8,

   The interface is,

   Receives incoming requests for one or more of profile selection, management of profile attribute data, profile state change, security authentication, profile management key management, and profile registration related management, and returns corresponding values according to the processing result of the request. Subscriber authentication device.
10. The method according to claim 1,

    And the profile provides secure messaging for communication with objects located within or outside the subscriber authentication device.
11. A subscriber authentication module including at least one network-connected application-related data and at least one profile having a unique identifier and installed in a terminal device; And

    Terminal device including a subscriber management module (Subscription Manager) in conjunction with the subscriber authentication module.
12. The method according to claim 11,

    The subscriber management module transmits a change or inquiry request for profile related information to the subscriber authentication module.
13. The method according to claim 12,

    The subscriber authentication module returns a response value according to the change or inquiry request to the subscriber management module.
14. The method according to claim 12,

    The profile related information includes one or more of profile attribute data and profile policy rules.
15. A profile configuration method in a subscriber authentication device embedded in a terminal device,

    Configuring one or more profiles comprising a set of one or more network-connected application related data and having a unique identifier.
16. The method according to claim 15,

    And receiving a change or inquiry request for profile-related information from an object located in or outside the subscriber authentication device.
17. The method according to claim 16,

    And returning a response value according to the change or inquiry request to an object located inside or outside the subscriber authentication device.
18. The method according to claim 15,

    And the profile manages one or more of profile attribute data and profile policy rules.
19. The method according to claim 18,

    The profile attribute data is

    And profile information, profile type, profile status information, network operator information, network connection application list belonging to the profile, privilege, size of profile data, profile version, and type of profile support terminal.
20. The method according to claim 18,

    The profile policy rule,

    And at least one rule of whether profile deletion is allowed, profile state change notification is allowed, profile state change is allowed, profile type change is allowed, and profile is initialized.
21. The method according to claim 18,

    Each profile attribute data and profile policy rule is defined as a separate elementary file under an application specific file (ADF).
22. The method according to claim 18,

    And the profile attribute data and the profile policy rule are defined as one elementary file under a master file.
23. The method according to claim 18,

    Wherein said profile attribute data and profile policy rule are defined as a data object template in a profile.

Images