Voice & Services¶
All Callflows / Sequence diagrams from Level 4
Scope of the diagrams
These sequence diagrams and their surrounding explanations and caveats are reproduced from the existing lessons. They include simplified and conditional examples, not every specification branch. Read the original explanations for applicability, omitted steps, implementation-dependent details, TS and clause references, and any qualifications marked as requiring verification.
VoNR — Voice over NR (5G-native voice)¶
Diagram 1 — Procedure — Call Flow¶
Original explanation, assumptions and specification references
The VoNR voice call is understood in three stages: (A) IMS PDU Session establishment → (B) SIP registration → (C) voice QoS Flow establishment at origination.
sequenceDiagram
participant UE
participant RAN as NG-RAN
participant AMF
participant SMF
participant UPF
participant PCF
participant IMS as IMS(P-CSCF=AF)
participant MEDIA as Media peer
Note over UE,IMS: (A) IMS PDU Session establishment (DNN=ims)
UE->>RAN: RRC ULInformationTransfer (NAS UL NAS Transport: PDU Session Establishment Request)
RAN->>AMF: NGAP Uplink NAS Transport (same NAS message)
AMF->>SMF: Nsmf_PDUSession CreateSMContext<br/>HTTP POST /sm-contexts
SMF-->>AMF: HTTP 201 Created (SMContextCreatedData)
SMF->>UPF: PFCP Session Establishment Request
UPF-->>SMF: PFCP Session Establishment Response
SMF->>AMF: Namf_Communication N1N2MessageTransfer<br/>HTTP POST /ue-contexts/{ueContextId}/n1-n2-messages
AMF-->>SMF: HTTP 200 OK (cause: N1_N2_TRANSFER_INITIATED)
AMF->>RAN: NGAP PDU Session Resource Setup Request (N2 SM info, NAS-PDU: 5GMM DL NAS TRANSPORT [N1 SM information: PDU SESSION ESTABLISHMENT ACCEPT])
RAN-->>UE: NR RRC DLInformationTransfer (5GMM DL NAS TRANSPORT [N1 SM information: PDU SESSION ESTABLISHMENT ACCEPT])
RAN-->>AMF: NGAP PDU Session Resource Setup Response (N2 SM info)
AMF->>SMF: Nsmf_PDUSession UpdateSMContext<br/>HTTP POST /sm-contexts/{smContextRef}/modify
SMF-->>AMF: HTTP 200 OK (SM context updated)
Note over UE,IMS: (B) SIP registration (to IMS)
UE->>IMS: SIP REGISTER (IMS signaling, over the 5QI=5 flow)
IMS-->>UE: SIP/2.0 401 Unauthorized (WWW-Authenticate challenge)
UE->>IMS: SIP REGISTER (Authorization)
IMS-->>UE: SIP/2.0 200 OK
Note over UE,IMS: (C) Origination → voice QoS Flow establishment
UE->>IMS: SIP INVITE (origination)
IMS-->>UE: SIP/2.0 100 Trying
IMS->>PCF: Npcf_PolicyAuthorization_Create<br/>HTTP POST /app-sessions (media component)
PCF-->>IMS: HTTP 201 Created (AppSessionContext)
PCF->>SMF: Npcf_SMPolicyControl_UpdateNotify<br/>HTTP POST {notificationUri}/update
SMF-->>PCF: HTTP 204 No Content
SMF->>UPF: PFCP Session Modification Request (install QoS rules)
UPF-->>SMF: PFCP Session Modification Response
SMF->>AMF: Namf_Communication N1N2MessageTransfer<br/>HTTP POST /ue-contexts/{ueContextId}/n1-n2-messages
AMF-->>SMF: HTTP 200 OK (cause: N1_N2_TRANSFER_INITIATED)
AMF->>RAN: NGAP PDU Session Resource Modify Request
RAN-->>UE: NR RRCReconfiguration (voice QoS Flow / DRB)
UE->>RAN: NR RRCReconfigurationComplete
RAN-->>AMF: NGAP PDU Session Resource Modify Response (N2 SM info)
AMF->>SMF: Nsmf_PDUSession UpdateSMContext<br/>HTTP POST /sm-contexts/{smContextRef}/modify (N2 SM info)
SMF-->>AMF: HTTP 200 OK (SM context updated)
IMS-->>UE: SIP/2.0 180 Ringing
IMS-->>UE: SIP/2.0 200 OK (INVITE)
UE->>IMS: SIP ACK
UE->>MEDIA: RTP media (voice QoS Flow)Explanation of the steps:
- (A) IMS PDU Session establishment — the UE's NAS PDU Session Establishment Request is carried to the AMF in RRC/NGAP. The AMF invokes Nsmf_PDUSession CreateSMContext (HTTP POST
/sm-contexts); the SMF configures the UPF with a PFCP Session Establishment Request/Response. N1N2MessageTransfer returns HTTP 200 OK to indicate transfer initiation. The PDU Session Establishment Accept is a 5GSM message carried in the N1 SM information of 5GMM DL NAS TRANSPORT, delivered in the NGAP Setup Request NAS-PDU and RRC DLInformationTransfer (TS 24.501 Clause 5.4.5.3.2 / Clause 6.4.1.3). NG-RAN returns the Setup Response's N2 SM information to the AMF, which returns it to the SMF with UpdateSMContext (HTTP POST/sm-contexts/{smContextRef}/modify). DNN=ims and the IMS-signaling QoS Flow (e.g. 5QI=5) depend on configuration. - (B) SIP registration — the UE sends SIP REGISTER, receives an authentication challenge, and resends REGISTER with authorization information. Registration is accepted with SIP
200 OK. - (C) Origination and voice QoS Flow establishment — upon the UE's SIP INVITE, the P-CSCF acts as an AF and invokes N5 Npcf_PolicyAuthorization_Create (HTTP POST
/app-sessions). The PCF notifies the SMF over N7; the SMF applies the QoS Flow through a PFCP Session Modification Request/Response and N1/N2 updates. After RRCReconfiguration/Complete, the RAN returns NGAP PDU Session Resource Modify Response, and the AMF returns its N2 SM information to the SMF with UpdateSMContext. SIP responses and ACK establish the call; RTP voice flows between the UE and media anchor/peer, not through the P-CSCF.
Terminating (MT) calls are symmetric too
In a terminating (Mobile Terminated) call, a SIP INVITE from the other party reaches the UE from the IMS, and the voice QoS Flow establishment of (C) occurs likewise. If the UE is CM-IDLE, it is first woken up with Paging → Service Request before the call is established.
Emergency — emergency calls (emergency calls in the 5GC)¶
Diagram 1 — Procedure — Call Flow¶
Original explanation, assumptions and specification references
Understand an emergency call in three stages: (A) Emergency Registration → (B) emergency PDU Session establishment → (C) IMS emergency call establishment (to the PSAP). Pay attention to the differences from VoNR (acceptance of unregistered UEs, skipping authentication, and priority).
sequenceDiagram
participant UE
participant RAN as NG-RAN
participant AMF
participant AUSF
participant SMF
participant PCF
participant UPF
participant IMS as IMS(emergency P-CSCF=AF)
participant PSAP
Note over UE,AMF: (A) Emergency Registration (unregistered UEs may also be accepted)
Note over UE,RAN: Initial NR RRC connection before NAS Registration Request
UE->>RAN: RRCSetupRequest
RAN-->>UE: RRCSetup
UE->>RAN: NR RRCSetupComplete (dedicatedNAS-Message: Registration Request, registration type = Emergency)
RAN->>AMF: NGAP Initial UE Message (NAS Registration Request)
alt When authentication is possible
AMF->>AUSF: Nausf_UEAuthentication HTTP POST /ue-authentications
AUSF-->>AMF: HTTP 201 Created (UEAuthenticationCtx)
AMF->>RAN: NGAP Downlink NAS Transport (NAS Authentication Request)
RAN->>UE: RRC DLInformationTransfer (NAS Authentication Request)
UE->>RAN: RRC ULInformationTransfer (NAS Authentication Response)
RAN->>AMF: NGAP Uplink NAS Transport (NAS Authentication Response)
AMF->>AUSF: Nausf_UEAuthentication HTTP PUT /ue-authentications/{authCtxId}/5g-aka-confirmation
AUSF-->>AMF: HTTP 200 OK (authentication result)
else When authentication is not possible (regulatory/implementation-dependent)
Note over AMF,AUSF: Skip authentication → may continue with NIA0/NEA0 (Null)
end
AMF->>RAN: NGAP Downlink NAS Transport (NAS Registration Accept)
RAN-->>UE: RRC DLInformationTransfer (NAS Registration Accept)
UE->>RAN: RRC ULInformationTransfer (NAS Registration Complete)
RAN->>AMF: NGAP Uplink NAS Transport (same NAS message)
Note over UE,SMF: (B) Emergency PDU Session establishment (emergency DNN)
UE->>RAN: RRC ULInformationTransfer (NAS UL NAS Transport: PDU Session Establishment Request)
RAN->>AMF: NGAP Uplink NAS Transport (same NAS message)
AMF->>SMF: Nsmf_PDUSession CreateSMContext<br/>HTTP POST /sm-contexts
SMF-->>AMF: HTTP 201 Created (SMContextCreatedData)
SMF->>PCF: Npcf_SMPolicyControl_Create<br/>HTTP POST /sm-policies
PCF-->>SMF: HTTP 201 Created (priority policy)
SMF->>UPF: PFCP Session Establishment Request
UPF-->>SMF: PFCP Session Establishment Response
SMF->>AMF: Namf_Communication N1N2MessageTransfer<br/>HTTP POST /ue-contexts/{ueContextId}/n1-n2-messages
AMF-->>SMF: HTTP 200 OK (cause: N1_N2_TRANSFER_INITIATED)
AMF->>RAN: NGAP PDU Session Resource Setup Request (N2 SM info, NAS-PDU: 5GMM DL NAS TRANSPORT [N1 SM information: PDU SESSION ESTABLISHMENT ACCEPT])
RAN-->>UE: RRC DLInformationTransfer (5GMM DL NAS TRANSPORT [N1 SM information: PDU SESSION ESTABLISHMENT ACCEPT])
RAN-->>AMF: NGAP PDU Session Resource Setup Response (N2 SM info)
AMF->>SMF: Nsmf_PDUSession UpdateSMContext<br/>HTTP POST /sm-contexts/{smContextRef}/modify (N2 SM info)
SMF-->>AMF: HTTP 200 OK (SM context updated)
Note over UE,PSAP: (C) IMS emergency call establishment
UE->>IMS: SIP INVITE (emergency service)
IMS-->>UE: SIP/2.0 100 Trying
IMS->>PCF: Npcf_PolicyAuthorization_Create<br/>HTTP POST /app-sessions (emergency media)
PCF-->>IMS: HTTP 201 Created (AppSessionContext)
PCF->>SMF: Npcf_SMPolicyControl_UpdateNotify<br/>HTTP POST {notificationUri}/update
SMF-->>PCF: HTTP 204 No Content
SMF->>UPF: PFCP Session Modification Request (priority QoS rules)
UPF-->>SMF: PFCP Session Modification Response
IMS->>PSAP: SIP INVITE (emergency call routing)
PSAP-->>IMS: SIP/2.0 100 Trying
PSAP-->>IMS: SIP/2.0 180 Ringing
PSAP-->>IMS: SIP/2.0 200 OK (INVITE)
IMS-->>UE: SIP/2.0 200 OK (INVITE)
UE->>IMS: SIP ACK
Note over UE,PSAP: RTP media path is outside this signaling diagramExplanation of the procedure:
- (A) Emergency Registration — the UE sends an Emergency registration-type Registration Request in the dedicatedNAS-Message of RRCSetupComplete after initial NR RRC setup, and NGAP Initial UE Message carries it to the AMF. When authentication is possible, the AMF creates a Nausf_UEAuthentication context and runs NAS Authentication Request/Response plus 5G-AKA confirmation. Whether registration is accepted and authentication can be omitted depends on applicable conditions; this does not apply uniformly to every unregistered UE.
- (B) Emergency PDU Session establishment — the UE's NAS request is carried over RRC/NGAP, and the AMF invokes Nsmf_PDUSession CreateSMContext. The SMF obtains PCF policy with Npcf_SMPolicyControl_Create (HTTP POST
/sm-policies, TS 29.512 Clause 4.2.2) and configures the session with a PFCP Session Establishment Request/Response. The PDU Session Establishment Accept is a 5GSM message carried in the N1 SM information of 5GMM DL NAS TRANSPORT, delivered in the NGAP Setup Request NAS-PDU and RRC DLInformationTransfer (TS 24.501 Clause 5.4.5.3.2 / Clause 6.4.1.3). After the HTTP 200 response to N1N2MessageTransfer, the AMF returns the N2 SM information in the NG-RAN Setup Response to the SMF with UpdateSMContext. Priority and emergency-DNN handling follow applicable specifications and configuration. - (C) IMS emergency call establishment — the UE sends SIP INVITE, and IMS/P-CSCF invokes Npcf_PolicyAuthorization_Create (HTTP POST
/app-sessions) as an AF QoS request. The PCF notifies the SMF of the changed SM Policy with Npcf_SMPolicyControl_UpdateNotify (HTTP POST{notificationUri}/update, TS 29.512 Clause 4.2.3.2), after which the SMF applies QoS rules using PFCP Session Modification Request/Response. IMS routes the call to the PSAP using SIP; the RTP media path is outside this signaling diagram. The voice QoS Flow mechanism is the same as (C) in VoNR.
Callback (a call-back from the PSAP)
For an emergency call, it may be required that the PSAP can originate a call back to the UE (callback) after disconnection. For this reason, care is taken to maintain the emergency registration state for a certain period, etc. (the details and the retention time are regulatory/implementation-dependent; to be confirmed).
EPS Fallback — The Mechanism for Completing Voice Calls in Areas Where VoNR Is Not Offered¶
Diagram 1 — Procedure — Call Flow¶
Original explanation, assumptions and specification references
EPS Fallback is understood in four stages: (A) a voice QoS Flow request arises → (B) the NG-RAN determines no VoNR support → (C) transition to 4G(EPS) → (D) VoLTE completion.
sequenceDiagram
participant UE
participant RAN as NG-RAN
participant AMF
participant SMF
participant PCF
participant MME as MME(4G)
participant ENB as eNB(4G/LTE)
participant UPF
participant IMS
Note over UE,PCF: (A) Voice call → voice QoS Flow (5QI=1) request (common with VoNR)
UE->>IMS: SIP INVITE
IMS-->>UE: SIP/2.0 100 Trying
IMS->>PCF: Npcf_PolicyAuthorization_Create<br/>HTTP POST /app-sessions (voice media)
PCF-->>IMS: HTTP 201 Created (AppSessionContext)
PCF->>SMF: Npcf_SMPolicyControl_UpdateNotify<br/>HTTP POST {notificationUri}/update
SMF-->>PCF: HTTP 204 No Content
SMF->>UPF: PFCP Session Modification Request (voice QoS rules)
UPF-->>SMF: PFCP Session Modification Response
SMF->>AMF: Namf_Communication N1N2MessageTransfer<br/>HTTP POST /ue-contexts/{ueContextId}/n1-n2-messages
AMF-->>SMF: HTTP 200 OK (cause: N1_N2_TRANSFER_INITIATED)
AMF->>RAN: NGAP PDU Session Resource Modify Request
RAN-->>AMF: NGAP PDU Session Resource Modify Response
Note over RAN: (B) Select EPS Fallback when VoNR is unsupported
alt EPS handover applies
RAN->>AMF: NGAP Handover Required
AMF->>MME: N26 Forward Relocation Request
MME->>ENB: S1AP Handover Request
ENB-->>MME: S1AP Handover Request Acknowledge
MME-->>AMF: N26 Forward Relocation Response
AMF->>RAN: NGAP Handover Command
RAN->>UE: NR RRC MobilityFromNRCommand (E-UTRA)
else EPS redirection applies
RAN->>UE: NR RRCRelease (redirectedCarrierInfo: E-UTRA)
Note over UE,ENB: UE reselects/reconnects on EPS and performs applicable Attach/TAU
end
IMS-->>UE: SIP/2.0 180 Ringing
IMS-->>UE: SIP/2.0 200 OK (INVITE)
UE->>IMS: SIP ACK
Note over UE,ENB: (C)/(D) EPS bearer and IMS session continuation are outside this diagramExplanation of the procedure:
- (A) A voice QoS Flow request arises — SIP INVITE triggers the P-CSCF's N5 Npcf_PolicyAuthorization_Create (HTTP POST
/app-sessions). The PCF sends an N7 SM Policy notification; the SMF uses PFCP Session Modification Request/Response and Namf_Communication N1N2MessageTransfer (HTTP 200 OK,N1_N2_TRANSFER_INITIATED) to convey N2 SM information to NG-RAN. - (B) Determination of no VoNR support — NG-RAN processes the PDU Session Resource Modify procedure and selects EPS Fallback based on radio/configuration conditions. This is a local procedure decision, shown as a Note rather than a fabricated packet.
- (C) Transition to EPS — for applicable EPS handover, NGAP Handover Required, N26 Forward Relocation Request, S1AP Handover Request/Acknowledge, N26 Forward Relocation Response, and NGAP Handover Command are shown, followed by NR RRC MobilityFromNRCommand to the UE (TS 38.331 Clause 5.4.3.3). Redirection uses NR RRCRelease to E-UTRA (TS 38.331 Clause 5.3.8.3); subsequent Attach/TAU depends on UE EPS state.
- (D) VoLTE continuation — EPS bearer setup and IMS session continuation depend on conditions and subsequent procedures, so individual packets are not specified here. Call control remains in IMS.
The same branch for incoming (MT) calls
Even for an incoming (Mobile Terminated) call, a 5QI=1 QoS Flow request arises from the voice call from the other party, and if the cell does not support VoNR, EPS Fallback is triggered similarly. If the UE is idle, it is first paged (Paging, etc.) before proceeding to the voice call establishment.
Emergency Services Fallback — Moving an Emergency Call to E-UTRA¶
Diagram 1 — Procedure — Call Flow¶
Original explanation, assumptions and specification references
The diagram shows two alternative EPS-target examples from NR: handover using N26 and redirection. It assumes that support was indicated to the UE and that the selected mobility procedure is applicable. The separate 5GC-connected E-UTRA branch is covered above, not through the MME below. Preparation responses, NAS/radio forwarding, session establishment and IMS nodes are abbreviated (TS 23.502 Clause 4.13.4.2 / Clause 4.11.1.2.1).
sequenceDiagram
participant UE
participant RAN as NG-RAN
participant AMF
participant MME as MME (EPC)
participant ENB as eNB / EPS-connected E-UTRA
Note over UE,AMF: (A) IMS emergency request pending#59; fallback support indicated
alt UE is CM-IDLE
UE->>RAN: RRCSetupRequest
RAN-->>UE: RRCSetup
UE->>RAN: RRCSetupComplete (dedicatedNAS-Message: Service Request)
RAN->>AMF: NGAP Initial UE Message (NAS Service Request)
else UE is CM-CONNECTED
UE->>RAN: RRC ULInformationTransfer (NAS Service Request)
RAN->>AMF: NGAP Uplink NAS Transport (NAS Service Request)
end
Note over RAN: Service type = emergency services fallback
AMF->>RAN: NGAP UE Context Modification Request<br/>(Emergency Fallback Indicator, Target CN = EPC)
RAN-->>AMF: NGAP UE Context Modification Response
Note over RAN: (B) NG-RAN selects an applicable EPS mobility procedure
alt NG-RAN selects EPS handover
RAN->>AMF: NGAP Handover Required
AMF->>MME: N26 Forward Relocation Request
MME->>ENB: S1AP Handover Request
ENB-->>MME: S1AP Handover Request Acknowledge
MME-->>AMF: N26 Forward Relocation Response
AMF->>RAN: NGAP Handover Command
RAN->>UE: NR RRC MobilityFromNRCommand (E-UTRA)
UE->>ENB: LTE RRCConnectionReconfigurationComplete
ENB->>MME: S1AP Handover Notify
MME->>AMF: N26 Forward Relocation Complete Notification
AMF-->>MME: N26 Forward Relocation Complete Acknowledge
else NG-RAN selects EPS redirection
RAN->>UE: NR RRCRelease (redirectedCarrierInfo: E-UTRA, target CN = EPC)
Note over UE,ENB: UE reselects/reconnects on EPS and performs applicable Attach/TAU
end
Note over UE,ENB: (C)/(D) EPS emergency PDN connection and IMS emergency session are outside this diagramStep-by-step explanation¶
- (A) Request emergency-services fallback: An IMS emergency request is pending, and fallback support has been indicated for the current RAT/TA. The UE sends Service Request with service type
emergency services fallback. In CM-IDLE, NAS is carried by RRCSetupComplete/NGAP Initial UE Message; in CM-CONNECTED, by RRC ULInformationTransfer/NGAP Uplink NAS Transport. It need not wait for a voice-QoS establishment request (TS 23.502 Clause 4.13.4.2 steps 1–3). - (B) The 5GC requests fallback from NG-RAN: The AMF indicates Emergency Fallback in NGAP UE Context Modification Request and includes Target CN when needed; NG-RAN responds with UE Context Modification Response. When initiating redirection for successfully authenticated UEs, the AMF supplies the security context (TS 23.502 Clause 4.13.4.2 step 4).
- (C) Execute the selected EPS mobility procedure: NG-RAN follows the Target CN indication or configuration. The EPS handover example shows N2 Handover Required, N26 Forward Relocation Request, S1AP Handover Request/Acknowledge, N26 Forward Relocation Response, NGAP Handover Command, NR RRC MobilityFromNRCommand (TS 38.331 Clause 5.4.3.3), and completion notifications in this order. The redirection example uses NR RRCRelease to indicate E-UTRA and Target CN=EPC (TS 38.331 Clause 5.3.8.3); subsequent Attach/TAU depends on applicable conditions (TS 23.502 Clause 4.13.4.2 step 5). This is not a branch selected solely by N26 availability.
- (D) Establish the emergency session at the target: Emergency PDN connection and IMS emergency-session establishment are outside this diagram. It shows the move to EPS and does not specify later NAS messages or guarantee call success (TS 23.502 Clause 4.13.4.2 step 6).
Formal NAS terminology
The message shown is Service Request, with Service type emergency services fallback. It is not a distinct message named "Emergency Service Request", and service type "emergency services" is a different value (TS 24.501 Clause 5.6.1 / Clause 9.11.3.50). Other NAS conditions can involve Registration procedures; do not substitute a generic emergency Registration for the specific request in this example.
Do not assume the same entry path for every UE state
This example depends on fallback support previously indicated in Registration Accept. It does not establish that every unregistered or limited-service UE can immediately send this Service Request. Check emergency registration and domain-selection conditions separately in Emergency (TS 23.502 Clause 4.13.4.1 / Clause 4.13.4.2; TS 24.501 Clause 5.5.1 / Clause 5.6.1).
SMS over NAS — Short Messages Carried on NAS¶
Diagram 1 — (A) Negotiation at Registration¶
Original explanation, assumptions and specification references
sequenceDiagram
participant UE
participant RAN as NG-RAN
participant AMF
participant UDM
participant SMSF
Note over UE,SMSF: Negotiate SMS over NAS availability during Registration
UE->>RAN: RRCSetupRequest
RAN-->>UE: RRCSetup
UE->>RAN: RRCSetupComplete (dedicatedNAS-Message: Registration Request, SMS over NAS capability)
RAN->>AMF: NGAP Initial UE Message (NAS Registration Request)
AMF->>UDM: Nudm_SDM_GetSmsData<br/>HTTP GET /{supi}/sms-data
UDM-->>AMF: HTTP 200 OK (SmsSubscriptionData)
AMF->>SMSF: Nsmsf_SMService SMServiceActivation<br/>HTTP PUT /ue-contexts/{supi}
SMSF-->>AMF: HTTP 201 Created / 204 No Content
SMSF->>UDM: Nudm_SDM_GetSmsData<br/>HTTP GET /{supi}/sms-data
UDM-->>SMSF: HTTP 200 OK (SmsSubscriptionData)
SMSF->>UDM: Nudm_UECM_Registration<br/>HTTP PUT /{ueId}/registrations/smsf-3gpp-access
UDM-->>SMSF: HTTP 201 Created / 200 OK / 204 No Content
AMF->>RAN: NGAP Downlink NAS Transport (NAS Registration Accept)
RAN-->>UE: RRC DLInformationTransfer (NAS Registration Accept)
UE->>RAN: RRC ULInformationTransfer (NAS Registration Complete)
RAN->>AMF: NGAP Uplink NAS Transport (NAS Registration Complete)Explanation of the steps:
- The UE indicates SMS over NAS capability in the Registration Request, carried from RRCSetupComplete to the AMF in NGAP Initial UE Message.
- The AMF retrieves SMS subscription data with Nudm_SDM_GetSmsData (HTTP GET
/{supi}/sms-data). - The AMF activates the SMSF with Nsmsf_SMService SMServiceActivation (HTTP PUT
/ue-contexts/{supi}). The SMSF retrieves SMS data from the UDM and registers as the SMSF using Nudm_UECM Registration. - The AMF returns Registration Accept in NGAP Downlink NAS Transport/RRC DLInformationTransfer, and the UE's Registration Complete returns over RRC/NGAP.
Diagram 2 — (B) MO-SMS (send: UE→network)¶
Original explanation, assumptions and specification references
sequenceDiagram
participant UE
participant RAN as NG-RAN
participant AMF
participant SMSF
participant SMSC as SMSC/IP-SM-GW
UE->>RAN: RRC ULInformationTransfer (5GMM UL NAS TRANSPORT [Payload container type: SMS, SMS CP-DATA with RP-DATA/SMS-SUBMIT])
RAN->>AMF: NGAP Uplink NAS Transport (same NAS message)
AMF->>SMSF: Nsmsf_SMService UplinkSMS<br/>HTTP POST /ue-contexts/{supi}/sendsms (SMS CP-DATA)
SMSF-->>AMF: HTTP 200 OK (SmsRecordDeliveryData)
SMSF->>AMF: Namf_Communication N1N2MessageTransfer<br/>HTTP POST /ue-contexts/{ueContextId}/n1-n2-messages (N1: SMS CP-ACK)
AMF-->>SMSF: HTTP 200 OK (cause: N1_N2_TRANSFER_INITIATED)
AMF->>RAN: NGAP Downlink NAS Transport (5GMM DL NAS TRANSPORT [Payload container type: SMS, SMS CP-ACK])
RAN-->>UE: RRC DLInformationTransfer (same NAS message)
Note over SMSF,SMSC: SMS-SC delivery processing is outside this Nsmsf and NAS exchange
SMSF->>AMF: Namf_Communication N1N2MessageTransfer<br/>HTTP POST /ue-contexts/{ueContextId}/n1-n2-messages (N1: SMS CP-DATA, payload: Submit Report)
AMF-->>SMSF: HTTP 200 OK (cause: N1_N2_TRANSFER_INITIATED)
AMF->>RAN: NGAP Downlink NAS Transport (5GMM DL NAS TRANSPORT [Payload container type: SMS, SMS CP-DATA, payload: Submit Report])
RAN-->>UE: RRC DLInformationTransfer (5GMM DL NAS TRANSPORT [Payload container type: SMS, SMS CP-DATA, payload: Submit Report])
UE->>RAN: RRC ULInformationTransfer (5GMM UL NAS TRANSPORT [Payload container type: SMS, SMS CP-ACK])
RAN->>AMF: NGAP Uplink NAS Transport (same NAS message)
AMF->>SMSF: Nsmsf_SMService UplinkSMS<br/>HTTP POST /ue-contexts/{supi}/sendsms (SMS CP-ACK)
SMSF-->>AMF: HTTP 200 OK (SmsRecordDeliveryData)Explanation of the steps: This is a CM-CONNECTED MO-SMS example. The UE sends SMS CP-DATA (containing RP-DATA/SMS-SUBMIT) in 5GMM UL NAS TRANSPORT, and the AMF forwards it to the SMSF with Nsmsf_SMService_UplinkSMS (HTTP POST /ue-contexts/{supi}/sendsms). The HTTP 200 response with SmsRecordDeliveryData is the Nsmsf API response, not the SMS CP-ACK (TS 29.540 Clause 5.2.2.4.2). Separately, the SMSF returns CP-ACK through Namf_Communication_N1N2MessageTransfer and the AMF carries it to the UE in 5GMM DL NAS TRANSPORT (TS 23.502 Clause 4.13.3.3 steps 2c–2d). After external SMS-SC processing, the SMSF carries the Submit Report in SMS CP-DATA over the same N1N2 path; the UE's ensuing CP-ACK returns through Nsmsf UplinkSMS (steps 3–5, 6a–6d). TS 29.540 Clause 6.1.6.4.2 specifies that SMS Payload Information may encode CP-DATA, CP-ACK, or CP-ERROR. The Submit Report's internal RP/TP structure and external SMS-SC transfer are not expanded here. A CM-IDLE UE first performs UE Triggered Service Request (step 1).
Diagram 3 — (C) MT-SMS (receive: network→UE)¶
Original explanation, assumptions and specification references
sequenceDiagram
participant SMSC as SMS-GMSC/IP-SM-GW
participant SMSF
participant AMF
participant RAN as NG-RAN
participant UE
SMSC->>SMSF: Nsmsf_SMService SendMtSMS<br/>HTTP POST /ue-contexts/{supi}/send-mt-sms
SMSF->>AMF: Namf_MT_EnableUEReachability<br/>HTTP PUT /ue-contexts/{ueContextId}/ue-reachind
alt UE is CM-IDLE
AMF->>RAN: NGAP Paging
RAN-->>UE: RRC Paging
UE->>RAN: RRCSetupRequest
RAN-->>UE: RRCSetup
UE->>RAN: RRCSetupComplete (dedicatedNAS-Message: Service Request)
RAN->>AMF: NGAP Initial UE Message (NAS Service Request)
else UE is CM-CONNECTED
Note over AMF,SMSF: The AMF responds to EnableUEReachability immediately
end
AMF-->>SMSF: HTTP 200 OK (EnableUeReachabilityRspData)
SMSF->>AMF: Namf_Communication N1N2MessageTransfer<br/>HTTP POST /ue-contexts/{ueContextId}/n1-n2-messages (N1: SMS CP-DATA)
AMF-->>SMSF: HTTP 200 OK (cause: N1_N2_TRANSFER_INITIATED)
AMF->>RAN: NGAP Downlink NAS Transport (5GMM DL NAS TRANSPORT [Payload container type: SMS, SMS CP-DATA])
RAN-->>UE: RRC DLInformationTransfer (same NAS message)
UE->>RAN: RRC ULInformationTransfer (5GMM UL NAS TRANSPORT [Payload container type: SMS, SMS CP-ACK])
RAN->>AMF: NGAP Uplink NAS Transport (same NAS message)
AMF->>SMSF: Nsmsf_SMService UplinkSMS<br/>HTTP POST /ue-contexts/{supi}/sendsms (SMS CP-ACK)
SMSF-->>AMF: HTTP 200 OK (SmsRecordDeliveryData)
UE->>RAN: RRC ULInformationTransfer (5GMM UL NAS TRANSPORT [Payload container type: SMS, SMS CP-DATA, payload: UE Delivery Report])
RAN->>AMF: NGAP Uplink NAS Transport (5GMM UL NAS TRANSPORT [Payload container type: SMS, SMS CP-DATA, payload: UE Delivery Report])
AMF->>SMSF: Nsmsf_SMService UplinkSMS<br/>HTTP POST /ue-contexts/{supi}/sendsms (SMS CP-DATA, payload: UE Delivery Report)
SMSF-->>AMF: HTTP 200 OK (SmsRecordDeliveryData)
SMSF->>AMF: Namf_Communication N1N2MessageTransfer<br/>HTTP POST /ue-contexts/{ueContextId}/n1-n2-messages (N1: SMS CP-ACK for Delivery Report)
AMF-->>SMSF: HTTP 200 OK (cause: N1_N2_TRANSFER_INITIATED)
AMF->>RAN: NGAP Downlink NAS Transport (5GMM DL NAS TRANSPORT [Payload container type: SMS, SMS CP-ACK])
RAN-->>UE: RRC DLInformationTransfer (same NAS message)
SMSF-->>SMSC: HTTP 200 OK (SmsDeliveryData)Explanation of the steps: This MT-SMS example covers CM-IDLE and CM-CONNECTED UEs. The SMSF first invokes Namf_MT_EnableUEReachability (HTTP PUT /ue-contexts/{ueContextId}/ue-reachind); for CM-IDLE, paging and Service Request precede its HTTP 200 response, while for CM-CONNECTED the AMF responds immediately (TS 29.518 Clause 5.4.2.2.1, TS 23.502 Clause 4.13.3.6). Once reachable, the SMSF transfers SMS CP-DATA with N1N2MessageTransfer, receiving HTTP 200 (N1_N2_TRANSFER_INITIATED) (TS 29.518 Clause 5.2.2.3.1.1). The UE's CP-ACK is forwarded to the SMSF using a separate Nsmsf_SMService_UplinkSMS request (HTTP POST /ue-contexts/{supi}/sendsms); the subsequent UE Delivery Report is carried in SMS CP-DATA and forwarded with the same operation. The SMSF acknowledges that report to the UE with another N1N2MessageTransfer carrying CP-ACK (TS 23.502 Clause 4.13.3.6 steps 5c–5d and 6a–6d, TS 29.540 Clause 5.2.2.4.2, Clause 6.1.6.4.2). CP-ACK is an SMS CP-layer acknowledgement, distinct from the later Delivery Report. The successful SendMtSMS response contains SmsDeliveryData with the MT-SMS Delivery Report (TS 29.540 Clause 5.2.2.5.2). The RRC_INACTIVE-specific variant and external SMS-SC exchange are not expanded here.
The biggest difference between MO and MT is Paging
Sending (MO) starts from a state where the UE can already send NAS (connected), so Paging is unnecessary. Receiving (MT) is an incoming from the network, and if the UE is idle it must be woken first. This is the same structure as VoNR's MT call.
Network Slicing¶
Diagram 1 — Procedure — Call Flow¶
Original explanation, assumptions and specification references
This is the heart of this page. The flow of slice selection is shown as a Mermaid sequenceDiagram. The basis is TS 23.502 (registration / slice selection procedures), TS 23.501 Clause 5.15 (Network Slicing; section number to be confirmed) / Clause 6.2.14 (NSSF), TS 24.501 (NAS NSSAI), TS 29.531 (Nnssf), and TS 38.413 (NGAP S-NSSAI). Because slice selection in many cases happens as part of Initial Registration, here we focus on slice selection (for the full registration procedure, see registration).
Precondition: slice selection happens inside the Registration procedure
From the UE presenting the Requested NSSAI to accepting the Allowed NSSAI is not an independent procedure; it takes place inside Initial Registration. This diagram extracts the slice selection (Requested → Allowed, NSSF query when needed) part of it. The operation names and ordering follow TS 23.502, but the fine details are version- and implementation-dependent, and some are to be confirmed.
sequenceDiagram
autonumber
participant UE
participant RAN as NG-RAN / gNB
participant AMF
participant NSSF
participant UDM
participant SMF
UE->>RAN: RRCSetupRequest
RAN-->>UE: RRCSetup
UE->>RAN: RRCSetupComplete (dedicatedNAS-Message: Registration Request, Requested NSSAI)
RAN->>AMF: NGAP Initial UE Message (NAS Registration Request)
AMF->>UDM: Nudm_SDM_GetAmData<br/>HTTP GET /{supi}/am-data
UDM-->>AMF: HTTP 200 OK (AccessAndMobilitySubscriptionData)
Note over AMF: Evaluate Requested NSSAI, subscription/mapping, and serving-network support
opt When the AMF cannot resolve on its own (conditional)
AMF->>NSSF: Nnssf_NSSelection_NSSelectionGet<br/>HTTP GET /network-slice-information (selection parameters)
NSSF-->>AMF: HTTP 200 OK (Allowed NSSAI / candidate AMF information)
end
opt When AMF reselection is needed (conditional)
Note over AMF: Relocate to the appropriate AMF (AMF reselection)
end
AMF->>RAN: NGAP Downlink NAS Transport (NAS Registration Accept, Allowed NSSAI)
RAN-->>UE: RRC DLInformationTransfer (NAS Registration Accept)
UE->>RAN: RRC ULInformationTransfer (NAS Registration Complete)
RAN->>AMF: NGAP Uplink NAS Transport (NAS Registration Complete)
Note over UE,AMF: Thereafter, slices can be used within the Allowed NSSAI
Note over UE,SMF: [At PDU Session time] Subsequent in-slice NF selection (overview)
UE->>RAN: RRC ULInformationTransfer (NAS UL NAS Transport: PDU Session Establishment Request, S-NSSAI + DNN)
RAN->>AMF: NGAP Uplink NAS Transport (same NAS message)
Note over AMF: Selecting an SMF by S-NSSAI+DNN is a local AMF selection action
AMF->>SMF: Nsmf_PDUSession CreateSMContext<br/>HTTP POST /sm-contexts (N1 SM message)
SMF-->>AMF: HTTP 201 Created (SMContextCreatedData)
Note over AMF,SMF: For the session-establishment continuation, see the PDU Session chapterStep-by-step explanation (numbers correspond to the diagram above)¶
1-4. UE→(R)AN→AMF: The UE's Registration Request is carried from RRCSetupComplete to the AMF in NGAP Initial UE Message and includes the Requested NSSAI.
5-6. AMF↔UDM: The AMF retrieves subscription data with Nudm_SDM_GetAmData (HTTP GET /{supi}/am-data) and evaluates the Requested NSSAI, subscription/mapping information, and serving-network support.
7-8. (conditional) AMF↔NSSF: If the AMF cannot resolve the slice on its own, it invokes Nnssf_NSSelection with HTTP GET /network-slice-information (N22) and obtains Allowed NSSAI etc. (TS 29.531, TS 23.501 Clause 6.2.14).
(conditional) AMF reselection: If the current AMF cannot accommodate the requested slices, the UE may be relocated to an appropriate AMF. This is a procedure decision, not a message arrow here.
9-12. Registration accept: Registration Accept is sent in NGAP Downlink NAS Transport/RRC DLInformationTransfer, and Registration Complete returns over RRC/NGAP.
13-16. (At PDU Session time) SMF selection: The UE's request carrying S-NSSAI + DNN is sent to the AMF over RRC/NGAP. The AMF invokes Nsmf_PDUSession CreateSMContext (HTTP POST /sm-contexts) at the selected SMF and receives HTTP 201 Created. See PDU Session Establishment for subsequent steps.
The NSSF query and AMF reselection are conditional
The query to the NSSF (steps 5-6) and AMF reselection (step 7) are omitted or vary depending on conditions such as whether the AMF can resolve on its own and whether the current AMF can accommodate the requested slices. Because the relevant procedure in 3GPP TS 23.502 includes many optional/conditional steps, the specific omission conditions need to be verified individually against the spec (some are to be confirmed).
References: TS 23.501 Clause 5.15 (Network Slicing; section number to be confirmed) / Clause 6.2.14 (NSSF), TS 23.502 (the registration procedure involving slice selection), TS 24.501 (NAS NSSAI), TS 29.531 (Nnssf), TS 38.413 (NGAP S-NSSAI).