KR101893934B1 - Method and Embedded UICC for Management and Execution of Policy Rule - Google Patents

Abstract

The present invention relates to a method for managing and executing policy rules in an eUICC, and provides a function of controlling (defining, setting, updating, etc.) policy rules according to requirements of a service provider or a service provider, , And a method and an eUICC for policy rule management and execution that provide a function of enforcement such as activation, deactivation, loading, or deletion of profiles based on the thus-controlled policy rule.

Description

A method for managing and executing policy rules, and an eUICC (Method and Embedded UICC for Management and Execution of Policy Rule)

The present invention relates to a method for managing (defining, updating, deleting, etc.) policy rules in an embedded UICC (eUICC: hereinafter referred to as "eUICC" .

In a conventional removable Universal Subscriber Identity Module (USIM) environment, policy rules of all providers and service providers are managed only on the server, and these policy rules are controlled and enforced on the server.

Conventionally, the method of managing and applying all the policy rules in the server in the existing USIM environment is different from the process of opening the eSIM of the server architecture of the embedded USIM (eSIM: Embedded Universal Subscriber Identity Module) Difficulties exist due to the business requirements of various stakeholders.

KR 10-2008-0021178 A US 2011/0158090 A

In order to solve the prior art, there is a need to define and apply the contents and structure of the policy rules existing on the eSIM, and therefore user cases for managing profiles and eSIM through policies on the eSIM are required .

Accordingly, the present invention invented a method for defining and applying the contents and structure of policy rules existing on the eSIM for resolving the prior art, and through this, user cases for managing profiles and eSIMs through policies on the eSIM are proposed do.

In more detail, the present invention provides a function of controlling the eSIM profiles according to the requirements of the service provider / service provider, and activating / deactivating / loading / deleting / disable / load / delete), and so on.

Also, the present invention provides a function of enabling / disabling / loading / deleting (enbling / disabling / loading / deleting) profiles according to policy rules according to capability on the eSIM.

Also, the present invention provides a function to enforce the profiles on the eSIM based on policy rules such as lock according to the requirements of the service provider / service provider.

In addition, the present invention is a built-in UICC (eUICC) for policy rule management and execution, which defines actions and conditions required to implement a policy, and includes policy rules for each profile and for eUICC A policy rule storage unit for storing policy rules including policy rules; A policy control function for defining, updating or deleting the policy rules; And an eUICC for policy rule management and execution including a policy enforcement function that executes the policy rules.

The present invention also provides a method for policy rule management and execution on an embedded UICC (eUICC), wherein the eUICC defines an action and a condition required to implement the policy, And policy rules for the eUICC; The eUICC setting the policy rules through a policy control function; And the eUICC executing the set policy rules through a policy enforcement function.

According to another aspect of the present invention, there is provided a method for policy rule management and execution on an embedded UICC (eUICC), comprising: setting a policy rule through a policy control function by a first external entity; And performing a policy enforcement function on the set policy rule such that the second external entity applies the set policy rule to the target profile or the eUICC as a whole do.

In the eUICC environment in which a profile is loaded remotely and multiple profiles are appropriately managed through the present invention, a profile owner (e.g., MNO (Mobile Network Operator) or a service provider, etc.) Change / delete service through the function of activation / deactivation / load / deletion (enble / disable / load / delete) of business flow and profile in the same manner as the policy rule do.

Figure 1 is an example of a third party profile for direct management by a service provider / OEM manufacturer according to an embodiment of the present invention.
FIG. 2 is a block diagram illustrating a configuration of a policy control function (PCF), a PCF rule, a policy enforcement function (PEF), and a target for policy rules on an eUICC according to an exemplary embodiment of the present invention. FIG. 4 is a diagram showing an architecture for a mobile terminal. FIG.
3 is a diagram illustrating a logical hierarchy of PCF rules according to an embodiment of the present invention.
FIG. 4 is a diagram illustrating a basic process for controlling and enforcing policy rules according to an embodiment of the present invention.
5 and 6 are diagrams illustrating an application process for controlling and implementing policy rules according to an embodiment of the present invention.
7 is a diagram of targets executed based on policy rules according to an embodiment of the present invention.
8 is a block diagram of an eUICC for policy rule management and execution according to an embodiment of the present invention.
9 is a flowchart of a method for policy rule management and execution according to an embodiment of the present invention.
10 is another flow diagram of a method for policy rule management and execution according to an embodiment of the present invention.

Hereinafter, some embodiments of the present invention will be described in detail with reference to exemplary drawings. It should be noted that, in adding reference numerals to the constituent elements of the drawings, the same constituent elements are denoted by the same reference symbols as possible even if they are shown in different drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear.

Unlike the existing detachable SIM, the integrated SIM (eSIM), which is integrated in the terminal, has many issues such as the opening authority, the initiative of the supplementary service business, and the subscriber information security due to the difference in the physical structure. To this end, the GSMA and ETSI international standardization organizations have been carrying out standardization activities on relevant elements such as operators, manufacturers, SIM vendors and other necessary elements including the top-level structure. As eSIM is discussed through standardization bodies, the central issue is the SM, called the Subscription Manager, which issues Operator Credentials (profile) to eSIM and processes the change of subscription. Means the entity performing the management role or its functions and roles.

In this environment, if you actually manage a profile remotely (for example, an Operational Profile or a Carrier Profile or a Provisioning Profile), you can use this profile (either an Operational Profile, a Carrier Profile, a Provisioning Profile, There is a principle and requirement that the policy of the business requirement in the existing removable USIM environment should be implemented in the eSIM environment as it is, including the policy of the owner chain or service provider of the party profile) do. Hereinafter, the embedded UICC (eUICC) is used in parallel with the eSIM.

Basically, there may be multiple profiles (e. G., Operational Profile or Operator Profile, Provisioning Profile, or a third party profile) on the eSIM, unlike conventional removable USIMs.

This environment presents difficulties in meeting the following requirements.

1. A mechanism is needed to control so that only one profile can be activated at any moment, even if several carrier profiles are present on the eSIM. For the following reasons, we need the ability to enable, disable, load, or delete multiple profiles on the eSIM. Here, "Enable" means technically selecting the profile.

(1) eSIM may want to activate a third party profile with a carrier profile by a service provider that essentially intends to load multiple profiles at the same time and utilize it for a separate service. Therefore, it needs a function to control it.

A third party profile definition: a profile that is not present within the carrier profile and is provided by a separate (third party) service provider that is equipped with a third party application

(2) When multiple carrier profiles are loaded into eSIM, the device may wish to provide one or more profiles that are activated according to the characteristics of the terminal and the requirements of the carrier / service provider. It is necessary to control this

2. Requires a mechanism to provide eSIM locking

(1) A mechanism to lock eSIM is needed due to problems such as subsidy, contract term, and theft. ESIM essentially loads the profiles of various carriers through the subscription manager (SM), so it controls the lock status of eSIM It may be necessary to do.

3. When you want to load, enable, disable, or delete a profile on the eSIM, the ability of eSIM to enforce it according to whether or not it is allowed need.

In the present invention, in order to solve the conventional technology, the contents and structure of the policy rule existing on the eSIM are defined and applied, and the user case for managing the profile and the eSIM through the policy on the eSIM ).

An enable status of a profile refers to a state in which an external entity can select the profile.

1. Provide the ability to control eSIM profiles based on the requirements of the provider / service provider and to enable, disable, load, or delete profiles based on these controlled policy rules. .

2. Provide the ability to enforce the activation, deactivation, loading, or deletion of profiles according to policy rules according to Capability on eSIM.

3. Provide the ability to enforce eSIM profiles based on policy rules, such as SIM locks, according to the requirements of the provider / service provider.

Figure 1 is an example of a third party profile for direct management by a service provider / OEM manufacturer according to an embodiment of the present invention.

With reference to Figure 1, some terms related to the present invention are briefly defined.

A Profile may be a combination of one or more of file structure, data, and applications that are present or provisioned on the eUICC 100.

The Provisioning Profile includes at least one network access applications and a profile between the eUICC 100 and the SM-SR, which is installed in the eUICC 100 and has transmission capabilities for eUICC 100 management, And an associated network access credentials that enable access to the communication network to provide management.

The Operational Profile is a profile that includes at least one network access applications and associated network access credentials.

The MNO (Mobile Network Operator) is an entity that provides communication services to customers through a mobile network. However, the MNO may have the same meaning as a communication company or a communication service provider.

Subscription Manager - Secure Routing (SM-SR: Subscription Manager - Secure Routing) may mean the role of performing functions that directly manage the operational profile and the provisioning profile on the eUICC 100 securely.

A third party profile (or a second party application) may be initiated by the third party service provider either directly through the SM-SR without the MNO's transfer of authority / , Deactivated, deleted, loaded).

FIG. 2 is a block diagram illustrating a policy control function (PCF), a PCF rule, a policy enforcement function (PEF), and a target for a policy rule on the eUICC 100 according to an exemplary embodiment of the present invention. (Architecture) for the Target (Target).

Referring to FIG. 2, in a policy rule, a policy rule (A) indicated by a bold box is a policy rule (s) associated with a currently active profile, and a policy enforcement function Only the policy rule (s) associated with the profile can be performed.

Referring to FIG. 2, in the policy rule, the remaining policy rules except for the policy rule A indicated by a bold box are the policy rules associated with the profile that is currently deactivated in the eUICC 100. It can not perform policy enforcement functions.

Referring to FIG. 2, the policy rules logically include a policy rule for a profile (also referred to as a policy rule associated with a profile), a policy rule for the eUICC 100 (a policy rule for eUICC 100), which is also referred to as a policy rule).

The two kinds of policy rules divided in this way may be physically managed as separate locations (or files) or as a single location (or one file).

In addition, policy rules may be physically internal or external to the profile (s).

Referring to FIG. 2, in External Entities, a Profile Owner or Creator is a profile owner or creator, which, as the entity or profile owner of a profile, creates policy rules for a profile ) Is an entity that has the authority to access and control.

Referring to FIG. 2, a profile manager or an enforcer (Profile Manager or Enforcer) of External Entities is an entity authorized to enforce the management of profiles existing on the eUICC 100. Here, management of the profiles may mean loading, activating, deactivating, deleting, etc. of the profile.

Referring to FIG. 2, in External Entities, a Profile Owner or Creator and a Profile Manager or an Enforcer are separately separated according to the requirements of the provider and the service provider It may or may not exist as a single entity.

2, the external entities may be servers connected to the eUICC 100 via a network, or terminals connected to the eUICC 100 or including the eUICC 100 .

On the other hand, the state of the profile on the eUICC 100 can be divided into activation (enable state = selectable), inactivation (disabled state = not selectable), and deletion.

FIG. 3 is a diagram showing a logical hierarchy of PCF rules according to an embodiment of the present invention.

Referring to FIG. 3, the policy rules can be divided into a policy rule for the profile and a policy rule for the eUICC (100).

Referring to FIG. 3, the policy rules that make up the profile can exist from 0 to a maximum number (Maximum) according to the policy rule for the eUICC 100.

The policy is a principle that reflects rules for controlling each entity (e.g., Subscription Manager) and the eUICC (100) necessary for remotely managing the eUICC (100).

A policy enforcement function is a function for executing a policy rule.

In addition, the policy enforcement function can evaluate the conditions of the policy rule and determine the performance of the commands.

A policy control function can define functions for updating or deleting policy rules for each policy.

Functions such as the above-described policy control function and policy enforcement function may be implemented by the functions provided by the platform inside the eUICC 100, or may be newly implemented and provided on the platform have.

The policy control function list may include the following items. The names of the functions can be different under the same premise because the purpose of the function is important. Also, the type of function may be added.

■ Execute (): Performing policy rules

- Only the policy rule for the profile currently active on the eUICC (100) is performed. The corresponding function is not performed for the disabled profile.

The policy control function list may include the following items. The names of the functions can be different under the same premise because the purpose of the function is important. The types of functions may also be added / deleted.

For example, functions such as Add () and Update () are the same as Update (), and the Add () function can be deleted.

It is also possible to add control functions such as Read () and Select (), for example.

■ Update (): Update policy rule values

■ Delete (): Remove a policy rule entry

■ Add (): Add policy rule yield

■ Other ...

Access conditions of external entities for performing policy control function and policy enforcement function are shown in Table 1 (policy rule for profile) and Table 2 policy rules for eUICC).

First, the types of credentials to be used for a security condition for a policy control function and a policy enforcement function are as follows.

Profile access credentials: Profile data such as data existing in the profile so that secure communication between the eUICC (100) and external entities can be set up to manage the structure and data of the profile.

Profile Installer Credentials: Profile installed in the eUICC 100 such that the profile downloaded from the external entity is decrypted and installed on the eUICC 100

Profile Management Credentials: Profile management credentials are data that exist in the eUICC 100 so that secure communication can be established between the external entities and the eUICC 100 for profile management on the eUICC 100. [

If the policy control function and the policy enforcement function need to be performed only by the authorized entity, the confidentiality, integrity, and authentication of each function are required.

Confidentiality, integrity, and authentication in the performance of these functions are determined as a combination of OR operations.

For example, Function 1 can be combined with confidentiality, Function 2 can be combined with confidentiality, Function 3 can be combined with confidentiality, integrity, and authentication. have.

The policy control function must be able to use the appropriate credentials in the eUICC 100 to satisfy confidentiality, integrity, and authentication.

For example, a credential for this may be a Profile Access Credentials or Profile Installer that can only be performed by authorized entities such as a Profile Owner or a Creator. Credentials).

The policy enforcement function must be able to use the appropriate credentials in the eUICC 100 to satisfy confidentiality, integrity, and authentication.

For example, the credentials for this may be Profile Management Credentials, which can only be performed by authorized entities, such as a Profile Manager or a Profile Enforcer.

In the following, the policy rules for the profile and the policy rules for the eUICC 100 with reference to Table 4 will be described in more detail with reference to Table 3 below.

First, referring to Table 3, a description will be given of a policy rule (a policy rule associated with each profile) for a profile.

Table 3 shows an example of the file structure (structure) of the policy rule associated with the profile.

Table 3 shows the types of policy rules, the types of policy rules, the place of each policy rule (eUICC exists in eUICC, and the external entity exists outside) .

In Table 3, Variables may have additional contents including implementation contents according to the contents of policy rules, and there may be Variables which are selectively used in this content.

In particular, a policy rule such as "profile management authority id" R3 is performed or authenticated from an authorized entity when a profile management command such as activation / deactivation / load / It is responsible for specifying whether or not it should be performed from an entity that has been created.

Next, the policy rules (euICC 100-related policy rules) for the eUICC 100 will be described with reference to Table 4.

Table 4 shows an example of the file structure of the policy rule associated with the eUICC (100).

Table 4 shows the types of policy rules, Variables are types of policy rules, Place is the location of each policy rule (eUICC exists in eUICC, External Entity exists outside) .

In Table 4, variables may have additional contents including the contents of the implementation according to the content of the policy rule, and there may be variables selectively used in the present invention.

FIG. 4 is a diagram illustrating a basic process for controlling and enforcing policy rules according to an embodiment of the present invention.

In Fig. 4, "targets executed based on policy rules" refer to profiles (applications, services) to be enforced or enforced by policy enforcement functions, And so on.

In Fig. 4, "targets executed based on policy rules" refer to profiles (profile 1, profile 2) to be enforced or enforced by the policy enforcement function, 2, profile 3), but in some cases it may be eUICC 100 or the like.

In Fig. 4, "External Entities" may be an entity such as MNO (Mobile Network Operator) or SM (Subscription Manager) or terminal.

Referring to FIG. 4, a method of controlling and enforcing a policy rule according to an embodiment of the present invention has the following basic procedure.

① An entity that has the authority to control the policy rule of the profile changes / deletes / adds the value of the policy rule through the policy control function. At this time, it is possible to secure and control security using the credentials shown in Tables 1 and 2.

② The values of the policy rules are set, controlled, updated, deleted, or added by the contents of Table 3 and Table 4 through the policy control function.

(3) The entity having the management or enforcement authority performs the policy enforcement function (functions in Table 1 and Table 2) for the policy rules set in (2) (Table 3 and Table 4).

④ The corresponding policy rules apply to the target (profile, eUICC (100), etc.).

5 and 6 are diagrams showing an application process (a process applying the basic process of FIG. 4) for controlling and implementing policy rules according to an embodiment of the present invention.

FIG. 5 illustrates an application process applied to a profile management method using a method (basic method) for policy rule management and execution on the eUICC 100 according to an embodiment of the present invention shown in FIG. 1 shows a procedure in which a policy rule is applied when a profile of the MNO is currently activated in the eUICC 100 and an attempt is made to change from the first MNO to the second MNO.

5, an application process applied to the profile management method includes a step S510 of confirming policy rules through a policy control function through an entity having a profile access right, a step S510, an eUICC 100 (eSIM) (S520) of setting the profile of the second MNO to the loadable profile ID through R8 in the policy rule for the eUICC 100, (S530) of confirming whether or not the profile of the second MNO can be installed (S530) by confirming the allowable profile number information, and determining whether the profile of the second MNO can be installed (S530) through the R12 and R14 of the policy rule for the eUICC (S540) of confirming the memory size information necessary for the profile to be activated, and a policy rule for the eUICC 100 to determine whether the profile management command is an Authorized dog (S550), and if the deletion of the profile of the first MNO is allowed through R5 in the policy rule for each profile, the eUICC (100) (S560) of deactivating or deleting the profile other than the profile of the second MNO through R10 in the policy rule (S560), and whether to notify the first MNO of the profile change via R11 in the policy rule for the eUICC (100) (S580) of setting a policy rule (R1-R6) for each profile; and a second MNO applying a policy rule set as a policy enforcement function through an object having a profile manager authority Step S590, and the like.

FIG. 6 is a diagram illustrating an application process applied to management of the eUICC 100 using a basic process for policy rule management and execution on the eUICC 100 according to an embodiment of the present invention in FIG.

Referring to FIG. 6, when a change from the first MNO to the second MNO is attempted in a situation where an eUICC lock is applied, the second MNO confirms policy rules with the policy control function through the entity having the profile access authority A step S620 of confirming whether the eUICC 100 is in the locked state through R15 of the policy rule for the eUICC 100 and a step S620 of checking whether the eUICC 100 is in the locked state via R16 in the policy rule for the eUICC 100. [ (S630) of confirming the valid period information and rejecting the change of the subscription to the second MNO (S640).

With the present invention, in an eUICC (100) environment in which a profile is loaded remotely and appropriate management of multiple profiles is required, the profile owner (e.g., MNO or service provider, etc.) It is possible to safely apply the service of subscription, modification or deletion according to the policy rule through the functions of activating, deactivating, deleting, loading, and the like.

Hereinafter, a method for managing and executing policy rules according to an embodiment of the present invention will be summarized.

FIG. 8 is a block diagram of an eUICC 100 for policy rule management and execution according to an embodiment of the present invention.

Referring to FIG. 8, the eUICC 100 for policy rule management and execution according to an embodiment of the present invention defines actions and conditions required to implement a policy, and generates policy rules for each profile and eUICC 100), a policy control function unit 820 for defining, updating, or deleting policy rules, a policy enforcement function unit 810 for executing policy rules, (830), and the like.

The policy control function unit 820 may be a module that performs a policy control function and the policy enforcement function unit 830 may be a module that performs a policy enforcement function.

The policy rule for each profile mentioned above may include a policy rule associated with the profile activated in the eUICC 100.

In addition, the policy rule for each profile may further include one or more policy rules associated with the profile deactivated in the eUICC 100.

Here, the policy rule associated with the activated profile is executable by the policy enforcement function 830. However, the policy rule associated with the deactivated profile may not be executable by policy enforcement function 830. [

The policy enforcement function 830 described above can evaluate the conditions of the policy rules and determine the execution of commands based on the evaluation.

The Credentials used in the security conditions for the policy enforcement function 830 and the policy control function 820 may include Profile Access Credentials, Profile Installer Credentials Installer Credentials, and Profile Management Credentials.

The policy rule for each profile and the policy rule for the eUICC 100 includes, for example, a type of a policy rule, a variable indicating a type of a policy rule, a place where a policy rule exists, Or more. (See Table 3 and Table 4)

For example, as shown in Table 3, the list of policy rules for each profile includes a policy rule R1 including a profile unique ID, a policy rule R2 having a profile owner ID as a variable, A policy rule (R3) having a management authority ID as a variable, a policy rule (R4) having a profile management type as a type and a provisioning profile use / nonuse information as a variable at a profile change, A policy rule R5, and a policy rule R6 having a type of a profile capability and a memory size information required for activating the profile, as variables.

Here, the policy rule R3 having the profile management authority ID as a variable is executed from an authorized entity when one of the profile management commands of activating, deactivating, loading, and deleting the profile is executed It may have a function to specify whether it should be executed from an authenticated entity.

In addition, the policy rule R3 having the profile management authority ID as a variable may be, for example, a policy rule that allows eUICC access only to at least one selected SM.

In addition, the policy rule associated with each profile may include, for example, a policy rule that defines allowed service names (Service Names) for owner authentication, which may include a profile owner ID Or a policy rule R2 as a variable.

For example, as shown in Table 4, the list of policy rules for the eUICC 100 includes a policy rule (R8) having a type of eUICC capability (Capabilities) and a list of profile IDs permitted to be downloaded and loaded as variables ), A policy rule (R10) having a variable number of active profile information as a variable, a policy rule (R10) having a profile ID list as a variable allowed to be activated, and a policy rule A policy rule R12 having the allowable memory size information as a variable on the eUICC 100 as a variable and the total allowable profile number information on the eUICC 100 as variables A policy rule R13, a policy rule R14 having a memory size information necessary for activating the profile as variables, an eUICC lock type, and an ICC lock Policy rule having a condition as a variable may include one or more policy rules, such as (R16) having the valid period information of the (R15) and, eUICC lock as a variable.

Among the above-mentioned policy rules, the policy rule R11 having the change notification information as a variable to the previous profile owner after changing the profile is a policy rule that determines that the eUICC 100 is allowed to inform the change of the profile status .

9 is a flowchart of a method for policy rule management and execution according to an embodiment of the present invention.

Referring to FIG. 9, a method for policy rule management and execution on an eUICC 100 according to an embodiment of the present invention includes a step of requesting an eUICC 100 to perform actions and conditions required to implement a policy, (S910) of storing policy rules including "policy rule for each profile" and "policy rule for eUICC (100) ", and the eUICC 100 defines a policy control function (S920), and the eUICC 100 executes the set policy rules through a policy enforcement function (S930), and the like.

10 is a flowchart of a method for policy rule management and execution according to an embodiment of the present invention.

Referring to FIG. 10, a method for managing and executing policy rules on the eUICC 100 according to an exemplary embodiment of the present invention includes a step S1010 of setting a policy rule through a policy control function of a first external entity A step S1020 of performing a policy enforcement function on the set policy rule so that the second external entity applies the policy rule set in the target profile or the eUICC 100 as a whole, (S1030) in which the policy rule set in the entirety of the policy rule is applied. Here, the first external entity and the second external entity may be the same or different entities (entities).

In the above-described step S1010, when the policy rule is set through the policy control function, security is secured based on a predefined credential (Credential) for the policy control function.

(Basic method) for policy rule management and execution on the eUICC 100 according to an embodiment of the present invention described above with reference to FIG. 10.

As an example of this case, when the profile of the first MNO is currently active in the eUICC 100 and attempts to change from the first MNO to the second MNO, the procedure in which the policy rule is applied is as shown in FIG. 5 Procedure.

Referring to FIG. 5, step S1020 of FIG. 10 includes a step S510 of checking the policy rules through the policy control function through the entity having the profile access authority, the step S510 of setting the policy rule for the eUICC 100 (Step S520) of setting the profile of the second MNO to the loadable profile ID (step S520), checking the number of active profile information and the total allowable profile number information through the policy rule for the eUICC 100, (S530) of confirming whether or not the profile of the profile can be installed (step S530), checking the memory size information necessary for the profiles and the memory size information necessary for activating the profile through the policy rules for the eUICC 100 S540) and a policy rule for the eUICC 100 to determine whether the profile management command is performed from an authorized entity or from an authenticated entity (Step S550), and if the deletion of the profile of the first MNO is allowed through the policy rule for each profile, the policy rule for the eUICC (100) A step S560 of inactivating or deleting the profile, a step S570 of confirming whether or not the first MNO is informed of the profile change through the policy rule for the eUICC 100 (S570), setting the policy rule for each profile Step S580, and the like.

If the step S1010 of FIG. 10 proceeds in detail, including the detailed steps of S510, S520, S530, S540, S550, S560, S570, and S580 of FIG. 5, the second MNO You can apply policy rules set by the policy enforcement feature through objects with profile administrator privileges.

Meanwhile, the present invention may be applied to the management of the eUICC 100 using a method (basic method) for policy rule management and execution on the eUICC 100 according to the embodiment of the present invention described above with reference to FIG.

As an example of this case, in a situation where the eNICC lock is applied, when changing from the first MNO to the second MNO, the step S1010 of FIG. 10 shows that the second MNO has the profile access right (S610) of confirming policy rules with the policy control function through an entity having the eUICC (100); checking (S620) whether the eUICC (100) is in a locked state through policy rules for the eUICC 100, the locking state of the eUICC 100 may include validation period information (S630), rejecting the subscription change to the second MNO (S640), and the like.

One embodiment of the present invention described above provides a function of controlling (defining, setting, updating, etc.) the policy rules according to the requirements of the service provider or the service provider of the profiles on the eUICC, , It is possible to provide functions of enforcement such as activation, deactivation, loading, or deletion of profiles.

With the present invention, in an eUICC (100) environment in which a profile is loaded remotely and appropriate management of multiple profiles is required, the profile owner (e.g., MNO or service provider, etc.) It is possible to safely apply the service of subscription, modification or deletion according to the policy rule through the functions of activating, deactivating, deleting, loading, and the like.

The foregoing description is merely illustrative of the technical idea of the present invention, and various changes and modifications may be made by those skilled in the art without departing from the essential characteristics of the present invention. Therefore, the embodiments disclosed in the present invention are intended to illustrate rather than limit the scope of the present invention, and the scope of the technical idea of the present invention is not limited by these embodiments. The scope of protection of the present invention should be construed according to the following claims, and all technical ideas within the scope of equivalents should be construed as falling within the scope of the present invention.

Claims (15)

Embedded Universal Integrated Circuit Card (eUICC) for policy rule management and execution,
A policy rule storage unit that defines actions and conditions required to implement the policy, and stores policy rules including policy rules for each profile and policy rules for the eUICC;
A policy control function for defining, updating or deleting the policy rules; And
And eUICC for policy rule management and execution comprising a policy enforcement function that executes the policy rules. The method according to claim 1,
The policy rule for each profile includes:
And a policy rule associated with the profile activated in the eUICC. 3. The method of claim 2,
The policy rule for each profile includes:
Further comprising one or more policy rules associated with the profile deactivated in the eUICC. ≪ RTI ID = 0.0 > 8. < / RTI > The method of claim 3,
Wherein the policy rule associated with the activated profile is executable by the policy enforcement function,
Wherein the policy rule associated with the deactivated profile is not executable by the policy enforcement function. The method according to claim 1,
The policy enforcement function,
Evaluating the conditions of the policy rules and determining the execution of the command based on the evaluation; and eUICC for policy rule management and execution. The method according to claim 1,
Wherein the policy enforcement function and the credentials used in the security condition for the policy control function include at least one of a profile access credential, a profile installer credential, and a profile management credential. EUICC for management and execution. The method according to claim 1,
Wherein the policy rule for each profile and the policy rule for the eUICC include:
Wherein the policy rule is a file structure having at least one of a type of a policy rule, a variable indicating a type of a policy rule, and a location where a policy rule exists. The method according to claim 1,
The list of policy rules for each profile includes:
A policy rule having a profile unique ID as a variable, a policy rule having a profile owner ID as a variable, a policy rule having a profile management authorization ID as a variable, and a policy rule having a profile management ID as a variable. A policy rule having a variable as a variable, a policy rule having a profile deletion permission / disapproval information as a variable, and a policy rule having a profile capacity as a type and memory size information required for activating the profile as variables, EUICC for policy rule management and implementation featuring. 9. The method of claim 8,
The policy rule, which has the profile management authority ID as a variable,
And a function for specifying whether the profile management command to be executed from an authorized entity or an authenticated entity is to be executed when one of the profile management commands for activating, deactivating, loading, and deleting the profile is executed. EUICC for policy rule management and enforcement. The method according to claim 1,
The list of policy rules for the eUICC includes:
a policy rule having a type of eUICC capability and having a list of profile IDs permitted to be downloaded and loaded as variables, a policy rule having a variable number of active profile information as a variable, and a list of profile IDs allowed to be activated as variables A policy rule having a policy rule, a policy rule having a change notify information as a variable to a previous profile owner after a profile change, a policy rule having a memory size information that is allowable for all profiles on the eUICC as a variable, A policy rule having variable number information as a variable, a policy rule having a memory size information required for activating a profile, a policy rule having a type of an eUICC lock and an ICC lock status as a variable, a validity period information of an eUICC lock As a variable. EUICC for policy rule management and enforcement. A method for policy rule management and execution on an embedded UICC (euICC: Embedded Universal Integrated Circuit Card)
Defining the actions and conditions required for the eUICC to implement the policy and storing the policy rules including the policy rules for each profile and the policy rules for the eUICC;
The eUICC setting the policy rules through a policy control function; And
And the eUICC executing the set policy rules via a policy enforcement function. A method for policy rule management and execution on an embedded UICC (euICC: Embedded Universal Integrated Circuit Card)
The first external entity establishing a policy rule through a policy control function; And
And performing a policy enforcement function on the set policy rule such that the second external entity applies the set policy rule to the target profile or the entire eUICC. 13. The method of claim 12,
Wherein, when the policy rule is set through the policy control function, security is secured based on a predefined credential (Credential) for the policy control function in the setting step. Way. 13. The method of claim 12,
When a change from the first MNO (Mobile Network Operator) to the second MNO is attempted,
Wherein the setting step comprises:
The second MNO verifying the policy rules via the policy control function through the entity having the profile access authority;
Setting a profile of the second MNO to a loadable profile ID through a policy rule for the eUICC;
Confirming whether the profile of the second MNO can be installed by checking the number of active profiles and the total number of allowable profiles through the policy rule for the eUICC;
Confirming with the policy rule for the eUICC the allowable memory size information for the entire profiles and the memory size information necessary for the profile to be activated;
Confirming through the policy rule for the eUICC whether the profile management command is performed from an authorized entity or an authenticated entity;
If the deletion of the profile of the first MNO is allowed through the policy rule for each profile, deactivating or deleting the remaining profiles except for the profile of the second MNO through the policy rule for the eUICC;
Confirming whether or not the first MNO is informed of a profile change through a policy rule for the eUICC; And
Setting policy rules for each of the profiles,
Wherein the step of performing comprises applying the set policy rule to the policy enforcement function through an entity having a profile manager authority to the second MNO. 13. The method of claim 12,
When a change from the first MNO (Mobile Network Operator) to the second MNO is attempted in the state where the eUICC lock is established,
Wherein the setting step comprises:
The second MNO verifying policy rules with the policy control function via an entity having profile access authority;
Confirming whether the eUICC is in a locked state through a policy rule for the eUICC;
Confirming the validity period information of the lock status of the eUICC through the policy rule for the eUICC; And
Rejecting the subscription change to the second MNO. ≪ RTI ID = 0.0 > 11. < / RTI >

Images