4.7.3 Contents of EAP-AKA’ messages

38.508-13GPP5GSPart 1: Common test environmentRelease 17TSUser Equipment (UE) conformance specification

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

For all the message definitions below, the acceptable order and syntax of attributes and fields within these attributes must be according to IETF RFCs where those attributes have been defined. Typically the order of attributes is not significant, but there could be well defined exceptions where the order is important.

The contents of the messages described in the present Annex is not complete – only the attributes required to be checked or generated by SS are listed here. The messages sent by the UE may contain additional attributes which are not checked and must thus be ignored by SS.

4.7.3.1 EAP-AKA’ message attributes

Table 4.7.3.1-1: AT_RAND_Def

Derivation Path: IETF RFC 4187 [30] clause 10.6
Information Element	Value/remark	Comment	Condition
AT_RAND	‘0000 0001’B	1
Length	‘0000 0101’B	5
Reserved	‘0000 0000 0000 0000’B
RAND	An arbitrarily selected 128 bits value

Table 4.7.3.1-2: AT_AUTN_Def

Derivation Path: IETF RFC 4187 [30] clause 10.7
Information Element	Value/remark	Comment	Condition
AT_AUTN	‘0000 0010’B	2
Length	‘0000 0101’B	5
Reserved	‘0000 0000 0000 0000’B
AUTN	128 bits value generated according to TS 24.501 [28] subclause 9.11.3.15

Table 4.7.3.1-3: AT_KDF_Def

Derivation Path: IETF RFC 5448 [31] clause 3.3
Information Element	Value/remark	Comment	Condition
AT_KDF	‘0001 1000’B	24
Length	‘0000 0001’B	1
KDF	‘0000 0000 0000 0001’	1: EAP_AKA’

Table 4.7.3.1-4: AT_KDF_INPUT_Def

Derivation Path: IETF RFC 5448 [31] clause 3.2
Information Element	Value/remark	Comment	Condition
AT_KDF_INPUT	‘0001 0111’B	23
Length	Set to the Length of attribute AT_KDF_INPUT in 4 bytes
Actual Network Name Length	Set to the actual length of ‘Network Name’ in bytes excluding any appended all zero bytes at end
Network Name	Value generated according to TS 24.501 [28] clause 9.12.1 and shall be a multiple of 4 bytes (appended with 1,2 or 3 bytes of all zero bits when necessary)

Table 4.7.3.1-5: AT_MAC_Def

Derivation Path: IETF RFC 4187 [30] clause 10.15
Information Element	Value/remark	Comment	Condition
AT_MAC	‘0000 1011’B	11
Length	‘0000 0101’B	5
Reserved	‘0000 0000 0000 0000’B
MAC	128 bits value generated according to RFC 4187 [30] subclause 10.15

Table 4.7.3.1-6: AT_RES_Def

Derivation Path: IETF RFC 4187 [30] clause 10.08
Information Element	Value/remark	Comment	Condition
AT_RES	‘0000 0011’B	3
Length	Set to Length of AT_RES attribute in 4 bytes.	1 byte
RES_LENGTH	Set to the actual length of ‘RES’ in bytes excluding any appended all zero bytes at end
RES	RES* value calculated according to TS 24.501 [28] clause 9.11.3.17, possibly appended with 1,2 or 3 bytes of all zero bits to make lenght multiple of 4 bytes.

Table 4.7.3.1-7: AT_AUTS_Def

Derivation Path: IETF RFC 4187 [30] clause 10.08
Information Element	Value/remark	Comment	Condition
AT_AUTS	‘0000 0100’B	4
Length	‘0000 0100’B	4
AUTS	14 octets RES* value not checked

Table 4.7.3.1-8: AT_PERMANENT_ID_Def

Derivation Path: IETF RFC 4187 [30] clause 10.2
Information Element	Value/remark	Comment	Condition
AT_PERMANENT_ID_REQ	‘0000 1010’B	10
Length	‘0000 0001’B	1
Reserved	‘0000 0000 0000 0000’B

Table 4.7.3.1-9: AT_ANY_ID_REQ_Def

Derivation Path: IETF RFC 4187 [30] clause 10.3
Information Element	Value/remark	Comment	Condition
AT_ANY_ID_REQ	‘0000 1101’B	13
Length	‘0000 0001’B	1
Reserved	‘0000 0000 0000 0000’B

Table 4.7.3.1-10: AT_FULLAUTH_ID_Def

Derivation Path: IETF RFC 4187 [30] clause 10.4
Information Element	Value/remark	Comment	Condition
AT_FULLAUTH_ID_REQ	‘0001 0001’B	17
Length	‘0000 0001’B	1
Reserved	‘0000 0000 0000 0000’B

Table 4.7.3.1-11: AT_IDENTITY_Def

Derivation Path: IETF RFC 4187 [30] clause 10.5
Information Element	Value/remark	Comment	Condition
AT_IDENTITY	‘0000 1110’B	14
Length	Set to the Length of AT_IDENTITY attribute in 4 bytes
Actual Identity Length	Set to the actual length of ‘identity’ in bytes excluding any appended all zero bytes at end
Identity	Value generated according to TS 24.501 [28] clause 9.11.3.4 and shall be a multiple of 4 bytes (appended with 1,2 or 3 bytes of all zero bits when necessary)

Table 4.7.3.1-12: AT_NOTIFICATION_Def

Derivation Path: IETF RFC 4187 [30] clause 10.19
Information Element	Value/remark	Comment	Condition
AT_NOTIFICATION	‘0000 1100’B	12
Length	‘0000 0001’B	1
Notification Code	16 bits value generated according to RFC 4187 [30] subclause 10.19.

4.7.3.2 EAP-AKA’ messages

Table 4.7.3.2-1: EAP-Request/AKA’-Challenge

Derivation Path: IETF RFC 4187 [30] clause 9.3, RFC 3748 [32] clause 4
Information Element	Value/remark	Comment	Condition
Code	1	Request
Length	Set to length of EAP packet
Data
AT_RAND	AT_RAND_Def
AT_AUTN	AT_AUTN_Def
AT_KDF	AT_KDF_Def
AT_KDF_INPUT	AT_KDF_INPUT_Def
AT_MAC	AT_MAC_Def

Table 4.7.3.2-2: EAP-Response/AKA’-Challenge

Derivation Path: IETF RFC 4187 [30] clause 9.4, RFC 3748 [32] clause 4
Information Element	Value/remark	Comment	Condition
Code	2	Response
Length	Set to length of EAP packet
Data
AT_Res	AT_Res_Def
AT_MAC	AT_MAC_Def

Table 4.7.3.2-3: EAP-Succes

Derivation Path: IETF RFC 4187 [30] clause 6.3.4, RFC 3748 [32] clause 4
Information Element	Value/remark	Comment	Condition
Code	3	Success
Length	Set to length of EAP packet
Data	Not present	Specific attributes not present

Table 4.7.3.2-4: EAP-Response/AKA-Authentication-Reject

Derivation Path: IETF RFC 4187 [30] clause 9.5, RFC 3748 [32] clause 4
Information Element	Value/remark	Comment	Condition
Code	4	Failure
Length	Set to length of EAP packet
Data	Not checked

Table 4.7.3.2-5: EAP-Response/AKA-Synchronization-Failure

Derivation Path: IETF RFC 4187 [30] clause 9.6, RFC 3748 [32] clause 4
Information Element	Value/remark	Comment	Condition
Code	4	Failure
Length	Set to length of EAP packet
Data
AT_AUTS	AT_AUTS_Def

Table 4.7.3.2-6: EAP-Failure

Derivation Path: IETF RFC 4187 [30] clause 6.3.3, RFC 3748 [32] clause 4
Information Element	Value/remark	Comment	Condition
Code	4	Failure
Length	Set to length of EAP packet
Data	Not present	Specific attributes not present

Table 4.7.3.2-7: EAP-Request/AKA-Identity

Derivation Path: IETF RFC 4187 [30] clause 9.1, RFC 3748 [32] clause 4
Information Element	Value/remark	Comment	Condition
Code	1	Request
Length	Set to length of EAP packet
Data
AT_PERMANENT_ID_REQ	AT_PERMANENT_ID_REQ_Def		SS requests that the UE send its permanent identity.
AT_ANY_ID_REQ	AT_ANY_ID_REQ_Def		SS does not specify which kind of an identity the UE should return.
AT_FULLAUTH_ID_REQ	AT_FULLAUTH_ID_REQ_Def		SS requests either the permanent identity or a pseudonym identity.

Table 4.7.3.2-8: EAP-Response/AKA-Identity

Derivation Path: IETF RFC 4187 [30] clause 9.2, RFC 3748 [32] clause 4
Information Element	Value/remark	Comment	Condition
Code	2	Response
Length	Set to length of EAP packet
Data
AT_IDENTITY	AT_IDENTITY_Def

Table 4.7.3.2-9: EAP-Request/AKA-Notification

Derivation Path: IETF RFC 4187 [30] clause 9.10, RFC 3748 [32] clause 4
Information Element	Value/remark	Comment	Condition
Code	1	Request
Length	Set to length of EAP packet
Data
AT_NOTIFICATION	AT_NOTIFICATION_Def

Table 4.7.3.2-10: EAP-Response/AKA-Notification

Derivation Path: IETF RFC 4187 [30] clause 9.11, RFC 3748 [32] clause 4
Information Element	Value/remark	Comment	Condition
Code	2	Response
Length	Set to length of EAP packet
Data	Not present	Specific attributes not present