docs/testing/user/userguide/nsb/tc_epc_network_service_request_landslide.rst

   1 .. This work is licensed under a Creative Commons Attribution 4.0 International
   2 .. License.
   3 .. http://creativecommons.org/licenses/by/4.0
   4 .. (c) OPNFV, 2018 Intel Corporation.
   5
   6 ****************************************************************
   7 Yardstick Test Case Description: NSB EPC NETWORK SERVICE REQUEST
   8 ****************************************************************
   9
  10 +-----------------------------------------------------------------------------+
  11 |NSB EPC network service request test case                                    |
  12 |                                                                             |
  13 +--------------+--------------------------------------------------------------+
  14 |test case id  | tc_epc_network_service_request_landslide                     |
  15 |              |                                                              |
  16 |              | * initiator: service request initiator side could be UE (ue) |
  17 |              |   or Network (network).                                      |
  18 |              |                                                              |
  19 +--------------+--------------------------------------------------------------+
  20 |metric        | All metrics provided by Spirent Landslide traffic generator  |
  21 |              |                                                              |
  22 +--------------+--------------------------------------------------------------+
  23 |test purpose  | The Spirent Landslide product provides one box solution which|
  24 |              | allows to fully emulate all EPC network nodes including      |
  25 |              | mobile users, network host and generate control and data     |
  26 |              | plane traffic.                                               |
  27 |              |                                                              |
  28 |              | This test covers case of network initiated service request & |
  29 |              | allows to check processing capabilities of EPC handling high |
  30 |              | amount of continuous Downlink Data Notification messages from|
  31 |              | network to UEs which are in Idle state.                      |
  32 |              |                                                              |
  33 |              | It's easy to replace emulated node or multiple nodes in test |
  34 |              | topology with real node or corresponding vEPC VNF as DUT and |
  35 |              | check it's processing capabilities under specific test case  |
  36 |              | load conditions.                                             |
  37 |              |                                                              |
  38 +--------------+--------------------------------------------------------------+
  39 |configuration | The EPC network service request test cases are listed below: |
  40 |              |                                                              |
  41 |              | * tc_epc_network_service_request_landslide.yaml              |
  42 |              |                                                              |
  43 |              | Test duration:                                               |
  44 |              |                                                              |
  45 |              | * is set as 60sec (specified in test session profile);       |
  46 |              |                                                              |
  47 |              | Traffic type:                                                |
  48 |              |                                                              |
  49 |              | * UDP;                                                       |
  50 |              |                                                              |
  51 |              | Packet sizes:                                                |
  52 |              |                                                              |
  53 |              | * 512 bytes;                                                 |
  54 |              |                                                              |
  55 |              | Traffic transaction rate:                                    |
  56 |              |                                                              |
  57 |              | * 0.1 trans/s.;                                              |
  58 |              |                                                              |
  59 |              | Number of mobile subscribers:                                |
  60 |              |                                                              |
  61 |              | * 20000;                                                     |
  62 |              |                                                              |
  63 |              | Number of default bearers per subscriber:                    |
  64 |              |                                                              |
  65 |              | * 1;                                                         |
  66 |              |                                                              |
  67 |              | Idle entry time (timeout after which UE goes to Idle state): |
  68 |              |                                                              |
  69 |              | * 5s;                                                        |
  70 |              |                                                              |
  71 |              | Traffic start delay:                                         |
  72 |              |                                                              |
  73 |              | * 1000ms.                                                    |
  74 |              |                                                              |
  75 |              | The above fields and values are the main options used for the|
  76 |              | test case. Other configurable options could be found in test |
  77 |              | session profile yaml file. All these options have default    |
  78 |              | values which can be overwritten in test case file.           |
  79 |              |                                                              |
  80 +--------------+--------------------------------------------------------------+
  81 |test tool     | Spirent Landslide                                            |
  82 |              |                                                              |
  83 |              | The Spirent Landslide is a tool for functional & performance |
  84 |              | testing of different types of mobile networks. It emulates   |
  85 |              | real-world control and data traffic of mobile subscribers    |
  86 |              | moving through virtualized EPC network.                      |
  87 |              | Detailed description of Spirent Landslide product could be   |
  88 |              | found here: https://www.spirent.com/Products/Landslide       |
  89 |              |                                                              |
  90 +--------------+--------------------------------------------------------------+
  91 |applicability | This EPC NETWORK SERVICE REQUEST test case can be configured |
  92 |              | with different:                                              |
  93 |              |                                                              |
  94 |              |  * packet sizes;                                             |
  95 |              |  * traffic transaction rate;                                 |
  96 |              |  * number of subscribers sessions;                           |
  97 |              |  * number of default bearers per subscriber;                 |
  98 |              |  * subscribers connection rate;                              |
  99 |              |  * subscribers disconnection rate;                           |
 100 |              |  * timeout after which UE goes to Idle state;                |
 101 |              |  * Traffic start delay;                                      |
 102 |              |                                                              |
 103 |              | Default values exist.                                        |
 104 |              |                                                              |
 105 +--------------+--------------------------------------------------------------+
 106 |references    | ETSI-NFV-TST001                                              |
 107 |              |                                                              |
 108 |              | 3GPP TS 32.455                                               |
 109 |              |                                                              |
 110 +--------------+--------------------------------------------------------------+
 111 | pre-test     | * All Spirent Landslide dependencies are installed (detailed |
 112 | conditions   |   installation steps are described in Chapter 13-            |
 113 |              |   nsb-installation.rst and 14-nsb-operation.rst file for NSB |
 114 |              |   Spirent Landslide vEPC tests;                              |
 115 |              |                                                              |
 116 |              | * The pod.yaml file contains all necessary information       |
 117 |              |   (TAS VM IP address, NICs, emulated SUTs and Test Nodes     |
 118 |              |   parameters (names, types, ip addresses, etc.).             |
 119 |              |                                                              |
 120 +--------------+--------------------------------------------------------------+
 121 |test sequence | description and expected result                              |
 122 |              |                                                              |
 123 +--------------+--------------------------------------------------------------+
 124 |step 1        | Spirent Landslide components are running on the hosts        |
 125 |              | specified in the pod file.                                   |
 126 |              |                                                              |
 127 +--------------+--------------------------------------------------------------+
 128 |step 2        | Yardstick is connected with Spirent Landslide Test           |
 129 |              | Administration Server (TAS) by TCL and REST API. The test    |
 130 |              | will resolve the topology and instantiate all emulated EPC   |
 131 |              | network nodes.                                               |
 132 |              |                                                              |
 133 +--------------+--------------------------------------------------------------+
 134 |step 3        | Test scenarios run, which performs the following steps:      |
 135 |              |                                                              |
 136 |              | * Start emulated EPC network nodes;                          |
 137 |              | * Establish subscribers connections to EPC network (default  |
 138 |              |   bearers);                                                  |
 139 |              | * Switch UE to Idle state after specified in test case       |
 140 |              |   timeout;                                                   |
 141 |              | * Send Downlink Data Notification from network to UE, that   |
 142 |              |   will return UE to active state. This process is continuous |
 143 |              |   and during whole test run UEs will be going to Idle state  |
 144 |              |   and will be switched back to active state after Downlink   |
 145 |              |   Data Notification was received;                            |
 146 |              | * Disconnect subscribers at the end of the test.             |
 147 |              |                                                              |
 148 +--------------+--------------------------------------------------------------+
 149 |step 4        | During test run, all the metrics provided by Spirent         |
 150 |              | Landslide are stored in the yardstick dispatcher.            |
 151 |              |                                                              |
 152 +--------------+--------------------------------------------------------------+
 153 |test verdict  | The test case will create the test session in Spirent        |
 154 |              | Landslide with the test case parameters and store the        |
 155 |              | results in the database for benchmarking purposes. The aim   |
 156 |              | is only to collect all the metrics that are provided by      |
 157 |              | Spirent Landslide product for each test specific scenario.   |
 158 |              |                                                              |
 159 +--------------+--------------------------------------------------------------+