Conditional Voice Fallback Logic for 5G Simultaneous Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current wireless communication systems face challenges in providing simultaneous voice and data services, particularly in scenarios where PDU or PDN sessions are not successfully established, leading to call drops and poor user experiences, especially in 5G NR and LTE networks.
Innovation Solution
A terminal with a processor and proximity sensor is configured to initiate or receive voice calls over NR or LTE networks, falling back to VoLTE or VoNR protocols based on conditions such as proximity sensor activation, screen lock status, and data requirements, to ensure seamless voice and data services.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the UE falls back to LTE network for voice calls when Internet PDU session establishment fails, then voice call reliability is improved, but call drop risk increases in certain scenarios
Solution Approach 1:
The patent changes the timer expiry parameter from triggering automatic fallback to triggering conditional fallback. The processor evaluates multiple parameters including proximity sensor status, screen lock state, active applications, and favorite contact status before deciding whether to fallback, rather than unconditionally falling back when the timer expires.
Solution Approach 2:
The patent introduces dynamic decision-making where the fallback behavior adapts based on real-time device state and call context. The system dynamically adjusts fallback execution by evaluating current sensor readings, screen status, running applications, and call importance metrics at the moment of timer expiry.
2Stability of the object's composition
If the UE maintains strict fallback conditions to avoid unnecessary switches, then network stability is improved, but voice service continuity deteriorates when PDU sessions fail
Solution Approach 1:
The patent prepares multiple fallback pathways in advance: conditional fallback to LTE for normal scenarios, and emergency fallback mechanisms for critical calls. By pre-configuring these alternative routes and the decision logic to select them, the system cushions against potential voice service interruptions when PDU session establishment fails.
3Loss of energy
If the UE evaluates multiple conditions before fallback, then unnecessary network switches are reduced, but decision complexity and processing time increase
Solution Approach 1:
The patent segments the fallback decision process into distinct evaluation stages: first checking proximity sensor and screen lock status, then evaluating active applications, and finally assessing call importance. This segmented approach organizes the complex multi-parameter evaluation into manageable, sequential steps that reduce processing overhead.
4Ease of operation
If the UE implements conditional fallback based on sensor and application state, then user experience is improved, but device processing load increases
Solution Approach 1:
The patent performs preliminary evaluation of sensor status, screen state, and active applications before the timer expires and fallback is needed. By having this information readily available from ongoing device operations, the system avoids intensive real-time analysis at the critical decision moment, reducing processing load while maintaining enhanced user experience.
Data Source
AI summary
Optimizations for simultaneous voice and data experiences in cellular networks include methods of handling voice call fallback, e.g.: (1) on VoNR when an IMS PDU session is established but an Internet PDU session is not yet established; (2) on VoNR when IMS and Internet PDU sessions are established in different network slices; (3) on VoNR when an IMS PDU session is established but a rejection is received for an Internet PDU session; (4) on an LTE network after an EPSFB procedure when an IMS bearer is not present; (5) on an LTE network after an EPSFB procedure when an IMS bearer is present but an Internet bearer is not; (6) on VoNR when a network does not support simultaneous voice and data; (7) when a VoNR-capable UE is camped to SA on a VPLMN; and (8) when a non-VoNR-capable UE is camped to SA on a network that supports VoNR.