Security Module OS Switching via Interface

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing security modules cannot be easily updated or replaced while operational, leading to outdated operating systems and reduced functionality, as current patching methods are complex and resource-intensive, and emergency operating systems offer limited functionality.

Innovation Solution

A method that allows seamless switching between two operating systems within a security module using an operating-system interface, enabling the primary application to access either system without modification, allowing the security module to remain operational and independent of the specific operating system version or variant.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the operating system is updated by reloading patches, then errors can be corrected and functionality extended, but the process is elaborate and causes considerable processing power losses

Engineering Contradiction:
Improveoperating system correctnessVSAvoidprocessing power loss
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies preliminary action by pre-loading the complete second operating system into the security module's memory before it is needed. This allows the operating system to be switched to immediately without time-consuming reloading or patching operations, thereby avoiding processing power losses while maintaining reliability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by creating a complete copy of the second operating system and storing it in the security module's memory. This copy can be activated instantly without modifying or reloading parts of the original system, eliminating the elaborate patching process and associated processing losses.

Inventive Principle:
Principle #26Copying

2Adaptability or versatility

If a new version of the operating system is created, then additional functions and improved performance are achieved, but the security module must be exchanged or the update is dispensed with

Engineering Contradiction:
Improveoperating system functionalityVSAvoidsecurity module replacement effort
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent applies dynamics by making the operating system configurable and switchable within the security module. The module can dynamically load and switch between different operating system versions stored in its memory, allowing functionality updates without physical replacement of the module.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent implements universality by designing the security module to support multiple operating system versions and types. The module can store and switch between a first operating system and a second operating system, providing multi-functionality that accommodates different operational requirements without requiring module exchange.

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

3Reliability

If the operating system is updated, then the security module remains operational with latest functions, but user code and data must be adapted or adjusted

Engineering Contradiction:
Improveoperating system currencyVSAvoidcode adaptation effort
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent uses an intermediary approach by introducing an operating system interface that mediates between user code and the operating system. This interface layer allows the operating system to be updated or switched while the user code remains unchanged, as all interactions go through the stable interface rather than direct OS dependencies.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent applies segmentation by separating the operating system from user code through a distinct interface layer. This segmentation allows independent updates of the operating system without affecting user code, maintaining reliability while reducing the complexity of code adaptation.

Inventive Principle:
Principle #1Segmentation

4Reliability

If an emergency operating system is implemented, then minimum functionality is ensured during errors, but many functions are not offered and user efforts to exchange the module are severe

Engineering Contradiction:
Improveminimum functionality assuranceVSAvoidoperating system functionality
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent uses parameter changes by allowing the security module to switch between different operating system configurations. Instead of being limited to a fixed emergency mode, the module can load and activate a complete second operating system with full functionality, changing the operational parameters from minimal to comprehensive based on needs.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS9390259B2Method for activating an operating system in a security module
Publication Date: 2016.07.12 GIESECKE & DEVRIENT EPAYMENTS GMBH
  • US9390259B2 patent drawing
  • US9390259B2 patent drawing
  • US9390259B2 patent drawing

AI summary

A method for activating an operating system in a security module, wherein the security module is operational either by means of a first operating system or by means of a second operating system. The method comprises the steps of: operating the security module by means of the first operating system and shifting the security module from the first operating system to the second operating system. A primary application incorporated in the security module accesses the respective operating system by means of an operating-system interface. The above concept are incorporated in a security module and employment of a security module in an end device.