Safety OS Migration and TEE Proxy for Secure Service Processing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Heterogeneous operating systems face challenges in meeting the information security requirements of functional safety operating systems due to the inability of functional safety operating systems to independently access trusted execution environments, leading to difficulties in ensuring data integrity and security.

Innovation Solution

Migrate a first safety operating system with high-functional safety and high-information security requirements from a non-secure world to a secure world, allowing direct invocation of local trusted applications for high-safety and high-trust services, and utilize a trusted execution environment operating system to execute encrypted requests based on trust and performance requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a functional safety operating system accesses a trusted execution environment operating system in a non-secure world, then information security requirements can be met, but data leakage and security risks increase

Engineering Contradiction:
Improveinformation securityVSAvoiddata leakage
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The system is divided into secure and non-secure worlds with clear isolation boundaries. The functional safety operating system runs in the non-secure world while the trusted execution environment operates in the secure world, preventing direct access and potential data leakage between them.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A trusted application acts as an intermediary between the functional safety operating system and the trusted execution environment. This intermediary component enables secure communication while maintaining isolation, allowing the functional safety operating system to access trusted services without direct exposure to the secure world.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Object-affected harmful factors

If a functional safety operating system is isolated from a trusted execution environment operating system, then data leakage is prevented, but information security requirements cannot be met

Engineering Contradiction:
Improvedata leakage preventionVSAvoidinformation security
Core Design Contradiction:
Object-affected harmful factorsVSReliability

Solution Approach 1:

The trusted application serves as a mediator that enables the functional safety operating system to access trusted execution environment services through secure interfaces. This intermediary maintains isolation boundaries while providing necessary security functions, resolving the contradiction between isolation and security accessibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The trusted application provides multiple security functions (encryption, authentication, key management) through a single unified interface, enabling the functional safety operating system to meet various information security requirements while remaining isolated from the trusted execution environment.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Reliability

If a first safety operating system is migrated to a secure world, then information security requirements are met, but development costs and resource occupation increase

Engineering Contradiction:
Improveinformation securityVSAvoiddevelopment costs
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Instead of migrating the entire functional safety operating system to the secure world, only the necessary trusted applications and services are segmented and placed in the secure world. This partial migration approach reduces development complexity and resource requirements while still meeting information security requirements.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The trusted application acts as an intermediary layer that provides security services without requiring full system migration. This intermediary approach allows functional safety operating systems to access trusted services with minimal changes to the original system architecture, reducing development costs.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If cryptographic operations are performed in a trusted execution environment, then information security is enhanced, but processing time and resource consumption increase

Engineering Contradiction:
Improveinformation securityVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Instead of performing all cryptographic operations within the trusted execution environment, only the essential security-critical operations are executed there. Less critical operations are performed in the non-secure world, reducing the time and resources consumed in the trusted environment while maintaining necessary security.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The trusted application serves as an intermediary that handles cryptographic operations efficiently. It provides secure cryptographic services to the functional safety operating system without requiring all operations to proceed through the full trusted execution environment, reducing processing time.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP4730706A1Business processing methods, and apparatuses
Publication Date: 2026.04.22 YINWANG INTELLIGENT TECHNOLOGIES CO LTD
  • EP4730706A1 patent drawingFigure 1
  • EP4730706A1 patent drawingFigure 2
  • EP4730706A1 patent drawingFigure 3~4

AI summary

Provided are a service processing method and apparatus, which relate to the field of security technologies, and can meet an information security requirement of a functional safety operating system, improve service processing security, and are easy to implement. According to the method, a functional safety operating system (a first safety operating system) having high functional safety and high information security requirements may be migrated to a secure world, to process a high-safety and high-trust service in the secure world. A functional safety operating system (a second safety operating system) deployed in a non-secure world may access, by using a secure TEE proxy technology, a TEEOS to execute a service, or access a local security service to execute a service.