UE Capability Exchange Using Equipment ID for Shared IMPU
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In the context of 3G mobile communication networks, the existing capability exchange methods for CSI phase 1 services fail to accurately identify the UE corresponding to shared IP multimedia public user identities (IMPU) and do not effectively handle changes in user terminals, leading to unreliable capability information and inefficient service request routing.
Innovation Solution
Incorporating equipment identity (ID) into the capability exchange process, where UEs send their equipment ID and capability information, allowing for correlation and storage, enabling precise identification and routing of service requests to the correct UE, even when multiple UEs share the same IMPU or when the user changes terminals.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If capability exchange is implemented without equipment ID for shared IMPU, then service setup is simplified, but accurate identification of specific UE is lost
Solution Approach 1:
The patent segments the identification process by introducing equipment ID as a separate identifier distinct from IMPU. While IMPU identifies the service subscription, equipment ID specifically identifies the physical device, allowing precise UE identification even when multiple devices share the same IMPU.
Solution Approach 2:
The equipment ID acts as an intermediary identifier between the service layer (IMPU) and the device layer. It mediates the identification process by providing a unique device-specific identifier that complements the service-oriented IMPU, enabling accurate routing and capability matching.
2Measurement precision
If equipment ID is incorporated into capability exchange, then accurate UE identification is achieved, but signaling complexity increases
Solution Approach 1:
The patent merges equipment ID exchange with existing capability exchange procedures. By combining these functions into a single signaling interaction, the patent avoids creating separate identification procedures, thereby minimizing additional signaling overhead while achieving accurate UE identification.
Solution Approach 2:
The equipment ID is designed to serve multiple functions: identifying the specific UE, enabling accurate capability matching, supporting routing decisions, and facilitating terminal change detection. This multi-functionality reduces the need for separate mechanisms, offsetting the signaling complexity with operational efficiency.
3Productivity
If capability information is cached without equipment ID correlation, then service setup speed is improved, but reliability of capability information decreases
Solution Approach 1:
The patent performs preliminary capability exchange and caching equipped with equipment ID correlation. By pre-exchanging capabilities and storing them with associated equipment IDs, the system prepares identification data in advance, enabling both fast service setup and reliable capability information through equipment ID-based validation.
Solution Approach 2:
The equipment ID enables feedback mechanisms where UEs can verify whether cached capability information corresponds to their current device. When a UE receives service requests, it can use its equipment ID to verify the authenticity and relevance of cached capability information, ensuring reliability while maintaining fast service setup.
4Reliability
If equipment ID is used for route control, then service requests are routed to correct UE, but network signaling overhead increases
Solution Approach 1:
The patent applies equipment ID-based routing selectively at critical network nodes where precise UE identification is necessary for service request routing. Rather than uniformly applying complex routing throughout the entire network, the equipment ID mechanism is implemented locally at routing decision points, minimizing overall signaling overhead while ensuring accurate delivery.
Data Source
AI summary
The present invention discloses a method of implementing UE capability exchange and a method of route control for parallel IMS and CS services in communication system, so as to distinguish among multiple UEs sharing a same IMPU during capability exchange and route control. Said method comprises: each of UEs involved in capability exchange sending its capability information to the opposite party respectively; the opposite party storing these information as well as the correlation between the information and the service ID; The UE including equipment ID of the opposite UE in an initiated service request; service control function entity in the network utilizing the equipment ID to query the established correlation among equipment ID, service ID, and address of the UE, so as to determine the address of the destination UE and route the service request to the destination UE. Said equipment ID identifies effectively a UE in the network.