GNB Interactions: 5G Standalone Access Registration: 1:Msg1: Preamble
GNB Interactions: 5G Standalone Access Registration: 1:Msg1: Preamble
GNB Interactions: 5G Standalone Access Registration: 1:Msg1: Preamble
2:Allocate Temporary C-RNTI The Temporary C-RNTI assignment will be signaled to the UE in
the Random Access Response message.
3:PDCCH DCI Format 1_0 [RA-RNTI] The RA-RNTI scrambled DCI message signals the frequency and
Frequency domain resource assignment, time resources assigned for the transmission of the Transport
Time domain resource assignment, Block containing the Random Access Response message.
Downlink MCS
4:Msg2: Random Access Response The UE detects a DCI Format 1_0 with CRC scrambled by the
Timing Advance Command, corresponding RA-RNTI and receives a transport block in a
UL Grant = { Frequency hopping flag, Msg3 PUSCH frequency+time resource corresponding PDSCH. The RAR carries the timing advance,
allocation, Uplink MCS, TPC command, CSI request}, uplink grant and the Temporary C-RNTI assignment.
Temporary C-RNTI
5:Msg3: RRCSetupRequest The RRC Setup Request is sent with the random ue-Identity and
ue-Identity, an establishment cause.
establishmentCause
6:PDCCH DCI Format 1_0 [C-RNTI] The C-RNTI scrambled DCI message signals the frequency and
Frequency domain resource assignment, time resources assigned for the transmission of the Transport
Time domain resource assignment, Block containing the RRC Setup message.
Downlink MCS
8:Msg4: RRCSetup The RRC Setup message is sent to setup SRB1 and the master
radioBearerConfig {srb-ToAddModList}, cell. The message carries the radioBearerConfig and
masterCellGroup {cellGroupId, rlc-BearerToAddModList, mac-CellGroupConfig, masterCellGroup information elements.
physicalCellGroupConfig}
9:PDCCH DCI Format 0_0 [C-RNTI] The gNB assigns uplink resource to the UE so that it can send
Frequency domain resource assignment, the RRC Setup Complete message.
Time domain resource assignment,
Uplink MCS
11:AMF Selection The gNB selects the Access and Mobility Function (AMF) for this
session.
allocate The gNB allocates a "RAN UE NGAP ID". The AMF will use this id
12:RAN UE NGAP ID to address the UE context on the gNB.
13: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, "RAN UE NGAP ID" and the "RRC Establishment Cause" are also
Requested NSSAI, UE Capability, List of PDU Sessions}, included in the message.
User Location Information,
RRC Establishment Cause,
5G-S-TMSI,
AMF Set ID
14: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
18:NAS Security Mode Command The AMF signals the selected NAS security algorithm to the UE.
Selected NAS security algorithms, The AMF also requests the IMEISV from the UE.
Replayed UE security capabilities,
IMEISV request,
ngKSI,
Additional 5G security information
19:NAS Security Mode Complete The UE signals the completion of the NAS security procedure.
NAS message container, The message contains the IMEISV.
IMEISV
20: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
UE Aggregate Maximum Bit Rate, message 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
The message also carries the "AMF UE NGAP ID", "UE Aggregate
Maximum Bit Rate", UE security capabilities and security key.
allocate Allocate the TEID that the UPF will use to send downlink data to
25:PDU Session Downlink TEID the gNB.
26: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).
27:NAS Registration Complete The UE signals the completion of the registration via the
"Registration Complete" message to the AMF.
29:Downlink Data The UPF sends the buffered data to the gNB using the Downlink
DTEID
TEID for the PDU session. All new downlink data also takes the
same path.