Now 3122 visitors
Today:0 Yesterday:0
Total: 136065 212S 50P 5R
2026-10-21, Week 43
Member Login
TACT Journal Homepage
Call for Paper
Committee
Find My Paper
Author Homepage
Statistics & History
Welcome Message
Paper Procedure
FAQ
Paper Archives
Outstanding Papers
Program & Proceedings
Presentation Platform
Hotel & Travel Info
Photo Gallery
Scheduler Login
Seminar
Archives Login
Sponsors




















IEEE/ICACT20260257 Question.2
Questioner: abilaaniloshan@gmail.com    2026-02-09 ¿ÀÈÄ 5:43:58
IEEE/ICACT20260257 Answer.2
Answer by Auhor hhl9438@chungbuk.ac.kr   2026-02-09 ¿ÀÈÄ 5:43:58
In a real 5G deployment, how would the proposed RESTCONF-based fault detection and slice-specific recovery mechanism handle simultaneous failures affecting multiple slices, and what would be the impact on recovery latency? In our current implementation, when a fault node is detected, backup paths are activated sequentially for all affected slices. As a PoC validated with two slices, handling large-scale simultaneous failures is recognized as future work. Regarding recovery latency, we use pre-calculated backup paths to eliminate real-time path computation overhead, enabling fast individual slice recovery. Future extensions include priority-based recovery policies, parallel processing, and AI-based predictive fault management.

Select Voice