KR20140056041A - Method of changing entity for managing subscriber certification module and apparatus using the same - Google Patents

Abstract

A method and an apparatus for changing an entity managing a subscriber identification module are disclosed. A method for changing a subscriber management entity comprises the steps of: receiving, by a subscriber identification module, a credential temporal change request message including a temporal credential from a first subscriber management entity to temporarily change the credential; delivering, by the first subscriber management entity, a delegation request message to a second subscriber management entity to delegate management of the subscriber identification module to the second subscriber management entity; and receiving, by the subscriber identification module, a credential confirmation request message based on the temporal credential from the second subscriber management entity to confirm a credential. Therefore, by changing a credential in eUICC, it is possible to securely change a subscriber management entity managing the eUICC and, consequently, to manage the eUICC built in a device effectively.

Description

BACKGROUND OF THE INVENTION 1. Field of the Invention [0001] The present invention relates to a method for changing an entity managing a subscriber identity module,

The present invention relates to management of a subscriber identity module, and more particularly, to a method and apparatus for changing an entity that manages a subscriber identity module.

In general, a UICC (Universal Integrated Circuit Card) is customized by a MNO (Mobile Network Operator), and performs network authentication using a unique identifier given by the MNO or a unique value generated randomly. In other words, by giving a key to access the UICC at the manufacturing stage of the UICC, the values in the UICC can be changed, added or deleted, and the application of the UICC can be added or deleted.

However, Embedded SIM (eSIM or eUICC) is produced by the eUICC manufacturer and delivered to the terminal maker using the eUICC, not by the order of the MNO.

Accordingly, the MNO acquiring the authority through the subscriber management entity (for example, Subscription Manger: SM) provided by the eUICC manufacturer can set or store the values required for the network connection in the eUICC, You can add or delete applications in the eUICC through the third-party SM.

However, using the SM provided by the eUICC manufacturer at the beginning, the MNO can set or store the values necessary for performing the network authentication in the eUICC, but it is necessary to change the SM in preparation for the bankruptcy of the eUICC maker.

On the other hand, if information about the MNO is set in the eUICC, it is necessary to change the SM managing the eUICC to the SM operated by the MNO. Furthermore, when a change of the MNO occurs, a change to the SM operated by the MNO is required.

In addition, changes to the SM may be required to accommodate different business models through the installation of applications within the eUICC.

Therefore, a technology capable of safely changing an SM having a special authority to change the value in the eUICC is required.

SUMMARY OF THE INVENTION It is an object of the present invention to provide a method for securely changing a subscriber management entity managing an eUICC.

It is another object of the present invention to provide an eUICC capable of securely changing a subscriber management entity.

According to an aspect of the present invention, there is provided a method of changing a subscriber management entity, the subscriber authentication module receiving a credential change request message including a temporary credential from a first subscriber management entity, A step in which the first subscriber management entity transmits a delegation request message for delegating the management of the subscriber identity module to the second subscriber management entity to the second subscriber management entity to request delegation; And receiving a credential confirmation request message based on the temporary credential from the second subscriber management entity to confirm the credentials.

Here, the provisional credential may be a credential of the second subscriber management entity.

Here, the temporary credential may be in the form of a certificate, a key, a cookie, and a token.

Here, the credential change request message may include credential type information and a credential value.

Here, the step of changing the credential may allow the subscriber identity module to authenticate the first subscriber management entity using a master credential for the first subscriber management entity.

Here, in the step of changing the credential, the temporary credential may be set as a secondary credential.

Herein, after performing the step of changing the credentials, the subscriber authentication module transmits a variable light response message including result information on the variable light to the first subscriber management entity and responds to the variable light path .

Here, the step of establishing the credentials may allow the subscriber identity module to authenticate the second subscriber management entity using the temporary credential.

Wherein the step of establishing the credentials may replace the master credential with a secondary credential.

Here, after performing the step of confirming the credential, the subscriber authentication module may further include transmitting a credential determination response message including result information on the confirmation to the second subscriber management entity.

According to another aspect of the present invention, there is provided a method for changing a subscriber management entity in a subscriber management entity, comprising the steps of: Receiving a variable change request message and changing a credential; transmitting a variable response message including result information on a variable path to a first subscriber management entity and responding to the variable path; And establishing a credential by receiving a credential confirmation request message based on a temporary credential from a second subscriber management entity delegated management by the subscriber management entity to the subscriber authentication module.

According to another aspect of the present invention, there is provided a subscriber authenticating apparatus for receiving a credential change request message including a temporary credential from a first subscriber management entity to change a credential A response module for transmitting a variable light response message including result information on variable light to a first subscriber management entity and responding to the variable light path by a first subscriber management entity; And a credential confirmation module for receiving the credential confirmation request message based on the temporary credentials from the second subscriber management entity delegated to the management of the second management entity to confirm the credentials.

The method for changing a subscriber management entity according to an embodiment of the present invention as described above can safely change a subscriber management entity that manages an eUICC by changing a credential in the eUICC and can effectively manage the eUICC built in the device do.

In addition, the SM can be effectively changed using the security mechanisms (certificates, keys, cookies, tokens, etc.) applied between the eUICC and the SM.

Also, there is an advantage that it is possible to restore the existing state even if an error occurs in the process of changing the SM.

1 is a basic flowchart for explaining a method for changing a subscriber management entity according to an embodiment of the present invention.
2 is a conceptual diagram illustrating a method for changing a subscriber management entity performed by each subject according to an embodiment of the present invention.
3 is a diagram for explaining a message used for changing a subscriber management entity according to an embodiment of the present invention.
4 is a flowchart illustrating a method for changing a subscriber management entity according to an embodiment of the present invention.
5 is a flowchart illustrating a method for changing a subscriber management entity using a certificate according to an embodiment of the present invention.
6 is a flowchart illustrating a method for changing a subscriber management entity using a certificate according to an exemplary embodiment of the present invention.
7 is a flowchart illustrating a method for changing a subscriber management entity according to another embodiment of the present invention.
8 is a flowchart illustrating a method for changing a subscriber management entity using a key according to another embodiment of the present invention.
9 is a flowchart illustrating a method for changing a subscriber management entity using a key according to another embodiment of the present invention in more detail.
10 is a block diagram illustrating a configuration of a subscriber identity module according to an embodiment of the present invention.
11 is a conceptual diagram for explaining a restoration method when an error occurs in a subscriber management entity change according to an embodiment of the present invention.

While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and will herein be described in detail.

It should be understood, however, that the invention is not intended to be limited to the particular embodiments, but includes all modifications, equivalents, and alternatives falling within the spirit and scope of the invention.

The terms first, second, etc. may be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, the first component may be referred to as a second component, and similarly, the second component may also be referred to as a first component. And / or < / RTI > includes any combination of a plurality of related listed items or any of a plurality of related listed items.

It is to be understood that when an element is referred to as being "connected" or "connected" to another element, it may be directly connected or connected to the other element, . On the other hand, when an element is referred to as being "directly connected" or "directly connected" to another element, it should be understood that there are no other elements in between.

The terminology used in this application is used only to describe a specific embodiment and is not intended to limit the invention. The singular expressions include plural expressions unless the context clearly dictates otherwise. In the present application, the terms "comprises" or "having" and the like are used to specify that there is a feature, a number, a step, an operation, an element, a component or a combination thereof described in the specification, But do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or combinations thereof.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with the meaning in the context of the relevant art and are to be interpreted in an ideal or overly formal sense unless explicitly defined in the present application Do not.

The term "subscriber identity module" used in the present application means an embedded SIM (Subscriber Identity Module) embedded in an eUICC (embedded UICC) or an eSIM (embedded SIM) Is used.

The term "terminal" used in the present application includes a mobile station (MS), a user equipment (UE), a user terminal (UT), a wireless terminal, an access terminal (AT), a terminal, a subscriber unit , A subscriber station (SS), a wireless device, a wireless communication device, a wireless transmit / receive unit (WTRU), a mobile node, a mobile, or other terminology. Various embodiments of the terminal may be used in various applications such as cellular telephones, smart phones with wireless communication capabilities, personal digital assistants (PDAs) with wireless communication capabilities, wireless modems, portable computers with wireless communication capabilities, Devices, gaming devices with wireless communication capabilities, music storage and playback appliances with wireless communication capabilities, Internet appliances capable of wireless Internet access and browsing, as well as portable units or terminals incorporating combinations of such functions have.

The terminal may include an M2M (Machine to Machine) terminal, an MTC (Machine Type Communication) terminal / device, but is not limited thereto.

The profile on the eUICC includes the network provider's unique data, key information, etc., and the network operator or third party entrusted by the network operator can create and manage the profile.

The term "subscriber management entity" as used in the present application may mean an external interworking device (e.g., Subscription Manager (SM), etc.) capable of creating and managing profiles on the eUICC.

In other words, the subscriber management entity (SM) is provided with Subscription Manager-Secure Routing (SM-SR) for securely managing the provider profile and configuration profiles directly on the eUICC and for preparing the provider profiles and configuration profiles to be securely provisioned on the eUICC (Subscription Manager-Data Preparation).

Also, in the present invention, the first subscriber management entity that manages the current eUICC may be referred to as SM-A, and a new second subscriber management entity that manages the eUICC through the change may be referred to as SM-B.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. In order to facilitate the understanding of the present invention, the same reference numerals are used for the same constituent elements in the drawings and redundant explanations for the same constituent elements are omitted.

FIG. 1 is a basic flowchart illustrating a method for changing a subscriber management entity according to an embodiment of the present invention. FIG. 2 is a conceptual diagram illustrating a method for changing a subscriber management entity performed by each subject according to an embodiment of the present invention .

Referring to FIG. 1 and FIG. 2, a method for changing a subscriber management entity according to an embodiment of the present invention may be performed by changing a credential.

The method for changing a subscriber management entity according to an embodiment of the present invention includes a step S10 for changing a credential, a step S20 for requesting a delegation, and a step S30 for establishing a credential.

Stage 1

The subscriber identity module may receive a credential change request message including a temporary credential from the first subscriber management entity to change the credential (S10). Here, the first subscriber management entity may refer to the SM-A 210 currently managing the eUICC 100. Here, the temporary credential may be a credential of the second subscriber management entity and may be in the form of a certificate, a key, a cookie, and a token. In addition, the credential change request message may include credential type information and a credential value.

the SM-A 210 managing the corresponding eUICC 100 can change the credentials in the eUICC 100, and the credential can be changed in step 2, which will be described later, as a step of temporarily changing the credentials in the eUICC 100. [ A temporary credential change can be made because it can be a security risk if an existing credential is exposed to another before sending it.

In addition, the subscriber identity module may authenticate the first subscriber management entity using a master credential for the first subscriber management entity.

Thus, in the step of changing the credential, the temporary credential can be set as the secondary credential.

Also, after performing the step of changing the credential, the subscriber identity module may transmit a variable response message including the result information on the variable size to the first subscriber management entity to respond to the variable size.

Step 2

The first subscriber management entity transmits a delegation request message for delegating the management of the subscriber identity module to the second subscriber management entity to the second subscriber management entity and requests delegation (S20). Here, the second subscriber management entity may mean the SM-B 220 that will manage the eUICC 100 through modification.

Step 3

The subscriber identity module can confirm the credential by receiving the credential confirmation request message based on the temporary credential from the second subscriber management entity (S30). That is, the master credential can be replaced with the secondary credential. For example, the SM-B 220, which will manage the eUICC 100 in the future, can confirm the temporary changed credentials or confirm the changed credentials after confirming the temporarily changed credentials.

In addition, the subscriber identity module may authenticate the second subscriber management entity using the temporary credential.

Further, after performing the step of establishing the credentials, the subscriber authentication module may forward a credential confirm response message containing the result information for the confirmation to the second subscriber management entity.

3 is a diagram for explaining a message used for changing a subscriber management entity according to an embodiment of the present invention.

Referring to FIG. 3, the messages used in the respective steps (steps 1, 2 and 3) will be described.

Credential_Change_Request () is a message sent from the SM-A 210 managing the eUICC 100 to the eUICC 100 to request a change of the credential.

Credential_Change_Request () may include information on Credential-Type and Credential values. Here, Credential-Type indicates the type of credentials such as Key, Certification, Cookie, Token, and so on. The Credential value represents the actual value of the credential and consists of the value of the type required by the type specified in Credential-Type.

Credential_Change_Response () is a response message to Credential_Change_Request () as a message sent from the eUICC 100 to the SM-A 210 managing itself.

Credential_Change_Request () may include information on Credential-Type and Credential values. Here, Credential-Type indicates the type of credentials such as Key, Certification, Cookie, Token, and so on. The Credential value represents the actual value of the credential and consists of the value of the type required by the type specified in Credential-Type.

Credential_Change_Request () may additionally include a Result, which may include information on the success or failure of the result of performing Credential_Change_Request ().

Credential_Delegate_Request () delivers the credentials set in the eUICC 100 to the SM-B 220 that the SM-A 210 managing the eUICC 100 will manage the eUICC 100 in the future, It is a request message.

Credential_Delegate_Request () may include information on Credential-Type and Credential values. Here, Credential-Type indicates the type of credentials such as Key, Certification, Cookie, Token, and so on. The Credential value represents the actual value of the credential and consists of the value of the type required by the type specified in Credential-Type.

The Credential_Delegate_Request () may additionally include an eUICCInfo, and the eUICCInfo is composed of information (for example, support function, memory, etc.) about the eUICC 100. [

Credential_Delegate_Response () is a response message to the Credential_Delegate_Request () message sent from the SM-B 220 that manages the eUICC 100 to the SM-A 210 managing the eUICC 100 in the future.

Credential_Delegate_Response () may include information on Credential-Type and Credential values. Here, Credential-Type indicates the type of credentials such as Key, Certification, Cookie, Token, and so on. The Credential value represents the actual value of the credential and consists of the value of the type required by the type specified in Credential-Type.

Credential_Delegate_Response () may additionally include a Result, which may include information on the success or failure of the result of performing Credential_Change_Request ().

For example, the SM-A 210 that manages the current eUICC 100 receives information on the received Credential-Type and Credential values from the Credential-Type and Credential values previously included in the Credential_Delegate_Request () If it is the same, it can be judged that the SM-B 220 that will manage the eUICC 100 in the future has accepted the delegation.

Credential_Change_Confirm () is a message exchanged between the eNICC 100 and the SM-B 220 to manage the eUICC 100 in the future. That is, it is a message for confirming the changed credentials in the eUICC 100. Here, Credential-Type indicates the type of credentials such as Key, Certification, Cookie, Token, and so on. The Credential value represents the actual value of the credential and consists of the value of the type required by the type specified in Credential-Type.

Credential_Change_Confirm () may additionally include a Result, which may include information on the success or failure of the result of performing Credential_Change_Confirm ().

4 is a flowchart illustrating a method for changing a subscriber management entity according to an embodiment of the present invention.

The eUICC 100 stores information on a credential for accessing the eUICC 100. In addition, the SM-A 210 managing the eUICC 100 has a credential stored in the eUICC 100. Here, the credential can be implemented by a method such as a key, a cookie, a token, and a certificate.

Also, the credential can be expressed and implemented according to the profile management credential and the profile installer credential according to the environment constituting the eUICC 100.

The method of changing the subscriber management entity through the change of the credential is largely carried out through the following process.

First, a secondary credential for future use as a master credential is registered. Here, the master credential is a credential stored in the eUICC 100, which may be a credential held by the SM-A 210. [ In addition, if security is required to perform this step, the SM-A 210 can be authenticated using the master credential.

Subsequently, a process of replacing the secondary credential with the master credential can be performed. That is, the secondary credential can be registered with the master credential. If security is required to perform these steps, authentication using a secondary credential can be performed to verify the secondary credential. If you do not need verification of the secondary credential, you can also use the master credential to perform authentication.

In addition, the existing master credential can be stored as a secondary credential in case recovery is required. That is, if an error situation or cancellation occurs before the secondary credential is registered as the master credential, it is possible to restore the previous state by maintaining the existing master credential and deleting the secondary credential.

Further, if restoration is required after the secondary credential is registered as the master credential, the existing master credential stored in the secondary credential for restoration can be set back to the current master credential. When security is required to perform this step, authentication can be performed using the current master credential.

The procedure for changing the credential according to the embodiment of the present invention is not limited to the case of changing the subscriber management entity. In other words, it can be used in any process to change the credentials associated with an external entity.

The eUICC 100 performs the following operation in response to a request from the SM-A 210. [

First, before performing a request according to Credential_Change_Request (), the authority for the request can be verified using the master credential.

The eUICC 100 may receive the Credential_Change_Request () and set the credential (CREDENTIAL_B) enclosed with the Credential_Change_Request () to the secondary credential (S410). In addition, the eUICC 100 may transmit a variable response message (Credential_Change_Request ()) including the result information on the variable size to the SM-A 210 to respond to the variable size (S420).

the eUICC 100 can confirm the authority for the request using the secondary credential before performing the Credential_Change_Confirm () request.

When the eUICC 100 receives the Credential_Change_Confirm (), the eUICC 100 may set the credential set as the secondary credential to the master credential (S450). If the credential is enclosed in Credential_Change_Confirm (), the enclosed credential can be set to the secondary credential and the secondary credential can be set to the master credential.

More specifically, since the eUICC 100 is initially managed by the SM-A 210, the CREDENTIAL_A, which is the credential of the SM-A 210, is set as the master credential. That is, the secondary credential is not set in the eUICC 100.

The SM-A 210 may transmit a secondary credential (CREDENTIAL_B) for use as a master credential to the eUICC 100 in operation S410. If security is required at this time, authentication can be performed in advance with the current master credential (CREDENTIAL_A).

the eUICC 100 can safely store (change the secondary secondary) CREDEN_B received from the SM-A 210. If security is requested at this time, the eUICC 100 pre-authenticates the current master credential (CREDENTIAL_A) It can be done as an enemy.

In addition, the eUICC 100 may transmit a Credential_Change_Request () containing result information on the variable size to the SM-A 210 and may respond to the variable size (S420).

The SM-A 210 can delegate a credential to the SM-B 220. [ That is, the SM-A 210 can transmit the secondary credential (CREDENTIAL_B) to the SM-B 220 through the Credential_Delegate_Request () (S430). Here, the authentication between the SM-A 210 and the SM-B 220 may use a separate authentication scheme.

In addition, the SM-B 220 may forward the Credential_Delegate_Response () to the SM-A 210 in response to the Credential_Delegate_Request (S440).

The SM-B 220 may request the eUICC 100 to register and register the secondary credential (CREDENTIAL_B) as the master credential through Credential_Change_Confirm () (S450).

In addition, after the eUICC 100 has registered the secondary credential (CREDENTIAL_B) as the master credential, the eUICC 100 may notify the result to the SM-B 220 using Credential_Change_Confirm () (S460).

A method for changing a subscriber management entity according to an embodiment of the present invention will now be described with reference to each subject.

First, a description will be made with reference to the eUICC 100 as follows.

Since the eUICC 100 is initially managed by the SM-A 210, the CREDENTIAL_A, which is the credential of the SM-A 210, is set as the master credential. That is, initially, the eUICC 100 does not set the secondary credential.

When the eUICC 100 receives the Credential_Change_Request () message from the SM-A 210 to perform the first step, the eUICC 100 may set the received Credentials to the secondary credential.

On the other hand, the result of the setting for the secondary credential can be transmitted to the SM-A 210 in the Credential_Change_Response () message.

The eUICC 100 is not involved in the second stage described above.

The eUICC 100 can set a master credential upon receiving a Credential_Change_Confirm () message for performing the above-described three steps from the SM-B 220. At this time, if Credential_Type and Credential are set, the received Credential can be set as the master credential. In other words, the secondary credential can be set to the master credential.

EUICC 100 may also send a Credential_Change_Confirm () message to SM-B 220 as a result of the credential establishment. Credential_Change_Confirm () may contain information on success or failure to establish a credential and an error.

Next, a description will be made with reference to the SM-A 210 as follows.

The SM-A 210 has a credential (CREDENTIAL_A) for managing the eUICC 100.

The SM-A 210 transmits a Credential_Change_Request () message to the eUICC 100 for performing the above-described step 1. At this time, the credentials to be changed can be added and transmitted.

The SM-A 210 may receive a Credential_Change_Reponse () message from the eUICC 100.

The SM-A 210 delivers a Credential_Delegate_Request () message to the SM-B 220 for performing the above two steps. At this time, the credentials included in Credential_Change_Request () can be transmitted together.

Finally, SM-B 220 will be described below.

The SM-B 220 does not have a credential for managing the eUICC 100. Therefore, the SM-B 220 is not involved in the above-described first step.

The SM-B 220 receives the Credential_Delegate_Request () message from the SM-A 210 to perform the above-described two steps. Here, the Credential included in the enclosed Credential_Delegate_Request () is a credential for managing the eUICC 100.

The SM-B 220 transmits a Credential_Delegate_Response () message to the SM-A 210. And transmits the management acceptance of the eUICC (100) to the SM-A (210).

In order to perform the above-described three steps, the SM-B 220 may transmit a Credential_Change_Confirm () message to the eUICC 100 and thereby determine the master credential of the eUICC 100. If there is a Credential in the Credential_Change_Confirm (), the master credential of the eUICC 100 can be set as a corresponding Credential. If the Credential does not exist in the Credential_Change_Confirm (), the secondary credential of the eUICC 100 can be set as the master credential. have.

5 is a flowchart illustrating a method for changing a subscriber management entity using a certificate according to an embodiment of the present invention.

A method for changing a subscriber management entity using a certificate will be described with reference to FIG.

Since the eUICC 100 is managed by the SM-A 210, it sets the certificate of the SM-A 210 as the master credential.

The eUICC 100 may receive a Credential_Change_Request () message from the SM-A 210 (S510). Here, the Credential_Change_Request () may include a certificate (CERTIFICATE_B) of the SM-B 220. Therefore, the eUICC 100 can set the CERTIFICATE_B to the secondary credential.

The eUICC 100 may transmit the result of the Credential_Change_Request () message to the SM-A 210 in the Credential_Change_Response () message (S520).

The SM-A 210 can delegate a credential to the SM-B 220. [ That is, the SM-A 210 may forward the CERTIFICATE_B to the SM-B 220 through the Credential_Delegate_Request () (S530). Here, the authentication between the SM-A 210 and the SM-B 220 may use a separate authentication scheme.

In addition, the SM-B 220 may forward the Credential_Delegate_Response () to the SM-A 210 in response to the Credential_Delegate_Request (S540).

The SM-B 220 may request the eUICC 100 to register the secondary credential (CERTIFICATE_B) as the master credential through Credential_Change_Confirm () (S550).

In addition, after the eUICC 100 has registered the secondary credential (CERTIFICATE_B) as the master credential, the eUICC 100 may notify the result to the SM-B 220 using Credential_Change_Confirm () (S560).

6 is a flowchart illustrating a method for changing a subscriber management entity using a certificate according to an exemplary embodiment of the present invention.

A method for changing a subscriber management entity using a certificate according to an embodiment of the present invention will be described in detail with reference to FIG.

First, the SM-A 210 can verify the eUICC ID (S610).

In detail, the SM-A 210 can read an identifier (e.g., eUICC ID) of the eUICC 100 (S611). That is, the SM-A 210 may obtain the eUICC ID from the eUICC 100 (S612). The eUICC ID may be an embedded Integrated Chip Card Identification (eICCID), an International Mobile Subscriber Identity (IMSI), a Chip Image Number (CIN) to be. Also, the eUICC ID may be a value used as the owner identifier of the eUICC certificate.

The SM-A 210 performs verification of the eUICC ID and the certificate information mapped to the eUICC ID value can be searched and verified by the SM-A 210 in the management database (S613).

For example, the SM-A 210 may obtain the certificate of the corresponding eUICC 100 from the database using the eUICC ID value or may generate data necessary for authentication using the certificate.

Second, the SM-A 210 may input the ID of the CERTIFICATE_B or the SM-B 220 to the eUICC 100 (S620).

In detail, the SM-A 210 selects a certificate management module (e.g., a Profile Manager) of the eUICC 100 (S621) and performs mutual authentication between the SM-A 210 and the eUICC 100 (S622).

For example, the SM-A 210 and the eUICC 100 perform mutual authentication through a procedure of signing an arbitrary value through a shared CERTIFICATE_A and a CERTIFICATE_eUICC with a certificate key and verifying the received value using their respective private keys .

After performing the mutual authentication, the SM-A 210 may perform a procedure of inputting the identifier of the SM-B 220 or the certificate chain of the SM-B 220 to the eUICC 100 through the shared session key S623).

As an embodiment of the command interface for inputting the certificate chain of the SM-B 220 or the identifier of the SM-B 220 to the eUICC 100, a STORE DATA command defined in the Global Platform may be used.

For example, as a data parameter of the STORE DATA command, a data object including the certificate chain of CERTIFICATE_B or the owner ID value of CERTIFICATE_B can be set. In addition, the eUICC 100 may store the owner ID value of CERTIFICATE_B or CERTIFICATE_B (S624).

Third, the SM-A 210 may delegate management of the eUICC 100 to the SM-B 220 (S630). That is, the procedure can be performed by exchanging Credential_Delegate_Request () and Credential_Delegate_Response () between the SM-A 210 and the SM-B 220. However, since this procedure does not have a direct interface with the eUICC 100, a detailed description thereof will be omitted.

Fourth, the certificate can be verified between the SM-B 220 and the eUICC 100 (S640).

In detail, the SM-B 220 selects a certificate management module (for example, Profile Manager) of the eUICC 100 (S641).

The SM-B 220 and the eUICC 100 may use a secure channel protocol (Secure Channel Protocol '10') using a Global Platform certificate as an embodiment of a command interface for verifying certificates of each other.

In the case of conforming to the Global Platform's certificate secure channel protocol procedure, the certificate validation step between the SM-B 220 and the eUICC 100 can be performed before the mutual authentication.

The command procedure for the certificate verification step may transmit the secure channel protocol parameter setting value to the eUICC 100 using the MANAGE SECURITY ENVIRONMENT command in the SM-B 220 (S642).

The SM-B 220 may forward the certificate chain of the user to the eUICC 100 through the PERFORM SECURITY OPERATION [verify certificate] command (S643).

After the eUICC 100 authenticates that the certificate or the certificate owner ID value stored in the second step S620 is the same as the owner ID value of the CERTIFICATE_B or CERTIFICATE_B received from the SM-B 220, the eUICC 100 The certificate chain of the CERTIFICATE_B can be verified by using the public key of the trust institution (for example, the public key of the top-level CA) possessed by the certificate authority (for example, S644 ).

In addition, the SM-B 220 may use the GET DATA [certificate] command to read the certificate of the eUICC 100 if necessary (S645, S646).

Fifth, the mutual authentication using the CERTIFICATE_B can be performed between the eUICC 100 and the SM-B 220 (S650).

The SM-B 220 may use the PERFORM SECURITY OPERATION [decipher] command to share the session key with the eUICC 100 (S651).

Then, the eUICC 100 can decrypt the session key and store it (S652).

In order to perform mutual authentication between the SM-B 220 and the eUICC 100, the SM-B 220 may acquire the random value of the card using the GET CHALLENGE command (S653) (S654). In addition, the SM-B 220 can generate a random value using the SM-B (220) secret key (S655).

Meanwhile, the signature data (value) of the SM-B 220 can be transferred to the eUICC 100 using the EXTERNAL AUTHENTICATE command defined in the Global Platform (S656). The eUICC 100 can verify the signature value using the CERTIFICATE_B (S657).

When necessary for mutual authentication, the SM-B 220 generates a random value and transmits it to the eUICC 100 (using the INTERNAL AUTHENTICATE command) (S658), and the eUICC 100 uses the secret key of the SM- B 220 and transmits the signature to the SM-B 220 as a response value (S659, S659-1).

The SM-B 220 can verify the signature value using the CERTIFICATE_eUICC 100 (S660). In addition, when mutual authentication is completed, the eUICC 100 can confirm and manage the final value after completing the verification of the CERTIFICATE_B.

1 and FIG. 2, the third embodies the second step (S20) of FIG. 1 and FIG. 2, the fourth and fifth embodied in FIG. 1 and FIG. The third step (S30) of FIG. 2 can be specified.

7 is a flowchart illustrating a method for changing a subscriber management entity according to another embodiment of the present invention.

7, the secondary credential of the eUICC 100 may be set to a temporary credential, CREDENTIAL_TEMP, and the value of the secondary credential may be transmitted to the SM-B 220 by the SM-A 210.

In addition, the SM-B (220) receiving the CREDENTIAL_TEMP describes the process of setting the CREDENTIAL_B using the corresponding credential.

First, before performing a request according to Credential_Change_Request (), the authority for the request can be verified using the master credential.

The eUICC 100 may receive the Credential_Change_Request () and set the credential (CREDENTIAL_TEMP) enclosed with the Credential_Change_Request () to the secondary credential (S710). In addition, the eUICC 100 may transmit a variable response message (Credential_Change_Request ()) including result information on the variable size to the SM-A 210 to respond to the variable size (S720).

the eUICC 100 can confirm the authority for the request using the secondary credential before performing the Credential_Change_Confirm () request.

Upon receiving the Credential_Change_confirm (), the eUICC 100 may set the credential set as the secondary credential to the master credential (S750). If the credential is enclosed in Credential_Change_Confirm (), the enclosed credential can be set to the secondary credential and the secondary credential can be set to the master credential.

More specifically, since the eUICC 100 is initially managed by the SM-A 210, the CREDENTIAL_A, which is the credential of the SM-A 210, is set as the master credential. That is, the secondary credential is not set in the eUICC 100.

The SM-A 210 may transmit the temporary credential CREDENTIAL_TEMP to the eUICC 100 (S710). If security is required at this time, authentication can be performed in advance with the current master credential (CREDENTIAL_A).

The eUICC 100 may store the CREDENTIAL_TEMP received from the SM-A 210 as a secondary credential (variable view). If security is required at this time, the eUICC 100 may perform authentication with the current master credential (CREDENTIAL_A) Can be performed.

In addition, the eUICC 100 may transmit the Credential_Change_Request () including the result information on the variable size to the SM-A 210 to respond to the variable size (S720).

The SM-A 210 can delegate a credential to the SM-B 220. [ That is, the SM-A 210 may transmit the CREDENTIAL_TEMP to the SM-B 220 through the Credential_Delegate_Request () (S730). Here, the authentication between the SM-A 210 and the SM-B 220 may use a separate authentication scheme.

In addition, the SM-B 220 may forward the Credential_Delegate_Response () to the SM-A 210 in response to the Credential_Delegate_Request (S740).

The SM-B 220 may transmit the CREDENTIAL_B to the SM-A 210 via the Credential_Change_Confirm () and request the eUICC 100 to determine the CREDENTIAL_B as the master credential (S750).

In addition, the eUICC 100 may notify the SM-B 220 of the result of the registration using the Credential_Change_Confirm () after registering the CREDENTIAL_B which is the credential of the SM-B 220 as the master credential (S760) .

8 is a flowchart illustrating a method for changing a subscriber management entity using a key according to another embodiment of the present invention.

A method for changing a subscriber management entity using a key will be described with reference to FIG.

Since the eUICC 100 is managed by the SM-A 210, the key (KEY_A) of the SM-A 210 is set as the master credential.

The eUICC 100 may receive a Credential_Change_Request () message from the SM-A 210 (S810). Here, Credential_Change_Request () may include a temporary key (KEY_TEMP).

Therefore, the eUICC 100 can set the KEY_TEMP to the secondary credential.

The eUICC 100 may transmit the result of the execution of the Credential_Change_Request () message to the SM-A 210 in the Credential_Change_Response () message (S820).

The SM-A 210 can delegate a credential to the SM-B 220. [ That is, the SM-A 210 can forward the KEY_TEMP to the SM-B 220 through the Credential_Delegate_Request () (S830). Here, the authentication between the SM-A 210 and the SM-B 220 may use a separate authentication scheme.

In addition, the SM-B 220 may forward the Credential_Delegate_Response () to the SM-A 210 in response to the Credential_Delegate_Request (S840).

The SM-B 220 may transmit the KEY_B to the SM-A 210 via the Credential_Change_Confirm () and request the eUICC 100 to determine that the KEY_B is the master credential (S850).

In addition, after the eUICC 100 has registered KEY_B as a master credential, the eUICC 100 can notify the result to the SM-B 220 using Credential_Change_Confirm () (S860).

9 is a flowchart illustrating a method for changing a subscriber management entity using a key according to another embodiment of the present invention in more detail.

First, the SM-A 210 can verify the eUICC ID (S910).

In detail, the SM-A 210 can read an identifier (e.g., eUICC ID) of the eUICC 100 (S911). That is, the SM-A 210 may obtain the eUICC ID from the eUICC 100 (S912). The eUICC ID may be an embedded Integrated Chip Card Identification (eICCID), an International Mobile Subscriber Identity (IMSI), a Chip Image Number (CIN) to be. Also, the eUICC ID may be a value used as the owner identifier of the eUICC key.

The SM-A 210 performs verification of the eUICC ID, and the SM-A 210 searches the management database for the key information mapped to the eUICC ID value (S913).

For example, in the SM-A 210, the key of the eUICC 100 may be fetched from the database using the eUICC ID value, or data necessary for authentication may be generated using the key.

Second, the SM-A 210 may input KEY_TEMP to the eUICC 100 (S920).

In detail, the SM-A 210 selects a certificate management module (e.g., Profile Manager) of the eUICC 100 (S921) and performs mutual authentication between the SM-A 210 and the eUICC 100 (S922).

Here, the SM-A 210 can perform mutual authentication through the KEY_A that is previously shared with the eUICC 100. [ The mutual authentication procedure may follow various schemes for authenticating the shared key, and the preferred embodiment may follow the authentication procedure defined by the Global Platform.

For example, the authentication procedure defined by the Global Platform is as follows. The SM-A 210 encrypts and decrypts the random value through the KEY_A through the INIT UPDATE and EXTERNAL AUTHENTICATE commands to perform key verification and mutual authentication.

When mutual authentication is successfully completed between the SM-A 210 and the eUICC 100, a KEY_TEMP value as a temporary key can be input to the eUICC 100 (S923). As an interface for inputting a key to the eUICC 100, You can use the PUT KEY command defined in the Global Platform Specification.

As the data field of the PUT KEY command, the key index value of the secondary key and the temporary key KEY_TEMP can be set.

In addition, the eUICC 100 may store the KEY_TEMP (S924).

Third, the SM-A 210 may delegate management of the eUICC 100 to the SM-B 220 (S930).

That is, the procedure can be performed by exchanging Credential_Delegate_Request () and Credential_Delegate_Response () between the SM-A 210 and the SM-B 220. However, since this procedure does not have a direct interface with the eUICC 100, a detailed description thereof will be omitted.

Fourth, the SM-B 220 can verify the eUICC 100 ID (S940).

In detail, the SM-B 220 can read an identifier (e.g., eUICC ID) of the eUICC 100 (S941). That is, the SM-A 210 may obtain the eUICC ID from the eUICC 100 (S942). The eUICC ID may be an embedded Integrated Chip Card Identification (eICCID), an International Mobile Subscriber Identity (IMSI), a Chip Image Number (CIN), or the like. The eUICC ID may be a value used as an identifier of the eUICC 100 in the SM- to be. Also, the eUICC ID may be a value used as the owner identifier of the eUICC key.

The SM-B 220 performs verification of the eUICC ID and the SM-B 220 can search and verify the key information mapped to the eUICC ID value in the management database (S943).

Fifth, the SM-B 220 can input and confirm a new key KEY_B in the eUICC 100 (S950).

The SM-B 220 may select a certificate management module (e.g., Profile Manager) of the eUICC 100 (S951) and perform mutual authentication through the temporary key KEY_TEMP (S952).

When the mutual authentication between the SM-B 220 and the eUICC 100 is successfully completed, the KEY_B value, which is a new key of the SM-B 220, can be input to the eUICC 100 (S953) S920) can be followed.

When the key input is successfully completed, the newly input KEY_B can be stored in the secondary credential area (S954).

Further, in order to change the newly input KEY_B to the master key, a command for confirming the key may be transmitted to the eUICC 100 (S955). For example, as an embodiment of the command interface for determining a key, an operation of changing an internal key of the eUICC 100 can be performed by transmitting the index of the master key and the index of the second key as parameters to PUT_KEY (S956) .

1 and FIG. 2, the third embodies the second step (S20) of FIG. 1 and FIG. 2, the fourth and fifth embodied in FIG. 1 and FIG. The third step (S30) of FIG. 2 can be specified.

10 is a block diagram illustrating a configuration of a subscriber identity module according to an embodiment of the present invention.

First, the eUICC 100 may have a master credential, and may additionally have a secondary credential.

Here, the master credential is a credential for confirming the authority of a request of an external entity, and the external entity may be a subscription manager (SM), an over the air server (OTA server), or the like.

The secondary credential is the candidate credential for use as the master credential.

the eUICC 100 may have one credential, i.e., a master credential, for confirming the authority of the request of the external entity, and temporarily or permanently, a secondary credential used for the SM change . Therefore, the master credential can be interpreted to mean one credential that the eUICC 100 always possesses.

Referring to FIG. 10, a subscriber authentication apparatus (module) according to an embodiment of the present invention includes a credential variable light module 110, a response module 120, and a credential determination module 130.

The credential variable light module 110 may receive a credential change request message including a temporary credential from the first subscriber management entity to change the credential. Here, the temporary credential may be a credential of the second subscriber management entity and may be in the form of a certificate, a key, a cookie, and a token.

Also, the credential variable light module 110 authenticates the first subscriber management entity using a master credential for the first subscriber management entity, and uses the temporary credential as a secondary credential Can be set.

The response module 120 may transmit the variable response message including the result information on the variable size to the first subscriber management entity to respond to the variable size.

The credential confirmation module 130 receives the credential confirmation request message based on the temporary credential from the second subscriber management entity that is delegated management by the first subscriber management entity to the subscriber authentication device and confirms the credential have.

In addition, the credential determination module 130 can authenticate the second subscriber management entity using the temporary credential, and replace the master credential with the secondary credential.

The response module 120 may also forward a credential resolution response message containing the result information for the determination to the second subscriber management entity.

The constituent parts of the subscriber identity device according to the embodiment of the present invention are described as being arranged in the respective constituent parts for convenience of explanation. However, at least two of the constituent parts may be combined into one constituent part, or one constituent part may be divided into plural constituent parts And the integrated and separate embodiments of each of these components are also included in the scope of the present invention unless departing from the essence of the present invention.

Also, the subscriber identity device can be implemented as a computer-readable program or code on a computer-readable recording medium. A computer-readable recording medium includes all kinds of recording apparatuses in which data that can be read by a computer system is stored. The computer-readable recording medium may also be distributed and distributed in a networked computer system so that a computer-readable program or code can be stored and executed in a distributed manner.

11 is a conceptual diagram for explaining a restoration method when an error occurs in a subscriber management entity change according to an embodiment of the present invention.

If there is only a master credential without distinguishing the repository of credentials from the master credential and the secondary credential in the eUICC (100), if an error occurs while changing the credential, the original master credential can not be restored .

Thus, the repository of credentials in the eUICC 100 can be divided into a master credential and a secondary credential.

Therefore, when the eUICC 100 is in the state of CREDENTIAL_A as the master credential, CREDENTIAL_B as the secondary credential, and an error occurs in changing the CREDENTIAL_B as the master credential and CREDENTIAL_A as the secondary credential, the existing master credential (CREDENTIAL_A) It can be restored to the existing credential state by storing and managing it separately.

The method and apparatus for changing a subscriber management entity according to an embodiment of the present invention as described above can safely change a subscriber management entity that manages the eUICC 100 by changing a credential in the eUICC 100, So that the embedded eUICC 100 can be effectively managed.

In addition, it is possible to effectively change the SM by using a security mechanism (certificate, key, cookie, token, etc.) applied between the eUICC 100 and the SN and to restore the SM to an existing state even if an error occurs during the SM change process Do.

It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined in the appended claims. It will be possible.

100: eUICC 110: Credential Variable Light Module
120: response module 130: credential confirmation module
210: SM-A 220: SM-B

Claims (24)

A method for changing a subscriber management entity managing a subscriber identity module,
The subscriber identity module receiving a credential change request message including a temporary credential from the first subscriber management entity and changing a credential;
Transmitting a delegation request message for delegating management of the subscriber identity module to the second subscriber management entity by the first subscriber management entity to the second subscriber management entity and requesting delegation; And
Wherein the subscriber identity module receives a credential confirmation request message based on the temporary credential from the second subscriber management entity and confirms the credential. The method according to claim 1,
The provisional credential includes:
And the second subscriber management entity is a credential of the second subscriber management entity. The method according to claim 1,
The provisional credential includes:
Wherein the subscriber management information is in the form of a certificate, a key, a cookie, and a token. The method according to claim 1,
Wherein the credential change request message comprises:
A credential type information, and a credential value. The method according to claim 1,
The step of variable citing the credential comprises:
Wherein the subscriber identity module authenticates the first subscriber management entity using a master credential for the first subscriber management entity. The method of claim 5,
The step of variable citing the credential comprises:
Wherein the temporary credential is set as a secondary credential. The method according to claim 1,
After performing the steps of varying the credential,
Wherein the subscriber identity module further transmits a variable light response message including result information on the variable size to the first subscriber management entity to respond to the variable size. The method according to claim 1,
The step of establishing the credentials comprises:
Wherein the subscriber identity module authenticates the second subscriber management entity using the provisional credential. The method of claim 6,
The step of establishing the credentials comprises:
And replacing the master credential with the secondary credential. The method according to claim 1,
After performing the step of establishing the credentials,
Further comprising: the subscriber identity module transmitting a credential determination response message including result information on the determination to the second subscriber management entity. In changing the subscriber management entity performed by the subscriber identity module,
Receiving a credential change request message including a temporary credential from a first subscriber management entity to change a credential;
Transmitting a variable light response message including result information on the variable size to the first subscriber management entity and responding to the variable size; And
Receiving a credential confirmation request message based on the temporary credential from a second subscriber management entity delegated management by the first subscriber management entity to the subscriber authentication module and establishing a credential; How to change objects. The method of claim 11,
The provisional credential includes:
And the second subscriber management entity is a credential of the second subscriber management entity. The method of claim 11,
The provisional credential includes:
Wherein the subscriber management information is in the form of a certificate, a key, a cookie, and a token. The method of claim 11,
The step of variable citing the credential comprises:
Authenticating the first subscriber management entity using a master credential for the first subscriber management entity,
Wherein the temporary credential is set as a secondary credential. 15. The method of claim 14,
The step of establishing the credentials comprises:
Authenticating the second subscriber management entity using the provisional credential,
And replacing the master credential with the secondary credential. 16. The method of claim 15,
The step of establishing the credentials comprises:
When an error occurs in replacing the master credential with the secondary credential,
And restoring the subscriber management entity before the step of establishing the credential. The method of claim 11,
After performing the step of establishing the credentials,
And forwarding a credential determination response message including result information on the confirmation to the second subscriber management entity. 1. A subscriber identity device built in a terminal device and changing a subscriber management entity,
A credential change module that receives a credential change request message including a temporary credential from the first subscriber management entity and changes the credential;
A response module for delivering a variable light response message including result information on the variable light to the first subscriber management entity and responding to the variable light path; And
And a credential confirmation module for confirming a credential by receiving a credential confirmation request message based on the temporary credential from a second subscriber management entity delegated management of the subscriber authentication apparatus by the first subscriber management entity . 19. The method of claim 18,
The provisional credential includes:
And the second subscriber management entity is a credential of the second subscriber management entity. 19. The method of claim 18,
The provisional credential includes:
Wherein the authentication information is in the form of a certificate, a key, a cookie, and a token. 19. The method of claim 18,
Wherein the credential variable light module comprises:
Authenticating the first subscriber management entity using a master credential for the first subscriber management entity,
Wherein the temporary credential is set as a secondary credential. 23. The method of claim 21,
The credential confirmation module includes:
Authenticating the second subscriber management entity using the provisional credential,
And replaces the master credential with the secondary credential. 19. The method of claim 18,
The response module comprises:
And transmits a credential determination response message including result information on the confirmation to the second subscriber management entity. 23. The method of claim 21,
Wherein the master credential and the secondary credential are distinguished from each other and stored.

Images