Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑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…

 

6  Security featuresp. 309

The security aspects of 3G are specified in TS 33.102 and TS 33.103. This clause gives information related to security features supported by the USIM to enable the following:
  • authentication of the USIM to the network;
  • authentication of the network to the USIM;
  • authentication of the user to the USIM;
  • data confidentiality over the radio interface;
  • file access conditions;
  • conversion functions to derive GSM parameters.
Up

6.1  Authentication and key agreement procedurep. 309

This clause gives an overview of the authentication mechanism and cipher and integrity key generation which are invoked by the network. For the specification of the corresponding procedures across the USIM/ME interface see clause 5.
The mechanism achieves mutual authentication by the user and the network showing knowledge of a secret key K which is shared between and available only to the USIM and the AuC in the user's HE. In addition, the USIM and the HE keep track of counters SQNMS and SQNHE respectively to support network authentication. SQNHE is a counter in the HLR/AuC, individual for each user and SQNMS denotes the highest sequence number the USIM has ever accepted.
When the SN/VLR initiates an authentication and key agreement, it selects the next authentication vector and sends the parameters RAND and AUTN (authentication token) to the user. Each authentication token consists of the following components: a sequence number SQN, an Authentication Management Field (AMF) and a message authentication code MAC over the RAND, SQN and AMF.
The USIM checks whether AUTN can be accepted and, if so, produces a response RES which is sent back to the SN/VLR. The SN/VLR compares the received RES with XRES. If they match the SN/VLR considers the authentication and key agreement exchange to be successfully completed. The USIM also computes CK and IK. The established keys CK and IK will be used by the ME to perform ciphering and integrity functions.
A permanent secret key K is used in this procedure. This key K has a length of 128 bits or 256 bits and is stored within the USIM for use in the algorithms described below. Also more than one secret key K can be stored in the USIM. The active key to be used by the algorithms is signalled within the AMF field in the AUTN.
Up

6.2  Cryptographic Functionsp. 309

The names and parameters of the cryptographic functions supported by the USIM are defined in TS 33.102. These are:
f1:
a message authentication function for network authentication used to compute XMAC;
f1*:
a message authentication function for support to re-synchronisation with the property that no valuable information can be inferred from the function values of f1* about those of f1, ..., f5, f5* and vice versa;
f2:
a message authentication function for user authentication used to compute SRES;
f3:
a key generating function to compute the cipher key CK;
f4:
a key generating function to compute the integrity key IK;
f5:
a key generating function to compute the anonymity key AK (optional);
f5*:
a key generating function to compute AK in re-synchronisation procedures with the property that no valuable information can be inferred from the function values of f5* about those of f1, f1*, f2, ..., f5 and vice versa.
These cryptographic functions may exist either discretely or combined within the USIM.
Up

6.3  GSM Conversion Functionsp. 310

To gain GSM access, the USIM provides the conversion functions c2 and c3. These functions derive the required GSM parameters (SRES, cipher key Kc) from available 3G parameters.

6.4  User verification and file access conditionsp. 310

The security architecture as defined in TS 31.101 applies to the USIM application with the following definitions and additions.
  • The USIM application shall use a global key reference as PIN and local key reference as PIN2. For access to DFTELECOM the PIN shall be verified. Access with PIN2 is limited to the ADF(USIM).
  • The only valid values for the usage qualifier are '00' (verification requirement is not used) and '08' (user authentication knowledge based (PIN)) as defined in ISO/IEC 7816-4 [20].
Disabling of PIN2 is allowed. This is, however, not the case if PIN2 is mapped to the CHV2 of a GSM application.
Up

Up   Top   ToC