WT/MD/SD# | CloudCo Projects | Abstract | | Editor(s) |
|---|
| CloudCO migration and co-existence | The purpose of this project is to suggest methods by which a existing/legacy broadband network may gradually migrate to one based on CloudCO and/or coexistence of the legacy and CloudCO architecture within segments of the same network. | JIRA contributions | |
| WT-411 | Definition of interfaces between Cloud CO Functional Modules | This work will define the Interfaces between the Functional Modules in the Cloud CO Architectural Framework, as well as the Cloud CO Northbound API. Network Transport Protocols will be defined to carry the interface attributes. Furthermore the data models, schemas or APIs that are signaled across them will be defined as well. Existing Open Interface works, as described in Standards and Open Source work will be leveraged as much as possible. This project is based on and will grow incrementally, driven by a series of Cloud CO Application Notes (APPNs). Cloud CO Application Notes will detail how a certain service is instantiated, maintained and consumed across the Cloud CO Architecture and will detail the necessary interactions between the different Functional Modules in the Architectural Framework, as well as the interactions with the Cloud CO Northbound API in order to achieve the necessary end result. | JIRA contributions | Wei Lin, Huawei Technologies Dharma Rajan, VMware |
| WT-412 | Test Cases for Cloud CO Applications | This work will define Test Cases for Cloud CO Applications. Cloud CO scenarios are described in Cloud CO Application Notes as well as TR-416. The Cloud CO Application Notes will detail how a certain service is instantiated, maintained and consumed across the Cloud CO Architecture. The Test Cases will be consumed by the Open Broadband Labs (OBLs), effectively validating the Cloud CO Application Note. The development of WT-411 Interfaces, WT-412 Testing and Application Notes are inter-dependent. | JIRA contributions | |
| WT-413 | SDN Management and Control Interfaces for CloudCO Network Functions | In the Cloud CO context, WT-413 specifies the management and control framework of Network Functions and a formalism to specify their NBIs to identify the supported macro functionalities and link them to existing/to-be YANG DMs. This work primarily enables the migration from SNMP/MIB towards NETCONF/YANG interfaces and potentially other protocols to exercise not only traditional FCAPS management functions but also fine grained flow control across VNFs and PNFs network service graphs. This is a key step towards Software Networking introduction and in turn the automation and Orchestration of PNFs and VNFs in a Cloud CO type of architecture. The development of this Working Text shall also shape the thinking on the way Cloud CO interfaces, especially for VNFs, are modeled and the opportunity to reuse/extend existing YANG work for that. | JIRA contributions | Georgios Karagiannis, Huawei Technologies Mauro Tilocca, Telecom Italia S.p.A |
| WT-435 | NETCONF requirements for Access Nodes and Broadband Access Abstraction | This project will develop the NETCONF requirements for the NETCONF/YANG Northbound interfaces (NBIs) of Access Physical Network Functions (PNFs) and the CloudCO BAA layer towards the Management and Control (M&C) elements that interact with them. | Jira contributions | Duane Remein Huawei Technologies
|
| WT-451 | vOMCI Interface Specification | The scope is to standardize the NBI and SBI of vOMCI function. The vOMCI function may support other administrative interfaces to modules (e.g., logging) to support non-OMCI related features, standardizing these interfaces are beyond the scope of this document. The vOMCI function is responsible for: - Receiving service configurations from the vOLT Management function
- Translating the received configurations into G.988 OMCI management entities (ME) and formatting them into OMCI messages
- Encapsulating and sending above formatted OMCI messages through the OLT to the attached ONU
- Translating the received ONU’s operational data from the OLT and sending it to the vOLT Management function
The OLT then would be responsible for: - Transparently sending OMCI messages received from vOMCI function, to the correct ONU using the PON OMCI channel
- Encapsulating received OMCI messages from the ONU and sending it to the vOMCI function
| Jira contributions | |
| WT-454 | YANG Modules for Access Network Map & Equipment Inventory | In a CloudCO architecture, the management of physical nodes requires interfaces to expose Access Network Map (ANM) and Equipment Inventory information to the SDN Management and Control and other CloudCO functional blocks. For the support of multiple tenants, it’s also useful to expose to Tenants only relevant ANM and Equipment Inventory information over the NB API. The project is defining YANG data models for ANM and Equipment Inventory applicable to the BAA layer and the Access SDN Management and Control. | Jira contributions | Yang Wenle Huawei Technologies Jie Chen CAICT |
| Application Notes |
| Application Notes (APPN) use the TR-384 framework to describe an implementable Use Case for a CloudCO 'application'. APPN includes - Assumptions and Preconditions
- System Description using TR-384 framework (components) + Drawing
- Description of Actors
- Interactions, which describe what information gets exchanged between the TR-384 functional elements and what happens as a result after an actor performs an 'action' i.e an API call at the CCO NB API or a user plane packet that enters the system. A ladder diagram shows the various interactions between the functional elements.
- Success Criteria for the interactions
- Various instances can be instantiated which detail a given implementation of the individual components
An Application Note Instance will then be created that details the exact components to be bootstrapped/installed onto an NFVI. ((i.e. it describes what VIM is chosen, etc, as well as e.g software releases etc). The APPN is then used to guide development of: - Interface Descriptions (WT-411)
- Test Case Descriptions (WT-412)
| Application Notes Under Development | |
