Management Framework for xDSL Bonding WT-157 Version 1.2Version 1.1
DSL Forum
Working Text
WT-157
Draft
Version 1.21.1
Management Framework for xDSL Bonding
28 February 2007
Produced by
Operations and Network Management Working Group
Editors: Moti Morgenstern, ECI Telecom
Edward Beili, Actelis Networks
Narendranath Nair, Wipro
Chair: Peter Adams, BT
Notice
The DSL Forum is a non-profit corporation organized to create guidelines for DSL network system development and deployment. This Working Text is a draft, and has not been approved by members of the Forum. Even if approved, this document is not binding on the DSL Forum, any of its members, or any developer or service provider. The document is subject to change. This document is protected by copyright by the DSL Forum and is for use by DSL Forum members only. Advance written permission by the DSL Forum is required for distribution of this document in its entirety or in portions outside the DSL Forum.
Version History
Version Number / Version Date / Version Editor / ChangesVersion 1.0 / 15 December 200615-Dec-2006 / · M. Morgenstern, ECI
· Edward Beili, Actelis
· Naren Nair, Wipro / First draft
Version 1.1 / 15 December 200628-Feb-2007 / · M. Morgenstern, ECI
· Edward Beili, Actelis
· Naren Nair, Wipro / - Comments from Dec-2006 Atlanta meeting
1.2 / 06-Mar-2007 / Edward Beili, Actelis / - Comments form Mar-2007 Vancouver meeting
Technical comments or questions about this document SHOULD be directed to:
Editors: Moti Morgenstern
ECI Telecom
30 Hasivim St.
Petah-Tikva, 49517, Israel
TelPhone: +972-3-9266258
Email:
Edward Beili
Actelis Networks
25 Bazel St.
Petach-Tikva, 49103, Israel
TelPhone: +972-3-924-3491 x302
Email:
Narendranath Nair
Wipro Technologies, Keonics Electronics City,
Bangalore - 560 100, India
TelPhone: +91-80-28520408 Ext. 85338
Email:
Table of Contents
1 Purpose 7
2 Scope 7
2.1 Abbreviations 7
2.2 Conventions 8
3 References 8
4 xDSL Multi-pair Bonding Overview 9
5 Management Framework Structure 10
5.1 Management Model 10
5.2 Containment 10
5.3 Managed Objects 11
6 Common Section 15
6.1 Multi-Pair Bonding Group and xDSL Bearer Channel Identification 16
6.2 xDSL Lines in Group 16
7 ATM-Based Multi-Pair Bonding Specific Section 16
7.1 ATM-Based Multi-Pair Bonding Group Object 16
7.1.1 ATM-Based Multi-Pair Bonding Group Configuration Parameters 16
7.1.2 ATM-Based Multi-Pair Bonding Group Status Parameters 16
7.1.3 ATM-Based Multi-Pair Bonding Group Performance Parameters 17
8 Ethernet-Based Multi-Pair Bonding Specific Section 17
8.1 Ethernet-Based Multi-Pair Bonding Group Object 17
8.1.1 Ethernet-Based Multi-Pair Bonding Group Configuration Parameters 17
8.1.2 Ethernet-Based Multi-Pair Bonding Group Status Parameters 17
8.1.3 Ethernet-Based Multi-Pair Bonding Group Performance Parameters 17
9 TDIM-Based Multi-Pair Bonding Specific Section 18
9.1 TDIM-Based Multi-Pair Bonding Group Object 18
9.1.1 TDIM-Based Multi-Pair Bonding Group Configuration Parameters 18
9.1.2 TDIM-Based Multi-Pair Bonding Group Status Parameters 18
9.1.3 TDIM-Based Multi-Pair Bonding Group Performance Parameters 19
List of Figures
Figure 51: xDSL Bonding – Entity Relationship diagram 11
List of Tables
Table 51: xDSL Multi-pair Bonding Management Capabilities 13
Summary
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).
DSL Forum Working Text WT-xxx
Management Framework for xDSL Bonding
1 Purpose
The purpose of this DSL Forum Technical Report is to define 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). This document defines the required managed objects and hierarchical relationships between them. The management framework 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).
2 Scope
This DSL Forum Technical Report provides a management model for xDSL multi-pair bonding based on ATM, Ethernet or TDIM technologies.
2.1 Definitions
The following definitions apply for the purposes of this document:
Asynchronous Transfer Mode (ATM): a connection-oriented high-speed communications protocol in which data is divided into 48 byte “cells” that can be individually switched and routed. Each cell is pre-appended with a 5 byte “header” containing an identifier of the connection of which the data is a part, along with quality of service parameters associated with the connection.
Bearer channel: A data stream at a specified data rate between two TPS-TC entities (one in each BTU) that is transported transparently over a single latency path by the PMS-TC and PMD sub-layers
Downstream: Information flow whose direction is from a Service Provider System (a.k.a. Central Office [CO] side) to an End-Service Consumer System (a.k.a. Remote Terminal [RT] side or Customer Premises Equipment [CPE]).
Layer/Sub-layer: A collection of objects of the same hierarchical rank.
Upstream: Information flow whose direction is from an End-Service Consumer System (RT/CPE) to a Service Provider System (CO).
2.2 Abbreviations
The following abbreviations apply for the purposes of this document:
ATM Asynchronous transfer mode
ATM-TC Asynchronous transfer mode - transmission convergence (sub-layer)
BCE Bonding Channel Entity
BTU Bonding Terminating Unit
BTU-C Bonding Terminating Unit, CO side
BTU-R Bonding Terminating Unit, RT (or CPE) side
CPE Customer Premises Equipment
CRC Cyclic redundancy code
DSLAM Digital subscriber line access multiplexer
EMS Element management system
FEC Forward error correction
GBS Generic Bonded Sub-layer
GBS-C Generic Bonded Sub-layer, CO side
GBS-R Generic Bonded Sub-layer, RT (or CPE) side
IMA Inverse multiplexing for ATM
NE Network element
PMD Physical media-dependent (sub-layer)
PMS-TC Physical media-specific - transmission convergence (sub-layer)
PTM-TC Packet transfer mode - transmission convergence (sub-layer)
RO Read-only
RT Remote Terminal
RW Read-write
STM Synchronous transfer mode
TDIM Time-division inverse multiplexing
TDM Time-division multiplexing
TPS-TC Transport protocol specific - transmission convergence (sub-layer)
xDSL a collective term referring to any of the various types of DSL technologies
28 February 200728 February 2007 14
Management Framework for xDSL Bonding WT-157 Version 1.2Version 1.1
28 February 200728 February 2007 14
Management Framework for xDSL Bonding WT-157 Version 1.2Version 1.1
2.3 Conventions
In this document, several words are used to signify the requirements of the specification. These words are often capitalized.
MUST This word, or the adjective “REQUIRED”, means that the definition is an absolute requirement of the specification.
MUST NOT This phrase means that the definition is an absolute prohibition of the specification.
SHOULD This word, or the adjective “RECOMMENDED”, means that there may exist valid reasons in particular circumstances to ignore this item, but the full implications must be understood and carefully weighted before choosing a different course.
MAY This word, or the adjective “OPTIONAL”, means that this item is one of an allowed set of alternatives. An implementation that does not include this option MUST be prepared to inter-operate with another implementation that does include the option.
3 References
The following DSL Forum Technical Reports and other references contain provisions, which, through reference in this text, constitute provisions of this Technical Report. At the time of publication, the editions indicated were valid. All Technical Reports and other references are subject to revision; users of this Technical Report are therefore encouraged to investigate the possibility of applying the most recent edition of the Technical Report and other references listed below. A list of the currently valid DSL Forum Technical Reports is published at www.dslforum.org.
NOTE – The reference to a document within this Technical Report does not give it, as a standalone document, the status of a Technical Report.
[1] ITU-T G.998.1 (January 2005), ATM-based multi-pair bonding
[2] ITU-T G.998.2 (January 2005), Ethernet-based multi-pair bonding
[3] ITU-T G.998.3 (January 2005), Multi-pair bonding using time-division inverse multiplexing
[4] IETF RFC2863 (June 2000), The Interfaces Group MIB
[5] IETF RFC2864 (June 2000), The Inverted Stack Table Extension to the Interfaces Group MIB
[6] IEEE Std. 802.3-2005 (December 2005), Local and metropolitan area networks - Specific requirements - Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications
[7] ISO/IEC 10165-1: 1993, Information technology—Open Systems Interconnection—Management information services—Structure of management information—Part 1: Management Information Model.
[8] ISO/IEC 10165-2: 1992, Information technology—Open Systems Interconnection—Structure of management information: Definition of management information.
[9] ISO/IEC 10165-4: 1992, Information technology—Open Systems Interconnection—Management information services—Structure of management information—Part 4: Guidelines for the definition of managed objects.
4 xDSL Multi-pair Bonding Overview
The xDSL Multi-Pair Bonding, specified in the three ITU-T recommendations below, allows a service provider to provide high bandwidth services to business and residential customers over multiple xDSL lines, with greater speed and resiliency, than the service over a single xDSL line, bridging the gap between xDSL and fiber-based transport.
There are three xDSL Multi-Pair Bonding schemes, also known under collective name G.Bond:
· The ATM-Based Multi-Pair Bonding, specified in ITU-T G.998.1 recommendation, which defines a method for bonding (or aggregating) of multiple xDSL lines (or individual bearer channels in multiple xDSL lines) into a single bi-directional logical link carrying an ATM stream.
This specification can be viewed as an evolution of the old IMA technology, applied to xDSL with variable rates on each line/bearer channel.
· The Ethernet-Based Multi-Pair Bonding, specified in ITU-T G.998.2 recommendation, which defines a method for bonding (or aggregating) of multiple xDSL lines (or individual bearer channels in multiple xDSL lines) into a single bi-directional logical link carrying an Ethernet stream.
This specification can be viewed as IEEE 802.3-2005 Clause 61 PME Aggregation Function (PAF), generalized to work over any xDSL technology.
· The Multi-pair bonding using time-division inverse multiplexing (TDIM), specified in ITU-T G.998.3 recommendation, which defines a method for bonding (or aggregating) of multiple xDSL lines into a single bi-directional logical link carrying a mix of various traffic streams (e.g. Ethernet, ATM, TDM).
All schemes allow bonding of up to 32 individual sub-layers with variable rates, providing common functionality for the configuration, initialization, operation and monitoring of the bonded link.
4.1 Layering Model
Architecturally all three bonding schemes define a new “bonded” TPS-TC sub-layer, stacked above multiple ATM-TC, Ethernet/PTM-TC or STM-TC (clear channel) sub-layers for the ATM, Ethernet or TDIM bonding respectively. Each underlying TPS-TC sub-layer represents a protocol specific γ-interface to an xDSL line or an individual bearer channel of an xDSL line. Bonding of multiple bearer channels in the same xDSL line is not allowed.
For the purpose of brevity we will refer to the bonded interface as Generic Bonded Sub-layer (GBS) and to the channel sub-layer as Bonding Channel Entity (BCE).
A generic G.Bond device can have a number of GBS ports, each connected to a particular upper layer (e.g. Media Access Control (MAC) interface for G.998.2 scheme), while simultaneously cross-connected to a number of underlying BCEs, with a single GBS per BCE relationship.
The following figure shows the layering diagram for the bonded xDSL interfaces:
: Figure 51: Layering diagram for xDSL Bonded interfaces
5 Management Framework Structure
This Technical Report defines a management framework that includes a common section with objects and attributes shared by all three xDSL Multi-pair Bonding technologies.
In addition to the common section, each technology has a specific management section.
The management of the underlying sub-layers (e.g. individual xDSL lines) is out of scope of this document.
5.1 Management Model
Management is viewed as a distributed application modeled as a set of interacting management processes. These processes are executed by systems within the open environment. A managing system executes a managing process that invokes management operations. A managed system executes a process that is receptive to these management operations and provides an interface to the resources to be managed. A managed object is the abstraction of a resource that represents its properties as seen by (and for the purpose of) management. Managed objects respond to a defined set of management operations. Managed objects are also capable of emitting a defined set of notifications.
Managed objects are defined in terms of four types of elements:
· Attributes - Data-like properties (as seen by management) of a managed object.
· Actions - Operations that a managing process may perform on an object or its attributes.
· Notifications - Unsolicited reports of events that may be generated by an object.
· Behavior - The way in which managed objects, attributes, and actions interact with the actual resources they model and with each other.
5.2 Containment
A containment relationship is a structuring relationship for managed objects in which the existence of a managed object is dependent on the existence of a containing managed object. The contained managed object is said to be the subordinate managed object, and the containing managed object the superior managed object. The containment relationship is used for naming managed objects. The local containment relationships among object classes are depicted in the entity relationship diagram below, which shows the names of the object classes and whether a particular containment relationship is one-to-one, one-to-many or many-to-one.
:Figure 51: xDSL Bonding – Entity Relationship diagram
5.3 Managed Objects
The following managed objects are defined for the xDSL Bonding:
oBondingGroup: the top-most managed object class of the xDSL Bonding containment tree shown in Figure 1-02Figure 1-02: . Note that this managed object class may be contained within another superior managed object class (e.g. oPHYEntity for the Ethernet bonding). Such containment is expected, but is outside the scope of this Report. The oBondingGroup managed object class provides the management controls necessary to allow an instance of an xDSL Bonded link to be managed.
oBond: this managed object class, contained within oBondingGroup, provides the Bonding Protocol Independent management controls, necessary to allow an instance of oBondingGroup to be managed.
oBondATM: if implemented this managed object class, contained within oBond, provides the ATM xDSL Bonding Protocol Specific management controls, necessary to allow an instance of oBondingGroup to be managed.