| Link | Work Areas, Project Streams | Projects |
| A&M | Architecture and Migration Work Area (A&M) ... Error rendering macro 'excerpt-include' No link could be created for 'Architecture - Migration'. | A&M Projects SD-397 The page Architecture - Migration was not found -- Please check/update the page name used in the MultiExcerpt-Include macro |
|
Architectural Modeling The page Architecture - Migration was not found -- Please check/update the page name used in the MultiExcerpt-Include macro | WT-390, WT-399, SD-365, SD-392 The page Architecture - Migration was not found -- Please check/update the page name used in the MultiExcerpt-Include macro |
| Broadband Assured Services The page Architecture - Migration was not found -- Please check/update the page name used in the MultiExcerpt-Include macro | WT-387, WT-388 The page Architecture - Migration was not found -- Please check/update the page name used in the MultiExcerpt-Include macro |
| Migration The page Architecture - Migration was not found -- Please check/update the page name used in the MultiExcerpt-Include macro | Migration Projects... The page Architecture - Migration was not found -- Please check/update the page name used in the MultiExcerpt-Include macro |
| BUS | Broadband User Services Work Area (BUS) ... The Broadband User Services Work Area provides the broadband industry with technical specifications, implementation guides, reference implementations, test plans, and marketing white papers for the deployment, management, and consumption of services by the broadband end user. Work Area Directors: - John Blackford, CommScope
- Jason Walls, QA Cafe
| BUS Projects |
| CWMP | MD-278, MD-353, SD-069, WT-069 |
| CWMP Data Model Error rendering macro 'excerpt-include' No link could be created for 'CWMP Data Model Project Stream'. | SD-323, SD-344, WT-106, WT-140, WT-181, WT-196 ... The page CWMP Data Model Project Stream was not found -- Please check/update the page name used in the MultiExcerpt-Include macro |
| Device Requirements | WT-124 |
| Network Measurement | MD-363, SD-333, WT-382 |
| Software Tools | SD-354 |
| User Services Platform | WT-369 |
| X-CONF CPE Management | SD-375, SD-376 |
| Wi-Fi in premises | SD-398, SD-401 |
| YANG | Common YANG ... Operators are constantly looking for ways to make their operations more efficient and more cost-effective. A common method used is automation of the configuration and control of network elements. One challenge to doing this effectively is ensuring interoperability between network components of different vendors. The Common YANG Work Area addresses this challenge by defining YANG data models for functionality which is common across access network equipment of various physical layer technologies. - The prime objective of the Common YANG Work Area is the specification of YANG modules that are applicable to multiple Work Areas and/or involve expertise from multiple Work Areas.
- Next to this, it also maintains the BBF YANG Best Current Practices (OD-360), BBF-wide YANG processes, procedures and tools.
- In the future, Common YANG has the mission to specify NETCONF/YANG test plans and certification for the defined YANG modules.
The Work Area is also responsible for identifying YANG work in other SDOs that could or should be used by BBF YANG projects, and will work directly with such SDOs as and when appropriate in order to assist in meeting BBF requirements and timescales. Since its creation, Common YANG has published a series of YANG modules which meanwhile have become accepted by the wide industry: - TR-355: YANG Modules for FTTdp Management
- Defines YANG data models for the management interfaces to support FTTdp, in order to enable interoperability for FTTdp management
- TR-383: Common YANG Modules for Access Networks
- Defines YANG data models for the management of Broadband Forum specified access network equipment used across many deployment scenarios
- With these modules, service providers can efficiently manage a range of broadband services supported over any access technology, including VDSL, G.fast and Passive Optical Networks (PON).
- TR-374: YANG Modules for Management of G.hn Systems in FTTdp Architectures
- Defines a YANG Module for all standardized parameters and associated types for G.hn configuration, status monitoring, performance management, testing and diagnostics
Work Area Directors: Joey Boyd, Adtran and Sven Ooghe, Nokia | YANG Projects |
| Common YANG | WT-383 |
| FAN | Fiber Access Networks Work Area (FAN) ... To define the requirements and data models for deploying Broadband Forum network architectures in fiber access technologies so as to accelerate deployments and ensuring interoperability. Work Area Director: Marta Seda, Calix
| FAN Projects |
| FAN - NGPON2 Wavelength Management | WT-352 |
| FAN - PON Based Mobile Backhaul | WT-311, WT-331 |
| FAN - PON Management | WT-312, WT-385, WT-394, WT-395 |
| FAN - Non-PS Assigned | MD-396, WT-142, WT-156, WT-280, WT-372 |
|
PON Abstraction Layer ... The page FAN PON Abstraction Layer Project Stream was not found -- Please check/update the page name used in the MultiExcerpt-Include macro | WT-402 |
| FTTdp | Fiber to the Distribution Point Work Area (FTTdp) ... Error rendering macro 'excerpt-include' User 'null' does not have permission to view the page. | FTTdp Projects |
| FTTdp - Architecture and Requirements | MD-246, MD-311, WT-301, WT-318, WT-355 |
| FTTdp - Management | WT-298, WT-371, WT-374, WT-393 |
| INN | Innovation Group ... Error rendering macro 'excerpt-include' No link could be created for 'Innovation Group'.
| Innovation Group Projects |
| Innovation - Broadband Assured Services Project Stream | SD-377 |
| Innovation - Broadband Assured Services Use Cases | SD-389 |
| PhyTx | Physical Layer Transmission Work Area (PHYtx) ... The Physical Layer Transmission Work Area provides test plans, technical documentation, and marketing papers to enable multi-vendor interoperability in deployments for both access and in-premises networks. Work Area Directors: Herman Verbueken, Nokia Evan Sun, Huawei
| PhyTx Projects |
| PhyTx - Bonding | WT-273, WT-400 |
| PhyTx - G.fast and RPF Certification | OD-334, OD-335, WT-285, WT-338, WT-347, WT-380 |
| PhyTx - Home Networking | WT-208, WT-381 |
| PhyTx - VDSL2 Physical Layer Testing | OD-297, WT-114, WT-115, WT-249, WT-346 |
| R-T | Routing and Transport Work Area (R&T) ... Error rendering macro 'excerpt-include' User 'null' does not have permission to view the page. | |
| | |
|
Mobile Transport and Routing
| |
| | |
| SDN and NFV Work Area ... This Work Area focuses on the introduction of Software Defined Networking (SDN) and Network Functions Virtualization (NFV) in conjunction with general purpose hardware to create the basis for cloud-based, edge and access networks. Building on this framework, projects address migration and coexistence of physical and virtual elements, into the broadband network, define interfaces, test cases Use Cases and scenarios, reference implementations and automation. Activities work with and coordinate with Open Broadband (OB) program regarding open source, like Open Broadband-Broadband Access Abstraction (OB-BAA) and testing Open Broadband Laboratories (OBLs). Work Area Directors: Bruno Cornaglia (Vodafone) and Mengmeng Li (China Mobile) | SDN&NFV Projects MD-322 MultiExcerpt named npsaprojects was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro |
| CloudCO Project Stream
| Description |
|---|
| 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.
TR-384: Cloud Central Office (CloudCO) Reference Architectural FrameworkTR/WT/MR/MD/SD# | Projects | Abstract | Related Contributions | Editor(s) |
|---|
TR-384 WT-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. | Contributions | Ding Hai (China Unicom) Tim Carey (Nokia) | 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) |
| | WT-328, WT-384 TR-384: Cloud Central Office (CloudCO) Reference Architectural FrameworkTR/WT/MR/MD/SD# | Projects | Abstract | Related Contributions | Editor(s) |
|---|
TR-384 WT-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. | Contributions | Ding Hai (China Unicom) Tim Carey (Nokia) | 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) |
|
| FANS MultiExcerpt named SDNpsfans was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro | WT-370, WT-386 Description: FTTx represents today a high-cost technology (in terms of Return on Investments) to enhance data rates to the end customers, but it requires a huge effort, in terms of CAPEX and OPEX for access network deployment. Due to this, some operators have recognized the need to partner in order to improve the return on investment of FTTx deployment. Sharing the access network infrastructure is a viable way to expand the network and achieve an effective roll-out of new technologies. FANS delivers one network sharing model with high flexibility for forward looking broadband network deployments and operations, facilitating the business innovation, enhancing the network efficiency and improving customer experience. FANS also addresses the virtualization of that shared infrastructure such that each operator could have their own virtual access node.
TR/WT/MR/MD/SD# | Projects | Abstract | Resources | Editor(s) |
|---|
TR-370 Issue 2 | 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. | Contributions | Bruno Cornaglia (Vodafone) | TR-386 WT-386 Issue 2 | Fixed Access Network Sharing - Access Network
Sharing Interfaces | This Technical Report specifies the system interfaces associated with FANS. This document provides details and the information required to define these interfaces as well as the rules for communicating with them. The interfaces described are defined in TR-370 “FANS – Architecture and Nodal Requirements”. | Contributions | Issue 1
Bruno Cornaglia (Vodafone) Issue 2
Haomian Zheng (Huawei)
Jan Diestelmans (Nokia) | | MR-432 | Fixed Access Network Sharing | This paper examines the potential positive business and operational impact of Fixed Access Network
Sharing (“FANS”). FANS enables broadband network infrastructure, and network management, to be
shared amongst operators with resulting cost and standardization benefits along with the opportunity
to handle a wider variety of service offerings. |
| Bruno Cornaglia (Vodafone)
Ken Kerpez (DZS) | | MR-453 | Fixed Access Network Sharing (FANS) Technical Overview | Deep fiber deployments for ultra-fast broadband are technically challenging. Broadband Forum is defining Fixed Access Network Sharing (FANS), to offer a highly enhanced form of virtual unbundling of broadband access networks, enabling cost sharing and enhancing the dynamics of a competitive landscape. FANS automates and harmonizes data, control, and management interfaces among wholesale Infrastructure Providers (InPs) and retail Virtual Network Operators (VNOs). Standardized FANS interfaces can decrease operational expense (OpEx) while increasing customer satisfaction. FANS logically partitions and isolates network resources shared among the VNOs, and such sharing can split the cost of network upgrades among several entities.
FANS works with virtualization, where control-plane functions are migrated from dedicated network
equipment into software running on commodity hardware, with FANS providing Network as a Service
(NaaS). This paper describes emerging Broadband Forum standards supporting FANS, use cases,
FANS components, and details of the architectures supporting FANS. |
| Bruno Cornaglia (Vodafone)
Ken Kerpez (DZS) | ... TR/WT/MR/MD/SD# | Projects | Abstract | Resources | Editor(s) |
|---|
WT-495 | Smart SD-WAN Architecture and Node Requirements | | Contributions | Feng Yang (China Mobile) | |
| MSBN MultiExcerpt named SDNpsmsb was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro | WT-358, WT-368 MultiExcerpt named sdnmsbnprojects was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro |
| WWC | Wireline-Wireless Convergence Work Area (WWC) ... The WWC Work Area addresses the needs of operators, which have integrated, wireline or mobile networks deployed so they can leverage their assets with combined subscriber offerings with a converged core. It aims to deliver more value with deployment options for integrated, wireline, and mobile operators and suppliers. It focuses on optimizing the Total Cost of Ownership by consolidating network, common control plane, and streamlined backend by a comprehensive, well-specified, deployed Wireless-Wireline-Convergence architecture and functions to deliver broadband services with the 5G Core. The Work Area incorporates capabilities from the 5G toolkit to realize a variety of use cases, including topics such as multi-/hybrid access, enhanced work from home, access sharing scenarios and convergence of voice with the 5G system. Broadband Forum is taking an important role in developing 5G, continuing the productive cooperation with 3GPP, and making recommendations for the connection points between the fixed and 5G mobile core networks in order to drive functional network convergence. Work Area Directors: Christele Bouchat (Nokia), Manuel Paul (DT) | WWC Projects |
| 5G Project Stream | Description | PS Leadership |
|---|
5G | This stream addresses architecture between wireline and wireless networks, leveraging a converged 5G Core network, in cooperation with 3GPP, aligned with 3GPP release plan. | |
| SD-357, SD-373, SD-406, SD-407 WT/MD/SD# | 5G PS
Projects | Abstract | Related Contributions | Editor(s) |
|---|
WT-456i3 | AGF Functional Requirements | Issue 3 of the AGF Specification | Contributions | | WT-458 Issue 2 | AGF CUPS | Wireless and Wireline Convergence with Control and User Plane Separation - Reference Architecture, Interface, and Protocol Specification | Contributions | | | WT-470i3 | 5G Wireless Wireline Convergence Architecture | 5G Wireless Wireline Convergence Architecture Issue 3 | Contributions | |
|
| Converged Policy and Control Project Stream | Description | PS Leadership |
|---|
Converged Policy and Control |
| |
| CP&C Projects... MultiExcerpt named WWCCP&CProjects was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro |
| Hybrid Access Project Stream | Description | PS Leadership |
|---|
Hybrid Access | This stream addresses broadband services over dual accesses (wireline and wireless). | |
| WT-378 WT/MD/SD# | Hybrid Access Projects | Abstract | Related Contributions | Editor(s) |
|---|
WT-378 | Hybrid Access Nodal Requirements | The purpose of is to define nodal requirements in support of TR-348 Hybrid Access broadband networks, which will enable service providers to offer higher throughput and reliability services to their subscribers by means of simultaneous use of fixed broadband and 3GPP access networks. | JIRA contributions | |
|
| BBF Software. Software projects for each work area are shown on this page.
They are also covered in detail on the BBF Software page |
|
