VOLTHA 1.3/2.0 Lockdown (Jan 2018) xPON Update Nokia Jan 2018

xPON in VOLTHA

VOLTHA Architecture in June 2017 No support for ONU pre-provisioning from NBI No support for PON provisioning from NBI OLT device can be pre-configured OLT device-id is auto-generated (improvement required in future for NBI configurable ID/name) Hard-coded PON and ONU provisioning Flows CLI REST NC OF-Agent CLI Chameleon NC Server (bottom-up RPCs) Use to relay OMCI messages between the ONU and OLT adapters gRPC (protobuf) Direct interface into core utility Kafka Global Handler Config (in memory) Local Handler Flow Decomposer Consul KV store Config handler Device Agent Supports configuration for flows No configuration support for PON related attributes Handles ONU-id assignment (based on a hard-coded formula UNI Port numbers are hard-coded Hardcoded GEM ports/alloc-ids Fluentd ONU Device automatically created when ONU is detected. All the ONU attributes are hard-coded) No pre-configuration UNI port numbers are hard-coded Some ONU adapters (e.g BCM ONU) use hard-coded VLAN ids (same as in-port) Adapter Agent omci IAdapter interface Proxy itf OLT Adapter . . . ONU Adapter

PON and ONU provisioning introduced by Nokia Introduction of xPON Handler & xPON Agent Support PON and ONU provisioning via NBI Derive protos from WT-385 xPON models IAdapter interface extended for PON and ONU provisioning in a generic fashion Envoy Proxy OF-Agent OF gRPC (protobuf) NC Server (bottom-up RPCs) CLI NC REST OLT Adapter ONU Adapter . . . Global Handler Local Handler Config Handler Adapter Agent Device Agent Flow Decomposer omci IAdapter interface xPON Handler xPON Agent Proxy itf Dispatcher xPON Handler responsible for handling PON and ONU provisioning Responsible for validation and saving provisioning to database TC-Id allocation (i.e. Gem-port and Alloc-IDs) xPON Agent handles all the post-processing of PON and ONU provisioning following the database save Responsible for sending the configuration towards the adapters Kafka Consul KV store Fluentd ONOS

xPON Contributions in VOLTHA 1.0 xPON handler xPON Handler responsible for handling PON and ONU provisioning Responsible for validation and saving provisioning to database TC-Id allocation (i.e. Gem-port and Alloc-IDs) xPON Agent Handles all the post-processing of PON and ONU provisioning following the database save Responsible for sending the configuration towards the adapters gRPC Protobuf Support PON and ONU provisioning via NBI Protobuf is derived from WT-385 xPON YANG model (https://wiki.broadband- forum.org/display/BBF/Software+Release+Registry?preview=/20744764/24346720/WT- 385_draft1.pdf#WT-385_draft1) xPON CLI added for all supported xPON objects IAdapter interface is extended for PON and ONU provisioning in a generic fashion

WT-385 xPON transport YANG Model Used for protobuf between NBI<->CORE and CORE<->adapters Not part of VOLTHA 1.0 Not part of VOLTHA 1.0

xPON support in VOLTHA 1.0 Create, Delete and Update for following objects are implemented in VOLTHA 1.0 channel-group, channel-partition, channel-pair, channel-termination ontani, vOntAni, vEnet Gemport, Tcont, traffic-descriptor Support for XGS-PON simplex PON operation Limited update functionality as required (Full blown blocked by core config-proxy, database limitation) Only Configuration is supported in VOLTHA 1.0 (no support for xPON operational data retrieval) Note: ONU device management to configure is missing in VOLTHA 1.0. For this reason, as a work- around the ONU device is auto-created upon vOntAni creation

xPON support not included in VOLTHA 1.0 Objects yet to be implemented Wavelength profile - Hardcoded for XGS-PON in VOLTHA 1.0 MC Gemport – Hardcoded on adapters in VOLTHA 1.0 Multicast distribution set – Hardcoded behavior in adapters in VOLTHA 1.0 Link table – No support in VOLTHA 1.0. vOntAni and OntAni use the same name for linking xPON operational data support In addition, ONU device management to configure is missing in VOLTHA 1.0. For this reason, as a work- around the ONU device is auto-created upon vOntAni creation. Next slide for more details.

Hardware Entity management for OLTs and ONUs ONU device cannot be pre-provisioned in VOLTHA. Therefore, in VOLTHA 1.0, it is auto-created when vOntAni is provisioned. The OLT ports are discovered and hardcoded and no provision for configuration in VOLTHA 1.0 No provision for configuration of ONU slots/ports in VOLTHA 1.0 Hardware Entity management for OLTs and ONUs Missing in VOTLHA 1.0 Missing in VOLTHA 1.0 Missing in VOLTHA 1.0 Need missing HW Entity management (aka device management) support in VOLTHA for OLTs and ONUs