Home → N3IWF

4.2.2.1.1 Handling of EAP-Identity Request message

 Home → N3IWF → 18.0.0
 33520-i00 → 33520-i10  
Test Name TC_N3IWF_REFRAIN_SEND_IDENTITY_REQUEST
Threat Reference

TBD
Requirement Name

Handling of EAP-Identity Request message
Requirement Reference

TS 33.501 [2], clause 7.2.1
Requirement Description

"The N3IWF shall refrain from sending an EAP-Identity request. The UE may ignore an EAP Identity request or respond with the SUCI it sent in the Registration Request." as specified in TS 33.501 [2], clause 7.2.1.
Test Purpose

Verify that the N3IWF will not send an EAP-Identity request message, and if the N3IWF sends EAP-Identity Request message, whether the N3IWF will conintue to proceed the EAP-5G procedure.
Pre-Conditions

  • The AMF network product shall be connected in emulated/real network environments. UE may be simulated.

  • A document describes whether the N3IWF will send an EAP-Identity Request message.
Execution Steps

  1. The UE initiates IKE_SA_INIT procedure without UE identity.

  2. The N3IWF responses an EAP message
Expected Results

If the EAP message is EAP-5G start, then it is ok.

If the EAP message is EAP-Identity Request meesage, then check whether the N3IWF sends a N2 msg to the AMF, and whether the procedure in 7.2 of TS 33.501[2] runs successfully.
Expected Format of Evidence

Save the logs and the communication flow in a .pcap file.
PDFs 2111b64f5fbffbd412116cc4393e1762