| This project stream is developing a next generation Central Office (CO) System that is part of BBF Open Broadband, which incorporates Software Defined Networking and Network Function Virtualization with SDN control & management running on a cloud-like infrastructure deployed at Central Offices. By ‘cloud-like’, it is meant that the infrastructure leverages commodity network switches and commodity compute nodes with virtualization software to host various virtualized network functions (VNFs). Infrastructure operators can offer these functions to 3rd parties and 3rd party network functions can be inserted into the platform, allowing Value Added Services. The goal of this project is building on the architectural framework for such a Cloud CO (TR-384), with appropriate abstracted functional modules, and interfaces, eventual API and protocol choices and/or definitions. The architectural framework allows interconnecting these functional modules in an interoperable manner. A secondary goal is to figure out and shows how standards organizations and open source projects can collaborate. This project will also establish a reference implementation of the Cloud CO framework, creating a platform for innovation and potential open source upstreaming into other organizations, as well as a platform for industry interoperability testing (OBL) and certification of NFs and the components that implement the aforementioned functional modules.
Multiexcerpt |
---|
MultiExcerptName | cloudcoprojects |
---|
| TR-384: Cloud Central Office (CloudCO) Reference Architectural FrameworkTR/WT/MR/MD/SD# | Projects | Abstract | Related Contributions | Editor(s) |
---|
TR-384 WT- | 411Definition 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. | Contributions | Tim Carey (Nokia) Wei Lin (Huawei) | 384 Issue 2
| Cloud Central Office (CloudCO) Reference Architectural Framework | This Cloud Central Office (CloudCO) document helps drive a key element of the BBF's strategy in enabling new revenue generating-services. It defines a platform that serves as a
platform for both wireline and wireless networks. Operators will have the opportunity to run a single network with all varieties of access technologies, and flexibly deploy innovative services. Issue 1 is the first phase in a multiphase project defining the high level architectural framework. Related specs include migration, detailed interface definitions, test cases & application notes, use cases & scenarios and reference implementations. | Contributions | Issue 1 Ding Hai (China Unicom) Georgios Karagiannis (Huawei Technologies) Issue 2 Ding Hai (China Unicom) Aihua Guo (Futurewei)
|
Projects Building on CloudCOTR/WT/MR/MD/SD# | Projects | Abstract | Related Contributions | Editor(s) |
---|
TR-408 | Cloud CO Migration and Coexistence | This Cloud Central Office (Cloud CO) document provides guidance to Service Providers as they transform their existing Multi Service Broadband Networks (MSBN) toward a Cloud CO based network that is more adaptable, agile, scalable and dynamic than the existing MSBN, while reducing costs by retaining investments that the Service Provider has made in their MSBN. This document identifies considerations that Service Providers need to consider when determining the deployment strategy of either migrating the existing network or deploying a Cloud CO based network that coexists with the existing MSBN. It also provides transformation assistance by identifying approaches to migrating their existing MSBN and discusses when and how to introduce the Cloud CO infrastructure or leverage their existing IT infrastructure. Finally, the document provides examples of how functionality in the management, control and user planes can be migrated toward Cloud CO |
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-dependentWT-413 Issue 2 | 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. | Contributions | Mauro Tilocca (Telecom Italia) Tim Carey (Nokia) | 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. | Contributions | Ken Kerpez (ASSIA) Mauro Tilocca (Telecom Italia) 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. | Contributions | Yang Wenle Huawei Technologies Jie Chen CAICT | WT-474 | Subscriber Session Steering | As Broadband Networks become more dynamic with SDN control and Cloud Central office, it is now possible to programmatically control which User Plane (UP) function each individual subscriber should be connected to. This creates many advantages for an operator to offer different service propositions to different customers. This project will define an architecture for Subscriber Session Steering, using the dBNG as an exemplary function. | Contributions | Jonathan Newton (Vodafone) Mach Chen (Huawei) | WT-477 | Cloud CO Enhancement - Access Node Hardware Disaggregation | Operators want their networks to be adaptable, agile, scalable and dynamic, while reducing costs. Besides reducing CAPEX and OPEX, shortened time-to-market is much more desired. SDN and NFV in conjunction with general purpose hardware are two powerful tools that are exploited in the industry to optimize current networks. In BBF, the CloudCO re-architects the broadband network using the above mentioned technologies running on a cloud-like infrastructure, deployed at Central Offices. It encompasses the enabling work required for dramatically faster and more efficient provisioning of new revenue generating-services. On the other hand, Opensource organizations have a different life-cycle, focused on the implementation of reference features and using immediately available standards which can lead to incomplete, non-compliant and tightly integrated components. The scope of this project is to perform a gap analysis between Cloud-CO and Opensource solution(s) by defining the missing interface(s) between Disaggregated OLT and physical OLT. | Contributions | Bruno Cornaglia (Vodafone) Francisco de Carvalho (BT) | WT-484 | Access Network Abstraction, Softwarization, and Disaggregation | TBD | Contributions | Call for Editors | 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: | Application Notes Under Development | Application Notes and how they relate to other work Coordinated by PSL: Yves Hertoghs, VMWare | TR-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. | Contributions | Tim Carey (Nokia) Wei Lin (Huawei) | TR-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. | Contributions | Ding Hai (China Unicom) | TR-413 WT-413 Issue 2 | 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. | Contributions | Issue 1 Mauro Tilocca (Telecom Italia) Haomian Zheng (Huawei) Issue 2 Mauro Tilocca (Telecom Italia)
| TR-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. | Contributions | Ken Kerpez (DZS) Mauro Tilocca (Telecom Italia)
| TR-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. | Contributions | Yang Wenle Huawei Technologies Jie Chen CAICT | TR-477 WT-477 Issue 2 | Cloud CO Enhancement - Access Node Hardware Disaggregation | Operators want their networks to be adaptable, agile, scalable and dynamic, while reducing costs. Besides reducing CAPEX and OPEX, shortened time-to-market is much more desired. SDN and NFV in conjunction with general purpose hardware are two powerful tools that are exploited in the industry to optimize current networks. In BBF, the CloudCO re-architects the broadband network using the above mentioned technologies running on a cloud-like infrastructure, deployed at Central Offices. It encompasses the enabling work required for dramatically faster and more efficient provisioning of new revenue generating-services. On the other hand, Opensource organizations have a different life-cycle, focused on the implementation of reference features and using immediately available standards which can lead to incomplete, non-compliant and tightly integrated components. The scope of this project is to perform a gap analysis between Cloud-CO and Opensource solution(s) by defining the missing interface(s) between Disaggregated OLT and physical OLT. | Contributions | Issue 1 Bruno Cornaglia (Vodafone) Francisco de Carvalho (Reply) Issue 2 Antonio Marsico (Net Reply) Francisco de Carvalho (Reply)
| TR-484 | Access Network Abstraction, Softwarization, and Disaggregation | This Technical Report specifies a Broadband Access Abstraction (BAA) Layer as part of a Software Defined Access Network (SDAN) architecture capable of: - Seamlessly supporting a multi-vendor, multi-technology network of Access Nodes (AN)
- Connecting different designs of physical ANs, e.g., traditional chassis-based and disaggregated ANs
- Disaggregating Management Plane and Control Plane functions from the physical ANs and hosting
the functions on centralized or distributed NFVI locations
This Technical Report describes the key functional components of a SDAN architecture, specifies the BAA Layer system and complements the family of Broadband Forum’s CloudCO specifications related to the access domain (e.g., TR-384 [9], TR-411 [12], TR-413 [13], TR-435 [14], TR-451 [15], WT-477 [18]). | Contributions | Mauro Tilocca (Telecom Italia) | 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: | Application Notes Under Development | Application Notes and how they relate to other work Coordinated by PSL: Yves Hetoghs (VMWare) |
|
|