Application Function Node User Plane Path Configuration Delay Handling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The current 5G system architecture does not adequately address delays in configuring or changing user plane paths for PDU Sessions, which can lead to service interruptions during application context relocation, especially when delays occur in the core network.

Innovation Solution

An AF node is configured to send messages regarding user plane path configuration events and, if no response is received within a predetermined time, it sends a failure message, allowing the AF to manage delays and maintain service continuity by potentially reverting to previous configurations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the core network configures or changes user plane paths for PDU Sessions, then routing control and service management are improved, but delays occur causing service interruptions during application context relocation

Engineering Contradiction:
Improveservice continuityVSAvoidconfiguration delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The AF node sends a first message to the core network regarding user plane path configuration events before the actual configuration occurs. This preliminary notification allows the AF to prepare for potential delays and initiate contingency plans, such as maintaining previous configurations or activating backup paths, thereby reducing service interruption time while preserving routing control benefits

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The AF node monitors for a second message from the core network confirming the user plane path configuration. If no response is received within a predetermined time period, the AF sends a third message indicating failure and can revert to previous configurations. This feedback mechanism ensures service continuity by detecting delays and triggering recovery actions, resolving the contradiction between maintaining routing control and preventing service interruptions

Inventive Principle:
Principle #23Feedback

2Manufacturing precision

If the AF waits for confirmation from the core network before proceeding, then routing accuracy is improved, but service continuity deteriorates due to delays

Engineering Contradiction:
Improverouting configuration accuracyVSAvoidservice continuity
Core Design Contradiction:
Manufacturing precisionVSReliability

Solution Approach 1:

The AF sends a preliminary message to the core network about user plane path configuration events before the configuration is actually applied. This allows the AF to prepare contingency measures in advance, such as maintaining existing routing configurations or activating backup paths, thereby ensuring service continuity while still allowing the core network to perform accurate routing configuration when ready

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The AF node establishes a predetermined time window for expecting confirmation from the core network. If the confirmation arrives within this window, normal routing configuration proceeds with full accuracy. If the window expires without confirmation, the AF has already prepared fallback configurations to prevent service interruption, thus cushioning against the potential harm of delays while maintaining routing precision when conditions allow

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

Data Source

PatentUS20240276567A1Application function node, user equipment, and methods therefor
Publication Date: 2024.08.15 NEC CORP
  • US20240276567A1 patent drawing
  • US20240276567A1 patent drawing
  • US20240276567A1 patent drawing

AI summary

An Application Function (AF) (5) sends to a core network (3) a first message regarding an event related to a configuration of a user plane path for a PDU Session. If the AF (5) receives a second message based on an occurrence of the event from the core network (3) before a first predetermined period of time expires after transmitting the first message, the AF (5) sends a positive response to the second message to the core network (3). Otherwise, the AF (5) sends a third message to the core network (3) indicating a failure of a process in the AF (5) corresponding to the event. This allows, for example, the application function or the UE, or both, to deal with delays incurred in a procedure in the core network to change the user plane path in terms of runtime coordination between the core network and the application function.