Jump to: navigation, search


Contributing Use Cases

The Telecommunications Working group welcomes use cases from Communication Service Providers (CSPs), Network Equipment Providers (NEPs) and other organizations in the telecommunications industry. To begin adding a use case simply copy the "Template" section of this page to the bottom of the list and rename it to a name that describes your use case.

When writing use cases focus on "what" you want to do and "why" rather than specific OpenStack requirements or solutions. Our aim as a working group is to assist in distilling those requirements or solutions from the use cases presented to ensure that we are building functionality that benefits all relevant telecommunications use cases. Submission of use cases that pertain to different implementations of the same network function (e.g. vEPC) are welcome as are use cases that speak to the more general demands telecommunications workloads place upon the infrastructure that supports them. In this initial phase of use case analysis the intent is to focus on those workloads that run on top of the provided infrastructure before moving focus to other areas.

Use cases are now written in ReStructured Text format and stored in the telcowg-usecases git repository on Stackforge.

Reviewing Use Cases

The working group uses OpenStack's Gerrit installation to collaborate on use case documentation, with the resultant work ultimately being stored in a git repository. To review items stored in Gerrit you will first need to create an account.

Note that to simply review items you will not need to sign the CLA, you will need to do this to upload use cases though. If you have any concerns about this process, consider joining one of the weekly TelcoWorkingGroup meetings to ask for assistance.

Once you have created an account you can find open items for review by opening this query in your web browser:

The result of which will look something like this:

Updating Use Cases

Contributed Use Cases



Describe the use case in terms of what's being done and why.


Describe important characteristics of the use case.

VPN Instantiation

Contributed by Margaret Chiosi

Etherpad: https://etherpad.openstack.org/p/telcowg-usecase-VPN_Instantiation


VPN services are critical for the enterprise market which the Telcos provide services to. As we look to virtualize our PEs, VPN instantiation on a vPE needs to be addressed since connectivity is important. Proposal is to focus on ODL/Neutron linkage to openstack orchestration. Instantiate a VPN service on a vPE connecting to either a vPE or PE. This includes identifying where the vPE needs to be located (some set of criteria needs to be defined - latency, diversity..) and then created on a virtualized environment. Connectivity to the other vPE/PEs need to be setup. Then finally the VPN service over the different vPE/PE which match the customer sites needs to get instantiated.


  • Affinity rules
  • ODL SDN Controller for connectivity setup
  • Physical connectivity between the different vPE/PE environments are assumed to exist
  • Logical connectivity between different vPE/PE needs to be setup as the vPE is instantiated
  • VPN service connectivity needs to be setup
  • need to add the flow logic between the openstack components and ODL


  • Affinity rules
  • ODL SDN Controller for connectivity setup
  • Physical connectivity between the different vPE/PE environments are assumed to exist
  • Logical connectivity between different vPE/PE needs to be setup as the vPE is instantiated
  • VPN service connectivity needs to be setup
  • Don't need to setup connectivity to customer router (CE) for this use case

Session Border Controller

Contributed by: Calum Loudon

Review: https://review.openstack.org/#/c/176301/

Virtual IMS Core

Contributed by: Calum Loudon

Review: https://review.openstack.org/#/c/158997/

Access to physical network resources

Contributed by: Jannis Rake-Revelant

Etherpad: https://etherpad.openstack.org/p/telcowg-usecase-Access_to_physical_network


This use case aims to solve the problem of accessing physical (network) devices outside of the Openstack Infrastructure, that are not addressable by a public IP address. This use case can currently be implemented in various ways, as will be detailed later on. The background of this use case is the necessity to communicate with physical devices, in our case e.g. an eNodeB, to a VNF, e.g. a vEPC. Communication/ addressability should be possible from either side. In the current environment different physical devices are separated by VLANs and private IP subnets. The goal is to establish L3 (or L2 if that is "easier") connectivity.

The main goal of this use case is not necessarily to implement something new but to discuss the practicability of the current implementations. If I missed an alternative implementation please add it to the list.


Possible current implementations include:

  • L3 gateways
    • SNAT
    • L3 forwarding
    • Floating IPs
  • External provider networks, e.g. VLAN backed
  • L2 gateways, currently only possible with 3rd party software (?)


Security Segregation (Placement Zones)

Contributed by: Daniel Schabarum (DaSchab)

Review: https://review.openstack.org/#/c/163399

Work In Progress

Service Chaining

Etherpad: https://etherpad.openstack.org/p/kKIqu2ipN6


Etherpad: https://etherpad.openstack.org/p/telco_orchestration


Etherpad: https://etherpad.openstack.org/p/mno-mvno

SIP Load-Balancing-as-a-Service

Etherpad: https://etherpad.openstack.org/p/telcowg-usecase-SIP_LBaaS