Members Only:
Join Broadband Forum Now Learn about the Forum
LinkedIn twitter.com/broadband_forum

Join

Join

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

Videos

Videos

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] [SDN in Broadband Networks]
[Service Innovation & Market Requirements]

BroadbandHome™

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-106: Certification Test Plan for CWMP Data Model Integrity
  • ID-181: CWMP Data Model Implementation Test Plan

  • MD-278: Managing Machine-to-Machine systems with CWMP - White Paper
  • MD-353: Best Practices for Deploying TR-069 - White Paper
  • MD-363: Home Network Diagnostics Mechanisms and Best Practices - Whitepaper

  • SD-069: Exploring CWMPv2
  • SD-279: TR-069 Proxy Management Implementation Guidelines
  • SD-282: Control Signaling Device Abstraction layer
  • SD-323: BBHome Work Items Related to WT-304
  • SD-324: TR-069 Protocol and Transport Separation
  • SD-333: Intra Customer Premises Network Measurements
  • SD-344: CWMP Root Data Model Transition Mechanisms
  • SD-354: New BBF CWMP Report Tool

  • IL-069: TR-069 Proposed Changes
  • IL-104: TR-104 Issues List
  • IL-106: TR-106 DM and DT Schema Proposed Changes
  • 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: BroadbandHome Publication Guidelines
  • OD-361: Program Requirements for BBF.069 Certification Program

  • WT# TITLE ABSTRACT
    WT-064
    Corrigendum 1
    LAN-Side DSL CPE Configuration Specification
    This corrigendum deprecates TR-064 which should only be used by legacy devices.
    WT-064
    Issue 2
    LAN-Side DSL CPE Configuration Specification

    This document describes a specific mechanism using UPnP Device Management BasicManagement:2 and ConfigurationManagement:2 to be used for CPE LAN-side configuration. This replaces the previous standard defined in TR-064 which is being deprecated in TR-064 Corrigendum 1.

    Updates for Issue 2 include:
    - Requirements to support UPnP Device Management BasicManagement:2 and ConfigurationManagement:2 for LAN-side CPE configuration
    - Usage examples
    - Changed title to remove "DSL". This mechanism applies to all CPE.

    WT-069
    Issue 2
    CPE WAN Management Protocol - Universal Service Platform (USP)
    In development.
    WT-131
    Amendment 1
    ACS Northbound Interface Requirements
    This document specifies requirements for the ACS Northbound Interface (NBI), which enables an integration of the Operational and Business Support Systems with the ACS to provision and manage devices. In this amendment we are adding new requirements related to M2M Service Layer for ACS Northbound Interface.
    WT-133
    Corrigendum 1
    TR-064 Extensions for Service Differentiation
    This corrigendum deprecates TR-133 which should only be used by legacy devices.
    WT-135
    Amendment 4
    Data Model for a TR-069 Enabled STB
    This is the next version of the STBService:1.4 Service Object definition which adds Service Monitoring of Events.
    WT-143
    Amendment 1 Corrigendum 1
    Enabling Network Throughput Performance Tests and Statistical Monitoring
    This corrigendum of TR-143 will fix minor technical and editorial corrections, such as:
      - Removing IGD:1.14 and Device:1.13 (which were mentioned but never published)
      - TestRespReplyFailureCount -> TestRespRecvTimeStamp and TestRespReplyTimeStamp. in A1.4 note
      - Fixing typos
    WT-157
    Amendment 10
    Component Objects for CWMP
    This working text is a new addendum to the latest issue of the specification. The new additions to the specification include enhancements to the Bulk Data component that adds capabilities to use HTTP/S transport capabilities.
    WT-181
    Issue 2
    Amendment 10
    Device Data Model for TR-069
    This amendment will add support for the MQTT protocol, bulk data collection over HTTP, scheduled and delayed reboots, dynamic DNS, and a new diagnostics data type to the Device:2 data model.
    WT-196
    Issue 2
    Amendment 1
    Femto Access Point Service Data Model
    This working text is a new addendum to the latest issue of the specification. The new additions to the specification includes new performance measurement parameters for HNB and HeNB nodes as well as configuration parameters for energy saving management for HeNB nodes.
    WT-330
    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-098 Amendment 2 Corrigendum 1, 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-124 Issue 4, 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 Amendment 1, 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-181 Issue 2 Amendment 8, 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:
    SD-357: Combined 3GPP and BBF Functions

    WT# TITLE ABSTRACT
    WT-317
    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.
    WT-321
    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.
    WT-328
    Virtual Business Gateway
    This Working Text specifies architecture and requirements for the virtual business gateway. The virtual business gateway architecture describes the migration of functionalities running on a business gateway to the network service provider's infrastructure for enabling network-based features and services. Such migration is expected to simplify the deployment and management of the network and business services.
    The purpose of this Working Text is to specify the virtual business gateway architecture as well as deployment scenarios. Such architecture would target different business premises sizes, e.g., small and medium enterprises (SMEs), campus, as well as single office and home offices (SOHO).
    WT-341
    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.
    WT-345
    Migrating to NFV in the context of WT-178
    Building on TR-101 and TR-178, WT-345 documents a set of architectures for broadband multi-service network, addressing infrastructures, topologies and deployment scenarios for Multi-Service Broadband Network Gateway (MS-BNG) with hierarchical instances realized as Virtualized Network Functions (VNF).

    Starting from such architectural models WT-345 defines the specific requirements necessary to support the addressed infrastructures, topologies and deployment scenarios, in order to fulfill the business requirements defined in TR-144. The main changes introduced in the WT-345 architectures compared to the TR-101 and TR-178 models are:
  • - Implications of scale out
  • - OAM and other Operational aspects
  • - Traffic management and QoS
  • WT-348
    Hybrid Access
    Bonding fixed broadband access and 3GPP access networks can enable service providers to offer higher throughput and better Wide Area Network (WAN) reliability solutions to their customers. In this bonding scenario, advanced traffic distribution mechanisms are needed. This Working Text defines the architectural requirements and solutions for the connections of premises by means of both fixed broadband (DSL, GPON, P2P Fiber) and 3GPP WAN interfaces.
    WT-359
    A Framework for Virtualization
    The purpose of this working text is to establish a framework to permit the Broadband Forum to effectively reference and specify systems such that the deployment of NFV (as defined by the ETSI NFV ISG) in Broadband Forum specified networks is facilitated.
    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-178, TR-187, TR-187 Issue 2, TR-203, TR-207, TR-242, TR-242 Issue 2, TR-254, TR-291, TR-296, TR-300, and TR-304

    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:
  • IL-280: WT-280 Issues List
  • IL-301: WT-301 Issues List

  • WT# TITLE ABSTRACT
    WT-280
    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.
    WT-301
    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.
    WT-331
    Architecture & Technical Requirements for PON-based Mobile Backhaul networks
    In development.
    WT-352
    Multi-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.

    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-305 Issue 3: MPLS Mobile Backhaul Evolution - 4G and Beyond - Tutorial
  • MD-325: Seamless MPLS for efficient broadband services delivery - Tutorial
  • MD-339: DWDM Integration Tutorial
  • MD-342: Energy Efficient Mobile Backhaul - White Paper
  • MD-343: Energy Efficient Mobile Backhaul - Tutorial

  • WT# TITLE ABSTRACT
    WT-221 Amendment 2
    Technical Specifications for MPLS in Mobile Backhaul Networks
    This provides a new amendment to TR-221 which includes specifications on timing (phase/frequency) synchronization, enhancements on scalability such as support of multi-area LSP signaling and BGP LSP routing. This amendment is applicable to address backhaul up through 3GPP Rel.11 and beyond.
    WT-319



    Part B



    Part C
    Achieving Packet Network Optimization using DWDM Interfaces

    Physically Separated/Logically Separated Model

    Physically separated/Logically Integrated

    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.

    WT-350
    Ethernet Services using BGP MPLS EVPN
    WT-350 is a new BBF project addressing architecture, requirements and use cases for Ethernet services implemented using BGP MPLS based Ethernet VPNs (EVPN) in an IP/MPLS network.

    Technical Reports Available:
    TR-221, TR-221 Amendment 1, TR-221 Corrigendum 1, TR-223, TR-224, TR-248/ATP-248 (IP/MPLS FORUM 23.0.0), TR-292, TR-293, TR-319 Base, and TR-319 Part A

    IP/MPLS Forum, MFA Forum, MPLS Forum, ATM Forum and Frame Relay Forum Specifications

    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:
  • ID-337: FAST Certification Test Plan

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

  • IL-114: WT-114 Issue 3 - Issues List
  • IL-115: WT-115 Issue 3 - Issues List
  • IL-208: WT-208 Issues List
  • IL-249: WT-249 Issue 2 - Issues List
  • IL-285: SD-285/WT-285 Issues List
  • IL-297: OD-297 Issues List
  • IL-335: OD-335 Issues List
  • IL-337: ID-337 Issues List
  • IL-346: WT-346 Issues List
  • IL-347: WT-347 Issues List
  • IL-362: OD-362 Issues List

  • OD-297: Interoperability Test Plan for G.Vector Plugfests
  • OD-334: Project Plan for G.fast & VDSL2 Testing for the FTTdp Architecture
  • OD-335: G.fast Interop Plugfest Test Plan
  • OD-362: Program Requirements for G.fast Certification Program

  • WT# TITLE ABSTRACT
    WT-114
    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.
    WT-115
    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).
    WT-208
    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.
    WT-249
    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.

    WT-338
    Reverse Power Feed (RPF) Test Plan
    In development.
    WT-346
    VDSL2 UPBO Guidelines
    This Working Text provides informative guidance on VDSL2 UPBO (upstream power back off) settings for non-vectored VDSL2, and vectored VDSL2 with and without legacy VDSL2 in the same cable.
    WT-347
    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-100 Issue 3, TR-100 Issue 3 Amendment 1, TR-105, TR-105 Corrigendum 1, TR-105 Corrigendum 2, TR-105 Issue 2, TR-105 Issue 2 Amendment 1, TR-105 Issue 2 Amendment 2, 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-138 Amendment 1, TR-202, TR-249, TR-249 Amendment 1, TR-273, TR-273 Corrigendum 1, TR-285, 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:
  • MD-311: Overview of Fiber Infrastructure Management Systems - White Paper

  • SD-332: Visualised Intelligent Network Platform for IP Network
  • SD-336: Operations and Management to support Customer Self-Install

  • OD-360: Best Current Practices for developing YANG models
  • WT# TITLE ABSTRACT
    WT-318
    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 (G.fast), 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.
    WT-349
    DSL Data Sharing
    This Working Text explores issues related to DSL data sharing and includes a standardized data model for DSL data sharing.
    WT-355
    YANG Modules for FTTdp Management
    This Working Text defines YANG data models for the management interfaces to support FTTdp. These models are to enable interoperability for FTTdp management.
    WT-356
    Alternate Management Path for Broadband
    This document describes a new method of managing broadband lines using an alternate data channel or path and particularly for diagnosing disconnections. For example, a smartphone can connect to a broadband modem or RG and access diagnostics data to troubleshoot a disconnected broadband line. This connection would be between the LAN side of the RG and the smartphone. The smartphone would then use an app or other system to relay this connection through the 3G/4G network back to a management server. Similarly, a neighboring WiFi connection or another data connection could be used instead of the smartphone relay. Re-configuration of the broadband modem or home network may also be performed over the alternate management path.
    Technical Reports Available:
  • TR-005, TR-015, TR-016, TR-022, TR-024, TR-027, TR-030, TR-034, TR-035, TR-041, TR-047, TR-050, TR-051, TR-052, TR-053, TR-054, TR-057, TR-063, TR-065, TR-066, TR-070, TR-090, TR-113, TR-128, TR-129, TR-130, TR-141, TR-159, TR-160, TR-165, TR-169, TR-176, TR-188, TR-188 Issue 2, TR-197, TR-197 Issue 2, TR-198, TR-198 Issue 2, TR-226, TR-252, TR-252 Issue 2, TR-252 Issue 3, TR-260, TR-260 Issue 2, TR-272, and TR-298
  • SDN in Broadband Networks Working Area

    Purpose and Scope:
    This work area of the Multi-Service Broadband 2.0 program focuses on introducing Software Defined Networking (SDN) concepts into MSB 2.0. The approach provides operators the opportunity to incrementally introduce SDN techniques of separated data plane and dynamic control plane with centralized control and new degrees of programmability while protecting existing investments. These techniques can improve management efficiency, enhance service flexibility, and provide numerous other benefits associated with SDN. In order to fully realize these benefits, it is important to align SDN functionality with the specific requirements and constraints associated with different elements in MSB 2.0.

    The scope of this Work Area (WA) will produce frameworks, requirements, interfaces, best practices, migrations plans, PoC, marketing related deliverables, etc. that leverage SDN where applicable within MSB 2.0. In all respects but particularly with regard to synergies and intersecting requirements that affect SDN and NFV technologies, the Work Area coordinates closely with other BBF activities to ensure consistent architecture, terminology and vision for the MSB 2.0 and other SDOs.

    Works in Progress:  
    WT# TITLE ABSTRACT
    WT-358
    Support 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.
     

    Service Innovation & Market Requirements

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

    Finalized Study Documents (Members Only Document Access):
    SD-302 "Framework for Cloud Services in Broadband Networks"
    SD-313 "High Level Requirements and Framework for SDN in Telecommunication Broadband Networks"
    SD-326 "Flexible Service Chaining"
    SD-340 "Stage 1 for introduction of Network Function Virtualization in MSBN"
    SD-340 "Stage 1 Analysis of Fixed Access Network Sharing"