Adding AtsNGAP config files

[MODULE_PARAMETERS]

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

NGAP_Pics.PICS_OFFLINE_MODE := true

NGAP_Pics.PICS_NGAP_AMF_IUT := true

# 5GRegAuthSec_deReg.pcap

LibNGAP_Pixits.PX_AMF_NAME         := "Kontron5G-amf"

LibNGAP_Pixits.PX_RAN_UE_NGAP_ID   := 0

LibNGAP_Pixits.PX_AMF_UE_NGAP_ID   := 22 #8934

LibNGAP_Pixits.PX_PLMN_IDENTITY    := '00f110'O

LibNGAP_Pixits.PX_AMF_REGION_ID    := '00000010'B

LibNGAP_Pixits.PX_AMF_SET_ID       := '0000000001'B

LibNGAP_Pixits.PX_AMF_POINTER      := '011111'B

LibNGAP_Pixits.PX_GNB_ID           := '0000000000000001001110'B

LibNGAP_Pixits.PX_RAN_NODE_NAME    := "Jenkins-Open5gs-1-0"

LibNGAP_Pixits.PX_TACode           := '000001'O

LibNGAP_Pixits.PX_SST              := '01'O

LibNGAP_Pixits.PX_SD               := '000009'O

Lib_NG_NAS_Pixits.PX_CHECK_SECURITY                  := false

Lib_NG_NAS_Pixits.PX_SUPI_FORMAT                     := '0000'B

Lib_NG_NAS_Pixits.PX_SUPI_DIGITS                     := '00f110214300014444330302'O

# OP

Lib_NG_NAS_Pixits.PX_OPERATOR_KEY                    := '00000000000000000000000000000000'O

# OPc

Lib_NG_NAS_Pixits.PX_OPERATOR_SECRET_KEY             := '00000000000000000000000000000000'O

Lib_NG_NAS_Pixits.PX_FORCE_USING_OPERATOR_SECRET_KEY := true

Lib_NG_NAS_Pixits.PX_SUBSCRIPTION_KEY                := '00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'B

Lib_NG_NAS_Pixits.PX_PLMN                            := '00f110'O;

NAS_5GC_Parameters.px_NAS_5GC_XRES_Length := 8 # In ETSI TS 135 206 V16.0.0 (2020-08) Table Table 5. f2 output, RES length is 8 octets (64 bits)

[LOGGING]

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

# you want to log into the file or display on console (standard error).

LogFile := "../logs/AtsNGAP/%e.%h-%r.%s"

FileMask := LOG_ALL | USER | DEBUG | MATCHING

ConsoleMask := LOG_ALL | USER | DEBUG | MATCHING

#FileMask := ERROR | WARNING | USER | MATCHING | EXECUTOR_RUNTIME | VERDICTOP | PORTEVENT | TESTCASE

#ConsoleMask := ERROR | WARNING | USER | MATCHING | EXECUTOR_RUNTIME | VERDICTOP | PORTEVENT | TESTCASE

LogSourceInfo := Stack

LogEntityName:= Yes

LogEventTypes:= Yes

#TimeStampFormat := DateTime

[TESTPORT_PARAMETERS]

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

#system.NGAP_gNB_1.params := "NGAP/SCTP(server=192.168.1.21,port=4444,debug=1)"

#system.N2_gNBaMF_P.params := "NGAP/SCTP(server=192.168.1.21,port=4444,debug=1)"

system.NGAP_gNB_1.params := "NGAP/SCTP_FILE/IP_OFFLINE/ETH(mac_src=8c554ac1eee0,mac_dst=8c554ac1eee1)/PCAP_FILE(file=../captures/5GRegAuthSec_deReg.pcap)"

system.N2_gNBaMF_P.params := "NGAP/SCTP_FILE/IP_OFFLINE/ETH(mac_src=8c554ac1eee0,mac_dst=8c554ac1eee1)/PCAP_FILE(file=../captures/5GRegAuthSec_deReg.pcap)"

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

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

[DEFINE]

# In this section you can create macro definitions,

# that can be used in other configuration file sections except [INCLUDE] and [ORDERED_INCLUDE].

[INCLUDE]

# To use configuration settings given in other configuration files,

# the configuration files just need to be listed in this section, with their full or relative pathnames.

[ORDERED_INCLUDE]

# To use configuration settings given in other configuration files,

# the configuration files just need to be listed in this section, with their full or relative pathnames.

[EXTERNAL_COMMANDS]

# This section can define external commands (shell scripts) to be executed by the ETS

# whenever a control part or test case is started or terminated.

#BeginTestCase := ""

#EndTestCase := ""

#BeginControlPart := ""

#EndControlPart := ""

[EXECUTE]

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

#AtsImsIot_TestControl.control

# Verify that the IUT can send a  PDU SESSION RESOURCE SETUP REQUEST with at least one PDU session resource list to established PDU session.

#NGAP_TestCases.TC_NGAP_AMF_PDU_01

# Verify that the IUT can send a  PDU_SESSION_RESOURCE_RELEASE_COMMAND to release PDU session.

#NGAP_TestCases.TC_NGAP_AMF_PDU_02

# Verify that the IUT can send a  PDU_SESSION_RESOURCE_MODIFY_REQUEST to modify PDU session.

#NGAP_TestCases.TC_NGAP_AMF_PDU_03

# Verify that the AMF node successfully processes a  PDU_SESSION_RESOURCE_MODIFY_INDICATION contains mandatory IEs and answers with PDU_SESSION_RESOURCE_MODIFY_CONFIRM for successfully modified PDU session.

#NGAP_TestCases.TC_NGAP_AMF_PDU_04

# Verify that the AMF node processes a  PDU_SESSION_RESOURCE_MODIFY_INDICATION contains mandatory IEs and answers with PDU_SESSION_RESOURCE_MODIFY_CONFIRM for not successfully modified PDU session.

#NGAP_TestCases.TC_NGAP_AMF_PDU_05

# Verify the IUT correctly sets the UE Context after Authentication and Security procedure has been executed

#NGAP_TestCases.TC_NGAP_AMF_CMP_01

# Verify that the IUT can send a UE CONTEXT RELEASE COMMAND that contains both the AMF_UE_NGAP_ID IE and the RAN_UE_NGAP_ID IE or only AMF_UE_NGAP_ID

NGAP_TestCases.TC_NGAP_AMF_CMP_02

# Verify that the IUT sends a UE CONTEXT RELEASE COMMAND after UE_CONTEXT_RELEASE_REQUEST to release the UE-associated logic NG-connection due to NG-RAN node generated reasons

#NGAP_TestCases.TC_NGAP_AMF_CMP_03

# Verify that the IUT can send a UE CONTEXT MODIFICATION REQUEST containing mandatory IEs

#NGAP_TestCases.TC_NGAP_AMF_CMP_04

# Verify that the IUT can send a CONNECTION ESTABLISHMENT INDICATION that contains mandatory IEs

#NGAP_TestCases.TC_NGAP_AMF_CMP_05

# Verify that the IUT can send an AMF CP RELOCATION INDICATION that contains mandatory IEs

#NGAP_TestCases.TC_NGAP_AMF_CMP_06

# Verify that the IUT can successfully request UE information from the AMF

#NGAP_TestCases.TC_NGAP_AMF_CMP_07

# Verify that the AMF node successfully processes a UE CONTEXT SUSPEND REQUEST containing mandatory IEs and answers with UE CONTEXT SUSPEND REQUEST RESPONSE with successfully suspend UE context

#NGAP_TestCases.TC_NGAP_AMF_CMP_08

# Verify that the AMF node successfully processes a UE CONTEXT SUSPEND REQUEST containing mandatory IEs and answers with UE CONTEXT SUSPEND FAILURE with failed suspension

#NGAP_TestCases.TC_NGAP_AMF_CMP_09

# Verify that the AMF node successfully processes a UE CONTEXT RESUME REQUEST containing mandatory IEs and answers with UE CONTEXT RESUME RESPONSE with successfully resume UE context

#NGAP_TestCases.TC_NGAP_AMF_CMP_10

# Verify that the AMF node successfully processes a UE CONTEXT RESUME REQUEST containing mandatory IEs and answers with UE CONTEXT RESUME FAILURE with failing to resume UE context

#NGAP_TestCases.TC_NGAP_AMF_CMP_11

# Verify that the AMF node successfully processes a HANDOVER REQUIRED message contains mandatory IEs and answers with HANDOVER COMMAND with successfully handover.

#NGAP_TestCases.TC_NGAP_AMF_MMP_01

# Verify that the AMF node successfully processes a HANDOVER REQUIRED message contains mandatory IEs and answers with HANDOVER PREPARATION FAILURE because the UE is not longer available.

#NGAP_TestCases.TC_NGAP_AMF_MMP_02

# Verify that the AMF node successfully sends a HANDOVER REQUEST message that contains mandatory IEs to the GNB.

#NGAP_TestCases.TC_NGAP_AMF_MMP_03

# Verify that the AMF node successfully processes a PATH SWITCH REQUEST message that contains mandatory IEs and answers with PATH SWITCH REQUEST ACKNOWLEDGE to acknowledge the path switch.

#NGAP_TestCases.TC_NGAP_AMF_MMP_04

# Verify that the AMF node successfully processes a PATH SWITCH REQUEST message that contains mandatory IEs and two PDU Sessions with same ID and answers with PATH SWITCH REQUEST FAILURE.

#NGAP_TestCases.TC_NGAP_AMF_MMP_05

# Verify that the AMF node successfully processes a HANDOVER CANCEL message that contains mandatory IEs and answers with HANDOVER CANCEL ACKNOWLEDGE to confirm that the ongoing handover was cancelled.

#NGAP_TestCases.TC_NGAP_AMF_MMP_06

# Verify that the AMF node successfully sends a DOWNLINK RAN STATUS TRANSFER message that contains mandatory IEs.

#NGAP_TestCases.TC_NGAP_AMF_MMP_07

# Verify that the NG-RAN node successfully sends a Handover Success message to the AMF.

#NGAP_TestCases.TC_NGAP_AMF_MMP_08

# Verify that the AMF node successfully sends a DOWNLINK RAN EARLY STATUS TRANSFER message that contains mandatory IEs.

#NGAP_TestCases.TC_NGAP_AMF_MMP_09

# Verify that the IUT can send an DOWNLINK NAS TRANSPORT message to carry NAS information over the NG interface.

#NGAP_TestCases.TC_NGAP_AMF_NAS_01

# Verify that the IUT can send an REROUTE NAS REQUEST message to reroute the INITIAL UE MESSAGE message to another AMF.

#NGAP_TestCases.TC_NGAP_AMF_NAS_02

# Verify that the AMF node successfully processes a NG SETUP REQEST message that contains mandatory IEs and answers with NG SETUP RESPONSE to acknowledge the setup.

#NGAP_TestCases.TC_NGAP_AMF_IMP_01

# Verify that the AMF node successfully processes a NG SETUP REQEST message that contains mandatory IEs and answers with NG SETUP RESPONSE to acknowledge the setup.

#NGAP_TestCases.TC_NGAP_AMF_IMP_02

# Verify that the AMF node successfully processes a NG SETUP REQEST message with optional field UE Retention Information and answers with NG SETUP RESPONSE to acknowledge the setup.

#NGAP_TestCases.TC_NGAP_AMF_IMP_03

# Verify that the AMF node successfully processes a NG SETUP REQEST message with different optional fields and answers with NG SETUP RESPONSE to acknowledge the setup.

#NGAP_TestCases.TC_NGAP_AMF_IMP_04

# Verify that the AMF node successfully processes a RAN CONFIGURATION UPDATE message with RAN CONFIGURATION UPDATE ACKNOWLEDGE to acknowledge the update.

#NGAP_TestCases.TC_NGAP_AMF_IMP_05

# Verify that the AMF node successfully declines a RAN CONFIGURATION UPDATE message with RAN CONFIGURATION UPDATE FAILURE when the AMF is not able to handle the request.

#NGAP_TestCases.TC_NGAP_AMF_IMP_06

# Verify that the IUT can send a AMF CONFIGURATION UPDATE message to the AMF.

#NGAP_TestCases.TC_NGAP_AMF_IMP_07

# Verify that the AMF node successfully processes a NG RESET message that contains mandatory IEs and answers with NG RESET ACKNOWLEDGE to acknowledge the reset.

#NGAP_TestCases.TC_NGAP_AMF_IMP_08

# Verify that the AMF can send a ERROR INDICATION to the GNB when a error occurs.

#NGAP_TestCases.TC_NGAP_AMF_IMP_09

# Verify that the AMF can send a AMF STATUS INDICATION to the GNB when a error occurs.

#NGAP_TestCases.TC_NGAP_AMF_IMP_10

# Verify that the AMF can send a OVERLOAD START to the GNB.

#NGAP_TestCases.TC_NGAP_AMF_IMP_11

# Verify that the AMF can send a OVERLOAD STOP to the GNB.

#NGAP_TestCases.TC_NGAP_AMF_IMP_12

# Verify that the IUT can send a WRITE REPLACE WARNING REQUEST to start broadcasting of warning messages.

#NGAP_TestCases.TC_NGAP_AMF_WTP_01

#Verify that the IUT can send a PWS CANCEL REQUEST to cancel broadcasting of warning messages.

#NGAP_TestCases.TC_NGAP_AMF_WTP_02

# Verify that the IUT can send a TRACE_START to initiate a trace session for a UE.

#NGAP_TestCases.TC_NGAP_AMF_TRP_01

# Verify that the IUT can send a DEACTIVATE_TRACE to deactivate a trace session for a UE.

#NGAP_TestCases.TC_NGAP_AMF_TRP_02

# Verify that the IUT can send a UE TNLA BINDING RELEASE REQUEST to initiate a UE TNLA Binding Release procedure.

#NGAP_TestCases.TC_NGAP_AMF_UBP_01

# Verify that the IUT can send a UE RADIO CAPABILITY ID MAPPING RESPONSE message that contains mandatory IEs to provide the UE radio capabilities id mapping.

#NGAP_TestCases.TC_NGAP_AMF_URP_02

# Verify that the IUT can send a DOWNLINK RIM INFORMATION TRANSFER.

#NGAP_TestCases.TC_NGAP_AMF_RIP_01

[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.

[COMPONENTS]

# This section consists of rules restricting the location of created PTCs.

[MAIN_CONTROLLER]

# The options herein control the behavior of MC.

KillTimer := 10.0

LocalAddress := 127.0.0.1

TCPPort := 12000

NumHCs := 1

[MODULE_PARAMETERS]

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

NGAP_Pics.PICS_NGAP_GNB_IUT := true

NGAP_Pics.PICS_NGAP_AMF_IUT := false

[LOGGING]

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

# you want to log into the file or display on console (standard error).

LogFile := "../logs/AtsNGAP/%e.%h-%r.%s"

FileMask := LOG_ALL | USER | DEBUG | MATCHING

ConsoleMask := LOG_ALL | USER | DEBUG | MATCHING

#FileMask := ERROR | WARNING | USER | MATCHING | EXECUTOR_RUNTIME | VERDICTOP | PORTEVENT | TESTCASE

#ConsoleMask := ERROR | WARNING | USER | MATCHING | EXECUTOR_RUNTIME | VERDICTOP | PORTEVENT | TESTCASE

LogSourceInfo := Stack

LogEntityName:= Yes

LogEventTypes:= Yes

#TimeStampFormat := DateTime

[TESTPORT_PARAMETERS]

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

aMFNGAPComponent.N2_gNBaMF_P.params := "NGAP/ETH/PCAP_FILE(file=../captures/free5gc.pcap)"

[DEFINE]

# In this section you can create macro definitions,

# that can be used in other configuration file sections except [INCLUDE] and [ORDERED_INCLUDE].

[INCLUDE]

# To use configuration settings given in other configuration files,

# the configuration files just need to be listed in this section, with their full or relative pathnames.

[ORDERED_INCLUDE]

# To use configuration settings given in other configuration files,

# the configuration files just need to be listed in this section, with their full or relative pathnames.

[EXTERNAL_COMMANDS]

# This section can define external commands (shell scripts) to be executed by the ETS

# whenever a control part or test case is started or terminated.

#BeginTestCase := ""

#EndTestCase := ""

#BeginControlPart := ""

#EndControlPart := ""

[EXECUTE]

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

#AtsImsIot_TestControl.control

# Verify that the NG-RAN node successfully processes a  PDU SESSION RESOURCE SETUP REQUEST contains mandatory IEs and answers with PDU SESSION RESOURCE SETUP RESPONSE for successfully established PDU session.

NGAP_TestCases.TC_NGAP_GNB_PDU_01

# Verify that the NG-RAN node reports the establishment of the corresponding PDU session as failed if a PDU SESSION RESOURCE SETUP REQUEST contains several PDU Session ID IEs set to the same value.

#NGAP_TestCases.TC_NGAP_GNB_PDU_02

# Verify that the NG-RAN node reports the establishment of the new PDU session as failed if a PDU SESSION RESOURCE SETUP REQUEST contains a PDU Session ID IE set to value that identifies an active PDU Session. NOTE: Run TP_NGAP_GNB_PDU_01 before this TP.

#NGAP_TestCases.TC_NGAP_GNB_PDU_03

# Verify that the NG-RAN node reports the establishment of the corresponding PDU session as failed if a PDU SESSION RESOURCE SETUP REQUEST contains a QoS Flow Setup Request List IE in the PDU Session Resource Setup Request Transfer IE including at least one Non-GBR QoS flow but the PDU Session Aggregate Maximum Bit Rate IE is not present.

#NGAP_TestCases.TC_NGAP_GNB_PDU_04

# Verify that the NG-RAN node successfully processes a  PDU SESSION RESOURCE RELEASE COMMAND contains mandatory IEs and answers with PDU SESSION RESOURCE RELEASE RESPONSE to release PDU session.

#NGAP_TestCases.TC_NGAP_GNB_PDU_05

# Verify that the NG-RAN node successfully processes a  PDU SESSION RESOURCE RELEASE COMMAND containing multiple PDU Session ID IEs set to the same value and ignore the duplication.

#NGAP_TestCases.TC_NGAP_GNB_PDU_05

# Verify that the NG-RAN node successfully processes a  PDU SESSION RESOURCE MODIFY REQUEST contains mandatory IEs and answers with PDU SESSION RESOURCE MODIFY RESPONSE for successfully modified PDU session.

#NGAP_TestCases.TC_NGAP_GNB_PDU_07

# Verify that the IUT can send a  PDU_SESSION_RESOURCE_NOTIFY that already established QoS flow or PDU session for given UE are release.

#NGAP_TestCases.TC_NGAP_GNB_PDU_08

# Verify that the IUT can send a PDU_SESSION_RESOURCE_MODIFY_INDICATION to request modification of established PDU session.

#NGAP_TestCases.TC_NGAP_GNB_PDU_09

# Verify that the IUT can send a HANDOVER REQUIRED message containing mandatory IEs.

#NGAP_TestCases.TC_NGAP_GNB_MMP_01

# Verify that the GNB node successfully processes a HANDOVER REQUEST message that contains mandatory IEs and answers with HANDOVER REQUEST ACKNOWLEDGE to acknowledge the handover.

#NGAP_TestCases.TC_NGAP_GNB_MMP_02

# Verify that the GNB node successfully processes a HANDOVER REQUEST message that contains mandatory IEs and answers with HANDOVER REQUEST FAILURE because the UE is not longer available.

#NGAP_TestCases.TC_NGAP_GNB_MMP_03

# Verify that the GNB node successfully processes a HANDOVER REQUEST message that contains optional IEs and answers with HANDOVER REQUEST ACKNOWLEDGE to acknowledge the handover.

#NGAP_TestCases.TC_NGAP_GNB_MMP_04

# Verify that the GNB node successfully processes a HANDOVER REQUEST message that contains optional IEs within the Handover Request Transfer IEs and answers with correct HANDOVER REQUEST ACKNOWLEDGE.

#NGAP_TestCases.TC_NGAP_GNB_MMP_05

# Verify that the GNB node successfully processes a HANDOVER REQUEST message for an intra-system handover and answers with HANDOVER REQUEST ACKNOWLEDGE to acknowledge the handover.

#NGAP_TestCases.TC_NGAP_GNB_MMP_06

# Verify that the AMF node successfully sends a HANDOVER NOTIFICATION message that contains mandatory IEs to the AMF.

#NGAP_TestCases.TC_NGAP_GNB_MMP_07

# Verify that the AMF node successfully sends a PATH SWITCH REQUEST message that contains mandatory IEs to the AMF.

#NGAP_TestCases.TC_NGAP_GNB_MMP_08

# Verify that the GNB node successfully sends a HANDOVER CANCEL message that contains mandatory IEs to the AMF.

#NGAP_TestCases.TC_NGAP_GNB_MMP_09

# Verify that the NG-RAN node successfully send a UPLINK RAN STATUS TRANSFER message to the AMF.

#NGAP_TestCases.TC_NGAP_GNB_MMP_10

# Verify that the NG-RAN node successfully sends a UPLINK RAN EARLY STATUS TRANSFER message to the AMF.

#NGAP_TestCases.TC_NGAP_GNB_MMP_11

# Verify that the IUT can send an INITIAL UE MESSAGE to indicate the initiation of a NAS Transport procedure.

#NGAP_TestCases.TC_NGAP_GNB_NAS_01

# Verify that the IUT can send an UPLINK NAS TRANSPORT message to the AMF.

#NGAP_TestCases.TC_NGAP_GNB_NAS_02

# Verify that the IUT can send a NAS NON DELIVERY INDICATION message to t.he AMF

#NGAP_TestCases.TC_NGAP_GNB_NAS_03

# Verify that the GNB node successfully sends a NG SETUP REQEST message to the AMF.

#NGAP_TestCases.TC_NGAP_GNB_IMP_01

# Verify that the IUT can send a RAN CONFIGURATION UPDATE message to the AMF.

#NGAP_TestCases.TC_NGAP_GNB_IMP_02

# Verify that the GNB node successfully processes a AMF CONFIGURATION UPDATE message with AMF CONFIGURATION UPDATE ACKNOWLEDGE to acknowledge the update.

#NGAP_TestCases.TC_NGAP_GNB_IMP_03

# Verify that the GNB node can send a AMF CONFIGURATION UPDATE FAILURE.

#NGAP_TestCases.TC_NGAP_GNB_IMP_04

# Verify that the GNB node successfully processes a NG RESET message that contains mandatory IEs and answers with NG RESET ACKNOWLEDGE to acknowledge the reset.

#NGAP_TestCases.TC_NGAP_GNB_IMP_05

# Verify that the GNB can send a ERROR INDICATION to the AMF when a error occurs.

#NGAP_TestCases.TC_NGAP_GNB_IMP_06

# Verify that the NG-RAN node successfully processes a WRITE-REPLACE WARNING REQUEST containing mandatory IEs and answers with WRITE-REPLACE WARNING RESPONSE to start broadcasting of warning messages.

#NGAP_TestCases.TC_NGAP_GNB_WTP_01

# Verify that the NG-RAN node successfully processes a WRITE-REPLACE WARNING REQUEST containing Message Identifier IE and/or Serial Number IE different from those in the warning message being broadcast and if Concurent Warning Message Indicator is not present then IUT node answers with WRITE-REPLACE WARNING RESPONSE  and replaces the warning message being broadcast with newly received one for that area.

#NGAP_TestCases.TC_NGAP_GNB_WTP_02

# Verify that the NG-RAN node successfully processes a PWS CANCEL REQUEST containing mandatory IEs and answers with PWS CANCEL RESPONSE to cancel an already ongoing broadcast warning messages in all of the cells in the NG-RAN.

#NGAP_TestCases.TC_NGAP_GNB_WTP_03

# Verify that the IUT can send a PWS RESTART INDICATION to inform AMF that PWS information for some or all cells may be reloaded from the CBC if needed.

#NGAP_TestCases.TC_NGAP_GNB_WTP_04

# Verify that the IUT can send a PWS FAILURE INDICATION to inform AMF that ongoing PWS operation for one or more cells has failed.

#NGAP_TestCases.TC_NGAP_GNB_WTP_05

# Verify that the IUT can send a TRACE_FAILURE_INDICATION to inform AMF that Trace Start procedure has failed due to an interaction with handover procedure.

#NGAP_TestCases.TC_NGAP_GNB_TRP_01

# Verify that the IUT can send a TRACE_FAILURE_INDICATION to inform AMF that a Deactivate Trace procedure has failed due to an interaction with handover procedure.

#NGAP_TestCases.TC_NGAP_GNB_TRP_02

# Verify that the IUT can send a CELL_TRAFFIC_TRACE to send the allocated Trace Recording Session Reference and Trace Reference to AMF.

#NGAP_TestCases.TC_NGAP_GNB_TRP_03

[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.

[COMPONENTS]

# This section consists of rules restricting the location of created PTCs.

[MAIN_CONTROLLER]

# The options herein control the behavior of MC.

KillTimer := 10.0

LocalAddress := 127.0.0.1

TCPPort := 12000

NumHCs := 1