Method of managing a tamper-proof device comprising several software containers

Patent metadata

Field	Value
Publication number	US-2020279059-A1
Application number	US-201816765199-A
Country	US
Kind code	A1
Filing date	Nov 6, 2018
Priority date	Nov 21, 2017
Publication date	Sep 3, 2020
Grant date	—

Abstract

The invention is a method for managing a tamper-proof device comprising a plurality of software containers and an operating system. The operating system is able to handle a set of communication protocols with external entities. The operating system accesses a pairing data in which each communication protocol of said set has been associated with a single software container and upon receipt of a message from one of the external entities, the operating system uses the pairing data to route the message to the software container associated with the communication protocol used to convey the message.

First claim

1 . A method for managing a secure element comprising a plurality of software containers and an operating system, said operating system being configured to handle a set of communication protocols with external entities,
wherein the operating system accesses a pairing data comprising a description of an association between each communication protocol of said set and a software container belonging to the plurality of software containers, each of said communication protocols being associated with a single software container, and wherein upon receipt of a message from one of said external entities, the operating system routes the message to the software container which is declared in the pairing data as being associated with the communication protocol used to convey the message.

2 . The method according to claim 1 , wherein each software container of said plurality comprises a file which is targeted by said external entities by means of a common identifier.

3 . The method according to claim 1 , wherein each software container of said plurality comprises a root file which is targeted by said external entities by means of a common identifier.

4 . The method according to claim 2 , wherein the operating system uses the pairing data to route the message only in case the message targets said common identifier.

5 . The method according to claim 1 , wherein the plurality of software containers comprises both a security domain compliant with GlobalPlatform Card Specification standard and a Telecom profile compliant with GSMA SGP 0.22 RSP Technical Specification standard.

6 . The method according to claim 1 , wherein the secure element is an embedded secure element, an integrated secure element, a secure enclave, a smart card or a Machine-To-Machine device.

7 . The method according to claim 1 , wherein the set of communication protocols comprises T=0 or T=1 as defined by ETSI ISO7816-3 and at least one of the following group: SWP contactless type A, SWP contactless type B, APDU Gate or SPI.

8 . A secure element comprising a plurality of software containers and an operating system, said operating system being configured to handle a set of communication protocols with external entities,
wherein the operating system comprises a pairing data comprising a description of an association between each communication protocol of said set and a software container belonging to the plurality of software containers, each of said communication protocols being associated with a single software container, and wherein the operating system comprises a routing agent configured to, upon receipt of a message from one of said external entities, route the message to the software container which is declared in the pairing data as being associated with the communication protocol used to convey the message.

9 . The secure element according to claim 8 , wherein each software container of said plurality comprises a file which is targeted by said external entities by means of a common identifier.

10 . The secure element according to claim 8 , wherein each software container of said plurality comprises a root file which is targeted by said external entities by means of a common identifier.

11 . The secure element according to claim 9 , wherein the routing agent is configured to use the pairing data to route the message to the software container associated with the communication protocol used to convey the message only in case the message targets said common identifier.

12 . The secure element according to claim 8 , wherein the plurality of software containers comprises both a security domain compliant with GlobalPlatform Card Specification standard and a Telecom profile compliant with GSMA SGP 0.22 RSP Technical Specification standard.

13 . The secure element according to claim 8 , wherein the secure element is an embedded secure element, an integrated secure element, a secure enclave, a smart card or a Machine-To-Machine device.

14 . The secure element according to claim 8 , wherein the set of communication protocols comprises T=0 or T=1 as defined by ETSI ISO7816-3 and at least one of the following group: SWP contactless type A, SWP contactless type B, APDU Gate or SPI.

15 . A host device embedding a secure element device according to claim 8 .

Assignees

• Thales Dis France Sa

Inventors

• Courtiade Fabien
• Labourie Florent
• Dubois Denis
• Ahmad Syarif
• Yang Jianrong
• Pahala Nopiga
• Yong Sharon Shier Loon Sharon

Classifications

• H04W4/60

  Subscription-based services using application servers or record carriers, e.g. SIM application toolkits · CPC title

• H04W12/04

  Key management, e.g. using generic bootstrapping architecture [GBA] · CPC title

• H04W12/45

  using multiple identity modules · CPC title

• H04W12/35

  Protecting application or service provisioning, e.g. securing SIM application provisioning · CPC title

• H04W12/086

  using security domains · CPC title