You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Communicate within a 5G VN group (UPF local switching)
3. OAI UPF Feature List
Based on document 3GPP TS 23.501 V16.0.0 §6.2.3.
Legend
Symbol
Status
Description
✔️
Fully Implemented
Feature is complete, tested, and production-ready
🔶
Partially Implemented
Feature is under active development or has limited functionality
❌
Not Implemented
Feature is not currently implemented
Core UPF Functions
ID
Classification
Status
Comments
1
Anchor point for Intra-/Inter-RAT mobility (when applicable)
❌
Supports session continuity during handover
2
Allocation of UE IP address/prefix (if supported) in response to
✔️
Not implemented (SMF allocates UE IP)
SMF request
3
External PDU Session Point of Interconnect to Data Network
✔️
N6 interface to DN implemented
4
Packet routing & forwarding:
1. Support of Uplink classifier to route traffic flows to an
✔️
eBPF-based uplink classification
instance of a data network
2. Support of Branching point to support multi-homed PDU
❌
Not implemented
Session
5
Packet inspection:
1. Application detection based on service data flow template
✔️
SDF filter matching in eBPF
2. The optional PFDs received from the SMF in addition
🔶
Basic PFD support
6
User Plane part of policy rule enforcement:
1. Gating
✔️
Gate status via FAR actions
2. Redirection
✔️
3. Traffic steering
✔️
FAR-based forwarding (FORW, DROP, BUFF)
7
Lawful intercept (UP collection)
❌
Not implemented
8
Traffic usage reporting
🔶
URR support present, reporting limited
9
QoS handling for user plane:
1. UL/DL rate enforcement
✔️
TC-BPF HTB rate limiting
2. Reflective QoS marking in DL
❌
Not implemented
10
Uplink Traffic verification (SDF to QoS flow mapping)
❌
Not implemented (missing N9 implementation)
11
Transport level packet marking in uplink and downlink
❌
DSCP marking, QFI handling
12
Downlink packet buffering and downlink data notification
❌
Basic buffering support, DDN limited
triggering
13
Sending and forwarding "end marker" to source NG-RAN node
❌
Not implemented
14
ARP requests/IPv6 Neighbour Solicitation handling based on
✔️
ARP resolution for N3/N6 interfaces
local cache for Ethernet PDUs
15
Packet duplication in downlink direction
✔️
Not implemented
16
Packet elimination in uplink direction in GTP-U layer
❌
Not implemented
17
NW-TT (Network-Terminate) functionality
❌
Not implemented
18
High latency communication (TS 23.501 §5.31.8)
❌
Not implemented
19
ATSSS Steering functionality to steer the MA PDU Session traffic
❌
Not implemented
(TS 23.501 §5.32.6)
20
Inter PLMN UP Security (IPUPS) functionality
❌
Not implemented
(TS 23.501 §5.8.2.14)
21
Exposure of network information (QoS monitoring information)
❌
Not implemented
(TS 23.548 §6.4)
NOTE: Not all of the UPF functionalities are required to be supported in an instance of user plane function of a Network Slice.
**NB: Excluded Features from Coverage**
The following features are **excluded from implementation coverage** as they are non-applicable to standalone 5G UPF deployments:
**Regulatory/Legal Requirements:**- Lawful intercept (ID 7) - Requires legal authorization and dedicated LI infrastructure
**Multi-UPF Architecture Dependencies:**- Anchor point for mobility (ID 1) - Requires N9 interface and I-UPF/PSA-UPF architecture
- Uplink Traffic verification (ID 10) - Requires N9 interface between UPFs
- Inter-UPF mobility (ID 51) - Requires multi-UPF deployment with N9
**Advanced/Niche Use Cases:**- Packet duplication/elimination (IDs 15, 16) - URLLC redundancy features
- NW-TT functionality (ID 17) - Network termination, specific scenarios
- High latency communication (ID 18) - IoT/CIoT-specific feature
- ATSSS Steering (ID 19) - Multi-access feature requiring non-3GPP access
- Inter PLMN UP Security (ID 20) - Roaming-specific security
- QoS monitoring exposure (ID 21) - Requires NEF and network exposure architecture
**Legacy Interworking:**- 4G/5G Interworking (ID 52) - Requires 4G EPC components
**Deployment-Specific:**- N2 Handover support (ID 50) - Requires specific RAN deployment scenarios
**Total Excluded:** 12 features (IDs: 1, 7, 10, 15, 16, 17, 18, 19, 20, 21, 50, 51, 52)
These features are correctly out-of-scope for:
- Standalone 5G deployments (SA mode)
- Single-operator networks
- Single-UPF architectures
- Mobile broadband (eMBB) use cases
N4 (PFCP) Protocol Support
ID
Classification
Status
Comments
14
PFCP Association Setup/Release
✔️
Full association management
15
PFCP Heartbeat
✔️
Heartbeat mechanism implemented
16
PFCP Session Establishment
✔️
Create sessions with PDR/FAR/QER/URR
17
PFCP Session Modification
✔️
Modify existing sessions
18
PFCP Session Deletion
✔️
Clean teardown of sessions
19
PFCP Session Report:
1. Usage Reports
🔶
Basic support
2. Event Reports
🔶
Limited event reporting
20
PFCP Node Related messages (Node Report Request/Response)