Members Only:
Learn about the Forum
LinkedIn

Join

Join

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

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.

Working Groups

DESIGN
END TO END ARCHITECTURE

Mission Statement:
To oversee and coordinate all Access architecture and transport related technical work within the Forum.

Works in Progress:
  • IL-001: IPv6 Issues List
  • PD-200: Generic Requirements for Shared Media Ethernet Access
  • PD-203: Fixed Mobile Convergence Use Cases
  • WT# TITLEABSTRACT
    WT-134
    Policy Control Framework
    An architectural framework for policy control of DSL access networks.
    WT-145
    Multi-service Broadband Network Functional Modules and Architecture
    This working text provides reference architectures for multi-service broadband networks, defines high level network requirements, and specifies functional modules to meet those networks requirements. This WT also provides guidance to distribute these functional modules onto multi-service broadband network elements. Detailed broadband network nodal requirements will be specified in further working texts e.g. WT-178.
    WT-146
    Internet Protocol (IP) Sessions
    Numerous members of the service provider community have recently shown significant interest in migrating from a pure PPP access environment towards one with IP subscriber sessions for delivery of all IP services such as voice, video and high speed internet over a common data transport protocol. A number of factors are driving the interest for such a transition. For one, operators see a potential in simplifying their operational/user support complexity, as well as harmonizing network element functionality around the IP protocol. Operators running multiple access networks also view IP service delivery as the key lowest common denominator towards delivering common services in a converged network, where the PPP would be specific only to PSTN dial and DSL access segments. Given these motivations, the ability to transition to an IP user service delivery model suggests the adoption of a subscriber IP session construct in order to allow the service provider to handle each subscriber according to their individual service contract. This document provides the description of the construct and relevant IP node requirements.
    WT-177
    IPv6 in the context of TR-101
    This working text documents modifications to the TR101 architecture to permit dual stack IPv4 and IPv6 operation. As such WT177 extends the TR101 architecture to add IPv6 based services and applications to the suite of services already supported by TR101. In doing so, it presents the requirements for protocol interworking, and security for the network elements that are part the TR-101 architecture.
    WT-178
    Nodal Requirements for WT-145
    In development.
    WT-201
    Generic Requirements for P2P Ethernet Access
    TR-101 provided an Ethernet-based architecture that has become a global standard for triple-play deployments for residential and business customers that use DSL as the broadband access technology. However, much of TR-101's architecture specifications are access agnostic, and they are also being widely used today with other access technologies, especially native Ethernet Access over copper and single- and dual stranded fiber. This type of access is often referred to as Point-to-Point Ethernet to the X (as in Any) or P2P ETTX
    WT-203
    Interworking between Next Generation Fixed and 3GPP Wireless Access
    Since the introduction of IP enabled mobile devices the overlap of wireless and wireline technologies has emerged. As the widespread growth of mobile devices continues to increase at an enormous rate and become more ubiquitous, their services offered become transparent between both fixed and wireless access networks. Fixed Mobile Convergence is a technology trend impacting almost all telecommunication and Information industries providing the subscribers access to services anywhere anytime regardless of the Access network type they are connected to and providing the Service Providers with the flexibility to ensure transparency of services to the end user.
    WT-207
    TR147bis
    The purpose of this Working Text is to extend Layer 2 Control Mechanism to include additional access technologies, new devices and support new services.
    WT-242
    Migration Strategies to Transition from IPv4 to IPv6
    The WT presents an integrated view of transitioning the network from IPv4 to IPv6 operation. As such it documents strategies for dealing with transitional phases with dual stack v4/v6 being considered the interim target, and the eventual sunsetting of IPv4 as the ultimate goal. The WT will document strategies to deal with inconsistent deployment of dual stack, and strategies for dealing with IPv4 address space exhaustion.
    Technical Reports Available:
    TR-044, TR-046, TR-062, TR-064, TR-068, TR-069, TR-094, TR-101, TR-102, TR-126, TR-144, TR-147, TR-156 TR-167 TR-187
    BroadbandHomeTM
    BROADBANDHOME

    Mission Statement:
    Provide the Broadband industry with technical specifications that define the devices in the DSL broadband Home and eases the deployment and management of broadband services.

    Works in Progress:
  • OD-128: TR-069 Testing
  • PD-104: WT-104 Updates
  • PD-124i3: RG Requirements (QoS, Performance, FMC, IMS)
  • PD-140: TR-140 Updates
  • PD-143: TR-143 Version 2
  • PD-158: Email and Browser Data Model
  • PD-174: Management of Non TR-069 Devices
  • PD-181i2: New Object Data Model for GPON
  • PD-193: IPv6 updates to TR-069 related TRs
  • PD-194: Software Module Management
  • PD-199: Object Addressing Extensions
  • PD-232: Bulk Data Collection
  • IL-069: TR-069 Updates
  • IL-104: TR-104 Updates
  • IL-135: TR-135 Updates
  • IL-154: DM and DT Schema and Tool Issues
  • IL-157: TR-069 Common Managed Objects
  • IL-196: Updates to Femtocell Data Model
  • MD-154:TR-069 Data Model XML User Guide
  • WT#TITLEABSTRACT
    WT-069
    TR-069 Updates
    This document describes the CPE WAN Management Protocol, intended for communication between a CPE and Auto-Configuration Server (ACS). The CPE WAN Management Protocol defines a mechanism that encompasses secure auto-configuration of a CPE, and also incorporates other CPE management functions into a common framework. This document specifies the generic requirements of the management protocol methods which can be applied to any TR-069 CPE. Other documents specify the managed objects, or data models, for specific types of devices or services.
    WT-104
    TR-104 Update (VoIP)
    This Working Text extends the scope of TR-104 to: microPBX functionalities DECT interfaces a better supervision of VoIP It does not include the changes proposed in PD-149, since it focuses on V2IP (Videophony) which is out of the scope of this amendment1.
    WT-106 Amendment 5
    Data Model Template for TR-069-Enabled Devices
    WT-106a5 specifies data model guidelines to be followed by all TR-069-enabled devices. These guidelines include structural requirements for the data hierarchy, requirements for versioning of data models, and requirements for defining profiles.

    In addition, WT-106a5 defines an XML Schema that as far as possible embodies these guidelines, and which is used for defining all TR-069 data models. This makes data model definitions rigorous, and helps to reduce the danger that different implementations will interpret data model definitions in different ways.

    WT-106a5 also defines an XML Schema that allows a device to describe its supported TR-069 data models. This description is both specific and detailed, allowing an ACS to know exactly what is supported by the device, including any vendor-specific objects and parameters. Use of this Schema enhances interoperability and significantly eases the integration of new devices with an ACS.
    WT-123
    TR-069: Validation Testing Architecture
    Describes scope, architecture, and methodology for TR-069 interoperability testing between the CPE and ACS.
    WT-124 Issue 3
    RG Requirements (QoS, Performance, FMC, IMS)
    In development.
    WT-140 Amendement1
    TR-069 Data Model for Storage Service Enabled Devices
    In development.
    WT-143(New Version)
    Enabling Network Throughput Performance Tests and Statistical Monitoring
    In development.
    WT-155
    Requirements for GPON RG
    This Working Text specifies requirements for an GPON-RGW. The GPON-RG is a Routing Gateway with GPON uplink. The base requirements for the GPON-RG are those in WT-124. This document provides a general framework for the GPON-RG, refers to specific modules/requirements from WT-124, and specifies additional requirements not found in WT-124.
    WT-164
    Requirements for CPE in Support of Accessing Emergency Services
    This document provides requirements for mass market broadband CPE that are used either to initiate calls to emergency services, or that provide LLDP, DHCP server, or location server functionality to such devices.
    WT-181 Issue 2 Amendment 1
    Device Data Model for TR-069
    This Working Text defines version 2 of the TR-069 Device data model (Device:2). The Device:2 data model applies to all types of TR-069-enabled devices, including End Devices, Internet Gateway Devices, and other Network Infrastructure Devices. It represents a next generation evolution that supersedes both Device:1 and InternetGatewayDevice:1. However, legacy installations can continue to make use of the InternetGatewayDevice:1 and Device:1 data models, which are still valid.

    A cornerstone of the Device:2 data model is the interface stacking mechanism. Network interfaces and protocol layers are modeled as independent data objects that can be stacked, one on top of the other, into whatever configuration a device might support.
    WT-196 Amendment 1
    TR-069 Data Model for Storage Service Enabled Devices
    The purpose of this Working Text is to specify the Data Model for Femto Access Point (FAP) for the remote management purpose using the TR-069 CWMP within the scope defined in the following section. This Working Text defines FAPService as the container associated with the remote management of objects for FAP devices. CPE devices making use of a FAPService object MUST adhere to all of the data-hierarchy requirements defined in TR-106 [4]. In the context of TR-106 [4], the FAPService object is a service object.

    Technical Reports Available:
    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-094, TR-098 Amendment 1, TR-098 Amendment 2, TR-106 Amendment 2, TR-106 Amendment 3, TR-106 Amendment 4, TR-109, TR-110, TR-111, TR-122, TR-124, TR-124 Issue 2, TR-126, TR-131, TR-133, TR-135, TR-140 Amendment 1, TR-142, TR-142 Issue 2, TR-143 Corrigendum 1, TR-157, TR-157 Amendment 1, TR-157 Amendment 2, TR-181Issue 1 TR-181 Issue 2 TR-196

    Fiber Access Network
    Fiber Access Network

    Mission Statement:

    Works in Progress:
    WT#TITLEABSTRACT
    WT-156i2
    Using GPON Access in the context of TR-101
    TR-101 provided an Ethernet-based architecture that has become a global standard for triple-play deployments for residential and business customers that use DSL as the broadband access technology. However, many of TR-101's architecture specifications are access agnostic, and they are also being widely used today with other access technologies, especially FTTx / PON. This Working Text strengthens the TR-101 requirements as applied to GPON by providing more detailed and specific requirements. In order to reduce operational complexity and maximize equipment interoperability, a subset of the GPON's flexible configuration arrangements are specified here to facilitate the implementation of TR-101's VLAN architecture options. Other parts of this specification enable providers to take full advantage of GPON's abilities to achieve TR-101 requirements for multicast, Quality of Service (QoS), OAM and NMS.
    WT-167i2
    GPON-fed TR-101 Ethernet Access Node
    WT-167a1 provides architectural and network element requirements to allow the use of GPON to feed an access node as defined in TR-101. TR-101 provides triple play application support in an architecture that migrates from ATM to Ethernet access technology.
    WT-200
    EPON & TR-101
    WT-200 is intended to provide the architectural basis and technical requirements needed to successfully deploy EPON equipment within the Broadband Forum architecture, either independently or together with other access technologies.
    WT-247 Part 1
    ONT Conformance Test Plan
    This test plan describes a series of tests that may be used to verify whether particular GPON ONT implementation conforms to TR-156 functional requirements and adopts the configuration recommendations described in the ITU-T "OMCI Implementer's Guide".
    WT-247 Part 2
    OLT + ONT Conformance Test Plan
    This test plan describes a series of tests that may be used to verify whether particular GPON OLT implementation conforms to TR-156 functional requirements and adopts the configuration recommendations described in the ITU-T "OMCI Implementer's Guide".
    WT-255
    GPON Interoperability Test Plan
    This test plan describes a series of tests that may be used to verify whether particular, identified combinations of GPON OLT and GPON ONU implementation are interoperable when configured for the particular service deployment models described within TR-156. The prerequisite to go through WT-255 is to be compliant with WT-247 (part1 and part2).

    Technical Reports Available:

    IP/MPLS & Core
    IP/MPLS & Core

    Mission Statement:
    Provide the broadband and telecommunications industries with specifications for application and deployment of IP/MPLS technology in converged networks.

    Works in Progress:
    WT#TITLEABSTRACT
    WT-221
    Technical Specifications for MPLS Based Mobile Backhual Networks for LTE
    This document provides the technical specifications for the use of MPLS in flat mobile networks (e.g.LTE/EPC, HSPA+ flat, mobile WiMAX). MPLS technology is used to provide transport services for both control and user plane traffic of flat mobile networks. Different IP/MPLS solutions can be used to transport IP TNL of flat mobile networks: L2VPN MPLS (e.g. VPWS, VPLS) or L3VPN MPLS (e.g. BGP L3VPN, RSVP-TE LSP).
    WT-222
    Technical Specifications for MPLS Based Mobile Backhaul Networks for 2G & 3G
    This Working Text provides the technical specifications for the use of MPLS in Mobile Backhaul access and aggregation networks. It provides solutions for transport services for control and user plane traffic in mobile networks. It also provides a reference architecture for MPLS in Mobile Backhaul networks and includes specifications for the various deployment and transport scenarios that are depicted in this reference architecture.
    WT-223
    Requirements for MPLS Over Aggregated Interfaces
    This document defines a set of requirements for the use of MPLS over aggregated interfaces, such as IEEE 802.3ad Ethernet link aggregation [802.3ad] and Multilink PPP (MLPPP) [RFC1990]. This work item shall be known as MPLS over Aggregated Interfaces, or MPLSoAI.
    WT-224
    MPLS in Carrier Ethernet Networks
    In Development.
    WT-225
    Abstract Test Suite for ATM Services Over MPLS
    This document defines test procedures based on requirements for encapsulating Asynchronous Transfer Mode (ATM) over MPLS networks.
    WT-241
    Abstract Test Suite for Ethernet Services Over MPLS
    This document defines test procedures based on requirements for encapsulating Ethernet Services over MPLS networks.
    Technical Reports Available:
    TR-248 IP/MPLS Forum 23.0.0
    TEST
    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:
  • OD-139: VDSL2 Interoperability Plugfest Test Plan
  • OD-195: Test Plan for G.hn interoperability plugfests
  • PD-013: Interoperability Test Plan for ADSL2/ADSL2+ Plugfests
  • PD-137: ADSL2 and ADSL2+ Open Test Event Methodology
  • PD-256: G.hn Use Case Scenarios
  • MD-257: Vectoring
  • WT#TITLEABSTRACT
    WT-100 Issue 2
    ADSL2/ADSL2plus Performance Test Plan
    This document describes performance and interoperability test cases required for ADSL2/ADSL2plus systems consisting of DSLAMs and CPE modems.
    WT-105 Issue 2
    ADSL2/2plus Functionality Test Plan
    WT-105i2, as part of the Broadband Suite, provides a set of test methods to verify a significant subset of the transceiver functional requirements of ADSL2/ADSL2plus modems implemented in accordance with ITU-T G.992.3 "Asymmetric digital subscriber line transceivers 2 (ADSL2)" and ITU-T G.992.5 "Asymmetric Digital Subscriber Line (ADSL) transceivers – Extended bandwidth ADSL2 (ADSL2plus)" as well as physical layer OAM configuration and performance monitoring parameters defined in ITU-T G.997.1. Its key value is in the verification of transceiver functionalities and management parameters such that network operators may deploy interoperable and successful ADSL2/ADSL2plus services in their networks. WT-105i2 accompanies TR-100 "ADSL2/ADSL2plus Performance Test Plan" and TR-138 "Accuracy Tests for Test Parameters". TR-100 provides a set of region specific performance requirements and test methods for ADSL2/ADSL2plus modems implemented in accordance with ITU-T G.992.3 and G.992.5. TR-138 defines the tests for verification of the accuracy of the reported test (Physical Layer OAM configuration and performance monitoring) parameters defined in ITU T G.992.3, G.992.5 and G.997.1.
    WT-114 Issue 2
    VDSL2 Performance Test Plan
    WT-114i2 provides a set of performance requirements for VDSL2 (ITU-T G.993.2) modems. The contents includes the region specific requirements for North American, European and Japanese deployments which have been identified by the Broadband Forum as being of special importance for service operators’ deployment. .
    WT-115 Corrigendum 2
    VDSL2 Functionality Test Plan
    In Development.
    WT-115 Issue 2
    VDSL2 Functionality Test Plan
    WT-115i2, as part of the Broadband Suite, provides a set of test methods to verify a significant subset of the transceiver functional requirements of VDSL2 modems implemented in accordance with ITU-T G.993.2 (Very high speed Digital Subscriber Line transceivers 2) as well as physical layer OAM configuration and performance monitoring parameters defined in ITU-T G.997.1. Its key value is in the verification of transceiver functionalities and management parameters such that network operators may deploy interoperable and successful VDSL2 services in their networks. WT-115i2 accompanies TR-114 "VDSL2 Performance Test Plan" and TR-138 "Accuracy Tests For Test Parameters". TR-114 provides a set of region specific performance requirements and test methods for VDSL2 modems implemented in accordance with ITU-T G.993.2. TR-138 defines the tests for verification of the accuracy of the reported test (Physical Layer OAM configuration and performance monitoring) parameters defined in ITU-T G.993.2 and G.997.1.
    WT-127 Issue 2
    Splitter Testing
    This Working Text enables high quality delivery of triple play services by maximizing the interoperability of splitters and in-line filters with xDSL transceivers in an active, dynamic, telephony environment for POTS and ISDN. This includes POTS events such as on-hook, off-hook, ringing, and ring trip events and ISDN initialization events of similar nature.  This Working Text relates to TR-100 (ADSL2/ADSL2plus Performance Test Plan). and also to TR-114.
    WT-208
    Performance Test Plan for G.hn
    In Development.
    WT-209
    Functionality Test Plan for G.hn
    In Development.
    WT-249
    Testing of Multi-pair DSL Systems
    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-067v2, TR-105, TR-105 Corrigendum 1, TR-114, TR-114 Corrigendum 1, TR-114 Corrigendum 2, TR-115, TR-115 Corrigendum 1, TR-120, TR-127, TR-127 Corrigendum 1, TR-138 TR-138 Corrigendum 1 and TR-202

    OPERATE
    OPERATIONS & NETWORK MANAGEMENT

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

    Works in Progress:
  • IL-206: Object Models
  • PD-161: Test and Diagnostics for Remote Acess Nodes
  • PD-166: Truncated Packet Interception for Performance Monitoring
  • PD-168: IPTV Performance Monitoring and Diagnostics - Gap Analysis
  • PD-188: DSL Quality Suite
  • PD-205: GPON Management
  • PD-253: Testing VoP
  • MD-180: IPTV over DSL Anywhere WP
  • Element Management
  • Flow-Through Management
  • Test & Diagnostics
  • EMS-NMS Interfaces
  • WT#TITLEABSTRACT
    WT-160
    IPTV Performance Monitoring and Diagnostics
    The purpose of this Working Text (WT) is to address the requirements for performace monitoring and diagnostics for IPTV services provided over next generation multi-service broadband access networks. It considers what capabilities exsist to meet the requirements, identifies gaps, and defines new capabilities where necessary.
    WT-188
    DSL Quality Suite
    This Working Text aims to specify a framework for the management of DSL line quality. The objective is to obtain a common reference to allow homogeneous definition of further documents devoted to specific management aspects. Then, in the DSL Quality Suite (DQS), the building bricks for the effective management of all the quality and stability aspects of a DSL line are described, to be used both by Manufacturers and Service Providers. This framework document identifies a collection of Broadband Forum PDs, WTs, and TRs already existing or to be started, ranging from nomenclature aspects to requirements and guidelines, finishing with best practices from Service Providers.
    WT-197
    DQS: DSL Quality Management Tecniques & Nomenclature
    A number of different schemes and acronyms can be found in the literature (e.g. DSM Level x, DLM, etc.) for defining the techniques and strategies for monitoring and assuring DSL line stability and quality. Sometimes these names and conceptual approaches are also used by commercial products or within the operational work-flows of access networks. To ease the definition of any further WT under the DSL Quality Suite, the concept of DSL Quality Management (DQM) is introduced as the abstract capability of proactive and efficient control of the quality, stability and efficient exploitation of broadband lines.
    WT-198
    DQS: Requirements for DQM Ready Systems
    This working text provides an architecture that identifies the key functions of a DQM system and the external functions on which it depends and to which it delivers its output. The requirements for each functional block are given. Interfaces between the functional blocks and between the functional blocks and the external functions are identified. Existing standards that are relevant to these interfaces are indicated and the need for new standardized interfaces identified.cRequirements on the interfaces are listed. The definition of the above requirements may be supported by the description of some generic approaches to the stabilisation and performance maximization of DSL lines.
    WT-226
    XML Data Model for TR-169
    The purpose of this Working Text is to define an XML data model describing the management information transferred across an interface between an Element Management System (EMS) and a Network Management System (NMS) in support of DSL to Ethernet aggregation in Access Nodes. In so doing, the goal is to leverage the Multi-Technology Network Management (MTNM) 3.5 requirements and model defined in the TeleManagement Forum (TMF).
    WT-252
    DSL OM
    This document specifies a protocol-independent management model for ADSL, ADSL2, ADSL2plus and VDSL2 based on the parameters described in the ITU-T Recommendation G.997.1.
    WT-260
    DQS: DCF Functional & Performance test Plan
    In Development.
    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-176, TR-159, TR-165
  • Operations: TR-022
  • EMS/NMS: TR-030, TR-035, TR-041, TR-050, TR-051, TR-065, and TR-169,
  • SRV: TR-047, TR-052, TR-053 and TR-054