Project Streams
Multiexcerpt | |||||||
---|---|---|---|---|---|---|---|
| |||||||
PS Leadership
|
Multiexcerpt | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||
Yves Hertoghs, VMWare Ning Zong, Huawei Technologies
| SDNpscloudcomponents | ||||||||||
Project Stream Page: Cloud Component Project Stream Project Stream Leads: Tim Carey , Nokia Mission: The project stream's mission is to provide specifications and guidance for Cloud-based components used in the broadband network. The specification and guidance provided by this project stream help ensure that Cloud-based Components are multi-vendor and inter-operable. Critical elements of the work provided by this project stream is the support the transition from existing architectures toward Cloud-based architecture and alignment, when applicable, with various Cloud-based architectural frameworks such as Cloud CO. Business Impact: The work creates the necessary architectural and interface specifications and associated guidance that enables a multi-vendor, inter-operable set of Cloud-based components that reduces the cost of development and deployment of Cloud-based components through standardized architectures, protocols, APIs and information elements. Scope: Specifically the project stream covers the following projects:
Enhance access and home networks with Cloud-based automation and intelligence, to achieve higher O&M efficiency and lower OPEX.
Considers the Edge Computing impacts on multi-service broadband network, reference architecture, interfaces and to identify metro computing networking requirement,
|
SDN and NFV Projects in Progress
|
WT/MD/SD#
Non-PS Assigned Projects
Abstract
Related Contributions
Editor(s)
This project will explore possible network innovation regarding the edge computing era. The goal is to consider the Edge Computing impacts on multi-service broadband network, reference architecture, interfaces and to identify metro computing networking requirements.
Ruobin Zheng (Huawei Technologies)
Bo Lei (China Telecom)
Multiexcerpt | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
WT/MD/SD#CloudCo ProjectsAbstractRelated ContributionsEditor(s)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
Contributions | Tim Carey (Nokia) Wei Lin (Huawei) 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. | Contributions | Ding Hai (China Unicom) 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. 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-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:
The OLT then would be responsible for:
Contributions | Tim Carey (Nokia) Zhang Dechao (China Mobile) 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 | 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
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 | | ||||||||||||||||||||||
Multiexcerpt | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
WT/MD/SD# | FANS Projects | Abstract | Related Contributions | Editor(s) | |||||||||||||||||||||||||||||||||||||||||||||||||||
Approved in April 2020: TR-370 Issue 2 (PDF) | Fixed Access Network Sharing – Architecture and Nodal Requirements | This Technical Report specifies technical aspects associated with Fixed Access Network Sharing (FANS) that involve the access network (including access nodes and aggregation nodes). It focuses on the cases of Passive Optical Network (PON) and DSL and G. fast access technologies. | Jira Contributions | Bruno Cornaglia | |||||||||||||||||||||||||||||||||||||||||||||||||||
|
Multiexcerpt | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Multiexcerpt | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
WT/MD/SD#SDN AIM ProjectsAbstractRelated ContributionsEditor(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. Yue Sun (China Unicom) Ken Kerpez (ASSIA) |