docs/testing/user/userguide/nsb/tc_epc_dedicated_bearer_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 DEDICATED BEARER
   8 *********************************************************
   9
  10 +-----------------------------------------------------------------------------+
  11 |NSB EPC dedicated bearer test case                                           |
  12 |                                                                             |
  13 +--------------+--------------------------------------------------------------+
  14 |test case id  | tc_epc_{initiator}_dedicated_bearer_landslide                |
  15 |              |                                                              |
  16 |              | * initiator: dedicated bearer creation initiator side could  |
  17 |              |   be UE (ue) 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 allows to check processing capability under        |
  29 |              | different levels of load (number of subscriber, generated    |
  30 |              | traffic throughput, etc.) for case when default and dedicated|
  31 |              | bearers are creating and using for traffic transferring.     |
  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 dedicated bearer test cases are listed below:        |
  40 |              |                                                              |
  41 |              | * tc_epc_ue_dedicated_bearer_create_landslide.yaml           |
  42 |              | * tc_epc_network_dedicated_bearer_create_landslide.yaml      |
  43 |              |                                                              |
  44 |              | Test duration:                                               |
  45 |              |                                                              |
  46 |              | * is set as 60sec (specified in test session profile);       |
  47 |              |                                                              |
  48 |              | Traffic type:                                                |
  49 |              |                                                              |
  50 |              | * UDP;                                                       |
  51 |              |                                                              |
  52 |              | Packet sizes:                                                |
  53 |              |                                                              |
  54 |              | * 512 bytes;                                                 |
  55 |              |                                                              |
  56 |              | Traffic transaction rate:                                    |
  57 |              |                                                              |
  58 |              | * 5 trans/s.;                                                |
  59 |              |                                                              |
  60 |              | Number of mobile subscribers:                                |
  61 |              |                                                              |
  62 |              | * 20000;                                                     |
  63 |              |                                                              |
  64 |              | Number of default bearers per subscriber:                    |
  65 |              |                                                              |
  66 |              | * 1;                                                         |
  67 |              |                                                              |
  68 |              | Number of dedicated bearers per default bearer:              |
  69 |              |                                                              |
  70 |              | * 1.                                                         |
  71 |              |                                                              |
  72 |              | The above fields and values are the main options used for the|
  73 |              | test case. Other configurable options could be found in test |
  74 |              | session profile yaml file. All these options have default    |
  75 |              | values which can be overwritten in test case file.           |
  76 |              |                                                              |
  77 +--------------+--------------------------------------------------------------+
  78 |test tool     | Spirent Landslide                                            |
  79 |              |                                                              |
  80 |              | The Spirent Landslide is a tool for functional and           |
  81 |              | performance testing of different types of mobile networks.   |
  82 |              | It emulates real-world control and data traffic of mobile    |
  83 |              | subscribers moving through virtualized EPC network.          |
  84 |              | Detailed description of Spirent Landslide product could be   |
  85 |              | found here: https://www.spirent.com/Products/Landslide       |
  86 |              |                                                              |
  87 +--------------+--------------------------------------------------------------+
  88 |applicability | This EPC DEDICATED BEARER test cases can be configured with  |
  89 |              | different:                                                   |
  90 |              |                                                              |
  91 |              |  * packet sizes;                                             |
  92 |              |  * traffic transaction rate;                                 |
  93 |              |  * number of subscribers sessions;                           |
  94 |              |  * number of default bearers per subscriber;                 |
  95 |              |  * number of dedicated bearers per default;                  |
  96 |              |  * subscribers connection rate;                              |
  97 |              |  * subscribers disconnection rate;                           |
  98 |              |  * dedicated bearers activation timeout;                     |
  99 |              |  * DMF (traffic profile);                                    |
 100 |              |  * enable/disable Fireball DMF threading model that provides |
 101 |              |    optimized performance;                                    |
 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 need to be installed.   |
 112 | conditions   |   The steps are described in NSB installation chapter for the|
 113 |              |   Spirent Landslide vEPC tests;                              |
 114 |              |                                                              |
 115 |              | * The pod.yaml file contains all necessary information (TAS  |
 116 |              |   VM IP address, NICs, emulated SUTs and Test Nodes          |
 117 |              |   parameters (names, types, ip addresses, etc.).             |
 118 |              |                                                              |
 119 +--------------+--------------------------------------------------------------+
 120 |test sequence | description and expected result                              |
 121 |              |                                                              |
 122 +--------------+--------------------------------------------------------------+
 123 |step 1        | Spirent Landslide components are running on the hosts        |
 124 |              | specified in the pod file.                                   |
 125 |              |                                                              |
 126 +--------------+--------------------------------------------------------------+
 127 |step 2        | Yardstick is connected with Spirent Landslide Test           |
 128 |              | Administrator Server (TAS) by TCL and REST API. The test     |
 129 |              | will resolve the topology and instantiate all emulated EPC   |
 130 |              | network nodes.                                               |
 131 |              |                                                              |
 132 +--------------+--------------------------------------------------------------+
 133 |step 3        | Test scenarios run, which performs the following steps:      |
 134 |              |                                                              |
 135 |              | * Start the emulated EPC network nodes;                      |
 136 |              | * Establish the subscribers connections to EPC network       |
 137 |              |   (default bearers);                                         |
 138 |              | * Establish the number of dedicated bearers as per per       |
 139 |              |   default bearer for each subscriber;                        |
 140 |              | * Create the sessions and transmit traffic through EPC       |
 141 |              |   network nodes during the specified traffic duration time;  |
 142 |              | * Disconnect dedicated bearers;                              |
 143 |              | * Disconnect subscribers at the end of the test.             |
 144 |              |                                                              |
 145 +--------------+--------------------------------------------------------------+
 146 |step 4        | During test run, all the metrics provided by Spirent         |
 147 |              | Landslide are stored in the yardstick dispatcher.            |
 148 |              |                                                              |
 149 +--------------+--------------------------------------------------------------+
 150 |test verdict  | The test case will create the test session in Spirent        |
 151 |              | Landslide with the test case parameters and store the results|
 152 |              | in the database for benchmarking purposes. The aim is only   |
 153 |              | to collect all the metrics that are provided by Spirent      |
 154 |              | Landslide product for each test specific scenario.           |
 155 |              |                                                              |
 156 +--------------+--------------------------------------------------------------+