5G SBI and AMF Service Operations

Mohammad Fazel Salimi

https://www.linkedin.com/in/mohammad-fazel-salimi1988/

In the Service Based Architecture (SBA), an NF provides multiple services for

other NFs through service-based interfaces (SBIs). Multiple service operations
are defined for each service. as we see above, every SBI has its own 3GPP
reference to describe related service, service operations, and data structure to
be considered and implemented by Telco vendors and service providers.

A service operation request or response message carries a structured object

that contains one or more IEs. The value of an IE depends on the data type of
the IE. For example, an IE of the structured data type may contain one or more
sub-IEs.
I have tried to use Namf as an example in the below figure to illustrate the
relationships between services, service operations, messages, and IEs.

The following describes the services provided by the Namf interface and the
service operations supported by each service.
Namf_Communication Service
Below service operations are supported by Namf_Communication service:

• UEContextTransfer: Used in a registration procedure. When the target

AMF receives a Registration Request message and the UE's 5G-GUTI in
this message contains the source AMF information, the target AMF
invokes this service operation of the source AMF to obtain UE contexts,
such as the UE SUPI and MM contexts.
• RegistrationStatusUpdate: Used in a registration procedure. The target
AMF invokes this service operation of the source AMF to update a UE's
registration status on the target AMF towards the source AMF. This
status reflects previous UE context transfer results for the specified UE.
• CreateUEContext: Used in an inter-NG-RAN N2-based handover
procedure. When the source AMF cannot serve a UE anymore, it invokes
this service operation of the target AMF that has been selected during a
handover. This creates UE contexts on the target AMF.
• ReleaseUEContext: Used in an inter-NG-RAN N2-based handover
cancellation procedure. When the source AMF receives a Handover
Cancel message from the (R)AN during a handover, the source AMF
invokes this service operation of the target AMF to release UE contexts
on the target AMF.
• N1N2MessageSubscribe: Used in a UE configuration update procedure.
An NF service consumer (such as the LMF or PCF) invokes this service
operation of the AMF to subscribe to notifications of a specific N1
message type (such as LPP or UPDP) or N2 information type (such as
NRPPa).
• N1N2MessageUnSubscribe: An NF service consumer (such as LMF or
PCF) invokes this service operation to instruct the AMF to stop notifying
of N1 or N2 messages of a specific type (such as LPP or UPDP).
• N1MessageNotify: Used in registration with AMF re-allocation
procedure or a UE configuration update procedure. In registration with
AMF reallocation procedure, the initial AMF obtains URI information of
the target AMF by using the network repository function (NRF), and
then invokes its own Namf_Communication_N1MessageNotify service
operation to provide the target AMF with information, such as RAN
NGAP ID, initial AMF name, RAN ID, N1 message, UE SUPI, and MM
context, and allowed NSSAI. In a UE configuration update procedure,
when the AMF receives a UPDP message from a UE, the AMF invokes its
own Namf_Communication_N1MessageNotify service operation to
notify the policy control function (PCF) of the UPDP message, as the PCF
has subscribed to N1 messages from the AMF.
• N2InfoNotify: Used in an inter-NG-RAN N2-based handover procedure
or a network-assisted positioning procedure. Inter-NG-RAN N2-based
handover procedure, target AMF invokes the
Namf_Communication_N2InfoNotify service operation to notify the
source AMF that a UE has been handed over to the target side. Network-
assisted positioning procedure when the AMF receives an NRPP
message from the 5G-AN, the AMF invokes the
Namf_Communication_N2InfoNotify service operation to notify the
LMF of the received location information.
• N1N2MessageTransfer: Used for different procedures, such as PDU
session establishment, modification, and release; network-triggered
service request; inter-NG-RAN node N2-based handover; and UE
configuration update. During PDU session establishment, the SMF
invokes this service operation of the AMF to send N1 session
management information (such as the UE IP address and QoS rules) and
N2 session management information (such as the CN tunnel
information and QoS profile) to UEs and the (R)AN through the AMF.
• N1N2TransferFailureNotification: Used for different procedures, such
as PDU session establishment, modification, and release; network-
triggered service request; inter-NG-RAN node N2-based handover; and
UE configuration update. The AMF uses this service operation to inform
an NF service consumer (such as an SMF) that it fails to send an N1
message to a UE because UE paging fails in the previously initiated
Namf_Communication_N1N2MessageTransfer procedure.
• AMFStatusChangeSubscribe: Used in an AMF-planned removal
procedure.
• AMFStatusChangeUnSubscribe: Used in an AMF-planned removal
procedure.
• AMFStatusChangeNotify: Used in an AMF-planned removal procedure.
This service operation is used to notify each NF service consumer that
has subscribed to receive notifications of AMF status changes (for
example, the AMF becomes unavailable).
• EBIAssignment: Used in a UE-requested PDU session establishment
procedure or a UE- or network-requested PDU session modification
procedure. An NF service consumer (such as the SMF) invokes this
service operation towards an NF service producer (such as the AMF) to
request the AMF to allocate EPS bearer IDs towards EPS bearers mapped
from QoS flows for an existing PDU session of a given UE.
• NonUeN2MessageTransfer: Used by an NF service consumer to transfer
N2 information to the 5G-AN through the AMF in the following
procedures:

1. Non-UE associated network assistance data obtaining

 2. Warning request transfer procedure
3. Configuration transfer procedure
4. During configuration transfer, the source AMF invokes this service
operation of the target AMF to transfer the RAN configuration
information from the source NG-RAN to the target NG-RAN through the
target AMF.

• NonUeN2InfoSubscribe: Used by an NF service consumer (such as the

LMF, CBCF, or PWS-IWF) to subscribe to the AMF for notifying non-UE-
specific N2 information of a specific type (such as NRPPa or PWS
indication).
• NonUeN2InfoUnSubscribe: Used by an NF service consumer (such as
the LMF) to unsubscribe to the AMF to stop notifying N2 information of
a specific type (such as NRPPa).
• NonUeN2InfoNotify: Use to obtain non-UE associated network
assistance data and receive PWS events from the NG-RAN. The AMF
invokes this service operation to notify an NF service consumer that it
has received non-UE N2 information from the 5G-AN.

Service Operati Operation Know 3GPP Procedure Messa Message Description

Operations on Description n ge
Semanti Cons
c umer
(s)
UEContextTra Request Provides the UE Peer TS 23.502, 4.2.2.2.1 4. new If the UE's 5G-GUTI was
nsfer / context to the AMF General AMF to included in the
Respon consumer NF. Registration Old Registration Request and
se AMF the serving AMF has
changed since last
Registration procedure,
the new AMF may invoke
the
Namf_Communication_U
EContextTransfer service
operation on the old AMF
including the complete
Registration Request NAS
message, which may be
integrity protected, as
well as the Access Type,
to request the UE's SUPI
and UE Context.
TS 23.502, 4.11.1.3.3 6a. AMF may invoke the
EPS to 5GS Mobility new Namf_Communication_U
Registration AMF to EContextTransfer to the
Procedure (Idle and Old old AMF identified by the
Connected State) AMF additional 5G-GUTI.
using N26 interface
CreateUECont Request This service Peer TS 23.502, 4.9.1.3.2 3. S- [Conditional] S-AMF to T-
ext / operation is used by AMF Inter NG-RAN node AMF to AMF:
Respon a source AMF to N2 based handover, T-AMF Namf_Communication_C
se create the UE context Preparation Phase reateUEContext Request
in a target AMF (N2 Information (Target
during handover ID, Source to Target
procedures. transparent container,
SM N2 information list,
PDU Session IDs), UE
context information
(SUPI, Service area
restriction, Allowed
NSSAI for each Access
Type if available, Tracing
Requirements, LTE M
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.
TS 23.502, 8a / Based on the received S-
4.11.1.2.2.2 EPS to 13a. NSSAI from the PGW-
5GS handover using Initial C+SMF, the Initial AMF
N26 interface, AMF to may reselect a target AMF
preparation phase Target as described in clause
AMF 5.15.5.2.1 of TS 23.501 [2],
accord and invokes
ing to Namf_Communication_C
S- reateUEContext request
NSSAI (SUPI, Target 5GAN Node
requir ID, N2 SM Information
ement received in step 7, Source
s to Target Transparent
Container, 5GS MM
Context, MME Tunnel
Endpoint Identifier for
Control Plane, MME
Address for Control
plane,PDU Session ID
and its associated S-
NSSAI of the VPLMN
value for each PDU
Session, the
corresponding S-NSSAI of
HPLMN 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.
ReleaseUECon Request This service Peer TS 23.502, 4.11.1.2.3 2. S- After receiving the
text / operation is used by AMF Handover Cancel AMF to handover cancel message
Respon a source AMF to procedure T-AMF from the source RAN, if
se release the UE the source CN node or the
context in a target target CN node is MME, it
AMF during sends a Relocation Cancel
handover cancel Request message to the
procedures. target CN node (MME or
AMF). If both the source
CN node and target CN
node are AMF, the source
AMF invokes the
Namf_Communication_R
eleaseUEContext Request
(UE Context ID,
Relocation Cancel
Indication) toward the
target AMF.
RegistrationSt Request This service Peer TS 23.502, 4.2.2.2.1 10. the new AMF informs the
atusUpdate / operation is used by AMF General new old AMF that the
Respon the consumer NF to Registration AMF to registration of the UE in
se inform the AMF that Old the new AMF is
a prior UE context AMF completed.
transfer has resulted
in the UE If the
successfully authentication/security
registering with it. procedure fails, then the
The UE context is Registration shall be
marked inactive in rejected, and the new
the AMF AMF invokes the
Namf_Communication_R
egistrationStatusUpdate
service operation with a
reject indication towards
the old AMF.

If one or more of the S-

NSSAIs used in the old
Registration Area cannot
be served in the target
Registration Area, the
new AMF determines
which PDU Session
cannot be supported in
the new Registration
Area. The new AMF
invokes the
Namf_Communication_R
egistrationStatusUpdate
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_Relea
seSMContext service
operation.
TS 23.502, 4.2.2.2.3 5. If another AMF is
Registration with Initial selected, the initial AMF
AMF re-allocation AMF to sends a reject indication
Old to the old AMF telling
AMF that the UE Registration
 procedure did not fully
complete at the initial
AMF.
N1MessageNot Subscri AMF notifies the N1 Peer TS 23.502, 4.2.2.2.3 7a. If the initial AMF, based
ify be / message received AMF Registration with Initial on local policy and
Notify from the UE to a AMF re-allocation AMF to subscription information,
destination CN NF. Target decides to forward the
AMF NAS message to the target
AMF directly, the initial
AMF invokes the
Namf_Communication_N
1MessageNotify to the
target AMF, carrying the
rerouted NAS message.
The
Namf_Communication_N
1MessageNotify 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
LMF TS 23.273, 6.3.1 17. UE If the request in step 16
Deferred 5GC-MT- to LMF can be supported, the UE
LR for periodic, (by returns a supplementary
triggered and UE AMF) services acknowledgment
available location to the LMF, which is
events transferred via the
serving AMF using the
immediate routing
identifier and delivered
to the LMF using an
Namf_Communication_N
1MessageNotify service
operation.
N1N2Message Request CN NF request to SMF TS 23.502, 4.2.3.2 5b. In the case that the SMF
Transfer / transfer downlink N1 UE Triggered UPF fails to find suitable I-
Respon and/or N2 message to Service Request Selecti UPF, the SMF may decide
se the UE and/or AN on to trigger re-
through the AMF. establishment of PDU
Session. After Service
Request procedure, SMF
sends N1 SM message to
the UE via the AMF by
invoking
Namf_Communication_N
1N2MessageTransfer
containing the cause
indicating PDU Session
re-establishment is
required for the UE.
TS 23.502, 4.2.3.3. 3. SMF SMF needs to send an N1
Network Triggered to UE message to the UE, using
Service Request (AMF) the
Namf_Communication_N
1N2MessageTransfer
service operation, and
the UE is in CM-IDLE
state
TS 23.502, 4.3.2.2. 11. SMF to AMF:
UE-requested PDU SMF to Namf_Communication_N
Session UE 1N2MessageTransfer
Establishment (AMF) (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 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
tunnel information
related with the UPFs that
terminate N3.
TS 23.502, 4.3.2.3. 3b. SMF invokes the
PDU Session SMF to Namf_Communication_N
Establishment UE 1N2MessageTransfer
authentication/auth (AMF) service operation on the
orization by a DN- AMF to transfer the DN
AAA server Request Container
information within N1
SM information sent
towards the UE.
TS 23.502, 4.3.3.2. 3b. For SMF requested
UE or network SMF to modification, the SMF
requested PDU UE invokes
Session (AMF) Namf_Communication_N
Modification 1N2MessageTransfer ([N2
SM information] (PDU
Session ID, QFI(s), QoS
Profile(s), [Alternative
QoS Profile(s)], Session-
AMBR, [CN Tunnel
Info(s)], QoS Monitoring
indication, QoS
Monitoring reporting
frequency, [TSCAI(s)]),
 N1 SM container (PDU
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))).
TS 23.502, 4.3.4.2. 3b. If the PDU Session
UE or network SMF to Release is initiated by the
requested PDU UE SMF or the PCF, the SMF
Session Release (AMF) invokes the
Namf_Communication_N
1N2MessageTransfer
service operation (N1 SM
container (PDU Session
Release Command), skip
indicator).
TS 23.502, 4.3.5.1. 2. PDU
Change of SSC Sessio
mode 2 PDU n
Session Anchor Releas
with different PDU e
Sessions proced
ure
(with
UPF1)
TS 23.502, 4.11.4.2. 3. 5GC
Handover from 5GS and
to EPC NG-
RAN
Resouc
e
release
SMSF TS 23.502, 4.2.3.3. SMSF SMSF needs to send an
Network Triggered to UE N1 message to the UE,
Service Request (AMF) using the
Namf_Communication_N
1N2MessageTransfer
service operation, and
the UE is in CM-IDLE
state.
TS 23.502, 4.13.3.3. 2c. The SMSF invokes
MO SMS over NAS SMSF Namf_Communication_N
in CM-IDLE to UE 1N2MessageTransfer
(AMF) service operation to
(CP forward SMS ack message
ack) to AMF.
6b. The SMSF forwards the
SMSF submit report to AMF by
to UE invoking
(AMF) Namf_Communication_N
(submi 1N2MessageTransfer
t service operation which
report) is forwarded to UE via
Downlink NAS transport.
If the SMSF knows the
submit report is the last
message to be transferred
for UE, the SMSF shall
include a last message
indication in the
Namf_Communication_N
1N2MessageTransfer
service operation so that
 the AMF knows no more
SMS data is to be
forwarded to UE

TS 23.502, 4.13.3.6. 5a. SMSF forward the SMS

MT SMS over NAS SMSF message to AMF by
in CM-IDLE state to UE invoking
via 3GPP access (AMF) Namf_Communication_N
(SMS 1N2MessageTransfer
body) service operation.
6c. The SMSF acknowledges
SMSF receipt of the delivery
to UE report to the UE. The
(AMF) SMSF uses
(CP Namf_Communication_N
ack for 1N2MessageTransfer
deliver service operation to send
y SMS CP ack message to
report) the AMF.
LMF TS 23.502, 4.2.3.3. LMF to The LMF triggers AMF,
Network Triggered UE(AM using the
Service Request F) Namf_Communication_N
1N2MessageTransfer
service operation, to
setup a NAS connection
with the UE and the UE is
in CM-IDLE state
N1N2Transfer Subscri The AMF uses this SMF, TS 23.502, 4.2.3.3. AMF to If the UE is not reachable
FailureNotific be / notification to SMSF Network Triggered SMF/S by AMF over both 3GPP
ation Notify inform the NF , Service Request MSF/L access and non-3GPP
service consumer LMF MF access, the AMF reports
that initiated an to the CN Requester that
earlier the UE Policy container
Namf_Communicati could not be delivered to
on_N1N2MessageTra the UE using
nsfer, that the AMF Namf_Communication_N
failed to deliver the 1N2TransferFailureNotifi
N1 message to the cation
UE as the UE failed to
respond to paging.
N2InfoSubscri Subscri An NF invokes this No The consumer NF
be be / service operation to know invokes the
Notify subscribe for the n Namf_Communication_N
delivery of cons 2InfoSubscribe service
information umer operation (CN NF ID, N2
contained in a in information type to
specific N2 message 3GPP subscribe) on the AMF.
type. R16.0
N2InfoUnSubs An NF can invoke No The consumer NF
cribe this service know invokes the
operation to n Namf_Communication_N
unsubscribe for the cons 2InfoUnSubscribe service
delivery of umer operation (CN NF ID, N2
information in information type to
contained in a 3GPP unsubscribe) on the AMF.
specific N2 message R16.0 The AMF deletes the
type. binding for the consumer
NF to for the requested
information to
unsubscribe.
N2InfoNotify The AMF uses this AMF Input, Required: AMF ID
service operation to (GUAMI), N2
notify a particular information.
event towards the NF Input, Optional:
Service Consumer Indication of the I-SMF
that has subscribed change/removal.
for the specific Output, Required: None.
information. The Output, Optional: None.
AMF receives
messages for such
events from NG-RAN
via N2.
LMF

EBIAssignmen Request The consumer NF SMF TS 23.502, 2. If the PGW-C+SMF,

t /Respon uses this service 4.11.1.4.1. EPS PGW-C determines that EPS
se operation to request bearer ID allocation + SMF bearer ID(s) needs to be
a bunch of EPS to AMF assigned to the QoS
Bearer IDs for a PDU flow(s) in the PDU
Session, and Session, PGW-C+SMF
optionally indicate to invokes
the AMF the list of Namf_Communication_E
EBI(s) to be released. BIAssignment Request.
AMFStatusCha Subscri This service SMF, TS 23.501, 5.21.2.2.2 The GUAMI(s) is used to
ngeSubscribe be / operation is used by SMSF AMF planned identify the AMF.The
Notify an NF to subscribe , removal procedure GUAMI(s) is used to
for AMF Status UDM without UDSF identify the AMF. For
Change notification. network deployment
AMFStatusCha This service SMF, without UDSF case, the
ngeUnSubscri operation is used by SMSF target AMF Name which
be an NF to unsubscribe , is to serve the user of the
for AMF Status UDM indicated GUAMI is also
Change notification. included.
AMFStatusCha Report AMF Status SMF,
ngeNotify change (e.g. AMF SMSF
unavailable and ,
Target AMF Name UDM
associated with the
indicated GUAMI)
notification to
subscribed NFs.
NonUeN2Mess Request NF Service Peer Input, Required: N2
ageTransfer /Respon Consumer requests AMF Message Container.
se to transfer a non-UE Input, Optional: TAI List,
specific message to RAT Selector (ng-eNB or
NG-RAN node(s) via gNB), Global RAN Node
N2. List, Send Write-Replace-
Warning-Indication, Send
Stop-Warning-Indication.
Output, Required: N2
Information Transfer
Result.
Output, Optional: PWS
Result Data.
CBCF TS 23.041, 9A.2.3.1 2. 2a) The CBCF sends a
Service flow for betwee Write-Replace-Warning
message transfer n Request message or a
CBCF Stop-Warning-Request
and message to the AMF
AMF using the
Namf_Communication_N
onUeN2MessageTransfer
service operation.
2b) The AMF returns a
Namf_Communication_N
onUeN2MessageTransfer
response message.
 LMF TS 23.273, 6.11.3 1. LMF The LMF invokes the
Obtaining Non-UE to AMF Namf_Communication_N
Associated Network (Netwo onUeN2MessageTransfer
Assistance Data rk service operation towards
Positio the AMF to request the
ning transfer of a Network
messa Positioning message to a
ge) NG-RAN node (gNB or ng-
eNB) in the NG-RAN. The
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.
TS 23.273, 6.14.1 1. LMF The LMF invokes the
Broadcast of to AMF Namf_Communication_N
Assistance Data by (Netwo onUeN2MessageTransfer
an LMF rk service operation towards
Assista the AMF to request the
nce transfer of a Network
Data) Assistance Data message
to an NG-RAN node (gNB
or ng-eNB) in the NG-
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.
NonUeN2Info Subscri The NF Service CBCF TS 23.041, 9A.2.3.1 1. If the CBCF supports
Subscribe be / Consumer invokes Service flow for CBCF reception of Wrtite-
Notify this service message transfer to AMF Replace-Warning
operation to Notifications and Stop-
subscribe to the Warning Notifications
delivery of non-UE then the CBCF uses the
specific information Namf_Communication_N
from the NG-RAN onUeN2InfoSubscribe
node sent via N2 to service operation to
the AMF. subscribe to these
notifications.
NonUeN2Info The NF Service CBCF
UnSubscribe Consumer invokes
this service
operation to
unsubscribe to stop
notifying non-UE
specific N2
information.
NonUeN2Info The AMF uses this LMF TS 23.273, 6.11.3 5. AMF The AMF invokes the
Notify service operation to Obtaining Non-UE to LMF Namf_Communication_N
notify a particular Associated Network onUeN2InfoNotify
event towards the NF Assistance Data service operation towards
Service Consumer the LMF indicated by the
that has subscribed routing identifier
for the specific received in step 4. The
information. The service operation
AMF receives includes the Network
messages for such Positioning message
events from NG-RAN received in step 4. Steps 1
via N2. to 5 may be repeated to
request further position
 related information from
the NG-RAN.

TS 23.273, 6.14.1 5. AMF The AMF invokes the

Broadcast of to LMF Namf_Communication_N
Assistance Data by onUeN2InfoNotify
an LMF service operation towards
the LMF indicated by the
routing identifier
received in step 4. The
service operation
includes the Network
Assistance Data Feedback
message received in step
4.
CBCF TS 23.041, 9A.2.2.3 The NonUeN2InfoNotify
Namf_Communicat service operation is used
ion_NonUeN2InfoN by AMF to notify a
otify service particular PWS event
operation 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.
When
NonUeN2InfoNotify
service operation is used
for PWS services, the N2
information consists of
all (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).

Namf_EventExposure Service
Below service operations are supported by Namf_EventExposure service:

• Subscribe: Used by an NF service consumer (such as the NEF) towards

the AMF to subscribe to an event for a specific UE, a group of UEs, or
any UE.
• Unsubscribe: Used by an NF service consumer (such as the NEF)
towards the AMF to remove an existing subscription previously created
by itself on the AMF.
 • Notify: Used by the AMF to send a notification to an NF service
consumer if certain events included in the subscription have taken
place.

Service Operatio Operation Known 3GPP Messag Message Description

Operations n Description Consumer(s Procedure e
Semantic )
Subscribe Subscribe The SMF, UDM TS 23.502: The NF consumer subscribes to the
/ Notify consumer 4.2.3.2 UE event notification by invoking
NF uses this Triggered Namf_EventExposure to the AMF.
service Service The AMF allocates an Subscription
operation to Request Correlation ID for the subscription
subscribe to 4.2.3.3 and responds to the consumer NF
or modify Network with the Subscription Correlation
event Triggered ID. UE ID identifies the UE, SUPI
reporting Service and/or GPSI. Event ID (see clause
for one UE, Request 4.15.1) identifies the events that the
a group of 4.2.5.2 UE NF consumer is interested in. The
UE(s) or Reachabilit Subscription Correlation ID is
any UE. y unique within the AMF Set.
Notification The ((set of) Event ID(s),
Request Notification Target Address (+
procedure Notification Correlation ID)) helps
4.2.5.3 UE the Event Receiving NF to co-relate
Activity a notification against a
Notification corresponding event subscription
procedure for the indicated Event ID.
4.9.1.2.2 Xn In the case that the NF consumer
based inter subscribes to the AMF on behalf of
NG-RAN other NF, the NF consumer include
handover the Notification Target
without Address(+Notification Correlation
User Plane ID) of other NF for the Event ID
function re- which is to be notified to other NF
allocation directly, and the Notification
4.9.1.3.2 Target Address(+Notification
Inter NG- Correlation ID) of itself for the
RAN node Subscription Correlation ID change
N2 based event. Each Notification Target
handover, Address(+ Notification Correlation
Preparation ID) is associated with the related
phase (set of) Event ID(s).When the
4.9.1.3.3 Subscription Correlation ID change
inter NG- due to the AMF reallocation, the
RAN node notification is sent to NF consumer
N2 based which triggers this subscription.
handover, Event filter may include "AN
execution type(s)" as part of the list of
phase parameter values to match, and it
indicates to subscribe the event per
Access Type.
Event receiving NF ID identifies
the NF that shall receive the event
reporting.
When the consumer NF needs to
modify an existing subscription
previously created by itself in the
AMF, it invokes
Namf_EventExposure_Subscribe
service operation which contains
the Subscription Correlation ID
and the new Event Filters with
Event ID to the AMF.
Unsubscrib The NF The NF consumer unsubscribes the
e consumer event notification by invoking
uses this Namf_EventExposure_Unsubscrib
service e (Subscription Correlation ID) to
operation to the AMF.
unsubscrib
e for a
specific
event for
one UE,
group of
UE(s), any
UE.
Notify Provides When the AMF detects a UE access
the and mobility event corresponding
previously to a Subscription, it invokes
subscribed Namf_EventExposure_Notify
event service operation to the NF
information consumer(s) which has subscribed
to the NF to the UE mobility event before.
Consumer The event is notified towards the
which has consumers for which the Event
subscribed filters (which may include "AN
to that type(s)") match. The Notification
event Target Address (+ Notification
before. Correlation ID) indicates to the
Event Receiving NF the specific
event notification subscription.
The event specific parameter
indicates the type of mobility event
and related information, e.g.
Registration Area Update/new
Registration Area.
The optional event specific
parameter list provides the values
that matched for generating the
event notification. The parameter
values to match are specified
during the event subscription (see
clause 5.2.2.3.2). For example if the
event type reported is "AN change",
the event specific parameter list
contains the value of the new AN.

Namf_MT Service:
Below service operations are supported by Namf_MT service:

• EnableUEReachability: Used in an MT SMS over NAS procedure in the

idle or connected state. An NF service consumer (such as the SMSF)
invokes the Namf_MT_EnableUEReachability service operation to
enable the reachability of a UE.
• ProvideDomainSelectionInfo: Used by an NF service consumer (such as
the UDM) to obtain the following UE information for terminating
domain selection of IMS voice services.

1. Indication of supporting IMS voice over PS sessions

 2. Timestamp of the last radio contact with the UE
3. Current access type and RAT type

Service Operations Operation Operation Known 3GPP Messa Message Description

Semantic Descriptio Consumer Procedu ge
n (s) re
EnableUEReachability Request/Respo The SMF TS NF (e.g. SMSF or SMF)
nse consumer 23.502, triggers AMF, using the
NF uses 4.2.3.3 Namf_MT_EnableUEReach
this Network ability service operation, to
service Triggere setup a NAS connection
operation d with the UE and the UE is in
to request Service CM-IDLE state: The trigger
enabling Request is specific to the procedure
UE and Step 4b (paging)
reachabili occurs.
ty. SMSF TS NF (e.g. SMSF or SMF)
23.502, triggers AMF, using the
4.2.3.3 Namf_MT_EnableUEReach
Network ability service operation, to
Triggere setup a NAS connection
d with the UE and the UE is in
Service CM-IDLE state: The trigger
Request is specific to the procedure
and Step 4b (paging)
occurs.
TS 4. The SMSF checks the SMS
23.502, SMSF management subscription
4.13.3.6 to data. If SMS delivery is
MT SMS AMF allowed, SMSF invokes
over Namf_MT_EnableUEReach
NAS in ability service operation to
CM- AMF. AMF pages the UE
IDLE using the procedure
state via defined in clause 4.2.3.4.
3GPP The UE responds to the
access page with Service Request
procedure.
ProvideDomainSelectio Request/Respo Provides UDM
nInfo nse the UE
informati
on for
terminati
ng
domain
selection
of IMS
voice to
the
consumer
NF.

Namf_Location Service
Below service operations are supported by Namf_Location service:

• ProvidePositioningInfo: Used in the following procedures:

 1. 5GC-MT-LR procedure
2. 5GC-MT-LR procedure without UDM query
3. Location continuity for handover of an emergency session from NG-
RAN
4. This service operation is invoked by an NF service consumer (such as
the GMLC) to request the current geodetic and optionally civic location
of a UE, and triggers the AMF to invoke services towards the LMF.

• EventNotify: This service operation is used to notify an NF service

consumer (such as the GMLC) of UE location events related to
emergency sessions in any of the following scenarios.

1. An emergency session is initiated.

2. A handover procedure takes place during an emergency session.
3. An emergency session is released.

Used in the following procedures:

1. 5GC-NI-LR procedure
2. Location continuity for handover of an emergency session from NG-
RAN

• ProvideLocationInfo: Used by an NF service consumer (such as the

UDM) to request the network-provided location information (NPLI) of a
target UE.

Service Operation Operatio Known 3GPP Message Message Description

Operations Semantic n Consume Procedur
Descripti r(s) e
on
ProvidePositionin Request/Resp Provides GMLC TS 5 / 10. 5. The GMLC invokes the
gInfo onse UE 23.273, betweenG Namf_Location_ProvidePositi
positioni 6.1.1 MLC and oningInfo service operation
ng 5GC-MT- AMF towards the AMF to request
informati LR the current location of the UE.
on to the procedur The service operation includes
consume e for the the SUPI, and client type and
r NF. regulator may include the required QoS
y location and Supported GAD shapes.
service 10. The AMF returns the
Namf_Location_ProvidePositi
oningInfo Response towards
the GMLC/LRF to return the
current location of the UE. The
service operation includes the
location estimate, its age and
accuracy and may include
information about the
positioning method.
TS 5. GMLC to The (H)GMLC or VGMLC
23.273, AMF invokes the
6.3.1 Namf_Location_ProvidePositi
Initiation oningInfo Request service
and operation to forward the
Reportin location request to the serving
g of AMF as described for step 5 in
Location clause 6.1.2 and includes the
Events (H)GMLC contact address and
LDR reference number. The
LDR reference number is
either allocated by (H-)GMLC
based on predefined rule, e.g.
operator's policy if the location
request is received in step 1a,
or allocated by NEF, if the
location request is received in
step 1b.
TS 2. GMLC to The LRF/GMLC determines
23.273, AMF the AMF by associating the
6.10.2 correlation information
5GC-MT- received from the external
LR client with other information
Procedur received previously from the
e without LMF as described in clauses
UDM 6.10.1 and 6.10.3. The GMLC
Query invokes the
Namf_Location_ProvidePositi
oningInfo service operation
towards the AMF to request
the current location of the UE.
The service operation includes
the SUPI or the PEI and an
indication of a location request
from an emergency services
client and may include the
required QoS and Supported
GAD shapes. The AMF
identifies the target UE using
the SUPI or in the case of a
USIM-less emergency session,
or non-registered USIM
emergency session, the PEI.
TS 2 / 7a. 2. At some later time, the LRF
23.273, Between may need the UE location and
6.10.3 GMLC and requests the source GMLC to
Location AMF invoke the
continuit Namf_Location_ProvidePositi
y for oningInfo service operation
Handove towards the AMF to request
r of an the current location of the UE.
Emergen The service operation includes
cy the SUPI or the PEI, the
session required QoS and an
from NG- indication of a location request
RAN from an emergency services
client.

7a. If steps 2 and 3 has

occurred, the source AMF
returns the
Namf_Location_ProvidePositi
oningInfo Response towards
the GMLC to return any
location estimate obtained for
the UE. The service operation
includes the target node
identity
EventNotify Subscribe / Provides GMLC TS 19. AMF to The AMF invokes the
Notify UE 23.273, GMLC Namf_Location_EventNotify
location 6.3.1 service operation towards the
related Initiation VGMLC for roaming, or
event and (H)GMLC for non-roaming,
informati Reportin and includes any location
on g of received at step 18 and, for
related to Location periodic or triggered location,
emergen Events a confirmation of whether or
cy not periodic or triggered
sessions location was successfully
or activated in the target UE. The
deferred VGMLC, if used, may be the
location same VGMLC used in steps 5
to the and 6 or may be a different
consume VGMLC. In the case of a
r NF. different VGMLC, the AMF
includes the HGMLC contact
address and LDR reference
number. The AMF also
includes the LMF
identification if received at
step 18. The AMF may then
release all resources for the
location request and cease
support for the procedure.
TS 5. AMF to For emergency services, the
23.273, GMLC AMF selects an GMLC based
6.10.1 on NRF query or configuration
5GC-NI- in AMF. The information
LR regarding the endpoint in the
Procedur GMLC to deliver the event
e notification, is obtained from
the NRF as specified in clause
7.1.2 of TS 23.501 [18] or from
local configuration in the
AMF. AMF invokes the
Namf_Location_EventNotify
service operation towards the
selected GMLC to notify the
GMLC of an emergency
session initiation. The service
operation includes the SUPI or
the PEI, and the GPSI if
available, the identity of the
AMF, an indication of an
emergency session and any
location obtained in step 3.
TS 7b. AMF to If steps 2 and 7a do not occur,
23.273, GMLC the source AMF may invoke
6.10.3 the
Location Namf_Location_EventNotify
continuit service operation towards the
y for source GMLC (i.e. the GMLC
Handove used in step 1) to indicate the
r of an handover. The service
Emergen operation includes the SUPI or
cy the PEI and the GPSI if
session available, an event type
from NG- indicating handover and the
RAN identity of the target node.
 ProvideLocationI Request/Resp Provides UDM Input, Required: UE
nfo onse Network Identification (SUPI).
Provided Input, Optional: 5GS Location
Location Information Request, Current
Informat Location Request, RAT type
ion Requested, Local Time Zone
(NPLI) of Request.
a target Output, Required:
UE to the Success/Failure indication.
consume Output, Optional: 5GS
r NF. Location Information (Cell
Identity, Tracking Area
Identity,
Geographical/Geodetic
Information, Current Location
Retrieved, Age of Location
Information, Current RAT
Type), Local Time Zone,
Failure Cause. In the case of
non-3GPP access: a UE local IP
address (used to reach the
N3IWF/TNGF) and optionally
UDP or TCP source port
number (if NAT is detected).
CancelLocation Request/Resp Cancels GMLC TS 4. GMLC to The (H)GMLC or VGMLC
onse an 23.273, AMF invokes the
ongoing 6.3.3 Namf_Location_CancelLocatio
deferred Cancellat n service operation to forward
location ion of the cancellation request to the
of a Reportin serving AMF and includes the
target UE g of (H)GMLC contact address,
to the Location LDR reference number and
consume Events by LMF identification if available.
r NF. an AF or
External
LCS
Client or
GMLC

Summary
to summarize what we discussed in this article, I have tried to merge all Namf
Service Operations, their NF consumers, use cases, and related 3GPP
procedure/messages in the below table.

Please try the below link for full quality:

.PNG:
https://drive.google.com/drive/folders/1CNtGBd3eAeyGyYhOda0AVSiWE0QRd
_GT?usp=sharing

.PDF:

https://drive.google.com/file/d/1VC4VrhkUu76UV1UWaQUcJDlTw7oFxQtz/vie
w?usp=sharing
Reference:
• 3GPP TS 23.501
• 3GPP TS 23.502
• 3GPP TS 29.518
• 3GPP TS 23.273
• 3GPP TS 23.041

I hope this article would be helpful to all Packet Core experts. please contact
me for any question or comment regarding this article.