 |
 |
|
 |
 |
|
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 | ||
|---|---|---|
| END TO END ARCHITECTURE | ||
| 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 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. | ||
| 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. | ||
| 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: | ||
| 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. | ||
| 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-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. | ||
| Describes scope, architecture, and methodology for TR-069 interoperability testing between the CPE and ACS. | ||
| In development. | ||
| In development. | ||
| In development. | ||
| 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. | ||
| 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 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. | ||
| 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: | ||
| IP/MPLS & Core | |||
|---|---|---|---|
| IP/MPLS & Core | |||
| Mission Statement: | |||
| WT# | TITLE | ABSTRACT | |
| 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). | |||
| 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. | |||
| 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: TR-248 IP/MPLS Forum 23.0.0 |
|||
| TEST | ||
|---|---|---|
| Metallic Transmission | ||
| Mission Statement: | ||
| WT# | TITLE | ABSTRACT |
| This document describes performance and interoperability test cases required for ADSL2/ADSL2plus systems consisting of DSLAMs and CPE modems. | ||
| 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-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. . | ||
| In Development. | ||
| 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. | ||
| 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. | ||
| In Development. | ||
| In Development. | ||
| In Development. | ||
|
Technical Reports Available: | ||
| OPERATE | ||
|---|---|---|
| OPERATIONS & NETWORK MANAGEMENT | ||
| Mission Statement: | ||
| WT# | TITLE | ABSTRACT |
| 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 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). | ||
| 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. | ||
| In Development. | ||
|
Technical Reports Available: |
||
© 1995-2010 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
