3GPP TS 33.105 V4.1.0 (2001-06) : 3rd Generation Partnership

3GPP TS 33.105 V4.1.0 (2001-06)
Technical Specification
3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
3G Security;
Cryptographic Algorithm Requirements
(Release 4)
The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP.
The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organisational Partners’ Publications Offices.
Release 4
2
3GPP TS 33.105 V4.1.0 (2001-06)
Keywords
UMTS, Security, Algorithm
3GPP
Postal address
3GPP support office address
650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Internet
http://www.3gpp.org
Copyright Notification
No part may be reproduced except as authorised by written permission.
The copyright and the foregoing restrictions extend to reproduction in all media.
© 2001, 3GPP Organizational Partners (ARIB, CWTS, ETSI, T1, TTA,TTC).
All rights reserved.
3GPP
Release 4
3
3GPP TS 33.105 V4.1.0 (2001-06)
Contents
Foreword............................................................................................................................................................ 5
1
Scope ....................................................................................................................................................... 6
2
References ............................................................................................................................................... 6
3
Definitions, symbols, abbreviations and conventions ............................................................................. 6
3.1
3.2
3.3
3.4
Definitions................................................................................................................................................................6
Symbols....................................................................................................................................................................7
Abbreviations ...........................................................................................................................................................7
Conventions .............................................................................................................................................................7
4
General algorithm requirements .............................................................................................................. 8
4.1
4.2
Resilience .................................................................................................................................................................8
World-wide availability and use ..............................................................................................................................8
5
Functional algorithm requirements.......................................................................................................... 8
5.1
Authentication and key agreement ...........................................................................................................................8
5.1.1
Overview ............................................................................................................................................................8
5.1.1.1
Generation of quintets in the AuC ......................................................................................................................8
5.1.1.2
Authentication and key derivation in the USIM.................................................................................................9
5.1.1.3
Generation of re-synchronisation token in the USIM.........................................................................................9
5.1.1.4
Re-synchronisation in the HLR/AuC................................................................................................................10
5.1.2
Use....................................................................................................................................................................10
5.1.3
Allocation .........................................................................................................................................................10
5.1.4
Extent of standardisation ..................................................................................................................................11
5.1.5
Implementation and operational considerations ...............................................................................................11
5.1.6
Type of algorithm .............................................................................................................................................11
5.1.6.1
f0
11
5.1.6.2
f1
11
5.1.6.3
f1* 11
5.1.6.4
f2
11
5.1.6.5
f3
11
5.1.6.6
f4
12
5.1.6.7
f5
12
5.1.6.8
f5* 12
5.1.7
Interface............................................................................................................................................................12
5.1.7.1
K
12
5.1.7.2
RAND12
5.1.7.3
SQN 12
5.1.7.4
AMF 13
5.1.7.6
MAC-A (equivalent for XMAC-A)..................................................................................................................13
5.1.7.7
MAC-S (equivalent for XMAC-S) ...................................................................................................................13
5.1.7.8
RES (or XRES) ................................................................................................................................................13
5.1.7.9
CK 13
5.1.7.10
IK 13
5.1.7.11
AK...............................................................................................................................................................14
5.2
Data confidentiality................................................................................................................................................14
5.2.1
Overview ..........................................................................................................................................................14
5.2.2
Use....................................................................................................................................................................14
5.2.3
Allocation .........................................................................................................................................................15
5.2.4
Extent of standardisation ..................................................................................................................................15
5.2.5
Implementation and operational considerations ...............................................................................................15
5.2.6
Type of algorithm .............................................................................................................................................15
5.2.7
Interfaces to the algorithm................................................................................................................................16
5.2.7.1
CK 16
5.2.7.2
COUNT-C ........................................................................................................................................................16
5.2.7.3
BEARER ..........................................................................................................................................................16
5.2.7.4
DIRECTION ....................................................................................................................................................16
3GPP
Release 4
4
3GPP TS 33.105 V4.1.0 (2001-06)
5.2.7.5
LENGTH ..........................................................................................................................................................17
5.2.7.6
KEYSTREAM..................................................................................................................................................17
5.2.7.7
PLAINTEXT ....................................................................................................................................................17
5.2.7.8
CIPHERTEXT..................................................................................................................................................17
5.3
Data integrity..........................................................................................................................................................18
5.3.1
Overview ..........................................................................................................................................................18
5.3.2
Use....................................................................................................................................................................18
5.3.3
Allocation .........................................................................................................................................................18
5.3.4
Extent of standardisation ..................................................................................................................................18
5.3.5
Implementation and operational considerations ...............................................................................................18
5.3.6
Type of algorithm .............................................................................................................................................18
5.3.7
Interface............................................................................................................................................................19
5.3.7.1
IK
19
5.3.7.2
COUNT-I .........................................................................................................................................................19
5.3.7.3
FRESH .............................................................................................................................................................19
5.3.7.4
MESSAGE .......................................................................................................................................................19
5.3.7.5
DIRECTION ....................................................................................................................................................19
5.3.7.6
MAC-I (and equivalently XMAC-I).................................................................................................................19
6
Use of the algorithm specifications ....................................................................................................... 20
6.1
6.2
6.3
6.4
6.5
Ownership ..............................................................................................................................................................20
Design authority .....................................................................................................................................................20
Users of the specification .......................................................................................................................................20
Licensing................................................................................................................................................................20
Management of the specification ...........................................................................................................................20
7
Algorithm specification and test data requirements .............................................................................. 20
7.1
7.2
7.3
7.4
Specification of the algorithm ................................................................................................................................21
Implementors test data ...........................................................................................................................................21
Design conformance test data ................................................................................................................................21
Format and handling of deliverables ......................................................................................................................21
8
Quality assurance requirements............................................................................................................. 21
8.1
8.2
8.3
Quality assurance for the algorithm .......................................................................................................................21
Quality assurance for the specification and test data..............................................................................................22
Design and evaluation report..................................................................................................................................22
9
Summary of the design authority deliverables ...................................................................................... 22
Annex A (informative):
Void ................................................................................................................ 23
Annex B (informative):
Change history .............................................................................................. 24
3GPP
Release 4
5
3GPP TS 33.105 V4.1.0 (2001-06)
Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
3GPP
Release 4
1
6
3GPP TS 33.105 V4.1.0 (2001-06)
Scope
This specification constitutes a requirements specification for the security functions which may be used to provide the
network access security features defined in [1].
The specification covers the intended use of the functions, the technical requirements on the functions and the
requirements as regards standardization.
For those functions that require standardization, it also covers the intended use of the algorithm specification, the
requirements on test data, and quality assurance requirements on both the algorithm and its documentation.
2
References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1]
3G TS 33.102: "3rd Generation Partnership Project (3GPP); Technical Specification Group (TSG)
SA; 3G Security; Security Architecture".
[2]
Wassenaar Arrangement, December 1998.
[3]
ISO/IEC 9797: "Information technology - Security techniques - Data integrity mechanism using a
cryptographic check function employing a block cipher algorithm".
3
Definitions, symbols, abbreviations and conventions
3.1
Definitions
For the purposes of the present document, the following definitions apply:
Confidentiality: The property that information is not made available or disclosed to unauthorised individuals, entities
or processes.
Data integrity: The property that data has not been altered in an unauthorised manner.
Data origin authentication: The corroboration that the source of data received is as claimed.
Entity authentication: The provision of assurance of the claimed identity of an entity.
Key freshness: A key is fresh if it can be guaranteed to be new, as opposed to an old key being reused through actions
of either an adversary or authorised party.
3GPP
Release 4
3.2
7
3GPP TS 33.105 V4.1.0 (2001-06)
Symbols
For the purposes of the present document, the following symbols apply:
||
⊕
f0
f1
f1*
f2
f3
f4
f5
f5*
f8
f9
3.3
Concatenation
Exclusive or
random challenge generating function
network authentication function
the re-synchronisation message authentication function;
user authentication function
cipher key derivation function
integrity key derivation function
anonymity key derivation function for normal operation
anonymity key derivation function for re-synchronisation
UMTS encryption algorithm
UMTS integrity algorithm
Abbreviations
For the purposes of the present document, the following abbreviations apply:
3GPP
AK
AuC
AUTN
COUNT-C
COUNT-I
CK
IK
IMSI
IPR
MAC
MAC
MAC-A
MAC-I
PDU
RAND
RES
RLC
RNC
SDU
SQN
UE
USIM
XMAC-A
XMAC-I
XRES
3.4
3rd Generation Partnership Project
Anonymity key
Authentication Centre
Authentication token
Time variant parameter for synchronisation of ciphering
Time variant parameter for synchronisation of data integrity
Cipher key
Integrity key
International Mobile Subscriber Identity
Intellectual Property Right
Medium access control (sublayer of Layer 2 in RAN)
Message authentication code
MAC used for authentication and key agreement
MAC used for data integrity of signalling messages
Protocol data unit
Random challenge
User response
Radio link control (sublayer of Layer 2 in RAN)
Radio network controller
Signalling data unit
Sequence number
User equipment
User Services Identity Module
Expected MAC used for authentication and key agreement
Expected MAC used for data integrity of signalling messages
Expected user response
Conventions
All data variables in this specification are presented with the most significant substring on the left hand side and the
least significant substring on the right hand side. A substring may be a bit, byte or other arbitrary length bitstring.
Where a variable is broken down into a number of substrings, the leftmost (most significant) substring is numbered 0,
the next most significant is numbered 1, and so on through to the least significant.
3GPP
Release 4
8
4
General algorithm requirements
4.1
Resilience
3GPP TS 33.105 V4.1.0 (2001-06)
The functions should be designed with a view to its continued use for a period of at least 20 years. Successful attacks
with a work load significantly less than exhaustive key search through the effective key space should be impossible.
The designers of above functions should design algorithms to a strength that reflects the above qualitative requirements.
4.2
World-wide availability and use
Legal restrictions on the use or export of equipment containing cryptographic functions may prevent the use of such
equipment in certain countries.
It is the intention that UE and USIMs which embody such algorithms should be free from restrictions on export or use,
in order to allow the free circulation of 3G terminals. Network equipment, including RNC and AuC, may be expected to
come under more stringent restrictions. It is the intention is that RNC and AuC which embody such algorithms should
be exportable under the conditions of the Wassenaar Arrangement [2].
5
Functional algorithm requirements
5.1
Authentication and key agreement
5.1.1
Overview
The mechanism for authentication and key agreement described in clause 6.3 of [1] requires the following
cryptographic functions:
f0
f1
f1*
f2
f3
f4
f5
f5*
the random challenge generating function;
the network authentication function;
the re-synchronisation message authentication function;
the user authentication function;
the cipher key derivation function;
the integrity key derivation function;
the anonymity key derivation function for normal operation;
the anonymity key derivation function for re-synchronisation.
5.1.1.1 Generation of quintets in the AuC
To generate a quintet the HLR/AuC:
-
computes a message authentication code for authentication MAC-A = f1K(SQN || RAND || AMF), an expected
response XRES = f2K (RAND), a cipher key CK = f3K (RAND) and an integrity key IK = f4K (RAND) where f4
is a key generating function.
-
If SQN is to be concealed, in addition the HLR/AuC computes an anonymity key AK = f5K (RAND) and
computes the concealed sequence number SQN ⊕ AK = SQN xor AK. Concealment of the sequence number is
optional.
-
Finally, the HLR/AuC assembles the authentication token AUTN = SQN [⊕ AK] || AMF || MAC-A and the
quintet Q = (RAND, XRES, CK, IK, AUTN).
3GPP
Release 4
9
3GPP TS 33.105 V4.1.0 (2001-06)
RAND
K
K
AMF
f5
xor
AK
SQN ⊕ AK
SQN
K
f1
f2
f3
f4
MAC-A
XRES
CK
IK
AUTN = SQN [⊕ AK] || AMF || MAC-A
Q = (RAND, XRES, CK, IK, AUTN)
Figure 1: Generation of quintets in the AuC
5.1.1.2
Authentication and key derivation in the USIM
Upon receipt of a (RAND, AUTN) pair the USIM acts as follows:
-
If the sequence number is concealed, the USIM computes the anonymity key AK = f5K(RAND) and retrieves the
unconcealed sequence number SQN = (SQN ⊕ AK) xor AK.
The USIM computes XMAC-A = f1K (SQN || RAND || AMF), the response RES = f2K(RAND), the cipher key
CK = f3K (RAND) and the integrity key IK = f4K (RAND).
K
f5
AK
SQN ⊕ AK
RAND
K
AMF
xor
SQN
K
f1
f2
f3
f4
XMAC-A
RES
CK
IK
Figure 2: Authentication and key derivation in the USIM
5.1.1.3
Generation of re-synchronisation token in the USIM
Upon the assertion of a synchronisation failure, the USIM generates a re-synchronisation token as follows:
a) The USIM computes MAC-S = f1*K(SQNMS || RAND || AMF*), whereby AMF* is a default value for AMF
used in re-synchronisation.
b) If SQNMS is to be concealed with an anonymity key AK, the USIM computes AK = f5*K(RAND), and the
concealed counter value is then computed as SQNMS ⊕ AK.
c) The re-synchronisation token is constructed as AUTS = SQNMS [⊕ AK] || MAC-S.
3GPP
Release 4
10
3GPP TS 33.105 V4.1.0 (2001-06)
RAND
SQNMS
K
AMF*
f1*
f5
xor
MAC-S
AK
SQNMS ⊕ AK
AUTS = SQNMS [⊕ AK] || MAC-S
Figure 3: Generation of re-synchronisation token in the USIM
5.1.1.4
Re-synchronisation in the HLR/AuC
Upon receipt of an indication of synchronisation failure and a (AUTS, RAND) pair, the HLR/AuC may perform the
following cryptographic functions:
RAND
SQNMS ⊕ AK
K
K
AMF*
f5
xor
f1*
AK
SQNMS
XMAC-S
MAC-S = XMAC-S ?
Figure 4: Re-synchronisation in the HLR/AuC
a) If SQNMS is concealed with an anonymity key AK, the HLR/AuC computes AK = f5*K(RAND)and retrieves the
unconcealed counter value as SQNMS = (SQNMS ⊕ AK) xor AK.
b) If SQN generated from SQNHE would not be acceptable, then the HLR/AuC computes XMAC-S = f1*K(SQNMS
|| RAND || AMF*), whereby AMF* is a default value for AMF used in re-synchronisation.
5.1.2
Use
The functions f0—f5 shall only be used to provide mutual entity authentication between USIM and AuC, derive keys to
protect user and signalling data transmitted over the radio access link and conceal the sequence number to protect user
identity confidentiality. The function f1* shall only be used to provide data origin authentication for the synchronisation
failure information sent by the USIM to the AuC. The function f5* shall only be used to provide user identity
confidentiality during re-synchronisation.
5.1.3
Allocation
The functions f1—f5, f1* and f5* are allocated to the Authentication Centre (AuC) and the USIM. The function f0 is
allocated to the AuC.
3GPP
Release 4
5.1.4
11
3GPP TS 33.105 V4.1.0 (2001-06)
Extent of standardisation
The functions f0—f5, f1* and f5* are proprietary to the home environment. Examples of the functions f1, f1* and f2 are
CBC-MACs or H-MACs [3].
5.1.5
Implementation and operational considerations
The functions f1—f5, f1* and f5* shall be designed so that they can be implemented on an IC card equipped with a 8bit microprocessor running at 3 MHz with 8 kbyte ROM and 300byte RAM and produce AK, XMAC-A, RES, CK and
IK in less than 500 ms execution time.
5.1.6
5.1.6.1
Type of algorithm
f0
f0: the random challenge generating function
f0: (internal state) Æ RAND
f0 should be (pseudo) random number generating function.
5.1.6.2
f1
f1: the network authentication function
f1: (K; SQN, RAND, AMF) Æ MAC-A (or XMAC-A)
f1 should be a MAC function. In particular, it shall be computationally infeasible to derive K from knowledge of
RAND, SQN, AMF and MAC-A (or XMAC-A).
5.1.6.3
f1*
f1*: the re-synchronisation message authentication function
f1*:
(K; SQN, RAND, AMF) Æ MAC-S (or XMAC-S)
f1 should be a MAC function. In particular, it shall be computationally infeasible to derive K from knowledge of
RAND, SQN, AMF and MAC-S (or XMAC-S).
5.1.6.4
f2
f2: the user authentication function
f2: (K; RAND) Æ RES (or XRES)
f2 should be a MAC function. In particular, it shall be computationally infeasible to derive K from knowledge of RAND
and RES (or XRES).
5.1.6.5
f3
f3: the cipher key derivation function
f3: (K; RAND) Æ CK
f3 should be a key derivation function. In particular, it shall be computationally infeasible to derive K from knowledge
of RAND and CK.
3GPP
Release 4
5.1.6.6
12
3GPP TS 33.105 V4.1.0 (2001-06)
f4
f4: the integrity key derivation function
f4: (K; RAND) Æ IK
f4 should be a key derivation function. In particular, it shall be computationally infeasible to derive K from knowledge
of RAND and IK.
5.1.6.7
f5
f5: the anonymity key derivation function for normal operation
f5: (K; RAND) Æ AK
f5 should be a key derivation function. In particular, it shall be computationally infeasible to derive K from knowledge
of RAND and AK.
The use of f5 is optional.
5.1.6.8
f5*
f5*: the anonymity key derivation function for re-synchronisation
f5*: (K; RAND) Æ AK
f5* should be a key derivation function. In particular, it shall be computationally infeasible to derive K from knowledge
of RAND and AK.
The use of f5* is optional.
5.1.7
5.1.7.1
Interface
K
K: the subscriber authentication key
K[0], K[1], …, K[127]
The length of K is 128 bits. The subscriber authentication key K is a long term secret key stored in the USIM and the
AuC.
5.1.7.2
RAND
RAND: the random challenge
RAND[0], RAND[1], …, RAND[127]
The length of RAND is 128 bits.
5.1.7.3
SQN
SQN: the sequence number
SQN[0], SQN[1], …, SQN[47]
The length of SQN is 48 bits. The AuC should include a fresh sequence number in each authentication token. The
verification of the freshness of the sequence number by the USIM constitutes to entity authentication of the network to
the user.
3GPP
Release 4
5.1.7.4
13
3GPP TS 33.105 V4.1.0 (2001-06)
AMF
AMF: the authentication management field
AMF[0], AMF[1], …, AMF[15]
The length of AMF is 16 bits. The use of AMF is not standardised. Example uses of the AMF are provided in annex F
of TS 33.102.
5.1.7.6
MAC-A (equivalent for XMAC-A)
MAC-A: the message authentication code used for authentication of the network to the user
MAC-A[0], MAC-A[1], …, MAC-A[63]
The length of MAC-A is 64 bits. MAC-A authenticates the data integrity and the data origin of RAND, SQN and AMF.
The verification of MAC-A by the USIM constitutes to entity authentication of the network to the user.
5.1.7.7
MAC-S (equivalent for XMAC-S)
MAC-S: the message authentication code used to provide data origin authentication for the synchronisation failure
information sent by the USIM to the AuC.
MAC-S[0], MAC-S[1], …, MAC-S[63]
The length of MAC-S is 64 bits. MAC-S authenticates the data integrity and the data origin of RAND, SQN and AMF.
MAC-S is generated by the USIM and verified by the AuC.
5.1.7.8
RES (or XRES)
RES: the user response
RES[0], RES[1], …, RES[n-1]
The length n of RES and XRES is at most 128 bits and at least 32 bits, and shall be a multiple of 8 bits. RES and XRES
constitute to entity authentication of the user to the network.
5.1.7.9
CK
CK: the cipher key
CK[0], CK[1], …, CK[127]
The length of CK is 128 bits. In case the effective key length should need to be made smaller than 128 bits, the most
significant bits of CK shall carry the effective key information, whereas the remaining, least significant bits shall be set
zero.
5.1.7.10
IK
IK: the integrity key
IK[0], IK[1], …, IK[127]
The length of IK is 128 bits. In case the effective key length should need to be made smaller than 128 bits, the most
significant bits of IK shall carry the effective key information, whereas the remaining, least significant bits shall be set
zero.
3GPP
Release 4
14
5.1.7.11
3GPP TS 33.105 V4.1.0 (2001-06)
AK
AK: the anonymity key
AK[0], AK[1], …, AK[47]
The length of AK is 48 bits. It equals the length of SQN.
5.2
Data confidentiality
5.2.1
Overview
The mechanism for data confidentiality of user data and signalling data that is described in 6.6 of [1] requires the
following cryptographic function:
f8 UMTS encryption algorithm.
Figure 1 illustrates the use of f8 to encrypt plaintext by applying a keystream using a bitwise XOR operation. The
plaintext may be recovered by generating the same keystream using the same input parameters and applying it to the
ciphertext using a bitwise XOR operation.
COUNT-C
BEARER
CK
COUNT-C
DIRECTION
LENGTH
f8
BEARER
CK
KEYSTREAM
BLOCK
PLAINTEXT
BLOCK
DIRECTION
LENGTH
f8
KEYSTREAM
BLOCK
CIPHERTEXT
BLOCK
Sender
UE or RNC
PLAINTEXT
BLOCK
Receiver
RNC or UE
Figure 1: Ciphering user and signalling data transmitted over the radio access link
The input parameters to the algorithm are the Cipher Key (CK), a time dependent input (COUNT-C), the bearer identity
(BEARER), the direction of transmission (DIRECTION) and the length of the keystream required (LENGTH). Based
on these input parameters the algorithm generates the output keystream block (KEYSTREAM) which is used to encrypt
the input plaintext block (PLAINTEXT) to produce the output ciphertext block (CIPHERTEXT).
The input parameter LENGTH shall affect only the length of the KEYSTREAM BLOCK, not the actual bits in it.
5.2.2
Use
The function f8 shall only be used to protect the confidentiality of user data and signalling data sent over the radio
access link between UE and RNC.
3GPP
Release 4
5.2.3
15
3GPP TS 33.105 V4.1.0 (2001-06)
Allocation
The function f8 is allocated to the UE and the RNC.
Encryption will be applied in the Medium Access Control (MAC) sublayer and in the Radio Link Control (RLC)
sublayer of the data link layer (Layer 2).
5.2.4
Extent of standardisation
The function f8 shall be fully standardized.
5.2.5
Implementation and operational considerations
The algorithm should be designed to accommodate a range of implementation options including hardware and software
implementations. For hardware implementations, it should be possible to implement one instance of the algorithm using
less than 10,000 gates (working assumption).
A wide range of UE with different bearer capabilities is expected, so the encryption throughput requirements on the
algorithm will vary depending on the implementation. However, based on the likely maximum user traffic data rates, it
must be possible to implement the algorithm to achieve an encryption speed in the order of 2Mbit/s on the downlink and
on the uplink.
1. RLC-transparent mode:
-
New keystream block required every physical layer frame (10ms)
-
Maximum number of bits per physical layer frame of 20000 bits
-
Minimum number of bits per physical layer frame of 1 bit
-
Granularity of 1 bit on all possible intermediate values.
2. For UM RLC mode:
-
New keystream block required per UMD PDU
-
Maximum number of bits in UMD PDU is 5000 bits
-
Minimum number of bits in UMD PDU is 16 bits
-
Granularity of 8 bit on all possible intermediate values.
3. For AM RLC mode:
-
New keystream block required per AMD PDU
-
Maximum number of bits in AMD PDU is 5000 bits
-
Minimum number of bits in AMD PDU is 24 bits
-
Granularity of 8 bit on all possible intermediate values.
The encryption throughput requirements should be met based on clock speeds upwards of 20MHz (typical clock speeds
are expected to be much greater than this).
5.2.6
Type of algorithm
The function f8 should be a symmetric synchronous stream cipher.
3GPP
Release 4
5.2.7
5.2.7.1
16
3GPP TS 33.105 V4.1.0 (2001-06)
Interfaces to the algorithm
CK
CK: the cipher key
CK[0], CK[1], …, CK[127]
The length of CK is 128 bits. In case the effective key length k is smaller than 128 bits, the most significant bits of CK
shall carry the effective key information, whereas the remaining, least significant bits shall repeat the effective key
information:
CK[n] = CK[n mod k], for all n, such that k ≤ n < 128.
5.2.7.2
COUNT-C
COUNT-C: the cipher sequence number.
COUNT-C[0], COUNT-C[1], …, COUNT-C[31]
The length of the COUNT-C parameter is 32 bits.
Sychronisation of the keystream is based on the use of a physical layer (Layer 1) frame counter combined with a
hyperframe counter introduced to avoid re-use of the keystream. This allows the keystream to be synchronised every
10ms physical layer frame. The exact structure of the COUNT-C is specified in TS 33.102.
5.2.7.3
BEARER
BEARER: the radio bearer identifier.
BEARER[0], BEARER[1], …, BEARER[4]
The length of BEARER is 5 bits.
The same cipher key may be used for different radio bearers simultaneously associated with a single user which are
multiplexed onto a single 10ms physical layer frame. To avoid using the same keystream to encrypt more than one
bearer, the algorithm shall generate the keystream based on the identity of the radio bearer.
5.2.7.4
DIRECTION
DIRECTION: the direction of transmission of the bearer to be encrypted.
DIRECTION[0]
The length of DIRECTION is 1 bit.
The same cipher key may be used for uplink and downlink channels simultaneously associated with a UE, which are
multiplexed onto a single 10ms physical layer frame. To avoid using the same keystream to encrypt both uplink and
downlink transmissions, the algorithm shall generate the keystream based on the direction of transmission.
The value of the DIRECTION is 0 for messages from UE to RNC and 1 for messages from RNC to UE.
An explicit direction value is required in preference to splitting the keystream segment into uplink and downlink
portions to allow for asymmetric bearer services.
3GPP
Release 4
5.2.7.5
17
3GPP TS 33.105 V4.1.0 (2001-06)
LENGTH
LENGTH: the required length of keystream.
LENGTH[0], LENGTH[1], …, LENGTH[15]
The length of LENGTH is 16 bits.
For a given bearer and transmission direction the length of the plaintext block that is transmitted during a single
physical layer frame may vary. The algorithm shall generate a keystream block of variable length based on the value of
the length parameter.
The input parameter LENGTH shall affect only the length of the KEYSTREAM BLOCK, not the actual bits in it.
The maximum RLC PDU / MAC SDU size is 5000 bits. The range of values of the length parameter will depend not
only on the RLC PDU / MAC SDU size but also the number of RLC PDUs / MAC SDUs which may be sent in a single
physical layer 10ms frame for a given bearer and transmission direction.
Not all values between the maximum and minimum values shall be required but it is expected that the ability to produce
length values of whole numbers of octets between a minimum and a maximum value will be required.
5.2.7.6
KEYSTREAM
KEYSTREAM: the output keystream.
KS [0], KS [1], …, KS [LENGTH-1]
The length of a keystream block equals the value of the input parameter LENGTH.
5.2.7.7
PLAINTEXT
PLAINTEXT: the plaintext.
PT[0], PT[1], …, PT[LENGTH-1]
The length of a keystream block equals the value of the input parameter LENGTH.
This plaintext block consists of the payload of the particular RLC PDUs / MAC SDUs to be encrypted for a given
bearer and transmission direction. It may consist of user traffic or signalling data:
-
For RLC UM mode, the plaintext block is the UMD PDU excluding the first octet, i.e. excluding the RLC UM
PDU header (see TS 25.322 [19]).
-
For RLC AM mode, the plaintext block is the AMD PDU excluding the two first octets, i.e. excluding the RLC
AM PDU header (see TS 25.322 [19]).
-
For RLC TM on DCH, the plaintext block consists of all the MAC SDUs containing data for one and the same
radio bearer and sent in one Transmission Time Interval. In this case, the CFN part of COUNT-C for the
plaintext block is the CFN for the first radio frame of the Transmission Time Interval containing the plaintext
block. (see TS 25.321 [18]).
5.2.7.8
CIPHERTEXT
CIPHERTEXT: the ciphertext.
CT[0], CT[1], …, CT[LENGTH-1]
The length of a keystream block equals the value of the input parameter LENGTH.
3GPP
Release 4
18
5.3
Data integrity
5.3.1
Overview
3GPP TS 33.105 V4.1.0 (2001-06)
The mechanism for data integrity of signalling data that is described in 6.6 of [1] requires the following cryptographic
function:
f9 UMTS integrity algorithm.
Figure 3 illustrates the use of the function f9 to derive a MAC-I from a signalling message.
DIRECTION
COUNT-I
MESSAGE
IK
COUNT-I
FRESH
DIRECTION
MESSAGE
IK
f9
FRESH
f9
MAC -I
XMAC -I
Sender
UE or RNC
Receiver
UE or RNC
Figure 2: Derivation of MAC-I (or XMAC-I) on a signalling message
The input parameters to the algorithm are the Integrity Key (IK), a time dependent input (COUNT-I), a random value
generated by the network side (FRESH), the direction bit (DIRECTION) and the signalling data (MESSAGE). Based
on these input parameters the user computes with the function f9 the message authentication code for data integrity
(MAC-I) which is appended to the message when sent over the radio access link. The receiver computes XMAC-I on
the messages received in the same way as the sender computed MAC-I on the message sent.
5.3.2
Use
The MAC function f9 shall be used to authenticate the data integrity and data origin of signalling data transmitted
between UE and RNC.
5.3.3
Allocation
The MAC function f9 is allocated to the UE and the RNC.
Integrity protection shall be applied at the RRC layer.
5.3.4
Extent of standardisation
The function f9 is fully standardized.
5.3.5
Implementation and operational considerations
The algorithm should be designed to accommodate a range of implementation options including hardware and software
implementations.
5.3.6
Type of algorithm
The function f9 shall be a MAC function.
3GPP
Release 4
5.3.7
5.3.7.1
19
3GPP TS 33.105 V4.1.0 (2001-06)
Interface
IK
IK: the integrity key
IK[0], IK[1], …, IK[127]
The length of IK is 128 bits.
5.3.7.2
COUNT-I
COUNT-I: a frame dependent input.
COUNT-I[0], COUNT-I[1], …, COUNT-I[31]
The length of COUNT-I is 32 bits.
The input parameter COUNT-I protects against replay during a connection. It is a value incremented by one for each
integrity protected message. COUNT-I consists of two parts: the HYPERFRAME NUMBER (HFN) as the most
significant part and a RRC Sequence Number as the least significant part. The initial value of the hyperframe number is
sent by the user to the network at connection set-up. The user stores the greatest used hyperframe number from the
previous connection and increments it by one. In this way the user is assured that no COUNT-I value is re-used (by the
network) with the same integrity key.
5.3.7.3
FRESH
FRESH: a random number generated by the RNC.
FRESH[0], FRESH[1], …, FRESH[31]
The length of FRESH is 32 bits.
The same integrity key may be used for several consecutive connections. This FRESH value is an input to the algorithm
in order to assure the network side that the user is not replaying old MAC-Is.
5.3.7.4
MESSAGE
MESSAGE: the signalling data.
MESSAGE[0], MESSAGE[1], …, MESSAGE[X-1]
The length of MESSAGE is X.
5.3.7.5
DIRECTION
DIRECTION: the direction of transmission of signalling messages (user to network or network to users).
DIRECTION[0]
The length of DIRECTION is 1 bit.
The same integrity key may be used for uplink and downlink channels simultaneously associated with a UE.
The value of the DIRECTION is 0 for messages from UE to RNC and 1 for messages from RNC to UE.
5.3.7.6
MAC-I (and equivalently XMAC-I)
MAC-I: the message authentication code for data integrity authentication
MAC-I[0], MAC-I[1], …, MAC-I[31]
The length of MAC-I is 32 bits.
3GPP
Release 4
6
20
3GPP TS 33.105 V4.1.0 (2001-06)
Use of the algorithm specifications
The purpose of this clause is to address ownership of the algorithm specification, to define which types of organisation
are entitled to use the algorithm specification, and to outline how and under what conditions such organisations may
obtain the specification.
6.1
Ownership
For those functions which require to be fully standardized, all copyright on the algorithm and test data specifications
shall be owned jointly by the 3GPP partner organisations.
6.2
Design authority
The design authority for the algorithms that require standardisation shall be ETSI SAGE. It is expected that the project
team assembled by SAGE will draw on appropriate expertise within the 3GPP partner organisations in addition to its
normal resource pool.
6.3
Users of the specification
For those functions which require to be fully standardized, the algorithm specification shall be published as a 3GPP
specification. It will be used by those who need the algorithm specification to build equipments or components which
embody the algorithm.
6.4
Licensing
For those functions which require to be fully standardized, the use of the algorithm shall be subject to a license
agreement which restricts the use of the algorithm as described in 5.3.2 and 5.4.2.
Users of the algorithm, and users of the algorithm specification, shall be required to sign the licence agreement.
Appropriate licence agreements shall be drawn up by the 3GPP partner organisations.
Licences shall be royalty free. In addition, the licence agreement shall require users of the specification not to attempt to
patent the algorithm or otherwise register an Intellectual Property Right (IPR) relating to the algorithm or its use.
6.5
Management of the specification
For those functions which require to be fully standardized, the algorithm specifications shall be published as a 3GPP
specification. The algorithms will thus be open for public evaluation. It is recognised that this will leave the algorithms
open to public criticism during the commercial operation of the system. The process of responding to public criticism
will need to be handled carefully by an appropriate 3GPP body.
7
Algorithm specification and test data requirements
For those functions that require standardization, the design authority should provide four separate deliverables: a
specification of the algorithm, a set of design conformance test data, a set of algorithm input/output test data and a
design and evaluation report. Requirements on the specification and test data deliverables are given in this clause, those
on the design and evaluation report in 9.3.
3GPP
Release 4
7.1
21
3GPP TS 33.105 V4.1.0 (2001-06)
Specification of the algorithm
An unambiguous specification of the algorithm needs to be provided which is suitable for use by implementers of the
algorithm.
The specification shall include an annex which provides simulation code for the algorithm written in ANSI C. The
specification may also include an annex containing illustrations of functional elements of the algorithm.
7.2
Implementors test data
The implementors test data is required to assist implementors of the algorithm in their realisation of the algorithm
specification.
This set of test data, as well as including algorithm input and output data, shall include details of the internal state of the
algorithm at various stages in its execution. Sufficient detail shall be provided to enable implementators to readily
identity the likely location of any errors in their implementation.
Final validation of the implementation shall be performed using the design conformance test data (see subclause 7.3).
7.3
Design conformance test data
Design conformance test data is required to allow implementers of the algorithm to validate their implementations, and
manufacturers to validate embodiments of the algorithm (e.g. in ASICs or FPGAs).
The test data set shall be presented as input/output test data, allowing the realisation to be tested as a ’black box’. (i.e. the
test data shall consist solely of data passed across the interfaces to the algorithm.)
The design conformance test data shall be designed to give a high degree of confidence in the correctness of any
implementation of the algorithm. The set of test data shall ensure that all elements of the algorithm are fully exercised.
7.4
Format and handling of deliverables
The specification of the algorithm shall be produced on paper, and published as a 3GPP specification.
The algorithm input/output test data shall be produced on paper and on magnetic disc, and published by 3GPP. The
document and disc shall be provided to 3GPP partner organisations.
8
Quality assurance requirements
This clause advises the design authority on measures needed to provide users of the algorithm with confidence that it is
fit for purpose, and users of the algorithm specification and test data assurance that appropriate quality control has been
exercised in their production.
The measures shall be recorded by the design authority in a design and evaluation report which shall be published as a
3GPP specification.
8.1
Quality assurance for the algorithm
Prior to its release to 3GPP, the algorithm needs to be approved as meeting the functional requirements specified in
clause 7 by all members of the design authority.
3GPP
Release 4
8.2
22
3GPP TS 33.105 V4.1.0 (2001-06)
Quality assurance for the specification and test data
Prior to delivery of the algorithm specification, two independent simulations of the algorithm needs to be made using
the specification, and confirmed against test data designed to allow verification of significant points in the execution of
the algorithm.
Design conformance and algorithm input/output test data needs to be generated using a simulation of the algorithm
produced from the specification and confirmed as above. The simulation used to produce this test data needs to be
identified in the test data deliverables and retained by the design authority.
8.3
Design and evaluation report
The design and evaluation report is intended to provide evidence to potential users of the algorithm, specification and
test data that appropriate and adequate quality control has been applied to their production. The report shall explain the
following:
-
the algorithm and test data design criteria;
-
the algorithm evaluation criteria;
-
the methodology used to design and evaluate the algorithm;
-
the extent of the mathematical analysis and statistical testing applied to the algorithm;
-
the principal conclusions of the algorithm evaluation;
-
the quality control applied to the production of the algorithm specification and test data.
The report shall confirm that all members of the design authority have approved the algorithm, specification and test
data.
The report shall contain key conclusions from the commissioned closed evaluation of the algorithm.
9
Summary of the design authority deliverables
For those cryptographic functions that require standardisation, the design authority shall deliver:
-
Specification of the algorithm;
-
Implementors test data;
-
Design conformance test data;
-
Design and evaluation report.
All these documents shall be delivered to 3GPP for subsequent publication.
3GPP
Release 4
23
Annex A (informative):
Void
Void.
3GPP
3GPP TS 33.105 V4.1.0 (2001-06)
Release 4
24
3GPP TS 33.105 V4.1.0 (2001-06)
Annex B (informative):
Change history
TSG SA
#
SA#04
SA#05
SA#05
SA#05
SA#06
SA#06
SA#07
SA#07
Version
CR
Tdoc SA
3.0.0
3.0.0
3.0.0
3.1.0
3.1.0
3.2.0
3.2.0
001
002
003
004
005
006
007
SP-99418
SP-99418
SP-99418
SP-99587
SP-99587
SP-000048
SP-000048
SA#07
SA#07
SA#07
SA#08
SA#09
SA#09
SA#09
SA#10
SP-11
SP-11
SP-11
SP-11
SP-12
3.2.0
3.2.0
3.2.0
3.3.0
3.4.0
3.4.0
3.4.0
3.5.0
3.6.0
3.6.0
3.6.0
3.7.0
4.0.0
008
009
010
011
012
013
014
015
016
017
018
020
SP-000075
SP-000048
SP-000048
SP-000271
SP-000445
SP-000444
SP-000445
SP-000627
SP-0100yy
SP-0100yy
SP-0100yy
SP-010321
Change history
New
Subject/Comment
Version
3.0.0
Approved at SA#04 and placed under TSG SA Change Control
3.1.0
Resources for cryptographic algorithms in the USIM
3.1.0
MAC used for data integrity of signaling messages
3.1.0
Cipher keystream block length
3.2.0
Time variant parameter for synchronisation of ciphering
3.2.0
Direction bit in f9
3.3.0
Authentication and key agreement
3.3.0
Enhanced user confidentiality (Some conflict with CR008. CR008
and 33.102 used as basis for terminology)
3.3.0
Refinement of EUIC for consistency with 33.102
3.3.0
Ciphering
3.3.0
Data integrity
3.4.0
Clarification of BEARER and DIRECTION parameters
3.5.0
Calculation of AK in re-synchronisation
3.5.0
Deletion of eUIC
3.5.0
Anonymity key computation during re-synchronisation
3.6.0
Layer 2 related corrections
3.7.0
Add bit ordering convention
3.7.0
RES has to be a multiple of 8 bits
3.7.0
Minimum clock frequency updated
4.0.0
Upgrade to Release 4
4.1.0
Deletion of the maximum size of a RRC message
3GPP
Download PDF
Similar pages