Merge branch 'TTF_T041' into 'TMP_KSCH'

# TP objective ideas reviewed

## Section 5.4.1.3.7 (FF)

- TP_5GNAS_AMF_AUT_ABN_01

    - Verify that the IUT sends a new IDENTIFICATION REQUEST message to obtain the SUCI from the UE upon receipt of an AUTHENTICATION FAILURE message indicating a 5GMM cause value #26 - non-5G authentication unacceptable. (FF)

        - This case is also valid in cases where the UE send Auth Response, but the response parameters do not match.

        - Please check Note 2: "... the network may also terminate the 5G AKA based primary authentication ..." Depends on ID used in Initial NAS message

- TP_5GNAS_AMF_AUT_ABN_02

    - Verify that the IUT sends a new AUTHENTICATION REQUEST message to re-initiate the 5G AKA based primary authentication upon receipt of an IDENTIFICATION RESPONSE message indicating an incorrect 5G-GUTI to SUPI mapping. (FF)

- TP_5GNAS_AMF_AUT_ABN_03

    - Verify that the IUT sends a AUTHENTICATION REJECT message to terminate the 5G AKA based primary authentication and key agreement authentication procedure upon receipt of an IDENTIFICATION RESPONSE message indicating an correct 5G-GUTI to SUPI mapping. (FF)

- TP_5GNAS_AMF_AUT_ABN_04

    - Verify that the IUT sends a new AUTHENTICATION REQUEST message after a successful re-synchronisation procedure upon receipt of an AUTHENTICATION FAILURE message indicating a 5GMM cause value #21 (Synch failure) and including the AUTS parameter. (FF)

## Section 5.4.2: Security mode control procedure (FF)

- TP_5GNAS_AMF_SEC_ACC_01

    - Verify that the IUT, upon receiving the NAS Security Mode Complete Message after completing the NAS Authentication and Security procedure, successfully completes the registration process by accepting the registration.

- TP_5GNAS_AMF_SEC_REJ_01

    - Verify that the IUT, upon receiving the NAS Security Mode Reject Message after a failed NAS Authentication and security procedure, successfully aborts the registration process by rejecting the registration.

- TP_5GNAS_AMF_SEC_ABN_01

    - Verify that the IUT sends a new AUTHENTICATION REQUEST message to re-initiate the 5G AKA based primary authentication upon receipt of an AUTHENTICATION FAILURE message indicating a 5GMM cause value #71 (ngKSI already in use). (FF)    See above in Section 5.4.1.3.7

## ## Section 5.4.3: Identification procedure (FF)

- TP_5GNAS_AMF_IDN_ACC_02

    - Verify that the IUT sends an IDENTITY REQUEST message correctly upon receipt of an AUTHENTICATION FAILURE message indicating a 5GMM cause value #20. (already implemented as: TP_5GNAS_AMF_AUT_REQ_04)

- TP_5GNAS_AMF_IDN_RES_01

    - Verify that the IUT, upon receiving an IDENTITY RESPONSE message from the UE with an incorrect IMSI, correctly sends an AUTHENTICATION REQUEST message. The IDENTITY REQUEST message is triggered during an authentication procedure with a failed authentication (AUTHENTICATION FAILURE).

- TP_5GNAS_AMF_IDN_REJ_01

    - Verify that the IUT, upon receiving an IDENTITY RESPONSE message from the UE with a correct IMSI, correctly sends an AUTHENTICATION REJECT message. The IDENTITY REQUEST message is triggered during an authentication procedure with a failed authentication (AUTHENTICATION FAILURE).

- TP_5GNAS_AMF_IDN_RES_02

    - Verify that the IUT stops re-sending an Identity REQUEST message if no Identity RESPONSE message is received on the fifth expiry of timer T3519.

## Section 5.4.5: NAS transport procedure (FF) ( 8.2.10, 8.2.11)

- TP_5GNAS_AMF_DLN_ACC_01

    - Verify that the IUT correctly handles a UL NAS transport message containing a PDU SESSION ESTABLISHMENT REQUEST from the UE and responds with a DL NAS transport message containing a PDU SESSION ESTABLISHMENT ACCEPT.

    **Note:** This test idea could be unnecessary. Since the messages DL and UL NAS transport are intrinsically linked to PDU Sessions, their functionality is already verified within the scope of sections 6.3 and 6.4.

[KSCH] PDU Session control is just one procedure using UL and DL TRANSFERs. Chapter 5.4.5.1 lists 9 different payload container types (a) to (i) most of them are not covered by the proposed TPs till now.

    - Verify that the IUT, upon receiving the PDU SESSION AUTHENTICATION COMPLETE Message after completing the PDU session authentication and authorization procedure, successfully completes the process by sending PDU SESSION ESTABLISHMENT ACCEPT.

## 6.3.1.2.3 Abnormal cases on the network side (FF)

TP_5GNAS_AMF_UPA_ABN_01

- TP_5GNAS_AMF_UPA_ABN_01

    - Verify that the IUT retransmits PDU SESSION AUTHENTICATION COMMAND message after timer T3590 expiration first time.

TP_5GNAS_AMF_UPA_ABN_02

- TP_5GNAS_AMF_UPA_ABN_02

    - Verify that the IUT aborts the procedure after timer T3590 expiration four times.

/*!

 * \file      params_ngap.hh

 * \brief     Header file for the parameter dictionary.

 * \author    ETSI TTF T033

 * \copyright ETSI Copyright Notification

 *            No part may be reproduced except as authorized by written permission.

 *            The copyright and the foregoing restriction extend to reproduction in all media.

 *            All rights reserved.

 * \version   0.1

 */

#pragma once

#include <map>

#include <string>

#include <vector>

#include "params.hh"

/*!

 * \class params_ngap

 * \brief This class provides basic functionalities for an ITS dictionary

 */

class params_ngap : public params {

public: //! \publicsection

  /*!

   * \brief Default constructor

   *        Create a new instance of the params_ngap class

   */

  params_ngap() : params() {};

  /*!

   * \brief Default destructor

   */

  virtual ~params_ngap(){};

}; // End of class params_ngap

/*!

 * \file      param_sits.cc

 * \brief     Source file for the parameter dictionary.

 * \author    ETSI TTF T033

 * \copyright ETSI Copyright Notification

 *            No part may be reproduced except as authorized by written permission.

 *            The copyright and the foregoing restriction extend to reproduction in all media.

 *            All rights reserved.

 * \version   0.1

 */

#include <regex>

#include <stdexcept>

#include "loggers.hh"

#include "params_ngap.hh"

[MODULE_PARAMETERS]

# This section shall contain the values of all parameters that are defined in your TTCN-3 modules.

NAS_Pics.PICS_NAS_AMF_IUT := false

NAS_Pics.PICS_NAS_AMF_IUT := true

#NAS_Pics.PICS_NAS_AMF_IUT := false

#NAS_Pics.PICS_NAS_AMF_IUT := true

NG_NAS_Pics.PICS_NGNAS := true

[LOGGING]

# In this section you can specify the name of the log file and the classes of events

[TESTPORT_PARAMETERS]

# In this section you can specify parameters that are passed to Test Ports.

aMFNASComponent.N2_gNBaMF_P.params := "NAS/ETH/PCAP_FILE(file=../captures/free5gc.pcap)"

system.NGAP_gNB_1.params := "NGAP/SCTP_FILE/IP_OFFLINE/PCAP_FILE(file=../captures/TP_5GNAS_AMF_REG_REJ_01.pcapng)"

system.N2_gNBaMF_P.params := "NGAP/SCTP_FILE/IP_OFFLINE/PCAP_FILE(file=../captures/TP_5GNAS_AMF_REG_REJ_01.pcapng)"

#aMFNASComponent.N2_gNBaMF_P.params := "NAS/SCTP_FILE/IP_FILE/ETH/PCAP_FILE(file=../captures/free5gc.pcap)"

[DEFINE]

# In this section you can create macro definitions,

# In this section you can specify what parts of your test suite you want to execute.

#AtsImsIot_TestControl.control

#NG_NAS_TestCases.TC_5GNAS_AMF_AUT_REQ_01

#NG_NAS_TestCases.TC_5GNAS_AMF_AUT_REQ_02

#NG_NAS_TestCases.TC_5GNAS_AMF_AUT_REQ_03

#NG_NAS_TestCases.TC_5GNAS_AMF_AUT_REQ_04

#NG_NAS_TestCases.TC_5GNAS_AMF_AUT_REQ_05

#NG_NAS_TestCases.TC_NGNAS_AMF_AUT_SEQ_01

#NG_NAS_TestCases.TC_5GNAS_AMF_REG_ACC_01

#NG_NAS_TestCases.TC_5GNAS_AMF_REG_ACC_02

#NG_NAS_TestCases.TC_5GNAS_AMF_REG_ACC_03

NG_NAS_TestCases.TC_5GNAS_AMF_REG_REJ_01

#NG_NAS_TestCases.TC_5GNAS_AMF_REG_REJ_02

[GROUPS]

# In this section you can specify groups of hosts. These groups can be used inside the

# [COMPONENTS] section to restrict the creation of certain PTCs to a given set of hosts.

[TESTPORT_PARAMETERS]

# In this section you can specify parameters that are passed to Test Ports.

aMFNASComponent.N2_gNBaMF_P.params := "NAS/ETH/PCAP_FILE(file=../captures/free5gc.pcap)"

system.NGAP_gNB_1.params := "NAS/NGAP/SCTP_FILE/IP_OFFLINE/PCAP_FILE(file=../captures/5g_reg.pcapng)"

system.N2_gNBaMF_P.params := "NAS/NGAP/SCTP_FILE/IP_OFFLINE/PCAP_FILE(file=../captures/5g_reg.pcapng)"

#aMFNASComponent.N2_gNBaMF_P.params := "NAS/SCTP_FILE/IP_FILE/ETH/PCAP_FILE(file=../captures/free5gc.pcap)"

[DEFINE]

# In this section you can create macro definitions,