From 373b3bf8807e69d1ebc8b9c15c5581b77003e34d Mon Sep 17 00:00:00 2001 From: Morgan Richomme Date: Fri, 21 Aug 2015 15:50:45 +0200 Subject: first upload for traffic profiles management JIRA: FUNCTEST-33 Change-Id: Ib7b9abd05d1fb880fc5aeddce24dff273c76ced7 Signed-off-by: Morgan Richomme --- commons/ims/readme.rst | 0 commons/mobile/readme.rst | 0 commons/traffic-profile-guidelines.rst | 60 ++++++++++++++++++++++++++++++++++ 3 files changed, 60 insertions(+) create mode 100644 commons/ims/readme.rst create mode 100644 commons/mobile/readme.rst create mode 100644 commons/traffic-profile-guidelines.rst (limited to 'commons') diff --git a/commons/ims/readme.rst b/commons/ims/readme.rst new file mode 100644 index 000000000..e69de29bb diff --git a/commons/mobile/readme.rst b/commons/mobile/readme.rst new file mode 100644 index 000000000..e69de29bb diff --git a/commons/traffic-profile-guidelines.rst b/commons/traffic-profile-guidelines.rst new file mode 100644 index 000000000..ffef50fe3 --- /dev/null +++ b/commons/traffic-profile-guidelines.rst @@ -0,0 +1,60 @@ +================================ +OPNFV traffic profile guidelines +================================ + +.. contents:: + +.. _introduction: + +------------ +Introduction +------------ + +In order to have consistent profiles for testing, it has been suggested to define and store traffic profiles based on operator representative scenario. + +These reference profiles may be used by any test projects, unitary, functional or performance tests. It is possible to adapt them to specific testcases. It is recommended to use them in order to avoid getting as many profiles as tests. It should be helpful to compare the results of test scenario. + +.. _howto: + +------------------------- +How to use these profiles +------------------------- + +The directory of the traffic profiles may be described as follow:: + + ├── commons + ├── ims + │ └── readme.rst + ├── mobile + │ └── readme.rst + └── traffic-profile-guidelines.rst + +the readme.rst details the profile. + + +.. _overview: + +------------------------ +Traffic profile overview +------------------------ + +The current profiles are available: + * Mobile traffic + * IMS residential traffic + * ... + +Mobile traffic +============== + +IMS residential traffic +======================= + + + + + +.. _reference: + +--------- +reference +--------- -- cgit 1.2.3-korg From f108ea3ed6501aca2583026056bc98cc9a2a0fbd Mon Sep 17 00:00:00 2001 From: Morgan Richomme Date: Mon, 24 Aug 2015 09:34:55 +0200 Subject: README for vIMS testcase Note that vIMS shall be also documented in the global functest rst guideline. JIRA: FUNCTEST-38 Change-Id: Ifebcbcdad5231283afd8ad721daa60fa13ced15e Signed-off-by: Morgan Richomme --- commons/traffic-profile-guidelines.rst | 10 +++++++--- testcases/vIMS/vIMS.md | 3 +++ 2 files changed, 10 insertions(+), 3 deletions(-) create mode 100644 testcases/vIMS/vIMS.md (limited to 'commons') diff --git a/commons/traffic-profile-guidelines.rst b/commons/traffic-profile-guidelines.rst index ffef50fe3..0b965b156 100644 --- a/commons/traffic-profile-guidelines.rst +++ b/commons/traffic-profile-guidelines.rst @@ -10,9 +10,13 @@ OPNFV traffic profile guidelines Introduction ------------ -In order to have consistent profiles for testing, it has been suggested to define and store traffic profiles based on operator representative scenario. +In order to have consistent testing profiles, it has been suggested to define and store traffic profiles. +These profiles shall be based on operator representative scenario. -These reference profiles may be used by any test projects, unitary, functional or performance tests. It is possible to adapt them to specific testcases. It is recommended to use them in order to avoid getting as many profiles as tests. It should be helpful to compare the results of test scenario. +These reference profiles may be used by any test projects, unitary, functional or performance tests. +It is possible to adapt them to specific testcases. +It is recommended to use them in order to avoid getting as many profiles as tests. +It should be helpful to compare the results of test scenario. .. _howto: @@ -21,7 +25,7 @@ How to use these profiles ------------------------- The directory of the traffic profiles may be described as follow:: - + ├── commons ├── ims │ └── readme.rst diff --git a/testcases/vIMS/vIMS.md b/testcases/vIMS/vIMS.md new file mode 100644 index 000000000..68f86d9fa --- /dev/null +++ b/testcases/vIMS/vIMS.md @@ -0,0 +1,3 @@ +# vIMS README + + -- cgit 1.2.3-korg From 3f65dc2c849c8368ae6867de1075ef69dba3e656 Mon Sep 17 00:00:00 2001 From: blsaws Date: Tue, 25 Aug 2015 11:18:27 -0700 Subject: Baseline of mobility traffic profile. JIRA: FUNCTEST-33 Change-Id: Ia61b3bb883f8b91f34b94eec7b7f8a5c9d87c274 Signed-off-by: blsaws --- commons/mobile/readme.rst | 116 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 116 insertions(+) (limited to 'commons') diff --git a/commons/mobile/readme.rst b/commons/mobile/readme.rst index e69de29bb..07c872503 100644 --- a/commons/mobile/readme.rst +++ b/commons/mobile/readme.rst @@ -0,0 +1,116 @@ +Mobility Traffic Profiles for OPNFV +=================================== + +Mobility User-Plane ++++++++++++++++++++ + +The following tables describe per-session average (in a range) for user-plane traffic related to classes of applications. + +Downlink Mobility User-Plane +---------------------------- + +.. list-table:: Downlink Mobility User-Plane + :widths: 25 25 25 25 + :header-rows: 1 + + * - Service/protocol + - Downlink Packet Size (bytes) + - Downlink Flow Size (KB) + - Downlink per-flow Throughput (Kbps) + + * - Browsing + Apps + - 1,220 - 1,260 + - 40 - 55 + - 130 - 253 + + * - HTTPS traffic + - 1,050 - 1,085 + - 32 - 40 + - 107 - 124 + + * - Video Streaming + - 1,360 - 1,390 + - 545 - 650 + - 690 - 790 + + * - VoLTE bearer (media, excluding signaling) + - 84 – 102 + - 116 - 142 + - 18 - 24 + + +Uplink Mobility User-Plane +-------------------------- +.. list-table:: Uplink Mobility User-Plane + :widths: 25 25 25 25 + :header-rows: 1 + + * - Service/protocol + - Uplink Packet Size (bytes) + - Uplink Flow Size (KB) + - Uplink per-flow Throughput (Kbps) + + * - Browsing + Apps + - 90 – 120 + - 3 – 10 + - 6 – 18 + + * - HTTPS traffic + - 140 – 200 + - 5 – 12 + - 8 – 15 + + * - Video Streaming + - 50 – 110 + - 10 – 20 + - 12 - 20 + + * - VoLTE bearer (media, excluding signaling) + - 84 – 102 + - 112 - 135 + - 18 - 24 + + +Mobility User-Plane Traffic Distribution +---------------------------------------- +.. list-table:: Mobility User-Plane Traffic Distribution + :widths: 33 33 33 + :header-rows: 1 + + * - Service/protocol + - Downlink + - Uplink + + * - HTTP + - 40 - 70% (60 – 40 split between ‘browsing + apps’ and ‘streaming’) + - 30 - 50% (55 – 45 split between ‘browsing + apps’ and ‘streaming’) + + * - HTTPS + - 25 - 50% + - 40 - 60% + + * - Email + - 1% + - 3% + + * - P2P + - 0.1% + - 0.5% + + * - VoLTE + - 0-5% + - 5-30% + + * - Others + - 4% + - 8% + +Mobility Control-Plane +++++++++++++++++++++++ + +This section will provide average per-session mobility control-plane traffic for various protocols associated with applications. + +Mobility Sessions per Hour +++++++++++++++++++++++++++ + +This section will provide per-hour average and min-max ranges for mobility application sessions. -- cgit 1.2.3-korg