Use 5G-S-TMSI in RRCSetupRequest (5.3.3.3. of TS 38.331 ) and rework of NAS RegistrationRequest
This MR includes the following implementation:
-
TS 38.331 5.3.3.3 Actions related to transmission of RRCSetupRequest message:
The UE shall set the contents of RRCSetupRequest message as follows:
1> set the ue-Identity as follows:
2> if upper layers provide a 5G-S-TMSI:
3> set the ue-Identity to ng-5G-S-TMSI-Part1;
-
Rework of RegistrationRequest:
-
NAS sends a NAS Registration Request:
- at startup
- when RRC state is set to IDLE, which means after RRC informing NAS about UEs in RRC_IDLE mode (4.3.1 of TS 38.331)
-
NAS -> RRC: RRC receives an ITTI message with NAS message that is stored in the RRC instance and later encoded as dedicatedNASMessage in RRCSetupComplete
-
send indication from NAS to RRC when GUTI is available and store 5G-S-TMSI
-
Initial implementation of Initial NAS Message: Service Request
WIP:
-
Proper NAS and security procedures after UE goes into RRC IDLE
addressing #772
Edited by Guido Casati