N26 Mobility — Connected / Idle in Both Directions¶
Why — Separate both state and direction¶
This chapter expands 4G-5G Interworking into Connected Handover and mobility starting from Idle. In the Connected examples, the source RAN initiates handover. In the Idle examples, the UE camps on the target access and starts TAU or Registration to retrieve information from the old CN. Because 5GS-to-EPS and EPS-to-5GS also differ in context preparation and subsequent processing, four independent diagrams are provided (TS 23.502 Clause 4.11.1.2 / Clause 4.11.1.3).
The scope is single-registration mode, non-roaming and normal IP sessions, with a shared SMF+PGW-C and UPF+PGW-U. All four diagrams show successful cases without direct or indirect data forwarding. Radio details, AMF reselection and individual handling of sessions that cannot transfer are omitted. Session continuity does not unconditionally guarantee lossless or interruption-free service.
Four procedures¶
- 5GS → EPS / Connected: Handover. N26 uses Forward Relocation, followed by TAU after the move.
- 5GS → EPS / Idle: Idle Mobility. TAU at the target triggers a Context Request from the MME to the AMF.
- EPS → 5GS / Connected: Handover. N26 uses Forward Relocation, followed by Mobility Registration after the move.
- EPS → 5GS / Idle: Idle Mobility. Registration at the target triggers a Context Request from the AMF to the MME.
References: TS 23.502 Clause 4.11.1.2.1 / Clause 4.11.1.2.2 / Clause 4.11.1.3.2 / Clause 4.11.1.3.3. Idle describes the state when the move starts. It does not eliminate the signalling connection needed to send TAU or Registration.
What — Context to transfer and paths to switch¶
- AMF / MME: Coordinate preparation and completion over N26 for Connected Handover; for Idle Mobility, the target CN retrieves context from the old CN.
- SMF+PGW-C: Maps 5GS PDU Session information to EPS PDN Connection/bearer information.
- UPF+PGW-U: Switches paths as the shared user-plane anchor.
- S-GW: Participates in the EPS user-plane path.
- QFI / EBI: Do not treat them as the same identifier; check the mapping between transferable QoS Flows and EPS bearers.
N26 availability alone does not make every session transferable. Check mapped EPS bearer information, 5G QoS information and anchor capabilities (TS 23.502 Clause 4.11.1.2.1 / Clause 4.11.1.2.2.1 / Clause 4.11.1.3).
Procedure — 5GS to EPS Handover¶
This is the Connected procedure. It shows a successful PDU Session transfer with usable EPS bearer information and no direct or indirect data forwarding. The target is an E-UTRAN eNB, and the N26 peer is the MME (TS 23.502 Clause 4.11.1.2.1).
sequenceDiagram
participant UE
participant G as Source NG-RAN
participant AMF
participant MME
participant E as Target eNB
participant SGW as S-GW
participant SMF as SMF + PGW-C
participant UPF as UPF + PGW-U
G->>AMF: NGAP Handover Required<br/>Target eNB
AMF->>SMF: Nsmf_PDUSession_ContextRequest<br/>POST /nsmf-pdusession/v1/sm-contexts/{smContextRef}/retrieve
opt EPS-side CN tunnel preparation is required
SMF->>UPF: PFCP Session Modification Request
UPF-->>SMF: PFCP Session Modification Response
end
SMF-->>AMF: Nsmf_PDUSession_ContextRequest<br/>HTTP 200 OK, EPS PDN connection
AMF->>MME: GTPv2-C Forward Relocation Request
MME->>SGW: GTPv2-C Create Session Request
SGW-->>MME: GTPv2-C Create Session Response
MME->>E: S1AP Handover Request
E-->>MME: S1AP Handover Request Acknowledge
MME-->>AMF: GTPv2-C Forward Relocation Response
AMF->>G: NGAP Handover Command
G->>UE: NR RRC MobilityFromNRCommand<br/>LTE RRC: RRCConnectionReconfiguration
UE->>E: LTE RRC RRCConnectionReconfigurationComplete
E->>MME: S1AP Handover Notify
MME->>AMF: GTPv2-C Forward Relocation Complete Notification
AMF-->>MME: GTPv2-C Forward Relocation Complete Acknowledge
MME->>SGW: GTPv2-C Modify Bearer Request
SGW->>SMF: GTPv2-C Modify Bearer Request
SMF->>UPF: PFCP Session Modification Request<br/>EPS downlink tunnel
UPF-->>SMF: PFCP Session Modification Response
SMF-->>SGW: GTPv2-C Modify Bearer Response
SGW-->>MME: GTPv2-C Modify Bearer Response
UE->>E: LTE RRC ULInformationTransfer<br/>NAS: Tracking Area Update Request
E->>MME: S1AP Uplink NAS Transport<br/>NAS: Tracking Area Update Request
Note over AMF: Source RAN resource-release timer expires
AMF->>G: NGAP UE Context Release Command
G-->>AMF: NGAP UE Context Release CompleteStep-by-step explanation¶
- Collect information usable in EPS: The AMF obtains mapped EPS PDN Connection information and related context from the SMF+PGW-C. Exclusion conditions apply to EBIs and PDU Sessions that cannot transfer.
- The MME prepares the EPS side: After Forward Relocation Request, it prepares S-GW and Target eNB resources.
- Move the UE after preparation: Without data forwarding, this diagram proceeds from Forward Relocation Response to Handover Command. If data forwarding, including direct forwarding, is used, additional processing such as UpdateSMContext with the SMF is required first (TS 23.502 Clause 4.11.1.2.1 steps 10a / 10c). Do not reuse the illustrated order unchanged.
- Coordinate completion over N26: After notification from the Target eNB, the MME notifies the AMF of completion.
- Switch the downlink user plane: Modify Bearer along MME → S-GW → SMF+PGW-C, together with N4 updates, switches the path to EPS.
- Check TAU and cleanup: The UE performs TAU. Cleanup of the old AMF's 3GPP-access registration and conditional handling of dedicated bearers and forwarding resources must also be considered. Source NG-RAN resources are released according to the AMF-side timer.
Reference: TS 23.502 Clause 4.11.1.2.1. The referenced EPC-side procedure is TS 23.401 Clause 5.5.1.2.2.
Not every QoS Flow is carried over unchanged
Retained sessions/flows depend on EBI allocation, transfer eligibility and the flow associated with the default QoS rule. Do not assume arbitrary one-to-one mappings between 5QI and QCI; inspect the mapped EPS bearer context actually transferred (TS 23.502 Clause 4.11.1.2.1 steps 2, 11 and 14–19).
Procedure — EPS to 5GS Handover¶
This is the Connected procedure. It shows successful transfer of a PDN Connection at the shared anchor to 5GS. The initially selected AMF remains the Target AMF, and neither direct nor indirect data forwarding is used (TS 23.502 Clause 4.11.1.2.2).
sequenceDiagram
participant UE
participant E as Source eNB
participant MME
participant AMF as Target AMF
participant G as Target NG-RAN
participant SMF as SMF + PGW-C
participant UPF as UPF + PGW-U
participant SGW as Source S-GW
E->>MME: S1AP Handover Required
MME->>AMF: GTPv2-C Forward Relocation Request
AMF->>SMF: Nsmf_PDUSession_CreateSMContext<br/>POST /nsmf-pdusession/v1/sm-contexts
SMF->>UPF: PFCP Session Modification Request<br/>5GS CN tunnel
UPF-->>SMF: PFCP Session Modification Response<br/>CN tunnel information
SMF-->>AMF: Nsmf_PDUSession_CreateSMContext<br/>HTTP 201 Created, N2 SM information
AMF->>G: NGAP Handover Request
G-->>AMF: NGAP Handover Request Acknowledge<br/>Target N3 tunnel
AMF->>SMF: Nsmf_PDUSession_UpdateSMContext<br/>POST /nsmf-pdusession/v1/sm-contexts/{smContextRef}/modify
SMF->>UPF: PFCP Session Modification Request<br/>Handover preparation
UPF-->>SMF: PFCP Session Modification Response
SMF-->>AMF: Nsmf_PDUSession_UpdateSMContext<br/>HTTP 200 OK / 204 No Content
AMF-->>MME: GTPv2-C Forward Relocation Response
MME->>E: S1AP Handover Command
E->>UE: LTE RRC MobilityFromEUTRACommand<br/>NR RRC: RRCReconfiguration
UE->>G: NR RRC RRCReconfigurationComplete
G->>AMF: NGAP Handover Notify
AMF->>MME: GTPv2-C Forward Relocation Complete Notification
MME-->>AMF: GTPv2-C Forward Relocation Complete Acknowledge
AMF->>SMF: Nsmf_PDUSession_UpdateSMContext<br/>POST /nsmf-pdusession/v1/sm-contexts/{smContextRef}/modify
SMF->>UPF: PFCP Session Modification Request<br/>Target N3 tunnel
UPF-->>SMF: PFCP Session Modification Response
SMF-->>AMF: Nsmf_PDUSession_UpdateSMContext<br/>HTTP 200 OK / 204 No Content
UE->>G: NR RRC ULInformationTransfer<br/>NAS: Registration Request (mobility registration updating)
G->>AMF: NGAP Uplink NAS Transport<br/>NAS: Registration Request
Note over E,SGW: MME cleans up old EPS resources according to conditions / timers (outline)Step-by-step explanation¶
- Transfer EPS context to the AMF: Forward Relocation Request over N26 is the entry point. The AMF converts EPS MM context into 5GS information.
- Prepare the 5GS SM context: The AMF requests
CreateSMContextfrom the SMF+PGW-C associated with the existing PDN Connection. It indicates HO Preparation so that the downlink path is not switched during preparation. - Apply Target RAN admission results: Prepare the Target RAN using S-NSSAI, EBI/QFI mappings and N2 SM information, then apply the returned N3 information at the SMF/UPF.
- Move the UE and notify completion over N26: After preparation, the UE moves, and the Target AMF notifies the MME of completion.
- Switch the downlink path to 5GS: On Handover Complete, the SMF+PGW-C updates N4. Conditional End Marker handling and PCF updates are omitted.
- Perform Mobility Registration and old-resource cleanup: The UE proceeds with EPS-to-5GS Mobility Registration, and the MME cleans up old EPS resources. PDN Connections that cannot transfer to 5GS require separate handling.
References: TS 23.502 Clause 4.11.1.2.2.2 / Clause 4.11.1.2.2.3, TS 36.331 Clause 5.4.3, TS 38.331 Clause 5.3.5.
Distinguish N26/no-N26 and Handover/Idle mobility
This diagram is a handover using N26. Do not mix it with Idle Context Request/Response or movement without N26. RelocateUEContext for AMF reselection during EPS-to-5GS handover is also omitted. It is not the same operation as Registration rerouting (TS 23.502 Clause 4.11.1.2.2.2 step 8a / Clause 4.11.1.3 / Clause 4.11.2).
Procedure — 5GS to EPS Idle Mobility¶
This is the Idle procedure. The UE moves from 5GS CM-IDLE to E-UTRA/EPS and starts TAU. There are transferable PDU Sessions, but no user-plane activation is requested using the TAU active flag, nor triggered by downlink data or similar events. TAU integrity verification succeeds, and the MME allocates a new GUTI (TS 23.502 Clause 4.11.1.3.2 / Clause 4.11.1.5.3; TS 23.401 Clause 5.3.3.1).
sequenceDiagram
participant UE
participant E as eNB
participant MME
participant AMF as Old AMF
participant SGW as S-GW
participant SMF as SMF + PGW-C
participant UPF as UPF + PGW-U
participant HSS as HSS + UDM
Note over UE: Camp on EPS from CM-IDLE<br/>No source RAN handover preparation
UE->>E: LTE RRC RRCConnectionSetupComplete<br/>NAS: Tracking Area Update Request
E->>MME: S1AP Initial UE Message<br/>NAS: Tracking Area Update Request
MME->>AMF: GTPv2-C Context Request<br/>TAU Request
Note over AMF: Verify TAU Request integrity
AMF->>SMF: Nsmf_PDUSession_ContextRequest<br/>POST /nsmf-pdusession/v1/sm-contexts/{smContextRef}/retrieve
opt CN tunnel information for EPS bearers needs allocation
SMF->>UPF: PFCP Session Modification Request
UPF-->>SMF: PFCP Session Modification Response
end
SMF-->>AMF: Nsmf_PDUSession_ContextRequest<br/>HTTP 200 OK, EPS PDN connection
AMF-->>MME: GTPv2-C Context Response<br/>Mapped MM / security context, EPS bearer contexts
opt Additional authentication / security processing is required
Note over UE,MME: Authentication and security details omitted
end
MME->>AMF: GTPv2-C Context Acknowledge
MME->>SGW: GTPv2-C Create Session Request
SGW->>SMF: GTPv2-C Modify Bearer Request
SMF->>UPF: PFCP Session Modification Request<br/>SGW-U tunnel information
UPF-->>SMF: PFCP Session Modification Response
SMF-->>SGW: GTPv2-C Modify Bearer Response
SGW-->>MME: GTPv2-C Create Session Response
MME->>HSS: Diameter Update Location Request
HSS->>AMF: Nudm_UECM_DeregistrationNotification<br/>POST {deregCallbackUri}
AMF-->>HSS: Nudm_UECM_DeregistrationNotification<br/>HTTP 204 No Content
Note over AMF,HSS: Clean up old 3GPP registration / subscriptions / policy, etc. (outline)
HSS-->>MME: Diameter Update Location Answer
MME->>E: S1AP Downlink NAS Transport<br/>NAS: Tracking Area Update Accept
E->>UE: LTE RRC DLInformationTransfer<br/>NAS: Tracking Area Update Accept
UE->>E: LTE RRC ULInformationTransfer<br/>NAS: Tracking Area Update Complete
E->>MME: S1AP Uplink NAS Transport<br/>NAS: Tracking Area Update Complete
Note over UE,MME: No radio / S1 user-plane activation in this exampleStep-by-step explanation¶
- The UE starts TAU from the target: The source RAN does not send Handover Required. The UE uses an EPS GUTI mapped from its 5G-GUTI and indicates movement from 5GC. The TAU Request is integrity protected with the 5G security context (TS 23.502 Clause 4.11.1.5.3).
- The MME retrieves information from the AMF: It sends Context Request over N26, and the AMF verifies the included TAU Request. This diagram assumes successful verification; it does not imply that authentication can always be omitted when verification fails.
- The AMF collects transferable session information: It sends ContextRequest to the SMF+PGW-C and obtains EPS bearer contexts. If needed, the UPF+PGW-U prepares EPS-side CN tunnel information.
- Acknowledge context retrieval and update EPS path information: Following conditional authentication/security processing, the MME returns Context Acknowledge. S-GW Create Session, Modify Bearer toward SMF+PGW-C and N4 updates are distinct from advance RAN preparation in Connected Handover.
- Update the serving registration: On the MME's Update Location, HSS+UDM notifies the old AMF of 5GS-to-EPS mobility. Distinguish release of non-transferable PDU Sessions from continuity of transferable sessions. Non-3GPP-access registration is not unconditionally deleted (TS 23.502 Clause 4.11.1.3.2 steps 15–15c).
- Accept TAU: Here the UE returns Complete for an Accept containing a new GUTI. Do not treat TAU Complete as an unconditional response in every TAU (TS 23.401 Clause 5.3.3.1 step 21).
User-plane activation is a separate decision during Idle mobility
The active flag, downlink data or downlink signalling can trigger radio/S1 bearer activation during TAU. Do not infer that the UE must remain idle throughout, or that successful TAU always means data can already flow. NAS forwarding and individual unsubscribe responses are omitted from the latter part of the diagram (TS 23.401 Clause 5.3.3.1; TS 23.502 Clause 4.11.1.3.2).
When Initial Attach replaces TAU
This diagram uses TAU because transferable PDU Sessions exist. If none exist and either the UE or EPC does not support attach without PDN connectivity, Initial Attach is used. Do not assume every 5GS-to-EPS Idle move uses TAU (TS 23.502 Clause 4.11.1.3.1).
Procedure — EPS to 5GS Idle Mobility¶
This is the Idle procedure. The UE moves from EPS ECM-IDLE to NG-RAN and starts Mobility Registration Update. N26 context retrieval succeeds, and PDN Connections at the shared anchor can transfer to 5GS. Retrieval of native 5G context from an old AMF, AMF reselection, user-plane reactivation requests and pending downlink data are excluded (TS 23.502 Clause 4.11.1.3.3).
sequenceDiagram
participant UE
participant RAN as NG-RAN
participant AMF
participant MME as Old MME
participant SMF as SMF + PGW-C
participant UPF as UPF + PGW-U
participant HSS as HSS + UDM
participant SGW as Old S-GW
Note over UE: Camp on NG-RAN from ECM-IDLE<br/>Not an MME-issued Handover Command
UE->>RAN: NR RRC RRCSetupComplete<br/>NAS: Registration Request (mobility registration updating)
RAN->>AMF: NGAP Initial UE Message<br/>NAS: Registration Request
AMF->>MME: GTPv2-C Context Request<br/>EPS GUTI, TAU Request
Note over MME: Verify the embedded TAU Request
MME-->>AMF: GTPv2-C Context Response<br/>EPS MM / bearer contexts
Note over AMF: Convert EPS MM Context to 5GS MM Context
opt New authentication or related processing is required
Note over UE,AMF: Authentication and security details omitted
end
AMF->>MME: GTPv2-C Context Acknowledge
AMF->>HSS: Nudm_UECM_Registration<br/>PUT /nudm-uecm/v1/{ueId}/registrations/amf-3gpp-access
HSS-->>AMF: Nudm_UECM_Registration<br/>HTTP 201 Created / 200 OK / 204 No Content
AMF->>HSS: Nudm_SDM_Get<br/>GET /nudm-sdm/v2/{supi}/am-data
HSS-->>AMF: Nudm_SDM_Get<br/>HTTP 200 OK
AMF->>SMF: Nsmf_PDUSession_CreateSMContext<br/>POST /nsmf-pdusession/v1/sm-contexts
SMF->>UPF: PFCP Session Modification Request<br/>PDU Session CN tunnel
UPF-->>SMF: PFCP Session Modification Response
SMF-->>AMF: Nsmf_PDUSession_CreateSMContext<br/>HTTP 201 Created
HSS->>MME: Diameter Cancel Location Request
MME-->>HSS: Diameter Cancel Location Answer
opt Old-resource release conditions / timer expiry
MME->>SGW: GTPv2-C Delete Session Request<br/>Operation Indication not set
SGW-->>MME: GTPv2-C Delete Session Response
end
AMF->>RAN: NGAP Downlink NAS Transport<br/>NAS: Registration Accept
RAN->>UE: NR RRC DLInformationTransfer<br/>NAS: Registration Accept
UE->>RAN: NR RRC ULInformationTransfer<br/>NAS: Registration Complete
RAN->>AMF: NGAP Uplink NAS Transport<br/>NAS: Registration Complete
Note over UE,AMF: Check session transfer and N3 reactivation completion separatelyStep-by-step explanation¶
- Start with Registration: The UE sets registration type to Mobility Registration Update and supplies a 5G-GUTI mapped from EPS GUTI and information indicating movement from EPC. For Idle mobility, Registration Request also contains a TAU Request protected with the EPS security context for the MME to verify (TS 23.502 Clause 4.11.1.3.3 step 2).
- The AMF contacts the old MME: It derives the MME and EPS GUTI from the mapped GUTI and sends Context Request over N26. The MME verifies TAU Request and returns EPS MM/bearer contexts.
- Decide security handling and acceptance: The AMF converts the received EPS information for 5GS. Without an available native 5G security context, derivation of a mapped context or new authentication is required. On acceptance, it returns Context Acknowledge (TS 23.502 Clause 4.11.1.3.3 steps 5–8).
- Create the SM context corresponding to the existing PDN Connection: The AMF requests CreateSMContext from SMF+PGW-C, which correlates it with the existing PDN Connection and updates N4. This is not unconditional creation of a completely new PDU Session from scratch.
- Clean up the old EPS side: HSS+UDM cancels the MME registration, and old S-GW resources are released according to conditions and timers. Here Delete Session Request does not set the Operation Indication, avoiding deletion at the shared PGW. Do not assume a fixed ordering of release relative to Registration Accept (TS 23.502 Clause 4.11.1.3.3 steps 15–16a; TS 23.401 Clause 5.3.3.1).
- Check registration results and session state: Accept carries updated 5G-GUTI, Allowed NSSAI, EPS bearer status and other information; the UE updates the corresponding state. Reactivation would require N2 SM information and RAN processing, but this example does not request it. Conditional SMF registration with the UDM and PCF updates are omitted (TS 23.502 Clause 4.11.1.3.3 steps 14–18).
Do not add Context Request to post-handover Registration
TS 23.502 Clause 4.11.1.3.3 also applies to Mobility Registration following EPS-to-5GS handover, not only to Idle mobility. However, when performed as part of handover, the N26 Context Request/Response/Acknowledge in steps 5 and 8 is not performed. Do not use the same diagram for registration updates after Connected Handover and those starting from Idle.
Idle mobility with data forwarding is a separate branch
Forwarding buffered downlink data adds the procedures in TS 23.502 Clause 4.11.1.3.2A / Clause 4.11.1.3.3A. Idle does not inherently rule out data forwarding; these examples explicitly choose the no-forwarding case.
Packet Analysis¶
First identify direction and state at the start of mobility. Use N26 Forward Relocation as the reference for Connected Handover, and target-initiated Context Request for Idle Mobility, then line up N11, N4 and TAU or Registration. Do not search for Handover Command as a mandatory message in an Idle procedure. Record EBI, QFI, PDU Session ID and per-interface TEIDs separately. Device log fields and correlation methods are implementation-dependent.
Knowledge check¶
- Does reversing a 5GS-to-EPS diagram produce EPS-to-5GS? → No. SM context/bearer preparation and subsequent TAU/Registration differ.
- Does Idle Mobility also use N26 Forward Relocation? → The Idle examples here use Context Request/Response/Acknowledge.
- Does Registration after EPS-to-5GS handover send another Context Request to the old MME? → Registration as part of that procedure omits the corresponding steps 5 and 8.
- Does N26 guarantee IP continuity for all sessions? → No. Check shared-anchor, mapped-QoS and transfer-eligibility conditions.
3GPP Specification¶
- TS 23.502 V18.14.0 Clause 4.11.1.2.1 / Clause 4.11.1.2.2.1–Clause 4.11.1.2.2.3
- TS 23.502 V18.14.0 Clause 4.11.1.3.1–Clause 4.11.1.3.3 / Clause 4.11.1.5.3
- TS 23.401 V18.5.0 Clause 5.3.3.1: Conditions for TAU, session updates and old-resource release.
Next Step¶
Interworking Overview / Inter-AMF Handover / EPS Fallback / N26 / Callflow