• vPE
  • Name of Use Case: Virtual Provider Edge
  • Use Case Authors: R.Prakash
  • Description: Virtual Provider Edge Router (vPE) is a VNF  serving as an edge router. This VNF could be a part of Network Services related to the edge cloud segment. The vPE VNF typically located between two networks such as the provider core network and the provider access network. The customer edge router sits in the provider access network and  cloud network, representing the provider core network. The edge router processes the traffic in both directions. The functionality of the edge router varies while processing each direction of traffic. The packets to the core network will be filtered, classified, and metered with Quality of Service (QoS) parameters. The packets to the access network will be shaped according to the subscription policy. 
    The following minimum features of a carrier-grade vPE system will be  configuring on  Vyyata open source router to achieve the requirement. Any unmet requirement for Edge will be supplemented through additional software APIs and code such as Application tate Management.
    
    
    
    • To Provide a command-line interface for each component of the edge router 
    • To provide North Bound Restful Admin and User APIs to be exposed for Network and Storage units to be programmed by applications.
    • The edge router shopuld support stateless and state managed sessions
    • The upstream and downstream sessions may have different work flows.
  • Users and Benefit:
  • VNF:
  • Work Flows:
  • Controll Automation:
  • Project Impact:
  • Work Commitment:
• Proposal 2
  • Use Case UML Diagram
  • Use Case Definitions
    • <Use Case Title>

Proposal 1

Name of Use Case:

<give it a name>

Use Case Authors:

<who wrote the use case>

Description:

<provide a description on what the use case does>

Users and Benefit:

< who would benefit from this use case, how and under what scenarios >

VNF:

< list the VNFs this use case will automate/impact/use, be both generic like EPC and specific in terms of software used e.g. which EPC code or vendor product>

Work Flows:

< describe the work flows which are part of the use case. E.g. Instantiation, Deletion of VNF >

Controll Automation:

< describe any control automation that is part of the use case E.g. auto scaling, auto fault detection or recovery>

Project Impact:

< list all projects that are impacted by this use case and identify any project which would have to be created >

Work Commitment:

< identify who is committing to work on this use case and on which part>

Proposal 2

Use Case UML Diagram

<Insert UML Use Case Diagram>

Use cases define how different users interact with a system under design.  Each use case represents an action that may be performed by a user (defined in UML as an Actor with a user persona).

Use Case Definitions

Each Use Case from the UML Use Case Diagram is defined in this section.

<Use Case Title>