Terminal Device Route Setting for Exclusive Secure Element Activation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In communication systems, particularly in mobile payment scenarios, existing technologies face challenges in ensuring exclusive operation of a secure element (SE) while managing host card emulators (HCEs) and non-exclusive SEs, leading to difficulties in terminating the operation of non-exclusive SEs like HCEs, which hinders normal functioning of exclusive SEs.

Innovation Solution

A route setting method and terminal device that checks if a newly connected SE is exclusive, supports default routing entries, and constructs or modifies routing tables to ensure only the exclusive SE is active, thereby avoiding the use of HCEs and ensuring normal operation of the exclusive SE by setting the SE flag and managing routing entries accordingly.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a mode setting instruction is used to control SE activation/deactivation, then the exclusive SE can be activated and non-exclusive SEs deactivated, but the HCE cannot be deactivated because its ID cannot be a target of the mode setting instruction

Engineering Contradiction:
Improveexclusive SE activationVSAvoidHCE deactivation
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent introduces a routing table as an intermediary mechanism between the CPU and NFCC. Instead of directly controlling HCE activation through mode setting instructions, the system uses routing table configuration to redirect NFC communications away from HCE, effectively deactivating it without requiring direct HCE control instructions.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the SE control mechanism into two independent parts: (1) mode setting instructions for direct SE activation/deactivation, and (2) routing table configuration for communication path management. This segmentation allows HCE deactivation to be achieved through routing table manipulation rather than requiring direct mode setting instruction support for HCE.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If the terminal allows multiple SEs to operate, then versatility is improved, but the exclusive SE requirement cannot be ensured when a new exclusive SE is connected

Engineering Contradiction:
Improvemultiple SE operationVSAvoidexclusive SE requirement
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements dynamic routing table configuration that automatically adapts when new SEs are detected. The system continuously monitors SE connections and dynamically adjusts routing entries to ensure that when an exclusive SE is connected, the routing table is reconfigured to route all NFC communications exclusively to that SE, thereby maintaining exclusive SE requirements while supporting multiple SE operations.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent establishes a feedback mechanism where the detection of a newly connected exclusive SE triggers automatic routing table reconfiguration. The system detects the exclusive SE connection status and provides feedback to the routing management module, which then adjusts the routing table accordingly to ensure only the exclusive SE receives NFC communications.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10142232B2Route setting method and terminal device
Publication Date: 2018.11.27 HUAWEI TECH CO LTD
  • US10142232B2 patent drawing
  • US10142232B2 patent drawing
  • US10142232B2 patent drawing

AI summary

A route setting method and a terminal device are provided, which relate to the communications field and can avoid use of a host card emulator. The method includes checking whether a newly connected secure element (SE) is an exclusive SE; if the newly connected SE is an exclusive SE, checking whether setting a default routing entry is supported; and if it is detected that setting a default routing entry is not supported, constructing a routing table that includes only a routing entry corresponding to the exclusive SE, and if setting a default routing entry is supported, setting the newly connected SE as a default routing target SE, where the constructed routing table may include or not include the routing entry corresponding to the exclusive SE.