# US 2020/0349252 A1 · Program execution and data proof scheme using multiple key pair signatures

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

- Number: US 2020/0349252 A1
- Document ID: US20200349252A1
- Status: Published application
- Kind: A1
- Application number: 16/933,629
- Filed: 2020-07-20
- Published: 2020-11-05
- Earliest claimed: 2019-03-26
- Assignees: Alibaba Group Holding Limited
- Applicants: Alibaba Group Holding Limited
- Inventors: Yirong Yu; Honglin Qiu
- Web page: https://patentgrep.com/patent/US20200349252A1

## CPC

- G06F 21/53: by executing in a restricted environment, e.g. sandbox or secure virtual machine
- G06F 21/602: {Providing cryptographic facilities or services}
- G06F 21/64: Protecting data integrity, e.g. using checksums, certificates or signatures
- G06F 21/72: in cryptographic circuits
- H04L 9/006: {involving public key infrastructure [PKI] trust models (network architecture or network communication protocol for supporting authentication of entities using certificates in a packet data network H04L63/0823)}
- H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD}
- H04L 9/3247: {involving digital signatures}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- 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

Methods, systems, and apparatus, including computer programs encoded on computer storage media for program execution and data proof scheme to prove that sub-logic code that was expected to be executed within a TEE was indeed executed, and that the resulting data is trustworthy. In some implementations, each sub-logic code of a plurality of sub-logic code is registered, and stored within the TEE, and a key pair (private key, public key) corresponding to the sub-logic code is generated. The client receives and stores the public key, sends requests to the TEE with an identifier of the sub-logic that is to be executed. The sub-logic code corresponding to the identifier is executed within the TEE, which signs the result using a digital signature that is generated using the private key of the sub-logic code. The client verifies the result based on the digital signature and the public key of the sub-logic code.

## Claims

### Claim at position 1

-24. (canceled)

### Claim 25

A computer-implemented method for program execution and data proof for executing a sub-logic code within a trusted execution environment (TEE), the method comprising:
transmitting, by a client device, a request to a node, the node executing a trusted program within a TEE, the request comprising an identifier and one or more request parameters, the identifier identifying the sub-logic code, the sub-logic code comprising computer-executable code for execution by the trusted program;
receiving, by the client device, a response to the request, the response comprising result data and a digital signature, the result data being generated by processing of the one or more request parameters using the sub-logic code within the TEE, and the digital signature being generated using a private code key of the sub-logic code; and
verifying, by the client device, the result data using the digital signature and a public code key of the sub-logic code.

### Claim 26 (depends on 25)

The method of claim 25, further comprising:
transmitting, by the client device, a registration request to register the sub-logic code with the trusted program within the TEE, the registration request comprising the identifier and the sub-logic code; and
receiving, by the client device, a registration result from the trusted program, the registration result comprising the public code key of the sub-logic code.

### Claim 27 (depends on 26)

The method of claim 26, further comprising:
verifying the registration result using a digital signature of the trusted program and a public key of the trusted program, the digital signature of the trusted program being generated using a private key of the trusted program, the public key and the private key of the trusted program being generated as a key pair during an attestation of the trusted program

### Claim 28 (depends on 25)

The method of claim 25, wherein the sub-logic code is retrieved from computer-readable memory based on the identifier, and is executed within the TEE to generate the result.

### Claim 29 (depends on 25)

The method of claim 25, wherein the sub-logic code is one of a plurality of sub-logic codes stored in the node.

### Claim 30 (depends on 25)

The method of claim 25, wherein the public code key and the private code key are generated as a code key pair during registration of the sub-logic code within the TEE.

### Claim 31 (depends on 25)

The method of claim 25, wherein the request further comprises a version number indicating a version of the sub-logic code that is to be executed to provide the result data.

### Claim 32 (depends on 25)

The method of claim 25, wherein the client device comprises a client node within a blockchain network.

### Claim 33

A non-transitory, computer-readable storage medium storing one or more instructions executable by a computer system to perform operations comprising:
transmitting, by a client device, a request to a node, the node executing a trusted program within a trusted execution environment (TEE), the request comprising an identifier and one or more request parameters, the identifier identifying a sub-logic code, the sub-logic code comprising computer-executable code for execution by the trusted program;
receiving, by the client device, a response to the request, the response comprising result data and a digital signature, the result data being generated by processing of the one or more request parameters using the sub-logic code within the TEE, and the digital signature being generated using a private code key of the sub-logic code; and
verifying, by the client device, the result data using the digital signature and a public code key of the sub-logic code.

### Claim 34 (depends on 33)

The non-transitory, computer-readable storage medium of claim 33, wherein the operations further comprise:
transmitting, by the client device, a registration request to register the sub-logic code with the trusted program within the TEE, the registration request comprising the identifier and the sub-logic code; and
receiving, by the client device, a registration result from the trusted program, the registration result comprising the public code key of the sub-logic code

### Claim 35 (depends on 34)

The non-transitory, computer-readable storage medium of claim 34, wherein the operations further comprise:
verifying the registration result using a digital signature of the trusted program and a public key of the trusted program, the digital signature of the trusted program being generated using a private key of the trusted program, the public key and the private key of the trusted program being generated as a key pair during an attestation of the trusted program.

### Claim 36 (depends on 33)

The non-transitory, computer-readable storage medium of claim 33, wherein the sub-logic code is retrieved from computer-readable memory based on the identifier, and is executed within the TEE to generate the result.

### Claim 37 (depends on 33)

The non-transitory, computer-readable storage medium of claim 33, wherein the sub-logic code is one of a plurality of sub-logic codes stored in the node.

### Claim 38 (depends on 33)

The non-transitory, computer-readable storage medium of claim 33, wherein the public code key and the private code key are generated as a code key pair during registration of the sub-logic code within the TEE.

### Claim 39 (depends on 33)

The non-transitory, computer-readable storage medium of claim 33, wherein the request further comprises a version number indicating a version of the sub-logic code that is to be executed to provide the result data.

### Claim 40 (depends on 33)

The non-transitory, computer-readable storage medium of claim 33, wherein the operations are performed by a client node within a blockchain network.

### Claim 41

A computer-implemented system, comprising:
one or more computers; and
one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations comprising:
transmitting, by a client device, a request to a node, the node executing a trusted program within a trusted execution environment (TEE), the request comprising an identifier and one or more request parameters, the identifier identifying a sub-logic code, the sub-logic code comprising computer-executable code for execution by the trusted program;
receiving, by the client device, a response to the request, the response comprising result data and a digital signature, the result data being generated by processing of the one or more request parameters using the sub-logic code within the TEE, and the digital signature being generated using a private code key of the sub-logic code; and
verifying, by the client device, the result data using the digital signature and a public code key of the sub-logic code.

### Claim 42 (depends on 41)

The system of claim 41, wherein the operations further comprise:
transmitting, by the client device, a registration request to register the sub-logic code with the trusted program within the TEE, the registration request comprising the identifier and the sub-logic code; and
receiving, by the client device, a registration result from the trusted program, the registration result comprising the public code key of the sub-logic code.

### Claim 43 (depends on 42)

The system of claim 42, wherein the operations further comprise:
verifying the registration result using a digital signature of the trusted program and a public key of the trusted program, the digital signature of the trusted program being generated using a private key of the trusted program, the public key and the private key of the trusted program being generated as a key pair during an attestation of the trusted program.

### Claim 44 (depends on 41)

The system of claim 41, wherein the sub-logic code is retrieved from computer-readable memory based on the identifier, and is executed within the TEE to generate the result.
