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

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.
| BroadbandHomeTM | ||
|---|---|---|
| BROADBANDHOME | ||
| Mission Statement: | ||
| WT# | TITLE | ABSTRACT |
Issue 2 |
Issue 2 adds support of IPBX, DECT handsets. It also improves Voice Quality indicators and makes a clear split between LAN & WAN objects. | |
Issue 2 Corrigendum 1 |
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. WT-124 Issue 2 Corrigendum 1 updates TR-124 Issue 2 to reconcile DS-Lite requirements with WT-242. | |
Issue 3 |
This Working Text presents a superset of requirements for broadband Residential Gateway 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. | |
Amendment 3 |
This Working Text, Data Model for a TR-069 Enabled STB, defines the data model for remote management of Digital Television (IPTV or broadcast) functionality on Set Top Box (STB) devices via CWMP as defined in TR-069 and TR-106. It covers the data model for describing an STB device as well as rules regarding notifications on parameter value change. General use cases are also described. | |
Issue 2 |
In development. | |
| XML User Guide for TR-069 Data and Device Type models | ||
| 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. | ||
Issue 2 Amendment 5 |
This is the next version of the Device:2 data model. It contains items that have been removed from WT-181i2a4, namely the WiFi Antenna and IPsec objects. | |
| This Working Text presents an IPDR-based mechanism that allows Service Providers to efficiently collect a potentially large amount of data from their entire CPE population on a regular basis. This bulk data collection mechanism is built upon the IPDR standard as defined in TMForum, instead of the CWMP standard as defined in TR-069, as CWMP is designed to be a device management protocol instead of data collection protocol. So, by utilizing IPDR instead of CWMP the management plane is not polluted and the transfer of the data is more efficient. Devices supporting the IPDR-based bulk data collection mechanism will have the mechanism configured via CWMP. | ||
|
Technical Reports Available: [CWMP Table] | ||
| DESIGN | ||
|---|---|---|
| END TO END ARCHITECTURE | ||
Mission Statement: | ||
| WT# | TITLE | ABSTRACT |
| An architectural framework for policy control of wireline Broadband 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. | ||
| 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. | ||
| 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. | ||
| 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. | ||
| This WT defines a focused test plan for TR-101 based access nodes. | ||
| 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-144, TR-147, TR-156, TR-167, TR-177 and TR-187 | ||
| Fiber Access Network | ||
|---|---|---|
| Fiber Access Network | ||
| Mission Statement: | ||
| WT# | TITLE | ABSTRACT |
Issue 2 |
In development. | |
| This test plan describes a series of tests that may be used to verify whether particular, identified combinations of G-PON OLT and G-PON 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. | ||
| A growing number of Broadband Forum Technical Reports are dedicated to the description of an Ethernet-based architecture optimized for multi-service PON networks catering to both residential and business customers. WT-287 extends this architecture by providing enhanced optical-layer management requirements. These requirements cover system architecture, use cases, functional requirements, and interoperability requirements. The specifications in WT-287 apply to both ITU-T and IEEE PON systems. | ||
| In development. | ||
|
Technical Reports Available: | ||
| IP/MPLS & Core | ||
|---|---|---|
| IP/MPLS & Core | ||
| Mission Statement: | ||
| WT# | TITLE | ABSTRACT |
| 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. | ||
| In Development. | ||
| This document defines test procedures based on requirements for encapsulating Asynchronous Transfer Mode (ATM) over MPLS networks. | ||
| This document defines test procedures based on requirements for encapsulating Ethernet Services over MPLS networks. | ||
|
Technical Reports Available: | ||
| TEST | ||
|---|---|---|
| Metallic Transmission | ||
Mission Statement: | ||
| WT# | TITLE | ABSTRACT |
Issue 2 |
This document describes performance and interoperability test cases required for ADSL2/ADSL2plus systems consisting of DSLAMs and CPE modems. | |
Issue 2 Amendment 1 |
WT-105i2a1 defines functionality tests that SHALL be used in addition to TR-105 Issue 2 to verify that an ATU (ATU-C or ATU-R) is functionally compliant to ITU-T Recommendation G.992.3/G.992.5 (Asymmetric Digital Subscriber Line/Extended bandwidth transceiver). | |
Issue 2 |
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. | |
Issue 2 |
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. | |
Issue 2 Amendment 1 |
In development. | |
| In Development. | ||
| This Working Text is intended to provide an interoperability test plan for Multi-pair Systems. Deployment scenarios in the scope of this Working Text include deployments from the Central Office (CO) and Fiber-to-the-x (FTTx) remote deployments. | ||
| This working text provides testing methodology of multiport xDSL systems which use pair bonding protocols, such as ITU g.998.x, to create an aggregate bandwidth pipe, approximately equal to the sum of the individual links bandwidth. | ||
| This test plan facilitates Metallic Line Testing functionalities (MELT) according to ITU-T G.996.2 when implemented on xDSL ports as described in ITU-T recommendations G.992.3 (ADSL2), G.992.5 (ADSL2plus), G.993.2 (VDSL2) and G.991.2 (SHDSL). The test plan includes the validation of MELT functions (test parameters) and its defined accuracies according to G.996.2 Annex E (MELT-PMD) and F (MELT-P) in combination with xDSL operation. Additionally it focuses on xDSL specific tests and stability criteria in combination with MELT functions and the impact of MELT procedures on xDSL transmission. | ||
|
Technical Reports Available: | ||
| OPERATE | ||
|---|---|---|
| OPERATIONS & NETWORK MANAGEMENT | ||
| Mission Statement: | ||
| WT# | TITLE | ABSTRACT |
| TR-141 issue 2 is a protocol-independent management model addressing Access Nodes that support either TR-101 or TR-156 requirements. | ||
Issue 2 |
In the light of Broadband as tomorrow's universal means for communications and a multitude of other services, it is an unavoidable need to tackle the issue of DSL stability and quality by means of advanced and efficient techniques. As the penetration of broadband increases and the related service offers become more and more structured, such techniques represents a tool (or tools) of utmost importance. This is to guarantee overall service quality and performance to customers as well as consolidate broadband as a main service-enabling network platform for Service Providers.
This Working Text contains the framework for a DSL Quality Suite (DQS) intended as a collection of Broadband Forum documents focused on the management of the quality and stability of DSL lines. | |
| 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. | ||
Issue 2 |
WT-198i2 is a component of the DQS (DSL Quality Suite) which is an ongoing initiative of the Broadband Forum to identify the building blocks (reference features and tools, equipment and system requirements, network strategies and practices) to be used by manufacturers and Service Providers to develop solutions that enable pro-active and efficient maintenance of broadband lines and services.
DSL Quality Management (DQM) encompasses a range of techniques that seek to monitor, analyse and improve performance and/or stability of a DSL line or a group of DSL lines. | |
| 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. | ||
| 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. The model is based on an earlier model specified in Broadband Forum TR-129 with the configuration part of the model replaced by the Vector of Profiles model specified in TR-165 and the extension of the model to include new parameters defined in a more recent version of G.997.1. Parameters are also included from G,997.1 Amendment 1 for the management of retransmission and vectoring. | ||
| This is issue 2 of the Working Text that specifies functional and performance tests for the Data Collection Function defined in WT-198 and is aimed to help the verification and maturing of DCF implementations. This is of great importance for Operators in order to improve their DQM strategies introducing this advanced collection capabilities in their networks. | ||
| WT-272 contains a gap analysis to compare BBF TR-252 xDSL management requirements with TeleManagement Forum (TMF) xDSL management requirements. The results of the gap analysis will be cooperatively worked with the TMF to effect industry alignment. In so doing, the goal is to leverage the Multi-Technology Network Management (MTNM) 3.5 requirements and propose enhancements to the Layered and Performance Parameters defined in the TMF. | ||
|
Technical Reports Available: TR-141, TR-159, TR-165, TR-176 and TR-252 |
||
© 1995-2012 The Broadband Forum. All rights reserved.
48377 Fremont Boulevard, #117, Fremont, CA 94538 USA | Tel: +1.510.492.4020 | Email: Info@Broadband-Forum.org
Managed by AMS