Application Server Dialog Status Notification for IMS
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In telecommunication networks, especially in IP Multimedia Subsystems, the sharing of public user identities among multiple private user identities leads to unnecessary idle load and resource reservation, even when only one device is active, making it difficult to optimize network resources and causing issues with Application Server failures and re-allocation.
Innovation Solution
A method where an Application Server receives a register message indicating a User Equipment's capability to receive standalone dialog status notifications, retrieves and sends these notifications to the first User Equipment without creating finite state machines, reducing idle signaling and network load, and ensuring resilience to Application Server failures.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If subscription-based dialog status notifications are implemented, then users can receive comprehensive dialog status information, but unnecessary idle load and resource reservation occur when only one device is active
Solution Approach 1:
The system dynamically adjusts the notification mechanism based on the number of active devices. When only one device is active, standalone notifications are used without creating subscription state machines. When multiple devices are active, the system transitions to subscription-based notifications. This dynamic adaptation resolves the contradiction by activating comprehensive notifications only when necessary.
Solution Approach 2:
The system changes the operational parameters of the notification mechanism based on device count. The parameter being changed is whether to create subscription state machines or use standalone notifications. This parameter change allows the system to maintain reliability when needed while avoiding idle load when not needed.
2Loss of information
If subscription state machines are created for each subscribing device, then dialog status information can be tracked, but processing resources and memory are reserved even when no traffic is running
Solution Approach 1:
The notification mechanism is segmented into two independent paths: standalone notifications for single-device scenarios and subscription-based notifications for multi-device scenarios. This segmentation allows the system to use only the necessary resources for each scenario, avoiding the overhead of maintaining subscription state machines when they are not needed.
Solution Approach 2:
The subscription state machine creation is extracted as an optional component that is only instantiated when multiple devices are active. In single-device scenarios, this complex mechanism is completely removed, leaving only the simpler standalone notification path. This extraction eliminates unnecessary resource reservation while preserving information tracking capabilities when needed.
3Productivity
If Application Servers are reallocated in cloud based environments, then resource optimization is achieved, but network signalling is generated down to all affected UEs
Solution Approach 1:
The system uses an intermediary mechanism where the Application Server can transfer subscription state to a new server without notifying all User Equipments. This intermediary transfer mechanism allows resource optimization through server reallocation while avoiding the generation of network signalling to all affected UEs, thus resolving the contradiction between productivity and energy loss.
4Reliability
If an Application Server fails, then service continuity is disrupted, but subscription identity is silently lost until subscription is refreshed
Solution Approach 1:
The system implements beforehand cushioning by creating standby Application Servers that can immediately take over when a primary server fails. The subscription state is pre-transferred to these standby servers, ensuring service continuity and preventing loss of subscription identity without requiring UE-initiated refreshes. This resolves the contradiction by maintaining reliability while preserving information.
Data Source
AI summary
A method of notifying a first User Equipment, UE, of a subscriber in a telecommunication network on a dialog status of a second UE of said same subscriber, said method comprising the steps of receiving, by an Application Server, AS, in said telecommunication network a register message for indicating to said AS that said first UE has registered in said telecommunication network, wherein said register message comprises an indication that said first UE is capable to receive Dialog Event notifications regarding dialog status events of UEs associated with said same subscriber, retrieving, by said AS, and triggered by said receiving of said register message, said dialog status of said second UE of said same subscriber, and sending, by said AS, to said first UE, a notify message for notifying said first UE on said retrieved dialog status of said second UE.