 |
|
 |
|
Join
Forge tech specs, share best practices & drive the broadband market.
Join the Broadband Forum now.
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.
- Work in Progress For Members Only (WT/PD Document Index, Balloting Info, Bubble Chart, Templates and Forms)
Working Groups
| DESIGN | ||
|---|---|---|
| ARCHITECTURE & TRANSPORT | ||
| Mission Statement: | ||
| WT# | TITLE | ABSTRACT |
| An architectural framework for policy control of DSL access networks. | ||
| 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. | ||
| 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. | ||
| This working text provides architectural and network element requirements to allow the use of a GPON ONU as an access node defined in TR-101. TR-101 provides triple play application support in an architecture that migrates from ATM access to Ethernet access technology. | ||
| This Working Text presents a Broadband Forum access network architecture that enables operators to migrate to IPv6. It is built upon Broadband Forum TR-101, which describes a popular and successful Broadband Forum architecture for supporting Ethernet-based DSL aggregation. This document extends the TR-101 architecture to enable IPv6-based services and applications. In doing so, it presents the requirements for protocol interworking, multicast and security for the network elements that are part the TR-101 architecture. | ||
| In development. | ||
| This Working Text extends the Broadband Forum architectures established in TR-59 and TR-101 to provide IPv6 service with minimal change. WT-187 builds on the capabilities of existing protocols such as the Point-to-Point Protocol (PPP) and Layer 2 Tunneling Protocol (L2TPv2) to provide an overlay IPv6 service in addition to today s IPv4 service. | ||
| In development. | ||
| 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 | ||
| 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. | ||
| The purpose of this Working Text is to extend Layer 2 Control Mechanism to include additional access technologies, new devices and support new services. | ||
| In development. | ||
| In development. | ||
|
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 | ||
| BroadbandHomeTM | ||
|---|---|---|
| BROADBANDHOME | ||
| Mission Statement: | ||
| WT# | TITLE | ABSTRACT |
| 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. | ||
| In development. | ||
| Describes scope, architecture, and methodology for TR-069 interoperability testing between the CPE and ACS. | ||
| In development. | ||
| In development. | ||
| In development. | ||
| This document describes how an ACS can remotely configure, troubleshoot, and manage a PON ONT with layer 3 capabilities using TR-069. | ||
| 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. | ||
| The purpose of WT-157 is to provide Component Objects for CWMP. A Component Object is defined as an object and their contained parameters intended for use in any applicable CWMP root data model (both Device and InternetGatewayDevice). The object(s) may reside at the top level or an appropriate sub-object level. | ||
| 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. | ||
| This Working Text defines version 1 of the TR-069 [2] Device data model (Device:1). The Device:1 data model applies only to TR-069-enabled End Devices, and is not applicable to Internet Gateway Devices or to other Network Infrastructure Devices. TR-069-enabled Infrastructure Devices instead use the TR-098 InternetGatewayDevice data model. | ||
| This Working Text defines version 2 of the TR-069 [2] 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 non-backwards- compatible evolution from Device:1, as well as from InternetGatewayDevice:1, and is expected to obsolete both of these earlier data models. | ||
| This Working Text describes IPv6 requirements for a residential gateway. It is expected to provide requirements in a format so that they can be added to TR-124, as a revision to that document. All service providers are currently considering their strategy for migrating to IPv6. These requirements will be a critical part of describing the RGs needed to support that migration. | ||
|
Technical Reports Available: | ||
| OPERATE | ||
|---|---|---|
| OPERATIONS & NETWORK MANAGEMENT | ||
| Mission Statement: | ||
| WT# | TITLE | ABSTRACT |
| TR-129 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. This working text is for updating TR-129 with new parameters from G.997.1 (2009). | ||
| 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. | ||
| This WT is for updating TR-165 by adding new configuration parameters from G.997.1 (2009). TR-165 addresses the need for greater flexibility in setting DSL profiles by defining a vector of profiles. The DSL configuration parameters are divided into independent, but technically related, sets of parameters. Each parameter set defines a profile. The profiles are referenced from a vector of indices, each index identifying a unique profile. This allows a large number of profiles to be used without having to store huge quantities of profile data. | ||
| 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. | ||
| 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. | ||
| 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. | ||
| 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). | ||
|
Technical Reports Available: |
||
| TEST | ||
|---|---|---|
| TESTING & INTEROPERABILITY | ||
| Mission Statement: | ||
| WT# | TITLE | ABSTRACT |
| This document describes performance and interoperability test cases required for ADSL2/ADSL2plus systems consisting of DSLAMs and CPE modems. | ||
| Contains the theoretical values for insertion loss, impedance and delay for ADSL, ADSL2/2+ and VDSL2 loop definitions. Also describes detailed stationary and dynamic splitter testing and requirements in the presence of POTS (stationary and transient) and DSL test signals and conditions. Annexes describe the DSL and POTS signal models. | ||
| In Development. | ||
| In Development. | ||
|
Technical Reports Available: | ||
© 1995-2009 The Broadband Forum. All rights reserved. Terms of Use. Privacy Policy.
48377 Fremont Boulevard, #117, Fremont, CA 94538 USA | Tel: +1.510.492.4020 | Email: Info@Broadband-Forum.org
Managed by AMS
