Secured Token Agent HTTP Message Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for managing applications embedded in smart cards via the HTTP channel are limited, as existing Admin Agent applications are not easily modifiable and cannot handle specific Content-type values beyond OMA-SCWS, RAM over HTTP, and RFM over HTTP, restricting the reuse of 'OTA over HTTP' protocols for purposes other than SCWS and Card content administration.
Innovation Solution
An enhanced agent within the secured electronic token registers applications by associating a reference with a message header element value, allowing it to forward only the message body to the appropriate application, enabling communication with distant servers using standard HTTP mechanisms and managing data formatting independently of the application's interface constraints.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the Admin Agent application is modified to handle multiple Content-type values, then the adaptability of the HTTP channel increases, but the device complexity and difficulty of modification increase since the Admin Agent is part of the operating system
Solution Approach 1:
The patent segments the Admin Agent functionality into two independent components: a fixed operating system-level Admin Agent that handles only standard Content-types (OMA-SCWS, RAM over HTTP, RFM over HTTP), and a separate downloadable application that handles custom Content-types. This segmentation allows the OS Admin Agent to remain unchanged while enabling HTTP channel adaptability through the downloadable application.
Solution Approach 2:
The patent introduces a downloadable application as an intermediary layer between the fixed Admin Agent and the embedded applications. This intermediary receives HTTP messages with custom Content-types, routes them to appropriate applications, and forwards responses back to the server, thereby enabling adaptability without modifying the core Admin Agent.
2Adaptability or versatility
If a new HTTP routing mechanism is implemented to support multiple applications, then the versatility of application access increases, but the memory consumption increases due to additional routing logic and data structures
Solution Approach 1:
The downloadable application serves multiple functions: it acts as an HTTP message router, a Content-type parser, an application launcher, and a response forwarder. By consolidating these functions into a single lightweight component rather than implementing separate routing logic throughout the system, memory consumption is minimized while maintaining high versatility in application access.
3Adaptability or versatility
If the Admin Agent is enhanced to support custom Content-types, then the reuse of OTA over HTTP protocol increases, but the ease of manufacture and deployment decreases due to OS modification requirements
Solution Approach 1:
The patent implements preliminary action by pre-configuring the downloadable application with all necessary routing logic and Content-type handling capabilities before deployment. The application is prepared in advance as a standalone package that can be downloaded and installed without any OS modification, thereby enabling protocol reuse while maintaining ease of deployment.
Solution Approach 2:
The patent treats the downloadable application as a disposable, replaceable component rather than a permanent OS modification. This allows the application to be updated, replaced, or removed independently of the operating system, making the system more flexible and easier to manufacture and deploy without permanent changes to the core system.
Data Source
Figure 1
Figure 2~4
AI summary
The invention is a method of managing an application embedded in a secured electronic token. The token is intended to receive a message from a server machine. The message has a header and a body. The token comprises an agent able to manage the message. The method comprises the steps of : a) registering the application in the agent by associating a reference of the application with a value of an element of the message header; b) when the message is received from the server machine, forwarding part of the message to the application if the message header contains an element having the value associated to the reference of the application.