Setting Up a Handoff Test

When you select a handoff test, you can define the node that will participate in the handoffs or the MN addresses used for handoffs, when the handoffs will begin, and in some cases, the number of handoffs and the handoff rate.

Learn more about handoff tests

These instructions assume that you are working with a saved test session, and only provide information on defining this test activity. See Related Topics for instructions on configuring the test cases that can use a handoff test.

TIP: Start with a test case that you have successfully executed with a Capacity Test.

To set up a handoff test:

Open a test session...
Edit the test case... that will run the test.
Select a handoff test from the Test Activity drop-down list on the Test Configuration tab.
Depending on the test case and handoff test type, you may either define a node emulator, a second set of MN addresses, or a second SUT that will receive the handoff sessions:

- In an HA Nodal Inter-PDSN test, define the Mobility FA Node that will receive the handoffs.
- In other Inter-PDSN tests or an Intra-PDSN test, define the Mobility PCF Node that will receive the handoffs.
- In an Inter-SGSN test, define the Mobility SGSN Node Group that will receive the handoffs.
- In an Inter-FA test, define the Mobility FA Node #2 that will receive the handoffs.
- In a Mobile Node Mobility test, either define the care-of addresses... that will be assigned to the MNs during the handoffs (Mobile IP testing) or define the Target Base Station.
- In a Returning Home test, the home addresses... defined on the Mobile Node tab are assigned to the MNs during the handoffs.
- In a CDMA/WiFi Convergence Inter-Technology Mobility test, define the PCF Node that will receive the handoffs.
- In a HNB Intra-HNB GW Mobility, define
- In a UMTS Mobility test, define the Mobility Control Node and the Mobility User Node.
- In a CSN Nodal Inter-Technology Mobility test, define the FA Node that will receive the handoffs.
- In a SGW Nodal Inter-MME Mobility test define Target eNodeB and Target MME Node and in a Intra-MME Mobility test define a Target eNodeB .
The SGW Nodal Inter-SGSN Mobility supports S4-SGSN to S4-SGSN Handoff and on the Network Devices tab define S4 SGSN Control Node and Target SGSN Control Node.
When Handoff protocol is UMTS Version 7, define S4 and Gn interface parameters.

When UMTS Version 8 is, define S4 and Target Bearer interface parameters.
- In a MME Nodal Intra-MME and Inter-MME test, you define the S1-MME interface with the NAS tab and Target eNodeB (User and Control) Nodes.
- In a AMF and SMF Nodal Intra-AMF Mobility supports Xn handover, you define the N1 interface with the NAS-5G-Sm, NAS-5G-MM tabs, and Target gNodeB User Node, Target gNodeB Control Node, (User and Control) Nodes.
- In a AMF and SMF Nodal Inter-AMF Mobility supports N2 handover, you define the N2 interface with the NGAP, NAS-5G-Sm, NAS-5G-MM tabs, and Target gNodeB User Node, Target gNodeB Control Node, (User and Control) Nodes. Adds support for AMF to AMF N2 Mobility scenarios (TAU and Handover) in AMF Nodal and SMF Nodal (Target AMF SBI Node and Target Namf, Target AMF-SMF also become available for input). To emulate two AMFs for Inter-AMF scenario in SMF-Nodal, it is required to create two sets of all SBI Sessions per subscriber which should handle the role of S-AMF and T-AMF over SBI Interface during Inter-AMF. Limits the Number of Subscribers to 1/2 the licensed max value when "Inter-AMF Mobility" is selected in SMF Nodal test case.
- In a AMF Nodal Dual Connectivity supports RAN Initiated QoS Flow Mobility , per 3GPP 23.502 , 38.413, 29.502. You define the N1 interface with the NAS-5G-Sm, NAS-5G-MM tabs, and gNB User Node, Secondary gNB User Node, gNodeB Control Node, (User and Control) Nodes.
- In gNB CU NSA Inter-CU Mobility - supports Secondary Node Change procedure initiated either by MN or SN and used to transfer a UE context from a source SN to a target SN and to change the SCG configuration in UE from one SN to another. (per Spec 3GPP TS 37.340 version 15.6.0 Release/section 10.5 Secondary Node Change (MN/SN initiated). In gNB CU NSA Nodal test case, you define the S1-MME interface with the NAS tab, F1 with F1-AP, X2-ENB with X2-AP and Target gNB DU Control Node, Target gNB DU User Node, (User and Control) Nodes. SUT is gNB CU (Number of Target gNB-CU SUTs).
- In gNB CU SA Inter-CU Mobility - supports Xn Handover Procedure which includes four components : 1. Based on the received measurements, Source gNB initiates the handover through Xn interface. 2. Target gNB provides a new RRC configuration and performs admission control. 3. Source gNB forwards the Handover Request Acknowledge message to the UE, along with cell ID, access information, and beam-specific information. 4. UE moves to RRC connected state with Target gNB and sends the RRC Reconfiguration Complete message.
- Per Spec 3GPP TS 38.401, section 8.2.1.1 Inter-gNB-DU Mobility.The Call Flow for Landslide's Xn Handover is shown below. In gNB CU SA Nodal test case, you define the NAS-5G interface with SM and MM, F1 with F1-AP, AS-5G with RRC and Message Editor and Target gNB DU Control Node, Target gNB DU User Node, (User and Control) Nodes. SUT is gNB CU (Number of Target gNB-CU SUTs).
- In gNB CU SA Intra-CU Mobility - 1) When target cell id in received measurement report message is local at the GNB-CU, the operation is identified as INTRA-CU handover 2) gNB-CU sends out UE Context Setup Request message to target GNB-DU 3) gNB-CU sends out UE Context Modification Request with RrcReconfiguration to source GNB-DU, when it receives UE Context Setup Response from target GNB-DU 4) gNB-CU releases UE Context at source GNB-DU when it receives RRCReconfiguration Complete message from target GNB-DU. When "Intra-CU Mobility" is selected, only one gNB-CU SUTs can be configured at at "Network Devices" tab at gNB CU SA Nodal test case. Spec references : 3GPP TS 23.502 - Procedures for the 5G System (5GS); Stage-2 , 3GPP TS 38.331 – NG-RAN RRC Protocol , 3GPP TS 38.401 - NG-RAN Architecture Description , 3GPP TS 38.473 – NG-RAN F1 Application Protocol. Message Flow : In gNB CU SA Nodal test case, you define the NAS-5G interface with SM and MM, F1 with F1-AP, AS-5G with RRC and Message Editor and Target gNB DU Control Node, Target gNB DU User Node, (User and Control) Nodes. SUT is gNB CU (Only 1 SUT is supported).
- In gNB CU SA Nodal test case Intra-DU Mobility - in which UE moves from one cell to another cell within the same gNB-DU, at gNB CU SA Nodal / gNB CU Node test cases. Per 3GPP 38.401 8.2.1.2 & 38.473 8.3.4. In this diagram, we show a UE moving from one cell to another cell within the same gNB-DU. This UE is served under the 5G NR air interface only.
  
  The UE is receiving DL data and sending UL data with a cell from a gNB-DU. As the UE performs RF measurements and finds another cell to be stronger to meet the handover criteria, it sends a Measurement Report message.
  
  • The gNB-DU forwards this message to the gNB-CU in the Uplink RRC Transfer message envelop.
  
  • The gNB-CU and the gNB-DU exchange UE Context modification messages.
  
  • Finally, gNB-CU informs the UE (via the gNB-DU) of the RRC Connection Reconfiguration message.
  
  • The UE performs a random access procedure with a new cell and finally sends an RRC Connection Reconfiguration Complete message back the gNB-CU (via the gNB-DU).
  
  • At this point, the handover is completed successfully to the new cell of the gNB-DU.
- In gNB CU NSA 5GNSA-4G Mobility supports 5G NSA to 4G (eNB) handover as described in spec 3GPP TS 37.340 / section 10.8 Master Node to eNB/gNB Change. You define the S1-MME interface with the NAS tab, F1 with F1-AP, X2-ENB with X2-AP and Target eNodeB Control Node, Target eNodeB User Node, (User and Control) Nodes. SUT is gNB CU . Additional details in 5GNSA-4G Mobility.
- In a SMF Nodal Intra-AMF Mobility supports Xn handover, you define the N1 interface with the NAS-5G-Sm, NAS-5G-MM tabs, and Target gNodeB User Node, (User Node).
- In a UPF Nodal Mobility supports Xn handover, you define the N1 interface with the NAS-5G-Sm, NAS-5G-MM tabs, and Target gNodeB User Node (User Node).

IMPORTANT: The addresses used for handoffs must be unique within the test case.

In some test cases, an additional tab is added to define the control protocol for the handoff node or SUT.
- In an Inter-SGSN test, you can define the GTP version, user addresses, RAI attributes, and QOS profile used for the handoffs on the Handoff GTP tab.
- In an Inter-PDSN or Intra-PDSN test, you can define the RP interface with the Handoff RP tab.
- In a CDMA/WiFi Convergence Inter-Technology Mobility test, you can define the RP interface with the RP and PPP tabs.
- In a UMTS Mobility test, you can define the Iu-PS interface with the Mobility IuPS or define the Gb interface with Mobility Gb tab.
Select the Test Configuration tab and click the Settings... button. A dialog window opens and displays the test activity parameters.
Mobility Delay Time... determines when a handoff is performed.
You can override the Retry behavior defined in the test case with Session Start Retries...
Use the When All Sessions Started and When Session Started... radio buttons to determine when handoffs will begin.
- If you select When All Sessions Started, you can define the Mobility Rate and vary the rate with a distribution model. After all of the MN sessions have been started, the test waits for the Mobility Delay Time and then begins to hand off sessions at the Mobility Rate.
- With When Session Started, the test starts the MN session, waits for the Mobility Delay Time and then hands the session off. The Activation Rate is the effective mobility rate in this case.
Use the Single Handoff and Continuous Handoff... radio buttons to define the volume of handoffs.
In an End-to-End Mobile IP Inter-PDSN test, select the SUT #2 FA... that will receive the handoffs.
The following options are available depending on the test case:
- In CDMA2000 test cases, you can choose Fast Handoff Support... or to Activate Dormant Session on Handoff...
- In the UMTS test case, you can choose Perform Serving RNS Relocation Procedure... or Perform PS Handover Procedure... depending on the type of interface being tested.
Click OK to close the test activity window.
Click OK to apply the test case settings. If you have entered a value outside of the allowable range you will receive an error.