NGAP Tab

NGAP Version (38.413)

Select NGAP Version. 38.413 is the Spec ID.

Options: 15.0.0/Jun2018, 15.1.0/Sep2018, 15.2.0/Jan2019 , 15.2.0-Variant1/Jan2019 , 15.2.0-Variant2/Mar2019 , 15.4.0/Jul2019, 16.2.0/July2020, 17.6.0/Sep2023 (default)

In the RIC Nodal Test Case, the N2 interface contains NGAP (gNB) and (AMF Node) tabs. Version 17.6.0/Sep2023 or greater is supported.

Tcl Parameter: AmfNgapVersion

Tcl Parameter: An5gNgapVersion

Tcl Parameter: N50NamfNgapVersion

Default Paging DRX

This is the default Paging DRX applied to AMF Nodal and RIC Nodal (under gNB tab) testing only.

Options: v32, v64, v128, v256

Default:  v32

Tcl Parameter: An5gNgapDefaultPagingDrx

Ignore Pages Before Answering

Enter number of pages to ignore. Can be used to create a paging escalation scenario for AMF Nodal to force AMF Node to do a paging escalation.

Range: -1 to 254 (-1 means the UE never answers)

Default:  0

Tcl Parameter: An5gNgapIgnorePages

Handover Notify Delay (ms)

Enter the Handover Notify delay in milliseconds.

Range: 0 to 10000

Default:  0

Tcl Parameter: An5gNgapHoNotifyDelay

Available in AMF Nodal. Add a Handover Timeout to trigger retries for N2 and Xn handovers when there is no response from the AMF DUT. 

When this timer expires, a timeout message is sent to MM layer which initiates a reset. 

Specification references :

23.502 - Procedures for the 5G System (5GS)

23.501 - System architecture for the 5G System (5GS)

38.413 - NG Application Protocol (NGAP)

Range: 0 to 65535

Default:  6

Tcl Parameter: An5gNgapHoTimer

Handover Release Delay (ms)

Enter the Handover Release delay in milliseconds. Available on AMF Node test case.

Range: 0 to 10000

Default:  1000

Tcl Parameters: AmfNgapHoReleaseDelay

Idle Entry Time (ms)

Enter the idle entry time in milliseconds per 3GPP 23.501 - section 5.3.3.3.3 - NAS Signalling Release Procedure initiated by 5G AN Node (N3IWF). Available on N3IWF Node test case.

Range: 0, or 1000 <= VALUE >= 4294967295

Default:  0

Tcl Parameter: An5gNgapIdleEntryTime

Available on AMF Nodal when Test Activity =  Inter Technology Mobility, Vo5G and EPS Fallback are enabled and Handoff Type = REG/TAU.

Enter time delay in milliseconds between UE Context Release Request and TAU Request.

Range: 0 to 10000 

Default:  0

Tcl Parameter: An5gNgapEpsRedirDelay

UE Capability Match Request procedure

This option is start checking the support condition of IMS voice over PS.
AMF node sent “UE Radio Capability Check Request” message to gNB.
This message is defined in following sections: 
TS38.413 8.14.2
TS38.413 9.2.13.2
 
The role of these messages is as follows:
UE Radio Capability check request: (from 38.413 8.14.2)
The purpose of the UE Radio Capability Check procedure is for the AMF to request the NG-RAN node to derive and provide an indication to the AMF on whether the UE radio capabilities are compatible with the network configuration for IMS voice.
 
UE Radio Capability match request: (from 36.413 8.3.5)
The purpose of the UE Radio Capability Match procedure is for the MME to request the eNB to derive and provide an indication to the MME whether the UE radio capabilities are compatible with the network configuration for voice.
community.

Available on AMF Node test case.

Per 3GPP TS 23.502 v 15.4.1 - 4.2.8a which is the same as Ue radio capability check procedure in 38.413 8.14.2

Available when NGAP Version is = or > 15.2.0

Tcl Parameter: AmfNgapUeCapMatchReqProcEn

Support Mobility NGAP Sessions

Limits the Number of Subscribers to 1/2 the licensed max value when "Support Mobility NGAP Sessions" is checked.  (by default, it is checked).

Available on AMF Node test case.

Tcl Parameter: AmfNgapHoSessEn

Select the NGAP Response (Initial Context Setup Request / Downlink NAS Transport) for each Initial UE Message Type.

When the UE Context Request IE is not received in the Initial UE Message, if "Trigger Ue Context procedure for all NAS procedures, When UE Context Request IE is not received in the Initial UE Message" is checked, then NGAP message InitialContextSetupRequest will be triggered right after security check was passed. Otherwise, NGAP message InitialContextSetupRequest will be delayed until first PDUSessionResourceSetupRequestTransfer be send out. Refer to 38.413-g20 > 8.2.5.2 or Specify NGAP Response per NAS Procedure:

When "Trigger Ue Context procedure for all NAS procedures, When UE Context Request IE is not received in the Initial UE Message" is checked, the AMF node responds with accept in the initial context setup for all the initial msg types, now this can be controlled by msg type. (See the table below for supported "Initial UE Message Type" and "NGAP Response").

For example, "Initial registration" the AMF node responds with accept in the "Initial Context Setup Request" if it is selected as the NGAP Response. However, for "Mobility Registration Update" the AMF node can respond with accept in the "Downlink NAS Transport" if it is selected as the NGAP Response. The user can control the NGAP response for each selected "Initial UE Message Type" that is supported in the table below.

Specify NGAP Response per NAS Procedure in the table below.

Select the Initial UE Message Type and the NGAP Response.

Available in AMF Node test case.

Tcl Parameter: AmfNgapTrigUeCtxNoUcrInitMsgEn

Tcl Parameter: AmfNgapInitRegRsp

Tcl Parameter: AmfNgapMobRegRsp

Tcl Parameter: AmfNgapPeriodRegRsp

Tcl Parameter: AmfNgapEmerRegRsp

Tcl Parameter: AmfNgapSvcRegRsp

Available in AMF Node test case.

When enabled, the AMF will send Handover Preparation Failure message in response to Handover Required Message from gNB/UE.

For example:

UE/gNB is connected to AMF -> UE/gNB sends HandoverRequired -> AMF sends HandoverPreparationFailure to gNB/UE -> UE/gNB sends HandoverRequired -> AMF handles it as normal -> UE/gNB sends HandoverRequired -> AMF sends HandoverPreparationFailure to gNB/UE -> AMF handles it as normal. If gNB/UE keep triggering handover without being disconnected, it will be toggled.

Cause is the Radio Network Cause value which is included in Handover Preparation Failure Message. This is the value of enumerated Radio Network Layer Cause defined in 9.3.1.2 Cause - TS 38.413. The default value, 7 is “Handover failure in target 5GC/NGRAN node or target system”.

Range : 0 to 255

Defult : 7

Tcl Parameter: AmfNgapHoPrepFailEmulEn

Tcl Parameter: AmfNgapHoPrepFailCause

Available in AMF Node test case.

When enabled, the AMF will add the OPTIONAL Extended Connected Time IE to the HANDOVER REQUEST Message. Specify the minimum time the RAN should keep the UE in RRC_CONNECTED state. Value of "0" indicates that the AMF is aware of pending data traffic, but no specific time value is requested.

3GPP 38.413 - 9.2.3.4 - HANDOVER REQUEST - Extended Connected Time. This "Extended Connected Time" is only applicable to Version 17.6.0 for HANDOVER REWQUEST Message.

3GPP 38.413 - 9.3.3.31 - SPEC for the Extended Connected Time IE. 

Range: 0 to 255

Default : 0

Tcl Parameter: AmfNgapExtConnTimeHoReqEn

Tcl Parameter: AmfNgapExtConnTimeHoReq

Available in AMF Node test case.

Enables NGAP Message Fuzzing tab.

From the N2/NGAP GUI, select the checkbox Enable NGAP Message Fuzzing. When enabled select the "Message Fuzzing" tab, to specify which messages are required for the test case and at what Probability (%) the message needs to be "Fuzzed."

Tcl Parameter: AmfNgapMsgFuzzingEn

Select for support for Indirect Forwarding for N2 Handover. Available on AMF Nodal test case and on gNB CU Node test case when SA Mode is enabled - select to support Xn HO with data forwarding.

Spec reference:

• 23.502 Procedures for the 5G System (5GS)
• 38.413 NG-RAN; NG Application Protocol (NGAP)
• 29.502 5G System; Session Management Services; Stage 3
• 29.244 Interface between the Control Plane and the User Plane nodes

The N2 based inter NG-RAN node handover is defined in 23.502 clause 4.9.1.3. The following steps highlight the differences between direct and indirect data forwarding:

If the "Direct Forwarding" checkbox is enabled, in the Handover Required message sent from source NG-RAN to source AMF, the Direct Forwarding Path Availability IE will be included in the SM N2 Info ( i.e. Handover Required Transfer ) for each PDU. Otherwise the Direct Forwarding Path Availability IE will NOT be included in the SM N2 Info. The SM N2 Info will then be transferred all the way to the SMF through the N14 ( between source AMF and target AMF ) and N11 ( between target AMF and SMF ) interface. 

If the received SM N2 Info contains an indication of Direct Forwarding Path Availability, the SMF will assume direct data forwarding. Otherwise, the SMF will decide between indirect data forwarding and no data forwarding depending on the network condition. Currently in Landslide, the SMF will always assume indirect dguiata forwarding in this case. The SMF will then send a response to target AMF, which will trigger a Handover Request message towards target NG-RAN. In the Handover Request Ack message, the target NG-RAN will include the DL data forwarding info ( i.e. IP and TEID )  in the SM N2 Info ( i.e. Handover Request Ack Transfer ) for each PDU. Again, this SM N2 Info will be forwarded to the SMF over the N11 interface. Based on prior knowledge, for the direct data forwarding case, the SMF will build an SM N2 Info  ( i.e. Handover Command Transfer ) containing DL forwarding Tunnel Info using what's received in the Handover Request Ack Transfer . For the indirect data forwarding case, the SMF will negotiate an indirect data forwarding tunnel with the UPF through the PFCP modification procedure over the N4 interface. The SMF will then build an SM N2 Info  ( i.e. Handover Command Transfer ) using the UPF DL data forwarding info. The SMF will then send a response to target AMF. For the indirect data forwarding case, the SMF will also start a timer to release the indirect data forwarding tunnel at this point. Currently this timer is hard coded as 1 second in Landslide.  The target AMF will then forward the received SM N2 Info  ( i.e. Handover Command Transfer ) all the way to source NG-RAN through the N14 and N2 interface. When the timer in the previous bullet expires, the SMF will release the indirect data forwarding tunnel on the UPF through the PFCP modification procedure.

Tcl Parameter: An5gNgapDirectFwdingEn

Available in AMF Nodal when "NGAP Version" is set to 16.2.0 or higher. When checked, include Notify Source NG-RAN Node IE in HANDOVER NOTIFY message.

Tcl Parameter: An5gNgapNotifySourceNgranEn

Available in Non 3GPP Access GW Node (previously N3IWF Node) when "NGAP Version" is set to 16.2.0 or higher. When checked, include Selected PLMN Identity IE in INITIAL UE MESSAGE for Non 3GPP Access GW Node. 

Tcl Parameter: An5gNgapPlmnIdInitMsgEn

IMS Voice Support Indicator in UE Capability Match Response

Select to indicate whether the UE Radio capabilities are compatible with the Network Configuration for the IMS Voice at gNodeB. Per 3GPP TS 38.413 v 15.2.0 - 9.3.1.89

Available when NGAP Version is = or > 15.2.0

Options : Supported (default) or Not Supported

Tcl Parameter: An5gNgapImsVoSuptIndInUeCapMatchRsp

Available in gNB CU Node test case when mode = SA Mode.

Enable to select the length of the gNB Node ID.

Rnage : 22 to 32

Default : 22

Tcl Parameter: An5gNgapGnbNodeIdLenEn

Tcl Parameter: An5gNgapGnbNodeIdLen

Select to simulate a location report failure. Per the NG-RAN Location reporting procedures in  TS23.502/4.10 in AMF nodal. NGAP Measurements : Location Reporting Control, Location Report Failure Indication, Location Reports

Reference : Section 8.12 of 3GPP 38413 (Message flows for Location report)

Limitation: From 3GPP38413 document, the maximum number of "area of interest" items are 64. However, due to a limitation in Landslide, we have limited the number of  "area of interest" items to one.

Tcl Parameter: An5gNgapSimLocReportFailEn

Available in AMF Nodal Test Case when NGAP version is set to 15.10 or higher.

When "Simulate UE Context Modification Failure" is enabled on  the N2 | NGAP tab, the UE Context Modification Failure message will be returned in response to UE Context Modification Request. This applies to UE Context Modification Request message received in any scenario.

Tcl Parameter: An5gNgapSimUeCtxtModFailEn

Select to include the UE Context Request IE in the INITIAL UE MESSAGE message. Available in AMF Nodal Test Case.

Reference: 3GPP 38.413 8.6.1 Initial UE Message - If the UE Context Request IE is included in the INITIAL UE MESSAGE message the AMF shall trigger an Initial Context Setup procedure towards the NG-RAN node.

Tcl Parameter: An5gNgapUcrInInitMsgEn

Select to include the optional UE Retention Information IE to the NG Setup request message. Available in AMF Nodal Test Case.

Reference: 3GPP 38.413 9.3.1.117 

Tcl Parameter: An5gNgapUeRetentionInfoEn

Select to include the voiceOverNR in the UE Radio Capability Indication message . Available in AMF Nodal Test Case. This message is sent by the NG-RAN node to provide UE radio capability related information to the AMF.

It requires NGAP Version 15.4.0 or higher.

Spec Reference : 3GPP 38.413 NGAP 

Tcl Parameter: An5gNgapVoiceOverNrEn

Select to simulate a new type of device which is known as RedCap (Reduced Capability) device defined in 3GPP release 17. 

RedCap indication IE is added in the following NGAP protocol messages.

• Initial UE Message
• Path Switch Request
• Handover Request Acknowledge

Available in AMF Nodal Test Case. 

It requires NGAP Version 17.6.0 or higher.

Spec Reference : 3GPP 23.502, 38.306, 38.413 NGAP 

Tcl Parameter: An5gNgapRedCapEn

Select to simulate RAN Configuration Update Failure in response to RAN Configuration update message. Available in AMF Node Test Case. Select RAN Time to Wait after Failure (s) before sending next RAN Configuration Update message.

Options: Not Included (default), 1, 2, 5, 10, 20, 60

Tcl Parameter: AmfNgapSimulateRanConfigFailureEn

Tcl Parameter: AmfNgapRanUpdateTimeToWait

Select to enable the RAN Configuration Update. The fields in the RAN Configuration Update Pane become available for input.

Available in AMF Nodal Test Case.

Tcl Parameter: An5gNgapRanUpdateConfigEn

Select to include the RAN Node Name IE in the RAN Configuration Update.

Enter up to 150 characters.

Default: GNB.Spirent.com

Tcl Parameter: An5gNgapRanNodeNameUpdateEn

Tcl Parameter: An5gNgapUpdateRanNodeName

Select to include the default Paging DRX IE in the RAN Configuration Update.

Options: v32, v64, v128, v256

Default:  v32

Tcl Parameter: An5gNgapDefaultPagingDrxUpdateEn

Tcl Parameter: An5gNgapUpdateDefaultPagingDrx

Enter the update interval time in milliseconds between consecutive RAN Configuration updates.

Range: 10000 to 60000 Default: 30000

Tcl Parameter: An5gNgapRanUpdateConfigTime

Enter the retry interval time in milliseconds. The time to wait before making a retry attempt to send a RAN Configuration update.

Range: 10000 to 60000

Default: 30000

Tcl Parameter: An5gNgapRanUpdateConfigRetryTime

• Starting TAC (Tracking Area Code)

Range : 0 to 16777215

Default:  0

With optional auto-increment pattern #(nnnnnnnn) or #(nnnnnnnn C/I)

• Number of TAC (Tracking Area Code)  - Can add up to 256 TACs per gNodeB.

Default:  1

Up to 256

• SNPN NID (Standalone Non-Public-Networks - New sized ID )  - Available when Version >= 16.2.0. Standalone Non-Public-Networks (SNPN) by adding NID configuration to PLMN ID's used for SNPN in network sharing mode. NID is included in the Broadcast PLMN Item IE for PlmnId’s configured as SNPN. A  default value of zero is used to indicate that NID has not been configured for the PLMN ie PLMN is not an NPN. Zero is used for this purpose as the NID value of zero is reserved (per 23.003). Reference: 3GPP TS 23.501 v16.2.0:  System Architecture for the 5G System, 3GPP TS 38.413 v16.2.0: NG-RAN; NG Application Protocol (NGAP), 3GPP TS 23.003 v16.2.0: Numbering, addressing and identification. (SNPN NID is included in the TDF configuration for NGAP)

Default:  0

Up to 11 Characters

• MCC (Mobile Country Code), and MNC (Mobile Network Code)

Default:  000

Tcl Parameter:

• Extra PLMNs (Public Land Mobile Networks)

Select to include Extra PLMNs in the RAN Configuration Update. Select up to 5 additional PLMNs (Public Land Mobile Network). Available on AMF Nodal Test case.

When Extra PMLNs are disabled, all the UEs use the same PLMN.

Enter Number of PLMNs. Enter MCC, MNC and SNPN NID (Available when Version >= 16.2.0. additional details listed above in SNPN NID section) for each PLMN.

Tcl Parameter: An5gNgapUpdateGnbNumExtraPlmns

Enter the Number of NSSAIs (Network Slice Selection Assistance Information).

Network Slice: A logical network that provides specific network capabilities and network characteristics.

Network Slice Instance: A set of Network Function instances and the required resources (e.g. compute, storage and networking resources) which form a deployed Network Slice.

Per 3GPP TS 23.501, 23.502 and 29.5xx.

The NSSAI contains two components: the SST (Slice / Service Type) and an optional SD (Slice Differentiator).

Range : 1 to 8

sst : 0 up to 255

sd : hex-string, maximum length = 6 (optional)

Tcl Parameter: An5gNgapUpdateGnbNumNssai

Tcl Parameter: An5gNgapUpdateGnbNssai_1

Tcl Parameter: An5gNgapUpdateGnbNssai_2

Tcl Parameter: An5gNgapUpdateGnbNssai_3

Tcl Parameter: An5gNgapUpdateGnbNssai_4

Tcl Parameter: An5gNgapUpdateGnbNssai_5

Tcl Parameter: An5gNgapUpdateGnbNssai_6

Tcl Parameter: An5gNgapUpdateGnbNssai_7

Tcl Parameter: An5gNgapUpdateGnbNssai_8

Select Enable NG-RAN TNL Association to Remove List checkbox for "Number of TNL Associations" dropdown list to become available to select a value in the range of 1-32 to specify the number of TNL Associations to remove.

Additional SCTP endpoint establish a link between the "gNB-A (IP2)" and AMF via SCTP association and RAN Configuration Update messages. gNB Control Node - Additional Transport Network Layer IP 

When the "Number of TNL Associations" is selected, a table with number of rows (1 to 32) equaling "Number of TNL Associations" to becomes available.

• This table contains the following 2 columns:
  • TNL Association Transport Layer Address - a valid IPv4 or IPv6 address is mandatory for each row of this column.
  • TNL Association Transport Layer Address at AMF - a valid IPv4 or IPv6 address is optional for each row of this column

Tcl Parameter: An5gNgapNgRanTnlAssocToRemoveListEn

Tcl Parameter: An5gNgapNgRanTnlAssocToRemoveListNum

Tcl Parameter: An5gNgapNgRanTnlAssocAddr_1

Tcl Parameter: An5gNgapNgRanTnlAssocAddrAtAmf_1

Number of Configurations

Select the Number of configuration profiles for Uplink RAN Configuration transfers. 

This feature supports testing Uplink/Downlink RAN Configuration Transfer message in AMF SUT using AMF Nodal testcase.

AMF Nodal initiates an Uplink RAN Configuration Transfer message towards AMF Node via Sequencer testing mode. Specifically, for each command in the sequencer, user selects message rate, target node, as well as the starting gNB and ending gNB that will initiate the Uplink RAN Configuration Transfer message. The target node information is configured via GUI, and up to 10 target nodes can be configured.

AMF Nodal also replies to Downlink RAN Configuration Transfer message with an Uplink RAN Configuration Transfer message if the Downlink message contains a request. 

The purpose of the Uplink RAN Configuration Transfer procedure is to transfer RAN configuration information from the NG-RAN node to the AMF. The AMF does not interpret the transferred RAN configuration information. This procedure uses non-UE associated signaling. 

The purpose of the Downlink RAN Configuration Transfer procedure is to transfer RAN configuration information from the AMF to the NG-RAN node. This procedure uses non-UE associated signaling.

Range : 1 to 10

Default : 1

Tcl Parameter: An5gNgapRanCfgXferProfileNum

SON Configuration Transfer

or

EN-DC SON Configuration Transfer

Enter the following for SON Configuration Transfer or EN-DC (E-UTRA-NR Dual Connectivity) SON Configuration Transfer (Available when NGAP version >= 15.4.0/Jul2019).

Tcl Parameter: An5gNgapRanCfgXferMode_1

Limitation / Caveat

1. The Uplink RAN Configuration Transfer can be triggered only in Sequencer testing mode.
2. The Inter-system SON Configuration Transfer IE won't be included in Uplink RAN Configuration Transfer message sent by AMF Nodal, and will be ignored if received in Downlink RAN Configuration Transfer message.
3. AMF Nodal takes no action when receiving a Downlink RAN Configuration Transfer message if the message does not contain a request.
4. For B2B testing purpose, when initiating an Uplink RAN Configuration Transfer message that contains EN-DC SON Configuration Transfer IE, the AMF Nodal will use the highest 28 bits of the Cell ID configured in the AMF Nodal GUI as the eNB ID of the source eNB.
5. AMF Node won't relay Uplink Configuration Transfer messages via the N14 interface to the AMF that serves the target gNB or via the N26 interface to the MME that serves the target eNB. Instead, for B2B testing purpose, AMF Node will echo back the Uplink RAN Configuration Transfer message as a Downlink RAN Configuration Transfer message to the same gNB that sent the Uplink RAN Configuration Transfer message.
6. AMF Node won't process RAN Configuration Transfer message received on N14 or N26 interface.

Select to enable AMF Configuration Update procedure per specification 38.413. Available in AMF Node test case. Per section 8.7.3.1 of specification 38.413 - The purpose of the AMF Configuration Update procedure is to update application level configuration data needed for the NG-RAN node and AMF to inter-operate correctly on the NG-C interface. This procedure does not affect existing UE-related contexts, if any.

When the AMF Node count is > 1 ( # of Nodes on the Network Devices/AMF Node tab ), Enable AMF Configuration Update Information is no longer configurable since the same TNL Association is not supposed to be used by different AMF nodes.

Tcl Parameter: AmfNgapAmfConfigUpdateEn

Select to include the AMF TNL Association to Add List IE in the AMF CONFIGURATION UPDATE message. The AMF TNL Association table becomes available for capture.

Tcl Parameter: AmfNgapAmfConfigTnlAssocToAddListEn

Enter up to 32 TNL Associations (AMF TNL Association to Add List IE) in the AMF CONFIGURATION UPDATE message. Available in AMF Node Test Case. Enter AMF TNL Association Address - Enter a valid IPv4 or IPv6 Address. Enter TNL Address Weight Factor.

Enter a number between 0 and 255.

Tcl Parameter: AmfNgapAmfConfigTnlAssocToAddListNum

Tcl Parameter: AmfNgapAmfNgapAmfTnlAssocAddr_1

Tcl Parameter: AmfNgapAmfNgapAmfTnlAssocAddrWf_1

Select to simulate AMF Configuration Update Failure in response to AMF Configuration update message. Available in AMF Nodal Test Case. Select AMF Time to Wait after Failure (s) before sending next AMF Configuration Update message.

Options: Not Included (default), 1, 2, 5, 10, 20, 60

Tcl Parameter: An5gNgapSimulateAmfConfigFailureEn

Tcl Parameter: An5gNgapAmfUpdateTimeToWait

Select to send RAN Configuration Update on Added TNLAs. Available in AMF Nodal Test Case. Per the specifications, RAN Config Update will be sent from gNB only when there is any change on RAN that needs to be informed to the core network. Or ,RAN Configuration Update can be sent for TNLA addition or Deletion of TNLA from RAN side.

Spec Reference : 38.412, 38.413

Tcl Parameter: An5gNgapSendRanConfigUpdEn

Select for AMF Nodal to respond to AMF Configuration Update message with an AMF Configuration Update Acknowledge message after UE registrations already started. 

Limitation : No other action will be taken by LS AMF Nodal (i.e. the newly received TNLA IP/weight factor will not be used for further UE-associated or non-UE-associated signaling).

Available only if the “Simulate AMF Configuration Update Failure” box is not checked.

Spec Reference : 38.413

Tcl Parameter: An5gNgapSendAmfConfigUpdAckAfterRegEn

Select for AMF Node to send Location Reporting Control immediately after the UE is attached to 5G core. When enabled, Location Reporting Control Request Type and Cancel Location Reporting become available for selection.

See 3GPP TS 23.502 Figure 4.13.6.1-1: EPS Fallback for IMS voice figure below.

Available in AMF Node test case.

Tcl Parameter: AmfNgapLocRptEn

Select for AMF Node to Send Location Reporting Control upon PDU Modification Request. When enabled, Data Network Name, Location Reporting Control Request Type and Cancel Location Reporting become available for selection.

To initiate Location Reporting Procedure and complete before sending NGAP: PDU session modification request (NAS: PDU session modification command) to setup QoS flow for IMS voice (Step 2 n Figure 4.13.6.1-1: EPS Fallback for IMS voice in TS 23.502).

Limitations : 

1. AMF does not have enough information to tell if the resource modification is for EPS Fallback or other cases. As such, this will apply to all cases.

2. AMF applies to originating side or terminating side, as AMF cannot differentiate at this time

3. AMF cannot guarantee (NGAP: PDU session modification request) will be sent out AFTER Location Report message received from gNB at this time

Tcl Parameter: AmfNgapLocRptForPduModReqEn

When Send Location Reporting Control upon PDU Modification Request is enabled, enter the Data Network Name for the PDU.

Enter up to 100 characters

Tcl Parameter: AmfNgapLocRptDataNtwkName

Select the Location Reporting Control Request Type.

Options : Direct (default), Change_of_serve_cell, UE_presence_in_area_of_interest

Tcl Parameter: AmfNgapLocRptReqType

Select to cancel location reporting. Available when Send Location Reporting Control upon UE Attach is enabled on AMF Node.

Options : No Action (default), Stop_Change_of_serve_cell, Stop_ue_presence_in_area_of_interest, Cancel_Location_reporting_for_the_ue.

When any of the option above are enabled, with the exception of No Action, enter the Cancel Location Reporting Delay in milliseconds.

Range : 0 to 65535

Tcl Parameter: AmfNgapLocRptCancAction

Tcl Parameter: AmfNgapLocRptCancDelay

Select for NG Reset procedure according to section 8.7.4 of TS 38.413. Selection "Reset All" or "Partial Reset". NG Reset initiated by NG-RAN node, NG Reset initiated by AMF.

On AMF Node & Nodal's N2|NGAP tab, when either test case is in the running state (for any test activity in the nodal), a Command button will be visible. An ODC named "ControlNgap" has been added. It has one operation named "NG Reset" that has no parameters. (Similar to S1-AP, S1Reset ODC.) . In AMF Nodal, "ControlNgap" shows up as a secondary ODC in Sequencer.

     ControlNgap { "op=NgReset" }

NG Reset initiated from gNB, 

NG Reset initiated from AMF:

Tcl Parameter: AmfNgapNgResetMode

Tcl Parameter: An5gNgapNgResetMode

Starting SUPI

Ending SUPI

When NG Reset Mode = Partial Reset, enter the Starting and Ending SUPI.

Enter 14 to 15 digits.

Tcl Parameter: AmfNgapNgResetSupiStart

Tcl Parameter: An5gNgapNgResetSupiStart

Tcl Parameter: AmfNgapNgResetSupiEnd

Tcl Parameter: An5gNgapNgResetSupiEnd

When NG Reset Mode = Partial Reset, select to include the "RAN UE NGAP ID" or "AMF UE NGAP ID" or "Both" in the NG Partial Reset Message. NGReset IE (Refer 38413 pg No 232).

Available in AMF Nodal and AMF Node.

Options : RAN UE NGAP ID , 

Default : RAN UE NGAP ID, AMF UE NGAP ID, Both

Tcl Parameter: AmfNgapNgResetIncUeNgapId

Tcl Parameter: An5gNgapNgResetIncUeNgapId

NGReset from CU to AMF on a DU initiated F1Reset Procedure. Select to include the "RAN UE NGAP ID" or "AMF UE NGAP ID" or "Both" in the NG Reset Message. NGReset IE (Refer 38413 pg No 232).

Available in gNB CU Node test case.

Options : RAN UE NGAP ID , 

Default : RAN UE NGAP ID, AMF UE NGAP ID, Both

Tcl Parameter: An5gNgapNgResetIncUeNgapId

Select to enable UE Context Modification procedure per specification 38.413. Available in AMF Node test case. This panel will only be enabled when Command Mode is enabled (“op=UeContextModify ") and when NGAP version is set to 15.10 or higher. 

The user can attempt to trigger a UE Context Modification Request message anytime after the test case enters RUNNING state. If the UE is currently in an inappropriate state for UE context modification (e.g. MM layer not in established state, conflict with other procedures, etc), the action will be aborted and an error cause returned. Up to 10 sets of modification with different combinations of optional IEs can be pre-configured for the UE Context Modification Request message. The following IEs are currently supported :

1. 1. RAN Paging Priority
   2. Security Key - This is implemented per 33.501 6.9.4.4  AS key re-keying - to create a new KgNB from the current KAMF. If this IE is selected, AMF Node will force a NAS SMC procedure to get a fresh uplink NAS COUNT before sending the UE Context Modification Request message.
   3. Index to RAT/Frequency Selection Priority
   4. UE Aggregate Maximum Bit Rate
   5. Core Network Assistance Information for RRC Inactive - Currently only mandatory sub IEs are supported.
   6. New AMF UE NGAP ID
   7. RRC Inactive Transition Report Request - There RRC inactive transition report types are currently supported: Subsequent, Single and Cancel.

On AMF Nodal, if you enable "Simulate UE Context Modification Failure" the N2 | NGAP tab, the UE Context Modification Failure message will be returned in response to UE Context Modification Request. This applies to UE Context Modification Request message received in any scenario.

Support of the RRC Inactive Transition Report Procedure and Interaction with the UE Context Modification : 

On AMF Nodal, the UE RRC state can be manipulated by provisioning the "RRC Inactive Time for 5G (R)AN Node (ms)", "Idle Entry Time for 5G (R)AN Node" and "Active Entry Time" on the NAS-5G | MM tab. Per 38.413, if the received UE Context Modification Request contains the RRC Inactive Transition Report Request IE, the current RRC State (connected or inactive) shall be reported in the UE Context Modification Response. In addition, in the RRC Inactive Transition Report Request IE,

• If the report type is set to Subsequent, the UE will send the RRC Inactive Transition Report each time UE enters or exits RRC inactive mode until UE enters RRC idle mode or when a Cancel report is received.
• If the report type is set to Single and the UE is currently in RRC inactive mode, the UE will send an additional RRC Inactive Transition Report when UE exits RRC inactive mode.
• If the report type is set to Cancel, RRC reporting will be stopped.

Tcl Parameter: AmfNgapUeCtxtModEn

When Enable UE Context Modification is enabled, you can select up to 10 Modifications.

Range : 1 to 10

Default : 1

Tcl Parameter: AmfNgapUeCtxtModSets

Select to enter the RAN Paging Priority and to include the RAN Paging Priority IE for the UE Context Modification Request message.

Range : 1 to 256

Default : 111

Tcl Parameter: AmfNgapRanPagingPriorityEn_1

Tcl Parameter: AmfNgapRanPagingPriority_1

Select to enter the Index to RAT/Frequency Selection Priority and to include the Index to RAT/Frequency Selection Priority IE for the UE Context Modification Request message.

Range : 1 to 256

Default : 250

Tcl Parameter: AmfNgapIndexToRfspEn_1

Tcl Parameter: AmfNgapIndexToRfsp_1

Select to include the Security Key - This is implemented per 33.501 6.9.4.4  AS key re-keying - to create a new KgNB from the current KAMF. If this IE is selected, AMF Node will force a NAS SMC procedure to get a fresh uplink NAS COUNT before sending the UE Context Modification Request message.

Tcl Parameter: AmfNgapSecurityKeyEn_1

Select to enter the UE Aggregate Maximum Bit Rate for Downlink and Uplink and to include the UE Aggregate Maximum Bit Rate IE for the UE Context Modification Request message.

Range : Range: 0 to 4,000,000,000,000

Default : 2000000000

Tcl Parameter: AmfNgapUeAmbrEn_1

Tcl Parameter: AmfNgapUeAmbrBrDl_1

Tcl Parameter: AmfNgapUeAmbrBrUl_1

Select to include the New AMF UE NGAP ID IE for the UE Context Modification Request message.

Range : 1 to 256

Default : 250

Tcl Parameter: AmfNgapNewAmfUeNgapIdEn_1

Select to include the RRC Inactive Transition Report Request IE for the UE Context Modification Request message.

Options : "Subsequent state transition report", "Single RRC connected state report" and "Cancel report".

Tcl Parameter: AmfNgapRrcInactiveReportReqEn_1

Tcl Parameter: AmfNgapRrcInactiveReportReq_1

Enter the Maximum buffered PWS messages.

Range : 8 to 64

Default : 10

AMF forwarding logic for CMAS warning messages has been added based on 

3GPP Spec in section 9.1.3.5.2 of 23.041:  

The AMF forwards Write-Replace Warning Message Request NG-RAN to NG-RAN nodes. The AMF shall use the list of NG-RAN TAIs to determine the NG-RAN nodes in the delivery area. If the list of NG-RAN TAIs is not included and no Global RAN Node ID has been received from the CBCF, the message is forwarded to all NG-RAN nodes that are connected to the AMF. If a Global RAN Node ID has been received from the CBCF, the AMF shall forward the message only to the NG-RAN nodeindicated by the Global RAN Node ID IE.

Tcl Parameter: AmfNgapNodeMaxBufferPwsMsg

Enter the PWS message broadcast rate (messages per second).

Range : 1 to 1000

Default : 10

Tcl Parameter: AmfNgapPwsBrRate

Name

Pointer

Set ID

Region ID

Enter the Name (e.g. AMF.spirent.com), and location of the AMF used by the peer during the attach process (with the AMF). 

Default : src#(N0).AMF.Spirent.com

Click to use the Auto-Increment Format Wizard.

Enter the AMF Pointer: Range: 0 to 63. Default: 0 

Enter the AMF Set ID: The AMD Set consists of some AMFs that server a given area and network slice. Multiple AMF sets may be defined per AMF region and network slice. Range: 0 to 1023. Default: 0 

Enter the AMF Region ID. The AMF Region consists of one or more multiple AMF Sets. Range: 0 to 255.

Tcl Parameter: AmfNgapName

Tcl Parameter: AmfNgapPointer

Tcl Parameter: AmfNgapSetId

Tcl Parameter: AmfNgapRegion

Custom Messages

You can customize Landslide generated messages and or compose your proprietary messages to perform negative testing with invalid values or malformed messages or to add proprietary information.

Select the Custom Messages checkbox, which makes available the New and Open buttons.

• New: Click New to display the Message Editor window. See Message Editor for details of entering a new message.

• Open: Click Open to display the Select Message Editor window. Select the library in which the message exists, select the message you wish to edit and then click the Edit button to display the Message Editor Window. See Message Editor for details of editing existing messages.

See additional details in NGAP_Msg_Edit_NGSetupRequestMessage_Template.

See list of NGAP message types supported in the Message Editor:

Tcl Parameter: AmfNgapCustomMsgEn

Tcl Parameter: AmfNgapCustomMsg

Tcl Parameter: An5gNgapCustomMsgEn

Tcl Parameter: An5gNgapCustomMsg

Tcl Parameter: N50NamfNgapCustomMsgEn

Tcl Parameter: N50NamfNgapCustomMsg

This tab is available when the Enable NGAP Message Fuzzing checkbox is selected from the N2->NGAP. Use the Message Fuzzing panel to select which messages are required for the test case and at what Probability (%) the message needs to be "Fuzzed."

With a message selected, set the desired Probability to be Fuzzed (%) value of the highlighted message. A fuzzing probability is configurable for each selected N2 message. All of the configurations are applied to each gNb node. Each gNb will calculate its own probability, which will be applied to messages from the gNb. See the following image.

Probability Range: 1 to 100

Default: 10

Tcl Parameter: AMfNgapMsgFuzzProbability_{message code} (With the message highlighted use the F2 button to display Tcl Parameter.)