Projects in Progress for this Work Area
WT-408 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. Wei Lin, Huawei Technologies Dharma Rajan, VMware 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. Georgios Karagiannis, Huawei Technologies Mauro Tilocca, Telecom Italia S.p.A 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: The OLT then would be responsible for: Tim CareyNokia Zhang Dechao ChinaMobile 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. Application Notes (APPN) use the TR-384 framework to describe an implementable Use Case for a CloudCO 'application'. APPN includes 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: Application Notes and how they relate to other work Coordinated by PSLs: Yves Hertoghs, VMWareWT/MD/SD#
CloudCo Projects
Abstract
Related Contributions
Editor(s)
CloudCO migration and co-existence 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 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 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 WT-451 vOMCI Interface Specification Jira contributions WT-454 YANG Modules for Access Network Map & Equipment Inventory Jira contributions Application Notes Jira contributions
Ning Zong, Huawei Technologies
WT/MD/SD# | FANS Projects | Abstract | Related Contributions | Editor(s) |
---|---|---|---|---|
WT-386 | FANS Access Network Sharing Interfaces | “FANS - Access Network Sharing Interfaces” investigates technical aspects related to the system interfaces associated with FANS. This document provides details and the necessary information required to effectively define these interfaces as well as the rules for communicating with them. | JIRA contributions | Peter Silverman, ASSIA |
MD-453 | Fixed Access Network Sharing (FANS) Technical Overview | This paper discusses this evolution and the potential impact of Fixed Access Network Sharing (FANS) for those interested in business-related aspects. FANS enables broadband network infrastructure, and network management, to be shared amongst operators; thus sharing the costs of gigabit-class broadband deployment while enabling operators to run their own operations. Compared with deploying multiple parallel networks, FANS can lower capital costs. (previously listed as MD-426) | Jira Contributions | Ken Kerpez, ASSIA |
WT/MD/SD# | SDN AIM Projects | Abstract | Related Contributions | Editor(s) |
---|---|---|---|---|
WT-436 | Access & Home Network O&M Automation/Intelligence | Over the past decade, growth in the Telco industry’s revenue has never outpaced growth in OPEX. As the scale of a network increases, OPEX increases with it. Therefore, it is expected that work needs to be done in order to reduce OPEX. This project will specify the logical framework of access & home network O&M automation, including necessary functional blocks, logical connection descriptions and information flows between the modules. In addition, this work will suggest possible applications of this framework to typical BBF service architectures. This identifies the information elements required in access & home network O&M automation, key use cases and KPIs, and analysis of the gaps with existing architectures to support these information elements. The project will describe what kinds of the information elements are required. |