Service Name Service Operations
If the UE's 5G-GUTI was included in the Registration Request and the serving AMF has changed since last
UEContextTransfer
CreateUEContext
ReleaseUEContext
RegistrationStatusUpdate
N1MessageNotify
N1N2MessageTransfer
Namf_Communication
N1N2TransferFailureNotification
N2InfoSubscribe
N2InfoUnSubscribe
N2InfoNotify
EBIAssignment
AMFStatusChangeSubscribe
AMFStatusChangeUnSubscribe
AMFStatusChangeNotify
NonUeN2MessageTransfer
NonUeN2InfoSubscribe
NonUeN2InfoUnSubscribe
NonUeN2InfoNotify
Operation Semantic Operation Description
Provides the UE context to
Request/ Response
the consumer NF.
This service operation is
used by a source AMF to
Request/ Response create the UE context in a
target AMF during handover
procedures.
This service operation is used
by a source AMF to release the
Request/ Response UE context in a target AMF
during handover cancel
procedures.
This service operation is
used by the consumer NF to
inform the AMF that a prior
UE context transfer has
Request/ Response
resulted in the UE
successfully registering with
it. The UE context is marked
inactive in the AMF
AMF notifies the N1
Subscribe / Notify message received from the
UE to a destination CN NF.
CN NF request to transfer
downlink N1 and/or N2
Request/ Response
message to the UE and/or
AN through the AMF.
The AMF uses this
notification to inform the NF
service consumer that
initiated an earlier
Namf_Communication_N1N
Subscribe / Notify
2MessageTransfer, that the
AMF failed to deliver the N1
message to the UE as the
UE failed to respond to
paging.
An NF invokes this service
operation to subscribe for
the delivery of information
contained in a specific N2
message type.
An NF can invoke this
service operation to
unsubscribe for the delivery
of information contained in a
Subscribe / Notify specific N2 message type.
The AMF uses this service
operation to notify a
particular event towards the
NF Service Consumer that
AMF
has subscribed for the
specific information. The
AMF receives messages for
such events from NG-RAN
via N2.
The consumer NF uses this
service operation to request
a bunch of EPS Bearer IDs
Request/Response for a PDU Session, and SMF
optionally indicate to the
AMF the list of EBI(s) to be
released.
This service operation is
used by an NF to subscribe
for AMF Status Change
notification.
This service operation is
used by an NF to
unsubscribe for AMF Status
Subscribe / Notify Change notification.
Report AMF Status change
(e.g. AMF unavailable and
Target AMF Name
associated with the indicated
GUAMI) notification to
subscribed NFs.
NF Service Consumer
requests to transfer a non-
Request/Response
UE specific message to NG-
RAN node(s) via N2.
The NF Service Consumer
invokes this service
operation to subscribe to the
delivery of non-UE specific
information from the NG-
RAN node sent via N2 to the
AMF.
The NF Service Consumer
invokes this service
operation to unsubscribe to
stop notifying non-UE
specific N2 information.
Subscribe / Notify
The AMF uses this service LMF
operation to notify a
particular event towards the
NF Service Consumer that
has subscribed for the
specific information. The
AMF receives messages for
such events from NG-RAN
via N2. CBCF
Known Consumer(s) 3GPP Procedure Message Message Description
Registration procedure, the new AMF may invoke the Namf_Communication_UEContextTransfer service
TS 23.502, 4.2.2.2.1 General Registration 4. new AMF to Old AMF
operation on the old AMF including the complete Registration Request NAS message, which may be integrity
Peer AMF protected, as well as the Access Type, to request the UE's SUPI and UE Context.
TS 23.502, 4.11.1.3.3 EPS to 5GS Mobility Registration AMF may invoke the Namf_Communication_UEContextTransfer to the old AMF identified by the additional 5G-
6a. new AMF to Old AMF
Procedure (Idle and Connected State) using N26 interface GUTI.
[Conditional] S-AMF to T-AMF: Namf_Communication_CreateUEContext Request (N2 Information (Target ID,
Source to Target transparent container, SM N2 information list, PDU Session IDs), UE context information
TS 23.502, 4.9.1.3.2 Inter NG-RAN node N2 based handover, (SUPI, Service area restriction, Allowed NSSAI for each Access Type if available, Tracing Requirements, LTE M
3. S-AMF to T-AMF
Preparation Phase Indication, the list of PDU Session IDs along with the corresponding SMF information and the corresponding S-
NSSAI(s), PCF ID(s), DNN, UE Radio Capability ID and UE Radio Capability Information). If the subscription
information includes Tracing Requirements, the old AMF provides the target AMF with Tracing Requirements.
Peer AMF Based on the received S-NSSAI from the PGW-C+SMF, the Initial AMF may reselect a target AMF as described
in clause 5.15.5.2.1 of TS 23.501 [2], and invokes Namf_Communication_CreateUEContext request (SUPI,
Target 5GAN Node ID, N2 SM Information received in step 7, Source to Target Transparent Container, 5GS MM
8a / 13a. Initial AMF to Target
TS 23.502, 4.11.1.2.2.2 EPS to 5GS handover using N26 Context, MME Tunnel Endpoint Identifier for Control Plane, MME Address for Control plane,PDU Session ID and
AMF according to S-NSSAI
interface, preparation phase its associated S-NSSAI of the VPLMN value for each PDU Session, the corresponding S-NSSAI of HPLMN
requirements
value for home routed PDU Session(s), PGW-C+SMF ID of each PDU Session, default V-SMF ID and SM
Context ID of each PDU Session, allocated EBIs of each PDU Session, Allowed NSSAI received from NSSF) to
the selected target AMF.
After receiving the handover cancel message from the source RAN, if the source CN node or the target CN node
is MME, it sends a Relocation Cancel Request message to the target CN node (MME or AMF). If both the source
Peer AMF TS 23.502, 4.11.1.2.3 Handover Cancel procedure 2. S-AMF to T-AMF
CN node and target CN node are AMF, the source AMF invokes the Namf_Communication_ReleaseUEContext
Request (UE Context ID, Relocation Cancel Indication) toward the target AMF.
the new AMF informs the old AMF that the registration of the UE in the new AMF is completed.
If the authentication/security procedure fails, then the Registration shall be rejected, and the new AMF invokes the
Namf_Communication_RegistrationStatusUpdate service operation with a reject indication towards the old AMF.
TS 23.502, 4.2.2.2.1 General Registration 10. new AMF to Old AMF If one or more of the S-NSSAIs used in the old Registration Area cannot be served in the target Registration
Peer AMF Area, the new AMF determines which PDU Session cannot be supported in the new Registration Area. The new
AMF invokes the Namf_Communication_RegistrationStatusUpdate service operation including the rejected PDU
Session ID towards the old AMF. Then the new AMF modifies the PDU Session Status correspondingly. The old
AMF informs the corresponding SMF(s) to locally release the UE's SM context by invoking the
Nsmf_PDUSession_ReleaseSMContext service operation.
If another AMF is selected, the initial AMF sends a reject indication to the old AMF telling that the UE Registration
TS 23.502, 4.2.2.2.3 Registration with AMF re-allocation 5. Initial AMF to Old AMF
procedure did not fully complete at the initial AMF.
If the initial AMF, based on local policy and subscription information, decides to forward the NAS message to the
target AMF directly, the initial AMF invokes the Namf_Communication_N1MessageNotify to the target AMF,
Peer AMF TS 23.502, 4.2.2.2.3 Registration with AMF re-allocation 7a. Initial AMF to Target AMF carrying the rerouted NAS message. The Namf_Communication_N1MessageNotify service operation includes
the information enabling (R)AN to identify the N2 terminating point, and the full Registration Request message,
and the UE's SUPI and MM Context if available
If the request in step 16 can be supported, the UE returns a supplementary services acknowledgment to the LMF,
TS 23.273, 6.3.1 Deferred 5GC-MT-LR for periodic, triggered
LMF 17. UE to LMF (by AMF) which is transferred via the serving AMF using the immediate routing identifier and delivered to the LMF using an
and UE available location events
Namf_Communication_N1MessageNotify service operation.
In the case that the SMF fails to find suitable I-UPF, the SMF may decide to trigger re-establishment of PDU
Session. After Service Request procedure, SMF sends N1 SM message to the UE via the AMF by invoking
TS 23.502, 4.2.3.2 UE Triggered Service Request 5b. UPF Selection
Namf_Communication_N1N2MessageTransfer containing the cause indicating PDU Session re-establishment is
required for the UE.
SMF needs to send an N1 message to the UE, using the Namf_Communication_N1N2MessageTransfer service
TS 23.502, 4.2.3.3. Network Triggered Service Request 3. SMF to UE (AMF)
operation, and the UE is in CM-IDLE state
SMF to AMF: Namf_Communication_N1N2MessageTransfer (PDU Session ID, N2 SM information (PDU
Session ID, QFI(s), QoS Profile(s), CN Tunnel Info, S-NSSAI from the Allowed NSSAI, Session-AMBR, PDU
Session Type, User Plane Security Enforcement information, UE Integrity Protection Maximum Data Rate, RSN),
N1 SM container (PDU Session Establishment Accept ([QoS Rule(s) and QoS Flow level QoS parameters if
needed for the QoS Flow(s) associated with the QoS rule(s)], selected SSC mode, S-NSSAI(s), UE Requested
TS 23.502, 4.3.2.2. UE-requested PDU Session Establishment 11. SMF to UE (AMF)
DNN, allocated IPv4 address, interface identifier, Session-AMBR, selected PDU Session Type, [Reflective QoS
Timer] (if available), [P-CSCF address(es)], [Control Plane Only indicator], [Header Compression Configuration],
[Always-on PDU Session Granted], [Small Data Rate Control parameters], [Small Data Rate Control Status],
[Serving PLMN Rate Control]))). If multiple UPFs are used for the PDU Session, the CN Tunnel Info contains
SMF tunnel information related with the UPFs that terminate N3.
TS 23.502, 4.3.2.3. PDU Session Establishment SMF invokes the Namf_Communication_N1N2MessageTransfer service operation on the AMF to transfer the
3b. SMF to UE (AMF)
authentication/authorization by a DN-AAA server DN Request Container information within N1 SM information sent towards the UE.
For SMF requested modification, the SMF invokes Namf_Communication_N1N2MessageTransfer ([N2 SM
information] (PDU Session ID, QFI(s), QoS Profile(s), [Alternative QoS Profile(s)], Session-AMBR, [CN Tunnel
TS 23.502, 4.3.3.2. UE or network requested PDU Session Info(s)], QoS Monitoring indication, QoS Monitoring reporting frequency, [TSCAI(s)]), N1 SM container (PDU
3b. SMF to UE (AMF)
Modification Session Modification Command (PDU Session ID, QoS rule(s), QoS Flow level QoS parameters if needed for
the QoS Flow(s) associated with the QoS rule(s), QoS rule operation and QoS Flow level QoS parameters
operation, Session-AMBR))).
If the PDU Session Release is initiated by the SMF or the PCF, the SMF invokes the
TS 23.502, 4.3.4.2. UE or network requested PDU Session
3b. SMF to UE (AMF) Namf_Communication_N1N2MessageTransfer service operation (N1 SM container (PDU Session Release
Release
Command), skip indicator).
TS 23.502, 4.3.5.1. Change of SSC mode 2 PDU Session 2. PDU Session Release
Anchor with different PDU Sessions procedure (with UPF1)
3. 5GC and NG-RAN Resouce
TS 23.502, 4.11.4.2. Handover from 5GS to EPC
release
SMSF needs to send an N1 message to the UE, using the Namf_Communication_N1N2MessageTransfer
TS 23.502, 4.2.3.3. Network Triggered Service Request SMSF to UE (AMF)
service operation, and the UE is in CM-IDLE state.
2c. SMSF to UE (AMF) (CP The SMSF invokes Namf_Communication_N1N2MessageTransfer service operation to forward SMS ack
ack) message to AMF.
The SMSF forwards the submit report to AMF by invoking Namf_Communication_N1N2MessageTransfer
TS 23.502, 4.13.3.3. MO SMS over NAS in CM-IDLE service operation which is forwarded to UE via Downlink NAS transport. If the SMSF knows the submit report is
6b. SMSF to UE (AMF) (submit
SMSF the last message to be transferred for UE, the SMSF shall include a last message indication in the
report)
Namf_Communication_N1N2MessageTransfer service operation so that the AMF knows no more SMS data is
to be forwarded to UE
5a. SMSF to UE (AMF) (SMS SMSF forward the SMS message to AMF by invoking Namf_Communication_N1N2MessageTransfer service
body) operation.
TS 23.502, 4.13.3.6. MT SMS over NAS in CM-IDLE state via
3GPP access 6c. SMSF to UE (AMF) (CP The SMSF acknowledges receipt of the delivery report to the UE. The SMSF uses
ack for delivery report) Namf_Communication_N1N2MessageTransfer service operation to send SMS CP ack message to the AMF.
The LMF triggers AMF, using the Namf_Communication_N1N2MessageTransfer service operation, to setup a
LMF TS 23.502, 4.2.3.3. Network Triggered Service Request LMF to UE(AMF)
NAS connection with the UE and the UE is in CM-IDLE state
If the UE is not reachable by AMF over both 3GPP access and non-3GPP access, the AMF reports to the CN
SMF, SMSF, LMF TS 23.502, 4.2.3.3. Network Triggered Service Request AMF to SMF/SMSF/LMF Requester that the UE Policy container could not be delivered to the UE using
Namf_Communication_N1N2TransferFailureNotification
No known consumer in The consumer NF invokes the Namf_Communication_N2InfoSubscribe service operation (CN NF ID, N2
3GPP R16.0 information type to subscribe) on the AMF.
The consumer NF invokes the Namf_Communication_N2InfoUnSubscribe service operation (CN NF ID, N2
No known consumer in
information type to unsubscribe) on the AMF. The AMF deletes the binding for the consumer NF to for the
3GPP R16.0 requested information to unsubscribe.
Input, Required: AMF ID (GUAMI), N2 information.
Input, Optional: Indication of the I-SMF change/removal.
Output, Required: None.
Output, Optional: None.
LMF
If the PGW-C+SMF, determines that EPS bearer ID(s) needs to be assigned to the QoS flow(s) in the PDU
TS 23.502, 4.11.1.4.1. EPS bearer ID allocation 2. PGW-C + SMF to AMF
Session, PGW-C+SMF invokes Namf_Communication_EBIAssignment Request.
SMF, SMSF, UDM
SMF, SMSF, UDM The GUAMI(s) is used to identify the AMF.The GUAMI(s) is used to identify the AMF. For network
TS 23.501, 5.21.2.2.2 AMF planned removal procedure without
deployment without UDSF case, the target AMF Name which is to serve the user of the indicated GUAMI is also
UDSF
included.
SMF, SMSF, UDM
Input, Required: N2 Message Container.
Input, Optional: TAI List, RAT Selector (ng-eNB or gNB), Global RAN Node List, Send Write-Replace-Warning-
Peer AMF Indication, Send Stop-Warning-Indication.
Output, Required: N2 Information Transfer Result.
Output, Optional: PWS Result Data.
2a) The CBCF sends a Write-Replace-Warning Request message or a Stop-Warning-Request message to the
CBCF TS 23.041, 9A.2.3.1Service flow for message transfer 2. between CBCF and AMF AMF using the Namf_Communication_NonUeN2MessageTransfer service operation.
2b) The AMF returns a Namf_Communication_NonUeN2MessageTransfer response message.
The LMF invokes the Namf_Communication_NonUeN2MessageTransfer service operation towards the AMF to
TS 23.273, 6.11.3 Obtaining Non-UE Associated Network 1. LMF to AMF (Network request the transfer of a Network Positioning message to a NG-RAN node (gNB or ng-eNB) in the NG-RAN. The
Assistance Data Positioning message) service operation includes the Network Positioning message and the target NG-RAN node identity. The Network
Positioning message may request position related information from the NG-RAN.
LMF
The LMF invokes the Namf_Communication_NonUeN2MessageTransfer service operation towards the AMF to
1. LMF to AMF (Network request the transfer of a Network Assistance Data message to an NG-RAN node (gNB or ng-eNB) in the NG-
TS 23.273, 6.14.1 Broadcast of Assistance Data by an LMF
Assistance Data) RAN. The service operation includes the Network Assistance Data message and the target NG-RAN node
identity. The Network Assistance Data message includes assistance data which may be optionally ciphered.
If the CBCF supports reception of Wrtite-Replace-Warning Notifications and Stop-Warning Notifications then the
CBCF TS 23.041, 9A.2.3.1Service flow for message transfer 1. CBCF to AMF CBCF uses the Namf_Communication_NonUeN2InfoSubscribe service operation to subscribe to these
notifications.
CBCF
The AMF invokes the Namf_Communication_NonUeN2InfoNotify service operation towards the LMF indicated
TS 23.273, 6.11.3 Obtaining Non-UE Associated Network by the routing identifier received in step 4. The service operation includes the Network Positioning message
5. AMF to LMF
Assistance Data received in step 4. Steps 1 to 5 may be repeated to request further position related information from the NG-
RAN.
The AMF invokes the Namf_Communication_NonUeN2InfoNotify service operation towards the LMF indicated
TS 23.273, 6.14.1 Broadcast of Assistance Data by an LMF 5. AMF to LMF by the routing identifier received in step 4. The service operation includes the Network Assistance Data
Feedback message received in step 4.
The NonUeN2InfoNotify service operation is used by AMF to notify a particular PWS event towards the NF
Service Consumer (e.g. CBCF or PWS-IWF) that has subscribed for the specific information. The AMF receives
messages for such PWS events from NG-RAN via N2.
TS 23.041, 9A.2.2.3
When NonUeN2InfoNotify service operation is used for PWS services, the N2 information consists of all
Namf_Communication_NonUeN2InfoNotify service operation
(mandatory and optionally) available information provided via N2 in the Write-Replace Warning Indication (see
subclause 9.2.30), a Stop Warning Indication (see subclause 9.2.31), a PWS Restart Indication (see subclause
9.2.32) or a PWS Failure Indication (see subclause 9.2.33).