EE3: 5G Modem IPerf Traffic logging
This is one of the sample experiments for Ericsson 5G network.
Note to the Experimenters:
Ericsson experiments are Non-Canonical experiments, meaning they don't follow the Canonical experiments model with Development or Emulation mode, so the experimenters are required to follow the procedure as described in Section 2.10 for Ericsson experiments.
1) Sample Experiment
Experiment Objective: The main goal of this experiment is to measure the 5G network performance for IPerf traffic along a preplanned vehicle trajectory using a 5G user device. For this experiment a portable node with a 5G UE modem mounted on an UAV and the CC1 at the AERPAW network as IPerf client and server respectively shall be used to collect the logs along the preprogrammed vehicle trajectory. At the end of the experiment, IPerf traffic logs collected shall be provided for post-processing.
HW Resources: This experiment shall use the following resources:
Ericsson 5G NSA Network
Quectel modem SPN as APRN (for IPerf Client)
CC1 as AFN (for IPerf Server)
A SAM UAV
Traffic type: IPerf TCP Downlink
Vehicle plan file: Default plan PF6
Expected output log files:
Traffic log files: iperf_log.txt
Note: This is a sample for the type of information an Experimenter is expected to provide in the AERPAW Experiment Information Request Form.
2) Test Description
Ericsson 5G Testbed comprises of a Portable node with Quectel 5G modem connected to the Ericsson 5G base station. The experiment sets up an RF link between the eNB/gNB on the Ericsson 5G network and an UE on the Portable node. On powering on the portable node, the UE attaches to the 5G network. but then at the start of an experiment the SPN starts the Traffic script for the IPerf application and starts recording the results. The IPerf client in the portable node uses the AFN in CC1 as the IPerf server. At the end of the experiment, the recorded data shall be available in the Results folder.
The network is already preconfigured and the portable node is pre-programmed to capture default parameters, so the user is not required to do anything.
Preconfigured 5G network configuration:
The 5G network radios supports band n78 for NR carrier operating in 3.3 - 3.5 GHz frequency band and band 66 for LTE carrier operating in 1.7/2.1 GHz frequency band. The 5G NSA network is pre-configured as in Section 4.1.6.
Preparing Vehicle plan file
This experiment uses a plan file PF6 given in Section 3.1.2.2. as shown here with the following parameters -
30m altitude, 5 m/s speed, 1278 m distance, zigzag flight path.
There are more sample vehicle mission plan files available here to choose from. In that case, the experimenter specifies the mission plan file that they would like to use in the AERPAW Experiment Information Request Form.
Alternatively, the experimenter can create their own mission plan file by following the procedure given in Section 3.1.2, and submit it by sending it to AERPAW Ops email id aerpaw-operations@ncsu.edu.
Preparing Traffic file
This experiment uses a IPerf traffic. The Traffic scripts in the Portable node and the CC1 AFN run the Iperf client and server respectively.
3) Preparing and Running an Experiment on the Testbed:
As a preparation to run the experiment on the testbed, the radio script for Quectel modem, traffic script for IPerf and the vehicle plan files are copied to appropriate folder files in the portable node E-VM.
At the start of the experiment, the quectel modem gets connected to the Ericsson 5G network, and the AT&T modem is connected to AT&T network. Like a regular UE, the modem in the SPN does a cell search to find a suitable cell, and initiates the registration procedure to attach to the Ericsson 5G network. After attaching to the 5G network, the SPN (UE) camps on the serving cell. Once the SPN is ready, the experiment is started that starts the Iperf client to initiate downlink traffic from the IPerf server at the AFN, and logging the data for iperf output into a file. The experiment continues with the UAV flight as planned in the vehicle plan file, and the logging of the data continues till the end flight. In the end, the experiment is stopped, that stops logging of the data.
4) Results:
The experiment generates timestamped measurement logs under the /root/Results folder. There are two different types of data are logged: Traffic log and the vehicle flight log.
The Results folder will have these log files:
Vehicle logging
yyyy-mm-dd_hh_mm_ss_vehicle_log.txt
yyyy-mm-dd_hh_mm_ss _vehicleOut.txt
Traffic logging
iperf_log_yyyy_mm_dd_hh_mm_ss.log.txt
Sample log file output
iPerf traffic output (from iPerf_log.txt)