Runtime Environment Protocol Bridge for Card Computing Devices

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems for card computing devices face challenges in bridging different communication protocols, limiting the ability of applications to communicate effectively between entities using disparate protocols.

Innovation Solution

A runtime environment, such as the Java Card Runtime Environment, is configured to act as a protocol bridge, enabling the use of Application Protocol Data Unit (APDU) messages over the Host Controller Interface (HCI) communication protocol, allowing applications to communicate across different protocols by encapsulating and transmitting APDU messages within HCI messages.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If applications are configured to communicate using a specific protocol (APDU), then communication reliability within card computing devices is improved, but adaptability to communicate with external entities using different protocols (HCI) deteriorates

Engineering Contradiction:
Improvecommunication reliabilityVSAvoidprotocol adaptability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a protocol bridge as an intermediary component that translates between APDU protocol (used by card computing devices) and HCI protocol (used by external entities). This mediator enables applications to maintain their native APDU communication while gaining access to HCI-based external entities, thus resolving the contradiction between communication reliability and protocol adaptability

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If a protocol bridge is implemented to enable multi-protocol communication, then adaptability is improved, but device complexity increases

Engineering Contradiction:
Improveprotocol adaptabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The protocol bridge is designed as a universal component within the runtime environment that can handle multiple protocol translations. By consolidating protocol adaptation functionality into a single multi-functional bridge rather than implementing separate translation mechanisms for each protocol pair, the patent reduces overall system complexity while maintaining high adaptability

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

3Adaptability or versatility

If APDU messages are encapsulated within HCI messages for transmission, then interoperability between different protocols is improved, but processing overhead increases

Engineering Contradiction:
ImproveinteroperabilityVSAvoidprocessing overhead
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements message nesting by encapsulating APDU messages within HCI messages for transmission between card computing devices and external entities. This nesting approach allows the protocol bridge to maintain clear message boundaries and structure, enabling efficient extraction and processing of inner APDU messages from outer HCI messages, thus managing processing overhead systematically

Inventive Principle:
Principle #7Nested doll (Nesting)

Data Source

PatentUS9665414B2Communication protocol bridge for card computing devices
Publication Date: 2017.05.30 ORACLE DEUT B V & CO KG
  • US9665414B2 patent drawing
  • US9665414B2 patent drawing
  • US9665414B2 patent drawing

AI summary

A runtime environment executing on a card computing device may handle communication of APDU messages received by a card computing device according to the HCI communication protocol over an APDU gate. APDU messages may be encapsulated and transmitted within multiple HCI messages and the runtime environment may be configured to extract and verify the APDU messages from within the received HCI messages, according to some embodiments. The runtime environment may be configured to receive commands to open an APDU pipe, manage multiple open pipes, receive incoming HCI commands, and route the encapsulated APDU messages to an appropriate application executing within the card computing device. The runtime environment may also be configured to receive APDU messages from the application, encapsulate the APDU messages within HCI messages and send the HCI messages over the same APDU pipe.