User Tools

Site Tools


transformer_-_carrier_grade_requirements_for_network_transformation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
transformer_-_carrier_grade_requirements_for_network_transformation [2015/01/22 11:53]
Youness Fettah
transformer_-_carrier_grade_requirements_for_network_transformation [2015/09/22 10:55]
Michael Wiegers
Line 1: Line 1:
 ==== OPNFV Project Proposal: Carrier Grade Requirements for Network Transformation ==== ==== OPNFV Project Proposal: Carrier Grade Requirements for Network Transformation ====
  
-Version: 0.(Jan 22, 2015)+Version: 0.(Sept 22, 2015)
  
 **Project Name: **  **Project Name: ** 
Line 11: Line 11:
 **Project Categories:​** **Project Categories:​**
  
-    * Integration & Testing+    * Documentation  ​
  
  
 **Project Description** **Project Description**
  
-The Transformer project aims at interoperability,​ functionality and performance testing of selected, important VNFs for a mixed physical NF (PNF) and VNF environment as typically found in service provider networks based on 3GPP standards. Interoperability and functionality testing shall be possible with minimal configuration following a sandbox approach using protocol analyzers on the relevant interconnection points based on standardized interfaces to the native network elements.+The Transformer project aims at complementing OPNFV projects in the area of interoperability,​ functionality and performance testing of selected, important VNFs for a mixed physical NF (PNF) and VNF environment as typically found in service provider networks based on 3GPP standards. ​
  
-The implementation and integration of Cloud solutions in 3GPP based telecom networks is - in majority of cases - expected to be done in a step-wise approach. New NVFI/VNF elements will be introduced into the existing network architecture and will have to co-exist, integrate and interwork with existing native, in many cases physical Network Elements. ​+The implementation and integration of Cloud/​NFV/​SDN ​solutions in 3GPP based telecom networks is - in majority of cases - expected to be done in a step-wise approach. New NVFI/VNF elements will be introduced into the existing network architecture and will have to co-exist, integrate and interwork with existing native, in many cases physical Network Elements. ​
  
-Knowing this, there is a requirement to secure interoperability on the “vertical” domain (like NFVI interoperability to VNF) and on the “horizontal” domain (i.e. between network functions, either virtualized or native). Last but not least interoperability to the devices and applications using the network functions is also required to ensure end-user experience.+Knowing this, there is a requirement to secure interoperability on the “vertical” domain (like NFVI interoperability to VNF) and on the “horizontal” domain (i.e. between network functions, either virtualized or native). Last but not least interoperability to the devices and applications using the network functions is also required to ensure end-user experience ​performance.
  
 The figure below illustrates the coexistence of virtualized infrastructure in a native 3GPP based network environment. This shows a typical scenario during the transformation phase towards a virtualized telecom network. ​ The figure below illustrates the coexistence of virtualized infrastructure in a native 3GPP based network environment. This shows a typical scenario during the transformation phase towards a virtualized telecom network. ​
Line 27: Line 27:
 {{ wiki:​3GPP-environment.png?​600 }} {{ wiki:​3GPP-environment.png?​600 }}
  
-Since the transformation of networks towards a fully virtualized environment will take a long time mixed deployments will be a reality for the years to come. +Since the transformation of networks towards a fully virtualized environment will take a long time mixed deployments will be a reality for the years to come. During Network Transformation service provider requirements with regard to overall network performance and NF characteristics with regard to e.g. latency or high availability (99.999%) have to be met.
- +
-During Network Transformation service provider requirements with regard to overall network performance and NF characteristics with regard to e.g. latency or high availability (99.999%) have to be met.+
  
 To ensure the service quality and network performance additional testing of NFVI and VNFs in a mixed native/​physical and virtual environment should be considered. Existing OPNFV projects address testing in a pure virtual environment only.  To ensure the service quality and network performance additional testing of NFVI and VNFs in a mixed native/​physical and virtual environment should be considered. Existing OPNFV projects address testing in a pure virtual environment only. 
  
-Transformer” aims at complementing ​these projects to assess carrier grade characteristics for mixed environments during network transformation.+Transformer aims at complementing ​OPNFV projects to assess carrier grade characteristics ​based on available standards (like 3GPP) for mixed environments during network transformation.
  
  
Line 39: Line 37:
  
 From Testing and Performance perspectives,​ there are three main levels of testing and validations to be considered: From Testing and Performance perspectives,​ there are three main levels of testing and validations to be considered:
-* **Interworking** ​ 
-* **Functionality** ​ 
-* **Performance** 
  
-The stability and correct interworking on the interfaces is the foundation for interoperability while the balanced and aligned setting of parameters in the involved network elements will be crucial to obtain the optimal performance.+  1Interoperability  
 +  2. Functionality 
 +  3. Performance
  
-The interworking ​and functionality testing shall be run as the base prior to performance testing, if possible with a minimal configuration/​Sandbox approach and protocol analyzers ​on the relevant interconnection points based on standardized ​interfaces ​to the native ​network elements.+Initial focus of Transformer is on Interoperability following 3GPP standards. ​The stability ​and correct interworking ​on 3GPP defined ​interfaces ​is the foundation for interoperability while the balanced and aligned setting of parameters in the involved ​network elements ​will be crucial to obtain the optimal performance.
  
-It is obvious, that the large number of open & standardized interfaces in telecommunication networks lead to big range of possible configurations of (multivendor) network solutionsincluding virtualized ​and non-virtualized elements+Transformer will define ​set of interoperability requirements per use-case. It will also anaylze and make recommendation for ProcessesMethods ​and Tools to be used for the actual testing activities. Additionaly Transformer will work on acceptance criteria for the test results.
  
-Since the potential full scope of work covering the complete Telecom domain would be very broad and not feasible to be handled in this project, it is recommended to look at selected VNF use cases only. +The interoperability and functionality testing shall be run as the base prior to performance testing, if possible with a minimal configuration/​Sandbox approach and protocol analyzers on the relevant interconnection points based on standardized interfaces to the native network elements. 
 + 
 +It is obvious, that the large number of open & standardized interfaces in telecommunication networks lead to a big range of possible configurations of (multi-vendor) network solutions, including virtualized and non-virtualized elements.  
 + 
 +Since the potential full scope of work covering the complete Telecom domain would be very broad and not feasible to be handled in this project, it is recommended to primarily ​look at selected VNF use cases only. 
  
 As an example, the table below provides an overview of horizontal integration points of typical EPC and IMS related VNFs towards native Network Elements: As an example, the table below provides an overview of horizontal integration points of typical EPC and IMS related VNFs towards native Network Elements:
Line 55: Line 56:
 {{ wiki:​interfaces_1.png }} {{ wiki:​interfaces_1.png }}
  
-It is also proposed ​to start with the interworking and functionality ​testing ​prior to performance testing since this will limit the requirements on the lab environment with regard to capacity ​and redundancy.+Transformer ​is not intended ​to execute or facilitate any integration or testing ​activities but will set the framework (Requirements,​ Acceptance Criteria, Processes, Methods, Tools) for such integration ​and testing projects
  
 ** Documentation ** ** Documentation **
  
-The primary documentation is the wiki pages, including the user guide for the testbeds.+Requirement Definition
  
-* Requirement Definition+Per VNF a requirement sheet about the high level scope for the interoperability,​ functionality and performance testing based on use cases will be defined. Each requirement sheet will be stored as separate file. 
  
-Per VNF a requirement sheet about the high level scope for the interworking,​ functionality ​and performance testing will be defined. Each requirement sheet will be stored as separate file. +Example ​for use case and applicable test case:
  
-ExampleOverview of requirements defined for vCSCF +{{::transformer_use_case_example.pdf|}} ​
- +
-  1(3GPP) Interoperability testing (incl. Cx interface to HSS, Gi interface to GGSN, Rx interface to PCRF, Dx interface to SLF, Mw interface to CSCF and SGW, etc.)  +
-  2. Functionality testing CSCF (incl. typical acceptance test cases to prove that all functionality of the application is covered) +
-  3. Performance Testing CSCF (incl. Redundancy, Load balance, Reliability,​ Stress & Negative testing, etc.)+
  
 ** Dependencies ** ** Dependencies **
  
-Other Test and Performance Projects & Proposals +  ​OPNFV projects: Tbd, but in general all projects participating in a release 
-  ​Virtualized Infrastructure Deployment Policies (“Copper”) +  * Other non-OPNFV owned projects and foras (like 3GPP, ETSI, ITU)
-  * High Availability for VNFs +
-  * Testbed Infrastructure ​(Pharos) +
-  * Base System Functionality Testing +
  
 ** Committers and Contributors ** ** Committers and Contributors **
Line 84: Line 77:
 Committers: Committers:
  
 +  * Younes Fettah (younes.fettah@ericsson.com)
   * Michael Wiegers (michael.wiegers@ericsson.com)   * Michael Wiegers (michael.wiegers@ericsson.com)
-  * Chitti Nimmagadda (Chitti.Nimmagadda@ericsson.com) 
  
 Contributors:​ Contributors:​
- 
  
  
 ** Planned Deliverables ** ** Planned Deliverables **
  
-Propose to start with the interworking ​and functionality testing prior to performance testing ​with minimal configuration/​Sandbox approach with protocol analyzers.+Propose to start with documentation for specific VNFs and use cases. Those should be agreed within ​the project ​and aligned ​with the community work.
  
 ** Proposed Release Schedule ** ** Proposed Release Schedule **
  
-To be aligned with the first OPNFV reference platform ​release ​planned. ​+Target for first Transformer release is OPNFV C-release ​
  
 ** References ** ** References **
Line 103: Line 95:
   1. ETSI NFV ISG Portal   1. ETSI NFV ISG Portal
   2. ETSI GS NFV 001 V1.1.1: Network Function Virtualization;​ Use cases   2. ETSI GS NFV 001 V1.1.1: Network Function Virtualization;​ Use cases
 +  ​
 +  ​
 +**Key Project Facts**
 +
 +Project Name: Transformer\\ ​
 +Repo name: Transformer\\ ​
 +Project Category: Documentation\\ ​
 +Lifecycle State: \\ 
 +Primary Contact: Younes Fettah ([[younes.fettah@ericsson.com]]),​ Michael Wiegers ([[michael.wiegers@ericsson.com]])\\ ​ Project Lead: Younes Fettah ([[younes.fettah@ericsson.com]])\\ ​
 +Jira Project Name: Tbd\\ 
 +Jira Project Prefix: [10 Characters max [A-Z] ]\\ 
 +mailing list tag [Should match Jira Project Prefix]\\ ​
 +Committers:​\\ ​
 +[[younes.fettah@ericsson.com]]\\  ​
 +[[michael.wiegers@ericsson.com]]\\ ​
 +Link to TSC approval: Tbd\\ 
 +Link to approval of additional submitters: Tbd
 +
 +
 +
 +
 +
 +
 +
transformer_-_carrier_grade_requirements_for_network_transformation.txt · Last modified: 2015/09/24 12:19 by Michael Wiegers