ETSI TR 102 390 V1.1.

1 (2005-03)
Technical Report

Transmission and Multiplexing (TM); Access networks; Requirements for the support of Voice over DSL

ETSI TR 102 390 V1.1.1 (2005-03)

Reference
DTR/TM-06021

Keywords
access, network, transmission, xDSL, VoDSL

ETSI
650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88

Important notice
Individual copies of the present document can be downloaded from: http://www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http://portal.etsi.org/chaircor/ETSI_support.asp

Copyright Notification
No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2005. All rights reserved. DECT , PLUGTESTS and UMTS are Trade Marks of ETSI registered for the benefit of its Members. TM TIPHON and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members. TM 3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
TM TM TM

ETSI

ETSI TR 102 390 V1.1.1 (2005-03)

Contents
Intellectual Property Rights ................................................................................................................................5 Foreword.............................................................................................................................................................5 1 2 3 4 5
5.1 5.1.1 5.1.2 5.1.3 5.1.4 5.1.4.1 5.1.4.2 5.1.5 5.1.6 5.1.7 5.2 5.2.1 5.2.2 5.2.3 5.2.4 5.2.5 5.2.6 5.3 5.4

Scope ........................................................................................................................................................6 References (replaces clause 2/[1])............................................................................................................6 Definitions................................................................................................................................................7 Abbreviations ...........................................................................................................................................7 VoDSL Reference Model (replaces clause 5/[1]) ....................................................................................8
VoDSL Reference Model Functional Block Definitions (replaces all of clause 5.1/[1]) ...................................9 Core Network................................................................................................................................................9 Access Network (AN)...................................................................................................................................9 Network Termination 1 (NT1)......................................................................................................................9 Network Termination 2 (NT2)......................................................................................................................9 B-NT2 .....................................................................................................................................................9 N-NT2 .....................................................................................................................................................9 Terminal Adapter (TA) .................................................................................................................................9 User Terminal .............................................................................................................................................10 Access Network Management ....................................................................................................................10 VoDSL Reference Model Interface Definitions (replaces all of clause 5.2/[1]) ..............................................10 Interfaces at the V Reference Point ............................................................................................................10 Interfaces at the U Reference Point ............................................................................................................10 Interfaces at the TN and TB Reference Points ..............................................................................................10 Interfaces at the S Reference Point .............................................................................................................10 Interfaces at the R Reference Point.............................................................................................................10 Interfaces at the Q Reference Point ............................................................................................................10 VoDSL IWF Reference Model.........................................................................................................................10 General VoDSL Service Model........................................................................................................................10

6
6.1 6.2 6.2.1 6.2.2 6.2.3 6.2.4 6.2.5 6.2.6 6.2.7 6.2.8 6.2.9 6.2.10 6.2.11 6.2.12 6.2.13 6.3 6.3.1 6.3.2 6.3.3 6.3.4

General Requirements for VoDSL .........................................................................................................11

General DSL Requirements (supplements clause 6.1/[1])................................................................................11 General System Requirements .........................................................................................................................11 Multi-Line Capability .................................................................................................................................11 Over-subscription .......................................................................................................................................11 Dynamic Bandwidth Allocation for Voice (supplements clause 6.2.3/[1]..................................................11 Voice Quality (replaces clause 6.2.4/[1])....................................................................................................12 Service Feature Transparency.....................................................................................................................12 Continuous Availability..............................................................................................................................12 Performance................................................................................................................................................12 Management ...............................................................................................................................................12 Network Security ........................................................................................................................................12 Network Compatibility ...............................................................................................................................12 Reliability ...................................................................................................................................................12 Jitter and Wander ........................................................................................................................................13 Lifeline Voice Service ................................................................................................................................13 General Service Requirements (supplements clause 6.3/[1]) ...........................................................................13 VoDSL Bearer Requirements .....................................................................................................................14 VoDSL Signalling Requirements ...............................................................................................................14 Class 5 Services ..........................................................................................................................................14 Class 4 Services ..........................................................................................................................................14

7
7.1 7.2

VoDSL Management..............................................................................................................................14
VoDSL Management Functions .......................................................................................................................14 VoDSL Management Architecture...................................................................................................................15

Annex A:

Voice over Asynchronous Transfer Mode (VoATM) (supplements Annex A/[1])..........16

ETSI

ETSI TR 102 390 V1.1.1 (2005-03)

Annex B: B.1 B.2 B.3

Voice over Synchronous Transfer Mode (VoSTM) ...........................................................17

Interfaces for CVoDSL ..........................................................................................................................17 Channelized Voice over ADSL..............................................................................................................17 Channelized Voice over SDSL...............................................................................................................17
POTS over SDSL .............................................................................................................................................18 ISDN over SDSL..............................................................................................................................................18 ETSI V5.1/V5.2 transported over SDSL ..........................................................................................................20 Lifeline Voice Service over SDSL using Dynamic Rate Repartitioning..........................................................23 Lifeline ISDN Example ..............................................................................................................................24 Lifeline POTS Example..............................................................................................................................26

B.3.1 B.3.2 B.3.3 B.3.4 B.3.4.1 B.3.4.2

B.4

Channelized Voice over VDSL..............................................................................................................27 Voice over Internet Protocol (VoIP)....................................................................................28

Annex C:

History ..............................................................................................................................................................30

ETSI

ETSI TR 102 390 V1.1.1 (2005-03)

Intellectual Property Rights

IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http://webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document.

Foreword
This Technical Report (TR) has been produced by ETSI Technical Committee Transmission and Multiplexing (TM). The present document is modelled after the DSL Forum's requirements for Voice over DSL, TR-039 [1] (Technical Report 039), and is intended to supplement it by providing information about Voice-over-DSL (VoDSL) applications and architectures specific to European networks. The document structure has been maintained from TR-039 [1], to allow easy comparison of contents. Since much of the information in TR-039 [1] is applicable to European networks, much of the present document consists of pointers; however, much information is new, and either supplements existing sections of TR-039 [1] or requires new sections entirely.

ETSI

ETSI TR 102 390 V1.1.1 (2005-03)

Scope

The present document specifies, from a European perspective, general AN functional requirements, in terms of transport means for signalling and voice channels, timing/synchronization, delay and BER performances, distribution of the relevant functions over AN elements and management, for in-band support of Voice and NB data communications over DSL systems. It is structured in the form of a supplement to the DSL Forum's TR-039 [1].

2
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15]

References (replaces clause 2/[1])

DSL Forum TR-039 (Version 1.1 - March 2001): "Requirements for Voice over DSL". ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces - Reference configurations". ITU-T Recommendation G.995.1 (2001): "Overview of Digital Subscriber Line (DSL) Recommendations". ATM Forum af-tm-0150.000 (July 2000): "Addendum to Traffic Management v4.1 optional minimum desired cell rate indication for UBR". ANSI T1.508: "Network Performance - Loss Plan for Evolving Digital Networks". ITU-T Recommendation G.114 (2003): "One-way transmission time". ITU-T Recommendation G.131: "Talk echo and its control". ITU-T Recommendation G.165: "Echo cancellers". ITU-T Recommendation G.168: "Digital network echo cancellers". ITU-T Recommendation G.992.1: "Asymmetric digital subscriber line (ADSL) transceivers". ITU-T Recommendation G.992.2: "Splitterless asymmetric digital subscriber line (ADSL) transceivers". ITU-T Recommendation G.107 (2003): "The E-model, a computational model for use in transmission planning". ETSI EN 300 347-1: "V Interfaces at the digital Local Exchange (LE); V5.2 Interface for the support of Access Network (AN); Part 1: V5.2 Interface Specification". ITU-T Recommendation G.960 (1993): "Access digital section for ISDN basic rate access". IEEE Draft P802.3ah/D3.3: "Draft amendment to - Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications - Media Access Control Parameters, Physical Layers and Management Parameters for subscriber access networks". ETSI TS 101 388: "Transmission and Multiplexing (TM); Access transmission systems on metallic access cables; Asymmetric Digital Subscriber Line (ADSL) - European specific requirements [ITU-T Recommendation G.992.1 modified]". ETSI TS 101 524: "Transmission and Multiplexing (TM); Access transmission system on metallic access cables; Symmetric single pair high bitrate Digital Subscriber Line (SDSL)". ETSI TS 101 270-2: "Transmission and Multiplexing (TM); Access transmission systems on metallic access cables; Very High Speed Digital Subscriber Line (VDSL); Part 2: Transceiver specification". ITU-T Recommendation G.711: "Pulse Code Modulation (PCM) of voice frequencies".

For the purposes of this Technical Report (TR), the following references apply:

[16]

[17] [18]

[19]

ETSI

ETSI TR 102 390 V1.1.1 (2005-03)

[20] [21] [22]

ITU-T Recommendation G.726: "40, 32, 24, 16 kbit/s Adaptive Differential Pulse Code Modulation (ADPCM)". ETSI ETS 300 297: "Integrated Services Digital Network (ISDN); Access digital section for ISDN basic access". ETSI EN 300 324-1: "V interfaces at the digital Local Exchange (LE); V5.1 interface for the support of Access Network (AN); Part 1: V5.1 interface specification".

Definitions

For the purposes of the present document, the terms and definitions given in TR-039 [1] apply.

4
AAL2 AAL5 ABR ADPCM AN BA BCC BER B-NT2 CAC CBR CLR CTD CVoDSL DRR DS EFaddr EFM EN eoc FCS FE GFR HDLC IEEE IOM-2 NOTE:

Abbreviations
ATM Adaptation Layer 2 ATM Adaptation Layer 5 Available Bit Rate Adaptive Differential Pulse-Code Modulation Access Network Basic rate Access Bearer Channel Connection Bit-Error Rate Broadband - NT2 Connection Admission Control Constant Bit Rate Cell-Loss Ratio Cell-Transfer Delay Channelized Voice over DSL Dynamic Rate Repartitioning Digital Section Envelope Function address Ethernet in the First Mile European Norm embedded operations channel Frame Check Sequence Function Element Guaranteed Frame Rate High-level Data Link Control Institute of Electrical and Electronic Engineers ISDN-Oriented Modular interface revision 2 IOM-2 is a registered trademark of SIEMENS AG. This information is given for the convenience of users of the present document and does not constitute an endorsement by ETSI of the product named. Equivalent products may be used if they can be shown to lead to the same results. Internet Protocol ISDN Basic rate Access Link Access Protocol for ISDN D channel Link Access Protocol for V5 interface LAPV5 Data Link sublayer LAPV5 Envelope Function sublayer Local Exchange Loss of Frame Alignment Loss Of Signal Line Termination Unit communication between Management and PHysical layer

For the purposes of the present document, the abbreviations given in TR-039 [1] and the following apply:

IP ISDN BA LAPD LAPV5 LAPV5-DL LAPV5-EF LE LFA LOS LTU MPH

ETSI

ETSI TR 102 390 V1.1.1 (2005-03)

MPH-AI MPH-AR MPH-AWI MPH-DI MPH-DSAI nrt-VBR N-ISDN N-NT2 NT1 NT1/2 NT2 NTU OSI PCM PH PHY PMD PMS PMS-TC PTM rt-VBR RTP SDSL STM TA TC TPS TPS-TC TS UBR V5DLaddr VDSL VoATM VoDSL VoIP VoSTM xDSL

MPH-Activation Indication MPH-Activation Request MPH-AWake Indication MPH-Deactivated Indication MPH-Digital Section partial Activation Indication Near-Realtime Variable Bit Rate Narrowband Integrated Services Digital Network Narrowband NT2 Network Termination 1 NT1 integrated with NT2 Network Termination 2 Network Termination Unit Open Systems Interconnection Pulse-Code Modulation communication between data-link layer and PHysical layer PHYsical layer Physical Medium-Dependent Physical Medium-Specific Physical Medium-Specific Transmission Convergence Packet Transfer Mode Real-Time Variable Bit Rate Real-time Transfer Protocol Symmetric single pair high bit rate Digital Subscriber Line Synchronous Transfer Mode Terminal Adapter Transmission Convergence Transmission Protocol-Specific Transmission Protocol-Specific - Transmission Convergence Technical Specification Unspecified Bit Rate V5 Data Link address Very high bitrate Digital Subscriber Line Voice over ATM Voice over DSL Voice over Internet Protocol Voice over Synchronous Transfer Mode collective term referring to any of the various types of DSL technologies

VoDSL Reference Model (replaces clause 5/[1])

TB B-NT2 TN NT1 N-NT2 S TA R User Terminal

Figure 1 depicts the reference configuration for a generic DSL system.

Access Network Management V Core Network Q U Access Network

Figure 1: Reference configuration for DSL This reference configuration is based on the reference configuration used for the N-ISDN in ITU-T Recommendation I.411 [2] and is also given in ITU-T Recommendation G.995.1 [3], and identifies the reference points in the context of access network.

ETSI

ETSI TR 102 390 V1.1.1 (2005-03)

NOTE:

The reference configuration in figure 1 shows the functional groupings, which may or may not correspond to physical groupings. Physical groupings may comprise of one or more functional groupings.

One or more of the elements in the reference configuration may be null or could be merged in different scenarios. At the functional interfaces there are reference points, although existence of a physical interface is not implied. There may be more than one interface specification for each of these reference points. The exact interpretation at these reference points will depend upon the local network architecture and regulatory environment.

5.1
5.1.1

VoDSL Reference Model Functional Block Definitions (replaces all of clause 5.1/[1])
Core Network

The Core Network is part of the Public Switched Telephone Network, which transports telephony services between subscribers. Where needed, the Core Network translates between the signalling and bearer methods used by existing telephony equipment and signalling and bearer methods used by the Access Network.

5.1.2

Access Network (AN)

The Access Network provides concentration for multiple NT1 devices, each with its own U reference point, to the Core Network, at the V reference point. In the case of VoDSL, this device is often referred to as a DSL Access Multiplexer (DSLAM). The reference architecture does not preclude the support of multiple services transported over DSL (e.g. VoSTM and VoATM in parallel).

5.1.3

Network Termination 1 (NT1)

The NT1 provides physical termination to the line from the Access Network (indicated at the U reference point), and provides service presentation to a customer at a logical or physical interface (indicated at the T reference point). The NT1 might not terminate the transport protocol from the Access Network (e.g. ATM) for user traffic. The NT1 may implement transport protocol functions such as rate adaptation required to support different T/U reference point characteristics.

5.1.4

Network Termination 2 (NT2)

An NT2 connects to the network at the T reference point, and may connect to multiple user terminals at the S reference point. The NT2 terminates the transport protocol (e.g. ATM) for user traffic, and may implement switching/routing functions. The NT2 may be integrated with an NT1 to form an NT1/2. The term "NT" designates the generic Network Termination for various services. For some services, it might be part of the Access Network, and for others not. The inclusion of the NT in the Access Network, or its exclusion, should not be taken to determine the ownership. The reference architecture does not preclude the integration of the Network Termination with other User Terminal functions.

5.1.4.1

B-NT2

The B-NT2 terminates the transport protocol (e.g. AAL5/ATM) for broadband data.

5.1.4.2

N-NT2

The N-NT2 terminates the transport protocol (e.g. AAL2/ATM) for voice data.

5.1.5

Terminal Adapter (TA)

The Terminal Adapter adapts the transport protocol to the specific requirements of a User Terminal.

ETSI

10

ETSI TR 102 390 V1.1.1 (2005-03)

5.1.6

User Terminal

Voice and data services are delivered to the users' voice and data terminals.

5.1.7

Access Network Management

Access Network Management element depicts the management functionalities.

5.2
5.2.1

VoDSL Reference Model Interface Definitions (replaces all of clause 5.2/[1])

Interfaces at the V Reference Point

The V reference point indicates the connection of the Core Network with the Access Network. Examples of interfaces at this point include ISDN or POTS over V5.2.

5.2.2

Interfaces at the U Reference Point

The U reference point indicates the connection of the physical layer from the Access Network with the NT1 at each customer's premises. Examples of interfaces at this reference point include ISDN basic rate and primary rate access transmission systems.

5.2.3

Interfaces at the TN and TB Reference Points

The TN reference point indicates the connection of the NT1 with the N-NT2, and the TB reference point indicates the connection of the NT1 with the B-NT2. The interfaces at these reference points may be internal functions when the NTs are integrated into an NT1/2. Logical or physical interfaces at the TN and TB reference points provide service presentation to customers. An N-NT2 that connects to the network at the TN reference point, or a B-NT2 that connects to the network at the TB reference point, may connect to multiple user terminals on interfaces at the S reference point.

5.2.4

Interfaces at the S Reference Point

The S reference point indicates the connection of the N-NT2 with the User Terminals.

5.2.5

Interfaces at the R Reference Point

The R reference point indicates the connection of the Terminal Adapter to the User Terminal.

5.2.6

Interfaces at the Q Reference Point

Access Network and the Access Network Management elements are separated at the Q reference point.

5.3

VoDSL IWF Reference Model

See clause 5.3 of TR-039 [1].

5.4

General VoDSL Service Model

See clause 5.4 of TR-039 [1].

ETSI

11

ETSI TR 102 390 V1.1.1 (2005-03)

6
6.1

General Requirements for VoDSL

General DSL Requirements (supplements clause 6.1/[1])

See clause 6.1 of TR-039 [1]. The discussion of DRR for ADSL in TR-039 is also applicable to SDSL.

6.2
6.2.1

General System Requirements

Multi-Line Capability

See clause 6.2.1 of TR-039 [1].

6.2.2

Over-subscription

See clause 5.3 of TR-039 [1].

6.2.3

Dynamic Bandwidth Allocation for Voice (supplements clause 6.2.3/[1]

See clause 6.2.3 of [1], which includes discussion of Dynamic Bandwidth Allocation for xDSL generally. When an SDSL link has an STM bearer and a Broadband bearer, the Dynamic Rate Repartitioning (DRR) procedure allows bandwidth to be lent from the STM to the Broadband bearer on a temporary basis. When an SDSL DSLAM provides voice service using CVoDSL, the support of the DRR procedure is highly recommended. When the CPE provides voice service using CVoDSL it is highly recommended that either the CPE support the DRR procedure, or else that it be possible to set up a permanent channel for voice service, via the management system. Services requiring a guaranteed minimum of bandwidth, such as video streams, should be protected during rate partitioning. Should the maximum voice traffic load be demanded, enough broadband bandwidth should still be available to carry these high-priority services. For example, when using the DRR procedure with a Broadband bearer carrying ATM services, it is important that services that require guaranteed bitrates are not affected; instead, the bandwidth lent by the voice bearer should only be used for best-effort services, such as UBR and UBR+ services (defined in the ATM Forum document af-tm-0150.000 [4]): Such services have no traffic-related service commitments, in terms of Cell-Loss Ratio (CLR) or Cell-Transfer Delay (CTD); nor is there any guarantee of fair utilization of bandwidth among these services. Two parameters can be used to define the constraints on the DRR procedure: The bandwidth committed for broadband services, BG: This is the amount of bandwidth that is guaranteed to be available for broadband services. For ATM services, BG is the amount of bandwidth that must be known to the CAC function, for traffic management purposes, as that which is to be used for services that cannot tolerate delay: CBR, rt-VBR, nrt-VBR, ABR and GFR. The BG must be calculated after start-up, and not changed during operation. The bandwidth committed for broadband is: BG = BNET BV where BNET is the net payload capacity of the link, and BV is the bandwidth allocated to voice services (POTS or ISDN). The bandwidth currently available for broadband services, BC: This is the total bandwidth that can be used for all broadband services. For ATM services, this includes UBR and UBR+ services; BC is to be communicated to the ATM layer during DRR actions: BC = BG + BV-R

ETSI

12

ETSI TR 102 390 V1.1.1 (2005-03)

where BV-R is the bandwidth that has been assigned to voice calls but which is not currently in use, and is thus available for release.

6.2.4

Voice Quality (replaces clause 6.2.4/[1])

Service Providers and end-users generally do not want to be forced to compromise on the quality of voice connections. Technology is available to ensure that the voice quality is indistinguishable from that provided by a conventional wireline connection to the PSTN. Maximum delay and echo cancellation requirements should be supported according to T1.508 [5], ITU-T Recommendations G.114 [6] or G.131 [7]. Examples include ITU-T Recommendations G.165 [8] or G.168 [9]. ITU-T Recommendation G.114 states that although a few applications may be slightly affected by end-to-end (i.e. "mouth-to-ear" in the case of speech) delays of less than 150 ms, if delays can be kept below this figure, most applications, both speech and non-speech, will experience essentially transparent interactivity. It also states that while delays above 400 ms are unacceptable for general network planning purposes, it is recognized that in some exceptional cases this limit will be exceeded. These end-to-end delay figures given in ITU-T Recommendation G.114 include the delay introduced in the CP-IWF(s), DSL network(s), AN-IWF(s), and the transport network(s) between the call originator and the destination and any delay in CPE. Appendix II further describes delay issues. The CP-IWF and AN-IWF implementations should take all measures to minimize the delay. In addition the delay in the DSL network itself can be significant. For example, with ADSL (ITU-T Recommendations G.992.1 [10] and G.992.2 [11]), network operators could consider using the fast path or setting minimal interleave depth. It should be noted that when the ADSL physical line bandwidth is sub-divided (e.g. into ADSL dual latency or other reserved channels) this will affect delay by reducing the "line rate" at which cells are inserted into the channel. The choice of codec also has an effect on voice quality. Further information on the effect of codecs, delay and echo on perceived quality can be found in ITU-T Recommendation G.107 [12].

6.2.5

Service Feature Transparency

See clause 6.2.5 of TR-039 [1].

6.2.6

Continuous Availability

See clause 6.2.6 of TR-039 [1].

6.2.7

Performance

See clause 6.2.7 of TR-039 [1].

6.2.8

Management

See clause 6.2.8 of TR-039 [1].

6.2.9

Network Security

See clause 6.2.9 of TR-039 [1].

6.2.10

Network Compatibility

See clause 6.2.10 of TR-039 [1].

6.2.11

Reliability

See clause 6.2.11 of TR-039 [1].

ETSI

13

ETSI TR 102 390 V1.1.1 (2005-03)

6.2.12

Jitter and Wander

At the interface towards the Core Network (the V interface), jitter and wander requirements given in the ETSI V5.2 interface specification EN 300 347-1 [13] should be fulfilled. To support ISDN basic rate access, the jitter and wander levels must not exceed the values given in ITU-T Recommendation G.960 [14]. To support POTS interfaces at the customer premises (the R interface), the jitter and wander levels must not exceed the values given in ITU-T Recommendation G.960 [14] at the digital interface of the codec at the customer premises.

6.2.13

Lifeline Voice Service

Support for lifeline voice service is optional; however, it should be noted that it may be necessary in some countries, because of regulatory requirements.

6.3

General Service Requirements (supplements clause 6.3/[1])

See clause 6.3 of TR-039 [1]. Voice over DSL methods are characterized by different network transport mechanisms, which can be distinguished by their relative placement in the OSI reference model. These are: Voice over STM (VoSTM), more commonly known as Channelized Voice over DSL (CVoDSL): This approach embeds the voice information directly into the PHY layer, without involving higher layers of the DSL link. Voice over ATM (VoATM): The VoATM approach employs the functionality of the ATM layer, which is located roughly at the Data Link layer of the OSI reference model. Voice over IP (VoIP): The VoIP approach employs the IP protocols, at the Network layer of the OSI model, to transport voice data and signalling. The IP can be carried over ATM or over the IEEE 802.3ah EFM protocol stack [15].

ETSI

14

ETSI TR 102 390 V1.1.1 (2005-03)

Figure 2 illustrates the typical protocol stacks for each of these three transport methods.

NOTE 1: The baseband POTS/ISDN capability of ADSL and VDSL is not considered a "Voice over DSL" service. NOTE 2: * PPP is not necessarily needed.

Figure 2: Principal Methods for VoDSL Services The applicability of a particular VoDSL service model depends on the capabilities of the network architecture.

6.3.1

VoDSL Bearer Requirements

See clause 6.3.1 of TR-039 [1].

6.3.2

VoDSL Signalling Requirements

See clause 6.3.2 of TR-039 [1].

6.3.3

Class 5 Services

See clause 6.3.3 of TR-039 [1].

6.3.4

Class 4 Services

See clause 6.3.4 of TR-039 [1].

7
7.1

VoDSL Management
VoDSL Management Functions

See clause 7 of TR-039 [1].

See clause 7.1 of TR-039 [1].

ETSI

15

ETSI TR 102 390 V1.1.1 (2005-03)

7.2

VoDSL Management Architecture

See clause 7.2 of TR-039 [1].

ETSI

16

ETSI TR 102 390 V1.1.1 (2005-03)

Annex A: Voice over Asynchronous Transfer Mode (VoATM) (supplements Annex A/[1])
The VoATM approach uses ATM for the Data Link layer, transporting voice samples over ATM Adaptation Layer (AAL) type 1 or type 2. VoATM provided over AAL 2 has been suggested by the DSL Forum as the VoATM protocol of choice.

Figure A.1: VoATM OSI Layer Relations Figure A.1 illustrates the transport of voice streams and signalling/control functions over ATM. These functions are out of scope for the present document. The VoATM approach is supported by all xDSL technologies defined by ETSI: ADSL (TS 101 388 [16]), SDSL (TS 101 524 [17]) and VDSL (TS 101 270-2 [18]). See annex A of TR-039 [1]. The provision of lifeline voice service in a VoATM scenario raises issues that need further study. It is expected that work underway in the DSL Forum will provide recommendations on this matter.

ETSI

17

ETSI TR 102 390 V1.1.1 (2005-03)

Annex B: Voice over Synchronous Transfer Mode (VoSTM)

The VoSTM approach (more commonly known as Channelized Voice over DSL (CVoDSL)) transports voice data over the xDSL PHY layer without additional protocol. PCM (ITU-T Recommendation G.711 [19]) or ADPCM (ITU-T Recommendation G.726 [20]) voice encoding is transported transparently between the LTU and the NTU.

Figure B.1: CVoDSL OSI Layer Relations As shown in figure B.1, the CVoDSL approach applies to the transport of voice over the access digital section. The realization of the CVoDSL TC layer is different for every xDSL technology. Call-related signalling and control are transported transparently, if applicable; in some aspects an interworking function at the customer premises (CP-IWF) is needed.

B.1

Interfaces for CVoDSL

The intent of the CVoDSL approach is to transport the usual voice services over xDSL access as transparently as possible, so that the usual voice terminals are connected to the PSTN or ISDN and handled in the usual way. There are three applicable interfaces to be met: The POTS interface. The ISDN interface. The ETSI V5.1/V5.2 interface, which supports both POTS and ISDN.

B.2

Channelized Voice over ADSL

For further study.

B.3

Channelized Voice over SDSL

A.6 TPS-TC for Synchronous ISDN; A.7 TPS-TC for POTS; A.10 TPS-TC for LAPV5 enveloped POTS or ISDN.

TS 101 524 [17] supports several options for CVoDSL, as specified in several clauses:

ETSI

18

ETSI TR 102 390 V1.1.1 (2005-03)

Additionally, the clause A.9 of SDSL specifies a combination from among the above CVoDSL techniques: Type 1: STM + Broadband; Type 2: STM + ATM; Type 3: STM + Clear Channel.

B.3.1
Transport

POTS over SDSL

The SDSL POTS service, as defined by clause A.7 of TS 101 524 [17], provides the following required functions:

64-kbit/s PCM channels are mapped onto B-channels. POTS signalling is mapped onto Z-channel(s) or B-channel(s), depending on the required bandwidth.

Protocol Handling PCM voice is transported transparently. POTS signalling/control is converted by the CP-IWF in accordance with TS 101 524 [17].

An example showing the functional relation to relevant reference points (with respect to the VoDSL Architectural Reference Model) shown in figure B.2.

CP-IWF Signalling/Control Voice Conversion S Reference Point PHY POTS TC PMS-TC PMD
Figure B.2

CO-IWF Signalling/Control Voice POTS TC PMS-TC PMD PHY V Reference Point

The service model does not preclude the integration of the CP-IWF with other Customer-Premise functions.

B.3.2
Transport

ISDN over SDSL

The SDSL ISDN service, as defined by clause A.6 of TS 101 524 [17], provides the following required functions:

ISDN data B-channels are mapped onto 64-kbit/s SDSL B-channels. ISDN D-channel signalling is mapped onto two 8-kbit/s Z-channels, or onto SDSL B-channels, if there are more than 3 D-channels. ISDN S-Bus control is mapped via ISDN eoc messages onto the SDSL eoc channel or onto the Fast eoc channel, depending on the number of supported ISDN BAs.

Protocol Handling ISDN B-channels are transported transparently. ISDN D-channel signalling is transported transparently. ISDN S-Bus control is handled by the CP-IWF and CO-IWF.

ETSI

19

ETSI TR 102 390 V1.1.1 (2005-03)

An example showing the functional relation to relevant reference points (with respect to the VoDSL Architectural Reference Model) is shown in figure B.3.

CP-IWF
Control Voice

CO-IWF
Control Voice Signalling

S-Bus Control S Reference Point

Signalling

ISDN TC PMS-TC PMD

ISDN TC PMS-TC PMD PHY

S-Bus Control V Reference Point

PHY

Figure B.3: SDSL ISDN Service Model The CP-IWF provides S-Bus control: the conversion of ISDN Message Codes (as defined by TS 101 524 [17], clause A.6.7.2) to ISDN PHY commands (typically IOM-2 Codes). IOM-2 is a registered trademark of SIEMENS AG. This information is given for the convenience of users of the present document and does not constitute an endorsement by ETSI of the product named. Equivalent products may be used if they can be shown to lead to the same results. The service model does not preclude the integration of the CP-IWF with other Customer-Premise functions. The CO-IWF provides S-Bus control at the CO: it converts the ISDN Message Codes (as defined by TS 101 524 [17], clause A.6.7.2) to the ISDN Function Elements (FEs) from the ISDN Digital Section for basic access (defined in ETS 300 297 [21], clause 8.4.3) that are required to support the ETSI V5.1 interface (EN 300 324-1 [22]). The CO-IWF is located at the V1 reference point in figure 31 of EN 300 324-1 [22], where the S-Bus Control communicates with the AN Port-Status FSM. The list of relevant FEs, taken from table 31 of ETS 300 297 [21], has been reproduced in table B.1; however, support of all the FEs from table 31 is not appropriate, since the Digital Section (DS) is provided by SDSL rather than ISDN basic rate access. Table B.1: ISDN basic access Digital Section FEs relevant to interface V5.1 (modified from table 31 of ETS 300 297)
FE FE1 FE2 FE3 FE4 FE5 FE6 FE7 FE8 FE9 FE10 FE11 FE12 FE13 Name activate access access activation initiated by user DS activated access activated deactivate access access deactivated LOS/LFA on DS or loss of power in NT1 activate loopback 2 activate loopback 1 (Not supported) activate loopback 1A (Not supported) activate partially the DS (Not supported) LOS/LFA at T reference point deactivate T whilst keeping the DS partially activated (Not supported) CO-IWF ET Meaning at ET in LE PH/MPH-AR MPH-AWI (awake indication) MPH-DSAI PH/MPH-AI MPH-DR PH/MPH-DI not directly relevant not directly relevant not directly relevant not directly relevant not directly relevant not directly relevant not directly relevant

failure in DS AN maintenance AN maintenance AN maintenance AN maintenance AN management information AN maintenance

ETSI

20

ETSI TR 102 390 V1.1.1 (2005-03)

B.3.3

ETSI V5.1/V5.2 transported over SDSL

SDSL can provide the ETSI V5.1 (EN 300 324-1 [22]) and V5.2 (EN 300 347-1 [13]) interfaces by using the LAPV5 enveloped POTS/ISDN capability for the following functions, as specified by clause A.10 of TS 101 524 [17]: Transport POTS PCM voice is mapped onto SDSL B-channels. ISDN data B-channels are mapped onto 64-kbit/s SDSL B-channels. ISDN D-channels are mapped onto two 8-kbit/s Z-channels, or onto SDSL B-channels, if there are more than 3 D-channels. POTS control and signalling messages are multiplexed together with ISDN control messages via LAPV5-DL. The payload sub-block ordering is defined in clause A.11.10 of TS 101 524 [17].

NOTE:

Protocol Handling ISDN B-channels are transported transparently. ISDN D-channel signalling is multiplexed with ISDN control and POTS signalling and control messages using the LAPV5 enveloped address function.

Figure B.4: SDSL LAPV5 enveloped POTS/ISDN Service Model An example showing the functional relation to relevant reference points (with respect to the VoDSL Architectural Reference Model, clause 5) is shown in figure B.4. The PMD, PMS-TC and LAPV5 TC blocks belong to the SDSL physical layer. The service model does not preclude the integration of the CP-IWF with other Customer Premise functions. CP-IWF The related protocol functions of the CP-IWF are: 1) 2) Mapping: as described in TS 101 524 [17], clause A.10. LAPV5-EF address: used to transport all ISDN- and POTS-related signalling and control information. The LAPV5-EF address is encapsulated in HDLC frames. The format is given in figure B.5.

ETSI

21

ETSI TR 102 390 V1.1.1 (2005-03)

Figure B.5: LAPV5-EF frame structure 3) LAPD: to be implemented as follows: D-channel frames received from the ISDN user ports are passed, after processing by the CP-IWF frame relay function, to the Envelope function for transmission on the LAPV5 TC. The EFaddr associated with the port is passed as a parameter. The processed frame is mapped into the envelope information field of the envelope function of the communications channel selected in accordance with V5.1, clause 8.45.1 of EN 300 324-1 [22]. When frames are received by the LAPV5-EF sublayer from the CO-IWF, and if the V5DLaddr lies within the range reserved for ISDN user port identification (as defined in clause 9.2.2.2 of EN 300 324-1 [22]), the envelope information field and the EFaddr is passed to the CP-IWF frame relay function for additional processing and transmission towards the ISDN user port. LAPV5-DL (data link) sublayer: used for peer-to-peer exchanges of information between the AN and the LE, employing frames conforming to the formats defined in figure B.6. Two format types are shown: 1) 2) format A for frames without information field; and format B for frames containing an information field.

4)

Figure B.6: LAPV5-DL frame structures 5) ISDN Port Control: user port status indication is based on the defined split of responsibilities between the AN and the LE. Only status information of the user port that has relevance to call control should influence the state machine in the LE via the V5.1 interface. Port tests, e.g. loop back operation, are ordinarily the responsibility of the AN, but with LAPV5 TC these function are located in the CP-IWF. Performance of loop backs is no longer required, as they are apply to the ISDN physical layer which no longer exists. Tests which interfere with the service are only to be performed when the port is "Blocked", either due to failure or due to request of, and by permission of, the LE. The function elements relevant to the CP-IWF are shown in table B.2, selected from table 31 of EN 300 324-1 [22]).

ETSI

22

ETSI TR 102 390 V1.1.1 (2005-03)

Table B.2: ETS 300 297 set of function elements with relevance to interface V5.1 (modified from table 31 of EN 300 324-1)
FE FE1 FE2 FE3 FE4 FE5 FE6 FE7 FE8 FE9 FE10 FE11 FE12 FE13 Name activate access access activation initiated by user DS activated access activated deactivate access access deactivated LOS/LFA on DS or loss of power in NT1 activate loopback 2 activate loopback 1 (Not supported) activate loopback 1A (Not supported) activate partially the DS (Not supported) LOS/LFA at T deactivate T whilst keeping DS partially activated (Not supported) DS ET Meaning at ET in LE PH/MPH-AR MPH-AWI (awake indication) MPH-DSAI PH/MPH-AI MPH-DR PH/MPH-DI not directly relevant not directly relevant not directly relevant not directly relevant not directly relevant not directly relevant not directly relevant

failure in DS AN maintenance AN maintenance AN maintenance AN maintenance AN management information AN maintenance

6)

POTS Port Control: user port status indication is based on the defined split of responsibilities between the CP-IWF and the LE. Only status information of the user port that has relevance to call control should influence the state machine in the LE via the V5.1 interface. Port tests, e.g. line tests, are no longer required because the access link is replaced by SDSL. Tests which interfere with the service are only to be performed when the port is "Blocked", either due to failure or due to request of, and by permission of, the LE. The function elements relevant to the CP-IWF are shown in table B.3, taken from table 37 of EN 300 324-1 [22]. The MPH-primitives towards the management function are shown in table B.4, taken from table 39 of EN 300 324-1 [22]. See also figure B.4. Table B.3: Set of function elements of interface V5.1 (from table 37 of EN 300 324-1)
FE FE201 FE202 FE203 FE204 FE205 Name Unblock Unblock Block Block block request AN LE Description request or acknowledgement request or acknowledgement Command Command Request

Table B.4: Set of management primitives in the AN relevant to V5.1 (from table 39 of EN 300 324-1)
Primitive MPH-UBR MPH-UBR MPH-UBI MPH-BI MPH-BI MPH-BR FSM Management Description Unblock request Unblock request Unblock indication block command block command block request

7)

PSTN: CP-IWF is to support the AN functionality from EN 300 324-1 [22] which includes the PSTN protocol (clause 13.3), general message format (clause 13.4) and PSTN call control (clause 13.5).

As shown in figure B.6, the CP-IWF is to support two PHY layers at the SB reference point. The conversion function is to provide the multiplexing/de-multiplexing of the ISDN D-channel and ISDN control from/to the ISDN PHY.

ETSI

23

ETSI TR 102 390 V1.1.1 (2005-03)

CO-IWF The related protocol functions of the CO-IWF are: 1) 2) Mapping: this function is described in EN 300 324-1 [22], clause A.10. Timeslot Management: it includes the following functions specified by EN 300 347-1 [13]: 3) Control Protocol: to take individual bearer channels (user ports for POTS or ISDN) out of service, or to return them to service; primarily for maintenance and testing purposes. Protection Protocol: to control the switchover of communications channels carrying the V5 message protocols (including the D-channels) from a failed to a back-up physical link. Link Control Protocol: to manage the physical links that make up the V5 interface; including auditing a link's identity, or taking one out of service.

Bearer Channel Connection (BCC): This a specific protocol feature of EN 300 347-1 [13] which allows the LE to instruct the AN to dynamically allocate bearer channels, either singly or in multiples, on demand. This function is only required if the interface between the CO-IWF and the LE is V5.2.

Figure B.4 indicates the point at which compliance to the V5.1/V5.2 interface is applicable, for the signalling and control.

B.3.4

Lifeline Voice Service over SDSL using Dynamic Rate Repartitioning

In most configurations and normal operation, the broadband-data interface of the SDSL transceiver will provide both the voice and the data services. However, in the event of a local power failure, it is also possible to operate an SDSL transceiver in a lower-power mode which can be sustained by line power on an emergency basis, and which will support voice for lifeline service. This procedure depends on specified optional capabilities in the SDSL standard. The procedure is as follows: When a power failure occurs, the SDSL system will: Transmit an indication of the use of line powering from the Central Office. Switch into a lower-power mode of operation that provides service to an emergency telephone. Initiate a DRR procedure that sets up the possibility of a CVoDSL connection between the emergency telephone and the PSTN, through the Access Node. (This assumes that the SDSL system is operating in Dual-Bearer mode type 1.)

The SDSL system will draw power from the CO through the line, as would an ISDN system in emergency operation. It can provide lifeline voice service based upon either POTS or ISDN basic access. When changing into the lower-power mode, it is acceptable that ongoing telephone calls are dropped on all phone lines with the exception of at least one line, designated as the lifeline interface(s). However, when changing back into normal mode, reconfiguration of the bearers should not result in a dropped call; if necessary, the DRR operation should be held until the call is finished.

Figure B.7: Dual-Bearer Application supporting ATM Data and Lifeline Voice

ETSI

24

ETSI TR 102 390 V1.1.1 (2005-03)

Figure B.7 illustrates that the lifeline phone is supported over the SDSL line in Dual-Bearer mode type 1 (STM + Broadband). In the lifeline application, the PCM data stream will be carried only during a power failure, as otherwise the bandwidth will be dedicated to ATM cells. Local power failure is to be detected by the Management and Control entity and indicated by setting the ps bit, as described in clause 10.2.8 "Loss of Local Power" of ITU-T Recommendation I.411 [2]. The LTU should provide the remote feeding power, as prescribed in clause 13.4 "Feeding Power from the LTU" of ITU-T Recommendation I.411 [2]. The Management and Control entity initiates the DRR procedure, resulting in a change of the framing, as shown below in figure B.8.

Figure B.8: Dual-Bearer Architecture with Lifeline support

B.3.4.1 Lifeline ISDN Example

ISDN lifeline service is defined in TS 101 524 [17], clause A.6.4. As a result of the DRR operation, the SDSL framing would change to shift some of the ATM bandwidth to the lifeline CVoDSL service. An example is shown below. In the example of figure B.9 during normal operation, the frame has: 1 Z-bit for the DRR channel: this assignment will not be changed. 2 Z-bits for ISDN signalling: this assignment can be fixed, or it can be dynamically allocated, using an Activation/Deactivation procedure using the S-Bus control, carried over the SDSL eoc channel. Although the transceiver is operating in the Dual-Bearer TPS-TC STM + Broadband mode, no B-channels are being used for voice. (n) ATM bytes mapped onto the B-channels (B1 - Bn): this assignment can be dynamically allocated.

ETSI

25

ETSI TR 102 390 V1.1.1 (2005-03)

48*(1+i+n*8) bits 14 2 12 * (i+n*8) 10 12 * (i+n*8) 10 12 * (i+n*8) 10 12 * (i+n*8) 2 S p a r e [bits]

Sync word

O H

P 0 1

P 0 2

P 0 3

......

P 1 2

O H

P 1 3

.........

P 2 4

O H

P 2 5

.........

P 3 6

O H

P 3 7

.........

P 4 8

0 ms TPS-TC a channel

Payload Block n * 8, n=3....36

Normal Operation
TPS-TC b channel [bits] ...... ...... B4 B5

6 ms

6 ms

Z1

Z2

Z3

B1

B2

B3

Bn

DRR channel

Lifeline ISDN Signaling

ATM

Loss of local Power

TPS-TC a channel Z1 Z2 Z3 B1 B2 B3 B4 TPS-TC b channel B5 ..... ..... [bits]

Bn

DRR channel

Lifeline ISDN Signaling + B1 & B2 Voice

ATM

= DRR protocol channel = B1/B2 ISDN voice channel

= ISDN signaling protocol (D-channel) = Used for ATM

Figure B.9: SDSL Dual-Bearer TPS-TC Framing with Lifeline ISDN After the loss of local power, the DRR procedure gives the following framing, for this example: 1 Z-bit for the DRR channel. 2 Z-bits for ISDN signalling. 2 B-channels for carrying the ISDN B1 and B2 channels over the SDSL in the TPS-TCa. (In the lifeline mode of ISDN, only one B-channel can be used.) (n 2) ATM bytes mapped onto the B-channels (B1 - Bn). Because this is a lifeline condition, in this case the ATM layer will be inactive above layer 1, and the ATM bytes will be only idle cells produced by the ATM TPS-TC of the SDSL NTU/LTU.

As a result of this procedure, the SDSL-based NTU will be able to meet the power-dissipation restrictions of clause 13.5 of TS 101 524 [17] while continuing to transmit the lifeline ISDN signalling and voice data.

ETSI

26

ETSI TR 102 390 V1.1.1 (2005-03)

B.3.4.2 Lifeline POTS Example

POTS lifeline service is defined in TS 101 524 [17], clause A.7.2. As a result of the DRR operation, the SDSL framing would change to shift some of the ATM bandwidth to the lifeline CVoDSL service. An example is shown below. In the example of figure B.10, during normal operation after start-up, the frame has: 1 Z-bit for the DRR channel: this assignment will not be changed. 1 Z-bit for POTS signalling: this assignment will not be changed. (n) ATM bytes mapped onto the B-channels (B1 - Bn): this assignment can be dynamically allocated. Although the transceiver is operating in the Dual-Bearer TPS-TC STM + Broadband mode, no B-channels are being used for voice.
48*(1+i+n*8) bits 14 2 12 * (i+n*8) 10 12 * (i+n*8) 10 12 * (i+n*8) 10 12 * (i+n*8) 2 S p a r e [bits]

Sync word

O H

P 0 1

P 0 2

P 0 3

......

P 1 2

O H

P 1 3

.........

P 2 4

O H

P 2 5

.........

P 3 6

O H

P 3 7

.........

P 4 8

0 ms TPS-TC a channel

Payload Block n * 8, n=3....36

TPS-TC b channel B2

Normal Operation
[bits] ...... ...... B5

6 ms

6 ms

Z1

Z2

B1

B3

B4

Bn

DRR channel

Lifeline POTS Signaling

ATM

Loss of local Power

TPS-TC a channel B2 TPS-TC b channel ..... ..... [bits] Z1 Z2 B1 B3 B4 B5

Bn

DRR channel

Lifeline POTS Signaling + 64 kBit/s Voice

ATM

= Used for DRR protocol = Used for 64 kBit/s POTS voice channel

= Used for POTS signaling protocol (or transmitted over the eoc channel) = Used for ATM

Figure B.10: SDSL Dual-Bearer TPS-TC Framing with Lifeline POTS

ETSI

27

ETSI TR 102 390 V1.1.1 (2005-03)

After the loss of local power, the DRR procedure gives the following framing, for this example: 1 Z-bit for the DRR channel. 2 Z-bits for POTS signalling. 1 B-channels for carrying the 64-kb/s POTS channel over the SDSL in the TPS-TCa. (n 1) ATM bytes mapped onto the B-channels (B1 - Bn). Because this is a lifeline condition, in this case the ATM layer will be inactive above layer 1, and the ATM bytes will be only idle cells produced by the ATM TPS-TC of the SDSL NTU/LTU.

As a result of this procedure, the SDSL-based NTU will be able to meet the power-dissipation restrictions of clause 13.5 of TS 101 524 [17] while continuing to transmit the lifeline POTS signalling and voice data.

B.4

Channelized Voice over VDSL

For further study.

ETSI

28

ETSI TR 102 390 V1.1.1 (2005-03)

Annex C: Voice over Internet Protocol (VoIP)

The VoIP approach uses the Internet Protocol (IP) as the Network layer to transport voice. Figure C.1 shows how VoIP is carried over ATM, in terms of the OSI layer model.

Figure C.1: VoIP OSI Layer Relations Conversely, figure C.2 shows how VoIP is carried over Ethernet.

NOTE:

* PPP is not necessarily needed.

Figure C.2: VoIP OSI Layer Relations The transport of voice streams and call-related signalling and control are carried using different transport-layer functions. The interaction of the ATM and ATM Transmission Convergence layers (ATM-TC) for the different xDSL technologies are specific for each technology, and are specified in the respective ETSI standards. The Packet Transport Mode (PTM) is a generic packet-based transmission system; an example implementation is IEEE 802.3ah [15] (EFM).

ETSI

29

ETSI TR 102 390 V1.1.1 (2005-03)

The provision of lifeline voice service in a VoIP scenario raises issues that need further study. It is expected that work underway in the DSL Forum will provide recommendations on this matter.

ETSI

30

ETSI TR 102 390 V1.1.1 (2005-03)

History
Document history V1.1.1 March 2005 Publication

ETSI