1 .. This work is licensed under a Creative Commons Attribution 4.0 International
3 .. http://creativecommons.org/licenses/by/4.0
4 .. (c) OPNFV, 2018 Intel Corporation.
6 ***********************************************************
7 Yardstick Test Case Description: NSB EPC UE SERVICE REQUEST
8 ***********************************************************
10 +-----------------------------------------------------------------------------+
11 |NSB EPC UE service request test case |
13 +--------------+--------------------------------------------------------------+
14 |test case id | tc_epc_{initiator}_service_request_landslide |
16 | | * initiator: service request initiator side could be UE (ue) |
17 | | or Network (nw). |
19 +--------------+--------------------------------------------------------------+
20 |metric | All metrics provided by Spirent Landslide traffic generator |
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 |
28 | | This test allows to check processing capabilities of EPC |
29 | | under high user connections rate and traffic load for case |
30 | | when UEs initiates service request (UE initiates bearer |
31 | | modification request to provide dedicated bearer for new |
32 | | type of traffic) |
34 | | It's easy to replace emulated node or multiple nodes in test |
35 | | topology with real node or corresponding vEPC VNF as DUT and |
36 | | check it's processing capabilities under specific test case |
37 | | load conditions. |
39 +--------------+--------------------------------------------------------------+
40 |configuration | The EPC ue service request test cases are listed below: |
42 | | * tc_epc_ue_service_request_landslide.yaml |
46 | | * is set as 60sec (specified in test session profile); |
56 | | Traffic transaction rate: |
60 | | Number of mobile subscribers: |
64 | | Number of default bearers per subscriber: |
68 | | Number of dedicated bearers per default bearer: |
72 | | TFT settings for dedicated bearers: |
74 | | * TFT configured to filter TCP traffic (Protocol ID 6) |
76 | | Modified TFT settings: |
78 | | * Create new TFT to filter UDP traffic (Protocol ID 17) from |
79 | | 2002 local port and 2003 remote port; |
81 | | Modified QoS settings: |
83 | | * Set QCI 5 for dedicated bearers; |
85 | | The above fields and values are the main options used for the|
86 | | test case. Other configurable options could be found in test |
87 | | session profile yaml file. All these options have default |
88 | | values which can be overwritten in test case file. |
90 +--------------+--------------------------------------------------------------+
91 |test tool | Spirent Landslide |
93 | | The Spirent Landslide is a tool for functional & performance |
94 | | testing of different types of mobile networks. It emulates |
95 | | real-world control and data traffic of mobile subscribers |
96 | | moving through virtualized EPC network. |
97 | | Detailed description of Spirent Landslide product could be |
98 | | found here: https://www.spirent.com/Products/Landslide |
100 +--------------+--------------------------------------------------------------+
101 |applicability | This EPC UE SERVICE REQUEST test case can be configured with |
104 | | * packet sizes; |
105 | | * traffic transaction rate; |
106 | | * number of subscribers sessions; |
107 | | * number of default bearers per subscriber; |
108 | | * number of dedicated bearers per default; |
109 | | * subscribers connection rate; |
110 | | * subscribers disconnection rate; |
111 | | * dedicated bearers activation timeout; |
112 | | * DMF (traffic profile); |
113 | | * enable/disable Fireball DMF threading model that provides |
114 | | optimized performance; |
115 | | * Starting TFT settings for dedicated bearers; |
116 | | * Modified TFT settings for dedicated bearers; |
117 | | * Modified QoS settings for dedicated bearers; |
119 | | Default values exist. |
121 +--------------+--------------------------------------------------------------+
122 |references | ETSI-NFV-TST001 |
126 +--------------+--------------------------------------------------------------+
127 | pre-test | * All Spirent Landslide dependencies are installed (detailed |
128 | conditions | installation steps are described in Chapter 13- |
129 | | nsb-installation.rst and 14-nsb-operation.rst file for NSB |
130 | | Spirent Landslide vEPC tests; |
132 | | * The pod.yaml file contains all necessary information |
133 | | (TAS VM IP address, NICs, emulated SUTs and Test Nodes |
134 | | parameters (names, types, ip addresses, etc.). |
136 +--------------+--------------------------------------------------------------+
137 |test sequence | description and expected result |
139 +--------------+--------------------------------------------------------------+
140 |step 1 | Spirent Landslide components are running on the hosts |
141 | | specified in the pod file. |
143 +--------------+--------------------------------------------------------------+
144 |step 2 | Yardstick is connected with Spirent Landslide Test |
145 | | Administration Server (TAS) by TCL and REST API. The test |
146 | | will resolve the topology and instantiate all emulated EPC |
149 +--------------+--------------------------------------------------------------+
150 |step 3 | Test scenarios run, which performs the following steps: |
152 | | * Start emulated EPC network nodes; |
153 | | * Establish subscribers connections to EPC network (default |
155 | | * Establish the number of dedicated bearer as specified in |
156 | | the test case as per default bearer for each subscriber; |
157 | | * start run users traffic through EPC network nodes; |
158 | | * During traffic is running, send bearer modification request|
159 | | after specified in test case timeout; |
160 | | * Disconnect dedicated bearers; |
161 | | * Disconnect subscribers at the end of the test. |
163 +--------------+--------------------------------------------------------------+
164 |step 4 | During test run, all the metrics provided by Spirent |
165 | | Landslide are stored in the yardstick dispatcher. |
167 +--------------+--------------------------------------------------------------+
168 |test verdict | The test case will create the test session in Spirent |
169 | | Landslide with the test case parameters and store the |
170 | | results in the database for benchmarking purposes. The aim |
171 | | is only to collect all the metrics that are provided by |
172 | | Spirent Landslide product for each test specific scenario. |
174 +--------------+--------------------------------------------------------------+