Xn Ap Tab

• Version (38.423)
• Initiate Connection
• Enable Full-Mesh Xn Connection

• Reset
  • Include UE X1-AP ID

Version (38.423)

Select the proprietary version of the application from the dropdown list. Available in gNB CU Node test case.

"Xn", when enabled, will be started either at a starting of a test session or at the processing of F1 Setup request. 

Message sequence and required content are listed in 3GPP 38.423 session 8.4.1 , 11.1. 

Options: 17.2.0/Sep2022, 16.6.0/July2021

Default: 17.2.0/Sep2022

Tcl Parameter: XnapVersion

Select to indicate whether this Xn-AP is required to initiate a connection to remote SUT. 

Tcl Parameter: XnapInitConnectionEn

Available in gNB CU Node test case.

This check box is for instructing landslide to prepare enough resources for supporting multiple connections between local and remote devices. 

The check is functioned as follows:

When unchecked (default behavior), each local “Xn” node will set up one (and only one) “Xn” connection (incoming or outgoing) with one remote “Xn” node (aka.  1-to-1 connection model). Each local node will be assigned with 1 remote “Xn” node taken from a configured SUT list.  SUT addresses are taken in order from first to last in a SUT list; and repeated as needed to ensure each local node has one SUT address.    For instance, local node#1 is assigned to SUT#1, local node#2 is assigned to SUT#2, so on.   

When checked and combined with the “Initiate Connection” checked,  every local emulated “Xn” node will be assigned with all provisioned SUT addresses and will attempt to connect to all SUTs.

Tcl Parameter: XnapMeshEn

Select for gNB-CU initiated Reset procedure for NR Stand-Alone.

Per O-RAN.WG5.C.1-v07.00.docx section 4.2.2.3.

Select to "Include UE X1-AP ID" . 

Options : RAN NODE1 Xn-AP ID (default), RAN NODE2 Xn-AP ID, Both

Available when SA Mode = 3GPP and Xn Interface are enabled on the gNB CU node test case.

Tcl Parameter: XnapResetOption