2.17.2.15. 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
|
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:
Test duration:
Traffic type:
Packet sizes:
Traffic transaction rate:
Number of mobile subscribers:
Number of default bearers per subscriber:
Number of dedicated bearers per default bearer: TFT settings for dedicated bearers:
Modified TFT settings:
Modified QoS settings:
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:
Default values exist. |
references | ETSI-NFV-TST001 3GPP TS 32.455 |
pre-test conditions |
|
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:
|
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. |