| ID | Interface | Status | Comment |
|---|---|---|---|
| 1 | N1 | ✔️ | Communicate with UE via NAS message |
| 2 | N2 | ✔️ | Communicate with gNB via NGAP message |
| 3 | N8 | ✔️ | Interface to/from UDM (e.g., retrieve UE subscription data) |
| 4 | N11 | ✔️ | Interface to/from SMF (e.g., N1N2MessageTransfer, PDU Session Services) |
| 5 | N14 | ❌ | Interface between AMFs |
| 6 | N15 | ✔️ | Interface between AMF and PCF |
All interfaces support both HTTP/1.1 and HTTP/2
Based on document 3GPP TS 23.501 V16.14.0 §6.2.1.
| ID | Classification | Status | Comments |
|---|---|---|---|
| 1 | Termination of RAN CP interface (N2) | ✔️ | Communicate with gNB via NGAP message |
| 2 | Termination of NAS (N1) | ✔️ | Communicate with UE via NAS message |
| 3 | NAS ciphering and integrity protection | ✔️ | |
| 4 | Registration management | ✔️ | |
| 5 | Connection management | ✔️ | |
| 6 | Reachability management | ❌ | |
| 7 | Mobility Management | ✔️ | Support N2 Handover |
| 8 | Lawful intercept (for AMF events and interface to LI System) | ❌ | |
| 9 | Provide transport for SM messages between UE and SMF | ✔️ | |
| 10 | Transparent proxy for routing SM messages | ❌ | |
| 11 | Access Authentication | ✔️ | |
| 12 | Access Authorization | ✔️ | |
| 13 | Provide transport for SMS messages between UE and SMSF | ❌ | |
| 14 | Security Anchor Functionality (SEAF) | ✔️ | |
| 15 | Location Services management for regulatory services | ❌ | |
| 16 | Provide transport for Location Services messages between | ||
| UE and LMF as well as between RAN and LMF | ✔️ | ||
| 17 | EPS Bearer ID allocation for interworking with EPS | ❌ | |
| 18 | UE mobility event notification | ✔️ | |
| 19 | Support for Control Plane CIoT 5GS Optimisation | ❌ | |
| 20 | Provisioning of external parameters | ❌ | |
| 21 | Support non-3GPP access networks | ❌ |
| ID | Interface | Status | Comment |
|---|---|---|---|
| 1 | N4 | ✔️ | between SMF and UPF (PFCP) |
| 2 | N7 | ✔️ | between SMF and PCF |
| 3 | N10 | ✔️ | between SMF and UDM (Nudm_SubscriberDataManagement) |
| 4 | N11 | ✔️ | between SMF and AMF (Nsmf_PDU_Session Services, Namf_N1N2MessageTransfer) |
| 5 | N16/16a | ❌ | between SMFs |
All interfaces support both HTTP/1.1 and HTTP/2
Based on document 3GPP TS 23.501 v16.14.0 (Section 6.2.2).
| ID | Classification | Status | Comments |
|---|---|---|---|
| 1 | Session Management (Session Establishment/Modification/Release) | ✔️ | |
| 2 | UE IP address allocation & management | ✔️ | IP Address pool is controlled by SMF |
| 3 | DHCPv4 (server and client) and DHCPv6 (server and client) function | ❌ | |
| 4 | Respond to ARP requests and/or IPv6 Neighbour Solicitation requests | ❌ | |
| 5 | Selection of UPF function | ✔️ | Local configuration/UPF discovery via NRF |
| 6 | Configures traffic steering at UPF | ✔️ | Based on traffic rules from PCF |
| 7 | 5G VN group management | ❌ | |
| 8 | Termination of interfaces towards PCFs | ✔️ | Only supporting traffic rules |
| 9 | Lawful intercept | ❌ | |
| 10 | Charging data collection and support of charging interfaces | ❌ | |
| 11 | Termination of SM parts of NAS messages | ✔️ | |
| 12 | Downlink Data Notification | ✔️ | |
| 13 | Determine SSC mode of a session | ✔️ | Only support SSC mode 1 |
| 14 | Initiator of AN specific SM information, sent via AMF over N2 to AN | ✔️ | |
| 15 | Support for Control Plane CIoT 5GS Optimisation | ❌ | |
| 16 | Support of header compression | ❌ | |
| 17 | Act as I-SMF in deployments | ❌ | |
| 18 | Provisioning of external parameters | ❌ | |
| 19 | Support P-CSCF discovery for IMS services | ❌ | |
| 20 | Act as V-SMF | ❌ | |
| 21 | Support for interaction with external DN | ❌ | |
| 22 | Instructs UPF/NG-RAN to perform redundant transmission | ❌ | |
| on N3/N9 interfaces |
| ID | Interface | Status | Comment |
|---|---|---|---|
| 1 | N3 | ✔️ | Communicate with gNB over GTP-U Tunnel |
| 2 | N4 | ✔️ | Communicate with SMF via PFCP message |
| 3 | N6 | ✔️ | Communicate with DN for plain IP traffic |
| 4 | N9 | ❌ | Communicate with other UPF(s) |
| 5 | N19 | ❌ | Communicate within a 5G VN group (UPF local switching) |
Based on document 3GPP TS 23.501 V16.0.0 §6.2.3.
| 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 |
| 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 Neighbor 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
| 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) | 🔶 | On-going URR |
| ID | Classification | Status | Comments |
|---|---|---|---|
| 21 | PDR ID allocation and management | ✔️ | Unique PDR identification per session |
| 22 | Precedence-based PDR matching | ✔️ | Rules sorted by precedence (TS 29.244) |
| 23 | Packet Detection Information (PDI): | ||
| 1. Source Interface (ACCESS, CORE, CP-FUNCTION) | ✔️ | N3, N6, N4 interface detection | |
| 2. F-TEID (GTP-U tunnel identification) | ✔️ | UL/DL TEID matching | |
| 3. UE IP Address | ✔️ | IPv4 address matching in eBPF | |
| 4. SDF Filter (5-tuple: IP, port, protocol) | ✔️ | eBPF SDF filter engine | |
| 5. Application ID (based on PFD from SMF) | 🔶 | Basic PFD support | |
| 24 | Outer Header Removal (GTP-U/UDP/IP) | ✔️ | N3 uplink GTP-U decapsulation |
| ID | Classification | Status | Comments |
|---|---|---|---|
| 25 | FAR ID allocation and management | ✔️ | Per-PDR FAR association |
| 26 | Apply Action: | ||
| 1. FORW (Forward) | ✔️ | Packet forwarding to destination | |
| 2. DROP | ✔️ | Packet dropping based on policy | |
| 3. BUFF (Buffer) | 🔶 | Basic buffering support | |
| 4. NOCP (Notify Control Plane) | 🔶 | On-going URR | |
| 5. DUPL (Duplicate) | ✔️ | Packet duplication for multi-path | |
| 27 | Forwarding Parameters: | ||
| 1. Destination Interface (ACCESS, CORE, CP-FUNCTION) | ✔️ | N3, N6, N4 interface forwarding | |
| 2. Outer Header Creation (GTP-U encapsulation) | ✔️ | N6 downlink GTP-U with TEID/gNB IP | |
| 3. Network Instance (DNN/APN selection) | ✔️ | Network instance routing | |
| 4. Redirect Information | ✔️ | ||
| 5. Header Enrichment | ❌ | Not implemented |
| ID | Classification | Status | Comments |
|---|---|---|---|
| 28 | QER ID allocation and management | ✔️ | Per-QoS-Flow QER enforcement |
| 29 | QoS Flow Identifier (QFI) mapping | ✔️ | QFI marking and enforcement (TS 38.415) |
| 30 | Maximum Bit Rate (MBR) enforcement: | ||
| 1. Uplink MBR | ✔️ | TC-BPF HTB rate limiting | |
| 2. Downlink MBR | ✔️ | TC-BPF HTB rate limiting | |
| 31 | Guaranteed Bit Rate (GBR) enforcement: | ||
| 1. Uplink GBR | ✔️ | TC-BPF HTB class rate configuration | |
| 2. Downlink GBR | ✔️ | TC-BPF HTB class rate configuration | |
| 32 | Reflective QoS (RQI bit handling) | ❌ | Not implemented |
| 33 | Gate Status (OPEN/CLOSED for flow control) | ✔️ | Implemented via FAR actions |
| 34 | Packet Rate Control (PPI - Paging Policy Indicator) | ❌ | Not implemented |
| 35 | Averaging Window for rate enforcement | ✔️ | HTB burst and quantum parameters |
| ID | Classification | Status | Comments |
|---|---|---|---|
| 36 | URR ID allocation and management | ✔️ | URR parsing and storage |
| 37 | Volume measurement: | ||
| 1. Uplink bytes | 🔶 | Basic infrastructure | |
| 2. Downlink bytes | 🔶 | Basic infrastructure | |
| 3. Total bytes | 🔶 | Basic infrastructure | |
| 38 | Duration measurement | 🔶 | Basic infrastructure |
| 39 | Quota enforcement: | ||
| 1. Time quota | 🔶 | On-going implementation | |
| 2. Volume quota | 🔶 | On-going implementation | |
| 40 | Usage reporting triggers: | ||
| 1. Periodic reporting | 🔶 | On-going implementation | |
| 2. Volume threshold | 🔶 | On-going implementation | |
| 3. Time threshold | 🔶 | On-going implementation | |
| 41 | Measurement Method (volume, duration, event) | 🔶 | Basic support |
| ID | Classification | Status | Comments |
|---|---|---|---|
| 42 | eBPF/XDP packet processing: | ||
| 1. XDP Native mode (hardware offload) | ✔️ | standalone mode | |
| 2. XDP SKB mode (software fast-path) | ✔️ | docker containers mode | |
| 43 | TC-BPF QoS enforcement: | ||
| 1. Hierarchical Token Bucket (HTB) | ✔️ | Rate limiting and shaping | |
| 2. Per-QFI QoS class | ✔️ | Individual flow QoS | |
| 44 | BPF map-based lookups: | ||
| 1. Session lookup by UE IP (O(1)) | ✔️ | Fast session identification | |
| 2. PDR lookup by (PDR_ID, SEID) | ✔️ | Fast PDR matching | |
| 3. SDF filter evaluation per QFI | ✔️ | Per-flow SDF matching | |
| 4. ARP table cache (N3/N6) | ✔️ | Next-hop MAC resolution | |
| 45 | Zero-copy packet forwarding (XDP_REDIRECT) | ✔️ | Direct interface forwarding |
| 46 | Multi-threaded packet processing | ✔️ | Pin CPUs to RX Queues CP, multi-queue XDP possible |
| ID | Classification | Status | Comments |
|---|---|---|---|
| 47 | PDU Session Type support: | ||
| 1. IPv4 | ✔️ | Full IPv4 support | |
| 2. IPv6 | 🔶 | Implemented partially | |
| 3. IPv4v6 | ❌ | Not implemented | |
| 4. Ethernet | ✔️ | Ethernet PDU Session | |
| 5. Unstructured | ❌ | Not implemented | |
| 48 | GTP-U extension headers: | ||
| 1. PDU Session Container (QFI extraction) | ✔️ | QFI parsing from GTP-U header | |
| 2. PDU Type (DL PDU Session Information) | ✔️ | Extension header parsing | |
| 49 | 3GPP Reference Points: | ||
| 1. N3 interface (gNB ↔ UPF) | ✔️ | GTP-U tunnel management | |
| 2. N4 interface (SMF ↔ UPF) | ✔️ | PFCP protocol implementation | |
| 3. N6 interface (UPF ↔ Data Network) | ✔️ | Internet/DN connectivity | |
| 4. N9 interface (UPF ↔ UPF) | ❌ | Not implemented |
| ID | Classification | Status | Comments |
|---|---|---|---|
| 50 | N2 Handover support: | ||
| 1. Xn-based handover | ❌ | Not implemented | |
| 2. N2-based handover | ❌ | Not implemented | |
| 3. Make-Before-Break handover | ❌ | Not implemented | |
| 51 | Inter-UPF mobility: | ||
| 1. I-UPF (Intermediate UPF) support | ❌ | Not implemented | |
| 2. PSA-UPF (PDU Session Anchor) support | ❌ | Not implemented | |
| 3. ULCL (Uplink Classifier) support | ❌ | Not implemented | |
| 52 | 4G/5G Interworking: | ||
| 1. S5/S8 interface support | ❌ | Not implemented | |
| 2. EPS Bearer to QoS Flow mapping | ❌ | Not implemented |
| ID | Classification | Status | Comments |
|---|---|---|---|
| 53 | Configuration management | ✔️ | YAML-based configuration |
| 54 | Logging and tracing: | ||
| 1. Structured logging (info/debug/error) | ✔️ | Multiple log levels | |
| 2. Per-component logging | ✔️ | Granular log control | |
| 3. PFCP message tracing | ✔️ | Full protocol traces | |
| 55 | Statistics and metrics: | ||
| 1. Session statistics | 🔶 | Basic statistics | |
| 2. Traffic statistics | 🔶 | Basic statistics | |
| 3. Metrics export (Prometheus, etc.) | ❌ | Not implemented | |
| 56 | Health monitoring: | ||
| 1. PFCP association status | ✔️ | Association state tracking | |
| 2. Heartbeat mechanism | ✔️ | Keep-alive monitoring | |
| 3. Interface status | ✔️ | N3/N4/N6 monitoring | |
| 57 | Graceful shutdown and cleanup | ✔️ | Clean resource release |
| Category | Total | Applicable | Implemented | Partial | Not Implemented |
|---|---|---|---|---|---|
| Core UPF Functions | 21 | 12 | 4 | 4 | 4 |
| N4 (PFCP) Protocol Support | 7 | 7 | 5 | 2 | 0 |
| Packet Detection Rules (PDR) | 4 | 4 | 3 | 1 | 0 |
| Forwarding Action Rules (FAR) | 3 | 3 | 1 | 2 | 0 |
| QoS Enforcement Rules (QER) | 8 | 8 | 6 | 0 | 2 |
| Usage Reporting Rules (URR) | 6 | 6 | 1 | 5 | 0 |
| Data Plane Acceleration | 5 | 5 | 5 | 0 | 0 |
| 5G Features | 3 | 3 | 1 | 2 | 0 |
| Mobility and Interworking | 3 | 0 | 0 | 0 | 0 |
| Management and Operations | 5 | 5 | 4 | 1 | 0 |
| TOTAL | 65 | 53 | 30 | 17 | 6 |
Applicable Features: 53/65 (81.5%) - 12 features excluded as non-applicable
Implementation Rate (of applicable features):
- Fully Implemented: 30/53 (56.6%)
- Partially Implemented: 17/53 (32.1%)
- Not Implemented: 6/53 (11.3%)
Overall Coverage: 88.7% (30 full + 17 partial / 53 applicable)
- Data Plane Acceleration (5/5 fully implemented)
- Core UPF Functions (4/12 full + 4/12 partial = 8/12 coverage)
- N4 (PFCP) Protocol (5/7 full + 2/7 partial = 7/7 coverage)
- Packet Detection Rules (3/4 full + 1/4 partial = 4/4 coverage)
- Forwarding Action Rules (1/3 full + 2/3 partial = 3/3 coverage)
- Usage Reporting Rules (1/6 full + 5/6 partial = 6/6 coverage)
- 5G Features (1/3 full + 2/3 partial = 3/3 coverage)
- Management and Operations (4/5 full + 1/5 partial = 5/5 coverage)
All remaining unimplemented features are enhancements, not core functionality:
- Transport level packet marking (ID 11) - Enhancement
- Downlink packet buffering (ID 12) - Enhancement
- End marker forwarding (ID 13) - Handover optimization
- Reflective QoS (ID 32) - Advanced QoS feature
- Packet Rate Control (ID 34) - Paging optimization
- Metrics export (ID 55.3) - Observability enhancement
| ID | Interface | Status | Comment |
|---|---|---|---|
| 1 | N35 | ✔️ | Communicate with UDM |
| 2 | N36 | ❌ | Communicate with PCF |
| 3 | N37 | ❌ | Communicate with NEF |
Based on document 3GPP TS 23.501 V16.14.0 §6.2.11.
| ID | Classification | Status | Comments |
|---|---|---|---|
| 1 | Storage and retrieval of subscription data by the UDM | ✔️ | |
| 2 | Storage and retrieval of policy data by the PCF | ❌ | |
| 3 | Storage and retrieval of structured data for exposure | ❌ | |
| 4 | Application data | ❌ | |
| 5 | Storage and retrieval of NF Group ID | ❌ |
| ID | Interface | Status | Comment |
|---|---|---|---|
| 1 | N12 | ✔️ | Communicate with AMF |
| 2 | N13 | ✔️ | Communicate with UDM |
All interfaces support both HTTP/1.1 and HTTP/2
Based on document 3GPP TS 23.501 V16.14.0 §6.2.8.
| ID | Classification | Status | Comments |
|---|---|---|---|
| 1 | Supports authentication for 3GPP access | ✔️ | |
| 2 | Supports authentication for untrusted non-3GPP access | ❌ |
| ID | Interface | Status | Comment |
|---|---|---|---|
| 1 | N8 | ✔️ | Communicate with AMF |
| 2 | N10 | ✔️ | Communicate with SMF |
| 3 | N13 | ✔️ | Communicate with AUSF |
| 4 | N35 | ✔️ | Communicate with UDR |
All interfaces support both HTTP/1.1 and HTTP/2
Based on document 3GPP TS 23.501 V16.14.0 §6.2.7.
| ID | Classification | Status | Comments |
|---|---|---|---|
| 1 | Generation of 3GPP AKA Authentication Credentials | ✔️ | |
| 2 | User Identification Handling | ✔️ | |
| 3 | Support of de-concealment of SUCI | ✔️ | |
| 4 | Access authorization based on subscription data | ❌ | |
| 5 | UE's Serving NF Registration Management | ❌ | |
| 6 | Support to service/session continuity | ❌ | |
| 7 | MT-SMS delivery support | ❌ | |
| 8 | Lawful Intercept Functionality | ❌ | |
| 9 | Subscription management | ❌ | |
| 10 | SMS management | ❌ | |
| 11 | 5GLAN group management handling | ❌ | |
| 12 | Support of external parameter provisioning | ❌ |
| ID | Interface | Status | Comment |
|---|---|---|---|
| 1 | N22 (*) | ✔️ | between NSSF and AMF |
| 2 | N31 | ❌ | between NSSFS |
(*): support both HTTP/1.1 and HTTP/2
Based on document 3GPP TS 23.501 v16.14.0 (Section 6.2.14).
| ID | Classification | Status | Comments |
|---|---|---|---|
| 1 | NSI Selection | ✔️ | Case: PDU Session (Non Roaming) |
| 2 | Determining the Allowed NSSAI | ❌ | |
| 3 | Determining the Configured NSSAI | ❌ | |
| 4 | Determining the AMF Set | ❌ |
| ID | Interface | Status | Comment |
|---|---|---|---|
| 1 | N7 (*) (**) | ✔️ | between PCF and SMF |
| 2 | N5 | ❌ | between PCF and AF |
| 3 | N15 | ❌ | between PCF and AMF |
| 4 | N24 | ❌ | between V-PCF and H-PCF |
| 5 | N36 | ❌ | between PCF and UDR |
(*): support both HTTP/1.1 and HTTP/2 (**): UpdateNotify feature not supported
Based on documents 3GPP TS 23.501 v16.0.0 (Section 6.2.4) and 3GPP TS 23.503 v16.0.0 (Section 6.2.1)
| ID | Classification | Status | Comments |
|---|---|---|---|
| 1 | Policy and charging control for a service data flows | ❌ | |
| 2 | PDU Session related policy control | ✔️ | Except UpdateNotify feature |
| 3 | PDU Session event reporting to the AF | ❌ | |
| 4 | Access and mobility related policy control | ❌ | |
| 5 | UE access selection and PDU Session selection related policy control | ❌ | |
| 6 | Negotiation for future background data transfer | ❌ | |
| 7 | Usage monitoring | ❌ | |
| 8 | Sponsored data connectivity | ❌ | |
| 9 | Input for PCC decisions | ❌ | Currently only local rules |
| 10 | Policy control subscription information management | ❌ | |
| 11 | V-PCF | ❌ | |
| 12 | H-PCF | ❌ | |
| 13 | Application specific policy information management | ❌ | |
| 14 | NRF NF Registration | ✔️ |
| ID | Interface | Status | Comment |
|---|---|---|---|
| 1 | NL1 | ✔️ | NL1 interface connects the LMF to the UE (via AMF) |
Based on document TS 23.273 (section 4.3.8 of TS 23.273).
| ID | Classification | Status | Comments |
|---|---|---|---|
| 1 | Support a request for a single location received from a serving AMF for a target UE | ✔️ | |
| 2 | Support a request for periodic or triggered location received from a serving AMF | ❌ | |
| for a target UE | |||
| 3 | Determine type and number of position methods and procedures based on UE and PLMN | ❌ | |
| capabilities, QoS, UE connectivity state per access type, LCS Client type, | |||
| co-ordinate type and optionally service type | |||
| 4 | Report UE location estimates directly to a GMLC for periodic or triggered location | ❌ | |
| of a target UE | |||
| 5 | Support cancellation of periodic or triggered location for a target UE | ❌ | |
| 6 | Support the provision of broadcast assistance data to UEs via NG-RAN in ciphered | ❌ | |
| or un-ciphered form and forward any ciphering keys to subscribed UEs via the AMF | |||
| 7 | Support change of a serving LMF for periodic or triggered location reporting for | ❌ | |
| a target UE |
Based on TS 29.520 V17.19.0:
- Event: NETWORK_PERFORMANCE
- Type: Number of connected users (NwPerType: NUM_OF_UE)
- Type: Session success ratio (NwPerType: SESS_SUCC_RATIO)
- Event: UE_COMMUNICATION
- Event: UE_MOBILITY
In addition to these features, we have also implemented an ML-based feature exclusively for the Events Subscription API:
- Event: ABNORMAL_BEHAVIOUR
