... | ... | @@ -250,6 +250,15 @@ The **`desc`** tag provides a description of the test-case. No syntax required. |
|
|
|
|
|
The **`Build_eNB_args`** are usual build_oai options.
|
|
|
|
|
|
**Behavior:**
|
|
|
|
|
|
- Connect to the remote server that will be the eNB
|
|
|
- Go to the specified working directory
|
|
|
- Git clone or fetch the specified repository
|
|
|
- Checkout to the specified commit ID
|
|
|
- If it is a merge-request and it is allowed, merge with `develop` branch
|
|
|
- Build with the specified options
|
|
|
|
|
|
## 5.3. Initialize_eNB class ##
|
|
|
|
|
|
```xml
|
... | ... | @@ -266,6 +275,15 @@ The **`desc`** tag provides a description of the test-case. No syntax required. |
|
|
|
|
|
The **`Initialize_eNB_args`** are usual lte-softmodem options. Note that the path to configuration file is relative to the root of the GIT repository. The python script will append the absolute path at runtime.
|
|
|
|
|
|
**Behavior:**
|
|
|
|
|
|
- Connect to the remote server that will be the eNB
|
|
|
- Go to the specified working directory
|
|
|
- Copy the configuration file and adapt it with the proper IP address (eNB and EPC)
|
|
|
- Start the eNB lte-softmodem executable with this modified configuration file
|
|
|
- Wait until the `got sync` message appears in the log file
|
|
|
- If it does not appear, it may be because of a bufferization in the standard output
|
|
|
|
|
|
## 5.4. TerminateeNB class ##
|
|
|
|
|
|
```xml
|
... | ... | @@ -279,6 +297,11 @@ The **`id`** tag SHALL be unique. But this test-case can be used several times i |
|
|
|
|
|
The **`desc`** tag provides a description of the test-case. No syntax required.
|
|
|
|
|
|
**Behavior:**
|
|
|
|
|
|
- Connect to the remote server that will be the eNB
|
|
|
- Kill all lte-softmodem processes
|
|
|
|
|
|
## 5.5. Initialize_HSS class ##
|
|
|
|
|
|
```xml
|
... | ... | @@ -292,6 +315,11 @@ The **`id`** tag SHALL be unique. |
|
|
|
|
|
The **`desc`** tag provides a description of the test-case. No syntax required.
|
|
|
|
|
|
**Behavior:**
|
|
|
|
|
|
- Connect to the remote server that will be the EPC
|
|
|
- Depending on EPC type, start the HSS
|
|
|
|
|
|
## 5.6. TerminateHSS class ##
|
|
|
|
|
|
```xml
|
... | ... | @@ -305,6 +333,11 @@ The **`id`** tag SHALL be unique. |
|
|
|
|
|
The **`desc`** tag provides a description of the test-case. No syntax required.
|
|
|
|
|
|
**Behavior:**
|
|
|
|
|
|
- Connect to the remote server that will be the EPC
|
|
|
- Depending on EPC type, kill all the proper HSS processes
|
|
|
|
|
|
## 5.7. Initialize_MME class ##
|
|
|
|
|
|
```xml
|
... | ... | @@ -318,6 +351,11 @@ The **`id`** tag SHALL be unique. |
|
|
|
|
|
The **`desc`** tag provides a description of the test-case. No syntax required.
|
|
|
|
|
|
**Behavior:**
|
|
|
|
|
|
- Connect to the remote server that will be the EPC
|
|
|
- Depending on EPC type, start the MME
|
|
|
|
|
|
## 5.8. TerminateMME class ##
|
|
|
|
|
|
```xml
|
... | ... | @@ -331,6 +369,11 @@ The **`id`** tag SHALL be unique. |
|
|
|
|
|
The **`desc`** tag provides a description of the test-case. No syntax required.
|
|
|
|
|
|
**Behavior:**
|
|
|
|
|
|
- Connect to the remote server that will be the EPC
|
|
|
- Depending on EPC type, kill all the proper MME processes
|
|
|
|
|
|
## 5.9. Initialize_SPGW class ##
|
|
|
|
|
|
```xml
|
... | ... | @@ -344,6 +387,11 @@ The **`id`** tag SHALL be unique. |
|
|
|
|
|
The **`desc`** tag provides a description of the test-case. No syntax required.
|
|
|
|
|
|
**Behavior:**
|
|
|
|
|
|
- Connect to the remote server that will be the EPC
|
|
|
- Depending on EPC type, start the SPGW
|
|
|
|
|
|
## 5.10. TerminateSPGW class ##
|
|
|
|
|
|
```xml
|
... | ... | @@ -357,6 +405,11 @@ The **`id`** tag SHALL be unique. |
|
|
|
|
|
The **`desc`** tag provides a description of the test-case. No syntax required.
|
|
|
|
|
|
**Behavior:**
|
|
|
|
|
|
- Connect to the remote server that will be the EPC
|
|
|
- Depending on EPC type, kill all the proper SPGW processes
|
|
|
|
|
|
## 5.11. Initialize_UE class ##
|
|
|
|
|
|
```xml
|
... | ... | @@ -370,6 +423,15 @@ The **`id`** tag SHALL be unique. But this test-case can be used several times i |
|
|
|
|
|
The **`desc`** tag provides a description of the test-case. No syntax required.
|
|
|
|
|
|
**Behavior:**
|
|
|
|
|
|
- Connect to the remote server that is the ADB server
|
|
|
- List all the connected UE devices
|
|
|
- Loop on the UE devices
|
|
|
- Connect to the remote server that is the ADB server
|
|
|
- Connect to the UE through ADB shell
|
|
|
- Put the UE in airplane mode ON
|
|
|
|
|
|
## 5.12. Terminate_UE class ##
|
|
|
|
|
|
```xml
|
... | ... | @@ -383,6 +445,16 @@ The **`id`** tag SHALL be unique. But this test-case can be used several times i |
|
|
|
|
|
The **`desc`** tag provides a description of the test-case. No syntax required.
|
|
|
|
|
|
**Behavior:**
|
|
|
|
|
|
- Connect to the remote server that is the ADB server
|
|
|
- List all the connected UE devices
|
|
|
- Loop on the UE devices
|
|
|
- Connect to the remote server that is the ADB server
|
|
|
- Connect to the UE through ADB shell
|
|
|
- Put the UE in airplane mode ON
|
|
|
- Kill any residual iperf processes on the UE
|
|
|
|
|
|
## 5.13. Attach_UE class ##
|
|
|
|
|
|
```xml
|
... | ... | @@ -396,6 +468,15 @@ The **`id`** tag SHALL be unique. But this test-case can be used several times i |
|
|
|
|
|
The **`desc`** tag provides a description of the test-case. No syntax required.
|
|
|
|
|
|
**Behavior:**
|
|
|
|
|
|
- Connect to the remote server that is the ADB server
|
|
|
- List all the connected UE devices
|
|
|
- Loop on the UE devices
|
|
|
- Connect to the remote server that is the ADB server
|
|
|
- Connect to the UE through ADB shell
|
|
|
- Put the UE in airplane mode OFF
|
|
|
|
|
|
## 5.14. Detach_UE class ##
|
|
|
|
|
|
```xml
|
... | ... | @@ -409,6 +490,15 @@ The **`id`** tag SHALL be unique. But this test-case can be used several times i |
|
|
|
|
|
The **`desc`** tag provides a description of the test-case. No syntax required.
|
|
|
|
|
|
**Behavior:**
|
|
|
|
|
|
- Connect to the remote server that is the ADB server
|
|
|
- List all the connected UE devices
|
|
|
- Loop on the UE devices
|
|
|
- Connect to the remote server that is the ADB server
|
|
|
- Connect to the UE through ADB shell
|
|
|
- Put the UE in airplane mode ON
|
|
|
|
|
|
## 5.15. Reboot_UE class ##
|
|
|
|
|
|
```xml
|
... | ... | @@ -422,6 +512,15 @@ The **`id`** tag SHALL be unique. But this test-case can be used several times i |
|
|
|
|
|
The **`desc`** tag provides a description of the test-case. No syntax required.
|
|
|
|
|
|
**Behavior:**
|
|
|
|
|
|
- Connect to the remote server that is the ADB server
|
|
|
- List all the connected UE devices
|
|
|
- Loop on the UE devices
|
|
|
- Connect to the remote server that is the ADB server
|
|
|
- Connect to the UE through ADB shell
|
|
|
- Reboot the UE
|
|
|
|
|
|
## 5.16. Ping class ##
|
|
|
|
|
|
```xml
|
... | ... | @@ -441,6 +540,17 @@ The **`ping_args`** tag provides typical linux ping options. |
|
|
|
|
|
The **`ping_packetloss_threshold`** tag provides a percentage threshold on lost ping packet. Above that number, the test-case will be considered a failure and the python will not execute the following test-cases in the list.
|
|
|
|
|
|
**Behavior:**
|
|
|
|
|
|
- Connect to the remote server that is the ADB server
|
|
|
- List all the connected UE devices
|
|
|
- Retrieve each IP address (should have been allocated by EPC)
|
|
|
- Loop on the UE devices
|
|
|
- Connect to the remote server that is the EPC server
|
|
|
- Ping the UE device with its IP address and the specified options
|
|
|
- Perform statistics and display them
|
|
|
- If the packet loss is superior to the specified threshold, the test-case is deemed a failure
|
|
|
|
|
|
## 5.17. Iperf class ##
|
|
|
|
|
|
```xml
|
... | ... | @@ -469,3 +579,18 @@ The **`iperf_profile`** tag provides a profile on bandwidth requirement per UE d |
|
|
- 2% of the requested bandwidth on (N-1) UE devices
|
|
|
- The rest (= 100 - 2*(N-1)) on the last device
|
|
|
|
|
|
**Behavior:**
|
|
|
|
|
|
- Connect to the remote server that is the ADB server
|
|
|
- List all the connected UE devices
|
|
|
- Retrieve each IP address (should have been allocated by EPC)
|
|
|
- Loop on the UE devices
|
|
|
- Connect to the remote server that is the ADB server
|
|
|
- Connect to the UE through ADB shell
|
|
|
- Check which version of iperf is installed
|
|
|
- Check if it is UL or DL iperf test
|
|
|
- Start iperf server on either the UE or the EPC remote server
|
|
|
- Compute the requested bandwidth based on device ID and profile option
|
|
|
- Start iperf client on the opposite side of iperf server
|
|
|
- Analyze report and display statistics
|
|
|
- If the packet loss is superior to the specified threshold, the test-case is deemed a failure |