CONTAINER

(Field of the invention)

The present invention relates to methods of updating a secret data stored in a credential container. It relates particularly to methods of updating secret data by using a communication channel established between a remote server and a Telecom equipment.

(Background of the invention)

In order to securely connect a telecom communication network, a user equipment needs to be provisioned with full Telecom credentials known as the couple IMSI/Ki, where IMSI is a unique identifier of the telecom subscription and Ki a secret key uniquely allocated to the subscription by a mobile network operator.

The couple IMSI/Ki is usually stored in a tamper resistant element which may be a SIM card, a Universal Integrated Circuit Card (UICC) , an embedded secure element (e.g. eUICC) , a software secure enclave or a secure element integrated (i.e. iUICC) within a System On Chip (SOC) .

A tamper resistant element is considered as secure because it is able to control the access to the data it contains and to authorize or not the use of its data by other machines or entities. Tamper resistant elements may also provide computation services based on cryptographic components (a.k.a. crypto processor). In general, tamper resistant elements have limited computing resources and limited memory resources and they are intended to be connected to a host machine which provides them with electric power. Tamper resistant elements may be removable or fixed to a host machine.

Due to security policies or user management policies, a network operator can need to update the secret values used by a device deployed on the field for authenticating to the communication network. Typically, a network operator may want to update the authentication key Ki of a UICC.

There is a need to securely update, in a tamper resistant element, the current secret data used to authenticate to a communication network.

( Summary of the Invention)

An object of the invention is to solve the above mentioned technical problem.

An object of the present invention is a method for updating a first secret data in a credential container including a subscriber identity module . The credential container comprises a set of secret parameters customized for a network operator and is configured to execute a symmetric mutual authentication algorithm using said set. The credential container receives from a remote server a second secret data enciphered using a second algorithm different from said symmetric mutual authentication algorithm and a subset of said secret parameters. The credential container deciphers the enciphered second secret data by using both the subset and a third algorithm and replaces the first secret data with the second secret data .

Advantageously, the symmetric mutual authentication algorithm may be the Milenage algorithm as defined by ETSI TS 135.206 or the TUAK algorithm as defined by ETSI TS 135.231.

Advantageously, the second and third algorithms may be identical.

Advantageously, the second algorithm may take the first secret data as input parameter for generating the enciphered second secret data.

Advantageously, the second algorithm may be based on a one-time-pad encryption.

Advantageously, the first secret data may be used as a mask applied on the set to identify the subset.

Advantageously, the first secret data may be a subscriber authentication key.

Another object of the invention is a credential container comprising a processor and a first secret data and able to receive a message from a remote server. The credential container includes a subscriber identity module and comprises a set of secret parameters customized for a network operator. The credential container is configured to execute a symmetric mutual authentication algorithm using said set. The message comprises a second secret data enciphered using both a subset of said secret parameters and a second algorithm different from the symmetric mutual authentication algorithm. The credential container comprises an updating agent adapted to be run by the processor for deciphering the enciphered second secret data by using both the subset and a third algorithm and replacing the first secret data with the second secret data.

Advantageously, the symmetric mutual authentication algorithm may be the Milenage algorithm as defined by ETSI TS 135.206 or the TUAK algorithm as defined by ETSI TS 135.231.

Advantageously, the second algorithm may take the first secret data as input parameter for generating the enciphered second secret data.

Advantageously, the second algorithm may be based on a one-time-pad encryption.

Advantageously, the credential container may be a SIM, a UICC, a eUICC or an iUICC.

Another object of the invention is a server comprising a processor and able to send a message to a credential container including both a subscriber identity module and a first secret data. The server comprises a set of secret parameters customized for a network operator and is configured to execute a symmetric mutual authentication algorithm using said set. The server comprises a provisioning agent adapted to be run by the processor for generating a second secret data enciphered using both a subset of said secret parameters and a second algorithm different from the symmetric mutual authentication algorithm and for including the enciphered second secret data in said message, the second secret data being intended to replace the first secret data in the credential container.

Advantageously the second algorithm may be based on a one-time-pad encryption. (Brief description of the drawings)

Other characteristics and advantages of the present invention will emerge more clearly from a reading of the following description of a number of preferred embodiments of the invention with reference to the corresponding accompanying drawings in which:

Figure 1 depicts schematically a system comprising an example of credential container and an example of server according to the invention,

- Figure 2A shows a first part of a flow diagram for updating a secret data according to an example of the invention, and

- Figure 2B shows a second part of a flow diagram for updating a secret data according to an example of the invention .

(Detailed description of the preferred embodiments)

The invention may apply to any type of credential container to be provisioned with new secret data.

Such a credential container may be a tamper resistant element like a SIM, a UICC, a eUICC, an iUICC, a MIM (Machine Identification Module) or a software secure enclave .

The credential container may be connected to a host device like a smartphone, a tablet, a personal computer, a smart watch, a vehicle, a meter, a slot machine, a TV or a computer for example.

Figure 1 shows schematically the architecture of a credential container 20 according to an example of the invention and the architecture of a remote server 30 according to an example of the invention. The system 100 includes both the credential container 20 and the server 30. In this example, the credential container is a UICC.

The server 30 can be an Authentication center (AuC) which is able to validate any attempt to connect a mobile communication network.

The credential container 20 comprises a processor 70, a working memory 74 (e.g. RAM) and a non-volatile memory 72. It is configured to communicate with the server 30 through command/response pairs.

The credential container 20 comprises a set 77 of secret parameters which have been customized for the network operator that manages a subscription installed in the UICC. These secret parameters are intended to be used to execute a symmetric mutual authentication algorithm in order to authenticate to a communication network. For instance, the secret parameters can include both the variables Cl to C5 and R1 to R5 as defined by ETSI TS 135.206 V9.0.0 (2010-02). The credential container 20 is configured to execute a symmetric mutual authentication algorithm using said set 77. In the example of Figure 1, the credential container 20 comprises a software authenticating agent 75 which is adapted to be run by the processor 70 for authenticating to the remote server 30 using a symmetric mutual authentication algorithm. In a preferred embodiment, the symmetric mutual authentication algorithm is the Milenage algorithm as defined by ETSI TS 135.206 V9.0.0 (2010-02).

In another embodiment, the symmetric mutual authentication algorithm can be the TUAK algorithm as defined by ETSI TS 135.231 V12.1.0 (2014-10). The authentication key Ki (i.e. secret data) 76 is stored in the non-volatile memory 72.

The credential container 20 is configured to receive, from the remote server 30, a message 85 that comprises a new secret data 78 which has been enciphered using both a subset 79 of the set 77 of secret parameters and an algorithm different from the symmetric mutual authentication algorithm.

The credential container 20 comprises an updating agent 73 adapted to be run by the processor 70 for deciphering the enciphered new secret data by using both the subset 79 and a deciphering algorithm and for replacing the secret data 76 (also named current secret data) with the new secret data 78.

Preferably, the ciphering algorithm used by the server 30 and the deciphering algorithm used by the credential container 20 are based on the one-time-pad encryption .

Alternatively the ciphering algorithm and the deciphering algorithm may be based on the Advanced Encryption Standard (AES) .

The one-time-pad encryption is a cryptographic mechanism based on the use of a one-time pre-shared key (also named one-time-pad) which has a size longer than (or equal to) the length of the data to encipher. Each bit of the data to encipher is encrypted by combining it with the corresponding bit from the one-time pre-shared key using a modular addition.

For instance, the new secret data may be enciphered by the server 30 as follows: Enciphered secret data = current secret data © new secret data © Cl © C2 © C3 © C4 © C5;

where © stands for the bitwise exclusive-OR operation .

This way, the new secret data 78 is enciphered with a one-time value based on both the value of the current secret data 76 (also named current secret data) and the variables Cl to C5 of the Milenage algorithm.

Then the new secret data 78 can be deciphered by the credential container 20 using the same algorithm:

New secret data = enciphered secret data © current secret data © Cl © C2 © C3 © C4 © C5.

In the above presented example, the subset 79 includes the variables Cl to C5 only.

In one embodiment, the subset can be predefined in both sides: Server and credential container.

In another embodiment, the subset definition may be sent from the server 30 to the credential container. For instance the message sent by the server to the credential container may include both the enciphered secret data and the definition of the subset 79.

In another embodiment, the subset can be defined using the content of the secret data 76. For instance, the secret data 76 may be used as a mask applied on the set 77. Let's assume that the 10 first bit of the secret data 76 are 0100010011, and that the set 77 if the ordered list of Milenage parameters Cl, ..., C5, Rl, ..., R5. By applying the mask, the following parameters are selected: C2, Rl, R4 and R5. Thus the new secret data can be enciphered by the server 30 as follows: Enciphered secret data = current secret data © new secret data © C2 © R1 © R4 © R5.

In the example of Figure 1, the server 30 comprises a processor 80 which is able to send a message 85 to the credential container. The server 30 comprises a non volatile memory 82 which stores the current secret data 76 (e.g. Ki) and the same set 77 as the credential container 20. The secret parameters are supposed to be uniquely allocated to the network operator and not shared with any third party.

It is to be noted that the set of secret parameters only depends on the network operator while the current secret data depends on the credential container.

The server 30 is configured to execute a symmetric mutual authentication algorithm using this set 77. Preferably, the symmetric mutual authentication algorithm is used to authenticate the credential container 20 when the credential container requests to access a communication network. The server 30 comprises a software provisioning agent 83 adapted to be run by the processor 80 for generating a new secret data 78 enciphered using both a subset 79 of the set 77 and another algorithm different from the symmetric mutual authentication algorithm. The provisioning agent 83 adapted is adapted to include the enciphered second secret data in the message 85.

In the above presented embodiments, the enciphering and deciphering algorithms take the current secret data 76 as input parameter. Alternatively, the server and the credential container may use a random value instead of the current secret data so that the one-time-pad has a value which is unique for each replacement operation. In this case, the server may send the random value to the credential container through the message 85.

In the above presented embodiments, the enciphering and deciphering algorithms are similar. Alternatively, they may be different. For instance, the enciphering and deciphering algorithms may be based on Public-key cryptography (also named asymmetric cryptography) that uses a pair of public and private keys.

It is to be noted that, the secret parameters of the selected subset may be combined to generate intermediate values which have a size greater than (or equal) the size of the secret data to be updated. For instance, the secret parameters Cl and C3 may be concatenated to generate an intermediate secret value having a length of 256 bits (i.e. 2 x 128 bits) .

Figures 2A and 2B show a flow diagram for updating a secret data according to an example of the invention.

The credential container 20 is assumed to be pre provisioned with an authentication key Ki, an OPC (as defined by ETSI TS 135.206 V9.0.0) and a set 77 of secret parameters defined for a symmetric mutual authentication algorithm like Milenage.

In this example, the server 30 comprises two elements: a K-HSS and a MNO-HSS. The MNO-HSS can be a conventional Home Subscriber Server (HSS) and the K-HSS may be a proxy HSS in charge of Ki management. In another embodiment, the K-HSS may be a conventional Home Subscriber Server connected to an Authentication center (AuC) . In another embodiment, the K-HSS and the MNO-HSS may be merged in a single server which acts as Authentication center (AuC) .

At step SOI, the mobile Network operator (MNO) which manages the subscription stored in the UICC 20 decides to update the authentication key Ki and the OPC for the UICC 20 which is identified by its IMSI (International Mobile Subscriber Identity) .

At step S02, the UICC 20 sends an Attach request comprising its IMSI to its connected MME (Mobile Management Entity) . The MME may be a smartphone for example) .

The traffic for this IMSI is routed to K-HSS to initiate the Ki update. This routing is MNO triggered. Thus the MME sends a SAI (Send Authentication Information or MAP_SEND_AUTHENTICATION_INFO service) comprising the IMSI to the K-HSS (i.e. to server 30) at step S03. More details about SAI can be found in ETSI TS 129 002 [V10.2.0] for example.

At step S04, the K-HSS computes a new Ki and a new OPC allocated to the IMSI. Alternatively, it may retrieve them from another entity in charge of the MNO Ki generation .

At step S05, the K-HSS identifies the subset 79 and enciphers the new Ki and OPC with this subset 79 and a first algorithm like one-time-pad encryption for instance. Authentication parameter RAND field and Authentication parameter AUTN field of an Authentication Request frame are defined by ETSI TS 124.008. The RAND can be set with the enciphered new Ki and the AUTN is computed with this RAND. Preferably, a bit in the AMF (Authentication Management Field) includes a reference that triggers the command to update the Ki . More details about AMF can be found in ETSI TS 133.102.

At step SO 6, the K-HSS sends to the MME a SAI Ack message comprising the enciphered new Ki, the computed AUTN and the AMF. The SAI Ack message is sent upon receipt of the SAI by the K-HSS.

At step S07, on receipt of the SAI Ack message, the MME sends to the UICC an Authentication request comprising the enciphered new Ki, the computed AUTN and the AMF .

At step S08, on receipt of the Authentication request, the UICC identifies both the network and the subset 79. Then it retrieves the new Ki by deciphering the enciphered new Ki using the subset and a second algorithm like one-time-pad encryption for instance. Additionally, the UICC analyzes the received AMF to identify the target of the update command, (i.e. the Ki)

More details related to the management of Authentication request and network identification can be found at §6.3.3 of ETSI TS 133.102 V3.6.0 for example.

Once the deciphering operation is complete, the UICC sends back an acknowledgment message in the synchronization token AUTS (i.e. AUTS parameter as detailed in ETSI TS 133 102) to continue the process. At step S09, the UICC sends to the MME an Authentication failure message comprising the IMSI and the AUTS. Preferably, the AUTS is set with the concatenation of the fourteen first bits of the enciphered Ki and the bits 5- 18 of the ICCID (Integrated Circuit Card Identifier) . At step S10, upon receipt of the Authentication failure message, the MME sends to the K-HSS a SAI message comprising the IMSI and the AUTS.

At step Sll, the K-HSS decodes the received AUTS message and validates the initial sender (i.e. the UICC 20) . If the UICC is successfully validated, the K-HSS prepares a new message to convey the new OPC. Although the new OPC has been enciphered at step 05, it may be enciphered at step Sll. The RAND can be set with the enciphered new OPC and the AUTN is computed with this RAND. Preferably, a bit in the AMF (Authentication Management Field) includes a reference that triggers the command to update the OPC.

At step S12, the K-HSS sends to the MME a SAI Ack message comprising the enciphered new OPC, the AUTN and the AMF .

As noted by the link "F", the sequence continues at Figure 2B.

At step S13, upon receipt of the SAI Ack message, the MME sends to the UICC an Authentication request comprising the enciphered new OPC, the AUTN and the AMF.

At step S14, the UICC identifies the network and retrieves the new OPC by deciphering the enciphered new OPC using the subset 79 and the second algorithm. The UICC checks the content of the received AMF to identify the target of the update command, (i.e. the OPC)

It is to be noted that the subset used for enciphering/deciphering the new OPC can be different from the subset used to enciphering/deciphering the new Ki .

At step S15, the UICC sends to the MME an Authentication answer comprising RES. Details related to RES management can be found in TS 133.102.

At step S16, the MME sends to the K-HSS a Location Update message.

At step S17, upon Location Update message, the MNO- HSS is updated with new Ki/OPC. The new Ki/OPC are sent to the MNO-HSS which activates these new values.

At step S18, upon receipt of the Location Update message, the K-HSS sends to the MME Location Update Error message .

At step S19, upon receipt of the Location Update Error message the MME sends to the UICC an Attach

Request reflecting a reject.

At step S20, upon receipt of the Attach Request reflecting a reject, the UICC replaces the previous pair (Ki,OPC) by the new pair (Ki,OPC) .

At step S21, the UICC performs a Refresh proactive command. Thanks to the Refresh command performed in ad- hoc mode, a new boot sequence is performed. This leads to new attachment to network and authentication.

At step S22, the UICC sends to the MME an Attach request (as defined by ETSI TS 124.008) comprising the IMS I .

At step S23, the MME sends to the K-HSS a SAI message comprising the IMSI.

At step S24, the K-HSS forwards the SAI message to the MNO-HSS which performs an authentication based on new Ki/OPC. The authentication can succeed since both Ki and OPC have been updated in both sides: Server 30 and UICC 20. The new Ki/OPC can be sent to the UICC by other protocols. For example, the server may send the new Ki/OPC through a conventional OTA channel or through a combination Internet/Wi-Fi .

The updating method of the invention can be used to update any keys stored in the credential container 20.

In particular, the invention allows to update the current secret data which is used to authenticate to a communication network, (i.e. current secret data used for secure communication between a credential container and a remote server) .

The invention is well-suited for managing the provisioning of a fleet of credential containers.

The invention is well-suited for updating a secret data whose value may be compromised. In particular, assuming that the initial secret data to replace and the secret parameters of the algorithm have been provisioned through separate channels, the invention allows to securely update the initial secret data even if the channel used to provision the initial secret data has been hacked.

The described embodiments or examples may be combined .