Secure Element Response Buffering for Low-Packet Remote Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing communication methods between secure elements and remote entities, particularly in IoT devices, suffer from low performance due to excessive packet transmission and high network bandwidth and power consumption, especially when using chunked transfer encoding with indefinite length coding.

Innovation Solution

A method involving a secure element that sequentially generates and stores responses to remote management commands in a transmission buffer before collectively transmitting them in a single packet, reducing the number of packets and transmission time, and optimizing network bandwidth and power consumption.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If chunked transfer encoding with indefinite length coding is used for RAM/RFM over HTTPS, then the size of random-access memory required is reduced, but the performance deteriorates due to excessive packet transmission

Engineering Contradiction:
Improvesize of random-access memoryVSAvoidperformance
Core Design Contradiction:
Quantity of substanceVSProductivity

Solution Approach 1:

The patent applies preliminary action by receiving the entire command script before executing it. The secure element waits for the complete command script to be received, then processes all commands and collects all responses in memory before transmitting them collectively. This eliminates the need for incremental response transmission and reduces the number of packets sent, thereby improving performance while maintaining low memory requirements during the reception phase.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If responses are sent in separate packets for each command received, then the communication follows the standard protocol, but the number of packets transmitted increases excessively

Engineering Contradiction:
Improveprotocol complianceVSAvoidnumber of packets
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent applies merging by combining multiple individual responses into a single collective response packet. Instead of sending one response packet for each command executed, the secure element executes all commands from the received script, collects all responses in memory, and transmits them together in one packet. This dramatically reduces the number of packets transmitted while maintaining protocol compliance through the use of appropriate delimiters and formatting.

Inventive Principle:
Principle #5Merging (Combining)

3Loss of information

If excessive packets are sent between secure element and server, then communication completeness is ensured, but network bandwidth consumption and power consumption increase

Engineering Contradiction:
Improvecommunication completenessVSAvoidpower consumption
Core Design Contradiction:
Loss of informationVSUse of energy by moving object

Solution Approach 1:

The patent reduces power consumption and network bandwidth usage by merging multiple response transmissions into a single collective transmission. By accumulating all responses in memory and sending them together in one packet, the number of radio interface activations is minimized, directly reducing power consumption. The communication remains complete as all responses are transmitted together with proper delimiters ensuring no information loss.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS20260046625A1Method for communication between secure element and remote entity, secure element, and system
Publication Date: 2026.02.12 GIESECKE DEVRIENT MOBILE SECURITY GERMANY GMBH
  • US20260046625A1 patent drawing
  • US20260046625A1 patent drawing
  • US20260046625A1 patent drawing

AI summary

A method for communication between a secure element and a remote entity involves the secure element receiving a request to establish a secure channel session with the remote entity; establishing that secure channel session; receiving a command script from the secure element that includes a series of remote management commands; sequentially generating responses by the secure element that correspond to each remote management command; sequentially storing these responses in a transmission buffer within the secure element; and collectively transmitting the stored responses to the remote entity via the secure channel session.