Both the Upstream and Downstream Bandwidth Profiles can be 'named' and Referenced from a Subscriber Record in the SADIS DB on ONOS.

When the vOLT Appplication uses a Subscriber Record for OpenFlow message generation to VOLTHA the vOLT Application Must read the Bandwidth Profile name and be able to retrieve the Profile from a Database of Bandwidth Profiles. The Named Profile is converted to a Meter and Meter Band(s) and configured on the VOLTHA Instance, and the Flows will reference the Meter.

Note the code should be written to follow the SADIS DB model where it is designed to reference an external database but the DB records can be cached locally.

The Upstream Bandwidth Profile will consist of the following optional components:

EIR (Bits/Sec)

EBS (Bytes)

CIR (Bits/Sec)

CBS (Bits/Sec)

AIR (Bits/Sec)

The Downstream Bandwidth Profile will consist of the following optional components:

EIR (Bits/Sec)

EBS (Bytes)

CIR (Bits/Sec)

CBS (Bits/Sec)

 Each bandwidth component will be interpreted as defined in the Technology Profile Whitepaper ([^vOLTHA_Access_Tech_AugmentationV0.6.pdf]

)

Change-Id: Ie4edf4e9f27e9b5b9a84e6c733dc4f283a9996a7
10 files changed
tree: ca886ca0e8db85fb75bd072693565305400cc826
  1. .cloudbees.md
  2. .gitignore
  3. .gitreview
  4. LICENSE.txt
  5. README.md
  6. TEST-README.md
  7. api/
  8. app/
  9. pom.xml
README.md

ONOS OLT OpenFlow Control Application

Build

Let's build all the code

mvn clean install