Members Only:
Join Broadband Forum Now Learn about the Forum



Forge tech specs, share best practices & drive the broadband market. Join the Broadband Forum now. Join



Check out the latest Broadband
Forum videos
. Register

Technical Work in Progress

There is a tremendous amount of technical work going on in the Broadband Forum, and below is a brief overview of the current initiatives. As all Working Texts are works-in-progress, they are not available to the public. Once the work progresses and is approved by the Broadband Forum membership, the Working Text converts to a public Technical Report. We provide the abstracts below to simply give you a sense of the work.

Members Only:

Working Groups

[BroadbandHome] [End to End Architecture] [Fiber Access Network] [IP/MPLS & Core]
[Metallic Transmission] [Operations & Network Management] [SIMR]


Mission Statement:
Provide the Broadband industry with technical specifications that define broadband enabled customer devices and ease the deployment and management of broadband services.

Works in Progress:
  • ID-069 Issue 2: TR-069 Conformance Test Plan
  • ID-181: CWMP Data Model Implementation Test Plan

  • SD-069: Exploring CWMPv2
  • SD-143: Large Scale Automated Testing Using TR69/TR143
  • SD-266: Functional Requirements for Broadband Business Gateway Devices
  • SD-278: Managing Machine-Type Devices using TR-069
  • SD-279: TR-069 Proxy Management Implementation Guidelines
  • SD-282: Control Signaling Device Abstraction layer
  • SD-294: ZigBee Data Model for TR-069
  • SD-308: Home Network Service Diagnostics Use Cases and Requirements
  • SD-323: BBHome Work Items Related to WT-304
  • SD-324: TR-069 Protocol and Transport Separation
  • SD-329: HGI SHAL Requirements
  • SD-333: Intra Customer Premises Network Measurements
  • SD-344: CWMP Root Data Model Transition Mechanisms

  • IL-069: TR-069 Proposed Changes
  • IL-106: TR-106, DM and DT Schema Proposed Changes
  • IL-124: WT-124 Issue 4, Issues List
  • IL-135: Issues List for TR-135
  • IL-157: Proposed TR-069 Data Model Objects and Parameters
  • IL-181: Device:2 Data Model and TR-181 Issue 2 Proposed Changes

  • OD-148: CWMP Index Page Configuration File
  • OD-290: TR-069 XML Template and Process Guide

    Amendment 2
    Corrigendum 1
    Internet Gateway Device Data Model for TR-069
    In development.
    Issue 4
    Functional requirements for broadband gateway devices
    This Working Text specifies a superset of requirements for broadband Residential Gateway (RG) devices that are capable of supporting a full suite of voice, data, broadcast video, video on demand and two-way video applications in broadband networks.
    The requirements are grouped into modules. This means that an RG can be specified by listing the modules that the RG is expected to support. No single device is expected to support all modules.
    Issue 1
    Amendment 1
    Enabling Network Throughput Performance Tests and Statistical Monitoring
    WT-143a1 defines the CPE data model objects for Network Service Providers to initiate performance throughput tests and monitor data on the IP interface of a CPE using the Diagnostic mechanism defined in TR-069 Amendment 2.
    Amendment 9
    Component Objects for CWMP
    In development.
    Issue 2
    Amendment 8
    Device Data Model for TR-069
    WT-181i2a8 was created in order to publish several important new features, including the following:
    • Updates to WiFi objects to add associated device statistics, additional reports and retry limits, and QoS parameters.
    • A simpler and more general approach to modelling tunnels, plus GRE and MAP data models that make use of it.
    • A new LLDP data model, and extensions to the existing UPnP and new LLDP objects in support of HTIP.
    • Updates to the DSL objects to support G.997.1-2012 and G.997.1a1/2.
    • Updates to the objects to support G.9962.
    • A new PCP data model.
    Issue 2
    Amendment 9
    Device Data Model for TR-069
    In development.
    Issue 2
    Corrigendum 2
    Femto Access Point Service Data Model
    In development.
    TR-069 UPnP-DM Proxy Management Guidelines
    WT-330 defines implementation guidelines for proxy management using TR-069 Proxying the UPnP-DM Protocol. The proxy management architecture and solution in Annex J and Appendix I of TR-069 Amendment 5 define the Embedded Object Mechanism and Virtual CWMP Device Mechanism. WT-330 seeks to provide a detailed implementation guide to proxy management of UPnP DM.

    Technical Reports Available: [CWMP Table], ATP-069
    TR-044, TR-046, TR-062, TR-064, TR-067 Issue 2, TR-068 Issue 2, TR-068 Issue 3, TR-069, TR-069 Amendment 1, TR-069 Amendment 2, TR-069 Amendment 3, TR-069 Amendment 4, TR-069 Amendment 5, TR-094, TR-098 Amendment 1, TR-098 Amendment 2, TR-104, TR-104 Issue 2, TR-106 Amendment 2, TR-106 Amendment 3, TR-106 Amendment 4, TR-106 Amendment 5, TR-106 Amendment 6, TR-106 Amendment 7, TR-109, TR-110, TR-111, TR-122, TR-124, TR-124 Issue 2, TR-124 Issue 3, TR-126, TR-131, TR-133, TR-135, TR-135 Amendment 1, TR-135 Amendment 3, TR-140 Amendment 1, TR-142, TR-142 Issue 2, TR-143 Corrigendum 1, TR-154, TR-155, TR-157, TR-157 Amendment 1, TR-157 Amendment 2, TR-157 Amendment 3, TR-157 Amendment 5, TR-181 Issue 1, TR-181 Issue 2, TR-181 Issue 2 Amendment 2, TR-181 Issue 2 Amendment 5, TR-181 Issue 2 Amendment 6, TR-181 Issue 2 Amendment 7, TR-196, TR-196 Amendment 1, TR-196 Issue 2, TR-232 and TR-262

    End to End Architecture

    Mission Statement:
    Responsible for the end to end architecture and associated nodal requirements with respect to the native service layer and above.

    Works in Progress:

    Multi-service Broadband Network Architecture and Nodal Requirements
    Building on TR-144 and WT-145, WT-178 documents a set of architectures for broadband multi-service network, addressing typical infrastructures, topologies and deployment scenarios, and specifies associated nodal requirements.
    WT-242 Issue 2
    IPv6 Transition Mechanisms for Broadband Networks
    Issue 2 of this document introduces Mapping of Address and Port (MAP) technology and requirements. MAP is a unified stateless solution based on a static algorithmic mapping of an IPv4 address and a range of ports into an IPv6 address/prefix.
    Nodal Requirements for Converged Policy Management
    Operators that have both fixed and wireless access networks have the opportunity to consider converged solutions that provide optimization of the network infrastructure. The purpose of this project is to enhance the 3GPP PCC architecture and the BBF architecture in order to achieve the service provider's needs in this scenario.
    WT-300 defines business requirements and a Converged Policy Management Reference Architecture to support extension of the BBF specifications that facilitate convergence with the 3GPP Evolved Packet Core network based on the 3GPP PCC architecture and interfaces with extensions, as needed. The solution is being developed in collaboration with 3GPP.
    Broadband Access Service Attributes and Performance Metrics
    This project will specify a test architecture and framework to enable standards-based testing and reporting of broadband performance. It will include: definitions of network segments under test; tests and methodologies appropriate for each segment; recommended testing intervals for network performance characterization; support of tests that span multiple operator networks; a standard method for quantifying and comparing access services; and tools to enable communication of service attributes and performance requirements between service providers, application providers and customers.
    Network Enhanced Residential Gateway
    This Working Text specifies the Network Enhanced Residential Gateway (NERG) architecture. This architecture consists in shifting some of the functionalities of a residential gateway to the operator's network, for enabling network based features. The aim is to facilitate the deployment, maintenance and evolution of both existing and new capabilities without adding complexity to the RG and/or the home network.
    Public WiFi Access
    Since the introduction of mobile devices that include Wi-Fi, there has been an increasing interest in improving Broadband Forum's multi-service broadband architecture to incorporate the public Wi-Fi access. WT-321 addresses use cases, physical and logical architecture and functional and/or nodal requirements for public Wi-Fi access capabilities that are used nomadically as part of a broadband network. WT-321 builds on the work done in IETF's CAPWAP architecture and comes up with a new public Wi-Fi access network architecture.
    Virtual Business Gateway
    In development.
    Radius Attributes Catalog

    The purpose of this Working Text is to consolidate the existing BBF AAA work into a single concise catalog or information model for authentication, authorization and accounting functions within a BBF network.

    This Working Text will also provide the opportunity to standardize common vendor specific implementations into standard attributes.
    Migrating to NFV in the context of WT-178
    In development.
    Technical Reports Available:
    TR-044, TR-046, TR-062, TR-064, TR-068, TR-069, TR-094, TR-101, TR-101 Issue 2, TR-102, TR-126, TR-134, TR-134 Corrigendum 1, TR-144, TR-145, TR-146, TR-147, TR-156, TR-167, TR-177, TR-187, TR-187 Issue 2, TR-203, TR-207, TR-242, TR-254, TR-291 and TR-296

    Fiber Access Network

    Mission Statement:
    To develop technical specifications related to Optical Access Nodes and associated test plans for conformance and inter-vendors interoperability.

    Works in Progress:
  • SD-331: Architecture & Technical Requirements for PON-based Mobile Backhaul networks

  • IL-280: WT-280 Issues List
  • IL-301: WT-301 Issues List

  • OD-274: Input to EU on BB CoC
  • OD-281: EU Code of Conduct on Energy Consumption of Broadband Equipment

    ITU-T PON in the context of TR-178
    WT-280 focuses on GPON systems in an unbundled services environment that addresses requirements not covered by TR-156. TR-156 and WT-247 address basic L2 GPON systems. There are "more complex" types of ONT and Service Providers have more complex requirements that need a reference in BBF GPON framework. ITU standards already cover these more complex functionalities from an OMCI point of view. What is missing are the architectural/functional requirements.
    Fiber to the
    Distribution point
    This Working Text defines a new node type, for use within the access network at the subscriber side fiber termination. This node provides a Distribution Point (DP) that supports one or more high-speed copper drops to individual subscribers. All aspects of the introduction of this node type into the network are considered and requirements are identified for the DP Unit (DPU) and all affected access section nodes.
    The requirements contained within this Working Text are defined within the framework of both the TR-101 and TR-144/145 architectures. The TR-101 architecture is required to support near term residential deployments while the TR-144/145 architecture is required for the evolution to a multi-service edge network that supports residential, business and wholesale deployments.

    Technical Reports Available: TR-247/ATP-247, ATP-247 Issue 2, ATP-247 Issue 3, TR-156 Issue 2, TR-156 Issue 3, TR-167 Issue 2, TR-200, TR-200 Corrigendum 1, TR-255, TR-287 and TR-309

    IP/MPLS & Core

    Mission Statement:
    Responsible for edge to edge architecture and associated nodal requirements with respect to the infrastructure protocols that support the native service layer.

    Works in Progress:
  • MD-339: Content Aware Network Use Case - White Paper
  • MD-342: Energy Efficient Mobile Backhaul - White Paper
  • MD-343: Energy Efficient Mobile Backhaul - Tutorial

    Corrigendum 1
    Technical Specifications for MPLS in Mobile Backhaul Networks
    This corrigendum provides updates to TR-221 including terminology, corrections to MS-PW OAM, and it also amends TR-221 with L3VPN OAM and BGP LSP routing capability.
    Technical Specification for MPLS in Carrier Ethernet Networks
    Carrier Ethernet services are being used in Broadband access networks, enterprise networks and backhaul networks. This document provides technical architecture and equipment requirements implementing the specified Ethernet services with an MPLS network. By specifying a common technical architecture, common equipment requirements and common set of feature options, this document promotes multi-vendor interoperability. This document may be used as a basis for conformance testing.
    Abstract Test Suite For MPLS OAM
    WT-292 defines testing and validation procedures based on requirements for MPLS OAM in MPLS Mobile Backhaul Networks as specified in TR-221.
    Energy Efficient Mobile Backhaul
    Create nodal requirements for energy efficiency focusing on the TR-221 Architecture, addressing Ethernet, TDM, ATM and IP Services for mobile backhaul.
    Achieving Packet Network Optimization using DWDM Interfaces
    Network Providers have identified the potential to better integrate their packet and DWDM/optical networks to address growing network capacity demands, increase efficiency and reduce OPEX. This document specifically addresses Packet and DWDM/Optical integration.
    Integrated packet/optical networks and network node equipment are based on a variety of protocols and functionalities specifications (e.g., physical layer, data plane, control plane, management plane, etc.) from different SDOs. This document identifies the set of specifications that are necessary for implementation of integrated packet optical networking equipment. The working text is aimed at fostering the development of interoperable solutions from multiple vendors to be the benefit of consumers and suppliers of broadband services alike.

    Technical Reports Available:
    TR-221, TR-221 Amendment 1, TR-223 and TR-248/ATP-248 (IP/MPLS FORUM 23.0.0)

    Metallic Transmission

    Mission Statement:
    To develop functional and performance test plans for cross-vendor interoperability of broadband transmission technologies that use metallic media.

    Works in Progress:
  • SD-285: Copper Transmission Models for Testing above 30 MHz

  • IL-100: WT-100 Issue 3 - Issues List
  • IL-114: WT-114 Issue 3 - Issues List
  • IL-115: WT-115 Issue 3 - Issues List
  • IL-138: WT-138 Amendment 1 - Issues List
  • IL-208: WT-208 Issues List
  • IL-249: WT-249 Issue 2 - Issues List
  • IL-281: OD-281 Issues List
  • IL-285: SD-285/WT-285 Issues List
  • IL-297: OD-297 Issues List
  • IL-335: OD-335 Issues List
  • IL-346: WT-346 Issues List

  • OD-281: EU Code of Conduct on Energy Consumption of Broadband Equipment
  • OD-297: Interoperability Test Plan for G.Vector Plugfests
  • OD-334: Project Plan for & VDSL2 Testing for the FTTdp Architecture
  • OD-335: Interop Plugfest Test Plan

    Issue 3
    ADSL2/ADSL2plus Performance Test Plan
    WT-100 Issue 3 describes performance and interoperability test cases required for ADSL2/ADSL2plus systems consisting of DSLAMs and CPE modems.
    Issue 3
    VDSL2 Performance Test Plan
    This Broadband Forum Working Text, WT-114i3, 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
    VDSL2 Functionality Test Plan
    This test plan describes a series of functionality tests that are used to verify that a VTU (VTU-O or VTU-R) is functionally compliant to ITU-T Recommendation G.993.2 (Very High Speed Subscriber Line transceiver 2). A VTU is functionally compliant to this test plan if it implements correctly the required functions and features of the ITU-T Recommendation G.993.2. In addition the VTU is functionally compliant if it implements the optional feature as specified in the standard. WT-115i3 also defines tests for some of the VDSL2 optional features such as dual latency and Seamless Rate Adaptation (SRA).
    Amendment 1
    Accuracy Tests for Test Parameters
    WT-138a1 provides accuracy tests for test parameters that are defined in the ITU-T Physical Layer Recommendations G.992.3 (ADSL2 transceivers), G.992.5 (ADSL2plus transceivers) and G.993.2 (VDSL2 transceivers), and that are also listed in G.997.1 (Physical Layer Operations, Administration, and Maintenance). The test parameters covered in this document represent the subset of the transceiver test parameters from G.997.1 that both have accuracy requirements defined in G.992.3 and G.993.2 and which have been identified by the Broadband Forum as being of special importance in DSL testing and operations support.
    Performance Test Plan For In-premises Powerline Communications systems

    This document is aimed to provide industry, operators, and test labs with a well defined test bed and an established set of tests that enable a performance comparison between powerline products and technologies that can be independently verified.

    Testing of wireline home-network transceivers from different vendors or technologies should be possible in a repeatable and reproducible fashion.
    Amendment 1
    Testing of G.993.5 Self-FEXT Cancellation (Vectoring)
    TR-249 Issue 1 provides a set of performance and functional requirements for vectoring capable VDSL2 implementations according to ITU T Recommendation G.993.5. This Amendment to TR-249 Issue 1 enhances the performance targets defined in TR-249 Issue 1 (expressed as "SHOULD") into requirements (expressed as "SHALL").
    Issue 2
    Testing of G.993.5 Self-FEXT Cancellation (Vectoring)
    In development.
    Corrigendum 1
    Testing of Bonded, Multi-Pair xDSL Systems
    This document contains corrections to TR-273 Issue 1 that are critical to the proper implementation of testing based on the technical report. These corrections include updates to the test procedures and test metrics. No new tests or test procedures have been included in this corrigenda document.
    Broadband Copper Cable Models

    This Working Text is focused on the subject of cable models for physical layer testing of the Access Network. It provides complete cable models focusing on the frequency range extending above 30 MHz. These models are complete. A cable model for the Access Network is complete when it presents a precise and unambiguous specification of the network characteristics of the cable across the total extent from the Distribution Point Unit (DPU) to the Network Interface Device (NID) located at the end subscriber. The cable over this total extent is termed the Loop End Access Network - The Final Drop.

    The intent of this Working Text is to provide those complete models which can be used in Broadband Forum Working Texts/Test Reports for interoperability and performance testing of and FTTdp Physical Layer 1 facilities.
    WT-337 System Test Plan
    In development.
    Reverse Power Feed (RPF) Test Plan
    In development.
    VDSL2 UPBO Guidelines
    In Development.
    CPE SELT Equipment Testing and Operation Guidelines
    In Development.

    Technical Reports Available:
    TR-023, TR-026, TR-029, TR-031, TR-033, TR-045, TR-048, TR-049, TR-055, TR-060, TR-060 Issue 2, TR-067, TR-067 Issue 2, TR-100, TR-100 Corrigendum 1, TR-100 Issue 2, TR-105, TR-105 Corrigendum 1, TR-105 Corrigendum 2, TR-105 Issue 2, TR-105 Issue 2 Amendment 1, TR-114, TR-114 Corrigendum 1, TR-114 Corrigendum 2, TR-114 Issue 2, TR-115, TR-115 Corrigendum 1, TR-115 Corrigendum 2, TR-115 Issue 2, TR-115 Issue 2 Amendment 1, TR-115 Issue 2 Corrigendum 1, TR-115 Issue 2 Corrigendum 2, TR-120, TR-127, TR-127 Corrigendum 1, TR-127 Issue 2, TR-127 Issue 2 Corrigendum 1, TR-138, TR-138 Corrigendum 1, TR-202, TR-249, TR-273, TR-286, TR-286 Amendment 1, and TR-320

    Operations & Network Management

    Mission Statement:
    Provide recommendations for operational, network management, and process aspects of broadband access networks.

    Works in Progress:
  • SD-332: Visualised Intelligent Network Platform for IP Network
  • SD-336: Operations and Management to support Customer Self-Install
    WT-141 Issue 2
    Protocol Independent Management Model for Access Nodes Supporting TR-101
    TR-141 Issue 2 is a protocol-independent management model addressing Access Nodes that support either TR-101 or TR-156 requirements.
    WT-197 Issue 2 Corrigendum 1
    DQS: DSL Quality Management Techniques & Nomenclature
    In Development.
    G-PON and XG-PON1 Management
    This Broadband Forum Working Text provides a management model to meet the requirements in TR-156 and related ITU-T recommendations. It derives from TR-156 the relevant managed objects and arranges them in the form of logical sets, called managed entities. This working text then defines the MIB of the OLT and then facilitate the integration of new technologies in operators IS.
    Fiber Infrastructure Management System: Architecture and Requirements
    Broadband Forum Technical Reports address an Ethernet-based architecture optimized for multi-service Passive Optical Network (PON) deployments focused on both residential and business customers. WT-311 addresses architecture and functional requirements of emerging intelligent Optical Distribution Network (ODN) systems that form the physical plant layer of PONs. These requirements cover system architecture, layer functional requirements, and interfaces and/or data models for interoperability with service provider operations support systems (OSS). The specifications in WT-311 apply to PON systems that are specified both in ITU-T G-Series Recommendations and IEEE 802-Series standards.
    GPON Access Node Management Requirements
    It is assumed that at an Access Node in the network there is equipment that implements the functionality defined in TR-101 and TR-156 with the access technology functionality defined in the G.984 series of Recommendations. This Working Text contains the Service Providers' requirements for the management of this equipment in order to deliver service activation, fault diagnosis and performance monitoring. The starting point is general and specific operational process requirements. Then use cases are provided to support these requirements. The use cases are combined where appropriate and then used to generate the management requirements. The management requirements detail specific management parameters or entities that are required to be available at the NMS/EMS interface and the necessary supporting operations.
    Management Architecture and Requirements for FttDP
    The architecture and requirements for FttDP are the subject of WT-301. Although there are similarities of FttDP with other types of concatenated fibre and copper access systems, e.g. FttCab, GPON ONUs there are also some very different aspects, e.g. Reverse Power Feeding, small node size, new copper technology (, low power consumption, etc. There are also some functions in a FttDP node that do not exist in other systems. These differences impact the management requirements for the FttDP node. This Working Text addresses these impacts; it specifies the management architecture and requirements and the management models for the component parts of the FttDP architecture.
    Technical Reports Available:
  • Phy: TR-005, TR-015, TR-016, TR-024, TR-027, TR-034, TR-057, TR-063, TR-066, TR-070, TR-090, TR-113, TR-128, TR-129, TR-130, TR-141, TR-159, TR-165, TR-176, TR-252, TR-252 Issue 2, TR-252 Issue 3 and TR-272
  • Operations: TR-022
  • EMS/NMS: TR-030, TR-035, TR-041, TR-050, TR-051, TR-065, TR-169 and TR-226
  • SRV: TR-047, TR-052, TR-053, TR-054, TR-160, TR-188, TR-188 Issue 2, TR-197, TR-198, TR-198 Issue 2, TR-260,
    TR-260 Issue 2 and TR-298
  • Service Innovation & Market Requirements

    Mission Statement:
    Drive BBF medium-to-long term work directions and requirements in order to lead innovation in broadband.

    Works in Progress:

  • IL-340: SD-340 Issues List

    High Level Requirements and Framework for SDN in Telecommunication Broadband Networks
    Software Defined Networking (SDN) may create a long-term evolution within telecommunication broadband networks. By incrementally introducing SDN concepts, without rebuilding the whole network, operators have the opportunity to migrate to SDN while protecting existing investment. This project will examine some deployment scenarios including where only some of the network equipments would support SDN functionalities, as well as possibility of supporting SDN capabilities by upgrading software only.
    Per the mission of SIMR WG, SD-313 will include recommendations for follow-on Broadband Forum work regarding SDN.
    Flexible Service Chaining

    In order to support business and residential, fixed and mobile, wholesale and retail markets, TR-144 described various requirements including the need for network interconnection standards for broadband access, QoS support, Bandwidth on demand, increased overall bandwidth, higher network reliability and availability.

    New ways of defining services are required to keep up with market needs, seeking more flexibility in service deployment, faster service feature delivery, increased automation, elastic service bursting, etc.

    Service chaining allows complex services to be created out of simpler service-enabling elements through composition, e.g. stringing service points together while possibly constraining the corresponding data path.

    The output of this project will provide guidance to BBF's Technical and Marketing Committees on the work needed to bring flexible service chaining concepts to the level of detail necessary to define broadband network element requirements for implementation. This Study Document will also provide a reference for other service chaining standards organizations.

    Stage 1 for introduction of Network Function Virtualization in MSBN
    In development.

    Finalized Study Documents (Members Only Document Access):
    SD-302 "Framework for Cloud Services in Broadband Networks"