2.10) Workflow Procedure for Ericsson Experiment

This section explains the workflow procedure and the steps for an Experimenter to follow. 

Before starting an experiment, the experimenter is required to read Section 1.4..4 and Section 4.1.6 and get familiarized on the Ericsson Network and the Testbed setup. Please review the 5G RAN preset configurations and the Portable node with the pre-programmed parameters for logging. 

Step 1: Follow the procedure as outlined in Section 1.8. for non-Canonical experiment , i.e., Register and Log into the AERPAW web portal, then create or join a project. Then, continue to your Project page to create an experiment. 

Step 2: In the Create Experiment page, fill out AERPAW Experiment Information Request Form described in Step 2, then follow to Step 3a in that page. 

In the AERPAW Experiment Information Request form, try to provide as much details as possible about the experiment. The experimenter is expected to provide at least the following details:

a) Short description of the experiment, objective and expected outcome.

b) The "HW Resources" required for the experiment.  

Default list of Resources use are:

• Ericsson 5G Network

• Quectel modem SPN as APRN

• CC1 as AFN (if traffic or any application is used by the experiment)

• UAV or UGV

c) If the experiment uses a traffic, specify the type of traffic or the application used for the traffic.

For example, 

Traffic type: No Traffic, TCP, UDP, Ping etc.

Application: iPerf, Ping

d) Vehicle plan file type - New or Default, i.e., will the experiment use one of the default plan files provided, or will create a new one?

e)  What are the expected output log files from the experiment?

Possible log files are:

• Radio log files 

  • Serving cell RF logs

  • Serving cell PHY logs

  • Neighboring cell logs

• Traffic logs files

  • Depending on the type of traffic / apps used

• Vehicle log files

Step 3: After submitting the Experiment Request form, the AERPAW OPs will contact you through an email. So, logout and wait for the email from AERPAW OPs. 

Step 4. After reviewing the experiment request, a meeting will be setup by the AERPAW Ops to discuss the details of the experiment. At this stage the following things maybe required from the Experimenter, say the vehicle plan file, or Application software/script, and that will be decided in the meeting.

• Mission Plan file:  The experimenter can use one of the preplanned mission files available in Section 3.1.2.2, or can design their own mission plan file following the procedure described in Section 3.1.2, and submit it by sending it to AERPAW Ops email id aerpaw-operations@ncsu.edu.

• Traffic application: Sample experiments use iPerf TCP downlink and Ping traffics. The Experimenter can use one of these or can design their own application layer script.