5G Standalone Access Registration AMF.

pdf

5G NodeB 5GC

gNB New AMF Old AMF SMF PCF AUSF

AMF Interactions: 5G Standalone Access Registration

Preconditions

1:NGAP Initial UE Message The gNB sends the Initial UE Message to the selected AMF. The
[NAS-PDU: Registration Request] message carries the "Registration Request" message that was
RAN UE NGAP ID,
received from the UE in the RRC Setup Complete message. The
NAS Registration Request = {Registration type, 5G-GUTI, Last TAI, Requested NSSAI, UE Capability, List of PDU Sessions}, "RAN UE NGAP ID" and the "RRC Establishment Cause" are also
User Location Information, included in the message.
RRC Establishment Cause,
5G-S-TMSI,
AMF Set ID

Obtain the UE Context from the Old AMF

2:Namf_Communication_UEContextTransfer Request Since the 5G-GUTI was included in the Registration Request and the
NAS Registration Request serving AMF has changed since last Registration procedure, the new
AMF requests context transfer from the old AMF. The complete NAS
registration message received from the UE is included in the context
request.
3:Namf_Communication_UEContextTransfer Response The Old AMF passes the AMF UE Context to the new AMF.
UE Context in AMF = {SUPI, 5G-GUTI,
PEI, UE Radio Capability, Registration
Area, ...}

4:NAS Identity Request The New AMF requests UE Identity (SUCI) from the UE via a NAS
Security header type, message.
Identity request message identity,
Identity type

5:NAS Identity Response The UE responds to the Identity Request.

Security header type,
Identity response message identity,
Mobile identity

NAS Authentication and Security

6:Nausf_UEAuthenticate_authenticate Request The AMF requests UE authentication vectors and algorithm
SUCI: Subscription Concealed Identifier information from the AUSF - Authentication Server Function

13-Feb-19 Generated with EventStudio System Designer - https://www.EventHelix.com/EventStudio/ 1

5G Standalone Access Registration AMF.pdf

5G NodeB 5GC

gNB New AMF Old AMF SMF PCF AUSF

7:Nausf_UEAuthentication_authenticate Response The response returns the master key which is used by AMF to derive
Authentication result, NAS security keys and other security key(s). The SUPI is also
SUPI returned to the AMF.

8:NAS Authentication Request Initiate the authentication procedure with the UE. Send the key
ngKSI, selector, RAND and AUTN to the UE.
RAND,
AUTN,
ABBA

9:NAS Authentication Response The UE responds to the authentication challenge.

Authentication response parameter

10:NAS Security Mode Command The AMF signals the selected NAS security algorithm to the UE. The
Selected NAS security algorithms, AMF also requests the IMEISV from the UE.
Replayed UE security capabilities,
IMEISV request,
ngKSI,
Additional 5G security information

11:NAS Security Mode Complete The UE signals the completion of the NAS security procedure. The
NAS message container, message contains the IMEISV.
IMEISV

12:Namf_Communication_RegistrationComplete_Notify Since the AMF has changed the new AMF notifies the old AMF that
the registration of the UE in the new AMF is completed.

Confirm that the UE is not blacklisted

5G-EIR

13:N5g-eir_EquipmentIdentityCheck Request Invoke the Equipment Identity Check service. This service is
PEI, provided by the 5G-EIR to check the PEI and determine whether the
SUPI PEI is blacklisted.

14:N5g-eir_EquipmentIdentityCheck Response The 5G-EIR reports that the Mobile (identified by the PEI) has not
PEI checking result been black listed.

13-Feb-19 Generated with EventStudio System Designer - https://www.EventHelix.com/EventStudio/ 2

5G Standalone Access Registration AMF.pdf

5G NodeB 5GC

gNB New AMF Old AMF SMF PCF AUSF

Register with the UDM and obtain the subscription data

UDM

15:Nudm_UEContextManagement_Registration Request Since the AMF has changed, the New AMF registers with the UDM.
PUT,
Amf 3Gpp Access Registration = { AMF Instance Id, Supported Features, PEI, dereg Callback Uri, ...}

16:Nudm_UEContextManagement_Registration Response A response code of "204 No Content" signals registration success.

204 No Content

17:Nudm_SubscriberDataManagement_Get Request The AMF retrieves the Access and Mobility Subscription data.
GET,
Requested data = Access and Mobility Subscription data

18:Nudm_SubscriberDataManagement_Get Response UDM responds with the requested data.

Access and Mobility Subscription data = {Supported Features, GPSI array, Network Slice Selection Info, ...}

19:Nudm_SubscriberDataManagement_Get Request The AMF retrieves the SMF Selection Subscription data.
GET,
Requested data = SMF Selection Subscription data

20:Nudm_SubscriberDataManagement_Get Response UDM responds with the requested data.

SMF Selection Subscription data = {Supported Features, List of S-NSSAIs and associated information}

21:Nudm_SubscriberDataManagement_Get Request The AMF retrieves the UE context in SMF data.

GET,
Requested data = UE context in SMF data

22:Nudm_SubscriberDataManagement_Get Response UDM responds with the requested data.

UE context in SMF data = {PDU Session Information, FQDNs for EPC Interworking}

23:Nudm_UEContextManagement_Deregistration_Notify The old AMF is notified that it is no longer serving the user. The
UDM sends a POST request to the callbackReference
(deregCallbackUri field in Amf3GppAccessRegistration) as provided
by the Old AMF during the registration.
24:Nsmf_PDUSession_ReleaseSMContext The Old AMF the SMF that it is no longer associated with the
SUPI, specified PDU Session.
PDU Session ID

13-Feb-19 Generated with EventStudio System Designer - https://www.EventHelix.com/EventStudio/ 3

5G Standalone Access Registration AMF.pdf

5G NodeB 5GC

gNB New AMF Old AMF SMF PCF AUSF

Update policy association with the PCF. The PCF registers for AMF events.
25:Npcf_AMPolicyControl_Create Request The AMF contacts the PCF to create a policy association and retrieve
the UE policy and/or Access and Mobility control policy.
26:Npcf_AMPolicyControl_Create Response The PCF responds with the policy association information.
Policy Association Request = { SUPI, GPSI, PEI, User Location, ...}

27:Namf_EventExpose_Subscribe Request The PCF registers for events like "Location Report", "Registration
State Report" and "Communication Failure Report".
28:Namf_EventExpose_Subscribe Response The AMF responds with "201 Created" to signal successful
201 Created, subscription.
Amf Created Event Subscription

29:Npcf_AMPolicyControl_Delete The Old AMF requests that the policy association is deleted as the
corresponding UE context is terminated.
30:Npcf_AMPolicyControl_Delete Response PCF signals the successful delete with the "204 No Content" HTTP
204 No Content response code.

Setup the User Plane Function (UPF)

31:Nsmf_PDUSession_UpdateSMContext Request Since "List Of PDU Sessions To Be Activated" was included in the
PDU Sessions, Registration Request, the New AMF initiates PDU Session
Operation Type = UP activate reactivation. The Session Management Function (SMF) is requested
to setup a new session.
32:Nsmf_PDUSession_UpdateSMContext Response The SMF informs the AMF that the Session Management context has
been updated.

33:Initial Context Setup Request The AMF initiates a session setup with the gNB. The message
[NAS-PDU: Registration Accept] typically contains the Registration Accept NAS message. The
AMF UE NGAP ID,
message carries one or more PDU Session setup requests. Each
RAN UE NGAP ID, PDU session is addressed with the "PDU Session ID". The message
UE Aggregate Maximum Bit Rate, also carries the uplink TEID for every PDU session.
GUAMI,
PDU Session Resource Setup Request List,
PDU Session ID,
PDU Session Uplink TEID,
UE IP Address,
NAS-PDU,
S-NSSAI,
PDU Session Resource Setup Request Transfer,
Allowed NSSAI,
UE Security Capabilities,
Security Key

13-Feb-19 Generated with EventStudio System Designer - https://www.EventHelix.com/EventStudio/ 4

5G Standalone Access Registration AMF.pdf

5G NodeB 5GC

gNB New AMF Old AMF SMF PCF AUSF

The message also carries the "AMF UE NGAP ID", "UE Aggregate
Maximum Bit Rate", UE security capabilities and security key.
34:Initial Context Setup Response The gNB signals the successful setup of PDU sessions. The
PDU Session Downlink TEID message also carries the Downlink TEID that should be used
(specified per PDU session).

35:NAS Registration Complete The UE signals the completion of the registration via the
"Registration Complete" message to the AMF.

Start Downlink and Uplink Data Transfer

36:Nsmf_PDUSession_UpdateSMContext Request The AMF modifies the Session Management Context based on the
Session Management Downlink TEID updates from the gNB. The Downlink TEIDs for all the PDU sessions
will be passed to the SMF.

37:Nsmf_PDUSession_UpdateSMContext Response The SMF notifies the AMF that session management context update
is complete.

13-Feb-19 Generated with EventStudio System Designer - https://www.EventHelix.com/EventStudio/ 5