|
|  |
Technical
Work
|  |
|
|
Technical Work in Progress
There is a tremendous amount of technical work going on in the DSL 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 DSL 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.
DSL Forum members can access the actual Working Texts and Proposed Drafts using their username/password by clicking here.
Working Groups
Click here for work in progress bubble chart.
|
DESIGN |
|
ARCHITECTURE & TRANSPORT |
| Mission Statement:
To oversee and coordinate all architecture and transport related technical work within the Forum.
Works in Progress:
| | WT# | TITLE | ABSTRACT |
| WT-134 |
Policy Control Framework |
An architectural framework for policy control of DSL access networks. |
| WT-145 |
BB Arch Requirements | 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-147 |
Layer 2 Control | This document degines a Layer 2 Control Mechanism between a BNG and an Access Node in a multi-service architecture in order to perform QoS-related, service-related and subscriber-related operations. |
| WT-156 |
Using GPON Access in the Context of TR-101 | This document provides architectural and network
element requirements to allow the use of GPON access nodes in the TR-101 access architecture. TR-1010 provides
triplay play application support in an architecture that migrates from ATM access to Ethernet access technology. |
| WT-167 |
PON Fed DSLAMs | 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. |
| WT-177 |
IPv6 for TR-101 | In development. |
| WT-178 |
Nodal Requirements for WT-145 | In development. |
| WT-181 |
IPv6 for PPP | 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 |
|
OPERATE |
|
OPERATIONS & NETWORK MANAGEMENT |
| Mission Statement:
Provide recommendations for operational, network management, and process aspects of DSL-based broadband access.
Works in Progress:
PD-025: Test and Diagnostics for Next Generation Multi-Service Acess
PD-168: IPTV Performance Monitoring and Diagnostics - Gap Analysis
Element Management
Flow-Through Management
Test & Diagnostics
EMS-NMS Interfaces
|
| WT# | TITLE | ABSTRACT |
| WT-159 |
Management Framework for xDSL Bonding |
This DSL Forum Technical Report provides the management framework for xDSL bonding technology per ITU-T recommendations G.998.1 (ATM-based multi-pair bonding), G.998.2 (Ethernet-based multi-pair bonding) and G.998.3 (Multi-pair bonding using time-division inverse multiplexing). The document defines the required managed objects. The document is protocol independent, which means it does not refer to any particular management protocol between the Element Management System (EMS) and the Network Element (NE).
|
| 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-169 |
EMS to NMS INterface Function Requirements |
The purpose of this Working Text (WT) is to provide high level functional requirements describing an interface from an Element Management System (EMS) to a Network Management System (NMS) in support of DSL migration to Ethernet. This Working Text leverages the ATM aggregation to Ethernet requirements defined in TR-101, the TR-141 Network Element (NE)-EMS information model, the DSL EMS-NMS interface requirements defined in TR-130, and the ITU-T Rec. Q.840.1 EMS-NMS information model requirements and terminology to produce a set of Ethernet aggregation requirements that is consistent with the direction of international standards.
|
| WT-176 |
ADSL2Plus Profiles for IPTV |
This document contains recommended ADSL2plus profile parameter settings for use in the deployment of
IPTV over ADSL2plus. The parameter values were derived from the experiences of service providers and vendors
who have already tested, trialled and/or deployed IPTV over ADSL2plus and hence represent current industry best
practise.
|
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
Operations: TR-022
EMS/NMS: TR-030, TR-035, TR-041, TR-050, TR-051, and TR-065
SRV: TR-047, TR-052, TR-053 and TR-054
|
|
TEST |
|
TESTING & INTEROPERABILITY |
| Mission Statement:
To develop functional and performance test plans for cross-vendor interoperability.
Works in Progress:
PD-013: Interoperability Test Plan for ADSL2/ADSL2+ Plugfests
PD-019: Test Report Template for TR-067
PD-067: Issues List for TR-067
PD-100: Issues List for WT-100
PD-105: Issues List for WT-105
PD-114: Issues List for WT-114
PD-115: Issues List for WT-115
PD-118: Issues List for WT-118
PD-120: Issues List for WT-120
PD-137: ADSL2 and ADSL2+ Open Test Event Methodology
PD-138: Issues List for WT-138
PD-139: Interoperability Test Plan for VDSL2 Plugfests |
| WT# | TITLE | ABSTRACT |
| WT-105 |
G.992.3/5 (ADSL2/ADSL2+) Functionality Test Plan |
Defines the functionality test plan for testing functional compliance to ADSL2 (G.992.3) or ADSL2plus (G.992.5). |
| WT-114 |
G.VDSL2 Performance Test Plan |
The VDSL2 performance test plan provides the DSL industry with a suite of tests for North America and
European operation to ensure a consistent set of commercially available VDSL2 modems with known performance
capabilities.
|
| WT-115 |
G.VDSL2 Functionality Test Plan |
Contains the plan for testing functional compliance to VDSL2 (ITU-T G.993.2). |
| WT-127 |
Splitter Testing |
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. |
| WT-138 |
Accuracy Requirements for Test Parameters |
This Working Text provides accuracy requirements for parameters that instrument G.992.3 and G.992.5 PHY Layers. These parameters represent a subset of these parameters from G.997.1 that have been identified by the DSL Forum of special importance in DSL testing and operations support. |
|
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 and TR-120
|
|
DSLHomeTM |
|
DSLHOME-TECHNICAL |
| Mission Statement:
Provide the DSL industry technical specifications that define the devices in the DSL broadband Home and eases the deployment and management of broadband services.
Works in Progress:
PD-068: WT-068 Living List
PD-106: TR-069 living list
PD-128: Interoperability Test Plan for TR-069 Plugfests
PD-154: XML Data Model Definitions
PD-157: TR-069 Common Managed Objects
PD-158: Email and Browser Data Model
PD-174: Management of Non TR-069 Devices
|
| WT# | TITLE | ABSTRACT |
| WT-107 |
Internet Gateway Device Data Model Version 2 |
Defines version 2 of the Internet Gateway Device data-model for the CPE WAN management protocol (TR-069). |
| WT-123 |
TR-069: Validation Testing Architecture |
Describes scope, architecture, and methodology for TR-069 interoperability testing between the CPE and ACS. |
| WT-131 |
ACS Northbound Interface Requirements |
Provides requirements for a northbound interface via which operational support systems can communicate with a TR-069 ACS to manage CPE. |
| WT-132 |
ACS Northbound Interface Definition |
Defines a northbound interface via which
operational support and other back-end systems can integrate with any TR-069 ACS. This interface meets the requirements outlined in WT-131 and maps them to current web services technologies.
|
| WT-135 |
Data Model for a TR-069-enabled STB |
Provides a data model for a Set Top Box (STB) CPE as an extension to TR-069. |
| WT-140 |
DSLHome Remote Management Data Model: Network Attached Storage (NAS) |
This document defines a data model for a device that maintains a Storage Service as an extension to TR-069. |
| WT-143 |
Network Service Provider Initiated Throughput Performance Test |
This contribution is the first version of WT-143 "Network Service Provider Initiated Throughput Performance Test". It defines CPE throughput performance test mechanism using the framework established in TR-069. |
| WT-148 |
Scalability Extensions for CWMP |
This Working Text presents use cases and requirements for extensions to the CWMP protocol which will allow CPE and ACS to communicate more efficiently. |
| WT-157 |
Components Objects for CWMP |
This document defines objects for use in CWMP managed devises. The objects may exist at the top level of hierarchy, or in some cases within an existing object. The objects are intended for use in all CWMP Root Objects. The objects define varying functionality, diagnostics etc, that are agnostic to the type of devise. |
|
Technical Reports Available:
TR-044, TR-046, TR-062, TR-064,
TR-067 Issue 2,
TR-068v2,
TR-068 Issue 3,
TR-069,
TR-069 Amendment 1,
TR-094,
TR-098 Amendment 1,
TR-106 Amendment 1,
TR-109, TR-110, TR-111, TR-122,
TR-124,
TR-126,
TR-133,
TR-142
|
|
|
|
|
|
