User Registration Verification Using Dual Identifiers in 3GPP IMS
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In 3G wireless communication systems, mismatched SIP URIs can trigger unnecessary deregistration procedures, leading to incorrect identification of serving controllers and inefficient resource management.
Innovation Solution
Implement a method that uses primary and secondary identifiers to accurately verify the serving controller in user registration requests, comparing SIP URIs and Diameter client addresses to prevent incorrect deregistration, thereby ensuring that only necessary deregistration procedures are initiated.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If SIP URI comparison is performed to identify serving controllers, then serving controller identification can be achieved, but mismatched SIP URIs trigger unnecessary deregistration procedures
Solution Approach 1:
A new Diameter identifier (Origin-Host AVP) is introduced as an intermediary element to mediate between the SIP URI comparison and the deregistration decision. This additional identifier acts as a mediator that helps distinguish between genuine serving controller changes and SIP URI formatting variations, preventing incorrect deregistration while maintaining accurate serving controller identification.
Solution Approach 2:
The system changes from using only SIP URI parameters for serving controller identification to using both SIP URI parameters and Diameter protocol parameters (Origin-Host AVP). This parameter change enables more robust comparison by considering multiple identification elements, thereby reducing false positives in serving controller change detection.
2Productivity
If deregistration procedures are initiated upon SIP URI mismatch, then serving controller changes can be detected, but unnecessary deregistration events occur
Solution Approach 1:
The system performs preliminary comparison of both SIP URI and Diameter Origin-Host AVP identifiers before initiating deregistration procedures. This preliminary action filters out false positives early in the process, preventing unnecessary deregistration operations and saving processing time while maintaining efficient detection of genuine serving controller changes.
3Ease of operation
If single identifier comparison is used for serving controller verification, then the process is simple, but incorrect identification occurs due to SIP URI variations
Solution Approach 1:
The serving controller identification process is segmented into multiple independent comparison stages: first comparing SIP URI parameters, then comparing Diameter Origin-Host AVP. This segmentation allows each comparison to be performed with appropriate precision while maintaining overall process clarity. The multi-stage approach breaks down the complex verification into manageable segments that are both simple to implement and highly accurate.
Data Source
AI summary
A method of registering users in a mobile communications system, the method comprising the steps of: storing in a user information store primary and secondary identifiers identifying a first serving controller; receiving a request from a serving controller, said request identifying that serving controller using primary and secondary identifiers; comparing the primary identifier in the user information store with the primary identifier in said request and, if there is a mismatch, comparing the secondary identifier in the user information store with the secondary identifier in said request wherein, when there is a mismatch between the secondary identifiers it is determined that the serving controller identified in the request is not the first serving controller; and when there is a match between the secondary identifiers it is determined that the serving controller identified in the request is the first serving controller.