Dynamic Application Logic Delivery in IMS Sessions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing IMS telephony sessions face limitations in executing application logic dynamically across user equipment, requiring pre-installation of applications and lacking mechanisms for automatic installation and execution during sessions, which restricts the development of enriched real-time communication applications.
Innovation Solution
A method for delivering and executing application program logic within IMS sessions by generating and sending executable scripts or links to remote user equipment, triggered by session events, allowing interaction with the terminal's UI and APIs, and enabling dynamic installation and execution of applications during IMS sessions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If application logic is pre-installed in user equipment before IMS sessions, then applications can execute during sessions, but device storage and complexity increase
Solution Approach 1:
The patent implements dynamic application logic delivery where application code is transmitted and executed during IMS sessions rather than being statically pre-installed. The system dynamically receives application logic from remote sources, installs it temporarily in the application runtime module, executes it during the session, and removes it afterward, making the system adaptable without permanent complexity accumulation
Solution Approach 2:
The patent segments the application delivery process into distinct phases: transmission during IMS session setup, temporary installation in the application runtime module, execution during the session, and removal after completion. This segmentation allows application capability to be provided on-demand without permanently increasing device complexity
2Extent of automation
If application logic is delivered during IMS sessions, then automatic deployment is enabled, but signaling overhead and session setup time increase
Solution Approach 1:
The patent merges the application logic transmission with the existing IMS session signaling flow. Application logic is delivered embedded within SIP messages during the natural session setup process, combining two functions (session establishment and application deployment) into a single integrated operation, thereby enabling automation without significant time penalty
Solution Approach 2:
The patent performs preliminary action by preparing and transmitting application logic during the IMS session setup phase, before the actual application execution is needed. This allows the application to be ready for immediate execution when the session begins, automating the deployment process in advance
3Adaptability or versatility
If application logic is executed in UE during IMS sessions, then enriched real-time communication is enabled, but security risks and system stability concerns increase
Solution Approach 1:
The patent implements beforehand cushioning through a controlled execution environment in the application runtime module that isolates dynamically loaded application logic from the core system. The module validates and manages application execution with proper resource constraints and error handling, cushioning the system against potential stability issues from untrusted or buggy applications
Solution Approach 2:
The application runtime module acts as an intermediary between the incoming application logic and the UE's core systems. It mediates the execution by providing a controlled interface that allows applications to function while protecting the underlying system from direct exposure to potentially harmful code, thus enabling enriched functionality while maintaining reliability
4Quantity of substance
If application logic is removed after session completion, then device storage is freed, but application execution capability is lost until next delivery
Solution Approach 1:
The system implements self-service by automatically receiving, installing, executing, and removing application logic based on session requirements. The application runtime module autonomously manages the application lifecycle without requiring manual user intervention, dynamically adapting the available execution capability to match current session needs while freeing storage when not in use
Data Source
Figure 1~2
Figure 3
Figure 4~5
AI summary
Mechanisms are disclosed for the provision and use of executable logic in user equipment during an IMS call/session. Application program logic is provided from a first User Equipment, UE, to a second UE communicating with each other. A first application in the first UE is executed to generate program logic, or a link to the program logic of a second application. The generated program logic, or link is sent to the second UE. A UE receiving a signal that includes program logic, or a link to program logic of the application, installs the program logic, or follows the link to download and install the program logic in the UE. The UE then executes the program logic to run the application.