|
1.1
|
|
|
|
(Native) Security flow
|
|
Attach Request (eKSI=no key available, UE security capability)
| | |
This is first power on with new USIM, so UE does not have previous security context. During next power-on, current security context would be taken from USIM or non-volatile memory.
eKSI=no key available
Capability
(void context)
|
|
partial native |
current |
| |
|
Authentication Request (eKSI=KSIASME/id=y, AUTN, RAND)
| | |
UE creates a non-current partial native security context and marks it for given eKSI.
eKSI=no key available
Capability
(void context)
|
|
partial native |
current |
|
eKSI=KSIASME/y
UL count=0
DL count=0
Capability
|
|
partial native |
non-current |
|
UE sends AUTHENTICATE command to USIM application to compute RES, CK, IK for given RAND. USIM application too authenticates network with AUTN. This is first step of AKA (Authentication and Key Agreement) procedure. UE then derives KASME with input as CK, IK, SN id (MCC/MNC), and (SQN⊕AK) taken from AUTN. This is updated in non-current security context.
eKSI=no key available
Capability
(void context)
|
|
partial native |
current |
|
eKSI=KSIASME/y
UL count=0
DL count=0
Capability
KASME
|
|
partial native |
non-current |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|