# US 2021/0334362 A1 · Method to upgrade a tee trusted application to a server mode

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0334362 A1
- Document ID: US20210334362A1
- Status: Published application
- Kind: A1
- Application number: 17/278,318
- Filed: 2019-09-17
- Published: 2021-10-28
- Earliest claimed: 2018-09-20
- Assignees: Thales Dis France SAS
- Applicants: Thales Dis France SA
- Inventors: Geoffroy COGNIAUX
- Web page: https://patentgrep.com/patent/US20210334362A1

## CPC

- G06F 21/53: by executing in a restricted environment, e.g. sandbox or secure virtual machine
- G06F 9/541: {via adapters, e.g. between incompatible applications}
- H04L 63/0281: {Proxies}
- G06F 8/61: Installation
- G06F 2221/033: Test or assess software
- G06F 2221/2149: Restricted operating environment
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Upgrade to a Trusted Application in a Trusted Execution Environment compliant to a Trusted Execution Environment standard to an as-a-server functioning by running, inside the Trusted Execution Environment, each instance of a Multi Instance/Single Session Trusted-Server Trusted Application compliant to the TEE standard in an infinite state-full loop polling a session of a Single Instance/Multi Session Trusted-Pipe Trusted Application, the single session of each of the instance of the Trusted-Server Trusted Application being adapted to perform a task as a server, said Trusted-Pipe Trusted Application being further polled by the Customer Application and opening session depending on command coming from the Customer Application.

## Claims

### Claim 1

A method to upgrade a Trusted Application in an Execution Environment compliant to a Trusted Execution Environment standard to an as-a-server functioning, said standard defining at least one of the following locks preventing the Trusted Application in a Trusted Execution Environment to function as-a-server:
a Customer Application having a session opened in an instance of a Trusted Application enters in a blocking state immediately after having sent a Command to the Trusted Application and while the Trusted Application's Task has not finished,
a Trusted Application cannot partially execute a Task,
execution context of a Trusted Application is deleted between an executed Task and a subsequent command in an opened instance/session,
a Trusted Application has to be Single Instance/Multi Session or Multi Instance/Single Session,
said method comprising:
running, inside the Trusted Execution Environment, each instance of a Multi Instance/Single Session Trusted-Server Trusted Application compliant to the TEE standard in an infinite state-full loop polling a session of a Single Instance/Multi Session Trusted-Pipe Trusted Application, the single session of each of the instance of the Trusted-Server Trusted Application being adapted to perform a task as a server,
meanwhile polling, by the Customer Application, said Trusted-Pipe Trusted Application,
opening a session depending on a command coming from the Customer Application,
exchanging data asynchronously between said Customer Application and said Trusted-Server Trusted Application by the polling mechanism making said Trusted-Pipe Trusted Application function as a mailbox for said Customer Application and said Trusted-Server Trusted Application,
wherein said Customer Application and said Trusted-Server Trusted Application accomplish their respective tasks without blocking each other and enabling the Trusted-Server Trusted Application to request data within its currently executing task without stopping it.

### Claim 2 (depends on 1)

The method according to claim 1, further comprising once a connection between the Customer Application and the Trusted-Server Trusted Application has been opened, allocating, by the Trusted-Pipe Trusted Application, two FIFO that permit data exchanges between the Customer Application and the Trusted-Server Trusted Application, one couple of FIFO being allocated for each connection between the Customer Application and the Trusted-Server Trusted Application and corresponds to one session allocated by the Trusted-Pipe Trusted Application.

### Claim 3 (depends on 2)

The method according to claim 2, wherein the polling commands sent either by said Trusted-Server Trusted Application to Trusted-Pipe Trusted Application consist in reading and writing the allocated two FIFO where the said Customer Application polls a first FIFO filled by the Trusted-Server Trusted Application using specific commands posted to the Trusted-Pipe Trusted Application, and where the said Trusted-Server Trusted Application polls a second FIFO filled by the Customer Application using specific commands posted to the Trusted-Pipe Trusted Application.

### Claim 4 (depends on 1)

The method according to claim 1, comprising preliminary steps of installing a Customer Application gateway on the client side while also installing the Single Instance/Multi Session Trusted-Pipe Trusted Application in the Trusted Execution Environment and the Multi Instance/Single Session Trusted-Server Trusted Application, said Customer Application gateway being adapted to manage communication between the Customer Application and said Trusted-Pipe Trusted Application.

### Claim 5 (depends on 1)

The method according to claim 1, wherein said method comprises the steps of:
opening, by the Customer Application, an Instance at the Trusted-Pipe Trusted Application,
opening, by the Trusted Pipe Trusted Application, several Sessions depending on the Tasks to be performed in the as-a-server functioning, each of these Sessions opening one Instance of the Trusted-Server Trusted Application,
opening, by the Trusted Server Trusted Application, a Single session for each of the multiple Instances opened by the Trusted-Server Trusted Application to execute the Tasks to be performed in the as-a-server functioning, each of these Single Sessions functioning in an infinite state-full loop polling the Trusted-Pipe Trusted Application as far as the Single Instance of the Trusted-Pipe Trusted Application is active, the multiple Single Sessions of the Trusted-Server Trusted Application enabling to perform any operation in parallel while being adapted to retrieve execution data when needed.

### Claim 6 (depends on 1)

The method according to claim 1, wherein said Customer Application gateway is a proxy server waiting for remote connections or a library statically linked to a classic customer application.

### Claim 7

A library intended to be installed in a Trusted Execution Environment to upgrade any Trusted Application in the Execution Environment compliant to a Trusted Execution Environment standard to an as-a-server functioning according to any one of the preceding claims, where such library exports functions at the Trusted Application to read and write data from/to the Customer Application, bootstrap capabilities starting the server infinite loop at the Trusted Application and communication capabilities at the Trusted Application to communicate with the Trusted-Pipe TA, making any Trusted Application linked to this library functioning as a Trusted-Server TA , the library comprising:
an upgrade to a Trusted Application in an Execution Environment compliant to a Trusted Execution Environment standard to an as-a-server functioning, said standard defining at least one of the following locks preventing the Trusted Application in a Trusted Execution Environment to function as-a-server:
a Customer Application having a session opened in an instance of a Trusted Application enters in a blocking state immediately after having sent a Command to the Trusted Application and while the Trusted Application's Task has not finished,
a Trusted Application cannot partially execute a Task,
execution context of a Trusted Application is deleted between an executed Task and a subsequent command in an opened instance/session,
a Trusted Application has to be Single Instance/Multi Session or Multi Instance/Single Session,
said method running, inside the Trusted Execution Environment, each instance of a Multi Instance/Single Session Trusted-Server Trusted Application compliant to the TEE standard in an infinite state-full loop polling a session of a Single Instance/Multi Session Trusted-Pipe Trusted Application (TP), the single session of each of the instance of the Trusted-Server Trusted Application being adapted to perform a task as a server, while said Trusted-Pipe Trusted Application being further polled by the Customer Application and opening session depending on command coming from the Customer Application, this polling mechanism making said Trusted-Pipe Trusted Application functioning as a mailbox for said Customer Application and said Trusted-Server Trusted Application to exchange data asynchronously, while accomplishing their respective tasks without blocking each other and enabling the Trusted-Server Trusted Application to request data within its currently executing task without stopping it.

### Claim 8

Trusted Execution Environment comprising:
an upgrade to a Trusted Application in an Execution Environment compliant to a Trusted Execution Environment standard to an as-a-server functioning, said standard defining at least one of the following locks preventing the Trusted Application in a Trusted Execution Environment to function as-a-server:
a Customer Application having a session opened in an instance of a Trusted Application enters in a blocking state immediately after having sent a Command to the Trusted Application and while the Trusted Application's Task has not finished,
a Trusted Application cannot partially execute a Task,
execution context of a Trusted Application is deleted between an executed Task and a subsequent command in an opened instance/session,
a Trusted Application has to be Single Instance/Multi Session or Multi Instance/Single Session,
said method running, inside the Trusted Execution Environment, each instance of a Multi Instance/Single Session Trusted-Server Trusted Application compliant to the TEE standard in an infinite state-full loop polling a session of a Single Instance/Multi Session Trusted-Pipe Trusted Application (TP), the single session of each of the instance of the Trusted-Server Trusted Application being adapted to perform a task as a server, while said Trusted-Pipe Trusted Application being further polled by the Customer Application and opening session depending on command coming from the Customer Application, this polling mechanism making said Trusted-Pipe Trusted Application functioning as a mailbox for said Customer Application and said Trusted-Server Trusted Application to exchange data asynchronously, while accomplishing their respective tasks without blocking each other and enabling the Trusted-Server Trusted Application to request data within its currently executing task without stopping it.

### Claim 9

An upgrade to a Trusted Application in an Execution Environment compliant to a Trusted Execution Environment standard to an as-a-server functioning, said standard defining at least one of the following locks preventing the Trusted Application in a Trusted Execution Environment to function as-a-server:
a Customer Application having a session opened in an instance of a Trusted Application enters in a blocking state immediately after having sent a Command to the Trusted Application and while the Trusted Application's Task has not finished,
a Trusted Application cannot partially execute a Task,
execution context of a Trusted Application is deleted between an executed Task and a subsequent command in an opened instance/session,
a Trusted Application has to be Single Instance/Multi Session or Multi Instance/Single Session,
said method running, inside the Trusted Execution Environment, each instance of a Multi Instance/Single Session Trusted-Server Trusted Application compliant to the TEE standard in an infinite state-full loop polling a session of a Single Instance/Multi Session Trusted-Pipe Trusted Application (TP), the single session of each of the instance of the Trusted-Server Trusted Application being adapted to perform a task as a server, while said Trusted-Pipe Trusted Application being further polled by the Customer Application and opening session depending on command coming from the Customer Application, this polling mechanism making said Trusted-Pipe Trusted Application functioning as a mailbox for said Customer Application and said Trusted-Server Trusted Application to exchange data asynchronously, while accomplishing their respective tasks without blocking each other and enabling the Trusted-Server Trusted Application to request data within its currently executing task without stopping it.

### Claim 10 (depends on 9)

The upgrade to a Trusted Application in an Execution Environment according to claim 9, wherein once a connection between the Customer Application and the Trusted-Server TA has been opened, the Trusted-Pipe TA allocates two FIFO that permit data exchanges between the Customer Application and the Trusted-Server TA, one couple of FIFO being allocated for each connection between the Customer Application and the Trusted-Server TA and corresponds to one session allocated by the Trusted-Pipe TA.

### Claim 11 (depends on 10)

The upgrade to a Trusted Application in an Execution Environment according to claim 10, wherein the polling commands sent either by said Trusted-Server Trusted Application to Trusted-Pipe Trusted Application consist in reading and writing the allocated two FIFO where the said Customer Application polls a first FIFO filled by the Trusted-Server Trusted Application using specific commands posted to the Trusted-Pipe Trusted Application, and where the said Trusted-Server Trusted Application polls a second FIFO filled by the Customer Application using specific commands posted to the Trusted-Pipe Trusted Application.

### Claim 12 (depends on 9)

The upgrade to a Trusted Application in an Execution Environment according to claim 9, comprising the preliminary steps of installing a Customer Application gateway on the client side while also installing the Single Instance/Multi Session Trusted-Pipe Trusted Application in the Trusted Execution Environment and the Multi Instance/Single Session Trusted-Server Trusted Application, said Customer Application gateway being adapted to manage communication between the Customer Application and said Trusted-Pipe Trusted Application.

### Claim 13 (depends on 9)

The upgrade to a Trusted Application in an Execution Environment according to claim 9, wherein said method comprises the steps of:
for the Customer Application, opening an Instance at the Trusted-Pipe Trusted Application,
for the Trusted-Pipe Trusted Application, opening several Sessions depending on the Tasks to be performed in the as-a-server functioning, each of these Sessions opening one Instance of the Trusted-Server Trusted Application,
for the Trusted-Server Trusted Application, opening a Single session for each of the multiple Instances opened by the Trusted-Server Trusted Application to execute the Tasks to be performed in the as-a-server functioning, each of these Single Sessions functioning in an infinite state-full loop polling the Trusted-Pipe Trusted Application as far as the Single Instance of the Trusted-Pipe Trusted Application is active, the multiple Single Sessions of the Trusted-Server Trusted Application enabling to perform any operation in parallel while being adapted to retrieve execution data when needed.

### Claim 14 (depends on 9)

The upgrade to a Trusted Application in an Execution Environment according to claim 9, wherein said Customer Application gateway is a proxy server waiting for remote connections or a library statically linked to a classic customer application.
