PFCP Dual Timeout Control for Resilient Packet Forwarding
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current PFCP protocols lack distinct timeouts for user plane resiliency and control plane/user plane restart/reboot scenarios, leading to inefficient resource consumption and network disruptions.
Innovation Solution
Implementing dual timeouts - a resiliency timeout and an association timeout - to manage user plane resiliency and control plane/user plane restarts/reboots, allowing for controlled state transitions based on heartbeat restoration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a single timeout is used for both user plane resiliency and control plane/user plane restart scenarios, then the protocol implementation is simple, but network disruptions are excessive and resource consumption is inefficient
Solution Approach 1:
The single timeout mechanism is segmented into two distinct timeouts: resiliency timeout for user plane resiliency scenarios and association timeout for control plane/user plane restart scenarios. This segmentation allows each timeout to be optimized for its specific use case, preventing unnecessary network disruptions and resource consumption while maintaining manageable complexity through clear functional separation.
2Device complexity
If a single timeout is used for both user plane resiliency and control plane/user plane restart scenarios, then the protocol implementation is simple, but network disruptions are excessive and resource consumption is inefficient
Solution Approach 1:
The timeout mechanism is segmented into resiliency timeout and association timeout, enabling differentiated handling of network scenarios. This improves network operations efficiency by preventing unnecessary disruptions during resiliency events while allowing proper restart procedures, thereby optimizing overall productivity without significantly increasing implementation complexity.
Solution Approach 2:
The system dynamically selects which timeout to apply based on the detected scenario type. When a resiliency scenario is detected, the resiliency timeout is applied; when a restart scenario is detected, the association timeout is applied. This dynamic adaptation optimizes network operations efficiency for each specific scenario while maintaining a unified protocol implementation.
3Reliability
If timeout is extended to handle restart scenarios, then restart handling is improved, but user plane resiliency response is delayed causing unnecessary disruptions
Solution Approach 1:
The timeout mechanism is segmented into two distinct timers with different durations and purposes. The resiliency timeout is set to a shorter duration to quickly detect and respond to user plane resiliency scenarios, minimizing disruption time. The association timeout is set to a longer duration to properly handle control plane/user plane restart scenarios without premature timeout. This segmentation resolves the contradiction by providing appropriate time scales for each scenario.
Solution Approach 2:
The timeout parameter is changed based on the detected scenario type. For resiliency scenarios, a shorter timeout value is applied to enable rapid response. For restart scenarios, a longer timeout value is applied to allow sufficient time for recovery. This parameter adaptation resolves the contradiction between fast resiliency response and reliable restart handling.
4Productivity
If timeout is reduced for faster resiliency detection, then resiliency response is improved, but restart procedures are prematurely terminated causing reliability issues
Solution Approach 1:
The timeout mechanism is segmented into resiliency timeout and association timeout with different duration settings. The resiliency timeout is reduced to enable faster resiliency detection and response, improving productivity. The association timeout is extended to ensure restart procedures are not prematurely terminated, maintaining reliability. This segmentation allows both contradictory requirements to be satisfied simultaneously for their respective scenarios.
Data Source
AI summary
A network device, with a user plane and a control plane, may establish a resiliency timeout and an association timeout for a packet forwarding control protocol utilized by the network device, and may detect expiration of the resiliency timeout. The network device may signal control plane or user plane applications based on the expiration of the resiliency timeout, and may cause the user plane to trigger a connected-pause state transition based on the expiration of the resiliency timeout.