Multi-SIM Mobile Equipment IMS Registration via Feature Tags
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Multi-SIM capable mobile equipment (MUSIM-capable ME) experiences unnecessary interruptions in data services due to the need to move away from one Public Land Mobile Network (PLMN) to receive notifications from another, leading to resource wastage and potential missed IMS-based services.
Innovation Solution
The ME establishes separate data connections and IMS registrations with different PLMNs using distinct feature tags and private user identities, allowing it to receive notifications without interrupting ongoing services and optimizing resource usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If the ME moves away from the second PLMN to receive a paging message from the first PLMN, then the ME can receive notifications from the first PLMN, but the ongoing data service on the second PLMN is interrupted
Solution Approach 1:
The patent segments the ME's network connections by establishing separate data connections for each PLMN (first data connection for first PLMN, second data connection for second PLMN). This allows independent operation of each connection, so the ME can receive paging messages on the first PLMN without disrupting the data service on the second PLMN, resolving the contradiction between notification reception and service continuity
Solution Approach 2:
The patent introduces a feature tag as an intermediary element that identifies the access type (3GPP or non-3GPP) in IMS registration messages. This intermediary allows the network to distinguish between different access types and route paging messages appropriately, enabling the ME to receive notifications without moving away from the current PLMN, thus maintaining data service continuity
2Loss of information
If the ME moves away from the second PLMN to receive a paging message from the first PLMN, then the ME can receive notifications from the first PLMN, but system resources are wasted
Solution Approach 1:
By segmenting the data connections into separate PLMN-specific connections, the ME maintains its position in the second PLMN while still being able to receive paging messages from the first PLMN through the feature tag mechanism. This eliminates the need for physical movement between networks, thereby conserving system resources and avoiding unnecessary resource reallocation
Solution Approach 2:
The feature tag acts as an intermediary that enables the network to identify and route paging messages to the correct data connection without requiring the ME to change its registered location. This intermediary mechanism allows efficient resource utilization by avoiding the resource-intensive process of moving the ME between PLMNs
3Device complexity
If the ME uses a single data connection for both PLMNs, then the device complexity is reduced, but the ME cannot receive notifications from one PLMN without interrupting services on the other
Solution Approach 1:
The patent implements separate data connections for each PLMN (first data connection for first PLMN, second data connection for second PLMN), which increases connection management complexity but enables independent operation of each connection. This segmentation allows the ME to receive paging messages on one PLMN without interrupting data services on the other PLMN, resolving the contradiction between simplicity and reliability
Solution Approach 2:
The feature tag serves as an intermediary that provides identification and routing information for different access types within the IMS registration process. This intermediary enables the network to manage multiple PLMN connections efficiently and route paging messages to the appropriate connection without requiring complex manual intervention, thus balancing management complexity with service reliability
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A communication method, an ME and a network entity are provided. The method includes: creating a first data connection in a first PLMN; performing a first IMS registration via the first data connection with a first network entity in the first PLMN, wherein performing the first IMS registration includes: sending a first feature tag for indicating a first access type of the first IMS registration, and a private user identity of the ME; creating a second data connection in a second PLMN; performing a second IMS registration via the second data connection, wherein performing the second IMS registration includes sending a second feature tag for indicating a second access type of the second IMS registration, and the private user identity; receiving a first communication message including the second feature tag from the first network entity, wherein the first access type is different from the second access type.