Gateway Node Policy Enforcement via User Plane API Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing 3GPP exposure framework is complex and inefficient in handling requests for rules and policies from content providers due to the need for mapping external IP addresses to real UE identities, leading to increased signaling and internal API exposure.
Innovation Solution
A mechanism is introduced using a User Plane (UP) based Application Programming Interface (API) for a gateway node to handle application data traffic, allowing content providers to request policies directly, bypassing the need for mapping and interactions with the 5G core network control plane functions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the existing 3GPP exposure framework is used to handle requests for rules and policies from content providers, then the framework provides a standardized interface for policy management, but the complexity increases and efficiency decreases due to the need for mapping external IP addresses to real UE identities
Solution Approach 1:
The patent extracts the IP address mapping functionality from the core network control plane and relocates it to the user plane gateway node. This separation allows the gateway to handle mapping locally using cached information, eliminating the need for complex internal API exposures and reducing overall framework complexity while improving handling efficiency
Solution Approach 2:
The gateway node acts as an intermediary between content providers and the core network. It receives policy requests from content providers, performs local IP address to UE identity mapping using cached data, and enforces policies without requiring direct interaction with control plane functions, thereby simplifying the framework architecture
2Productivity
If the existing 3GPP exposure framework performs IP address mapping to UE identity, then the framework ensures accurate policy enforcement, but the signaling overhead increases and performance decreases
Solution Approach 1:
The gateway node performs preliminary actions by caching UE identity information and IP address mappings in advance. When policy requests arrive, the gateway can immediately perform mapping using cached data without initiating new signaling exchanges with the core network, significantly reducing processing time and signaling overhead
Solution Approach 2:
The gateway node serves itself by maintaining local caches of UE identity and IP address mapping information. It independently resolves mapping requests without external assistance from control plane functions, eliminating the time-consuming signaling rounds that would otherwise be required
Data Source
AI summary
A method performed by a gateway node for handling application data traffic of a session between a UE and an application server in a wireless communications network is provided. Upon establishing the session, the gateway node obtains from a policy node, an identity identifying one or more rules provisioned for the UE. The identity is associated with the session and with a UP based API to be used for the session. The gateway node receives through the UP based API, a message from the UE. The message comprises the identity and a flow identifier identifying the application data traffic related to the identity. The message requests the one or more rules to be enforced by the gateway node. Upon detecting application data traffic associated with the flow identifier, the gateway node enforces the one or more rules, according to the obtained identity, for the detected application data traffic between the UE and the application server.