Technical Work in Progress

The following sortable table covers the top Forum projects that will ultimatedly be desginated for publication as documents or software. A number of important projects being developed by the mebership are also listed. Many more and the technical details of work in progress is available on the members wiki

Projects where the project leaders have recorded introductory videos are indicated in the table.

Broadband Forum Technical Projects in Progress

A&MWT-387Broadband Assured IP Services Architecture In Development.
A&MWT-388Broadband Assured IP Services Technical Specification In Development.
BUSWT-069a6CPE WAN Management Protocol
This WT defines version 1.5 of the CPE WAN Management Protocol, incorporating items from the Issue List IL-069. It includes updates to the firmware management system, security updates, and updates to the XMPP connection request and notification mechanisms.
BUSWT-181 Issue 2 Amendment 12Device Data Model for TR-069 In Development.
BUSWT-382Test Plan for 1905.1/1a In Development.
BUSMembers' DocumentHome Network Measurement
White paper on home network problems in develpment, test plans
BUSWT-369User Service Platform (USP)
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.
    This document describes:
  • The overall architecture of USP Agents, Controllers, and service elements
  • The proxy mechanisms for addressing non-USP service elements
  • Requirements for the transport protocol used to handle USP messages, and defined bindings for specific protocols.
  • The various CUSP messages, their requirements, and expected behavior patterns, along with on-the-wire encoding of CUSP messages
  • The protocol requirements for discovery, end-to-end security, authentication, and authorization
  • An explanation of the data model and how it is used to enable USP, service elements, proxying, and object defined operations
The objects necessary to implement USP are described in the Device:2 data model of the CPE WAN Management Protocol, (CWMP).
SoftwareWT-383 Amendment 1Common YANG In Development.
FANWT-372Framework-for-multi-management-PON-devices This document is intended to define a framework for remote management of CPE over various PON access technologies. TR-069 is the protocol of choice used by service providers worldwide for the remote management and configuration of many kinds of broadband CPE. The scope of this document is to detail the applicability to CPE having a PON WAN interface and in particular to clarify the relationship between different management protocols for example TR-069, NETCONF, and OMCI IEEE 802.3ah.

The scope of this document addresses any PON device that is managed by different management protocols, for example, Single Family Units, Single Business Units, Multi-Dwelling Units, Multi-Tenant Units, and Distribution Point Units.

FANWT-352 Issue 2Multi-wavelength PON Inter-Channel-Termination Protocol (ICTP) Specification The purpose of this Working Text is to specify a protocol that is executed between the OLT Channel Terminations and, based on the architecture and functional descriptions outlined in ITU-T Recommendation G.989.3, enables wavelength channel management within an NG- PON2 system.
FANWT-331Architecture & Technical Requirements for PON-based Mobile Backhaul networks

A number of Broadband Forum Technical Reports are dedicated to the description of an Ethernet-based architecture optimized for multi-service PON networks and technical requirements for PON systems catering to both residential and business customers.

Based on TR-221, this document extends the architecture and technical requirements to providing enhanced mobile backhaul functionality. These requirements cover system architecture, use cases, technical requirements as well as some implementation guideline, so as to for foster multi-vendor interoperability. The specifications in this document apply to both ITU-T and IEEE PON systems and focus on LTE and LTE advanced.

FANWT-385YANG model for management of ITU-T PON In Development.
FANWT-394YANG Models for Management of PON ONUs In Development.
FANWT-395NETCONF Management of PON ONUs Architecture Specification In Development.
FANWT-414PON NETCONF and YANG Data Model Interoperability Test Plan In Development.
FANMembers OnlyONU Conformance Test
In Development.
Common YANGWT-355 Amendment 1YANG Modules for FTTdp Management
This document defines YANG data models for the management interfaces to support FTTdp. These models are to enable interoperability for FTTdp management.
Common YANGWT-374Yang Models for Management of Systems in FTTdp Architecture This specification defines the Yang data models necessary for the management of ITU-T technology when used in FTTdp architectures.
Common YANGWT-393Persistent Management Agent Aggregator (PMAA) Management Model In Development.
InnovationSD-377Broadband Assured IP Services Source Document
Broadband Assured IP Services Source Document. Working documenbt for various uses cases and archtiectural documents
InnovationSD-389Broadband Assured IP Services Use Cases In Development.
PhyTxWT-347CPE SELT Equipment Testing and Operation Guidelines In Development.
PhyTxWT-338Reverse Power Feed (RPF) Test Plan 

This document specifies tests for the RPF functions of a DPU and the customer premises' Power Supply Equipment (PSE) either as a stand-alone device or as a function integrated in a FAST Network Termination.

Test cases are mainly specified with reference to ETSI TS 101 548 and BBF WT-301 requirements. Furthermore they are designed to ensure safe deployment of RPF equipment. Performance Test Plan 

In Development.

PhyTxWT-381Test Plan for Recommendation ITU-T G.9977 "Mitigation of Interference between DSL and PLC" 

ITU-T G.9977 Recommendation specifies functionality of a mechanism to mitigate interference caused by in-home powerline communication (PLC) devices to xDSL network termination. This mechanism allows service providers to detect possible interference, measure the effect of the interference, analyze the effect of the interference on the overall access system and, finally appropriately configure the parameters of DSL and PLC systems to minimize the effect of the interference on the user experience.

Issue 3 Ammendment 1
VDSL2 Performance Test Plan This document, as part of the Broadband Suite, provides a set of region specific performance requirements and test methods for VDSL2 modems implemented in accordance with ITU-T G.993.2 (Very high speed Digital Subscriber Line transceivers 2). Its key value is in the verification of performance such that network operators may deploy consistent and successful VDSL2 services in their networks.
Issue 3 Amendment 1
VDSL2 Functionality Test Plan Amentment 1 address updates in Annex Q.
Issue 2
Testing of G.993.5 Self-FEXT Cancellation (Vectoring) 

This Working Text is intended to provide an interoperability/performance/functionality test plan for ITU T Recommendation G.993.5 "Self-FEXT cancellation (vectoring) for use with VDSL2 transceivers". Deployment scenarios in the scope of this Working Text include deployments from the Central Office (CO) and Fiber-To-The-x (FTTx) remote deployments.

The scope of this Working Text also covers validation of the functionality of the Control, Inventory, and Reported parameters defined in ITU T Recommendation G.997.1 for the related G.993.5 functionality.

R&TMD-367Data Center Interconnect and other applications of EVPN - Tutorial In Development.
R&TMD-391Evolution to 5G Mobile Transport Networks - White Paper
In Development.
R&TWT-350 Phase 2Ethernet Services using BGP MPLS Based Ethernet VPNS (EVPN)
In Development.
R&TMD-339DWDM Integration Tutorial In Development.
R&TMD-366IP/Optical Integration - White Paper In Development.
SDN&NFVWT-384Cloud Central Office Reference Architectural Framework
A framework for cloud infrastructure in the Central Office (CO). It describes a Cloud platform for CO and define what virtualize network functions are necessary to run in the CO optimized to support Broadband 20/20 network functions as well as necessary interfaces. Publication slated end Jan 2018
SDN&NFVWT-411Definition of interfaces between Cloud CO Functional Modules This work will define the Interfaces between the Functional Modules in the Cloud CO Architectural Framework, as well as the Cloud CO Northbound API. Network Transport Protocols will be defined to carry the interface attributes. Furthermore the data models, schemas or APIs that are signaled across them will be defined as well. Existing Open Interface works, as described in Standards and Open Source work will be leveraged as much as possible. It is foreseen that this work will grow incrementally, based upon a series of Cloud CO Application Notes. 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.
SDN&NFVWT-412Test 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. 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, effectively validating the Cloud CO Application Note.
SDN&NFVWT-413Migration to SDN-Enabled Management and Control 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.
SDN&NFVWT-370FANS Overall Architecture and Requirements FANS Overall Architecture and Requirements investigates on the technical aspects associated with Fixed Access Network Sharing (FANS), which covers the Access Network and part of the Customer Network in case of PON architecture, addressing the typical infrastructures, topologies and deployment scenarios. It also provides security considerations necessary to support multi-operator access sharing. This project outlines technical aspects related to the migration of TR-101 and TR-178 based architectures toward a shared converged broadband access network architecture that supports the business drivers defined in SD-351. Besides multi-operator sharing scenarios, this project can be also appropriate for a network operator that wants to slice its access network to offer different services toward customers (e.g., for residential or enterprise markets) and wants to be able to manage it using a vertical organization structure. Furthermore, FANS Overall Architecture and Requirements is the ongoing pilot project for the upcoming activities related to Access Network Sharing interface(s) and SDN-Enabled FANS.
SDN&NFVWT-386FANS Access Network Sharing Interfaces
The scope of "FANS - Access Network Sharing Interfaces" is to extend the SD-351 "Stage 1 Analysis of Fixed Access Network Sharing (FANS)" document with a deeper analysis of the systems interfaces involved in information exchange between FANS architecture systems.
SDN&NFVWT-358Support for SDN in Access Network Nodes
WT-358 "Requirements for Support of SDN in Access Nodes" has two goals. The first goal is to define the requirements necessary to support SDN-based implementations for Access Nodes including FTTdp. This work is based on use cases identified in SD-313 and existing TRs such as TR-101 and TR-178 developed within BBF. A second goal is to identify gaps in current SDN protocols relative to the requirements identified and to communicate those gaps to the appropriate development organizations.
SDN&NFVWT-368YANG Models for ANs in SDN 

WT-368 is developing YANG models in support of WT-358 "Requirements for Support of SDN in Access Nodes." The project will document both the YANG models required for SDN-enabled Access Nodes and the relationships between those models and other YANG models used by ANs.

WWCSD-3735G Requirements and Enablers (jointly with Innovation)
WWCWT-378Hybrid Access Nodal Requirements

The solutions document for TR-348 - Hybrid Access Broadband Network Architecture for the home and business

WWCSD-406End-to-End Network Slicing This work investigates the concept of network slicing with respect to the BBF architecture. Network slicing is considered as a fundamental enabler to migrate “one architecture fits all” to the logical “network per service”. Network slicing will enable value creation for vertical segments that lack physical network infrastructure, by offering network and cloud resources
WWCSD-4075G Fixed Mobile Convergence 

The purpose of this work is to investigate common interfaces for the Access Network and Core Network, to support converged wireline-wireless networks that use the 5G core network. It studies the N1, N2 and N3 interfaces in order to provide detailed feedback to 3GPP in the context of 5G Fixed networks (as recommended by the joint 3GPP-BBF 2017 Workshop) and to facilititae 3GPP work in this area as swiftly as possible. 

This project will specify of a 5G Access Gateway Function (AGF) that adapts fixed access onto the 5G core, and then consider and specify several architectural deployment options as well as the underlying infrastructure sharing aspects. It will also devise strategies and develop specifications to address operator requirements for interworking of existing fixed access subscribers and deployed equipment into a 5G core.