ENUM Server NAPTR Record Selection for VoLTE Fault Recovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
VoLTE networks face challenges in maintaining communication sessions due to faults, which can lead to undesirable operational states, disrupting service quality and requiring swift transitions between circuit-switched and packet-switched networks.
Innovation Solution
A method involving dual or single databases of Name Authority Pointer (NAPTR) records, where ENUM servers select appropriate records based on network conditions to initiate communication sessions via VoLTE or PLMN networks, ensuring minimal downtime during faults and recovery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the network operates exclusively on VoLTE packet-switched architecture, then service modernization and data capability are improved, but service disruption occurs when network faults exceed tolerable levels
Solution Approach 1:
The system dynamically switches between VoLTE packet-switched mode and CSFB circuit-switched mode based on real-time network fault conditions. The fault detection mechanism triggers automatic mode transitions, allowing the network to adapt its operational state from normal packet-switched operation to fallback circuit-switched operation when faults exceed tolerable thresholds, thereby maintaining service continuity across varying network conditions
Solution Approach 2:
The system changes the operational parameter of network mode (packet-switched vs. circuit-switched) based on fault level parameters. When the fault level parameter exceeds a predefined threshold, the system transitions from VoLTE packet-switched mode to CSFB circuit-switched mode, effectively using parameter changes to resolve the contradiction between maintaining modern network architecture and ensuring service reliability under fault conditions
2Reliability
If rapid transition between network modes is implemented, then service continuity during faults is improved, but system complexity increases
Solution Approach 1:
The system performs preliminary fault detection and assessment before actual service disruption occurs. By continuously monitoring network conditions and identifying faults early, the system can proactively initiate mode transitions before service quality degrades, reducing the need for complex reactive control mechanisms and simplifying the overall fault response system
Solution Approach 2:
The system introduces a fault detection and decision-making intermediary layer between the network infrastructure and service delivery. This intermediary mechanism assesses fault conditions and determines appropriate mode transitions, isolating the complexity of fault management from both the network infrastructure and service delivery components, thereby managing system complexity while maintaining rapid response capability
3Reliability
If fault tolerance thresholds are set low, then service quality is maintained, but unnecessary network mode transitions occur
Solution Approach 1:
The system applies a threshold-based fault tolerance mechanism that allows partial degradation of network conditions before triggering mode transitions. By setting thresholds that tolerate minor faults, the system avoids excessive or unnecessary transitions while still responding appropriately to significant failures, effectively balancing service quality maintenance with transition frequency reduction
4Stability of the object's composition
If fault tolerance thresholds are set high, then network stability is maintained, but service quality degrades during faults
Solution Approach 1:
The system implements a feedback mechanism that continuously monitors service quality metrics and fault conditions. This feedback loop allows the system to assess whether current fault levels warrant mode transitions, ensuring that transitions occur only when necessary to maintain acceptable service quality. The feedback mechanism prevents both premature transitions and delayed responses, optimizing the balance between network stability and service quality
Data Source
AI summary
A system that incorporates the subject disclosure may perform, for example, operations including receiving a request from a communication device to initiate a communication session, obtaining a first name authority pointer (NAPTR) record that replaces a second NAPTR record responsive to an undesirable fault level in a voice over long term evolution (VoLTE) network, obtaining the second NAPTR record responsive to determining that there is no fault or a tolerable level of faults in the VoLTE network, and initiating the communication session according to one of the first NAPTR record or the second NAPTR record obtained by the system. The first NAPTR record can include instructions for initiating the communication session utilizing a circuit-switched communication network, and the second NAPTR record can include instructions for initiating the communication session utilizing the VoLTE network. Other embodiments are disclosed.