Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 31.102  Word version:  18.3.0

Top   Top   Up   Prev   Next
0…   3…   4…   4.2.9…   4.2.17…   4.2.26…   4.2.34…   4.2.44…   4.2.52…   4.2.60…   4.2.68…   4.2.76…   4.2.85…   4.2.93…   4.2.101…   4.2.107…   4.3…   4.4.2…   4.4.2.4…   4.4.3…   4.4.4…   4.4.5…   4.4.6…   4.4.8…   4.4.8.7…   4.4.9…   4.4.11…   4.4.11.7…   4.4.11.17…   4.4.12…   4.5…   4.6…   4.7   5…   5.2…   5.3…   5.4…   5.9…   6…   7…   7.1.2…   7.3…   A   B…   D   E…   G   H…   I…   L…   M… 
5.2 USIM security related procedures  5.2.1 Authentication algorithms computation  5.2.2 IMSI request  5.2.3 Access control information request  5.2.4 Higher Priority PLMN search period request  5.2.5 Location information  5.2.6 Cipher and Integrity key  5.2.7 Forbidden PLMN  5.2.9 User Identity Request  5.2.10 GSM Cipher key  5.2.11 GPRS Cipher key  5.2.12 Initialisation value for Hyperframe number  5.2.13 Maximum value of START  5.2.14 HPLMN selector with Access Technology request  5.2.15 Packet Switched Location information  5.2.16 Cipher and Integrity key for Packet Switched domain  5.2.17 LSA information  5.2.18 Voice Group Call Services  5.2.19 Voice Broadcast Services  5.2.20 Generic Bootstrapping architecture (Bootstrap)  5.2.21 Generic Bootstrapping architecture (NAF Derivation)  5.2.22 MSK MIKEY Message Reception  5.2.23 MTK MIKEY Message Reception  5.2.25 EHPLMN request  5.2.26 Last RPLMN Selection Indication request  5.2.27 EPS Location Information  5.2.28 EPS NAS Security Context  5.2.29 Non Access Stratum Configuration  5.2.30 PWS Configuration  5.2.31 5GS Location Information  5.2.32 5GS NAS Security Context  5.2.33 SUPI_NAI request  5.2.34 URSP request  5.2.35 Trusted non-3GPP Serving network name list request  5.2.36 Steering of roaming connected mode control information request 
...

 

5.2  USIM security related procedures  p. 281

5.2.1  Authentication algorithms computation  p. 281

The ME selects a USIM application and uses the AUTHENTICATE command (see clause 7.1.1). The response is sent to the ME (in case of the T=0 protocol when requested by a subsequent GET RESPONSE command).
After a successful AUTHENTICATE command, the ME shall perform cipher and integrity key update procedure.

5.2.2  IMSI request  p. 281

Requirement:
Service No. 130 is "not available".
Request:
The ME performs the reading procedure with EFIMSI.

5.2.3  Access control information request  p. 282

The ME performs the reading procedure with EFACC.

5.2.4  Higher Priority PLMN search period request  p. 282

The ME performs the reading procedure with EFHPPLMN.

5.2.5  Location information  p. 282

Request:
The ME performs the reading procedure with EFLOCI.
Update:
The ME performs the updating procedure with EFLOCI.
In the case when updating EFLOCI with data containing the TMSI value and the card reports the error '6581' (Memory Problem), the ME shall terminate 2G or 3G operation.

5.2.6  Cipher and Integrity key  p. 282

Request:
The ME performs the reading procedure with EFKeys.
Update:
The ME performs the updating procedure with EFKeys.

5.2.7  Forbidden PLMN  p. 282

Request:
The ME performs the reading procedure with EFFPLMN.
Update:
The ME performs the updating procedure with EFFPLMN.

5.2.8  Void

5.2.9  User Identity Request  p. 282

The ME selects a USIM and performs:
Up

5.2.10  GSM Cipher key  p. 282

Requirement:
Service No. 27 "available".
Request:
The ME performs the reading procedure with EFKc.
Update:
The ME performs the updating procedure with EFKc.

5.2.11  GPRS Cipher key  p. 282

Requirement:
Service No. 27 "available".
Request:
The ME performs the reading procedure with EFKcGPRS.
Update:
The ME performs the updating procedure with EFKcGPRS.

5.2.12  Initialisation value for Hyperframe number  p. 282

Request:
The ME performs the reading procedure with EFSTART-HFN.
Update:
The ME performs the updating procedure with EFSTART-HFN.

5.2.13  Maximum value of START  p. 283

Request:
The ME performs the reading procedure with EFTHRESHOLD.

5.2.14  HPLMN selector with Access Technology request  p. 283

Request:
The ME performs the reading procedure with EFHPLMNwAcT.

5.2.15  Packet Switched Location information  p. 283

Request:
The ME performs the reading procedure with EFPSLOCI.
Update:
The ME performs the updating procedure with EFPSLOCI.

5.2.16  Cipher and Integrity key for Packet Switched domain  p. 283

Request:
The ME performs the reading procedure with EFKeysPS.
Update:
The ME performs the updating procedure with EFKeysPS.

5.2.17  LSA information  p. 283

Requirement:
Service No. 23 "available".
Request:
The ME performs the reading procedure with EFSAI, EFSLL and its associated LSA Descriptor files.
Update:
The ME performs the updating procedure with EFSLL.

5.2.18  Voice Group Call Services  p. 283

Requirement:
Service No. 57 "available".
Voice Group Call Service
Request:
The ME performs the reading procedure with EFVGCS.
Voice Group Call Service Status
Request:
The ME performs the reading procedure with EFVGCSS.
Update:
The ME performs the updating procedure with EFVGCSS.

5.2.19  Voice Broadcast Services  p. 283

Requirement:
Service No. 58 "available".
Voice Broadcast Service
Request:
The ME performs the reading procedure with EFVBS.
Voice Broadcast Service Status
Request:
The ME performs the reading procedure with EFVBSS.
Update:
The ME performs the updating procedure with EFVBSS.

5.2.20  Generic Bootstrapping architecture (Bootstrap) |R6|  p. 284

The ME uses the AUTHENTICATE command in GBA security context (Bootstrapping Mode) (see clause 7.1.1). The response is sent to the ME.
After a successful GBA_U Procedure, the ME shall update the B-TID field and the Key Life Time field in EFGBABP.

5.2.21  Generic Bootstrapping architecture (NAF Derivation) |R6|  p. 284

The ME shall first read EFGBABP. The ME then uses the AUTHENTICATE command in GBA security context (NAF Derivation Mode) (see clause 7.1.1). The response is sent to the ME.

5.2.22  MSK MIKEY Message Reception |R6|  p. 284

The ME performs the reading of EFMUK and retrieves the Time Stamp Counter Value associated with the involved MUK. Then it proceeds with Timestamp Payload checking as described in TS 33.246.

5.2.23  MTK MIKEY Message Reception |R6|  p. 284

The ME performs the reading of EFMSK and retrieves the Time Stamp Counter Value associated with the involved MSK. Then it proceeds with Timestamp Payload checking as described in TS 33.246.

5.2.24  Void

5.2.25  EHPLMN request |R7|  p. 284

Requirement:
Service No. 71 "available".
Request:
The ME performs the reading procedure with EFEHPLMN.

5.2.26  Last RPLMN Selection Indication request |R7|  p. 284

Requirement:
Service No. 74 "available".
Request:
The ME performs the reading procedure with EFLRPLMNSI.

5.2.27  EPS Location Information |R18|  p. 284

Requirement:
Service No. 85 "available".
Request:
The ME performs the reading procedure with EFEPSLOCI.
Update:
The ME performs the updating procedure with EFEPSLOCI.

5.2.28  EPS NAS Security Context |R18|  p. 284

Requirement:
Service No. 85 "available".
Request:
The ME performs the reading procedure with EFEPSNSC.
Update:
The ME performs the updating procedure with EFEPSNSC.
In order to prevent UICC memory wear out due to excessive writing, the update of EPS NAS security context shall be according to the rules and procedures specified in TS 33.401.

5.2.29  Non Access Stratum Configuration |R10|  p. 284

Requirement:
Service No. 96 "available".
Request:
The ME performs the reading procedure with EFNASCONFIG.
For each NAS configuration parameter, a parameter provided in EFNASCONFIG shall take precedence over the corresponding parameter stored in the ME's non-volatile memory.

5.2.30  PWS Configuration |R11|  p. 285

Requirement:
Service No. 97 "available".
Request:
The ME performs the reading procedure with EFPWS.

5.2.31  5GS Location Information |R18|  p. 285

Requirement:
Service No. 122 "available".
Request:
The ME performs the reading procedure with EF5GS3GPPLOCI or with EF5GSN3GPPLOCI.
Update:
The ME performs the updating procedure with EF5GS3GPPLOCI or with EF5GSN3GPPLOCI.

5.2.32  5GS NAS Security Context |R18|  p. 285

Requirement:
Service No. 122 "available".
Request:
The ME performs the reading procedure with EF5GS3GPPNSC and EF5GSN3GPPNSC.
If service No. 136 is "available" in addition, the ME shall associate the NAS security context to the appropriate PLMN by parsing the two records and by retrieving the matching PLMN identifier of the second record.
5GS NAS Security Context in the first record shall be associated with 5G GUTI in the 5G LOCI file for the same access type (e.g. EF5GS3GPPNSC) and the 5GS NAS Security Context in the second record shall be associated with the 5G GUTI as indicated in the PLMN Identifier.
Update:
The ME performs the updating procedure with EF5GS3GPPNSC and EF5GSN3GPPNSC as described in clauses 4.4.2.1 and C.1 of TS 24.501 in Annex C.
In order to prevent UICC memory wear out due to excessive writing, the update of 5GS NAS security context shall be according to the rules and procedures specified in TS 33.501.
Up

5.2.33  SUPI_NAI request |R15|  p. 285

Requirement:
Service No. 130 is "available".
Request:
The ME performs the reading procedure with EFSUPI_NAI.

5.2.34  URSP request |R16|  p. 285

Requirement:
Service No. 132 is "available".
Request:
The ME performs the reading procedure with EFURSP.
How the ME uses the URSP rules defined in EFURSP is specified in clause 4.2.2.2 of TS 24.526.

5.2.35  Trusted non-3GPP Serving network name list request |R16|  p. 285

Requirement:
Service No. 135 is "available".
Request:
The ME performs the reading procedure with EFTN3GPPSNN.

5.2.36  Steering of roaming connected mode control information request |R17|  p. 286

Requirement:
Service No. 138 is "available".
Request:
The ME performs the reading procedure with EFSOR-CMCI as specified in TS 23.122.

Up   Top   ToC