You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 141 Next »

This page introduces the work in progress within the Forum, organized into work areas. For updates or changes to this page please email the Secretariat at help@broadband-forum.org.

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...

Work Areas, Project Streams and Projects

Work Areas, Project Streams

Projects

Error rendering macro 'excerpt-include'

User 'null' does not have permission to view the page.

WT-359 A Framework For Virtualization - Issue 2                                                 

WT-399 Support of Multicast-ABR in Broadband Forum networks                                                      

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

Projects that don’t fit under the scope of an existing Project Stream or if they fit under the scope of more than one Project Stream, are developed under the Non-PS Assigned category. 

There are no Projects that fall into this category.

MultiExcerpt named BUSxCONFPS was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro

MultiExcerpt named BUSxCONFProjects was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro

Project Stream Page: Compliance Testing Project Stream

Project Stream Leads: Jason Walls 

Description: This project develops test plans and certification guidelines for standards created by the BUS Work Area.

ProjectTitleDescriptionResourcesEditors

ATP-069 Issue 2

TR-069 Abstract Test Plan

ATP-069 provides a test plan that may be used to verify conformance of a CPE Device to the requirements defined in TR-069.

In force version: ATP-069 Issue 2 Corrigendum 1


DTP-181 Amendment 3

CWMP Interoperability and Functionality Test Plan

In order to ensure the continued growth of the TR-069 market and further the interoperability of the protocol, the Broadband Forum is creating a TR-069 Certification Program. Within this program, devices implementing a TR-069 management interface may be tested for their conformance to the TR-069 specification and various use cases.  The TR-069 Certification Program started with the TR-069 Conformance Test Plan and now the CWMP Data Model Implementation Test Plan.  To provide a consistent scope for this verification, BBF developed these test plans that are to be used by the testing agencies in the verification process.

This Internal Document provides a test plan that may be used to verify Interoperability of a CPE Device with an ACS Server through use cases.

Specification

Kanban Board

In force version: TP-181 Amendment 2


DTP-469Conformance Test Plan for USP Agents

Testing is crucial to promoting the interoperability and adoption of standards. To meet this, the Broadband Forum regularly produces test suites that validate the conformance of implementations of their standards. This specification defines the test setup, test procedures, and test metrics to validate Agent and implementations of the User Services Platform (USP), published as BBF TR-369.

This purpose of this document is to provide a definitive guide for validating the compliance of USP Agents in accordance with the specification.

The tests defined below are intended to validate the specific requirements outlined in the USP specification, as well as those requirements defined in the Device:2 Data Model for USP Agents for objects, parameters, commands, and events necessary for the operation of USP.

Test Plan

Bitbucket

Kanban Board

In force version: TP-469 Amendment 1

Jason Walls, QA Cafe

Project Stream Page: CWMP Project Stream

Project Stream Leads: None

Description: This project stream manages the development, maintenance, and updating of the CPE WAN Management Protocol, commonly known as TR-069.

ProjectTitleDescriptionResourcesEditors

Nothing being worked on at this time






Project Stream Page: BUS Data Modeling Project Stream

Project Stream Leads: Matthieu Anne (Orange) and Daniel Egger (Axiros)

Description: This project stream develops the data model objects to manage connected devices using the CPE WAN Management Protocol and/or the User Services Platform. In addition it defines the data model schema and the necessary tool support.

The page CWMP Data Model Project Stream was not found  -- Please check/update the page name used in the MultiExcerpt-Include macro

MultiExcerpt named BUSDRPS was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro

MultiExcerpt named BUSDRProjects was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro

MultiExcerpt named BUSNMPS was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro

MultiExcerpt named BUSNMProjects was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro

MultiExcerpt named BUSSTPS was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro

MultiExcerpt named BUSSTProjects was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro

Project Stream Page: User Services Platform Project Stream

Project Stream Leads:Chen Li (AT&T) and Tim Spets (Nokia)

Description: The project stream handles the development, maintenance, and updating of the User Services Platform.

ProjectTitleDescriptionResourcesEditors
WT-369The User Services Platform

This document describes the architecture, protocol, and data model that builds an intelligent User Service Platform. It is targeted towards application developers, application service providers, CPE vendors, consumer electronics manufacturers, and broadband and mobile network providers who want to expand the value of the end users network connection and their connected devices.

The Data Model Schema and Data Model Objects for USP are developed in the BUS Data Modeling Project Stream (below).

Specification

Bitbucket

Kanban Board

TBD

WT-479Framework for USP-Enabled DOCSIS DevicesShow how USP (TR-369) plus DOCSIS provisioning could do for Cable what TR-142 did for PON in terms of separating physical layer provisioning from higher “service” layer device management.Kanban BoardJohn Blackford (CommScope)

MultiExcerpt named BUSWiFiIPPS was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro

MultiExcerpt named WiFiIPProjects was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro

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

WT/MD/SD#

Projects

Abstract

Related Contributions

Editor(s)

WT-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. 

Code

Jira

Nick Hancock , Adtran
Shiya Ashraf, Nokia

Kevin Noll, Cablelabs 

WT-355YANG Modules for FTTdp ManagementDefines YANG data models for the management interfaces to support FTTdp, in order to enable interoperability for FTTdp management.

Code

Jira

Joey Boyd, Adtran
Ken Kerpez, DZS

WT-393 (dormant project)Persistent Management Agent Aggregator Management Model

Defines the PMAA Northbound Interface (NBI) and the YANG data modules in line with the data models specified in TR-383 and TR-355 for management of DPUs by means of PMAA NBI

Code

Jira

WT-496YANG Modules for MoCA Access 2.5 Interface

Defines YANG data models for the management of MoCA Access 2.5 interfaces.

Code

Jira

WT-513Access Node Management at Scale

Defines YANG data models for the management of Access Nodes in large scale systems

Code

Jira

OD-360

BBF YANG Best Current Practices

Provides a guide to creation of BBF Standard YANG Data Models and their development progress through approval and publication.

Wiki

Jira

Joey Boyd, Adtran

OD-379 (dormant project)Interoperability Test Plan for FTTdp PMA/DPU Management InterfaceThis document defines a suite of basic management tests for a PMA to manage a DPU with defined YANG models. The intent is to provide a structure for vendor-to-vendor interoperability tests (plugfests).

Jira

Martin Casey, Calix
Lincoln Lavoie, UNH InterOperability Lab

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

Project Stream

Description

PS Leadership

Non-PS Assigned

Projects that don’t fit under the scope of an existing Project Stream or if they fit under the scope of more than one Project Stream, are developed under the Non-PS Assigned category. 

Vacant, managed by FAN WA Directors.

MultiExcerpt named FANNonProjects was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro

Project Stream

 Description

PS Leadership

Interoperability and Test

Interoperability project stream is dedicated to PON system interoperability of telecom services over multi-vendor and multi-carrier inter-connections.  The Interoperability project stream has also added OLT NETCONF management interoperability between OLT NETCONF server interfaces and third-party NETCONF clients such as an SDN controller. 


Interoperability and test project is responsible for creating test cases documents for vendor certification and conformance.  Both vendors and operators benefit from these documents as they describe agreed-upon use cases to support.  Being able to exchange information between devices and management applications is crucial for the modern economy.

MultiExcerpt named FANInterTestProjects was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro

Project Stream

Description

PS Leadership

NGPON2 Wavelength Management

The NGPON2 Wavelength Mobility Management project stream is dedicated to the development of NGPON2 Inter-Channel Termination Protocol (ICTP) for interoperability among suppliers of the TWDM and PTP WDM NG-PON2 subsystem, as well as the suppliers of the TWDM CTs for business and residential applications. 

Vacant

WT/MD/SD#

(JIRA Link)

PON Management Projects

Abstract

Related Contributions

Editor(s)

WT-489 Issue 1Authentication of an ONU and selection of eOMCI or vOMCIWT-489 covers requirements concerning the authentication of ONUs and the decision whether it should rely on eOMCI or vOMCI.

CONTRIB-23126 - Getting issue details... STATUS

WT/MD/SD#

(JIRA Link)

Architectural Projects

Abstract

Related Contributions

Editor(s)

 WT-280 Issue 2

Multi-service Broadband Network Architecture and Nodal Requirements (TR-178) in the context of PON

WT-280 documents a set of architectures for a broadband multi-service network, addressing typical infrastructures, topologies and deployment scenarios, and specifies the associated nodal requirements for PON Systems.


Martin Renner , Maxlinear

LE BRAS Hugues, Orange

WT-142 Issue 4

Framework for CWMP and USP enabled PON Devices

The scope of TR-142 Issue 4 includes:

  • Editorial updates from TR-142 Issue 3: 
    • Update both text and diagrams to align with the current editions of the relevant technical specifications: from TR-069 to USP, from ACS to Controller, from TR-098 to TR-181, from G.984.4 to G.988, from 3G to 5G, etc. 
    • Update the References section with the current editions of the relevant technical specifications.
  • Remove text related to B-PON. 
  • Add new new requirements related to Telemetry (USP access to read-only PON parameters), and enable/disable a PON WAN interface on an integrated PON CPE with multiple WAN interfaces.


Samuel Chen , Broadcom

WT/MD/SD#

(JIRA Link)

Interoperability Test Assigned Projects

Abstract

Related Contributions

Editor(s)

DTP-247 Issue 4

G-PON & XG-PON & XGS-PON ONU Conformance Test Plan

DTP-247 Issue 4 defines G-PON & XG-PON & XGS-PON ONU test cases for TR-280 ITU-T PON compliant ONUs.  Executing these test cases as part of a multi-supplier test event will help OLT and ONU's implementation of the specifications operate as a functional system.


Vincent Buchoux, LAN

WT-423PMD Layer Test Plan

Operators that plan to use ITU-T XG(S)-PON (with or without XG-PON), and NG-PON2 requested the FSAN and BBF Groups to document a PMD (Physical Media Dependent) layer test plan for Conformance Events.  Executing these test cases as part of a multi-supplier test event will help OLT and ONU's implementation of the specifications operate as a functional system.


Hal Roberts, Calix

Project Stream

Description

PS Leadership

PON Abstraction Interface for Time-critical Applications

For flexible and agile service adaptation at a low cost in the next-generation optical access system, a new system architecture, which is based on SDN/NFV technologies, should be required. The most promising way to pursue the new architecture is disaggregating PON functions to functional modules with open interfaces.  The project propose a new work item to progress the architecture further by specifying a PON abstraction interface for time-critical processing functions, e.g. Dynamic Bandwidth Assignment (DBA), which is not covered existing BBF documents and on-going projects.

MultiExcerpt named FANPONAbProjects was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro

Project Stream

 Description

PS Leadership

PON Based Mobile Backhaul

The PON based Mobile backhaul project stream is dedicated to the development of PON based Mobile backhaul use cases, mobile system general requirements as well as nodal requirements.

Vacant

MultiExcerpt named FANPONBackProjects was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro


Project Stream

 Description

PS Leadership

PON Management

The PON Management Project Stream is dedicated to the development of NETCONF management models to manage ITU-T and IEEE PON  YANG models. Common PON model promote interoperability between NETCONF servers and 3rd party NETCONF clients.

Joey Boyd, ADTRAN

MultiExcerpt named FANPONMgmtProject was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro

Error rendering macro 'excerpt-include'

User 'null' does not have permission to view the page.

Error rendering macro 'excerpt-include'

No link could be created for 'Innovation Group'.

The page Innovation Group was not found  -- Please check/update the page name used in the MultiExcerpt-Include macro

The page Innovation Group was not found  -- Please check/update the page name used in the MultiExcerpt-Include macro

The page Innovation Group was not found  -- Please check/update the page name used in the MultiExcerpt-Include macro

The page Innovation Group was not found  -- Please check/update the page name used in the MultiExcerpt-Include macro

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

MultiExcerpt named PHYtxNonPS was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro

MultiExcerpt named PHYtxNonProjects was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro

MultiExcerpt named PHYtxBondingPS was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro

MultiExcerpt named PHYtxBondingProjects was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro

MultiExcerpt named PHYtxGfastCertPS was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro

MultiExcerpt named PHYtxGfastCert was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro

MultiExcerpt named PHYtxHNPS was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro

MultiExcerpt named PHYtxHNProjects was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro

MultiExcerpt named PHYtxVDSL2PS was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro

MultiExcerpt named PHYtxVDSL2Projects was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro

Error rendering macro 'excerpt-include'

User 'null' does not have permission to view the page.





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)

Project Stream

Description

Non-PS Assigned


Leadership:

Mengmeng Li China Mobile

Projects that don’t fit under the scope of an existing Project Stream or if they fit under the scope of more than one Project Stream, are developed under the Non-PS Assigned category. 


MultiExcerpt named npsaprojects was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro

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 Framework

TR/WT/MR/MD/SD#

Projects

Abstract

Related Contributions

Editor(s)

TR-384

WT-384 Issue 2


Cloud Central Office (CloudCO) Reference Architectural FrameworkThis 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 CloudCO

TR/WT/MR/MD/SD#

Projects

Abstract

Related Contributions

Editor(s)

TR-408Cloud 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:

  • Interface Descriptions (WT-411)

  • Test Case Descriptions (WT-412)

Application Notes Under Development

Application Notes and how they relate to other work

Coordinated by PSL:

Yves Hetoghs (VMWare)

 




TR-384: Cloud Central Office (CloudCO) Reference Architectural Framework

TR/WT/MR/MD/SD#

Projects

Abstract

Related Contributions

Editor(s)

TR-384

WT-384 Issue 2


Cloud Central Office (CloudCO) Reference Architectural FrameworkThis 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 CloudCO

TR/WT/MR/MD/SD#

Projects

Abstract

Related Contributions

Editor(s)

TR-408Cloud 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:

  • Interface Descriptions (WT-411)

  • Test Case Descriptions (WT-412)

Application Notes Under Development

Application Notes and how they relate to other work

Coordinated by PSL:

Yves Hetoghs (VMWare)

 


MultiExcerpt named SDNpsfans was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro

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.

ContributionsBruno 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-432Fixed Access Network SharingThis 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-453Fixed Access Network Sharing (FANS) Technical OverviewDeep 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)

  • SD-WAN:

...

TR/WT/MR/MD/SD#
Projects
Abstract
Resources
Editor(s)

WT-495

Smart SD-WAN Architecture and Node Requirements

...

ContributionsFeng Yang (China Mobile) 

MultiExcerpt named SDNpsmsb was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro

MultiExcerpt named sdnmsbnprojects was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro


Error rendering macro 'excerpt-include'

No link could be created for 'Wireline-Wireless Convergence'.

The page Wireline-Wireless Convergence was not found  -- Please check/update the page name used in the MultiExcerpt-Include macro

The page Wireline-Wireless Convergence was not found  -- Please check/update the page name used in the MultiExcerpt-Include macro

The page Wireline-Wireless Convergence was not found  -- Please check/update the page name used in the MultiExcerpt-Include macro

The page Wireline-Wireless Convergence was not found  -- Please check/update the page name used in the MultiExcerpt-Include macro
The page Wireline-Wireless Convergence was not found  -- Please check/update the page name used in the MultiExcerpt-Include macro

The page Wireline-Wireless Convergence was not found  -- Please check/update the page name used in the MultiExcerpt-Include macro

The page Wireline-Wireless Convergence was not found  -- Please check/update the page name used in the MultiExcerpt-Include macro
The page Wireline-Wireless Convergence was not found  -- Please check/update the page name used in the MultiExcerpt-Include macro
BBF Software. Software projects for each work area are shown on this page.
They are also covered in detail on the BBF Software page


  • No labels