Deferred Invocation of Communication Services in IMS
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In the 3GPP Internet protocol (IP) multimedia subsystem (IMS), the serving call session control function (S-CSCF) currently invokes all possible telephony features at the beginning of a session, leading to unnecessary messaging and resource usage, as it is unclear which features will be needed during the session.
Innovation Solution
Implementing a deferred invocation method where conditions are set for real applications to be invoked only when specific future events occur, using stub applications to check conditions and invoke real applications only when necessary, thereby reducing unnecessary messaging and resource usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If all possible telephony features are invoked at the beginning of a session, then all features are available for use during the session, but unnecessary messaging and resource usage increase
Solution Approach 1:
The system performs preliminary registration of applications with the S-CSCF before the session begins, but defers their actual invocation. The applications are pre-configured and registered in the network, ready to be activated only when their specific conditions are met during the session, thus avoiding premature invocation while ensuring readiness.
Solution Approach 2:
The system dynamically determines which applications to invoke based on real-time session conditions and events. Instead of a static upfront invocation of all applications, the system continuously monitors session progress and activates applications only when their specific triggering conditions are satisfied, optimizing resource usage based on actual needs.
2Adaptability or versatility
If all possible telephony features are invoked at the beginning of a session, then all features are available for use during the session, but device complexity and processing overhead increase
Solution Approach 1:
The system segments the application invocation process into distinct phases: registration phase (where applications are pre-registered with the S-CSCF) and invocation phase (where specific applications are activated based on session conditions). This segmentation separates the complexity of managing multiple applications from the actual session flow, reducing processing overhead during call setup.
Solution Approach 2:
The S-CSCF acts as an intermediary between the session control and the applications. It maintains a registry of available applications and selectively invokes only those needed based on session conditions, thereby simplifying the overall system architecture by centralizing the decision-making logic and reducing direct complexity at other network elements.
3Loss of energy
If conditions are set for deferred invocation of real applications, then unnecessary applications are not invoked, but additional condition checking and stub applications are required
Solution Approach 1:
The system uses stub applications as simplified copies or placeholders for the real applications during the session setup phase. These stubs contain the logic to evaluate conditions and trigger real application invocation when appropriate, allowing the system to manage application invocation complexity centrally without requiring complex logic distributed throughout the session flow.
Data Source
AI summary
In one embodiment, a network device determines one or more conditions for invoking one or more real applications to the network device for a session. This determination may be made at the initiation of the session, such as when a SIP INVITE message is received. The one or more conditions allow real applications to be invoked when a future event satisfies the condition. When it is determined that a condition is satisfied, a real application associated with the condition is then invoked. Accordingly, conditions may be set for real applications that may be tested against future events that have not yet occurred. This allows deferred invocation of real applications. Accordingly, if real applications are not needed for a session, then they are not invoked. But, when a real application is needed, it can be invoked.