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