Command Mode Test Activity

• AMF Nodal Test Case

• NGAP On Demand Commands

• GGSN Nodal Test Case

• GNB CU NSA Nodal Test Case

• GNB CU SA Nodal Test Case

• HA Nodal test Case

• MME Nodal Test Case

• • SMS On Demand Commands

  • S1AP On Demand Commands

  • VoLTE On Demand Commands

• LCS Nodal Test Case

• PCRF Nodal Test Case

• PGW Nodal Test Case

• RIC Nodal Test Case

• SGW Nodal Test Case

• SMF Nodal Test Case

• UE Node Test Case

• UMTS Test Case

• UPF Nodal Test Case

• Wifi Offload Gateway Nodal Test Case

• AAA Server Node
• AMF Node
• AMF Node - NGAP On Demand Commands
• DRA Node Test Case
• gNB CU Node
• HSS Node
• IMS Node
• IP Application Node
• LCS Node
• MME Node Test Case
• • S1AP On Demand Commands
• OCS Node Test Case
• OFCS Node Test Case
• PCRF Node Test Case
• RIC Node Test Case
• SMF Node Test Case

Control5G tab

When you select Test Activity as Sequencer on the Test Configuration tab, the Control5G tab displays (with parameters described in Step 3.) where you may select and setup a sequence of commands, as required.

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

In AMF Nodal, you can select Uplink RAN Configuration Transfer. 

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.

ExecuteExtApps tab

1.

When the Test Case is running, double-click the test case to open/edit, and the test case opens.

2.

Click the Command button tab. The Execute Command window opens. Select the command options and enter the appropriate values in the parameters.

• Command: Select the test operation from the drop down list. Select option: Register, Periodic Registration Update, Deregister, PDU Connect, PDU Release, Release Connection, Activate Connection, Path Switch (Xn Handover), Handover (N2), Reg/Tau Mobility, WiFi-LTE Handover, Reset, PDU Modify, PDU Session Resource Notify

3.

Enter the parameters required for the Command you select: the Rate, Starting Subscriber Index, Ending Subscriber Index, Starting Target Node Index, Ending Target Node Index, PDUs Starting Index, PDUs Ending Index, Follow On, Target Protocol, and Modification Set (Flow, Action, QFI and 5QI).

Register

Applies to 5GS Register or LTE Attach

Failure Scenario - Additional details listed below

Control5G { [“op=Register" ]

“rate=RATE”

“start_sub=START_SUB_INDEX”

“end_Sub=END_SUB_INDEX”

“start_node=START_NODE_INDEX”

“end_node=END_NODE_INDEX”

"follow_on=1_0"

"failure_msg_1=SCENARIO"

"failure_msg_2=SCENARIO" }

Periodic Registration Update

(select to trigger Periodic Registration Update procedure on demand independent of T3512 timer value that the UE received from the AMF in Registration Accept) -  only when the UE is in Established or Idle Mode 5GMM state.

Control5G { [“op=RegUpdate" ]

“rate=RATE”

“start_sub=START_SUB_INDEX”

“end_Sub=END_SUB_INDEX”

"follow_on_per_reg=1_0" }

Deregister | -  Applies to 5GS Deregister or LTE Detach

Reset |

ActivateConnection | - Applies to 5GS or LTE Connection Activation

Control5G { [“op=Deregister | Reset |  ActivateConnection" ]

“rate=RATE”

“start_sub=START_SUB_INDEX”

“end_Sub=END_SUB_INDEX” }

Control5G { [“ReleaseConnection"]

“rate=RATE”

“start_sub=START_SUB_INDEX”

“end_Sub=END_SUB_INDEX”

"cause=OPTIONAL" }

PduConnect | PduRelease

Applies to 5GS PDU Connect or LTE PDN Connect

Applies to 5GS PDU Release or LTE PDN Disconnect

Control5G { [“op=PduConnect | PduRelease "]

“rate=RATE”

“start_sub=START_SUB_INDEX”

“end_Sub=END_SUB_INDEX”

“start_pdu=START_PDU”

“end_pdu=END_PDU” }

PduModify

Control5G { [“op=PduModify "]

“rate=RATE”

“start_sub=START_SUB_INDEX”

“end_Sub=END_SUB_INDEX”

“pdu=PDU_INDEX”

“mod=MOD_SET_1_10” }

Path Switch / XnHandover - Applies to Xn based handover

Control5G { [“op=XnHandover" ]

“rate=RATE”

“start_sub=START_SUB_INDEX”

“end_Sub=END_SUB_INDEX”

“start_node=START_NODE_INDEX”

“end_node=END_NODE_INDEX” }

N2Handover - Applies to N2 based or N26 based handover

Control5G { [“op=N2Handover" ]

“rate=RATE”

“start_sub=START_SUB_INDEX”

“end_Sub=END_SUB_INDEX”

“start_node=START_NODE_INDEX”

“end_node=END_NODE_INDEX” }

Control5G { [“op=WifiLTEHandover" ]

“rate=RATE”

“start_sub=START_SUB_INDEX”

“end_Sub=END_SUB_INDEX”

“start_node=START_NODE_INDEX”

“end_node=END_NODE_INDEX”

"target_protocol=wifi_LTE_5GS"}

Reg/TauMobility - Applies to 5GS Mobility Registration, EPS to 5GS Mobility Registration using N26 interface or 5GS to EPS TAU using N26 interface

Control5G { [“op=RegTauMobility" ]

“rate=RATE”

“start_sub=START_SUB_INDEX”

“end_Sub=END_SUB_INDEX”

“start_node=START_NODE_INDEX”

“end_node=END_NODE_INDEX” }

Control5G { [“op=PduSessNtf"]

“rate=RATE”

“start_sub=START_SUB_INDEX”

“end_Sub=END_SUB_INDEX”

“start_pdu=START_PDU”

“end_pdu=END_PDU”

“start_qf_index=START_QOS_FLOW_INDEX”

“end_qf_index=END_QOS_FLOW_INDEX”

"pdu_ntf_cause=0/1"

}

ExecuteVoLTEScript

VoLTE On Demand Commands

ExecuteVolteScript { [“op=1|2|3|4|5|6|7|8|9|10" ]

“rate=RATE”

“start_sub=START_SUB_INDEX”

“end_Sub=END_SUB_INDEX” }

Select Failure Scenario Message.

Options: Security Mode Complete, Security Mode Complete, Registration Accept

Select Action. 

Options: Abort, Abort Reregister, Abort Reregister 5G GUTI, Deregister, Deregister Reregister, Insert Reregister, Insert Reregister 5G GUTI

Enter Value.

Measurements are located in the AMF Nodal Failure Scenario tab.

"Abort", "Abort Reregister", "Abort Reregister 5G GUTI", "Deregister", "Deregister Reregister", "Insert Reregister", "Insert Reregister 5G GUTI" failure scenario actions are added to "Security Mode Command", "Security Mode Complete", and "Registration Accept" messages in registration procedure.

"Abort"          -  set or not set reregister flag based on the configured failure scenario; start Abort timer when receive or send the configured message; send Registration Request if reregister flag is set.

"Deregister"  -  send Deregistration Request message; set or not set reregister flag based on the configured failure scenario; start Abort timer when receive or send the configured message; send Registration Request if reregister flag is set.

"Insert"          -  add in registration request with SUCI or 5GGUTI when receive or send the configured message.

Example message flow:

Nas5gSecModeCmd/Abort/Reregister 

Nas5gRegistAcc/Deregister/Reregister 

Nas5gSecModeComp/Insert/Dereregister 

Select for NG Reset procedure according to section 8.7.4 of TS 38.413.  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:

Available on AMF Node test case when running in Command Mode. Click the "Command" button under the N2 tab to execute an SCTP SHUTDOWN message. It will be sent to gNB to shut down each SCTP connection. Internal use only.

ControlNgap

{ "op=StopSctp" }

Only available on AMF Nodal test case using Sequencer test activity. Command Mode is not supported.

Select Uplink RAN Configuration Transfer. 

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. NGAP (Uplink RAN Configuration Transfer)

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

Enter the parameters required for the Uplink RAN Configuration Transfer Command you select: the Rate, gNB Starting Index, gNB Ending Index, Configuration Index 

This feature supports Uplink RAN Configuration Transfer and Downlink RAN Configuration Transfer messages.

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.

Per Specification reference : 3GPP TS 23.501, 3GPP TS 36.413, 3GPP TS 38.413 (section 8.8)

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.

ControlNgap

{ "op=RanConfigTransfer" \

"rate=RATE" \

"start_gnb=START_GNB" \

"end_gnb=END_GNB" \

"cfg_index=CFG_INDEX" }

Available on AMF Node's ControlNgap ODC, operation = Send AMF Configuration Update.  It has two parameters for "TNLA IP to Add" and "Weight Factor".

When this command is executed, an AMF Configuration Update message is sent to connected gNB nodes. This message contains 1 item in the TNLAssociationToAddList with TransportLayerAddress and TNLAddressWeightFactor set to the value of "TNLA IP to Add" and "Weight Factor", respectively.

TNLA IP to Add - requires an IPv4 or IPv6 address.  
Weight Factor - range is 0 - 255, default = 0.  

Used for back-to-back testing to Send AMF Configuration Update.

ControlNgap

{ "op=AmfCfgUpd"\

"tnla_ip=TNLA_IP"\

"weight=WEIGHT_FACTOR" }

Operation

Test Case Command ExecuteExtApps

In ODC Name ExecuteExtApps, the only parameter is the test name preceded by "Start". 

Operations : Start HTTP, Start Ping, Start Video, Start Speed Test, Start Speed Test Lab, Start FTP, Start Traceroute, Start MMS Client, Start Android VM, Stop

Stop is not supported in Sequencer. The Stop operation applies to whatever test is currently running.

An optional parameter is added to HTTP to allow single client selection. When in Command Mode and "Start HTTP" is the selected operation, a checkbox labeled "Start Single Client" is visible along with a selection table. When "Start Single Client" is checked, the table is enabled and the user can select one of the entries.

See External App Configuration for test case parameters. 

Each application can only run 1 time (in sequencer). For Sequencer , validation has been added that blocks using the same operation twice.

The Estimated Duration in a Sequencer test is the total timeout value for each test found in the External App Configuration.  However, each test type has a different formula for Timeout value. If a test runs longer than the Estimated duration, Landslide will stop executing the test and mark it as a failure.

Estimated Duration test calculation : 

HTTP Test estimated duration =  (# of URL * timeout * Iteration) 

Traceroute test estimated duration = (timeout * (1 + # of Ping) * # of Host) 

TWAMP Test estimated duration =  (timeout * # of Host * Iteration) 

Android VM estimated duration = add up all the timeout value of enabled tests

For all other tests, the estimated duration =  Use timeout value in External App Configuration as estimated duration.

Example of Command Sequence: 

Test name

ExecuteExtApps { "test=Http" "index=0"} ExecuteExtApps { "test=Traceroute" } ExecuteExtApps { "test=Ping" } ExecuteExtApps { "test=Video" } ExecuteExtApps { "test=SpeedTest" } ExecuteExtApps { "test=SpeedTestLab" } ExecuteExtApps { "test=Twamp" } ExecuteExtApps { "test=Ftp" } ExecuteExtApps { "test=MmsClient" } ExecuteExtApps { "test=AndroidVm" }

ExecuteExtApps { "test=Stop" }

Command : Deregister 

Used to trigger Network Initiated Deregistration Request in Command Mode. To configure parameters for network initiated Deregistration Request messages, Deregistration Cause is added under the NAS-5G|MM tab, and the T3346 Timer and T3346 Timer Unit are enabled only if the "Deregistration Cause" or "Reject Cause" is set to 22.

Command : Release Connection 

When the "Release Connection” ODC (On-Demand Command) is executed, AMF Node will decide which of the UE Context Release Command message to send based on UE’s CM status. If a UE is in the CM-Connected status, AMF Node will send the UE Context Release message to gNB and execute the AN Release AMF Initiated procedure. 

When AMF-initiated AN Release is triggered by AMF Node - ODC command, Ngap Cause in UE Context Release Command will be set "unspecified".

Reference: TS23.502 -. 4.2.6 AN Release

• If UE is registered with AMF and N2/N3 is connected, AMF will initiate AMF-Initiated AN Release procedure. UE will be specified by SUPI/IMSI.
• If UE is not registered, the following information will be displayed. Ex: " No such SUPI 310310140000120"
• If UE is registered but is not in the connected (established) state, the following information will be displayed. Ex: " Session(s), Mm(s) are not ready, not in est state."

Command : PDU Release 

Applies to AMF Initiated PDU Session Release. The function is enabled on AMF with or without N11. Reference: TS23.502, TS 29.502

Command : PDU Modify

Select to to trigger the NW initiated PDU Session Modification procedure on-demand.

Spec Reference:

• 3GPP TS 38.413, 8.2.3 PDU Session Resource Modify

• 3GPP TS 38.413, 9.3.4.3 PDU Session Resource Modify Request Transfer

• 3GPP TS 24.501, 8.3.9 PDU session modification command

In order for this operation to be available, the test configuration must have "SMF Emulation" enabled, "PGW-C Emulation" disabled, and at least one DNN tab must have "QoS Modification" enabled on NAS-5G|SM (Nas 5G Sm).  The Starting PSI and Ending PSI parameters have a fixed range of 1-15.  The Mod Set parameter has a fixed range of 1-10. 

Examples of error messages that may be returned:

• No such SUPI
• PSI does not exist for the UE
• Sm session(s) are not ready, not in est or idlemode state.
• Sm session(s) skip PDU modification
• Sm session(s) fail to send PDU modification

Command : UE Context Modification 

Applies to UE Context Modification Request message. Up to 10 sets of configuration are currently supported for the UE Context Modification Request message. Available when NGAP version is set to 15.10 or higher.

Reference : 3GPP TS 38.413 - NG-RAN;  NG Application Protocol (NGAP), 3GPP TS 23.502 - Procedures for the 5G System (5GS); Stage 2, 3GPP TS 33.501 - Security architecture and procedures for 5G system.

Command : Request Position Info

Click the Command button on the LPP Tab and AMF-LMF to execute the Request Position Info Command. The Execute Command window opens. Select the command options and enter the appropriate values in the parameters.

Command : Send Message, Stop Message

Available on AMF Node when Emergency Alert is enabled. Use the PWS Tab to create the messages to be sent. The PWS Tab for the N2 interface allows the user to define requests related to Commercial Mobile Alert System (CMAS) Broadcast System for 5G.

Click the Command button on the PWS Tab  to execute the Send Message, Stop Message Command. The Execute Command window opens. Select the command options and enter the appropriate values in the parameters.

1.

When the Test Case is running, double-click the test case to open/edit, and the test case opens.

2.

Click the Command button on the Mobile Subscriber pane of the Emulator Configuration tab to execute Deregister Command. The Execute Command window opens. Select the command options and enter the appropriate values in the parameters.

• Command: Select the test procedure from the drop-down list. Select option: Deregister, Release Connection Tab.

Click the Command button on the LPP Tab and AMF-LMF to execute the Request Position Info Command. The Execute Command window opens. Select the command options and enter the appropriate values in the parameters.

• Command: Select the test procedure from the drop-down list. Select option: Request Position Info Tab.

Click the Command button on the PWS Tab  to execute the Send Message, Stop Message Command. The Execute Command window opens. Select the command options and enter the appropriate values in the parameters.

• Command: Select the test procedure from the drop-down list. Select option: Send Message, Stop Message Tab.

3.

Enter the parameters required for the Command you select: the Rate, Starting SUPI, Ending SUPI, SUPI, AMF Node, and PWS Message.

Deregister

Release Connection

Control5G  { op=Deregister, Op=ReleaseConnection

“rate=RATE”

“start_supi=START_SUPI”

“end_Supi=END_SUPI” }

PduRelease

Applies to AMF Initiated PDU Session Release 

Control5G { [“op=PduRelease "]

“rate=RATE”

“start_pdu=START_PDU”

“end_pdu=END_PDU” 

“start_supi=START_SUPI”

“end_supi=END_SUPI”}

PduModify

Control5G { [“op=PduModify "]

“rate=RATE”

“start_psi=START_PSI”

“end_psi=END_PSI” 

“start_supi=START_SUPI”

“end_supi=END_SUPI”

"mod_set=MOD_SET_1_10"}

Control5G { [“op=UeContextModify "]

“rate=RATE”

“start_supi=START_SUPI”

“end_supi=END_SUPI”

"mod_set=MOD_SET_1_10"}

ControlLcs  { op=ReqPositionInfo

“supi=SUPI”}

Start Message

Stop Message

ControlPws  { op=start, op=stop

“start_node=START_NODE_INDEX”

“end_node=END_NODE_INDEX” 

“start_msg=START_MSG_INDEX”

“end_msg=END_MSG_INDEX” }

1.

When the Test Case is running, double-click the test case to open/edit, and the test case opens.

2.

Click the Command button on the Mobile Subscriber pane of the Emulator Configuration tab. The Execute Command window opens. Select the command options and enter the appropriate values in the parameters.

• Command: Select the test procedure from the drop-down list. Select option: Send RAR, Send ASR on ControlAaa tab and Re-Map APNs/Contexts on UpdateConfig Tab.

3.

Enter the parameters required for the Command you select: the Rate, Subscriber Group, and Contexts.

SendRAR | SendASR

ControlAaa  { op=SendRAR | op=SendASR

“rate=RATE”

“start_sub=START_SUB_INDEX”

“end_Sub=END_SUB_INDEX” }

ReMapContext

UpdateConfig  { op=ReMapContext

  "sub_group=SUB_GROUP_IDX"

  "contexts=CONTEXTS_CSVS"

1.

When the Test Case is running, double-click the test case to open/edit, and the test case opens.

2.

Click the Command button on the Mobile Subscriber pane of the Emulator Configuration tab. The Execute Command window opens. Select the command options and enter the appropriate values in the parameters.

• Command: Select the test procedure from the dropdown list. Select option: Transport Loss, Communication Loss, Failover Recovery.

3.

Enter the parameters required for the Command you select: the Rate, Starting Subscriber Index, Ending Subscriber Index, Default Bearer, and Dedicated Bearer.

TransLoss | CommLoss | Recovery

ControlNodes  { op=TransLoss | op=CommLoss | op=Recovery

 "rate=RATE"

 "start_node=START_NODE_INDEX"

 "end_node=END_NODE_INDEX"

• Operation:

Select the test operation from the dropdown list. Options are: Create Primary(s), QOS Update Primary(s), Delete Primary(s), Create Secondary(s), QOS Update Secondary(s), Delete Secondary(s), Handover, Reset, Mobile Update, Direct Tunnel Update

• Log Execution

• Rate

• Subscribers

• Primary Contexts

• Secondary Contexts

• QoS Update Set

Select the QOS Update Set to be included in Update PDP Context Request messages. Six sets (1 to 6) of QOS Update profiles may be included in Update PDP Context Request messages:

• Set 1 values are from the Quality of Quality of Service of the Gn >GTP tab.   
• Set 2 to 6 values are from the Command Mode > QOS Update window which opens when you click Settings (Test Activity > Command Mode > Settings).

• Mobile Update Set

Select the Mobile Update Set to be included in Update PDP Context Request messages. Ten sets ( 1 to 10) of Mobile Update settings may be included in Update PDP Context Request messages:

• Set 1 values are from Gn >GTP tab: Routing Area Identity Code (when GTP Version 1 and 0), User Location Information (GTP Version 1), and Time Zone (GTP Version 1).   
• Set 2 to 10 values are from the Command Mode > Mobile Update window which opens when you click Settings (Test Activity is Command Mode > Settings).

• Target SGSN

• Target RNC/BSS

• Direct Tunnel

Available when you have selected Direct Tunnel on the Test Configuration tab.

Select to allow the RNC and GGSN to by-pass the SGSN and establish a direct connection to the GTP User Plane.

• Use SGSN Address

Available only when you select Direct Tunnel.

The default The SGSN_ADDR_1_0 parameter is set to 0, when you do not select Use SGSN Address. The following shows results based on your selection of Direct Tunnel and Use SGSN Address:

CreatePrimary | DeletePrimary

ControlPDP {CreatePrimary | DeletePrimary

RATE \

STARTING_SUBSCRIBER_INDEX ENDING_SUBSCRIBER_INDEX \

STARTING_PRIMARY_CONTEXT ENDING_PRIMARY_CONTEXT }

CreateSecondary | DeleteSecondary

ControlPDP {CreateSecondary | DeleteSecondary

RATE \

STARTING_SUBSCRIBER_INDEX ENDING_SUBSCRIBER_INDEX

STARTING_SECONDARY_CONTEXT ENDING_SECONDARY_CONTEXT

STARTING_SECONDARY_CONTEXT ENDING_SECONDARY_CONTEXT }

QosUpdatePrimary

ControlPDP {[QosUpdatePrimary]

RATE \

STARTING_SUBSCRIBER_INDEX ENDING_SUBSCRIBER_INDEX \

STARTING_PRIMARY_CONTEXT ENDING_PRIMARY_CONTEXT \

QOS_UPDATE_SET_1_6 }

QosUpdateSecondary

ControlPDP {[QosUpdateSecondary]

RATE \

STARTING_SUBSCRIBER_INDEX ENDING_SUBSCRIBER_INDEX \

STARTING_PRIMARY_CONTEXT ENDING_PRIMARY_CONTEXT \

STARTING_SECONDARY_CONTEXT ENDING_SECONDARY_CONTEXT \

QOS_UPDATE_SET_1_6 }

Handover

ControlPDP {[Handover]

RATE \

STARTING_SUBSCRIBER_INDEX ENDING_SUBSCRIBER_INDEX \

TARGET_SGSN_INDEX TARGET_RNC_BSS_INDEX }

Reset

ControlPDP {[Reset]

RATE STARTING_SUBSCRIBER_INDEX ENDING_SUBSCRIBER_INDEX }

MobileUpdate

ControlPDP {[MobileUpdate]

RATE STARTING_SUBSCRIBER_INDEX ENDING_SUBSCRIBER_INDEX \

MOBILE_UPDATE_SET_1_10 }

TunnelUpdate

ControlPDP {[TunnelUpdate]

RATE STARTING_SUBSCRIBER_INDEX ENDING_SUBSCRIBER_INDEX \

DIRECT_TUNNEL_1_0 SGSN-ADDR_1_0}

ControlBearer tab

When you select Test Activity as Sequencer on the Test Configuration tab, the ControlBearer tab displays (with parameters described in Step 3.) where you may select and setup a sequence of commands, as required.

Per Spec reference :

O-RAN.WG5.C.1 Section 4.1.2.3 – Reset (gNB-DU initiated) for EN-DC
O-RAN.WG5.IOT.0-v06.00 Section 2.3.1.25 – Reset (gNB-DU initiated) for EN-DC
3GPP 36.423 Section 8.3.4 Reset
3GPP 36.423 Section 8.7.14 Partial reset of EN-DC
3GPP 38.473 Section 8.2.1.2.2 Reset Procedure Initiated from the gNB-DU

1.

When the Test Case is running, double-click the test case to open/edit, and the test case opens.

2.

Click the Command button tab. The Execute Command window opens. Select the command options and enter the appropriate values in the parameters.

• Commands for ControlBearer : Select the test operation from the drop down list. Select option: PDN Connect, PDN Disconnect, Attach, Detach

• Commands for ControlF1ap : Select the test operation from the drop down list. Select option: F1 Reset

PdnConnect | PdnDisconnect

Control5G { [“op=PdnConnect | PdnDisconnect "]

“rate=RATE”

“start_sub=START_SUB_INDEX”

“end_Sub=END_SUB_INDEX”

“def=DEFAULT_BEARER_INDEX”

 }

Attach

Detach

Control5G { [“op=Attach | Detach "]

“rate=RATE”

“start_sub=START_SUB_INDEX”

“end_Sub=END_SUB_INDEX”

 }

Control5G tab

When you select Test Activity as Sequencer on the Test Configuration tab, the Control5G tab displays (with parameters described in Step 3.) where you may select and setup a sequence of commands, as required.

1.

When the Test Case is running, double-click the test case to open/edit, and the test case opens.

2.

Click the Command button tab. The Execute Command window opens. Select the command options and enter the appropriate values in the parameters.

• Commands for Control5G : Select the test operation from the drop down list. Select option: Register, Deregister, PDU Connect, PDU Release

• Commands for ControlF1ap : Select the test operation from the drop down list. Select option: F1 Reset, Add Cell, Modify Cell, Delete Cell, Service Status Change

Register

Control5G { [“op=Register" ]

“rate=RATE”

“start_sub=START_SUB_INDEX”

“end_Sub=END_SUB_INDEX”

“start_node=START_NODE_INDEX”

“end_node=END_NODE_INDEX”

}

Deregister | -  Applies to 5GS Deregister or LTE Detach

Control5G { [“op=Deregister"]

“rate=RATE”

“start_sub=START_SUB_INDEX”

“end_Sub=END_SUB_INDEX” }

PduConnect | PduRelease

Applies to 5GS PDU Connect or LTE PDN Connect

Applies to 5GS PDU Release or LTE PDN Disconnect

Control5G { [“op=PduConnect | PduRelease "]

“rate=RATE”

“start_sub=START_SUB_INDEX”

“end_Sub=END_SUB_INDEX”

“start_pdu=START_PDU”

“end_pdu=END_PDU” }

ControlF1ap { [“op=AddCell"]

“gnb_idx=GNB_IDX”

“cell_id=CELL_ID”

“pci=PCI” }

ControlF1ap { [“op=ModifyCell"]

“cell_id=CELL_ID”

“cell_type=0_1_2_3” }

Delete Cell

Service Status Change

ControlF1ap { [“op=DeleteCell" | "op=SvcStatusChng"]

“cell_id=CELL_ID”

}

When the Test Case is running, double-click the test case to open/edit, and the test case opens.

Click the Command button on the Mobile Subscriber pane of the Test Configuration tab. The Add OnDemand Command window opens. Select the Command Operation from the dropdown list and enter the appropriate values in the parameters.

Enter the parameters required for the Command Operation you select: the Rate, Starting Subscriber Index, Ending Subscriber Index, Target Node Starting Index, and Target Node Ending Index.

Attach | Detach | Revocation | Dmu

ControlMipHa { [“op=Attach | Detach | Revocation" | Dmu]

“rate=RATE”

“Start_sub=START_SUB_INDEX”

“end_Sub=END_SUB_INDEX” }

InterPdsnHandover

ControlMipHa { “op=InterPdsnHandover”

“rate=RATE”

“Start_sub=START_SUB_INDEX”

“end_Sub=END_SUB_INDEX”

“start_node=STARTING_TARGET_NODE”

“end_node=ENDING_TARGET_NODE” }

Reset

ControlMipHa { “op=Reset”

“rate=RATE”

“Start_sub=START_SUB_INDEX”

“end_Sub=END_SUB_INDEX” }

• Sends per APN Bearer parameter modification (e.g., UL/DL bit rate change).
• Sends modification to Operator Determined Barring, was applied, changed, or removed.
• Sends information to the MME or SGSN to indicate that the HSS has requested to be notified when the UE is reachable.

• Sends (HSS) request to MME/SGSN to delete a specified subscriber data (DSR)

• Sends (HSS) request to MME/SGSN to Cancel Location Request (CLR).

• Sends (HSS) request to MME/SGSN to Reset Request (RSR).

• Enabling a user defined result code in HSS answer message. Select the appropriate Answer Message from drop down menu.
• Update Location Answer (ULA), Purge UE Answer (PUA), Authentication Information Answer (AIA), or Notify Answer (NOA)

• Disabling Force Result Code feature.

• Select CbcSendMessage when running the SBC Interface to send a "WRITE_REPLACE WARNING REQUEST" or to send a "STOP WARNING REQUEST".

1.

When the Test Case is running, double-click the test case to open/edit, and the test case opens.

2.

Click the Command button on the on the HSS | HSS Server | PDN Contexts tab. The Execute Command window opens. Select the command options and enter the appropriate values in the parameters.

• Command: Select the test procedure from the dropdown list. Select option: Send IDR; Send DSR. Send CLR; Send RSR; Force Result Code; Stop Force Result Code.

The Command button is available on SBc-AP tab when SBc Interface is enabled on HSS Node Emulator Configuration. The Execute Command window opens. Select the command options and enter the appropriate values in the parameters.

• Command: Select the test procedure from the dropdown list. Select option: Send WRITE_REPLACE WARNING REQUEST or Send STOP WARNING REQUEST.

3.

Enter the parameters required for the Command you select: the Rate, Starting Subscriber Index, Ending Subscriber Index, PDN Context Index , Flags, Response Message, Force Result Code Type, Result Code , Message Index, MME Index.

SendIdr

ControlHss { op=SendIdr

rate=RATE start_sub=START_SUB end_sub=END_SUB pdn_context=PDN_INDEX }

ControlHss { op=SendIdr

rate=RATE start_sub=START_SUB end_sub=END_SUB pdn_context=PDN_INDEX flags=8HEX_DIGITS_Flags }

SendDsr

ControlHss { op=SendDsr

rate=RATE start_sub=START_SUB end_sub=END_SUB pdn_context=PDN_INDEX  }

ControlHss { op=SendDsr

rate=RATE start_sub=START_SUB end_sub=END_SUB pdn_context=PDN_INDEX flags=8HEX_DIGITS_Flags }

SendClr

ControlHss { op=SendClr

rate=RATE start_sub=START_SUB end_sub=END_SUB cancellation_type=0_1_2_3_4 }

ControlHss { op=SendClr

rate=RATE start_sub=START_SUB end_sub=END_SUB flags=8HEX_DIGITS_Flags cancellation_type=0_1_2_3_4 }

SendRsr

ControlHss { op=SendRsr

rate=RATE start_sub=START_SUB end_sub=END_SUB inc_user_id=true_false  }

ForceCode

ControlHss { op=ForceCode

rate=RATE start_sub=START_SUB end_sub=END_SUB msg=0_1_2_3 code_set=1_2 code=diameter_code }

Msg = "ULA" = "0",  "PUA" = "1",  "AIA" = "2",  "NOA" = "3"

Code_set (Result Code Type) "Message-Level" = "1", "Experimental" = "2"

StopForce

ControlHss { op=StopForce

rate=RATE start_sub=START_SUB end_sub=END_SUB  }

SendWrwrReq | SendSwReq

CbcSendMessage  is not functional until the SBc interface is enabled and messages have been configured on the SBc|SBc-AP tab. 

CbcSendMessage { "op=SendWrwrReq | SendSwReq"

"rate=RATE" \

"msg_index=MSG_INDEX" \

"start_mme=START_MME_INDEX" \

"end_mme=END_MME_INDEX"  }

SIP VoIP tab

When you select Test Activity as Sequencer on the Test Configuration tab, the SIP VoIP tab displays where you may select and setup a sequence of commands, as required.

See VoLTE OnDemand Commands.

When the Test Case is running, double-click the test case to open/edit, and the test case opens.

Click the Command button on the Mobile Subscriber pane of the Test Configuration tab. The Add OnDemand Command window opens. Select the Command Operation from the dropdown list and enter the appropriate values in the parameters.

Enter the parameters required for the Command Operation you select: the Rate.

SIP VoIP tab

When you select Test Activity as Sequencer on the Test Configuration tab, the SIP VoIP tab displays where you may select and setup a sequence of commands, as required.

See VoLTE OnDemand Commands.

When the Test Case is running, double-click the test case to open/edit, and the test case opens.

Click the Command button on the Mobile Subscriber pane of the Test Configuration tab. The Add OnDemand Command window opens. Select the Command Operation from the dropdown list and enter the appropriate values in the parameters.

Enter the parameters required for the Command Operation you select: the Rate.

ControlLrr  tab

When you select Test Activity as Sequencer on the Test Configuration tab, the ControlLrr tab displays (with parameters described in Step 3.) where you may select and setup a sequence of commands, as required.

1.

When the Test Case is running, double-click the test case to open/edit, and the test case opens.

2.

Click the Command button tab. The Execute Command window opens. Select the command options and enter the appropriate values in the parameters.

• Command: Select the test operation from the dropdown list. Select option: Send LRR

3.

Enter the parameters required for the Command you select: the Rate, Starting Subscriber Index, Ending Subscriber Index, and LRR.

Send LRR

ControlLrr { [“op=SendLrr" ]

“rate=RATE”

“Start_sub=START_SUB_INDEX”

“end_Sub=END_SUB_INDEX”

 "lrr=LRR_TO_SEND" }

ControlPlr  tab

When you select Test Activity as Sequencer on the Emulator Configuration tab, the ControlPlr tab displays (with parameters described in Step 3.) where you may select and setup a sequence of commands, as required.

1.

When the Test Case is running, double-click the test case to open/edit, and the test case opens.

2.

Click the Command button tab. The Execute Command window opens. Select the command options and enter the appropriate values in the parameters.

• Command: Select the test operation from the dropdown list. Select option: Send PLR

3.

Enter the parameters required for the Command you select: the Rate, Starting Subscriber Index, Ending Subscriber Index, and PLR.

Send PLR

ControlPlr { [“op=SendPlr" ]

“rate=RATE”

“Start_sub=START_SUB_INDEX”

“end_Sub=END_SUB_INDEX”

"prr=LRR_TO_SEND" }

ControlBearer tab

When you select Test Activity as Sequencer on the Test Configuration tab, the ControlBearer tab displays (with parameters described in Step 3.) where you may select and setup a sequence of commands, as required.

SMS On Demand Commands

In MME Nodal Test Case, the SMS Command button is available on the S1-MME | SMS tab only when the test case is running. Use the Command button to manually select the test command to Start and Stop SMS on demand in Command Mode. You may also use the command when running the Command Sequencer test activity.

The command is available if the Test activity is Command Mode and you select Control Plane SMS (Short Message Service) on the Test Configuration tab (provided you have system license for SMS).

When you select Test Activity as Sequencer and select Control Plane SMS (Short Message Service) on the Test Configuration tab, the ControlSMS tab displays next to the ControlBearer command tab.

S1 AP On Demand Commands

MME Nodal test case supports S1 Reset and eNB Configuration Transfer operation in Command Mode test activity.

A Command button is available at the top of the S1-MME | S1-AP tab during test execution when the Test Activity is Command Mode. A command mode tab labeled ControlS1 displays on the On Demand Command window in MME Nodal test case. The ControlS1 tab is also available on the Sequencer tab in MME Nodal test case.

MME Nodal supports Activate Cell Traffic Trace and Deactivate Cell Traffic Trace in Command Mode tab under ControlS1 tab. See  S1-AP Cell Traffic Trace for addition information.

VoLTE tab

When you select Test Activity as Sequencer on the Test Configuration tab, the VoLTE tab displays where you may select and setup a sequence of commands, as required.

See VoLTE OnDemand Commands.

Click the Command button on the Mobile Subscriber pane of the Test Configuration tab. The Execute Command window opens. Select the command options and enter the appropriate values in the parameters.

• Command: Select the test procedure from the dropdown list. Select option: PDN Connect, PDN Disconnect, Attach, Detach, Reset, Connection Release, ActivateConnection, S1/IRAT Handover, Handover, X2 Handover, TAU/RAU Handover, Emergency Attach, Emergency PDN Connect, ActivateDedicated, DeactivateDedicated, ModifyDefault, ModifyDedicated, Trigger Error Indication, Secondary Node Modification, Secondary Node Release, Switch gNB on Source eNB

3.

Enter the Rate, Starting Subscriber Index, Ending Subscriber Index, Default Bearer Index, Dedicated Bearer Index, Target Node, UDP Port Ext Header, Private Extension IE, Private Extension ID, Private Extension Value, Error Indication Direction and Error Packet Count.

Click Execute to send command and keep the On Demand Command window open, Execute and Close to send command and close the window, Close to cancel your selection. Your selection is sent from the TAS while the test is running and executed on the Test Server.

PdnConnect

ControlBearer {“op=PdnConnect”

“rate=RATE” \

“start_sub=START_SUB_INDEX” \

“end_sub=END_SUB_INDEX” \

"def=DEFAULT_BEARER_INDEX" \

"mod_apn=APN"  \

"mod_pdn=PDN_TYPE_1_2_3"

"failure_msg_1=SCENARIO"  \

"failure_msg_2=SCENARIO" }

Attach

ControlBearer  { "op=Attach" "rate=RATE"

“start_sub=START_SUB_INDEX” \

“end_sub=END_SUB_INDEX” \

"mod_pdn=MPDN_TYPE_1_2_3"

"failure_msg_1=SCENARIO"  \

"failure_msg_2=SCENARIO" }

RESET | Detach |

S1Release |

ActivateConnection |

EmergAttach

ControlBearer  { "op=RESET | Attach | Detach | S1Release |

ActivateConnection | EmergAttach"

"rate=RATE"

“start_sub=START_SUB_INDEX” \

“end_sub=END_SUB_INDEX” \

}

PdnDisconnect |

EmergPdnConnect

ControlBearer  { "op=PdnDisconnect | EmergPdnConnect"

"rate=RATE"

“start_sub=START_SUB_INDEX” \

“end_sub=END_SUB_INDEX” \

"def=DEFAULT_BEARER_INDEX" }

S1/IRAT Handover

ControlBearer  { "op=S1Handover"

"rate=RATE"

“start_sub=START_SUB_INDEX” \

“end_sub=END_SUB_INDEX” \

"start_node=STARTING_TARGET_NODE_INDEX" \

"end_node=ENDING_TARGET_NODE_INDEX" }

Handover

ControlBearer  { "op=Handover"

"rate=RATE"

“start_sub=START_SUB_INDEX” \

“end_sub=END_SUB_INDEX” \

"start_node=STARTING_TARGET_NODE_INDEX" \

"end_node=ENDING_TARGET_NODE_INDEX" }

X2Handover |

TauHandover

ControlBearer  { "op=X2Handover | TauHandover"

"rate=RATE"

“start_sub=START_SUB_INDEX” \

“end_sub=END_SUB_INDEX” \

"start_node=STARTING_TARGET_NODE_INDEX" \

"end_node=ENDING_TARGET_NODE_INDEX" }

ActivateDedicated |

DeactivateDedicated

ControlBearer { "op=ActivateDedicated | DeactivateDedicated"

"rate=RATE"

“start_sub=START_SUB_INDEX” \

“end_sub=END_SUB_INDEX” \

"def=DEFAULT_BEARER_INDEX" \

"ded=DEDICATED_BEARER_INDEX" \

"deact_msg = DEACT_MSG_INDEX }  When deact_msg = Request Bearer Resource Modification (value 1)

ModifyDefault

ControlBearer {"op=ModifyDefault"

    "rate=RATE"

“start_sub=START_SUB_INDEX” \

“end_sub=END_SUB_INDEX” \

"def=DEFAULT_BEARER_INDEX" \

"mod_qos_set=QOS_SET" }

ModifyDedicated

ControlBearer { "op=ModifyDedicated"

"rate=RATE"

“start_sub=START_SUB_INDEX” \

“end_sub=END_SUB_INDEX” \

"def=DEFAULT_BEARER_INDEX \

ded=DEDICATED_BEARER_INDEX" \

"deact_msg = DEACT_MSG_INDEX \

"mod_qos_set=QOS_SET" }

TriggerError

ControlBearer { "op=TriggerError"

"rate=RATE"

“start_sub=START_SUB_INDEX” \

“end_sub=END_SUB_INDEX” \

"dir=ERR_DIR_1_2" \

"pkt_cnt=ERR_PKT_CNT" \

"prt_ext=PORT_EXT_1_0" \

"priv_ext=PRIV_EXT_1_0" \

"priv_id=PRIV_EXT_ID" \

"priv_val=PRIV_EXT_VAL" }

SnModification

ControlBearer { "op=SnModification"

"rate=RATE" \

“start_sub=START_SUB_INDEX” \

“end_sub=END_SUB_INDEX” \

"def=DEFAULT_BEARER_INDEX" \

"ded=DEDICATED_BEARER_INDEX" \

"pkt_cnt=PKT_CNT" \

"ded_en=DED_EN" \

"inc_all_deds=INC_ALL_DEDS" }

SnRelease

ControlBearer { "op=SnRelease"

"rate=RATE" \

“start_sub=START_SUB_INDEX” \

“end_sub=END_SUB_INDEX”  }

ControlBearer { "op=SwGnbUserNode"

"rate=RATE" \

“start_sub=START_SUB_INDEX” \

“end_sub=END_SUB_INDEX”  }

1.

When the Test Case is running, double-click the test case to open/edit, and the test case opens.

2.

Click the Command button on the S1-MME | SMS tab. The Execute Command window opens. Select the command options and enter the appropriate values in the parameters.

• Command: Select the test operation from the dropdown list. Select option: Start, Stop.

3.

Enter the parameters required for the Command you select: the Rate, Starting Subscriber Index, Ending Subscriber Index, Default Bearer, and Dedicated Bearer.

ControlSms { op=Start|op=Stop

rate=[RATE] start_sub=[STARTING_SUBSCRIBER_INDEX]\ end_sub=[ENDING_SUBSCRIBER_INDEX] }

Execute Command window

When you select Mobility as Command Mode on the Emulator Configuration tab, the Execute Command window displays (with parameters described in Step 3) where you may select and setup a sequence of commands, as required.

ControlBearer tab and OverloadControl tab

When you select Mobility as Command Mode on the Emulator Configuration tab, the ControlBearer tab displays (with parameters described in Step 3.) where you may select and setup a sequence of commands, as required.

Command : Request Position Info

Click the Command button on the LPP Tab to execute the Request Position Info Command. The Execute Command window opens. Select the command options and enter the appropriate values in the parameters.

S1 AP On Demand Commands

MME Node test case supports S1 Reset operation in Command Mode test activity.

A Command button is available at the top of the S1-MME | S1-AP tab during test execution when the Mobility is Command Mode. A command mode tab labeled ControlS1 displays on the On Demand Command window in MME Node and Nodal test cases. The ControlS1 tab is also available on the Sequencer tab in MME Nodal test case.

1.

When the Test Case is running, double-click the test case to open/edit, and the test case opens.

2.

Click the Command button on the Mobile Subscriber pane of the Emulator Configuration tab. The Execute Command window opens. Select the command options and enter the appropriate values in the parameters.

• Command: Select the test procedure from the dropdown list. Select option: Page, Activate Dedicated Bearer, Deactivate Dedicated Bearer.

3.

Enter the parameters required for the Command ControlBearer you select: the Rate, Starting Subscriber Index, Ending Subscriber Index, Default Bearer, and Dedicated Bearer.

Enter the parameters required for the Command OverloadControl you select: the Operation, Duration (s), Action, and Target MME.

Enter the parameters required for the Command ControlLcs you select: the Operation, and IMSI.

Click Execute to send command and keep the On Demand Command window open, Execute and Close to send command and close the window, Close to cancel your selection. Your selection is sent from the TAS while the test is running and executed on the Test Server.

Page

ControlBearer { "op=Page" \

"rate=RATE" \

“start_sub=START_SUB_INDEX” \

“end_sub=END_SUB_INDEX”  }

ActivateDedicated | DeactivateDedicated

ControlBearer { "op=ActivateDedicated" | "op=DeactivateDedicated"

r

"rate=RATE" \

“start_sub=START_SUB_INDEX” \

“end_sub=END_SUB_INDEX”  \

"def=DEFAULT_BEARER_INDEX" \

"ded=DEDICATED_BEARER_INDEX" }

OverloadControl

OverloadControl { "op=OverloadStart"

"duration=DURATION"

"ol_action=OL_ACTIONX"

"target_mme=TARGET_MME" }

ControlLcs  { op=ReqPositionInfo

“imsi=IMSI”}

Reset Procedure Initiated from the MME (Landslide response)

If there is a failure at MME resulting in loss of some or all transaction reference information, a RESET message is sent to the eNodeB.

After receiving a RESET message, the eNodeB releases all allocated resources on S1 related to the UE association(s) indicated in the RESET message and removes UE contexts including S1AP ID.

After the eNodeB releases all assigned S1 resources and all UE associations, the eNodeB responds with a RESET ACKNOWLEDGE message.

Reset Procedure Initiated from the E-UTRAN (Landslide Initiated)

If there is a failure at the eNodeB resulting in the loss of some or all transaction reference information, a RESET message is sent to the MME.

After receiving a RESET message, the MME releases all allocated resources on S1 related to the UE association(s) and removes the S1AP ID for the indicated UE associations.

After the MME releases all assigned S1 resources and the UE S1AP IDs for all UE associations, the MME responds with a RESET ACKNOWLEDGE message.

MME load re-balancing between MMEs

(MME Rebalance/Offload - MME Node only)

Select to initiate a load re-balancing/offload between MMEs. Load re-balancing per TS 23.401 chapter 4.3.7.3.

The MME initiates the S1 Release procedure with release cause "load balancing TAU required". The S1 and RRC connections are released and the UE initiates a TAU but provides neither the S-TMSI nor the GUMMEI to eNobeB in the RRC establishment.

eNB Configuration Transfer per 3GPP TS 36.413 version 15.5.0/section 8.15 (packet 259).

Enter Rate, Starting Index/Ending Index and Configuration Index (Number of Configurations) on S1-AP eNodeB Configuration Transfer.

MME Nodal supports the following procedures: 

eNB Configuration Transfer per 3GPP TS 36.413 version 15.5.0/section 8.15 (packet 259)

MME Configuration Transfer per 3GPP TS 36.413 version 15.5.0/section 8.16 (packet 261)

Call Flow:

Limitations:

For MME Node(B2B test), it will sent MME Configuration Transfer message to the same eNB who sent the corresponding eNB Configuration Transfer request message for EN-DC SON Configuration Transfer, which means MME does not store the information about the relationship between eNB and en-gNB.

We only support X2 TNL Configuration Info option for SON Information Request IE in this version. 

We do not support eNB X2 Extended Transport Layer Addresses and eNB Indirect X2 Transport Layer Addresses for X2 TNL Configuration info IE in this version.

S1Reset

ControlS1 { "op=S1Reset" }

Activate Cell Traffic Trace (MME Nodal Only)

ControlS1 { "op=ActivateTrace" }

Deactivate Cell Traffic Trace (MME Nodal Only)

ControlS1 { "op=DeactivateTrace" }

MME Rebalance/Offload  (MME Node Only)

ControlS1 { "op=MmeRebalance" }

         ControlS1 { "op=MmeRebalance"

                            "rate=RATE",

                            "start_enb=START_ENB",

                            "end_enb=END_ENB",

                            "cfg_index=CFG_INDEX"  }

1.

When the Test Case is running, double-click the test case to open/edit, and the test case opens.

2.

Click the Command button on the Mobile Subscriber pane of the Emulator Configuration tab. The Add ControlCredit Command window opens. Select the command options and enter the appropriate values in the parameters.

• Command: Select the test procedure from the dropdown list. Select option: Send ASR, Send RAR, Transport Loss, Failover Recovery, Force MSCC Level Responses, Force Msg Level Responses, Force MSCC & Msg Level Responses, Stop Forced Responses

Select the test operation when the test is running. Options are:

4a.

Send ASR: Parameters on the Add ControlCredit Command window.

4b.

Send RAR: Parameters on the Add ControlCredit Command window.

4c.

Transport Loss/Communication Loss and Failover Recovery: Sends RAR using the information you provide on the Add ControlCredit Command window.

4d.

ForceMsccNegative, ForceMsgNegative, and ForceMsccMsgNegative: Parameters on the Add ControlCredit Command window.

5.

Click Execute to send command and keep the On Demand Command window open, Execute and Close to send command and close the window, Close to cancel your selection. Your selection is sent from the TAS while the test is running and executed on the Test Server.

SendASR | SendRAR

ControlCredit {SendASR | SendRAR

STARTING_SUBSCRIBER_INDEX    

ENDING_SUBSCRIBER_INDEX  

RATE   

RATING_GROUP_IDS or none

SERVICE_IDS or none }

TransLoss | CommLoss | Recovery

ControlCredit {TransLoss | CommLoss | Recovery

RATE

STARTING_NODE_INDEX

ENDING_NODE_INDEX }

ForceMsccNegative |

ForceMsccMsgNegative

ControlCredit { ForceMsccNegative | ForceMsccMsgNegative

RATE \

STARTING_SUBSCRIBER_INDEX ENDING_SUBSCRIBER_INDEX \

RESULT_CODE \

STARTING_MSCC_INDEX \

ENDING_MSCC_INDEX}

ForceMsgNegative

ControlCredit { ForceMsgNegative

RATE \

STARTING_SUBSCRIBER_INDEX ENDING_SUBSCRIBER_INDEX \

RESULT_CODE }

StopNegative

ControlCredit { StopNegative

RATE \

STARTING_SUBSCRIBER_INDEX ENDING_SUBSCRIBER_INDEX }

1.

When the Test Case is running, double-click the test case to open/edit, and the test case opens.

2.

Click the Command button on the Mobile Subscriber pane of the Emulator Configuration tab. The Add ControlNodes Command window opens. Select the command options and enter the appropriate values in the parameters.

• Command: Select the test procedure from the dropdown list. Select option: Communication Loss, Failover Recovery

Select the test operation when the test is running. Options are:

4.

Transport Loss/Communication Loss and Failover Recovery: Sends RAR using the information you provide on the Add ControlNodes Command window.

5.

Click Execute to send command and keep the On Demand Command window open, Execute and Close to send command and close the window, Close to cancel your selection. Your selection is sent from the TAS while the test is running and executed on the Test Server.

CommLoss | Recovery

ControlNodes {CommLoss | Recovery

rate=RATE \

start_node=START_NODE_INDEX \

end_node=END_NODE_INDEX }

1.

When the Test Case is running, double-click the test case to open/edit, and the test case opens.

2.

Click the Command button on the Mobile Subscriber pane of the Test Configuration tab. The Execute Command window opens. Select the command options and enter the appropriate values in the parameters.

• Command: Select the test procedure from the dropdown list. Select option:  Provision, Modify, Open Gate, Close Gate, Terminate.

3.

Enter the parameters required for the Command you select: the Rate, Starting Subscriber Index, Ending Subscriber Index. Starting MCD Index, Ending MCD Index

Rate	Indicates (controls) the rate of call flow across IMSIs/UEs. Enter a valid range between 1.0 - 1000.0 (default value is 1).
Starting Subscriber Index, Ending Subscriber Index	Enter the Starting Index and Ending Index. Indicates the range of subscribers to which the selected operation is applied. Valid range is equal to the Number of Subscribers specified on the Mobile Subscriber pane on the Emulator Configuration tab.
MCD Starting Index, MCD Ending Index	Enter the MCD Starting Index and MCD Ending Index.  Only in Command mode or Sequencer are you allowed to configure up to three MCDs. NOTE: Only in Command mode or Sequencer are you allowed to configure up to three MCDs. Some fields within the MCD configuration are edit-able at run-time.
Select Actions	Depending on the interface and LTE specs version, different lists will become available to select.

Provision

ControlAfSession {“op=Provision”

“rate-RATE”

“start_sub=START_SUB_INDEX”

“end_sub-END_SUB_INDEX”

“start_mcd=STARTING_MCD_NUMBER”

“end_mcd=ENDING_MCD_NUMBER”

“actions=ACTIONS_BITMASK_INT”}

Modify| OpenGate | CloseGate

ControlAfSession {“op=Modify|OpenGate|CloseGate”

“rate-RATE”

“start_sub=START_SUB_INDEX”

“end_sub-END_SUB_INDEX”

“start_mcd=STARTING_MCD_NUMBER”

“end_mcd=ENDING_MCD_NUMBER”}

Terminate

ControlAfSession {“op=Terminate”

“rate-RATE”

“start_sub=START_SUB_INDEX”

“end_sub-END_SUB_INDEX” }

• Operation:

Select the test operation when the test is running. Options are:

• Rate

Enter the maximum rate (activation/deactivation) allowed by your test case (defined by your license).

Starting Index and Ending Index

• Subscribers

• IPv4, IPv6, Dual Stack Rule Sets

• APNs

• Monitors

• Nodes

Enter the Starting and Ending indexes for the following:

• Subscribers: Enter the starting and ending Subscriber numbers for all operations.

• IPv4, IPv6, Dual Stack Rule Sets: Enter the starting and ending rule set numbers for all Install Rule and Remove Rule operations.

• APNs: Enter starting and ending APNs for Install APN Rule and Remove APN Rule operation.

• Monitors: Enter a range of starting and ending monitoring instance numbers to Start/Stop Monitoring  or Request Monitoring Report.

For Request Monitoring Report, if both starting and ending monitoring instance numbers are zero, PCRF will request PCEF to report current usage of all active monitoring instances.

• Nodes: Enter a range of starting and ending Nodes used for failover purposes.

• Release Cause

Indicates releasing APN session. Enter a range of  APN to release and select the Release Cause from the dropdown list.

• Unspecified
• UE Subscription
• Insufficient Resources

• Include Triggers

• Force Result Code Type

Allows you to force send specified result code type in the CCA success or failure messages for a range of subscribers, during a specified period of time.

Select the result code type and then select the appropriate Result_Code you wish to send from the list:

• Message Level (1)
• Experimental (2)

The Mobile Subscriber outside of the specified ranges receives regular CCA messages (that is, without the Force Result Type).

• Result Code

Allows you to specify the result code for the Result Code Type you selected.

See List of Result CodeSee List of Result Code

• Force Node Types

Allows you to specify whether to force a Result Code on both Primary and Secondary nodes.

Select : Primaries and Secondaries (Default), Primaries, Secondaries

InstallRule | RemoveRule | ExecuteRules

ControlRules {"op=InstallRule" | "op=RemoveRule" | "op=ExecuteRules"

“rate-RATE” \

“start_sub=START_SUB_INDEX” \

“end_sub-END_SUB_INDEX” \

"Start_v4rs=START_V4_RULE_SET" \

      "end_v4rs=END_V4_RULE_SET" \

      "start_v6rs=START_V6_RULE_SET" \

      "end_v6rs=END_V6_RULE_SET" \

      "start_dsrs=START_DS_RULE_SET" \

      "end_dsrs=END_DS_RULE_SET" \

      "TriggerMask0=MASK_0" \

      "TriggerMask23=MASK_23" }

InstallApnRule | RemoveApnRule | ExecutepnRules

ControlRules {"op=InstallApnRule" | "op=RemoveApnRule" | "op=ExecuteApnRules "    

“rate-RATE” \

“start_sub=START_SUB_INDEX” \

“end_sub-END_SUB_INDEX” \

      "start_apn=START_APN_INDEX" \

      "end_apn=END_APN_INDEX"            

      "TriggerMask0=MASK_0" \

      "TriggerMask23=MASK_23" }

ReleaseSession

ControlRules {"op=ReleaseSession"        

“rate-RATE” \

“start_sub=START_SUB_INDEX” \

“end_sub-END_SUB_INDEX” \

      "start_apn=START_APN_INDEX" \

      "end_apn=END_APN_INDEX"      \     

      "cause=RELEASE_CAUSE" }

StartMon | StopMon | ReqMonReport

ControlRules { "op=StartMon" | "op=StopMon" | "op=ReqMonReport"

“rate-RATE” \

“start_sub=START_SUB_INDEX” \

“end_sub-END_SUB_INDEX” \

      "start_mon=START_MONITOR_INDEX" \

      "end_mon=END_MONITOR_INDEX"       \     

      "TriggerMask0=MASK_0" \

      "TriggerMask23=MASK_23" }

TransLoss| CommLoss| Recovery

ControlRules {"op=TransLoss"| "op=CommLoss" | "op=Recovery"

“rate-RATE” \

“start_node=START_NODE_INDEX” \

“end_node-END_NODE_INDEX” }

ForceNegative

ControlRules {"op=ForceNegative"

“rate-RATE” \

“start_sub=START_SUB_INDEX” \

“end_sub-END_SUB_INDEX” \

      "set=CODE_SET_1_2" \

      "code=RESULT_CODE"      \     

      "nodes=0_1_2" }

StopNegative

ControlRules {"op=StopNegative"

“rate-RATE” \

“start_sub=START_SUB_INDEX” \

“end_sub-END_SUB_INDEX” }

SctpAction

ControlRules {"op=AckEnable" | "AckDisable"

          PATH

                INTERFACE }

VoLTE tab

When you select Test Activity as Sequencer on the Test Configuration tab, the VoLTE tab displays where you may select and setup a sequence of commands, as required.

See VoLTE OnDemand Commands.

• Operation:

Select the test operation from the dropdown list. Options are:  Attach, Detach, Detach Local, S1 Release, Reset, StartDedicateds, StopDedicateds, PdnConnect, PdnDisconnect, ModifyBearerHSSInit, ModifyBearerMMEInit, ModifyBearerUEInit, StartUE, StopUE, RegisterRouter, DeRegisterRouter

• Log Execution

• Rate

• Subscriber

OR

• Mobile Routers

Enter the Starting Subscriber Index, Ending Subscriber Index. Valid range is equal to the Number of Subscribers specified on the Mobile Subscriber pane of the Test Configuration tab.

The label Mobile Routers displays when you select NEMO Emulation on the Test Configuration tab (the ControlBearer commands operate on routers). Enter the Starting Mobile Router Index and Ending Mobile Router index.  Valid range is equal to the Number of Mobile Routers specified on the Mobile Subscriber pane of the Test Configuration tab.  

• Default Bearer

Enter the Starting Default Bearer Index, Ending Default Bearer Index.

Valid range: 1 - 11 and <= the number of Default Bearer Per Session selected on the Mobile Subscriber pane of the Test Configuration tab.

When you select NEMO Emulation the maximum Default Bearer per Session is 1.

• Dedicated Bearers

• Stop Separately

• Target SGW

• UE

• UDP Port Ext Header

Available when Operation type = Detach Local.

Enable to provide the UDP Source Port of the G-PDU that triggered the Error Indication in the Extension header.

• Private Extension IE
• Private Extension ID
• Private Extension Value

Available when Operation type = Detach Local.

Enable to include the Private Extension Header in the Error Indication Message. When enabled, the two fields Private Extension ID and Private Extension Value will be included in the Private Extension Header of the Error Indication message.

Private Extension ID: 0 to 65535, Default = 0

Private Extension Value: 64 bit Hex Value  Default = 0x0

• Router Prefix

Indicates the Router prefix to which the UE is attached.  

Valid Range: 1 - the Number of Prefixes, entered on the MIP NEMO tab

Attach | Detach | Reset | ModifyBearerMMEInit | DeRegisterRouter

ControlBearer { "op=Attach" | "op=Detach" | "op=Reset" |

"op=ModifyBearerMMEInit" | "op=DeRegisterRouter"

"rate=RATE"

"start_sub=START_SUB_INDEX" \

"end_sub=END_SUB_INDEX" }

Detach Local  

ControlBearer { ["op=DetachLocal" ]

"rate=RATE"

"start_sub=START_SUB_INDEX" \

"end_sub=END_SUB_INDEX" \

"prt_ext_en=1_0" \

"priv_ext_en=1_0" \

"priv_ext_id=ID" \

"priv_ext_val=VAL" }

PdnConnect | PdnDisconnect

ControlBearer { "op=PdnConnect" | "op=PdnDisconnect" \

"rate=RATE"

"start_sub=START_SUB_INDEX" \

"end_sub=END_SUB_INDEX" \

"start_def=STARTING_DEFAULT_BEARER_INDEX" \

"end_def=ENDING_DEFAULT_BEARER_INDEX" }

StopDedicated | StartDedicated

ControlBearer { "op=StopDedicated" |  "op=StartDedicated" \

"rate=RATE"

"start_sub=START_SUB_INDEX" \

"end_sub=END_SUB_INDEX" \

"start_def=STARTING_DEFAULT_BEARER_INDEX" \

"end_def=ENDING_DEFAULT_BEARER_INDEX"  \

"start_ded=STARTING_DEDICATED_BEARER_INDEX" \

"end_ded=ENDING_DEDICATED_BEARER_INDEX

"separately=STOP_SEPARATELY }

ModifyBearerHSSInit

ControlBearer { "op=ModifyBearerHSSInit" \

"rate=RATE"

"start_sub=START_SUB_INDEX" \

"end_sub=END_SUB_INDEX" \

"def=DEFAULT_BEARER_INDEX" }

ModifyBearerUEInit

ControlBearer { "op=ModifyBearerUEInit" \

"rate=RATE"

"start_sub=START_SUB_INDEX" \

"end_sub=END_SUB_INDEX" \

"def=DEFAULT_BEARER_INDEX" \

"ded=DEDICATED_BEARER_INDEX" }

S1Handover | X2Handover | TauHandover

ControlBearer { "Op=S1Handover" | "op=X2Handover" |

"op=TauHandover" \

"rate=RATE"

"start_sub=START_SUB_INDEX" \

"end_sub=END_SUB_INDEX" \

"start_nodeSTARTING_TARGET_SGW_INDEX" \

"end_node=ENDING_ TARGET_SGW_INDEX" }

StartUE | StopUE

ControlBearer { "op=StartUE" | "op=StopUE" \

"rate=RATE"

"start_sub=START_SUB_INDEX" \

"end_sub=END_SUB_INDEX" \

"start_ue=STARTING_UE_INDEX" \

"end_ue=ENDING_UE_INDEX" }

RegisterRouter

ControlBearer { "op=RegisterRouter" \

"rate=RATE"

"start_sub=START_SUB_INDEX" \

"end_sub=END_SUB_INDEX" \

"start_pfx=STARTING_PREFIX_INDEX" \

"end_pfx=ENDING_PREFIX_INDEX" }

Use this to restart the MME Control Node, send an Echo Request with a retart counter/value (recovery IE) and (SGW) delete all bearer contexts affected by the restart.

ExecuteExtApps tab

Used to execute the External Apps via ODC. The Start the test with On-Demand command on External Apps Tab must be enabled. Currently supported in AMF Nodal, SGW Nodal and UE Node test cases. When running the test in Command Mode, the "Command" button for the External Apps ODC will be visible on L3-7|External Apps tab.

VoLTE tab

When you select Test Activity as Sequencer on the Test Configuration tab, the VoLTE tab displays where you may select and setup a sequence of commands, as required.

See VoLTE OnDemand Commands

When the Test Case is running, double-click the test case to open/edit, and the test case opens.

Click the Command button on the Mobile Subscriber pane of the Test Configuration tab. The Execute Command window opens. Select the Command Operation from the dropdown list and enter the appropriate values in the parameters.

ControlBearer Command

ControlNodes Command

4.

ExecuteExtApps Command

Click Execute to send command and keep the On Demand Command window open, Execute and Close to send command and close the window, Close to cancel your selection. Your selection is sent from the TAS while the test is running and executed on the Test Server.

Operation

Test Case Command ControlBearer

ControlBearer { op=Attach

                rate=RATE

       start_sub=START_SUB_INDEX

       end_sub=END_SUB_INDEX

       mod_apn=MODIFY_APN_1_0

       mod_pdn=MODIFY_PDN_TYPE_1_0 }

---------------------------------------------------

       rate=RATE

       start_sub=START_SUB_INDEX

       end_sub=END_SUB_INDEX

       mod_apn=MODIFY_APN_1_0

       apn=APN

            mod_pdn=MODIFY_PDN_TYPE_1_0

       pdn_type=PDN_TYPE_1_2_3

Detach |  

Reset | SendBRI

ControlBearer { [op=Detach | op=Reset | op=SendBRI ]

       rate=RATE

       start_sub=START_SUB_INDEX

       end_sub=END_SUB_INDEX }

S1Release

ControlBearer { [op=S1Release ]

       rate=RATE

       start_sub=START_SUB_INDEX

       end_sub=END_SUB_INDEX

       pause_chrg=1_0}

Detach Local  

ControlBearer { [op=DetachLocal ]

       rate=RATE

       start_sub=START_SUB_INDEX

       end_sub=END_SUB_INDEX

       prt_ext=PORT_EXT_1_0

       priv_ext=PRIV_EXT_1_0}

---------------------------------------------------

ControlBearer { [op=DetachLocal ]

       rate=RATE

       start_sub=START_SUB_INDEX

       end_sub=END_SUB_INDEX

       prt_ext=PORT_EXT_1_0

       priv_ext=PRIV_EXT_1_0

       priv_id=PRIV_EXT_ID

       priv_val=PRIV_EXT_VAL }

Suspend | Resume

ControlBearer { [op=Suspend | op=Resume ]

       rate=RATE

       start_sub=START_SUB_INDEX

 end_sub=END_SUB_INDEX

 option=SUSPEND_OPTION |option=RESUME_OPTION }

EmergAttach

ControlBearer { [op=EmergAttach]

       rate=RATE

       start_sub=START_SUB_INDEX

 end_sub=END_SUB_INDEX }

PDNConnect

ControlBearer { [op=PDNConnect ]

       rate=RATE

       start_sub=START_SUB_INDEX

 end_sub=END_SUB_INDEX

 start_def=START_DEFAULT_INDEX

 end_def=START_DEFAULT_INDEX

 mod_apn=MODIFY_APN_1_0

 apn= APN

 mod_pdn=MODIFY_PDN_TYPE_1_0

 pdn_type=PDN_TYPE_1_2_3 }

PDNDisconnect

ControlBearer { [op=PDNDisconnect]

       rate=RATE

       start_sub=START_SUB_INDEX

 end_sub=END_SUB_INDEX

 start_def=START_DEFAULT_INDEX

 end_def=START_DEFAULT_INDEX }

EmergPDNConnect

ControlBearer { [op=EmergPDNConnect]

 rate=RATE

       start_sub=START_SUB_INDEX

 end_sub=END_SUB_INDEX

 start_def=START_DEFAULT_INDEX

 end_def=START_DEFAULT_INDEX }

StartDedicateds | StopDedicateds

ControlBearer { [op=StartDedicateds | op=StopDedicateds]

 rate=RATE

       start_sub=START_SUB_INDEX

 end_sub=END_SUB_INDEX

 start_def=START_DEFAULT_INDEX

 end_def=START_DEFAULT_INDEX

 start_ded=START_DEDICATED_INDEX

 end_ded=END_DEDICATED_INDEX }

ModifyBearer

ControlBearer { op=ModifyBearer

 rate=RATE

       start_sub=START_SUB_INDEX

 end_sub=END_SUB_INDEX

 mod_init=MOD_INITIATOR

 mod_set=MOD_SET_1_10

 def=DEFAULT_INDEX

 ded=DEDICATED_INDEX

 tft_op=TFT_OP_CODE }

Handover

(SGW Relocation or Circuit Switched Fallback is not available)

ControlBearer { [op=Handover]

 rate=RATE

       start_sub=START_SUB_INDEX

 end_sub=END_SUB_INDEX

 start_node=START_NODE_INDEX

 end_node=END_NODE_INDEX }

Handover

(SGW Relocation or Circuit Switched Fallback is available)

ControlBearer { [op=Handover]

 rate=RATE

       start_sub=START_SUB_INDEX

 end_sub=END_SUB_INDEX

 start_node=START_NODE_INDEX

 end_node=END_NODE_INDEX

 option=OPTION1 }

Handover Bearer

ControlBearer { [op=HandoverBearer]

 rate=RATE

       start_sub=START_SUB_INDEX

 end_sub=END_SUB_INDEX

 def=DEFAULT_INDEX

 start_node=START_TGT_NODE_INDEX

 end_node=END_TGT_NODE_INDEX

 detach=DETACH_BEARER_1_0 }

S1Handover | X2Handover

ControlBearer { [op=S1Handover | op=X2Handover | \

 rate=RATE

       start_sub=START_SUB_INDEX

 end_sub=END_SUB_INDEX

 def=DEFAULT_INDEX

 start_node=START_TGT_ENODEB_INDEX

 end_node=END_TGT_ENODEB_INDEX

 sgw_relo=SGW_RELO_1_0 }

TauHandover

ControlBearer { [op=TauHandover

 rate=RATE

       start_sub=START_SUB_INDEX

 end_sub=END_SUB_INDEX

 def=DEFAULT_INDEX

 start_node=START_TGT_ENODEB_INDEX

 end_node=END_TGT_ENODEB_INDEX

 sgw_relo=SGW_RELO_1_0

 flag=ACTIVE_FLAG_0_1_2}

ModifyBearerHSSInit

ControlBearer { [op=ModifyBearerMMEInit]

 rate=RATE

       start_sub=START_SUB_INDEX

 end_sub=END_SUB_INDEX

 mod_init=MOD_INITIATOR

 mod_set=MOD_SET_1_10

 def=DEFAULT_INDEX }

ModifyBearerMMEInit

ControlBearer { [op=ModifyBearerMMEInit]

 rate=RATE

       start_sub=START_SUB_INDEX

 end_sub=END_SUB_INDEX

 mod_init=MOD_INITIATOR

 mod_set=MOD_SET_1_10

 def=DEFAULT_INDEX }

ModifyBearerUEInit

ControlBearer { [ModifyBearerMMEInit]

 rate=RATE

       start_sub=START_SUB_INDEX

 end_sub=END_SUB_INDEX

 mod_init=MOD_INITIATOR

 mod_set=MOD_SET_1_10

 def=DEFAULT_INDEX

 ded=DEDICATED_INDEX

 tft_op=TFT_OP_CODE }

TriggerError

ControlBearer { op=TriggerError

 rate=RATE

 start_sub=STARTING_SUB_INDEX

 end_sub=ENDING_SUB_INDEX

 dir=ERR_DIR_1_2

 pkt_cnt=ERR_PKT_CNT

 prt_ext=PORT_EXT_1_0

 priv_ext=PRIV_EXT_1_0

 priv_id=PRIV_EXT_ID

 priv_val=PRIV_EXT_VAL }

Operation

Test Case Command ControlNode

MmeRestart

ControlNodes { op=MmeRestart

rate=RATE

start_node=STARTING_NODE_INDEX end_node=ENDING_NODE_INDEX }

Operation

Test Case Command ExecuteExtApps

In ODC Name ExecuteExtApps, the only parameter is the test name.

Operations : Start HTTP, Start Ping, Start Video, Start Spped Test, Start Speed Test Lab, Start FTP, Start Traceroute

See External App Configuration for test case parameters. 

Each application can only run 1 time (in sequencer). For Sequencer , validation has been added that blocks using the same operation twice.

The Estimated Duration in a Sequencer test is the total timeout value for each test found in the External App Configuration.  However, each test type has a different formula for Timeout value. If a test runs longer than the Estimated duration, Landslide will stop executing the test and mark it as a failure.

Estimated Duration test calculation : 

HTTP Test estimated duration =  (# of URL * timeout * Iteration) 

Traceroute test estimated duration = (timeout * (1 + # of Ping) * # of Host) 

TWAMP Test estimated duration =  (timeout * # of Host * Iteration) 

Android VM estimated duration = add up all the timeout value of enabled tests

For all other tests, the estimated duration =  Use timeout value in External App Configuration as estimated duration.

Example of Command Sequence: 

Test name

Control5G tab

When you select Test Activity as Sequencer on the Test Configuration tab, the Control5G tab displays (with parameters described in Step 3.) where you may select and setup a sequence of commands, as required.

1.

When the Test Case is running, double-click the test case to open/edit, and the test case opens.

2.

Click the Command button tab. The Execute Command window opens. Select the command options and enter the appropriate values in the parameters.

• Command: Select the test operation from the dropdown list. Select option: Register, Deregister, PDU Connect, PDU Release, Active Connection, Release Connection, Reset, PDU Modify, Xn Handover, N2 Handover, Reg/Tau Mobility, EPS Attach, EPS/5GS Handover, X2 Handover, S1 Handover, Reg/TAU Mobility

3.

Enter the parameters required for the Command you select: the Rate, Starting Subscriber Index, Ending Subscriber Index, Target Node Type, Starting Target Node Index, Ending Target Node Index, PDUs Starting Index, PDUs Ending Index  and Modification Set (Flow, Action, QFI and 5QI).

Register |

Xn Handover |

N2 Handover | 

X2 Handover | 

S1 Handover

Control5G { [“op=Register" | "XnHandover" | "N2Handover" | | "X2Handover" | "S1Handover" ]

“rate=RATE”

“start_sub=START_SUB_INDEX”

“end_Sub=END_SUB_INDEX”

“start_node=START_NODE_INDEX”

“end_node=END_NODE_INDEX” }

Deregister | Reset | ActivateConnection | ReleaseConnection

Control5G { [“op=Deregister | Reset | ReleaseConnection | ActivateConnection "]

“rate=RATE”

“start_sub=START_SUB_INDEX”

“end_Sub=END_SUB_INDEX”  }

Eps5gsHandover |

RegTauMobility 

Control5G { [“op=Eps5gsHandover" | "RegTauMobility" ]

“rate=RATE”

“start_sub=START_SUB_INDEX”

“end_Sub=END_SUB_INDEX”

“start_node=START_NODE_INDEX”

“end_Node=END_NODE_INDEX”

 "target_node_type=gnb or sgw"

"eabi=1_0"

}

Control5G { [“op=EpsAttach"]

“rate=RATE”

“start_sub=START_SUB_INDEX”

“end_Sub=END_SUB_INDEX”

“start_node=START_NODE_INDEX”

“end_Node=END_NODE_INDEX” }

PduConnect | PduRelease

Control5G { [“op=PduConnect "]

“rate=RATE”

“start_sub=START_SUB_INDEX”

“end_Sub=END_SUB_INDEX”

“start_pdu=START_PDU”

“end_pdu=END_PDU”

"failure_msg_1=SCENARIO }

PduRelease

Control5G { [“op=PduRelease "]

“rate=RATE”

“start_sub=START_SUB_INDEX”

“end_Sub=END_SUB_INDEX”

“start_pdu=START_PDU”

“end_pdu=END_PDU” }

PduModify

Control5G { [“op=PduModify "]

“rate=RATE”

“start_sub=START_SUB_INDEX”

“end_Sub=END_SUB_INDEX”

“pdu=PDU_INDEX”

“mod_set=MOD_SET_1_10” }

Rate

Indicates (controls) the rate of nodes/sec. Enter a valid range between .001 - 30000.0 (default value is 1.0). The maximum rate depends on your system license.

Available for All Operations. 

Reset

ControlRic { "op=RicE2Reset, 

“rate=RATE”}

Available when Non-RT and A1 Interface are enabled on the RIC Node Emulator Configuration test case for Policy commands.

Command : Query Policy Type Identifiers, Query All Policy Identifiers, Query Policy Type, Create Policy, Update Single Policy, Query Single Policy, Query Policy Status, Delete Policy

Click the Command / Sequencer button on the RIC Node Emulator Configuration to execute the Query Policy Type Identifiers, Query All Policy Identifiers, Query Policy Type, Create Policy, Update Single Policy, Query Single Policy, Query Policy Status, Delete Policy Commands. The Execute Command window opens. Select the command options and enter the appropriate values in the parameters.

Available when Near-RT and Test A1EI are enabled on the RIC Node Emulator Configuration test case for (Enrichment Information Service) Query Job Procedures.

Command : Query Type Identifiers, Query Type, Query Job Identifiers, Query Job, Create Job, Update Job,  Query Job Status, Delete Job

Click the Command / Sequencer button on the RIC Node Emulator Configuration to execute the Query Type Identifiers, Query Type, Query Job Identifiers, Query Job, Create Job, Update Job,  Query Job Status, Delete Job Commands. The Execute Command window opens. Select the command options and enter the appropriate values in the parameters.

Available when Near-RT and E2 Interface  are enabled on the RIC Node Emulator Configuration test case for RIC Subscription and ROC Control per spec O-RAN.WG3.E2SM-RC-v01.03.

Command : RIC Subscription, RIC Subscription Delete, RIC Control, Reset

Click the Command / Sequencer button on the RIC Node Emulator Configuration to execute the RIC Subscription, RIC Subscription Delete, RIC Control, Reset Commands. The Execute Command window opens. Select the command options and enter the appropriate values in the parameters.

ControlRic Reset will be blocked in sequence validation if there is not at least one subscription by the Target E2 Node Type for any RAN Function type. In addition, a Reset will clear the subscription lists (all Functions) for either CU or DU depending on the Target E2 Node command parameter. This will block Deletes of any Function/Reference after Reset that have not been resubscribed to.

Available when Non-RT and O1 Interface are enabled on the RIC Node Emulator Configuration test case for Policy commands.

Command : Create MOI, Modify MOI, Delete MOI, Read MOI, Lock Data Store, Unlock Data Store

Click the Command / Sequencer button on the RIC Node Emulator Configuration to execute the Create MOI, Modify MOI, Delete MOI, Read MOI, Lock Data Store, Unlock Data Store Commands. The Execute Command window opens. Select the command options and enter the appropriate values in the parameters.

1.

When the Test Case is running, double-click the test case to open/edit, and the test case opens.

2.

3.

Enter the parameters required for the Command you select: the Rate, Policy Index, Type Index

Query Policy Type Identifiers

Query All Policy Identifiers

Query Policy Type

ControlA1p { "op=QueryPolicyTypeIdentifiers" |