WO2013066077A1

WO2013066077A1 - Method for managing multiple profiles in an embedded uicc, and embedded uicc and terminal therefor

Info

Publication number: WO2013066077A1
Application number: PCT/KR2012/009129
Authority: WO
Inventors: 이진형; 윤여민; 정윤필
Original assignee: 주식회사 케이티
Priority date: 2011-11-04
Filing date: 2012-11-01
Publication date: 2013-05-10

Abstract

The present invention relates to a technology for managing profiles in an eUICC embedded in a terminal, and more particularly, to a method for efficiently managing profiles in an eUICC in consideration of a case in which multiple profiles are able to be stored in the eUICC, as well as to an embedded eUICC and terminal therefor.

Description

How to manage multiple profiles in the built-in ICC and the built-in IC and terminal

The present invention relates to a technology for managing a plurality of profiles inside an embedded universal integrated circuit card (UIC) embedded in a terminal.

A UICC (Universal Integrated Circuit Card) is a smart card that can be inserted into a terminal and used as a module for user authentication. The UICC may store the personal information of the user and the operator information on the mobile communication provider to which the user subscribes. For example, the UICC may include an International Mobile Subscriber Identity (IMSI) for identifying a user. The UICC is also called a Subscriber Identity Module (SIM) card in the case of the Global System for Mobile communications (GSM) scheme, and a Universal Subscriber Identity Module (USIM) card in the case of the Wideband Code Division Multiple Access (WCDMA) scheme.

When the user mounts the UICC on the user's terminal, the user is automatically authenticated using the information stored in the UICC so that the user can conveniently use the terminal. In addition, when the user replaces the terminal, the user can easily replace the terminal by mounting the UICC removed from the existing terminal to a new terminal.

Terminals requiring miniaturization, for example, terminals for machine-to-machine (M2M) communication, have difficulty in miniaturization of terminals when manufactured in a structure capable of detachable UICC. Thus, an embedded UICC (hereinafter referred to as eUICC or eSIM) structure, which is a detachable UICC, has been proposed. In the built-in UICC, user information using the UICC should be recorded in IMSI format.

The existing UICC can be attached to or detached from the terminal, and the user can open the terminal regardless of the type of terminal or the mobile communication provider. However, from the time of manufacturing the terminal, the manufactured terminal can be assigned an IMSI in the embedded UICC only when the premise that the terminal is used only for a specific mobile communication provider is satisfied. Both mobile operators and terminal manufacturers ordering terminals have no choice but to pay attention to product inventory, which leads to a problem that product prices rise. The user is inconvenient to change the mobile operator for the terminal. Therefore, even in the case of the built-in UICC, a method for allowing a user to open the terminal regardless of the mobile communication provider is required.

On the other hand, the recent introduction of the built-in UICC has become necessary to update the subscriber information of the various mobile operators from the remote to the UICC, accordingly subscription management device (Subscription Manager (hereinafter referred to as "SM") or for subscriber information management) Profile Manager (hereinafter referred to as "PM") is discussed.

On the other hand, on the eUICC, MNO's operational profiles are in application and data form, and may exist in multiple, but only one active operational profile may exist at a time. At this time, the rest becomes an Inactive Operational Profile. In this case, there is a potential disadvantage of two possible performance degradation factors.

An object of the present invention is to provide a method for efficiently managing a plurality of profiles in the eUICC.

Another object of the present invention is to provide a method for efficiently using a plurality of profiles in consideration of a case where a plurality of profiles can be stored in an eUICC.

Another object of the present invention, when a plurality of profiles can be stored in the eUICC, by separately managing data (common data) commonly used by a plurality of profiles among the data available for each of a plurality of profiles, a plurality of profiles in the eUICC To manage your profile efficiently.

Another object of the present invention is to use a common profile (common data) as a kind of profile, in which a plurality of profiles can be stored in the eUICC, and commonly used by multiple profiles among data available for each of the plurality of profiles. New definition, to efficiently manage multiple profiles in the eUICC.

In one aspect, the present invention is an embedded Universal Integrated Circuit Card (eUICC) interworking with a mobile network operator (MNO) and embedded in a terminal, and a plurality of profiles in the form of one or more of applications and data are common. Provided is an eUICC characterized by storing a common profile having common data available.

In another aspect, the present invention is a method for interworking with a mobile network operator (MNO) and managing a profile in an embedded Universal Integrated Circuit Card (eUICC) embedded in a terminal, wherein the eUICC is an application and data. Mounting a common profile of at least one of the following and having multiple data in the eUICC having common data usable in common; And updating the common data of the common profile when the activation profile is loaded.

In still another aspect, the present invention relates to a method of managing multiple profiles in an embedded universal integrated circuit card (eUICC) interworking with a mobile network operator (MNO) and embedded in a terminal, wherein the eUICC is an application and data. Storing a common profile having common data that can be commonly used by a plurality of profiles in the eUICC, which may be in one or more forms; And accessing, by the eUICC, a common profile of the plurality of profiles to the common profile to use the common data.

In another aspect, the present invention is a terminal for providing a communication service in conjunction with a mobile network operator (MNO), a common profile (Common) having a common data that can be commonly used by a plurality of profiles in the form of one or more of applications and data It provides a terminal characterized in that embedded embedded UICC (eUICC: storing a Profile).

Figure 1 shows the overall service architecture including the eSIM (eUICC) to which the present invention is applied.

2 shows a system architecture of an SM separation environment to which the present invention may be applied.

3 illustrates a case where two operational profiles are stored as an internal structure of a general eUICC.

4 illustrates an eUICC internal structure when using a common operational profile, according to one embodiment of the invention.

5 illustrates access control for a common operational profile according to an embodiment of the present invention.

6 through 9 illustrate a process of storing or updating an operational profile in an eUICC according to an embodiment of the present invention.

10 is a flowchart illustrating a plurality of profile management methods in an eUICC according to an embodiment of the present invention.

11 is another flowchart of a method of managing a plurality of profiles in an eUICC according to an embodiment of the present invention.

Hereinafter, some embodiments of the present invention will be described in detail through exemplary drawings. In adding reference numerals to the components of each drawing, it should be noted that the same reference numerals are assigned to the same components as much as possible even though they are shown in different drawings. In addition, in describing the present invention, when it is determined that the detailed description of the related well-known configuration or function may obscure the gist of the present invention, the detailed description thereof will be omitted.

M2M (Machine-to-Machine) terminal, which is actively discussed in the current GSMA, should be small in size. In the case of using the existing UICC, a module for attaching the UICC to the M2M terminal must be separately inserted. If the M2M terminal is manufactured, it is difficult to miniaturize the M2M terminal.

Therefore, an embedded UICC structure that is not detachable from the UICC is being discussed. In this case, the eUICC mounted on the M2M terminal includes information on a mobile network operator (hereinafter referred to as “MNO”) that uses the UICC. It must be stored in the UICC in the form of an identifier (International Mobile Subscriber Identity, IMSI).

However, since the terminal manufactured from the time of manufacturing the M2M terminal can be assigned IMSI in the eUICC only if the premise that the terminal is used only in a specific MNO is established, both the M2M terminal or the MNO ordering the UICC or the M2M manufacturer manufacturing the M2M terminal have a lot of attention to the product inventory. There is a problem that can not only be assigned to the product price will rise, which is a big obstacle to the expansion of M2M terminal.

As such, unlike the conventional removable SIM, the built-in SIM (hereinafter, referred to as eSIM or eUICC) that is integrally mounted on the terminal has many issues regarding the authority to open, additional service business initiative, and subscriber information security due to the physical structure difference. Are present. To this end, the international standardization bodies of the GSMA and ETSI are conducting standardization activities on relevant elements such as operators, manufacturers, SIM vendors (Vendors), and other necessary elements, including top-level structures. SM is at the center of issues as eSIM is discussed through standardization bodies, and issues an important profile (which can be called Operator Credential, MNO Credential, Profile, eUICC Profile, Profile Package, etc.) to eSIM and initiates the process of changing subscriptions. It refers to an entity or a function / role that plays an overall administrative role for eSIM, such as processing.

Recently, the GSMA has proposed a structure that classifies SM into SM-DP (Data Preparation), which plays a role in generating operator information, and SM-SR (Secure Routing), which carries carrier information directly to eSIM. It does not mention the technical actual issuance method.

Accordingly, the present invention proposes a method for managing eSIM by utilizing dynamic encryption key (public key, etc.) generation in the SM role separation environment of GSMA.

In this specification, eSIM and eUICC are used as equivalent concepts.

eSIM attaches the IC chip on the terminal circuit board at the terminal manufacturing stage, and then attaches the SIM data (open information, additional service information, etc.) in software form to OTA (Over The Air) or offline (technology-based connection such as USB to PC). Is a new concept of SIM technology in the manner of issuing through. IC chips used in eSIM generally support hardware-based Crypto Co-Processor (CCP) to provide hardware-based public key generation, and APIs that can be utilized in application (eg applet) based SIM platform (eg , Java Card Platform, etc.). Java Card Platform (Java Card Platform) is one of the platforms that can provide services and load multiple applications, such as smart cards.

Because of limited memory space and security reasons, anyone should not embed an application in a SIM, which requires a SIM service management platform that is responsible for loading and managing applications in addition to the platform for application loading. The SIM service management platform issues data to the SIM memory area through authentication and security with management keys.The Global Platform and Remote File Management (RFM) and RAM (Remote Application Management) of ETSI TS 102.226 It is a standard technology of the service management platform.

SM, one of the important elements in the eSIM environment, eSIM is responsible for issuing communication and additional service data remotely through management keys (UICC OTA Key, GP ISD Key, etc.).

Here, the management key or the eSIM management key or the eUICC management key is an access authentication key to the eSIM for safely delivering the operator information to the eSIM, and is a concept distinct from the encryption key (public key, etc.) mainly dealt with in the present invention. As described below, it may be expressed as eUICC access credentials.

In the GSMA, the roles of SM are classified into SM-DP and SM-SR. SM-DP securely builds IMSI, K, OPc, supplementary service applications, supplementary service data, etc. in addition to the operational profile (or operator information) to form a credential package. SM-SR securely downloads the credential package generated by SM-DP to eSIM through SIM remote management technology such as Over-The-Air (OTA) or GP Secure Communication Protocol (GP SCP).

In addition, the structure of the “circle of trust” of FIG. 1 is proposed below, and an end-to-end between the MNO and the eSIM through the overlap of trust relationships between similar entities or entities. We proposed the concept of establishing a trust relationship. In other words, MNO1 is SM1, SM1 is SM4, SM4 forms a trust relationship with the eSIM, thereby forming a trust relationship between the MNO and eSIM.

Before describing the present invention, terms first used in the present specification will be described.

A mobile network operator (MNO) refers to a mobile communication operator and means an entity that provides a communication service to a customer through a mobile network.

A subscription manager (SM) is a subscription management device and performs a management function of an eUICC.

eUICC Supplier means a person who supplies eUICC module and embedded software (firmware and operating system, etc.).

Device Vendor includes a device's provider, in particular a wireless modem function via a mobile network driven by the MNO, and consequently means a supplier of a device requiring a UICC (or eUICC) form.

Provisioning refers to the process of loading a profile into an eUICC, and a provisioning profile refers to a profile used by a device to connect to a communication network for the purpose of provisioning other provisioning profiles and operational profiles.

Subscription means a commercial relationship for providing a service between a subscriber and a wireless communication service provider.

eUICC access credentials refer to data in the eUICC that allows secure communication between the eUICC and external entities to be set up to manage profiles on the eUICC.

Profile access credentials are data that resides within a profile or within an eUICC, and means data that allows secure communications to be set up between the eUICC and external entities to protect or manage the profile structure and its data. .

A profile is a combination of file structures, data, and applications that can be provisioned or managed within an eUICC.The profile is an operator profile, an operator profile, a provisioning profile for provisioning, and other policy control functions (PCFs). It means all information that can exist in eUICC such as profile.

Operational Profile or operator information refers to all kinds of profiles related to Operational Subcription.

The overall system is described as follows.

The eUICC system architecture to which the present invention can be applied may include a plurality of MNO systems, one or more SM systems, an eUICC manufacturer system, a device manufacturer system including an eUICC, an eUICC, and the like for each entity or subject. The explanation is as follows.

The dashed line in FIG. 1 shows the trust circle, and the two solid lines represent the secure link.

If a scenario is required where subscription information is stored and communicated, it should be done under the approval of the MNO and under the control of the MNO. There must be only one active profile on a single eUICC at any given time, meaning that the active profile is added to a single HLR at a particular time.

The MNO and eUICC must be able to decode the MNO Credentials information, that is, the profile (operational profile, provisioning profile, etc.). The only exception to this could be a third party authorized by a particular MNO, for example a SIM vendor. However, it is not a general function of a third party to do this.

Subscriptions cannot be switched within the eUICC outside of operator policy control. The user must be aware of any changes in the MNO content and its active subscription, must be able to avoid security risks, and have a level of security that is compatible with the current UICC model.

The MNO credential or profile may mean a subscription credential including K, algorithm, algorithm parameters, supplementary service application, supplementary service data, and the like.

The transfer of MNO credentials or profiles must be done in a secure manner from end to end. The transmission can be made in successive steps without breaking the security chain, and all steps in the transmission chain must be made under the recognition and approval of the MNO. No entity in the transport chain should be able to see the MNO credentials clearly, but the only exception may be a third party delegated from a particular MNO, for example a SIM vendor. However, it is not a general function of a third party to do this.

The operator must have complete control over his credentials and the operator must have strong supervision and control over the SM operation.

SM functions must be provided by the MNO or a third party, if provided by the third party, there may be a commercial relationship established between the SM and the MNO.

The SM has no direct relationship with the MNO subscriber for subscription management. Although the MNO has a relationship with the subscriber and should be the entry point for the customer subscription, it is not intended to piggyback on the contractual relationship an M2M service provider (the M2M service provider is an MNO subscriber) may have with its customers.

While the MNOs are swapped, the donor and receiving MNOs may or may not have a prior agreement with each other. There must be a mechanism to approve pre-contracts. The donor operator's policy control function can be defined for the condition of removing his / her credential, and the policy control function (PCF) can implement this function.

The architecture introduces a feature defined as SM, and SM's primary role is to prepare and deliver a package or profile containing the MNO credentials to the eUICC. The SM function may be provided directly by the MNO, or the MNO may contract with a third party to obtain the SM service.

The role of SM can be divided into two sub-functions such as SM-SR and SM-DP.

Indeed, these SM-SR and SM-DP functions may be provided by another entity or may be provided by the same entity. Therefore, there is a need to clearly demarcate the functions of SM-DP and SM-SR, and to define the interface between these entities.

SM-DP is responsible for secure preparation of package or profile to be delivered to eUICC, and works with SM-SR for actual transmission. The key functions of the SM-DP are 1) managing the functional characteristics and certification levels of the eUICC, and 2) one of the MNO credentials or profiles (e.g., IMSI, K, supplementary service applications, supplementary service data). Some of these are potentially managed by the MNO, and 3) the ability to calculate the OTA package for download by the SM-SR. Could be added.

If the SM-DP function is provided by a third party, security and trust relationships become very important. In addition to real-time provisioning, SM-DP can have a significant amount of background processing, and the requirements for performance, scalability and reliability are expected to be important.

SM-SR is responsible for securely routing and delivering the credential package to the corresponding eUICC. The key features of the SM-SR are 1) managing OTA communication with the eUICC via a ciphered VPN, and 2) other SM-SR to form an end-to-end up to the eUICC. To manage communication with the eUICC, 3) to manage eUICC data used for SM-SR OTA communication provided by the eUICC provider, and 4) to protect the communication with the eUICC by filtering only allowed entities. (Firewall function).

The SM-SR database is provided by eUICC vendors, device (such as M2M terminal) vendors, and potentially MNOs, and can be used by MNOs through the SM-SR mesh network.

The circle of trust enables end-to-end security links during provisioning profile delivery, and the SM-SR shares the trust circle for secure routing and eUICC discovery of the provisioning profile. The MNO can be linked with SM-SR and SM-DP entities in the trust circle, and can provide this functionality on its own. EUICC and MNO Credentials to prevent illegal use of eUICC (cloning, illegal use of credentials, denial of service, illegal MNO context changes, etc.) without violating MNO's contractual and legal obligations with respect to its customers. There is a need for a secure end-to-end link between.

That is, in FIG. 1, 110 represents a trust circle formed between SMs, more specifically, between SM-SR members, 120 represents a trust circle of MNO partners, and 130 represents an end-to-end trust link.

2 illustrates a configuration in which an SM-SR and an SM-DP are located in a system in an SM separation environment.

As shown in FIG. 2, the SM is divided into an SM-DP for safely preparing various profiles related to the eUICC (operational profile, provisioning profile, etc. of the MNO), and an SM-SR for routing the same. It can be linked with the SM-SR in a trust relationship, and the SM-DP is linked with the MNO system.

Of course, the arrangement of the SM-DP and the MNO system may be implemented differently from FIG. 2. (Ie SM-DP can be linked with SM-SR and MNO system can be linked with SM-DP)

In such an environment, the MNO's operational profiles on the eUICC are in application and data form, can exist in multiple, and only one Active Operational Profile will exist at a time. At this time, the rest becomes an Inactive Operational Profile. In this case there are potentially two performance degradation factors.

First, the slow speed, and second, the problem of memory resources.

The second problem in this case is that if a plurality of operational profiles have contents of elementary files (EF) independently of each other, memory resource waste may occur. In addition, there is a requirement that data such as a phonebook stored by a specific MNO in the eUICC is alive because the user is the same even if the MNO is changed and another operational profile is activated.

FIG. 3 illustrates a case where two operational profiles are stored as an internal structure of a general eUICC embedded in a device. In FIG. 3, the device is also referred to as a terminal.

In this case, the eUICC has preloaded the MNO's operational profiles in advance, or there are multiple operational profiles in the process of changing the MNO, and only one operational profile remains active at any one of them. do. At this time, each operational profile has all the basic files of MNO independently.

However, the eUICC may be an M2M terminal or a mobile terminal. As the memory capacity of the eUICC increases, the cost increases. From this point of view, if each Operational Profile has contents of MNO's basic files independently, the following problems can occur.

1. Waste of memory resources is incurred.

2. It also slows down the process of sending an operational profile remotely and installing it.

In addition, data such as phonebooks stored by a particular MNO in the eUICC have a requirement that the user wants to be alive because the MNO is changed and other operational profiles are activated.

That is, user data or data that does not need to be erased should be maintained even on MNO changes and swap of operational profiles. Here, swap of an operational profile means activation and deactivation of an operational profile, or deletion and loading.

Accordingly, the proposed method of the present invention is to create and use contents that can be commonly used in common operational profiles (EF: Elementary Files) that can be commonly used by multiple operational profiles.

Accordingly, an embodiment of the present invention provides a method of separately managing data commonly used among parameters or fields of all operational profiles in an eUICC storing various communication schemes and / or operational profiles of various operators. To provide.

According to an embodiment of the present invention, data commonly used among parameters or fields of all operational profiles may be used in an eUICC that stores various communication schemes and / or operational profiles of various operators. In addition to that, separate data unique to each communication method or communication service provider to be managed separately.

In this specification, an active profile or an activation profile means a profile that a file or an application can select by the UICC-Terminal interface under the control of a Policy Control Function (PCF) associated with an MNO.

In addition, the common operational profile refers to data of contents that can be used in common by the operational profiles of respective MNOs among the operational profile contents.

As shown in FIG. 4, the contents (common profile data) that the common operational profile of the MNO may have and the contents (unique profile data of each MNO or communication method) that each operational profile may have may be as follows. have. However, it is possible to subtract the contents that the MNO does not use in the operational profile from the contents uniquely independent of the operational profiles.

-The content of common operation profile is common to both 2G, 3G and LTE.

-The contents of the common operational profile may consist of the following files. Firstly, files that the user changes (ex. Phonebook), and secondly, files in which values obtained from the terminal system are stored, that is, files changed by the terminal system (ex. Location information: LOCI, SLOCI )) And so on.

A scenario where a common operational profile is populated is as follows.

The common operational profile is filled with default values on initial load. (ex. May be filled with "F" values or null values as default values in memory.)

When the operational profile of MNO1 is loaded, the common operational profile contents (files) that need to be changed by the terminal system are filled. (ex. LOCI, SLOCI, etc.)

The common operational profile file contents that can be changed by the user are filled in. (ex. phonebook, SMS, etc.)

The carrier change is made from MNO1 to MNO2.

The common operational profile contents (files) that need to be changed by the terminal system when the MNO2 operational profile is loaded are updated. (ex. LOCI, SLOCI, etc.)

The user can still read the contents of the common operational profile that was changed by the user in the MNO1 subscription state. (ex. phonebook, SMS, etc.)

The contents of the common operation profile files that have been changed by the user in the subscription state of MNO1 are updated (ex. Phonebook, SMS, etc.).

The data included in the common profile is a file structure including items such as a master file (MF), a universal subscriber identity module (USIM), GSM-ACCESS, GSM, and TELECOM, and information related to each item. It may be. Information related to each item in the above example may be as Tables 1 to 6 below, but is not limited thereto.

Table 1

TABLE 2

TABLE 3

Table 4

Table 5

Table 6

In the case of a phonebook, the number of initial creations in a common operational profile is made to be controlled by an input parameter.

On the other hand, the unique data parameters (fields) that the plurality of operational profiles independently have, Universal Subscriber Identity Module (USIM), IP Multimedia Service Identity Module (ISIM) -ACCESS, Home Node B (HNB), GSM, It may have a file structure including items such as TELECOM and information related to each item. Information related to each item mentioned above may be as follows, but is not limited thereto.

Independent data of multiple operational profiles may include items (parameters or fields) included in Tables 7 to 11 below, but are not limited thereto.

TABLE 7

Table 8

Table 9

Table 10

Table 11

In Tables 1 to 11, the information related to each item may be included in an elementary file (EF) defined in the eUICC or may be the elementary file itself.

Referring to FIG. 5, in the embodiment of the present invention, the content of the common operational profile may control access of another application (another profile) in the terminal eUICC through the following access control.

When another application in the eUICC accesses a common operational profile to read data, it must always be given an operational profile ID (also called an "operational ID" or "profile ID"), along with certain parameters (access parameters). In this case, the common operational profile causes the pre-registered operational profile ID and the promised parameters to respond only to the identified request. (In the figure below, unregistered profiles will prohibit access.)

In other words, referring to FIG. 5, in order to access a common operational profile and read data (information, value, etc.) from the common operational profile, another profile (application) such as an operational profile is used. Profile ID and access parameter together with the access request to the common operational profile.

6 illustrates a case where a common operational profile is mounted in an eUICC when an eUICC is embedded in a terminal according to the present invention.

In this case, when the common operational profile is mounted, the phonebook file can be made to control the number of inputs at the time of initial generation in the common operational profile.

7 illustrates the case where the original MNO loads an operational profile.

Referring to FIG. 7, when the MNO first loads an operational profile, 1) externally loads an operational profile, and 2) assigns an operational profile ID (or an operational ID or profile ID) to a common offer. 3) the access parameter is obtained from the common operational profile.

8 is a diagram illustrating a process of reading or writing a value (data) required for a common operational profile in a terminal (device), that is, a terminal system.

Through the process illustrated in FIG. 8, data (common data) included in the common operational profile may be generated or updated.

9 illustrates the case of changing the operational profile from MNO1 to MNO2.

Referring to FIG. 9, in case of changing the operational profile from MNO1 to MNO2, 1) externally load the operational profile, 2) register the operational profile ID with the common operational profile, and 3) access This can be done by obtaining a parameter from a common operational profile.

According to the method of managing a plurality of profiles in an eUICC according to an embodiment of the present invention described above, each of a plurality of operational profiles in an eUICC is common among data (which may be information, contents, files, etc.) for use. By storing a common operational profile having common data that can be used, each of the plurality of operational profiles need only have remaining data (unique data) except common data among data for use.

Using a plurality of profile management methods in the eUICC according to an embodiment of the present invention, since each of the plurality of operational profiles does not need to have common data, it is possible to reduce waste of memory resources of the eUICC.

In addition, the plurality of profile management methods in the eUICC according to an embodiment of the present invention described above provides inter-profile access control in the case where a plurality of operational profiles use common data of the common operational profile. can do.

Thus, unauthorized access to the profile common operational profile can be controlled.

As described above, a plurality of profile management methods in the eUICC according to an embodiment of the present invention described above, and a terminal incorporating the eUICC and the eUICC therefor will be described once again below. However, the operational profile and the common operational profile described above are one type of profile, hereinafter, the operational profile is described as a profile, and the common operational profile is described as a common profile.

As illustrated in FIGS. 4 to 9, an eUICC according to an embodiment of the present invention is a UICC interworking with a mobile network operator (MNO) and embedded in a terminal. A plurality of profiles are stored in a common profile having common data that can be used in common.

The eUICC may include a memory resource as a configuration in order to store one or more profiles, a common profile, and the like.

The data used by each of a number of profiles already stored in the eUICC or to be stored in the future does not require that the profile be used in common with other profiles and that the common profile has a common profile and that the profile does not need to be used in common with other profiles. It may include unique data data that the profile has independently.

For example, data (eg, EF files) used by one first profile (eg, an operational profile of the first MNO) may include common data and unique data. The common data is data that the first profile can use in common with other profile (s) among the data used by the first profile, and the unique data is profile (s) different from the first profile among the data used by the first profile. This data does not need to be used in common with. Also, common data is included in a common profile (eg, common operational profile), and unique data is included in the first profile.

In addition, the common data mentioned above may include one or more of eUICC identification information (eg, eICCID) and user data.

User data (also referred to as customer data or subscriber data) that may be included in the common data may include, for example, data about one or more of a phonebook and a message in which contacts such as a phone number are stored. . Here, the message may be, for example, a Short Message Service (SMS) message, a Multimeda Message Service (MMS) message, or the like.

In addition, the aforementioned common data may include data (terminal system related data) obtained from the terminal system when the activation profile is loaded.

The terminal system related data that may be included in the common data may include, for example, location information. Here, the location information may include, for example, LOC (LOCcation Information), PSLOCI (Packet Switched LOCation Information), and the like.

The common data mentioned above may include, for example, a master file (MF), a universal subscriber identity module (USIM: Universal Subscriber Identity Module, etc.), a network access (eg, GSM- as shown in Tables 1 to 6). ACCESS, etc.), a communication network (eg, GSM, etc.), telecom (Telecom), etc., and may have a file structure containing one or more information related to each item. The information (content) related to each item may be in the form of an elementary file (EF) of the eUICC.

Meanwhile, except for the common data of the common profile among the data used by each of the plurality of profiles, the unique data of each of the plurality of profiles independently may be, for example, as shown in Tables 7 to 11 above. One or more of the following: Universal Subscriber Identity Module (USIM), Access to IP Multimedia Service Identity Module (ISIM), Base Station (e.g., Home Node B, etc.), Network (e.g., GSM), and Telecom And a file structure including one or more pieces of information related to each item. The information (content) related to each item may be in the form of an elementary file (EF) of the eUICC.

The common data of the common profile may be updated based on at least one of terminal system-related data obtained from the terminal system and user data according to a user input when the activation profile is loaded.

As described above, the common data included in the common profile may include various types of information or contents, and among them, one or more of eUICC identification information (for example, eICCID) and user information (for example, phone book, etc.) may be included in the common data. Information that must be included and can be included in common data. Other information except for the eUICC identification information (e.g. eICCID, etc.) and user information (e.g., phonebook, etc.) To Table 6) may optionally be included in common data.

Meanwhile, in the common profile, access of another profile may be controlled according to a profile ID registered in advance. In other words, when a profile attempts to access a common profile, access to the common profile may be controlled according to the profile ID of the profile.

For example, the profile ID of profile 1 is registered in the common profile, and then profile 1 sends an access request and profile ID to the common profile, so that the common profile has previously registered the profile ID received from profile 1 It checks with the ID and responds to the access request.

Each of the plurality of profiles described above may be an Operational Profile of a corresponding MNO, and the common profile may be a Common Operational Profile.

Referring to FIG. 10, in a method of interworking with an MNO and managing a profile in an eUICC embedded in a terminal according to an embodiment of the present invention, an eUICC is one or more types of applications and data, and multiple profiles inside the eUICC are common. Mounting a common profile that can have common data available (S1000), and based on one or more of the terminal system-related data obtained from the terminal system at the time of loading the activation profile and the user data according to the user input, etc. Updating the common data of the common profile (S1002) and the like.

Common data (contents, information, files, etc.) included in the common profile mentioned above are data that can be used by a plurality of profiles in common, and are data that need to be maintained even if the activation profile is changed.

Such common data may include, for example, eUICC identification information (eg, eICCID).

In addition, the common data may include user data by a user input, and the user data may include, for example, data about one or more of a phonebook and a message.

In addition, the common data may include terminal system-related data obtained from the terminal system, wherein the terminal system-related data may include, for example, location information such as LOC (LOCcation Information) and PSLOCI (Packet Switched LOCation Information). It may include.

On the other hand, as shown in Figure 10, a plurality of profile management method in the eUICC according to an embodiment of the present invention, after the above-described step S1002, the step of loading the activation profile changed according to the change of the activation profile (S1004) and Updating common data of the common profile based on terminal system related data obtained from the terminal system, and maintaining usable data after the change of the activation profile among the common data in the state before the change of the activation profile (S1006); It may further include.

For example, in the above-described step S1004, when the user changes the carrier from the first MNO to the second MNO, the profile (operational profile) of the first MNO is activated before the carrier change. After the carrier change, it may mean that the profile (operational profile) of the first MNO is deactivated and the profile (operational profile) of the second MNO is activated. That is, it may mean that the activation profile is changed from the profile of the first MNO to the profile of the second MNO.

Meanwhile, the activation profile mentioned above may be an operational profile of a mobile network operator (MNO) to which a user currently subscribes.

Referring to FIG. 11, in the method of managing a plurality of profiles in an eUICC interworking with an MNO and embedded in a terminal according to an embodiment of the present invention, a plurality of profiles in an eUICC in which the eUICC may be one or more of an application and data, etc. Storing a common profile having common data available in common (S1100), and a specific profile (which may be an active profile) of the plurality of profiles, the eUICC accesses the common profile to use the common data Step S1104; and the like.

In step S1104 described above, the eUICC may register a profile accessible to the common profile and allow access to the common profile only for the registered profile.

To this end, in step S1104, the eUICC may control whether a specific profile can access the common profile according to a profile ID registered in advance.

As such, in order to control access to the common profile according to the pre-registered profile ID, as shown in FIG. 11, before the step S1104, the step S1102 of registering a specific profile to be accessed with the common profile is performed. You may need more.

In step S1102, the eUICC registers the specific profile as a profile accessible to the common profile by registering the profile ID in the eUICC profile with the common profile and the profile in the eUICC obtaining an access parameter from the common profile. Can be.

In the step S1104 performed after this step S1102, a specific profile in the eUICC sends its profile ID and access parameters to the common profile along with a request for access to the common profile, and the common profile has been verified the profile ID and access parameters. It allows access only to access requests, so that a particular profile can access a common profile to read or write some data that the common profile has and is intended to use.

Common data that can be commonly used by a plurality of profiles may include, for example, one or more of eUICC identification information (eg, eICCID) and user data. Here, the user data may include, for example, data about one or more of a phonebook and a message.

In addition, the common data in which a plurality of profiles can be commonly used may include terminal system related data obtained from the terminal system. Here, the terminal system related data may include, for example, location information such as LOC (LOCcation Information), PSLOCI (Packet Switched LOCation Information), and the like.

The device illustrated in FIGS. 4 to 9 is a terminal providing a communication service in cooperation with a mobile network operator (MNO), and the terminal includes a plurality of profiles in the form of one or more of applications and data. The (operational profile) may include a built-in eUICC that stores a common profile (common operational profile) having common data that can be commonly used.

The common data included in the common profile may include, for example, one or more of eUICC identification information (eg, eICCID) and user data. Here, the user data may include, for example, data about one or more of a phonebook and a message.

In addition, the common data included in the common profile may include terminal system related data obtained from the terminal system. Here, the terminal system related data may include, for example, location information such as LOC (LOCcation Information), PSLOCI (Packet Switched LOCation Information), and the like.

As described above, the present invention can provide a method for efficiently managing a plurality of profiles in an eUICC.

In addition, according to the present invention, in consideration of the case where a plurality of communication schemes and / or profiles of various operators can be stored in the eUICC, a method for efficiently using a plurality of profiles can be provided.

According to the present invention, when multiple communication schemes and / or profiles of various service providers can be stored in the eUICC, data (common data) commonly used by a plurality of profiles among data available for each of the plurality of profiles can be used. By managing separately, multiple profiles in the eUICC can be managed efficiently.

According to the present invention, when multiple communication schemes and / or profiles of various service providers can be stored in the eUICC, data (common data) commonly used by a plurality of profiles among data available for each of the plurality of profiles can be used. As a kind of profile, it is newly defined as a common profile, so that many profiles in the eUICC can be managed efficiently.

The above description is merely illustrative of the technical idea of the present invention, and those skilled in the art to which the present invention pertains may make various modifications and changes without departing from the essential characteristics of the present invention. Therefore, the embodiments disclosed in the present invention are not intended to limit the technical idea of the present invention but to describe the present invention, and the scope of the technical idea of the present invention is not limited thereto. The protection scope of the present invention should be interpreted by the following claims, and all technical ideas within the equivalent scope should be interpreted as being included in the scope of the present invention.

CROSS-REFERENCE TO RELATED APPLICATION

This patent application is related to the patent application No. 10-2011-0114765 filed with Korea on November 4, 2011 and patent application No. 10-2012-0122793 filed with Korea on November 1, 2012. Priority is claimed under section (a) (35 USC § 119 (a)), all of which is incorporated by reference in this patent application. In addition, if this patent application claims priority for the same reason for countries other than the United States, all its contents are incorporated into this patent application by reference.

Claims

An embedded UICC (eUICC) embedded in the terminal and interworking with a mobile network operator (MNO),

EUICC, characterized in that for storing a common profile having a common data that can be commonly used by a plurality of profiles in the form of one or more of applications and data.
The method of claim 1,

The common data includes at least one of eUICC identification information and user data.
The method of claim 2,

The user data, eUICC, characterized in that it comprises data for one or more of the phonebook (Phonebook) and the message (Message).
The method of claim 1,

The common data is eUICC, characterized in that it comprises data obtained from the terminal system.
The method of claim 1,

The common profile is,

EUICC, characterized in that access of another profile is controlled based on a profile ID registered in advance.
As a method of interworking with a mobile network operator (MNO) and managing a profile in an embedded Universal Integrated Circuit Card (eUICC) embedded in a terminal,

Mounting, by the eUICC, a common profile in which one or more of an application and data are present, and multiple profiles within the eUICC may have common data that can be commonly used; And

When loading an activation profile, updating the common data of the common profile.
The method of claim 6,

The common data, eUICC identification information, characterized in that a plurality of profile management method in the eUICC.
The method of claim 6,

In the updating, when the activation profile is loaded, a plurality of profiles in the eUICC are updated based on one or more of data obtained from a terminal system and user data according to a user input. How to manage.
The method of claim 8,

The user data includes data about one or more of a phonebook and a message,

The data obtained from the terminal system, a plurality of profile management method in the eUICC, characterized in that the location information.
The method of claim 6,

After the updating step,

Loading the changed activation profile according to the change of the activation profile; And

Updating the common data of the common profile based on data obtained from the terminal system, and maintaining data available after the change of the activation profile among the common data in a state before the change of the activation profile; How to manage multiple profiles in eUICC.
As a method of managing multiple profiles in an embedded universal integrated circuit card (eUICC) interworking with a mobile network operator (MNO) and embedded in a terminal,

Storing, by the eUICC, a common profile having common data that can be commonly used by a plurality of profiles within the eUICC, which may be in the form of one or more of an application and data; And

And the eUICC accessing the common profile by a particular one of the plurality of profiles to use the common data.
The method of claim 11,

In the accessing step, the eUICC,

And controlling whether the specific profile can access the common profile according to a profile ID registered in advance.
The method of claim 12,

Prior to the accessing step,

The specific profile registers the profile ID to the common profile, and the specific profile in the eUICC obtains an access parameter from the common profile, thereby registering the specific profile as a profile accessible to the common profile. The method of managing a plurality of profiles in the eUICC further comprising a step.
A terminal providing a communication service in conjunction with a mobile network operator (MNO),

A terminal comprising a built-in embedded universal integrated circuit card (eUICC) for storing a common profile (common profile) having a common data that can be commonly used for a plurality of profiles in the form of one or more applications and data.
The method of claim 14,

The common data terminal, characterized in that it comprises one or more of eUICC identification information and user data.