OpenOLT Adapter Support for Technology Profile and Meter support in addition to existing OpenFlow Configuration

When the OpenOLT Adapter is passed the OpenFlow programming information it will look for a Technology Profile Reference by examining the Flow Table ID index. An Index in the range 64-255 will indicate it is a Reference to a Technology Profile. The OLT Adapter will use it's Technology Type (XPON/EPON etc.) as a Key in conjunction with the Flow Table ID to look up the Referenced Technology Profile and any Meters from the KV Store.

The Meter(s) referenced in the OpenFlow messages will be used to generate the Downstream Bandwidth Profile for the Service and also the Upstream DBA Bandwidth Parameters.

Both Upstream and Downstream Flows are required before Progressing.

The algorithm for deriving the Downstream and Upstream Bandwidth Profile Parameters is described in the Epic Link as an attached file "VOLTHA_Access_Tech_AugmentationV0.6".

When the OpenOLT Adapter retrieves both the OpenFlow Programming Messages and a specific Technology Profile it will use the Technology Profile and Flow Data to create a Service Specific Profile Instance. The XPON OpenOLT Adapter will provide an XPON TC Layer Resource Manager function so that it can allocate service specific Alloc-ID values and GEM Port-ID values based on the Technology Profile defined number of GEM Ports/Queues. A Technology Specific Profile Instance will be Created by the OpenOLT Adapter and used to store any System allocated values. System allocated Resources MUST not be reused until released back to the Resource Manager. Resource Allocations MUST also survive an pOLT or VOLTHA Server Reboot/Restart.  

It is assumed that the physical OLT chassis will allocate an ONU-ID to a Discovered ONU and the OMCI alloc-id and GEM Port ID assigned from the reserved range (see G.989.3), however depending on the Adapter implementation the Resource Manager may be used to manage the ONU-ID assignment.

The OLT Adapter will use a combination of the OpenFlow Logical Port, Technology Profile Flow ID and Technology to uniquely identify the Service Profile Instance in the KV Store.

(Note initially the Two Technology Profile Instance control attributes, ONU Instance Control and UNI Instance control, will use only the ONU Instance Control [Multi-Instance or Single Instance] and the UNI Control will always be set to be 'Single Instance' - this allows the ONU adapter to derive the lookup Key for the Service Profile Instance simply - in future we may support multiple instances of the same profile on the same UNI [differentiated by, for example, the QTAG value of the incoming frame as an additional Instance lookup Key]- but not initially)