IMS Registration Status Notification Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current IMS systems fail to provide specific notifications of service registration failures, leading to unnecessary termination of all applications and lack of information on failure reasons, causing inefficiencies in re-registration attempts.
Innovation Solution
A system and method that allows mobile device applications to receive detailed notifications of registration status changes on a per-application-service basis, including reasons for failures, using XML documents and extended Subscription to Registration Information defined by IETF, enabling targeted remedial actions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If generic notification is used to alert registration failures, then the notification system is simple, but the application cannot identify which specific service registration failed and cannot take targeted remedial actions
Solution Approach 1:
The patent segments the generic registration failure notification into specific per-service notifications. Each notification now includes the service identifier (icsi-ref) and registration outcome, allowing applications to identify which specific service registration succeeded or failed. This segmentation transforms a single undifferentiated notification into multiple differentiated notifications, each containing targeted information about a specific service registration event.
Solution Approach 2:
The patent implements feedback by providing detailed registration status information back to the application. The notification includes not only the registration outcome (success or failure) but also the specific service identifier and, in case of failure, the reason code. This enriched feedback loop enables the application to understand the registration status of each service and take appropriate remedial actions.
2Reliability
If all applications are terminated when registration fails, then the system maintains consistency, but functional applications are unnecessarily stopped causing loss of service
Solution Approach 1:
The patent enables selective termination by segmenting the application termination logic based on service-specific registration outcomes. Instead of a blanket termination approach, the system now allows applications to identify which specific service registrations failed and terminate only those affected services while keeping functional services running. This is achieved through per-service notification that includes the icsi-ref identifier.
Solution Approach 2:
The patent applies local quality by allowing different termination behaviors for different services within the same application. The application can now assess the registration status of each service individually and apply termination only to the specific service that failed registration, rather than applying a uniform termination policy to all services. This localized response preserves service availability for unaffected services.
3Ease of operation
If no failure reason is provided, then the notification is simple, but the application cannot assess what additional steps to take for re-registration
Solution Approach 1:
The patent enhances feedback by including the failure reason (cause code) in the registration status notification. When a service registration fails, the notification now contains the specific reason for failure, enabling the application to assess what additional steps might be needed for successful re-registration. This feedback mechanism provides actionable information to guide remedial actions.
Data Source
Figure 1A
Figure 1B
Figure 2A
AI summary
A system and method that allows mobile device applications to receive changes in registration status from application services that are accessed via an Internet Protocol Multimedia Subsystem (IMS). Applications on a mobile device subscribe to receive notifications of changes in registration status for requested services. When a change to the registration status of a service occurs, a notification message is transmitted to the application on the mobile device. Notifications of changes in status are thereby received by each application on a per-application- service basis. In some embodiments, when a request to register with an application service fails, the corresponding notification message includes a reason for the failure. In some embodiments, notification messages are originated by a registration manager that operates in the IMS and transmitted to an IMS client operating on a mobile device. In some embodiments, notification messages are originated by each application service and transmitted directly to subscribed applications.