Skip to content

TS 23.401 — General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access⚓︎

Release: Rel 15 · Version assessed: 15.3.0 · Network: 4G · Applies to: MME, SGW, PGW, HSS

Mandatory items: 98, of which 92 supported, 3 partially supported, 1 not supported and 2 not applicable. A further 240 clauses of the specification carry no conformance requirement and are not listed.

Mandatory items⚓︎

Ref. Item Status Support Remarks
4.3.7.2 Load balancing between MMEs Mandatory Supported Weights are stored in MME
4.3.8 Selection functions Mandatory Supported
4.3.8.1 PDN GW selection function (3GPP accesses) Mandatory Supported
4.3.8.2 Serving GW selection function Mandatory Supported
4.3.8.3 MME selection function Mandatory Supported
4.3.12 IMS Emergency Session Support Mandatory Supported This section is partially supported.
4.3.12.1 Introduction Mandatory Not applicable (Emergency services) Partially supported: Configuration option 1 and 2 has been combined.
4.3.12.2 Architecture Reference Model for Emergency Services Mandatory Supported
4.3.12.3 Mobility and Access Restrictions for Emergency Services Mandatory Supported
4.3.12.3a Reachability Management for UE in ECM-IDLE state Mandatory Supported
4.3.12.5 QoS for Emergency Services Mandatory Partial Only QCI and ARP are configured for emergency bearers.
4.3.12.8 IP Address Allocation Mandatory Not applicable (Emergency services)
4.3.13 Closed Subscriber Group functions Mandatory Partial CSG identities are decoded, stored and forwarded; CSG membership is not enforced.
4.4.2 MME Mandatory Supported
4.7.1 PDN connectivity service Mandatory Supported
4.7.2 The EPS bearer Mandatory Supported
4.7.2.1 The EPS bearer in general Mandatory Supported
4.7.2.3 The EPS bearer with PMIP-based S5/S8 Mandatory Supported
5.0 Functional description and information flows Mandatory Supported
5.1.1.2 eNodeB - MME Mandatory Supported
5.1.1.3 UE - MME Mandatory Supported
5.1.1.8 MME - S‑GW Mandatory Supported
5.1.1.9 MME - HSS Mandatory Supported
5.1.1.10 MME - EIR Mandatory Supported
5.1.1.11 Void Mandatory Supported
5.2.1 EPS bearer identity Mandatory Supported
5.2.2 Globally Unique Temporary UE Identity Mandatory Supported
5.2.3 Tracking Area Identity (TAI) Mandatory Supported
5.2.4 eNodeB S1-AP UE Identity (eNB S1-AP UE ID) Mandatory Supported
5.2.5 MME S1-AP UE Identity (MME S1-AP UE ID) Mandatory Supported
5.2.6 Closed Subscriber Group ID Mandatory Partial CSG identities are stored and forwarded; an attach from a CSG cell the subscriber is not subscribed to is not rejected.
5.3.2 Attach procedure Mandatory Supported Legacy network and ISR is not supported
5.3.2.1 E-UTRAN Initial Attach Mandatory Supported
5.3.2.2 UTRAN/GERAN Initial Attach Mandatory Supported
5.3.3 Tracking Area Update procedures Mandatory Supported Legacy network and ISR is not supported
5.3.3.0 Triggers for tracking area update Mandatory Supported
5.3.3.0A Provision of UEs TAI to MME in ECM-CONNECTED state Mandatory Supported
5.3.3.1 Tracking Area Update procedure with Serving GW change Mandatory Supported
5.3.3.2 E-UTRAN Tracking Area Update without S‑GW Change Mandatory Supported
5.3.4 Service Request procedures Mandatory Supported
5.3.4.1 UE triggered Service Request Mandatory Supported
5.3.4.2 Handling of abnormal conditions in UE triggered Service Request Mandatory Supported
5.3.4.3 Network Triggered Service Request Mandatory Supported Paging Optimization is not supported.
5.3.5 S1 release procedure Mandatory Supported
5.3.8 Detach procedure Mandatory Supported
5.3.8.1 General Mandatory Supported
5.3.8.2 UE-initiated Detach procedure Mandatory Supported
5.3.8.2.1 UE-initiated Detach procedure for E-UTRAN Mandatory Supported
5.3.8.3 MME-initiated Detach procedure Mandatory Supported The MME runs no implicit detach timer for emergency services.
5.3.8.4 HSS-initiated Detach procedure Mandatory Supported
5.3.9 HSS User Profile management function procedure Mandatory Supported
5.3.9.1 General Mandatory Supported
5.3.9.2 Insert Subscriber Data procedure Mandatory Supported
5.3.9.3 Purge function Mandatory Supported
5.3.10 Security Function Mandatory Supported
5.3.10.1 General Mandatory Supported
5.3.10.2 Authentication and Key Agreement Mandatory Supported
5.3.10.3 User Identity Confidentiality Mandatory Supported
5.3.10.4 User Data and Signalling Confidentiality Mandatory Supported
5.3.10.4.1 AS security mode command procedure Mandatory Supported
5.3.10.4.2 NAS Security Mode Command procedure Mandatory Supported
5.3.11 UE Reachability procedures Mandatory Supported
5.3.11.1 General Mandatory Supported
5.3.11.2 UE Reachability Notification Request procedure Mandatory Supported
5.3.11.3 UE Activity Notification procedure Mandatory Supported
5.4 Session Management, QoS, and interaction with PCC functionality Mandatory Supported
5.4.1 Dedicated bearer activation Mandatory Supported
5.4.2 Bearer modification with bearer QoS update Mandatory Supported
5.4.2.1 PDN GW initiated bearer modification with bearer QoS update Mandatory Supported
5.4.2.2 HSS Initiated Subscribed QoS Modification Mandatory Supported
5.4.3 PDN GW initiated bearer modification without bearer QoS update Mandatory Supported
5.4.4 Bearer deactivation Mandatory Supported
5.4.4.1 PDN GW initiated bearer deactivation Mandatory Supported
5.4.4.2 MME Initiated Dedicated Bearer Deactivation Mandatory Supported
5.4.5 UE requested bearer resource modification Mandatory Supported
5.4.7 E-UTRAN initiated E-RAB modification procedure Mandatory Supported
5.4.8 E-UTRAN initiated UE Context Modification procedure Mandatory Supported
5.5 Handover Mandatory Supported Assessed per sub-clause.
5.5.1 Intra-E-UTRAN handover Mandatory Supported
5.5.1.1 X2-based handover Mandatory Supported
5.5.1.1.1 General Mandatory Supported
5.5.1.1.2 X2-based handover without Serving GW relocation Mandatory Supported
5.5.1.1.3 X2-based handover with Serving GW relocation Mandatory Supported
5.5.1.2 S1-based handover Mandatory Supported
5.5.1.2.1 General Mandatory Supported
5.5.1.2.2 S1-based handover, normal Mandatory Supported
5.5.1.2.3 S1-based handover, Reject Mandatory Supported
5.5.1.2.4 S1-based handover, Cancel Mandatory Supported
5.7.2 MME Mandatory Supported Classmark, Supported codecs, MS capability, Selected CN operator Id, ODB for PS parameters, RFSP, OMCI, restriction list, GRE key are not stored. For emergency services only emergency APN list and QoS parameters (QCI and ARP) are configured.
5.7.6 Handling of Wild Card APN Mandatory Supported
5.10.2 UE requested PDN connectivity Mandatory Supported
5.10.3 UE or MME requested PDN disconnection Mandatory Supported
5.12 Warning message delivery Mandatory Supported
5.12.1 General Mandatory Supported
5.12.2 Void Mandatory Supported
5.12.3 Void Mandatory Supported
5.16 MME-initiated procedure on UE's CSG membership change Mandatory Not supported A change of CSG membership does not trigger an MME-initiated procedure.
J.4 Downlink data transfer Mandatory Supported

Optional items⚓︎

The specification leaves these 112 items to the implementation; 19 are supported or partially supported. An item marked Not applicable belongs to an area the platform does not provide, named in the Support column. Expand for the full list.

112 optional items
Ref. Item Support Remarks
4.3.2a Support for Dual Connectivity Supported
4.3.5.2 Reachability Management for UE in ECM-IDLE state Not supported ISR is not supported
4.3.7.1a GTP-C signalling based Load and Overload Control Not supported
4.3.7.1a.1 GTP-C Load Control Not supported
4.3.7.1a.2 GTP-C Overload Control Not supported
4.3.7.4 MME control of overload Not supported
4.3.7.4.1b Throttling of NIDD Submit Requests Not supported
4.3.12.4 PDN GW selection function (3GPP accesses) for Emergency Services Supported PGW default selection rules still apply for the Emergency Attach.
4.3.12.11 Support of eCall Only Mode Not supported
4.3.17.3 Optimizing periodic TAU Signalling Not supported The extended periodic TAU timer is not configured or used; the periodic TAU timer IE is used.
4.3.17.4 UE configuration and usage of indicators Supported The low access priority indication is stored in the MME and sent in GTP messages on S11.
4.3.17.7 High latency communication Not supported
4.3.17.8 Support for Non-IP Data Delivery (NIDD) Not supported
4.3.17.8.1 General Not supported
4.3.17.8.2 ESM Procedures Not supported
4.3.17.8.3 Delivery mechanism Not supported
4.3.17.9 Service Gap Control Not supported
4.3.21 Core Network assisted eNodeB parameters tuning Not supported
4.3.21.1 CN Assistance Information Not supported
4.3.21.2 Void Not supported
4.3.21.3 Core Network Assistance Procedures Not supported
4.3.22 UE Power Saving Mode Supported
4.3.23 Access network selection and traffic steering based on RAN-assisted WLAN interworking Not supported
4.3.23a Access network selection and traffic steering based on RAN-Controlled WLAN interworking Not supported
4.3.24 RAN user plane congestion management function Not supported
4.3.24.1 General Not supported
4.3.24.2 RAN user plane congestion mitigation in the RAN Not supported
4.3.24.3 RAN user plane congestion mitigation in the CN Not supported
4.3.25 Dedicated Core Networks (DCNs) Not supported
4.3.25.1 General Not supported
4.3.25.1a UE assisted Dedicated Core Network selection Not supported
4.3.25.2 Considerations for Roaming Not supported
4.3.25.3 Considerations for Network Sharing Not supported
4.3.26 Support for Monitoring Events Not supported
4.3.27 Paging Enhancements Not supported
4.3.27.1 Paging for Enhanced Coverage Not supported
4.3.27a Restriction of use of Enhanced Coverage for voice centric UE Not supported
4.3.27b Enhanced Coverage for data centric UEs Not supported
4.3.28 Restriction of use of Enhanced Coverage Not supported
4.3.29 3GPP PS Data Off Not supported
4.8 Compatibility Issues Not supported
4.9 Paging Policy Differentiation Not supported
4.10 Introduction of CIoT EPS Optimisations Not supported
5.1 Control and user planes Supported GTP & PMIP based S5/S8 supported.
5.1.1.4 SGSN - MME Not supported
5.1.1.7 MME - MME Supported
5.1.1.12 MME - CSS Not supported
5.1.1.13 MME - RCAF Not supported
5.3.3.1A Tracking Area Update procedure with Serving GW change and data forwarding Not supported
5.3.3.3 Routing Area Update with MME interaction and without S‑GW change Not supported
5.3.3.4 Void Not supported
5.3.4.A Connection Suspend procedure Not supported
5.3.4B Data Transport in Control Plane CIoT EPS optimisation Not supported
5.3.4B.1 General Not supported
5.3.4B.2 Mobile Originated Data Transport in Control Plane CIoT EPS optimisation with P-GW connectivity Not supported
5.3.4B.3 Mobile Terminated Data Transport in Control Plane CIoT EPS optimisation with P-GW connectivity Not supported
5.3.5A Connection Resume procedure Not supported
5.3.7 GUTI Reallocation procedure Not supported
5.3.8.2.2 UE-initiated Detach procedure for GERAN/UTRAN with ISR activated Not supported
5.3.10.5 ME identity check procedure Not supported
5.3.12 Update CSG Location Procedure Not supported
5.3.13 CSS subscription data management function procedure Not supported
5.3.13.1 General Not supported
5.3.13.2 Insert CSG Subscriber Data procedure Not supported
5.3.14 UE Radio Capability Match Request Not supported
5.5.2 Inter RAT handover Not supported
5.5.2.0 General Not supported
5.5.2.1 E-UTRAN to UTRAN Iu mode Inter RAT handover Not supported
5.5.2.1.1 General Not supported
5.5.2.1.2 Preparation phase Not supported
5.5.2.1.3 Execution phase Not supported
5.5.2.1.4 E-UTRAN to UTRAN Iu mode Inter RAT handover Reject Not supported
5.5.2.2 UTRAN Iu mode to E-UTRAN Inter RAT handover Not supported
5.5.2.2.1 General Not supported
5.5.2.2.2 Preparation phase Not supported
5.5.2.2.3 Execution phase Not supported
5.5.2.2.4 UTRAN Iu mode to E-UTRAN Inter RAT handover reject Not supported
5.5.2.3 E-UTRAN to GERAN A/Gb mode Inter RAT handover Not supported
5.5.2.3.1 General Not supported
5.5.2.3.2 Preparation phase Not supported
5.5.2.3.3 Execution phase Not supported
5.5.2.3.4 E-UTRAN to GERAN A/Gb mode Inter RAT handover reject Not supported
5.5.2.4 GERAN A/Gb mode to E-UTRAN Inter RAT handover Not supported
5.5.2.4.1 General Not supported
5.5.2.4.2 Preparation phase Not supported
5.5.2.4.3 Execution phase Not supported
5.5.2.4.4 GERAN A/Gb mode to E-UTRAN Inter RAT handover reject Not supported
5.5.2.5 Inter RAT handover Cancel Not supported
5.5.2.5.1 General Not supported
5.5.2.5.2 Source RAN to Target RAN Inter RAT handover Cancel Not supported
5.6 Network Assisted Cell Change Not supported
5.6.1 Architecture Principles for E-UTRAN to GERAN NACC Not supported
5.7A.2 Usage Data Reporting for Secondary RAT Not supported
5.7A.3 Secondary RAT Usage Data Reporting Procedure Not supported
5.7A.4 Secondary RAT Periodic Usage Data Reporting Procedure Not supported
5.8 MBMS Not supported
5.9.1 Location Reporting Procedure Not supported Current TAI + ECGI sent by eNodeB during Tracking Area Update is used by MME.
5.10.4 MME triggered Serving GW relocation Not supported
5.11.1 General Supported
5.11.2 UE Radio Capability Handling Supported
5.11.3 UE Core Network Capability Supported
5.11.4 UE Radio Capability for Paging Information Not supported
5.13 Discontinuous Reception and UE Specific DRX Parameter handling Supported DRX received in Attach request is sent towards UE in Attach Accept
5.13a Extended Idle mode Discontinuous Reception (DRX) Supported
5.14 Configuration Transfer procedure Supported
Annex D Interoperation with Gn/Gp SGSNs Supported
D.1 General Considerations Supported Only Gn interface (GTPv1) between MME and SGSN is supported
D.3.3 MME to 3G SGSN combined hard handover and SRNS relocation procedure Supported
D.3.4 3G SGSN to MME combined hard handover and SRNS relocation procedure Supported
D.3.5 Routing Area Update Supported
D.3.6 Gn/Gp SGSN to MME Tracking Area Update Supported
Annex F Dedicated bearer activation in combination with the default bearer activation at Attach and UE requested PDN connectivity procedures Supported

Assessed 2026-09-15 against TS 23.401 version 15.3.0.