0% found this document useful (1 vote)

747 views

Manual Anymedia

Alcatel-Lucent assumes no responsibility for inaccuracies contained herein. Information presented is subject to change without notice. Technical support is available for AnyMedia Access System indoor / outdoor applications.

Uploaded by

consultach

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (1 vote)

747 views

Manual Anymedia

Uploaded by

consultach

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 908

AnyMedia® Access System

(30 Channel)
Applications and Planning Guide
Narrowband and ATM xDSL services
Releases up to R1.34 and R1.33

363-211-586
CC109562751
Issue 6
July 2007
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their
respective owners.

The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.
Copyright © 2007 Alcatel-Lucent. All Rights Reserved.

Notice

Every effort has been made to ensure that the information contained in this information product was accurate at the time of printing. However,
information is subject to change.

Ordering information

See “How to order” (p. xxiii).

Technical support

Technical support is available for AnyMedia Access System indoor/outdoor applications, for AnyMedia Access System 800, for AnyMedia LAG
System, and for AnyMedia Element Manager (Navis AnyMedia Element Manager).

AnyMedia service is complemented by a full range of services available to support planning, maintaining and operating your system.
Applications testing, network integration, and upgrade conversion support is available.

Alcatel-Lucent service personnel will troubleshoot field problems 24 h a day over the phone and on site (if necessary) based on Alcatel-Lucent
service contracts by Local/Regional Customer Support (LCS/RCS) and by Remote Technical Support (RTS).

Contacting your Alcatel-Lucent support: For Europe call the International Customer Management Center (ICMC): +353 1692 4579 or call the
toll free number: 00 800 00 58 2368. For Asia Pacific, Caribbean and Latin America Region, Saudi Arabia, Middle East and Africa call the
local Alcatel-Lucent Customer Technical Support Team.
Contents

About this information product

Purpose ........................................................................................................................................................................................ xvii

Reason for reissue ................................................................................................................................................................... xvii

Intended audience ................................................................................................................................................................ xviii

Conventions used ................................................................................................................................................................... xviii

How to order ........................................................................................................................................................................... xxiii

How to comment .................................................................................................................................................................... xxiv

1 Services

Overview ...................................................................................................................................................................................... 1-1

Narrowband services

Overview ...................................................................................................................................................................................... 1-2

Overview ...................................................................................................................................................................................... 1-3

V5.x (switched) services / Subscriber side .................................................................................................................... 1-4

V5.x (switched) services / Network side ........................................................................................................................ 1-6

V3 switched services / Subscriber side ........................................................................................................................... 1-9

V3 switched services / Network side ............................................................................................................................ 1-10

Non-switched services / Subscriber side ...................................................................................................................... 1-11

Non-switched services / Network side .......................................................................................................................... 1-14

Host/remote terminal interconnection service ............................................................................................................ 1-15

ATM xDSL-based services and configurations

Overview ................................................................................................................................................................................... 1-16

ATM xDSL services ............................................................................................................................................................. 1-17

Quality of service for ATM xDSL services ................................................................................................................ 1-24

Configuration options for the ATM xDSL subsystem ............................................................................................ 1-26

Daisychaining of AnyMedia ® LAG Shelves ............................................................................................................... 1-32

Local shelf daisychaining ................................................................................................................................................... 1-33

Remote shelf daisychaining via SDH ring ................................................................................................................ 1-34

2 Physical interfaces

Overview ...................................................................................................................................................................................... 2-1

Physical interfaces related to narrowband services

E1 interface (network side) .................................................................................................................................................. 2-3

Z interface (subscriber side) ................................................................................................................................................ 2-4

U interface (subscriber side) ................................................................................................................................................ 2-6

HDSL interface (subscriber side) ...................................................................................................................................... 2-9

Physical E1 interface (remote terminal link) .............................................................................................................. 2-11

Synchronization interfaces for narrowband services ............................................................................................... 2-12

OAM&P interfaces for narrowband services ............................................................................................................. 2-13

Craft interface terminal port .............................................................................................................................................. 2-14

10BaseT LAN interface ...................................................................................................................................................... 2-15

Remote operations channel (ROC) ................................................................................................................................. 2-16

Remote operations channel (ROC) for remote terminal ........................................................................................ 2-17

Alarm interfaces ..................................................................................................................................................................... 2-18

Testing interfaces ................................................................................................................................................................... 2-19

Physical interfaces related to ATM xDSL services

ATM feeder and xDSL interfaces ................................................................................................................................... 2-20

ATM feeder interfaces ......................................................................................................................................................... 2-21

ATM xDSL interfaces .......................................................................................................................................................... 2-22

CPE Interfaces ........................................................................................................................................................................ 2-24

Synchronization interfaces for ATM xDSL services ............................................................................................... 2-25

ATM OAM&P interfaces for xDSL services ............................................................................................................. 2-26

Console port ........................................................................................................................................................................... 2-27

10BaseT port ............................................................................................................................................................................ 2-28

BB ATM Operations Channel ........................................................................................................................................... 2-29

Communication with the AFM over the ROC .......................................................................................................... 2-30

ATM xDSL CPE interfaces ............................................................................................................................................... 2-32

3 OAM&P for narrowband services

Overview ...................................................................................................................................................................................... 3-1

Configuration management

Overview ...................................................................................................................................................................................... 3-5

Configuration management .................................................................................................................................................. 3-7

Database management ............................................................................................................................................................ 3-8

Software management ............................................................................................................................................................ 3-9

System turn-up ........................................................................................................................................................................ 3-10

Provisioning and service activation ................................................................................................................................ 3-11

POTS subscriber ..................................................................................................................................................................... 3-15

ISDN BRA subscriber .......................................................................................................................................................... 3-16

V5 ISDN PRA subscriber .................................................................................................................................................. 3-17

V3 ISDN PRA subscriber .................................................................................................................................................. 3-19

V5 frame relaying (ISDN) ................................................................................................................................................. 3-21

POTS/ISDN operation modes ........................................................................................................................................... 3-22

Analog leased lines ............................................................................................................................................................... 3-23

Digital leased lines ................................................................................................................................................................ 3-24

N × 64 kbps leased lines .................................................................................................................................................... 3-26

Unstructured leased line subscriber via IO_E1 ......................................................................................................... 3-28

Unstructured leased line subscriber via AP_E1 ........................................................................................................ 3-30

Provisioning model ............................................................................................................................................................... 3-31

Service state model ............................................................................................................................................................... 3-34

Remote operations channel (ROC) ................................................................................................................................. 3-36

Remote operations channel (ROC) for remote terminal ........................................................................................ 3-37

Mismatch of provisioning between host and remote terminal ............................................................................ 3-40

Managed NTU provisioning .............................................................................................................................................. 3-42

V5 re-provisioning ................................................................................................................................................................ 3-44

Clock synchronization management in the AnyMedia Access System ........................................................... 3-49

Protection switching ............................................................................................................................................................. 3-54

COMDAC protection ........................................................................................................................................................... 3-56

Synchronization source protection using TDM COMDAC ................................................................................. 3-57

V5.2 Communication channel protection .................................................................................................................... 3-58

IO_HDLC protection ............................................................................................................................................................ 3-59

IO_E1 protection .................................................................................................................................................................... 3-61

AP port protection ................................................................................................................................................................. 3-63

Ringing protection in the AnyMedia ® LAG 4300 Shelf ....................................................................................... 3-66

Ringing in the AnyMedia ® LAG 1900 Shelf ............................................................................................................. 3-71

Ringing protection in the AnyMedia ® ETSI V5 Shelf ........................................................................................... 3-73

Protection switch characteristics ...................................................................................................................................... 3-75

Inventory management

Overview ................................................................................................................................................................................... 3-77

Retrievable inventory items ............................................................................................................................................... 3-78

System identification name [target identifier (TID)] .............................................................................................. 3-80

Internet protocol (IP) address ........................................................................................................................................... 3-81

Reportable database changes ............................................................................................................................................. 3-82

NTU inventory data .............................................................................................................................................................. 3-83

Fault management

Overview ................................................................................................................................................................................... 3-84

Maintenance ............................................................................................................................................................................. 3-86

Alarms and events ................................................................................................................................................................. 3-90

Common alarms ..................................................................................................................................................................... 3-92

Equipment alarms .................................................................................................................................................................. 3-93

Facility alarms (2-Mbps transmission) .......................................................................................................................... 3-99

Host and remote terminal alarms .................................................................................................................................. 3-100

Alarm signaling paths ........................................................................................................................................................ 3-101

Miscellaneous alarm inputs ............................................................................................................................................. 3-102

Alarm output relays ............................................................................................................................................................ 3-106

Local alarm and status indicators ................................................................................................................................. 3-107

Alarm reporting and retrieval via TL1 ....................................................................................................................... 3-108

Built-in self tests .................................................................................................................................................................. 3-109

Testing possibilities ............................................................................................................................................................. 3-113

On-demand tests using integrated capabilities ........................................................................................................ 3-114

Detection test of a test termination .............................................................................................................................. 3-125

Draw and break dial tone test ........................................................................................................................................ 3-126

DTMF, pulse character or register recall (hook flash) test ................................................................................ 3-127

Sending of test tone for POTS CPE ........................................................................................................................... 3-128

Ringing test for POTS CPE ............................................................................................................................................ 3-129

CRC tests for ISDN application packs ....................................................................................................................... 3-130

Sending a single pulse ....................................................................................................................................................... 3-131

NT1 detection test ............................................................................................................................................................... 3-132

Noise measurement on a subscriber line ................................................................................................................... 3-133

Loop current measurement .............................................................................................................................................. 3-134

Tone measurement .............................................................................................................................................................. 3-135

Howler tone on demand on POTS drops in reduced battery state ................................................................. 3-136

Quick line test ....................................................................................................................................................................... 3-137

Talk to subscriber test session ....................................................................................................................................... 3-140

Loopbacks ............................................................................................................................................................................... 3-141

Loopbacks at the E1 link side ....................................................................................................................................... 3-142

Loopbacks at the U interface (subscriber side) ...................................................................................................... 3-143

Loopbacks at the HDSL interface ................................................................................................................................ 3-146

Loopbacks at the SHDSL port ....................................................................................................................................... 3-151

BER testing with external loopback devices ........................................................................................................... 3-154

Subscriber line test via external test head ................................................................................................................ 3-155

Performance management

Overview ................................................................................................................................................................................. 3-157

Performance management definitions ......................................................................................................................... 3-158

Performance management data ...................................................................................................................................... 3-160

Performance management operations .......................................................................................................................... 3-162

V5.2 protocol error logging ............................................................................................................................................ 3-163

Traffic statistics and COMDAC load measurement ............................................................................................. 3-166

Measurement data collection .......................................................................................................................................... 3-167

Measurement types ............................................................................................................................................................. 3-168

Post-processing and presentation .................................................................................................................................. 3-170

Security management

Overview ................................................................................................................................................................................. 3-171

Security management capabilities ................................................................................................................................ 3-172

4 OAM&P for ATM xDSL services

Overview ...................................................................................................................................................................................... 4-1

ATM configuration management

Overview ...................................................................................................................................................................................... 4-3

ATM configuration management - Memory administration ................................................................................... 4-4

ATM configuration management - Software management ..................................................................................... 4-5

ATM configuration management - Turn-up and service provisioning ............................................................... 4-7

Shelf provisioning .................................................................................................................................................................... 4-8

System configuration ............................................................................................................................................................ 4-10

Pack and port provisioning ................................................................................................................................................ 4-12

ATM cross-connect provisioning ..................................................................................................................................... 4-13

Daisychaining (E3/DS3 and STM-1/OC-3c) .............................................................................................................. 4-19

ATM configuration management - Inventory management .................................................................................. 4-20

ATM fault management

Overview ................................................................................................................................................................................... 4-23

ATM fault management - Maintenance ........................................................................................................................ 4-24

ATM fault management - Alarms, status conditions, and events ..................................................................... 4-27

ATM fault management - Protection switching ........................................................................................................ 4-35

ATM fault management - Testing ................................................................................................................................... 4-37

Feeder loopback testing ..................................................................................................................................................... 4-41

Diagnosing network troubles using F4/F5 OAM cells .......................................................................................... 4-45

ATM payload loopback ....................................................................................................................................................... 4-47

SHDSL loopback test ........................................................................................................................................................... 4-48

CPE Routing - remote access to CPEs ......................................................................................................................... 4-49

ATM xDSL performance management

Overview ................................................................................................................................................................................... 4-51

ATM feeder performance management ........................................................................................................................ 4-52

ADSL performance management ................................................................................................................................... 4-60

SHDSL performance management ................................................................................................................................. 4-65

IMA performance management ........................................................................................................................................ 4-67

ATM cell traffic ...................................................................................................................................................................... 4-68

ATM security management

Access security ...................................................................................................................................................................... 4-73

5 System planning and engineering for NB services

Overview ...................................................................................................................................................................................... 5-1

System planning

Overview ...................................................................................................................................................................................... 5-3

System capacity of the AnyMedia ® LAG 1900 Shelf .............................................................................................. 5-5

System capacity of the AnyMedia ® LAG 4300 Shelf .............................................................................................. 5-8

System capacity of the AnyMedia ® ETSI V5 Shelf ................................................................................................ 5-11

Growth scenarios ................................................................................................................................................................... 5-16

Engineering POTS-only configurations ........................................................................................................................ 5-19

Configurations with V5.1 interfaces .............................................................................................................................. 5-23

Configurations with V5.2 interfaces .............................................................................................................................. 5-25

Engineering mixed POTS/ISDN configuration ......................................................................................................... 5-26

Engineering configurations with PLLs ......................................................................................................................... 5-33

Engineering POTS + ADSL service with LPZ110 and LPA432 APs .............................................................. 5-36

Using the BB ATM Operations Channel to transport NB OAM&P ................................................................ 5-38

Traffic engineering

Overview ................................................................................................................................................................................... 5-41

Reference loads ....................................................................................................................................................................... 5-42

Call capacity evaluations .................................................................................................................................................... 5-43

Configuration limits affecting the system traffic ...................................................................................................... 5-45

Traffic engineering ................................................................................................................................................................ 5-46

Overload control ..................................................................................................................................................................... 5-52

Interface configurations

Overview ................................................................................................................................................................................... 5-53

Z interface for POTS or ALL services ......................................................................................................................... 5-55

Configuration data POTS services .................................................................................................................................. 5-56

Configuration data ALL services ..................................................................................................................................... 5-57

Z interface subscriber loop dimensioning .................................................................................................................... 5-58

U interface for ISDN BRA and DLL services .......................................................................................................... 5-61

Configuration data ISDN BRA services ....................................................................................................................... 5-62

Configuration data DLL services .................................................................................................................................... 5-63

DLL services via managed NTU ..................................................................................................................................... 5-64

HDSL interface for V5 ISDN PRA, V3 ISDN PRA, VLL, GLL, UVLL or UGLL services ............... 5-66

Configuration data V5 ISDN PRA services ............................................................................................................... 5-79

Configuration data V3 ISDN PRA services ............................................................................................................... 5-80

Configuration data n × 64 kbps GLL services .......................................................................................................... 5-81

Configuration data n × 64 kbps VLL services .......................................................................................................... 5-82

Configuration data UGLL services ................................................................................................................................. 5-83

Configuration data UVLL services ................................................................................................................................. 5-84

E1 (2-Mbps) interface .......................................................................................................................................................... 5-85

E1 interfaces on IO_E1 ....................................................................................................................................................... 5-86

E1 interfaces on AP_E1 ...................................................................................................................................................... 5-87

V5 parameters ......................................................................................................................................................................... 5-89

Ringer configuration in AnyMedia ® LAG 4300 Shelf ........................................................................................... 5-90

Ringer configuration in AnyMedia ® ETSI V5 Shelf .............................................................................................. 5-91

Product reliability

Overview ................................................................................................................................................................................... 5-92

Product reliability .................................................................................................................................................................. 5-93

6 System planning and engineering for ATM xDSL services

Overview ...................................................................................................................................................................................... 6-1

ATM xDSL system capacity

Overview ...................................................................................................................................................................................... 6-5

ATM xDSL system capacity of the AnyMedia ® Access System ......................................................................... 6-6

Maximum number of shelves in a daisy-chain set ..................................................................................................... 6-9

Maximum number of virtual connections .................................................................................................................... 6-10

Maximum traffic per feeder .............................................................................................................................................. 6-12

ATM xDSL data transfer performance ......................................................................................................................... 6-15

ATM xDSL growth, degrowth and migration scenarios

Overview ................................................................................................................................................................................... 6-18

Introduction .............................................................................................................................................................................. 6-19

Growth scenarios ................................................................................................................................................................... 6-20

Degrowth scenarios ............................................................................................................................................................... 6-23

Migrating from simplex to duplex AFM mode ......................................................................................................... 6-24

Migrating from duplex to simplex AFM mode ......................................................................................................... 6-25

Migration from an ATM xDSL system to an IP system via IP-AFM ............................................................. 6-26

ATM xDSL installation and connection recommendations

Overview ................................................................................................................................................................................... 6-27

Installation recommendations ........................................................................................................................................... 6-28

Initial deployment with no ATM xDSL services ...................................................................................................... 6-30

Growth situations ................................................................................................................................................................... 6-31

Cables and hardware ............................................................................................................................................................ 6-32

Large ATM xDSL deployments ....................................................................................................................................... 6-33

Interoperability ........................................................................................................................................................................ 6-34

Engineering narrowband to ADSL upgrade ................................................................................................................ 6-35

Engineering for ADSL over ISDN ................................................................................................................................. 6-39

Engineering the BB ATM Operations Channel for shelves cascaded via E1IMA APs ............................ 6-40

New installation concept ..................................................................................................................................................... 6-42

Engineering the LAN connection ................................................................................................................................... 6-45

BB ATM Operations Channel ......................................................................................................................................... 6-50

ATM xDSL Port Numbering ............................................................................................................................................. 6-52

Quality of Service Provisioning

Overview ................................................................................................................................................................................... 6-55

Connection Admission Control algorithm ................................................................................................................... 6-56

Shelf provisioning for QoS ................................................................................................................................................ 6-57

Special considerations for a daisy chain ...................................................................................................................... 6-62

xDSL transmission profile effect on QoS .................................................................................................................... 6-64

ATM traffic profile provisioning for QoS ................................................................................................................... 6-65

Cross-connect provisioning .............................................................................................................................................. 6-67

Overbooking factor ............................................................................................................................................................... 6-69

Congestion management schemes ................................................................................................................................... 6-70

Traffic shaping - Policing - Scheduling ....................................................................................................................... 6-72

ATM xDSL system turn-up and service provisioning scenarios and parameters

Overview ................................................................................................................................................................................... 6-74

Introduction .............................................................................................................................................................................. 6-75

Turn-up provisioning ............................................................................................................................................................ 6-77

Service activation ................................................................................................................................................................... 6-81

Shelf cascading via E1IMA APs ..................................................................................................................................... 6-83

Port provisioning and addressing for duplex mode AFMOs ............................................................................... 6-85

Slot numbering and AIDs for the AnyMedia ® LAG Shelves ............................................................................. 6-88

Service states .......................................................................................................................................................................... 6-90

Profiles ....................................................................................................................................................................................... 6-96

ADSL parameters - port settings ..................................................................................................................................... 6-98

Setting other ADSL transmission parameters using the ADSL transmission profile .............................. 6-102

SHDSL parameters - port settings ................................................................................................................................ 6-106

E1IMA AP settings ............................................................................................................................................................. 6-109

ATM traffic parameters ..................................................................................................................................................... 6-111

Parameters in failure report profiles ............................................................................................................................ 6-112

Default values for ATM xDSL system provisioning parameters

Overview ................................................................................................................................................................................. 6-114

Turn-up and service activation provisioning default values .............................................................................. 6-116

Predefined ADSL transmission profiles ..................................................................................................................... 6-128

Predefined SHDSL transmission profiles .................................................................................................................. 6-132

Predefined ADSL performance management profiles .......................................................................................... 6-133

Predefined SHDSL performance management profiles ....................................................................................... 6-134

Predefined ATM traffic profiles .................................................................................................................................... 6-135

Predefined ATM Traffic statistics threshold profiles ............................................................................................ 6-137

Predefined failure report profiles .................................................................................................................................. 6-138

Parameters in DMT profile ............................................................................................................................................. 6-142

Parameters in RFI notch profiles .................................................................................................................................. 6-143

ADSL transmission specification summary .............................................................................................................. 6-144

Alarm severity values

Alarm severity and GSI ATM xDSL identifiers tables ........................................................................................ 6-146

ATM feeders

Overview of ATM feeders ............................................................................................................................................... 6-159

ATM E3/DS3 feeder .......................................................................................................................................................... 6-161

E3/DS3 connections to the ATM backbone network when using a single AFME3/DS3 in simplex mode
with no daisychaining .................................................................................................................................................... 6-163

E3/DS3 connections to the ATM backbone network when using two AFME3/DS3s in duplex mode
with no daisychaining .................................................................................................................................................... 6-164

E3/DS3 Daisychaining capability ................................................................................................................................. 6-165

ATM E1 feeder (Background on IMA) ..................................................................................................................... 6-170

ATM E1 feeder ..................................................................................................................................................................... 6-171

ATM STM-1/OC-3c feeder ............................................................................................................................................. 6-174

STM-1/OC-3c Daisychaining capability .................................................................................................................... 6-177

AFMOs in duplex mode ................................................................................................................................................... 6-180

Optical couplers ................................................................................................................................................................... 6-187

Optical AFM Attenuation Design ................................................................................................................................. 6-188

ATM xDSL synchronization and timing

Overview ................................................................................................................................................................................. 6-193

Synchronization and timing for E3/DS3 ATM network feeder interface ..................................................... 6-194

Synchronization and timing for E1 ATM network feeder interface ............................................................... 6-196

Synchronization and timing for STM-1/OC-3c ATM network feeder interface ....................................... 6-198

ATM xDSL timing .............................................................................................................................................................. 6-200

Synchronization and timing for the AnyMedia ® LAG 4300 Shelf ................................................................ 6-201

Miscellaneous

Overview ................................................................................................................................................................................. 6-202

ATM xDSL product reliability ....................................................................................................................................... 6-203

ATM xDSL system powering ......................................................................................................................................... 6-204

Testing of drops on ATM xDSL application packs ............................................................................................... 6-205

A ATM xDSL Engineering Work Orders for AFMDS3

Overview ..................................................................................................................................................................................... A-1

Work Order for ATM xDSL Services — Simplex AFMDS3 ............................................................................... A-3

Work Order for ATM xDSL Services — Duplex AFMDS3 ............................................................................... A-27

B ATM xDSL Engineering Work Orders for AFME3

Overview ..................................................................................................................................................................................... B-1

Work Order for ATM xDSL Services — Simplex AFME3 ................................................................................... B-3

Work Order for ATM xDSL Services — Duplex AFME3 .................................................................................. B-28

C ATM xDSL Engineering Work orders for AFMO

Overview ..................................................................................................................................................................................... C-1

Work Order for ATM xDSL Services — Simplex AFMO ..................................................................................... C-3

Work Order for ATM xDSL Services — Duplex AFMO .................................................................................... C-28

D ATM xDSL Engineering Work Order for AFME1

Overview ..................................................................................................................................................................................... D-1

Work Order for ATM xDSL Services — Simplex AFME1 .................................................................................. D-3

Glossary

Index

Purpose
The Applications and Planning Guide (APOG) for the AnyMedia ® Access System
consists of three parts which are closely related to each other. They are not considered
to be independent information products. The titles of the three APOG parts are:
• AnyMedia ® Access System, Overview (363-211-585)
• AnyMedia ® Access System, Narrowband and ATM xDSL services (363-211-586)
• AnyMedia ® Access System, IP-based services (363-211-587).
The two APOG parts Overview and Narrowband and ATM xDSL services replace the
former combined APOG with the ordering number 363-211-110.
This APOG part Narrowband and ATM xDSL services provides the description of the
narrowband services and the ATM xDSL services of the AnyMedia ® Access System.
The following information is provided in this information product:
• Description of the various services
• Description of the physical interfaces
• Operations, administration, maintenance, and provisioning (OAM&P) actions and
tasks for narrowband services
• Operations, administration, maintenance, and provisioning (OAM&P) actions and
tasks for ATM xDSL services
• System planning and engineering for narrowband services
• System planning and engineering for ATM xDSL services
• ATM xDSL engineering work orders.

Reason for reissue

This is Issue 6 of the AnyMedia ® Access System, Applications and Planning Guide,
Narrowband and ATM xDSL services.
It has been reissued to include the following:
• Support of SHDSL Loopback tests
• CPE Routing - Remote Access to CPEs
• Downstream SRA supported by LPA420 and LPA833.
Note that the features descriptions may be spread across the three APOG parts,
depending on where the description matches best the overall context.
....................................................................................................................................................................................................................................
363-211-586 xvii
Issue 6, July 2007
,
About this information product

Intended audience
Customers who use this APOG include the following:
• Standardization groups
• Product evaluators
• Network planners
• Engineers.

Conventions used
The following conventions are used throughout this Applications and Planning Guide,
Narrowband and ATM xDSL services.
Acronyms and abbreviations
In the text acronyms are expanded the first time they are used in the main text of a
chapter (for example permanent leased line (PLL)). If the acronym is a trademark, it
will not be spelled out. A list of acronyms is provided at the end of this document.
Apparatus code followed by empty parentheses
An apparatus code followed by empty parentheses ″()″ includes the letter-suffixed
versions of the circuit pack. For example, LPP100( ) represents the LPP100 AP and/or
the LPP100B AP.
Commands
AnyMedia ® Access System TL1 command names and messages are displayed in
constant-width font and are uppercase (for example RTRV-COND).
Terms used (alphabetically ordered)
The following are terms used in this information product that may have a different
meaning than the general or common use of the term.
• a/b-cables refer generically to the tip/ring pair cables that attach to the faceplate of
all application packs (APs).
• In the AnyMedia ® Access System, the term access means that the system provides
the primary service interface for the subscriber to enter the network.
• ADSL line refers to the twisted copper pair carrying ADSL and narrowband
services.
• ADSL modem means the ADSL data circuit-terminating equipment at the
subscriber’s site.
• ADSL services refers to all services provided by ADSL APs and by the ADSL part
of combo APs.
• ADSL2/ADSL2+ is the ADSL technology which refers to the ITU-T standard
G.992.3 to G.992.5. This term will be used to distinguish between the legacy
ADSL technology and the next ADSL generation.
• AFM refers to all ATM feeder multiplexers regardless of the feeder type.

• The ATM feeder multiplexer AFME3 provides an E3 ATM user network interface.
If a DS3 interface is required the ATM feeder multiplexer AFMDS3 has to be used
instead, if an E1 interface is required the ATM feeder multiplexer AFME1 has to be
used, or if an STM-1/OC-3c interface is required the ATM feeder multiplexer
AFMO has to be used.
• The term AnyMedia ® ETSI V5 Shelf is used when the text especially refers to the
basic ETSI shelf with 16 AP slots. It houses the COMDAC(s), CIU and AFM(s).
The AnyMedia ® ETSI V5 Shelf can house narrowband services and ATM xDSL
services.
• The term AnyMedia ® LAG Shelf is generally used for an AnyMedia ® shelf with a
high capacity backplane, independently of the physical design of the shelf. It may
house COMDAC(s), CIU, AFM(s), IPFM(s) and APs. Currently two AnyMedia ®
LAG Shelves are available, the AnyMedia ® LAG 1900 Shelf and the AnyMedia ®
LAG 4300 Shelf.
In comparison to an AnyMedia ® ETSI V5 Shelf the backplane of the AnyMedia ®
LAG Shelf has expanded capacity.
• The AnyMedia ® LAG 1900 Shelf is a specific LAG Shelf. It contains seven 1N
high slots for 1N-sized common packs and 17 3N high slots for common packs
(COMDAC, CIU, IPFM, AFM) and application packs with subscriber interfaces.
The AnyMedia ® LAG 1900 Shelf can house narrowband services, ATM xDSL
services and/or IP-based services.
• The AnyMedia ® LAG 4300 Shelf is a specific LAG Shelf. It is designed as a
double-row LAG Shelf housed in an indoor cabinet.
Each AnyMedia ® LAG 4300 Shelf may contain one NB subsystem, one IP-based
subsystem and up to two BB subsystems.
In comparison to an AnyMedia ® ETSI V5 Shelf the backplane of the AnyMedia ®
LAG 4300 Shelf has expanded capacity.
• The AnyMedia LAG 4300 System can be delivered in three configurations:
– Configuration 1 - One AnyMedia ® LAG 4300 Shelf
– Configuration 2- Two AnyMedia ® LAG 4300 Shelves
– Configuration 3- Two AnyMedia ® LAG 4300 Shelves and two AnyMedia ®
ETSI V5 Shelves.
• The term AnyMedia ® Mainshelf is used in a description that refers to any
AnyMedia ® shelf that may contain COMDAC(s), CIU, AFM(s), IPFM(s) and APs,
regardless whether it is an AnyMedia ® ETSI V5 Shelf, an AnyMedia ® LAG Shelf
or an AnyMedia ® 800 Shelf.
• The term AnyMedia ® shelves is used whenever the text does not need to
distinguish between the shelf types. It is mostly used where services and service
packs are described.
• The AnyMedia ® 800 Shelf consists of a shelf very similar to an AnyMedia ® ETSI
V5 Shelf, but 8 slots are equipped with an internal power subshelf instead of APs.
• ATM Operations Channel is a an ATM permanent virtual connection configured to
transmit OAM&P information.

• ATM OAM&P interfaces in the AnyMedia ® Access System include the following
alternatives for connecting OAM&P interfaces:
– Console port on the AFM faceplate
– 10BaseT port on the AFM faceplate
– ATM Operations Channel
• ATM xDSL services refer to all typically supported ADSL, SDSL, and SHDSL
services and future digital subscriber line (DSL) services.
• In some occurrences the term broadband is used for ATM xDSL related terms
where ATM xDSL would be too specific or not commonly used (e.g. broadband
bus).
• Combo pack refers to an AP that supports narrowband services and ADSL services
combined on one physical subscriber port.
• The term customer premises equipment (CPE) in general covers subscriber’s
installation and subscriber’s terminal. For ADSL lines the CPE consists among
other equipment of an ADSL modem and a splitter (to separate the narrowband
signal from the data signal). If both units are meant as a whole the term customer
premises equipment (CPE) is used in this manual.
• The term DS3 interface refers to a bit rate of 44.736 Mbps and a framing
according to ITU-T recommendations G.804, I.432 and ANSI T1.107. without
specifying the physical interface.
• The term DSX-3 interface refers to everything that DS3 refers to with the addition
of a specific physical interface according to Bellcore standard GR-499. The ATM
feeder multiplexer AFMDS3 provides a DSX-3 interface. In this manual the more
general term DS3 interface is used.
• E1 interface refers to the 2048-kbps digital feeder interfaces on the network side.
• E3 interface refers to the 34.368-Mbps digital feeder interface that carries the ATM
payload cells. The E3 interface is provided by the ATM feeder multiplexer AFM.
• The general term Element Management System (EMS) denotes a software tool used
for management actions and tasks. The element management system designed for
the AnyMedia ® Access System is the Navis ™ AnyMedia ® Element Management
System (NAM).
• The AnyMedia ® Graphical System Interface software (GSI) includes narrowband,
ATM xDSL and IP-based services.
• The term GSI/EMS stands for the function of the network management system for
the AnyMedia ® Access System, independent of using the GSI or another EMS like
the NAM.
• Inband signaling via ATM Operations Channel within ATM permanent virtual
connection (PVC) means sending messages not via a special OAM&P interface but
embedded in the ATM cell stream.
• The term IP-based services refers to all services that are transported via the IP
network.
• The term legacy ADSL refers to ADSL technology regarding ITU-T G.992.1. This
term will be used to distinguish between the first ADSL generation and the next
(ADSL2/ADSL2+) technology.
...................................................................................................................................................................................................................................
xx 363-211-586
Issue 6, July 2007
,
About this information product

• Mixed configuration means a configuration of the AnyMedia ® shelves including

packs for narrowband services and for ATM xDSL services.
• The Navis ™ AnyMedia ® Element Management System (NAM) is an element
management system (EMS) that includes network management capabilities for
narrowband and ATM xDSL services.
• Narrowband services typically include POTS services, permanent leased line (PLL)
and ISDN as well as n-times 64 kbps to 2 Mbps.
• The term pack is generally used for common packs (e.g. COMDAC, CIU, IO_E1,
IO_HDLC, PFU, AFME3, AFMDS3) and application packs (APs).
• SDSL services refers to all services provided by SDSL APs.
• SHDSL services refers to all services provided by SHDSL APs.
• The term [S]HDSL refers to both: HDSL and SHDSL (narrowband services).
• The term system application is used here for the AnyMedia ® Access System when
the text refers to how a certain network element is used with respect to services.
• The term system configuration is used here for the AnyMedia ® Access System
when the text refers to as a system equipped with certain packs or units for a
certain application including the related database.
• TDM COMDAC generally refers to a COMDAC in a system configuration with
IO_E1 packs where the narrowband signals are transported within physical E1 links
across a TDM network.
• TL1 system interface (TL1SI) means any interface for operations using TL1
commands.
• V5.x is used whenever the following text refers to V5.1 as well as to V5.2.
• xDSL service means any ATM xDSL service transmitted over twisted pairs.
Examples are ADSL, SDSL, SHDSL, universal asymmetric digital subscriber line
(UDSL), and very high bit rate digital subscriber line (VDSL).
• In this manual the subscriber interface for analog POTS is named Z interface. In
some countries this interface can be called a/b-interface where the a-leg sometimes
may be called tip and the b-leg ring.
Trademarks
Trademarks of Alcatel-Lucent and other companies are in italics. They are identified
with the registered mark ( ®) or trademark (™) symbol the first time the trademarks are
used in the text (for example Alcatel-Lucent AnyMedia ® Access System).

Related documentation
The following is orderable documentation related to the AnyMedia ® Access System
and for additional components. For the ordering address see “How to order” (p. xxiii).
Additionally, these information products are accessible from the Alcatel-Lucent’
internal webpage: http://access.de.lucent.com/ACCESS/cdoc/index.html

Manual Type Comcode CIC Ordering

Number (1)
Applications and Planning Guide (APOG), Overview 109 562 744 363-211-585

Manual Type Comcode CIC Ordering

Number (1)
Applications and Planning Guide (APOG), Narrowband and 109 562 751 363-211-586
ATM xDSL services
Applications and Planning Guide (APOG), IP-based services 109 562 769 363-211-587
Data Sheet Book 109 218 651 363-211-251

Ordering Guide 109 097 782 363-211-144

Commands and Procedures for Narrowband Services with 109 105 635 363-211-119
TDM COMDAC
Commands and Procedures for ATM xDSL Services 109 024 737 363-211-133
Commands and Procedures for IP-based Services 109 562 736 363-211-555
Installation Manual for DC-Powered Racks for ETSI V5 and 109 576 140 363-211-603 ( 2)
LAG 1900 Shelves
Installation Manual for the Mainshelf and DC-powered racks 109 024 752 363-211-207 ( 3)
Installation Manual for AC-powered racks 109 024 745 363-211-206
AnyMedia ® LAG 4300 System, Installation Manual (IM) 109 461 939 363-211-256
Customer Documentation on CD-ROM 108 298 787 363-211-114

Notes:
1. For the ordering address see “How to order” (p. xxiii).
2. Applicable for the new DC-powered racks based on CABI600 mechanics (J1C293B-1 L1 and
J1C301B-1 L1)
3. Applicable for the established DC-powered racks J1C283B-1 L2 and J1C293A-1 L2.

Print copy (hard copy)

All listed documents are available in print.
CD-ROM
The following table lists the information products for the AnyMedia ® Access System
which are available in PDF format and/or in HTML format on CD-ROM. An Adobe
Acrobat Reader ® is provided to view them.

CD-ROM Comcode Ordering Number

AnyMedia ® Access System Customer Documentation on 108298787 363-211-114 (1)
CD-ROM includes:
• Applications and Planning Guide (APOG), Overview in
pdf format
• Applications and Planning Guide (APOG), Narrowband
and ATM xDSL services in pdf format
• Applications and Planning Guide (APOG), IP-based
services in pdf format
• Data Sheet Book in pdf format
• Ordering Guide in pdf format
• Commands and procedures for Narrowband Services with
TDM COMDAC in HTML and pdf format
• Commands and Procedures for ATM xDSL Services in
HTML and pdf format
• Commands and Procedures for IP-based Services in
HTML and pdf format
• Installation Manual for the Mainshelf and for
DC-powered Racks in pdf format
• Installation Manual for AC-powered Racks in pdf format
• Description of TL1 commands in HTML format

Notes:
1. For the ordering address see “How to order” (p. xxiii).

How to order
For ordering information products or to request placement on the standing order list,
send or call in an order as follows.
For ordering, a purchase order number, or charge card number is required with all
orders. A charge card number cannot be accepted from outside USA.

Mail Order Telephone/Fax Order/Email Web Orders

Alcatel-Lucent Within USA: Commercial customers:
Attention: Order Entry Phone: http://www.lucentdocs.com or
2855 N. Franklin Road 1-888-LUCENT8 http://www.lucent8.com
USA-Indianapolis, IN (1-888-582-3688) Alcatel-Lucent Associates:
46219 FAX from USA: http://www.cic.lucent.com
+1-800-566-9568
Outside USA:
Phone:
+1-317-322-6836
FAX Outside USA:
+1-317-322-6699
E-mail:
[email protected]

Methods of payment for Commercial Customers:

• Credit card is required for orders totaling $1000 or less. Visa, MasterCard, and
American Express are accepted. Prepayment by check is not acceptable.
• Orders totaling over $1000 may be paid for using credit card, or invoice upon
receipt of a purchase order. Purchase orders may be faxed or mailed using the
information provided above.
Methods of payment for Alcatel-Lucent Associates:
• Orders placed by Alcatel-Lucent associates are billed using a cost center number.
One-time orders include the contents for the current document issue in effect at the
time of order.
You may request an update on the standing order list for all later reissues of any
document. The standing order list for each document provides automatic distribution
for all reissues of the document.

How to comment
To comment on this information product, go to the Online Comment Form
(http://www.lucent-info.com/comments/enus/) or e-mail your comments to the
Comments Hotline ([email protected]).
Because customer satisfaction is extremely important to Alcatel-Lucent, every attempt
is made to encourage feedback from customers about our information products.

Purpose
Alcatel-Lucent AnyMedia ® Access System offers a wide range of services to meet the
telecommunications provider’s needs. This chapter details the various services
supported by the AnyMedia ® Access System.
Note that all kind of IP-based services are covered in the Applications and Planning
Guide for IP-based Services (363-211-587).
Typical applications of the AnyMedia ® Access System in telecommunication networks
are shown in the Applications and Planning Guide Overview (363-211-585).

Contents

Narrowband services 1-2

Overview 1-3
V5.x (switched) services / Subscriber side 1-4
V5.x (switched) services / Network side 1-6
V3 switched services / Subscriber side 1-9
V3 switched services / Network side 1-10
Non-switched services / Subscriber side 1-11
Non-switched services / Network side 1-14
Host/remote terminal interconnection service 1-15
ATM xDSL-based services and configurations 1-16
ATM xDSL services 1-17
Quality of service for ATM xDSL services 1-24
Configuration options for the ATM xDSL subsystem 1-26
®
Daisychaining of AnyMedia LAG Shelves 1-32
Local shelf daisychaining 1-33
Remote shelf daisychaining via SDH ring 1-34

Narrowband services

Purpose
The narrowband services supported by the AnyMedia ® Access System are shown on
the next pages.
Narrowband services
Important! In the LAG Shelves special COMDAC types with extended
functionality are used to support NB services. For a description refer to the
Datasheet Book (363-211-251).
Important! An AnyMedia ® Access System acting as remote terminal in a
host/remote terminal application solely supports POTS, ISDN BRA, V5 SPALL and
V5 SPDLL subscriber services.

Contents

V5.x (switched) services / Subscriber side

Switched NB services subscriber side

The following narrowband services are supported on the subscriber side:
• POTS service via Z interface
• ISDN BRA service via U interface
• V5 ISDN PRA service via HDSL interface.

POTS service
The POTS service via Z interface provides the connection of analog subscriber lines.
Normally the Z interface is used for switched telephony. It carries signals such as
voice and voice-band data and multi-frequency push-button signals, etc. It is
provisioned on a Z port which must provide the DC feeding of the subscriber’s
terminal and functions such as DC signaling, ringing, periodic pulse metering, etc.,
where appropriate.

ISDN BRA service

The ISDN BRA service via U interface provides the connection of digital switched
subscriber lines. The U interface can be provisioned to use one or two B-channels (1
or 2 × 64-kbps transmission capability for voice and data) and one D-channel (16-kbps
transmission capability for signaling and data).
Following line codings are used:
• 2B1Q
• 4B3T.

V5 ISDN PRA service

The V5 ISDN primary rate access (PRA) service via HDSL interface according to
ETSI ETS 300233 provides the connection of a private branch exchange (PBX).
Depending on the [S]HDSL application mode the following capacity is available:
• Point-to point mode (HDSL application mode)
The full transmission capability of 30 B-channels (30 × 64 kbps) and one
D-channel (64 kbps) is available in this mode.
• Single-pair mode (HDSL application mode).
The transmission capability of 15 B-channels (15 × 64 kbps) and one D-channel
(64 kbps) is available in this mode.
• Point-to-point single pair mode (SHDSL application mode)
The full transmission capability of 30 B-channels (30 × 64 kbps) and one
D-channel (64 kbps) is available in this mode.
For more details and for configuration examples refer to “HDSL application modes”
(p. 5-69)and “SHDSL application modes” (p. 5-74)
A V5 ISDN PRA subscriber is connected to the network via a V5.2 interface.
...................................................................................................................................................................................................................................
1-4 363-211-586
Issue 6, July 2007
Services V5.x (switched) services / Subscriber side

V5 SPALL service
The semipermanent analog leased line (SPALL) service is transported via a
semipermanent leased line using a 2-wire Z interface for analog subscriber terminals.
Semipermanent analog leased line service is used for purposes other than telephony -
for example, data transmission with modems that do or do not contain equalizers. The
AnyMedia ® Access System supports SPALL according to ITU M.1020, ITU M.1025
and ITU M.1040.

V5 SPDLL service
The semipermanent digital leased line (SPDLL) service is transported via a
semipermanent leased line (SPLL) using a 2-wire U interface for digital subscriber
terminals. For example a digital leased line service is used for data transmission with
terminal adapters. The AnyMedia ® Access System supports DLLs for international
leased lines according to ETR 080, ETS 300 297 and ETS 300 012. On the
subscriber side the subscriber line is terminated by a network termination.
The SPDLL service offers different transmission capabilities: It may be defined as
single channel SPLL using one B-channel of the U interface as well as multiple
channel SPLL using one or two B-channels of the U interface.
Two B-channels of the U interface offer two independent 64-kbps bit streams at the
terminal equipment (TE). If the subscribers want higher data rates in one bit stream (N
× 64-kbps) at the TE, multiple B-channels of more than one U interface can be used in
connection with appropriate terminal adapters.
An SPDLL service can be provided by using a managed NTU, that is a 2B1Q ISDN
digital subscriber line NTU which is fully managed by the AnyMedia ® Access System.
The NTU provides the subscriber a single channel operating at one of many speeds,
depending on the NTU type and configuration, from 1.2 kbps through to 128 kbps.
Management of managed NTUs is performed via the D-channel, so that channel is not
available to the subscriber. The NTU management requires the use of one of the
HDLC channels on the COMDAC. The use of a single HDLC channel to manage all
NTUs imposes the following restrictions:
• The AnyMedia ® Access System can communicate with one NTU at a time.
• If an NTU is not responding then any time spent waiting for the NTU to time-out
blocks communication with other NTUs. This time-out is at most 10 seconds.
• Managed NTUs must be polled on a regular basis to acquire alarm information.
With a single HDLC channel available and many NTUs configured it will take a
significant amount of time to poll all NTUs.

V5.x (switched) services / Network side

V5.1 and V5.2 switched services

The AnyMedia ® Access System provides up to sixteen 2-Mbps (E1) links. Each link
provides 31 channels of 64 kbps (TS0 is used for synchronization). The AnyMedia ®
Access System can be configured to support V5.1 and V5.2 interfaces. A mix of V5.1
and V5.2 switched services on the same system is possible.

Channel types
An E1 channel can be either of the following two types:
• Bearer channel for transporting speech or data
• Communication channel (CC) for transporting control information. Communication
channels are transmitted in provisioned timeslots which carry
– ISDN D-channel information
– PSTN signaling information
– Port interface control information.

V5.1 switched services

The V5.1 network interface specification (ETS 300 324) does not support subscriber
traffic concentration and therefore has no dynamic timeslot assignments. Consequently,
the number of 64-kbps bearer channels at the V5 interface determines the number of
subscriber interfaces which may be configured for operation.
The V5.1 network interface consists of one 2-Mbps (E1) link. One 2-Mbps link
comprises 32 64-kbps timeslots. Between one and three of them are used as
communication channels (CC); up to two CCs for POTS only and up to three CCs for
POTS/ISDN mixed mode. Timeslot 0 is allocated for synchronization and maintenance,
the others are used as bearer channels. Typically there is one communication channel
per 2-Mbps link. A maximum number of 16 × V5.1 network interfaces can be
connected to one AnyMedia ® ETSI V5 Shelf or LAG Shelf.
The V5 bearer channels can be assigned to any arbitrary subscriber port. Each
subscriber has a dedicated channel within the E1 link.

V5.1 interface protocols

The V5.1 interface specification specifies the following protocol which is transported
in communication channels:
• Port control and common control protocol.
The protocol is used for blocking and unblocking of subscriber ports and interface
related control information.

V5.1 subscriber protocols

The V5.1 interface specification specifies the following subscriber protocols:
• PSTN signaling
• ISDN D-channel information.

V5.2 switched services

The V5.2 network interface specification (ETS 300 347) allows subscriber traffic
concentration, has dynamic timeslot assignments and allows the optional protection of
E1 link faults. One V5.2 interface has up to sixteen 2-Mbps links. Furthermore up to
three 64-kbps channels per 2-Mbps link can be used as CCs. A minimum of two CCs
is sufficient for a V5.2 interface. The actual number of CCs can be freely configured:
Provisionable CCs (per V5.2 interface)

Provisioned Links Active CCs Standby CCs

1 1 or 2 or 3 -
2 or more 1 1
2 1 or 2
3 to 47 1 or 2 or 3

Because of the subscriber traffic concentration the AnyMedia ® Access System can be
equipped with a maximum of up to 512 × 64-kbps subscriber channels. The number of
configured subscriber channels is independent of the number of connected 2-Mbps
links on the V5.2 interface, but it has an impact on the subscriber traffic concentration
ratio.
The V5 bearer channels can be associated to any arbitrary subscriber port.

V5.2 interface protocols

The V5.2 interface specification specifies the following protocols:
• Port control and common control protocol
The protocol is used for blocking and unblocking of subscriber ports and interface
related control information.
• Link control protocol
In contrary to the V5.1 interface, the V5.2 interface comprises several physical
interfaces. To be able to identify the individual physical interfaces the V5.2
interface uses the link control protocol. Besides identification of physical links, the
link control protocol is used for blocking and unblocking of V5 links.
• Protection protocol
The protection protocol of the V5.2 interface is used to switch logical
communication paths on a failed communication channel to a stand-by channel.
• Bearer channel connection protocol (BCC protocol).
The BCC protocol is a V5.2 protocol which allocates bearer channels on demand.

V5.2 subscriber protocols

The V5.2 interface specification specifies the following subscriber protocols:
• PSTN signaling
• ISDN signaling
• ISDN packet information
• ISDN framing information.

V3 switched services / Subscriber side

Switched NB service subscriber side

The following narrowband service is supported on the subscriber side:
• V3 ISDN PRA service via HDSL interface.

V3 ISDN PRA service

The V3 ISDN primary rate access (PRA) service via HDSL interface according to
ETSI ETS 300 233 provides the connection of a private branch exchange (PBX).
To support V3 ISDN PRA service the
• HDSL interface must be provisioned in the V3 point-to-point application mode (see
“HDSL application modes” (p. 5-69)) or the
• HDSL interface must be provisioned in the V3 point-to-point single pair application
mode (see “SHDSL application modes” (p. 5-74)).
In these modes the full transmission capability of 32 channels (32 × 64 kbps) is
available.
A V3 ISDN PRA subscriber is connected to the network via a V3 interface.

V3 switched services / Network side

V3 switched services
The AnyMedia ® Access System provides up to sixteen 2-Mbps (E1) links. Each link
may be used for V3 service. Thus a maximum of sixteen V3 ISDN PRA subscribers
can be provisioned in the AnyMedia ® Access System. Each link used for V3 service
provides 32 channels of 64 kbps (including timeslot 0).

Channel types
Timeslot 0 is used for OAM&P as defined in ETSI ETS 300 233 and timeslot 16
carries the D-channel information for one ISDN PRA subscriber. The remaining
timeslots are used for bearer channels.

Non-switched services / Subscriber side

Non-switched services subscriber side

The following non-switched services are supported on the subscriber side:
• ALL service via Z interface
• DLL service via U interface
• n × 64 kbps digital leased line services via HDSL interface:
– GLL service via a G.703 interface
– VLL service via V.35, V.36 or X.21 interface
• unstructured 2 Mbps leased line services via HDSL interface:
– UGLL service via a G.703 interface
– UVLL service via V.35, V.36 or X.21 interface.

ALL service
The analog leased line (ALL) service is provided via a 2-wire Z interface for
transmission only.
An analog leased line service is used for purposes other than telephony - for example,
data transmission with modems that do or do not contain equalizers. The AnyMedia ®
Access System supports ALL according to ITU M.1020, ITU M.1025 and ITU
M.1040.

DLL service via U interface

The digital leased line service (DLL) is provided via a 2-wire U interface for digital
subscriber terminals. For example a digital leased line service is used for data
transmission with terminal adapters. The AnyMedia ® Access System supports DLLs for
international leased lines according to ETR 080, ETS 300 297 and ETS 300 012. On
the subscriber side the subscriber line is terminated by a network termination.
The DLL services offer different transmission capabilities:
• One B-channel
• One B-channel and one D-channel
(D-channel is not supported by semipermanent leased lines via V5.x interface
(SPDLL).)
• One D-channel2
(D-channel is not supported by semipermanent leased lines via V5.x interface
(SPDLL).)
• Two B-channels
• Two B-channels and one D-channel2.
(D-channel is not supported by semipermanent leased lines via V5.x interface
(SPDLL).)

Two B-channels of the U interface offer two independent 64-kbps bit streams at the
terminal equipment (TE). If the subscribers want higher data rates in one bit stream (N
× 64-kbps) at the TE, multiple B-channels of more than one U interface can be used in
connection with appropriate terminal adapters.
All the timeslots providing the service for a unique DLL subscriber are allocated in the
same E1 link.
A DLL service can be provided by using a managed NTU, that is a 2B1Q ISDN digital
subscriber line NTU which is fully managed by the AnyMedia ® Access System. The
NTU provides the subscriber a single channel operating at one of many speeds,
depending on the NTU type and configuration, from 1.2 kbps through to 128 kbps.
Management of managed NTUs is performed via the D-channel, so that channel is not
available to the subscriber. The NTU management requires the use of one of the
HDLC channels on the COMDAC. The use of a single HDLC channel to manage all
NTUs imposes the following restrictions:
• The AnyMedia ® Access System can communicate with one NTU at a time.
• If an NTU is not responding then any time spent waiting for the NTU to time-out
blocks communication with other NTUs. This time-out is at most 10 seconds.
• Managed NTUs must be polled on a regular basis to acquire alarm information.
With a single HDLC channel available and many NTUs configured it will take a
significant amount of time to poll all NTUs.

N × 64 kbps digital leased line services: GLL and VLL service

The AnyMedia ® Access System supports two kinds of [S]HDSL n × 64 kbps
(n = 1 ... 31) digital leased line services:
• Digital leased line with a G.703 interface (GLL)
• Digital leased line via a data interface (VLL), which can be either
– V.35 interface according to ITU-T V.35 or
– V.36 interface according to ITU-T V.36 or
– X.21 interface according to ITU-T X.21.
In both cases the particular interface is provided by means of an NTU.
Depending on the [S]HDSL application mode different transmission capabilities have
to be taken into consideration. For details see “Services via HDSL” (p. 5-73) and
“ISDN PRA services via SHDSL NTU” (p. 5-78). According to the application mode
the system creates automatically the HDSL timeslots for the HDSL interface.
GLLs and VLLs are provided by connecting a number of bearer channels with the
same number of timeslots of an E1 link. The E1 link has to be provisioned to be used
for permanent leased lines purposes.
All the timeslots providing the service for a unique GLL or VLL subscriber are
allocated in the same E1 link.

Unstructured 2 Mbps leased line services: UGLL and UVLL service

The AnyMedia ® Access System supports two kinds of unstructured 2 Mbps leased line
services:
• Unstructured 2 Mbps leased line with a G.703 interface (UGLL)
• Unstructured 2 Mbps leased line via a data interface (UVLL), which can be either
– V.35 interface according to ITU-T V.35 or
– V.36 interface according to ITU-T V.36 or
– X.21 interface according to ITU-T X.21.
In both cases the particular interface is provided by means of an NTU.
To support unstructured 2 Mbps leased line service the
• HDSL interface must be provisioned in the unstructured point-to-point application
mode (see “HDSL application modes” (p. 5-69)) or the
• HDSL interface must be provisioned in the unstructured point-to-point single pair
application mode (see “SHDSL application modes” (p. 5-74)).

Non-switched services / Network side

Non-switched services network side

The following non-switched services are supported on the network side:
• Leased line service
• Unstructured leased line service.

Leased line services

A leased line interface is used to support permanent leased lines. It carries
non-switched services. It consists of one single 2-Mbps link containing 31 channels of
64 kbps serving one or more subscribers. The AnyMedia ® Access System provides up
to sixteen 2-Mbps (E1) links. Each link may be used for leased line service.
LLs are provided by provisioning an E1 link to support a LL link. The LL link is
connected to either a data multiplexer (DACS) or an inter-office data network for
routing permanent leased line services.

Channel type
Each E1 channel may be used for transporting speech or data.

Unstructured leased line services

The AnyMedia ® Access System provides up to sixteen 2-Mbps (E1) links. In addition
the AnyMedia ® Access System provides 2-Mbps (E1) links (physical E1 links on
SHDSL AP). Each link may be used for unstructured leased line service and provides
2048 kbps. For the maximum number of unstructured leased lines via AP_E1 see
“System capacity of the AnyMedia ® LAG 4300 Shelf” (p. 5-8) and“System capacity of
the AnyMedia ® ETSI V5 Shelf” (p. 5-11).

Clock transparency
Dependent on the used E1 link the AnyMedia ® Access System supports unstructured
2-Mbps leased line services with and without clock transparency.
Clock transparency is provided if physical E1 links on SHDSL AP are used for the
network connection. In this case timing is not provided from the network. The user is
responsible for provisioning the circuit timing (according to ETS 300 418).
No clock transparency is provided if the physical E1 links on IO_E1 pack are used. In
this case timing is derived from the network via the AnyMedia ® Access System to the
user.

Channel type
Each E1 channel may be used for transporting speech or data.

Host/remote terminal interconnection service

Proprietary E1 interface
In a host/remote terminal application the host and remote terminal systems are
interconnected via standard E1 interfaces using a proprietary signalling protocol: the
remote terminal links. Time slots on the remote terminal links are allocated by a
proprietary bearer channel control protocol on a call by call basis. The host terminal is
the master of the bearer channel allocation algorithm. These remote terminal links can
be carried via any transport network.

ATM xDSL-based services and configurations

Purpose
This section discusses ATM xDSL services which are transported via an ATM network.
Note that the Applications and Planning Guide for IP-based Services (363-211-587)
includes the description of xDSL services which are transported via an IP network.
That also includes ATM xDSL traffic that is packetized into Ethernet frames via an
IP-AFM.

Contents

ATM xDSL services 1-17

Quality of service for ATM xDSL services 1-24
Configuration options for the ATM xDSL subsystem 1-26
®
Daisychaining of AnyMedia LAG Shelves 1-32
Local shelf daisychaining 1-33
Remote shelf daisychaining via SDH ring 1-34

ATM xDSL services

Overview
The ATM xDSL capability of the AnyMedia ® Access System may be part of any of the
applications discussed in the Applications and Planning Guide Overview
(363-211-585).
Typically, ATM xDSL services will be part of a mixed services application
(narrowband and ATM xDSL) of the AnyMedia ® Access System, or ATM xDSL may
be the only service on an AnyMedia ® Access System.
What differs for the ATM xDSL configuration option is the configuration of the
AnyMedia® Shelves. This section describes the following:
• Supported ATM xDSL services
• Providing ATM xDSL services
• ATM xDSL APs
• ATM network feeder options and AFM types
• Attributes of ATM xDSL circuit packs
• ATM cell transfer
• Use of multiple E1 feeders according to the Inverse Multiplexing for ATM (IMA)
standard
• Use of E1IMA APs as distribution packs for connecting further ATM xDSL
subsystems to an ATM xDSL host; each cascaded subsystem requires one E1IMA
AP in the host shelf
• ADSL technology (including ADSL2 and ADSL2+)
• SHDSL technology
• Configuration options
• Local and remote shelf daisychaining
Shelf configuration examples for narrowband and ATM xDSL services as well as for
ATM xDSL-only services are shown in the Applications and Planning Guide Overview
(363-211-585).

Supported ATM xDSL services

The AnyMedia ® Access System supports the following ATM xDSL services with high
bit rates to end users via twisted copper pairs, using ATM cell transfer:
• Internet access
• Remote LAN access
• Virtual private network (VPN)
• Point-to-point protocol (PPP) over ATM.

The subscriber interface is determined by the modem or CPE. Interfaces options

include:
• 10BaseT LAN (Ethernet)
• Universal serial bus (USB)
• Network interface card (NIC) installed in a PC.

Providing ATM xDSL services

The AnyMedia ® Access System provides ATM xDSL services to subscribers using
ATM cell transfer and xDSL interface technology.
Two circuit pack types are used to provide ATM xDSL services in the AnyMedia ®
Access System as follows:
• xDSL APs (includes ADSL APs, and SHDSL APs, and combo APs)
• AFM circuit pack.
Attributes of the ADSL APs (and ADSL2 APs) include the following:
• Provide 16 or 32 ADSL data lines per each AP (the older packs LPA400, LPA408
and LPA414 can still be used)
• ADSL service may be combined with POTS or ISDN from another AP
• Installation into any of the AP slots with the exception of the preferred AFM slot.
Attributes of the SHDSL APs include the following:
• Provide 16 SHDSL data lines per each AP
• Support 2-wire mode and/or 4-wire mode according to ITU G.991.2
• Installation into any of the AP slots with the exception of the preferred AFM slot.
Attributes of the combo APs include the following:
• Provide on-board circuitry for both ADSL and narrowband services.
Attributes of the E1IMA APs include the following:
• Transmit the ATM xDSL traffic from the cascaded shelves to the AFM in the host
shelf
• Provide up to 8 E1 links in one IMA group or a single E1 link in UNI mode
Attributes of the AFM circuit packs include the following:
• Multiplexing/demultiplexing of ATM cells between the ATM feeder interface and
the xDSL subscriber ports on the xDSL APs
• Connection to the ATM network
• Uses AP slot marked AP-16 and slot AP-15 in case of duplex AFM mode in the
AnyMedia ® ETSI V5 Shelf
• One AFM serves up to 15 xDSL APs in the AnyMedia ® ETSI V5 Shelf or up to 23
xDSL APs in a BB subsystem in the AnyMedia ® LAG 4300 Shelf
• Connection for daisy-chaining to other AnyMedia® Shelves available with E3/DS3
and STM-1/OC-3c feeder options.

ATM xDSL APs

The ADSL over POTS APs provide ADSL service that may be combined with POTS
service from another AP. The ADSL over POTS APs are:
• ADSL16p LPA416 - internal splitter on board
• ADSL_16p LPA420 - internal splitter on board (supports ADSL Annex A), ADSL
(ANSI T1.413), ADSL2 Annex A, READSL2 Annex L, and ADSL2+ Annex A/M).
• ADSL32p LPA432 - The ports can be directly connected to the ports of the POTS
AP LPZ110 at the MDF without cable routing. Otherwise an external splitter is
required
The ADSL over ISDN APs provide ADSL service that may be combined with ISDN
service from another AP. The ADSL over ISDN APs are:
• ADSL16i LPA417 - internal splitter on board
• ADSL32i LPA434 - an external splitter is required
• ADSL32i LPA438 (supports ADSL2 and ADSL2+, Annex B).
Combo APs provide narrowband and ADSL service simultaneously, as well as
narrowband only or ADSL only. They include the splitter function for each line and
eliminate the need to route the a/b pair from a separate narrowband AP into an ADSL
AP. The combo AP LPA832 is designed for POTS service and ADSL:
• P32A32 LPA832.
• P32A32 LPA833 (supports ADSL2 Annex A and ADSL2+ Annex A/M)
The SHDSL APs provide SHDSL service. The SHDSL APs are:
• SHDSL16 LPS702.

Other ATM xDSL related APs

E1IMA APs are used as distribution packs for connecting further ATM xDSL
subsystems to an ATM xDSL host, whereas each cascaded subsystem requires one
E1IMA AP in the host shelf.

ATM network feeder options and AFM types

Several options are available for ATM network feeder interface as follows:
• E3
• DS3
• E1
• STM-1
• OC-3c.
The choice of AFM depends on the ATM network feeder being used as follows:
• AFME3 for a E3 interface
• AFMDS3 for a DS3 interface
• AFME1 for up to 8 E1 interfaces
• AFMO for an STM-1 or OC-3c interface.
....................................................................................................................................................................................................................................
363-211-586 1-19
Issue 6, July 2007
Services ATM xDSL services

The choice of AFM may be limited by the type of ATM network feeder available.
Aside from this constraint, the AFM being used may depend on the volume of ATM
packet traffic anticipated.

ATM cell transfer

The AnyMedia ® Access System supports end-to-end ATM cell transfer between
customer premises equipment (CPE) xDSL modems and an ATM network switch.
• ATM connections are established using permanent virtual circuits (PVCs)
• Protocols above the ATM layer are carried transparently between customer premises
equipment (CPE) xDSL modems and an ATM network switch.
• Allows subscriber access to Internet service providers (ISPs) and remote LAN
applications.

ATM connections
ATM connections are permanent virtual circuits (PVCs). A connection is provisioned
with one of the following service categories defined in the ATM Forum Traffic
Management Specification, Version 4.0:
• Constant bit rate (CBR)
• Real time variable bit rate (rt-VBR)
• Non-real time variable bit rate (nrt-VBR)
• Unspecified bit rate (UBR).
CBR is best for any application that contains smooth traffic or has stringent response
time requirements. Typical applications for CBR include videoconferencing and
transport of narrowband traffic.
The rt-VBR and nrt-VBR service categories are suitable for any application that can
benefit from statistical multiplexing, transmits variable rate information, and can
tolerate a small random loss ratio. Typical applications for rt-VBR are VoDSL and
other ATM voice applications with bandwidth compression and silence suppression.
Typical applications for nrt-VBR are response-time critical transaction processing such
as banking transactions or process monitoring.
UBR applications are those that are very tolerant of delay and cell loss, such as
internet access and file transfer of large files.

IMA applications
IMA applications in the AnyMedia ® Access System require the use of a LPA941 used
as AFME1 or as E1IMA AP. The LPA941 can interface up to eight E1 feeders, using
the ATM Forum’s IMA protocol to distribute the total ATM cell traffic among the
feeders; at the far end a similar IMA terminal reconstitutes the ATM payload into a
single path for presentation to the ATM network. The same inverse multiplexing and
reconstitution occurs in the downstream direction.

Transport of the ATM feeder payload to/from a distant location is typically by means
of an optical multiplexer – but transport could also be a set of E1 lines terminated
locally by office repeaters. However, if the ATM network itself has a local appearance
with IMA ports the feeder connection will be direct to that network interface. The local
connections are typically made via a E1 cross-connect panel.
The following figure illustrates a typical network configuration featuring the AFME1
pack and a SDH multiplexer as part of the feeder. Each MUX uses ″low-speed″ ports
that are available as a means of fully utilizing the MUX’s high speed capacity. The
MUX that is local to the AFME1 might be installed in the same cabinet that houses the
AnyMedia® Shelf, it might be in an adjacent cabinet, or it might be co-located at
customer premises.
The following figure shows a typical network configuration using an AFME1 pack and
SDH Multiplexer

Cascading shelves via E1IMA APs

Further ATM xDSL subsystems may be connected and cascaded via up to eight E1
links per cascaded shelf to a host shelf by using E1IMA APs LPA941 as distribution
packs. Each cascaded ATMxDSL subsystem requires one E1IMA AP in the host shelf.
The E1 links comply with the Inverse Multiplexing for ATM (IMA) Specification
Version 1.1 of the ATM Forum Technical committee or one E1 link operates in UNI
mode. For more information refer to “Background on inverse multiplexing for ATM”
(p. 6-170). The host shelf has to groom the E1 traffic to the ATM feeder. The ATM
feeder in the host shelf may be any type.
The cascaded shelves are equipped with an AFME1 feeder. They may be connected to
the host shelf either via a single E1 link in UNI mode or via up to eight E1 links in
one IMA group.

E1IMA APs may be inserted in any AP slot with the exception of the preferred AFM
slots and the AFM protection slots. For a definition of preferred AFM slots and AFM
protection slots refer to “Slot numbering and AIDs for the AnyMedia ® LAG Shelves”
(p. 6-88).
Note that an LPA941 must be upgraded to the R1.25 software in the preferred AFM
slot before it can be used as E1IMA AP in an AP slot.
The following figure shows the system architecture of a host shelf and 2 cascaded
shelves. Cascaded shelf 1 is connected to the host shelf via several physical E1 links
operating in IMA mode, whereas cascaded shelf 2 is connected to the host shelf via 1
physical E1 link operating in UNI mode. Each shelf has its own OAM&P channel, that
means, host and cascaded shelves are independent network elements from OAM&P
point of view.
The following figure shows a host shelf and cascaded shelves (connected via E1IMA
APs)

Network interface

Host Shelf
Any
AFM

BB bus

E1IMA ADSL E1IMA

AP AP AP

up to 8
physical E1s

IMA mode UNI mode

Cascaded Shelf 1 Cascaded Shelf 2

IMA IMA
AFM AFM

BB bus BB bus

ADSL ADSL SHDSL ADSL ADSL SHDSL

AP AP AP AP AP AP

Traffic channels

OAM&P channels

ADSL technology
The ADSL lines to subscribers according to ETR328 use discrete multitone (DMT)
modulation to support ADSL-based service over twisted copper pairs. These ADSL
service lines can be either:
• Full-rate ADSL (G.992.1, Annex A)
• ADSL-lite (G.992.2 or G.lite, Annex A)
(not supported by all ADSL APs; for details refer to the Datasheet Book
363-211-251)
• ADSL2 (G.992.3 Annex A)
(supported by LPA420 and LPA833)
• ADSL2 (G.992.3 Annex B)
(supported by LPA438)
• READSL2 (ITU G.992.3 Annex L)
(supported by LPA420 and LPA833)
• ADSL2+ (G.992.5 Annex A/M)
(supported by LPA420 and LPA833)
• ADSL2+ (G.992.5 Annex B)
(supported by LPA438)
All ADSL lines have the following features:
• They are rate-adaptive and rate-provisionable
• They permit ADSL and analog POTS or ISDN (ADSL over ISDN is not available
with ADSL lite). to be carried on a distribution cable toward the end user. The
narrowband service may be provided by a narrowband pack.
• They support various options for modems located at the customer premises.
Full-rate ADSL requires splitters placed at the customer premises network interface
device, in addition to splitters contained in the AnyMedia® APs. ADSL-lite does not
require splitters at the customer premises; however, some ADSL-lite applications may
require in-line microfilters.

SHDSL technology
SHDSL lines to subscribers provide symmetric full duplex connections, ranging from
192 kbps to 2304 kbps in 64 kbps increments and 2312 kbps in 2-wire mode and
384 kbps to 4624 kbps in 4-wire mode via TC-PAM line code, which transmit ATM
cells containing the direct cell mapped application.
An SHDSL modem must be used.

Quality of service for ATM xDSL services

Overview
The AnyMedia ® Access System provides the following ATM functions in order to
maintain quality of service (QoS) of ATM connections:
• Connection admission control (CAC)
• Usage parameter control (UPC)
• Buffer management
• Congestion management
Maintaining QoS fairness among shelves in a daisy chain set requires restrictions on
VP usage.

Connection admission control

When a connection is provisioned, the AnyMedia ® Access System verifies that there is
bandwidth and buffer capacity to support the new connection while maintaining the
QoS objectives of the other existing connections. The connection is denied, if:
• the requested QoS objectives cannot be met or
• by accepting the connection, the QoS objectives of already established connections
are violated.
If the connection can be accepted, sufficient bandwidth to support requested QoS is
earmarked for the new connection.

Usage parameter control

The AnyMedia ® Access System performs usage parameter control (UPC) function on
upstream traffic to make sure that the end user ingress traffic entering the ATM
network conforms to their traffic descriptors. The policing is done on virtual circuits
(VCs)/virtual paths (VPs) that reside on an AnyMedia® shelf.
The action taken by the UPC function will include the following:
• Pass throughs - the UPC will pass through the incoming cell stream corresponding
to a VC/VP, if its traffic is in conformance to the traffic descriptor.
• Cell tagging - the nonconforming UBR, rt-VBR and nrt-VBR cells are tagged, if
the connection is provisioned for tagging.
• Discard - the cells which are nonconforming to the traffic contract will be
discarded if the connection is not provisioned for tagging.
The individual connections are policed on each shelf where they reside. The traffic
from subtending shelves (daisy chain) is carried to a northbound shelf on VPIs. This
upstream traffic conforms to their traffic descriptor, as a result of the policing on the
shelf where the VPI resides. Therefore policing is not performed on every shelf that a
VPI passes through on its way to the ATM feeder.

Buffer management
The AnyMedia ® Access System supports cell buffering to shape burst traffic as well as
to enable congestion management and fairness across ports. The buffers on the AFM
and ATM xDSL APs are configured and served so that high priority traffic is not
delayed and at the same time the buffer space is fairly managed such that traffic on a
misbehaving physical port on an AP does not affect the other traffic.

Congestion management
Congestion can occur when the offered load approaches or exceeds the design limits
for guaranteeing the QoS specified in the traffic contracts. Congestion can occur
upstream as well as downstream.
The congestion in upstream direction is due to the upstream traffic reaching the feeder
facility limits and nearing the available buffer capacity. The AnyMedia ® Access System
intelligently drops cells as described in “Congestion management schemes” (p. 6-70).

Fairness among shelves in a daisy chain set

A VP/VC is treated fairly within the shelf on which it resides. In order to be treated
fairly across a daisy chain set, all VCs in a VP will be treated as the VP service class
(UBR, rt-VBR, nrt-VBR, or CBR).

Configuration options for the ATM xDSL subsystem

Configuration options
As mentioned earlier, ATM xDSL services may be the only services on an AnyMedia ®
Access System or they will be part of a mixed services application (narrowband and
ATM xDSL services) of the AnyMedia ® Access System. This is realized by different
shelf equipage.
The following figure shows a typical network with an AnyMedia ® Access System
configured with ATM xDSL related components only. In this example the ADSL line
carries data only.

AnyMedia
Access System
ATM xDSL related Components ATM Network (Example)

ADSL AP ATM Ethernet

ADSL line AFMO Router/Switch Server
ADSL
Splitter STM-1
Modem
Data

e.g. 10BaseT
Ethernet

The following figure shows an application with the same AnyMedia ® Access System
configuration. In this case the ADSL line carries the data signal together with a POTS
signal. The POTS signal is split from the data signal in the ADSL AP and connected
externally to a co-located LE.

AnyMedia
POTS Access System
POTS ATM xDSL related Components ATM Network (Example)

ADSL AP ATM Ethernet

ADSL line AFMO Router/Switch Server
ADSL
Splitter Splitter STM-1
Modem
Data &
POTS
e.g. 10BaseT CPE
Ethernet

POTS from co-located LE

The following figure depicts an example of a mixed configuration with narrowband

and ATM xDSL related components.

ATM Network (Example)

ADM E3/ ATM Ethernet

Server
DS3 Router/Switch

MDF/FDI

AnyMedia STM-1 WaveStar

ADM 4/1 LE
Access System Ring
POTS
E1
POTS ATM xDSL related Components

ADSL AP
ADSL line AFM
ADSL
Modem Splitter Splitter
Data &
POTS E3/
CPE ADM
e.g. 10BaseT DS3 (co-located)
Ethernet
AnyMedia E1
Access System
Narrowband Components

POTS
POTS AP IO_E1

COMDAC

MDF Main distribution frame

FDI Feeder distribution interface
SN Service node

The following figure shows an ADSL network diagram, E3 network feeder, USB
subscriber interface

The following figure shows an ADSL network diagram, E3 network feeder, NIC in PC

The following figure shows an ADSL network diagram, E3 network feeder, 10BaseT
Ethernet subscriber interface, ISDN-compatible modem

The following figure shows an SHDSL network diagram, ATM network feeder,
10BaseT Ethernet subscriber interface

®
Daisychaining of AnyMedia LAG Shelves
...................................................................................................................................................................................................................................

Daisychaining of AnyMedia ® LAG Shelves

The two BB subsystems in an AnyMedia ® LAG 4300 Shelf can be daisychained to
increase the network feeder utilization across subscriber ports. Daisychaining
AnyMedia ® LAG Shelves is identical to daisychaining AnyMedia ® ETSI V5 Shelves
(see “Local shelf daisychaining” (p. 1-33)). Each BB subsystem in the daisy-chain is
managed independently.
Furthermore, AnyMedia ® LAG Shelves can be daisychained with AnyMedia ® ETSI V5
Shelves. Each BB subsystem is configured in duplex AFM mode and is managed
separately.
The following figure shows a daisychaining of an AnyMedia ® LAG 4300 Shelf with an
AnyMedia ® ETSI V5 Shelf

AFM 0
Front Access Connectors
AFM 1
AP 27
AP 28
AP 29
AP 30
AP 31
AP 32
AP 33
AP 34
AP 35
AP 36
AP 37
AP 38
AP 39
AP 40
AP 41
AP 42
AP 43
ATM E3 E3
network

Splitter/ E3
combiner

Splitters/
combiners
Fans and Cables
AFM 0
AFM 1
AP 3
AP 4
AP 5
AP 6
AP 7
AP 8
AP 9
AP 10
AP 11
AP 12
AP 13
AP 14
AP 15
AP 16
AP 17
AP 18
AP 19
AP 20
AP 21
AP 22
AP 23
AP 24
E3

Splitters/
combiners
E3
AP 1
AP 2
AP 3
AP 4
AP 5
AP 6
AP 7
AP 8
AP 9
AP 10
AP 11
AP 12
AP 13
AP 14
AFM 1
AFM 0

Local shelf daisychaining

Connection from the AFM (AFME3, AFMDS3, or AFMO can be used) to the network
ATM switch or synchronous digital hierarchy transport is via coaxial connectors on the
faceplate of the AFM. Two sets of E3/DS3 transmit and receive coaxial connectors are
provided. E3/DS3 Port 1 is always cabled to connect toward the network, while
E3/DS3 Port 2 is always cabled downstream toward any shelves that may be
daisy-chained as shown in “Local shelf daisychaining” (p. 1-33). A single E3/DS3
ATM transport network interface supports two or more daisychained shelves. The
number of daisychained shelves that can be configured depends on the number of
xDSL lines equipped per shelf, on the permissible jitter and on the traffic load on the
common 34-Mbps E3 (or 45-Mbps DS3) interfacing the network.
The AFM must be installed in the preferred AFM slot. Refer to “ATM feeder
interfaces” (p. 2-21) for more details on the ATM feeder interface.
Important! Daisychaining is not possible with the AFME1.
The following figure shows the E3/DS3 interface with local shelf daisychaining.

AnyMedia
Access System Payload & OAM of shelf 1, 2, 3
Shelf 1
E3/DS3 Port 1 ADM
SDH Ring
ATM xDSL STM-1
CPE E3/DS3 Port 2
Payload &
OAM

AnyMedia Payload & OAM of shelf 2, 3

Access System
Shelf 2

ATM xDSL E3/DS3 Port 1

CPE
Payload & E3/DS3 Port 2
OAM

AnyMedia Payload & OAM of shelf 3

Access System
Shelf 3

ATM xDSL E3/DS3 Port 1

CPE
Payload &
OAM

CPE Customer Premises Equipment

ADM Add-Drop Multiplexer

Remote shelf daisychaining via SDH ring

Remote shelf daisychaining

Besides the local shelf daisy-chaining the shelves can be daisychained over an SDH
transport network as shown in “Remote shelf daisychaining” (p. 1-34).
The following figure shows the E3/DS3 interface with remote shelf daisychaining via
SDH ring.

ATM Network (Example)

E3/DS3 ADM
Ethernet ATM
Router/Switch
Server

AnyMedia Payload & OAM of shelf 1, 2, 3

Access System
Shelf 1

ATM xDSL ADM

CPE E3/DS3 Port 1
Payload &
OAM E3/DS3 Port 2
SDH Ring
AnyMedia Payload & OAM of shelf 2, 3 STM-1
Access System
Shelf 2

ATM xDSL ADM

CPE
E3/DS3 Port 1
Payload &
OAM E3/DS3 Port 2

AnyMedia Payload & OAM of shelf 3

Access System
Shelf 3

ATM xDSL E3/DS3 Port 1

CPE ADM
Payload &
OAM

CPE Customer Premises Equipment

ADM Add-Drop Multiplexer

Purpose
This chapter describes the interfaces of Alcatel-Lucent AnyMedia ® Access System
located on all types of AnyMedia ® shelves.
The interfaces are ordered according to the following categories:
• AnyMedia ® Mainshelf interfaces related to narrowband services
– Service interfaces
– Synchronization interfaces
– OAM&P interfaces
• AnyMedia ® Mainshelf interfaces related to ATM xDSL services
– ATM feeder and xDSL interfaces
– Synchronization interfaces
– OAM&P interfaces.

Contents

Physical interfaces related to narrowband services 2-3

E1 interface (network side) 2-3
Z interface (subscriber side) 2-4
U interface (subscriber side) 2-6
HDSL interface (subscriber side) 2-9
Physical E1 interface (remote terminal link) 2-11
Synchronization interfaces for narrowband services 2-12
OAM&P interfaces for narrowband services 2-13
Craft interface terminal port 2-14
10BaseT LAN interface 2-15
Remote operations channel (ROC) 2-16
Remote operations channel (ROC) for remote terminal 2-17

Alarm interfaces 2-18

Testing interfaces 2-19
Physical interfaces related to ATM xDSL services 2-20
ATM feeder and xDSL interfaces 2-20
ATM feeder interfaces 2-21
ATM xDSL interfaces 2-22
CPE Interfaces 2-24
Synchronization interfaces for ATM xDSL services 2-25
ATM OAM&P interfaces for xDSL services 2-26
Console port 2-27
10BaseT port 2-28
BB ATM Operations Channel 2-29
Communication with the AFM over the ROC 2-30
ATM xDSL CPE interfaces 2-32

Physical interfaces related to narrowband services

E1 interface (network side)

E1 interface
The E1 interface is an HDB3-coded interface with separate wires for transmit and
receive direction. The bit rate is 2048 kbps. The electrical and physical characteristics
correspond to ITU-T Recommendations G.703 and G.823 (for jitter aspects).
The E1 interface is used for interconnecting digital network components. Via this
interface, digital signals are transmitted in frames, according to ITU-T
Recommendation G.704 and G.706.

Z interface for POTS

The physical interface functions which are provided by Z interfaces used for POTS are
also called BORSCHT functions (Most of the BORSCHT function requirements are
customer-specific). (BORSCHT is an artificial term).

B Battery Supplies a feeding current to the subscriber’s terminal

O Overvoltage Each Z port is protected against overvoltages and overcurrents according
protection to ITU-T Recommendation K.20
R Ringing Supplies a ringing signal to the subscriber’s terminal
S Signaling Detection of: On-/Off-hook signals Hook flash signals Pulse dialing
signals Supplies PPM signals (12/16-kHz pulses)
C Coding Coding and hybrid together support:
• Analog/digital and digital/analog PCM signal conversion according to
ITU-T Recommendation G.711 and G.712
• Hybrid, conversion between 2-wire signal transmission of transmit
H Hybrid
and receive signals at digital side
• Signal transmission characteristics according to ITU-T
Recommendation Q.551 and Q.552
T Test access Provides a metallic test access to subscriber’s line (drop) and to Z port
circuitry (channel).

Z interface for transmission only

The physical interface functions which are provided by Z interfaces used for
transmission-only are a subset of the Z interface functions provided for POTS.
The term transmission-only implies that mainly signal transmission is supported.
The subset of BORSCHT functions consists of the following functions:

O Overvoltage Each Z port is protected against overvoltages and overcurrents according

protection to ITU-T Recommendation K.20

C Coding Coding and hybrid together support:

• Analog/digital and digital/analog PCM signal conversion according to
ITU-T Recommendation G.711 and G.712
• Hybrid, conversion between 2-wire signal transmission of transmit
H Hybrid
and receive signals at digital side
• Signal transmission characteristics according to ITU-T
Recommendation Q.551 and Q.552
T Test access Provides a metallic test access to subscriber’s line (drop) and to Z port
circuitry (channel).

Additionally transmission characteristics according to ITU-T Recommendation M.1020,

M.1025 and M.1040 are provided.

U interface (subscriber side)

Overview
The U interface is a 2-wire digital subscriber interface for ISDN basic rate access
(BRA) service or digital leased lines (DLL) service. A U interface permits the
transmission of two 64-kbps B-channels (voice and data), one 16-kbps D-channel
(message signaling and packet data) and a maintenance channel (EOC, framing,
CRC,...) over a single metallic pair. Remote powering (on/off) may be enabled via
provisioning.

ETSI and ITU standards

The U interface specifications are based on the following ETSI and ITU standards:
• ETSI ETR 080: Defines the electrical (static and dynamic) behavior of a
U interface with line code 2B1Q and 4B3T
• ITU-T G.961: Digital Sections and Digital Line Systems, Digital Transmission
System on Metallic Local Lines for ISDN Basic Rate Access, March 1993
• ETSI ETS 300 297: Integrated Services Digital Network (ISDN); Access digital
section for ISDN basic access
• ETSI ETS 300 012: Integrated Services Digital Network (ISDN); Basic
user-network interface Layer 1 specification and test principles
• ITU K.20: Resistibility of telecommunication switching equipment to overvoltages
and overcurrents.

NT1 - universal network termination unit

The physical termination on the AnyMedia ® Access System side of the subscriber line
is the line termination function (LT) which is included in the ISDN AP; the physical
termination on the subscriber side is the universal network termination (NT1), see the
figure below. The NT1 can be used for realizing V5 ISDN BRA or DLL service.
The LT function provides remote power feeding (91 V...99 V) for one optional
regenerator and for the network termination (NT1) and a dedicated subscriber terminal
in case of a mains power loss on the subscriber side.

Managed network termination units

To realize DLL service the following products can be used as managed network
termination unit (NTU; this can be for example a FlexRate NTU), instead of an NT1:
• V.24 NTU: This NTU supports speeds 1.2 kbps, 2.4 kbps, 4.8 kbps, 9.6 kbps, 14.4
kbps, 19.2 kbps and provides a V.24 interface to the subscriber. The electrical
characteristics of interchange circuits conform to ITU-T (CCITT) Recommendation
V.28.
• V.35 NTU: This NTU supports speeds of 48 kbps, 56 kbps, 64 kbps, 128 Kbps and
provides a V.35 interface to the subscriber. The electrical characteristics of
interchange circuits 103, 104, 114 and 115 should be described in Appendix II, of
ITU-T (CCITT) Recommendations X.21bis. The rest of the circuits conform to
Recommendation V.28.
• X.21 NTU: This NTU can operate in low speed mode and high speed mode and
thus supports all speeds of a V.24 and a V.35 NTU: 1.2 kbps, 2.4 kbps, 4.8 kbps,
9.6 kbps, 14.4 kbps, 19.2 kbps, 48 kbps, 56 kbps, 64 kbps and 128 kbps. The NTU
provides a X.21 interface to the subscriber. The electrical characteristics of
interchange circuits comply with ITU-T (CCITT) Recommendations X.27 but with
a load termination resistance of 3.9 kW. The electrical characteristics at the DTE
side of the interface comply with ITU-T Recommendation X.27 (with or without
cable termination in the load).
The following figure shows configurations for ISDN BRA and digital leased line
services.

Subscriber side Network side

AnyMedia Access System

ISDN AP

ISDN BRA
configuration TE NT1 LT

S interface U interface

DLL configuration TE NT1 LT

S interface U interface

managed LT
DLL configuration TE
NTU

V.24 interface U interface

V.35 interface
X.21 interface

ISDN BRA
configuration TE NT1 REG LT
with regenerator

optional
S interface U interface

HDSL interface (subscriber side)

Overview
The AnyMedia ® Access System supports
• HDSL systems with two copper pairs according to ETSI TS 101 135
The transmission rate of the HDSL system is 1168 kbps on each copper pair.
• SHDSL systems with one copper pair according to ITU G.991.2 Single-pair
high-speed digital subscriber line (SHDSL) transceivers.
The maximum transmission rate of the SHDSL system is 2056 kbps on the copper
pair.
Bearer channels and maintenance channel (EOC, framing, CRC-6) are transmitted via
the HDSL interface.
The physical termination on the AnyMedia ® Access System side of the subscriber line
is the line termination unit (LTU) function which is included in the [S]HDSL AP.
The physical termination on the subscriber side is the Network Termination Unit
(NTU).
NTUs with the following interfaces are supported by provisioning the AnyMedia ®
Access System:
• G.703 interface
• Data interfaces
– V.35 interface according to ITU-T V.35
– V.36 interface according to ITU-T V.36
– X.21 interface according to ITU-T X.21.
The following figure shows configurations for ISDN PRA and leased line services.

Subscriber side Network side

AnyMedia Access System

T reference point
[S]HDSL AP

V5 / V3 ISDN PRA
configuration PBX NTU LTU

G.703 interface HDSL interface

Leased line /
unstructured leased TE NTU LTU
line configuration

G.703 interface and/or HDSL interface

V.35 interface or
V.36 interface or
X.21 interface

Physical E1 interface (remote terminal link)

Overview
The following physical interfaces for remote terminal links are provided
• in the host terminal for remote terminal links:
– IO_E1 “Server” Port on FAC500B
– AP_E1 “Server” Port on LPS510
• in remote terminal for remote terminal links:
– IO_E1 “Feeder” Port on FAC500B

Synchronization interfaces for narrowband services

Synchronization sources
For network synchronization of the narrowband subsystem the COMDAC recovers
timing from:
• a composite clock supply interface (64 kHz synchronization signal, providing
8 kHz phase information) connected to the external clock pins of the office clock
connector in the connector field.
• a digital clock supply interface (64 kHz synchronization signal, providing 8 kHz
and 400 Hz phase information) connected to the external clock pins of the office
clock connector in the connector field.
• a 2048 kHz digital office timing supply (DOTS) E1 signal connected to the
external clock pins of the office clock connector in the connector field.
• an external synchronization equipment delivering a synchronization signal to the
station clock interface (SCI) connected to the station clock pins in the office clock
connector.
• E1 links (clock derived from up to two E1 link signals).

OAM&P interfaces for narrowband services

Overview
This chapter describes the maintenance interfaces for operations, administration,
maintenance, and provisioning (OAM&P) of the AnyMedia ® Mainshelves. The
AnyMedia ® Mainshelves provide the following OAM&P interfaces:
• Craft interface terminal (CIT) port
• 10BaseT LAN interface
• Remote operations channel (ROC)
• Remote operations channel (ROC) for remote terminal in remote terminal
applications.
A PC-based graphical system interface, the AnyMedia ® Access System graphical
system interface software (GSI) operates over all OAM&P interfaces. For a description
of the GSI see Applications and Planning Guide Overview (363-211-585).

Craft interface terminal port

The craft interface terminal (CIT) port is an EIA-232C connector. It is located on the
faceplate of the CIU. A GSI can be connected to the CIT port locally or remotely via
various kinds of DCN networks, see Applications and Planning Guide Overview
(363-211-585).

10BaseT LAN interface

A local LAN interface is available via the 9-pin female D-sub connector J107 in the
AnyMedia ® LAG 4300 Shelf connector field or via the connector LAN in the shelf
connection panel of the AnyMedia ® ETSI V5 Shelf/800 Shelf respectively. The LAN
interface provides access to an Ethernet LAN through 10BaseT connection according to
IEEE 802.3. All communications through this interface occur over transaction control
protocol/internet protocol (TCP/IP). This interface is expected to be used if the system
is installed in locations where an Ethernet LAN already exists.

Remote operations channel (ROC)

Remote operations channel (ROC) for remote terminal

ROC for remote terminal

A ROC for remote terminal is used in remote terminal applications for transporting
management information between host and remote terminal and the GSI/EMS. The
information is transported via an embedded 64-kbps channel that is part of the remote
terminal link (E1 link) between host and remote terminal. The system supports the
following types of ROC for remote terminal:
• remote semipermanent V5.2 ROC
• ROC via nailed-up remote link timeslot and leased line link transport in host
terminal
• ROC via nailed-up remote link timeslot and IP-routed transport in host terminal.

Alarm interfaces
...................................................................................................................................................................................................................................
The following alarm interfaces exist for the AnyMedia ® Access System:

Local alarm and status indicators

The packs have light emitting diodes (LEDs) on the faceplate to indicate status and
alarm conditions. Any alarms indicated by the LEDs are reported also via the OAM&P
interfaces.

Office alarm outputs

Three software-controlled relays on the CIU are used as alarm outputs to indicate
active alarms. The relays may be connected to audible or visible alarm indication
devices. The assignment to the alarm LEDs is provisionable by TL1 commands.

Miscellaneous alarm closure inputs

The CIU supports 8 ground closure alarm inputs to indicate environmental fault
conditions. Alarms detected at the miscellaneous alarm inputs are reported also via the
OAM&P interfaces. An additional LED MISC on the CIU faceplate indicates an active
alarm input.

Alarm support via external alarm collector box

The system supports a TL1 command (REPT-CLOSURES) to raise and retire
environmental alarms. For this purpose a kind of virtual miscellaneous contact unit,
with up to to 64 virtual miscellaneous alarm input contact closures, is provided.
The TL1 command allows any external system (for example alarm collector box) to
trigger the usual environmental alarm reports (REPT-ALM-ENV). The command can
be issued on any operations interface of the system, e.g. TELNET, CIT, VC, and
especially also on the RTU interface of each shelf type.
For details about alarms see “Alarm signaling paths” (p. 3-101) and the Applications
and Planning Guide Overview (363-211-585).

Alarm cut-off function

The alarm cut-off function (ACO) provides the possibility to immediately cut off the
audible/visible alarms active on the alarm interface outputs. The ACO function is
activated by pressing the ACO button on the CIU faceplate or with a TL1 command.

Inhibiting/resuming alarm
The system provides the capability to inhibit and resume autonomous alarm reporting
to any narrowband OAM&P interfaces. It is possible to disable all alarms of one (or
more) specific entity or of an entity group. The ability to disable alarms can be useful
for example during troubleshooting to avoid a great amount of alarm reports.

Testing interfaces
...................................................................................................................................................................................................................................

Interfaces for manual testing

Interfaces for manual testing
• Faceplate jack DROP on the CIU
This interface is used for metallic test access to the subscriber line and to partly the
equipment on the subscriber side.
• Faceplate jack CHAN/MON on the CIU
This interface is used for metallic test access to the port hardware and for listening
to an existing call.

Interfaces for integrated testing

Interfaces for integrated testing
• TAP connector for metallic test access on the shelf connection panel of the
AnyMedia ® ETSI V5 Shelf/800 Shelf
• TAP connector J106 for metallic test access in the connector field of the
AnyMedia ® LAG 4300 Shelf
• Connector on the faceplate of the test application pack.

Interface for external test head testing

Interface for external test head testing
• Serial EIA-232C RTU port for control access.
The RTU port does not perform a user login and password verification and is therefore
limited by the system to the RTU test session commands (see Chapter 5, User Service
Manual). On the other management interfaces the RTU test session commands are also
available but only with authorization check.

Physical interfaces related to ATM xDSL services

ATM feeder and xDSL interfaces

Overview
This chapter discusses the ATM and OAM&P interfaces for the AnyMedia ® Access
System ATM xDSL services.
• ATM network feeder interfaces
• ATM OAM&P interfaces
• ATM xDSL CPE interfaces.
Each OAM&P interface supports simple network management protocol (SNMP) and
file transfer protocol (FTP) operations.
The following term is used throughout this document:
• ATM OAM&P interfaces identifies all three alternatives for connecting to OAM&P
ATM operations interfaces, including the following:
– Console port on the AFM pack for connecting to the GSI
– 10BaseT port for LAN connection
– BB ATM Operations Channel.

ATM feeder interfaces

Overview
The AnyMedia ® Access System provides subscriber access to ATM xDSL services
using asynchronous transfer mode (ATM) technologies. At the xDSL APs and the
AFM, the AnyMedia ® Mainshelves provide multiplexing/demultiplexing of ATM cell
streams between the AnyMedia ® Access System’s feeder interface and the subscriber
ports. This provides ATM cell transfer end-to-end from the CPE to the remote data
network.
ATM provides multiplexed data transfer via fixed length (53 octet) cells. The ATM
cells provide the data payload carried on the feeder interface to the ATM backbone
network, where the feeder may interface an ATM switch directly or through an SDH
multiplexer. The ATM cell format is provided in accordance with the ATM Forum UNI
3.1 and UNI4.0 specifications.
Depending on the AFM type used the AnyMedia ® Access System provides the
following feeder interface options:
• E3
The E3 ATM feeder interface can provide up to 80,000 ATM cells per second. It is
a single physical interface.
• DS3
The DS3 ATM feeder interface can provide up to 104,269 ATM cells per second. It
is a single physical interface.
• E1 (up to eight E1s)
Up to eight physical E1 interfaces can be provisioned to work together to form one
inverse multiplexing for ATM (IMA group. The interface provides up to 4508 × n
ATM cells per second, where n is the number of E1 interfaces that have been
provisioned. The maximum cell rate depends on the IMA frame rate (see
“Maximum traffic for an E1 feeder/IMA group” (p. 6-12)); 4508 results when M =
256, the maximum.
• STM-1/OC-3c
The STM-1/OC-3c ATM feeder interface provides up to 353,207 ATM cells per
second. It is a single physical interface.
The different feeder types are described in more detail in “ATM feeders” (p. 6-159).

ATM xDSL interfaces

Full-rate ADSL interface (subscriber side)

The full-rate ADSL interface is a twisted 2-wire subscriber interface according to ANSI
T1.413 and ITU-T G.992.1 and according to ETSI TS 101 388 for ADSL over ISDN.
It provides voice and data transmission using discrete multitone (DMT) technology.
The connection can carry ADSL traffic as well as the POTS or ISDN signal.
The full-rate ADSL interface is provided by the following packs:
• ADSL16p LPA416
• ADSL16i LPA417
• ADSL32p LPA432
• ADSL32i LPA434
• P32A32 LPA832
• P32A32 LPA833
• ADSL_16p LPA420
• ADSL32i LPA438

ADSL-lite interface (subscriber side)

The ADSL-lite interface is a twisted 2-wire subscriber interface according to
ITU-T G.992.2. It provides voice and data transmission using discrete multitone
(DMT) technology without splitter. The connection can carry ADSL traffic as well as
the POTS signal.
The ADSL-lite interface is provided by the following packs:
• ADSL16p LPA416
• ADSL32p LPA432
• P32A32 LPA832.

Full-rate ADSL2 / ADSL2+ interface (subscriber side)

The full-rate ADSL2 interface according to ITU-T G.992.3 and ADSL2+ according to
ITU-T G.992.5 interface is a twisted 2-wire subscriber interface. It provides voice and
data transmission using discrete multitone (DMT) technology. The connection can carry
ADSL traffic as well as the POTS or ISDN signal.
The full-rate ADSL2 / ADSL2+ interface is provided by the following packs:
• ADSL_16p LPA420
• P32A32 LPA833
• ADSL2_32i LPA438.

SHDSL interface (subscriber side)

SHDSL provides symmetric transmission bit rates from 192 kbps to 2312 kbps over a
single twisted 2-wire subscriber interface (2-wire mode) or 384 kbps to 4608 kbps
over two adjacent bonded twisted pairs (4-wire mode).
The SHDSL interface is provided by the SHDSL16 LPS702 pack. For the ATM cell
transport TC-PAM SHDSL line-coding is used.

E1 interface on E1IMA AP
The E1 interface on the E1IMA APs LPA941 is used for connecting further ATM
xDSL subsystems to an ATM xDSL host. Each cascaded ATM xDSL subsystem
requires one E1IMA AP in the host shelf. This E1 interface is identical to that
described in “ATM feeder interfaces” (p. 2-21).

CPE Interfaces
...................................................................................................................................................................................................................................
The interface provided by the CPE to the customer depends on the type of modem
used. The AnyMedia ® Access System supports a various range of modems.

Synchronization interfaces for ATM xDSL services

Synchronization interfaces BB subsystem

The AFM synchronizes its
• E3/DS3 or
• E1 or
• STM-1 or OC-3c
feeder interfaces to the ATM network. This is done by the AFME3, AFMDS3, AFMO,
and AFME1.
The AFME3 recovers timing from the E3 feeder, AFMDS3 recovers timing from the
DS3 feeder, AFMO recovers timing from the optical feeder, and the AFME1 from any
of the E1 interfaces, provisioned as primary or secondary timing reference.
The AFMs support an 8 kHz timing reference signal towards the broadband bus to be
used by the xDSL APs for providing a network timing reference (NTR) signal to
synchronize narrowband services in the CPE.
Timing for each xDSL interface is derived from an internal crystal oscillator in the AP.
It is not synchronized to the clock distributed by the AFM. This timing reference is
used regardless of the status of the feeder signal from the network.

ATM OAM&P interfaces for xDSL services

Overview
The AnyMedia ® Access System provides the following operations, administration,
maintenance, and provisioning (OAM&P) interfaces for managing xDSL services:
• Console port on the faceplate of the AFM
• 10BaseT port on the faceplate of the AFM for LAN connection. The 10BaseT port
is also used when managing the AFM through the TDM COMDAC’s Remote
Operations Channel (ROC). In this case an external cross-over 10BaseT cable
connects the 10BaseT port of the AFM with the LAN connector in the shelf
connection panel (see “Communication with the AFM over the ROC” (p. 2-31)).
In an AnyMedia ® LAG 4300 Shelf each subsystem is connected to the GSI over
the LAN port via an external hub. The hubbing device is connected to the
management station over a LAN connection.
• BB ATM Operations Channel (an ATM PVC configured to transmit OAM&P
information)
Each OAM&P interface supports simple network management protocol (SNMP) and
file transfer protocol (FTP) operations.
Important! When multiple shelves are daisychained, each AnyMedia ® Mainshelf
provides these interfaces and must be independently addressed for OAM&P.
Important! The 10Base-T port and the BB ATM Operations Channel can be used
for OAM&P. However either the 10Base-T or the BB ATM Operations Channel can
be used for remote access but not both at the same time. For example, if the BB
ATM Operations Channel is used for remote access, a management system
connected via 10Base-T port must be either connected directly via cross-over cable,
via Ethernet hub or switch, but not via an intermediate router.
Important! It is possible to transport also narrowband OAM&P information via the
ATM network. The AFM extracts this information from the ATM PVC and routes it
to the 10BaseT port. To transmit the narrowband OAM&P information to the
COMDAC both 10BaseT ports (AFM 10BASE-T port and LAN connector in the
shelf connection panel) have to be connected.

Console port
...................................................................................................................................................................................................................................

Console port
The Console port on the faceplate of the ATM Feeder Multiplexer is an EIA-232E/574
local access terminal interface port for the AnyMedia ® graphical system interface
software (GSI). A DB-9 faceplate connector is provided on the AFM. In cases where a
shelf uses two AFMs in duplex mode, the connector must be connected to the active
AFM. A special Y cable connection can also be used.
The Console port is not applicable for an LPA941 that is used as an E1IMA AP.

10BaseT port
...................................................................................................................................................................................................................................

10BaseT port
The 10BaseT port on the faceplate of the ATM Feeder Multiplexer is a 10-Mbps
interface that connects the GSI installed on either a PC equipped with an Ethernet
LAN card or a computer equipped with a NIC (LAN). An RJ-45 faceplate connector is
provided on the AFM for local access. In cases where a shelf uses two AFMs in
duplex mode, the connector must be connected to the active AFM. A special Y cable
connection or a hub can also be used. The maximum cable length is 100 m when
category 4 or 5 distribution pair unshielded cabling is used. The interface is IEEE
802.3-compliant.
The 10BaseT port is not applicable for an LPA941 that is used as an E1IMA AP.

External system LAN

The 10BaseT port can be connected to a LAN for remote access to operations. The
maximum cable length and interface specifications are the same as for connecting the
10BaseT port to a PC or computer. In cases where a shelf utilizes duplex AFMs, the
10Base T ports of both AFMs are joined using a hub or a special Y cable connection.

BB ATM Operations Channel

The AnyMedia ® Access System supports an ATM connection on the ATM network
backbone for remote operations. The BB ATM Operations Channel can carry
narrowband and ATM xDSL management information (see “Using the BB ATM
Operations Channel to transport NB OAM&P” (p. 5-38) and “Communication with the
AFM over the ROC” (p. 2-31) for the physical connection).
The BB ATM Operations Channel can be provisioned using either a VC within a Shelf
VP, or using its own (that means, non-shelf) VP.
If an AnyMedia ® Access System is upgraded from a previous software version (in this
case the BB ATM Operations Channel will always be UBR whether that channel uses a
VC within a Shelf VP or its own VP) to the current version, and if the BB ATM
Operations Channel was previously provisioned using a VC within a Shelf VPI, then
that VP (and VC) remains as UBR after the upgrade. However, if the BB ATM
Operations Channel was previously provisioned on its own VP, then the service class
of that VP is automatically changed from UBR to rt-VBR when the upgrade takes
effect. In this case, the ATM network must be reprovisioned with the new service class.
If an AnyMedia ® Access System is a new installation using the current software, then
the BB ATM Operations Channel can be provisioned either as its own new VP using
rt-VBR, or as a new VC within the rt-VBR Shelf VP.

Communication with the AFM over the ROC

In a mixed narrowband and ATM xDSL system configuration, it is possible to manage
the AFM via the ROC and the COMDAC IP routing capability, although it is
recommended to manage the NB subsystem via the BB ATM operations channel as
described in “Using the BB ATM Operations Channel to transport NB OAM&P”
(p. 5-38).
There are a number of requirements for the communication with the AFM using the
ROC and COMDAC routing:
• An IP assignment for the Ethernet port of the AFM circuit pack, which must be on
the same subnet as the IP assignment for the Ethernet port of the COMDAC. The
Ethernet port IP address of the AFM and the COMDAC must be different.
• The default router of the AFM is set to the Ethernet port IP address of the
COMDAC. The COMDAC’s default route (ENT-ROUTE) is then set to the remote
end of the ROC interface (the IP address of the ROC router).
• A ROC configured to communicate remotely with the COMDAC using TCP/IP.
The ROC IP and the Ethernet LAN IP must be on different subnets.
• A LAN crossover cable (ED7C829-32, Group 6 Crossover 10BaseT cable) to
connect from the AFM circuit pack 10BaseT port to the LAN connector on the
connector field of the AnyMedia ® Shelf.
The following figure shows the physical LAN connection from the AFM to the shelf
connection panel.

ROC within E1 signal contains OAM&P

information for COMDAC and for AFM

LAN
OAM&P information for
ATM xDSL passes through
backplane to CIU and then
over the LAN cable to AFM
COMDAC

10BaseT port

Rx and Tx port
for feeder cable

ATM xDSL CPE interfaces

Definition
The interface provided by the customer premises equipment (CPE) to the customer
depends on the type of modem used.
For a description of the interfaces between the AnyMedia ® Shelves and the CPE, see
“ADSL technology” (p. 1-23).

Purpose
This chapter gives an overview of the Operations, Administration, Maintenance, and
Provisioning (OAM&P) actions and tasks for narrowband services in the
Alcatel-Lucent AnyMedia ® Access System.
The OAM&P management actions are as follows:
• Narrowband configuration management
– Database management
– Software management
– System turn-up
– Provisioning and service activation
– V5 re-provisioning
– Clock synchronization management
– Protection switching
• Inventory management
• Narrowband fault management
– Maintenance
– Alarms and events
– Testing
• Narrowband performance management
• Narrowband security management.
To support the narrowband OAM&P functionality the following management interfaces
are provided by the AnyMedia ® Access System:
• Craft interface terminal (CIT) port
• 10BaseT LAN interface
• Remote operations channel (ROC)
• Remote operations channel (ROC) for remote terminal in remote terminal
applications.

For further information about the management interfaces see “OAM&P interfaces for
narrowband services” (p. 2-13).

Contents

Configuration management 3-5

Configuration management 3-7
Database management 3-8
Software management 3-9
System turn-up 3-10
Provisioning and service activation 3-11
POTS subscriber 3-15
ISDN BRA subscriber 3-16
V5 ISDN PRA subscriber 3-17
V3 ISDN PRA subscriber 3-19
V5 frame relaying (ISDN) 3-21
POTS/ISDN operation modes 3-22
Analog leased lines 3-23
Digital leased lines 3-24
N × 64 kbps leased lines 3-26
Unstructured leased line subscriber via IO_E1 3-28
Unstructured leased line subscriber via AP_E1 3-30
Provisioning model 3-31
Service state model 3-34
Remote operations channel (ROC) 3-36
Remote operations channel (ROC) for remote terminal 3-37
Mismatch of provisioning between host and remote terminal 3-40
Managed NTU provisioning 3-42
V5 re-provisioning 3-44
Clock synchronization management in the AnyMedia Access System 3-49
Protection switching 3-54
COMDAC protection 3-56
Synchronization source protection using TDM COMDAC 3-57
V5.2 Communication channel protection 3-58
IO_HDLC protection 3-59
IO_E1 protection 3-61

AP port protection 3-63

Ringing protection in the AnyMedia ® LAG 4300 Shelf 3-66
Ringing in the AnyMedia ® LAG 1900 Shelf 3-71
Ringing protection in the AnyMedia ® ETSI V5 Shelf 3-73
Protection switch characteristics 3-75
Inventory management 3-77
Retrievable inventory items 3-78
System identification name [target identifier (TID)] 3-80
Internet protocol (IP) address 3-81
Reportable database changes 3-82
NTU inventory data 3-83
Fault management 3-84
Maintenance 3-86
Alarms and events 3-90
Common alarms 3-92
Equipment alarms 3-93
Facility alarms (2-Mbps transmission) 3-99
Host and remote terminal alarms 3-100
Alarm signaling paths 3-101
Miscellaneous alarm inputs 3-102
Alarm output relays 3-106
Local alarm and status indicators 3-107
Alarm reporting and retrieval via TL1 3-108
Built-in self tests 3-109
Testing possibilities 3-113
On-demand tests using integrated capabilities 3-114
Detection test of a test termination 3-125
Draw and break dial tone test 3-126
DTMF, pulse character or register recall (hook flash) test 3-127
Sending of test tone for POTS CPE 3-128
Ringing test for POTS CPE 3-129
CRC tests for ISDN application packs 3-130
Sending a single pulse 3-131
NT1 detection test 3-132
Noise measurement on a subscriber line 3-133

Loop current measurement 3-134

Tone measurement 3-135
Howler tone on demand on POTS drops in reduced battery state 3-136
Quick line test 3-137
Talk to subscriber test session 3-140
Loopbacks 3-141
Loopbacks at the E1 link side 3-142
Loopbacks at the U interface (subscriber side) 3-143
Loopbacks at the HDSL interface 3-146
Loopbacks at the SHDSL port 3-151
BER testing with external loopback devices 3-154
Subscriber line test via external test head 3-155
Performance management 3-157
Performance management definitions 3-158
Performance management data 3-160
Performance management operations 3-162
V5.2 protocol error logging 3-163
Traffic statistics and COMDAC load measurement 3-166
Measurement data collection 3-167
Measurement types 3-168
Post-processing and presentation 3-170
Security management 3-171
Security management capabilities 3-172

Configuration management

Purpose
Configuration management is the system activity for operations that control and
provision the system, including the following:
• Database management - used to manage the nonvolatile data storage (NVDS) of the
AnyMedia ® Access System
• Software management - used to manage the nonvolatile program storage (NVPS) of
the system
• System turn-up - represents a typical initial system turn-up scenario
• Provisioning and service activation
Process of preparing the system for service by defining its function and setting any
required options and preparing the system for service by configuring the
cross-connections between its bandwidth management entities, moving entities in
service, and setting any required options.
• Inventory management - system activity of collecting, updating, and reporting data
on system equipment and system status
• Clock synchronization management
• Protection switching - automatic recovery mechanisms when a fault is detected in
the system.

Contents

Configuration management 3-7

Database management 3-8
Software management 3-9
System turn-up 3-10
Provisioning and service activation 3-11
POTS subscriber 3-15
ISDN BRA subscriber 3-16
V5 ISDN PRA subscriber 3-17
V3 ISDN PRA subscriber 3-19
V5 frame relaying (ISDN) 3-21
POTS/ISDN operation modes 3-22
Analog leased lines 3-23
Digital leased lines 3-24

N × 64 kbps leased lines 3-26

Unstructured leased line subscriber via IO_E1 3-28
Unstructured leased line subscriber via AP_E1 3-30
Provisioning model 3-31
Service state model 3-34
Remote operations channel (ROC) 3-36
Remote operations channel (ROC) for remote terminal 3-37
Mismatch of provisioning between host and remote terminal 3-40
Managed NTU provisioning 3-42
V5 re-provisioning 3-44
Clock synchronization management in the AnyMedia Access System 3-49
Protection switching 3-54
COMDAC protection 3-56
Synchronization source protection using TDM COMDAC 3-57
V5.2 Communication channel protection 3-58
IO_HDLC protection 3-59
IO_E1 protection 3-61
AP port protection 3-63
Ringing protection in the AnyMedia ® LAG 4300 Shelf 3-66
Ringing in the AnyMedia ® LAG 1900 Shelf 3-71
Ringing protection in the AnyMedia ® ETSI V5 Shelf 3-73
Protection switch characteristics 3-75

Configuration management
...................................................................................................................................................................................................................................

Configuration management capabilities

The following sections describe the configuration management capabilities.

Database management
...................................................................................................................................................................................................................................

NVDS
Database management is used to manage the nonvolatile data storage (NVDS) of the
AnyMedia ® Access System. NVDS contains provisioning data. Physically the NVDS is
implemented via flash memory devices on the COMDAC.
The system periodically audits the NVDS. If the system is in simplex mode, that
means only one COMDAC is plugged in, it checks the self-consistency of the NVDS.
If the system is in duplex mode (COMDAC is pack-protected), it checks self- and
mutual-consistency of both copies of the NVDS.

NVDS backup
The system supports backing up of the NVDS data. Backups of the NVDS data are
done through the NVDS database upload from the NVDS to a graphical system
interface (GSI). NVDS backup will not occur automatically; it must be initiated by the
operator via TL1 command.

NVDS restoration
The system also supports restoration of the NVDS data. NVDS restoration is used
• In the event of a backout of a new software release
• In case of catastrophic multiple faults of the NVDS.
The restoration of previous NVDS data is done through the NVDS database download
from a GSI/EMS.

NVDS evolution
During software upgrades from one release to another, the system supports automatic
(built-in) transformation of the database. In the AnyMedia ® Access System this is
called database evolution. The site-specific configuration is completely retained.
This advanced feature avoids the complex procedure of retrieving the old database,
transforming it off-line and reloading it to the upgraded system.

Provisioning inhibition
The AnyMedia ® Access System supports a provisionable operation mode where TL1
commands which would alter the NVDS can be inhibited to be executed.
The TL1 commands to be inhibited are grouped into the operations category ″Memory
Administration″, which includes a factory defined TL1 command set.
Note: The inhibition can only be activated/released on privilege level. The inhibition
state is stored in the NVDS database.

Software management
...................................................................................................................................................................................................................................

NVPS
Software management is used to manage the nonvolatile program storage (NVPS) of
the AnyMedia ® Access System.
The AnyMedia ® Access System has reprogrammable program memories. One program
memory resides in each COMDAC. If the system is in simplex mode, the system has
one copy of the program memory. If the system is in duplex mode, it has two copies
of the program memory.
The AnyMedia ® Access System routinely audits the integrity of the NVPS. If the
system is in simplex mode, the system will check the checksum of the NVPS. If the
system is in duplex mode, the system will check the program version of both copies of
the NVPS.

Program storage
The NVPS in the COMDAC is reprogrammable. The AnyMedia ® Access System is
capable of modifying these reprogrammable program memories through a software
download operation.
The software download impacts the provided service after downloading by a system
restart.

New software release

A new software release can be deployed to the AnyMedia ® Access System by three
methods:
• COMDAC replacement, service affecting (SA)
• Simplex software download, service affecting (SA)
• Duplex software download, non-service affecting (NSA) during software download
but service affecting during the activation of the new load by performing a side
switch.
The activation of the new load is non-service affecting in the sense that stable calls
are retained. There is only a certain time during which new calls cannot be
accepted.
Important! The downtime for a software download to an AnyMedia ® Access
System in simplex mode can be shortened significantly by temporarily using a
second COMDAC and putting the system into duplex mode while downloading.

System turn-up
...................................................................................................................................................................................................................................

Introduction
This section describes the initial system turn-up. The system can be reconfigured at
any time after turn-up.
Important! In a mixed narrowband and ATM xDSL configuration it is assumed
that the NB subsystem is installed and turned up before turning up the BB
subsystem of the system.

System turn-up procedure at mainshelf location

The following is the recommended initial system turn-up procedure at mainshelf
location. This procedure represents a typical initial system turn-up scenario.
1. COMDAC installation
2. CIU installation, GSI connection and logging on
3. Verifying COMDAC software and clearing nonvolatile data storage (NVDS)
provisioning memory or downloading COMDAC software with boot download
procedure (if necessary)
4. Setting customer configuration
5. Setting ISDN mode configuration
6. IO_HDLC non-protection installation (for switched ISDN services only); IO_HDLC
packs are not used in the AnyMedia ® LAG 4300 Shelf.
7. Adding IO_HDLC pack protection (for switched ISDN services only); IO_HDLC
packs are not used in the AnyMedia ® LAG 4300 Shelf.
8. Switching configuration
9. Setting source identifier of the system SID (is used in TL1 commands as target
identifier TID) and the mainshelf type and a miscellaneous mainshelf information
10. Setting date and time
11. Setting up filters for autonomous messages to GSI/EMS (default setting for GSI via
EIA-232C: send messages)
12. Setting the IP address if 10BaseT LAN or ROC are used
13. Setting up IP routing if used
14. IO_E1 non-protection installation
15. Adding IO_E1 pack protection
16. Setting synchronization parameters, if not using the default parameters of IO_E1
17. Application packs (AP) installation
18. Establishing the ROC interface (if ROC is used)
19. Verifying proper system turn-up
20. Logging off the AnyMedia ® Mainshelf.

Provisioning and service activation

Definition
Service activation is the process of preparing the AnyMedia ® Access System for
service by configuring the cross-connections between a service node and an access
network element (ANE). The ANE is responsible for the physical connection (or
termination) of subscriber lines whereas the local exchange (LE) is responsible for
switching and call processing (including the knowledge of supplementary services,
charging etc.).

Provisioning summary
Prior to service activation on the AnyMedia ® Access System several data items need to
be provisioned. It is necessary to configure service types and cross-connects between
logical and physical entities.
The following figures show functional diagrams of the cross-connections between
subscriber side and network side. The AnyMedia ® Access System supports up to 16
V5.1 or up to 16 V5.2 or up to 16 V3 or up to 16 permanent leased line (structured or
unstructured) interfaces, in any combination not exceeding the maximum of 16 E1
links in the system.

Functional diagram of cross-connects within the AnyMedia ® LAG 4300 Shelf

Subscriber side Network side

64 kbps
maximum of 480 subscriber lines for V5.1
2 Mbps
POTS V5.1 IO_E1
24 lines Application 2 Mbps
Pack 30 Interface

64-kbps Cross
Connection
e.g. LPP100 (one logical
V5 link) 4 x E1 link
maximum of 12 ISDN BRA subscribers per LAG 4300 Shelf

Connection
64 kbps
V5.1
ISDN 2 Mbps
Interface

E1 Logical
30

Cross
12 lines Application
Pack (one logical
e.g. LPU112 V5 link)

POTS
64 kbps 2 Mbps 2 Mbps IO_E1
32 lines Application
V5.2
maximum of 1728 subscriber lines for V5.2

Pack
e.g. LPZ100
Interface max.
Subscriber Line
1730
V5.2 Interface -

(up to 16 logical 16 4 x E1 link

Association

V5 links)

64 kbps 2 Mbps
V5.2
ISDN 2 Mbps IO_E1
Application 1730 Interface max.
12 lines (up to 16 logical 16
Pack
e.g. LPU112 V5 links)
4 x E1 link
POTS
24 lines Application 64 kbps
Pack LL
maximum of 496 subscriber lines for LL

e.g. LPP100 2 Mbps

Interface
64-kbps Cross

31
Connection

(one logical
ISDN LL link)
12 lines Application
Pack
e.g. LPU112
64 kbps
LL
[S]HDSL 2 Mbps 2 Mbps
31 Interface IO_E1
4 lines Application
Pack (one logical
e.g. LPS501 LL link)
4 x E1 link
Cross Con-
nection 1:1

V3
subscriber lines
maximum of 16

2-Mbps

[S]HDSL 2 Mbps 2 Mbps

Application
Interface
for V3

4 lines
Pack
e.g. LPS503 (one logical
V3 link)
subscriber lines

Cross Con-
maximum of 16

nection 1:1

[S]HDSL ULL
2-Mbps
for ULL

2 Mbps 2 Mbps
4 lines Application Interface
Pack
e.g. LPS504 (one logical
ULL link)
maximum of 272
subscriber lines

SHDSL
for ULL

8 lines Application
Pack
4 unstructured AP_E1 lines with clock transparency
e.g. LPS510

Functional diagram of cross-connects within the AnyMedia ® ETSI V5 Shelf

Subscriber side Network side

64 kbps
maximum of 480 subscriber lines for V5.1
2 Mbps
POTS V5.1 IO_E1
24 lines Application 2 Mbps
Pack 30 Interface

64-kbps Cross
Connection
e.g. LPP100 (one logical
V5 link) 4 x E1 link

Connection
64 kbps
V5.1
ISDN 2 Mbps
Interface

E1 Logical
30

Cross
12 lines Application
Pack (one logical
e.g. LPU112 V5 link)

POTS 2 Mbps
Application 64 kbps 2 Mbps IO_E1
32 lines
Pack V5.2
maximum of 768 subscriber lines for V5.2

e.g. LPZ100
Interface max.
Subscriber Line 768
V5.2 Interface -
(up to 16 logical 16 4 x E1 link
Association

ISDN V5 links)
16 lines Application
Pack
e.g. LPU430
64 kbps 2 Mbps
V5.2
[S]HDSL 2 Mbps IO_E1
Application 768 Interface max.
4 lines (up to 16 logical 16
Pack
e.g. LPS501 V5 links)
4 x E1 link
POTS
24 lines Application 64 kbps
Pack LL
maximum of 496 subscriber lines for LL

e.g. LPP100 2 Mbps

Interface
64-kbps Cross

31
Connection

V3
subscriber lines
maximum of 16

2-Mbps

[S]HDSL 2 Mbps 2 Mbps

Application
Interface
for V3

4 lines
Pack
e.g. LPS503 (one logical
V3 link)
subscriber lines

Cross Con-
maximum of 16

nection 1:1

[S]HDSL ULL
2-Mbps
for ULL

2 Mbps 2 Mbps
4 lines Application Interface
Pack
e.g. LPS504 (one logical
ULL link)
maximum of 256
subscriber lines

SHDSL
for ULL

8 lines Application
Pack
4 unstructured AP_E1 lines with clock transparency
e.g. LPS510

Supported lines per interface

Each interface contains the provisioning data for its E1 ports. 64-kbps and E1
cross-connections provide the linkage between the used protocol and the corresponding
physical interfaces. Each V5.1 interface supports one E1 port (2 Mbps) and up to 30
subscriber lines (64 kbps). Each V5.2 interface supports up to 16 E1 ports (2 Mbps)
and up to 768 subscriber lines (64 kbps) (1728 subscriber lines for the LAG 4300
Shelf). Each V3 interface supports one E1 port (2 Mbps) and one subscriber line
(2 Mbps). Each leased line interface supports one E1 port (2 Mbps) and up to 31
analog leased lines (64 kbps), digital leased line channels, or VLL or GLL bearer
channels. Each unstructured leased line interface supports one E1 port (2 Mbps) and
one UVLL or one UGLL subscriber line (2 Mbps).
Important! A mix of services (V5.x and leased lines) on one E1 link is not
possible.

POTS subscriber
...................................................................................................................................................................................................................................

Connection
A POTS subscriber can be connected to the network via a V5.1 or V5.2 interface. In
the case of V5.1 it is associated with a specific 64-kbps timeslot of a V5.1 interface. In
the case of V5.2 it is associated with a V5.2 interface where the current 64-kbps
timeslot is selected on a per call base. The association of a POTS subscriber to a V5.x
interface is made on the service assignments layer (see “Provisioning tables” (p. 3-32)).
A concentration of POTS subscribers is only possible in the case of V5.2.

Provisioning
A POTS subscriber of the AnyMedia ® Access System must be provisioned to a Z port
located on an application pack capable of supporting POTS. It is possible to
pre-provision all entities to the database without having real hardware equipped at that
moment. Nevertheless the provisioning of a POTS subscriber on an application pack is
only possible if the application pack with its type was provisioned before and supplies
its Z ports for service. Therefore it is possible to check at provisioning time of any
subscriber whether the related pre-provisioned application pack is capable of serving
the subscriber. For example the provisioning of a 25th subscriber on a 24 Z port AP is
rejected at provisioning time. Furthermore the compatibility of the requested subscriber
type and the application pack can be checked. For example the provisioning of a POTS
subscriber on an ISDN AP is rejected at provisioning time.

Allocated Z ports
Each provisioned POTS subscriber allocates a Z port. The AnyMedia ® Access System
supports a retrieval with the physical access identifier as key to show the operator
which Z ports are already allocated and which ones are not used for any service yet.

ISDN BRA subscriber

Connection
An ISDN BRA subscriber has the transmission capability of two B-channels
(2×64 kbps) and one D-channel (16 kbps). The B-channels are transported in the
bearer channels of the V5.x interface; the D-channel is transported in the
communication channels of the V5.x interface. An ISDN BRA subscriber can be
connected to the network via a V5.1 or V5.2 interface. In the case of V5.1 up to two
B-channels are associated with up to two 64-kbps timeslots of a V5.1 interface. In the
case of V5.2 the current 64-kbps timeslots are selected on a per call basis. The
association of the D-channel to the communication channels of the V5.x interface is
always done by provisioning. The association of an ISDN BRA subscriber to a V5.x
interface is made on the service assignments layer (see “Provisioning tables” (p. 3-32)).
A concentration of ISDN BRA subscribers is only possible in the case of V5.2.

Provisioning
An ISDN BRA subscriber of the AnyMedia ® Access System must be provisioned to a
U port located on an application pack capable of supporting ISDN BRA service. It is
possible to pre-provision all entities to the database without having real hardware
equipped at that moment. Nevertheless the provisioning of an ISDN BRA subscriber on
an application pack is only possible if the application pack with its type was
provisioned beforehand and provides its U ports for service. Therefore it is possible to
check at provisioning time of any subscriber whether the related pre-provisioned
application pack is capable of serving the subscriber. For example the provisioning of a
13th subscriber on an ISDN AP with 12 U ports is rejected at provisioning time.
Furthermore the compatibility of the requested subscriber type and the application pack
can be checked. For example the provisioning of an ISDN BRA subscriber on a POTS
AP is rejected at provisioning time.

Allocated U ports
Each provisioned ISDN BRA subscriber allocates a U port. The AnyMedia ® Access
System supports a retrieval with the physical access identifier as key to show the
operator which U ports are already allocated and which ones are not used for any
service yet.

V5 ISDN PRA subscriber

Connection
A V5 ISDN PRA subscriber has the transmission capability of up to 30 B-channels
(30×64 kbps) and one D-channel (64 kbps). The B-channels are transported in the
bearer channels of the V5.2 interface; the D-channel is transported in the
communication channels of the V5.2 interface. A V5 ISDN PRA subscriber is
connected to the network via a V5.2 interface. It is associated to a V5.2 interface
where the current 64-kbps timeslots are selected on a per call basis. The association of
the D-channel to the communication channels of the V5.2 interface is done by
provisioning. The association of a V5 ISDN PRA subscriber to a V5.2 interface is
made on the service assignments layer (see “Provisioning tables” (p. 3-32)).

Provisioning
Prior to provisioning of a V5 ISDN PRA subscriber an HDSL logical interface must be
provisioned:
• The HDSL logical interface must be provisioned on top of one or two HDSL ports
located on an HDSL application pack. The usage of one or two HDSL ports
depends on the provisioned HDSL application mode and defines the maximum
bearer channel capacity of 15 or 30 bearer channels. HDSL logical interfaces
autocreate HDSL logical timeslots which may be used by the services. After that a
V5 ISDN PRA subscriber can be provisioned on top of the HDSL logical interface.
The used HDSL logical timeslots are specified in a provisioning command. Note
that on top of an HDSL logical interface also other services and a service mix can
be provisioned.
• The HDSL logical interface must be provisioned on top of an SHDSL port located
on an SHDSL application pack. The HDSL logical interface autocreates logical
timeslots which are used by the services. After that a V5 ISDN PRA subscriber can
be provisioned on top of the HDSL logical interface.
It is possible to pre-provision all entities to the database without having real hardware
equipped at that moment. Nevertheless the provisioning of a V5 ISDN PRA subscriber
on an application pack is only possible if the application pack with its type was
provisioned beforehand and provides its [S]HDSL ports for service. Therefore it is
possible to check at the provisioning time of any subscriber whether the related
pre-provisioned application pack is capable of serving the subscriber. Furthermore the
compatibility of the requested subscriber type and the application pack can be checked.

Allocated HDSL timeslots

Each provisioned V5 ISDN PRA subscriber allocates HDSL timeslots on an HDSL
logical interface. The AnyMedia ® Access System supports a retrieval to show the
operator which HDSL timeslots on an HDSL logical interface are already allocated and
which ones are not used for any service yet.

Allocated [S]HDSL ports

Each provisioned HDSL interface allocates one or two HDSL ports, or one
SHDSL port. The AnyMedia ® Access System supports a retrieval with the physical
access identifier as key to show the operator which [S]HDSL ports are already
allocated and which ones are not used for any service yet.

V3 ISDN PRA subscriber

Connection
A V3 ISDN PRA subscriber is provided by connecting all 32 64 kbps timeslots
supplied by two HDSL ports or by one SHDSL port to 32 timeslots of one E1 port.
Both the subscriber and the service node side have to be provisioned to support V3
line. For the service node side this has to be done for the E1 link. The E1 link is used
for V3 service only.
The association of a V3 subscriber with a V3 interface is made on the service
assignments layer (see “Provisioning tables” (p. 3-32)).

Provisioning
Prior to provisioning of a V3 ISDN PRA subscriber an HDSL logical interface in V3
point-to-point mode must be provisioned on top of two HDSL ports located on an
HDSL application pack, or an HDSL logical interface in V3 point-to-point single pair
mode must be provisioned on top of an SHDSL port located on an SHDSL application
pack. This HDSL logical interface autocreates 32 HDSL logical timeslots which are
used by the V3 service. After that a V3 ISDN PRA subscriber can be provisioned on
top of the HDSL logical interface. Note that on top of an HDSL logical interface in V3
point-to-point mode or in V3 point-to-point single pair mode exactly one V3 ISDN
PRA subscriber can be provisioned.
It is possible to pre-provision all entities to the database without having real hardware
equipped at that moment. Nevertheless the provisioning of a V3 ISDN PRA subscriber
on an application pack is only possible if the application pack with its type was
provisioned beforehand and provides its [S]HDSL ports for service. Therefore it is
possible to check at the provisioning time of any subscriber whether the related
pre-provisioned application pack is capable of serving the subscriber. Furthermore the
compatibility of the requested subscriber type and the application pack can be checked.

Allocated HDSL timeslots

Each provisioned V3 ISDN PRA subscriber allocates 32 HDSL timeslots on an HDSL
logical interface. The AnyMedia ® Access System supports a retrieval to show the
operator which HDSL timeslots on an HDSL logical interface are already allocated and
which ones are not used for any service yet. In case of V3 ISDN PRA service always
all timeslots are allocated.

Allocated [S]HDSL ports

Each HDSL interface provisioned in V3 point-to-point mode allocates two
HDSL ports, each HDSL interface provisioned in V3 point-to-point single pair mode
allocates one SHDSL port. The AnyMedia ® Access System supports a retrieval with
the physical access identifier as key to show the operator which [S]HDSL ports are
already allocated and which ones are not used for any service yet.

V5 independency
The V3 ISDN PRA subscriber is independent of the V5.x interface. It is transported on
E1 links, which are exclusively used for that purpose.

V5 frame relaying (ISDN)

Frame handling
Frames received from the local exchange (LE) on a certain communication channel are
to be discriminated according to their information type and sent either to the
COMDAC or to the ISDN user port concerned.

Routing topology
Based on the provisioning the AnyMedia ® Access System routes
• in the downstream (from the LE) direction to the correct pack all V5 frames
received from communication channels
• in the upstream direction (towards the LE) towards the V5 communication channel
concerned all D-channel frames received from the ports.
The following figure shows the HDLC frame relaying.

Subscriber Side Network Side

1
2
3 V5 CC in V5.x interface
4 1

ISDN D 16
12 ports Application
frame routing

Pack
e.g. LPU112

HDSL D 64
4 ports Application
Pack
e.g. LPS501
48

253
254
255
256

POTS/ISDN operation modes

Default mode
Per default the AnyMedia ® Access System is provisioned for a POTS-only operation
mode.

POTS-only mode
In POTS-only mode no ISDN frame relaying function is supported and an IO_HDLC
is not necessary. Digital leased line services (DLL) and semipermanent digital leased
line services (SPDLL) are supported in POTS-only mode.

POTS and small ISDN mode

The POTS and small ISDN operation mode is defined in the AnyMedia ® LAG 4300
Shelf only. In this mode a maximum of 36 ISDN BRA or 36 ISDN PRA subscribers is
provisionable and no IO_HDLC pack is necessary.

Mixed POTS/ISDN mode

The mixed POTS/ISDN operation mode is defined in the AnyMedia ® ETSI V5 Shelf
and in the AnyMedia ® 800 Shelf only. In this mode a maximum of 256 ISDN BRA or
64 ISDN PRA subscribers is provisionable and at least one IO_HDLC pack is
necessary.

Number of CCs
In POTS-only and POTS and small ISDN operation mode a maximum of 16 V5
communication channels are provisionable. In mixed POTS/ISDN operation mode at
least one IO_HDLC must be provisioned for supporting V5 communication channels
and switched ISDN services. In this case 48 V5 communication channels are
supported.

Analog leased lines

Purpose
An analog leased line (ALL) service is used for purposes other than telephony - for
example, data transmission with modems. The AnyMedia ® Access System supports
ALL according to ITU M.1020, M.1025, and M.1040.

Connection of ALL subscribers

An ALL subscriber is connected to the network via a leased line interface which is
associated with a specific 64-kbps timeslot. ALLs are provided by cross-connecting a
Z port on the subscriber side (located at a POTS AP) with one timeslot of an E1 link
on the network side. The Z port has to be provisioned to support ALL and the E1 link
has to be provisioned for permanent leased line (PLL) purposes. In this way the
subscriber’s terminal equipment (TE) is connected to either a digital access
cross-connect system (DACS) or an inter-office data network for routing PLL service
circuits. The association of an ALL subscriber with a leased line interface is made on
the service assignments layer (see “Provisioning tables” (p. 3-32)).

Connection of SPALL subscribers

An SPALL subscriber is connected via a V5.1 or via V5.2 interface to a local exchange
(LE). SPALL is provisioned on top of a Z port and uses one bearer channel. The
bearer channels are established semipermanently under control of the LE by the BCC
protocol (V5.2) in agreement with the access network or via provisioning in the access
network (V5.1).

Provisioning
An (SP)ALL subscriber of the AnyMedia ® Access System must be provisioned to a
Z port located on an application pack capable of supporting ALL. It is possible to
pre-provision all entities to the database without having real hardware equipped at that
moment. Nevertheless the provisioning of an ALL subscriber on an application pack is
only possible if the application pack with its type was provisioned before and supplies
its Z ports for service. Therefore it is possible to check at provisioning time of any
subscriber whether the related pre-provisioned application pack is capable of serving
the subscriber. Furthermore the compatibility of the requested subscriber type and the
application pack can be checked.

Service mix on leased line links

A mix of DLL, ALL, VLL and GLL on one E1 leased line link is possible.

Digital leased lines

Connection of DLL subscribers

The AnyMedia ® Access System supports digital leased lines (DLL) with a transmission
capability of two B-channels (2×64 kbps) and one D-channel (16 kbps) on one
U interface. The DLLs are provided by connecting a U port located at an ISDN AP
with up to three timeslots of an E1 link. The U port has to be provisioned to support
DLL and the E1 link has to be provisioned to be used for permanent leased line
purposes. In this way the subscriber’s terminal equipment (TE) is connected to the
network provider’s digital leased line service node (DLLSN) for routing permanent
leased line service circuits. A DLL subscriber is connected to the network via a leased
line interface with up to three 64-kbps timeslots, two for the B-channels and one for
the D-channel. The 16-kbps D-channel is carried over a 64-kbps timeslot. The
association of a DLL subscriber with a leased line interface is made on the service
assignments layer (see “Provisioning tables” (p. 3-32)).

Connection of SPDLL subscribers

An SPDLL subscriber is connected via a V5.1 or via V5.2 interface to a local
exchange (LE). SPDLL is provisioned on top of a U port with a transmission
capability of up to two B-channels. The D-channel is not used for SPDLLs. The
B-channels to be used are provisionable. The bearer channels are established
semipermanently under control of the LE by the BCC protocol (V5.2) in agreement
with the access network or via provisioning in the access network (V5.1).

Provisioning
A (SP)DLL subscriber of the AnyMedia ® Access System must be provisioned on an AP
which supports U ports. It is possible to pre-provision all entities to the database
without having real hardware equipped at that moment. Nevertheless the provisioning
of a DLL subscriber on an application pack is only possible if the application pack
with its type was provisioned beforehand and provides its U ports for service.
Therefore it is possible to check at provisioning time of any subscriber whether the
related pre-provisioned application pack is capable of serving the subscriber.
Furthermore the compatibility of the requested subscriber type and the application pack
can be checked.

Multiple B-channels (n × 64 kbps)

Two B-channels of the U interface offer two independent 64-kbps bit streams at the
TE. If the subscribers want higher data rates in one bit stream (n × 64 kbps) at the TE,
multiple B-channels of more than one U interface can be used. The byte integrity of
these different B-channels must be maintained by the TE, that is the AnyMedia ®
Access System does not support it. Additionally the subscriber D16-channel can be
transmitted transparently over an LL interface 64-kbps bit stream.

All the timeslots providing the service for a unique DLL subscriber are allocated in the
same E1 link.

Service mix on leased line links

A mix of DLL, ALL, VLL and GLL on one E1 leased line link is possible.

DLL via managed NTUs

A DLL service can be provided by using a managed NTU, that is a 2B1Q ISDN digital
subscriber line NTU which is fully managed by the AnyMedia ® Access System. The
NTU provides the subscriber a single channel operating at one of many speeds,
depending on the NTU type and configuration, from 1.2 kbps through to 128 kbps.

N × 64 kbps leased lines

Two types of n × 64 kbps leased lines

The AnyMedia ® Access System supports two kinds of n × 64 kbps digital leased line
services over HDSL interface:
• VLL
A digital leased line via a data interface is supported, which can be either V.35,
V.36 or X.21
• GLL
A leased line with G.703 interface is supported.
In both cases the interface is provided by means of an NTU which is located on the
subscriber side of an HDSL transmission system.

Connection
An n × 64 kbps digital leased line (VLL or GLL) subscriber has the transmission
capability of up to 31 B-channels (31 × 64 kbps) and is connected to the network via
a leased line interface with up to 31 64-kbps timeslots. VLL and GLL subscribers are
provided by connecting a number of bearer channels supplied by a VLL or GLL entity
with the same number of timeslots of a leased line interface. The association of a VLL
or GLL subscriber with a leased line interface is made on the service assignments layer
(see “Provisioning tables” (p. 3-32)).

Provisioning
Prior to provisioning of a VLL or GLL subscriber an HDSL logical interface must be
provisioned on top of one or two HDSL ports located on an HDSL application pack, or
an HDSL logical interface must be provisioned on top of an SHDSL port located on an
SHDSL application pack. The usage of one or two HDSL ports depends on the
provisioned HDSL application mode and defines the maximum bearer channel capacity
of 15 or 31 bearer channels. HDSL logical interfaces autocreate HDSL logical
timeslots which may be used by the services. After that a VLL or GLL subscriber can
be provisioned on top of the HDSL logical interface. The used HDSL logical timeslots
are specified in a provisioning command. Note that on top of an HDSL logical
interface also other services and a service mix can be provisioned.
It is possible to pre-provision all entities in the database without having real hardware
equipped at that moment. Nevertheless the provisioning of a VLL or GLL subscriber
on an application pack is only possible if the application pack with its type was
provisioned beforehand and provides its [S]HDSL ports for service. Therefore it is
possible to check at the provisioning time of any subscriber whether the related
pre-provisioned application pack is capable of serving the subscriber. Furthermore the
compatibility of the requested subscriber type and the application pack can be checked.
All the timeslots providing the service for a unique VLL or GLL subscriber are
allocated in the same E1 link.

V5 independency
VLL and GLL are independent of the V5.x interface. They are transported on E1 links,
which are exclusively used for leased line purposes. A mix of DLL, ALL, VLL and
GLL on one E1 link is possible.

Allocated HDSL timeslots

Each provisioned VLL and GLL subscriber allocates up to 31 HDSL timeslots on an
HDSL logical interface. The AnyMedia ® Access System supports a retrieval to show
the operator which HDSL timeslots on an HDSL logical interface are already allocated
and which ones are not used for any service yet.

Allocated [S]HDSL ports

Each HDSL interface provisioned for VLL and GLL subscribers allocates one or two
HDSL ports, or one SHDSL port. The AnyMedia ® Access System supports a retrieval
with the physical access identifier as key to show the operator which [S]HDSL ports
are already allocated and which ones are not used for any service yet.

Unstructured leased line subscriber via IO_E1

Connection
An unstructured leased line subscriber is provided by connecting all 32 64 kbps
timeslots supplied by up to two [S]HDSL ports to 32 timeslots of one E1 port. Both
the subscriber and the service node side have to be provisioned to support unstructured
leased line. For the service node side this has to be done for the E1 link. The E1 link
is used for unstructured leased line service only.
The association of an unstructured leased line subscriber with an unstructured leased
line interface is made on the service assignments layer (see “Provisioning tables”
(p. 3-32)).

Provisioning
Prior to provisioning of an unstructured leased line subscriber an HDSL logical
interface in unstructured point-to-point mode must be provisioned on top of two HDSL
ports located on an HDSL application pack, or an HDSL logical interface in
unstructured point-to-point single pair mode must be provisioned on top of an SHDSL
port located on an SHDSL application pack. This HDSL logical interface autocreates
32 HDSL logical timeslots which are used by the unstructured leased line service.
After that an unstructured leased line subscriber can be provisioned on top of the
HDSL logical interface. Note that on top of an HDSL logical interface in unstructured
point-to-point mode or in unstructured point-to-point single pair mode exactly one
unstructured leased line subscriber can be provisioned.
It is possible to pre-provision all entities to the database without having real hardware
equipped at that moment. Nevertheless the provisioning of an unstructured leased line
subscriber on an application pack is only possible if the application pack with its type
was provisioned beforehand and provides its [S]HDSL ports for service. Therefore it is
possible to check at the provisioning time of any subscriber whether the related
pre-provisioned application pack is capable of serving the subscriber. Furthermore the
compatibility of the requested subscriber type and the application pack can be checked.

Allocated HDSL timeslots

Each provisioned unstructured leased line subscriber allocates 32 HDSL timeslots on
an HDSL logical interface. The AnyMedia ® Access System supports a retrieval to show
the operator which HDSL timeslots on an HDSL logical interface are already allocated
and which ones are not used for any service yet. In case of unstructured leased line
service always all timeslots are allocated.

Allocated [S]HDSL ports

Each HDSL interface provisioned in unstructured point-to-point mode allocates two
HDSL ports, each HDSL interface provisioned in unstructured point-to-point single
pair mode allocates one SHDSL port. The AnyMedia ® Access System supports a
retrieval with the physical access identifier as key to show the operator which
[S]HDSL ports are already allocated and which ones are not used for any service yet.

V5 independency
The unstructured leased line subscriber is independent of the V5.x Interface. It is
transported on E1 links, which are exclusively used for that purpose.

Unstructured leased line subscriber via AP_E1

Connection
An unstructured leased line subscriber is provided by connecting all 32 64 kbps
timeslots supplied by one SHDSL port to 32 timeslots of one E1 port located on the
same SHDSL AP. Both the subscriber and the service node side have to be provisioned
to support unstructured leased line. The E1 link on the SHDSL AP is used for
unstructured leased line service only.
The association of an unstructured leased line subscriber with an unstructured leased
line interface is made on the service assignments layer (see “Provisioning tables”
(p. 3-32)).

Provisioning
Prior to provisioning of an unstructured leased line subscriber an HDSL logical
interface in unstructured point-to-point single pair mode must be provisioned on top of
an SHDSL port located on an SHDSL application pack. This HDSL logical interface
autocreates 32 HDSL logical timeslots which are used by the unstructured leased line
service. After that an unstructured leased line subscriber can be provisioned on top of
the HDSL logical interface. Note that on top of an HDSL logical interface in
unstructured point-to-point single pair mode exactly one unstructured leased line
subscriber can be provisioned.
It is possible to pre-provision all entities to the database without having real hardware
equipped at that moment. Nevertheless the provisioning of an unstructured leased line
subscriber on an application pack is only possible if the application pack with its type
was provisioned beforehand and provides its SHDSL ports for service. Therefore it is
possible to check at the provisioning time of any subscriber whether the related
pre-provisioned application pack is capable of serving the subscriber. Furthermore the
compatibility of the requested subscriber type and the application pack can be checked.

Allocated HDSL timeslots

Each provisioned unstructured leased line subscriber allocates 32 HDSL timeslots on
an HDSL logical interface. The AnyMedia ® Access System supports retrieval with the
physical access identifier as key to show the operator which HDSL timeslots on an
HDSL logical interface are already allocated and which ones are not used for any
service yet.

Provisioning model
...................................................................................................................................................................................................................................

Definition
Provisioning will supply the AnyMedia ® Access System with all necessary data to meet
the customer configuration, for example to prepare the Z port and U port circuits for
service by defining their function and setting any required options. All provisioned data
will be stored in a nonvolatile data storage (NVDS).

Provisioning model
“Provisioning tables” (p. 3-32) shows the provisioning model of the AnyMedia ® Access
System in a simplified data-oriented view. This structure reflects a client/server
concept, consisting of several layers which are linked by means of relationships. In this
structure the lower layer acts as a server and the upper layer as a client. The given
structure implies that several objects of these layers have to be provisioned before the
AnyMedia ® Access System can provide service.
These layers are
• Equipment
• Logical line / logical interface
• Service assignment.

Provisioning tables
The data which are to be provisioned for the particular layers are modeled by means of
tables. For every layer one or more tables may exist. Lower layers must be provisioned
before the upper layers following the client/server structure. As the subscriber side and
the network side are independent of each other, the sequence of provisioning is not
predefined.
The next figure shows a layered provisioning model.

Layers
These are the layers of the provisioning model:
• The equipment layer at the bottom contains all the configuration data of the
hardware equipment.
This includes the type of application packs on the subscriber side and the IO_E1s
on the network side.
• The logical line/logical interface layer defines the usage (for example POTS, ISDN,
V5.1) of the hardware.
Subscriber side and network side can be provisioned independent of each other.
Usage-dependent configuration data are defined here (for example feeding current,
interface identity).
• The service assignment layer connects both sides, subscriber and network side.
The service assignments layer represents the ability of the system to associate a
logical interface on the network side with a logical line on the subscriber side
rather than a hard-wired cross-connect. The physical cross-connection is done on
demand depending on service and call states.

Equipment layer
On the equipment layer the type of the application packs is defined. On this layer all
physical ports (for example Z ports, U ports) and their usage can be retrieved. The
definition of an application pack is independent of the existence of the real hardware,
that is pre-provisioning is possible.

Logical line/logical interface layer

The AnyMedia ® Access System supports various narrowband services. The subscriber
interfaces for these services are supported via several APs. The APs contain no
physical option switches; instead, their function is controlled by electronic service
provisioning information which is stored in a non-volatile manner in the AnyMedia ®
Access System. The database in the AnyMedia ® Access System compares this stored
service provisioning information with the equipped APs and, if they are compatible, the
software conditions the AP hardware to provide the desired service. To establish
service on a physical port of the AnyMedia ® Access System, the physical port must be
assigned to a logical line within the system. A physical port may be assigned to only 1
logical line, except for multiservice capable HDSL ports, which allow more than one
logical line.
The association between a logical line and a physical port can be changed by deleting
and entering a new logical line. This permits the physical appearance of a logical line
to be easily moved from one physical port to another physical port without changing
the serving switch’s database.
The AnyMedia ® Access System supports V5.1/V5.2, V3, and PLL logical interfaces to
connect to a network. All these interfaces are supported via the E1 links, their function
is controlled by electronic service provisioning information which is stored in a
non-volatile manner in the AnyMedia ® Access System.

Service assignment layer

To establish service through the system, a logical line must be assigned to a logical
interface. This is done in the service assignment layer by means of logical
cross-connections.

Service state model

Service state overview

Most of the physical or logical entities within the AnyMedia ® Access System maintain
a service state to indicate their respective operational state and usability. The
AnyMedia ® Access System facilitates two kinds of service states, an administrative as
well as a system-driven service state. In each case the service state is divided into a
mandatory primary service state and an optional secondary service state.

Administrative service state

An administrative service state is used for physical or logical entities which can be
configured to be ″in service″ (IS) or ″out of service″ (OOS). In this case the primary
service state is set by the operator via management functions. This primary service
state is stored in the database of the AnyMedia ® Access System and expresses the
desired operational state of such an entity, that is, not necessarily the current
operational state. Such an administrative service state allows the operator for example
to temporarily remove an entity from service without deleting its configuration data.
Whether the entity is really operational is indicated by the accompanying secondary
service state. The secondary service state is system-driven and indicates any failure
condition that the entity might have. A ″null″ secondary service state with an ″in
service″ primary service state shows that the entity is operational without any failure
condition. Any secondary service state with an ″in service″ primary service state means
that the entity is supposed to be working but currently a fault prevents it from being
operational.

System-driven service state

Contrary to the administrative service state the system-driven service state is used for
entities which cannot be configured to be ″in service″ or ″out of service″. For these
entities the primary as well as the secondary service state is system-driven and
indicates the operational state of the entity. Here the primary service state alone already
indicates whether the entity is operational (″in service″) or not (″out of service″). If the
entity is not operational the accompanying secondary service state indicates which
failure condition led to the failure.

Primary service state

The primary service state is always one of the following values:
• In service (IS)
• Out of service (OOS).
In the case of an administrative service state it is set by the operator while for a
system-driven service state it is set autonomously by the AnyMedia ® Access System.

Secondary service state

The following table lists some example values used for the secondary service state. A
complete list is available in the Commands and procedures for narrowband services.

Secondary service state Meaning

NAC Not accessible The unit is not accessible
NOP Not operational The unit is not operational
SHD Shutting down SHD is a special state triggered by the operator. The
operator intends to move the unit from IS to OOS, but needs
a positive acknowledgement from the network to succeed.
UEQ Unequipped The hardware is not present
FLT Fault Hardware fault detected

Remote operations channel (ROC)

ROC carried over leased line interface

The ROC carried over leased line interface (LL ROC) is independent of the V5.x
interface. It is transported on E1 links, which are used exclusively for that purpose or
also for ALL, DLL, VLL or GLL.
For provisioning an LL ROC also the layered structure applies. The given structure
implies that three objects have to be provisioned with data for the lines and the service
assignments layer before the ROC can be used. These three objects are ’ROC’, ’leased
line interface’ and ’leased line service’.
The ROC acts as a virtual port. Therefore there is no equipment and slot layer for the
ROC. Provisioning and maintenance of the E1 link (equipment layer) and IO_E1 (slot
layer) is the same as for ALL.

SPLL ROC over V5.x interface

The ROC carried over semipermanent leased line (SPLL ROC) is transported via V5.x
interface on E1 links, which can be used for that ROC and for other purposes, for
example POTS or ISDN.
For provisioning an SPLL ROC also the layered structure applies. The given structure
implies that several objects have to be provisioned with data for the lines and the
service assignments layer before the ROC can be used. These objects are ’ROC’, ’V5.x
interface’ and ’V5.x cross-connection’.
The ROC acts as a virtual port. Therefore there is no equipment and slot layer for the
ROC. Provisioning and maintenance of the E1 link (equipment layer) and IO_E1 (slot
layer) is the same as for PLN.

Remote operations channel (ROC) for remote terminal

OAM&P interfaces for remote terminal

The figure below displays all supported OAM&P interfaces of a remote terminal and
the supported transported capabilities via a host terminal. In any case both the host and
the remote terminal are separate management entities and a management system must
setup independent management connections to each of the two systems. There are no
means in place that any provisioning done in one system is automatically propagated to
the other system. However, if both systems are connected in any of the described ways
to a DCN it is possible at both network element locations to connect via the local LAN
or CIT (if PPP is used) connectors and via the DCN to the other system. At the routing
solution (3) in the figure even a direct connection, without any external DCN, is
possible between host and remote terminal.
The dedicated ROC timeslot is only used if any of the nailed-up ROC configurations
as described below is used. If none are used this nailed-up ROC timeslot is usable as
normal bearer channel.

GSI/EMS

DCN
LE
(V5 switch)

V5 LLL LLL V5 V5 LLL

Bearer channel
Host timeslots Remote
terminal terminal
Remote
1 terminal link V5
ROC SSPLL
Remote V5 SSPLL ROC
LAN 2 ...
CIT IP Proprietary LAN
Router IP CIT
3 Router
... 4
Dedicated ROC roc-2...n
roc-2...n timeslot

Remote operations for remote terminal can be performed via the standard OAM&P
interfaces or via ROC for remote terminal.
The standard OAM&P interfaces (4) in the figure are:
• ROC via locally connected leased line link
• ROC via locally connected V5 interface

• CIT interface
• LAN interface.

ROC for remote terminal

A ROC for remote terminal is used for transporting management information between
host and remote terminal and the GSI/EMS. The information is transported via an
embedded 64-kbps channel that is part of the remote terminal link (E1 link) between
host and remote terminal. The system supports the following types of ROC for remote
terminal:
• remote semipermanent V5.2 ROC, (1) in the figure above
• ROC via nailed-up remote link timeslot and leased line link transport in host
terminal, (2) in the figure above
• ROC via nailed-up remote link timeslot and IP-routed transport in host terminal, (3)
in the figure above.

Remote semipermanent V5.2 ROC

The remote terminal supports the transport of a V5.2 semipermanent leased line
connected to a ROC in the remote terminal. This setup treats the ROC as any other
remote subscriber in the remote terminal. This means that the ROC is using one of the
remote link bearer channels and not the dedicated nailed-up timeslot of the remote link.
As such a ROC is transparent for the host terminal no IP provisioning is needed in the
host terminal. In the host terminal only the single-channel semipermanent leased line
user port, without any ROC specifics, needs to be provisioned. In the remote terminal
the ROC is provisioned as usual, that is, the ROC is associated to a single-channel
semi-permanent leased line V5 user port of the host interface. Also the IP related
provisioning of the ROC is done in the remote terminal. IP routing to other OAM&P
interfaces of the remote terminal is supported as in prior releases.

Nailed-up leased line link timeslot ROC

In this case a timeslot of a leased line link connected to the host terminal is
cross-connected by provisioning to a remote terminal interface in the host terminal.
The system then transparently transports this ROC in the nailed-up ROC time slot on
the remote link. For protection purposes this ROC timeslot is reserved on all remote
terminal links. Such a ROC is transparent for the host terminal and therefore no IP
provisioning is needed in the host terminal. As this kind of ROC is mutually exclusive
with the ROC via nailed-up remote link timeslot and IP-routed transport in host
terminal, a provisioning of both is denied in the host terminal.

Nailed-up IP-routed ROC

In the host terminal additional ROC entities are introduced for this application. When
the ROC interface is activated for a remote terminal interface the system allocates a
QMC termination for it and activates the transport via the nailed-up ROC time slot on
the remote link. IP related provisioning is done in the host terminal. As this kind of

ROC is mutually exclusive with the ROC via nailed-up remote link timeslot and leased
line link transport in host terminal, a provisioning of both is denied in the host
terminal.

Mismatch of provisioning between host and remote terminal

Provisioning mismatch checks

A mismatch check of the provisioning of the interface related attributes
• nailed-up ROC usage
• ISDN service support, that is, the ISDN D-Channel channel (IDCC) usage
is done right after the interface identification check. At any mismatch of the settings
the interface startup fails, the interface stays not operational and an appropriate alarm
is raised. This is to ensure that the proper remote terminal link timeslots are reserved
for these usages.
An alignment between the provisioning in the host and the remote terminal is done on
base of
• the V5 user port type,
• the V5 layer 3/envelope function address,
• and the V5 interface access identifier of the related V5 interface in the host, if
multiple host terminal interfaces are provisioned for the remote terminal. As the V5
interface access identifier is the internal unique key to route ISDN D-channel data
within the remote terminal it must be ensured within the remote terminal that this
Id is unique across multiple host terminal interfaces. Whenever the V5 interface
access identifier is synchronized between host and remote terminal the remote
terminal has to check whether the delivered V5 interface access identifier does not
exist yet within the other host terminal interface. If it already exists, the remote
terminal reacts in the synchronization procedure with a failed indication towards
the host terminal and does not enter the “synced” state for the specified user port.
This behavior ensures that the user port will never get operational.

Treatment of provisioning mismatches

The sequence of provisioning of remote terminal subscribers can be done in any order
in the host and the remote terminal. Intermediate provisioning mismatches are treated
as below:
• User port to V5 interface cross-connection provisioned in the host. User port to
host interface cross-connection not provisioned in remote terminal.
Host behavior: This case is identified in the host by system internal messaging via
the remote link. For a single user port this case is treated like an application pack
failure in classic mainshelf/subshelf application. The user port is set to blocked
towards the switch with a V5 block indication message. Any unblock request by

the switch is denied/answered with block indication. As the V5 user port entity
does not support any operator visible service state this case is not visible for the
operator.
Remote terminal behavior: Nothing special, a standalone ″V5 User Port″ is always
in the internal “Not Associated” sync state.
• User port to V5 interface cross-connection not provisioned in the host (but ″V5
User Port″ can already exist). User port to host interface cross-connection
provisioned in remote terminal.
Host behavior: Nothing special, a standalone ″V5 User Port″ is always in the
internal “Not Associated” sync state.
Remote terminal behavior: This case is identified in the remote terminal by system
internal messaging via the remote link. On the operator interface this case is
reflected with the existing line termination service state “Network Side Failed”.
This means that for remote subscribers in the remote terminal this service state
either indicates that
– the host interface of the remote terminal is failed
– the V5 interface in the host is failed
– a missing provisioning of the user port in the host
– a missing provisioning of the user port cross-connection to the V5 interface in
the host.

Managed NTU provisioning

Description of managed NTUs

A managed NTU is a 2B1Q ISDN digital subscriber line NTU which is fully managed
by the AnyMedia ® Access System. The NTU provides the subscriber a single channel
operating at one of many speeds, depending on the NTU type and configuration, from
1.2 kbps through to 128 kbps. Speeds below 56 kbps are provided using the X.50 Div.
3 standard except for 1.2 kbps which uses a proprietary protocol. Speeds of 64 kbps
or below use only the first B-channel of the digital leased line.
Management of managed NTUs is performed via the D-channel, so that channel is not
available to the subscriber. The NTU management requires the use of one of the
HDLC channels on the COMDAC. The use of a single HDLC channel to manage all
NTUs imposes the following restrictions:
• The AnyMedia ® Access System can communicate with one NTU at a time.
• If an NTU is not responding then any time spent waiting for the NTU to time-out
blocks communication with other NTUs. This time-out is at most 10 seconds.

Managed NTU configurable parameters

The managed NTU attributes configurable by the AnyMedia ® Access System are:
• NTU interface type
• NTU speed
• Data clocking mode
• Character length
• V.14 mode
• RTS to CTS delay
• Control/RTS mode
• Indication/RLSD mode
• DSR/DTR mode
• Remote loopback inhibit mode
• X.21 byte timing
• External clock mode
• Anti-streaming timer
• Anti-streaming retry timer.
Many of these attributes need not have a value specified when the NTU is created - if
no value is given then the attribute receives a default value from the NTU default
profile. The default profile may be viewed and changed by the TL1 commands.

NTU status information

The user is able to retrieve the following current NTU status information:
• Control line status
• Loopback status
• Anti-streaming state
• LED status.
These are all retrieved through the ISDN port using the TL1 command
RTRV-EXTEQPT.

NTU service states

An NTU has two primary service states (IS and OOS). These service states are divided
into different secondary service states (IS, IS-ECM, IS-MON, IS-TST, OOS,
OOS-NAC, OOS-TST).
The NTU has these service states in the following conditions:
• OOS-NAC: The initial state. The U port is OOS.
• OOS: The U port is IS. Layer 1 is down.
• OOS-TST: The NTU or remote NTU has been looped by the AnyMedia ® Access
System while in state OOS (a non-transparent loopback).
• IS: The U port is IS. Layer 1 is up. The drop is usable. The NTU type matches the
configured type.
• IS-ECM: The U port is IS. Layer 1 is up. The drop is usable. The NTU type does
not match the configured type.
• IS-MON: A non-service affecting NTU alarm has been raised.
• IS-TST: The NTU or remote NTU has been looped by the AnyMedia ® Access
System while in state IS (a transparent loopback).

V5 re-provisioning
...................................................................................................................................................................................................................................

Definition
The re-provisioning capability allows the operator of V5 networks to enter standby V5
interface provisioning datasets in both the local exchange (LE) and the access network
(AN) without disturbing existing services of the V5 interface. In the AnyMedia ®
Access System the standby provisioning datasets are stored within the system itself and
not for example in the related EMS. The creation of standby provisioning datasets can
be performed asynchronously (and without notice to each other) in the local exchange
and the access network at different times. The equality of these both standby
provisioning datasets is in the responsibility of the overall network management. The
activation of a standby provisioning dataset can be initiated on demand either at the
local exchange or the access network and is then performed via the V5 message
protocol between the two nodes. Both involved systems check the existence, but not
the equality, of the provisioning dataset to be switched to, block all associated user
ports of the V5 interface, then switch over to the new provisioning dataset and unblock
all user ports again. In this way a change from one provisioning dataset to another can
be accomplished with a minimum of downtime of existing services.

Usage of re-provisioning
The re-provisioning capability should not be used for incremental changes of single
user ports or single V5 links. Incremental changes on the active dataset with single
TL1 commands is still available and should be used because these actions do not
disturb existing service of the interface. The main reason to use re-provisioning instead
of incremental changes is the need to change a huge amount of provisioning data at a
dedicated time, for example at disaster recovery or reorganization of the network.

Basic re-provisioning procedure

The basic procedure of a switch over to a new variant initiated in the AN is
• optionally verifying that the provisioning variant id to be switched to is available in
LE
• requesting a switch over with the provisioning variant id to be switched to
• blocking of related user ports in the LE, no explicit user port block messages are
sent by the LE
• acknowledging and indicating to start the provisioning variant switch from LE
• blocking V5 user ports internally in the AN
• changing to new provisioning variant dataset on both sides
• making old current interface dataset now a standby provisioning variant
• restarting V5 interface as at normal V5 interface activation
• unblocking of user ports.

Provisioning variant states

The following provisioning variant states are defined. For each state a different level of
provisioning integrity of the provisioning variant is defined.
• PV0 - Not ready for re-provisioning PV0 integrity means: Internal integrity,
external existence integrity, changes allowed
• PV1 - Ready for re-provisioning PV1 integrity means: Internal integrity, external
allocation integrity, no changes allowed
• PV2 - Re-provisioning in progress No additional integrity checks
• PV3 - Active PV3 integrity means: Internal integrity, external allocation integrity,
changes allowed.

Scenario extension of dataset

The following figure illustrates a re-provisioning scenario which extends the dataset of
a V5 interface. The example given here is for one interface only to reduce the
illustration complexity but can be extended for more interfaces in the same manner.
Re-provisioning scenario - extension of dataset

Current Interface Current Interface Provisioning Variant

dataset dataset
Step 1: Provisioning variant 20 contains
same associations as in current interface
dataset (PVAR10), State PV0

PVAR 10 PVAR 20

Step 2: Current system dataset is extended with objects,

provisioning variant 20 is extended with associations
to objects in current system dataset, State PV0

PVAR 10 PVAR 20
time

Step 3: Provisioning variant 20 is checked against

current system dataset at setting it ‘available’, related
objects in current system dataset are ‘PV1-allocated’,
State PV1
PVAR 10 PVAR 20

Step 4: Re-provisioning has taken place, provisioning

variant 20 is part of current interface dataset, old current
interface dataset is now provisioning variant 10 in state PV1

PVAR 20 PVAR 10

Legend:

Objects only, maybe Associations only Associations Objects Activated objects

PV0 allocated pre-allocated pre-allocated and associations

At the 1st step an empty provisioning variant is created and then filled with a copy of
the current interface dataset. This provisioning is still in state PV0 and can now be
modified.
At the 2nd step the provisioning variant and/or the current system dataset is
incrementally extended with new objects and associations. The integrity as defined for
state PV0 is secured by the system. The related objects in the current system dataset
are marked ’PV0-allocated’ which means that they are now part of a provisioning
variant in state PV0. This ’PV0-allocated’ information is needed to support additional
checks which must be performed to ensure the integrity of a provisioning variant in
state PV0.

At the 3rd step the provisioning variant is checked against the current system dataset
and other provisioning variants in state PV1. All associations defined in the
provisioning variant must be able to be fulfilled by the objects in the current system
dataset. This means either
• that the new objects for this interface have no association in the current system
dataset or in another provisioning variant in state PV1 or
• that the objects are already part of the current interface dataset (that is part of the
active provisioning) and its associations are unchanged or
• that the objects are already part of the current interface dataset but its associations
are changed within the interface (for example V5 user ports are re-associated to
other ISDN communication paths).
The related objects in the current system dataset are marked ’PV1-allocated’ which
means that they are now part of a provisioning variant in state PV1. This
’PV1-allocated’ information is needed to support additional checks which must be
performed to ensure the integrity of a provisioning variant in state PV1.
At the 4th step the actual switch over is performed. The object associations defined in
the provisioning variant are activated and added to the current interface dataset. The
associations of the old current interface dataset are still available as standby
provisioning variant for switch back purposes.

Scenario dual homing

Moving subscribers between interfaces is a mean for recovery of V5 interface failures.
Subscribers are associated to two (or more) interfaces and in case that the preferred
interface A fails, the subscribers are moved with few management actions to a backup
interface B. This is achieved by provisioning variants for both interfaces. The preferred
interface gets a provisioning variant without the subscribers (PVAR 20) and the backup
interface gets a provisioning variant with the subscribers which shall be protected
(PVAR 60). These provisioning variants can be created at any time and are used in
case of a failure. First the provisioning variant of the failed interface is activated to
free up the subscribers. The old provisioning dataset is now available as standby
provisioning variant of the failed interface A and must be set ’not available’.
Afterwards the provisioning variant of the backup interface is set to ’available’ and
then activated by a switch over to put the subscribers into service on V5 interface B. It
must be noted that a management connection must exist to the system for this recovery
procedure.
Re-provisioning scenario - moving subscribers between interfaces (Dual homing)

Current Dataset Provisioning Variant Current system Provisioning Variant Current Dataset
for interface A for interface A dataset for interface B for interface B

Generate prov. variant copy

PVAR 10 PVAR 20 PVAR 60 PVAR 50

time

Set prov. variant to ‘available’ for interface A

PVAR 10 PVAR 20 PVAR 60 PVAR 50

Prov. variant without Prov. variant with
subscribers to protect subscribers to protect

Switch variant of interface A via TL1 command

! Failure of interface A !

PVAR 20 PVAR 10 PVAR 60 PVAR 50

Set prov. variant to ‘unavailable’ for interface A

PVAR 20 PVAR 10 PVAR 60 PVAR 50

Set prov. variant to ‘available’ for interface B

PVAR 20 PVAR 10 PVAR 60 PVAR 50

Switch variant of interface B
via TL1 command or via
V5 protocol of interface B

PVAR 20 PVAR 10 PVAR 50 PVAR 60

Usage of re-provisioning in the host terminal

The hosted subscribers cannot take part in the host in V5 re-provisioning of local V5
interfaces. This is denied at the ENT-CRS-UPI command. It prohibits that a
provisioning variant is specified with a cross-connection involving a V5 user port
provisioned on a remote terminal interface.

Usage of re-provisioning in the remote terminal

Remote subscribers cannot take part in the remote terminal in V5 re-provisioning of
local V5 interfaces. This is denied at the ENT-CRS-UPI command. It prohibits that a
provisioning variant is specified with a cross-connection involving a V5 user port and a
host terminal interface.

Clock synchronization management in the AnyMedia Access

System
...................................................................................................................................................................................................................................

Synchronization modes
The supported synchronization modes depend on the COMDAC type used in the
AnyMedia ® Access System. The table below shows the possible synchronization modes
and the COMDAC types supporting them.

The synchronization mode ... ... can be used by the <COMDAC type> in the <shelf type>

COM501 in the COM503 in the COM520 in the COM521 in the COM503 in the
AnyMedia ® AnyMedia ® AnyMedia ® AnyMedia ® AnyMedia ®
ETSI V5 Shelf ETSI V5 Shelf LAG 4300 Shelf LAG 4300 Shelf LAG 1900 Shelf

Loop timed to E1 feeder or x x x x x

single station clock
External synchronization from - - x x x
DOTS E1

External synchronization from - - - x x

DCS
External synchronization from - - - x x
composite clock
Free running x x x x x

“Loop timed to IO_E1 interface or SC-CIU” mode

In this mode the COMDAC derives its synchronization from an E1 feeder input signal
or from a single 2048 kHz station clock signal connected to the station clock pin (SC)
of the office clock connector.
The station clock is provided via the CIU using the “Loop timed” mode. The station
clock input from the CIU is treated like an E1 feeder input.
Either of the reference signals can be the SC-CIU timing signal, so that it is possible to
protect the station clock with the recovered clock of a E1 feeder input. If the station
clock is used exclusively (in an unprotected mode!) then it is provisioned to both
primary and secondary reference source.
For protection purposes two synchronization reference sources specified as “primary”
and “secondary” can be selected via provisioning. The primary and secondary reference
signals can be selected from any physical E1 feeder inputs on any two IO_E1 packs, or
from two E1 feeder inputs on the same IO_E1 pack. The NB subsystem can continue
to derive timing from the reference inputs if one or both of the physical inputs is (are)
switched to the IO_E1 protection pack.
The COMDAC autonomously synchronizes to the source which provides a valid
synchronization first. In case of a synchronization source failure the system
autonomously switches to the other source if it provides a valid synchronization. Such
a protection switch is not revertive if the first source recovers.

If both sources fail then temporarily the mode “Free-running” is autonomously entered
by the NB subsystem. As soon as one synchronization source is available again the
system automatically switches back to “Loop timed”.
To use a digital office timing supply (DOTS) E1 synchronization signal in “Loop
timed” mode as synchronization reference source the E1 feeder which terminates the
signal has to be used. A pseudo leased line link service should be provisioned on the
related E1 feeder to get the appropriate E1 signal alarming from the NB subsystem.
Important! In this case the leased line link cannot be used for end user service due
to the specifications of the DOTS E1 synchronization signal.

“External synchronization from DOTS E1” mode

In mode “External synchronization from DOTS E1” the COMDAC derives its
synchronization from a 2048 kHz DOTS E1 signal connected to the external clock
pins of the office clock connectors.
When a digital office timing supply (DOTS) E1 clock is available it is recommended
to use this clock for synchronization of the NB subsystem in LAG Shelves. The TDM
COMDAC can be provisioned by GSI/EMS operation or TL1 command to be
externally timed to DOTS E1 interface.
The DOTS E1 clock is a framed, HDB3 coded 2048 kHz signal according to ITU-T
G.703 section 9. Its payload is “all 1”. There is no handling of timeslot 16. The
accuracy depends on the timing generator.

“External synchronization from DCS” mode

In mode “External synchronization from DCS” the COMDAC derives its
synchronization from a digital clock supply interface (64 kHz synchronization signal,
providing 8 kHz and 400 Hz phase information) connected to the external clock pins
of the office clock connector in the connector field.
This synchronization mode is required to be used for LPU508 applications, if the
LPU508 application pack(s) are not directly connected to a DCS signal via their
faceplate connector.

“External synchronization from composite clock” mode

In mode “External synchronization from composite clock” the COMDAC derives its
synchronization from a composite clock supply interface (64 kHz synchronization
signal, providing 8 kHz phase information) connected to the external clock pins of the
office clock connector in the connector field.

Protection in the “External synchronization from ...” modes

For protection purposes two fixed synchronization inputs are provided for all “External
synchronization from ...” modes. The COMDAC autonomously synchronizes to the
input which provides a valid synchronization signal first. In case of a synchronization

signal failure at the input used as timing reference, the system autonomously switches
to the other input if it provides a valid synchronization signal. Such a protection switch
is not revertive if the first synchronization signal recovers.
If both synchronization signals fail, then temporarily the mode “Free-running” is
autonomously entered by the NB subsystem. As soon as one synchronization signal is
available again the system automatically switches back to the prior mode.

“Free-running” mode
In free-running mode, the NB subsystem derives its timing from an internal oscillator
with an accuracy not worse than ± 20 parts per million (ppm) over full range of power
supply, temperature, and lifetime. The “Free-running” mode is intended only for
turn-up and fault conditions in cases where no timing reference is available.

Phase locked loop (PLL) alarm on COMDAC

The COMDAC provides a phase locked loop (PLL), which is able to synchronize to
the selected clock source in order to observe the timing reference source input. If the
PLL can not retain the synchronization to the valid input signal, a “PLL out-of-lock”
alarm is raised. As only the active clock source can be observed, no automatic
synchronization mode switch can take place, unless a “sync input failes” alarm is
detected at the same time.

Synchronization failure alarming

The following alarm indications are given by the system:
• Single synchronization source failure alarm
• Both synchronization sources failure alarm (free-running)
• Synchronization reference switch report.

Fault conditions
The AnyMedia ® Access System uses the following external criteria to determine if a
timing signal has failed:
For station clock (SC or SC-CIU):
• Loss of signal (LOS)
For “Loop timed to SC-CIU” mode:
• Loss of signal (LOS)
For “Loop timed to IO_E1 interface” mode:
• Loss of signal (LOS)
• Loss of frame (LOF)
• High bit error ratio (two consecutive seconds with BER 10-3)
• Alarm indication signal (AIS)

• The received E1 signal is lost due to failures or circuit pack removal

• The E1 signal is in a loopback state
For “External synchronization from DOTS E1” mode:
• Loss of signal (LOS)
• Loss of frame (LOF) (CRC4 checksum not supported for DOTS E1)
• Alarm indication signal (AIS)
For “External synchronization from DCS” mode:
• Loss of signal (LOS)
• Incorrect bipolar violations (BPV)
For “External synchronization from composite clock” mode:
• Loss of signal (LOS)
• Incorrect bipolar violations (BPV).

Clock performance criteria

The table below gives a brief overview of the clock accuracy in the different
hierarchies of the synchronization network.

Parameter Clock type Comment

± 1 ppm × 10-11 Type 1/PRC
-8
± 1.6 ppm × 10 Type 2/SSU
-6
± 4.6 ppm × 10 Type 3/SEC
± 50 ppm × 10 -6 Type III clock Accuracy for systems at the
border of the network

The figure below shows a typical network configuration for clock supply.

Protection switching
...................................................................................................................................................................................................................................

Introduction
Protection switching provides an automatic recovery mechanism when a fault is
detected in the AnyMedia ® Access System. In the AnyMedia ® LAG Shelf the
COMDAC, the IO_E1 and the RGP100 (RGP100 only used in the AnyMedia ® LAG
4300 Shelf) can be protected with a redundant pack, in the AnyMedia ® ETSI V5 Shelf
this applies for the COMDAC, the IO_HDLC and the IO_E1. Additionally in the
AnyMedia ® Mainshelf some APs that comply with special hardware requirements,
provide on demand application pack port protection switching.
Protection switching is based on the following principles:
• Protected elements are protected either 1:1 or 1:N
• Performed as non-revertive or revertive switching
– 1:1 is always non-revertive
– 1:N is always revertive.

Redundancy of protection
For 1:1 protection, one element serves as the active element (primary); the other serves
as a protection or standby element. For 1:N protection, one element serves as the
protection or standby element for all N active elements. If an active element fails, the
fault is detected and service is automatically protection switched to the protection
element.

Revertive versus non-revertive

In the AnyMedia ® Access System, protection can be revertive or non-revertive.
Revertive protection switching implies that the active and standby elements return to
their original configuration once the fault causing the protection switching has been
repaired. Non-revertive switching does not return the elements to their original
configuration. In non-revertive switching, the repaired element becomes the new
standby element.
Automatic and manual switching is possible for the revertive mode as well as for the
non-revertive mode.

Protected elements
Protection switching is provided for the following elements:
• COMDAC - automatic/manual (1:1)
• Synchronization sources - automatic/manual (1:1)
• V5.2 communication channels - automatic/manual (N:M)
• IO_HDLC packs - automatic/manual (1:1) (IO_HDLC packs are only used in the
AnyMedia ® ETSI V5 Shelf)
• IO_E1 packs - automatic/manual (1:N)
...................................................................................................................................................................................................................................
3-54 363-211-586
Issue 6, July 2007
OAM&P for narrowband services Protection switching

• Application pack ports on LPZ641 - manual (1:N)

• RGP100 - automatic (1:1 with load sharing) (RGP100 packs are only used in the
AnyMedia ® LAG 4300 Shelf).
• RGU100 - automatic (1:1) (RGU100 packs are only used in the AnyMedia ® LAG
4300 Shelf and in the AnyMedia ® ETSI V5 Shelf).
• RGU550 - automatic (1:1) (RGU550 packs are only used in the AnyMedia ® LAG
1900 Shelf and in the AnyMedia ® LAG 200 Shelf).

COMDAC protection
...................................................................................................................................................................................................................................

COMDAC protection
The COMDAC provides the core functions, including bandwidth management and
timeslot interchange function.
The system supports both duplex and simplex operation modes. Both active and
standby units are continuously monitored.
Duplex operation mode supports the following:
• Scheduled or manual side switching is hitless
• In-service software upgrade
• Side switch at hardware faults

Synchronization source protection using TDM COMDAC

Synchronization source protection

The protection switch of the synchronization source is automatically initiated upon
detection of faults of the active synchronization source or on demand. For more
information on clock synchronization see “Clock synchronization management in the
AnyMedia Access System” (p. 3-49).

V5.2 Communication channel protection

V5.2 CC protection
A V5.2 interface can be configured to support communication channel (CC) protection
in a multi-link configuration. The protection covers a single link fault in a V5.2
interface, that is it supports up to three standby timeslots which protect the active CCs.
In the event of a link fault the carried CCs are switched non-revertively to the standby
timeslots. This occurs without service impact. On recovery of the faulty link the former
CC timeslots are used as new standby timeslots.

V5 protection switching
In addition to the (active) communication channels, standby channels may be defined
which are used for protection of the active channels. If an error occurs on an active
channel, the protection protocol switches the traffic associated to this communication
channel to another (standby) channel which then becomes active.

IO_HDLC routing data

From the IO_HDLC point of view this means that frames in the ANE to LE direction
now have to be routed to the communication channel which has been selected by the
protection switch. The IO_HDLC has to be informed about this by updating the
IO_HDLC routing data.

IO_HDLC protection
...................................................................................................................................................................................................................................

IO_HDLC protection
The IO_HDLC (IO_HDLC packs are not used in the AnyMedia ® LAG 4300 Shelf)
provides the frame relay function of D-channel messages between the ISDN
subscribers connected to an AnyMedia ® Access System and a number of V5
communications channels and vice versa. Therefore the IO_HDLC has the same
importance for the AnyMedia ® Access System as the COMDAC.
The protection status refers to the pack protection switching state. The protection status
changes on system-driven protection switches (automatic and routine switches) as well
as on manual protection switches initiated by the operator.

Protection states
The following protection states are defined:
• Active
Indicates the pack which is currently responsible for carrying the traffic in a
protected configuration.
• Stand-by
Indicates the pack which is ready for taking over the service from the active pack
but is not carrying service because no protection switch has been requested.
If both IO_HDLC packs are faulty or both are in service state OOS, the protection
states remain unchanged.
Important! In a protected configuration (second IO_HDLC provisioned) protection
states are shown in all cases, regardless of the service states of the packs. This
means that protection states are shown even in service state OOS. If the standby
pack is deleted however, the protection status is not shown.

1:1 protection
For the IO_HDLC pack 1:1 protection applies where one IO_HDLC serves as a service
or active pack and the other serves as a standby pack. If an active pack fails, the fault
is detected and service is automatically ″protection switched″ to the standby pack. The
protection switching can also be requested on demand (manually).

Non-revertive protection
For the IO_HDLC non-revertive protection switching applies, which does not return
the system entities to their original configuration, that is the repaired pack becomes the
new standby pack.

Protection switching
Both IO_HDLC packs receive the same data, they have the same provisioning
information and they perform the same frame relay functions, but only data from the
active IO_HDLC is routed through the TSI. In case of a switch (for example for
protection), the only actions to take is a reconfiguration of the COMDAC’s TSIs.
An IO_HDLC protection switch may be initiated either manually via TL1 command or
automatically due to an IO_HDLC error detected by status monitoring and testing.

IO_E1 protection
...................................................................................................................................................................................................................................

IO_E1 protection
The IO_E1 pack protection switching provides an automatic recovery mechanism in
the AnyMedia ® Access System when an IO_E1 pack fault is detected. The system
supports both protected and unprotected IO_E1 operations. In case of protected
operations, the IO_E1(P) packs will run in an active and standby mode. The pack
protection is controlled by the active COMDAC.
In order to meet a short switch over time the protection pack (IO_E1P) is populated
with the provisioning information during pack initialization and kept up-to-date in case
of reconfigurations.

Protection status
The protection status refers to the pack protection state and indicates whether an
IO_E1 pack protection switch has been executed or not. It also indicates which kind of
protection switch (automatic or manual) has been executed.
The following protection states are defined:
• Active
Indicates the pack which is currently responsible for carrying the traffic in a
protected configuration.
• Standby
Indicating the pack which is currently responsible for providing the protection but
is not carrying service because no protection switch has been requested, that is it is
also applicable for a protection pack which is faulty or set to OOS.
• Automatic switch
Indicates a service pack where traffic has been switched over automatically to the
protection pack. The protection status is also shown in case the protection pack is
not able to carry the traffic due to a pack fault or moving it to OOS after the
automatic switch.
• Manual switch
Indicates a service pack where traffic has been switched over manually to the
protection pack. The protection status is also shown in case the protection pack is
not able to carry the traffic due to a pack fault or moving it to OOS.
Important! In a protected IO_E1 configuration (IO_E1P provisioned) the
protection status is shown in any case regardless of the service states of service- or
protection pack. This means that also in service state OOS the protection status is
shown. If the IO_E1P is deleted however (unprotected IO_E1 configuration) the
protection status is not applicable anymore.

1:N protection
The AnyMedia ® Access System provides 1:N protection switching, where N can be 1
to 4 service IO_E1 packs protected by one protection pack IO_E1P.

An IO_E1 protection switch may be initiated either manually via TL1 command or
automatically due to an IO_E1 pack fault detected by status monitoring and testing.

Revertive protection
The IO_E1 pack protection switching is revertive, that means the traffic is switched
back from the IO_E1P to the service IO_E1 pack once the fault causing the protection
switch disappears. Revertive protection switching is only applicable for automatic
protection switches.

Protection switching
The pack protection is achieved by switching the four E1s from an active IO_E1 pack
to the IO_E1P pack. The pack protection is controlled by the active COMDAC. The
IO_E1 pack processor is not involved in the protection switching operation of the
packs, since pack protection must work even if the pack processor fails.
Important! For protection switching of the IO_E1 packs only the protection pack
IO_E1P must be an IO_E1 pack with apparatus code FAC500B.

AP port protection
...................................................................................................................................................................................................................................

AP port protection
By using the metallic test bus architecture of the backplane it is possible to provide a
1:N application pack port protection. The basic concept is to switch a metallic test path
from the port to be protected via the general purpose bus on the backplane, via the
CIU which inter-connects the outward bus with the inward bus and then again via the
general purpose bus to another application pack port which provides the protection
circuit.
Important! For support of the 1:N application pack port protection a CIU DTP500
with ICC version S2:8 or greater is required.

Metallic protection path

To support 1:N protection for application pack ports the following hardware
requirements apply:
• The application pack which serves the port to be protected must support at least
outward metallic test access and the capability to isolate the port circuitry from the
subscriber loop and the test-in test bus.
• The application pack which serves the port providing protection must support at
least inward metallic test access and the capability to isolate the related subscriber
line from the test-out bus.
• The application pack which serves the port providing protection must support at
least the same port capabilities like the application pack which serves the port to be
protected, for example balance network parameters, feeding current, signalling
capabilities etc.
• The CIU must be equipped to bridge the test-in and test-out bus from the general
purpose bus.
• Metallic line testing in the same shelf is mutual exclusive to an active 1:N
application pack port protection switch as both need the same general purpose bus
of the shelf.
The 1:N protection for application pack ports supports only manual, that is, on operator
demand, protection switching. Automatic protection switching is not supported. It is
solely on operators discretion whether to switch a protection for a specific port,
probably based on test results from former metallic line tests, circuit tests or due to
subscriber complaints.
Metallic protection path for application pack port 1:N protection

The schematics shown in the figure above are conceptual only. The real relay positions
on the application packs may differ.

Provisioning of the protection port

The system supports exactly one protection port per mainshelf. To define a protection
port a new line termination type “Backup Line” is introduced. This line termination is
provisioned on the drop which is used as protection port.
The “Backup Line” is only an entity to define the protection port. It has no
interrelations to the network interfaces of the system and so no further service
provisioning like cross-connections to network interfaces are applicable.

Manual protection switching

The manual protection switch is initiated via TL1 command specifying the port to be
protected. The system automatically selects the appropriate backup line within the same
shelf and therefore the protection port must not be specified by the operator. A
protection switching request is rejected if
• no backup line is provisioned in the same shelf as the port to be protected
• the general purpose bus in the same shelf is already allocated either by a metallic
line test or a protection switch is already active
• blocking of a V5 switched service is not granted by the local exchange.
The protection switch request is released via TL1 command specifying the port which
is currently protected. No active call is disrupted by releasing a protection switch in
normal mode while the forced mode unconditionally releases the protection switch.

Test capabilities and protection switch

While a protection switch request is active all metallic line test capabilities of the
system are not supported anymore due to the usage of the general purpose bus for the
protection switch. Beside that also integrated test capabilities are affected by the
protection switching:
• Send howler tone and test ringing signal
Both tests are not directly affected by a protection switch request in the same shelf
as they do not use any general purpose bus resources of the backplane or the
application packs. So these tests are fully supported without any changes for all
POTS ports not involved in a protection switch in the system.
• Test circuit
The integrated circuit test of application packs is using the test relay resources on
the application pack for its self-tests. For this reason an integrated circuit test on
any port of the involved application packs (protected as well as protecting) is
denied.
Important! Testing of the protection drop is not supported even if no protection
switch request is active. To test the protection drop the backup line entity must be
temporarily deleted. Please note that this restriction is not relevant for operation as
the protection drop is not connected to a subscriber line anyway.

Supported application pack types

1:N application pack port protection is supported by the application pack type LPZ641
for both the port to be protected and the port providing protection. 1:N application
pack port protection is only supported in the AnyMedia ® Mainshelf.

Ringing protection in the AnyMedia ® LAG 4300 Shelf

Overview
For the reliability ringing protection is recommended. The AnyMedia ® LAG 4300
Shelf provides two ringing busses, which may be fed by either internal or external
ringing sources. Both ringing busses are accessible by each AP slot. The POTS APs in
each slot can use either ringing bus. The actual usage of the ringing bus depends on
the number of available ringing sources/busses, which is dependent on
• number of provisioned ringing sources
• ringing source failures.

Load sharing mode with two RGP100 packs

If two ringing sources are available the two ringing busses will be loaded nearly
equally in a fully equipped AnyMedia ® LAG 4300 Shelf (POTS APs only). About half
of the POTS APs within the AnyMedia ® LAG 4300 Shelf use the ringing voltage from
ringing bus 0, while the other half of the POTS APs use the ringing voltage from
ringing bus 1.
By default the ringing bus 0 is primary ringing bus for the POTS APs in slot 2, 3, 6, 7,
10, 11, 14, 15, 18, 19, 22, 23, 25, 26, 29, 30, 33, 34, 37, 38, 41 and 42. The ringing
bus 1 is the primary ringing bus for the POTS APs in all other slots (see the
figures below). This default load sharing mode (primary bus) is chosen to ensure, that
a power supply failure for a ringing generator pack (RGP100) keeps the number of
affected POTS APs at a minimum, if internal ringing is used. If one ringing voltage on
one of the two ringing busses fails, all POTS APs use the available ringing bus. If both
ringing sources are available again, the POTS APs, which use the secondary ringing
bus, make a reverting switch to their primary ringing bus.
The following figure shows the LAG 4300 Shelf slot numbering and primary ringing
bus for each slot in load sharing mode with two RGP100 packs.

Cabinet Distribution Panel

Connector field

RB1
RB0

RB1
spare

RB1
(RGP0) RB0
RB0
RB0
RB1
RB1
RB0
RB0
RB1
RB1
RB0
RB0
RB1
RB1
RB0
RB0
I/O

4 5
COMDAC
COMDAC

(RGP1)
CIU
I/O
I/O

AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
2 3

AP
AP
AP
AP
I/O
I/O

P 1 1 0 1 25 26 2728 29 30 3132 3334 3536 37 38 39 40 41 42 43

Fan Unit

RB1
RB1
RB0

RB1
RB0
RB0
RB0
RB1
RB1
RB0
RB0
RB1
RB1
RB0
RB0
RB1
RB1
RB0
RB0
RB1
RB1
RB0
RB0
RB1
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
1 2 3 4 5 6 7 8 9 10 1112 13 14 15 16 17 18 19 20 21 22 23 24

Load sharing mode with mixed ringing sources

This load sharing mode can be used together with an RGU100 and one RGP100B or
external ringer, where the RGU100 feeds ringing bus 0 (from any AP slot) and the
ringing bus 1 is fed by an RGP100 in AP slot 42/43 or an external ringer.
The RGU100 feeds ringing bus 0 only due to backplane pin usage and allows ringing
protection.
The following figure shows the LAG 4300 Shelf providing load sharing mode with
mixed ringing sources.

Cabinet Distribution Panel

Connector field

RB0

RB1
spare

RB0

RB1
RB1

RB0
RB0
AP RGU RB1
RB1
RB0
RB0
RB1
RB1
RB0
RB0
RB1
RB1
RB0
RB0
I/O

4 5
COMDAC
COMDAC

RGP
CIU
I/O
I/O

AP
AP
AP
AP
AP
AP
AP
AP

AP
AP
AP
AP
AP
AP
AP
AP
2 3

AP
AP
I/O
I/O

P 1 1 0 1 25 26 27 28 29 30 3132 3334 35 36 37 38 39 40 41 42 43

Fan Unit

RB1
RB1
RB0
RB0
RB1
RB1
RB0
RB0
RB1
RB1
RB0
RB0
RB1
RB1
RB0
RB0

RB0
RB0
RB1
RB1
RB0
RB0
RB1
RB1
AP RGU
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP

AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24

Ringing configurations
The AnyMedia ® LAG 4300 Shelf supports the following ringing configurations:
• Unprotected ringing configurations:
– One RGP100
– One RGU100
– One external ringer
• Protected ringing configurations:
– Two RGP100
– Two RGU100
– Two external ringers
– One RGU100 and one RGP100
– One RGU100 and one external ringer
– One RGP100 and one external ringer.

Internal ringer protection

The internal ringing protection is provided as follows:
• By two RGP100
In this configuration there is no explicit ringing protection provisioned. The ringing
protection is implicit provided by provisioning of two ringers. If only one ringer is
provisioned, it is assumed that only one ringing bus is used. All POTS APs are
connected to that ringing bus. If two ringers are provisioned it is assumed that both
ringing busses are used. All POTS APs are connected to their primary ringing bus.
An RGP100 can’t be provisioned, if an external ringer entity is already provisioned
for the ringing bus in question and vice versa. The related TL1 command is
rejected.
Each RGP100 connects its ringing voltage output to one ringing bus. The dual slot
RGP100 in slot positions 40 and 41 drives ringing bus 0, while the dual slot
RGP100 in slot positions 42 and 43 drives ringing bus 1. Two RGP100 provide
protection in active/active mode.
In case of a ringing source failure, the POTS AP takes its ringing voltage from the
other ringing bus, if it is available. In case of a failure one RGP100 is able to carry
the full ringing load, that is the individual RGP100 load has to be engineered less
than 50% of the available ringing power from the RGP100 (100W).
• By one RGU100 and one RGP100 or external ringer
This configuration is mainly intended to support a migration from a protected
RGP100 configuration to a protected RGU100 configuration. In this configuration
one RGU100 is installed in any AP slot and feeds ringing bus 0. Ringing bus 1 is
fed by an RGP100 in AP slot 43 or by an external ringer. No RGP100 must be
equipped in AP slot 41 or taken into service. This configuration also allows
protected RGU100, supporting ringing bus 0.
In case of a ringing source failure, the RGU100 and the RGP100 or the external
ringer are able to carry the full ringing load.
• By two RGU100 in controlled mode
Two RGU100 provide ringer pack protection utilizing ringing bus 0 only. All POTS
APs are connected to that ringing bus. The COMDAC entirely controls the
RGU100 protection switch and ensures, that only one RGU100 is feeding ringing
bus 0. The active RGU100 is feeding ringing bus 0, whereas the standby RGU100
will be isolated from this ringing bus. This means, two RGU100 provide protection
in an active/standby mode.
The LAG 4300 Shelf supports the RGU100 in any slot. For RGU100 pack
non-revertive protection switching applies, which does not return the system entities
to their original configuration, that is, the repaired pack becomes the new standby
pack.
If the active RGU100 fails, the COMDAC initiates a protection switch to the
standby RGU. The protection switching can also be requested on demand
(manually). The COMDAC disconnects the former active RGU from ringing bus 0
and monitors the bus for ringing voltage. If there is none, the COMDAC closes the
output relay of the standby RGU. Thus a collision on the bus is avoided.

External ringer protection

External ringing is provided by external bulk ringer(s). The bulk ringer(s) is connected
via an optional ringer filter unit to one or both ringing busses. The protection is
provided external by the bulk ringers as well. The protection is provided by external
ringer by use of one or both ringing busses. It is recommended, that the number of
used ringing busses is aligned with the number of provisioned ringers. If the external
ringers are connected to both ringing busses, the load sharing mode applies.

Ringing in the AnyMedia ® LAG 1900 Shelf

Separate ringing busses

In the AnyMedia ® LAG 1900 Shelf ringing bus 1 is grounded due to safety issues.
Ringing bus 0 is divided into two partitions A and B. The ringing bus 0-A serves the
AP slots 1, 4, 5, 8, 9, 12 and 13 while the ringing bus 0-B serves AP slots 2, 3, 6, 7,
10, 11 and 14. Therefore both partitions must be connected to a ringing source if
ringing service is required in all application pack slots.
The following figure shows the LAG 1900 Shelf slot numbering and the serving
ringing bus for each slot.

GREEN- RED-
ACTIVE FAULT Fan unit and air outlet
IO-E1P IO-E1 RGU RGU PFU PFU
IO_E1P

IO_E1
IO_E1

RGU

PFU
PFU

0 1 2 0 1 0 1
RB0-A
RB0-B
RB0-B
RB0-A
RB0-A
RB0-B
RB0-B
RB0-A
RB0-A
RB0-B
RB0-B
RB0-A
RB0-A
RB0-B
IPFM or AP
IPFM or AP
AFM or AP
AFM or AP
COMDAC

COMDAC
CIU

AP
AP
AP
AP
AP
AP
AP
AP
AP
AP

1 2 1 1 2 03 04 05 06 07 08 09 10 11 12 13 14

COM-1COM-2 CIU AP-1 AP-2 AP-3 AP-4 AP-5 AP-6 AP-7 AP-8 AP-9 AP-10 AP-11 AP-12 AP-13 AP-14

Cable trough and air inlet (baffle)

LAG 1900 Shelf configuration using RGU500/510 packs

For this configuration no jumper has to be equipped on the backplane. Ringing bus 0 is
operated in the split mode. Both external ringing generator entities need to be
provisioned. There is no ringing source protection within the AnyMedia ® LAG 1900
Shelf. If one of the ringing generator units RGU500/510 fails then half of the
application packs has no access to a ringing signal anymore.

LAG 1900 Shelf configuration using external ringing generator

For this configuration two jumpers have to be equipped on the backplane, one for
connecting both partitions of ringing bus 0 and the other for connecting the external
ringing to the internal busses. Ringing bus 0 is operated in the interconnected mode.
Both external ringing generator entities need to be provisioned. There is no ringing
source protection within the AnyMedia ® LAG 1900 Shelf. If protection is needed then
the protection must be established within the external ringing generator.

Ringing protection by using RGU550 packs

The AnyMedia ® LAG 1900 Shelf using RGU550 packs supports both protected and
unprotected configurations, that is, the RGU550 pack can be 1:1 protected or there is
no pack protection. The active RGU550 feeds both ringing bus 0 partitions. In
protected configuration, the RGU550 packs are running in an active/standby mode and
are configured with the same data (must have the identical jumper-settings).
In a protected configuration the protection is controlled by two RGU550 by their own
and it is ensured, that only one RGU550 is active. Although ringing bus 0 is not
operated in the split mode, both partitions are monitored by COMDAC for ringing
voltage. The active RGU550 is feeding, whereas the standby RGU is isolated from this
ringing bus.
The POTS APs are instructed by the COMDAC to use the ringing bus 0 only. If the
active RGU550 fails, a protection switch to the standby RGU550 occurs. The
protection switch is non-revertive and the system entities do not return to their original
configuration, that is, the repaired RGU pack becomes the new standby pack.

Ringing protection in the AnyMedia ® ETSI V5 Shelf

Overview
For the reliability ringing protection is recommended. The AnyMedia ® ETSI V5 Shelf
configuration supports provisioning of
• internal ringing provided by up to two internal ringing generator unit(s) RGU100 in
“controlled” mode
• external ringing provided by
– up to two internal ringing generator unit(s) RGU100 in “uncontrolled” mode
– external ringing source.

Internal ringer protection

The internal ringing protection is provided by two RGU100 in “controlled” mode
Two RGU100 provide ringer pack protection utilizing ringing bus 0 only. All POTS
APs are connected to that ringing bus. The COMDAC entirely controls the RGU100
protection switch and ensures, that only one RGU100 is feeding ringing bus 0. The
active RGU100 is feeding ringing bus 0, whereas the standby RGU100 will be isolated
from this ringing bus. This means, two RGU100 provide protection in an
active/standby mode.
The AnyMedia ® ETSI V5 Shelf supports the RGU100 in any slot. For RGU100 pack
non-revertive protection switching applies, which does not return the system entities to
their original configuration, that is, the repaired pack becomes the new standby pack.
If the active RGU100 fails, the COMDAC initiates a protection switch to the standby
RGU. The protection switching can also be requested on demand (manually). The
COMDAC disconnects the former active RGU from ringing bus 0 and monitors the
bus for ringing voltage. If there is none, the COMDAC closes the output relay of the
standby RGU. Thus a collision on the bus is avoided.

External ringer protection

For external ringing two scenarios apply:
• external ringing provided by up to two internal ringing generator unit(s) RGU100
in “uncontrolled” mode
The AnyMedia ® ETSI V5 Shelf using RGU100 packs supports both protected and
unprotected configurations, that is, the RGU100 pack can be 1:1 protected or there
is no pack protection. The active RGU100 feeds the ringing bus 0. In protected
configuration, the RGU100 packs are running in an active/standby mode and are
configured with the same data (must have the identical jumper-settings).
In a protected configuration the protection is controlled by two RGU100 by their
own and it is ensured, that only one RGU100 is active. Ringing bus 0 is monitored
by COMDAC for ringing voltage. The active RGU100 is feeding, whereas the

standby RGU is isolated from this ringing bus.

If the active RGU100 fails, a protection switch to the standby RGU100 occurs. The
protection switch is non-revertive and the system entities do not return to their
original configuration, that is, the repaired RGU pack becomes the new standby
pack.
• external ringing provided by external ringing source
If external ringing is provided by external ringing generator(s), the external ringing
generator(s) is connected via an optional ringer filter unit to the ringing bus. If
protection is needed then the protection must be established within the external
ringing generator.

Protection switch characteristics

Characteristics
The following table lists how each protected pack or element in the system is
protected, its protection switching behavior, and whether or not it can be switched on
demand.

Protected pack or Protection Automatic Switch mode Manual

element mode switch switch
COMDAC (Core) 1:1 (optional) Yes Non-revertive Yes ( 1)
Synchronization Source 1:1 (optional) Yes Non-revertive Yes
(E1/SC) ()2

V5.2 CC POTS-only N: M Yes Non-revertive Yes

mode N =1 - 2 ( 3)
M = 1 - 16
(optional)
V5.2 CC POTS/ISDN N: M Yes Non-revertive Yes
mixed mode N =1 - 3 ( 3)
M = 1 - 48
(optional)
4
IO_HDLC ( ) 1:1 (optional) Yes Non-revertive Yes
IO_E1 1: N Yes Revertive Yes
(1 ≤ N ≤ 4)
(optional)
Application pack ports 1: N No Revertive Yes
N = number of
application pack
ports
(optional)
RGP100 (5) 1:1 with load Yes Revertive No
sharing
RGU100 (6) 1:1 (optional) Yes Non-revertive Yes
RGU550 ( 7) 1:1 (optional) Yes Non-revertive Yes ( 8)

Notes:
1. Besides manual switching the routine side switching capability is provided
2. After system recovery an attempt is made to go back to the primary source
3. Only for protection group 2
4. Only used in the AnyMedia ® ETSI V5 Shelf
5. Only used in the AnyMedia ® LAG 4300 Shelf
...................................................................................................................................................................................................................................
363-211-586 3-75
Issue 6, July 2007
OAM&P for narrowband services Protection switch characteristics

6. Only used in the AnyMedia ® LAG 4300 Shelf and in the AnyMedia ® ETSI V5 Shelf
7. Only used in the AnyMedia ® LAG 1900 Shelf
8. Switching can be initiated implicitly by unplugging the active RGU550

Inventory management

Purpose
Inventory management is the system activity of collecting, updating, and reporting data
on system equipment and system status.
The following sections describe the inventory management capabilities.

Contents

Retrievable inventory items 3-78

System identification name [target identifier (TID)] 3-80
Internet protocol (IP) address 3-81
Reportable database changes 3-82
NTU inventory data 3-83

Retrievable inventory items

Inventory requirements define data stored on each pack. These data are used to identify
the hardware as well as the firmware.
Retrievable pack inventory items include the following:
• TYPE - a mnemonic name that identifies the kind of equipment (for example
POTS)
• APP - the apparatus code that uniquely identifies the equipment function (for
example LPP100, LPU112)
• ICC - the interchangeability code stored in the form of Sm-n, where m is the issue
number and n is the series number
• CLEI - the common language equipment identifier is a 10-character code
identifying each pack type
• ECI - the equipment catalog item is a 6-character code identifying each pack type.
This code corresponds to the bar coded label on the faceplate of the pack and is
uniquely equivalent to the CLEI. The ECI code is not applicable for IO_E1,
IO_HDLC and CIU.
• SN - the serial number is a 12-character code that uniquely identifies each pack.
The SN includes the date and place of manufacture.

Software identifiers
Software identifiers (for the COMDAC only on the initial release) are as follows:
• PVRSN - the program version of the software currently stored in the pack
• PCDE - the program code (J code) of the software currently stored in the pack.

Hardware identifiers
Hardware identifiers (for the AnyMedia ® Mainshelf backplane only) are as follows:
• TYPE - the string identifier for the backplane
• PVRSN - the backplane version.
Hardware identifiers retrievable for the IO_E1 packs are as follows:
• TYPE - the impedance of the E1 link termination which is set by jumpers on the
IO_E1 pack

Slot state information

Primary and secondary slot state information is also retrievable for each pack.
Primary slot state - the valid values are as follows:
• IS - In service
• OOS - Out of service.

Secondary slot state only exists for primary service state OOS - the valid values are as
follows:
• SWDL - Software download
• FLT - Fault
• INIT - Initialization including diagnostics
• UEQ - Unequipped
• FEF - Family of equipment failed.

Physical data label - Pack labels

On the front of each pack is an electronically scannable bar code and a human
readable inventory data label. The human-readable component contains the common
language equipment identifier code (CLEI), apparatus code (APP), entity type (TYPE),
interchangeability code (ICC), and serial number (SN). The bar code scannable
component of the label contains the equipment catalog item code (ECI). The label does
not contain the ECI code for IO_E1, IO_HDLC and CIU.

System identification name [target identifier (TID)]

TID
The target identifier (TID) is the first parameter in the parameter block of a TL1
command which can be given by the operator on the GSI/EMS (for example
system00). The TID input parameter has the following characteristics:
• The TID must be the same value as the system identifier (SID) code assigned to
the AnyMedia ® Access System. The TID/SID value is normally provisioned during
system turn-up.
• The TID/SID is optional, and the AnyMedia ® Access System accepts an input
command that does not contain a TID. If the TID is not given, or its value is either
different from the AnyMedia ® Access System SID string or syntactically incorrect,
the system uses the AnyMedia ® Access System SID value as part of the error
response.
• The TID/SID can have up to 20 alphanumeric characters, including the ″#″ and the
″_″ characters.
• The TID/SID is case sensitive.
Important! The SID should have the same value as the site ID entered for the
AFM in a mixed narrowband/ATM xDSL configuration. The provisioning of the
parameter site ID is described in the Commands and Procedures for ATM xDSL
Services.

Internet protocol (IP) address

IP address
The IP address is stored in NVDS. This means next time the operator resets or reboots
the COMDAC, the network will come up automatically, unless the operator runs an
INIT-SYS or clears the NVDS again. In the latter case the operator has to reprovision
the IP address from the serial CIT port.
For a COMDAC duplex configuration, after the repainting of NVDS has taken place,
the mate COMDAC will have the same IP address as the active one after a side
switch. This means the operator is still able to connect to the system with the same IP
address.

Reportable database changes

Autonomous reports
Autonomous notification is provided when changes occur to the inventory database as
a result of the execution of provisioning commands, state changes, or changes in the
physical inventory.

NTU inventory data

Overview
The [S]HDSL network termination unit (NTU) is not part of the AnyMedia ® Access
System.
The NTU is able to provide the following inventory data:
• Product name
• HW configuration
• SW version
• Serial number
• Manufacture date.
This information is stored on the COMDAC. Every time an HDSL interface is newly
synchronized, this information is fetched from the NTU.
The information is provided by a TL1 command on the equipment layer to the
GSI/EMS.

Managed NTU inventory data

The managed NTUs provide the following inventory data:
• Model identifier
• Hardware version
• Firmware version.
The managed NTU inventory is retrieved through the ISDN port using the TL1
command RTRV-EXTEQPT.

Fault management

Purpose
Fault management is the system activity for operations that cover the following:
• Maintenance
• Alarms and events
• Alarm signaling path
• Testing.
The following sections describe the fault management capabilities.

Contents

Maintenance 3-86
Alarms and events 3-90
Common alarms 3-92
Equipment alarms 3-93
Facility alarms (2-Mbps transmission) 3-99
Host and remote terminal alarms 3-100
Alarm signaling paths 3-101
Miscellaneous alarm inputs 3-102
Alarm output relays 3-106
Local alarm and status indicators 3-107
Alarm reporting and retrieval via TL1 3-108
Built-in self tests 3-109
Testing possibilities 3-113
On-demand tests using integrated capabilities 3-114
Detection test of a test termination 3-125
Draw and break dial tone test 3-126
DTMF, pulse character or register recall (hook flash) test 3-127
Sending of test tone for POTS CPE 3-128
Ringing test for POTS CPE 3-129
CRC tests for ISDN application packs 3-130
Sending a single pulse 3-131

NT1 detection test 3-132

Noise measurement on a subscriber line 3-133
Loop current measurement 3-134
Tone measurement 3-135
Howler tone on demand on POTS drops in reduced battery state 3-136
Quick line test 3-137
Talk to subscriber test session 3-140
Loopbacks 3-141
Loopbacks at the E1 link side 3-142
Loopbacks at the U interface (subscriber side) 3-143
Loopbacks at the HDSL interface 3-146
Loopbacks at the SHDSL port 3-151
BER testing with external loopback devices 3-154
Subscriber line test via external test head 3-155

Maintenance
...................................................................................................................................................................................................................................

Definition
Maintenance is the set of activities performed automatically and/or manually to ensure
continued operation and to minimize service degradation. This section addresses the
following:
• Maintenance objectives
• Several different maintenance strategies.
Accurate maintenance is based on the assumption that the system is properly installed
and provisioned.

Maintenance objectives
Maintenance provides mechanisms to do the following:
• Detect all faults in the system
• Isolate faults accurately for maintenance personnel
• Report faults as soon as they occur with sufficient supporting information
• Recover from faults via automatic protection actions to minimize service
degradation and/or via field dispatch
• Support proactive maintenance to discover faults before they can affect service
• Provide maximum test coverage of protection units.

Detection strategy
Detection is the act of determining that a problem exists in the system. A problem can
be either permanent or transient. In the system, the detection of these kinds of
problems is accomplished in two ways:
• Unit fault detection
The first and most prevalent way to detect a problem is unit fault detection. Unit
fault detection has been designed into most replaceable units in the system and
allows the units to determine their own health, determine the quality of their inputs,
and report any malfunctions. Unit fault detection is used mostly for permanent
faults, which are reported as alarms. See “Alarms and events” (p. 3-90) for details.
• Performance management
The second way to detect a problem is performance management (PM). PM
monitors the quality of the communications (bit error rate, protocol violations, etc.)
between network elements. Some transient conditions are immediately reported as
events and some are accumulated until they exceed a predetermined threshold, then
a threshold crossing alert (TCA) is reported. See “Performance management”
(p. 3-157) for details.
Both methods of fault detection are used throughout the system to ensure complete
system coverage. Both methods are done continuously and do not interrupt service or
limit the ability to provide service.

Isolation strategy
Isolation is the process of analyzing system alarms, TCAs, events, etc., that have been
detected and reported to determine the root cause of the detected conditions in the
system.
The goal is to isolate the fault to a replaceable unit. The exact location and replaceable
unit are not necessarily known at the time when the fault is detected. Sometimes
additional analysis is needed when a detected event is transient or manifests itself with
other sympathetic conditions. For example the removal of an AP causes the loss of
communications (sympathetic condition) between the COMDAC and the AP.
The isolation of transient errors such as TCAs requires an external operations system to
perform analysis of additional data.

Transient fault isolation strategy

For fault isolation the COMDAC implements a transient fault count for each pack
which prevents the system to initiate endless restart attempts. After four faults of a
pack in a specified time frame the system does not retry to restart it and the pack
enters a stable fault state. In this state a retry to restart the pack is only possible with
operator interaction either by a removal and reinsertion of the pack or via TL1
command.

Reporting strategy
Reporting is the process of communicating the detected system faults to a central office
site (CO) for field dispatch or further analysis. All system alarms and events are
reported across all OAM&P interfaces.
In addition alarms are indicated by Light Emitting Diodes (LEDs) and alarm output
relays.
All system faults are reported autonomously as they occur. Some system faults are
discovered and reported during routine system operation and surveillance. All single
faults are reported within a few seconds after they have been detected.

Alarm classification and inhibiting

Some pre-processing of data is done during the reporting phase. Time stamps are added
to aid in correlating other events and alarms. Alarms are classified by severity
(operator provisionable) to aid in determining urgency. The system can be instructed
via an external request
• to enter an alarm-inhibiting mode in which autonomous alarm messages for all
system entities are prevented from being transmitted
• to cut off the alarm output relays.
Autonomous alarm message inhibiting and resuming features are useful to handle
special maintenance, service activation, or system reconfiguration situations.

Recovery strategy
Recovery is the action taken to prevent a detected fault from continuing to affect
service. Hardware fault recovery mechanisms include
• the automatic protection action taken to minimize service degradation and/or
• manual service recovery (maintenance personnel).
When the system detects a pack fault or pack removal condition, it performs a
protection switch, if the implicated pack is protected. If the pack is not protected, the
system attempts to recover the failed pack with a hard reset of the implicated pack.
The system also automatically initiates its recovery when power is restored. The
system returns all services to the state prior to power loss within a few minutes after
the return of valid and stable power.

Shared equipment strategy

Shared equipment is equipment which is used by the narrowband and ATM xDSL
domain of the AnyMedia ® Access System. The recovery of shared equipment is
different from the recovery of equipment dedicated to only one domain. This
equipment enters its operational state right after power up without any activation
trigger or configuration data from the COMDAC or AFM. It allows for each domain
the deactivation of the own part of the shared equipment which is dedicated to that
domain. A deactivation which will interfere the other domain is not possible. A partly
failed shared equipment, with faults related only to one domain, is marked faulty only
in this domain whereas in the other domain it is fault free.

Proactive maintenance strategy

Proactive maintenance is the ability to predict or discover a system fault before it
becomes service affecting. The system provides the capability to
• monitor both active and standby equipment continuously
• exercise standby equipment routinely
in order to discover faults before they can affect service.
In duplex COMDAC operation, some improvement in system downtime margin can be
expected with routine off-line diagnostics that are performed for the COMDAC, as
well as routine side switching performed for the COMDAC:
• In a duplex configuration, the active COMDAC periodically triggers the execution
of diagnostics on the standby (off-line) COMDAC. This assures proper operation of
the standby COMDAC prior to a side switch.
• One hour before the scheduled side switch, the active COMDAC resets the standby
COMDAC. Self-test routines verify the function of the standby COMDAC. In case
of a detected self-test failure, the scheduled side switch is automatically inhibited
and an alarm is raised for the standby COMDAC.
• If scheduled side switching is disabled, the active COMDAC triggers the off-line
diagnostics on the standby COMDAC every month.

The system also provides the capability to allow maintenance activity to monitor the
integrity of transmission paths. These maintenance activities include performing
channel/drop tests, E1 loopbacks, manual switch protection etc.

Alarms and events

Monitoring capabilities
The surveillance capabilities of the AnyMedia ® Access System consist of equipment
and facility (2 Mbps) monitoring. During normal operation, the system provides
continuous or periodic surveillance through the following non-invasive diagnostics:
• Active and/or standby units
• E1 signal inputs
• Equipment power
• Environmental conditions.

Monitoring results
The results of these monitoring activities generate alarms, fault conditions and/or
transient conditions reports.

Alarm classification
Detected alarms are classified as one of the following:
• Common alarms
• Equipment alarms
• Facility alarms (2 Mbps transmission)
• External alarm inputs (miscellaneous alarms).

Alarm severities
For each alarm one of the following alarm severities is defined:
• CR Critical
• MJ Major
• MN Minor.
The alarm severities are predefined by the manufacturer and if necessary can be
reassigned by the operator. The alarm severity levels are indicated by LEDs on the
COMDAC faceplate.

Additional attributes
The alarms are divided into:
• NE Near-end alarms
• FE Far-end alarms.
The additional alarm attributes are indicated by LEDs on the COMDAC faceplate.

Service affecting (SA)

Refers to a condition affecting the service (for example telephony) at the time it is
detected.
...................................................................................................................................................................................................................................
3-90 363-211-586
Issue 6, July 2007
OAM&P for narrowband services Alarms and events

Non-service affecting (NSA)

Refers to a condition not affecting the service (for example telephony) at the time it is
detected.

Common alarms
...................................................................................................................................................................................................................................

Common alarms fault conditions

The common alarms include the following fault conditions:
• NVDS mismatch in duplex configuration
• System is free-running if both synchronization sources have failed.

Equipment alarms
...................................................................................................................................................................................................................................

Equipment alarms fault conditions

The equipment alarms include the following general fault conditions:
• Pack faults, missing, not responding to poll or incompatible
• Data link faults
• Input power fault
• Fault to update system data and programs
• System memory faults.

POTS AP fault conditions

POTS AP faults are fault conditions which influence all Z ports on POTS AP.
Examples for POTS AP faults are:
• Pack removal
• Pack not responding to poll
• Power fault
• Front cable not plugged
• Hardware errors.

Z port circuit fault conditions

Z port circuit faults are fault conditions which influence the whole POTS AP. Checks
for circuit faults will be performed during BIST or on-demand. See the section
“Built-in self tests” (p. 3-109) for details.
Examples for Z port (circuit) faults are:
• Subscriber feeding circuitry error
• On/Off-hook detection circuitry error
• Ringing signal injection circuitry error
• PPM signal injection circuitry error
• Ring-Trip detection circuitry error
• AC transmission circuitry error
• Z port fuse blown.

ISDN AP fault conditions

ISDN AP faults are fault conditions which influence all U ports on an ISDN AP.
Examples of ISDN AP faults are:
• Pack removal
• Pack not responding to poll
• Power fault

• Front cable not plugged

• Hardware errors.

U interface fault conditions

U interface faults are fault conditions which influence only a single U port. The fault
can be on the U port or at the U drop. See the section “Built-in self tests” (p. 3-109)
for details.
Examples of U port faults are:
• Echo canceller defect
• Feeding circuit defect
• Loopback 1 not successfully executed.

Ambiguous fault conditions

Examples of ambiguous faults (not assignable to U drop or U port) are:
• Power limit overflow on U interface
This fault can be caused by a port fault or a short circuit between a- and b-wire.
After detection of a power overflow at the U interface the feeding voltage is
switched off. After a certain length of time the feeding voltage is switched on
again. The procedure of switching the feeding voltage on/off is repeated
periodically.
• Loss of signal (LOS) / Loss of frame (LOF)
• BER-3/ BER-6 (Bit Error Ratio 10-3 and 10-6) detectable separately in upstream and
downstream direction (applicable for LPU112)
• BER-3/ BER-6 summary for both directions (applicable for LPU430, which is not
supported by the AnyMedia ® LAG Shelves)
Important! If one of these faults is detected (except for BER-6) for ISDN BRA
lines an automatic subscriber line test is started which detects whether the fault is
at the U port line or on the pack itself.

Managed NTU fault conditions

The AnyMedia ® Access System gets the following managed NTU fault condition
related to all three NTU types (V.24, X.21 and V.35):
• NTU not responding - the NTU is not responding to management communications.
If V.24 and X.21 NTUs are operating in low speed mode additionally these NTUs
report the following X.50 alarms:
• Alarm indication signal (AIS)
• Loss of alignment (LOA)
• Network out of service (NOS)
• Remote alarm - signals that the remote NTU has reported an alarm.

If an AnyMedia ® Access System is configured with a great number of NTUs (for

example 100 NTUs) it may take up to about 60 seconds between the alarm event
occurring and the generation of the TL1 message reporting the alarm.

[S]HDSL AP fault conditions

[S]HDSL AP faults are fault conditions which influence all [S]HDSL pairs on a
[S]HDSL AP.
Examples of [S]HDSL AP faults are:
• Pack removal
• Pack not responding to poll
• Power fault
• Front cable not plugged
The SHDSL AP has two front cables for SHDSL ports and unstructured E1 ports
respectively. Faults are reported only against the cable connected to the SHDSL
ports.
• Hardware errors
• Loss of 4 MHz clock.

[S]HDSL interface fault conditions

[S]HDSL interface faults are related to a single [S]HDSL port. The fault can be on the
[S]HDSL port(s) or at the [S]HDSL drop(s).
Example for [S]HDSL port fault is:
• Loopback 1 not successful executed.
Drop faults are external fault conditions on the [S]HDSL pairs (a- and b-wire) which
influence an individual [S]HDSL port on the [S]HDSL AP.
Examples for subscriber line faults are:
• a-wire short to ground
• b-wire short to ground
• Short circuit between a-wire and b-wire
• Power cross (caused by a foreign voltage).

Ambiguous fault conditions

Example of ambiguous [S]HDSL faults (not assignable to [S]HDSL drop or [S]HDSL
port) is:
• Loss of frame (LOF)
• HBER, LBER in upstream and downstream direction.
The root cause can be a fault at the [S]HDSL port or [S]HDSL drop.

2-Mbps payload fault conditions on HDSL

The HDSL ports within the AnyMedia ® Access System can be provisioned for various
services. For applications via a 2-Mbps interface according to G.703 the following
faults are detected (Not for unstructured application modes):
• Alarm indication signal (AIS)
• Loss of frame (LOF)
• High bit error ratio (HBER) (Not for V3 application modes)
• Remote alarm indication (RAI)
• Low bit error ratio (LBER) (Not for V3 application modes).
The 2-Mbps faults are detected within the 2-Mbps payload at the HDSL AP. The
2-Mbps payload faults are reported via HDSL drop identifier. The HDSL interface
faults ″LOF/LOS″ are higher order fault conditions and mask the 2 Mbps payload
faults at the same HDSL port.

AP_E1 link faults on SHDSL AP

When an AP_E1 port is routed to an SHDSL port, the [S]HDSL fault conditions and
LOS for the AP_E1 port can be generated. When an AP_E1 port is routed to the PCM
highway, the alarms LOS, LOF, AIS, RAI, HBER and LBER can be generated for the
AP_E1 port. The AP_E1 faults on SHDSL AP are:
• AP_E1 front cable not connected
• Loss of signal (LOS)
• Loss of frame (LOF)
• Alarm indication signal (AIS)
• Remote alarm indication (RAI)
• High bit error ratio (HBER)
• Low bit error ratio (LBER).
LOF, AIS, RAI, HBER and LBER are valid only for AP_E1 ports used as RT links.

Fault conditions at HDSL or SHDSL NTUs

The AnyMedia ® Access System is able to detect:
• Loss of layer 1 capability , which may result from following 2-Mbps faults at the
G.703 input of the NTU:
– LOF (Not for unstructured application modes)
– LOS
– HBER (Only for HDSL).
• Loss of power at the NTU for HDSL in the V3 application and for SHDSL in all
applications. Afterwards LOS/LOF at the HDSL interface is detected. The NTU
power fault alarm is cleared if the HDSL interface has recovered.
• The fault conditions AIS, RAI, HBER, and LBER upstream at G.703 input of the
SHDSL NTU are respond as 2-Mbps payload fault conditions.

These faults are reported via the [S]HDSL drop identifier. For the location of the
different [S]HDSL fault conditions, see the two figures below.
The following figure shows the location possibilities of HDSL faults (example).

Subscriber side Network side

AnyMedia shelf

NTU HDSL AP(LTU)

2 HDSL port 1
TRCVR1 TRCVR1

TE
2 HDSL port 2 TRCVR2
TRCVR2

G.703 interface fault HDSL drop fault HDSL port fault 2 Mbps payload fault
at NTU input
HDSL AP fault

The following figure shows the location possibilities of SHDSL faults (example)

Subscriber side Network side

AnyMedia shelf

SHDSL AP
(LTU)
2 SHDSL port 1...8 G.703
TE NTU 2 Mbps
(E1)

AP_E1 feeder
1...4

2-Mbps fault (AIS, RAI,

G.703 interface fault HBER, LBER upstream)
at NTU input (LOF, LOS)

SHDSL drop fault SHDSL port fault SHDSL AP fault

4
Unstruct.
AP_E1 link fault
AP_E1
lines

Ringer application fault conditions

For the ringer application in the AnyMedia ® LAG 4300 Shelf and in the AnyMedia ®
ETSI V5 Shelf four different categories of fault conditions apply:
• General RGP faults. The general fault alarms for RGP are defined as follows:
– Pack removal
– Pack mismatch
– Pack not responding to poll
– Power fault
– Unexpected, AP internal
– Hardware errors.
• Specific RGP faults. Besides the general fault alarms there are RGP specific
alarms:
– RGP shut down
– RGP output voltage too low
– Foreign voltage on ringing bus
– RGP ringing voltage failure on ringing bus.
• External ringer alarms
If an external ringing source is provisioned and the ringing voltage detector on the
COMDAC does not detect ringing voltage an alarm ″ringing voltage failure on
ringing bus″ is raised.
• Ringing summary alarms
There are two ringer alarms raised for ringing application with the shelf AID.
These alarms are summary alarms which indicate, that something is worse with the
ringing. Either ringer provisioning is missing or there is a failure with the
provisioned ringing resource.

Facility alarms (2-Mbps transmission)

Facility alarm fault conditions

Facility alarms indicate E1 link and synchronization network access facility problems.
Every E1 SLIP error will be reported. The AnyMedia ® Access System uses the
following external criteria to determine if a signal has failed:
For E1 link transmission fault
• Loss of signal (LOS)
• Loss of frame (LOF)
• Alarm indication signal (AIS)
• High/low bit error ratio (HBER / LBER)
• Remote alarm indication (RAI).
LOF, AIS, RAI, HBER and LBER not for unstructured application modes, furthermore
HBER and LBER not for V3 application modes.

Host and remote terminal alarms

Host and remote terminal interface alarms

The following alarms are reported for host and remote terminal interfaces:
• Host/remote terminal interface failed
• Host/remote terminal interface degraded
• Signalling and control data link error

Remote terminal link alarms

The following alarms are reported for remote terminal links:
• Remote terminal link identification pending (RT only)
• Remote terminal link identification failed
• Remote terminal link layer 2 failed
• Remote terminal link layer 3 failed
• Remote terminal link interface identification failed.

Alarm signaling paths

Alarm collector box

(external) Rack connection panel (RCP)
Any operational TL1 interface Miscellaneous alarm inputs Alarm output

8 physical

AnyMedia Mainshelf

Alternative:
TL1 via RTU port ALARM IN ALARM OUT

Shelf connection panel LAN

8 physical + 64 virtual

Alarm inputs Alarm output relays

CIU
EIA-232C
Alarm inputs CIT port
via TL1

LED
Display
COMDAC ROC
Alarm processing (ext. and int.)
CRITICAL

MAJOR

MINOR

Alarm logging

Miscellaneous alarm inputs

The AnyMedia ® Mainshelf (CIU) support 8 miscellaneous alarm closure inputs which
are provisionable by the operator. A closure to common ground will indicate an
external fault condition.
To each individual alarm input an alarm name/type (character string) and an alarm
severity (major or minor) can be assigned. Alarms detected at the miscellaneous alarm
inputs are treated in the same way as alarms in the system itself. An additional LED at
the CIU indicates an active alarm input.

Monitoring of alarm inputs

The monitoring of the alarm inputs is performed by the system. To avoid the reporting
of short contact closures the closure is active respectively inactive for 5 seconds before
the fault respectively the clearance is reported.
Activated alarm inputs generate autonomous alarm messages indicating which contact
is activated..

Alarm support via external alarm collector box

The AnyMedia ® Access System supports a TL1 command (REPT-CLOSURES) to raise
and retire environmental alarms. For this purpose a kind of virtual miscellaneous
contact unit, with up to 64 virtual miscellaneous alarm input contact closures, is
provided.
The TL1 command allows any external system (for example alarm collector box) to
trigger the usual environmental alarm reports (REPT-ALM-ENV). The commands can
be issued on any operations interface of the system, e.g. TELNET, CIT, VC, and
especially also on the RTU interface of each shelf type.
Important! While on the first mentioned operations interfaces a user login of at
least the ″Reports Only″ privilege level must be performed, the RTU interface
allows to issue the commands without any prior user login.
Each of the virtual miscellaneous alarm input contact closures (alarm input detectors)
are configurable within the system regarding its alarm type (e.g. FAN, MJF, MISCx...)
and its severity (CR, MJ, MN), see the following table. The provisioning is done with
the TL1 command SET-ATTR-ENV.

Options for power/environmental alarm parameters

The following table provides options for the power/environmental alarm parameters. If
the power/environmental alarm parameters have not been provisioned, the default
values are: ″closure not provisioned″; ″mc-1-{x}″, ″NONE″; ″MN″.

Power/environmental fault conditions and alarm attributes. The abbreviations are used
as at the TL1 interface (AID, condition type, severity level, mc/submc/vmc =
miscellaneous alarm input contact). The condition type ″NONE″ is used to reset the
assignment of the alarm input detectors.

Miscellaneous Fault Condition Possible Cause

mc-1-{x}, ACF, MN AC input power failure
submc-{y}-{x}, ACF, MN
vmc-1-{x}, ACF, MN
mc-1-{x}, AIRCOND, MJ Air conditioning failure
submc-{y}-{x}, AIRCOND, MJ
vmc-1-{x}, AIRCOND, MJ
mc-1-{x}, BATTERY, MJ Battery failure
submc-{y}-{x}, BATTERY,MJ
vmc-1-{x}, BATTERY, MJ
mc-1-{x}, BD, MJ Battery on discharge
submc-{y}-{x}, BD,MJ
vmc-1-{x}, BD, MJ
mc-1-{x}, FAN, MJ Fan unit failure
submc-{y}-{x}, FAN, MJ
vmc-1-{x}, FAN, MJ
mc-1-{x}, FIRE, MJ Fire
submc-{y}-{x}, FIRE, MJ
vmc-1-{x}, FIRE, MJ
mc-1-{x}, FLOOD, MJ Flood
submc-{y}-{x}, FLOOD, MJ
vmc-1-{x}, FLOOD, MJ
mc-1-{x}, HICUR, MN High current
submc-{y}-{x}, HICUR, MN
vmc-1-{x}, HICUR, MN
mc-1-{x}, HIHUM, MN High humidity
submc-{y}-{x}, HIHUM, MN
vmc-1-{x}, HIHUM, MN
mc-1-{x}, HITEMP, MN High temperature
submc-{y}-{x}, HITEMP, MN
vmc-1-{x}, HITEMP, MN

Miscellaneous Fault Condition Possible Cause

mc-1-{x}, HIVG, MJ High voltage
submc-{y}-{x}, HIVG, MJ
vmc-1-{x}, HIVG, MJ
mc-1-{x}, HIWTR, MJ High water
submc-{y}-{x}, HIWTR, MJ
vmc-1-{x}, HIWTR, MJ
mc-1-{x}, LWTEMP, MN Low temperature
submc-{y}-{x}, LWTEMP,MN
vmc-1-{x}, LWTEMP, MN
mc-1-{x}, LWVG, MJ Low voltage
submc-{y}-{x}, LWVG, MJ
vmc-1-{x}, LWVG, MJ
mc-1-{x}, LWWTR, MN Low water
submc-{y}-{x}, LWWTR, MN
vmc-1-{x}, LWWTR, MN
mc-1-{x}, MISC1, MISC2.....MISC64, All alarm input detectors are available for
CR/MJ/MN customer-designated usage with configurable alarm
submc-{y}-{x}, MISC1, MISC2.....MISC64, message and severity level via the condition types
CR/MJ/MN MISC1.....MISC64.

vmc-1-{x}, MISC1, MISC2.....MISC64,

CR/MJ/MN
mc-1-{x}, MJF, MJ Fuse failure major
submc-{y}-{x}, MJF, MJ
vmc-1-{x}, MJF, MJ
mc-1-{x}, MNF, MN Fuse failure minor
submc-{y}-{x}, MNF, MN
vmc-1-{x}, MNF, MN
mc-1-{x}, NONE, MN Closure not provisioned
submc-{y}-{x}, NONE, MN
vmc-1-{x}, NONE, MN
mc-1-{x}, PMJ, MJ Power failure major
submc-{y}-{x}, PMJ, MJ
vmc-1-{x}, PMJ, MJ
mc-1-{x}, PMN, MN Power failure minor
submc-{y}-{x}, PMN, MN
vmc-1-{x}, PMN, MN

Miscellaneous Fault Condition Possible Cause

mc-1-{x}, RECT, MJ Rectifier failure
submc-{y}-{x}, RECT, MJ
vmc-1-{x}, RECT, MJ
mc-1-{x}, RECTHI, MN Rectifier high voltage
submc-{y}-{x}, RECTHI, MN
vmc-1-{x}, RECTHI, MN
mc-1-{x}, TAMPER, MJ Intrusion (door open)
submc-{y}-{x}, TAMPER, MJ
vmc-1-{x}, TAMPER, MJ
mc-1-{x}, TEMP, MJ Temperature failure
submc-{y}-{x}, TEMP,MJ
vmc-1-{x}, TEMP, MJ

Alarm output relays

There are three software-controlled output relays on the CIU. They can be used to
indicate active alarms. None, one or more alarm attributes can be assigned to each
output relay. If ″none″ is assigned, no alarm output will be generated. The default
delivery assignment for the three alarm contacts is CR, MJ and MN.
The alarm relays are activated if alarms with corresponding attribute values are
detected. The relays are deactivated if all alarms having the corresponding attribute
values are cleared or cut-off with the ACO function.
The alarm contacts do not necessarily correspond to the status displayed by the system
LEDs. The system LEDs and the alarm contacts will only display the same if they
have the same assignments.

Alarm cut-off function (ACO)

The ACO function provides the possibility to immediately cut off the audible/visible
alarms active on the alarm interface outputs. The ACO function can be activated by
pressing the ACO button on the CIU or by TL1 command.

Local alarm and status indicators

Severity levels
Light emitting diodes (LEDs) on the faceplates reflect fault and/or status conditions of
the pack. Additional LEDs on the faceplate of the COMDAC indicate the currently
active alarms divided into the severity levels:
• CR - Critical
• MJ - Major
• MN - Minor.
If the alarm severities are reassigned by an operator the status of the LEDs will be
updated.

Alarm categories
Furthermore the alarms are divided into the following categories:
• NE - Near-end alarms
• FE - Far-end alarms.
The five COMDAC LEDs are independent of the TL1 alarm reporting mode, the alarm
contact attribute values and the alarm-cut-off mode.

LED indicators
For the LED indicators on the faceplates of the packs, their meanings and colors see
the Data Sheet Book 363-211-251.
In some cases the AnyMedia ® Access System does not send information about FAULT
LED changes to the GSI. In such cases the shelf view of the GSI may not reflect the
current status of the LEDs on the real shelf.

Alarm reporting and retrieval via TL1

Reporting
All detected alarms and all system messages are reported by autonomous TL1
messages via the external interface provided by the CIU. For reporting, the user must
be logged in and the autonomous messages must not be suppressed for the OAM&P
interfaces.

Retrieval
Next to the autonomous alarm messages the operator can retrieve all active alarms and
status conditions supported by some filters concerning alarm and equipment types.
The functions supported are:
• Equipment and facility alarms
• Miscellaneous alarms
• Status conditions.

Alarm logs
Further the operator can retrieve the autonomous message output log (1000 records for
alarms, events, database changes, security) and the history log (500 records for alarms,
events and operator TL1 commands).
If the 1001st message output record or the 501st history record occurs, the first record
in the output log or in the history log respectively is deleted (wrap around).

Inhibiting/resuming alarm
The system provides the capability to inhibit and resume autonomous alarm reporting
to any narrowband OAM&P interfaces.
It is possible to disable all alarms of one (or more) specific entity or of an entity
group. The ability to disable alarms can be useful for example during troubleshooting
to avoid a great amount of alarm reports.

Built-in self tests

Testing pack integrity

A part of testing the integrity of a pack are on-line tests. These tests are executed
continuously or periodically within the system during pack operation. All on-line tests
are non-service affecting. They are performed on both, active and standby packs.
• Communication path integrity check
The communication path (UART link) integrity is maintained by periodic polling of
each pack by the active COMDAC. The polling is non-service affecting. The
occurrence of two consecutive failed attempts for a single pack will result in a pack
not responding to poll alarm being raised against the pack in question. For APs
additionally the slot state changes to OOS-FLT.
• Pack missing/power fault monitoring
Removal of a pack or DC power converter fault on a pack cannot be distinguished.
After a fault of the polling, the COMDAC will attempt to re-establish
communication with the pack in question. The occurrence of a repeatable failed
attempt will result in a pack missing/power fault alarm. For HDSL APs the slot
state changes to OOS-UEQ, for POTS/ISDN APs the slot state changes to
OOS-FLT.
• BB packs cannot be recovered by the COMDAC. This can only be done by the
AFM. If a BB pack, which is considered by the COMDAC as faulty, is recovered
by the AFM, the COMDAC won’t be notified that the BB pack is operational
again. Therefore, in deviation from the handling for COMDAC controlled packs,
the polling of BB packs continues until they are responding to the polling request.
If this is the case, the ″pack not responding to poll″ alarm is cleared and the slot
state changes back to IS, the pack state to xxx-<null> or xxx-MEA if a pack
provisioning mismatch is detected (xxx depends on the administrative primary
service state) and the drop states to IS or IS-NAC if a pack provisioning mismatch
is detected.
• Data path integrity tests for IO_E1(P)
The data path (feeder link) integrity is maintained primarily by monitoring parity
errors both upstream and downstream. The IO_E1(P) packs monitor parity errors on
the active side of the upstream feeder link only and report the results to the active
COMDAC. Each IO_E1(P) will hit-time the detection.
• Clock/framesync signal monitoring for IO_E1(P)
Each IO_E1(P) monitors the 4-MHz clock and 8-kHz framesync signal received on
both the active and the standby side. The IO_E1(P) will hit-time the detection of
clock and framesync errors and report resulting fault conditions to the active
COMDAC via UART messages.

• E1 signal/loop time reference source monitoring

The IO_E1(P) monitors all incoming E1 signals including the E1s being assigned
as synchronization reference signal inputs and supports the generation and detection
of the AIS and RAI alarms.
The active COMDAC monitors the reference signal. A synchronization reference
failed alarm will be reported regardless of the root cause of the problem, that is
either an E1 signal failed (AIS, LOS, LOF or HBER) or an IO_E1(P) fault
occurred.
• Clock signal monitoring for IO_HDLC
Each IO_HDLC monitors the 4-MHz clock signal received. The IO_HDLC will
hit-time the detection of loss of clock and report this fault condition to the active
COMDAC via UART messages.
• Data loopback test for IO_HDLC
To allow the IO_HDLCs to test their HDLC controllers, the COMDAC loops two
64-kbps timeslots from both the active and standby IO_HDLC back to the source
pack (see the following figure). Because two 64-kbps timeslots of TSI loopback
capacity are required per IO_HDLC it is possible to loop both packs back and
perform the loopback tests on both standby and active IO_HDLC while up and
running. The IO_HDLCs generate and detect the test patterns autonomously. In the
event of an error the COMDAC is informed.
The following figure shows the data loopback test mode.

COMDAC
TSI up

active or standby
data looped back IO_HDLC

IS or
2 x 64 kbps
IS-STB
TSI down 2 x 64 kbps

Built-in self-test
The built-in self-test (BIST) is used at pack level and is performed for both, active and
standby packs. After a power-on or a hardware reset the packs perform a sanity check
including microprocessor initialization, clearing of RAM and initialization of system
data.

After the sanity check the COMDAC performs a pack diagnostic and for the APs a test
of all line circuits. The test algorithms specific to the fault conditions are developed
and embedded within the pack. A full set or a subset of BIST is performed in other
on-demand tests.
Important! For combo packs in the AnyMedia ® Mainshelf the built-in self-test is
performed, if the combo pack is inserted in a system with a running COMDAC in
steady state. In cases where the COMDAC recovers in a system with an already
installed combo pack, the test of the combo pack is not performed to avoid an
interruption of the ATM xDSL service carried by the combo pack.

Components of the built-in self-test

The BIST components include the following pack diagnostic categories:
• Program integrity test — testing the integrity of the address space and devices in
which executable code is stored
• Memory integrity test — testing the integrity of the volatile and nonvolatile
memory address space and devices, including partial memory tests
• Hardware functional verification tests for all major component functions
• Internal bus and internal interface verification tests
• Component level (internal) loopback tests for IO_HDLC/IO_E1(P)
• Internal metallic tests (relay testing) for APs.
A full set of BIST is performed at power-on as test routine diagnostics. Therefore the
BIST is not service affecting. The occurrence of a BIST fault of any type results in a
pack fault. The execution of the BIST on a particular pack does not affect the functions
of any other packs in the system. Power-on test is done during pack initialization.
Routine off-line diagnostics are initiated by the active COMDAC.

[S]HDSL port test

When the activation of the HDSL interface has failed, an [S]HDSL port test is
performed. The test can also be performed on demand from the operator. The HDSL
port test includes automatically the second HDSL port on the HDSL interface. The
HDSL interface test lasts about 35 seconds and includes the following functions:
• All HDSL interface registers
• Loopback 1 test
After the sanity check the COMDAC performs a pack diagnostic and a test of all line
circuits.

POTS/ISDN AP port test

The test categories of all line circuits are:
• Z ports circuit tests on POTS AP
• EOC and performance monitoring (PM) channel test on ISDN AP, applicable for
LPU112

• U port test on ISDN AP with following functions:

– Testing of all U port registers
– Transceiver/echo canceller test (ECT), applicable for LPU112
– 160-kbps loopback test
Test algorithms are embedded within the POTS/ISDN AP. No external test equipment
is necessary. The occurrence of a BIST fault of any type will result in a POTS/ISDN
AP fault.
For the AnyMedia ® Access System the pack level is defined as the smallest fault unit.
The execution of the BIST on a particular POTS/ISDN AP does not affect the
functions of any other packs in the system.
Important! Also a single Z/U interface fault causes a POTS/ISDN AP fault if the
fault is detected in the BIST after reset or power-up.
In addition for 4B3T U ports it is possible to measure the feeding voltage. But this test
will be performed on demand from the operator.

Testing possibilities
...................................................................................................................................................................................................................................

Testing capabilities for NB services

The AnyMedia ® Access System supports a variety of tests for narrowband and
broadband services and has a priority order for any kind of tests. The following list
shows the tests from high priority to low priority:
• High priority tests
– Tests using integrated and external capabilities
– Drop tests using internal TAP10x/LPZ200
– Drop tests using external test head
– Test access path test
– CRC tests
– Application pack circuit test
– Ringing test
• Medium priority tests
– Send single pulse (applicable for LPU430).
– NT1 detection test
– Send howler tone
• Low priority tests
– Loopbacks for line test and measurement
Important! A test request while a test with the same or higher priority is already
running is denied. A test request with higher priority will stop any test with lower
priority and will then perform the higher priority test.

GSI/EMS impact
The GSI/EMS initiates all test actions. The AnyMedia ® Access System controls the
testing. This means it checks the state of the entities, requests blocking, and is able to
abort the test session even if the connection to the GSI/EMS is lost.
The GSI and EMS have the ability to configure test scripts for the subscriber types.
The results are viewed via the GSI or EMS.
Only the operator mode will be supported by the AnyMedia ® Access System. This
means the results are viewed directly and do not need to be stored in a database. The
database handling will be performed in a test operation system (TOS) which is not part
of the AnyMedia ® Access System. A TOS can be connected to the system to invoke
the test and evaluate and store the results.

On-demand tests using integrated capabilities

Test types
In general two different types of tests can be performed on demand:
• Drop test and measurement
This test is used for testing the subscriber line and partly the customer premises
equipment (CPE). With the test the electrical parameters of the subscriber line are
measured. The measured parameters comprise foreign voltage, insulation and
capacitance. The results are used to detect broken or poor quality wires even before
the subscriber notices a lack of quality. For POTS APs and ISDN APs additionally
an inward feeding voltage test is supported.
• Circuit test
This test is used for testing the port hardware (HW) in the system. The functions of
the port test rather depend on the HW function of the circuit (for example POTS,
BB, pulse metering...). In the AnyMedia ® Access System these tests are performed
on each AP using a part of its self-test capability.
After the testing the subscriber returns to its condition before the testing, irrespective
of the test result.
Important! If the hardware of an BB AP supports relays for metallic test access to
the subscriber line then the drop test and measurement as well as the test with
external test head capabilities of the system can be used. The test control is
performed by the COMDAC with the same commands as for NB drops. The
metallic test access is service affecting if the subscriber line is currently in use for
NB or BB service. A request for metallic test access is always granted regardless of
any active service without further notice to the broadband controller AFM. The
COMDAC only checks whether the requested subscriber line drop is accessible for
testing. Only one subscriber line can be tested on an AnyMedia ® Access System at
a time.

Measurement modes
The AnyMedia ® Access System supports three test session modes for drop test and
measurement and one test session mode for testing the test access setup itself. Within a
test session several tests and measurements, either by an integrated test application
pack at modes INT and TALK or by external test equipment at modes MAN, MON
and WIRE, can be performed. Following different test session modes are available:
• Integrated testing
Integrated testing means testing using only the system’s integrated testing
capabilities provided by the test application pack (TAP10x/LPZ200). Thus it can be
done even remotely.
Note: TAP10x corresponds either to TAP100 or TAP100B (supported by release
R1.6.2 or higher) or TAP101 (supported by release R1.6.3 or higher). It can be
installed per each AnyMedia ® Mainshelf and plugged-in in any application pack
slot.
• Manual testing
Manual testing means a local testing with external equipment, without using the
system’s integrated testing capabilities.
• Monitoring
Monitoring can only be done locally via the faceplate connector (bridged drop and
circuit). It is not possible to perform it remotely.
• Wiring
At the test session mode WIRE, the maintenance personnel is able to check the
Internal test path switched from CIU faceplate connector via the backplane to
TAP-B interface, test access at faceplate connector and TAP-B interface.
• Circuit testing (self-tests).
All test modes have to be initiated by a TL1 command. The system supports up to
eight simultaneous test sessions but only one per shelf at the same time. Any test
session is automatically stopped by the system if any involved system entity changes to
a not operational state by error conditions or its primary service state is changed by a
TL1 command.

Measurement principles
The general principle for any measurement performed by the TAP10x/LPZ200 is that
only the most dominant parameter (for example high foreign voltage, low resistance, or
high capacitance) can be measured with the defined accuracy. This dominant parameter
is most likely to represent the principal problem to be resolved for that particular
subscriber line.

The suggested method for trouble shooting a suspect subscriber circuit using the
capabilities of the TAP10x/LPZ200 is as follows:
• Check the foreign voltage (AC/DC) present on the circuit. Resistance and
capacitance measurements will be accurate only if the outcome of the foreign
voltage (AC/DC) test is within the desired or expected range.
• Check the insulation resistance of the subscriber circuit. If this test indicates a low
resistance path to ground or battery then the capacitance measurements will less
accurate.
• Check the capacitance of the subscriber circuit.
For resistance measurements the a/b-wire of a drop with the lowest resistance is
measured most accurately; other a/b-wires with considerably higher values will be
measured with less accuracy (see Insulation and loop resistance measurements). The
same is true for the capacitance measurement, that means the a/b-wire of a drop with
the highest capacitance is measured most accurately (see Capacitance measurements).

Impact of NT1 on ISDN testing

The ISDN test accesses are terminated by a network termination (NT1). Some test
results performed by the TAP10x/LPZ200 are affected for the presence of the NT1 in
the line. In order to avoid it, the TAP10x/LPZ200 applies a reduced test voltage when
it is testing a NT line. All insulation resistance measurements on digital local lines can
be performed because the TAP10x/LPZ200 applies a DC voltage of less than 10V. This
can result in less accurate measurements for the insulation resistance test.

Testing in reduced battery state

For the test session modes MAN, INT-BLK and TALK it is allowed to tear down the
served service of the drop for the test session. This means that for switched services
the service is blocked in cooperation with the connected exchange during the complete
test session. For switched POTS services in reduced battery state a special handling is
implemented. In this case an on-hook event is simulated towards the exchange and
then the service is blocked in cooperation with the connected exchange. This allows
testing of switched POTS services which are in a ″Line Lock Out″ state in the
exchange.

Testing via ″Line Test window″

The ″Line Test window″ is used to provide a user friendly and comprehensive screen
to perform line testing. It provides access and control to perform metallic line testing
with a TAP10x/LPZ200. This screen does not support the initial installation or
provisioning of the TAP10x/LPZ200, test line entity or test access path integrity
checks. To be usable these steps needs to be performed beforehand by other means.

The ″Line Test window″ supports

• a list of all active test sessions in the system
• to setup and maintain metallic test sessions of the following test modes:
– INT with blocking mode BLK, FRCD or UNBLK
– Talk with blocking mode BLK or FRCD.
• to perform a user specified collection of the following measurement and test
capabilities.

Measurement and test capabilities

If a TAP10x/LPZ200 is used, the following measurements and tests can be done:
• AC and DC foreign voltages of the a/b-wire of a drop
• Feeding voltage measurement (POTS/ISDN APs)
• Insulation and loop resistance of the a/b-wire of a drop
• Capacitance of the a/b-wire of a drop
• Distance to open measurement for a specified drop
• Detection test of the test termination in the master line jack of the subscriber
• Draw and break dial tone test (LPZ200 or TAP100B or higher needed by dial tone
analysis)
• DTMF, pulse character or register recall (hook flash) test
• Sending of test tone for POTS CPE
• Ringing test for POTS CPE (no TAP10x/LPZ200 needed)
• Noise measurement on a subscriber line (LPZ200 or TAP100B or higher needed)
• Loop current measurement (LPZ200 or TAP100B or higher needed)
• Tone measurement with specific frequencies (LPZ200 or TAP100B or higher and
additional test equipment at subscriber side needed)
• Howler tone on demand on POTS drops in reduced battery state (no
TAP10x/LPZ200 needed) (not via Line Test window)
• Quick line test (TAP101 or LPZ200 needed) (not via Line Test window)
• Talk to subscriber test (no TAP10x/LPZ200 needed)
• Test of the correct cabling between the CIU and the test application pack (not via
Line Test window)
• Circuit test on a specified application pack (no TAP10x/LPZ200 needed) (not via
Line Test window)
• CRC test of a specified ISDN drop (no TAP10x/LPZ200 needed) (not via Line Test
window)
• Send single pulses on an ISDN drop (no TAP10x/LPZ200 needed) (not via Line
Test window)
• NT1 detection test (no TAP10x/LPZ200 needed) (not via Line Test window)
• Operate E1 line loopback (no TAP10x/LPZ200 needed) (not via Line Test window)

• Operate ISDN line loopback (no TAP10x/LPZ200 needed) (not via Line Test
window)
• Operate HDSL and SHDSL loopback (no TAP10x/LPZ200 needed) (not via Line
Test window).
Important! One Test Application Pack (TAP10x) can be installed per AnyMedia ®
Mainshelf. It can be plugged in in any application pack slot.

Test capabilities overview

The following table lists which integrated tests are supported on the various application
pack types.

Test capabilities Application pack types

LPP100 LPZ12x (1) LPU112 LPU132 LPS504 BBP (3)

LPZ100 LPZ640 LPU430 (2) LPS510
LPZ110 LPU432
LPZ200 LPU508
LPZ641
LPA832
LPA833

Set up a metallic test X X - - - X

access (Integrated,
subscriber remains
unblocked during test
access)
Set up a metallic test X X X X X X
access (Integrated,
subscriber remains
blocked during test
access)
Set up a ″talk to X X - - - -
subscriber″ session for
metallic line testing

Set up a metallic test X X X X X X

access (Manual)

Set up a metallic test X - - - - -

access (Monitoring)
Stop a drop test and X X X X X X
measurement session

Measure all AC/DC X X X X X X

foreign or feeding
voltages of a-wire and
b-wire of a drop. Split
measurement in
equipment (outward)
direction
Measure all AC/DC X - X X ( 7) - -
foreign or feeding
voltages of a-wire and
b-wire of a drop in
normal polarity mode.
Split measurement in
facility (inward) direction

Test capabilities Application pack types

LPP100 LPZ12x (1) LPU112 LPU132 LPS504 BBP (3)

LPZ100 LPZ640 LPU430 (2) LPS510
LPZ110 LPU432
LPZ200 LPU508
LPZ641
LPA832
LPA833

Measure all AC/DC X - - - - -

foreign or feeding
voltages of a-wire and
b-wire of a drop in
reverse polarity mode.
Split measurement in
facility (inward reverse)
direction
Measure the insulation X X X X X X
resistance of the a-wire
and the b-wire of a drop
Measure the loop X X X X X X
resistance between the
a-wire and the b-wire of
a drop

Measure the capacitance X X X X X X

of the a-wire and the
b-wire of a drop
Measure the distance to X X X X X X
open of the specified
drop
Measure the master line X X X X X X
jack at the end of the
subscriber line
Measure the background X X X X X X
noise on a terminated
subscriber line (4)

Measure the loop current X X - - - -

on the real subscriber
line which is fed by a
reference feeding circuit
on the test application
pack (4)

Measure the loop current X - - - - -

on the simulated test
subscriber line which is
fed by the subscriber
application pack circuit (4
)

Measure the frequency X X X X X X

and power level of the
most significant tone
present on the subscriber
line (4)

Test capabilities Application pack types

LPP100 LPZ12x (1) LPU112 LPU132 LPS504 BBP (3)

LPZ100 LPZ640 LPU430 (2) LPS510
LPZ110 LPU432
LPZ200 LPU508
LPZ641
LPA832
LPA833

Start a circuit self-test of X X X X - -

one port of a specified
AP

Start a CRC test for the - - X - - -

specified ISDN drop
Start a non-service - - X X - -
affecting NT test for a
specified ISDN drop

Initiate a draw and break X - - - - -

dial-tone test for the
specified drop

Start a cadenced ring X X - - - -

signal on a specified drop
to the POTS CPE

Analyze incoming dial X X - - - -

pulse or DTMF
characters present on the
drop
Initiate generation of a X X X X X X
test tone and connect it
to the drop
Terminate the sending of X X X X X X
a test tone to the drop
Execute a configurable X X X X X X
series of tests with one
command invocation:
Quick line test (5) (6)

Send/remove single - - - X (7) - -

pulses on/from an ISDN
drop

Operate/release a - - X X - -
loopback on an ISDN
drop

Operate/release a - - - - X -
loopback on HDSL and
SHDSL drops

Send/remove customer X X - - - -
specific howler tone
on/from a drop, which
serves a switched POTS
subscriber

Notes:
1. LPZ12x includes the application pack types LPZ120B, LPZ121B, LPZ122B, and LPZ123.
2. Not supported by the AnyMedia ® LAG Shelves.
3. This includes broadband pack types (BBPs) with test relays; the features and functions list of each BBP
in the Data Sheet Book 363-211-251 shows, whether metallic line test is provided for this BBP.
4. This test is only supported by LPZ200 test head and by TAP100B or higher.
5. This test is only supported by LPZ200 test head and by TAP101 or higher.
6. For each subtest the same restrictions as for the explicit single test apply.
7. This test is not supported for LPU508.

Important! Some tests supported on analog APs (for example LPP100,

LPZ100, ... ) are not allowed in case of ALL service is provisioned. For details,
see the table below.

Test command Type of provisioned service

No service POTS service ALL service

CONN-TACC-DROP (INT-BLK/INT- allowed allowed allowed if INT-FRCD or

FRCD) ALL service is OOS,
rejected if INT-BLK and
ALL service is IS

CONN-TACC-DROP (INT-UNBLK) rejected allowed rejected

CONN-TACC-DROP (TALK-BLK/TALK- rejected allowed rejected
FRCD)

CONN-TACC-DROP (MAN) allowed allowed allowed

CONN-TACC-DROP (MON) allowed allowed allowed

MEAS-VG (SPLTE-outward) allowed allowed allowed
MEAS-VG (SPLTF-inward) allowed allowed allowed

MEAS-VG (SPLTF_REV-inward allowed allowed rejected

reverse)

MEAS-RES(INSUL) allowed allowed allowed

MEAS-RES(LOOP) allowed allowed rejected

MEAS-CAPNC allowed allowed allowed

MEAS-DIS allowed allowed allowed

MEAS-MLJ allowed allowed allowed
1
MEAS-NSE ( ) allowed allowed allowed

MEAS-CUR ( 1) allowed allowed allowed

1
MEAS-TN ( ) allowed allowed allowed

MEAS-ALL ( 2) ( 3) allowed allowed allowed

4
CONN-TN/ DISC-TSTSIG ( ) allowed allowed allowed

TST-RINGSGNL allowed allowed rejected

MEAS-OUTPLSE allowed allowed rejected

Test command Type of provisioned service

No service POTS service ALL service

TST-DIALTONE ( 5) rejected allowed rejected

6
SND-HOWLER/ RMV-HOWLER rejected allowed ( ) rejected

Notes:
1. This test is only supported by LPZ200 test head and by TAP100B or higher.
2. This test is only supported by LPZ200 test head and by TAP101 or higher.
3. For each subtest the same restrictions as for the explicit single test apply.
4. On-hook detection is only supported by LPZ200 test head and by TAP100B or higher.
5. Dial tone analysis is only supported by LPZ200 test head and by TAP100B or higher.
6. If the drop (subdrop) is in ″reduced battery″ state.

Measurements
The measurements described in the following tables can be done.

AC voltage measurement of a/b-wire of a drop

Measuring point Foreign voltage range Relative/absolute tolerance

a-wire to earth 200 Vrms ± 4%/± 2 V
b-wire to earth 200 V rms ± 4%/± 2 V
a-wire to b-wire 200 V rms ± 4%/± 2 V

DC voltage measurement of a/b-wire of a drop

Measuring point Foreign voltage range Relative/absolute tolerance

a-wire to earth ± 150 VDC ± 2%/± 1 V
b-wire to earth ± 150 V DC ± 2%/± 1 V
a-wire to b-wire ± 150 V DC ± 2%/± 1 V

Feeding voltage range for POTS/ISDN APs

Measuring point Feeding voltage range

a-wire to b-wire The feeding voltage measurement measures all AC and DC feeding
and foreign voltages in the inward (facility) direction.
The feeding voltage measurement in reverse polarity mode delivers
a result which differs in respect to the sign from the measurement
in normal polarity mode.

Insulation and loop resistance measurements of a/b-wire of a drop

Measuring point Ranges for Ranges for Relative/absolute tolerance

drops POTS/ drops xDSL POTS/ISDN/xDSL
ISDN
a-wire to earth 0 - 16 MΩ 0 - 3 MΩ absolute tolerance:
0 - 1 kΩ ± 100 Ω
relative tolerance for POTS
b-wire to earth 0 - 16 MΩ 0 - 3 MΩ drop:
1 kΩ - 5 kΩ ±10%
5 kΩ - 1 MΩ ± 5%
a-wire to b-wire (insulation) / 0 - 16 MΩ 0 - 3 MΩ
b-wire to a-wire (insulation) 1 MΩ - 5 MΩ ±10%
5 MΩ - 10 MΩ ±20%
10 MΩ - 16 MΩ ±40%
a-wire/b-wire to earth 0 - 8 MΩ 0 - 3 MΩ relative tolerance for
xHDSL/ISDN drop:
1 kΩ - 5 kΩ ±10%
a-wire to battery 0 - 16 MΩ 0 - 3 MΩ 5 kΩ - 200 kΩ ± 5%
200 kΩ - 1 MΩ ±10%
1 MΩ - 2 MΩ ±20%
b-wire to battery 0 - 16 MΩ 0 - 3 MΩ
2 MΩ - 3 MΩ ±40%
3 MΩ - 16 MΩ not defined
a-wire to b-wire (loop) 0 - 2 kΩ 0 - 2 kΩ Tolerance for loop resistance:
0 - 500 Ω: ± 100 Ω
500 Ω - 10 kΩ: 5%
> 2 kΩ not applicable

Capacitance measurements

Measuring point Capacitance range Relative/absolute tolerance

a-wire to earth 20 nF - 9 µF relative tolerance over complete
range: ± 10%
b-wire to earth 20 nF - 9 µF
absolute tolerance over
a-wire to b-wire 20 nF - 9 µF complete range: ± 20 nF

Distance to open measurement for a specified drop

Measuring point Range Relative/absolute tolerance

distance to open 0.5 km - 20 km ± 10% (1)
lowest measured capacitance of 20 nF - 9 µF
a-wire or b-wire to earth

Notes:
1. The accuracy of the average line capacity per length has a direct impact on the result. As this value could
have a tolerance of 30% the result of the DIS will be approximately 30% - 40%.

Detection test of a test termination

Customer-side Application
master line jack pack
a-wire

b-wire

Initiation of the detection test

The detection test of the test termination checks the existence of a diode by measuring
the resistance in forward and backward direction ″a-wire to b-wire″ and ″b-wire to
a-wire″. The TAP10x/LPZ200 is prepared for these measurements and if a significant
difference is detected between the two measurements the existence of the diode is
assumed. Furthermore the lower measured resistance value of the two measurements
must be between approximately 200 KΩ and 500 KΩ to assume the existence of a test
termination resistor. If both tests are successful the detection test delivers a positive test
result via GSI/EMS.
If the detection test of the test termination delivers a negative test result this may be
caused by
• other subscriber line faults like broken wire, short circuit between wires and so on
• connected phone of POTS line is off-hook
• ISDN BRA lines with an installed NT1 on the customer side
• no installed test termination
• ADSL splitters with central office splitter signature or remote terminal signature.
If the detection test fails the operator may check the subscriber line for fault conditions
via the existing integrated test and measurement procedures.

Draw and break dial tone test

Draw dial tone test

The TAP10x/LPZ200 is connected to the specified drop (subdrop) of a POTS AP. The
TAP10x/LPZ200 generates an off-hook towards the exchange and measures how long
it takes to get a dial tone (draw dial tone test). If a dial tone is found, the
TAP10x/LPZ200 simulates dialing of the CPE by performing pulse dialing of a single
digit and then determines how long it takes for the dial tone to disappear (break dial
tone test).
The draw dial tone test analyses the received tone, if any, and delivers as test result:
• Time in milliseconds until a tone was detected
• Analysis whether the dial tone delay time was good, slow or failed
• Analysis whether the received tone was a dial tone, some other tone or no tone
(LPZ200 or TAP100B or higher needed).
The specification of a valid dial tone is stored as customer specific data within the
AnyMedia ® Access System and can be tailored to the customer needs. The tone
analysis of the system supports the detection of steady dial tones with 1 to 3
simultaneous frequencies. A dial tone is only detected when present for a customer
specified duration.

Break dial tone test

The break dial tone test can be executed if a ″dial tone″ or ″other tone″ is detected.
The break dial tone test will report success, if AC energy disappears within a specified
time (default 1s) otherwise it reports a failure.

DTMF, pulse character or register recall (hook flash) test

Sending of test tone for POTS CPE

Ringing test for POTS CPE

CRC tests for ISDN application packs

CRC test on U interface

The CRC test checks the proper working of the CRC generator and detector of the
U interface, applicable for 2B1Q. This test requires interworking with the NT1. To
check both sides two modes of CRC test have been developed:
• Upstream direction
This test checks whether the CRC evaluation works properly. The test invokes the
NT1 to send corrupt CRCs in each superframe towards the network (upstream
direction) for a specified time period. The LT counts the number of corrupt CRCs.
The number of corrupt CRCs is reported to the GSI/EMS.
• Downstream direction
This test checks whether the CRC evaluation works properly. The test invokes the
LT to send corrupt CRCs in each superframe towards the NT1 (downstream
direction) for a specified time period. The NT1 reports the CRC errors back to the
LT via the FEBE bit in the maintenance channel. The number of corrupt CRCs is
reported to the GSI/EMS.

Sending a single pulse

NT1 detection test

Noise measurement on a subscriber line

Subscriber AP Test AP

Z-port

Filter

Test setup wiring

Termination at subscriber side

Loop current measurement

Subscriber AP Test AP

SLIC
Z-port

Test setup wiring

to CPE

• Split to Facility: The loop current measurement is performed on a simulated test

line while the application pack circuitry is feeding the line (see the figure below).
This simulated test loop is provided by the TAP100B/TAP101/LPZ200 and
switched onto the port circuitry during the test. This measurement is service
affecting.
The following figure shows the loop current measurement with simulated test line

Subscriber AP Test AP

Z-port

Sim. line
Test setup wiring

to CPE

Tone measurement
...................................................................................................................................................................................................................................
The tone measurement is a means to determine the attenuation of a subscriber line at
specific frequencies. For this measurement additional test equipment is attached to the
far end of the subscriber line (see the figure below). This equipment inserts a steady
tone at a specific frequency and power level. This tone is then measured by the
TAP100B/TAP101/LPZ200 in the system and delivers as test result the detected
frequency and power level of the most significant tone on the subscriber line.
Important! This measurement is designed for frequencies in the normal voice band
and not for wideband frequencies.
The following figure shows the setup (schematic) for tone measurement

Subscriber AP Test AP

Z-port

Tone
detector

Test setup wiring

Tone generator at subscriber side

Howler tone on demand on POTS drops in reduced battery

state
...................................................................................................................................................................................................................................

Overview
Via TL1 command a customer specific howler tone on a drop (subdrop) which serves a
switched POTS subscriber can be sent. The sending of the howler tone is not signalled
in any way to the connected exchange.
This howler tone sending does not require a test application pack or explicit test
session setup via command CONN-TACC-DROP. Even the related line termination and
drop remain in normal operation as no implicit test session is set up for sending the
howler tone.

Initiation of howler tone

The howler tone can only be applied and initiated locally or remotely via GSI/EMS if
the drop (subdrop) is in reduced battery state, otherwise the TL1 command is denied. It
can be specified whether the howler tone will be sent as long the reduced battery state
persists or terminated earlier after a given maximum time. The tone can also always be
terminated on operator request via TL1 command.

Reduced battery state

The reduced battery state is defined only for switched POTS lines. This state is entered
(on request by the switch via a V5 message) if a subscriber line is detected which is in
steady off-hook state. In this state, also called Line Lock Out or Parking state, the
feeding to the subscriber line is reduced to a minimum and no service is active. Only
an on-hook detection is enabled on the application pack to recognize the termination of
the steady off-hook condition to return to normal service. Whether a drop is in reduced
battery state can be retrieved by TL1 command.

Quick line test

Overview
The quick line test is no additional test capability but a configurable collection of other
tests which are performed with only one command invocation. This method reduces the
TL1 message overhead.

Test capabilities
The quick line test command sequentially executes the requested subtests and delivers
the individual subtest results line by line back to the operator interface. The test
capabilities of the individual subtests are the same as at the single test invocation
method. For the quick line test the same restrictions as defined for the individual tests
are obeyed by the system. Contrary to the single test invocation method, where the test
command is denied in failure cases, the quick line test command is not denied if a
subtest fails. Instead the command executes successfully but the specific subtest is not
executed while still executing all other requested subtests.

Implicit test session

The quick line test command establishes an implicit test session eliminating the need to
setup an explicit test session via command CONN-TACC-DROP. The implicit test
session blocks any switched line under test for all subtests but also automatically
unblocks the line if an inward draw with or without break dial tone subtest is
requested. The draw with or without break dial tone test is always performed as last
subtest if it is requested in combination with other subtests. This subtest ordering
reduces the likelihood of interfering activities on the subscriber port.

Configurable subtests
The following subtests are configurable via the quick line test command:
• Foreign voltage (outward)
• Feeding and foreign voltage (inward)
• Feeding and foreign voltage (inward with reverse polarity)
• Insulation resistance
• Loop resistance (only a to b)
• Short versus off-hook detection
• Capacitance
• Distance to open
• Draw with or without break dialtone
• Master line jack detection
• Noise level
• Loop current (inward)

• Loop current (outward)

• Tone frequency and level detection.

Deny of subtests
If a requested subtest is not supported by the application pack of the line under test,
not allowed due to the line configuration, or fails for any other reason then only the
subtest type parameter with an additional information about the failure reason is
delivered while still executing the other requested subtests.
Deny reasons for subtests of the quick line test

Subtest Condition Reason for deny

All operational test failure delivered drop is not suitable for testing
from TAP10x/LPZ200
Feeding voltage (inward) LPZ12x, LPZ640, LPS50x, no inward test access available
LPS510, BBP
Feeding voltage (inward) LPU508 test not allowed for application
pack type
Feeding voltage (inward with LPZ12x, LPZ640, LPS50x, no inward test access available
reverse polarity) LPS510, BBP
Feeding voltage (inward with LPU112, LPU132, LPU430, test not allowed for application
reverse polarity) LPU432, LPU508 pack type
Feeding voltage (inward with analog leased line service served line termination of drop
reverse polarity) does not allow test
Loop resistance LPU112, LPU132, LPU430, test not allowed for application
LPU432, LPU508, LPS50x, pack type
LPS510
Off-hook versus short LPU112, LPU132, LPU430, test not allowed for application
LPU432, LPU508, LPS50x, pack type
LPS510
Loop current (inward) LPZ12x, LPZ640 no inward test access available
Loop current (inward) LPU112, LPU132, LPU430, test not allowed for application
LPU432, LPS50x, LPS510, pack type
BBP
Loop current (outward) LPU112, LPU132, LPU430, test not allowed for application
LPU432, LPU508, LPS50x, pack type
LPS510, BBP
Draw with or without break LPZ12x, LPZ640 no inward test access available
dialtone
Draw with or without break LPU112, LPU132, LPU430, test not allowed for application
dialtone LPU432, LPU508, LPS50x, pack type
LPS510, BBP

Subtest Condition Reason for deny

Draw with or without break no service provisioned served line termination of drop
dialtone does not allow test
Draw with or without break analog leased line service served line termination of drop
dialtone does not allow test
Loop resistance analog leased line service served line termination of drop
does not allow test
Off-hook versus short analog leased line service served line termination of drop
does not allow test

Talk to subscriber test session

Overview
It is possible to setup a test session, that allows the operator to talk to the subscriber
under test between the actual measurements. For that purpose a virtual POTS line must
be provisioned once. From the network point of view this virtual POTS line entity is a
normal V5.x POTS subscriber while in the system this subscriber is terminated on the
COMDAC and is not using any physical port on an application pack.
The talk to subscriber test session can be initiated locally or remotely via GSI/EMS
operations or TL1 commands, which specify a call-in talk voice path of a virtual POTS
line for integrated metallic line testing.

Test session ″Talk″

For talking to the subscriber under test between the actual measurements, a test session
of mode ″Talk″ has to be setup with a TL1 command, which specifies the physical port
under test. If such a test session is active the virtual subscriber can be called to
establish a talk voice path to the subscriber under test. The call will be answered by
the system and kept on hold until the request to alert the subscriber under test by a
subsequent TL1 command. Once the subscriber under test goes off-hook the voice path
is connected to the subscriber under test. All supported measurements can be
performed. During a measurement the voice path will be temporarily put on hold and
automatically re-established after the measurement.

Loopbacks
...................................................................................................................................................................................................................................

Overview
This section describes the types of loopbacks required for line test and measurement
purposes for the AnyMedia ® Access System.

Fault location
The reason for loopbacks is to test whether a fault has occurred in a facility (for
example in the E1 connection between service node and system). The loopbacks can be
conducted to sectionalize and locate the fault.

Initialization
The loopback control is done either remotely from an EMS or locally at the system
from the GSI but in any case the service node maintenance personnel is not informed
of an E1 loopback. This maintenance action is applicable when a system installed with
a TDM COMDAC is being initially turned up or if an E1 is not connected to a service
node.
Important! When E1s are connected to a service node coordination with the
service node staff is required if an E1 loopback is initiated.

Loopbacks at the E1 link side

E1 line loopbacks
The AnyMedia ® Access System supports E1 line loopbacks (not for V3 application
modes). E1 line loopbacks are executed by TL1 command.
A line loopback (see the figure below) loops the entire received E1 signal without
clock recovery back onto the transmit path. The received data are continuously sent to
the downstream direction. The normal transmit path (system upstream) is disconnected.
The following figure shows a E1 line loopback

Receivee Data
Receiv
Continue
Continue Framing and
D ownstream Payload Looped
Payload
E1 link

Loopbacks at the U interface (subscriber side)

U interface loopbacks
The ISDN AP supports different loopbacks (1, 1A, and 2) for diagnostic tests in the
transmission section from LT to NT1. They are used to examine different sections of
the access transmission system (ATS). Besides the activation via GSI/EMS U interface
loopbacks can be invoked autonomously by the system after U interface fault in the
case of ISDN BRA.
The figures below show the location of the loopbacks.
Location of U interface loopbacks related to NT

AnyMedia Access System

G.703
ISDN AP
2 Mbps
REG (E1)
NT11
NT NT1
or LT
TE
ITEs
optional
S/T interface U interface U interface

Loopback 2 Loopback 1A Loopback 1

Location of U interface loopbacks related to managed NTU

Loopback 2 Loopback 1A Loopback 1 Loopback 2

U interface loopback types related to NT

Loopback 1 and 1A are closed as near to the U interface as possible. Loopback 2 is
closed as near to the S/T interface as possible. The request for loopback 1A activation
and loopback 2 activation is transported via EOC channel (embedded in the
maintenance channel) for 2B1Q U interface and via maintenance channel for 4B3T U
...................................................................................................................................................................................................................................
363-211-586 3-143
Issue 6, July 2007
OAM&P for narrowband services Loopbacks at the U interface (subscriber side)

interface to the NT/REG (Regenerator)/ITE (Intermediate Transmission Element). Due

to this reason transmission of EOC channel or maintenance channel respectively over
the ATS must be possible. This is fulfilled when the U interface is activated.
Activation of the S/T interface is not necessary for loopbacks.

U interface loop back types related to managed NTU

The request for local/remote loopback 2 activation is transported via D-channel to the
managed NTU connected to AnyMedia ® Access System. The managed NTU performs
either the local loopback 2 itself or sends the (remote) loopback 2 request according to
the V.54 inband protocol to the managed NTU at the far end. The managed NTU loops
the data during loopback 2 to the network side and the subscriber side (TE).

U interface loopback properties

Depending on service states and provisioning, the loopbacks (loopback 1, 1A and 2)
may have the following properties:
• Loopbacks on U ports, which serve operational DLL service (IS) are called
transparent. In this case the cross-connection between the E1 link timeslots and the
U port is established.
For transparent loopbacks the transmission path between the U port and the E1
timeslots is transparent (TSI connection established, but only possible if the
cross-connection at the service assignment layer is provisioned). With this feature
the quality of the transmission path can be evaluated at the far subscriber side of a
DLL service.
• Loopbacks on U ports, which serve ISDN BRA service or no service (OOS) are
called non-transparent.
For non-transparent loopbacks there is no TSI connection. The transmission path
between the U port and the E1 timeslots is released.

Blocking and non blocking loopbacks

For ISDN BRA service the AnyMedia ® Access System does or does not request
blocking of the ISDN BRA subscriber towards the LE, dependent on the parameter
blocking control (blocking/non blocking) given with the TL1 command to invoke the
loopback. A loopback is only transparent, if the ISDN BRA subscriber is not blocked
towards the LE and a V5 time slot(s) is allocated for the ISDN BRA subscriber. A
loopback with the parameter blocking control set to non blocking is denied, if the
U port is disabled due to any reason (for example if the ISDN BRA subscriber is out
of service (OOS), if the ISDN BRA subscriber is blocked by the LE, if the V5.x
interface is not operational, or if the administrative service state of the ISDN AP is
OOS).
Transmission path (ISDN BRA service) with a test pattern inserted in the LE

AnyMedia Access System LE

PBRS BER
Gen. Meter
ISDN AP

NT REG LT
LT
TE

optional
S/T interface U interface U interface V5.x interface

Loopback 2 Loopback 1A Loopback 1

BER test during loopbacks on LPU508

The TSI on the ISDN AP LPU508 is used to inject/monitor PRBS test patterns during
loopbacks towards the network. These tests always disrupt normal payload traffic and
can be run in two modes, see the figure below. Additionally it can be selected whether
the BER test is to be performed on one B-channel or on both B-channels (B1, B2 or
B1 + B2). During the tests, results are accumulated continuously and are reported in
certain time intervals.
The LPU508 reports BER results every 10 seconds to the COMDAC. Due to TSI
limitations only one BER test per LPU508 can be enabled at any given time.
The following figure shows the ISDN BER test on LPU508 during loopback towards
the network.

Subscriber side Network side

AnyMedia shelf

NT ISDN AP LPU508

TSI
PRBS
TE
BER meter

Application interface TCM U-interface

(S/T, a/b
RS232, USB)

Loopback 2 Loopback 1

Pseudo Random Bit Pattern

Loopbacks at the HDSL interface

HDSL interface loopbacks

Possible HDSL interface loopbacks are located on the HDSL ports (loopback 1) and
on the application interface (loopback 2) of the Network Termination Unit (NTU). The
loopbacks are initiated by the operator from the GSI/EMS by a TL1 command with the
following parameters:
• Loopback location (loopback 1 or loopback 2)
• Loopback with or without BER testing.
The HDSL interface loopbacks are reflected in service states of the equipment layer
and lines layer model. The relevant service states for V5 ISDN PRA, VLL, GLL,
UVLL and UGLL service are IS-TST or OOS-TST.
Important! If an HDSL logical interface is provisioned in V3 point-to-point mode,
the loopback 1 and the loopback 2 can’t be initiated by the operator from the
GSI/EMS. The loopback 1 at the HDSL AP and the loopback 2 at the NTU are
controlled by the LE via A-bit and Sa5-/Sa6-bits in timeslot 0 of the 2Mbps bit
stream. For a successfully closed loopback an event is reported to the GSI/EMS.
During loopback 1 and loopback 2 in V3 point-to-point mode no change of the
service state takes place.

Application modes for HDSL loopbacks

Depending on the application mode in which the HDSL interface is operating, there
exists a different set of loopbacks which can be activated from the HDSL AP, that
means from the Line Termination Unit (LTU). Following application modes for HDSL
loopbacks are possible:
• HDSL loopbacks in point-to-point mode / V3 point-to-point mode / unstructured
point-to-point mode
• HDSL loopbacks in single pair mode
• HDSL loopbacks in point-to-multipoint mode
• HDSL loopbacks including BER test.
The figures below show the location of the HDSL loopbacks for these application
modes.
HDSL loopbacks in point-to-point mode / V3 point-to-point mode / unstructured
point-to-point mode

Subscriber side Network side

AnyMedia shelf

NTU HDSL AP(LTU)

HDSL pair 1 2
G.703
TRCVR1 TRCVR1 2 Mbps
(E1)
TE
HDSL pair 2 2
TRCVR2
TRCVR2

Application interface
(V.35, V.36, X.21,
G.703)
Loopback 2 Loopback 1

HDSL loopbacks in single pair mode

Subscriber side Network side

AnyMedia shelf

NTU HDSL AP (LTU)

HDSL pair 1 G.703
2
TRCVR1 TRCVR1 2 Mbps
(E1)
TE
TRCVR2
TRCVR2

Application interface
(V.35, V.36, X.21
G.703)
Loopback 2 Loopback 1

HDSL loopbacks in point-to-multipoint mode

NTU HDSL pair 2

TRCVR1

TE
TRCVR2

Application interface
(V.35, V.36, X.21
G.703)
Loopback 2 Loopback 1

HDSL interface loopback types

The loopback 1 is closed as near to HDSL interface as possible on the HDSL AP. The
whole HDSL frames of both transceivers (TRCVR1/2) from the HDSL AP are included
in loopback 1 (point-to-point mode, point-to-multipoint mode). An individual loopback
1 on one HDSL transceiver is not possible in these modes. In single pair mode the
HDSL frames of TRCVR1 are in loopback 1.
The loopback 2 is closed as near to the application interface as possible in the NTU. In
point-to-point mode the data from both HDSL pairs are loopbacked. In
point-to-multipoint mode it is possible to loopback the data transmitted over HDSL
pair 1 or HDSL pair 2. Additional the data from both HDSL pairs can be loopbacked.
In single pair mode the timeslots transmitted over HDSL pair 1 are included in
loopback 2.

HDSL BER test during loopbacks

The HDSL AP provides a mechanism for validating the circuit utilizing a
2 Mbps PRBS generator and BER meter (see the figure below). This diagnostic test
disrupt the normal flow of payload traffic to the HDSL AP and requires a loopback.
The test runs at a full 2 Mbps rate. The BER results are accumulated continuously and
are reported. The HDSL BER test for loopbacks of type 2 is possible in point-to-point
mode, unstructured point-to-point mode, or if no HDSL interface is provisioned.

The following figure shows the HDSL BER test during loopback at NTU in
point-to-point mode

Subscriber side Network side

AnyMedia shelf

NTU HDSL AP (LTU)

G.703
HDSL pair 1 2
TRCVR1 TRCVR1 2 Mbps
PRBS
(E1)
TE
BER meter
TRCVR2 TRCVR2
HDSL pair 2 2

Application interface
(V.35, V.36, X.21
G.703)

Loopback 2 Loopback 1

HDSL loopbacks invocation

Loopbacks are invoked with the HDSL drop access identifier. Due to the fact that
loopbacks invoke partly the whole HDSL interface (two HDSL ports) during the
loopback, the second HDSL port of the HDSL interface is included automatically in
the loopback. This depends on the application mode and the location of the loopback
(see the figures above). Also multiple services at the lines layer can be included in the
test (one V5 ISDN PRA service and up to two n × 64 kbps digital leased line
services).
Any loopback which involve both HDSL ports can be installed via each of the both
HDSL ports. The same is valid for release of these loopbacks.

HDSL interface loopback properties

Depending on service states and provisioning, the loopbacks (loopback 1 and 2) may
have the following properties:
• Transparent loopbacks
This kind of loopback is used for V3 ISDN PRA subscribers and for n × 64 kbps
digital leased line subscribers with primary service state IS. For transparent
loopbacks the transmission path between the network interface (E1 interface) and
the HDSL AP is not broken. The cross-connection on the COMDAC is still
established.
• Non-transparent loopbacks

For non-transparent loopbacks the TSI connection is broken. The non-transparent

loopback mode depends on provisioned service, the primary service state of the
lines layer and the availability of cross-connection. Following non-transparent
loopbacks for HDSL pairs are used:
– Loopbacks which are provisioned for n × 64 kbps digital leased line service
and primary state of lines layer is OOS.
– Loopbacks which are provisioned for V5 ISDN PRA service.
– Loopbacks which carry no service.
In the 64 kbps timeslots towards the network side AIS is inserted.
Important! A non-transparent loopback is setup for an HDSL interface operating
in unstructured mode if the HDSL interface is not active at the time of receiving
the loop request.

Loopbacks at the SHDSL port

SHDSL port loopbacks

The SHDSL AP supports different loopbacks for diagnostic tests in the transmission
section from LTU to NTU. The loopbacks are located on the SHDSL ports (loopback
1) and on the NTU (loopback 2). They are used to examine different sections of the
transmission system. The SHDSL port loopbacks are closed either towards the network
or towards the subscriber. The loopbacks are initiated by the operator from the
GSI/EMS by a TL1 command with the following parameters:
• Loopback location (loopback 1 or loopback 2) and loopback direction (towards
network or towards subscriber)
• Loopback with or without BER testing. BER testing is only supported for
loopbacks towards the network.
The SHDSL port loopbacks are reflected in service states of the equipment layer and
lines layer model. The relevant service states for V5 ISDN PRA, ULL or n × 64 DLL
service are IS-TST or OOS-TST.
Important! The SHDSL port loopbacks initiated by the operator are rejected, if
the V3 ISDN PRA service is provisioned on top of the SHDSL port. For the V3
ISDN PRA service the SHDSL port loopbacks are controlled via Sa6 bits from the
LE and are only possible towards the network.

SHDSL loopbacks without BER testing

Subscriber side Network side

AnyMedia Shelf

SHDSL AP
NTU SHDSL pair 1 (LTU)
2 G.703
2 Mbps
pair 2...7 (E1)
TE
SHDSL pair 8 2

E1
E2
AP E1 ports E3
Application interface
(V.35, V.36, X.21 E4
G.703)

Loopback 2 Loopback 1
towards towards towards towards
subscriber network subscriber network

The SHDSL loopbacks without BER testing can be performed in the direction towards
the network and towards the subscriber. Loopback 1 and loopback 2 can be used.

The loopback 1 is closed on the SHDSL AP. The whole SHDSL frame is looped in
loopback 1.
The loopback 2 is closed on the NTU. The whole SHDSL frame is looped in loopback
2.

SHDSL loopback properties

Depending on service states and provisioning, the loopbacks (loopback 1 and 2) may
have the following properties:
• Transparent loopbacks towards the network
This kind of loopback is used for V3 ISDN PRA subscribers and for n × 64 kbps
DLL subscribers with primary service state of lines layer is IS.
For transparent loopbacks the transmission path between the network interface (E1
interface) and the SHDSL AP is not broken. The cross-connection on the
COMDAC is still established.
• Partly transparent loopbacks towards the network
Due to the fact that an HDSL interface can carry V5 ISDN PRA and n × 64 kbps
DLL service, partly transparent loopbacks towards the network are possible. The
cross-connection for n × 64 kbps DLL service remains, whose primary state of
lines layer is IS. The other cross-connections are broken. In the broken 64 kbps
timeslots towards the network side AIS is inserted.
Important! Partly transparent loopbacks are not supported in ULL modes.
• Non-transparent loopbacks towards the network
For non-transparent loopbacks the TSI connection is broken. The non-transparent
loopback mode depends on provisioned service, the primary service state of the
lines layer and the availability of cross-connection. Following non-transparent
loopbacks for SHDSL pairs are used:
– Loopbacks for ports which are provisioned for ULL or n × 64 kbps DLL
service and primary state of lines layer is OOS.
– Loopbacks for ports which are provisioned for V5 ISDN PRA service.
– Loopbacks for ports which carry no service.
Important! In the 64 kbps timeslots towards the network side AIS is inserted.
• Loopbacks towards the subscriber
Loopbacks towards the subscriber are mainly needed during subscriber line
installation. The maintenance personnel on subscribers site wants to verify, whether
the SHDSL line is installed correct or not. For this purpose a SHDSL loopback
towards the subscriber is closed. The data stream inserted at the application
interface of SHDSL modem is either loopbacked at the SHDSL modem (loopback
2) or at the SHDSL AP (loopback 1). When one of these loopbacks is active the
data stream inserted at the application interface is received at the application
interface. This way the maintenance personnel can verify, whether the SHDSL
subscriber line is installed correct or not. The loopbacks towards the subscriber are
invoked via TL1 command interface from GSI/EMS.
Important! During a loopback towards the subscriber AIS is inserted in upstream
direction from the location of the loopback towards the network.
....................................................................................................................................................................................................................................
3-152 363-211-586
Issue 6, July 2007
OAM&P for narrowband services Loopbacks at the SHDSL port

SHDSL BER test during loopbacks towards network

The TSI on the SHDSL AP is used to inject/monitor PRBS test patterns during SHDSL
loopbacks towards the network. These tests always disrupt normal payload traffic and
can be run in both modes, see the figure below. During the tests, results are
accumulated continuously and are reported in certain time intervals.
The SHDSL AP reports BER results every 10 seconds to the COMDAC. The reporting
interval can be configured from the COMDAC if required, to any time between 1
second and 31 seconds.
The BER testing is stopped before the loopback is released. Due to TSI limitations
only one BER test per SHDSL AP can be enabled at any given time. The baud rate
used for testing depends on the provisioned application mode. If a logical interface is
not provisioned, the HDSL interface is tested in unstructured mode.
The following figure shows the SHDSL BER test during loopback towards the
network.

Subscriber side Network side

AnyMedia shelf

NTU SHDSL AP (LTU)

G.703
SHDSL TX TSI
2 Mbps
PRBS (E1)
TE
BER meter
SHDSL RX

Application interface
(V.35, V.36, X.21
G.703)

Loopback 2 Loopback 1

SHDSL loopbacks invocation

The SHDSL loopbacks are invoked
• via GSI/EMS with the SHDSL port access identifier for no service, V5 ISDN PRA
service or n × 64 kbps DLL services provisioned on top of SHDSL port. The
invocation depends on the application mode and the location of the loopback (see
“SHDSL loopbacks without BER testing” (p. 3-151))
or
• via Sa6 bit from the LE for V3 ISDN PRA service provisioned on top of
SHDSL port. Nevertheless the AnyMedia ® Access System reports a successful
closed loopback. It is also reported, whether the loopback is closed at the NTU
(loopback 2) or locally on SHDSL AP (loopback 1).

BER testing with external loopback devices

The SHDSL AP inserts on request from the COMDAC in all timeslots of the
concerning subscriber service a pseudo random bit sequence (PRBS) in downstream
direction (The PRBS has a length of 215-1 and is according to ITU O.151). If the
external loopback is in place, the PRBS is loopbacked in upstream direction and is
evaluated by the BER meter on the SHDSL AP. A BER test on the G.703 interface of
the SHDSL NTU is non service affecting for a service on the V.35/V.36/X.21 interface
of the same SHDSL NTU and vice versa.

Subscriber line test via external test head

Testing environment
The main components of this test environment are:
• Test system controller (TSC)
• External test head (RTU, remote test unit)
• AnyMedia ® Access System with CIU, TAP connector and RTU connector on the
connector field/shelf connection panel (SCP).

Testing assumption
The RTU is connected to the TSC which coordinates and controls the RTU tests. The
type of this connection is beyond the scope of this document and depends on the
capabilities of the RTU and the location of the system. Possible connections are via a
modem dial-up connection, serial link, LAN, et cetera.
The AnyMedia ® Access System provides a test capability to the RTU via TL1
commands which switch a loop at the TAP-B interface. This loop enables the RTU to
verify the correct test access cabling between the RTU and the system.
This infrastructure is described and defined in “Subscriber line test via external test
head” (p. 3-155).

AP test access capabilities

Due to hardware restrictions of some AP types not all test access modes can be
supported by the AnyMedia ® Access System. The following table describes the test
access capabilities of the APs. The ″Full″ in the split access column means that both
equipment and facility pair are accessible at the same time, whereas ″Half″ means that
only one pair is accessible at the same time.
Application pack test access capabilities

AP Type Equipment Facility Bridged Split Comments

Pair Pair Access Access
LPP100/ yes yes yes Full Facility pair supports enabled
LPZ100/ port but without incoming
LPZ110/ ringing.
LPZ200/
LPZ641/
LPA832/
LPA833
...................................................................................................................................................................................................................................
363-211-586 3-155
Issue 6, July 2007
OAM&P for narrowband services Subscriber line test via external test head

AP Type Equipment Facility Bridged Split Comments

Pair Pair Access Access
LPZ12x/ yes no no Half Facility pair supports enabled
LPZ640 port but without incoming
ringing.
LPU112/ yes yes no Half Split access to equipment pair
LPU132/ is possible.
LPU430/ Port is always disabled
LPU432/ during test access.
LPU508
LPS504/ no
LPS510
LPA416/ yes no no Half Only split access to
LPA417/ equipment pair. Facility pair
LPA432/ is not accessible at all.
LPA434/
LPS702/
LPS716

Fault handling
The fault handling is performed during an active RTU test session for all involved
equipment in the test access path. This includes the AP of the subscriber line under test
and the CIU. Any fault of this equipment releases an active RTU test session. This
autonomous release of the RTU test session switches all test relays on the CIU to their
normal operation mode and returns the subscriber line back to normal operation. The
RTU test session is not resumed if the fault condition is cleared, and has to be set up
again.

Performance management

Purpose
This section describes the performance management capabilities of the AnyMedia ®
Access System regarding the narrowband services.

Contents

Performance management definitions 3-158

Performance management data 3-160
Performance management operations 3-162
V5.2 protocol error logging 3-163
Traffic statistics and COMDAC load measurement 3-166
Measurement data collection 3-167
Measurement types 3-168
Post-processing and presentation 3-170

Performance management definitions

Definition
Performance management is a generic term which involves the identification and
rectification of problems and faults within a network. Measurements are generally
taken either by interrupting the service and running pseudo-random bit patterns over
the connection path, or by using non-intrusive error checking mechanisms over blocks
of the data. Non-intrusive measurements are typically done over a single link on a path
(for example a copper cable), where the underlying (data link layer) protocol reports
that a block has been errored.

Bit error versus block errors

If a customer has a data connection from one premises to another via third-party
equipment (for example via the PSTN or a dedicated digital network), then he will
want to be assured that the data connection is of a certain quality, preferable in terms
of a bit error rate measure. The customer (or the network managers) can easily
determine the bit error rate at any time by interrupting the service and sending
pseudo-random bit sequences, and then observing the data at another point. While this
is a suitable method to use when installing equipment or if a fault has occurred, it is
not a viable way to do continuous monitoring of a service.
The alternative is to measure errors in-service, by monitoring errors on a block of data.
For example, a G.704 service can provide reports of CRC-4 errors over an 8-frame
multiframe (2048 bits). Note, however, that this will report that one or more bits out of
the 2048 bit block was errored, which is not the same as measuring the number of bits
in error. The relationship between block errors and bit errors is not linear, as the
temporal distribution of the bit errors which cause the block errors cannot be assumed
to be uniform.
The measurement of performance using block errors is widely used for in-service
monitoring, and is used in the AnyMedia ® Access System.

Monitoring of transmission quality

Performance management in the AnyMedia ® Access System deals moreover with the
monitoring of transmission quality of E1 links, U interfaces, or [S]HDSL lines, and the
generation of threshold crossing alerts (TCAs).
Performance monitoring is classified as reactive maintenance since the information
which is supplied aids in detecting faults which degrade the monitored signals and
which may worsen and cause a hard fault. Performance monitoring information can
also be used for tracking the quality of the service provided on the network, and for
verifying subscriber complaints.

Link versus path statistics

A data connection between two points may traverse a number of nodes and links (for
example CPE to AnyMedia ® Access System to local exchange to a second exchange to
another CPE). The end-user customer is interested in the quality of the whole path of
its connection, and not in the intermediate links and equipment. The network manager,
however, is more interested in maintaining the links between the various pieces of
network equipment because if these are all of satisfactory quality, then an individual
connection will probably also be of suitable quality.
In order to do full-path performance statistics in-service (rather than using
out-of-service bit error rate equipment as described earlier), it is necessary to have
some sort of overhead data sent with the customer data. Although this is done for
individual links (for example an HDSL link from the AnyMedia ® Access System node
to the CPE), these protocols do not operate over the node and so end-to-end statistics
are not available. If a customer is running a higher-level protocol over its connection
(for example IP), then within the IP stack there is the facility to monitor connection
quality.
Performance management on the AnyMedia ® Access System is essentially link-based,
and operates on block errors reported by the low-level protocol on the link (for
example HDSL CRC-6, G.704 CRC-4, and so on). This means that the statistics
operate on the link from the AnyMedia ® Access System node, through the physical
medium, until terminated on other equipment.
Important! In some circumstances, such as when multiple E1 ports are multiplexed
into a higher-order PDH link, the statistics will cover the path from the AnyMedia ®
Access System port to the far-end G.704 port; this may involve a number of hops
through the fiber network.

Link statistics
Link statistics measured on the AnyMedia ® Access System are a subset of those
described in the ITU recommendation G.826 and SHDSL parameters according to
G.991.2. Events are reported as described in M.2120.
The PM counts are reported for 15 minute and 24 hour time periods, and threshold
crossing reports are generated.
All thresholds are configurable via the TL1 interface on a per-port basis. It is also
possible to upload a limited amount of historical data stored on the AnyMedia ® Access
System node.

Performance management data

E1 links
The following performance management parameters are measured at the E1 links:
• High bit error ratio (HBER) on the implicated E1 link signal exceeds 10-3
• Low bit error ratio (LBER)
The LBER threshold value is provisionable.
Once a bit error ratio value exceeds a given threshold, an autonomous message is
generated to indicate a TCA.

U interfaces
The following performance management parameters are measured at the U interface:
• High bit error ratio (HBER) on the implicated U interface exceeds 10-3
• Low bit error ratio (LBER) on the implicated U interface exceeds 10-6.
Once a bit error ratio value exceeds a given threshold, an autonomous message is
generated to indicate a TCA.

HDSL lines
The following performance management parameters are measured at the HDSL line:
• High bit error ratio (HBER) on the 2-Mbps payload of the HDSL interface exceeds
10-3
• Low bit error ratio (LBER) on the 2-Mbps payload of the HDSL interface exceeds
10-6.
Once a bit error ratio value exceeds a given threshold, an autonomous message is
generated to indicate a TCA.
In addition the following performance management parameters are measured at the
HDSL line:
• ESL - errored seconds-line
• UASL - unavailable-seconds-line.

SHDSL lines
The following performance management parameters according to G.826 and G.991.2
are measured at the SHDSL line:
• High bit error ratio (HBER) on the SHDSL frame exceeds 10-3
• Low bit error ratio (LBER) on the SHDSL frame exceeds 10-6
• High bit error ratio (HBER) on the 2-Mbps payload of the HDSL interface exceeds
10-3
• Low bit error ratio (LBER) on the 2-Mbps payload of the HDSL interface exceeds
10-6.

Once a bit error ratio value exceeds a given threshold, an autonomous message is
generated to indicate a TCA.
In addition the following performance management parameters according to G.826 and
G.991.2 are measured at the SHDSL line:
• Related to G.826
– BBE-L - background block errors-line
– EBL - errored blocks-line
– ESL - errored seconds-line
– SESL - severely errored seconds-line
– UASL - unavailable-seconds-line.
• Related to G.991.2
– SNRML - signal to noise ratio (SNR) margin-low
– SNRMH - signal to noise ratio (SNR) margin-high
– LATTL - line attenuation-low
– LATTH - line attenuation-high
– PRL - power received-low
– PRH - power received-high
– NLL - noise level-low
– NLH - noise level-high.
For the G.826 parameters ESL and SESL and for the SNR margin an alarm with user
configurable threshold will be generated by the AnyMedia ® Access System, if a
statistic parameter crosses the threshold.

Performance management operations

E1 links
For the E1 links the following performance management operations are possible:
• Set and retrieve the threshold values for alarm generation
• Report the alarm concerning a threshold crossing.

U interfaces
For the U interfaces performance management operations consist of:
• Report the alarm concerning a threshold crossing.

HDSL interfaces
For the HDSL interfaces the following performance management operations are
possible:
• Enable/disable performance monitoring (collecting statistics and sending
autonomous reports)
• Control the detection and reporting of threshold crossing alerts (when a threshold is
exceeded a report event message is sent out)
• Control the reporting of unavailability alarms (when a period of unavailability
starts/stops a report alarm message is sent)
• Provision of performance monitoring start time
• Initialize of performance monitoring data registers and event counters
• Retrieve of performance monitoring data.

V5.2 protocol error logging

Protocol errors
The V5.2 standard defines V5.2 protocol errors for adverse conditions. The AnyMedia ®
Access System detects V5.2 protocol errors. Main V5.2 protocol errors are alarmed on
the GSI/EMS. Besides the main V5.2 protocol errors there are V5.2 protocol errors,
which are not alarmed immediately at their occurrence on the GSI/EMS. These V5.2
protocol errors are recorded for each V5.2 interface in a corresponding V5.2 protocol
error log. The following V5.2 protocol errors are recorded:
• V5.2 PSTN protocol errors
• BCC allocation rejects
• BCC de-allocation rejects.
V5.2 Protocol errors are recorded on the AnyMedia ® Access System for POTS
subscribers, SPALL subscribers, SPDLL subscribers, the SPLL ROC subscriber and the
VPLN subscriber. V5.2 Protocol errors for ISDN subscribers are not recorded.

V5.2 protocol error log per V5.2 interface

The V5.2 protocol errors above are recorded in the corresponding V5.2 protocol error
log. The content of the V5.2 protocol error logs is stored in volatile memory. The
concept of recording the V5.2 protocol errors does not impact system performance as
much as alarming each V5.2 protocol error on the GSI/EMS. Alarming of each V5.2
protocol error would lead to a flood of alarms on the GSI/EMS under adverse
conditions like
• LE and AN support different V5.2 protocol versions (V5.2 edition 1/V5.2 edition 2)
• LE and AN support different V5.2 country specific versions
• Different provisioning data in the LE and AN regarding
– V5 links
– V5 user ports
• Instable transmission links
• Overload conditions in the LE or AN.
V5.2 PSTN protocol errors and allocation/ de-allocation rejects are recorded in a
“non-wrap around” V5.2 protocol error log. The error recording is running as long as
the V5.2 protocol error log is not full. If the V5.2 protocol error log has exceeded a
certain fill level an alarm is raised. The fill level to be exceeded, at which the alarm is
raised, can be provisioned at the TL1 interface.
For each V5.2 PSTN protocol error and BCC allocation/de-allocation reject an entry is
made in the V5.2 protocol error log. Each entry in the V5.2 protocol error log has at
least sufficient information to identify the kind of V5.2 protocol error and the
concerned subscriber. Each entry has sufficient diagnostic information to identify the
V5.2 protocol error.

V5.2 protocol errors and measurement types

There exist about 20 V5.2 PSTN protocol errors and about 10 BCC allocation/de-
allocation reject reasons on the V5.2 interface. V5.2 PSTN errors and BCC
allocation/de-allocation reject reasons are categorized into different measurement types.
The measurement types are
• V5.2 PSTN protocol errors
– PSTN protocol time-outs
– PSTN message errors
• BCC allocation rejects
– V5 link error
– V5 port error
– data inconsistency
• BCC de-allocation rejects
– V5 link error
– V5 port error
– data inconsistency.
The V5.2 protocol errors are recorded for
• POTS subscribers (PSTN errors and BCC protocol rejects),
• the virtual POTS line termination (PSTN errors and BCC protocol rejects),
• single channel SPLL subscribers with Layer 3 address (BCC protocol rejects) and
• the ROC subscriber (BCC protocol rejects).

Enable/disable filter for measurement types per V5.2 interface

It is possible to enable/disable the recording of the V5.2 protocol errors per
measurement type. Enabling or disabling recording of each measurement type can be
provisioned on each V5.2 interface via the TL1 interface independently. If the
recording for a certain measurement type is enabled, then all V5 protocol errors of this
measurement type are recorded in the V5.2 protocol error log concerned. If the
recording for a certain measurement type is disabled, no V5.2 protocol errors of this
measurement type for the corresponding V5.2 interface are recorded. Changing the
recording of a measurement type from enable to disable or vice versa is only possible,
if the recording of the V5.2 protocol errors for the V5.2 interface concerned is not
started respectively stopped. By default recording is enabled for each measurement
type.

Start/stop recording V5.2 protocol errors per V5.2 interface

The recording of V5.2 protocol errors is started respectively stopped per V5.2 interface
via TL1 interface. If the recording of the V5.2 protocol errors for a V5.2 interface is
started, all V5.2 protocol error measurement types for which recording is enabled, are
recorded in the V5.2 protocol error log concerned. If the recording of the V5.2

protocol errors for a V5.2 interface is stopped, no V5.2 protocol errors are recorded in
the corresponding V5.2 protocol error log. This is independent of enable/disable
recording of a certain measurement type on the V5.2 interface.

V5.2 protocol error log alarming

When the V5.2 protocol error log of a V5.2 interface has exceeded a provisioned fill
level, a “V5.2 protocol error log threshold exceeded” alarm is raised. The alarm is
cleared manually via TL1 interface via one of the following actions:
1. TL1 command to clear V5.2 protocol error log content
2. TL1 command to clear the alarm
3. The fill level to raise the “V5.2 protocol error log threshold exceeded” alarm is
changed at the TL1 interface and the level is lower or equal the actual fill level.
If the alarm is cleared via the TL1 interface and the fill level is at or above the
provisioned threshold, then the “V5.2 protocol error log threshold exceeded” is raised
again, when the next V5.2 protocol error is recorded in the V5.2 protocol error log.

V5.2 protocol error log functions

The V5.2 protocol error log for a V5.2 interface is created by the system, if the V5.2
interface is provisioned by the operator for the first time. The V5.2 protocol error log
for a V5.2 interface is deleted by the system, if the V5.2 interface is deleted by the
operator. If the V5.2 protocol error log is created, by default no V5.2 protocol errors
are recorded. Firstly the operator has to provision, what measurement types should be
recorded and at which fill level the alarm “V5.2 protocol error log threshold exceeded”
is raised. If these V5.2 protocol error log parameters are provisioned, recording may be
started via TL1 interface. The whole content or the N entries of the V5.2 protocol error
log may be retrieved via TL1 interface. An existing alarm “V5.2 protocol error log
threshold exceeded” may be cleared at TL1 interface. The content of the V5.2 protocol
error log can be deleted at any time.
The list of actions on the V5.2 protocol error log at the TL1 interface are:
1. Start/stop recording of V5.2 protocol errors on a V5.2 interface
2. Enable/disable recording of V5.2 protocol errors of a certain measurement type
3. Clear V5.2 protocol error log content via TL1 interface
4. Retrieve V5.2 protocol error log content (last N events or the whole V5.2 protocol
error log content)
5. V5.2 protocol error log alarm clear with or without V5.2 protocol error log content
clear
6. Setting V5.2 protocol error log fill level at which an alarm is raised
7. V5.2 protocol error log parameter retrieval
• Fill level at which an alarm is raised
• Measurement type filter value
• Actual fill level.

Traffic statistics and COMDAC load measurement

Definition
Traffic statistics and COMDAC load measurement are carried out to observe the
effectiveness of the network element. They consist of a set of functions for collecting,
processing and administrating data reflecting the behavior of telephony calls or the
load of the COMDAC.
Measurement data collection is done in the COMDAC and post-processing and
presentation is to the GSI/EMS. For that reason the COMDAC is periodically polled
by the GSI/EMS. Further processing may be done in a traffic management system.
For traffic statistics and for COMDAC load measurement the following conditions
apply:
• V5 traffic statistics are supported for V5.2 POTS only
• V5 traffic statistics data are collected on a per V5.2 interface basis
• There are no C-channel measurements
• RTI traffic statistics data are collected on a per remote terminal interface (RTI)
basis
• RTI traffic statistics data are collected and retrievable only on the host terminal
• The traffic statistics data sum of all RTIs connected to a host terminal (with no
local subscribers) does not exactly match the corresponding V5 traffic statistics
count for all counters. V5 terminating call attempt failures due to V5 protocol
failures for example which prevent further call processing are not reflected in the
RTI failure counts.
• Traffic statistics data for local subscribers (that is, provisioned on the host terminal)
are not explicitly collected but can be derived from the V5 traffic statistics data
when the RTI traffic statistics data are substracted (for exceptions see the previous
bullet item).
• There are no threshold definitions and alarms
• All data are stored volatile.

Measurement data collection

Measurement data intervals

Measurement data collection is done on base of fixed time intervals (measurement
intervals). For both traffic statistics and COMDAC load measurement a measurement
interval of 5 minute applies. The 5 minute intervals are synchronized to the real time 5
minute pattern: that is, an interval always starts at hh.m0 or hh.m5 and ends at hh.m5
or hh.m0, respectively.
When measurement data collection is enabled each measurement interval of a certain
measurement instance is related to a register appropriate for the measurement type
concerned.

Measurement data registers

For each measurement instance there is a set of registers. There is one current register
where the measurement data of the current measurement interval are stored and there
are up to 288 history registers where the measurement data of past measurement
intervals are stored. So there is history for 24 hours. The register with the measurement
data of the measurement interval right before the current register is called the most
recent register.
History registers are numbered in ascending order in accordance to the measurement
interval they correspond, beginning with the most recent register carrying the number
1. They carry a date and time stamp identifying the start time of the measurement
interval concerned. Note that registers related to a time period when statistics
measurements were disabled do not exist.
Measurement data of the current measurement interval (that is, the measurement
interval is not yet completed) are stored in the current register. When the current
measurement interval is completed, the contents of all history registers are moved to
the register that carries the next higher identification number (when measurement is
enabled for less than 24 hours this implies creation of one new register). When this
takes place the contents of the register which identification number equals the
maximum identification number is lost (same behavior as a ring buffer). Afterwards the
contents of the current register (including timestamp) is moved to most recent register
(#1). Now the current register is cleared, the timestamp is set, the validity is set to
valid and measurement data collection continues in the current register.

Clearance of measurement data registers

All registers are cleared on COMDAC recovery and release upgrades (including
non-service affecting upgrades).

Measurement types
...................................................................................................................................................................................................................................

Two different measurement types

With respect to their behavior there are two different measurement types. These are
event count measurement type and resource observation measurement type.

Event count measurement type

Registers for event count measurement type are capable of counting events related to
certain resources, for example the number of terminating calls on a certain V5.2
interface. This measurement type is not applicable for COMDAC load measurement.
There are several measurements which are of event count measurement type:
• Originating call attempts
• Terminating call attempts
• Successful originating calls
• Successful terminating calls
• Originating call build-up resource fail
• Originating call build-up protocol fail
• Originating call build-up overload fail
• Terminating call build-up resource fail
• Terminating call build-up protocol fail
• Stable call failure caused by E1
• Stable call failure caused by subscriber port
• Stable call failure caused by V5 interface
• Stable call failure caused by V5 protocol
• Number of line showering events
• Number of ports affected by line showering events
• Number of V5 port block messages due to line showering events
• Number of V5 port unblock messages due to line showering events.

Resource observation measurement type

Registers for resource observation measurement type collect data related to certain
resources, like the usage of these resources or the total number of available resources
(for example the number of busy BCs or the number of usable BCs of a certain V5.2
interface). These registers are always kept updated (for example either when a value
changes or in regular time intervals). If the calculation of an average value applies,
updating is also done for the average value.
Measurements which are of resource observation measurement type are for example:
• Average number of busy BCs
• Number of usable BCs

• Average number of busy POTS BCs

• CPU load.

Post-processing and presentation

Post-processing functions on the GSI/EMS

The GSI/EMS provides a variety of data collection and post-processing functions
including scheduled periodic collection of data and presentation of results on table
format and/or graphs. For more complex correlations and archiving purposes the data
can be provided for import by a dedicated traffic management system. The functions to
be performed in the GSI/EMS are as follows:
• Periodic Polling
If enabled, the GSI/EMS periodically polls the NE for retrieval of historical
measurement data. The maximum polling rate is 5 minutes (according to the 5
minute register resolution). The minimum polling rate is 24 hours (that’s the
COMDACs storage capacity). The NE does not provide autonomous reporting of
measurement data.
• Measurement types without post-processing
The GSI/EMS shows the measurement types listed in “Measurement types”
(p. 3-168) as provided by the COMDAC without post-processing. Please note that
this does not mean there is no post-processing on these measurement types at all. It
simply means they are also retrievable without post-processing as computed by the
NE. Additionally some of them are used for processing of derived measurement
types.
• Derived Measurement types
These measurement types are calculated from the measurement types as provided
by the NE by applying a formula which depends on the measurement type. The
COMDAC provides counters only, any post-processing is performed by the
GSI/EMS. The following are examples of derived measurement types:
– Originating POTS call attempt failures
– Terminating POTS call attempt failures
– Stable POTS call failures
– Bearer channel usage
– Average number of busy POTS BCs
– Mean call hold time.
• Total counts and long term averages
The GSI/EMS provides total counts and long term averages for a time interval
specified at the GSI/EMS. The total counts are provided for event count
measurement types and the long term averages for resource observation
measurement types.
Important! This applies to 5 min registers for both GSI and EMS. The EMS
additionally supports a table representation for derived registers representing a
longer time interval (for example 1 hour or 24 hours).
• Table representation and charts
The GSI/EMS provides table representation as well as charts for graphical
presentation of measurement results. This applies to any measurement type
including the derived measurement types.
...................................................................................................................................................................................................................................
3-170 363-211-586
Issue 6, July 2007
OAM&P for narrowband services

Security management

Purpose
Security management is the system activity for the following:
• Authentication of a user login identifier (ID) and password
• Management of user login IDs, CIDs, passwords, and privilege levels.
Security management is provided for all user interfaces.
The following sections describe the security management capabilities.

Contents

Security management capabilities 3-172

Security management capabilities

Access security
The system authenticates the user ID and password before establishing a connection.

User security classes

Each login is assigned to a user security class. The supported user security classes are
as follows:
• Privileged user - user login allows access to all TL1 commands and GSI
capabilities.
A privileged user has the additional system administration capabilities as follows:
– Add, delete, or change user security parameters for the user ID, password,
security class, and TL1 inactivity time-out
– Retrieve the security parameters associated with a user, including the user ID,
channel ID the user is logged on, and security class
– Set alarm severity code and define environmental alarms
– Set and retrieve security parameters associated with the system including post-
and pre-login messages, login delay, login timer, intrusion alert parameters
– Activate/release alarm inhibition and provisioning inhibition mode.
• General user - user login allows access to all TL1 commands and GSI capabilities
except for those security management commands that affect other users, such as
login creation and deletion, password modification, security class assignments,
commands for setting alarm severity, and defining environmental alarms.
• Reports-only user - user login allows access to a limited set of TL1 commands for
retrieving system information and autonomous messages. Reports-only users do not
have access to any TL1 commands that create, change, or remove service, or to any
security commands that affect other users.
Up to 30 user IDs can be defined and stored in the COMDAC. At least two of these
IDs must be privileged users (Deletion of the last two privileged user IDs is denied by
the system). The remaining 28 IDs can be any combination of privileged, general and
reports-only user IDs.

Management capabilities
The login can be restricted for each operator to a specific external interface. For this
purpose each operator can be categorized in one or all of the following management
capabilities:
• User interface (UI)
The operator is allowed to log into the system
– via the CIT port on the CIU
– via TELNET (TCP/IP).

These interfaces are used by the GSI.

• TL1
The operator is allowed to log into the system via virtual circuits (TCP/IP). This
interface is used by the EMS.
• File Transfer Protocol (FTP)
The operator is allowed to use only FTP for file transfer to or from the system.
This interfaces is used by the GSI and by the EMS.
• ALL
The operator is allowed to log into the system via all of the above mentioned
interfaces.

Purpose
This chapter describes the Operations, Administration, Maintenance, and Provisioning
(OAM&P) operations for ATM xDSL services for the AnyMedia ® Access System.
This section discusses OAM&P for ATM xDSL services which are transported via an
ATM network. Note that the Applications and Planning Guide for IP-based Services
(363-211-587) includes the description of xDSL services which are transported via an
IP network.

Contents

ATM configuration management 4-3

ATM configuration management - Memory administration 4-4
ATM configuration management - Software management 4-5
ATM configuration management - Turn-up and service provisioning 4-7
Shelf provisioning 4-8
System configuration 4-10
Pack and port provisioning 4-12
ATM cross-connect provisioning 4-13
Daisychaining (E3/DS3 and STM-1/OC-3c) 4-19
ATM configuration management - Inventory management 4-20
ATM fault management 4-23
ATM fault management - Maintenance 4-24
ATM fault management - Alarms, status conditions, and events 4-27
ATM fault management - Protection switching 4-35
ATM fault management - Testing 4-37
Feeder loopback testing 4-41
Diagnosing network troubles using F4/F5 OAM cells 4-45

ATM payload loopback 4-47

SHDSL loopback test 4-48
CPE Routing - remote access to CPEs 4-49
ATM xDSL performance management 4-51
ATM feeder performance management 4-52
ADSL performance management 4-60
SHDSL performance management 4-65
IMA performance management 4-67
ATM cell traffic 4-68
ATM security management 4-73
Access security 4-73

ATM configuration management

Purpose
Configuration management is the system activity for operations that control and
provision the system, including the following:
• Memory administration- used to manage the nonvolatile data storage (NVDS) of
the AnyMedia ® Access System.
• Software management - used to manage the nonvolatile program storage (NVPS) of
the system.
• Service provisioning - used to turn up an AnyMedia ® Mainshelf in preparation for
providing ATM xDSL service and to prepare an AP port circuit for service by
defining the AP’s function and setting any required ports.
• Inventory management - system activity of collecting, updating, and reporting data
on system equipage and system status.

Contents

ATM configuration management - Memory administration 4-4

ATM configuration management - Software management 4-5
ATM configuration management - Turn-up and service provisioning 4-7
Shelf provisioning 4-8
System configuration 4-10
Pack and port provisioning 4-12
ATM cross-connect provisioning 4-13
Daisychaining (E3/DS3 and STM-1/OC-3c) 4-19
ATM configuration management - Inventory management 4-20

ATM configuration management - Memory administration

Overview
Memory administration is used to manage the nonvolatile data storage (NVDS) of the
AnyMedia ® Access System.

NVDS
The system has the following types of data storage:
• Volatile data storage, which is in random access memory (RAM)
• NVDS, which is implemented using a FLASH memory device on the AFM.
In the case of duplex AFM, the standby AFM’s NVDS is automatically updated with
any changes to the active AFM’s NVDS. If an AFM is replaced, the NVDS of the new
AFM automatically gets updated with the NVDS from the other AFM.

NVDS backup and restore

The system supports backups of the NVDS data in case of failures of the NVDS.
Backups of the NVDS data are done through the NVDS database upload from the
NVDS to the GSI/EMS. NVDS backup will not occur automatically; it must be
initiated either locally or remotely.
The system also supports restoration of a previous release’s NVDS data in the event of
a back out of a new software release. The restoration of previous data is done through
the NVDS database download from the EMS or GSI. In the case of duplex AFMs, the
NVDS of both packs is restored by this process.

ATM configuration management - Software management

Overview
Software management is used to manage the nonvolatile program storage (NVPS) of
the AnyMedia ® Access System.
Note that previous software releases may not support the AnyMedia ® LAG Shelves:
• The AnyMedia ® LAG 4300 Shelf is not supported by R1.23 and earlier releases
• The AnyMedia ® LAG 1900 Shelf is not supported by R1.25, R1.23 and earlier
releases
In theses cases a software download and a software upgrade will be required. Note that
only the SW Download functionality will be supported and no other activity should be
performed.

NVPS
The system has re-programmable program memories in the AFM and each xDSL AP.
Each AFM contains its own program memory and load images for the xDSL APs.
Each xDSL AP contains its own program memory. Customer premises equipment
(CPE) program memory is not downloadable from the AnyMedia ® Access System.
The AFM routinely polls the ATM xDSL APs and verifies the xDSL AP program
memory. If the ATM xDSL program memory is corrupted, the AFM will automatically
download the appropriate load image to the program memory to the ATM xDSL AP. If
an ATM xDSL AP is replaced, the NVPS is automatically downloaded to the new pack.

Program storage
The system is capable of modifying the AFM and xDSL AP program memories
through
• an AFM software download operation or through
• AFM replacement.
For the combo APs, only the ADSL portion is re-programmable. POTS circuit packs
are not re-programmable.
The software download to the AFM is through any ATM OAM&P interface, and the
software download has no impact on subscriber service. For duplex AFMs, the
software is downloaded to both the active and standby AFMs.
Software download to the AFMs in an AnyMedia ® LAG 4300 Shelf requires two file
transfer operations. The two BB subsystems do not have to have identical AFM
software versions, but the software versions need to support the AnyMedia ® LAG
Shelf. It is the operator’s responsibility to backup/restore the correct database on a
specific subsystem. When an incompatible database is restored the AFM will revert
back to its original database, and the operator will be required to re-restore a
compatible database. For more details refer to “ATM configuration management -
Memory administration” (p. 4-4).
...................................................................................................................................................................................................................................
363-211-586 4-5
Issue 6, July 2007
OAM&P for ATM xDSL services ATM configuration management - Software management

Each different ATM xDSL AP function code has its own software. The software
download from the AFM to the ATM xDSL APs is through ATM cells. The software
download from the AFM to the ATM xDSL APs may impact subscriber service.
Narrowband service is not affected when ADSL software of one of the combo APs is
updated.
The shelf configuration can affect the time to download software and return to full
operation. Each different ATM xDSL AP function code installed on an AnyMedia shelf
means that a separate load image must be downloaded. The AFM broadcasts software
to all APs of the same function code. As the number of different types of APs
increases, download time increases.
The CPE software must be managed independent of the AnyMedia ® Access System.

ATM xDSL software delivery

A new ATM xDSL software release can be deployed to the system as follows:
• AFM pack replacement
AFM replacement is a service-affecting action.
• Electronic transfer of the software version from the GSI/EMS via an ATM
OAM&P interface to the AFM.
Local or remote transfer/download of the AFM or xDSL AP software version is a
non-service-affecting action provided that the xDSL AP transceiver image is not
being downloaded. However, in the case of a new xDSL AP transceiver image
download, once the transceiver image has been downloaded, the transceivers must
be re-initialized to change to the new software. This will happen to all ports at
once on a pack and can interrupt service for up to three minutes.
For details see the system release description (SRD) provided with the new
software. POTS service that shares the same a/b pair with ADSL service is not
affected.

ATM configuration management - Turn-up and service

provisioning
...................................................................................................................................................................................................................................
Important! In a mixed narrowband and ATM xDSL configuration it is assumed
that the NB subsystem has already been installed and turned up before turning up
the BB subsystem.

Remark for AnyMedia ® LAG 4300 Shelf

In an AnyMedia ® LAG 4300 Shelf it does not matter in which order the two rows are
turned up and provisioned. Turn-up and provisioning is identical for all AnyMedia®
shelf types. Only the AFM slot references differ.
Turn-up and provisioning of the second BB subsystem in an AnyMedia ® LAG 4300
Shelf is similar to the growth of a daisy-chained AnyMedia ® ETSI V5 Shelf. Since the
two BB subsystems are two independent entities, it is the operator responsibility to
correlate the parameters associated with the two subsystems, e.g. traffic profiles,
coordination of daisy chained VPCs.

Turnup overview
Turn-up for ATM xDSL service includes:
• Shelf provisioning AnyMedia® Mainshelves
• Pack provisioning
• Pack installation and cabling.
Service activation for ATM xDSL service includes:
• Port provisioning
• Cross-connect provisioning.
All must be completed for service to be activated. It is recommended that the items
above be done in the order listed, with the exception of pack installation and cabling,
which can occur at any point in the turn-up and service provisioning process.
The AnyMedia® shelves must be provisioned before any other provisioning operations.
Specific parameter definitions, ranges and defaults are contained in Chapter 6, “System
planning and engineering for ATM xDSL services”. The work order is contained in the
Appendix.

Shelf provisioning
...................................................................................................................................................................................................................................

Overview
Shelf provisioning refers to the procedure resulting in an operational BB subsystem in
an AnyMedia ® Mainshelf. The AFM is installed and initialized, and parameters that
apply to the entire shelf are provisioned. Shelf provisioning can begin when a shelf is
installed and powered. When adding a BB subsystem to a daisy chain, it should always
be added at the end of the daisy chain to avoid affecting existing service.
The Work Order contains all the information to be provisioned for the different AFM
types (AFME3, AFMDS3, AFME1, AFMO).
Important! The terms ″preferred AFM slot″ and ″AFM protection slot″ have been
added to the slot designations ″slot 16″ and ″slot 15″ in order to remind the user
that the slot designations in the BB subsystems in an AnyMedia ® LAG 4300 Shelf
are different from those used in the AnyMedia ® ETSI V5 Shelf. For a reference list
of the slot designations refer to “Slot numbering and AIDs for the AnyMedia ®
LAG Shelves” (p. 6-88).
If shelf provisioning is for simplex mode, the steps required include:
1. Install the AFM, which includes:
• Insert AFM circuit pack into slot AP-16 (preferred AFM slot)
• Cable the ATM feeder
• Verify the software load
• Initialize the system database.
Proceed to Step 4 for simplex mode provisioning.
If shelf provisioning is for duplex mode, the steps required include:
2. Install the AFMs, which includes:
• Insert the first AFM circuit pack into slot AP-16 (preferred AFM slot)
• Cable the ATM feeder
• Verify the software load
• Initialize the system database.
Continue with Step 3 for duplex mode provisioning.
3. Install the second AFM in slot AP-15 (AFM protection slot) and cable the feeder.
(When using duplex AFME3 or AFMDS3 this involves re-cabling the feeder of
both AFMs including installation of an external combiner and splitter. Use of
duplex AFMOs assumes that there are duplex feeders as well.) The second AFM
then initializes.
4. Provision communications parameters which allow the AFM to communicate over
the ATM OAM&P interfaces. Also provision information about system
configuration (see “System configuration” (p. 4-10)). If adding a BB subsystem to
a daisy chain, provision existing VPs on the other shelves as Upstream Vp on the
shelf being added to the daisy chain.
5. If adding a shelf to a daisy chain, provision existing VPs on the other shelves as
Upstream Vp on the shelf being added to the daisy chain.
...................................................................................................................................................................................................................................
4-8 363-211-586
Issue 6, July 2007
OAM&P for ATM xDSL services Shelf provisioning

6. Provision the BB ATM Operations Channel.

7. Provision the feeder bandwidth allocated to the shelf (Shelf Peak Cell Rate
upstream and downstream).
8. Provision parameters related to QoS functions (shelf over booking factors, cell
transfer delay, cell delay variation and cell loss ratio). These parameters to be
provisioned are QoS class-dependent (CBR, rt-VBR, nrt-VBR, UBR). See Chapter
6, “System planning and engineering for ATM xDSL services”for the parameters
required for each service class.
9. Provision the Shelf VPs. These are the VPs that support VC cross connects. Up to
128 Shelf VPs may be provisioned per BB subsystem. Each VP may be
provisioned for any of the four service classes.
If adding a BB subsystem to a daisy chain, the following additional steps are also
required:
10. Provision VPs used on this shelf as Downstream VP on the other shelves in the
daisy chain. This is needed to treat each VP as the appropriate service class and
assure quality of service for data that passes through other shelves in a daisy chain.
11. Provision VPs used on other shelves in the daisy chain as Upstream VP on this
shelf. This step is needed so that this shelf can prevent the use of Feeder VPs that
are being used by other shelves in the daisy chain.
12. Provision the ATM feeder port parameters and the protection mode, if applicable,
for Port 2 of the existing BB subsystem that will feed the new shelf in the daisy
chain. Also, provision the ATM feeder port parameters and the protection mode, if
applicable, of the new shelf’s port 1.

System configuration
...................................................................................................................................................................................................................................

Customer configuration
The customer configuration allows the BB subsystem to support different system
behavior depending on the customer’s need. Currently it allows control of
• the Fault LED behavior on the APs in case of an a/b cable disconnect failure
(BB-Tip/Ring cable disconnect detected) and
• the Dying Gasp behavior and other port related PM counts.
The following table shows the customer configuration regarding the AP fault LED
behavior.

Customer Configuration AP Fault LED Behavior in case of front cable

disconnect
1 (default) Steady off
2 Steady on

The following table shows the customer configuration regarding the dying gasp
behavior.

Customer Configuration Dying Gasp behavior

1 (default) Dying Gasp count is the sum of the ″Power Loss″
messages from the modem.
If the port is set administratively to ″OOS″ then
the Dying Gasp count will be set to zero and the
counting is stopped.
If the port is set to ″IS″ the counting will be
restarted.
2 Dying Gasp count is the sum of the ″Power Loss″
messages from the modem and the transitions of
the administrative state from ″IS″ to ″OOS″.
If the port is set administratively to ″OOS″ then
the Dying Gasp count will be incremented. The
counting is continued as usual.
The counter will be reset to zero when deleting
the port but not when the port is set
administratively to ″OOS″.

Shelf type
The following different shelf types can be used for housing the AnyMedia ® Access
System
• AnyMedia ® ETSI V5 Shelf (full capacity mainshelf configuration)
• AnyMedia ® 800 Shelf, some application pack slots are used to house external
equipment (reduced capacity mainshelf configuration)
• AnyMedia ® LAG 4300 Shelf, including 2 independent BB subsystems.
To allow management systems to distinguish between these two shelf types in order to
display the correct graphical view of the shelf the Main Shelf Type information has
been introduced in the AFM and COMDAC. The provisionable mainshelf types are:
• AnyMedia AS
• AnyMedia AS 800.
For the AnyMedia LAG Shelf no shelf type needs to be provisioned.
The main shelf type is set separately on the AFM and on the COMDAC. There is no
synchronization between AFM and COMDAC concerning the provisioned value. In
case of a mismatch the management system displays the default view of the shelf type.

Mainshelf miscellaneous information

The provisioning item Main Shelf Miscellaneous Information provides a free selectable
text string to the network operator. It can be used for any purpose, e.g. shelf location
information, maintenance personnel contact information or any arbitrary identifier used
on the management system. This data is retrievable, but it is not further used by the
AFM.

Pack and port provisioning

Pack provisioning
Pack provisioning refers to provisioning the slot with a pack type of ADSL, SHDSL,
or E1-IMA.
The ATM xDSL engineering work orders in the Appendix contain the information to be
provisioned.

Pack installation and cabling

For a description of which pins are used in the APs, see the Datasheet Book.
Connecting an ADSL AP to an a/b pair that is providing POTS-only is described in
“Pack upgrade (ADSL only)” (p. 6-20). The a/b wiring for combo APs is the same as
the wiring for the narrowband AP.

Port provisioning
Port provisioning refers to the provisioning of transmission and performance
management (PM) parameters.
Transmission profiles and PM profiles allow common parameter sets to be applied to
different ports. Predefined profiles are provided; new profiles can be created.
Different transmission parameters need to be specified for ADSL, or SHDSL pack
types, and for flexible or explicit rate adaptation. Transmission parameters should be
selected based on the modem used. The ATM xDSL engineering work orders in the
Appendix contain the information to be provisioned.

ATM cross-connect provisioning

Cross-connect provisioning refers to the provisioning required to connect the feeder
ATM connection to the subscriber ATM connection.
Different ATM traffic parameters need to be specified for the service classes CBR,
rt-VBR, nrt-VBR and UBR. The ATM xDSL engineering work orders in the Appendix
contain the information to be provisioned. ATM traffic profiles allow common
parameter sets to be applied to different connections. Predefined profiles for each
service class are provided; new profiles can be created.

ATM connections
ATM transmission supports many virtual connections within one physical connection.
In the AnyMedia ® Access System, the physical connections that carry ATM cells are
the feeders and the ATM xDSL lines.
The overhead bytes of an ATM cell include a means of identifying to which virtual
connection the given cell belongs. These identifiers are the virtual path identifier (VPI)
and virtual channel identifier (VCI). A VP is defined by a VPI number only, while a
VC is defined by a VPI number and a VCI number.
There are five types of feeder VPs in the AnyMedia ® Access System:
• Shelf VP
• OAM&P VP
• Local VP
• Downstream VP
• Upstream VP.
OAM&P VPs are discussed in “Using the BB ATM Operations Channel to transport
NB OAM&P” (p. 5-38).
Downstream and upstream VPs are discussed in “Daisychaining (E3/DS3 and
STM-1/OC-3c)” (p. 4-19).
Shelf VPs are discussed in “Shelf VP (VP/VC cross- connects)” (p. 4-14) and “Local
VP” (p. 4-17).
Up to 255 feeder VPs can be defined per feeder connection to the ATM transport
network (that means, per daisy-chained set). For the rules that govern these
connections, see “ATM xDSL system capacity” (p. 6-5).
In the AnyMedia ® Access System, a subscriber’s ATM connection is established by
cross-connecting virtual connections on the ATM network feeder to virtual connections
on the DSL distribution.

Cross-connects are defined two different ways in the AnyMedia (800) Access System:
• As VC cross-connections (the feeder VP is a Shelf VP, see “Shelf VP (VP/VC
cross- connects)” (p. 4-14))
• As VP cross-connections (the feeder VP is a local VP, see “Local VP” (p. 4-17)).

Shelf VP (VP/VC cross- connects)

A Shelf VP supports VP/VC cross-connects only within a single shelf. Up to 128 Shelf
VPs can be provisioned with any of the four service classes. Multiple Shelf VPs may
have the same service category, or each of the Shelf VPs may have a different
category. As shown in the following table, any Shelf VP and available VC on the ATM
network feeder side may be cross-connected to any ATM xDSL distribution VP/VC.
The following table shows ATM VP/VC cross-connects.

Feeder Cross-Connected to ATM xDSL Distribution

Any one of the Shelf VPIs ---> Any VPI
Any available VCI within ---> Any VCI
the Shelf VPI

In the AnyMedia ® Access System, the ranges of VPIs and VCIs that can be used for
VPI/VCI cross-connects are shown in the next table. The ranges differ depending on
the AFM.
The table shows the range of VPI and VCI for VP/VC cross-connects. Any VPI or VCI
outside of these ranges cannot be selected. For the maximum number of VPs and VCs
that can be defined, see “ATM xDSL system capacity” (p. 6-5).

Facility VPI Range VCI Range

ATM Network Feeder 1 to 255 33 to 9723
ATM xDSL Distribution 0 to 255 0 to 1023

Each BB subsystem may have up to 128 Shelf VPIs and a BB ATM Operations
Channel that might have its own VPI. The latter can be the same as a Shelf VPI, but it
does not have to be. When the BB ATM Operations Channel is carried in a Shelf VPI,
the VCI is fixed at 32. When the BB ATM Operations Channel is carried in a VPI that
is not a Shelf VPI, the VCI can be provisioned to be any value from 32 to 64, and the
VPI can be provisioned to be any value from 1 to 255.
An example of a set of three VP/VC cross-connects is given in “Shelf VP (VP/VC
cross- connects)” (p. 4-15). In the figure, the Shelf VPI#1 is 10. The same VPI and
VCI values are used on each DSL distribution pair in this example. The VPI and VCI
are not required to be the same on each distribution pair. However, operations are
simpler if they are the same. The table below the figure lists the cross-connects shown
in “Shelf VP (VP/VC cross- connects)” (p. 4-15).

The following figure shows an example of ATM VP/VC cross-connects.

This table lists the VP/VC cross-connects shown in “Shelf VP (VP/VC cross-
connects)” (p. 4-15).

ATM Network Cross- ADSL Distribution

Connected to
Feeder Feeder AP Slot AP Port Sub- Sub-
VPI VCI scriber scriber
VPI VCI
10 40 ---> 1 1 1 33
10 41 ---> 1 3 1 33
10 100 ---> 3 5 1 33

When provisioning a new Shelf VP, the following parameters have to be selected:
• Service Category: CBR, rt-VBR, nrt-VBR, or UBR
• Highest VCI Allowed: The VCI range for the feeder side of an ATM cross-connect
begins with 33 and ends with the value provisioned for this parameter. Parameters
similar to this one are common in ATM switches.

The Feeder VCI ranges given in “Shelf VP (VP/VC cross- connects)” (p. 4-14) for
each AFM type are the largest values that the Highest VCI Allowed parameter can
have. Highest VCI Allowed can be given that value in a shelf with one Shelf VP. The
maximum Feeder VCI values listed in “Shelf VP (VP/VC cross- connects)” (p. 4-14)
represent the total Feeder VCI address space in the shelf. When a Shelf VP is created,
a certain amount of that space is allocated to the new Shelf VP. This allocation
decreases the range the system permits for Highest VCI Allowed for the next Shelf VP
that may be created. Note that when a Shelf VP is deleted, the address space allocated
to it becomes available for other Shelf VPs.
When creating a new Shelf VP, the largest value permitted for the Highest VCI
Allowed parameter is given by A - B - C where:
A = Highest value in the Feeder VCI range given in “Shelf VP (VP/VC cross-
connects)” (p. 4-14).
B = Sum of all values of the Highest VCI Allowed parameter of all provisioned Shelf
VPs in the given shelf.
C = How many Shelf VPs are provisioned in the given shelf.
When the Highest VCI Allowed parameter is being edited for an existing Shelf VP, the
largest value permitted is given by K + N + 1 where:
K = A - B - C described above. For the value of B, include the contribution from the
Shelf VP to be edited.
N = Current value of the Highest VCI Allowed for the Shelf VP to be edited.
• The administrator can retrieve the following information that can be used when
making engineering decisions for adding, deleting, or manipulating Shelf VPs:
• Service category and Highest VCI Allowed for each provisioned Shelf VP.
• Service category and VP Type of all other Feeder VPs.
• Highest VCI Used for a cross-connect in each provisioned Shelf VP. When editing
an existing Shelf VP, the value of the Highest VCI Allowed parameter cannot be
made lower than the Highest VCI Used parameter.
• Number of Shelf VPs that can still be provisioned. Note that the total number of
Feeder VPs a shelf can have is 255. Therefore, the total number of Shelf VPs
allowed will be less than 128 if more than 127 Feeder VPs of other types have
been provisioned.
• Largest value permitted for the Highest VCI Allowed parameter for a new Shelf
VP. This value is the A - B - C value described above.
• Largest value permitted for the Highest VCI Allowed parameter for an existing
Shelf VP. Consider this value when editing an existing Shelf VP. This value is the
K + N + 1 value described above.

Local VP
A cross-connect can also be specified as a VP cross-connect. In this case, the feeder
VP is called a local VP. VP cross-connects are defined as shown in the following table.

ATM Network Feeder Cross-Connected Distribution

to
Any VPI except the Shelf VPIs ---> Any VPI on xDSL
distribution pair
VCIs in a VP cross-connect are not visible to the BB subsystem

In the AnyMedia ® Access System, the ranges of VPIs that can be used for VP
cross-connects are as follows:

Facility VPI Range

1
ATM Network Feeder 1 to 243
ATM xDSL Distribution 0 to 255

Notes:
1. Note that the VPI range of 1 to 243 is for VP cross-connects within a given shelf. The
values 244 to 255 can be used by other shelves in a daisy-chain.

Any VPI outside of these ranges cannot be selected. Any unused VPI may be used
(but, see “Daisychaining (E3/DS3 and STM-1/OC-3c)” (p. 4-19), “Daisychaining
(E3/DS3 and STM-1/OC-3c)” (p. 4-19)). For the maximum number of VPs that can be
defined, see “ATM xDSL system capacity” (p. 6-5).
For VP cross-connects, VCs are defined at the ATM switch and at the CPE. However,
because the AnyMedia ® Access System only cross-connects the VP, a set of VCs that
enter the BB subsystem within one VP will all exit the shelf within one (different) VP.
In this case, there is no VCI cross-connect provisioning and no VCI translation in the
AnyMedia ® Access System.
An example of a set of three VP cross-connects is given in “Local VP” (p. 4-18). Note
how the VCs carried in each VP are shown passing through the cross-connect without
their identifiers being translated. The Shelf VPIs are not shown in the figure because
they cannot be used for a VP-only cross-connect. The same VPI value is used on each
DSL distribution pair. The VPI is not required to be the same on each distribution pair.
However, operations are simpler if it is the same. The table below the next figure
displays the cross-connects shown in “Local VP” (p. 4-18).
The following figure shows an example of ATM VP cross-connects.

The following table describes the VP cross-connects shown in “Local VP” (p. 4-18).

ATM Network Feeder Cross-Connected to ADSL Distribution

Feeder VPI Shelf Slot AP Port Subscriber
VPI
4 ---> 2 1 2
6 ---> 2 2 2
9 ---> 2 3 2

Daisychaining (E3/DS3 and STM-1/OC-3c)

Shelf daisychaining
Daisy-chained shelves share a common feeder connection to the ATM transport
network (see “Local shelf daisychaining” (p. 1-33)). Up to 128 shelf VPs can be
provisioned per BB subsystem for use by that shelf. As a rule, the AFM in each shelf
in the daisy-chain forwards VPs that it does not use to system shelves further out the
chain. In other words, if the shelf does not use or cross-connect a specific VP, it
forwards it to the next system in the chain.
VPs must be unique among all shelves in a daisy-chain set. Therefore, the system
administrator must be certain that each shelf in a daisy-chain is provisioned with
information on the VPs in use by all upstream and downstream shelves in the
daisy-chain. This provisioning ensures that the GSI will return an error in case of
either of the following:
• someone tries to provision a new shelf being added to the daisy-chain with VPs
already in use by other shelves
• someone tries to add a new VP to an existing shelf anywhere in the daisy-chain
with a VP already in use by another shelf
Additionally, ensuring proper traffic management requires that each shelf in a
daisy-chain be provisioned with information on the VPs in use by all downstream
shelves in the daisy-chain.
“Scenario 3: Turning up new daisy-chained Mainshelves in simplex AFM mode”
(p. 6-78), and “Scenario 4: Turning up new daisy-chained Mainshelves using duplex
AFM mode ” (p. 6-78) address this need.
The value range for an upstream VP, as well as for a downstream VP, is from one to
255.
For an illustration of how upstream VPs and downstream VPs are provisioned, see
“Special considerations for a daisy chain” (p. 6-62).

ATM configuration management - Inventory management

Overview
Inventory management for the AFM circuit packs and the ATM xDSL APs is similar to
the narrowband system in that the pack data of the equipment are the same. Inventory
management information for the AFM and the ATM xDSL APs can be retrieved via the
ATM OAM&P interfaces using SNMP commands as soon as the packs have been
inserted. A technician using the GSI/EMS sees a graphical representation of the
AnyMedia shelves populated with AFM circuit pack(s) and ATM xDSL packs.
Inventory management information for ADSL modems is also retrievable using the
GSI.
In mixed configurations of narrowband and ATM xDSL services, inventory
management information for ATM xDSL packs, as well as narrowband APs, can be
retrieved via the COMDAC through the CIU using TL1 commands. A technician using
the GSI/EMS logged into the COMDAC sees a graphical representation of the
AnyMedia shelves populated with both narrowband and ATM xDSL packs. A
technician using the GSI/EMS in a mixed configuration when connected to the AFM
sees a graphical representation of the AnyMedia shelves populated with ATM xDSL
packs only.
The ATM inventory management functions are identical for all configurations of the
AnyMedia ® Access System, regardless of which shelf type is used.

Retrievable inventory items

Electronically readable inventory management information for each ATM xDSL pack in
the system can be retrieved on demand.
Below is a list of definitions for retrievable network inventory items for ATM xDSL
circuit packs, followed by examples of such items for the ADSLp LPA416 AP.
Retrievable pack inventory items include the following:
• CLEI - a 10-character code that identifies each pack type.
• Serial Number - a 12-character code that uniquely identifies each pack. The serial
number includes the date and place of manufacture.
• Apparatus Code - uniquely identifies the equipment function (for example
LPA911); packs with different apparatus codes are not interchangeable.
• Interchangeability Code - used to specify the backward compatibility of two packs
with the same type and apparatus code but different manufacturing versions (that
means different series). The marking takes the form m:n where n is the series of
the marked pack and m is the series that the circuit pack is compatible with.
– Example 1:
1:3 means that this pack is a series 3 pack. It is backward compatible with
series 2 packs and also series 1 packs.
– Example 2:

2:3 means that this pack is a series 3 pack. It is backward compatible with
series 2 packs only.
– Example 3:
2:2 means that this circuit is a series 2 pack. It is not backward compatible with
any other series.
• Equipment Catalog Item - a 6-character code that identifies each pack type. This
code corresponds to the bar-coded label on the faceplate of the pack and is
uniquely equivalent to the CLEI.
• Circuit Pack Type (Function Code) - a mnemonic name that identifies the general
type of function (for example ADSL16p).
The following table shows as an example the retrievable inventory items from the
ADSL16p LPA416 AP.

Item Value
CLEI Code E5PQA2BAAC
Serial Number 000C12154760
Apparatus Code LPA416
Interchangeability Code 1:3
Equipment Catalog Item 275754
Circuit Pack Type ADSLF+L

Retrievable inventory items for ADSL modems

Electronically readable inventory for ADSL modems connected to certain ADSL APs in
the system can be retrieved on demand.
Below is a list of definitions for retrievable network inventory items for ADSL
modems.
Retrievable inventory items include the following:
• Vendor ID - Identifies the modem’s country of origin and the vendor that
manufactured the modem. May include additional information at the discretion of
the manufacturer.
• Serial Number - Serial number of the modem in a format determined by the
manufacturer.
• Version Number - Information provided at the discretion of the manufacturer.

Physical data labels

ATM xDSL packs include the same type of human-readable inventory data label as
narrowband packs (see “Retrievable inventory items” (p. 3-78)).

Reportable data base changes

Autonomous notification is provided over the ATM OAM&P interfaces when changes
occur to the inventory database as a result of changes in the physical inventory (see
“Turn-up and service activation provisioning default values” (p. 6-116)).

ATM fault management

Purpose
Fault management is the system activity for operations that cover the following:
• Maintenance - automatic and manual activities to ensure continued operation and
minimize service degradation.
• Alarms, status conditions, and events - equipment and facility monitoring that
results in alarms, status condition reports, and transient condition reports.
• Protection switching—Recovery mechanisms that automatically switch from a
failing AFM and/or facility to a standby AFM and/or facility when a fault is
detected in the system.
• Testing - turn-up tests, loopbacks, and on-demand circuit testing.
The ATM fault management functions are identical for all configurations of the
AnyMedia ® Access System, regardless of which shelf type is used.
In principle the alarms are also identical for all configurations of the AnyMedia ®
Access System. But due to the differently designated slots in the AnyMedia ® LAG
4300 Shelf, the GSI identifiers are different.

Contents

ATM fault management - Maintenance 4-24

ATM fault management - Alarms, status conditions, and events 4-27
ATM fault management - Protection switching 4-35
ATM fault management - Testing 4-37
Feeder loopback testing 4-41
Diagnosing network troubles using F4/F5 OAM cells 4-45
ATM payload loopback 4-47
SHDSL loopback test 4-48
CPE Routing - remote access to CPEs 4-49

ATM fault management - Maintenance

Overview
Maintenance is the set of activities performed automatically and/or manually to ensure
continued operation and to minimize service degradation. This section addresses the
following:
• Maintenance objectives
• Maintenance concepts of detection, isolation, reporting and recovery
• Proactive maintenance.

Maintenance objectives
Accurate maintenance can be performed on a system that has been properly installed
and provisioned.
Maintenance provides the tools that fulfill the following objectives:
• Detect the majority of all faults in the system.
• Isolate faults accurately to avoid false dispatching.
• Report faults as soon as the faults occur with sufficient supporting information.
• Support proactive maintenance to discover faults before the faults can affect
service.

Detection
Detection is the act of determining that a problem exists in the system. A problem can
be either permanent or transient in nature. In the system, the detection of these kinds
of problems is accomplished in two ways:
• Unit fault detection
The first and most prevalent way to detect a problem is unit fault detection. Unit
fault detection has been designed into most replaceable units in the system and
allows the unit to determine its own health, determine the quality of its inputs, and
report any malfunctions. Unit fault detection is used mostly for permanent faults,
which are reported as alarms.
• Performance management
The second way to detect a problem, which is more proactive and used primarily
for transient conditions, is performance management (PM). PM monitors the data
path integrity between system elements. Some transient conditions are immediately
reported as events and some are accumulated until they exceed a predetermined
threshold, when a threshold crossing alert (TCA) is reported. See “ATM xDSL
performance management” (p. 4-51) for details.
Both methods of fault detection are used throughout the system to ensure complete
system coverage. Both methods are done continuously and do not interrupt service or
limit the ability to provide service.

Isolation
Isolation is the process of analyzing system alarms, TCAs, events, that have been
detected and reported to determine the root cause of the detected conditions in the
system.
The goal is to isolate the fault to a replaceable unit. In most cases, the exact location
and replaceable unit are known at the time when the fault is detected. Sometimes
additional analysis is needed when a detected event is transient or manifests itself with
other sympathetic conditions. For example the removal of an AP (or root cause) causes
the loss of communications (sympathetic condition) between the AFM and the AP.
The isolation of transient errors such as TCAs requires an external operations system to
perform analysis of additional data.

Reporting
Reporting is the process of communicating the detected system faults or events to a
management system. All system alarms and events are reported across the ATM
OAM&P interfaces to provisioned destinations. Most system faults or events are
reported autonomously as they occur. Some system faults are discovered and reported
during routine system operation and surveillance. Most single faults are reported within
a few seconds after the faults have been detected.
In addition to alarm and event reporting, local LED indicators on the equipment
faceplate indicate equipment faults or status conditions.
In the AnyMedia ® LAG 4300 Shelf two BB subsystems may be present. The lower and
upper AFMs provide independent fault and alarm indications.
A summary alarm indicator for each side of the cabinet is provided on the top of the
rack.

Recovery
Recovery is the action taken to prevent a detected fault from continuing to affect
service. When the system detects a pack fault, the system attempts to recover the failed
pack with a hard reset of the implicated pack. The system also automatically initiates
its recovery when power is restored. The system returns all services to the state prior
to power loss within a few minutes after the return of valid and stable power, with the
possibility that some data may not be recovered

Proactive maintenance
Proactive maintenance is the ability to predict or discover a system failure before it
becomes service affecting. The system provides the capability to monitor equipment
and data paths continuously or periodically.

The system also provides the capability to allow periodic maintenance activity to
monitor the integrity of transmission paths. These maintenance activities include the
following:
• Performing metallic loop testing
• Loopbacks.
These maintenance activities can be initiated via SNMP commands over the ATM
OAM&P interfaces.

ATM fault management - Alarms, status conditions, and events

Overview
The surveillance capabilities of the system consist of equipment and facility
monitoring. During normal operation, the system uses noninvasive diagnostics to
continually or periodically monitor the following:
• Individual circuit packs
• Facilities, including
– ATM feeder physical network interfaces and ATM layers
– ATM xDSL distribution span physical and ATM layers
• IMA groups and links (valid only when an AFME1 or an E1IMA AP is used in
IMA mode).
The results of these monitoring activities can generate the following:
• Alarms - predefined system abnormalities with an assigned severity level that
reflects the alarm’s effect on service or the urgency of the problem. Alarm
severities are provisionable. Depending on the alarm type, alarm severities can be
set to:
– Information
– Critical
– Minor
– Major
– No report.
Alarms indicate the need for corrective action. Alarms are cleared once the problem
is corrected.
• Status conditions - standing conditions that reflect ″abnormal″ conditions or other
anomalies that are not assigned a severity level. (A standing condition is a
condition that is active for an extended period of time.) Both alarms and status
conditions are standing conditions.Status conditions are necessary to indicate to the
network management system or to a technician that the system is in an abnormal
state or is performing an action that may interfere with system operations, such as
loopback, software installation, or a forced or inhibited protection switch. A status
condition is reported via a report sequence consisting of a ″status condition set″
report and a ″status condition cleared″ report. An example of a status condition
would be a message stating ″AP pack download in progress set″ followed by a
second message stating ″AP pack download in progress cleared″. As with other
status conditions, there is no corrective action needed, yet it is information the
network management system or technician needs to be aware of. Status conditions
are cleared once the condition is no longer detected by the system.
• Events (also known as transient conditions) - conditions that do not change the
basic state of the system for an extended period of time. An example of an event is
a performance monitoring threshold crossing alert. Technicians may need to log this
information. Unlike alarms or status conditions, transient conditions are not cleared
when the condition is no longer detected by the system.

The AnyMedia ® Access System provides the following capabilities:

• Classifying detected alarms
• Reporting and retrieving alarms, status conditions, and events
• Inhibiting and resuming alarms
• Provisioning of alarm severity levels.

Alarms
Detected alarms are classified as one of the following:
• Equipment alarms
• Facility alarms
• IMA group/link alarms (valid only when an AFME1 or an E1IMA AP is used in
IMA mode).

Equipment alarms
Examples of possible equipment alarms include the following fault conditions:
• Circuit pack fault
• Circuit pack missing
• Mismatch of installed AP and provisioned pack type, port, or ATM traffic profile
• ATM xDSL AP not responding to poll
• Failed software update (applicable for xDSL APs only)
• AP a/b cable disconnect
• ADSL subscriber network timing reference (NTR).
The following equipment alarms apply only to duplex AFM operations:
• Mismatched AFMs
• AFM software version mismatch
• AFMO cross-couple failure (see the AFMO section in the Data Sheet Book
363-211-251 for a short description of the cross-couple)
• AFM pack not responding to poll
• AFM pack removed
• AFM pack failed.

Facility alarms
Facility alarms indicate feeder physical network access problems. These alarms indicate
faulty conditions in the incoming signals. Examples of possible feeder facility alarm
types include for example the following:
• Loss of frame (LOF)
• Loss of signal (LOS)
• Loss of continuity (LOC)
• Remote defect indicator (RDI)

• Alarm indication signal (AIS)

• High bit error ratio (HBER)
• Synchronization signal failed
• Line loopback.

IMA group/link alarms

Examples of possible IMA group alarms include the following fault conditions:
• Timing modes at near end and far end do not match
• Far end terminal is starting up
• Far end is using unacceptable configuration parameters
• Far end is reporting unacceptable configuration parameters
• Number of working links available to the AFME1 is less than the minimum
number provisioned
• Number of working links available to the far end terminal is less than the minimum
number provisioned at that end
• Far end has been inhibited by its user.
Examples of possible IMA link alarms include the following fault conditions:
• Persistent Out-of-IMA-frame anomalies for at least two seconds
• Link is not synchronized with other links for at least two seconds
• Far end reports transmission unusable
• Far end reports Rx signal unusable
• Tx link is not connected to the same FE IMA unit as are the other links
• Rx link is not connected to the same FE IMA unit as are the other links
• Two or more links are failed.

Status conditions and events

Status conditions and events are not assigned a severity level as are alarms. However,
status conditions contain information to indicate to the network management system or
to the technician that the system is in an abnormal state or is performing an action,
while an event contains information that a technician might want to log.
Examples of possible status conditions and events include the following:
• Threshold crossing alerts (TCAs) for feeder physical network access or ATM xDSL
distribution span problems
• AP reset
• AP link up or link down
• AP initialization in progress or completed
• AP insertion or removal
• AP download in progress or completed
• Detection of unknown AP type

• Enabling/disabling of alarm reporting

• AFM NVDS backup/restore in progress or completed
• Failed database backup/restore
• Loss of sync timing, AFM free running
• Loopback in progress
• Port state change.
The following status conditions and events apply only to duplex AFM operation:
• Automatic AFM protection switch
• Forced AFM protection switch
• Inhibit AFM protection switch
• Clear inhibit AFM protection switch.

High Bit Error Ratio (HBER) on ADSL lines

The AnyMedia ® Access System monitors ADSL lines for High Bit Error Ratio
(HBER), which is a failure condition. When this failure occurs, a link down event
report is sent and the link retrains. Under many conditions, this retrain will return
transmission to an acceptable BER and bit rate.
The AnyMedia ® Access System provides a choice of two algorithms for determining
this failure:
• Fixed CRC threshold (the default)
• Fixed BER threshold.
This provisioning is implemented per system and so it is the same for all ADSL ports.
This provisioning has no impact on HBER algorithms used for SHDSL APs.
The two algorithms mentioned above are defined as follows:
Fixed CRC threshold
This threshold is reached when there are ten consecutive seconds with each second
having one or more of the following anomalies:
• At least 18 ADSL superframes with ADSL CRC anomalies
• At least 0.1 seconds in which the received power has dropped to six dB below the
reference power
• At least one ADSL superframe with synchronization anomalies.
This threshold is the default because it was used before the fixed BER threshold
was introduced. The fixed CRC threshold conditions apply regardless of what the
trained bit rate is. As a result, this threshold is higher at lower trained bit rates.

Fixed BER threshold

This threshold is reached when there are 20 consecutive blocks with each block having
one or more of the following anomalies:
• A BER of 4 × 10-6. The BER of each block is estimated by counting the number of
CRC violations.
A block is a length of K seconds, where K depends on the trained bit rate. For
lower bit rates, K is longer. Therefore, the length of time that the anomaly exists
before this failure is detected will be longer for lower bit rates. For example, at a
trained bit rate of 192 kbps, K is 14 seconds; at a trained bit rate of 6144 kbps, K
is one second.
• At least K occurrences in which the received power has dropped to six dB below
the reference power
• At least K ADSL superframes with synchronization anomalies.
More details on fixed thresholds
For the fixed CRC threshold, the transmission degradation required to trigger the
retrain depends on the trained bit rate. For the fixed BER threshold, the threshold is
independent of the trained bit rate.
For the fixed CRC threshold, at lower bit rates the transmission degradation must be
quite severe before a retrain occurs. For example, at 192 kbps, the equivalent BER
threshold using the CRC algorithm is about 1 × 10-4, which is much worse than the 4
× 10-6 threshold used with the fixed BER algorithm.
At lower trained bit rates, the length of time required to detect an HBER failure using
the fixed BER threshold is longer than that required to detect this failure using the
fixed CRC threshold. For example, the failure detection time for the fixed BER
threshold is almost five minutes when the trained bit rate is 192 kbps; in contrast, the
failure detection time for the fixed CRC threshold is always 10 seconds, regardless of
the trained bit rate.
At higher trained bit rates, for example at 4480 kbps, the equivalent BER threshold for
the fixed CRC threshold algorithm is approximately equal to the threshold used for the
fixed BER threshold. At this same bit rate, the failure detection time using the fixed
BER threshold algorithm is 20 seconds, compared with 10 seconds for the fixed CRC
threshold.

Failure reporting
The BB subsystem provides two provisioning mechanisms regarding the failure
reporting. It depends on the entity type which of the two provisioning mechanisms is
applicable:
• Alarm severity provisioning per alarm type

The alarm severity provisioning allows an operator to assign an alarm severity of

any particular alarm condition on a per entity type basis for service affecting and
non-service affecting failures to each alarm type. These provisioned alarm
severities are the same for all entities of this type, that means it is not possible to
have individual severities per specific entity. The alarms applicable to the alarm
severity provisioning per alarm type are grouped into alarm categories. The
following alarm categories are defined:
– AFM Pack Fault
– AFM Memory Fault
– AP Fault
– Provision Mismatch
– Feeder Sonet/SDH
– Feeder DS3/E3
– Feeder DS1/E1
– Feeder IMA.
• Provisionable failure reporting per entity
The provisionable failure reporting allows to provision an alarm severity or disable
failure reporting for each failure or condition per individual entity. The
provisionable failure reporting per entity is only available for the entity types ″port
on application pack″ and ″port on application pack in subshelf″.
Predefined and provisionable failure report profiles assist the user in assigning the
correct failure reporting behavior to the entities. The profiles contain the following
information for each applicable failure of the entity:
– No reporting
– Alarm reporting for this failure.

Reporting and retrieving alarms

Environmental or miscellaneous alarms for the AnyMedia® shelves are reported via the
OAM&P interfaces for narrowband services.
The alarms for ATM xDSL APs and the AFM are reported/retrieved via the ATM
OAM&P interfaces in the same manner whether they are reported and retrieved for an
ATM xDSL-only configuration or for a mixed configuration of narrowband and ATM
xDSL services. In a mixed narrowband and ATM xDSL configuration also, the
COMDAC reports the following alarms for the ATM xDSL APs and the AFM over the
TL1 interfaces:
• Pack missing or power fault.
• Pack not responding to poll.
• ATM xDSL summary alarm, which is raised whenever there is any alarm in the
AnyMedia ® Access System supporting ATM xDSL services.

Reporting/retrieving alarms via ATM OAM&P interfaces

The AnyMedia ® Access System provides consistent alarm/event information over the
ATM OAM&P interfaces. The system also supports query for alarms and status
conditions over these interfaces. The functions supported over these interfaces include
the following:
• Reporting equipment and facility alarms
• Reporting status and transient conditions, including TCAs
• Retrieving currently active equipment and facility alarms
• Retrieving currently active status conditions
• Retrieving alarm/status history report
• Retrieving ADSL status
• Retrieving SHDSL status
• Retrieving IMA status.
Reporting alarms via visual indicators
Alarms are also reported via visual indicators:
• LEDs on the faceplates of all APs and AFM types in the system reflect fault
conditions of the pack.
In some cases the AnyMedia ® Access System does not send information about
FAULT LED changes to the GSI (e.g. reset of a BB AP). In such cases the shelf
view of the GSI may not reflect the current status of the LEDs on the real
AnyMedia® shelf.
• Additionally LEDs on the faceplates of the AFM indicate if system alarms or fault
conditions are present.

Alarm inhibiting/ resuming

The AnyMedia ® Access System provides the capability to inhibit and resume
autonomous alarm reporting to all ATM OAM&P interfaces.

Provisioning of alarm severity level

The system provides the capability to provision the alarm severity of any particular
alarm condition on a per entity type basis (with the exception of those alarms that have
a default severity value of critical-service-affecting (CR-SA Critical alarms are always
service-affecting; such alarms must not be changed to nonservice-affecting.).

Reporting System failures towards the ATM transport network

At the ATM layer, the fault management function is supported. The OAM cells
transporting ATM layer information are F4 and F5 cells. F4 cells transport Virtual Path
(VP) level information, while F5 cells transport Virtual Channel (VC) level
information.

The AnyMedia ® Access System generates F4/F5 OAM cells in the following cases:
• In a daisy-chained configuration, when port 2 of an AFM experiences a failure. In
this case, end-to-end VP-AIS (F4 cells) is sent to the ATM network for all affected
VPs.
• In any AnyMedia® shelf, when there is a failure on an xDSL line. In this case,
end-to-end VC-AIS (F5 cells) or VP-AIS (F4 cells are sent from the AnyMedia®
shelf towards the ATM network for all VCs or VPs which are transported via the
failed xDSL line. Whether or not AIS is sent when an xDSL line fails is
provisionable on a per port basis.
The failure can be caused by any of the following:
– Loss of signal on the xDSL line
– Removal of the a/b faceplate connector from the front of an ATM xDSL AP
– Removal of an ATM xDSL AP
– Failure of an ATM xDSL AP.
• When an ATM Continuity Check (CC) fails, AIS is transmitted in the forward
direction and RDI is transmitted in the backward direction. (See “ATM continuity
check” (p. 4-71)for details.)

Reporting receipt of AIS and RDI ATM cells

The AnyMedia ® Access System can receive ATM AIS and ATM RDI (both F4 and F5)
cells from the network. Receipt of these cells from the ATM transport network
indicates that another node in the network has detected one or more defects.
Administrators of the AnyMedia ® Access System may not have access to the alarms
sent by the node that detected the defects. The AnyMedia ® Access System issues the
alarms so that these administrators will know that transmission is being affected by a
defect that may not be occurring in the AnyMedia ® Access System.
The AnyMedia ® Access System issues SNMP alarm messages upon receipt of the
following cells:
• End-to-end VP-AIS from the network on Shelf VPI. An end-to-end VP-RDI (F4
cells) is sent towards the ATM transport network on the same Shelf VPI.
• End-to-end VP-RDI (F4 cells) from the network on Shelf VPI
• End-to-end VC-AIS (F5 cells) on the BB ATM Operations Channel. An end-to-end
VC-RDI (F5 cells) is sent towards the ATM transport network on the same channel.
• End-to-end VC-RDI (F5 cells) on the BB ATM Operations Channel.
All other AIS and RDI cells are passed on to either the downstream AFM or the
modem, as appropriate. The only exception is that, when the AFM is configured as the
segment endpoint, then Segment AIS and Segment RDI cells are dropped.

ATM fault management - Protection switching

Overview
Protection switching provides an automatic recovery mechanism when a fault is
detected in the system.
Protection switching is based on the following principles:
• Redundancy of components where components are protected 1:1
• Revertive or non revertive switching to protected components.

Redundant components
For 1:1 protected components, one component serves as the active or primary
component. The other component serves as a protection or standby component. If the
active component fails, the failure is detected, and service is automatically protection
switched to the protection component.

Non-revertive protection
In the AnyMedia ® Access System, protection switching of ATM xDSL components is
non revertive. Non revertive switching implies that the components do not return to the
original configuration prior to the failure. In non revertive switching, a recovered
component becomes the new standby component.

Components protected
Protection switching is provided for the following components:
• AFM packs (AFME3, AFMDS3, and AFMO)
• STM-1/OC-3c feeder facility
• Synchronization source.

AFM protection
The active AFM pack serves as the common control and feeder interface unit for the
AnyMedia ® Access System’s ATM xDSL services. The AFMs can be switched on
demand.
Both active and standby units are continuously monitored.

STM-1/OC-3c feeder and/or pack protection

An STM-1/OC-3c feeder facility employs a separate optical fiber for each direction.
The AFMO supports two protection modes:
• Double Board Single Fibre protection mode (DBSF)
This protection mode provides pack protection and feeder facility protection for the
feeder section between the AFMO and a pair of external optical couplers. The
optical couplers split the receive signal to both AFMOs and couple the active
transmit signal of either AFMO to the transmit fiber. Beyond the optical coupler
only one fiber pair is used as feeder.
• Duplex 1+1 protection mode
Four fibers—one send and one receive for each of the two feeders are connected
directly to each AFMO. For SDH this applies to unidirectional 1+1 linear Multiplex
Section Protection (MSP) per ITU-T G.841, for SONET it applies to unidirectional
1+1 line protection per Telcordia, GR-253.
In DBSF protection mode the active AFMO is protected by a protection pack, and both
AFMs use a single optical feeder pair on their logical port. In Duplex 1+1 protection
mode the optical feeders are duplicated. Packs can be switched on demand.
In a daisy-chain, both protection modes can be combined, i.e., logical port 1 may be
provisioned in DBSF protection mode while logical port 2 is provisioned in Duplex
1+1 protection mode.

Synchronization source protection

The system has two synchronization sources:
• The active AFM itself (free running)
• An upstream source (line timing).
Line timing is preferred on all AFMs.
If the line timing fails on the AFME3 LPA911, AFMDS3 LPA901, or the AFMO
LPA920, they will switch to free running timing.
The AFME1 LPA941 supports full synchronization source timing protection. The
AFME1 has its primary and secondary timing sources defined from among its 8
possible upstream timing inputs. A protection switch is initiated automatically when
faults are detected on the active timing synchronization source. If both timing sources
fail, the AFME1 reverts to free-running. Also, if there is only one E1 being used, and
its timing source fails, synchronization reverts to free-running.

ATM fault management - Testing

Tests for BB services

The following types of testing are done on an AnyMedia ® Access System that is
supporting ATM xDSL services:
• Metallic loop testing
• ATM xDSL port test
• Built-in self tests of the packs
• ADSL modem self-test
• Bidirectional corrupt CRC testing (ADSL APs only)
• Dual ended line tests DELT (ADSL2/ADSL2+ APs only)
• Single ended line tests SELT (ADSL2/ADSL2+ APs only)
• Forced power state test (ADSL2/ADSL2+ APs only)
• Feeder loopback testing
• Autonomous turn-up tests
• Diagnosing network troubles using F4/F5 OAM cells
• SHDSL payload loopback testing
The first type of testing corresponds to drop testing for narrowband services.

Metallic loop testing

The system supports metallic drop testing of an ADSL circuit if there is a narrowband
circuit carried on the same metallic pair as the ADSL circuit. This drop testing is
supported whether the narrowband service is provided via a separate
narrowband-compatible AP or via a combo AP. Drop testing is done in exactly the
same manner as specified in “Testing possibilities” (p. 3-113).
NB metallic drop tests are initiated via the narrowband OAM&P interfaces, regardless
whether POTS is provided via a separate narrowband-compatible AP or via a combo
AP. In the case of the combo AP, a metallic drop test interrupts ADSL service on the
loop being tested. The AFM issues two event reports for drop tests that interrupt ADSL
service as follows:
• Indicates when the test begins
• Indicates when the test ends.
This way the maintenance center can correlate interruptions in ADSL with NB metallic
drop tests that have occurred.

ATM xDSL port self test

A technician can use the GSI to request a self test on a selected ATM xDSL port
circuit on the ATM xDSL AP to verify that it is performing properly. This test is
service affecting.

Built-in self tests

The built-in self tests are run autonomously as each AFM and xDSL AP is inserted into
a shelf slot. A detected failure results in an illuminated red FAULT LED on the
faceplate of the pack.
Important! For combo packs in the AnyMedia® Mainshelves the built-in self-test
is performed, if the combo pack is inserted in a system with a running COMDAC
in steady state. In cases where the COMDAC recovers in a system with an already
installed combo pack, the test of the combo pack is not performed to avoid an
interruption of the ATM xDSL service carried by the combo pack.

ADSL modem self-test

During power-up the ADSL modem runs through a self-test. According to ITU-T
G992.1 section 9.2.3/9.2.4 the result of this self-test is reported for each port on the
ADSL packs. In the AnyMedia ® Access System the test result is retrievable via the
Data Status screen.
Note that the ADSL modem self-test result is only retrievable for the ADSL APs
LPA417 and LPA434.

Bidirectional corrupted CRC testing (ADSL APs only)

Corrupted CRC-8 testing of the ADSL lines is done using the GSI. It is accomplished
by counting the CRC errors at one end after forcing corrupted CRC-8 to be generated
at the other end. Corrupted CRC-8 can be forced from either the ADSL port located on
the ADSL AP or from the customer premises equipment (CPE). This test is non-service
affecting.
The Performance Monitoring counters at the monitoring end (ADSL AP or CPE)
increment based on the duration of the test.
Once the test has been completed, a comparison of the returned result with the
expected number of errors can be made.
Running a corrupt CRC test in conjunction with an ADSL port self test at the ADSL
AP and a test of the metallic loop will serve to isolate problems to the ADSL port on
the ADSL AP, the ADSL port on the CPE, or the copper pair connecting the two.

DELT Test
The Dual-ended loop test (DELT) is applicable only to ADSL2/ADSL2+ packs and
includes the complete set of DELT parameters and 512-BIN DELT results. A DELT test
needs to be executed with modem connected, because the test requires the response of
the remote terminal. The DELT test includes the following tests that can be requested
simultaneously (but only one DELT test or SELT test per pack is supported at a time.
• Channel characteristics per bin
• Quiet line noise per bin
• SNR per bin

Group of test results for:

– Line Attenuation
– Signal to Noise Ratio Margin
– Signal Attenuation
– Attainable net data rate
– ATU-R aggregate transmit power
– ATU-C aggregate transmit power
• 512 bin DELT test.
Note: The DELT test is service affecting and takes about 60 seconds for completion.
During test execution power management and Seamless Rate Adaptation (SRA) is not
applicable.

SELT test
The Single-ended loop testing (SELT) is applicable to ADSL2/ADSL2+ only, but it is
not supported by the LPA833 and LPA420. A SELT test doesn’t require a modem for
operation, moreover a SELT test should be executed without a modem connected to
avoid erroneous results due to modem inter-operability. SELT tests are supported only
for the LPA438. The SELT test provides the following diagnostics information that can
be requested simultaneously:
• Equivalent loop length estimation of a straight loop
• Prediction up-stream/down-stream data rate for the actual wire gauge
• Classification and power measurement of relevant near-end crosstalk disturbers
• Detection of radio frequency ingress (RFI) disturbers
• Detection of open/shorts
• Wire gauge measurements for the first segment of the loop only.
Note: The SELT test is running without a modem connected and is not service
affecting.

Forced power state test

Besides enabling/disabling “automatic power mode” via provisioning, ADSL2/ADSL2+
ports support a “forced power state” for test purposes. That means an ADSL2/ADSL2+
port can be configured to stay in one of the three supported power states L0, L2, L3.
A forced power state test is dependent on the port administrative state, i.e. it can only
be executed in administrative state IS. If the admin state is IS, forcing the state to L2
degrades the service and forcing the state to L3 disrupts the service. Alarming is still
enabled (admin state is IS) during forced power state.
A forced power state test needs a modem being connected to the port under test. This
test is usually done during system turn-up or pack installation or for maintenance
purposes as dependent on the forced power state the service is degraded or disrupted.
Note: The link retrains after exiting the forced power state.

Note that the LPA420 and LPA833 doesn’t support enabling/disabling of L2 and/or L3
state separately this parameter is changed to simply enable/disable automatic power
mode.

Feeder loopback testing

Overview
AFM loopback testing is used to isolate line and connectivity problems that may exist.
Feeder loopbacks can be initiated at the AnyMedia ® Access System by the methods,
listed in the following table for all the possible feeder interface types.

Loopback initiation Interface types

1
E3 DS3 E1 STM-1/
OC-3c
FEAC loopback pattern x
Receipt of OAM&P loopback command x x x x

Notes:
1. E1 type is used to support IMA functionality; E1 line loopbacks are also supported by the
E1IMA AP.

A loopback timer on the AFM allows to provision the duration of the loopback
between 1 minute and 24 hours (in steps of 1 minute). After the expiry of the loopback
timer, the loopback is released automatically. A value of 0 is interpreted as non-timed
loopback.
When port 1 is in loopback, this will be indicated by a blinking faceplate LED on the
AFM. For the LED labeling see the table below.
This table shows the LED loopback indications.

AFM pack type LED blinking

AFME3/AFMDS3 CLF1
AFME11 CLF
AFMO FAC1

Notes:
1. There is only one CLF LED for all E1 ports

Feeder loopback testing using an AFME3/DS3 in simplex mode

When an AFME3/DS3 is being used in simplex mode, an E3/DS3 line loopback can be
initiated. This loopback is only applicable for E3/DS3 port 1 of the AFM. The receive
direction for port 1 is looped back to the transmit direction. This loopback can be
initiated by the following methods:
• Detection of a FEAC loopback (16-bit pattern) code word (on a DS3 feeder only)
• Receipt of an OAM&P loopback command to activate a loopback on a designated
E3/DS3.
This loopback is service-affecting.
The FEAC code can be sent from the ATM transport network (ATM switch, SONET,
or DS3 transmission test set). In a daisy-chain configuration, the FEAC loopback
control applies only for the DS3 port that interfaces directly to the ATM transport
network.
The OAM&P loopback command can be directed to any AFME3/DS3 in a
daisy-chained network of AnyMedia® Mainshelves. The possible E3/DS3 daisy-chained
loopbacks are indicated in the following figure.

When an E3/DS3 port is in loopback, the CLF1 LED on the corresponding AFM
blinks. During the loopback, ATM signal received is looped back to the sending end,
and the E3/DS3 monitors the receive line to detect the FEAC deactivate command
code or the deactivate loopback OAM&P command.

Feeder loopback testing using AFMDS3 circuit packs in duplex mode

Feeder loopback testing using AFME3/DS3s in duplex mode is similar to the simplex
AFME3/DS3 testing described above, but with the following differences:
In a duplex AFMDS3 configuration, the FEAC loopback code word or OAM&P
loopback command is detected by the active AFMDS3 only, and is applied to both
DS3 Ports 1 (active and standby) of the active pack. (This is true whether or not the
AFMDS3 is part of a daisy chain.)
In a duplex AFME3/DS3 configuration, the CLF1 LED on both the active and standby
AFME3/DS3s blinks during loopback.
As in the simplex case above, this loopback using 2 AFME3/DS3s in duplex mode is
service-affecting.

Feeder loopback testing using an AFME1 or an E1IMA AP

When an AFME1 is being used, a line loopback that loops an individual E1 coming
from the ATM network back toward that network can be initiated. When an E1IMA
APis being used, the line loopback loops an individual E1 coming from the cascaded
shelf to the host shelf back towards the cascaded shelf. This loopback occurs at the
framer inside the pack.
On the AFME1 this loopback is service-affecting in IMA mode if there are not a
sufficient number of IMA links remaining to carry service. It is not service-affecting on
the E1IMA AP because it is allowed only on an E1 link being administratively out of
service. This loopback can be initiated by a local or remote GSI user. An IMA group
loopback is not supported on the E1IMA AP.
During the loopback, the CLF LED on the AFME1 or the E1IMA AP blinks.

Feeder loopback testing using an AFMO circuit pack in simplex mode

When an AFMO is being used in simplex mode, a forced line loopback can be
initiated. This loopback is only applicable for port 1 of the AFMO, which is cabled to
transmit toward the ATM network. This loopback can be initiated by receipt of an
OAM&P loopback command that originated locally or remotely.
This loopback is service-affecting.
The OAM&P forced loopback command can be directed to any AFMO in a
daisy-chained network of AnyMedia® Mainshelves. The possible daisy-chained
STM-1/OC-3c loopbacks are indicated in the following figure.
During the loopback, the AFMO FAC1 LED blinks.
The following figure shows STM-1/OC-3c loopbacks with shelf daisychaining.

Feeder loopback testing using an AFMO circuit pack in duplex mode

When AFMOs are being used in duplex mode, there are two types of OAM&P
loopbacks that can be initiated:
• Forced facility loopback - a requested loopback will always be initiated, whether
the feeder is active or not
• Non-forced facility loopback - a requested loopback will only be initiated if the
feeder is not active.

Both of these loopbacks are only applicable for port 1 of the AFM, which is cabled
either toward the ATM network or to the preceding shelf in a daisy chain. They may
be requested for port 1 of either the active or the standby AFM, but the request is
always made to the active AFM, since it connects to both physical ports. These
loopbacks can be initiated by receipt of an OAM&P loopback command that originated
locally or remotely.
During the loopback, the FAC1 of the AFM associated with the port being looped back
blinks yellow.
In case of a requested feeder loopback, the system behavior is different in Duplex 1+1
protection mode than it is in DBSF protection mode.
Feeder loopback testing in Duplex 1+1 protection mode
When a forced facility loopback is requested, if the Rx fiber of the port to be looped
back carries traffic, then the system attempts to switch the traffic to the other Rx
feeder before activating the loopback. If the system is successful in switching the
traffic to the other feeder, then the loopback will not be service-affecting. However, if
the traffic cannot be switched to the other feeder, then the loopback is activated
anyway; this latter case will be service-affecting.
When a non-forced facility loopback is requested, if the port to be looped back carries
traffic, then the system does not allow the loopback to be executed.
If a protection switch occurs, the loopback is terminated.
Feeder loopback testing in DBSF protection mode
If a forced loopback is initiated and the receive signal (Rx) is taken from the addressed
feeder then the system attempts to switch the receive signal to the other feeder. If the
transmit direction (Tx) is active on the addressed feeder, it will also be switched over
to the other feeder. However, if the traffic cannot be switched to the other feeder, then
the loopback is activated anyway; this latter case will be service-affecting.
If the facility to be looped back is the protecting facility then the laser is switched on
after sending a confirmation message to all OAM&P interfaces.
For testing the connection between the optical couplers and the protecting feeder a
non-forced non-service affecting loopback can be initiated.
When a non-forced facility loopback is requested, if the port to be looped back carries
traffic, then the system does not allow the loopback to be executed.
Important! In any case, before initiating the loopback, the operator has to
disconnect at least the transmit direction (Tx) of the addressed feeder between the
optical coupler (combiner) and AFMO. When initiating the loopback a confirmation
message at the GSI reminds the operator to disconnect the feeder and the laser of
the feeder is switched on after confirmation to allow measurements.

Diagnosing network troubles using F4/F5 OAM cells

Overview
In ATM architecture, one of the responsibilities of the ATM layer is maintenance. One
way it does this is by supporting ATM OAM cells, i.e., F4 and F5 cells. F4 cells are
used for VP maintenance and F5 cells are used for VC maintenance.
One of the ATM layer fault management functions supported is F4/F5 loopbacks. The
AnyMedia ® Access System supports these loopbacks in 2 ways:
• By responding to externally generated LB (loopback) cells
• By generating, within the AnyMedia ® Access System, LB cells.
These two types of loopback support are discussed below.

Response to externally generated LB cells

The AnyMedia ® Access System responds to certain LB (loopback) cells that are
injected into VPs or VCs by an ATM switch or external ATM test equipment. It does
so by returning the cell back toward the direction from which the cell was received.
The AnyMedia ® Access System responds to the following types of LB (loopback) cells
generated from the network:
• F4 end-to-end LB cells with the AFM provisioned as the connection endpoint, i.e.,
connections with the VPI equal to Shelf VPI
• F4 segment LB cells with the AFM provisioned as the segment endpoint (the AFM
can be provisioned as an F4 segment endpoint for connections with any VPI value)
• F5 segment LB cells with the AFM provisioned as the segment endpoint (the AFM
can be provisioned as an F5 segment endpoint only for connections with the VPI
equal to Shelf VPI
• F5 end-to-end LB cells received on the BB ATM Operations Channel.
All other F4/F5 cells are passed through the AnyMedia® shelf.
ATM switch (F4/F5) and modem (F5) support is required.
The AFM will process up to 100 OAM (includes AIS, RDI, and LB) cells per second.
The excess OAM cells will be dropped arbitrarily.
“Use of F4/F5 cells to diagnose a network problem” (p. 4-46) illustrates the use of
F4/F5 cells to diagnose a network problem. F4 cells looping at different nodes are
injected into the network. These cells contain a loopback address field that indicates at
which node they are to be looped back. If, for example, one sends a loopback cell
(such is LB cell a in “Use of F4/F5 cells to diagnose a network problem” (p. 4-46)) to
the end node (in this case, the AnyMedia ® Access System), and that cell is successfully
looped back, then no problems are indicated. If that loopback fails, one then sends a
loopback cell (such as LB cell c) to be looped back at a closer node (such as node 2).
If that cell is successfully looped back, then the problem is between node 2 and the

AnyMedia ® Access System. One then increases the loopback segment length (to node 3
in “Use of F4/F5 cells to diagnose a network problem” (p. 4-46)) until the problem is
isolated.

Use of F4/F5 cells to diagnose a network problem

This figure shows the use of F4/F5 cells to diagnose a network problem.

Internal generation of LB cells

At the request of the operator, the AnyMedia ® Access System can originate loopback
tests. It does this by inserting an LB cell and waiting for a response in the reverse
direction.
The AnyMedia ® Access System can generate the following types of LB cells when the
Feeder VPI is a Shelf VPI:
• F4 end-to-end LB cells in the upstream direction
• F4 segment LB cells in upstream direction
• F5 end-to-end LB cells in the upstream or downstream direction
• F5 segment LB cells in the upstream or downstream direction.
The AnyMedia ® Access System can generate the following types of LB cells when the
Feeder VPI is a local VPI or downstream VPI:
• F4 end-to-end LB cells in the upstream or downstream direction
• F4 segment LB cells in the upstream or downstream direction.

ATM payload loopback

Description
The ATM payload loopback feature loopbacks the ATM cells of a virtual path or
virtual connection. This can be done in both directions, towards the subscriber’s CPE
(downstream) or towards the ATM network (upstream). ATM payload loopbacks are
initiated on ATM VC level and ATM VP level. Their duration is provisionable. Up to
eight ATM payload loopbacks can be supported simultaneously.
The figure below shows an example (with SHDSL) for use of ATM payload loopbacks.
The modems connected to the AnyMedia ® Access System via SHDSL are CES
modems which emulate circuits, i.e. they get/send VC payload from/to the AnyMedia ®
Access System via SHDSL and send/get TDM payload to/from the E1 tester.

Initiating an ATM payload loopback

An ATM payload loopback can only be initiated if the cross-connection has been
provisioned as local VPC or VCC, the administrative state of the connection is IS (in
service), no loopback (F4/F5 or ATM payload loopback) is in progress for that
cross-connection and a maximum number of active loopbacks is not exceeded. The test
result is retrievable.

SHDSL loopback test

Description
An SHDSL loopback test is used to detect a transmission failure manually. The main
purpose of the loopback is to inject traffic into the system using an external equipment
which is also responsible for measuring the BER in the loop.
The required parameters are the shelf type, slot number of the SHDSL pack, the port
number, the test type and duration of the SHDSL loopback test. If the CPEs are
connected to a bonded pair of SHDSL lines, either the even or the odd port number
can be used as a parameter for the invocation of the loopback tests.
Following loopback tests are available:
• CPE Network Port Loop (loopback test between the CPEs SHDSL framer at the
network port and the corresponding port of the SHDSL AP.
• Network CBR Maintenance Loop (loopback test between the CPEs CES framer at
the CBR user port and the corresponding port of the SHDSL AP).
• User CBR Local Port Loop (loopback test at the CBR port of the CPE)
• User CBR Payload Loop (loopback test at the CBR framer of the CPE)
• Dual Network and Serial Port Loop (bidirectional loopback test involving the CPEs
SHDSL network port (upstream) and the user serial port (downstream)).
The SHDSL loopback test is service-affecting and takes about 60 seconds to 86,400
seconds (1 minute thru 24 hours) for completion.
Once the loopback tests are finalized, following error statistics are displayed in
upstream and downstream direction:
• Code Violations (CV)
• Errored Seconds (ES)
• Severely Errored Seconds (SES)
• Loss of Word Sync Failure (LOSWS)
• Unavailable Seconds (UAS).

CPE Routing - remote access to CPEs

Description
The CPE routing process is used to specify the parameters to setup a new CPE remote
connection on the specified SHDSL ATM line.
The network operator uses the NAM or the GSI to configure the routing functions in
the AFM. In this way the cross-connections are created which route the CPE OAM&P
traffic towards the proper SHDSL port. Once this setup is done, the CPE OAM&P
functions can be accessed by regular SNMP, HTTP and Telnet applications to provision
CPEs.
The remote provisioning of the CPEs is based on the inband VC connection which is
available via the CPE SHDSL network port. The AFM controller implements routing
and network address translation functions so, that the CPE OAM&P IP is visible on the
customer OAM&P network. This function is supported only by the SHDSL application
pack (LPS702) and requires that a CellPipe 40H/41H SHDSL modem is connected and
trained.
In downstream direction, the AFM receives from the network an SNMP/Telnet/HTTP
message through its inband OAM&P channel with destination port (dest Port). The
message is routed to the CPE connected to the corresponding SHDSL ATM port
replacing the destination IP address (dest IP) by the corresponding CPE IP address
(CPE_IP), and the destination port (dest Port) by the corresponding CPE
SNMP/Telnet/HTTP port.
In upstream direction, the AFM receives from the subscribers connected to the LPS702
packs an SNMP/Telnet/HTTP message. The message is routed to the network through
its inband OAM&P channel replacing the message source IP address of the CPE
(source IP) by its in-band IP address (AFM_IN_BAND_IP). Additionally, if the
message source Port (source Port) is the SNMP/Telnet/HTTP port configured in the
routing table for the CPE side of that SHDSL ATM port, then the source Port is
replaced by the corresponding AFM network side SNMP/Telnet/HTTP port.
The following figure illustrate how the AFM routes a telnet message in downstream
direction.

ATM xDSL performance management

Purpose
Performance management is the system activity for collecting and reporting data on the
quality of transmission on the ATM feeder and on the ADSL, SHDSL and E1
distribution. In an IMA application (AFME1 or E1IMA AP) performance management
parameters are collected for IMA links and the IMA group. Performance management
operation includes data collection, specification of thresholds for TCAs, and
performance management data over ATM OAM&P interfaces. ATM xDSL performance
management also includes ATM cell traffic statistics.
Performance Management data is also collected and reported for the CPU load of the
active AFM.
Finally, VP and VC connections can be monitored using F4/F5 Continuity Check cells,
to indicate that the specified connections can carry cells, even if no end-user data has
been transmitted recently.
If a protection switch is performed, the current 15-minute and current 24-hour counts
are marked as corrupt. All the previous, the current 24-hour and recent 95 15-minute
performance counts are not lost due to protection switch.
The ATM xDSL performance management functions are identical for all configurations
of the AnyMedia ® Access System, regardless of which shelf type is used.

Contents

ATM feeder performance management 4-52

ADSL performance management 4-60
SHDSL performance management 4-65
IMA performance management 4-67
ATM cell traffic 4-68

ATM feeder performance management

ATM feeder performance management operation

For performance management, the system continuously collects performance
management data internally. These data can be retrieved via the ATM OAM&P
interfaces on a 15-minute or 24-hour basis. E3 and E1 performance management aligns
with the recommendations in ITU G.826, ETS 300 417-1 path monitoring. DS3
performance management aligns with the recommendations in Telcordia’s GR-820 for
DS3 path monitoring.
Note that the description of the E1 performance management applies to the E1 feeders
of the AFME1 and to the E1IMA AP.
The lists below show the performance management data being collected for the various
ATM feeder interfaces and for IMA (used with AFME1 and E1IMA AP only).

E3 performance management data

E3 performance management data is collected for the following items:
• Errored seconds (ES)
• Unavailable seconds (UAS).
E3 performance management data is stored as follows for each parameter:
• For the current 15-minute interval
• For the previous 96 15-minute intervals (for a total equal to 24 hours)
• From rolling 24-hour totals. This means the register always contains the sum of the
last 96 15-minute counts.

DS3 performance management data

DS3 performance management data is collected for the following items:
• P-bit severely errored seconds (PSES)
• Unavailable seconds (UAS).
DS3 performance management data is stored as follows for each parameter:
• For the current 15-minute interval
• For the previous 96 15-minute intervals (for a total equal to 24 hours)
• From rolling 24-hour totals. This means the register always contains the sum of the
last 96 15-minute counts.

STM-1 performance management data

STM-1 performance management data is collected for the following items:
Regenerator Section Near End PM parameters:
• Regenerator Section - Near End Background Block Error (RS-N-BBE)
• Regenerator Section - Near End Errored Seconds (RS-N-ES)

• Regenerator Section - Near End Severely Errored Seconds (RS-N-SES)

• Regenerator Section - Near End Unavailable Seconds (RS-N-UAS)
• Regenerator Section - Near End Unavailable Time (RS-N-UAT)
There is no Far End Regenerator Section PM defined.
Multiplex Section Near End PM parameters:
• Multiplex Section - Near End Background Block Error (MS-N-BBE)
• Multiplex Section - Near End Errored Seconds (MS-N-ES)
• Multiplex Section - Near End Severely Errored Seconds (MS-N-SES)
• Multiplex Section - Near End Unavailable Seconds (MS-N-UAS)
• Multiplex Section - Near End Unavailable Time (MS-N-UAT)
Multiplex Section Far End PM parameters:
• Multiplex Section - Far End Background Block Error (MS-F-BBE)
• Multiplex Section - Far End Errored Seconds (MS-F-ES)
• Multiplex Section - Far End Severely Errored Seconds (MS-F-SES)
• Multiplex Section - Far End Unavailable Seconds (MS-F-UAS)
• Multiplex Section - Far End Unavailable Time (MS-F-UAT)
Path Near End PM parameters:
• Path Near End Background Block Errors (HP-N-BBE)
• Path Near End Errored Seconds (HP-N-ES)
• Path Near End Severely Errored Seconds (HP-N-SES)
• Path Near End Unavailable Second (HP-N-UAS)
• Path Near End Unavailable Time (HP-N-UAT)
Path Far End PM parameters:
• Path Far End Background Block Errors (HP-F-BBE)
• Path Far End Errored Seconds (HP-F-ES)
• Path Far End Severely Errored Seconds (HP-F-SES)
• Path Far End Unavailable Second (HP-F-UAS)
• Path Far End Unavailable Time (HP-F-UAT)
Far-End Path Layer performance-monitoring is not be supported in the case of Duplex
1+1 protection mode and DBSF protection mode. However, the Far-End Path PM data
is taken from the active AFMO on both AFMOs. During a protection switch the
Far-End Path PM counts are marked as corrupt and the new active AFMO is now
providing the Far End PM counts.
STM-1 performance management data is stored as follows for each parameter:
• For the current and previous 15-minute interval
• For the current and previous 24-hour interval
• For 95 additional previous 15-minute intervals (for a total equal to 24 hours).

OC-3c performance management data

OC-3c performance management data is collected for the following items:
Section Near End PM parameter:
• Section - Near End - Coding violations (CV-S)
• Section - Near End - Errored Seconds (ES-S)
• Section - Near End - Severely Errored Seconds (SES-S)
• Section - Near End - Errored Framing Seconds (SEFS-S)
Line Near End PM parameters:
• Line - Near End - Coding violations (CV-L)
• Line - Near End - Errored Seconds (ES-L)
• Line - Near End - Severely Errored Seconds (SES-L)
• Line - Near End - Unavailable Seconds (UAS-L)
• Line - Near End - Failure Counts (FC-L)
• Protection Switching Counts (PSC)
Line Far End PM parameters:
• Line - Far End - Coding Violations (CV-LFE)
• Line - Far End - Errored Seconds (ES-LFE)
• Line - Far End - Severely Errored Seconds (SES-LFE)
• Line - Far End - Unavailable Seconds (UAS-LFE)
• Line - Far End - Failure Counts (FC-LFE)
Path Near End PM parameters:
• Path Near End Coding Violations (CV-P)
• Path Near End Errored Seconds (ES-P)
• Path Near End Severely Errored Seconds (SES-P)
• Path Near End Unavailable Seconds (UAS-P)
• Path Failure Counts (FC-P)
Path Far End PM parameters:
• Path Far End Coding Violations (CV-PFE)
• Path Far End Errored Seconds (ES-PFE)
• Path Far End Severely Errored Seconds (SES-PFE)
• Path Far End Unavailable Seconds (UAS-PFE)
• Path Far End Failure Counts (FC-PFE)
Far-End Path Layer performance-monitoring is not be supported in the case of Duplex
1+1 protection mode and DBSF protection mode. However, the Far-End Path PM data
is taken from the active AFMO on both AFMOs. During a protection switch the
Far-End Path PM counts are marked as corrupt and the new active AFMO is now
providing the Far End PM counts.

OC-3c performance management data is stored as follows for each parameter:

• For the current and previous 15-minute interval
• For the current and previous 24-hour interval
• For 95 additional previous 15-minute intervals (for a total equal to 24 hours).

E1 performance management data

E1 path layer performance management data is collected for the following items
• Errored Block (EB)
• Errored Second (ES)
• Severely errored second (SES)
• Background Block Errors (BBE)
• Unavailable Seconds (UAS).
E1 performance management data is stored as follows for each parameter:
• For the current and previous 15-minute interval
• For the current and previous 24-hour interval
• For 95 additional previous 15-minute intervals (for a total equal to 24 hours).

IMA performance management data

IMA group performance management data is collected for the following items:
• IMA group unavailable seconds (GR-UAS-IMA)
• Near end group failure count (GR-FC).
IMA link performance management data is collected for the following items on a
per-link basis:
• ICP violations (count of errored, invalid or missing ICP cells (IV-IMA)
• IMA severely errored seconds (SES-IMA)
• IMA unavailable seconds (UAS-IMA)
• IMA transmit unusable seconds (Tx-UUS-IMA)
• IMA receive unusable seconds (Rx-UUS-IMA).
IMA-related performance management data is stored as follows:
• For the current and previous 15-minute interval
• For the current and previous 24-hour interval
• For 95 additional previous 15-minute intervals (for a total equal to 24 hours).
The 24-hour interval start time is configurable. The default start time is midnight.

Retrievable counts
For 15-minute reports, each occurrence of one of the events listed above for each
feeder type increments the ″current″ counter. After a 15-minute interval ends, the count
is moved to the ″previous″ interval and then starts over again at zero. Both the
″current″ and the ″previous″ 15-minute performance management counts are stored.
....................................................................................................................................................................................................................................
363-211-586 4-55
Issue 6, July 2007
OAM&P for ATM xDSL services ATM feeder performance management

The AFME1 and AFMO support a current 24-hour interval register and a previous
24-hour interval register. The current 24-hour register contains the impairment count
for the parameter during a 24-hour interval. It summarizes the values of the current
15-minute registers at the end of each 15-minute interval. The current register is reset
to zero at the end of the 24-hour interval after the data is transferred to the previous
24-hour register (the old data from the previous 24-hour register is discarded). The
current 24-hour register does not store a rolling 24-hour counter.
Depending on the AFM type the following counts can be retrieved from the GSI:
The following table shows, depending on AFM type, which counts can be retrieved
from the GSI.

AFME3/DS3 AFME1 (E1 AFME1 (IMA AFMO

PM) PM)
Current 15-minute interval X X X X
register
Previous 15-minute interval X X X X
register
Last 24-hour register (rolling X - - -
report)
Most recent 15-minute recent 95 95 95 95
interval registers
Current 24-hour interval register - X X X
Previous 24-hour interval register - X X X

Performance management can be disabled or enabled. Performance management

disabled is the default condition on turn-up. This inhibits generation of autonomous
reports during turn-up or system tests, or when not required.
Once a performance management count exceeds a threshold, an autonomous message is
sent through the ATM OAM&P interfaces to indicate a TCA. The threshold values can
be set externally for the individual performance management counts.
A performance management data register is marked as corrupt when the register
contains data for a period less than the nominal accumulation interval. Some examples
of when a register is marked as corrupt include the following:
• When PM counting has just been enabled (that is, if PM is enabled in the middle
of a counting interval, then the affected registers will be marked as corrupt)
• When PM registers have just been cleared
• During the time that PM is disabled.
If an AFM protection switch is performed, the current feeder PM count is marked as
corrupt.

When PM is enabled, a PM register will not be marked as corrupt under the following
conditions:
• When the register is for a previous interval and it has been allowed to accumulate
data for its entire period
• When the register is for a current interval, and it started counting at the beginning
of the interval and has accumulated some data without being cleared.

ATM feeder performance management capabilities

Performance management has general capabilities as follows:
• Retrieve performance management information
• Set and retrieve the threshold crossing alert values. The ranges for these values for
the 15-minute counter threshold and for the 24-hour counter threshold are shown in
the following tables. The default values for the PM thresholds for feeder port 1 and
feeder port 2 are provided in “Turn-up and service activation provisioning default
values” (p. 6-116).
• Reset the performance management counts
• Report the occurrence of a TCA
• Allow/inhibit the TCA reporting.
The following table shows the E3 performance management threshold crossing alert
values.

Performance Parameters 15-minute Counter 24-hour Counter

Threshold Threshold
Range Range
ES (Errored seconds) 1 to 900 1 to 86,400
UAS (Unavailable seconds) 1 to 900 1 to 86,400

The following table shows the DS3 performance management threshold crossing alert
values

Performance Parameters 15-minute Counter 24-hour Counter

Threshold Threshold
Range Range
PSES (P-bit severely errored 1 to 900 1 to 86,400
seconds)
UAS (Unavailable seconds) 1 to 900 1 to 86,400

The following table shows the E1 performance management threshold crossing alert
values.

Performance Parameters 15-minute Counter 24-hour Counter

Threshold Threshold
Range Range
ES Errored seconds 1 to 900 1 to 86,400
SES Severely errored second 1 to 900 1 to 86,400
UAS Unavailable seconds 1 to 900 1 to 86,400

The following table shows the IMA link threshold crossing alert values.

Performance Parameters 15-minute Counter 24-hour Counter

Threshold Threshold
Range Range
IV-IMA 1 to 8192 1 to 32,768
SES-IMA 1 to 300 1 to 1000
UAS-IMA 1 to 300 1 to 1000
Tx-UUS-IMA 1 to 300 1 to 1000
Rx-UUS-IMA 1 to 300 1 to 1000

The following table shows the E1 IMA group threshold crossing alert values.

Performance Parameters 15-minute Counter 24-hour Counter

Threshold Threshold
Range Range
UAS-IMA 1 to 100 1 to 300
FC 1 to 1000 1 to 5000

The following table shows the STM-1 regenerator section performance management
threshold crossing alert values.

Performance Parameters 15-minute Counter 24-hour Counter

Threshold Threshold
Range Range
RS-N-ES, RS-N-SES, RS-N-UAS 1 to 900 1 to 65,535
RS-N-BBE 1 to 65,535 1 to 65,535

The following table shows the STM-1 multiplex section near end and far end
performance management threshold crossing alert values.

Performance Parameters 15-minute Counter 24-hour Counter

Threshold Threshold
Range Range
MS-N-ES, MS-N-SES, 1 to 900 1 to 65,535
MS-N-UAS, MS-F-ES,
MS-F-SES, MS-F-UAS
MS-N-BBE, MS-F-BBE 1 to 65,535 1 to 65,535

The following table shows the OC-3c section performance management threshold
crossing alert values.

Performance Parameters 15-minute Counter 24-hour Counter

Threshold Threshold
Range Range
CV-S 1 to 16,383 1 to 1,048,575
ES-S 1 to 900 1 to 65,535
SES-S 1 to 900 1 to 65,535
SEFS-S 1 to 900 1 to 65,535

The following table shows the OC-3c line near end and far end performance
management threshold crossing alert values.

Performance Parameters 15-minute Counter 24-hour Counter

Threshold Threshold
Range Range
CV-L, CV-LFE 1 to 16,383 1 to 1,048,575
ES-L, ES-LFE 1 to 900 1 to 65,535
SES-L, SES-LFE 1 to 900 1 to 65,535
UAS-L, UAS-LFE 1 to 900 1 to 65,535

ADSL performance management

ADSL performance management operation

For performance management on the ADSL spans, the system continuously collects
performance management data internally, and an external system can retrieve this data
on a 15-minute or 24-hour basis. ADSL performance management is consistent with
the specifications in ANSI T1.413, Issue 2 and ITU-T G992.1 for error performance
parameter reporting for ADSL transmission.
Performance management data are collected on ADSL interface for the events shown in
the next table and on ATM level for the events shown in the table after.
The following table shows the ADSL performance management data on ADSL
interface level.

Upstream Downstream
ES ES
CV CV
EC EC
HBER failure HBER failure
LOS failure LOS failure
LOF failure RFI failure
Dying gasp events at the modem N/A
Superframes transmitted on the ADSL port N/A
Superframes received on the ADSL port N/A

The following table shows the ADSL performance management data on ATM level.

Upstream Downstream
Loss Of Cell Delineation Loss Of Cell Delineation.
No Cell Delineation. No Cell Delineation.
Header Error Control Violation. Header Error Control Violation.

Performance management data for the current 15-minute interval and for one previous
15-minute interval of these counts are stored. Also, data for the current 24-hour
interval and one previous 24-hour interval are stored. All counts can be retrieved from
the ATM OAM&P interfaces.
Once a performance management count exceeds a threshold, an autonomous report is
generated to indicate a TCA. The threshold values can be set externally for the
individual performance management counts. TCA messages can be inhibited. SNMP

MIB profiles are used to set the thresholds for ADSL performance management TCAs.
Predefined ADSL profiles are described in “Predefined ADSL performance
management profiles” (p. 6-133).

ADSL performance management capabilities

ADSL performance management has general capabilities as follows:
• Retrieve performance management information
• Set and retrieve the threshold values for TCA generation for certain parameters, as
indicated in the next table.
• Reset the performance management counts.
• Report the occurrence of a TCA for certain parameters.
• Allow/inhibit the TCA reporting for certain parameters.
The following table shows the ADSL performance management threshold crossing alert
values.

Performance Parameters 15-minute Counter 24-hour Counter Threshold

Threshold
Range Range
Upstream ES 1 to 900 1 to 86,400
HBER failure 1 to 90 1 to 8,640
LOS failure 1 to 90 1 to 8,640
LOF failure 1 to 90 1 to 8,640
CV TCA not supported TCA not supported
EC TCA not supported TCA not supported
Dying gasp events at TCA not supported TCA not supported
the modem
Superframes TCA not supported TCA not supported
transmitted on the
ADSL port
Superframes received TCA not supported TCA not supported
on the ADSL port
Loss Of Cell TCA not supported TCA not supported
Delineation.
No Cell Delineation. TCA not supported TCA not supported
Header Error TCA not supported TCA not supported
Correction Violation.

Downstream ES 1 to 900 1 to 86,400

HBER failure 1 to 90 1 to 8,640
LOS failure 1 to 90 1 to 8,640
RFI failure 1 to 90 1 to 8,640
CV TCA not supported TCA not supported
EC TCA not supported TCA not supported
Loss Of Cell TCA not supported TCA not supported
Delineation.
No Cell Delineation. TCA not supported TCA not supported
Header Error TCA not supported TCA not supported
Correction Violation.

The TCA for a given parameter is inhibited by setting the threshold to zero (numeral
0).
As stated earlier, SNMP MIB profiles are used to set the thresholds for ADSL
Performance Management TCAs. The AnyMedia ® Access System contains a library of
two built-in ADSL performance management profiles. The profiles are provided in
“Predefined ADSL performance management profiles” (p. 6-133).
The performance parameters listed in the following table are those for which TCAs are
not provided. The value range for each PM counter for those parameters is given.
The following table shows the ADSL performance management counter value ranges.

Performance Parameters 15-minute Counter 24-hour Counter Range

Range
Upstream CV 0 to 52,920 0 to 5,080,320
EC 0 to 52,920 0 to 5,080,320
Dying gasp events at 0 to 90 0 to 900
the modem
Superframes (blocks) 0 to 52,920 0 to 5,080,320
transmitted on the
ADSL port
Superframes (blocks) 0 to 52,920 0 to 5,080,320
received on the
ADSL port
Loss Of Cell 0 to 52,920 0 to 5,080,320
Delineation.
No Cell Delineation. 0 to 52,920 0 to 5,080,320
Header Error 0 to 52,920 0 to 5,080,320
Correction Violation.

Performance Parameters 15-minute Counter 24-hour Counter Range

Range
Downstream CV 0 to 52,920 0 to 5,080,320
EC 0 to 52,920 0 to 5,080,320
Loss Of Cell 0 to 52,920 0 to 5,080,320
Delineation.
No Cell Delineation. 0 to 52,920 0 to 5,080,320
Header Error 0 to 52,920 0 to 5,080,320
Correction Violation.

ADSL line monitoring

The ADSL line monitoring is used to retrieve capabilities for the ADSL lines between
the AnyMedia ® Access System and the ADSL modem at the customer site.
This is done by displaying the number of bits (0...15) which are transmitted (or
allocated on every 4.3 kHz tone frequency used by the ADSL DMT (Discrete Multi
Tone) line coding.
According to the ADSL standards the channels 0 to 31 are used for the upstream traffic
while the remainder channels are used for downstream traffic.
The following table shows the channel range used for ADSL line monitoring in
upstream and downstream direction.

ADSL and ADSL-lite Line Monitoring Channel range

Upstream 0 to 31
Downstream 32 to 255
32 to 127 in case of ADSL-lite(1)

Notes:
1. ADSL-lite and ADSL2-lite are not supported in the LPA833 and LPA420. Several legacy
ADSL packs support ADSL-lite but don′t support bin configuration in R1.27.

The channel ranges used for ADSL2/ADSL2+ line monitoring in upstream and
downstream direction is shown in the following table.

ADSL2 and ADSL2+ Line Monitoring Channel range

Upstream 0 to 31
Downstream 32 to 255 in case of ADSL / ADSL2
32 to 511 in case of ADSL2+

The information how many bits per channel are used is displayed on the GSI in a table
with columns for upstream (US) and downstream (DS) bit allocation. Furthermore a
graphical display (on the GSI) shows the used channels in the ADSL line spectrum. It
is possible to increase the frequency resolution of the graphical output by specifying
the start and the stop position of the channels.

SHDSL performance management

SHDSL performance management operation

For performance management on the SHDSL spans, the system continuously collects
performance management data internally, and an external system can retrieve this data
on a 15-minute or 24-hour basis. SHDSL performance management is consistent with
the specifications in ITU-T G. 991.2, (02/2001) for error performance parameter
reporting for SHDSL transmission.
SHDSL performance management data are collected for the events shown in the
following table.

Upstream Downstream
ES ES
SES SES
UAS UAS

Performance management data for the current 15-minute interval and for one previous
15-minute interval of these counts are stored. Also, data for the current 24-hour
interval and one previous 24-hour interval are stored. All counts can be retrieved from
the ATM system OAM&P interfaces.
Once a performance management count exceeds a threshold, an autonomous report is
generated to indicate a TCA. The threshold values can be set externally for the
individual performance management counts. TCA messages can be inhibited. SNMP
MIB profiles are used to set the thresholds for SHDSL performance management
TCAs. Predefined SHDSL profiles are described in “Predefined SHDSL performance
management profiles” (p. 6-134).

SHDSL performance management capabilities

SHDSL performance management has general capabilities as follows:
• Retrieve performance management information.
• Set and retrieve the threshold values for TCA generation, as indicated in the next
table.
• Reset the performance management counts.
• Report the occurrence of a TCA.
• Allow/inhibit the TCA reporting.

The following table shows the SHDSL performance management threshold crossing
alert values.

Performance Parameters 15-minute Counter 24-hour Counter

Threshold Range Threshold Range
Upstream ES 1 to 900 1 to 86,400
SES 1 to 900 1 to 86,400
UAS 1 to 900 1 to 86,400
Downstream ES 1 to 900 1 to 86,400
SES 1 to 900 1 to 86,400
UAS 1 to 900 1 to 86,400

The TCA for a given parameter is inhibited by setting the threshold to zero (numeral
0).
As stated earlier, SNMP MIB profiles are used to set the thresholds for SHDSL
performance management TCAs. The AnyMedia ® Access System contains a library of
two predefined SHDSL performance management profiles. The profiles are provided in
“Predefined SHDSL performance management profiles” (p. 6-134).

IMA performance management

IMA performance management operation

For performance management on the E1 lines of an E1IMA AP refer to “E1
performance management data” (p. 4-55) and “IMA performance management data”
(p. 4-55).
Performance management thresholds for E1 ports and IMA groups/links are
auto-created when an E1IMA AP is provisioned. If threshold values are changed to ″0″,
threshold crossing alerts are disabled.

ATM cell traffic

Overview
The AnyMedia ® Access System provides ATM traffic statistics on demand. It collects
counts of events for the entire shelf as well as for specific connections over 15-minute
and 24-hour monitoring intervals for the current and the previous 15-minute and
24-hour intervals.

ATM traffic statistics operation - shelf-level

The following statistics can be collected for the entire shelf:
Upstream direction
• Total number of cells sent to the ATM network
• Total number of cells dropped due to PPD when the system is in congestion state
• Total number of cells dropped due to EPD when the system is in congestion state
• Total number of AAL5 frames dropped due to EPD when the system is in
congestion state
• Total number of cells lost due to buffer overflow.
Downstream direction
• Total number of cells sent to daisy-chained shelves
• Total number of cells sent to all distribution ports connected to this shelf.
When enabled for collection, the BB subsystem collects the shelf-level ATM traffic
statistics for all connections established at the shelf, regardless of whether they are
enabled for collection of connection-level specific statistics or not. All cells passing
through the system are taken into account. The counts also include OAM cells.
As the default, shelf-level ATM traffic statistics are disabled. Statistics connections can
be enabled to use the default threshold values, or these default values can be changed
as per the range given in “ATM traffic statistics capabilities” (p. 4-69).
Important! The system is in congestion state when a CLP1 threshold is crossed.

ATM traffic statistics operation - connection-level

ATM traffic statistics collection is supported for up to 128 ATM cross-connections per
shelf including the ATM Operations Channel.
The following statistics can be collected for the ATM Operations Channel:
• Upstream direction
– Number of cells (untagged) sent to the ATM network interface
– Number of cells received from the AFM controller function
• Downstream direction
– Number of cells received from the ATM network interface
– Number of cells transmitted to the AFM controller function.
...................................................................................................................................................................................................................................
4-68 363-211-586
Issue 6, July 2007
OAM&P for ATM xDSL services ATM cell traffic

The following statistics can be collected on a per connection basis:

• Upstream direction
– Number of cells (tagged and untagged) sent to the ATM network interface
– Number of cells received from an end-user port
– Number of CLP1 cells received from an end-user port
– Number of cells tagged by the AFM
These are cells tagged by the AFM. Already tagged cells received by the BB
subsystem are not included in this count.
– Number of cells dropped due to policing.
• Downstream direction
– Number of cells received from the ATM network interface
– Number of cells transmitted to an end-user port.
A technician may choose to activate statistics collection on the following:
• All connections on an AP
• All connections on an end-user port
• An individual connection.
A technician may provision up to 128 ATM connection-level traffic threshold profiles.
Each connection has a profile associated with it. However, statistics collection can only
be enabled for 128 connections at any given time. The use of threshold profiles
simplifies the provisioning of ATM traffic statistics.

ATM traffic statistics capabilities

ATM traffic statistics has general capabilities as follows:
• Retrieve ATM traffic statistics information
• Set and retrieve the threshold values for TCA generation for those statistics
indicated in the table below
• Reset the ATM traffic statistics counts
• Report the occurrence of a TCA
• Allow/inhibit the TCA reporting.
The following table shows the TCA threshold values for ATM traffic statistics
parameters on shelf-level (in upstream direction).

ATM traffic statistics Range (in steps of 1 Default threshold

parameter cell or 1 frame as value
applicable)
Total number of cells dropped due to PPD
15 Minute Interval 0 to 318000 cells 1000 cells
24 Hour Interval 0 to 30.6 × 10 6 cells 1 × 10 6 cells
Total number of cells dropped due to EPD

ATM traffic statistics Range (in steps of 1 Default threshold

parameter cell or 1 frame as value
applicable)
15 Minute Interval 0 to 318000 cells 1000 cells
24 Hour Interval 0 to 30.6 × 10 6 cells 1 × 106 cells
Total number of cells lost due to buffer overflow
15 Minute Interval 0 to 318000 cells 1000 cells
6
24 Hour Interval 0 to 30.6 × 10 cells 1 × 106 cell
Total number of AAL5 frames dropped due to EPD
15 Minute Interval 0 to 318000 frames 1000 frames
24 Hour Interval 0 to 30.6 × 10 6 frames 1 × 106 frames

The following table shows the TCA threshold values for ATM traffic statistics
parameters on connection-level (in upstream direction).

ATM traffic statistics Range (in steps of 1 Default threshold

parameter cell) value
Number of cells tagged by the AFM (not applicable for ATM Operations Channel
statistics)
15 Minute Interval 0 to 87000 cells 3000 cells
24 Hour Interval 0 to 84 × 10 6 cells 3 × 106 cells
Number of cells dropped due to policing (not applicable for ATM Operations Channel
statistics)
15 Minute Interval 0 to 87000 cells 3000 cells
24 Hour Interval 0 to 84 × 10 6 cells 3 × 106 cells

The TCA for a given parameter is inhibited by setting the threshold to zero.

Retrievable counts
For 15-minute reports, each occurrence of one of the events listed above increments
the ″current″ counter. At the end of a 15-minute interval, the count is moved to the
″previous″ interval and then counting starts over again at zero. Both the ″current″ and
the ″previous″ 15-minute performance management counts are stored.
For 24-hour measurements the BB subsystem supports a current 24-hour interval
register and a previous 24-hour interval register. The current 24-hour register adds to
its total the values of the current 15-minute registers at the end of each 15-minute
interval. The current 24-hour register is reset to zero at the end of the 24-hour interval
after the data has been transferred to the previous 24-hour register. (The old data from
the previous 24-hour register is discarded). The start time for the 24-hour register is
provisionable; the default value for this start time is ″0″ (i.e., midnight).
....................................................................................................................................................................................................................................
4-70 363-211-586
Issue 6, July 2007
OAM&P for ATM xDSL services ATM cell traffic

At the shelf-level, all statistics counts listed in “ATM traffic statistics operation -
shelf-level” (p. 4-68)can be retrieved.
At the connection-level, the following ATM traffic statistics can be retrieved:
• ATM traffic statistics belonging to all connections on an AP
• ATM traffic statistics belonging to all connections on an end-user port
• ATM traffic statistics belonging to all connections which are enabled for statistics
collection
• ATM traffic statistics belonging to individual connections, including the ATM
Operations Channel.
In addition, information indicating which connections are activated for ATM traffic
statistics collection can be retrieved.

AFM CPU load

The system tracks the CPU load of the active AFM as follows:
• Continuously monitors the time the CPU is not idle
• Every 10 seconds, computes the fraction of time the CPU was not idle in the
10-second measurement interval that just ended
• Every 5 minutes, computes the average of the 30 10-second measurement intervals
that just completed.
A technician can retrieve CPU load data for the following time intervals:
• The most recently completed 10-second measurement interval
• The 5-minute interval that is currently accumulating (i.e., the current register)
• The 288 most recently completed intervals (i.e., the recent history registers).

ATM continuity check

ATM continuity check is a mechanism for monitoring ATM-layer transmission. In
particular, the purpose of the ATM continuity check mechanism is to indicate that a
connection can carry cells, even if no end-user data has been transmitted recently.
When continuity check has been activated on a connection, OAM continuity check
cells are inserted by the originating point. When the terminating point has not received
end-user traffic cells or a continuity check cell for a given time interval (3.5 ± 0.5
seconds), the terminating point responds as follows:
• It declares a Loss of Continuity (LOC) defect and issues an alarm
• It transmits an ATM layer RDI in the backward direction on the affected ATM
connection.
• It transmits an ATM layer AIS in the forward direction on the affected ATM
connection.
F4 continuity check cell flows are used for VP connections and F5 continuity check
cell flows are used for VC connections.

Continuity checks can be performed end-to-end, or they can performed for a segment
of a connection. Each continuity check can be provisioned with any of the following
options:
• Disabled - No continuity check cell is generated or monitored
• Enabled for CC generation - continuity check cells for the defined connection are
generated at the rate of one cell per second
• Enabled for CC receipt - incoming continuity check cells and user cells for the
defined connection are monitored; LOC is reported when no end-user traffic cells
or continuity check cells have been received for 3.5 ± 0.5 seconds.
• Enabled for CC cell generation and receipt - continuity check cells for the defined
connection are generated at the rate of one cell per second; incoming continuity
check cells and user cells for the defined connection are monitored; LOC is
reported when no end-user traffic cells or continuity check cells have been received
for 3.5 ± 0.5 seconds.
Continuity checks can be enabled (or disabled) for the following types of VPs:
• Shelf VP
• Downstream VP
• Local VP.
Note that the following continuity checks are not applicable: F4 end-to-end CC for a
downstream VP or local VP.
Additionally, Continuity Checks can be enabled (or disabled) for the following types of
VCs:
• VCs within Shelf VPs
• The ATM operations channel.
Note that the following CCs are not applicable: F5 end-to-end CC for a VC within a
shelf VP, F5 end-to-end CC or F5 segment CC for a VC within a downstream VP, F5
end-to-end CC or F5 segment CC for a VC within a local VP)
The AnyMedia ® Access System supports up to 32 simultaneously active Continuity
Checks.

ATM security management

Access security
...................................................................................................................................................................................................................................

Overview
Security management is the system activity for authentication of a security identifier
(ID).
Security is provided for the ATM OAM&P interfaces as follows:
• Console port
• 10BaseT port
• BB ATM Operations Channel.

Access security
The system authenticates the security ID before establishing a connection. Once the
security ID is authenticated, the user has access to all SNMP commands and GSI
capabilities.
The same security ID is used for each of the ATM OAM&P interfaces. A default
security ID is installed as a result of AFM power-up. Any security ID mismatch over
these interfaces results in an autonomous message being returned to the message
source.
The security ID for an ATM OAM&P interface may be changed at any time following
AFM power-up.
The ATM xDSL security management functions are identical for all configurations of
the AnyMedia ® Access System, regardless of which shelf type is used.

Purpose
The chapter System Planning and Engineering for narrowband services provides the
information necessary to plan and engineer access networks for data and voice
frequency (VF) services including AnyMedia ® Access System applications.

Contents

System planning 5-3

System capacity of the AnyMedia ® LAG 1900 Shelf 5-5
System capacity of the AnyMedia ® LAG 4300 Shelf 5-8
System capacity of the AnyMedia ® ETSI V5 Shelf 5-11
Growth scenarios 5-16
Engineering POTS-only configurations 5-19
Configurations with V5.1 interfaces 5-23
Configurations with V5.2 interfaces 5-25
Engineering mixed POTS/ISDN configuration 5-26
Engineering configurations with PLLs 5-33
Engineering POTS + ADSL service with LPZ110 and LPA432 APs 5-36
Using the BB ATM Operations Channel to transport NB OAM&P 5-38
Traffic engineering 5-41
Reference loads 5-42
Call capacity evaluations 5-43
Configuration limits affecting the system traffic 5-45
Traffic engineering 5-46
Overload control 5-52
Interface configurations 5-53

Z interface for POTS or ALL services 5-55

Configuration data POTS services 5-56
Configuration data ALL services 5-57
Z interface subscriber loop dimensioning 5-58
U interface for ISDN BRA and DLL services 5-61
Configuration data ISDN BRA services 5-62
Configuration data DLL services 5-63
DLL services via managed NTU 5-64
HDSL interface for V5 ISDN PRA, V3 ISDN PRA, VLL, GLL, UVLL 5-66
or UGLL services
Configuration data V5 ISDN PRA services 5-79
Configuration data V3 ISDN PRA services 5-80
Configuration data n × 64 kbps GLL services 5-81
Configuration data n × 64 kbps VLL services 5-82
Configuration data UGLL services 5-83
Configuration data UVLL services 5-84
E1 (2-Mbps) interface 5-85
E1 interfaces on IO_E1 5-86
E1 interfaces on AP_E1 5-87
V5 parameters 5-89
Ringer configuration in AnyMedia ® LAG 4300 Shelf 5-90
Ringer configuration in AnyMedia ® ETSI V5 Shelf 5-91
Product reliability 5-92
Product reliability 5-93

System planning

Purpose
This section describes the planning and engineering of the AnyMedia ® Access System
for narrowband interfaces.

Application pack types

The following types of application packs (APs) are used:
• LPZ100 (32 Z ports)
• LPZ110 (32 Z ports); interworking with the LPA432 (ADSL over POTS without
external splitters)
• LPZ200 (32 Z ports); integrated test head
• LPZ64x (64 Z ports)
• LPA832 (32 Z ports for POTS and ADSL simultaneously, as well as POTS only or
ADSL only)
• LPA833 (32 Z ports for POTS and ADSL simultaneously, as well as POTS only or
ADSL only) same usage as LPA832, but hardware ready for supporting future
ADSL standards ADSL2 and ADSL2+
• LPP100 (24 Z ports)
• LPU112 (12 ISDN U ports)
• LPU132 (32 ISDN U ports) with 2B1Q line code
• LPU430 (16 ISDN U ports)
• LPU432 (32 ISDN U ports)
• LPU508 (8 ISDN U ports) with TCM line code
• LPS504 (2 × 2 HDSL ports)
• LPS510 (8 SHDSL ports)
• TAP10x (Test application pack).
For characteristics and details see the Data Sheet Book 363-211-251.

Contents

System capacity of the AnyMedia ® LAG 1900 Shelf 5-5

System capacity of the AnyMedia ® LAG 4300 Shelf 5-8
System capacity of the AnyMedia ® ETSI V5 Shelf 5-11
Growth scenarios 5-16
Engineering POTS-only configurations 5-19

Configurations with V5.1 interfaces 5-23

Configurations with V5.2 interfaces 5-25
Engineering mixed POTS/ISDN configuration 5-26
Engineering configurations with PLLs 5-33
Engineering POTS + ADSL service with LPZ110 and LPA432 APs 5-36
Using the BB ATM Operations Channel to transport NB OAM&P 5-38

System capacity of the AnyMedia ® LAG 1900 Shelf

Overview
The capacity of the AnyMedia ® LAG 1900 Shelf is impacted by the
• number of AP slots
• number of 2-Mbps links on network side
• range of AIDs
• processor performance (call capacity limitation).

Maximum capacity of the AnyMedia ® LAG 1900 Shelf

The following table shows the maximum number of possible subscriber lines for the
different services in one AnyMedia ® LAG 1900 Shelf and the limitation reasons.

Interfaces/services Maximum capacity Limitation reasons

V5.1: Max. number of V5 CCs 16 arbitrary limited by software

1
V5.1: Max. supported POTS subscriber lines 240 number of E1 timeslots
V5.1: Max. supported ISDN BRA subscriber lines 43 (LPU112) number of HDLC terminations on
COMDAC
240 (LPU132, LPU432)2 number of E1 timeslots
V5.2: Max. number of V5 CCs 16 arbitrary limited by software

V5.2: Max. number of V5 user ports in remote terminal 5000 arbitrary limited by call
applications concentration ratio
V5.2: Max. supported POTS subscriber lines 896 number of LAG Shelf slots

V5.2: Max. supported ISDN BRA subscriber lines 43 (LPU112) number of HDLC terminations on
COMDAC
448 (LPU132, LPU432) number of LAG Shelf slots
V5.2: Max. supported V5 ISDN PRA subscriber lines 43 number of HDLC terminations on
COMDAC

Max. supported V3 ISDN PRA subscriber lines 8 number of E1 links

Max. supported analog leased lines 248 number of E1 timeslots

Max. supported digital leased lines 248 number of E1 timeslots

Max. supported VLL subscriber lines 56 (HDSL AP)3 number of LAG Shelf slots
3
112 (SHDSL AP) number of LAG Shelf slots

Max. supported GLL subscriber lines 56 (HDSL AP)3 number of LAG Shelf slots
3
112 (SHDSL AP) number of LAG Shelf slots
Max. supported UVLL/UGLL subscriber lines via IO_E1 8 number of E1 links

Max. supported UVLL/UGLL subscriber lines via 56 number of LAG Shelf slots
AP_E1 (only for SHDSL APs)

Notes:
1. Because of the E1 links the maximum number of bearer channels is limited to 240. The following
applies: Max. subscriber = 248 - #(V5 CCs).
2. Because of the E1 links the maximum number of bearer channels is limited to 240. Therefore the
maximum number of V5.1 ISDN BRA subscribers using two B-channels is 120.
3. Max. of 248 timeslots.

Special rules for the capacity evaluation

If a test application pack (TAP10x) is used, only up to 13 application packs can be
configured in the LAG 1900 Shelf.
The POTS APs and the ISDN AP LPU112 use a fixed number of timeslots (24 or 32
timeslots). The number of timeslots for the ISDN APs LPU132 and LPU432 is
provisionable from 1 timeslot to up to 96 timeslots.
The number of timeslots for the [S]HDSL AP is provisionable from 1 timeslot to up to
64 timeslots (HDSL AP) and up to 128 timeslots (SHDSL AP).
For HDSL APs there are no restrictions/limitations due to the PCM highway and
HDSL APs can be plugged into each AP slot in the AnyMedia ® LAG 1900 Shelf
providing full service.

Maximum capacity in remote terminal application

The LAG 1900 Shelf in a remote terminal application supports
• up to 10 remote terminal interfaces to connect 10 remote terminals
• up to 2 host terminal interfaces to be connected as remote terminal to up to 2 host
terminals
• in host terminal: Up to 20 remote terminal links in any mix of IO_E1 or AP_E1
based E1 feeders to support one or more remote terminal interfaces
• in remote terminal: Up to 20 remote terminal links in any mix of IO_E1 or AP_E1
based E1 feeders (AP_E1 only with COM503/LAG1900) to support one or more
host terminal interfaces
• up to 5000 V5 user ports for local, hosted or remote subscribers in any mix
(arbitrary limited by call concentration ratio).

System management capacity for managed NTU

Mixed NB and ATM xDSL service configurations

For mixed service configurations the numbers of each service type are lower but a
simultaneous usage of ATM xDSL services in free slots does not reduce the
narrowband (NB) capabilities.

System capacity of the AnyMedia ® LAG 4300 Shelf

Overview
The capacity of the AnyMedia ® LAG 4300 Shelf is impacted by the
• number of AP slots
• number of 2-Mbps links on network side
• range of AIDs
• processor performance (call capacity limitation).

Maximum capacity of the AnyMedia ® LAG 4300 Shelf

The following table shows the maximum number of possible subscriber lines for the
different services in one AnyMedia ® LAG 4300 Shelf and the limitation reasons.

Interfaces/services Maximum capacity Limitation reasons

V5.1: Max. number of V5 CCs 16 arbitrary limited by software

1
V5.1: Max. supported POTS subscriber lines 480 number of E1 timeslots
V5.1: Max. supported ISDN BRA subscriber lines 43 (LPU112) number of HDLC terminations on
COMDAC
480 (LPU132, LPU432)2 number of E1 timeslots
V5.2: Max. number of V5 CCs 16 arbitrary limited by software

V5.2: Max. number of V5 user ports in remote terminal 5000 arbitrary limited by call
applications concentration ratio
V5.2: Max. supported POTS subscriber lines 2752 number of LAG Shelf slots

V5.2: Max. supported ISDN BRA subscriber lines 43 (LPU112) number of HDLC terminations on
COMDAC
1376 (LPU132, LPU432) number of LAG Shelf slots
V5.2: Max. supported V5 ISDN PRA subscriber lines 43 number of HDLC terminations on
COMDAC

Max. supported V3 ISDN PRA subscriber lines 16 number of E1 links

Max. supported analog leased lines 496 number of E1 timeslots

Max. supported digital leased lines 496 number of E1 timeslots

Max. supported VLL subscriber lines 172 (HDSL AP)3 number of LAG Shelf slots
3
344 (SHDSL AP) number of LAG Shelf slots

Max. supported GLL subscriber lines 172 (HDSL AP)3 number of LAG Shelf slots
3
344 (SHDSL AP) number of LAG Shelf slots
Max. supported UVLL/UGLL subscriber lines via IO_E1 16 number of E1 links

Max. supported UVLL/UGLL subscriber lines via 172 number of LAG Shelf slots
AP_E1 (only for SHDSL APs)

Notes:
1. Because of the E1 links the maximum number of bearer channels is limited to 480. The following
applies: Max. subscriber = 496 - #(V5 CCs).
2. Because of the E1 links the maximum number of bearer channels is limited to 480. Therefore the
maximum number of V5.1 ISDN BRA subscribers using two B-channels is 240.
3. Max. of 496 timeslots.

Special rules for the capacity evaluation

If a test application pack (TAP10x) is used, only up to 42 application packs can be
configured in the LAG 4300 Shelf. The use of up to two 2-slot internal ringer APs also
reduces the amount of application packs. In a LAG 4300 Shelf with TAP10x and with
two internal ringer APs up to 38 application packs can be configured.
The POTS APs and the ISDN AP LPU112 use a fixed number of timeslots (24 or 32
timeslots). The number of timeslots for the ISDN APs LPU132 and LPU432 is
provisionable from 1 timeslot to up to 96 timeslots.
The number of timeslots for the [S]HDSL AP is provisionable from 1 timeslot to up to
64 timeslots (HDSL AP) and up to 128 timeslots (SHDSL AP).
For HDSL APs there are no restrictions/limitations due to the PCM highway and
HDSL APs can be plugged into each AP slot in the AnyMedia ® LAG 4300 Shelf
providing full service.

Maximum capacity in remote terminal application

The LAG 4300 Shelf in a remote terminal application supports
• up to 10 remote terminal interfaces to connect 10 remote terminals
• up to 2 host terminal interfaces to be connected as remote terminal to up to 2 host
terminals
• in host terminal: Up to 20 remote terminal links in any mix of IO_E1 or AP_E1
based E1 feeders to support one or more remote terminal interfaces
• in remote terminal: Up to 16 IO_E1 based remote terminal links to support one or
more host terminal interfaces
• up to 5000 V5 user ports for local, hosted or remote subscribers in any mix
(arbitrary limited by call concentration ratio).

System management capacity for managed NTU

If the AnyMedia ® Access System is configured with ISDN APs (LPU112), the system
can support and manage up to 384 managed NTUs with the following restriction:
• The remote management of the NTUs is supported via the COMDAC and a
limitation occurs due to polling load on the COMDAC.
• In order to meet the fault reporting time (time-out is at most 10 seconds), up to 100
managed NTUs can be supported per COMDAC. If the reporting time is relaxed,
the full complement of 384 NTUs can be achieved.
....................................................................................................................................................................................................................................
363-211-586 5-9
Issue 6, July 2007
System planning and engineering for NB services System capacity of the AnyMedia ® LAG 4300 Shelf

Mixed NB and ATM xDSL service configurations

For mixed service configurations the numbers of each service type are lower but a
simultaneous usage of ATM xDSL services in free slots does not reduce the
narrowband (NB) capabilities.
The AnyMedia ® LAG 4300 Shelf supports two independent broadband subsystems, one
in the upper row and one in the lower row.

System capacity of the AnyMedia ® ETSI V5 Shelf

Overview
The capacity of the AnyMedia ® ETSI V5 Shelf is impacted by the
• number of AP slots
• number of 2-Mbps links on network side
• range of AIDs
• processor performance (call capacity limitation).

Maximum capacity of the AnyMedia ® ETSI V5 Shelf with COM501

The following table shows the maximum number of possible subscriber lines for the
different services in one AnyMedia ® ETSI V5 Shelf with COM501 and the limitation
reasons.

Interfaces/services Maximum capacity Limitation reasons

1
V5.1: Max. number of V5 CCs 16 / 48 COMDAC / IO_HDLC
V5.1: Max. supported POTS subscriber lines 480 2 number of E1 timeslots
V5.1: Max. supported ISDN BRA subscriber lines 192 (LPU112) number of shelf slots

256 (LPU430)3 number of shelf slots

3
480 (LPU132, LPU432) number of shelf slots
V5.2: Max. number of V5 CCs 16 / 481 COMDAC / IO_HDLC
V5.2: Max. number of V5 user ports in remote terminal 2000 COMDAC memory constraints
applications
V5.2: Max. supported POTS subscriber lines 768 4 number of shelf slots
V5.2: Max. supported ISDN BRA subscriber lines 192 (LPU112) number of shelf slots

256 (LPU430) number of shelf slots

512 (LPU132, LPU432) number of shelf slots

V5.2: Max. supported V5 ISDN PRA subscriber lines 32 (HDSL AP) number of shelf slots

128 (SHDSL AP)5 number of shelf slots

Max. supported V3 ISDN PRA subscriber lines 16 number of E1 links

Max. supported analog leased lines 496 number of E1 timeslots

6
Max. supported digital leased lines 192 (LPU112) number of shelf slots

256 (LPU430)6 number of shelf slots

6
496 (LPU132, LPU432) number of shelf slots
Max. supported VLL subscriber lines 64 (HDSL AP)6 number of shelf slots
6
128 (SHDSL AP) number of shelf slots

Max. supported GLL subscriber lines 64 (HDSL AP)6 number of shelf slots
6
128 (SHDSL AP) number of shelf slots

Max. supported UVLL/UGLL subscriber lines via IO_E1 16 number of E1 links

Interfaces/services Maximum capacity Limitation reasons

Max. supported UVLL/UGLL subscriber lines via 64 number of shelf slots

AP_E1

Notes:
1. 16 without IO_HDLC, 48 with IO_HDLC.
2. Because of the E1 links the maximum number of bearer channels is limited to 480. The following
applies: Max. subscriber = 496 - #(V5 CCs).
3. Because of the E1 links the maximum number of bearer channels is limited to 480. Therefore the
maximum number of V5.1 ISDN BRA subscribers using two B-channels is 240.
4. Due to power feeding limitations, a maximum of 8 APs with 64 subscriber lines and 8 APs with 32
subscriber lines can be used. So the maximum number of supported V5.2 POTS subscriber lines
calculates to 8 x 64 + 8 x 32 = 768. In addition, the APs with 64 subscriber lines must be equally
distributed on even and odd slots. It is recommended to install them in slots 1 to 8.
5. Max. of 1536 timeslots (PCM highway).
6. Max. of 496 timeslots (E1 timeslots).

Maximum capacity of the AnyMedia ® ETSI V5 Shelf with COM503

The following table shows the maximum number of possible subscriber lines for the
different services in one AnyMedia ® ETSI V5 Shelf with COM503 and the limitation
reasons.

Interfaces/services Maximum capacity Limitation reasons

V5.1: Max. number of V5 CCs 16 arbitrary limited by software

V5.1: Max. supported POTS subscriber lines 4801 number of E1 timeslots
2
V5.1: Max. supported ISDN BRA subscriber lines 43 (LPU112) number of HDLC terminations on
COMDAC
480 (LPU132, LPU432)3 number of E1 timeslots
V5.2: Max. number of V5 CCs 16 arbitrary limited by software

V5.2: Max. number of V5 user ports in remote terminal 5000 arbitrary limited by call
applications concentration ratio

V5.2: Max. supported POTS subscriber lines 7684 number of shelf slots
2
V5.2: Max. supported ISDN BRA subscriber lines 43 (LPU112) number of HDLC terminations on
COMDAC
512 (LPU132, LPU432) number of shelf slots

V5.2: Max. supported V5 ISDN PRA subscriber lines 32 (HDSL AP) number of shelf slots
43 (SHDSL AP) number of HDLC terminations on
COMDAC

Max. supported V3 ISDN PRA subscriber lines 16 number of E1 links

Max. supported analog leased lines 496 number of E1 timeslots

Max. supported digital leased lines 192 (LPU112)2 5
number of E1 timeslots
5
496 (LPU132, LPU432) number of E1 timeslots

Interfaces/services Maximum capacity Limitation reasons

5
Max. supported VLL subscriber lines 64 (HDSL AP) number of shelf slots

128 (SHDSL AP)5 number of shelf slots

5
Max. supported GLL subscriber lines 64 (HDSL AP) number of shelf slots

128 (SHDSL AP)5 number of shelf slots

Max. supported UVLL/UGLL subscriber lines via IO_E1 16 number of E1 links

Max. supported UVLL/UGLL subscriber lines via 64 number of shelf slots
AP_E1

Notes:
1. Because of the E1 links the maximum number of bearer channels is limited to 480. The following
applies: Max. subscriber = 496 - #(V5 CCs).
2. LPU430 is not supported in this configuration.
3. Because of the E1 links the maximum number of bearer channels is limited to 480. Therefore the
maximum number of V5.1 ISDN BRA subscribers using two B-channels is 240.
4. Due to power feeding limitations, a maximum of 8 APs with 64 subscriber lines and 8 APs with 32
subscriber lines can be used. So the maximum number of supported V5.2 POTS subscriber lines
calculates to 8 x 64 + 8 x 32 = 768. In addition, the APs with 64 subscriber lines must be equally
distributed on even and odd slots. It is recommended to install them in slots 1 to 8.
5. Max. of 496 timeslots.

Special rules for the capacity evaluation

If a test application pack TAP10x is used, only up to 15 application packs can be
configured in the AnyMedia ® ETSI V5 Shelf.
The POTS APs and the ISDN APs LPU112 and LPU430 use a fixed number of
timeslots (24 or 32 timeslots). The number of timeslots for the ISDN APs LPU132 and
LPU432 is provisionable from 1 timeslot to up to 96 timeslots.
The number of timeslots for the [S]HDSL AP is provisionable from 1 timeslot to up to
64 timeslots (HDSL AP) and up to 128 timeslots (SHDSL AP).
Up to release R1.4.1 two adjacent odd-even HDSL APs can allocate in total 96
timeslots. For release R1.6 or higher two adjacent odd-even HDSL APs can allocate in
total 128 timeslots and two adjacent odd-even SHDSL APs can allocate in total 192
timeslots.
In the AnyMedia ® ETSI V5 Shelf with COM503 each AP slot supports 128 timeslots.

Maximum capacity in remote terminal application

The AnyMedia ® ETSI V5 Shelf with COM501 in a remote terminal application
supports
• up to 4 remote terminal interfaces to connect 4 remote terminals
• up to 2 host terminal interfaces to be connected as remote terminal to up to 2 host
terminals
....................................................................................................................................................................................................................................
363-211-586 5-13
Issue 6, July 2007
System planning and engineering for NB services System capacity of the AnyMedia ® ETSI V5 Shelf

• in host terminal: Up to 2 IO_E1 based and up to 18 AP_E1 based remote terminal

links in any mix to support one ore more remote terminal interfaces
• in remote terminal: Up to 16 IO_E1 based remote terminal links to support one or
more host terminal interfaces
• up to 2000 V5 user ports for local, hosted or remote subscribers in any mix
(limited due to COMDAC memory constraints).
The AnyMedia ® ETSI V5 Shelf with COM503 in a remote terminal application
supports
• up to 10 remote terminal interfaces to connect 10 remote terminals
• up to 2 host terminal interfaces to be connected as remote terminal to up to 2 host
terminals
• in host terminal: Up to 20 remote terminal links in any mix of IO_E1 or AP_E1
based E1 feeders to support one or more remote terminal interfaces
• in remote terminal: Up to 20 remote terminal links in any mix of IO_E1 or AP_E1
based E1 feeders to support one or more host terminal interfaces
• up to 5000 V5 user ports for local, hosted or remote subscribers in any mix
(arbitrary limited by call concentration ratio).

System capacity AnyMedia ® 800 Shelf

The AnyMedia ® 800 Access System is designed for mounting on a wall. The
AnyMedia ® 800 Shelf can be equipped with the same type of application packs (APs)
as the AnyMedia ® ETSI V5 Shelf.
The AnyMedia ® 800 Access System supports up to eight application packs (AP)
therefore the maximum number of subscriber lines for narrowband subscribers (POTS,
ISDN) is 256.
Additional the AnyMedia ® 800 Access System supports a full ATM xDSL transport
capacity if an E1 (IMA), E3, or DS3 feeder is available in the system.
The AnyMedia ® 800 Access System complies with the following specifications:
• ETS 300 019 storage class 1.2, transportation class 2.3, operation class 3.2
(cold-start temperature - 5° C)
• IEC 60364
• IEC 60950
• IEC 60529.

System management capacity for managed NTU

If the AnyMedia ® Access System is configured with ISDN APs (LPU112), the system
can support and manage up to 384 managed NTUs with the following restriction:
• The remote management of the NTUs is supported via the COMDAC and a
limitation occurs due to polling load on the COMDAC.
• In order to meet the fault reporting time (time-out is at most 10 seconds), up to 100
managed NTUs can be supported per COMDAC. If the reporting time is relaxed,
the full complement of 384 NTUs can be achieved.
....................................................................................................................................................................................................................................
5-14 363-211-586
Issue 6, July 2007
System planning and engineering for NB services System capacity of the AnyMedia ® ETSI V5 Shelf

Mixed NB and ATM xDSL service configurations

For mixed service configurations the numbers of each service type are lower but a
simultaneous usage of ATM xDSL services in free slots does not reduce the
narrowband (NB) capabilities.

Growth scenarios
...................................................................................................................................................................................................................................

Overview
This section defines system and pack growth, and degrowth. Sample scenarios
demonstrate the methods for performing different growth and degrowth situations.
Important! The basic growth (and degrowth) operations may be performed by
different maintenance personnel at different times without the need to complete one
task before the other.

Application pack and subscriber port growth

To install and provide service to an additional AP requires the following steps:
• Provisioning of the AP type
• Provisioning of a logical subscriber line for each AP port to provide service
• Dispatch a technician to the site to insert the AP.

IO_E1 and feeder growth

To install and provide service to an additional IO_E1 requires the following steps:
• Provisioning of the IO_E1 pack
• Provisioning of a logical link for each feeder on the IO_E1, to add capacity to an
existing V5.x interface or to create a new V5.x or PLL interface
• Dispatch a maintenance person to the site to insert the IO_E1.

Growth from POTS-only mode to POTS and ISDN

Per default the AnyMedia ® Access System is provisioned for POTS-only operation
mode regardless of whether an IO_HDLC is inserted or not; within this mode no
switched ISDN services can be provisioned.
To reconfigure from POTS-only to mixed mode requires the following steps:
• Inserting IO_HDLC (slot HDLC -1 is recommended) in an AnyMedia ® ETSI V5
Shelf/800 Shelf configuration
• Provisioning of IO_HDLC in an AnyMedia ® ETSI V5 Shelf/800 Shelf
configuration
• Changing the ISDN mode configuration to mixed POTS/ISDN mode via TL1
command
• Switching the standby system configuration to active via TL1 command
The system performs a restart and recovers with POTS/ISDN operation mode.
• Provisioning of switched ISDN services.

System degrowth
System degrowth is the removal of feeder and/or distribution capacity from an existing
operational AnyMedia ® Access System shelf. System capacity can be rearranged for
load balancing or other needs by combining the growth and degrowth operations.
...................................................................................................................................................................................................................................
5-16 363-211-586
Issue 6, July 2007
System planning and engineering for NB services Growth scenarios

Degrowth from POTS and ISDN to POTS-only mode

To change the configuration from mixed mode to POTS-only mode requires the
following steps:
• Removing switched ISDN services and updating other provisioning data according
to POTS-only communication channel restrictions
• Changing the ISDN mode configuration to POTS-only mode via TL1 command
The system performs a restart and recovers with POTS-only operation mode.
• Deprovisioning of (both) IO_HDLC(s) in an AnyMedia ® ETSI V5 Shelf/800 Shelf
configuration
• Removing (both) IO_HDLC(s) in an AnyMedia ® ETSI V5 Shelf/800 Shelf
configuration.

Examples of growth scenarios

Three different growth scenarios are described in more detail:
• Adding line and feeder capacity
• Adding E1 link via capacity activation
• Load balancing.
These growth scenarios assume that any necessary provisioning at the terminating end
of the system (for example, a LE) has been performed or will be completed in time to
meet the planned service date. These examples illustrate the AnyMedia ® Access System
shelf capabilities.

Scenario 1: Adding line and feeder capacity

Assume that an AnyMedia ® Access System shelf is installed to service a low growth
rate area and that it is initially equipped with the minimum line and feeder capacity
required. A single V5.2 interface is used. When additional line capacity is required,
maintenance personal is dispatched to install the necessary APs. To keep the
concentration ratio the same, both line capacity and feeder capacity must be added. The
necessary provisioning can be performed remotely or locally by maintenance personnel
via the GSI/EMS.

Scenario 2: Adding E1 link via capacity activation

Assume a fully equipped AnyMedia ® Access System shelf is installed, but only part of
the line capacity is initially required to provide service. This approach may be useful in
a high growth rate area to reduce the number of maintenance personnel dispatches
necessary to install new packs. A V5.2 interface using 4 E1s exists on the system.
Not all of the line capacity or feeder capacity is used (see “System capacity of the
AnyMedia ® ETSI V5 Shelf” (p. 5-11)). A number of Z ports and E1 ports are left
without being cross-connected. Greater than expected traffic is experienced on the V5.2
interface and it is desirable to add feeder capacity to reduce the concentration ratio.
From a remote GSI/EMS, enough E1 link capacity is added to the V5.2 to reduce the

concentration ratio. This capacity activation is achieved without dispatching a

maintenance person to the remote site. Completion of capacity activation is achieved
by assigning the E1 to the existing interface.

Scenario 3: Load balancing

Assume an AnyMedia ® Access System is installed with three V5.2 interfaces. Each
V5.2 supports five E1 ports (2 Mbps). The three V5.2 interfaces terminate on a
different local exchange (LE) interface. Over time, the following is observed:
• One of the LE interfaces is loaded with more traffic than anticipated.
• One of the LE interfaces is loaded with the traffic anticipated.
• One LE interface has significantly less load than the traffic anticipated.
Load balancing can be achieved by moving a number of 2 Mbps feeders from the
lightly loaded interface to the heavily loaded interface. From a remote GSI/EMS, TL1
commands can be sent to the system to first delete the E1 logical cross-connect
associating a 2-Mbps line to be moved from one V5.2 interface and then to enter a
new E1 logical cross-connect associating the feeder with a different V5.2. This
capacity rearrangement is achieved without visiting the remote site. The capacity
rearrangement is completed by entering the corresponding changes in the switch
database.
This is a simple example and does not represent a detailed procedure for load
balancing. Other operations at the LE are required to verify the integrity of the
changes. This scenario illustrates the operational capability of the AnyMedia ® system
architecture.

Engineering POTS-only configurations

POTS-only engineering constraints

In a POTS-only configuration no IO_HDLC pack is necessary. Therefore the
communication channels are terminated on the COMDAC. The specifications for a
POTS-only configuration lead to the following conditions for the number of
communication channels (CCs) in an AnyMedia ® Access System:
• For one V5.1 interface at least one CC is needed. There can be up to 16 V5.1
interfaces. This leads to a requirement of at least 16 CCs for a fully equipped V5.1
terminal.
• Each V5.1 interface uses a maximum of two CCs.
• The V5.2 interface can have 1 to 16 2-Mbps links, so the system can have 1 to 16
interfaces. At least one CC per interface is needed. For interfaces with multiple
links at least two CCs are needed. If working with more interfaces more CCs are
needed.
• Each V5.2 interface can use up to two CCs per link.
• POTS-only mode supports up to 16 CCs in total.
• A remote operations channel (ROC) is supported additionally for TDM COMDAC.

Concentration in configurations with V5.2

The V5.2 interface allows concentration, so that the number of reserved bearer
channels can be less than the total number of all provisioned subscribers. The
subscribers share the available bandwidth.

Blocking probability
The blocking probability of the system can be calculated by the Erlang B formula,
where (A) is the total given traffic, (C) is the number of bearer channels and (B) is the
blocking probability:
C
A 1
B=

∑
C
C! k
A
k!
k=0

The total traffic A is the product of the traffic per subscriber and the number of
subscribers. This formula assumes an infinite population of subscribers. This formula is
a good approximation if the number of subscribers is several times the number of
bearer channels and if the traffic is low. As the number of subscribers approximates the
number of bearer channels, the Erlang B formula becomes conservative. In that case,
the Engset distribution provides an accurate value. The probability is given by the next
formula, where (a) represents the traffic per subscriber, (M) the total population of
subscribers and (C) the number of bearer channels acting as servers.

B=
( ) M
C
a
C

∑( )
C
M k
a
k
k=0

Concentration ratio
The V5.2 interface protocol allows any kind of concentration and does not impose any
kind of restriction on the number of subscribers. However, the maximum number of
POTS subscribers is limited due to the number of application packs (APs). It is the
responsibility of the network operator to ensure a certain grade of service by selecting
an appropriate concentration ratio. The concentration ratio is given by the equation:

Number_of_subscribers_in_V5.2_interface
Concentration ratio =
Number_of_reserved_bearer_channels_per_V5.2_interface

The quality of service of a given concentration ratio depends on the number of bearer
channels and the traffic. Larger concentration ratios for a given blocking probability
can be obtained with larger number of subscribers and bearer channels.

Examples of V5 POTS-only configuration

In a V5 POTS-only configuration a large range of subscriber lines from 1 to 512
subscribers is possible.
The table “Configuration examples” (p. 5-22) presents some configuration options. The
first three examples work with the V5.1 interface and therefore no concentration.
Configuration 4 is an example with a V5.2 interface (concentration ratio: 2.1:1).
For 24-channel POTS APs the maximum number of subscribers is limited to 384.
With a given number of subscribers and the concentration ratio, the number of required
bearer channels is calculated by:

#(bearer channels) = (#(POTS subscribers) + 2 × #(ISDN subscribers)) / C-ratio

With a given number of CCs the required number of E1 links for V5 interfaces is
calculated by:

#(E1 links) = (#(bearer channels) + #(CCs)) / 31

The following sections describe each configuration in more detail.

Configuration 1 small line size, V5.1

128 subscriber lines are supported without concentration (concentration ratio 1:1), so
128 bearer channels have to be supported.
According to the above formula and assuming one CC per E1 link the required number
of E1 links is calculated by:
• #(E1 links) = (128 bearer channels + #(E1 links)) / 31
• #(E1 links) = (128 bearer channels) / 30
• #(E1 links) = 5.
Four 32-line APs (or six 24-line APs) are needed at the subscriber side to connect the
128 subscribers.
Optionally, a TAP10x can be installed.
Five HDLC channels for V5 are used on the COMDAC.

Configuration 2 medium line size, V5.1

256 subscriber lines are supported without concentration (concentration ratio 1:1), so
256 bearer channels have to be supported.
The required number of E1 links is calculated by 256 / 30 = 9 E1 links, that is 3
IO_E1s are needed.
Eight 32-line APs (or eleven 24-line APs) are needed to connect the 256 subscribers.
Optionally, a TAP10x can be installed.
Nine HDLC channels for V5 are used on the COMDAC.

Configuration 3 largest line size, V5.1

480 subscriber lines are supported without concentration (concentration ratio 1:1), so
480 bearer channels have to be supported.
The required number of E1 links is calculated by 480 / 30 = 16 E1 links, that is 4
IO_E1s are needed.
Fifteen 32-line APs are needed to connect the 480 subscribers (sixteen 24-line APs
support 384 subscribers).
Optionally, a TAP10x can be installed.
Sixteen HDLC channels for V5 are used on the COMDAC.

Configuration 4 large line size, V5.2

This configuration supports a maximum number of subscriber lines. This is only
possible with a V5.2 interface with concentration. The 512 subscribers are supported
assuming a concentration ratio of 2.1:1, so 244 bearer channels have to be supported.
There shall be one V5.2 interface to the LE. Two V5 CCs shall be defined for the
whole V5.2 interface.

The required number of E1 links is calculated by (512 / 2.1 + 2) / 31 = 8 E1 links,

that is 2 IO_E1s are needed.
Sixteen 32-line APs are needed to connect the 512 subscribers, so there is no space left
for a TAP10x.
Two HDLC channels for V5 are used on the COMDAC.

Configuration examples
POTS-only configuration examples

Configuration 1 small Configuration 2 Configuration 3 Configuration 4 large

line size medium line size largest line size line size

V5.1 interface V5.1 interface V5.1 interface V5.2 interface

Subscriber lines supported: 128 256 480 512

32 channel APs 128 256 384 384
24 channel APs

Concentration ratio/interface 1:1 1:1 1:1 2.1:1

Required bearer channels 128 256 480 244

E1 links 5 9 16 8
IO_E1s 2 3 4 2
POTS APs (32-channel) 4 8 15 16

POTS APs (24-channel) 6 11 16 16

TAP10x (optional) 0 ... 1 0 ... 1 0 ... 1 01

V5 CCs 2 5 9 16 2
PLL ROC (optional)3 0 ... 1 0 ... 1 0 ... 1 0 ... 1
3
SPLL ROC (optional) . 0 ... 1 0 ... 1 0 ... 1 0 ... 1
HDLC channels provided by 5 ... 6 9 ... 10 16 ... 17 2 ... 3
the COMDAC4

Notes:
1. If 16 APs are installed, no more slot is available for the test application pack
2. Providing V5.1 interface(s): #(V5 CCs) = #(E1 links); Providing V5.2 interface(s): #(V5 CCs) = 2
3. PLL ROC and SPLL ROC are mutually excluded
4. #(HDLC channels provided by the COMDAC) = #(V5 CCs) + #(ROCs)

Configurations with V5.1 interfaces

Overview
The following two tables show configuration examples for the range of 1 to 15 POTS
32 channel APs.
Configuration examples in dependency of the number of POTS APs (1 to 8 APs)

Number of POTS APs

1 2 3 4 5 6 7 8
Subscriber lines 32 64 96 128 160 192 224 256
supported =
required bearer
channels
E1 links 2 3 4 5 6 7 8 9
IO_E1s 1 1 1 2 2 2 2 3
TAP10x 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1
(optional)
V5 CCs 1 2 3 4 5 6 7 8 9
PLL ROC 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1
(optional) 2
SPLL ROC 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1
(optional) 2
HDLC channels 2 ... 3 3 ... 4 4 ... 5 5 ... 6 6 ... 7 7 ... 8 8 ... 9 9 ... 10
provided by the
COMDAC 3

Notes:
1. #(V5 CCs) = #(E1 links)
2. PLL ROC and SPLL ROC are mutually excluded
3. #(HDLC channels provided by the COMDAC) = #(V5 CCs) + #(ROCs)

Configuration examples in dependency of the number of POTS APs (9 to 15 APs)

Number of POTS APs

9 10 11 12 13 14 15
Subscriber lines supported = 288 320 352 384 416 448 480
required bearer channels
E1 links 10 11 12 13 14 15 16
IO_E1s 3 3 3 4 4 4 4
TAP10x (optional) 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1

Number of POTS APs

9 10 11 12 13 14 15
1
V5 CCs 10 11 12 13 14 15 16
PLL ROC (optional) 2 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1
SPLL ROC (optional) 2 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1
HDLC channels provided by the 10 ... 11 ... 12 ... 13 ... 14 ... 15 ... 16 ...
COMDAC 3 11 12 13 14 15 16 17

Notes:
1. #(V5 CCs) = #(E1 links)
2. PLL ROC and SPLL ROC are mutually excluded
3. #(HDLC channels provided by the COMDAC) = #(V5 CCs) + #(ROCs)

Configurations with V5.2 interfaces

Introduction
The number of bearer channels and V5 feeders depends on the concentration ratio.
As an example, taking a system with 512 subscribers, a single V5.2 interface and a
traffic of 0.1 E per subscriber, three configurations are shown for call blocking
probabilities of 0.01%, 0.1% and 1%. Bearer channels and therefore concentration
ratios are calculated by the ErlangB formula.
POTS-only configuration with V5.2 interfaces

Blocking probability 1% 0.1% 0.01%

Subscriber lines supported 512 512 512
Required bearer channels 65 73 79
Concentration ratio 7.8 : 1 7.01 : 1 6.48 : 1
E1 links 3 3 3
IO_E1s 1 1 1
1
V5 CCs 2 ... 4 2 .... 4 2 ... 4
2
PLL ROC (optional) 0 ... 1 0 ... 1 0 ... 1
SPLL ROC (optional) 2 0 ... 1 0 ... 1 0 ... 1
HDLC channels provided by 2 ... 5 2 ... 5 2 ... 5
the COMDAC 3

Notes:
1. #(V5 CCs) = 1 common CC + 1 common CC protection + 1 PSTN CC + 1 PSTN
protection
2. PLL ROC and SPLL ROC are mutually excluded
3. #(HDLC channels provided by the COMDAC) = #(V5 CCs) + #(ROCs)

Engineering mixed POTS/ISDN configuration

Embedding IO_HDLC
An IO_HDLC is required if switched ISDN services have to be supported.
TheAnyMedia ® shelf allows equipage of up to two IO_HDLCs. If two packs are
equipped, one is the protection pack.
The main tasks of the IO_HDLC are to provide a frame relay mechanism between
ISDN D-channels and V5 communication channels and to route the V5 control and
PSTN information to the active COMDAC, where they are terminated.
In this configuration the V5 CCs contain also ISDN D-channel data. The separation of
the D-channel data from the V5 CCs data is done by the IO_HDLC.
The HDLC implementation supports up to 48 V5 CCs. This corresponds to the max.
requirements of the ETSI V5 standards.

Engineering rules for mixed configuration POTS/ISDN

Engineering rules for mixed ISDN/POTS configurations with V5.1 interfaces:
• There is one bearer channel (BC) reserved for every provisioned subscriber BC.
• Per ETSI standard a minimum of one and a maximum of three V5 CCs have to be
provisioned per V5.1 feeder depending on the traffic load.
• The number of bearer channels per V5.1 plus the number of V5 CCs at the
interface must be less than or equal to 31.

BC per V5.1 interface + CC per V5.1 interface ≤31

Up to 16 V5.1 interfaces can be supported. At maximum 480 bearer channels are

available (480 POTS or 240 ISDN subscribers).
Engineering rules for mixed ISDN/POTS configurations with V5.2 interfaces:
• As V5.2 supports concentration, the network planner can engineer the number of
feeder bearer channels according to the number of subscribers and their traffic
values (Erlang).
• The network planner can start with a blocking probability B to be met, the traffic
per POTS subscriber APi, the number of POTS subscribers SP, the traffic per ISDN
B-channel AIi and the number of ISDN subscribers SI.
• The number of bearer channels C must be calculated so that:

ErlangB [(APi × SP + AIi × 2 × SI),C] ≤ B

The number of communication channels is at minimum 1 and at maximum 48. But one
communication channel is used for protection in a multilink configuration and one is
always needed as a minimum for all communication paths. The maximum number of
bearer channels available is 494 [(16 packs × 31 channels) - 2 V5 CCs].
...................................................................................................................................................................................................................................
5-26 363-211-586
Issue 6, July 2007
System planning and engineering for NB services Engineering mixed POTS/ISDN configuration

Calculation of system capacity

The table below defines the variables:

Variable Description
x up to the next whole integer, for example if x is 1.01 it becomes 2
x truncated, for example if x is 1.99 it becomes 1
BC number of reserved bearer channels for subscribers
CC number of communication channels (CCs) per system
CR concentration ratio
IFR internal frame relay
IOP number of IO_E1 packs
NAP number of APs
NAP-I number of ISDN APs
NHDLC number of used HDLC channels in the HDLC pack
ROC number of ROCs
S total number of subscribers
SI total number of ISDN subscribers
SP total number of POTS subscribers
V5f number of V5 feeders
V5f_1CC number of V5 feeders with 1 CC
V5f_2CC number of V5 feeders with 2 CCs
V5f_3CC number of V5 feeders with 3 CCs

The following variables are taken into consideration:

Bearer channels BC = SP + (SI × 2)

 
V5 links BC + CC
V5f =
31

 30 
BC
V5f_1CC = if for each link 1 V5 CC is configured

 29 
BC
V5f_2CC = if for each link 2 V5 CC are configured

 28 
BC
V5f_3CC = if for each link 3 V5 CC are configured

V5f ≤ 16 - (# of ROCs)

4
IO_E1 packs V5f
IOP =

IOP ≤ 4
HDLC channels NHDLC = CC + SI + IFR + ROC-supp.ch. + test-ch =
supported by = CC + SI + 4 ≤ 244 (for LPU112)
the HDLC pack
= CC + SI + 4 ≤ 308 (for LPU430)
Application NAP ≤ 16
packs

 
SP - 32
NAP - 32 =
32

 
SP - 24
NAP - 24 =
24

 
SI - 12
NAP - 12 = (for LPU112)
12

 
SI - 16
NAP - 16 = (for LPU430)
16

Subscribers SP = S-32 + S-24 ≤ 768 (in V5.2)

≤ 480 (in V5.1)

SI ≤ 192 (for LPU112)

SI ≤ 256 (for LPU430)

S = SI + SP
Concentration SP + (SI 2)
ratio
CR =
BC

Examples of mixed POTS/ISDN configuration

The following tables present some examples of mixed POTS/ISDN configurations.
They are sorted according to the number of supported ISDN subscribers.
Configuration with 32-channel POTS APs and ISDN APs in a V5.1 interface
The table below shows the mixed POTS/ISDN configurations in a V5.1 interface. Each
V5.1 interface (link) is assumed to have 3 V5 CCs.

Config. 1a Config. 1b Config. 2a Config. 2b Config. 3a Config. 3b

Small ISDN Small ISDN Medium ISDN Medium ISDN Large ISDN Large ISDN
line size line size line size line size line size line size

12-Channel 16-Channel 12-Channel 16-Channel 12-Channel 16-Channel

ISDN AP ISDN AP ISDN AP ISDN AP ISDN AP ISDN AP

POTS subscriber 416 192 0

lines supported

ISDN subscriber 12 16 96 128 168 224

lines supported

Number of 13 6 0
POTS APs
(32-channel)
Number of ISDN 1 8 14
APs

Required bearer 440 448 384 448 336 448

channels
Number of E1 16 16 14 16 12 16
links

Number of 4 4 4 4 3 4
IO_E1s

TAP10x Optional No No

Number of V5 48 48 42 48 36 48
CCs

Config. 1a Config. 1b Config. 2a Config. 2b Config. 3a Config. 3b

Small ISDN Small ISDN Medium ISDN Medium ISDN Large ISDN Large ISDN
line size line size line size line size line size line size

12-Channel 16-Channel 12-Channel 16-Channel 12-Channel 16-Channel

ISDN AP ISDN AP ISDN AP ISDN AP ISDN AP ISDN AP

HDLC 48 48 42 48 36 48
terminations at
the network side

HDLC 12 16 96 128 168 224

terminations at
the subscriber
side

Configuration with 32-channel POTS APs and ISDN APs in a V5.2 interface
For the V5.2 interface, a traffic per POTS subscriber of 0.1 E is assumed and a traffic
of 0.2 E for ISDN B-channels. The blocking probability is assumed as 0.1%.
It is assumed that the following configuration of V5 CCs applies:
• one CC for all the controlling functionality (CRTL, LCTRL, BCC)
• one CC for PTSN signaling
• one standby CC for protection group 1
• 3 standby CCs for protection group 2
• one CC for ISDN Ds-type data per set of 128 ISDN subscribers
• one CC for Df-type and Dp-type data per set of 128 ISDN subscribers.
This leads to a number of 8 V5 CCs for a configuration lower or equal 128 ISDN
subscribers and a number of 10 V5 CCs for more than 128 ISDN subscribers.
The table below shows the mixed POTS/ISDN configurations - one V5.2 interface

Config. 1a Config. 1b Config. 2a Config. 2b Config. 3a Config. 3b

Small ISDN Small ISDN Medium ISDN Medium ISDN Large ISDN Large ISDN
line size line size line size line size line size line size

12-Channel 16-Channel 12-Channel 16-Channel 12-Channel 16-Channel

ISDN AP ISDN AP ISDN AP ISDN AP ISDN AP ISDN AP

POTS subscriber 480 256 0

lines supported

ISDN subscriber 12 16 96 128 192 256

lines supported

Number of 15 8 0
POTS APs
(32-channel)

Number of ISDN 1 8 16
APs

Required bearer 75 77 88 102 102 131

channels

Concentration 6.72:1 6.65:1 5.09:1 5.02:1 3.76:1 3.91:1

ratio

Config. 1a Config. 1b Config. 2a Config. 2b Config. 3a Config. 3b

Small ISDN Small ISDN Medium ISDN Medium ISDN Large ISDN Large ISDN
line size line size line size line size line size line size

12-Channel 16-Channel 12-Channel 16-Channel 12-Channel 16-Channel

ISDN AP ISDN AP ISDN AP ISDN AP ISDN AP ISDN AP

Number of E1 3 3 4 4 4 5
links
Number of 1 1 1 1 1 2
IO_E1s

Number of V5 8 8 8 8 10 10
CCs

HDLC 8 8 8 8 10 10
terminations at
the network side
HDLC 12 16 96 128 192 256
terminations at
the subscriber
side

The table below shows the mixed POTS/ISDN configurations - two V5.2 interfaces

Config. 4a Config. 4b Config. 4c

Small ISDN line size Medium ISDN line Large ISDN line size
size

16-Channel ISDN AP 16-Channel ISDN AP 16-Channel ISDN AP

POTS subscriber lines supported 480 128 0

ISDN subscriber lines supported 16 128 256

Number of POTS APs (32-channel) 15 8 0

Number of ISDN APs 1 8 16
Required bearer channels 2 × 44 = 88 2 × 50 = 100 2 × 73 = 146

Concentration ratio 5.82 : 1 3.84 : 1 3.51 : 1

Number of E1 links 2×2 = 4 2×2 = 4 2×3 = 6

Number of IO_E1s 1 1 2

Number of V5 CCs 2 × 8 = 16 2 × 8 = 16 2 × 10 = 20

HDLC terminations at the network side 16 16 20

HDLC terminations at the subscriber side 16 128 256

The table below shows the ISDN-only configurations - one V5.2 interface

Blocking probability 1% 0.1% 0.01%

Subscriber lines supported 16-channel 256 256 256
ISDN APs
Required bearer channels 120 131 139
Concentration ratio 4.27 : 1 3.91 : 1 3.68 : 1

Blocking probability 1% 0.1% 0.01%

Number of E1 links 5 5 5
Number of IO_E1s 2 2 2
Number of V5 CCs 1 4 ... 10 4 ... 10 4 ... 10
PLL ROC (optional) 2 0 ... 1 0 ... 1 0 ... 1
SPLL ROC (optional) 2 0 ... 1 0 ... 1 0 ... 1
HDLC terminations at the network 4 ... 10 4 ... 10 4 ... 10
side
HDLC terminations at the subscriber 256 256 256
side

Notes:
1. #(V5 CCs) = 1 common CC + 1 common CC protection + 1 ISDN CC + 1 ISDN CC
protection
2. PLL ROC and SPLL ROC are mutually excluded

Engineering configurations with PLLs

Overview
Permanent Leased Lines (PLLs) are not carried by V5.x interfaces to the LE but use
separate 2-Mbps interfaces. A POTS or an ISDN subscriber can be provisioned as a
PLL, analog or digital, respectively. An analog leased line (ALL) subscriber needs one
64-kbps timeslot and a digital leased line (DLL) subscriber needs up to three 64-kbps
timeslots, two for the B-channels and one for the D-channel.

Engineering rules for ALL and DLL subscriber

The 16-kbps D-channel is carried over a 64-kbps timeslot. The DLL subscriber can be
provisioned in B, 2B, D, B+D or 2B+D mode. Each 2-Mbps interface reduces the
number of E1 ports available for V5 interfaces. If the ROC is carried via leased line
link, it needs one bearer channel of a leased-line 2-Mbps link.
The table below defines the variables

x up to the next whole integer, for example if x is 1.01 it becomes 2

SDLL1 Total number of DLL subscribers provisioned in B or D mode
SDLL2 Total number of DLL subscribers provisioned in 2B or B+D mode
SDLL3 Total number of DLL subscribers provisioned in 2B+D mode
SALL Total number of ALL subscribers
N2M Total number of 2-Mbps interfaces used for PLLs
ROC Total number of remote operations channel subscribers provisioned
for PLLs

The 2-Mbps interfaces needed for PLLs:

 
SALL + SDLL1 + SDLL2 2 + SDLL3 3 + ROC
N2M =
31

The number of available V5 feeders: V5f ≤ 16 - N2M

If the system is configured with a large number of PLLs the limiting factor is the
number of available timeslots in the E1 ports (16 × 31 TS = 496 TS). Therefore:
SALL + SDLL1 + SDLL2 × 2 + SDLL3 × 3 + ROC ≤ 496

Engineering rules for n × 64 leased line subscriber

The AnyMedia ® Access System supports two kinds of N × 64 digital leased line
services (GLL and VLL). The number of GLLs and VLLs depends on the HDSL
application mode, see “Services via HDSL” (p. 5-73) and “ISDN PRA services via
SHDSL NTU” (p. 5-78).
• The maximum number of subscribers (8 subscribers = 4GLL + 4VLL) for one
HDSL AP can be reached by using the application mode ″point-to-multipoint″. This
means each HDSL AP provides two interfaces carrying two HDSL links, where
each HDSL link can carry one GLL and one VLL subscriber.
• The maximum number of subscribers (16 subscribers = 8 GLL+ 8 VLL) for one
SHDSL AP can be reached by using the application mode ″point-to-point single
pair″. This means each SHDSL AP provides eight interfaces carrying an SHDSL
link, where each SHDSL link can carry one GLL and one VLL subscriber.
Each GLL or VLL subscriber allocates a minimum of 1 up to a maximum of 31 bearer
channels for the service. Each bearer channel is related to one timeslot on an E1 link.
All the timeslots providing the service for a unique GLL or VLL subscriber are
allocated in the same E1 link.

Engineering rules for unstructured 2 Mbps leased lines

The AnyMedia ® Access System supports unstructured 2 Mbps leased lines via a G.703
interface (UGLL) and via V.35, V.36 or X.21 interface (UVLL). In both cases the
particular interface is provided by means of an NTU which is the far end of an HDSL
or SHDSL transmission system.
• An HDSL AP supports up to two unstructured 2 Mbps leased lines (UGLL,
UVLL). Each UGLL or UVLL subscriber allocates one E1 link (32 bearer
channels) for the service. An unstructured 2 Mbps leased line on top of an HDSL
AP uses one E1 link provided by an IO_E1 pack. Each link is related to one of the
16 E1 links provided by the IO_E1 pack. Therefore the total number of
unstructured 2 Mbps leased line subscribers on top of HDSL supported by the
AnyMedia ® Access System is 16 unstructured 2 Mbps leased line subscribers.
• An SHDSL AP supports up to eight unstructured 2 Mbps leased lines (UGLL,
UVLL). Each UGLL or UVLL subscriber allocates one E1 link (32 bearer
channels) for the service. An unstructured 2 Mbps leased line on top of an SHDSL
AP uses either an E1 link provided by the IO_E1 pack or an E1 link provided by
the SHDSL AP. The AnyMedia ® Access System supports 16 unstructured 2 Mbps
leased line subscribers via E1 links provided by IO_E1 pack. In addition it supports
up to 64 (60 in AFM simplex mode, 56 in AFM duplex mode) 2 Mbps leased line
subscribers via E1 links provided by SHDSL APs in ETSI V5 Shelf and up to 32
2 Mbps leased line subscribers via E1 links provided by SHDSL APs in one
subshelf. Maximum number of unstructured 2 Mbps leased line subscribers on top
of SHDSL supported by the AnyMedia ® Access System is 272 (256 for 8
subshelves and 16 via IO_E1 pack) unstructured 2 Mbps leased line subscribers.

Engineering rules for V3 ISDN PRA subscriber

The AnyMedia ® Access System supports V3 ISDN PRA on HDSL AP or SHDSL AP.
• An HDSL AP supports up to two V3 ISDN PRA subscribers. Within release R1.4.1
two adjacent HDSL APs (1&2, 3&4, ..) support up to three V3 ISDN PRA
subscribers. Within release R1.6 or higher two adjacent HDSL APs (1&2, 3&4, ..)
support up to four V3 ISDN PRA subscribers.
• An SHDSL AP supports up to four V3 ISDN PRA subscribers. Two adjacent
SHDSL APs (1&2, 3&4, ..) support up to six V3 ISDN PRA subscribers.
Each V3 ISDN PRA subscriber allocates one 2 Mbps link for the service. Each link is
related to one of the 16 E1 links. The total number of V3 ISDN PRA subscribers
supported by the AnyMedia ® Access System is 16 V3 ISDN PRA subscribers.

Engineering POTS + ADSL service with LPZ110 and LPA432

APs
...................................................................................................................................................................................................................................

Overview
The application packs LPZ110 and LPA432 are designed to work together to provide
32 lines of POTS + ADSL service.
Note that the LPA432 can interwork with any POTS AP if the installation is done via
the new installation concept (NIC) as described in Chapter “New installation concept”
(p. 6-42) and using a splitter module.

POTS + ADSL wiring methods

The figure below shows the wiring together of the a/b pairs of the LPZ110 and the
LPA432

If local practices permit, the a/b pairs from the application packs LPZ110 and LPA432
may be joined at the MDF or FDI, as show in the next figure.
The figure below shows ADSL + POTS with LPZ110 and LPA432 (Method #1)

The figure below shows ADSL + POTS with LPZ110 and LPA432 (Method #2)

Using the BB ATM Operations Channel to transport NB

OAM&P
...................................................................................................................................................................................................................................

Overview
Operations, administration, and maintenance messages may be sent to and from the
COMDAC on the AnyMedia ® Mainshelf via the BB ATM Operations Channel. The BB
ATM Operations Channel is part of a feeder connected to the AFM circuit pack on the
AnyMedia ® Mainshelf. Using the BB ATM Operations Channel as a communications
link provides an alternative to a LAN connection.
There are a number of requirements for the BB ATM Operations Channel:
• IP address assignment for the PC running the GSI
• IP assignment for the PC Gateway
• IP assignment for the BB ATM Operations Channel on the AFM circuit pack
• A LAN crossover cable or Ethernet hub to connect from the AFM circuit pack
10BaseT jack to the J2 LAN connection on the shelf connection panel of the
AnyMedia ® ETSI V5 Shelf/800 Shelf or accordingly to the J107 LAN connection
on the connector field of the AnyMedia ® LAG 4300 Shelf.
The figure below shows a physical connection for the BB ATM Operations Channel in
an AnyMedia ® ETSI V5 Shelf

LAN
OAM&P information for
narrowband passes
through backplane
COMDAC

10BaseT port

Rx and Tx port
for feeder cable

BB ATM Operations Chan-

nel carries OAM&P infor-
mation for narrowband
management and ATM
xDSL management

Special duplex cabling is required when two AFMs are installed. For details on this
cabling, see the AnyMedia ® Access System Commands and Procedures for ATM xDSL
services online documentation (363-211-133).

IP assignments
The IP assignments in the next figure are examples. The IPs that are used in each
network must be assigned to work with the local data network configuration. The IP
assignments are made using several different mechanisms. The PC’s IP and gateway
are assigned using the Windows (Windows is a registered trademark of Microsoft
Corporation) operating system Network input screens. Router IP addresses are entered
using the router’s operations interface. The AnyMedia ® Mainshelf IPs are entered using
the GSI. In the next figure , the IPs designated are as follows:
A is the IP of the PC on which the GSI is installed.
B is the IP of the BB ATM Operations Channel on the AFM circuit pack.
C is the Ethernet port on the AFM circuit pack.
D is the IP of the AnyMedia ® Mainshelf.
The figure below shows an IP assignments for network configuration including BB
ATM Operations Channel

Physical requirements
The BB ATM Operations Channel is part of the feeder to the AFM circuit pack. A
LAN crossover cable or Ethernet hub is used to connect the AFM 10BaseT jack to the
LAN jack on the shelf connection panel or the connector field of the AnyMedia ®
Mainshelf.

Provisioning
For the provisioning of the BB ATM Operations Channel see “Using the BB ATM
Operations Channel to transport NB OAM&P” (p. 5-38).

Traffic engineering

Purpose
The call capacity of the AnyMedia ® Access System is specified using ITU-T traffic
models and reference loads.
The AnyMedia ® Access System exceeds the corresponding traffic values.

Contents

Reference loads 5-42

Call capacity evaluations 5-43
Configuration limits affecting the system traffic 5-45
Traffic engineering 5-46
Overload control 5-52

Reference loads
...................................................................................................................................................................................................................................
Reference loads used in this document are load models on subscriber lines to
characterize the sets of traffic parameters and services that are considered to be typical
for the access network and includes the traffic mix (originating, terminating...), the mix
of service classes (residential, business, coin boxes...), the types of supplementary
services (call waiting, call forwarding), and other characteristics.

Reference load A
Reference load A represents the normal upper mean level of activity which the
administrations would wish to provide for on subscriber lines: typically the mean for
the 30 busiest hours of the year (excluding exceptional days)

Reference load B
Reference load B represents an increased level beyond normal planned activity levels
leading to an acceptable level of degraded performance. Reference load B is defined as
a traffic increase over reference load A for subscriber lines of: +25% in Erlangs, with
+35% in busy hour call attempts (BHCA).

Call capacity evaluations

Overview
Determining an average traffic behavior of a subscriber or subscriber group is not
possible. Therefore the calculations are done on the basis of special, relatively high,
traffic values on the subscriber line, resulting from the most unfavorable, but
practically possible application case.
Important! In the event of overload, originating call attempts are rejected. There is
no dial tone provided to the subscriber in this case.

V 5.1 call capacity data

For a high traffic PSTN subscriber of the AnyMedia ® Access System, ITU-T
Recommendation Q.543 suggests as an upper limit for Reference Load A and the
subscriber line type Z:
• Average traffic intensity per line = 0.17 E (Erlang)
• Busy hour call attempt = 6.8 BHCA
ETSI Recommendation ETS 300 795 recommends a value of 90 sec for the busy hour
call holding time.
• For a maximum of 480 subscribers in a non-concentrating V5.1 interface the busy
hour call attempt is 3264 BHCA
Finally for the AnyMedia ® Access System with 480 PSTN subscribers in a V5.1
environment, the number of calls per second referencing Reference Load A can be
evaluated to:
• Number of calls per second = 0.91 calls/sec, that is 3264 BHCA.
Referencing Reference Load B gives an increased number of:
• Number of calls per second = 1.22 calls/sec, that is 4406 BHCA.

V5.2 call capacity data

For the evaluation of V5.2 call capacity there are two different approaches, both
independent of the service applied. One is based on subscriber line occupancy which
was used for V5.1 in the last section, and the other is based on the activity on V5
bearer channels with a fixed occupancy of 0.7 E on all V5 bearer channels. In the
AnyMedia ® Access System the subscriber line occupancy is used for the evaluation
base because the subscriber traffic intensity determines the concentration ratio of the
system (that is the number of subscribers in relation to the number of bearer channels
and consequently the number of E1 links)
For V5.2 the same subscriber type as for V5.1 will be taken for the capacity
evaluation.

The upper limit for Reference Load A and subscriber line type Z is:
• Average traffic intensity per line = 0.17 E (Erlang)
• Busy hour call attempt = 6.8 BHCA
• Busy hour call hold time = 90 sec.

BHCA for AnyMedia ® ETSI V5 Shelf

Due to concentration up to 512 subscribers can be connected to the AnyMedia ® Access
System (ETSI V5 Shelf). This leads to the busy hour call attempt for the system of:
• Busy hour call attempt (512 subscribers) = 3482 BHCA
Finally for the AnyMedia ® Access System with 512 PSTN subscribers in a V5.2
environment, the number of calls per second referencing Reference Load A can be
evaluated to:
• Number of calls per second = 0.97 calls/sec, that is 3482 BHCA.
Referencing Reference Load B will give an increased number of:
• Number of calls per second = 1.31 calls/sec, that is 4700 BHCA.

POTS/ISDN total traffic calculation in config. with V5.2

In the dealing with concentration in configurations with V5.2 one difference between
an ISDN subscriber and a POTS subscriber is the traffic value.
The ISDN subscriber can also use one or two bearer channels for the B-channel.
A simplification for calculating the total traffic of the AnyMedia ® Access Systems is to
use the traffic of the ISDN B-channel, multiply it by two and add the result to the total
POTS traffic.
The total traffic of the AnyMedia ® Access System for POTS/ISDN mixed mode is
calculated as follows:
Atotal = APOTSsubscriber × POTSsubscribers + AISDNB-channel × 2 × ISDNsubscribers

Configuration limits affecting the system traffic

Limits
The limits that apply to the AnyMedia ® Access System traffic model include the
following:
• A total of 16 E1 links may be engineered per system.
• Up to 16 V5.1 may be engineered per system.
• Up to 16 V5.2 may be engineered per system.
• Up to 31 permanent leased lines (PLL) may be engineered per E1 link.

Traffic engineering
...................................................................................................................................................................................................................................

General
The traffic engineering of the AnyMedia ® Access System determines the correct
number of E1 links to be allocated for the desired level of service, types of service to
be engineered (POTS, ISDN, PLL), and selected interfaces (V5.1, V5.2).

V5.1 traffic engineering

V5.1 traffic engineering principles include the following:
• The AnyMedia ® Access System supports up to 16 V5.1.
• Each V5.1 is assigned one E1 link for each 30 lines.
• Each V5.1 may terminate at a different point in the network.
• All subscriber lines terminating at a given point in the network are treated as one
group in determining the number of E1 links required for the V5.1(s) terminating at
the given point. An example follows: If there are 75 subscriber lines terminating on
switch A and 116 subscriber lines terminating on switch B, three V5.1 with three
E1 links are needed for switch A, and four V5.1 with four E1 links are needed for
switch B.

V5.2 traffic engineering

V5.2 traffic engineering principles include the following:
• The AnyMedia ® Access System supports up to 16 V5.2.
• Each V5.2 may terminate at a different point in the network.
• All subscriber lines terminating at a given point in the network are treated as one
group in determining the number of E1 links required for the V5.2(s) terminating at
the given point.
An example follows: If there are 75 subscriber lines terminating on switch A and
116 subscriber lines terminating on switch B, three V5.2 with three E1 links are
needed for switch A, and four V5.2 with four E1 links are needed for switch B.
• The grade-of-service to be provided to the subscribers on the V5.2 (in other words,
the loss probability for engineering this interface, see the following diagrams).

Traffic values
The AnyMedia ® Access System provides the capability to concentrate traffic on the
V5.2 (that is, more lines may be assigned to the V5.2 than there is bandwidth available
to carry calls on them if calls were attempted on all lines at the same time).
For an AnyMedia ® Access System with 512 subscribers and a concentration ratio of
approximately 1:4 four E1 links and 120 bearer channels would be sufficient. With that
assumption the following traffic values apply:
• 0.97 calls/sec for Reference Load A
• 1.31 calls/sec for Reference Load B.
The diagram below shows a call capacity (example of loss probability 0.1).
...................................................................................................................................................................................................................................
5-46 363-211-586
Issue 6, July 2007
System planning and engineering for NB services Traffic engineering

Bearer channels
per V5.2 interface

1200
⑤

1000 ➃

800 ➂

600
➁
400

200 ➀

0
1 501 1001 1501 2001 2501 3001 3501 4001 4501

Subscriber lines

➀ Loss probability 0.10000 for 0.05 Erl. per subscriber bearer channel
➁ Loss probability 0.10000 for 0.10 Erl. per subscriber bearer channel
➂ Loss probability 0.10000 for 0.17 Erl. per subscriber bearer channel
➃ Loss probability 0.10000 for 0.21 Erl. per subscriber bearer channel
⑤ Loss probability 0.10000 for 0.25 Erl. per subscriber bearer channel

The diagram below shows a call capacity (example of loss probability 0.01).

Bearer channels
per V5.2 interface

1400
⑤
1200
➃
1000
➂
800

600
➁
400
➀
200

0
1 501 1001 1501 2001 2501 3001 3501 4001 4501
Subscriber lines

➀ Loss probability 0.01000 for 0.05 Erl. per subscriber bearer channel
➁ Loss probability 0.01000 for 0.10 Erl. per subscriber bearer channel
➂ Loss probability 0.01000 for 0.17 Erl. per subscriber bearer channel
➃ Loss probability 0.01000 for 0.21 Erl. per subscriber bearer channel
⑤ Loss probability 0.01000 for 0.25 Erl. per subscriber bearer channel

The diagram below shows a call capacity (example of loss probability 0.001).

Bearer channels
per V5.2 interface

1400
⑤
1200
➃
1000
➂
800

600 ➁

400
➀
200

0
1 501 1001 1501 2001 2501 3001 3501 4001 4501

Subscriber lines

➀ Loss probability 0.00100 for 0.05 Erl. per subscriber bearer channel
➁ Loss probability 0.00100 for 0.10 Erl. per subscriber bearer channel
➂ Loss probability 0.00100 for 0.17 Erl. per subscriber bearer channel
➃ Loss probability 0.00100 for 0.21 Erl. per subscriber bearer channel
⑤ Loss probability 0.00100 for 0.25 Erl. per subscriber bearer channel

The diagram below shows a call capacity (example of loss probability 0.0001).

Bearer channels
per V5.2 interface

1600

1400 ⑤
1200 ➃
1000 ➂
800

600 ➁

400
➀
200

0
1 501 1001 1501 2001 2501 3001 3501 4001 4501

Subscriber lines

➀ Loss probability 0.00010 for 0.05 Erl. per subscriber bearer channel
➁ Loss probability 0.00010 for 0.10 Erl. per subscriber bearer channel
➂ Loss probability 0.00010 for 0.17 Erl. per subscriber bearer channel
➃ Loss probability 0.00010 for 0.21 Erl. per subscriber bearer channel
⑤ Loss probability 0.00010 for 0.25 Erl. per subscriber bearer channel

The diagram below shows a call capacity (example of loss probability 0.00001)

Bearer channels
per V5.2 interface

1600

1400 ⑤

1200 ➃

1000 ➂

800

600 ➁

400
➀
200

0
1 501 1001 1501 2001 2501 3001 3501 4001 4501

Subscriber lines

➀ Loss probability 0.00001 for 0.05 Erl. per subscriber bearer channel
➁ Loss probability 0.00001 for 0.10 Erl. per subscriber bearer channel
➂ Loss probability 0.00001 for 0.17 Erl. per subscriber bearer channel
➃ Loss probability 0.00001 for 0.21 Erl. per subscriber bearer channel
⑤ Loss probability 0.00001 for 0.25 Erl. per subscriber bearer channel

PLL traffic engineering

Permanent leased line (ALL, DLL, VLL or GLL) traffic engineering principles include
the following:
• Up to 31 lines can be assigned to an E1 link.
An E1 link with assigned permanent leased lines cannot be used for other purposes
(for example V5.x).

Overload control
...................................................................................................................................................................................................................................
Overload is a transient condition where the utilization of monitored resources exceeds
an implementation-dependent threshold. However, an overload condition is last from a
few seconds up to several days, depending on the root cause. Overload control includes
the monitoring of those resources and the responses that the AnyMedia ® Access
System makes to maintain system sanity. The objectives of overload control are to:
• prevent reset of the system controller or APs caused by the overload condition,
• maintain a high call processing throughput during the overload condition,
• limit the increase in the system’s mean response time to external message traffic, to
minimize retransmissions and subsequent queue buildup,
• maintain the quality of service for accepted calls.

Overload scenario AnyMedia ® Access System

Overload may be due to very high call volumes and/or maintenance actions.
1. The AnyMedia ® Access System detects that a monitored resource is nearing
exhaustion by comparing its utilization to a fixed threshold value.
2. The AnyMedia ® Access System transitions to the overload state. Appropriate
internal controls are applied, for example originating traffic throttling.
The system provides notification of overload onset to the management system and
to the craft interface, if present.
3. As the overload condition recovers, throttling will be disabled.
4. The AnyMedia ® Access System clears the overload condition and releases traffic
controls.
5. The AnyMedia ® Access System reports the clearance of overload to the
management system and to the craft interface, if present when the system has
remained below threshold for 10 minutes.
Upon completion of this scenario the AnyMedia ® Access System has recovered from a
traffic overload. The management system is informed of the onset and the clearing of
overload, and normal call processing and OAM&P are active on the system.

Overload scenario AnyMedia ® LAG 4300 Shelf

If internal ringing is used, the RGP100 indicates an overload condition if the ringing
load is too high on the RGP100. If an overload condition exists, additional terminating
POTS calls destined to the POTS AP concerned are rejected. When the overload
condition is resolved, the system resumes normal operation and accepts terminating
calls destined to the POTS AP concerned again. To avoid oscillation, a hysteresis is
used.

Interface configurations

Purpose

Overview
The AnyMedia ® Access System provides different external transmission interfaces.
Following external transmission interfaces are supported on:
• Subscriber side
– Z interface for POTS or ALL services
– U interface for ISDN BRA or DLL services
– HDSL interface for V5 ISDN PRA, V3 ISDN PRA, VLL, GLL, UVLL, or
UGLL services
• Network side
– E1 (2-Mbps) interface for V5.x, V3, leased line, or unstructured leased line
services

Parameter settings
Customer-specific system configurations (parameter settings) are possible for subscriber
interfaces and network interfaces to adapt the system for customer-specific transmission
and signaling requirements. This will be done via customer-specific configuration data
(Reflects the particular configuration needs of a customer. Customer-specific
configuration of the system is achieved by constant data which is part of the code. For
example customer-specific application pack data or PSTN protocol data belong to this
kind of configuration data. Colloquially customer-specific is sometimes called
country-specific) and provisionable settings.
For hardware configuration, jumpers on IO_E1(P) and CIU for termination impedance
have to be set.

Primary protection
The AnyMedia ® Access System installations require a protected wire system, which
consists of gastube arrestors on all outside plant telecommunication circuits (primary
protection).
All a/b, E1, E3/DS3, xDSL cables and the alarm cabling should not leave the building
premises unless connected to telecommunication devices providing primary protection
(for example protector blocks) as applicable.

Contents

Z interface for POTS or ALL services 5-55

Configuration data POTS services

Customer-specific configuration data

The following customer-specific configuration data are needed:
• Definition of normal polarity (NP) for subscriber line feeding
• Pulse dialing parameters
• Hook-flash timing parameter
• Loop supervision timing parameter
• Parameter for periodic pulse metering (PPM): tone pulses (12/16 kHz) or polarity
reversal pulses
• Parameter for calling line identification presentation (CLIP)
• Pulse code modulation (PCM) code law
• Line termination impedance.

Provisionable parameters
Provisionable parameters are:
• Select feeding current (low and high current)
• PPM supports 12/16 kHz on/off
• Input relative level
• Output relative level
• Select one of up to five balance networks.

Configuration data ALL services

Customer-specific configuration data

The following customer-specific configuration data are needed:
• PCM code law
• Line termination impedance

Provisionable parameters
Provisionable parameters are:
• Input relative level
• Output relative level.

Z...................................................................................................................................................................................................................................
interface subscriber loop dimensioning
POTS feeding range
For dimensioning Z interface subscriber loops the following feeding ranges have to be
taken into account:
• RLoop = 2200 Ω (includes subscriber terminal, DC resistance typically between
280 Ω and 540 Ω), ILoop ≥ 16 mA at V = - 48 V
• RLoop = 1800 Ω (includes subscriber terminal, DC resistance typically between
280 Ω and 540 Ω), ILoop ≥ 18 mA at V = - 48 V
• RLoop = 1500 Ω (includes subscriber terminal, DC resistance typically between
280 Ω and 540 Ω), ILoop ≥ 22 mA at V = - 48 V
The diagram below shows the feeding range and the feeding current limits for the
application pack LPZ100.
I/mA

40
Feeding current limits for example LPZ100:
Feeding current limit high = 42mA
Feeding current limit low = 27mA

0 R/Ohms
0 800 1000 1200 1400 1600 1800 2000 2200

Loop population for CO applications

The loop population for CO applications is characterized through a wide variety of
loop lengths and many different kinds of cables. Also it is possible that a subscriber
line is fed through different cable types which are connected (including cables with
different diameters of wires). Furthermore a subscriber loop can be loaded or
non-loaded. Loaded subscriber loop means there is a coil (pupin coil) inserted in a
subscriber line. Loaded subscriber loop will not be supported by the system.

The following parameters are valid for subscriber lines fed through cables:
• Typical loop length: 0 to 14 km
• Max. DC loop resistance (The values include the terminal DC resistance, typically
between 280 and 540 Ω): 1800 Ω to 2250 Ω.
A further possibility for subscriber connection are overhead lines which allow longer
loop lengths.

Loop population for remote access application

Usually access applications have shorter loops than CO applications, have a smaller
range of loop length distribution and an a/b pair is not fed through so many different
cables. Normally cables with smaller diameters (of wires) are used.

Physical characteristics for cables

The following table lists the parameters for three typical cables.
The table below shows the parameters of cables for subscriber loops

Parameter cable 1 cable 2 cable 3

Diameter of wire in mm 0.4 0.6 0.8
DC resistance R0’ in Ω/km 290 119 71
Capacitance C’ in nF/km 44 36 40
Inductance L’ in mH/km 0.68 0.64 0.62
Attenuation loss at 1 kHz a’ in 1.73 0.99 0.80
dB/km

Physical characteristics for overhead lines

Overhead lines have different physical characteristics in comparison with cables:
• Attenuation loss is lower (caused by larger diameters of wires)
• Attenuation loss, group delay time and line impedance nearly independent of
frequency
• Variation of line parameters due to influences of the weather
• High space consumption for the line tracks
• Overhead lines are very susceptible to lightning strikes.
The table below lists the parameters for overhead lines.

Parameter Overhead line Overhead line Overhead line

1 2 3
Diameter of wire in mm 2.5 3.0 4.0
DC resistance R0’ in Ω/km 7.4 5.5 2.8

Parameter Overhead line Overhead line Overhead line

1 2 3
Capacitance C’ in nF/km 5.5 6.0 6.4
Inductance L’ in mH/km 2.13 2.0 1.9
Attenuation loss at 1 kHz a’ in 0.06 0.05 0.03
dB/km

U interface for ISDN BRA and DLL services

Physical termination
The physical termination at the network end is the line termination (LT); the physical
termination at the user end is the network termination (NT1). Normally the digital
subscriber line (DSL) connects the LT with the NT1. In the worst case the DSL
connects the LT/NT1 to an optional regenerator or intermediate transmission elements
instead of directly connecting to the NT1/LT (see the Applications and Planning Guide
Overview (363-211-585).
The LT can provide power feeding for the NT1 and a dedicated subscriber terminal.
Optionally the power for an additional regenerator can be supplied.

Physical characteristics for cables

The two tables above list the parameters for typical cables. For ISDN transfer,
however, the cables have to fulfill additional requirements.
The table below shows the additional parameters for ISDN cables

Parameter Line code 2B1Q Line code 4B3T

Insertion loss (40 kHz) 36 dB 32 dB
Near-end crosstalk (40 kHz) 50 dB 50 dB
Typical loop length for 0.4 mm ∅ 4.2 km 4.2 km
Typical loop length for 0.6 mm ∅ 8 km 8 km
Cable diameters 0.3 mm up to 1.4 mm 0.3 mm up to 1.4 mm
Remote feeding voltage range 91 V to 99 V 91 V to 99 V
Minimum voltage at NT 28 V 28 V

Configuration data ISDN BRA services

Customer-specific configuration data

The following is customer-specific configuration data:
• Definition of feeding voltage (on/off)
• Remote power feeding default (on/off) per subscriber line. Remote power feeding is
needed, if the remote NTU is not locally powered.

Provisionable parameters
The following parameters are provisionable:
• Grading information to LE (enable/disable)
• Number of used B-channels (default 2)
• Used B-channel; only relevant, if number of used B-channels is 1
• Remote power feeding (on/off) per subscriber line. Remote power feeding is
needed, if the remote NTU is not locally powered.

Configuration data DLL services

Customer-specific configuration data

Provisionable parameters
The following parameter is provisionable:
• Automatic line activation (enable/disable)
• Transmission capability:
– One B-channel
– One B-channel and one D-channel
– Two B-channels
– Two B-channels and one D-channel
– One D-channel
• Remote power feeding (on/off) per subscriber line. Remote power feeding is
needed, if the remote NTU is not locally powered.

DLL services via managed NTU

Managed NTUs
Another possibility to realize digital leased line (DLL) services for ISDN applications
is to use following network termination units (NTU):
• Managed NTU V.24 (model AS2064-M11): This NTU supports speeds 1.2 kbps,
2.4 kbps, 4.8 kbps, 9.6 kbps, 14.4 kbps, 19.2 kbps and provides a V.24 interface to
the subscriber.
• Managed NTU V.35 (AS2063-M14): This NTU supports speeds of 48 kbps, 56
kbps, 64 kbps, 128 Kbps and provides a V.35 interface to the subscriber.
• Managed NTU X.21(AS2062-M9): This NTU can operate in low speed mode and
high speed mode and thus supports all speeds from 1.2 kbps up to 128 kbps. The
NTU provides a X.21 interface to the subscriber.
Important! Some NTU types can be incompatible with an applied remote power
feeding of the U-interface. In this case the remote power feeding must be turned
off at the provisioning of the related DLL. NTUs incompatible to remote power
feeding are for example NTUs which have a small DC current resistance between
a- and b-wire. A too small resistance leads to a power overload condition on the
subscriber line.

Managed NTU provisioning data

The managed NTU needs certain provisioning data to support the services. This
provisioning data are introduced directly to the managed NTU by TL1 command via
GSI/EMS. Local provisioning of the NTUs is not necessary.
Each time if the managed NTU hardware is reset or power-cycled it will reset all of
these provisioning data to values read from DIP switches internal to the NTU. In such
a situation the AnyMedia ® Access System downloads the NTU configurations again.
The table below lists the provisioning data of the managed NTUs.

Provisioning data NTU Provisionable via TL1 Default configuration value

command ENT-NTU
NTU type FR_V24, FR_V35, FR_X21 N/A
NTU interface speed 1.2 kbps up to 128 kbps N/A
dependent on NTU type
Data clocking mode CLKMODE Synchronous mode
Character length DATABITS 8
V.14 mode V14MODE Basic
RTS to CTS delay RTS2CTS 11 +/- 1 ms delay from RTS to
CTS
Control/RTS mode RTS C/RTS line controlled from DTE
(STD)

Provisioning data NTU Provisionable via TL1 Default configuration value

command ENT-NTU
Indication/RLSD mode RLSD I/RLSD line controlled from the
network (STD)
DSR/DTR mode DSRDTR DSR/DTR line controlled by
NTU/DTE (STD)
Remote loopback inhibit mode REMLP This NTU is able to place a
remote loopback (ENABLED)
X.21 byte timing BYTETIMING Byte timing disabled
(DISABLED)
External clock mode EXTCLK External Clock enabled
(ENABLED)
Anti-streaming timer ASTIMER 0
Anti-streaming retry timer ASRETRYTIMER 0

The following table shows the technical specifications for managed NTUs

Specifications for Managed NTU V.24 Managed NTU V.35 Managed NTU X.21
Electrical conform to ITU-T 103, 104, 114 and 115 comply with ITU-T
characteristics of (CCITT) should be described in (CCITT)
interchange circuits Recommendation V.28 Appendix II, of ITU-T Recommendations X.27
(CCITT) but with a load
Recommendations termination resistance of
X.21bis. The rest of the 3.9 kΩ. The electrical
circuits conform to characteristics at the
Recommendation V.28. DTE side of the
interface comply with
ITU-T Recommendation
X.27 (with or without
cable termination in the
load)
Line length The typical minimum range over 0.4 mm twisted pair telephone lines is 5.5 km
Power supply 100 to 264 V AC, 50 to 60 Hz, 100 mA or 40 to 75 V DC, 200 mA. The
connection is via an IEC 320 power inlet 1 at the rear of the NTU.
Operating Temperature 0 - 40° C. Humidity maximum 95% non-condensing
environment

Notes:
1. The NTU V.24 with a two pin IEC 320 power inlet does not require a protective earth.

HDSL interface for V5 ISDN PRA, V3 ISDN PRA, VLL, GLL,

UVLL or UGLL services
...................................................................................................................................................................................................................................

Physical termination
The AnyMedia ® Access System supports
• HDSL interfaces on two metallic pairs with 2B1Q line coding (ETSI TS 101 135)
via HDSL APs. The transmission rate is 1168 kbps on each metallic pair.
• HDSL interfaces on a single metallic pair with TC-PAM line coding via SHDSL
APs. The transmission rate is 200 kbps up to 2056 kbps per SHDSL port.
The physical termination at the network end is the line termination unit (LTU). The
physical termination at the user end is the network termination unit (NTU). The LTU
can provide sealing current to the HDSL interface (provisionable). The HDSL
interfaces support V5 ISDN PRA, V3 ISDN PRA, n × 64 kbps digital leased line
services and unstructured leased line services.

Transmission range for HDSL

The next table shows the transmission range for various cable sizes over
unconditioned, non loaded copper pairs. Transmission ranges are limited by cross talk
noise and BER rate performance. The second column in the table indicates
transmission range in low or no noise environments, while the third column in the
table indicates transmission range in a typical environment. A typical environment
consists of a cable group with 3 or 4 other HDSL services. The last column in the
table indicates transmission range in cable group with all other pairs carrying HDSL
service. In each column each transmission range is determined by a BER performance
of 10-8.
The table below shows the transmission range for HDSL.

Cable diameter in Maximum range line Typical range line Minimum range line
mm specification at 10-8 specification at 10-8 specification at 10-8
BER in km BER in km BER in km
AWG 26 (0.4) 3.4 3.2 2.4
AWG 24 (0.51) 4.4 4.1 3.2
AWG 22 (0.64) 5.7 5.3 4.1
AWG 19 (0.91) 8.1 7.6 5.8

Payload bit rate range for SHDSL

The AnyMedia ® Access System and the supported SHDSL NTUs are compliant to
ITU-T G.991.2/Annex B for payload bit rate ranges 192 kbps up to 2048 kbps. A
bi-directional data transmission using the echo cancellation technology. The max. reach
at 2048 kbps SHDSL link rates without noise at 0.4 mm is approximately 3.5 km.

NTU - universal transmission unit types for HDSL

To realize V5 ISDN PRA, V3 ISDN PRA or n × 64 kbps digital leased line services
for different HDSL applications following universal transmission units (UTU) can be
used:
• UTU-801: Two pair line UTU with G.703 interface (firmware version 4.61 or
higher for V3 service)
• UTU-802: Two pair line UTU with n × 64 kbps V.35 or V.36 or X.21 interface
• UTU-804: Two pair line UTU with G.703 and n × 64 kbps V.35 or V.36 or X.21
interface (firmware version 4.61 or higher for V3 service)
The universal transmission units (UTUs) from ADC Telecommunications are devices
which can be provisioned as LTU or NTU. The default configuration is NTU.

NTU - universal transmission unit types for SHDSL

To realize TDM services via SHDSL port the following types of SHDSL NTUs are
supported:
• SHDSL modem variant with
– SHDSL network interface (RJ45)
– G.703 (120 Ω (symmetrical) customer interface)
– X.21 customer interface (DB-15)
– V.35/V.36 customer interface (M34)
– V.28 local management interface (DB-9)
Important! The V.36 requires an adapter.
• SHDSL modem variant with
– SHDSL network interface (RJ45)
– G.703 (120 Ω (symmetrical) customer interface)
– X.21/V.35/V.36 customer interface (DB-25)
– V.28 local management interface (DB-9)
Important! Adapter cable required from DB-25 female to V.36.
One SHDSL NTU must be configured as STU-R. The other NTU must be configured
as STU-C. The STU-C and STU-R modes are selected via the local management port
only. The default mode for the NxNTU is STU-R.

NTU management
The management of the SHDSL modems is integrated in the AnyMedia ® Access
System and is performed using the SHDSL link EOC channel.
The NTU software (SW) upgrades can only be done by authorized maintenance
personnel using the NTU local console port. The local console ports are password
protected.

NTU configuration data for [S]HDSL

The NTU needs certain configuration data. The configuration data are not introduced
directly to the NTU. They are either fixed or derived from the provisioned service (see
“Configuration data V5 ISDN PRA services” (p. 5-79) up to “Configuration data n ×
64 kbps VLL services” (p. 5-82)). Local provisioning of NTUs is not necessary. The
provisioning data of the NTU are sent from the LTU to the NTU, every time when the
HDSL interface recovers.
The table below lists the provisioning data of the NTU.

Provisioning data NTU Derived from Remark

1
Line lock out Fixed parameter Provisioning of NTU via its local
EIA-232C interface is prevented
Protection switch Fixed parameter No protection switch (system
setting)
Sealing current mode Provisioning data of System setting
[S]HDSL AP - none or
- sealing current
AIS mode 1 Logical HDSL interface Depends on application mode
Application mode Logical HDSL interface - Point-to-point
- V3 point-to-point
- Single pair
- Unstructured point-to-point
- Point-to-multipoint
- Point-to-point single pair
- V3 point-to-point single pair
- Unstructured point-to-point
single pair
- Multirate single pair
Primary timing source of NTU Provisioned service(s) NTU derives timing from
(V.35/V.36/X.21) provisioned services (G.703 input
or [S]HDSL)
Transmit clock source VLL service Only for V.35, V.36, X.21 services
TS0 handling Provisioned service
Data rate (V.35/V.36/X.21)

Beginning TS
Interface type VLL service Only for V.35, V.36, X.21 services

Provisioning data NTU Derived from Remark

V.35/V.36 interface control V.35/V.36 services
signals:
- DSR-mode (on, off, standard)
- CTS-mode (on, off, standard)
- RLSD-mode (on, off,
standard)
X.21 interface control signals: X.21 services RLSD is known as status signal
- RLSD-mode (on, off, ″I″ on X.21 interface
standard)

Notes:
1. Only applicable to HDSL

HDSL application modes

The HDSL interface on an HDSL AP can be operated in different provisionable
application modes which impact the supported services:
• Point-to-point mode (see point-to-point mode - leased line and point-to-point mode
- leased line and ISDN PRA)
Full bandwidth of 2048 kbps for up to 31 × 64 kbps timeslots for different
structured applications. It can support one G.703 service (V5 ISDN PRA or n ×
64 kbps GLL) and additionally one n × 64 kbps digital leased line service
according to V.35, V.36, or X.21 (VLL).
• V3 point-to-point mode
Full bandwidth of 2048 kbps for 32 × 64 kbps timeslots for one V3 ISDN PRA
subscriber (PBX). The data transmission (complete 2-Mbps bit stream including
TS0) is switched transparently through the AnyMedia ® Access System.
In the V3 application the AnyMedia ® Access System and the NTU are part of the
digital section (DS), and AnyMedia ® provides the LTU functionality (see V3
point-to-point mode).
• Unstructured point-to-point mode
Full bandwidth of 2048 kbps for 32 × 64 kbps timeslots for one unstructured leased
line subscriber (UVLL or UGLL subscriber). The data transmission (complete
2-Mbps bit stream including TS0) is switched transparently through the
AnyMedia ® Access System.

• Single-pair mode, fractional installation

Half of the 2.048-Mbps payload (n × 64 kbps) can be transported. It can support
one G.703 service (V5 ISDN PRA or n × 64 kbps) and additionally one n ×
64-kbps digital leased line service according to V.35, V.36, or X.21 (VLL).
• Point-to-multipoint mode
A bandwidth of 30 × 64-kbps timeslots is supported. The 30 timeslots are split to
two independent HDSL interfaces (2 × 15 × 64-kbps timeslots). Two NTUs located
at the same or different subscribers can be connected. Each HDSL interface can
support one n × 64-kbps digital leased line service according to G.703 (GLL) and
additionally one n × 64 kbps digital leased line service according to V.35, V.36, or
X.21 (VLL).
Point-to-point mode, example for a leased line application.

Subscriber side Network side

AnyMedia Access System

NTU HDSL AP
HDSLpair 1 2
E1 HDSL
TE frame HDSLpair 2 module (LTU)
G. 703
2

n x 64 HDSL
TE kbps module (LTU)

V.35
V.36 HDSL
X.21

Point-to-point mode, example for a combination of leased line application and V5

ISDN PRA application.

Subscriber side Network side

AnyMedia Access System

T reference point

NTU HDSL AP
HDSLpair 1 2
V5
ISDN E1 HDSL
PBX frame HDSLpair 2 module (LTU)
PRA
G. 703 2

n x 64 HDSL
TE kbps module (LTU)

V.35
V.36 HDSL
X.21

Single-pair mode (fractional installation), example.

Subscriber side Network side

G. 703 AnyMedia Access System

(partially filled)
NTU HDSL AP
HDSLpair 1 2

TE E1 HDSL
frame module (LTU)

n x 64 HDSL
TE kbps module (LTU)

V.35
V.36 HDSL
X.21

Point-to-multipoint mode, example

G. 703 HDSL link 2

or
V.35/V.36/X.21

V3 point-to-point mode, example

Subscriber side Network side

T reference point V3 reference point

Digital section

AnyMedia Local
Access System Exchange
LTU

NTU 1) HDSL AP IO_E1

(LPS503) (FAC500B)
HDSLpair 1 2
V3 E1 HDSL
ISDN PBX frame HDSLpair 2 2
PRA module
G. 703 HDSL G. 703

1) Firmware version 4.61 or higher needed.

Unstructured point-to-point mode, example

Subscriber side Network side

AnyMedia Access System

HDSL AP
NTU (LPS504)
HDSLpair 1 2
E1 frame
or HDSL
TE HDSLpair 2 module (LTU)
n x 64 kbps
2
G. 703
or HDSL
module (LTU)
V.35/V.36/X.21

HDSL

The table below shows, which services can be provisioned on top of an HDSL logical
interface. The NTU at the customer premise must be able to support the chosen
service.

Services via HDSL

Services depending on the application mode via HDSL AP

Service types Point-to-point per V3 point-to-point Single pair per Unstructured Point-to-multipoint
HDSL interface per HDSL interface HDSL interface point-to-point per per HDSL link
HDSL interface

V5 ISDN PRA up to 31 bearer not applicable up to 16 bearer not applicable not applicable
(G.703) channels channels
(including TS 16) (including TS 16)

V3 ISDN PRA not applicable 32 bearer channels not applicable not applicable not applicable
(G.703) (including TS 0)

V5 ISDN PRA up to 31 bearer not applicable up to 16 bearer not applicable not applicable
(G.703) + VLL channels for V5 channels for V5
ISDN PRA ISDN PRA
(including TS 16), (including TS 16),
remaining remaining
timeslots for VLL timeslots for VLL

GLL up to 31 timeslots not applicable up to 16 timeslots not applicable up to 15 timeslots

(including TS 16) (including TS 16) (TS 16 not used)
VLL up to 31 timeslots not applicable up to 16 timeslots not applicable up to 15 timeslots

GLL + VLL up to 31 timeslots not applicable up to 16 timeslots not applicable up to 15 timeslots

for GLL, for GLL, for GLL (TS 16
remaining remaining not used),
timeslots without timeslots without remaining
TS 16 for VLL TS 16 for VLL timeslots for VLL

Service types Point-to-point per V3 point-to-point Single pair per Unstructured Point-to-multipoint
HDSL interface per HDSL interface HDSL interface point-to-point per per HDSL link
HDSL interface

UGLL not applicable not applicable not applicable 32 bearer channels not applicable
(including TS 0)
UVLL not applicable not applicable not applicable 32 bearer channels not applicable
(including TS 0)

SHDSL application modes

The interface on an SHDSL AP can be operated in different provisionable application
modes which impact the supported services:
• Point-to-point single pair mode and Point-to-point single pair mode with leased line
and ISDN PRA
Full bandwidth of 2048 kbps for up to 31 × 64 kbps timeslots for different
structured applications. It can support one G.703 service (V5 ISDN PRA or n ×
64 kbps GLL) and additionally one n × 64 kbps digital leased line service
according to V.35, V.36, or X.21 (VLL).
• V3 point-to-point single pair mode
Full bandwidth of 2048 kbps for 32 × 64 kbps timeslots for one V3 ISDN PRA
subscriber (PBX). The data transmission (complete 2-Mbps bit stream including
TS0) is switched transparently through the AnyMedia ® Access System.
• Unstructured point-to-point single pair mode and Unstructured point-to-point single
pair mode-AP_E1
Full bandwidth of 2048 kbps for 32 × 64 kbps timeslots for one unstructured leased
line subscriber (UVLL or UGLL subscriber). The data transmission (complete
2-Mbps bit stream including TS0) is switched transparently through the
AnyMedia ® Access System.
• Multi-rate single pair mode
Full bandwidth of 2048 kbps for 3 to 31 × 64 kbps timeslots for different
structured applications. It can support one n × 64 kbps digital leased line service
(VLL or GLL).
Point-to-point single pair mode, example for a leased line application

Subscriber side Network side

SHDSL AnyMedia Access System

SHDSL NTU SHDSL AP

SHDSLpair 2 E1 link
SHDSL port 1
TE E1 2
frame SHDSL port 2
G. 703
2
n x 64
SHDSL port 8
TE kbps E1 port 1

V.35 E1 port 4
V.36
X.21

Point-to-point single pair mode, example for a combination of leased line application
and V5 ISDN PRA application

Subscriber side Network side

SHDSL AnyMedia Access System

T reference point

SHDSL NTU SHDSL AP

SHDSLpair 2 E1 link
V5 SHDSL port 1
ISDN PBX E1 2
PRA frame SHDSL port 2
G. 703
2
n x 64
SHDSL port 8
TE kbps E1 port 1

V.35 E1 port 4
V.36
X.21

V3 point-to-point single pair mode, example for a V3 ISDN PRA application

Subscriber side Network side

SHDSL AnyMedia Access System

G. 703
SHDSL NTU SHDSL AP
SHDSL pair 2 E1 link
V3 SHDSL port 1
ISDN PBX E1 2
PRA frame SHDSL port 2
2
SHDSL port 8
E1 port 1

E1 port 4

Unstructured point-to-point single pair mode, example for an unstructured IO_E1

application

Subscriber side Network side

SHDSL AnyMedia Access System

SHDSL NTU SHDSL AP

SHDSL pair 2 E1 link
SHDSL port 1
TE 2048 kbps 2
SHDSL port 2
2
G. 703 SHDSL port 8
or
E1 port 1
V.35/V.36/X.21

E1 port 4

Unstructured point-to-point single pair mode, example for an unstructured AP_E1

application

Subscriber side Network side

SHDSL AnyMedia Access System

SHDSL AP
2
SHDSL port 1
SHDSL NTU
2
SHDSL port 4
SHDSL pair 2
TE 2048 kbps
2
SHDSL port 5
SHDSL port 6
2
G. 703 2
SHDSL port 7
or SHDSL port 8
V.35/V.36/X.21 E1 port 4
E1 port 3
E1 port 2
E1 port 1

Unstructured AP_E1 with clock transparency

Multi-rate single pair mode, example for a leased line application

Subscriber side Network side

SHDSL AnyMedia Access System

SHDSL NTU
SHDSL AP
SHDSLpair 2 E1 link
n x 64 SHDSL port 1
TE kbps 2
SHDSL port 2

V.35 2
V.36 SHDSL port 8
X.21 E1 port 1

E1 port 4

ISDN PRA services via SHDSL NTU

The table below shows, which services can be provisioned on top of an HDSL logical
interface on an SHDSL AP. The SHDSL NTU at the customer premise must be able to
support the chosen service.
Services depending on the application mode via SHDSL AP

Different service Point-to-point single V3 point-to-point single Unstructured Multi-rate single pair
types pair pair point-to-point single
pair

V5 ISDN PRA up to 31 bearer not applicable not applicable not applicable

(G.703) channels (including TS
16)

V3 ISDN PRA not applicable 32 bearer channels not applicable not applicable
(G.703) (including TS 0)

V5 ISDN PRA up to 31 bearer not applicable not applicable not applicable

(G.703) + VLL channels for V5 ISDN
PRA (including TS
16), remaining
timeslots for VLL

GLL up to 31 timeslots not applicable not applicable up to 31 timeslots

(including TS 16) (including TS 16)

VLL up to 31 timeslots not applicable not applicable up to 31 timeslots

GLL + VLL up to 31 timeslots for not applicable not applicable not applicable
GLL, remaining
timeslots without TS
16 for VLL
UGLL not applicable not applicable 32 bearer channels not applicable
(including TS 0)

UVLL not applicable not applicable 32 bearer channels not applicable

(including TS 0)

Configuration data V5 ISDN PRA services

Fixed configuration data

The following are fixed configuration data:
• Timing reference (derived from AnyMedia ® system clock)
• PBX loops receive timing (system clock) to transmit clock.

Provisionable parameters
The following parameters are provisionable:
• Application mode (single pair, point-to-point)
• Number of timeslots (excluding timeslot 16)
• Starting timeslot
• Grading information to LE (enable/disable)
• Sa5/Sa6 bit setting during normal operation
• Sealing current (on/off) per application pack.

Configuration data V3 ISDN PRA services

Fixed configuration data

The following are fixed configuration data:
• Timing reference (derived from AnyMedia ® system clock)
• PBX loops receive timing (system clock) to transmit clock.

Provisionable parameters
The following parameters are provisionable:
• Application mode (V3 point-to-point)
• Sealing current (on/off) per application pack.

Configuration data n × 64 kbps GLL services

Fixed configuration data

The following are fixed configuration data:
• Timing reference (derived from AnyMedia ® system clock)
• TE loops receive timing (system clock) to transmit clock.

Provisionable parameters
The following parameters are provisionable:
• Application modes (single pair, point-to-point and point-to-multipoint for HDSL;
point-to-point single pair and multi-rate single pair for SHDSL)
• Number of timeslots (excluding timeslot 16)
• Starting timeslot
• Sealing current (on/off) per application pack
• Cyclic redundancy check 4 (CRC-4) on/off for SHDSL drop only.

Configuration data n × 64 kbps VLL services

Provisionable parameters
The following parameters are provisionable:
• Application mode (single pair, point-to-point, point-to-multipoint)
• Number of timeslots
• Starting timeslot
• Data interface type (V.35, V.36, X.21)
• Transmit clock (internal rising, internal falling, external)
• Interface control signals
– CTS (clear to send control signal) on/off for V.35 and V.36
– DSR (data set ready) on/off for V.35 and V.36
– RLSD (receive line signal detection) on/off) for V.35, V.36 and X.21.

Configuration data UGLL services

Fixed configuration data

The following are fixed configuration data:
• Timing reference (derived from AnyMedia ® system clock)
• TE loops receive timing (system clock) to transmit clock.

Provisionable parameters
The following parameters are provisionable:
• Application mode (unstructured point-to-point).

Configuration data UVLL services

Provisionable parameters
The following parameters are provisionable:
• Application mode (unstructured point-to-point)
• Data interface type (V.35, V.36, X.21)
• Transmit clock (internal rising, internal falling, external)
• Interface control signals
– CTS (clear to send control signal) on/off for V.35 and V.36
– DSR (data set ready) on/off for V.35 and V.36
– RLSD (receive line signal detection) on/off) for V.35, V.36 and X.21.

E1 (2-Mbps) interface
...................................................................................................................................................................................................................................

Overview
The E1 Interface is an HDB3-coded interface with separate wires for transmit and
receive direction. The bit rate is 2048 kbps. It defines the electrical and physical
characteristics according to ETS 300 166, based on CCITT Recommendations G.703
and G.823. It is used for interconnecting digital network components. The AnyMedia ®
Access System supports two kinds of E1 interfaces:
• E1 interfaces on IO_E1
• E1 interfaces on SHDSL AP (AP_E1).

E1 interfaces on IO_E1
...................................................................................................................................................................................................................................
Via this interface, digital signals are transmitted in frames, according to ETS 300 167,
based on CCITT Recommendations G.704 and G.706.

E1 termination impedance
The following hardware configuration is adjustable on IO_E1 level:
• E1 termination impedance 75 Ω (unsymmetrical)
• E1 termination impedance 120 Ω (symmetrical)
Each of the four E1 ports has the same termination impedance.
Important! The cable impedance for the E1 cabling must fit the selected
termination impedance. The setting at delivery is 120 Ω.

Provisionable parameters
Provisionable parameters are:
• Far-end feeder signal degrade (10-7 to 10-4)
• Near-end feeder signal degrade (10-7 to 10-4)
• CRC4 on/off.

Signaling
V5.1, V5.2, and V3 signaling, as well as leased line and unstructured application, is
supported by the AnyMedia ® Access System.
If the E1 interfaces are used in leased line or unstructured application the information
content is determined by the customer via inband signaling.

E1 interfaces on AP_E1
...................................................................................................................................................................................................................................

E1 interfaces on SHDSL AP
The SHDSL AP (LPS510) provides four AP_E1 ports which can be used either as
unstructured 2.048 kbps links with clock transparency or as remote terminal links.

E1 termination impedance
The E1 termination impedance on the AP_E1 ports is 120 Ω (symmetrical). Via patch
panel the E1 termination impedance 75 Ω (unsymmetrical) is possible.

Interrelation between AP_E1 and SHDSL Ports

The four AP_E1 ports can be routed to an SHDSL port on the SHDSL AP
(unstructured leased line) or to the PCM highway on the backplane (remote terminal
link). The routing between AP_E1 ports and SHDSL ports is fix, when it is used (see
table below).

AP_E1 SHDSL port

AP_E1 Port 1 SHDSL Port 5
AP_E1 Port 2 SHDSL Port 6
AP_E1 Port 3 SHDSL Port 7
AP_E1 Port 4 SHDSL Port 8

AP E1 port used as unstructured leased line

An E1 interface via E1 port on SHDSL AP (AP_E1) used for unstructured leased line
applications according to ETS 300 418 provides clock transparency. The clock
transparency provided by a network is a mechanism to transport the clock information
provided at one subscriber’s end through the network to the others subscriber’s end.
The clock needs not to be synchronous to the network clock.

AP E1 port used as remote terminal link

When an AP_E1 port is used as remote terminal link, the corresponding SHDSL port
can not be used for any service.

Provisionable parameters
Provisionable parameters for AP_E1 ports used as remote terminal links are:
• Far-end feeder signal degrade (10-7 to 10-4)
• Near-end feeder signal degrade (10-7 to 10-4)

Signaling
The signaling for AP_E1 ports used as remote terminal links is a proprietary
AnyMedia ® signaling.

V5 parameters
...................................................................................................................................................................................................................................
V5 is an interface which is defined in ETS 300 324-1 (V5.1) and in ETS 300 347-1
(V5.2). The specification allows country (customer) dependent implementation. In the
following the country (customer) specific configuration data are shown.

Customer-specific V5.1 configuration data

The following customer-specific V5.1 configuration data are needed:
• E1 layer 1 error persistency time
• PSTN protocol information elements
• PSTN protocol timing parameter
• Call collision preference.

Customer-specific V5.2 configuration data

The following customer-specific V5.2 configuration data are needed:
• E1 layer 1 error persistency time
• PSTN protocol information elements
• PSTN protocol timing parameter
• Call collision preference
• Link identity check procedure
• BCC protocol timing parameters.

Provisionable parameters
Provisionable parameters are:
• V5 interface protocol type (V5.1, V5.2)
• V5 interface unique identifier
• V5 interface active provisioning variant
• Service degrade threshold
• HDLC flag monitoring
• Edition of the V5 protocol standard.

Ringer configuration in AnyMedia ® LAG 4300 Shelf

Configuration data for RGP100/RGU100

The RGP100/RGU100 parameters are associated with the customer key code. They are
stored per AnyMedia ® LAG 4300 Shelf on the COMDAC520. The values are fixed per
country and configured at compile time for each customer key code.
The following parameters are possible:
• Configuration data for RGP100:
– Ringing frequency
20 Hz, 25 Hz or 30 Hz
– Ringing voltage
75, 80, 85 or 90 Vrms
– Ringing mode
battery backed or earth backed ringing
• Configuration data for RGU100:
– Ringing frequency
16 Hz, 20 Hz, 25 Hz, 30 Hz or 50 Hz
– Ringing voltage
70, 75, 80, 85, 90, 95 or 100 Vrms
– Ringing mode
battery backed or earth backed ringing.

Ringer configuration in AnyMedia ® ETSI V5 Shelf

Purpose
The ringer provisioning is necessary, so that a ringing source is considered available in
the system (If no ringer is provisioned in the system, no ringing job is sent to the
POTS APs, respectively the POTS APs have no connection to the ringing busses). The
AnyMedia ® ETSI V5 Shelf supports provisioning of
• one internal ringer or
• one external ringer.
There is no explicit ringing protection provisioned. Ringing protection is implicitly
provided by provisioning of two ringers.

Configuration data for RGU100

The RGU100 parameters are associated with the customer key code. They are stored
per AnyMedia ® ETSI V5 Shelf on the COMDAC. The values are fixed per country
and configured at compile time for each customer key code.
The following parameters are possible for RGU100:
• Ringing frequency
16 Hz, 20 Hz, 25 Hz, 30 Hz or 50 Hz
• Ringing voltage
70, 75, 80, 85, 90, 95 or 100 Vrms
• Ringing mode
battery backed or earth backed ringing
• Master mode
controlled mode or uncontrolled mode.
The setting of these parameters is done via eight DIP switches on the RGU100. In the
“controlled” mode, the ringing frequency, the ringing output voltage, and the ringing
mode are configured by the COMDAC and the related DIP switches are not valid in
the “controlled” mode. For the description of the DIP switch settings see the Data
Sheet Book 363-211-251.

Product reliability

Purpose

Contents

Product reliability 5-93

Product reliability
...................................................................................................................................................................................................................................

Compliance with Bellcore reliability standards

The AnyMedia ® Access System adheres to applicable reliability sections of the
following Bellcore standards:
• TR-NWT-000057: Functional Criteria for Digital Loop Carrier Systems
• TR-NWT-000332: Reliability Prediction Procedure for Electronic Equipment
• TR-NWT-000357: Generic Requirements for Assuring the Reliability of
Components Used in Telecommunications Systems
• TR-NWT-000418: Generic Reliability Assurance Requirements for Fiber Optic
Transport Systems
• TA-NWT-000909: Generic Requirements and Objectives for Fiber in the Loop
Systems
• TA-NWT-000942: Hardware Reliability Assurance Program: Generic Requirements
for Telecommunications Products
• ETS 300 795 (DE/SPS-03027): Local exchange (LE) and access network (AN);
performance design objectives for call handling and bearer connection management;
May 1998

Downtime
Reliability is compliant with the availability and maintainability requirements in
TR-NWT-000057. The downtime for any individual subscriber line caused by the
AnyMedia ®Remote Terminal System is expected to be less than the required average of
17 minutes per year. This corresponds to an availability of 99.99677%. The table
below summarizes the downtime and maintainability requirements for the AnyMedia ®
Remote Terminal Systems.
Downtime and maintainability requirements for the AnyMedia® RT Systems

Remote Terminal systems (RT) Fiber-in-the-Loop systems (FITL)

Allocated downtime Narrow- band Broad- band Narrowband Broadband

(POTS & ISDN) ADSL HDT HDT

Overall downtime per year and per line ≤ 17 min ≤ 95 min ≤ 10 min ≤ 103 min

Hardware downtime per year and line ≤ 13 min ≤ 72 min ≤ 79 min

Software and procedural errors ≤ 4 min ≤ 23 min - -

Overall maintenance actions per 100 lines per year ≤ 1.5 min ≤ 3.5 min ≤ 3.5 min ≤ 3.5 min

Maintenance actions per 100 lines per year due to ≤ 1.2 min ≤ 3.0 min ≤ 3.0 min ≤ 3.0 min
hardware failures

Purpose
This chapter provides the information necessary to plan and engineer ATM applications
of the AnyMedia ® Access System.
This section discusses system planning and engineering of ATM xDSL services which
are transported via an ATM network. Note that the Applications and Planning Guide
for IP-based Services (363-211-587) includes the description of xDSL services which
are transported via an IP network.

Contents

ATM xDSL system capacity 6-5

ATM xDSL system capacity of the AnyMedia ® Access System 6-6
Maximum number of shelves in a daisy-chain set 6-9
Maximum number of virtual connections 6-10
Maximum traffic per feeder 6-12
ATM xDSL data transfer performance 6-15
ATM xDSL growth, degrowth and migration scenarios 6-18
Introduction 6-19
Growth scenarios 6-20
Degrowth scenarios 6-23
Migrating from simplex to duplex AFM mode 6-24
Migrating from duplex to simplex AFM mode 6-25
Migration from an ATM xDSL system to an IP system via IP-AFM 6-26
ATM xDSL installation and connection recommendations 6-27
Installation recommendations 6-28
Initial deployment with no ATM xDSL services 6-30
Growth situations 6-31

Cables and hardware 6-32

Large ATM xDSL deployments 6-33
Interoperability 6-34
Engineering narrowband to ADSL upgrade 6-35
Engineering for ADSL over ISDN 6-39
Engineering the BB ATM Operations Channel for shelves cascaded via 6-40
E1IMA APs
New installation concept 6-42
Engineering the LAN connection 6-45
BB ATM Operations Channel 6-50
ATM xDSL Port Numbering 6-52
Quality of Service Provisioning 6-55
Connection Admission Control algorithm 6-56
Shelf provisioning for QoS 6-57
Special considerations for a daisy chain 6-62
xDSL transmission profile effect on QoS 6-64
ATM traffic profile provisioning for QoS 6-65
Cross-connect provisioning 6-67
Overbooking factor 6-69
Congestion management schemes 6-70
Traffic shaping - Policing - Scheduling 6-72
ATM xDSL system turn-up and service provisioning scenarios and 6-74
parameters
Introduction 6-75
Turn-up provisioning 6-77
Service activation 6-81
Shelf cascading via E1IMA APs 6-83
Port provisioning and addressing for duplex mode AFMOs 6-85
Slot numbering and AIDs for the AnyMedia ® LAG Shelves 6-88
Service states 6-90
Profiles 6-96
ADSL parameters - port settings 6-98
Setting other ADSL transmission parameters using the ADSL 6-102
transmission profile
SHDSL parameters - port settings 6-106
E1IMA AP settings 6-109

ATM traffic parameters 6-111

Parameters in failure report profiles 6-112
Default values for ATM xDSL system provisioning parameters 6-114
Turn-up and service activation provisioning default values 6-116
Predefined ADSL transmission profiles 6-128
Predefined SHDSL transmission profiles 6-132
Predefined ADSL performance management profiles 6-133
Predefined SHDSL performance management profiles 6-134
Predefined ATM traffic profiles 6-135
Predefined ATM Traffic statistics threshold profiles 6-137
Predefined failure report profiles 6-138
Parameters in DMT profile 6-142
Parameters in RFI notch profiles 6-143
ADSL transmission specification summary 6-144
Alarm severity values 6-146
Alarm severity and GSI ATM xDSL identifiers tables 6-146
ATM feeders 6-159
Overview of ATM feeders 6-159
ATM E3/DS3 feeder 6-161
E3/DS3 connections to the ATM backbone network when using a single 6-163
AFME3/DS3 in simplex mode with no daisychaining
E3/DS3 connections to the ATM backbone network when using two 6-164
AFME3/DS3s in duplex mode with no daisychaining
E3/DS3 Daisychaining capability 6-165
ATM E1 feeder (Background on IMA) 6-170
ATM E1 feeder 6-171
ATM STM-1/OC-3c feeder 6-174
STM-1/OC-3c Daisychaining capability 6-177
AFMOs in duplex mode 6-180
Optical couplers 6-187
Optical AFM Attenuation Design 6-188
ATM xDSL synchronization and timing 6-193
Synchronization and timing for E3/DS3 ATM network feeder interface 6-194
Synchronization and timing for E1 ATM network feeder interface 6-196
Synchronization and timing for STM-1/OC-3c ATM network feeder 6-198
interface

ATM xDSL timing 6-200

Synchronization and timing for the AnyMedia ® LAG 4300 Shelf 6-201
Miscellaneous 6-202
ATM xDSL product reliability 6-203
ATM xDSL system powering 6-204
Testing of drops on ATM xDSL application packs 6-205

ATM xDSL system capacity

Purpose
This section describes the ATM xDSL capacity of the AnyMedia ® Access System
depending on the different shelf types used, and on whether the system operates as a
standalone system or is part of a daisy-chain.

Contents

ATM xDSL system capacity of the AnyMedia ® Access System 6-6

Maximum number of shelves in a daisy-chain set 6-9
Maximum number of virtual connections 6-10
Maximum traffic per feeder 6-12
ATM xDSL data transfer performance 6-15

ATM xDSL system capacity of the AnyMedia ® Access System

Overview
The ATM xDSL capacity of an AnyMedia ® Access System or a set of daisy-chained
shelves is determined by the following factors:
• The number of subscriber lines, based on the type/number of ATM xDSL pack
installed.
Note that for the discussion of system capacity in this section, it is assumed that
the AnyMedia ® Access System is populated entirely with ATM xDSL packs. In a
mixed system that includes traditional narrowband packs, the ATM xDSL capacity
of the system would be reduced accordingly.
• System capacity, based on the number of ATM xDSL APs installed
• The number of BB subsystems daisy-chained (one AnyMedia ® LAG 4300 Shelf
contains two BB subsystems which may be daisy-chained)
• The number of virtual connections, limited by VP/VC rules
• The amount of traffic the system can carry, depending on the feeder type
Important! Except where noted, all of the details regarding ATM xDSL data
transfer performance apply to all AFM types.
This section discusses the above factors, followed by a discussion of connection
admission control (CAC). CAC verifies that there are sufficient resources for each
connection when it is provisioned.

Maximum number of slots for APs per BB subsystem

The maximum number of slots that can be equipped with APs depends on whether the
BB subsystems use one or two AFMs.
The following table shows the maximum numbers of usable slots for a BB only
configuration

Mainshelf LAG 1900 LAG 4300 upper LAG 4300 lower AnyMedia ®
800 Shelf

Simp. Dup. Simp. Dup. Simp. Dup. Simp. Dup. Simp

No. of 15 14 13 12 18. 17 23 22 7
usable
slots

Maximum number of subscriber lines

The maximum number of ATM xDSL service subscriber lines per AnyMedia ® Access
System arrangement is determined by the following:
• The type of ATM xDSL AP being deployed
• Whether one or two BB subsystems are installed
• Whether the BB subsystems are using one or two AFMs (simplex or duplex).

The following table summarizes the maximum number of various DSL services
supported per ATM xDSL AP, and per AnyMedia ® Access System when each shelf
contains either one AFM or two AFMs. The table assumes that all of the shelf’s AP
slots are equipped with the same type of AP.
The following table shows the maximum numbers of ATM xDSL subscriber lines in a
BB-only configuration

xDSL AP Function Max. No. of ETSI V5 Shelf LAG 1900 LAG 4300 LAG 4300 Shelf AnyMedia ®
Code xDSL lines Shelf Shelf upper lower row 800 Shelf
per pack row

Simp. Dup. Simp. Dup. Simp. Dup. Simp. Dup. Simp.

ADSL16p LPA416 16 240 224 208 192 288 272 368 352 112

ADSL16i LPA417 16 240 224 208 192 288 272 368 352 112
ADSL_16p LPA420 16 240 224 208 192 288 272 368 352 112
1
ADSL32 LPA432 32 480 448 416 384 576 544 736 704 224
LPA434
P32A32 LPA832 32 480 448 416 384 576 544 736 704 224
LPA833

SHDSL16 LPS702 16 260 224 352 208 288 272 368 352 112
IMA AP LPA941 1 IMA 15 14 13 12 18 17 23 22 n.a.
Group or
1 E1-UNI

Notes:
1. For POTS services only in conjunction with LPZ110

The following table shows the maximum number of ATM xDSL subscriber lines per
BB subsystem assuming that:
• the AnyMedia ® Mainshelf is configured for simplex AFM mode
• the AnyMedia ® Mainshelf is connected to the maximum number of ONUs
• all eight AP slots in the ONUs are fully equipped with ATM xDSL APs of the
same type.

Mainshelf LAG1900 LAG 4300 upper LAG 4300 lower AnyMedia ®

800 Shelf

Simp. Dup. Simp. Dup. Simp. Dup. Simp. Dup.

ADSL16p 912 896 784 768 288 272 1328 1312 400

ADSL4i 228 224 196 192 72 68 332 328 100

ADSL16i 912 896 784 768 288 272 1328 1312 400

ADSL32 1824 1792 1568 1536 576 544 2656 2624 800

P32A32 1824 1792 1568 1536 576 544 2656 2624 800

Mainshelf LAG1900 LAG 4300 upper LAG 4300 lower AnyMedia ®

800 Shelf

Simp. Dup. Simp. Dup. Simp. Dup. Simp. Dup.

SHDSL16 912 896 784 768 288 272 1328 1312 400

Maximum number of shelves in a daisy-chain set

AnyMedia ® ETSI V5 Shelves may be daisy-chained, so that they are served by a single
feeder to the ATM network. The maximum number of AnyMedia® ETSI V5 Shelves
that can be daisy-chained depends on whether the timing source is set to line-timed or
free-running, as follows:
• Line-timed: up to eight AnyMedia ETSI V5 Shelves
• Free-running: limited only by the availablility of VPIs; however, eight is the
recommended limit.
AnyMedia ETSI V5 Shelves in a daisy chain may be placed at any distance supported
by their connecting feeder cables, for example, in different racks, on different floors, or
in different buildings.
Timing sources are discussed in “ATM xDSL synchronization and timing ” (p. 6-193).

Maximum number of virtual connections

Rules
Each ATM xDSL line can be provisioned with one or more virtual connections. The
rules that govern the maximum number of virtual connections are as follows:
1. There is a maximum of 255 VPs per feeder connection to the ATM transport
network (that is, per daisy-chained set). This total includes all upstream VPs,
downstream VPs, local VPs, OAM&P VPs, and shelf VPs for all shelves.
2. There is a maximum of 243 VP cross-connects in a single shelf. Therefore a non
daisy-chain configuration can only support 243 VP cross-connections. However, a
daisy-chain configuration supports up to 255 VPs, with no more than 243 VP
cross-connects on any one shelf in the daisy-chain. Note that the maximum number
of VC cross-connects allowed in a shelf at any given time is not affected by (i.e., is
independent of) the number of VP cross-connects in the shelf.
3. There is a maximum of 5500 VC cross-connects per shelf.
4. Up to 128 Shelf VPs support VC cross-connects on the AFMs. All of the VC
cross-connects can be on one Shelf VP.
5. The maximum of 243 VP cross-connects a shelf supports can be distributed among
the xDSL ports in any combination.
6. The set of VCs within a shelf VP can be distributed across ATM xDSL lines.
7. An xDSL AP supports VC cross-connects on up to 56 different subscriber VPs
distributed in any combination among its xDSL ports. In this context, a VP is
identified by the xDSL port and subscriber VPI. Here are some examples of VPs
that are different in this context:
• Port1/VPI3 and Port2/VPI3 are two different subscriber VPs in this context.
• Port3/VPI2 and Port3/VPI4 are two different subscriber VPs in this context.
Up to 1024 VC cross-connects can be supported within one of these subscriber
VPs. Otherwise, the maximum number of VC cross-connects a shelf supports
can be distributed among the xDSL ports in any combination. So, in the second
example above, up to 2048 VC cross-connects can be supported on Port 3 (that
is, up to 1024 VC cross-connects on each subscriber VP).
Note that most configurations can be accommodated using only one of these
subscriber VPs on an xDSL port. All VC cross-connects to the same end-user
can use the same subscriber VP on the xDSL port, regardless of the mix of
service categories among the VCs. For example, two VCs, each with a different
service category, can be placed on the same subscriber VP on an xDSL port.
This behavior is different from the rules for using a Shelf VP (on the feeder).
That is, all the VCs carried in the same Shelf VP must have the same service
category. There is no restriction like this for the subscriber VPs associated with
an xDSL port.
8. An E1-IMA AP supports
• up to 255 VP connections
• up to 9 channelized VPs (a channelized VP is a VP which contains VCCs)
• up to 1024 VCCs per channelized VP
• up to 9 × 1024 = 9216 VCCs (configured within 9 channelized VPs).
...................................................................................................................................................................................................................................
6-10 363-211-586
Issue 6, July 2007
System planning and engineering for ATM xDSL services Maximum number of virtual connections

As the AFM supports a maximum of 243 VPCs only up to 243 VPCs will be
configured on an E1IMA AP.
As the AFM supports a maximum of 5500 VCCs only up to 5500 VCCs will be
configured on an E1IMA AP.
9. A VP cannot be split across AnyMedia ® ETSI V5 Shelves.
10. Each AnyMedia ® ETSI V5 Shelf (standalone or in a daisy-chained set or cascaded)
requires one virtual connection with rt-VBR service class for the BB ATM
Operations Channel (see “BB ATM Operations Channel ” (p. 6-50)). If the BB
ATM Operations Channel is to be carried by a shelf VP, then that shelf VP has to
be provisioned for the rt-VBR service class. If the BB ATM Operations Channel is
to be carried on its own VP, then the system automatically sets the service class for
rt-VBR.
11. All VC connects within a Shelf VP must be provisioned with the same service
class as the Shelf VP
12. An ADSL AP supports partial packet discard (PPD) in downstream direction for up
to 511 VCCs. If more than 511 VCCs are provisioned for an AP with PPD enabled,
for these VCCs (above 511) PPD will not be executed independent of “AAL5
frame discard” parameter value.
13. An ADSL2_32i (LPA438) supports on subscriber side VC cross-connects as
follows:
• Up to 224 different VPs
• Possible VPI values range from 0 to 255
• Possible VCI values range from 0 to 1023
• Up to 256 VCI cross connections to each VPI.
The following are examples of provisioning 5500 VCs on a shelf:
• Three UBR shelf VPs, two with 2000 VCs and one with 1500 VCs
• One UBR shelf VP with 3250 VC connections and one rt-VBR shelf VP with 2250
VCs
• One UBR shelf VP with 3000 VCs, one rt-VBR shelf VP with 2000 VCs, one
nrt-VBR shelf VP with 490 VC connections, and one CBR shelf VP with 10 VCs
• Four UBR shelf VPs, each with 1375 VCs
• Ten UBR shelf VPs with 100 VCs per shelf VP, 75 rt-VBR shelf VPs with 10 VCs
per shelf VP, seven nrt-VBR shelf VPs with 300 VCs per shelf VP, and 10 CBR
shelf VPs with 165 VCs per shelf VP
• One UBR shelf VP with 2750 VCs, one rt-VBR shelf VP with 2750 VCs, and 50
VP cross-connects (with no VC connections) each provisioned as any of the
supported service classes. Note that the maximum number of 5500 VC
cross-connects allowed in a shelf at any given time is not affected by the number
of VP cross-connects in the shelf.

Maximum traffic per feeder

Maximum traffic for an E3/DS3 feeder

For an E3 or a DS3 feeder, the maximum ATM traffic is given in the following table
for the different feeder and framing options. The choice of this option should be
compatible with the ATM network. Direct cell mapping is applicable for E3 and DS3,
whereas PLCP is applicable only for DS3. These numbers are based on 53 bytes per
cell. For information on provisioning these framing formats, see “ATM E3/DS3 feeder”
(p. 6-161).

Rate Direct Cell Mapping PLCP

Feeder type DS3 E3 DS3
Megabits per second (Mbps) 44.096 33.920 40.704
Cells per second 104,000 80,000 96,000

For daisy-chained shelves, the maximum bandwidth on the feeder to the ATM transport
network is shared by all virtual connections in all shelves.
Important! When filling out an Engineering Work Order for a shelf that is to be
added to a daisy chain using AFME3/DS3s, be sure that the sum of the Shelf PCRs
for all of the shelves is no greater than the maximum allowed PCR value (which
equals the full bandwidth of the feeder interface to the ATM network).

Maximum traffic for an E1 feeder/IMA group

For an AFME1 feeder or for an E1IMA AP, the maximum ATM traffic ranges are the
following:
• UNI mode (one feeder)
– 1.920 Mbps payload
– 4,528 ATM cells per second
• IMA mode (where N is the number of E1 interfaces that are active):
– 1.920 × N Mbps payload at E1 rate
– ATM cells per second (Ranges of Shelf PCR values see table below)
The following table shows ranges of Shelf PCR values for an IMA-E1 feeder or for an
E1IMA AP, (cells/s).

IMA Maximum value for the given number of E1 lines Min. Default
Frame upstream/
length 1 2 3 4 5 6 7 8 downstream
(cells) (cells/s)

32 4,384 8,769 13,153 17,538 21,923 26,307 30,692 35,077 452/450 4,384

64 4,455 8,910 13,366 17,821 22,276 26,732 31,187 35,642

128 4,490 8,981 13,472 17,962 22,453 26,944 31,435 35,925

256 4,508 9,016 13,526 18,033 22,542 27,050 31,558 36,067

UNI mode
4,528 452/450 4,528

The admissible bandwidth is calculated as:

Admissible bandwidth (up) ≤ shelfPCR − 452
Admissible bandwidth (down) ≤ shelfPCR − 450
For information on provisioning an E1-IMA feeder, see “ATM E1 feeder (Background
on IMA)” (p. 6-170).
The following table shows the maximum bandwidth of an E1IMA AP, (cells/s),
depending on the IMA frame length and the number of links.

IMA Maximum bandwidth for the given number of E1 lines

Frame
length 1 2 3 4 5 6 7 8
(cells)
32 4,384 8,769 13,153 17,538 21,923 26,307 30,692 35,077
64 4,455 8,910 13,366 17,821 22,276 26,732 31,187 35,642
128 4,490 8,981 13,472 17,962 22,453 26,944 31,435 35,925
256 4,508 9,016 13,526 18,033 22,542 27,050 31,558 36,067
UNI mode
4,528

Maximum traffic for an STM-1/OC-3c feeder

For an STM-1/OC-3c feeder, the maximum ATM traffic is
• 149.760 Mbps
• 353,200 ATM cells per second.
This maximum bandwidth is shared by all virtual connections in all shelves in a
daisy-chained set. For information on provisioning an STM-1/OC-3c feeder, see “ATM
STM-1/OC-3c feeder” (p. 6-174).

Important! When filling out an Engineering Work Order for a shelf that is to be
added to a daisy chain using AFMOs, be sure that the sum of the Shelf PCRs for
all of the shelves is no greater than the maximum allowed PCR value (which
equals the full bandwidth of the feeder interface to the ATM network).

Connection admission control

The AnyMedia ® Access System will verify that sufficient resources are available for a
connection at the time it is provisioned. If not, the connection request will fail. The
connection admission control (CAC) function takes into account the connection traffic
contract, available system resources to support QoS objectives of the connection, and
the level of overbooking, in deciding whether to accept the connection. Since there are
no QoS objectives associated with connections based on the UBR service category, no
bandwidth-related admission criterion is placed on UBR connections, i.e., UBR
connections are simply accepted. The term QoS objective in this context means the
quality of service requirement, such as CLR, associated with the connection.
The number of connections the AnyMedia ® Access System can support, in other words
the system capacity from a bandwidth perspective, is dependent on the connection
traffic contract and the other parameters associated with QoS provisioning. The
AnyMedia ® Access System can support up to 5500 ATM cross connects per shelf from
all four service categories.

ATM xDSL data transfer performance

Overview
There are a number of interactive issues that affect the data transfer performance of
TCP/IP applications (for example, FTP) over ATM xDSL networks. The overhead
associated with the various layers of the protocol stack reduces the throughput of data
transfer. In an end-to-end network that includes an AnyMedia ® Access System, the
sources of overhead are as follows:
• TCP/IP
• AAL5
• ATM
• Physical layers.
Except where noted, all of the details regarding ATM xDSL capacity apply to all AFM
types.

One-way data transfer

If the effects of retransmissions due to errors and network congestion are not included,
and if one-way data transfer is assumed, then the efficiency is somewhere between
70% and 80%. The maximum expected throughput is controlled by the segment in the
end-to-end transmission path with the lowest physical-layer bit rate multiplied by the
efficiency.
In an end-to-end network that includes an AnyMedia ® Access System, the bit rate on
the ATM xDSL transmission span between the AnyMedia ® Access System and the
end-user’s modem is likely to be the lowest physical-layer bit rate in the network.
Therefore, the efficiency of data transfer in this configuration is the ADSL bit rate
multiplied by the efficiency (for example, if the downstream ADSL bit rate is
6.144 Mbps, then the maximum throughput of an FTP transfer from a host to the end
user is between about 4.4 Mbps and about 5.0 Mbps).

Bidirectional data transfer

The discussion so far applies to data transfer in one direction (for example, an FTP
transfer from a server to an end-user’s client PC). However, the situation changes when
data transfer occurs simultaneously in both directions.
An example is two FTP transfers occurring at the same time for the same end user, as
follows:
• From a server to the end-user’s client PC
• From the end-user’s client PC to a server.

In this case, if an ADSL AP is used, the asymmetrical upstream and downstream

transmission rates on the ADSL transmission span cause the downstream throughput to
go down. Typically, the downstream throughput will be about the same as the upstream
throughput. This effect is caused by the following two activities that compete for
throughput in the upstream direction (that is, the direction that is slower):
• Acknowledgements the subscriber’s PC sends toward the network for FTP traffic it
receives from downstream transmission.
• The upstream FTP traffic itself.
The upstream traffic reduces the rate at which the acknowledgements can be sent. The
reduced acknowledgement rate forces the downstream throughput to be lower. This
effect is a characteristic of TCP/IP. It occurs for any application that operates in the
protocol stack above TCP/IP.
Following is an example of the effect on downstream transmission:
• Downstream rate: 6.144 Mbps
• Upstream rate: 640 kbps
• Upstream throughput if efficiency is 75%: 480 kbps
• Downstream throughput is about 480 kbps, similar to upstream.
Important! The downstream rate did not figure in the throughput calculation.

Adjustments to improve xDSL data transfer performance

If the measured throughput is less than expected based on the efficiency discussion
above, there are several items that can be checked and/or adjusted at the ends of the
network (for example, a server and/or the end-user’s PC) to improve throughput:
• The server or end-user’s PC must use Path MTU Discovery (RFC1191). This
allows systems to use the largest possible packet size, rather than the default of
512 bytes.
• The server or end-user’s PC must support RFC1323 Large Windows extensions to
TCP. These extensions enable new features in the TCP/IP protocols needed for high
speed transfers.
• The server or end-user’s PC must support large enough socket buffers for reading
and writing data to the network. Typical Unix systems include a default maximum
value for the socket buffer size between 128 kbit and 1 Mbit. For many paths, this
value is not enough and must be increased.
• The application must set its send and receive socket buffer sizes (at both ends) to at
least the bandwidth multiplied by the delay. (The round-trip delay for a link can be
measured with traceroute.)

• MTU size can be optimized for either one-way or bidirectional throughput. For
one-way transmission, larger MTU sizes improve throughput. As stated above, in
“One-way data transfer” (p. 6-15), the maximum one-way efficiency is between
70% and 80%. To reduce the difference in downstream throughput between
one-way transmission and bidirectional transmission, the following settings are
needed:
– Larger MTU sizes downstream (just like when optimizing for one-way
throughput)
– Smaller MTU sizes upstream (opposite of optimizing for one-way throughput).
Therefore, in a network optimized for bidirectional throughput, one-way upstream and
one-way downstream efficiencies will be less than the maximum one-way upstream
and one-way downstream efficiencies.

ATM xDSL growth, degrowth and migration

scenarios

Purpose
There are several ways to grow and degrow ATM xDSL capacity in an AnyMedia ®
Access System. In addition, it is possible to migrate from simplex to duplex AFM
mode and from duplex to simplex AFM mode, software releases may be upgraded or
feeder bandwidth can be increased by changing the AFM type.

Contents

Introduction 6-19
Growth scenarios 6-20
Degrowth scenarios 6-23
Migrating from simplex to duplex AFM mode 6-24
Migrating from duplex to simplex AFM mode 6-25
Migration from an ATM xDSL system to an IP system via IP-AFM 6-26

Introduction
...................................................................................................................................................................................................................................

Overview
Important! The terms ″preferred AFM slot″ and ″AFM protection slot″ have been
added to the slot designations ″slot 16″ and ″slot 15″ in order to remind the user.
that the slot designations in the BB subsystems in an AnyMedia ® LAG 4300 Shelf
are different from those used in the AnyMedia ® ETSI V5 Shelf. For a reference list
of the slot designations refer to “Slot numbering and AIDs for the AnyMedia ®
LAG Shelves” (p. 6-88).
Growth of ATM xDSL services
The method for system growth depends on existing AnyMedia® shelves capacity and
ATM feeder bandwidth utilization. All of these methods for system growth can be used
altogether or individually. The following scenarios are provided:
• Pack upgrade
• AnyMedia ® Mainshelf expansion
• AnyMedia ® Mainshelf addition - standalone
• AnyMedia ® Mainshelf addition - daisy chain
• AnyMedia ® Mainshelf addition - cascading
Assuming that there are still unequipped slots in the shelf, only pack upgrade affects
existing service.
Degrowth of ATM xDSL services
Two types of system degrowth are possible. The following scenarios are provided:
• Removing an ATM xDSL AP
• Removing ATM xDSL services from shelf.
Important! Except where noted, all of the details regarding ATM xDSL growth
and degrowth apply to all AFM types.
Migration between simplex and duplex AFM modes
Both, simplex and duplex modes are supported by all AFMs with the exception of
LPA941 and some old AFM types. The following scenarios are provided:
• Migrating from simplex to duplex AFM mode
• Migrating from duplex to simplex AFM mode.
Release upgrade
For the feasibility and details of a Release upgrade please contact your local
representative from Alcatel-Lucent or the International Deployment team.
Growth of feeder bandwidth
The feeder bandwidth to the system can be increased by exchanging an AFM with
smaller bandwidth with an AFM type with more bandwidth.

Pack upgrade (ADSL only)

ADSL growth, can be achieved by replacing existing ADSL packs with new ADSL
packs of greater modularity. For example, existing ADSL4p packs can be replaced with
ADSL8p packs, or existing ADSL8p packs can be replaced with new ADSL16p packs.
(In each case noted above, the new ADSL packs will double the number of data lines
that may be served from a shelf. Doubling is not required, however, and increases of
other multiples can be achieved, depending on the modularity of the existing packs,
and whatever new ADSL packs are chosen.) Existing ADSL service automatically
migrates to the same pair on the replacement pack. New customers can be
accommodated on additional ports provided by the new AP.
For another example, if additional POTS lines are needed, an ADSL4p AP may be
upgraded to one of the combo APs. The ADSL customer’s POTS service can be
provided by this pack, making the external POTS line free for a new customer. In this
case a POTS disconnect, new combo pack provisioning, and rewiring are required to
restore POTS service.
Important! If you are upgrading an AnyMedia® shelf in an already existing DC
rack of type J1C283B-1List1 with high-capacity ADSL packs - including 16 ports
or more - and the shelf is equipped with a PFU500, don’t insert more than a total
of 11 ADSL APs at a maximum per AnyMedia ® shelf because of the higher power
consumption.

AnyMedia ® Mainshelf
In this scenario, an existing AnyMedia ® Mainshelf already equipped with an AFM has
empty slots remaining to accommodate the growth needs. A new ATM xDSL AP is
inserted to accommodate new customers. Subscriber service is activated as described in
“ATM xDSL system turn-up and service provisioning scenarios and parameters”
(p. 6-74).

AnyMedia ® Mainshelf addition (standalone)

In this scenario, all the feeder bandwidth to the ATM transport network and/or all the
shelf capacity has been used. Therefore, a new shelf and feeder are required. The new
AnyMedia ® Mainshelf is turned up as described in “ATM xDSL system turn-up and
service provisioning scenarios and parameters” (p. 6-74). The remaining installation
and growth for each customer is identical to the AnyMedia ® Mainshelf expansion
scenario.

AnyMedia ® Mainshelf addition (daisy-chain)

In this scenario, a shelf already provides the maximum number of ATM xDSL lines,
and the feeder that connects to the ATM transport network has spare capacity.

An additional AnyMedia ® Mainshelf can be used to add more ATM xDSL lines at the
site, as follows:
• Use another AnyMedia ® Mainshelf, which is already installed, that has AP slots
available for one AFM and additional ATM xDSL APs.
• Or, install a new AnyMedia ® Mainshelf as described in the AnyMedia ® Mainshelf
addition (standalone) scenario.
In either case, the second AnyMedia ® Mainshelf is provisioned as described in the
AnyMedia ® Mainshelf addition (standalone) scenario, but the shelf’s feeder input
connection comes from the feeder output of the first shelf (that is, the Mainshelf with
no AP slots available). The second Mainshelf does not connect directly to the ATM
switch. The first Mainshelf in the daisy-chain is then provisioned to enable it to pass
its unused virtual paths to its feeder connection. The remaining installation and growth
for each customer is identical to the AnyMedia ® Mainshelf expansion scenario.
The daisychaining feature allows two or more shelves configured to carry ATM xDSL
to share the same feeder connection to the ATM switch. For more details, see “Local
shelf daisychaining” (p. 1-33) and “Remote shelf daisychaining via SDH ring ”
(p. 1-34). Without daisychaining, each AnyMedia ® Mainshelf at a site that provides
ATM xDSL would need a separate feeder to the ATM switch. When shelves are
daisy-chained, the rules in “ATM xDSL system capacity” (p. 6-5) need to be followed
to ensure that the shared feeder has enough bandwidth for the number of ATM xDSL
customers to be served. If the feeder to be shared does not have enough capacity,
feeder lines need to be added to the site to provide the bandwidth required. In this
case, the Mainshelves would not be daisy-chained.
Important! Daisychaining is not possible when using the AFME1 LPA941.

Daisy-chain partition and addition of a new E3/DS3 feeder

In this scenario, the E3/DS3 feeder that feeds a daisy-chain is approaching its full
capacity. Therefore, the daisy-chain is partitioned into two components, daisy-chain 1
and daisy-chain 2, and daisy-chain 2 is connected to a new E3/DS3 feeder.
The procedure is as follows: after the daisy-chain alarms are disabled, VPIs are
reconfigured for what are to become the new daisy-chain 1 and daisy-chain 2. Cable
connections are broken between the last AFME3/DS3 in daisy-chain 1 and the first
AFME3/DS3 in daisy-chain 2. The new E3/DS3 feeder is connected to the first
AFME3/DS3 of daisy-chain 2. The VPIs for each daisy-chain are updated. Alarms are
enabled for both daisy-chains.

AnyMedia ® Mainshelf addition - cascading

In this scenario, the ATM xDSL capacity of an AnyMedia ® Mainshelf equipped with
an AFM grows by adding further BB subsystems via shelf cascading . E1 feeders
connect the E1IMA AP in the host shelf to the AFME1 in a cascaded shelf.
The procedure can be used for applications where a new shelf is turned up with an
AFME1 and then via shelf cascading connected to an existing host shelf with any
AFM type inserted or for connecting existing shelves with an AFME1 inserted via
....................................................................................................................................................................................................................................
363-211-586 6-21
Issue 6, July 2007
System planning and engineering for ATM xDSL services Growth scenarios

shelf cascading to a new host shelf with a higher capacity AFM inserted, e.g. the
AFMO. The second application is service-affecting when the E1 feeders are
disconnected and reconnected to the E1IMA APs.
For each cascaded subsystem the hosting AnyMedia ® Mainshelf has to be equipped
with an E1IMA AP. If an LPA941 is determined to operate as an E1IMA AP, the
current software load has to be R1.25 or higher. Otherwise the LPA941 needs to be
inserted in the preferred AFM slot of a powered shelf and upgraded to R1.25 before it
can be used in an AP slot as E1IMA AP.

Growth of feeder bandwidth

The feeder bandwidth of the system can be increased by changing an AFM with
smaller bandwidth against an AFM type with more bandwidth, e.g.
• AFME1 → AFME3/DS3
• AFME1 → AFMO
• AFME3/DS3 → AFMO.
For this procedure only few actions are required:
• Backup the database of the AFM inserted
• Remove this AFM from the shelf
• Insert the new AFM type into the same slot
• Restore the database of the previous AFM on the new AFM
• Provision the feeder port to support the new AFM type.
The provisioning of the xDSL ports, the ATM cross-connects and the profiles will be
retained during the migration.
Note that the upgrade can only be done within the same BB subsystem, that means,
within the same AnyMedia ® ETSI V5 Shelf or in the AnyMedia ® LAG 4300 Shelf
within the same row.
The procedure is service-affecting.

Degrowth scenarios
...................................................................................................................................................................................................................................

Removing an ATM xDSL AP

System capacity can be rearranged for load balancing or other needs by combining the
growth and degrowth operations.
This system degrowth scenario is the removal of an ATM xDSL AP from an in-service
AnyMedia ® shelf. This scenario assumes that customer service is no longer required on
any of the ports of the ATM xDSL AP that is being removed.
Suppose that some ATM xDSL services on an AnyMedia ® shelf are no longer required,
but that the AnyMedia ® shelf will retain ATM xDSL service on some ports. To avoid
alarms, you will need to log onto the AFM via the GSI to take the pack Out of Service
before it is physically removed from the shelf. If the existing configuration is
narrowband and ATM xDSL, you must log onto the COMDAC via the GSI or the
TLSI to edit the configuration. This will prevent an alarm from being issued via the
narrowband OAM&P interfaces. The ATM xDSL AP that was removed is then replaced
with a blank faceplate.

Removing ATM xDSL services from a shelf

This scenario assumes that the AnyMedia ® shelf will no longer be used for ATM xDSL
services. First remove the AFM and then the ATM xDSL APs. If the AnyMedia ® shelf
will still be used for narrowband services, you will need to log onto the COMDAC via
the GSI or TLSI terminal to edit the configuration. This will prevent an alarm from
being issued via the narrowband OAM&P interfaces. The AFM and the ATM xDSL
APs that were removed are replaced with blank faceplates.

Migrating from simplex to duplex AFM mode

Migration in a standalone shelf

The migration from simplex to duplex AFM mode depends on the AFM type used.
Migration with AFME3 or AFMDS3 installed
To migrate from simplex to duplex AFM mode on a standalone AnyMedia® shelf,
install the second AFM in slot 15 (AFM protection slot). Provision the shelf’s
protection mode as duplex using the GSI. Activate the SW running on AFM in slot 16
(preferred AFM slot) also on AFM in slot 15 (AFM protection slot) if not already
running by using the GSI. The database is automatically synchronized with that of the
other AFM in slot 16 (preferred AFM slot).
Install the coax splitters/combiners and install the associated cabling for both circuit
packs. The end-user service will be interrupted during this cabling operation.
Migration with AFMO installed
To migrate from simplex to duplex AFM mode on a standalone AnyMedia® shelf,
install the second AFM in slot 15 (AFM protection slot), and install the 995A cross
couple connector. If the system is to be provisioned in DBSF protection mode, install
the optical couplers. Provision the shelf’s protection mode as duplex, either in DBSF
protection mode or in Duplex 1+1 protection mode, using the GSI. Activate the SW
running on AFM in slot 16 (preferred AFM slot) also on AFM in slot 15 (AFM
protection slot) if not already running by using the GSI. The database is automatically
synchronized with that of the other AFM in slot 16 (preferred AFM slot).
If Duplex 1+1 protection mode is provisioned, a second STM-1/OC-3c feeder to/from
the ATM network will be used. Connect the Rx and Tx fibers of this new feeder from
the AFMO in slot 15 (AFM protection slot) to the ATM circuit pack in the ATM
switch or multiplexer. For more details see “Duplex 1+1 protection mode” (p. 6-181).
In DBSF protection mode install two optical couplers and connect the Tx cables of
both AFMs to one of them and the Rx cables to the other. Then connect the optical
couplers to the ATM circuit pack in the ATM switch or multiplexer. For more details
see “DBSF protection mode” (p. 6-180).

Migration in a Mainshelf daisy-chain

Migrating from simplex to duplex AFM mode (AFME3, AFMDS3 or AFMO) in an
AnyMedia ® shelf daisy-chain requires the appropriate steps described above for each
shelf of the daisy-chain. The order in which the shelves are migrated is not important.
However, in the AFME3 and in the AFMDS3 case as well as in the AFMO case when
provisioned in DBSF protection mode, each time the feeder cables are disconnected for
a given shelf, end user service is interrupted for the given shelf and all the other
shelves downstream from that shelf. In the case of the AFMO, when it is provisioned
in Duplex 1+1 protection mode, service is not affected.

Migrating from duplex to simplex AFM mode

Migration duplex to simplex in a standalone shelf

The migration from duplex to simplex AFM mode depends on the AFM type used.
Migration with AFME3 or AFMDS3 installed
To migrate from duplex to simplex AFM mode in a standalone AnyMedia ® shelf,
determine whether the AFM in slot 16 (preferred AFM slot) is the active AFM.
If it is, provision the shelf’s protection mode as simplex, otherwise perform a pack
protection switch using the GSI. Disconnect the cabling between port 1 of each AFM
and the coax splitter/combiner, then remove the splitter/combiner. Remove the AFM
from slot 15 (AFM protection slot) and reconnect the cabling between the AFM in slot
16 (preferred AFM slot) and the ATM network. The end-user service will be
interrupted during this cabling operation.
Migration with AFMO installed
To migrate from duplex to simplex AFM mode in a standalone AnyMedia® shelf,
determine whether the AFM in slot 16 (preferred AFM slot) is the active AFM. If it is
not, perform a pack protection switch using the GSI.
If the AFMO was provisioned in Duplex 1+1 protection mode, determine whether the
AFMO feeder connected to the AFMO in slot 16 (preferred AFM slot) is the active
feeder. If it is not, perform a feeder protection switch. Using the GSI, provision the
shelf’s protection mode as simplex. Disconnect the fiber between port 1 of the AFMO
in slot 15 (AFM protection slot) and the ATM switch or multiplexer. Remove the
AFMO from slot 15 (AFM protection slot). This migration is non-service affecting.
If the AFMO was provisioned in DBSF protection mode, disconnect the cabling
between port 1 of each AFMO and the optical couplers, then remove the optical
couplers. Remove the AFMO from slot 15 (AFM protection slot) and reconnect the
cabling between the AFM in slot 16 (preferred AFM slot) and the ATM network. The
end-user service will be interrupted during this cabling operation.

Migration in a Mainshelf daisy-chain

To migrate from duplex to simplex AFM mode (AFME3, AFMDS3 or AFMO) in a
Mainshelf daisy-chain, perform the appropriate steps above for each shelf in the
daisy-chain. The port 2 cabling operations are similar to those described above for port
1. The order in which the shelves are migrated is not important. However, in the
AFME3 and in the AFMDS3 case as well as in the AFMO case when provisioned in
DBSF protection mode, each time the feeder cables are disconnected for a given shelf,
end user service is interrupted for the given shelf and all the other shelves downstream
from that given shelf. In the case of the AFMO, when it is provisioned in Duplex 1+1
protection mode, service is not affected. However, when the fiber is disconnected from
the AFMO in slot 15 (AFM protection slot), the shelf at the other end of that fiber will
raise an alarm. When this latter shelf is migrated to simplex AFM mode, the alarm will
retire.
...................................................................................................................................................................................................................................
363-211-586 6-25
Issue 6, July 2007
System planning and engineering for ATM xDSL services

Migration from an ATM xDSL system to an IP system via

IP-AFM
...................................................................................................................................................................................................................................

Migration from ATM AFM to IP-AFM

The IP-AFM supports the migration of ATM xDSL services to IP while preserving APs
and shelves that are already in use. Note that this procedure is service-affecting.
Following steps are required for the migration scenario:
• Backup the database NVDS for ATM xDSL services on the ATM AFM
• Disconnect all cables from the ATM AFM
• Remove the ATM AFM(s) and insert the new IP-AFM(s) into the ATM AFM slots
• Perform a database restore from the NVDS on the IP-AFM via GSI
• Reconnect the cables and install the appropriate Ethernet uplink cables for the
IP-AFM
• Verify software load for the IP-AFM
• Provision the IP-AFM and save this new configuration to the NVDS.
The IP-AFM supports also the uplink protection. In this case a second IP-AFM is
required (active/standby) in an duplex mode configuration. The standby IP-AFM
provides the redundant link for protection.

ATM xDSL installation and connection

recommendations

Purpose
The description of the ATM xDSL service capabilities of the AnyMedia ® Access
System suggests a very flexible product within the AnyMedia® shelves. This section
presents some suggestions for deploying this service that consider system flexibility
and economic concerns.

Contents

Installation recommendations 6-28

Initial deployment with no ATM xDSL services 6-30
Growth situations 6-31
Cables and hardware 6-32
Large ATM xDSL deployments 6-33
Interoperability 6-34
Engineering narrowband to ADSL upgrade 6-35
Engineering for ADSL over ISDN 6-39
Engineering the BB ATM Operations Channel for shelves cascaded via 6-40
E1IMA APs
New installation concept 6-42
Engineering the LAN connection 6-45
BB ATM Operations Channel 6-50
ATM xDSL Port Numbering 6-52

Installation recommendations
...................................................................................................................................................................................................................................

Recommendations
The discussions in this section assume that the user is using the AnyMedia ® Access
System for narrowband services. To upgrade the AnyMedia ® Access System for ATM
xDSL services consider the following rules:
1. Any ATM xDSL AP in AnyMedia® shelves must be supported by an AFM pack on
the applicable AnyMedia ® Mainshelf. To get maximum value per line, the more
ATM xDSL APs supported by a single AFM, the lower the cost per line.
In the AnyMedia ® LAG 4300 Shelf, each of the two rows must be equipped with
an AFM because the BB subsystems in both rows are logically separated.
2. Daisychaining of AFM packs among several shelves does not require that every
adjacent shelf be daisy-chained. Provisioning for daisychaining between any two or
more AnyMedia ® Mainshelves in a rack is acceptable, and even can be
accomplished between racks. The figure below shows an example of adjacent
daisy-chained AnyMedia ® Mainshelves.
The AFME1 does not support daisychaining.
3. The first installed AFM must be connected to an ATM network, which may be at
the same site as the ATM xDSL equipped shelf, or may be transported to another
location over a transport system capable of supporting the feeder signal.
4. When ATM xDSL services are provided to a subscriber by an ADSL-only AP,
POTS for the subscriber is provided by a separate POTS-compatible,
narrowband-services-only AP. Therefore, the POTS lines that are connected to the
ATM ADSL lines do not need to be in the same shelf, or even in the same rack.
The same applies to ISDN APs.
5. When a combo pack is used, both POTS and ADSL are served by the same combo
pack. Combo packs do not need to be connected to a separate POTS AP.
6. It is assumed that the user is not willing to remove or rearrange other APs, nor
commit to expensive line and station transfers.
7. Using the new installation concept (NIC) as described in “New installation
concept” (p. 6-42) allows a flexible modification of the provided services without
changing the system cabling.
The figure below shows a daisy-chain interconnection of AnyMedia ® Mainshelves
(example with AnyMedia ® ETSI V5 Shelves).

AFM *
Application pack
Application pack
Application pack
Application pack
Application pack
Application pack

Application pack
Application pack
Application pack
Application pack
Application pack
Application pack
Application pack
Application pack
Application pack
TX-1 To ATM
Backbone
RX-1

TX-2

RX-2
1 2 1 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16

COM-1COM-2 CIU AP-1 AP-2 AP-3 AP-4 AP-5 AP-6 AP-7 AP-8 AP-9 AP-10 AP-11 AP-12 AP-13 AP-14 AP-15 AP-16

AFM *
Application pack
Application pack
Application pack
Application pack
Application pack
Application pack

Application pack
Application pack
Application pack
Application pack
Application pack
Application pack
Application pack
Application pack
Application pack

TX-1

RX-1

TX-2

RX-2
1 2 1 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16

COM-1COM-2 CIU AP-1 AP-2 AP-3 AP-4 AP-5 AP-6 AP-7 AP-8 AP-9 AP-10 AP-11 AP-12 AP-13 AP-14 AP-15 AP-16

* AFME3, AFMDS3, or AFMO

To
Next
Shelf

Initial deployment with no ATM xDSL services

Recommendations
The engineer should obtain a forecast of the expected number of ATM xDSL lines at
the remote terminal (RT) location for a standard planning interval, such as six months
or one year. Observe the most recently installed, lowest fill AnyMedia ® shelf. If there
are sufficient slots in that AnyMedia ® shelf to support the planned amount of ATM
xDSL lines, install an AFM in the preferred slot (and optionally also in the protection
slot). Then equip or reserve sufficient slots to provide ATM xDSL services for the
planning interval. The AFM(s) must also be connected to the ATM network perhaps via
an SDH multiplexer.
If the needed number of slots for ATM xDSL lines exceeds the current AnyMedia ®
shelf capacity, activate the next available, inactive AnyMedia ® shelf. The cost of this
activation is small since it requires turning on power and equipping the AnyMedia ®
Mainshelf with only an AFM pack (or optionally 2 AFM packs) and the needed
number of ATM xDSL APs. If this AnyMedia ® Mainshelf subsequently requires POTS
or other narrowband services, it must be equipped with the needed common units and
APs for those services.

Growth situations
...................................................................................................................................................................................................................................

Recommendations
Growth situations occur when the number of ATM xDSL lines on the AnyMedia ®
shelves is exceeded due to an incorrect low estimate of growth, or when the next
planning interval needs must be accommodated. See “ATM xDSL growth, degrowth
and migration scenarios” (p. 6-18) for further information.
In configurations first determine if there are still enough vacant slots on the working
AnyMedia ® Mainshelf to support the next planning interval needs of ATM xDSL APs.
If there are enough, install or reserve those slots for ATM xDSL lines.
If there are insufficient slots, check if there is sufficient space on any other operating
AnyMedia ® shelf in the same rack or cabinet to support this next planning interval
need for ATM xDSL APs. If there is space, and if the ATM network interface is
E3/DS3 or STM-1/OC-3c, install an AFME3/DS3 or AFMO pack in the preferred slot
of that AnyMedia ® Mainshelf (and optionally a second AFME3/DS3 or AFMO pack in
the protection slot) and daisy-chain to the initial AnyMedia ® Mainshelf with ATM
xDSL service.
Important! If the ATM network interface is E1, each shelf must be directly
connected to the ATM feeder.

Cables and hardware

Associated Hardware
Alcatel-Lucent provides cables and hardware to support daisychaining with different
lengths. Lightguide build-out (LBO) for AFMOs, splitters/combiners and optical
couplers for duplex AFM mode are also available from Alcatel-Lucent.
If no active AnyMedia ® shelves can accommodate the growth, a new shelf should be
put into service as described in “Initial deployment with no ATM xDSL services”
(p. 6-30). Also, it may be necessary to turn up a new shelf in an adjacent rack or
cabinet to accommodate growth.
A varied set of cables are provided for connection to the ATM network from the AFM.
For ordering information see the Ordering Guide 363-211-144.

Large ATM xDSL deployments

Recommendations
In situations where large numbers of ATM xDSL lines are expected, entire AnyMedia ®
shelves or racks should be committed to supporting ATM xDSL services only using
ATM xDSL APs. This is preferred since full AnyMedia ®shelves or racks of ATM xDSL
APs do not require AnyMedia ® Access System narrowband common equipment, and
the cost of the AFM packs per ATM xDSL line is minimized. Records and cabling are
also simplified for more efficient deployment of ATM xDSL services.

Interoperability
...................................................................................................................................................................................................................................

Recommendations
Refer to Customer Technical Support for the latest information on ATM xDSL CPE
modems that are currently supported.

Engineering narrowband to ADSL upgrade

NB to ADSL upgrade
Any NB subscriber from any system can be upgraded to ADSL service via a
cross-connect on the system side of a main distribution frame (MDF) or feeder
distribution interface (FDI) to any available ADSL interface. The external connection is
shown in “NB to ADSL upgrade” (p. 6-36).
The following figure shows the upgrade connections for a NB-only subscriber line to
ADSL.

Application Pack NB Pairs ADSL + NB Pairs ADSL Pairs

LPA416, LPA417 2, 4, 6, 8, 10, 12, 14, 16, 1, 3, 5, 7, 9, 11, 13, 15,
18, 20, 22, 24, 26, 28, 30, 17, 19, 21, 23, 25, 27, 29,
32 31
LPA432(1), LPA434( 2) — — 1 through 32

Notes:
1. For engineering information about how to upgrade POTS service to ADSL using the the POTSZF
LPZ110 and the ADSL32p LPA432 see “Engineering POTS + ADSL service with LPZ110 and LPA432
APs” (p. 5-36).
2. An external splitter is required, see the wiring diagram for the LPA434.

For the ADSL upgrade remove/connect on the FDI or MDF as described:

• Remove the original NB-only connection between the subscriber line and the NB
interface
• Connect the subscriber line to any available ADSL interface
• Connect the referring NB interface of the ADSL AP to a NB interface on a NB-like
AP.
Important! Ensure there is a protector in the jack of the protector block for the
designated subscriber loop as primary protection.

NB to ADSL upgrade using a combo pack (LPA832)

Any NB subscriber from any system can be easily upgraded to ADSL service via a
combo pack LPA832 which supports POTS and ADSL service on the same subscriber
lines. As shown in the following figure, the existing cabling can be reused, no
additional cabling is required.
The following figure shows the upgrade connections for a NB-only subscriber line to
ADSL via a combo pack LPA832.

Protector Block
NB
2 2
Line
Interface Subscriber line
carrying NB-only services
AnyMedia Access System

FDI
or MDF

LPA832
Protector Block
POTS
2 2
and/or
ADSL Subscriber line
carrying NB and/or ADSL services
AnyMedia Access System

Existing cabling can be reused

Important! The combo pack has to be provisioned from the NB subsystem and
from the BB subsystem. When provisioning the combo pack make sure that the
ADSL port for a subscriber line is provisioned in the BB subsystem exactly to the
same port as the POTS port in the NB subsystem.
Important! Ensure there is a protector in the jack of the protector block for the
designated subscriber loop as primary protection.

Engineering for ADSL over ISDN

Recommendations
Subscriber lines that connect to an ADSL4i or ADSL16i (ADSL over ISDN) AP should
not be in the same binder group with subscriber lines that connect to an ADSL over
POTS AP, as this configuration may cause spectral interference. However, ADSL4i APs
or ADSL16i APs may reside on the same AnyMedia ® shelf as ADSL over POTS APs.
This rule applies both to the cabling between the MDF and the AnyMedia ® shelves,
and to the outside plant (OSP) feeder cable.
This binder group restriction does not apply to narrowband APs (that means, supported
narrowband APs may reside in the same binder group with any ADSL AP, including an
ADSL over ISDN AP).

Binder group restrictions for the OSP feeder cable

A single binder group in the OSP feeder cable may not contain customer lines that
connect to both an ADSL over ISDN AP and to an ADSL over POTS AP.
Important! It is permissible for a single binder group to contain both customer
lines providing combined ADSL and ISDN (or ADSL and POTS) service, and
customer lines providing only narrowband services (i.e., POTS or ISDN only).

Engineering the BB ATM Operations Channel for shelves

cascaded via E1IMA APs
...................................................................................................................................................................................................................................

Overview
This section discusses the engineering rules for the BB ATM Operations Channel for a
shelf with an AFME1 included that is cascaded via an E1 line to the E1IMA AP in a
host shelf.
The operator is responsible for provisioning the cross-connections in the host shelf and
cross-connections in the cascaded shelf consistently regarding QoS class, traffic profile
etc.

Traffic parameters
For provisioning the cross-connection for the BB ATM Operations Channel in the host
shelf the operator has to use traffic parameters as defined in the following table:

Traffic Parameter Value Units

Service Category rt-vbr enum value
PCR upstr./downstr. 500 cells/s
SCR upstr./downstr. 450 cells/s
MBS upstr./downstr. 32 cells
CDVT for PCR 1330 msec
CDVT for SCR 1330 msec
-05
CLR 10 n/a
Cell Loss Priority clp0 enum value
Cell tagging false TruthValue
AAL5 frame discard true TruthValue

Engineering options
There are 3 options to configure the BB ATM Operations Channel in a host shelf:
• Provision a user VCC in the host shelf within a shelfVP (rt-VBR) with VCI in the
range of 33 to 64 by using the traffic parameters from the table above and
provision an OAM&P; VP in the cascaded shelf with VPI/VCI equal to the
VPI/VCI of the connection in the host shelf.
• Provision a user VPC (rt-VBR) in the host shelf and provision an BB ATM
Operations Channel in a shelfVP (rt-VBR) in the cascaded shelf with VPI equal to
the user VPI of the connection in the host shelf.
In this case the BB ATM Operations Channel is expected to be in VC 32 of the
user VPC in the host shelf and hence in VC 32 of the shelfVP in the cascaded
shelf. The traffic profile of the provisioned user VPC in the host shelf must
consider the traffic parameters necessary for the BB ATM Operations Channel for
the cascaded shelf.
• Provision a user VPC (rt-VBR) in the host shelf and provision an BB ATM
Operations Channel in an OAM&P; VP (rt-VBR) in the cascaded shelf with VPI
equal to the user VPI of the connection in the host shelf.
In this case the BB ATM Operations Channel is expected to be in VCI range 32 to
64 of the user VPC in the host shelf and hence in VCI range 32 to 64 of the
OAM&P; VP in the cascaded shelf. The traffic profile of the provisioned user VPC
in the host shelf must consider the traffic parameters necessary for the BB ATM
Operations Channel for the cascaded shelf.

New installation concept

Concept
The new installation concept (NIC) makes use of small module containers on the MDF
instead of disconnect terminal blocks. The module containers are equipped with very
compact application specific modules which are connected via system cables to the
AnyMedia ® Access System.

Modules
The height of the modules complies with that of conventional disconnect terminal
blocks. Depending on the service, the modules are designed either as connect-through
modules or include most modern splitter technology. Therefore there is no need to
install external splitter shelves.
One module container can support 32 subscribers. Depending on the service, it can be
equipped with up to 4 modules. The modules are designed for 8 subscribers each. Each
module container is connected on the rear side to the AnyMedia ® Access System. If
splitter modules are used, the NB service is fed to the left side.
Connect-through modules directly connect the system cabling to the subscriber lines
while splitter modules combine ADSL and NB services on the subscriber line.
Note that connect-through modules may be replaced by common disconnect terminal
blocks. In this case the flexibility of the new cabling concept gets lost.
The following figure shows a module container with four modules.

The following figure shows the use of different modules for different service
applications in NIC. For NB services only connect-through modules are used.
...................................................................................................................................................................................................................................
6-42 363-211-586
Issue 6, July 2007
System planning and engineering for ATM xDSL services New installation concept

NB-only Connect-through
module

NB
NB Subscriber line
NB AP
Applicable for all NB APs (including the combo pack
P32A32 LPA832
MDF

ATM SHDSL, SDSL POTS and ADSL via combo pack

Connect-through Connect-through
module module
POTS+ADSL
SHDSL, SDSL POTS + ADSL
Subscriber line LPA832 Subscriber line
BB AP
16 ports

MDF MDF

Applicable for ATM SHDSL and SDSL packs Applicable for LPA832

NB via ADSL packs with splitters POTS over ADSL via LPA432/LPZ110
Connect-through
Connect-through
module module

NB + ADSL NB + ADSL POTS + ADSL

ADSL Subscriber line
Subscriber line LPA432 32 ports
BB AP

NB
Splitters on board NB Splitters on board POTS

Any POTS
LPZ110
NB AP 32 ports
NB
MDF MDF
Applicable for all ADSL APs Applicable for LPA432 combined with LPZ110
except LPA432 and LPA434

POTS over ADSL via LPA432 ADSL over ISDN via LPA434
Splitter module Splitter module

POTS + ADSL ISDN + ADSL

ADSL Subscriber line ADSL Subscriber line
LPA432 S LPA434 32 ports S
32 ports

No splitters on board POTS No splitters on board ISDN

Any POTS Any ISDN

POTS ISDN
AP AP

MDF MDF
Applicable for LPA432 combined with any POTS pack Applicable for LPA434

Change of services
Where the initial installation has been done according to NIC, the service provided to a
certain port on the AnyMedia ® Access System can be changed quickly at a later point
of time.

When the service requirements change, the modules can be easily upgraded while the
cabling to the MDF remains the same. So the required new service can be provided
with a minimized installation effort.

Engineering the LAN connection

LAN connection for ATM xDSL services

The 10BaseT interface for ATM xDSL services is accessed via an RJ-45 connector
located on the AFM. The pinout of the RJ-45 connector is given in the table below.
This interface can be used for local and remote access.
The following table shows the signals on the RJ-45 connector.

RJ-45 Pin Signal

1 Transmit Data +
2 Transmit Data -
3 Receive Data +
6 Receive Data -

Connection configurations for a single BB subsystem

There are two configurations of LAN connections that can be made to the AFM(s) on
a single BB subsystem: one is to a direct connection and the other is through an
Ethernet hub. Use the direct connection when you are accessing the AnyMedia ® shelf
with a local PC. Otherwise, use the Ethernet hub to access the AnyMedia ® shelf
through a remote OS.
The direct connection must use a crossover cable, which connects the transmit signal to
the receive pins in both directions. The connection to an Ethernet hub uses a
straight-through cable.
When AFMs are used in duplex mode on a single shelf, the 10BaseT interfaces are
joined at a hub (for remote access) or by a special Y-assembly (for local access). In
either case, both AFMs use the same IP address. An alternative to using the Y-assembly
in duplex mode is to use the simplex 10BaseT port cable and connect this cable to the
active AFM. In this case, if the AFM executes a protection switch, the cable has to be
moved to the newly active AFM.
Two examples are given below to illustrate the difference between the two types of
cabling.
• Example 1 illustrates the wiring for a crossover cable used with a direct
connection.
• Example 2 describes the wiring for a straight-through cable, such as would be used
when making a permanent connection between the AFM and a 10BaseT Ethernet
hub.
Example 1. Direct connection for ATM xDSL services
In this example, a temporary local connection is to be made between a PC/GSI and a
single AFM in simplex mode to carry out initial turn-up of the shelf for ATM xDSL
services.
...................................................................................................................................................................................................................................
363-211-586 6-45
Issue 6, July 2007
System planning and engineering for ATM xDSL services Engineering the LAN connection

A crossover 10BaseT cable is used to connect the 10BaseT RJ-45 LAN port of the
PC/GSI to the AFM RJ-45 faceplate connector.
The signaling on the crossover 10BaseT cable terminated with RJ-45 connectors on
both ends must be as shown in the following table.

RJ-45 Pin Signal Signal RJ-45 Pin

1 Transmit Data + Receive Data + 3
2 Transmit Data - Receive Data - 6
3 Receive Data + Transmit Data + 1
6 Receive Data - Transmit Data - 2

This is a standard cable and can be ordered from commercial catalogs. Part numbers
for the crossover cables can be found in the AnyMedia ® Access System, Ordering
Guide 363-211-144.
Example 2. LAN connection for ATM xDSL services
In this example, the AnyMedia ® Mainshelf turn-up has been completed, and a
permanent connection is to be made between a Tier 2 NMS or Navis ™ AnyMedia ®
Element Management System (NAM) and the AFM. (This example assumes the AFM
is in simplex mode.) To make the permanent connection, the AFM will be connected to
a 10BaseT Ethernet hub.
Note: When AFMs are used in duplex mode on a single shelf, the 10BaseT interfaces
are joined at a hub (for remote access) or by a special Y-assembly (for local access). In
either case, both AFMs use the same IP address. An alternative to using the Y-assembly
in duplex mode is to use the simplex 10BaseT port cable and connect this cable to the
active AFM. In this case, if the AFM executes a protection switch, the cable has to be
moved to the newly active AFM.).
A straight-through 10BaseT cable with RJ-45 connectors on both ends is used to make
this connection.
The signaling on the straight-through 10BaseT cable terminated with RJ-45 connectors
on both ends must be as shown in the following table.

RJ-45 Plug Signal Signal RJ-45 Plug

1 Transmit Data + Transmit Data + 1
2 Transmit Data - Transmit Data - 2
3 Receive Data + Receive Data + 3
6 Receive Data - Receive Data - 6

This is a standard cable and can be ordered from commercial catalogs. Part numbers
for the straight-through cables can be found in the AnyMedia ® Access System,
Ordering Guide 363-211-144.
....................................................................................................................................................................................................................................
6-46 363-211-586
Issue 6, July 2007
System planning and engineering for ATM xDSL services Engineering the LAN connection

Connection configuration to both BB subsystems in an AnyMedia ® LAG 4300 Shelf

The LAN connection to the AFMs in both BB subsystems of an AnyMedia ® LAG
4300 Shelf is made through an Ethernet hub, regardless whether the AFMs are used in
simplex or in duplex mode. When AFMs are used in duplex mode both AFMs in one
BB subsystem use the same IP address.
The example below illustrates the wiring to the LAN ports of the NB subsystem and
the two BB subsystems which may be included in an AnyMedia ® LAG 4300 Shelf.
Straight-through cables with RJ-45 connectors on both ends are used when making the
connection between the AFM(s), the COMDAC(s) and a 10BaseT Ethernet hub.
Example: LAN connection to all subsystems in an AnyMedia ® LAG 4300 Shelf
(two BB subsystems and one NB subsystem)
The following figure shows a wiring example for the LAN connections in an
AnyMedia ® LAG 4300 Shelf.

The signaling on the straight-through 10BaseT cable terminated with RJ-45 connectors
on both ends must be as shown in the following table.

RJ-45 Plug Signal Signal RJ-45 Plug

1 Transmit Data + Transmit Data + 1
2 Transmit Data - Transmit Data - 2
3 Receive Data + Receive Data + 3
6 Receive Data - Receive Data - 6

This is a standard cable and can be ordered from commercial catalogs. Part numbers
for the straight-through cables can be found in the AnyMedia ® Access System,
Ordering Guide 363-211-144.

Hub connection
The hub in a 10BaseT network functions as a multiport repeater (that is, it receives and
regenerates signals received from any attached device). The hub is transparent to the IP
addresses and creates a small star-type local area network of ATM xDSL systems,
narrowband systems, and the GSI.

BB ATM Operations Channel

Overview
The BB ATM Operations Channel should be provisioned as a AAL5 PVC through the
ATM network. The traffic parameters for the connection should be provisioned as:

Parameter Value
Service Category: rt-VBR.3
Peak Cell Rate up/down: 500 cells/sec (≈ 212 kbps)
Sustained Cell Rate up/down: 450 cells/sec (≈ 191 kbps)
Maximum Burst Size: 32 cells
Cell Loss Ratio: 10 -5
PCR CDVT: as high as possible, (maximum value which is supported
by the ATM nodes of the transport network); min. 50 ms
SCR CDVT: as high as possible, (maximum value which is supported
by the ATM nodes of the transport network); min. 50 ms
Cell Tagging: disabled
AAL5 frame discard: enabled (it may not be possible to enable AAL5 frame
discard in conjunction with policing disabled. In this case
leave AAL5 frame discard disabled)

Example for a network setup

The following figure shows an example for a network setup.

For a description of how operations, administration, and maintenance messages may be

sent to and from the COMDAC on the AnyMedia ® shelf via the BB ATM Operations
Channel, see “Using the BB ATM Operations Channel to transport NB OAM&P”
(p. 5-38).

ATM xDSL Port Numbering

Overview
The GSI uses port numbers for many activities related to ATM xDSL ports. These
activities include
• ATM xDSL port provisioning
• ATM cross-connect provisioning
• Status information retrieval
• Alarm and event retrieval.
Up to 32 ports can be provisioned for any given slot; however, if a given ATM xDSL
AP is installed in a slot that has a port provisioned that the given AP does not have,
then the operational state of the port will be MEA (see Service states on page 11-73).
For example, suppose slot 4 of the AnyMedia ® ETSI V5 Shelf were provisioned for a
pack type of ADSL and slot 4, Port 27 were provisioned for service. Then, if an
ADSL16p LPA416 AP was installed in slot 4, the operational state of slot 4, port 27
would be MEA, because port 27 is not connected on the ADSL16p LPA416.

Alternating and sequential pinouts

The following ATM xDSL APs are alternating pinout APs:
• ADSL16p LPA416
• ADSL16i LPA417.
For this type of AP, the ATM xDSL signal appears on alternating a/b pairs on the
faceplate connector, starting with Pair 1 (that is, Pairs 1, 3, 5, 7, and so forth). The
even-numbered pairs are for the connection to the incoming POTS or ISDN signal.
The following ATM xDSL APs are sequential pinout xDSL APs:
• SHDSL16
• ADSL32p
• ADSL32i
• P32A32.
For this type of AP, the xDSL signal appears on sequential a/b pairs on the faceplate
connector, starting with Pair 1 (that is, Pairs 1, 2, 3, 4, and so forth).

Distribution port numbering modes

Two distribution port numbering modes are provided. These modes determine what
port numbers are used for the GSI activities listed above. The modes are
• Physical: A port number entry on the GSI corresponds to the identification number
of the a/b pair on the AP faceplate connector that provides the service. This mode
is similar to narrowband operations in which the pack pair number is part of the
TL1 AID for a drop.
• Logical: port entries on the GSI are numbered contiguously from 1 to n in the
order in which they appear on the AP faceplate connector. Earlier releases of the
AnyMedia ® Access System ATM xDSL port operations used this mode.
In the GSI, the distribution port numbering mode being used is shown in the System
Information section of the Main Shelf tab. The Main Shelf tab is accessed in the GSI
by selecting Provisioning → System Turnup → Mainshelf → Data.
For alternating pinout ATM xDSL APs, the GSI port number entries that correspond to
the a/b pairs that provide the service depend on which distribution port numbering
mode is in effect. This behavior is caused by the skipped a/b pairs. On the other hand,
for sequential pinout ATM xDSL APs, the GSI port number entries that correspond to
the a/b pairs that provide the service are the same regardless of the distribution port
numbering mode.
The default setting of the distribution port numbering mode is physical. However, if
the AFM software is updated from a release that provides only the logical distribution
port numbering mode to a release that provides both modes, then the setting will
automatically be set to logical. That way, the mode does not change as a result of the
software-update activity.
The distribution port numbering mode can be changed during system turn up when
both of the following conditions are true:
• The shelf is provisioned as simplex
• No ATM xDSL packs have been provisioned yet.
The distribution port numbering mode cannot be changed under any other conditions.

Examples
An example using the ADSL8p, an alternating pinout AP, is given in the following
table.

AP a/b Pair Number Port Number Entered or Observed on GSI

Physical Mode Logical Mode
1 1 1
3 3 2
5 5 3
7 7 4

AP a/b Pair Number Port Number Entered or Observed on GSI

Physical Mode Logical Mode
9 9 5
11 11 6
13 13 7
15 15 8

So, if, for example, ADSL service (and POTS if applicable) is needed on AP pair 5 on
an ADSL8p, then the port number used on the GSI for each mode is:
• Physical: Port 5,
• Logical: Port 3.
However, for the ADSL32p LPA432, ADSL32i LPA434, P32A32 LPA832, SHDSL16
LPS702 AP, which are sequential pinout APs, the a/b pairs that provide service are
pairs 1, 2, 3, and so forth. In this case, the port number used on the GSI is the same
regardless of the distribution port numbering mode.
The following table shows as an example the SHDSL16 Port Numbering (sequential
pinout).

AP a/b Pair Number Port Number Entered or Observed on GSI

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

Quality of Service Provisioning

Purpose
Provisioning the AnyMedia ® Access System for quality of service (QoS) must be
performed at the shelf level and for each connection. Port profiles that can be applied
to many connections also need to be provisioned. This section discusses how
provisioning affects QoS operation.
For QoS commitments to be met, the end-to-end network must be provisioned
consistently.
Note
A modem that is not provisioned for rate-pacing is likely to send cells that may be
noncompliant for CBR, rt-VBR, and nrt-VBR connections.

Contents

Connection Admission Control algorithm 6-56

Shelf provisioning for QoS 6-57
Special considerations for a daisy chain 6-62
xDSL transmission profile effect on QoS 6-64
ATM traffic profile provisioning for QoS 6-65
Cross-connect provisioning 6-67
Overbooking factor 6-69
Congestion management schemes 6-70
Traffic shaping - Policing - Scheduling 6-72

Connection Admission Control algorithm

Parameters used
The CAC function of the BB subsystem uses the following parameters:
• Shelf Peak Cell Rate (Shelf PCR)
• Admissible Bandwidth
• Guaranteed Bandwidth
• Minimum line bandwidth for xDSL ports
• Traffic Parameters for CBR
– Peak Cell Rate (PCR)
– Cell Loss Ratio (CLR)
• Traffic Parameters for rt-VBR and nrt-VBR
– Sustainable Cell Rate (SCR)
– Maximum Burst Size (MBS)
– Cell Loss Ratio (CLR)
• Overbooking factor
• Buffer size allocated to rt-VBR and nrt-VBR traffic.

CAC initialization
The CAC algorithm runs when:
• A new connection is established
• Shelf PCR is modified
• The overbooking factor is modified
• A CLR value is modified
• An admissible bandwidth is modified
• A guaranteed bandwidth is modified.
The CAC algorithm uses two mathematical approximations to calculate the required
effective bandwidth to support the QoS objective of a connection. One approximation
assumes that all connections in the system share the same traffic characteristics as the
connection to be admitted. The other approximation uses the source traffic
characteristics of the other actual connections (the characteristics of which may vary
from connection to connection) as well as the traffic characteristics of the connection
to be admitted. The CAC uses the lesser of these two approximations to determine the
bandwidth required to ensure the QoS objectives of a connection.
Of the two schemes, the former approximation gives a more conservative effective
bandwidth calculation. General capacity planning tools may use only linear algorithms
to approximate bandwidth requirements. Therefore, as the system is populated with
new connections, the GSI may show more free effective bandwidth than was calculated
using a planning tool.

Shelf provisioning for QoS

Provisionable parameters
The following parameters need to be provisioned when turning up a shelf or when
converting from an earlier software release.
• Shelf peak cell rate (PCR)
• Shelf overbooking factor
• Admissible bandwidth per service category
• Guaranteed bandwidth per service category (except UBR service) in the upstream
direction
• Cell loss ratio.

Shelf peak cell rate (PCR)

The shelf peak cell rate (PCR) is the maximum bandwidth, in cells per second, that a
shelf can guarantee and is used in determining whether a new connection can be
admitted to the shelf. There is an upstream Shelf PCR value and a downstream Shelf
PCR value. In a single shelf system, the default upstream and downstream Shelf PCR
values correspond to the full upstream and downstream bandwidth of the feeder
interface to the ATM network. The AnyMedia ® Access System uses the Shelf PCR
value when deciding whether to accept a connection with a service category of CBR,
rt-VBR, or nrt-VBR. (Such a calculation is not made for the UBR service category.)
When the Shelf PCR (upstream or downstream) is lower than the feeder bandwidth, the
remaining bandwidth can be used by connections transporting UBR traffic. See
“Special considerations for a daisy chain” (p. 6-62) for additional information when
provisioning a shelf for a daisy chain.
The following discussion applies to IMA feeders.
The system supports Shelf PCR values according to “Maximum traffic for an E1
feeder/IMA group” (p. 6-12), which shows the maximum supportable Shelf PCR values
depending on the number and the configuration of the IMA links, and the supportable
Shelf PCR of the single UNI feeder. The system rejects requests for setting parameters
outside these ranges.
The provisioned Shelf PCR value should always be changed by the operator
corresponding to the new number of links whenever a IMA link is added or deleted
from the group or when a switch between UNI/IMA mode is performed.
Whenever the physical bandwidth is changed (adding/deleting IMA links to/from the
IMA group or switching between IMA/UNI mode) the system checks the provisioned
Shelf PCR to the value corresponding to the new configuration. It might reject the
changes if the provisioned value is outside the maximum supportable value.

Shelf overbooking factor

The shelf overbooking factor is a kind of concentration in the traditional sense. This
factor divides the effective bandwidth needed by a connection when the CAC
determines whether a new connection can be admitted to the shelf. Separate factors
apply to the CBR, rt-VBR, and nrt-VBR service categories.
At present, UBR connections are not considered by the CAC, which also means that,
in calculations concerning network interface aggregate effective bandwidth, UBR
connections are not taken into account.
To determine whether to admit a CBR connection, CAC compares the PCR of the
connection to the shelf-level parameters of the shelf PCR and the overbooking factor.
(An example of how the shelf overbooking factor functions is as follows: when the
overbooking factor for CBR is 2 and only CBR service is provided by the shelf, CBR
connections will be accepted until the total bandwidth required by these connections
exceeds twice the shelf PCR.)
To determine whether to admit an rt-VBR or nrt-VBR connection, CAC checks
whether the effective bandwidth (which depends on the service category and the
overbooking factor of that service category) of the connection exceeds the shelf PCR.
Effective bandwidth equals the bandwidth resources required to guarantee QoS for the
connection.
The difference in the CAC calculations for CBR connections and rt-VBR and nrt-VBR
connections is that CAC uses the effective bandwidth for rt-VBR and nrt-VBR instead
of the PCR. The effective bandwidth for rt-VBR and nrt-VBR connections depends on
three connection parameters: PCR, SCR, and MBS.
The larger the shelf overbooking factor, the better the network is utilized, but the
greater the risk of congestion, thereby degrading QoS. The values selected for the
overbooking factor may need to be adjusted after monitoring the ATM traffic statistics.
If congestion is being encountered too frequently, the overbooking factor may need to
be reduced. The setting range for the overbooking factor is given in “Overbooking
factor” (p. 6-69)

Admissible bandwidth
Admissible bandwidth per service category (except UBR service) in the upstream and
downstream direction.
The admissible bandwidth is the amount of bandwidth allocated to a service category
minus the bandwidth reserved for the BB ATM operations channel. Admissible
bandwidth can be specified independently for the upstream direction and the
downstream direction for each service category except UBR.
The sum of the effective bandwidths allocated to all connections supported by a service
category, divided by the overbooking factor of that service category, must not exceed
the admissible bandwidth of that service category.

Note that the sum of all admissible bandwidths may exceed the Shelf PCR, but
connection setup will only be allowed until the Shelf PCR minus the BB ATM
Operations Channel bandwidth is reached.

Guaranteed bandwidth
Guaranteed bandwidth per service category (except UBR service) in the upstream
direction is the portion of the feeder throughput (feeder bandwidth) made available to a
service category to be used during periods of sustained congestion. Guaranteed
bandwidth is explicitly specified for CBR, rt-VBR and nrt-VBR by means of
provisioning the weights for the weighted round robin (WRR) scheduler. The excess
feeder bandwidth not allocated across the mentioned three service categories is
assigned to UBR service category by the AFM. Once the WRR is configured it will
guarantee bandwidth for the service categories according to the specified weights. See
“Values provisioned for Cell Loss Priority and Cell Tagging” (p. 6-66) for a description
of how the WRR scheduler is configured to guarantee bandwidth across the service
categories. Guaranteed bandwidth is not applicable for an AFME1.

Cell loss ratio (CLR)

Cell loss ratio is the ratio of the number of cells lost to the total number of cells sent
in a given interval. The CLR parameter is the value the network agrees to offer as an
objective over the lifetime of the connection. The CLR value is specified per service
category at the time the shelf is turned up. The CAC algorithm will accept or reject
connections based on the CLR guarantees and the system resources available at the
time of the connection attempt. Therefore, changing CLR values requires reevaluation
of the system resources to support QoS guarantees for the existing connections. If the
CLR is to be changed to a smaller value, it is possible that all existing connections
may not be supported with the new CLR guarantees. It is recommended that the CLR
value not be changed once it has been provisioned. The customer traffic engineering
strategy should be to select an optimum CLR value for the planned customer
applications.
The following table shows the setting range for the CLR.

Parameter Service Setting ranges

Class
Cell Loss Ratio (CLR) rt-VBR, 10-9 to 10-1
nrt-VBR
CBR Fixed to 10 -9

In addition, when upgrading from a software release that only supports UBR to a
release that supports multiple service categories, it may be desirable to delete an
existing BB ATM Operations Channel that was UBR service category and provision a
new one that is rt-VBR service category. This gives some QoS guarantees to operations
commands and responses. As with any connection, the end-to-end connection must be
provisioned consistently through the entire network.
....................................................................................................................................................................................................................................
363-211-586 6-59
Issue 6, July 2007
System planning and engineering for ATM xDSL services Shelf provisioning for QoS

Other (not provisionable) parameters

Cell Transfer Delay (CTD) and Cell Delay Variation (CDV) are end-to-end connection
parameters. Each network element along the path of an end-to-end connection
contributes to the CTD and CDV.
• The CTD contribution of the AnyMedia ® Access System to an end-to-end
connection is fixed by the underlying hardware architecture. CTD within the
AnyMedia ® Access System is about 100 microseconds.
• CDV is caused by multiplexing, when a cell from a particular connection is
delayed while cells from other connections are being inserted at the output of the
multiplexer. As a result, cell inter-arrival times at the receiving end of a connection
will fluctuate randomly.

Retrievable information on admitted bandwidth

To support QoS provisioning at the GSI admitted bandwidth (i.e., aggregate used
effective bandwidth) and free bandwidth can be retrieved for several collection points.
The following information is retrievable on demand to indicate admitted bandwidth for
each direction of transmission:
• Total aggregate bandwidth divided by the overbooking factor at the network
interface for all provisioned connections.
The BB ATM Operations Channel is a pre-allocated connection and is not regarded
in this count. Also bandwidth which is used for UBR connections is not included in
the aggregate effective bandwidth because UBR is not regarded by the CAC.
• Effective bandwidth allocated for the BB ATM Operations Channel.
• The sum of the aggregate effective bandwidths divided by the overbooking factor
for all provisioned connections at the network interface for each Shelf VPC. The
ATM operations channel is displayed as a separate entry even if included as part of
a Shelf VPC. For Shelf VPCs of service category UBR the aggregate effective
bandwidth is uncommitted bandwidth.
• The sum of the aggregate effective bandwidths divided by the overbooking factor
of all its provisioned connections at the network interface for each local VP. For
CBR, rt-VBR and nrt-VBR VPs the aggregate effective bandwidth is named
’Admitted Bandwidth’ on the GSI, for UBR VPs the term ’Uncommitted
Bandwidth’ is used.
• The sum of the aggregate effective bandwidths divided by the overbooking factor
for all its provisioned connections at the network interface for all its service
categories. For CBR, rt-VBR and nrt-VBR counts the term ’Admitted Bandwidth’
is used on the GSI, UBR counts are depicted as ’Uncommitted Bandwidth’.
The BB ATM Operations Channel is a pre-allocated connection and is not regarded
in this count.
• The sum of the aggregate effective bandwidths for all its provisioned connections at
a port. The bandwidth which is used for UBR connections is not included in the
aggregate effective bandwidth because UBR is not regarded by the CAC. But the
overbooking factor is considered in the displayed effective bandwidth.

Retrievable information on free bandwidth

The following information is retrievable on demand to indicate free, (i.e. unused)
bandwidth for each direction of transmission:
• Free bandwidth at the network interface. The bandwidth for the BB ATM
Operations Channel is considered in the displayed effective bandwidth The free
bandwidth is calculated by subtracting the bandwidth allocated to the BB ATM
Operations Channel and allocated to provisioned connections from the Shelf PCR.
• Free bandwidth of a subscriber interface. The free bandwidth is calculated by
subtracting the effective bandwidth divided by the overbooking factor for all
provisioned connections at the subscriber interface from the provisioned minimum
transmission rate of this subscriber interface.

Special considerations for a daisy chain

QoS provisioning for a daisy chain

Following are additional considerations to be made when provisioning a daisy chain:
• In a daisy chain set, the sum of the Shelf PCRs for all the shelves must be no
greater than the maximum allowed PCR value (which equals the full bandwidth of
the feeder interface to the ATM network). The Shelf PCRs do not have to be
evenly divided among the shelves in a daisy chain; for each shelf, the PCR depends
on such factors as the number of subscribers and their requested traffic. As for a
single shelf, the remaining bandwidth can be used by UBR traffic.
• For all shelves in a daisy chain, the CLR parameters must be provisioned so that
the value provisioned for any individual shelf equals the value provisioned for each
of the other shelves.
• Every VP used in a daisy chain must be provisioned on every shelf in the daisy
chain. The VP identifier, service category, and VP type are needed. This is to
ensure proper handling of the different service categories as well as to prevent the
same VP from being cross-connected on more than one shelf.
VPs from other shelves are provisioned as follows:
– From shelves closer to the network interface, each VP is provisioned as VP type
Upstream Vp
– On shelves farther from the network interface, each VP is provisioned as VP
type Downstream Vp.
An example of the provisioning of VPs on every shelf in a daisy chain is shown in the
following figure.

xDSL transmission profile effect on QoS

Minimum bit rate

The minimum bit rate (upstream and downstream) specified in the xDSL transmission
profile (see “Default values for ATM xDSL system provisioning parameters” (p. 6-114)
) is the minimum rate at which the xDSL link will train. The customer loop
qualification tests should give a good indication of the value to be selected for this
parameter.
This minimum bit rate is used in determining whether a new connection can be
admitted to the shelf. For a CBR connection, the minimum bit rate must be able to
support the PCR of the connection. For an rt-VBR or nrt-VBR connection, the
minimum bit rate in the upstream direction must be able to support the upstream
effective bandwidth, and the minimum bit rate in the downstream direction must be
able to support the downstream SCR of the connection. If the minimum bit rate is less
than the connection requires, the connection is refused. Note that the profile may be
accepted by the system when it is created, but a connection using the profile may be
rejected. If multiple connections are provisioned on a port, the sum of the PCRs (for
CBR) and the SCRs (for rt-VBR and nrt-VBR) must be supported by the minimum bit
rate. UBR connections are not affected.
To compare the minimum bit rate to PCR or SCR, multiply the minimum bit rate in
kbits per second (kbps) by 1000/(53×8) to convert to cells per second (cps).

xDSL transmission profile provisioning

A transmission profile is applied to a port during port provisioning. The parameters in
the transmission profile must be chosen to be compatible with the planned service and
the modem to be used.
The built-in transmission profiles have been provided to serve as templates for creating
custom profiles that meet the required service needs and match the modem to be used.
Even for UBR service, a particular modem may operate better with a custom
transmission profile than with one of the built-in profiles.
Important! Once a transmission profile is used in making a cross-connect, it
cannot be edited. When a change is needed, it is recommended that a new
transmission profile be defined and a new cross-connect be created.
Important! Starting with R1.17.1U3 the minimum bit rate defined in the ADSL
transmission profiles has to be at least 64 kbps. Already existing transmission
profiles with a minimum bit rate of 32 kbps are still allowed for assignments to a
port but any modification in the profile will not be allowed till the minimum bit
rate is modified to the new introduced restriction of 64 kbps.

ATM traffic profile provisioning for QoS

Background
ATM traffic profiles can be provisioned for CBR, rt-VBR, nrt-VBR, or UBR service
categories. ATM Forum Traffic Management 4.0 specifies conformance definitions
within each service category. These definitions are listed in “Weighted round robin
scheduler” (p. 6-72). Conformance definitions are based on Cell Loss Priority (CLP).
Depending on the service category provisioned, the following parameters are
applicable:
• Peak Cell Rate (PCR) upstream and downstream (cps) - PCR is specified for CBR,
rt-VBR and nrt-VBR and UBR connections
Peak Cell Rate is the cell rate which the cell source may never exceed in order to
be compliant with the traffic contract.
• Sustainable Cell Rate (SCR) upstream and downstream (cps) - SCR is specified for
rt-VBR and nrt-VBR connections
SCR is the upper bound on the average rate of the conforming cells of an ATM
rt-VBR and nrt-VBR connection over time intervals which are longer than those for
which the PCR is specified. (Conforming cells are cells which conform to the
specified traffic contract).
• Maximum Burst Size (MBS) upstream and downstream - MBS is specified for
rt-VBR and nrt-VBR connections
MBS is the maximum number of cells which can be transmitted by the source at
the peak rate.
• PCR CDVT (msec) - Cell-Delay Variation Tolerance (CDVT) is specified for all
service categories.
The CDVT specified in the ATM traffic profile is used in the GCRA to determine
conformance. The larger the CDVT, the more tolerant the connection to variations
in the receiving rate of data from the modem.
• SCR CDVT (msec) - Cell-Delay Variation Tolerance (CDVT) is specified for the
rt-VBR and nrt-VBR service categories only.
• Cell Loss Priority (CLP)
The CLP bit in the ATM header is used to designate the priority of the cell, where
0 means high and 1 means low.
In the ATM traffic profiles, the CLP parameter specifies whether the SCR applies
to the CLP=0 (service compliant cells only) or to CLP0+1 (untagged and tagged
cells) for the rt-VBR and nrt-VBR service categories. The table below lists the
values for these parameters for the conformance definitions specified by the ATM
Forum.
• Cell Tagging
When the tagging option is activated, the Usage Parameter Control (UPC) changes
the value of the CLP bit to 1 in each high-priority cell (CLP=0) it declares to be
nonconforming with the traffic contract of the connection. A cell whose priority
was downgraded is said to be tagged
• AAL5 Frame Discard (upstream and downstream)

The AAL5 frame discard parameter should be set to true only when both of the
following conditions apply:
– The cell stream is AAL5
– Packet discard (EPD/PPD) is to be invoked.

Values provisioned for Cell Loss Priority and Cell Tagging

In the AnyMedia ® Access System the conformance definitions are provisioned by
selecting service categories, CLP, and cell tagging.
The following table shows the values provisioned for Cell Loss Priority and Cell
Tagging to comply with ATM Forum Conformance Definitions

Conformance Definition Cell Loss Priority Cell Tagging

CBR.1 Not applicable Not applicable
VBR.1 CLP=0+1 False
VBR.2 CLP=0 False
VBR.3 CLP=0 True
UBR.1 Not applicable False
UBR.2 Not applicable True

On the GSI, once a service category is selected, unused fields are grayed out. “ATM
traffic parameters” (p. 6-111) shows the possible ranges for these parameters.
If AAL5 frame discard is invoked for cells that are not AAL5, all data will be dropped
once one cell is noncompliant.

Cross-connect provisioning
...................................................................................................................................................................................................................................

Overview
Provisioning a cross-connect involves specifying the slot, port (VPI, VCI), and ATM
traffic profile associated with the cross-connect. A successful cross-connect must be
assigned to the appropriate hardware and pass CAC.
If the installed AP does not support the service category, the cross-connect will be
created, but a mismatch of equipment and attributes (MEA) alarm will be generated.
This alarm is cleared either by deleting the cross-connect or by replacing the pack with
one that supports the service category.
The creation of the cross-connect can fail because the CAC rejects the requested
connection. The CAC takes into account all of the following:
• Requested service category
• Shelf PCR - upstream and downstream direction
• Overbooking factor and CLR for the service category
• Minimum bit rate of the transmission profile - upstream and downstream direction
• PCR, SCR, and MBS of the connection specified within the ATM traffic profile
• Admissible bandwidth - upstream and downstream direction
• Guaranteed bandwidth - upstream direction
(Guaranteed bandwidth is not applicable for an AFME1)
• Reserved bandwidth for the BB ATM Operations Channel
• Aggregate parameters of existing connections on the shelf and on the port.
The CAC algorithm determines the effective bandwidth of the requested connection
and allocates it from the Shelf PCR if the connection is admitted. This does not
provide exclusive use of the allocated bandwidth; all connections actively transmitting
data share the feeder bandwidth with priority scheduling. For UBR connections, all
requests are admitted up to the limit of the maximum number of connections on a shelf
provided all parameters are within range.

Application of CAC algorithm to CBR connections

For CBR connections, the CAC algorithm uses the PCR as the effective bandwidth.
The CAC refuses a connection request if the effective bandwidth cannot be
accommodated along with existing connections on the shelf and port. Following are
two examples of CAC connection refusal:
• Example 1
Assume an ADSL port has an upstream Minimum Bit Rate setting of 1 Mbps. A
request is made for a CBR connection with upstream PCR = 3000 cps = 1272
kbps. The connection is refused.
• Example 2
Assume an ADSL port has an upstream minimum bit rate setting of 1 Mbps and
that it already has a CBR connection with an upstream
PCR = 1000 cps = 424 kbps. Any CBR connection requested with an upstream
PCR greater than 1500 cps (636 kbps) will be rejected.
The CAC algorithm is applied to both the upstream and downstream rates.

Application of CAC algorithm to VBR connections

For rt-VBR and nrt-VBR connections, the CAC algorithm provides statistical
multiplexing to provide more efficient utilization of the bandwidth. The upstream SCR
is compared with the upstream minimum bit rate for the port. The algorithm calculates
the effective bandwidth based on the port state. A rule of thumb when selecting the
SCR on a port is to check the following:
• Check whether the aggregate upstream SCR divided by the overbooking factor over
the port is less than or equal to the upstream port bandwidth (in cps).
• Check whether the downstream minimum bit rate (in cps) is at least equal to the
aggregate downstream PCR divided by the overbooking factor of the connections.

Overbooking factor
...................................................................................................................................................................................................................................

Overbooking factor
The overbooking factor is specified per service category. The setting range of the
overbooking factor is given in the following table.

AFM type QoS Overbooking factor

Setting range (in steps of 0.5)
AFMO UBR 1-10
nrt-VBR 1-10
rt-VBR 1-10
CBR 1-10
AFME3/DS3, AFME1 UBR 1-10
nrt-VBR 1-50
rt-VBR 1-10
CBR 1-10

The larger the shelf overbooking factor, the better the network can be utilized, but the
greater the risk of congestion, thereby degrading QoS. The values selected for the
overbooking factors may need to be adjusted after monitoring the ATM traffic
statistics. If congestion is being encountered too frequently, the overbooking factors
may need to be reduced.
A request to modify overbooking factors will be allowed if no previously established
one would fail with the new overbooking factor.

UBR connections
For UBR connections, all requests are admitted up to the limit of the maximum
number of connections on a shelf provided all parameters are within the range.

Congestion management schemes

Threshold scheme types

There are three intelligent congestion management schemes supported at the feeder
interface to alleviate sustained congestion. These are cell/packet discard schemes
triggered on a per connection basis depending on the level of congestion. Threshold
schemes are supported per service category although the cell/packet discard is
performed at connection level.
Following are the three non-provisionable congestion management thresholds which are
set in each transmit buffer belonging to a service category, supported at the
multiplexing point of the upstream feeder interface:
• CLP=1 threshold:
When the buffer fill exceeds this threshold but not the next one, the system
discards the first tagged cell (CLP=1) and all further cells of the frame
(independent of the CLP bit) except the last one (EOF cell). In doing so, it
exercises PPD. The PPD region spans between CLP=1 threshold and the EPD
threshold. If all received cells are non-tagged, PPD will not be executed and hence
the next buffer level will be reached/exceeded (see EPD threshold). The system
always passes through the last cell of a partially-discarded AAL5 frame
disregarding its CLP value.
• EPD threshold:
When the buffer fill exceeds this threshold but is lower than the next one
(maximum limit), the system discards the entire incoming AAL5 frames (including
the EOF cell), regardless of whether any of their cells are tagged or not
• Maximum limit:
When the buffer fill reaches this threshold (because of connections where AAL5
frame discard is not enabled or daisy-chain traffic), the system discards all the
incoming cells.
The downstream behavior when AAL5 frame discard is enabled for a connection is the
following:
When congestion is detected in a (downstream) transmit buffer (on an ADSL AP)
belonging to a service category, tagged cells are discarded prior to non-tagged cells and
PPD is executed to all further cells of the frame (independent of the CLP bit) except
the last one (EOF cell).

More details on threshold schemes

These thresholds are applicable for rtV-BR, nrt-VBR and UBR service categories. They
are configured independently across the service categories. The thresholds in rt-VBR
are static, whereas nrt-VBR and UBR are dynamic, based on Lucent/Bell Labs
patented adaptive dynamic threshold scheme. This scheme allows the available buffer
space to be dynamically shared between nrt-VBR and UBR, depending on the level of
traffic received on each service category. Note that in the current implementation the
buffer spaces allocated for CBR, rt-VBR and nrt-VBR/UBR traffic are treated

independently, also the thresholds are defined for each buffer space. If a buffer space
reaches a threshold tagging/dropping cells is initiated for the service category to which
this buffer space is allocated.
In addition a maximum buffer size is also defined for buffers allocated for each service
category. When the buffer occupancy reaches the maximum buffer limit all the
incoming cells CLP=0+1 are discarded.
The following figure represents how these threshold settings are applied to a buffer
associated with a service category other than CBR. There is no threshold setting for a
CBR buffer. In addition, the CLP1 threshold is set to the equivalent of the maximum
CBR buffer limit.

A buffer assigned to a class

EPD CLP1
other than CBR

ATM cells Buffer output

Threshold where CLP1 cells get dropped

Region where PPD occurs

Threshold where all incoming packets get dropped

Maximum buffer limit

CLP1 threshold Threshold where low priority cells start to get dropped
EPD threshold Threshold where entire incoming AAL5 packets start to get dropped
PPD region Region where partial packet discard occurs
Maximum buffer limit Limit at which all incoming cells are dropped

Traffic shaping - Policing - Scheduling

Traffic shaping
Traffic shaping changes the characteristics of the cell stream on a connection to
improve efficiency (while meeting the QoS objectives). Local cell-scheduling policies
shape upstream traffic to reduce PCR, limit burst size, and space cells to reduce CDV.

Policing
The traffic is policed in the upstream direction on the shelf where the end user xDSL
line terminates.
Downstream traffic is expected to be policed at the entry point to the ATM network.
Therefore, policing is not performed on the downstream traffic.
Noncompliant cells in the upstream direction are tagged or dropped according to the
provisioned ATM traffic profile. The algorithm for this is the GCRA specified in the
ATM Traffic Management Forum 4.0.

Scheduling
The AnyMedia ® Access System supports two types of scheduling algorithms:
• The strict service category priority scheduling
• The weighted round-robin (WRR) scheduling.

Service category priority scheduler

When using strict service category priority scheme, the traffic will be scheduled in the
following order: CBR first, then rt-VBR, nrt-VBR, and UBR last. In a daisy chain, the
priority of connections from subtending shelves is treated in the same manner. Traffic
engineering must ensure that some bandwidth on each shelf is allocated for UBR
traffic such that a connection based on the UBR category is not bandwidth-starved.
In the event of congestion at the upstream feeder interface due to the total upstream
bandwidth exceeding the feeder throughput, cells will be buffered in the respective
priority queues (priority buffers). Buffers will be filled depending on the incoming
traffic and the order in which the buffers are served by the scheduler. As the buffer
occupancy reaches the threshold levels mentioned in “Congestion management
schemes” (p. 6-70), congestion management schemes will be triggered and
cells/packets are dropped accordingly.
This can occur at any shelf in a daisy chain.

Weighted round robin scheduler

The AnyMedia ® Access System supports weighted round robin (WRR) scheduler to
ensure bandwidth guarantees to each service category at the upstream feeder interface
during periods of sustained congestion.

The WRR scheduler is a per service category-based traffic shaping scheme that uses
operator defined weights to serve traffic from each ATM service category. Once the
WRR is configured, bandwidth is guaranteed during periods of sustained congestion
based on the weights assigned to a service category. The guaranteed bandwidth is
provisioned for CBR, rt-VBR and nrt-VBR by means of configuring the WRR
scheduler as follows.
When allocating the feeder bandwidth of an AFME3/DS3 or an AFMO to individual
service categories, the feeder throughput is divided into 16 parts. For an AFME1 it is
divided into 4 parts. One such part is designated as a weight of one. Weights of n in
terms of feeder bandwidth is equivalent to (feeder throughput/16) × n, where n has to
be less than or equal to 16 (for an AFME1 “16” has to be replaced by “4”). Weights
are provisioned across CBR, rt-VBR and nrt-VBR service categories by the technician.
The sum of the weights provisioned across the three service categories has to be less
than or equal to 16 (or 4 for an AFME1). When the sum is less, the AnyMedia ®
Access System assigns the unused weights to the UBR service category. On the other
hand, when the CBR service category is assigned a weight of 16 (or 4 for an AFME1),
the scheduling scheme defaults to strict priority. The provisioning of upstream
guaranteed bandwidth for WRR is rejected, if the feeder is an E1-IMA feeder and the
IMA group has less than 3 E1 links.
To ensure that CBR service is always served, the guaranteed bandwidth for CBR
service must be set greater than or equal to the required effective bandwidth for all
CBR connections (including the new requested connection). If it is set less than the
effective bandwidth, provisioning will be denied. In daisy-chain configurations, the
local shelf CBR guaranteed bandwidth provisioning must take into account the CBR
guaranteed bandwidth provisioning of the daisy chained shelves.
For rt-VBR and nrt-VBR service, provisioning of guaranteed bandwidth less than the
required effective bandwidth will be accepted, but a message will warn the operator of
the condition. Note that the bandwidth reserved for the BB ATM Operations Channel is
not included in the effective bandwidth calculation for rt-VBR.

ATM xDSL system turn-up and service provisioning

scenarios and parameters

Purpose
This section describes the turn-up provisioning for ATM xDSL service. Sample
scenarios demonstrate the methods for performing turn-up and service provisioning for
simplex and duplex modes for standalone or daisy-chained shelves.

Contents

Introduction 6-75
Turn-up provisioning 6-77
Service activation 6-81
Shelf cascading via E1IMA APs 6-83
Port provisioning and addressing for duplex mode AFMOs 6-85
Slot numbering and AIDs for the AnyMedia ® LAG Shelves 6-88
Service states 6-90
Profiles 6-96
ADSL parameters - port settings 6-98
Setting other ADSL transmission parameters using the ADSL 6-102
transmission profile
SHDSL parameters - port settings 6-106
E1IMA AP settings 6-109
ATM traffic parameters 6-111
Parameters in failure report profiles 6-112

Overview
This section describes the following topics:
• Turn-up provisioning scenarios
• Service activation for xDSL
• Port provisioning and addressing for duplex mode AFMOs
• Service states
• Maintenance of the protection status of protected optical facilities
• The role of profiles in provisioning
• Port provisioning for an ADSL, or SHDSL port
• Port provisioning for E1 ports on an E1IMA AP
• Provisioning ATM traffic parameters
• VP quality of services
Important! The Work Orders in the Appendix provide step-by-step, detailed
information for turn-up and service activation for technicians using the Commands
and Procedures for ATM xDSL services turn-up and service activation
documentation. The scenarios that follow are high-level descriptions for planning
purposes only. These service activation scenarios assume that the technicians have
access to the Work Orders.
Important! In a mixed narrowband and ATM xDSL configuration it is assumed
that the NB subsystem has already been installed and turned up before turning up
the BB subsystem.

Notes on LAG 4300 Shelf

When an AnyMedia ® LAG 4300 Shelf is being turned up, the two BB subsystems in
the upper and in the lower row of an AnyMedia ® LAG 4300 Shelf have no common
communication link. They are managed separately and independently. Therefore
provisioning procedures require the user to explicitly select which of the two BB
subsystems is the provisioning target.
It does not matter in which order the two rows of the AnyMedia ® LAG 4300 Shelf are
turned up and provisioned. Turn-up and provisioning is identical for all AnyMedia ®
shelf types. Only the AFM slot references differ. For a reference list refer to “Slot
numbering and AIDs for the AnyMedia ® LAG Shelves” (p. 6-88).
Turn-up and provisioning of the second BB subsystem in an AnyMedia ® LAG 4300
Shelf is similar to the growth of a daisy-chained AnyMedia ® ETSI V5 Shelf. Since the
two BB subsystems are two independent entities, it is the operator’s responsibility to
correlate the parameters associated with the two subsystems, e.g. traffic profiles,
coordination of daisy chained VPCs.

The AnyMedia ® LAG 4300 Shelf is not supported by R1.23 and earlier releases. In
this case a software download and a software upgrade will be required. Note that only
the SW Download functionality will be supported.

Note on LAG 1900 Shelf

The AnyMedia ® LAG 1900 Shelf is not supported by R1.25, R1.23 and earlier
releases. In this case a software download and a software upgrade will be required.
Note that only the SW Download functionality will be supported.

Turn-up provisioning
...................................................................................................................................................................................................................................

High-level procedures
Turn-up is used to establish the parameters that are common to all of the subscriber
connections. These parameters are illustrated in the following turn-up scenarios:
• Turning up a new standalone Mainshelf in simplex AFM mode
• Turning up a new standalone Mainshelf in duplex AFM mode
• Turning up new daisy-chained Mainshelves in simplex AFM mode
• Turning up new daisy-chained Mainshelves in duplex AFM mode
• Turning up the first BB subsystem in an AnyMedia ® LAG 4300 Shelf in simplex
AFM mode
• Turning up the second BB subsystem in an AnyMedia ® LAG 4300 Shelf in simplex
AFM mode
• Turning up the first BB subsystem in an AnyMedia ® LAG 4300 Shelf in duplex
AFM mode
• Turning up the second BB subsystem in an AnyMedia ® LAG 4300 Shelf in duplex
AFM mode.
Both turn-up and service provisioning have to occur before customers receive service.
Scenario 1: Turning up a new standalone Mainshelf in simplex AFM mode
Assume that a new AnyMedia ® Mainshelf is installed but does not have any ATM
xDSL circuit packs. Determine the ATM feeder option (this may be either E3, DS3,
E1, STM-1, or OC-3c). Install the AFME3, the AFMDS3, the AFME1, or the AFMO
in the preferred AFM slot (see “Slot numbering and AIDs for the AnyMedia ® LAG
Shelves” (p. 6-88)). Verify (and upgrade, if necessary) the AFM software load, then
initialize the system database.
Connect the cabling from the AFM to the ATM transport network.
Provision the appropriate communications parameters, shelf parameters, and date and
time. Provision the AFME3/DS3 or AFMO feeder port parameters for Port 1. Provision
Port 2 as OOS. For the AFME1, provision the feeder(s) parameters and the IMA group
parameters, create the group, add the desired links to the group, and provision the
feeder, group, and link performance monitoring thresholds.
Scenario 2: Turning up a new standalone Mainshelf in duplex AFM mode
Perform all steps in Scenario 1 above except connecting the cabling from the AFM to
the ATM transport network (which will be done later). Note that the AFME1 cannot be
used in duplex mode. For an AFMO select either DBSF protection mode or Duplex
1+1 protection mode.
Install the other AFM in the AFM protection slot. Provision the shelf for duplex mode.

Connect the cabling from the duplex AFMs to the ATM transport network.
• If the AFMs are of the type AFME3/DS3, then this includes additionally the
installation of splitters/combiners.
• If the AFMs are of the type AFMO, and the protection mode has been set to DBSF
protection mode, then this includes additionally the installation of optical couplers.
• If the AFMs are of the type AFMO, and the protection mode has been set to
Duplex 1+1 protection mode, then there are two STM-1/OC-3c feeders to connect
to the ATM transport network.
The AFM in the protection slot (see “Slot numbering and AIDs for the AnyMedia ®
LAG Shelves” (p. 6-88)) initializes and synchronizes its software and database with
that of the AFM in the preferred slot.
Scenario 3: Turning up new daisy-chained Mainshelves in simplex AFM mode
Turn up each shelf in the daisy-chain individually, following “ Scenario 1: Turning up
a new standalone Mainshelf in simplex AFM mode” (p. 6-77) above except for the
following differences:
• For the first shelf in the daisy-chain, perform the cabling as listed in Scenario 1
above. However, for all other shelves in the daisy-chain, cable the AFM to the
previous AFM in the daisy-chain.
• After the communications provisioning and shelf provisioning is completed, and
before the feeder port provisioning is done, update the daisy-chain VPIs.
• Provision port 2 as IS (except for the last shelf, where port 2 is provisioned as
OOS).
Always add each new shelf at the end of the daisy-chain.
Scenario 4: Turning up new daisy-chained Mainshelves using duplex AFM mode
Assume that the new AnyMedia ® Mainshelves are installed but do not have any ATM
xDSL circuit packs. Determine the ATM feeder option, which is either the E3, DS3,
STM-1 or the OC-3c.
Turn up each shelf in the daisy-chain as follows:
• Install one AFM in the preferred slot (see “Slot numbering and AIDs for the
AnyMedia ® LAG Shelves” (p. 6-88)). Verify (and upgrade, if necessary) the AFM
software load, then initialize the system database.
• Provision the appropriate communications parameters, shelf parameters, and date
and time. Update the daisy-chain VPIs. Provision the feeder port parameters for
port 1. Provision port 2 as IS (except for the last shelf in the daisy-chain, which is
provisioned as OOS).
• Install the other AFM in the protection slot. Provision the shelf for duplex mode,
for an AFMO select either DBSF protection mode or Duplex 1+1 protection mode.
The AFM in the protection slot initializes and synchronizes its software and
database with that of the AFM in the preferred slot.

• For the first shelf in the daisy-chain, connect the cabling from the duplex AFMs to
the ATM transport network.
– If the AFMs are of the type AFME3/DS3, then this includes additionally the
installation of splitters/combiners.
– If the AFMs are of the type AFMO, and the protection mode has been set to
DBSF protection mode, then this includes additionally the installation of optical
couplers.
– If the AFMs are of the type AFMO, and the protection mode has been set to
Duplex 1+1 protection mode, then there are two STM-1/OC-3c feeders to
connect to the ATM transport network.
• For all other shelves in the daisy-chain, cable the duplex AFMs to the previous
duplex AFMs in the daisy-chain as described above for the ATM transport network.
Always add each new shelf at the end of the daisy-chain.
Scenario 5: Turning up the first BB subsystem in an AnyMedia ® LAG 4300 Shelf
in simplex AFM mode
This scenario is identical to “ Scenario 1: Turning up a new standalone Mainshelf in
simplex AFM mode” (p. 6-77) , but the operator has first to select which of the two
BB subsystems will be turned up. Based on the BB subsystem, the GSI is connected
to, the GSI will only offer the operator the choice of selecting parameters associated
with that subsystem.
Scenario 6: Turning up the second BB subsystem in an AnyMedia ® LAG 4300
Shelf in simplex AFM mode
The two BB subsystems in the AnyMedia ® LAG 4300 Shelf are independent systems
and could be connected to the ATM network via separate ATM feeders. In this case
this scenario would be identical to “ Scenario 1: Turning up a new standalone
Mainshelf in simplex AFM mode” (p. 6-77). But most probably they will be
daisy-chained. Then refer to “Scenario 3: Turning up new daisy-chained Mainshelves
in simplex AFM mode” (p. 6-78). In both cases the user has first to select which of the
two BB subsystems will be turned up. Based on the BB subsystem, the GSI is
connected to, the GSI will only offer the operator the choice of selecting parameters
associated with that subsystem.
Scenario 7: Turning up the first BB subsystem in an AnyMedia ® LAG 4300 Shelf
in duplex AFM mode
This scenario is identical to “ Scenario 2: Turning up a new standalone Mainshelf in
duplex AFM mode” (p. 6-77), but the user has first to select which of the two BB
subsystems will be turned up. Based on the BB subsystem, the GSI is connected to, the
GSI will only offer the operator the choice of selecting parameters associated with that
subsystem.
Scenario 8: Turning up the second BB subsystem in an AnyMedia ® LAG 4300
Shelf in duplex AFM mode.
The two BB subsystems in the AnyMedia ® LAG 4300 Shelf are independent systems
and could be connected to the ATM network via separate ATM feeders. In this case
this scenario would be identical to “ Scenario 2: Turning up a new standalone
....................................................................................................................................................................................................................................
363-211-586 6-79
Issue 6, July 2007
System planning and engineering for ATM xDSL services Turn-up provisioning

Mainshelf in duplex AFM mode” (p. 6-77). But most probably they will be
daisy-chained. Then refer to “Scenario 4: Turning up new daisy-chained Mainshelves
using duplex AFM mode ” (p. 6-78). In both cases the user has first to select which of
the two BB subsystems will be turned up. Based on the BB subsystem, the GSI is
connected to, the GSI will only offer the operator the choice of selecting parameters
associated with that subsystem.

Service activation
...................................................................................................................................................................................................................................

Overview
Service activation provides the subscriber with one or more ATM virtual connections.
Both turn-up and service provisioning must occur before customers receive service.
Provisioning subscriber service generally results in establishing an ATM cross-connect
between the ATM network side and the subscriber line in one of the four service
categories. Ultimately, this virtual connection is terminated on the subscriber’s CPE at
one end and on the service provider’s equipment at the other.

Service activation for ADSL

The following high-level scenario describes how ADSL service is activated for a
subscriber. The scenario begins after the following activities are complete:
• Shelf installation and all narrowband provisioning and service activation
• ATM xDSL services turn-up (see “ATM xDSL system turn-up and service
provisioning scenarios and parameters” (p. 6-74).
The scenario begins before any ADSL APs are installed.
If the circuit pack to be installed is a combo AP, then both POTS and ADSL can be
provided to the subscriber. The POTS circuit has to be provisioned via the COMDAC.
In this case, install the combo AP following the provisioning information in the
Commands and procedures for narrowband services. Then follow the required steps to
activate the ADSL service.
To activate ADSL service for any ADSL-type AP, install the ADSL AP and connect the
appropriate a/b pairs. Create or verify the ADSL transmission profile to be used for a
given ADSL port and if needed, provision the necessary parameters (both upstream and
downstream) within an ADSL transmission profile. The allowed values of these
parameters are described in “ADSL parameters - port settings” (p. 6-98) and “ADSL
parameters - further settings” (p. 6-102).
Provision the ADSL port.
Create or verify the ATM traffic profile to be used for a given cross-connect (see
“Profiles” (p. 6-96)). Provision all the necessary parameters and the ATM
cross-connect.
Provision the ATM cross-connect by selecting the appropriate parameters.
To minimize the provisioning effort, several ADSL transmission profiles and several
ATM traffic profiles are built into the system. See “Predefined ADSL transmission
profiles” (p. 6-128), and “Predefined ATM traffic profiles” (p. 6-135).

Service activation for SHDSL

The following high-level scenario describes how SHDSL service is activated for a
subscriber. The scenario begins after the following activities are complete:
• Shelf installation and all traditional DLC provisioning and service activation
• ATM xDSL services turn-up provisioning (see “ATM xDSL system turn-up and
service provisioning scenarios and parameters” (p. 6-74)).
The scenario begins before any SHDSL APs are installed.
To activate SHDSL service for any SHDSL AP, install the SHDSL16 AP and connect
the appropriate a/b pairs.
Create or verify the SHDSL transmission profile to be used for the given SHDSL port
(see “Profiles” (p. 6-96)) and provision the required parameters. The allowed values of
these parameters are described in “SHDSL parameters - port settings” (p. 6-106).
Provision the SHDSL port by selecting the SHDSL transmission profile. Create or
verify the ATM traffic profile to be used for the given cross connect (see “Profiles”
(p. 6-96)) and provision the required parameters.
Provision the ATM cross-connect.
To minimize the provisioning effort, several SHDSL transmission profiles and several
ATM traffic profiles are built into the system. See “Predefined SHDSL transmission
profiles” (p. 6-132) and, “Predefined ATM traffic profiles” (p. 6-135).

Shelf cascading via E1IMA APs

Assumptions
The following high-level scenario describes how shelves are cascaded via E1IMA APs.
The scenario begins after the following activities are complete:
• The LPA941 has been upgraded to the R1.25 software in the preferred AFM slot of
any powered AnyMedia ® shelf.
• After the upgrade the LPA941 can be plugged into every AP slot or AFM slot with
the exception of the AFM protection slot:
– If plugged into an AP slot, it recovers and operates as E1IMA AP.
– If plugged into the preferred AFM slot, it recovers and operates as AFME1.
• For simplifying the description, it is assumed that the cascaded shelf that will be
connected to an E1IMA AP in the host shelf has been turned up already. Otherwise
it has to be turned up before as described in “ Scenario 1: Turning up a new
standalone Mainshelf in simplex AFM mode” (p. 6-77).
• Shelf installation and ATM xDSL services turn-up provisioning for the host shelf
have been completed (see “ATM xDSL system turn-up and service provisioning
scenarios and parameters” (p. 6-74)).

Shelf cascading via E1IMA APs

The scenario begins before any E1IMA APs are installed.
• Provision the E1IMA AP in the host shelf.
Eight E1 ports, 1 logical interface ’IMA line’ and an IMA group with 1 IMA link
(belonging to E1 port 1) are auto-created with default values of the corresponding
configuration parameters.
Enable performance monitoring for all ports on the pack, if required, and
eventually change the pack performance management thresholds.
• Install an E1IMA AP in the host shelf. Connect the E1 connector on the faceplate
of the E1IMA AP to the E1 connector on the faceplate of the AFME1 in the
cascaded shelf. Therefore special Y-cables with 16 pairs are required on both sides
to which two 8-pair E1 cables are connected.
• Provision the E1 ports if default settings have to be changed.
Eight E1 ports with default values of the configuration parameters have been
auto-created by provisioning the E1IMA AP. These ports get assigned a
corresponding default failure report profile. Alarm reporting of all alarms of the
default failure report profile are set to ’no reporting’. The administrative service
state and the default failure report profile can be changed by the operator.
Line loopbacks - provisionable per port - may be initiated from the same screen.

• Add E1 links to the IMA group if required and enable performance monitoring for
the IMA group and all its link if applicable or provision the E1IMA AP in UNI
mode (refer to “E1IMA AP settings” (p. 6-109)). The autocreated IMA group and
the IMA link get assigned their corresponding default failure report profile. When
an IMA link is added by an operator, it can get assigned an operator defined
profile. Alarm reporting of all alarms of the default failure report profiles are set to
‘no reporting’.
• Enable VP/VC AIS, if required. The AIS setting applies to all E1 links, regardless
whether IMA mode or UNI mode is provisioned.
• Provision the feeder VPs as an upstream VP in all the shelves that are farther
downstream than the shelf in which the VP cross-connect was created.
• Provision the ATM cross-connects. Note that these provisioning data have to be the
same on the host shelf and on the cascaded shelf In the host shelf a
cross-connection has to be provisioned for the BB ATM Operations Channel to the
cascaded shelf.

Port provisioning and addressing for duplex mode AFMOs

...................................................................................................................................................................................................................................
For duplex mode AFMOs, two levels of port entities are distinguished:
• Physical feeder ports (pfp’s)
• Logical feeder ports (lfp’s).
Physical feeder ports
The physical feeder port concept allows the addressing of SDH/SONET physical
medium, RS/Section, and MS/Line layer entities. The physical feeder ports correspond
to the physical terminations of electrical or optical feeders. A single AFMO provides
two physical feeder ports. A shelf operating in simplex mode with one AFMO has a
total of two physical feeder ports. A shelf operating in duplex mode with two AFMOs
has a total of four physical feeder ports.
Logical feeder ports
The logical feeder port concept is primarily relevant in duplex mode (for consistency,
the concept is also applied to simplex mode). It associates two physical ports that have
entities or attributes in common (in SDH/SONET terms, the two physical ports form a
″protection group″; a typical common entity of the protection group is the ″path″. A
typical common attribute is the administrative service state). An AnyMedia ® shelf,
regardless of whether using one or two AFMOs, always has 2 logical feeder ports.
In simplex mode, logical feeder port one is associated with physical feeder port one,
and logical feeder port two is associated with physical feeder port two. In duplex
mode, logical feeder port one is associated with both physical feeder ports one of the
AFM in the protection slot and physical feeder port one of the AFM in the preferred
slot. Also in duplex mode, logical feeder port two is associated with both physical
feeder ports two of the AFM in the protection slot and physical feeder port two of the
AFM in the preferred slot.
Feeder port provisioning at the GSI
SDH/SONET RS/Section Layer and MS/Line Layer provisioning is performed at the
physical level, using the Physical Feeder tab in the GSI Feeder Provisioning screen.
SDH/SONET Path Layer provisioning is performed at the logical level, using the
Logical Feeder tab in the GSI Feeder Provisioning screen.

Feeder port alarm reporting at the GSI

The addressing scheme for the feeder port alarm reporting at the GSI depends on
which shelf type is used.
Addressing scheme for the AnyMedia ® ETSI V5 Shelf
For AnyMedia ® ETSI V5 Shelf applications, the physical feeder port addressing
scheme for alarms is as follows at the GSI (where the address format is
″pfp-shelf-slot-port″):
• pfp-1-16-1 — physical feeder port 1 of the AFM in slot 16
• pfp-1-16-2 — physical feeder port 2 of the AFM in slot 16

• pfp-1-15-1 — physical feeder port 1 of the AFM in slot 15

• pfp-1-15-2 — physical feeder port 2 of the AFM in slot 15.
At the GSI, the logical feeder port addressing scheme for alarms is as follows (where
the address format is ″lfp-shelf-port″):
• lfp-1-1 — logical feeder port 1
• lfp-1-2 — logical feeder port 2.
In duplex mode, the relationship of the lfp to the pfp’s is as follows:
• lfp-1-1 is associated with pfp-1-15-1 and pfp-1-16-1
• lfp-1-2 is associated with pfp-1-15-2 and pfp-1-16-2.
In simplex mode, there is a one-to-one relationship of physical and logical feeder ports:
• lfp-1-1 is associated with pfp-1-16-1
• lfp-1-2 is associated with pfp-1-16-2.
Addressing scheme for the AnyMedia ® LAG 4300 Shelf
For AnyMedia ® LAG 4300 Shelf applications, the physical feeder port addressing
scheme for alarms is as follows at the GSI (where the address format is
″pfp-shelf-slot-port″):
AFM in the lower row of the LAG 4300 Shelf:
• pfp-1-1-1 (physical feeder port 1 of the AFM in the preferred slot)
• pfp-1-1-2 (physical feeder port 2 of the AFM in the preferred slot)
• pfp-1-2-1 (physical feeder port 1 of the AFM in the protection slot)
• pfp-1-2-2 (physical feeder port 2 of the AFM in the protection slot)
AFM in the upper row of the LAG 4300 Shelf:
• pfp-1-25-1 (physical feeder port 1 of the AFM in the preferred slot)
• pfp-1-25-2 (physical feeder port 2 of the AFM in the preferred slot)
• pfp-1-26-1 (physical feeder port 1 of the AFM in the protection slot)
• pfp-1-26-2 (physical feeder port 2 of the AFM in the protection slot)
At the GSI, the logical feeder port addressing scheme for alarms is as follows (where
the address format is ″lfp-shelf-port″):
• lfp-1-1 — logical feeder port 1
• lfp-1-2 — logical feeder port 2.
In duplex mode, the relationship of the lfp to the pfp’s is as follows:
Lower row of the shelf:
• lfp-1-1 is associated with pfp-1-1-1 and pfp-1-2-1
• lfp-1-2 is associated with pfp-1-1-2 and pfp-1-2-2
Upper row of the shelf:
• lfp-1-1 is associated with pfp-1-25-1 and pfp-1-26-1
• lfp-1-2 is associated with pfp-1-25-2 and pfp-1-26-2

In simplex mode, there is a one-to-one relationship of physical and logical feeder ports:
Lower row of the shelf:
• lfp-1-1 is associated with pfp-1-1-1
• lfp-1-2 is associated with pfp-1-1-2
Upper row of the shelf:
• lfp-1-1 is associated with pfp-1-25-1
• lfp-1-2 is associated with pfp-1-25-2.

Slot numbering and AIDs for the AnyMedia ® LAG Shelves

Slot designations
Descriptions of the BB subsystem include the terms ″preferred AFM slot″ and ″AFM
protection slot″ in order to avoid the slot designations which are different for the BB
subsystems in the AnyMedia ® LAG 1900 Shelf , the AnyMedia ® LAG 4300 Shelf and
in the AnyMedia ® ETSI V5 Shelf. The table below shows the correlation between
these slots.

Shelf/row Preferred AFM AFM protection Further AP slots

slot slot
AnyMedia ® LAG 1900 3 4 1, 2, 5-14
Shelf
AnyMedia ® LAG 4300 1 2 3-24
Shelf lower row
AnyMedia ® LAG 4300 25 26 27-43
Shelf upper row
AnyMedia ® ETSI V5 16 15 1-14
Shelf

AIDs
A reference list of the access identifiers used for the user interfaces of the AnyMedia ®
LAG Shelves and the AnyMedia ® ETSI V5 Shelf is shown in the following table.
These AIDs appear only on the GSI and the Navis ™ AnyMedia ® Element Management
System.

Entity AIDs on AIDs on AIDs on LAG AIDs on LAG

AnyMedia ® ETSI AnyMedia ® LAG 4300 Shelf lower 4300 Shelf upper
V5 Shelf 1900 Shelf row row
Application pack ap-{1}-{1-15} ap-{1}-{1, 2, ap-{1}-{2-24} ap-{1}-{26-43}
4-14}
Port on an AP ap-{1}-{1-15}- ap-{1}-{1, 2, ap-{1}-{2-24}- ap-{1}-{26-43}-
{1-64} 4-14}-{1-64} {1-64} {1-64}
1
Subshelf subsh-{1-7} subsh-{1-6} subsh-{1-11} N/A
OCP subcp-{1-7} subcp-{1-6} subcp-{1-11} N/A
AP on a subshelf subap-{1-7}-{1-8} subap-{1-6}-{1-8} subap-{1-11}- N/A
{1-8}
Port of an AP on subap-{1-7}-{1- subap-{1-6}-{1- subap-{1-11}-{1- N/A
a subshelf 8}-{1-64} 8}-{1-64} 8}-{1-64}
Physical AFM afm-1-{15-16} afm-1-{3-4} afm-1-{1-2} afm-1-{25-26}

Entity AIDs on AIDs on AIDs on LAG AIDs on LAG

AnyMedia ® ETSI AnyMedia ® LAG 4300 Shelf lower 4300 Shelf upper
V5 Shelf 1900 Shelf row row
Physical feeder pfp-1-{15-16}- pfp-1-{3-4}-{1-2} pfp-1-{1-2}-{1-2} pfp-1-{25-26}-
port (non IMA) {1-2} {1-2}
Physical feeder pfp-1-{16}-{1-8} pfp-1-{3}-{1-8} pfp-1-{1}-{1-8} pfp-1-{25}-{1-8}
port (IMA)
Logical AFM afm-{1}
Logical feeder lfp-1-{1-2}
port
Virtual path vp-1-{0-255}
Virtual channel vc-1-{1-255}-{33-9723}

Notes:
1. Although the subshelf numbering allowed is 1 to 11, the total number of ONUs supported will be 10
when the LAG 4300 Shelf is configured for ATM xDSL services (on the lower row)

Service states
...................................................................................................................................................................................................................................

Overview
At any given time, each entity in the AnyMedia ® Access System has a defined service
state. The service state consists of two parts: an administrative state and an operational
state. Generally, the administrative state is set by a system user. The operational state is
controlled autonomously by the system. Service state values are given below for the
following entities:
• xDSL APs
• Duplex mode AFMs
• Simplex or duplex mode optical feeders.

Service states of xDSL APs

The administrative state of packs and ports can be provisioned to be IS (in service) or
OOS (out of service).
The system provides operational state information for slots, packs, and ports as
follows:
• Slot operational state — the valid values are as follows:
– Equipped - slot is equipped
– Unequipped - slot is unequipped
– Dormant - controlling entity is not IS.
• Pack operational state - the valid values are as follows:
– Fault Condition - a service-affecting or non-service-affecting fault condition has
been detected
– Out of Service - an out-of-service condition exists due to one of the following:
- the administrative state has been set to OOS
- the pack is initializing
- the pack is not present
- there is a pack/provisioning mismatch.
– In Service - the administrative status has been set to IS and the entity is able to
perform its designated service functions
– UnderSWDL - the pack is having software downloaded to it
– Not Provisioned - the pack has not been provisioned
– MEA - mismatch of equipment and attributes–equipped pack and its
provisioning do not match.
• Port operational state - the valid values are as follows:
– Out of Service - an out-of-service condition exists due to one of the following:
- an administrative state has been set to OOS
- a service-affecting fault condition has been detected.
– In Service - the administrative status has been set to IS and the port is able to
perform its designated service functions
...................................................................................................................................................................................................................................
6-90 363-211-586
Issue 6, July 2007
System planning and engineering for ATM xDSL services Service states

– Dormant - controlling entity is not IS

– Not Provisioned - the port number has not been provisioned
– MEA - mismatch of equipment and attributes–provisioning for the port is not
supported by the equipped pack that provides the port.
• ATM cross-connect operational state - the valid values are as follows:
– Out of Service - an out-of-service condition exits due to one of the following:
- an administrative state has been set to OOS
- a service-affecting fault condition has been detected.
– In Service - the administrative status has been set to IS and the cross-connect is
able to perform its designated service functions
– Dormant - controlling entity is not IS
– MEA - mismatch of equipment and attributes–provisioning for the cross-connect
is not supported by the equipped pack that provides the cross-connect.
In a controlling/controlled entity relationship, the operational condition of the
controlled entity depends on the operational condition of the controlling entity. In the
above description, controlling entities are, in order:
1. Slot
2. Pack
3. Port
4. Cross-connect.
So, for example, the operational condition of ports and cross-connects depends on the
operational condition of a pack. If a pack is OOS, all ports and cross-connects
associated with the pack are dormant.

Service states of duplex mode AFMs

There are no administrative states for duplex mode AFMs.
• Slot operational state — The valid values are as follows:
– Equipped (EQ) — Slot is equipped
– Unequipped (UEQ) — Slot is unequipped.
• Pack operational state — The operational state of the active AFM is always IS. The
standby AFM can have one of several possible operational states. Note that each of
these states further indicates, by a suffix, whether the active AFM can communicate
with the standby AFM. The suffix ″-EQ″ indicates that communication is possible,
while the suffix ″-UEQ″ indicates that no communication is possible. The valid
values for the standby AFM’s operational state are as follows:
– Out of Service (OOS-UEQ) — A temporary out-of-service condition occurs
when the active AFM first determines that it cannot communicate with the
standby AFM. This condition exists due to one of the following:
- The standby AFM is not present
- The standby AFM is present but has not completed initialization

- The standby AFM does not answer a polling request from the active AFM.
– Fault (FLT-UEQ) — The active AFM has been unable to communicate with the
standby AFM for five minutes. This condition exists due to one of the
following:
- The standby AFM is not present
- The active AFM is not able to communicate with the standby AFM
persistently.
– Mismatch of equipment and attributes (MEA-EQ) — This condition exists due
to one of the following:
- A pack other than the type of the active AFM has been installed in slot 15
(AFM protection slot)
- The standby AFM has a current program image different from that of the
active AFM.
Initializing (INIT-EQ) — The standby AFM is either initializing or
synchronizing with the active AFM
Standby (STBY-EQ) — The standby AFM is synchronized with the active AFM
and is fully ready to protect the active AFM
Fault (FLT-EQ) — A fault has occurred which can only be cleared by replacing
the standby AFM
Maintenance (MTCE-EQ) — Planned protection switching to the standby AFM
is inhibited. In this state, unplanned protection switching to this AFM is also
inhibited as long as the previously active AFM is able to recover successfully.
Also in this state, the standby AFM is no longer synchronized with the active
AFM.

Service states of simplex or duplex mode optical feeder ports

Facility administrative states exist only for logical port 2 in order to enable or disable
the port depending on whether or not there is daisy chaining. The valid values are IS
and OOS.
Facility operational states occur on a per-physical-port basis. The valid values are as
follows:
• OOS — Indicates that the associated logical port is in administrative state OOS
• IS — Indicates that the associated logical port is in administrative state IS
• DORMANT (duplex mode only) — Indicates that the controlling entity of the
physical port (in this case the standby AFM) is in an operational state that either
does not allow for determining the state of the physical port, or that does not allow
changing the physical port’s operational state from OOS to IS
• LPBK — Indicates that for this particular feeder there is an active loopback.
Occurs on physical port 1 only. (In duplex mode, it can be on physical port 1 of
either the active or the standby AFMO.)

Protection status of protected optical facilities

The status of the transmit and receive channels of both the active and standby optical
feeder is maintained by the AnyMedia ® Access System. The protection status allows a
user to determine the following:
• Which channels are in use
• Which channels have degraded
• Which channels have failed.
This information is especially useful for any AFM maintenance activities. For example,
a technician can use this information to determine whether a pack can be removed
without affecting service, whether a manual facility protection switch should be
performed before removing a pack, etc.
The possible status values for the transmit and receive channels of both the active and
standby optical feeder are different for the Duplex 1+1 protection mode and the DBSF
protection mode.
Duplex 1+1 protection mode
Note, that the terms transmit and receive are always related to the AnyMedia ® Access
System. For instance, a transmit channel can be selected by the far end to receive
traffic.
In the Duplex 1+1 protection mode the possible status values for the transmit and
receive channels of both the active and standby optical feeder are as follows:
Receive channel
• ACTIVE — The AFM has selected this channel to receive incoming payload. This
channel is also used for the external reference clock.
• ACTDEG (active degraded) — The AFM has selected this channel to receive
incoming payload. However, there is a signal degrade on this channel. This channel
is also used for the external reference clock.
• STBY (standby) — This channel is for protection
• STBYDEG (standby degraded) — This channel is for protection. However, there is
a signal degrade on this channel.
• ACTUNAV (active unavailable) — This occurs only if the active channel fails
while the standby channel is already unavailable
• STBYUNAV (standby unavailable) — This standby channel cannot be used for
carrying traffic anymore
Transmit channel
• ACTIVE — This channel is currently used by the far end to receive data
• ACTDEG — This channel is currently used by the far end to receive data.
However, there is a signal degrade on this channel.
• STBY — This channel is for protection
• STBYDEG (standby degraded) — This channel is for protection. However, there is
a signal degrade on this channel.

• ACTUNAV (active unavailable) — This occurs only if the active channel fails
while the standby channel is already unavailable
• STBYUNAV (standby unavailable) — This standby channel cannot be used for
carrying traffic anymore
• UNKNOWN — The protection status of this channel cannot be determined.
DBSF protection mode
In the DBSF protection mode the term transmit has a different meaning than in Duplex
1+1 mode. In DBSF protection mode the transmit protection state gives an indication
which feeder is transmitting traffic, which one is used for facility protection and
whether failures are detected or not. The protection status is maintained on a per
physical port basis.
In the DBSF protection mode the possible status values for the transmit and receive
channels of both the active and standby optical feeder are as follows:
Receive
• ACTIVE
The AFMO has selected this channel to receive incoming payload. Additionally,
this channel is taken for the external reference clock. The other receiver is
deselected. However, it is continuously monitored.
• ACTDEG (active degraded)
The AFMO has selected this channel to receive incoming payload. However, there
is a Signal Degrade condition on that channel. Additionally, this channel is taken
for the external reference clock.
According to the DBSF architecture a Signal Degrade will probably occur on active
and standby channel. If a Signal Degrade is detected only on one receive signal a
failure has occurred between the optical coupler and the AFMO.
• STBY
This channel serves for protection. In case of a feeder protection switch request
(planned or unplanned) it instantaneously can take over for receiving data.
Currently it is deselected and monitored.
• STBYDEG (standby degraded)
This channel serves for protection. However, there is a Signal Degrade condition on
that channel. In case of a feeder protection switch request (planned or unplanned) it
instantaneously can take over for receiving data. Currently it is deselected and
monitored.
According to the DBSF architecture a Signal Degrade will probably occur on active
and standby channel. If a Signal Degrade is detected only on one receive signal a
failure has occurred between the optical coupler and the AFMO.
• ACTUNAV (active unavailable)
This state occurs if the active channel fails. Failures include near end fault
condition on the line or a fault condition of the pack the feeder is residing upon.
• STBYUNAV (standby unavailable)
This standby channel cannot be used for carrying traffic. Reasons include a near
end fault condition on the line, a fault condition of the pack the feeder is residing
upon or the line being in loopback.

Transmit
• ACTIVE
This channel is used to transmit traffic. The laser of this channel is switched on.
• STBY
This channel serves for protection. The laser of this channel is switched off. In case
of a feeder protection switch request it instantaneously can take over transmission
of the traffic.
• ACTUNAV (active unavailable)
This channel is used to transmit traffic but a failure was detected. This may be a
cross-couple connector failure, a mate pack failure or the remote end indicates a
failure.
• STBYUNAV (standby unavailable)
This channel serves as protecting channel and a failure was detected on this
channel. This may be a cross-couple connector failure, a mate pack failure or the
remote end indicates a failure.

Profiles
...................................................................................................................................................................................................................................

Overview
A common feature of systems that are managed using SNMP are profiles. A profile is a
fixed set of parameters with specific values that needs to be provisioned only once but
that can be used by any number of system entities of the same type. In the AnyMedia ®
Access System, the following parameters are provisioned in profiles:
• ADSL, and SHDSL transmission parameters (see “ADSL parameters - port
settings” (p. 6-98), “ADSL parameters - further settings” (p. 6-102), and “SHDSL
parameters - port settings” (p. 6-106)).
• ADSL, and SHDSL performance management thresholds (see “ADSL performance
management capabilities” (p. 4-61)and “SHDSL performance management
capabilities” (p. 4-65)).
• ATM traffic parameters (see “ATM traffic parameters” (p. 6-111))
• Failure report profiles (see “Parameters in failure report profiles” (p. 6-112)).
Up to 128 profiles each of the ADSL, and SHDSL transmission parameters can be
created, and up to 128 profiles each of the Performance Management thresholds. Up to
256 profiles of the ATM traffic parameters can be created. The BB subsystem supports
a total of 120 port specific user defined failure report profiles. It is recommended not
to define more than 30 profiles per service type (ADSL, SHDSL).
Examples
A single profile can be created that contains a specific set of values for the ADSL
transmission parameters. Then, this profile can be associated with any number of
ADSL lines. Another example would be to create two profiles; call them Profile A and
Profile B. Five lines use Profile A and seven lines use Profile B.
Predefined profiles
The AnyMedia ® Access System contains a library of the following predefined profiles.
These profiles cannot be edited or deleted, but they can be used to generate new
profiles as required.
• ADSL transmission profiles — Nine predefined profiles are provided. The
parameters for these nine profiles are described in “Predefined ADSL transmission
profiles” (p. 6-128).
• SHDSL transmission profiles — Three predefined profiles are provided. The
parameters for these three profiles are described in “Predefined SHDSL
transmission profiles” (p. 6-132).
• ADSL performance management profiles — Two predefined profiles are provided.
The parameters for these two profiles are described in “Predefined ADSL
performance management profiles” (p. 6-133).
• SHDSL performance management profiles — Two predefined profiles are provided.
The parameters for these two profiles are provided in “Predefined SHDSL
performance management profiles” (p. 6-134).

• ATM traffic profiles — Eight predefined profiles are provided. Four are for ADSL,
and four are for SHDSL. For ADSL, and SHDSL, one profile is provided for each
service category. The parameters for these profiles are provided in “Predefined
ATM traffic profiles” (p. 6-135).
• Failure report profiles — Predefined profiles are provided, one for ADSL ports one
for SHDSL ports, one for E1IMA AP port, one for an IMA link and one for an
IMA group (refer to “Parameters in failure report profiles” (p. 6-112)). As specified
in the tables, one of them in each service class is the default failure report profile
which is used if no profile has been assigned by the user.
• DMT profiles — There is one predefined DMT profile available (only applicable
for ADSL2/ADSL2+). The parameters for this profile are provided in “Parameters
in DMT profile” (p. 6-142).
• RFI Notch Profile — The predefined RFI Notch profiles are assigned to a port
(only applicable for ADSL2+). The parameters for this profile are provided in
“Parameters in RFI notch profiles” (p. 6-143).

ADSL parameters - port settings

Overview
When an ADSL port is provisioned using the GSI, the technician must select the
following:
• A startup mode (described in “ADSL startup modes” (p. 6-98))
• A transmission profile (described in “Predefined ADSL transmission profiles”
(p. 6-128); also see “Setting the bit rate for the ADSL port using the ADSL
transmission profile” (p. 6-99), and “Setting other ADSL transmission parameters
using the ADSL transmission profile” (p. 6-102)).
• A performance monitoring profile (the parameters of which are described in
“ADSL performance management operation” (p. 4-60) and “ADSL performance
management capabilities” (p. 4-61)).
• DMT profile
• Failure report profile

ADSL startup modes

An ADSL port can be provisioned with a particular startup mode. The startup mode is
the particular method that the two ends of an ADSL span use to exchange training
information so that the ADSL physical layer can begin to operate. If an ADSL span is
to ″train up,″ each end of the span has to use a startup mode that is compatible with
the other end.
The choices of startup modes in the AnyMedia ® Access System provide compatibility
with a variety of subscriber ADSL modems. The startup modes are shown in the
following table:

Startup mode in ADSL standards ADSL modem type

GSI
Multimode G.992.1, Annex A, B, A/M (G.dmt) legacy ADSL, ADSL2/ADSL2+
G.992.2 (G.lite) legacy ADSL
G.992.3, Annex A, B, A/M (adsl2) ADSL2/ADSL2+
G.992.3, Annex L(readsl) ADSL2/ADSL2+
G.992.5, Annex A, B, A/M (adsl2+) ADSL2/ADSL2+
T1.413 (ANSI.dmt) legacy ADSL, ADSL2/ADSL2+
ADSL-over-ISDN legacy ADSL
G.994.1 (G.hs) G.992.1, Annex A (G.dmt) legacy ADSL, ADSL2/ADSL2+
G.992.2 (G.lite) legacy ADSL
ADSL-over-ISDN legacy ADSL
T1.413 T1.413 (ANSI dmt) legacy ADSL, ADSL2/ADSL2+
adsl2 G.992.3 ADSL2/ADSL2+

Startup mode in ADSL standards ADSL modem type

GSI
adsl2+ G.992.5 ADSL2/ADSL2+

Note that the ADSL-lite standards G-lite according to ITU-T G.992.2 and ITU-T
G.992.4 are not supported by LPA833 and LPA420. Additionally, neither LPA420 nor
LPA438 support ADSL-lite/ADSL2-lite standards.
Same startup modes support more than one ADSL modem type. In these cases, any of
the listed modem types are expected to operate with an ADSL port provisioned for one
of these startup modes, provided that the ADSL transmission profile parameters are
compatible with the modem (see “Profiles” (p. 6-96)). For example, switching from a
G.dmt modem (ADSL full-rate) to a G.lite modem (ADSL-lite) may require a different
transmission profile if the bit rate settings in the original profile were too high for
ADSL-lite. Otherwise, with these two startup modes, no provisioning changes should
be needed when a subscriber changes from one modem type to another. These two
modes provide a feature that is often called ″autosensing.″
The Multimode setting is expected to work with the widest variety of ADSL modems.
However, some modems may have particular needs regarding startup mode. In these
cases, one of the other two modes might be needed. For many cases when a subscriber
replaces his or her ADSL modem with an ADSL modem that needs a different startup
mode, the only change needed in the AnyMedia ® Access System will be to change the
startup mode setting for the corresponding ADSL port. But, as stated above, a different
ADSL transmission profile may be needed in some cases.
Setting the bit rate for the ADSL port using the ADSL transmission profile
As part of provisioning the ADSL transmission profile (see “Predefined ADSL
transmission profiles” (p. 6-128)), the technician must choose a rate adaptation method.
An ADSL port can be provisioned for one of two rate adaptation methods:
• Flexible or
• Explicit.
With flexible rate adaptation, maximum and minimum bit rates are set for each
direction of transmission, as shown in the next table.

Flexible rate adaptation

The following table shows the parameters for flexible rate adaptation used for ADSL
transmission.

Type of rate adaptation=flexible

1
Parameter Direction Allowed Values
DS=Downstream
US=Upstream
Maximum bit rate, flexible DS Any multiple of 32 from
rate adaptation, kbps 64 to 13120
US Any multiple of 32 from
64 to 1440
Minimum bit rate, flexible DS Any multiple of 32 from
rate adaptation, kbps 64 2. to 13120
US Any multiple of 32 from
64 2. to 1440

Notes:
1. For ADSL-lite, the framing structure limits the maximum downstream rate to
approximately 4500 kbps.
2. For transmission profiles generated with BB releases prior to R1.17.1U3 32 kbps is also
allowed. But be aware that such a profile cannot be modified without changing this value
to 64 kbps

When flexible rate adaptation is chosen, the ADSL circuits select a bit rate in the range
between the minimum and maximum rates provisioned according to the table above.
The rate selected by the ADSL circuits is the highest rate at which ADSL transmission
can operate within the bounds set by the parameters provisioned according to “ADSL
parameters - further settings” (p. 6-102). If the ADSL circuits cannot operate within the
bounds of the provisioned parameters, then the ADSL startup algorithm will cycle until
conditions change so that the ADSL circuits can operate. If conditions do not change
satisfactorily, the algorithm will recycle indefinitely. Following are possible ways for
the technician to change the ADSL conditions so that the circuits can operate:
• Change the provisioning
• Make repairs to the a/b pair that carries the ADSL signal
• Remove interference that may be entering the ADSL transmission span.
To accommodate various service offerings to subscribers, the minimum and maximum
bit rates for a given direction of transmission can be set as close together as is desired.
They can even be set to the same values.
Explicit rate adaptation
With explicit rate adaptation, data rate options are set for each direction of
transmission, as shown in the following table.

This table shows the parameters for explicit rate adaptation used for ADSL
transmission.

Type of rate adaptation=explicit

1
Parameter Direction Allowed Values
DS=Downstream
US=Upstream
Option 1 bit rate, kbps DS Any multiple of 32 from
Option 2 bit rate, kbps 64 2 to 8160

Option 3 bit rate, kbps

Option 4 bit rate, kbps
Option 1 bit rate, kbps US Any multiple of 32 from
Option 2 bit rate, kbps 64 2 to 1440

Option 3 bit rate, kbps

Option 4 bit rate, kbps

Important! When a bit rate parameter is provisioned to a value that is between two
allowed values, the system instead sets the provisioned value to the highest allowed
value which is less than the specified value.
When explicit rate adaptation is chosen, the ADSL circuits select the bit rate by
first attempting to operate at the Option 1 rates, as provisioned according to the
table above. If Option 1 is not achievable within the bounds set by the parameters
provisioned according to the next table, then the circuits attempt to operate at
Option 2, and so on. As with flexible rate adaptation, if the ADSL circuits cannot
operate within the bounds of the provisioned parameters, then the ADSL startup
algorithm will cycle indefinitely or until conditions change so that the ADSL
circuits can operate.
To accommodate various service offerings to subscribers, the rate options can be
set as close together as is desired. Two or more rate options for a given direction of
transmission can even be set to the same value.

Setting other ADSL transmission parameters using the ADSL

transmission profile
...................................................................................................................................................................................................................................

ADSL parameters - further settings

Further ADSL transmission parameters, which are provisioned using ADSL
transmission profiles (see “Predefined ADSL transmission profiles” (p. 6-128)), are
shown in the following table.

Parameter Direction Allowed Values

DS=Downstream
US=Upstream

SNR margin, dB DS Integer between 0 and 15

inclusive
US Integer between 0 and 15
inclusive

Interleave depth DS 1, 2, 4, 8, 16, 32, 64

US 1, 2, 4, 8, 16, 32, 64

Latency DS and US Interleaved, fast

Parity bytes per DS 0, 2, 4, 6, 8, 10, 12, 14, 16

1
Reed-Solomon codeword US 0, 2, 4, 6, 8, 10, 12, 14, 16

DMT symbols per DS 1, 2, 4, 8, 16

1
Reed-Solomon codeword US 1, 2, 4, 8, 16

PSDM, -dBm/Hz DS only 1 dB steps from 40 to 60

Notes:
1. The two R-S parameters can only be provisioned if type of rate adaptation is explicit.
When type of rate adaptation is flexible, the system automatically chooses the R-S
parameters using an optimization algorithm, regardless how the parameters are
provisioned.

ADSL2/ADSL2+ parameters - further settings

Further ADSL transmission parameters, which are provisioned using ADSL2/ADSL2+
transmission profiles (see “Predefined ADSL transmission profiles” (p. 6-128)), are
shown in the following table.

Parameter Direction Default Allowed Values

US=Upstream
DS=Downstream

Type of Rate Adaptation: Flexible Flexible, Dynamic (1)

SNR Margin, dB US and DS 6 dB 0 to 15, in steps of 1

Parameter Direction Default Allowed Values

US=Upstream
DS=Downstream

Upshift SNR Margin, dB US and DS 9 dB 0 to 31, in steps of 0.1

Upshift SNR Margin Time, sec US and DS 60 sec 0 to 16383, in steps of 1

Downshift SNR Margin, dB US and DS 5 dB 0 to 31, in steps of 0.1

Downshift SNR Margin Time, sec US and DS 30 sec 0 to 16383, in steps of 1

Min SNR Margin, dB US and DS 4 dB 0 to 31, in steps of 0.1

Max SNR Margin, dB US and DS 15 dB 0 to 31, in steps of 0.1
3
Max Aggregate Tx Power, dBm ( ) US and DS 10 dBm 0 to 25.5, in steps of 0.1

Max Tx PSD, dBm/Hz US -38 dBm/Hz -60 to -38

DS -40 dBm/Hz -60 to -40

Max Data Rate, kbps US 2048 kbps 64 to 3072, in steps of 32

DS 24000 kbps 64 to 30016, in steps of 32

Min Data Rate, kbps US 384 kbps 64 to 2048, in steps of 32

DS 1024 kbps 64 to 24000, in steps of 32

Interleave, msec US and DS 20 msec 0 to 254, in steps of 1

Latency US and DS interleaved interleaved, fast
Minimum INP (2) US and DS auto auto, no-symbol, half-symbol,
one-symbol, two-symbols

PSD Mask US Default Default, Mask1 to Mask9 (4)

DS Default Default

Enable/Disable READSL2 DS Disabled Disabled, Wide Band, Narrow Band

2
Enable/Disable automatic Power Mgmt ( ) DS Disabled Disabled, Enabled
Min L0 time, sec (2) DS 30 sec 0 to 255, in steps of 1
2
Min L2 time, sec ( ) DS 30 sec 0 to 255, in steps of 1
Max Aggregate Tx Power Reduc., dB (2) DS 1 dBm 0 to 31, in steps of 0.1

Notes:
1. The type of rate adaptation Dynamic is supported only by LPA420 and LPA833.
2. Not supported by LPA420 and LPA833.
3. The only supported value by LPA420 and LPA833 is 10.0 dbm.
4. Mask1 to Mask9 in upstream direction are used when the line is operating in Annex M mode (requires a
compatible modem at the other end). Not supported by LPA438.

Activate Seamless Rate Adaptation

As part of provisioning the ADSL2/ADSL2+ transmission profile (see
“ADSL2/ADSL2+ parameters - further settings ” (p. 6-102)), the technician must
choose a type of rate adaptation. An ADSL2/ADSL2+ port can be provisioned for one
of two rate adaptation modes:
• Flexible
The flexible rate adaptation, is used as rate adaptation during startup and being fix
during showtime.
• Dynamic
The dynamic rate adaptation, is used as rate adaptation during startup and showtime
(corresponds to SRA). If flexible mode is provisioned, SRA is not applicable.
Seamless Rate Adaptation (SRA) enables that in case of changing noise environment
an ADSL2+ line can change the transmission rates dynamically in order to maintain a
minimum SNR margin without retraining the link.
The following parameters are provisionable for SRA in upstream and downstream
direction:
• Upshift SNR Margin - If on the trained link the actual SNR Margin is above this
value for the time provisioned in the corresponding Upshift SNR Margin Time, the
line transceiver will attempt to increase the transmission rate in order to achieve an
SNR margin below this limit. The Upshift SNR Margin value must be greater than
or equal to the target SNR Margin and less than or equal to the Max SNR Margin.
• Upshift SNR Margin time - Specifies for how long the actual SNR margin has to
stay above the Upshift SNR Margin before the transceiver attempts to increase the
transmission rate.
• Downshift SNR Margin - If on the trained link the actual SNR Margin is below
this value for the time provisioned in the corresponding Downshift SNR Margin
Time, the line transceiver will attempt to decrease the transmission rate in order to
achieve an SNR margin above this limit. The Downshift SNR Margin value must
be less than or equal to the target SNR Margin and greater than or equal to the Min
SNR Margin.
• Downshift SNR Margin time - Specifies for how long the actual SNR margin has
to stay below the Downshift SNR Margin before the transceiver attempts to
decrease the transmission rate
Note that the line transmission rate stays within the bounds of the provisioned
minimum and maximum transmission rates of each direction.
Enable/disable automatic power management
The ADSL2/ADSL2+ packs supports the capability to automatically use a power state
depending on data traffic or to force a specific power state.

The following power states are supported:

• L0 - full transmit power and data rate.
• L2 - reduced transmit power and data rate. A transition from L0 to L2 state takes
place when user traffic decreases. A transition from L2 to L0 state takes place
when throughput is needed. The longer the time in L2 state is, the lower the
transmit power becomes.
Transitions between L0 and L2 are transparent to the end user.
• L3 - sleep mode, i.e. no traffic flows. State transitions from L2 to L3 during idle
periods. When traffic flow is needed, it takes about 3 seconds to initialize and
return to L0 (fast startup or short initialization sequence). A full retrain is not
necessary to reach L0 state.
If automatic power management is enabled, the following parameters are provisionable:
• Minimum L0 time interval between L2 exit and next L2 entry - represents the
minimum time between an exit from L2 (into L0 state) and the next entry into the
L2 state. It ranges from 0 to 255 seconds in steps of 1 second.
• Minimum L2 time interval between L2 entry and first L2 trim - represents the
minimum time between an entry into the L2 state and the first power trim in the
L2 state and between 2 consecutive power trims in the L2 state. It ranges from 0 to
255 seconds in steps of 1 second.
• Maximum Aggregate Tx Power Reduction per L2 trim - represents the maximum
aggregate transmit power reduction that can be performed through a single power
trim in the L2 state. It ranges from 0 to 31 dBm in steps of 0.1 dBm.

SHDSL parameters - port settings

Overview
When an SHDSL port is provisioned using the GSI, the technician must select the
following:
• The SNR margin threshold, the SNR target margin (only applicable for flexible rate
adaptation), the loop attenuation threshold, and the annex mode and if the port will
be bonded (see table below).
• A transmission profile (described in “Predefined SHDSL transmission profiles”
(p. 6-132) on ; also see “Setting the bit rate for the SHDSL port using the SHDSL
transmission profile” (p. 6-107).
• A performance management profile (the parameters of which are described in
“SHDSL performance management” (p. 4-65)).
Setting SHDSL port-level parameters
Other parameters that the technician must enter when provisioning an SHDSL port
using the GSI are listed in the following table.

Parameter Description/Allowed Values

SNR Margin Threshold (dB) Threshold for reporting the SNR margin defect. If the actual SNR
margin falls below the threshold, the system sets a standing
condition. The condition is cleared when the actual SNR margin
moves above the threshold. The same threshold is used for both
directions of transmission.
The range for this parameter is 1 dB to 15 dB. A setting of 0
disables the standing condition. The standing condition is not an
alarm. It has a severity of ″information″.
SNR Target Margin (dB) The SHDSL startup algorithm cycles until the SNR target margin
conditions are fulfilled.
The range for this parameter is 0 dB to 15 dB.
Note: SNR Target Margin - SNR Margin Threshold has to be
greater than or equal to 2 dB.
Loop Attenuation Threshold Threshold for reporting the loop attenuation defect. If the actual
(dB) loop attenuation moves above the threshold, the system sets a
standing condition. The condition is cleared when the actual loop
attenuation moves below the threshold. The same threshold is used
for both directions of transmission.
The range for this parameter is 1 dB to 127 dB. A setting of 0
disables the standing condition. The standing condition is not an
alarm. It has a severity of ″information″.
Annex Mode Determines which G.991.2 SHDSL regional specifications are used.
Annex A corresponds to North America, while Annex B corresponds
to Europe.

Parameter Description/Allowed Values

Bonding If this check box is checked (activated for odd numbered ports
only), the odd port and the adjacent even port on the SHDSL AP
are bonded together to work in 4-wire SHDSL mode. The operator
does not need to provision the even port.
If this check box is unchecked each port has to be provisioned
independently from the others (2-wire SHDSL mode).

Setting the bit rate for the SHDSL port using the SHDSL transmission profile
As part of provisioning the SHDSL transmission profile (see “Predefined SHDSL
transmission profiles” (p. 6-132)), the technician must choose a rate adaptation method.
An SHDSL port can be provisioned for one of two rate adaptation methods:
• Flexible
With flexible rate adaptation, maximum and minimum bit rates need to be set (see
next table).
• Explicit
With explicit rate adaptation, only one data rate needs to be set (see next table).
When flexible rate adaptation is chosen, the SHDSL circuits select a bit rate in the
range between the minimum and maximum rates provisioned according to the next
table. Also select the SNR target margin according to the table after the next table. If
the SHDSL circuits cannot operate within the bounds of the provisioned minimum and
maximum rates and the provisioned SNR target margin, then the SHDSL startup
algorithm will cycle until conditions change so that the SHDSL circuits can operate. If
conditions do not change satisfactorily, the algorithm will recycle indefinitely.
Following are possible ways for the technician to change the SHDSL conditions so that
the circuits can operate:
• Change the provisioning
• Make repairs to the a/b pair that carries the SHDSL signal
• Remove interference that may be entering the SHDSL transmission span.
When flexible rate adaptation is chosen, to accommodate various service offerings to
subscribers, the minimum and maximum bit rates can be set as close together as is
desired. The bit rates can even be set to the same values.
When explicit rate adaptation is chosen, the SHDSL circuits select the data rate as
provisioned according to the next table. Note that provisionable SNR target margin
does not apply when explicit rate adaptation has been selected. Similar to flexible rate
adaptation, if the SHDSL circuits cannot operate within the bounds of the provisioned
parameters, then the SHDSL startup algorithm will cycle until conditions change so
that the SHDSL circuits can operate. If conditions do not change satisfactorily, the
algorithm will recycle indefinitely.
The following table shows flexible and explicit rate adaptation, used for SHDSL
transmission.

Type of Rate Parameter Allowed Values

Adaptation
Flexible Maximum bit rate, flexible rate Any multiple of 64 from 192 to
adaptation, Kbps 2304 and 2312
Minimum bit rate, flexible rate Any multiple of 64 from 192 to
adaptation, Kbps 2304 and 2312
Explicit Explicit data rate, Kbps Any multiple of 64 from 192 to
2304

Important! When a bit rate parameter is provisioned to a value that is between two
allowed values, the system automatically sets the parameter to the smaller of the
two allowed values.
The following table shows other SHDSL transmission parameters.

Parameter Allowed values

SNR Target Margin, dB (upstream and Integer between 0 and 15 inclusive
downstream) 1

Notes:
1. Only used with profiles set to flexible rate adaptation.

E1IMA AP settings
...................................................................................................................................................................................................................................

Default settings
When provisioning an E1IMA AP the following is automatically created with default
settings:
• Eight E1 ports with a default failure report profile assigned to them; alarm
reporting of all alarms is set to no reporting
• One logical interface IMA line
• An IMA group with 1 IMA link assigned to E1 port 1.
The E1IMA AP supports the following fixed configuration parameters:
• Line Type
• Line Coding
• Signal Code
• BER Degrade Threshold
These parameters cannot be changed by the operator.

Provisionable E1 pack/port configuration parameters

Provisionable configuration parameters are:
• Performance monitoring
Performance monitoring can be enabled/disabled per pack. Per default setting
performance monitoring is disabled. the performance management thresholds are
provisionable.
• Loopback
Loopbacks can be configured per port.
• Failure report profile
A default failure report profile is assigned to each port. This failure report profile
can be changed.

Provisionable IMA line configuration parameters

The following IMA line configuration parameters can be changed by the operator:
• Up to seven IMA links can be added to the IMA group
• E1 port for transmission changeable from IMA mode to UNI mode
The IMA link then becomes the UNI mode link. When in UNI mode the operator
is allowed to change the E1 port number. But both of these actions are
service-affecting.

• VP/VC Alarm Indication Signal (F4/F5 AIS)

VP/VC AIS can be enabled/disabled per IMA line and applies to all E1 links being
in use (either 1 E1 link, if UNI mode, or up to 8 E1 links, if IMA mode). If AIS is
enabled, AIS will be sent upstream towards the ATM network on affected
VPCs/VCCs when the IMA line goes out of service.
• IMA performance monitoring
IMA performance monitoring is applicable for the IMA group and its links. It can
be enabled or disabled. Per default setting IMA performance monitoring is disabled.
Cell scrambling is supported. It applies to all E1 links being in use and cannot be
disabled.

Provisionable IMA group parameters

The following IMA group configuration parameters can be changed by the operator:
• Failure Report Profile Index (a change is not service-affecting)
• Group Inhibition
• Group Symmetry (a change is service-affecting; it causes reconfiguration)
• Min Number of Tx Links (a change is service-affecting; it causes a restart of the
IMA group)
• Min Number of Rx Links (a change is service-affecting; it causes a restart of the
IMA group)
• Near-end Tx Clock Mode (a change is service-affecting; it causes reconfiguration)
• Tx Amas IMA ID (a change is service-affecting; it causes reconfiguration)
• Tx Frame Length (a change is service-affecting; it causes reconfiguration)
• Max Differential Delay (a change is service-affecting; it causes a restart of the IMA
group)
• Alpha Value (a change is service-affecting; it causes a restart of the IMA group)
• Beta Value (a change is service-affecting; it causes a restart of the IMA group)
• Gamma Value (a change is service-affecting; it causes a restart of the IMA group)
• IMA version (a change is service-affecting; it causes reconfiguration)
For a reconfiguration the outage time may take up to 1 minute.

Provisionable IMA link parameters

The following IMA link configuration parameters can be changed by the operator:
• Failure Report Profile Index (a change is not service-affecting)
• Link Inhibition.

ATM traffic parameters

ATM traffic parameters and allowed values

ATM traffic parameters are shown in the table below. These parameters are part of the
ATM traffic profile; values are assigned to them as part of ATM connection
cross-connect provisioning (see “ATM cross-connect provisioning” (p. 4-13)).

Parameter Allowed Values

Service Category UBR, CBR, rt-VBR,
nrt-VBR
Profile name String of maximum length 64
Peak Cell Rate upstream (cells/sec) 150 to 108940
Peak Cell Rate downstream (cells/sec) 150 to 108940
Sustainable Cell Rate upstream (cells/sec) 150 to 108939
Sustainable Cell Rate downstream (cells/sec) 150 to 108939
Maximum Burst Size upstream (cells) 1 to 100
Maximum Burst Size downstream (cells) 1 to 210
1
PCR CDVT 680 ns to 1.33s
2
SCR CDVT 680 ns to 1.33s
3
Cell Loss Priority CLP=0, CLP=0+1
Cell Tagging True, False
Frame Discard True, False

Notes:
1. In some cases, the system does not use the provisioned value of the PCR CDVT, but
rather, it rounds up to the next highest value based on the formula 2k (1 + m/23 ) × 680 ×
10-6, where the value of k is from 0 to 20 and the value of m is from 0 to 7. The actual
value of PCR CDVT used by the system is reflected in the PCR CDVT-Actual box on the
ATM Traffic Profile Screen on the GSI.
2. The system calculates the sum of Burst Tolerance (BT) and the provisioned value of SCR
CDVT and rounds it up to the next highest value based on the formula 2k (1 + m/23 ) ×
680 × 10-6, where the value of k is from 0 to 20 and the value of m is from 0 to 7. The
BT is calculated from the provisioned value of MBS, SCR and PCR as BT = (MBS - 1)
× (1/SCR - 1/PCR). The actual value of SCR CDVT used by the system is reflected in
the SCR CDVT-Actual box on the ATM Traffic Profile Screen on the GSI.
3. The combination of Cell Tagging = True and Cell Loss Priority = CLP=0+1 is not
allowed for rt-VBR and nrt-VBR.

Parameters in failure report profiles

Parameters used in port specific user defined failure report profiles are shown in the
following table.

ADSL port failure report profile

Failure/Condition Possible values
Parameter Service Affect Report Severity for Alarm
Dying Gasp NSA, SA No, Yes n/a, Ino. MN, MJ
LOS
LOF
HBER
FE-LOS
RFI
FE-HBER
SHDSL port failure report profile
Failure / Condition Possible values
Parameter Service Affect Report Severity for Alarm
LOSW (upstream) NSA, SA No, Yes n/a, Info. MN, MJ
FE-HBER
LOS-W (downstream)
HBER
E1 port failure report profile
LOS NSA, SA No, Yes n/a, Info. MN, MJ, CR
LOF
AIS
RAI
HBER
EquFail
IMA link failure report profile
LIF NSA No, Yes n/a, Ino. MN, MJ, CR
LODS
TxUnusable-FE
RxUnusable-FE
TxMisConn

RxMisConn
IMA group failure report profile
StartupFail-FE NSA, SA No, Yes n/a, Ino. MN, MJ, CR
ConfigAbort
ConfigAbort-FE
InsuffLinks
InsuffLinks-FE
Blocked-FE

VP quality of service
Each VP has an associated service class, CBR, rt-VBR, nrt-VBR, or UBR. The
different Shelf VPs may have different service categories in any combination. A VC
must have the same service class as its shelf VP, defined by the associated ATM traffic
profile. This assures proper quality of service treatment, particularly when
daisychaining. (If the VC has a service class that is different form its VP, it will be
treated as though it has the same service class as the VP).

Default values for ATM xDSL system provisioning

parameters

Purpose
This section provides a summary of the ATM xDSL default provisioning parameter
default values for the AnyMedia ® Access System. The default values are restored when
Initialize System Database is initialized. The exception to this is the IP address of the
10BaseT interface. If this IP address has been changed, the new IP value will persist.

Note
The technician needs to record any changes made to the 10BaseT IP address in order
to allow AnyMedia ® Access System access via that port after any system initialization.
In general, an AFM reboot is necessary after a change in an IP address. The reboot is
automatic after Initialize System Database.
This section first lists the turn-up and service activation provisioning parameter default
values that appear in the Main Shelf Turnup GSI screen. It then lists the default values
contained in the system-predefined profiles for the following:
• ADSL transmission
• SHDSL transmission
• ADSL PM
• SHDSL PM
• ATM traffic.
Finally, this section lists alarm severity default values and predefined failure report
profiles.

Contents

Turn-up and service activation provisioning default values 6-116

Predefined ADSL transmission profiles 6-128
Predefined SHDSL transmission profiles 6-132
Predefined ADSL performance management profiles 6-133
Predefined SHDSL performance management profiles 6-134
Predefined ATM traffic profiles 6-135
Predefined ATM Traffic statistics threshold profiles 6-137
Predefined failure report profiles 6-138
Parameters in DMT profile 6-142

Parameters in RFI notch profiles 6-143

ADSL transmission specification summary 6-144

Turn-up and service activation provisioning default values

Overview
System turn-up and service provisioning establish the shelf parameters that are
common to all of the subscriber connections, and provide the subscriber with ATM
virtual connections. The system Main Shelf Turnup GSI screen indicates the following
main options:
• Communications
• Main Shelf, which includes System Information, Global ATM Parameters, Shelf VP
Information
• Feeder
• Pack
• Port
• Cross-Connect
• IMA.
Each main option has more sub-options, which are used to establish the connections;
these sub options are listed as the subheadings in the following table. The table
indicates the default values for the parameters provided in these GSI screens. The term
Edit is indicated in fields where there are no default values.
Important! The table does not include those GSI fields that are read-only.

Turn-up and service activation default values - Communications tab

The following table shows the turn-up and service activation default values in the
Communications tab.

Parameter Default Value

COMMUNICATIONS TAB
Security ID public
IP Configuration section
10BaseT IP Address 192.168.160.160 (factory set initial value)
10BaseT Subnet Mask 255.255.0.0
ATM IP Address 135.117.134.100
ATM Subnet Mask 255.255.0.0
Console Port IP Address 192.168.0.1
Console Port Subnet Mask 255.255.0.0
10BaseT Default Router 0.0.0.0 (must be provisioned)
Autonomous Message Destination Section
Selected Address 0.0.0.0

Parameter Default Value

Addresses Stored in Memory

Turn-up and service activation default values - Mainshelf tab

The following table shows the turn-up and service activation default values in the
Mainshelf tab.

Parameter Default Value

MAIN SHELF TAB
MAIN SHELF TAB - System Subtab
System Configuration Section
Transmission Mode (AFMO only) SONET
Protection Mode (Does not apply to Simplex
AFME1)
Timing Source (AFMO only) Line-Timed
Distribution Port Numbering Mode Physical
AFM configuration xDSL
Customer Configuration 1
Main Shelf Type AnyMedia AS
High BER Algorithm Fixed CRC Threshold
System Information Section
Contact Edit
Location Edit
Main Shelf Misc. Information Edit
System Identification Section
System Identification
MAIN SHELF TAB - Global ATM Parameters Subtab
Parameters Section
ATM Operations Channel VPI 254
ATM Operations Channel VCI 32
ATM Operations Channel F5 EtoE CC Disabled

Parameter Default Value

Shelf PCR (cells/sec) Upstream 80000 for E3,
104000 for DS3 with direct cell mapping
96000 for DS3 with PLCP framing
4384 for E1
353,200 for STM-1/OC-3
Shelf PCR (cells/sec) Downstream 80000 for E3,
104000 for DS3 with direct cell mapping
96000 for DS3 with PLCP framing
4384 for E1 353,200 for STM-1/OC-3c
Service Category Section
Shelf Overbooking Factor CBR=1
rt-VBR=1
nrt-VBR=1
Guaranteed Bandwidth upstream (cells/s) CBR=16 for a feeder on an AFME3/DS3
or an AFMO
CBR=4 for an E1-IMA feeder
rt-VBR=0
nrt-VBR=0
Admissible Bandwidth upstream and For CBR, rt-VBR, and nrt-VBR equal to
downstream (cells/s) Shelf PCR minus the bandwidth reserved
for the BB ATM Operations Channel
Cell Loss Ratio (10 -9) 1
CBR=1
rt-VBR=10,000
nrt-VBR=10,000
Traffic Statistics Thresholds Section
Timing Interval 15 Minutes
Cells Dropped due to PPD 1000
Cells Dropped due to EPD 1000
Cells Dropped due to Buffer Overflow 1000
AAL5 Frames Dropped due to EPD 1000
MAIN SHELF TAB - Feeder VP Provisioning Subtab
New Shelf VP Information Section
Shelf VPs Remaining Non-editable parameter
Max Highest VCI Allowed for New Shelf Non-editable parameter
VP
Specific Feeder VP Information Section

Parameter Default Value

VPI Edit (one default Shelf VP with VPI=255)
VP Type Edit (one default Shelf VP with VPI=255)
Service Category Edit (UBR for default Shelf VP)
Highest VCI Allowed Edit (1999 for default Shelf VP)
F4 VP Segment Disabled
F4 Segment CC Disabled
F4 End-to-End CC Disabled
CC Cell Flows Remaining Non-editable parameter
Highest VCI Used Non-editable parameter
Max Highest VCI Allowed for Existing Non-editable parameter
Shelf VP
Global Downstream VP Provisioning Section
Enable AIS for All Downstream VPs Disabled

Notes:
1. For all shelves in a daisy chain, the CLR parameters must be provisioned so that the
value provisioned for any individual shelf equals the value provisioned for each of the
other shelves; that means, the CLR parameter on the first shelf must have the same value
as the CLR parameter on each of the other shelves.

Turn-up and service activation default values - Feeder tab

The following table shows the turn-up and service activation default values in the
Feeder tab.

Parameter Default Value

FEEDER TAB (for E3 Feeder Type)
Feeder Port Edit
Feeder Type Non-editable parameter
FEEDER TAB - Feeder Port Parameters Subtab (for E3 Feeder Type) - when Feeder
Port 1 is selected
Administrative State Always enabled for Port 1
Timing Source Free running
Cell Scrambling Enabled
Single Bit Error Correction Enabled
Frame Format Not applicable for E3
Line Length Not applicable for E3

Parameter Default Value

Expected API AMAS TTI
Transmitted API AMAS TTI
Accepted API Not applicable
Trailtrace Alarm Enable True
PM Enable Unchecked
FEEDER TAB - Feeder Port Parameters Subtab (for E3 Feeder Type) - when Feeder
Port 2 is selected
Administrative State Disabled
Timing Source Not applicable for port 2
All other parameters are the same as for
port 1
FEEDER TAB - Performance Monitoring Thresholds Subtab (for E3 Feeder Type) -
when Feeder Port 1 is selected
Timing Interval Edit
P-bit Severely Errored Seconds Not applicable for E3
Unavailable seconds 10
Errored seconds 972 when timing interval set to 24 hours;
180 when timing interval set to 15
minutes.
FEEDER TAB - Performance Monitoring Thresholds Subtab (for E3 Feeder Type) -
when Feeder Port 2 is selected
These parameters are the same as for port 1
FEEDER TAB (for DS3 Feeder Type)
FEEDER TAB - Feeder Port Parameters Subtab (for DS3 Feeder Type) - when Feeder
Port 1 is selected
Administrative State Always enabled for Port 1
Timing Source Free running
Cell Scrambling Enabled
Single Bit Error Correction Enabled
Frame Format HEC (direct cell mapping)
Line Length 0-224 ft. (0-68 meters)
Expected API Not applicable for DS3
Transmitted API Not applicable for DS3
Accepted API Not applicable for DS3
Trailtrace Alarm Enable Not applicable for DS3
PM Enable Unchecked

Parameter Default Value

FEEDER TAB - Feeder Port Parameters Subtab (for DS3 Feeder Type) - when Feeder
Port 2 is selected
Administrative State Disabled
Timing Source Not applicable for port 2
All other parameters are the same as for port 1
FEEDER TAB - Performance Monitoring Thresholds Subtab (for DS3 Feeder Type) -
when Feeder Port 1 is selected
Timing Interval Edit
P-bit Severely Errored Seconds 40 when timing interval set to 24 hours; 4
when timing interval set to 15 minutes.
Unavailable Seconds 10
Errored seconds Not applicable for DS3
FEEDER TAB - Performance Monitoring Thresholds Subtab (for DS3 Feeder Type) -
when Feeder Port 2 is selected
These parameters are the same as for port 1
FEEDER TAB (for E1 Feeder Type)
FEEDER TAB - Feeder Port Parameters Subtab (for E1 Feeder Type)
Administrative State OOS, except for UNI mode
Operational Port State Non-editable parameter
Transmit Clock Source Non-editable parameter
FEEDER TAB - Timing Source Subtab (for E1 Feeder Type)
Timing Source Status Non-editable parameter
Primary Timing Source 1
Secondary Timing Source 2
FEEDER TAB - Failure Thresholds Subtab (for E1 Feeder Type)
Timing Interval Edit
Errored Seconds 1728 when timing interval set to 24 hours;
120 when timing interval set to 15
minutes.
Severely Errored Seconds 86 when timing interval set to 24 hours;
15 when timing interval set to 15 minutes.
Unavailable seconds 10 when timing interval set to 24 hours;
3 when timing interval set to 15 minutes.
(Feeder Provisioning for OC-3c Feeder Type) LOGICAL FEEDER TAB
General Info Section

Parameter Default Value

Administrative State Out of Service (Port 2 only) 1.
Facility Protection Mode Duplex 1+1
Path RDI Code One-Bit RDI-P code
Path Trace
Transmitted API
Expected API
API Monitor Disabled
(Feeder Provisioning for OC-3c Feeder Type) PHYSICAL FEEDER TAB
Physical Feeder Info Section
2
Line Name Port 16-1 Working
Port 16-2 Working
Port 15-1 Protection
Port 15-2 Protection
External Conditions Section
Loopback (port 1 only) No Loop
Loopback Duration (port 1 only) 15 Minutes
Section Trace Section
Trace Mode Unspecified
Transmitted API AnyMedia_Access
Expected API AnyMedia_Access
API Monitor Disabled
(Feeder Provisioning for OC-3c Feeder Type) BER THRESHOLDS TAB
Line Signal Degrade Threshold 10 -6
Line Signal Fail Threshold 10 -3
(Feeder Provisioning for STM-1 Feeder Type) LOGICAL FEEDER TAB
General Info Section
Administrative State Out of Service (Port 2 only). 1
Path RDI Code One-Bit RDI-P code
(Feeder Provisioning for STM-1 Feeder Type) PHYSICAL FEEDER TAB
Physical Feeder Info Section
2
MS Named Port 16-1 Working
Port 16-2 Working
Port 15-1 Protection
Port 15-2 Protection

Parameter Default Value

External Conditions Section
Loopback (port 1 only) No Loop
Loopback Duration (port 1 only) 15 Minutes
RS Trace Section
Trace Mode Unspecified
Transmitted API AnyMedia_Access
Expected API AnyMedia_Access
API Monitor Disabled
FEEDER TAB - BER Thresholds Subtab (for STM-1 Feeder Type
MS Signal Degrade Threshold 10 -6
MS Signal Fail Threshold 10 -3

Notes:
1. The administrative state of Feeder Port 1 is always in service; it is not provisionable.
2. Line Name applies only when the shelf is provisioned for duplex protection mode.

Turn-up and service activation default values - Pack tab

The following table shows the turn-up and service activation default values in the Pack
tab.

Parameter Default Value

PACK PROVISIONING TAB
Shelf Main Shelf
Slot Number Edit
Pack Type Edit
Configured State Edit

Turn-up and service activation default values - Port tab

The following table shows the turn-up and service activation default values in the Port
tab.

Parameter Default Value

PORT PROVISIONING TAB
Shelf Edit
Slot Number Edit

Parameter Default Value

Port Number Edit
Service State Edit
Startup Mode (ADSL only) Multimode
ATM xDSL Transmission Profile Edit
PM Profile Edit
SNR Margin Threshold (SHDSL only) Edit
Loop Attenuation Threshold (SHDSL Edit
only)
Annex Mode (SHDSL only) Edit
Enable AIS Disabled
Bonding (SHDSL only; can be enabled for Disabled
odd numbered ports only)

Turn-up and service activation default values - Cross Connect tab

The following table shows the turn-up and service activation default values in the
Cross Connect tab.

Parameter Default Value

CROSS CONNECT TAB
CROSS CONNECT TAB - xDSL Subtab
Feeder Section
Type Non-editable parameter
VPI Edit
VCI Edit
F4 Segment (only when VP not equal to Disabled
shelf VP)
F4 Segment CC (only when VP not equal Disabled
to shelf VP)
F5 Segment (only when VP equal to shelf Disabled
VP)
F5 Segment CC (only when VP equal to Disabled
shelf VP)
Highest VCI Allowed Non-editable parameter
Subscriber Section
Shelf Main Shelf

Parameter Default Value

Slot Edit
Port Edit
VPI Edit
VCI (if applicable) Edit
Circuit ID Edit
ATM Traffic Profile Edit
Threshold Profile Edit
Script Mode Disabled

Turn-up and service activation default values - IMA tab

The following table shows the turn-up and service activation default values in the IMA
tab.

Parameter Default Value

IMA tab (used with the AFME1 or with E1IMA AP only)
Shelf Mainshelf
Slot Number Edit
IMA Group 1
IMA Mode Non-editable parameter
PM Enable Disabled
AIS Disabled
Cell Scramble Enabled
USUsedEffBW Non-editable parameter
DSUsedEffBW Non-editable parameter
USFreeBW Non-editable parameter
DSFreeBW Non-editable parameter
IMA tab - UNI Mode Subtab
UNI Mode Link #1
IMA TAB - IMA Group Subtab
Provisioned Protocol Version 1.0
IMA Group Configuration Section
Symmetry Mode Symmetric configuration and symmetric
operation
Sufficient Tx Links 1

Parameter Default Value

Sufficient Rx Links 1
Tx Frame Length 128 cells
Tx AMAS IMA ID 1
Tx Clocking Mode common
Maximum Differential Delay 25 ms
Synchronization Parameters: Alpha 2
Synchronization Parameters: Beta 2
Synchronization Parameters: Gamma 1
Failure Report Profile 1015 - IMA group default profile
IMA TAB - IMA Link Subtab
IMA Link Configuration Section
Link Edit
Failure Report Profile 1020 - IMA link default profile
IMA TAB - IMA PM Thresholds Subtab
IMA Group PM Thresholds Section
Timing Interval Edit
UAS 3 seconds (for 15-minute interval) 10
seconds (for 24-hour interval)
FC 90 failures (for 15-minute interval) 900
failures (for 24-hour interval)
IMA Link PM Thresholds Section
Timing Interval Edit
IV 128 ISP cells (for 15-minute interval) 512
ISP cells (for 24-hour interval)
SES 10 seconds (for 15-minute interval) 100
seconds (for 24-hour interval)
UAS 10 seconds (for 15-minute interval) 100
seconds (for 24-hour interval)
Tx USS 10 seconds (for 15-minute interval) 100
seconds (for 24-hour interval)
Rx USS 10 seconds (for 15-minute interval) 100
seconds (for 24-hour interval)

ATM traffic statistics parameters (default values)

The following table shows the default values for the ATM traffic statistics parameters.

Parameter Default Value

15-minute period 24-hour period
Shelf Level Thresholds
Upstream direction
Cells Dropped due to PPD 1000 cells 1 × 10 6 cells
Cells Dropped due to EPD 1000 cells 1 × 10 6 cells
Cells Dropped due to Buffer 1000 cells 1 × 10 6 cells
Overflow
AAL5 Frames Dropped due to EPD 1000 frames 1 × 10 6 frames
Connection Level Thresholds (set via profiles, see “Predefined ATM Traffic statistics
threshold profiles” (p. 6-137))

Predefined ADSL transmission profiles

Overview
The AnyMedia ® Access System contains a library of several predefined ADSL default
transmission profiles. These profiles cannot be deleted or edited. The predefined
profiles are:
• 1 - ADSL-Default Lite Flexible-1
• 2 - ADSL-Default Full Flexible-1
• 3 - ADSL-Default Lite Explicit-1
• 4 - ADSL-Default Full Explicit-1
• 122 - ADSL-Default Lite Flexible-2
• 123 - ADSL-Default Full Flexible-2
• 124 - ADSL-Default Lite Explicit-2
• 125 - ADSL-Default Full Explicit-2
• 129 - ADSL2/ADSL2PLUS Default.

Predefined ADSL transmission profiles

The parameter values for the predefined ADSL transmission profiles listed above are
provided in the following three tables.

Parameter Direction 1-ADSL- 2-ADSL- 3-ADSL- 4-ADSL-

DS=Downstream Default Lite Default Full Default Lite Default Full
US=Upstream Flexible-1 Flexible-1 Explicit-1 Explicit-1

Type of rate adaptation DS and US Flexible Flexible Explicit Explicit

Maximum bit rate, kbps DS 4480 9984 N/A N/A

US 1024 1024
Minimum bit rate, kbps DS 64 64 N/A N/A

US 64 64

Option 1 bit rate, kbps DS N/A N/A 4480 8160

Option 2 bit rate, kbps 3072 7168

Option 3 bit rate, kbps 1792 4352

Option 4 bit rate, kbps 384 1536

Option 1 bit rate, kbps US N/A N/A 1024 1024

Option 2 bit rate, kbps 736 736

Option 3 bit rate, kbps 448 448

Option 4 bit rate, kbps 128 160

Interleave depth DS 1 1 1 1
US 1 1 1 1

Latency DS and US Interleave Interleave Interleave Interleave

Parameter Direction 1-ADSL- 2-ADSL- 3-ADSL- 4-ADSL-

DS=Downstream Default Lite Default Full Default Lite Default Full
US=Upstream Flexible-1 Flexible-1 Explicit-1 Explicit-1

Parity bytes per R-S DS 2 2 4 4

codeword
US 2 2 4 4
DMT symbols per R-S DS 1 1 1 1
codeword
US 1 1 1 1

PSDM, – dBm/Hz DS only 40 40 40 40

Parameter Direction 122-ADSL- 123-ADSL-Default 124-ADSL- 125-ADSL-

DS=Downstream Default Lite Full Flexible-2 Default Lite Default Full
US=Upstream Flexible-2 Explicit-2 Explicit-2

Type of rate DS and US Flexible Flexible Explicit Explicit

adaptation
Maximum bit rate, DS 4480 9984 N/A N/A
kbps
US 1024 1024

Minimum bit rate, DS 1024 1024 N/A N/A

kbps
US 384 384
Option 1 bit rate, DS N/A N/A 4608 8160
kbps

Option 2 bit rate, 4480 8160

kbps
Option 3 bit rate, 3072 7168
kbps
Option 4 bit rate, 1792 4352
kbps
Option 1 bit rate, US N/A N/A 1152 1152
kbps

Option 2 bit rate, 1024 1024

kbps

Option 3 bit rate, 736 736

kbps
Option 4 bit rate, 448 448
kbps

SNR margin, dB DS 4 6 4 6
US 4 6 4 6

Interleave depth DS 1 1 1 1

US 1 1 1 1

Latency DS and US Interleave Interleave Interleave Interleave

Parity bytes per R-S DS 2 2 4 4

codeword
US 2 2 4 4
DMT symbols per R-S DS 1 1 1 1
codeword
US 1 1 1 1

Parameter Direction 122-ADSL- 123-ADSL-Default 124-ADSL- 125-ADSL-

DS=Downstream Default Lite Full Flexible-2 Default Lite Default Full
US=Upstream Flexible-2 Explicit-2 Explicit-2

PSDM, – dBm/Hz DS only 40 40 40 40

This table shows the ADSL2/ADSL2+ transmission profile (ADSL2/ADSL2PLUS

Default)

Parameter Direction Default Allowed Values

US=Upstream
DS=Downstream

Type of Rate Adaptation: Flexible Flexible, Dynamic (1)

SNR Margin, dB US and DS 6 dB 0 to 15, in steps of 1

Upshift SNR Margin, dB US and DS 9 dB 0 to 31, in steps of 0.1

Upshift SNR Margin Time, sec US and DS 60 sec 0 to 16383, in steps of 1

Downshift SNR Margin, dB US and DS 5 dB 0 to 31, in steps of 0.1

Downshift SNR Margin Time, sec US and DS 30 sec 0 to 16383, in steps of 1

Min SNR Margin, dB US and DS 4 dB 0 to 31, in steps of 0.1

Max SNR Margin, dB US and DS 15 dB 0 to 31, in steps of 0.1

3
Max Aggregate Tx Power, dBm ( ) US and DS 10 dBm 0 to 25.5, in steps of 0.1
Max Tx PSD, dBm/Hz US -38 dBm/Hz -60 to -38

DS -40 dBm/Hz -60 to -40

Max Data Rate, kbps US 2048 kbps 64 to 3072, in steps of 32

DS 24000 kbps 64 to 30016, in steps of 32

Min Data Rate, kbps US 384 kbps 64 to 2048, in steps of 32
DS 1024 kbps 64 to 24000, in steps of 32

Interleave, msec US and DS 20 msec 0 to 254, in steps of 1

Latency US and DS interleaved interleaved, fast

Minimum INP (2) US and DS auto auto, no-symbol, half-symbol,
one-symbol, two-symbols

PSD Mask US Default Default, Mask1 to Mask9 (4)

Enable/Disable READSL2 DS Disabled Disabled, Wide Band, Narrow Band

Enable/Disable automatic Power Mgmt (2) DS Disabled Disabled, Enabled

2
Min L0 time, sec ( ) DS 30 sec 0 to 255, in steps of 1
Min L2 time, sec (2) DS 30 sec 0 to 255, in steps of 1
2
Max Aggregate Tx Power Reduc., dB ( ) DS 1 dBm 0 to 31, in steps of 0.1

Notes:
1. The Type of rate adaptation Dynamic is supported only by LPA420 and LPA833 .
2. Not supported by LPA420 and LPA833.
3. The only supported value by LPA420 and LPA833 is 10.0 dbm.

4. Mask1 to Mask9 in upstream direction are used when the line is operating in Annex M mode (requires a
compatible modem at the other end). Not supported by LPA438.

Following installation of ADSL APs and selecting an ADSL transmission profile per
the Pack and Port screens, the ADSL Transmission Profiles screen allows reviewing or
changing ADSL parameters and creating a new profile. For details on generating new
profiles, see the AnyMedia ® Access System, Commands and Procedures for ATM xDSL
services.

Predefined SHDSL transmission profiles

Overview
The AnyMedia ® Access System contains three predefined SHDSL Default Transmission
Profiles. These profiles cannot be deleted or edited.

Predefined SHDSL transmission profiles - values

The following table shows the default parameter values in these predefined SHDSL
transmission profiles.

Parameter Predefined SHDSL Transmission Profiles

120 - SHDSL- Default 121 - SHDSL- Default
Flexible Explicit
Minimum Bit Rate, kbps 192 N/A
Maximum Bit Rate, kbps 2304 N/A
Bit Rate N/A 1152
1
SNR Margin (dB) 6 N/A

Notes:
1. For upstream and downstream.

Following installation of SHDSL APs and selecting an SHDSL transmission profile per
the Pack and Port screens, the SHDSL Transmission Profiles screen allows reviewing
or changing SHDSL parameters and creating a new profile. For details on generating
new profiles, see the AnyMedia ® Access System, Commands and Procedures for ATM
xDSL Services.

Predefined ADSL performance management profiles

Overview
The AnyMedia ® Access System provides a library of two predefined ADSL
performance management (PM) profiles. These profiles cannot be deleted or edited. In
Default PM Profile 1, all TCAs are set to zero. In Default PM Profile 2, all TCAs are
set to the default values.

Predefined ADSL performance management profiles - values

This table shows the predefined ADSL PM profiles.

Parameter Default Values

1 - Default 1: All ADSL TCAs All TCAs disabled (that means, set to zero)
Disabled
2 - Default 2: ADSL TCAs Enabled Thresholds set to the default values in the next
table.

This table shows the values of the predefined ADSL PM profile 2 - Default 2: ADSL
TCAs enabled

Downstream Default Upstream Default

Performance Parameters Performance Parameters
15 Minutes ES 10 15 Minutes ES 10
HBER 2 HBER 2
LOS 2 LOS 2
RFI fault 2 LOF fault 2
1 Day ES 100 1 Day ES 100
HBER 10 HBER 10
LOS 10 LOS 10
RFI 10 LOF fault 10

New ADSL PM profiles can be generated as required. For details on generating new
profiles, see the AnyMedia ® Access System, Commands and Procedures for ATM xDSL
Services.

Predefined SHDSL performance management profiles

Overview
The AnyMedia ® Access System provides a library of two predefined SHDSL PM
profiles. These profiles cannot be deleted or edited. In Default PM Profile 1, all TCAs
are set to zero. In Default PM Profile 2, all TCAs are set to the default values.

Predefined SHDSL performance management profiles

This table shows the predefined SHDSL PM profiles

Profile Identifier Default Values

126 - Default 1: All SHDSL TCAs All TCAs disabled (i.e., set to zero)
Disabled
125 - Default 2: SHDSL TCAs Thresholds set to the default values in the next
Enabled table.

This table shows the predefined SHDSL PM Profile 125 - Default 2: SHDSL TCAs
enabled.

Downstream Default Upstream Default

Performance Performance Parameters
Parameters
15 Minutes ES 10 15 Minutes ES 10
SES 20 SES 20
UAS 20 UAS 20
1 Day ES 100 1 Day ES 100
SES 100 SES 100
UAS 100 UAS 100

New SHDSL PM profiles can be generated as required. For details on generating new
profiles, see the AnyMedia ® Access System, Commands and Procedures for ATM xDSL
Services.

Predefined ATM traffic profiles

Overview
The AnyMedia ® Access System provides a library of eight predefined ATM traffic
profiles, four for ADSL and four for SHDSL. These profiles cannot be deleted or
edited.

Predefined ATM traffic profiles for ADSL

This table shows the predefined ATM traffic profiles for ADSL.

Predefined ATM Traffic Profiles

Parameter 1 - ADSL UBR 2 - ADSL CBR 3 - ADSL rt-VBR 4 - ADSL nrt-VBR

Peak Cell Rate upstream 905 905 1810 1810

(cells/sec)
Peak Cell Rate 2415 2415 4830 4830
downstream (cells/sec)

Sustainable Cell Rate - - 905 905

upstream (cells/sec)
Sustainable Cell Rate - - 2415 2415
downstream (cells/sec)
Maximum Burst Size - - 32 32
upstream (cells)
Maximum Burst Size - - 32 32
downstream (cells)
PCR CDVT (millisec) 4.7872 4.7872 4.7872 4.7872
SCR CDVT (millisec) - - 4.7872 4.7872

Cell Loss Priority - - clp0+1 clp0+1

Cell Tagging True - False False
Frame Discard True - True True

Predefined ATM Traffic Profiles for SHDSL

Predefined ATM Traffic Profiles

Parameter 509-SDSL/SHDSL 510-SDSL/SHDSL CBR 511-SDSL/SHDSL 512-SDSL/SHDSL

UBR rt-VBR nrt-VBR

Peak Cell Rate upstream 784 784 1568 1568

(cells/sec)

Peak Cell Rate 784 784 1568 1568

downstream (cells/sec)
Sustainable Cell Rate - - 784 784
upstream (cells/sec)

Predefined ATM Traffic Profiles

Parameter 509-SDSL/SHDSL 510-SDSL/SHDSL CBR 511-SDSL/SHDSL 512-SDSL/SHDSL

UBR rt-VBR nrt-VBR

Sustainable Cell Rate - - 784 784

downstream (cells/sec)
Maximum Burst Size - - 32 32
upstream (cells)

Maximum Burst Size - - 32 32

downstream (cells)
PCR CDVT (millisec) 4.7872 4.7872 4.7872 4.7872

SCR CDVT (millisec) - - 4.7872 4.7872

Cell Loss Priority - - clp0+1 clp0+1

Cell Tagging True - False False

Frame Discard True - True True

New ATM traffic profiles for ADSL, or SHDSL can be generated as required. For
details on generating new profiles, see the AnyMedia ® Access System, Commands and
Procedures for ATM xDSL Services.

Predefined ATM Traffic statistics threshold profiles

Overview
The AnyMedia ® Access System provides ATM traffic statistics threshold profiles on:
• Shelf level (upstream) and on
• Connection level (upstream).

ATM traffic statistics threshold profile on shelf level

The following predefined ATM traffic statistics threshold profile is provided for
shelf-level traffic statistics collection (in upstream direction):

Parameter 1 - Threshold default

Parameter value Parameter value
15-minute period 24-hour period
Total number of cells dropped due to 1 × 103 cells 1 × 106 cells
PPD
Total number of cells dropped due to 1 × 10 3 cells 1 × 106 cells
EPD
Total number of AAL5 frames dropped 1 × 10 3 frames 1 × 106 frames
due to EPD
Total number of cells lost due to buffer 1 × 10 3 cells 1 × 106 cells
overflow

ATM traffic statistics threshold profile on connection level

This table shows the predefined ATM traffic statistics threshold profile provided for
connection-level traffic statistics collection (in upstream direction). It is assigned by
default to all newly created cross connections.

Parameter 1 - Threshold default

Parameter value Parameter value
15-minute 24-hour period
period
Number of cells tagged by the AFM (does not 3 × 103 cells 3 × 106 cells
apply to ATM Operations Channel traffic
statistics)
Number of cells dropped due to policing 3 × 10 3 cells 3 × 106 cells
(does not apply to ATM Operations Channel
traffic statistics)

Predefined failure report profiles

Overview
Provisionable failure reporting is used for application pack ports. Port alarm severities
are provisionable. They can be set to:
• Information
• Minor
• Major
• Critical
• No report
One default profile exists with all arms switched off. (When upgrading from previous
releases to R1.23 or higher, this default profile is assigned to all provisioned ports.)
The following service dependent failure report profiles are predefined:
• Predefined default failure report profiles for ADSL ports
• Predefined default failure report profiles for SHDSL ports
• Predefined default failure report profiles for E1 ports
• Predefined default failure report profiles for IMA groups
• Predefined default failure report profiles for IMA links.

ADSL port predefined default failure report profile

The following table shows the predefined default failure report profile for SHDSL
ports.

ADSL port predefined default failure report profile

Failure/Condition Service Affect Report Severity for Alarm
Dying Gasp NSA No n/a
SA
LOS NSA
SA
LOF NSA
SA
HBER NSA
SA
FE-LOS NSA
SA
RFI NSA
SA
FE-HBER NSA
SA

SHDSL port predefined default failure report profile

The following table shows the predefined default failure report profile for SHDSL
ports.

SHDSL port predefined default failure report profile

Failure/Condition Service Affect Report Severity for Alarm
LOSW (upstream) NSA No n/a
SA n/a
FE-HBER NSA n/a
SA n/a
LOSW (downstream) NSA n/a
SA n/a
HBER NSA n/a
SA n/a

E1 port predefined default failure report profile

The following table shows the predefined default failure report profile for E1 ports.

E1 port predefined default failure report profile

Failure/Condition Service Affect Report Severity for Alarm
LOS NSA No n/a
SA n/a
LOF NSA n/a
SA n/a
AIS NSA n/a
SA n/a
RAI NSA n/a
SA n/a
HBER NSA n/a
SA n/a
EquFail NSA n/a
SA n/a

IMA link predefined default failure report profile

The following table shows the predefined default failure report profile for the IMA
link.

IMA link predefined default failure report profile

Failure/Condition Service Affect Report Severity for Alarm
LIF NSA No n/a
LODS
TxUnusable-FE
RxUnusable-FE
TxMisConn
RxMisConn

IMA group predefined default failure report profile

The following table shows the predefined default failure report profile for the IMA
group.

IMA group predefined default failure report profile

Failure/Condition Service Affect Report Severity for Alarm
StartupFail-FE NSA No n/a
SA No n/a
ConfigAbort NSA No n/a
SA No n/a
ConfigAbort-FE NSA No n/a
SA No n/a
InsuffLinks NSA No n/a
SA No n/a
InsuffLinks-FE NSA No n/a
SA No n/a
Blocked-FE NSA No n/a
SA No n/a

Parameters in DMT profile

Overview
ADSL2/ADSL2+ provides the opportunity to define the range of upstream bins and
downstream bins. Furthermore the user can enable or disable dedicated bins with the
GSI. The table below presents the parameter range of this feature.
Note that currently only the non-overlapped mode is supported, i.e. the upstream range
is restricted to 6-31 and the downstream range is restricted to 32-511.
The table below shows the parameter range for DTM profiles.

Parameter Allowed and default values

Upstream Default Downstream Default
DMT Start Bin 0 - 63 6 32 - 511 32
DMT End Bin 0 - 63 31 32 - 511 255
DMT Configured Bins 0 - 63 all bin enabled 32 - 511 all bin enabled

Parameters in RFI notch profiles

Overview
The RFI notching profile can be used to define the frequency breakpoints for insertion
of notches in the standard ADSL2+ transmit power spectral mask. It is applicable only
to the signal transmitted by the ATU-C.
Default values of the downstream PSD mask for RFI notching:

DS mask Breakpoints Comment

default-mask - - indicates that no
RFI notch is to be
applied to the
downstream signal.
mask-1 t(1) = subcarrier 400 PSD = -46.7 dBm/Hz Specifies notches on
t(2) = subcarrier 419 PSD = -75.0 dBm/Hz bands:
• RFI Band 1
t(3) = subcarrier 429 PSD = -75.0 dBm/Hz
1,810 kHz to
t(4) = subcarrier 448 PSD = -47.2 dBm/Hz 1,850 kHz
t(5) = subcarrier 485 PSD = -47.5 dBm/Hz • RFI Band 2
2,173.5 kHz to
t(6) = subcarrier 504 PSD = -75.0 dBm/Hz 2,190.5 kHz
t(7) = subcarrier 508 PSD = -75.0 dBm/Hz
t(8) = subcarrier 511 PSD = -70.5 dBm/Hz
mask-2 t(1) = subcarrier 233 PSD = -95.0 dBm/Hz mask-2 provides
t(2) = subcarrier 260 PSD = -36.5 dBm/Hz notch on the ADSL1
portion of the
t(3) = subcarrier 400 PSD = -46.7 dBm/Hz spectrum.
t(4) = subcarrier 419 PSD = -75.0 dBm/Hz For non RFI
t(5) = subcarrier 429 PSD = -75.0 dBm/Hz notching capable
packs, this field
t(6) = subcarrier 448 PSD = -47.2 dBm/Hz
must be set to
t(7) = subcarrier 485 PSD = -47.5 dBm/Hz default-mask. If not,
t(8) = subcarrier 504 PSD = -75.0 dBm/Hz a non-supported
capability alarm will
t(9) = subcarrier 508 PSD = -75.0 dBm/Hz be issued.
t(10) = subcarrier 511 PSD = -70.5 dBm/Hz

ADSL transmission specification summary

Overview
The table below presents the transmission performance data for the ADSL interface of
the. Unless otherwise stated, transmission specifications apply between the ADSL AP
and the CPE (ADSL transceiver unit - remote end).
ADSL interface transmission specifications of the AnyMedia ® Access System

Parameter Performance
Modulation Discrete multitone (DMT)
Transmission rates on CSA Rate adaptation: explicit
loops (performance with or flexible
impairments per ANSI T1.413
and ITU-T G.992.2)
Downstream, kbps Full-rate ADSL 6144 maximum
ADSL-lite 1536 maximum
Upstream, kbps Full-rate ADSL 640 maximum
ADSL-lite 512 maximum
Output impedance 100 ohms
Longitudinal balance > 40 dB from 30 kHz to
(measured per ANSI T1.413) 1104 kHz
Transmit power spectral Full-rate ADSL, –36.5 dBm/Hz
density, inband, peak downstream, 26 kHz to
1104 kHz
ADSL-lite, downstream, –36.5 dBm/Hz
138 kHz to 552 kHz
Full-rate ADSL, upstream, –34.5 dBm/Hz
26 kHz to 138 kHz
ADSL-lite, upstream, 26 kHz –34.5 dBm/Hz
to 138 kHz
Transmit power spectral Full-rate ADSL, < 4 kHz
density, out-of-band, peak downstream (measured –97.5 dBm/Hz
per ANSI T1.413)
> 3093 kHz –90 dBm/Hz
ADSL-lite, downstream < 4 kHz –97.5 dBm/Hz
(measured per ITU-T G.992.2)
> 2290 kHz –90 dBm/Hz
Full-rate ADSL, upstream < 4 kHz –97.5 dBm/Hz
(measured per ANSI T1.413)
> 307 kHz –90 dBm/Hz

Parameter Performance
ADSL-lite, upstream < 4 kHz –97.5 dBm/Hz
(measured per ITU-T G.992.2)
> 307 kHz –90 dBm/Hz
ADSL performance in presence Per ANSI T1.413,
of impulse noise and VF Category I
interferers
Direct current (DC) loop £ 25 W
resistance added by each
splitter
Insertion loss added by each £ 1.0 dB at 1004 Hz
splitter
VF attenuation distortion Maximum variation, 1.5
added by each splitter dB, 0.2 kHz to 3.4 kHz,
relative to 1004 Hz

Alarm severity values

Alarm severity and GSI ATM xDSL identifiers tables

Overview
This section shows the GSI ATM xDSL identifiers table related to the alarm strings,
the alarm strings and the alarm severity values.
In principle the alarms for the AnyMedia ® LAG 4300 Shelf application and the
AnyMedia ® ETSI V5 Shelf application are the same. But due to the different slot
designations, the GSI identifier are different.

GSI ATM xDSL identifiers

This table contains the GSI identifiers used in alarm messages which are displayed on
the GSI. The GSI identifiers for the AnyMedia ® LAG 4300 Shelf are marked by angle
brackets in the table.

GSI Identifier Explanation Entity Type

Identifiers for entity types where alarm severity provisioning is applicable
ap-1-{1-15} ap-{shelf#}-{slot#} Application pack
<ap-1-{2-24}>
<ap-1-{26-43>
ap-1-(1-14)-(1-8) ap-{shelf#}-{slot#}-{port#} E1 port on an E1IMA AP
<ap-1-(3-24)-(1-8)>
<ap-1-(27-43)-(1-8>)
ap-1-(1-14)-1 ap-{shelf#}-{slot#}-IMA group IMA group on an E1IMA AP
<ap-1-(3-24)-1>
<ap-1-(27-43)-1>
ap-1-(1-14)-(1-8) ap-(shelf#)-{slot#}-(IMA link#) IMA link on an E1IMA AP
<ap-1-(3-24)-(1-8)
<ap-1-(27-43)-(1-8)
pfp-1-{15-16}-{1-2} pfp-{shelf#}-{slot#}-{physical Physical feeder port of AFMO
<pfp-1-{1-2}-{1-2}> port#} circuit pack

<pfp-1-{25-26}-{1-2}>
lfp-1-{1-2} lfp-{shelf#}-{logical port#} Logical Feeder Port of AFMO
circuit pack
afm-1-16 afm-{shelf#}-{slot#} AFME1 circuit pack
<afm-1-1>
<afm-1-25>
...................................................................................................................................................................................................................................
6-146 363-211-586
Issue 6, July 2007
System planning and engineering for ATM xDSL services Alarm severity and GSI ATM xDSL identifiers tables

GSI Identifier Explanation Entity Type

Identifiers for entity types where alarm severity provisioning is applicable
afm-1-16-{1-8} afm-{shelf#}-{slot#}-{port#} Feeder of AFME1 circuit pack
<afm-1-1-{1-8}>
<afm-1-25-{1-8}>
afm-1-{15-16}-{1-2} afm-{shelf#}-{slot#}-{port#} Feeder of AFME3/DS3 circuit
<afm-1-{1-2}-{1-2}> pack
<afm-1-{25-26}-{1-2}>
afm-1 afm-{shelf#} AFME3/DS3 or AFME1 or
AFMO circuit pack
afm-1-{15-16} afm-{shelf#}-{slot#} AFME3/DS3 or AFMO circuit
<afm-1-{1-2}> pack
<afm-1-{25-26}>
vp-1-{1-255} vp-{shelf#}-{vpi#} Feeder virtual path
vp-1-{0-255} vp-{shelf#}-{vpi#} Subscriber virtual path
vc-1-{1-255}-{32-64} vc-{shelf#}-{VPI#}-{VCI#} ATM Virtual Connection
core-1 core-{shelf#} Logical COMDAC resource
subsh-{1-7} subsh-{logical subshelf#} Logical subshelf
<subsh-{1-12}>
subap-{1-7-{1-8} subap-{subshelf#}-{slot#} Application pack in subshelf
<subap-{1-12-{1-8}>
Identifiers for entity types where failure report profiles are applicable
ap-1-{1-15}-{1-32} ap-{shelf#}-{slot#}-{port#} Port on application pack
<ap-1-{2-24}-{1-32}>
<ap-1-{26-43}-{1-32}>
subap-{1-7-{1-8}-{1-32} subap-{shelf#}-{subshelf#}-{slot#}- Port on application pack in
<subap-{1-12-{1-8}-{1-32}> {port#} subshelf

ATM xDSL system alarm defaults

Upon initialization of the nonvolatile data memory, the default alarm severities as
shown in the following tables are established.
Important! The GSI identifiers for the AnyMedia ® LAG 4300 Shelf are marked by
angle brackets in the tables.

Provisioning mismatch alarms

The following table shows the ATM xDSL system alarm defaults related to any kind of
mismatches.
....................................................................................................................................................................................................................................
363-211-586 6-147
Issue 6, July 2007
System planning and engineering for ATM xDSL services Alarm severity and GSI ATM xDSL identifiers tables

GSI Identifier Message Impact on Default

Service Severity
Provisioning Mismatch Alarms
ap-1-{1-15} BB-Mismatch of installed pack and provisioned NSA SA MN
subap -{1-7}-{1-8} pack type MJ
<ap-1-{2-24}>
<ap-1-{26-43}>
subap -{1-12}-{1-8}
ap-1-{1-15}-{1-32} BB-Mismatch of installed pack and provisioned SA MN
subap port
-{1-7}-{1-8}-{1-32}
<ap-1-{2-24}-{1-32}>
<ap-1-{26-43}-{1- BB-Mismatch of installed pack and provisioned SA MN
32}> ATM traffic profile
<subap
-{1-12}-{1-8}-{1-32}>

OC-3c alarms
The following table shows the ATM xDSL system alarm defaults related to OC-3c
feeders.

GSI Identifier Message Impact on Default

Service Severity
OC-3C Alarms
pfp-1-{15-16}-{1-2} BB-Section - Loss of Signal NSA MN
SA CR
BB-Section - Loss of Frame NSA MN
SA CR
BB-Line - Signal Degrade Bit Error Ratio NSA MN
threshold exceeded SA MJ
BB-Line - Signal Fail Bit Error Ratio threshold NSA MJ
exceeded SA CR
BB-Line - Alarm Indication Signal NSA MN
SA CR
BB-Line - Remote Failure Indication NSA MN
SA CR

GSI Identifier Message Impact on Default

Service Severity
lfp-1-{1-2} BB-Path - Loss of Pointer SA CR
BB-Path - Alarm Indication Signal SA CR
BB-Path - Remote Failure Indication SA CR
BB-Path - Signal Label Mismatch SA CR
pfp-1-{15-16}-{1-2} BB-Section - Trace Identifier Mismatch NSA MN
SA CR
lfp-1-{1-2} BB-ATM Layer - Loss of Cell Delineation SA CR
pfp-1-{15-16}-{1-2} BB-APS channel failure - APS Protocol Fail NSA MN
(does not apply to DBSF protection mode)
BB-APS channel failure - APS Mode mismatch NSA MN
(does not apply to DBSF protection mode)
lfp-1-{1-2} BB-Path - Signal Degrade Bit Error Ratio SA MJ
Threshold Exceeded
BB-Path - Signal Fail Bit Error Ratio Threshold SA CR
Exceeded
BB-Path - Trace Identifier Mismatch SA CR
pfp-1-{15-16}-1 BB-Loopback activated NSA MN
SA CR

STM-1 alarms
The following table shows the ATM xDSL system alarm defaults related to STM-1
feeders.

GSI Identifier Message Impact on Default

Service Severity
STM-1 Alarms

GSI Identifier Message Impact on Default

Service Severity
pfp-1-{15-16}-{1-2} BB-Regenerator Section - Loss of Signal NSA MN
SA CR
BB-Regenerator Section - Loss of Frame NSA MN
SA CR
BB-Regenerator Section - Trace Identifier NSA MN
Mismatch SA CR
BB-Multiplex Section- Signal Degrade Bit Error NSA MN
Ratio threshold exceeded SA MJ
BB-Multiplex Section - Signal Fail Bit Error NSA MN
Ratio threshold exceeded SA CR
BB-Multiplex Section - Alarm Indication Signal NSA MN
SA CR
BB-Multiplex Section - Remote Failure NSA MN
Indication SA CR
BB-APS channel failure - Invalid section NSA MN
lfp-1-{1-2} BB-Path - Loss of Pointer SA CR
BB-Path- Alarm Indication Signal SA CR
BB-Path - Remote Failure Indication SA CR
BB-Path - Signal Label Mismatch SA CR
BB-ATM Layer - Loss of Cell Delineation SA CR
pfp-1-{15-16}-{1-2} BB-APS channel failure - APS Protocol Fail NSA MN
BB-APS channel failure - APS Mode mismatch NSA MN
lfp-1-{1-2} BB-Path - Signal Degrade Bit Error Ratio SA MJ
Threshold Exceeded
BB-Path - Signal Fail Bit Error Ratio Threshold SA CR
Exceeded
BB-Path - Trace Identifier Mismatch SA CR
pfp-1-{15-16}-1 BB-Loopback activated NSA MN
SA CR

E1 timing alarms
The following table shows the ATM xDSL system alarm defaults related to E1 timing.

GSI Identifier Message Impact on Default

Service Severity
E1 Timing Alarms
afm-1-16 BB-E1 timing lost - AFM free-running SA MJ
<afm-1-1>
<afm-1-25>

IMA group alarms

The following table shows the ATM xDSL system alarm defaults related to IMA
groups.

GSI Identifier Message Impact on Default

Service Severity

IMA Group Alarms

afm-1-16 BB-Grp Timing-Mismatch NSA MN
<afm-1-1> BB-Group Start-up, Far End SA MJ
<afm-1-25> BB-Group Config-Aborted SA MJ
BB-Group Config-Aborted Far End SA MJ
BB-Insufficient-Links SA MJ
BB-Insufficient-Links, Far End SA MJ
BB-Grp Blocked, Far End SA MJ

GSI Identifier Message Impact on Default

Service Severity
ap-1-{1-14}-{1-8} BB-Ima Group - Start-up Failed, Far End (SA) SA no report
<ap-1-{3-24}-{1-8}> BB-Ima Group - Start-up Failed, Far End (NSA) NSA no report
<ap-1-{27-43}-{1-8}> BB-Ima Group - Configuration Aborted (SA) SA no report
BB-Ima Group - Configuration Aborted (NSA) NSA no report
BB-Ima Group - Configuration Aborted, Far End SA no report
(SA)
BB-Ima Group - Configuration Aborted, Far End NSA no report
(NSA)
BB-Ima Group - Insufficient Links (SA) SA no report
BB-Ima Group - Insufficient Links (NSA) NSA no report
BB-Ima Group - Insufficient Links, Far End SA no report
(SA)
BB-Ima Group - Insufficient Links, Far End NSA no report
(NSA)
BB-Ima Group - Blocked, Far End (SA) SA no report
BB-Ima Group - Blocked, Far End (NSA) NSA no report
BB-Ima Group - Timing Synchronization Failed SA no report
(SA)
BB-Ima Group - Timing Synchronization Failed NSA no report
(NSA)

IMA link alarms

The following table shows the ATM xDSL system alarm defaults related to IMA links.

GSI Identifier Message Impact on Default

Service Severity

IMA Link Alarms

afm-1-16-{1-8} BB-Link Loss of IMA Frame (LIF) SA MJ

BB-Link Out of Delay Synch (LODS) SA MJ
BB-Link Tx-Unusable, Far End SA MJ
BB-Link Rx-Unusable, Far End SA MJ
BB-Link Tx Mis-Connected SA MJ
BB-Link Rx Mis-Connected SA MJ

GSI Identifier Message Impact on Default

Service Severity
ap-1-{1-14}-{1-8} BB-Ima Link - Loss of Ima Frame (NSA) NSA no report
BB-Ima Link - Out of Delay Synch (NSA) NSA no report
BB-Ima Link - Tx Unusable, Far End (NSA) NSA no report
BB-Ima Link - Rx Unusable, Far End (NSA) NSA no report
BB-Ima Link - Tx Mis-Connected (NSA) NSA no report
BB-Ima Link - Rx Mis-Connected (NSA) NSA no report

E1 alarms
The following table shows the ATM xDSL system alarm defaults related to E1 feeders.

GSI Identifier Message Impact on Default

Service Severity
1
E1 Alarms
afm-1-16-{1-8} BB-Loss of Signal on E1 feeder SA MJ
<afm-1-1-{1-8>} BB-Loss of Frame on E1 feeder SA MJ
<afm-1-25-{1-8>} BB-Alarm Indication Signal on E1 feeder SA MJ
BB-Remote Alarm Indication on E1 feeder SA MJ
BB-HBER on E1 feeder SA MJ
BB-Equipment Fault has caused E1 Failures SA MJ

Notes:
1. The extent to which this alarm is service-affecting depends on the relationship among the number of
active links, the amount of ATM traffic, and the number of Sufficient Links that have been provisioned in
each direction. Take as an example the situation where in each direction eight links are active, ATM
traffic can be carried comfortably over only five links, and the number of Sufficient Links is three – in
this case the loss of one link due to a feeder fault will not affect service. Or, if only five links are active,
the loss of one link will degrade service during peak traffic conditions. But if only five links are active
and the number of Sufficient Links is provisioned to five also, the loss of one link will terminate all ATM
traffic.

E3/DS3 alarms
The following table shows the ATM xDSL system alarm defaults related to E3/DS3
feeders.

GSI Identifier Message Impact on Default

Service Severity
E3/DS3 Alarms

GSI Identifier Message Impact on Default

Service Severity
afm-1-{15-16}-{1-2} BB-Equipment Fault has caused E3/DS3 failure SA CR
<afm-1-{1-2}-{1-2}> BB-E3/DS3 receive Loss of Signal SA CR
<afm-1-{25-26}- BB-E3/DS3 receive Loss of Frame SA CR
{1-2}>
BB-E3/DS3 receive has Alarm Indication Signal SA CR
- AIS
BB-E3/DS3 receive has Remote Alarm SA CR
Indication signal - RAI
BB-E3/DS3 signal degraded with Bit Error Rate SA CR
> 10E-6
afm-1-{15-16}-1 BB-E3/DS3 is in line loopback SA CR
<afm-1-{1-2}-1>
<afm-1-{25-26}-1>
afm-1-{15-16}-{1-2} BB-DS3 receive Loss of Frame (PLCP) SA CR
<afm-1-{1-2}-{1-2}> BB-DS3 receive has Remote Alarm Indication SA CR
<afm-1-{25-26}- Signal - RAI (PLCP)
{1-2}> BB-E3 receive has Trail Trace Identifier SA CR
Mismatch
BB-E3/DS3 receive FEBE Failure SA CR
BB-E3/DS3 receive has Remote Alarm NSA MN
Indication signal - RAI
BB-E3/DS3 receive Loss of Frame NSA MN
BB-E3/DS3 receive Loss of Signal NSA MN
BB-E3/DS3 signal degraded with Bit Error Rate NSA MN
> 10E-6
BB-DS3 receive Loss of Frame (PLCP) NSA MN
BB-E3 receive has Trail Trace Identifier NSA MN
Mismatch

AFM circuit pack alarms

The following table shows the ATM xDSL system alarm defaults related to AFM
circuit packs.

GSI Identifier Message Impact on Default

Service Severity
AFM Circuit Pack Alarms

GSI Identifier Message Impact on Default

Service Severity
afm-1-16 BB-AFM failure (AFME1) SA CR
<afm-1-1>
<afm-1-25>
afm-1-{15-16} BB-AFM failure (AFMO) SA MJ
<afm-1-{1-2}> BB-AFM self test pack failure SA CR
<afm-1-{25-26}> BB-AFM self test pack failure prior to service NSA MN
activation
BB-AFM determined to be incompatible prior to NSA MN
service activation
BB-AFM software validation has failed NSA MN
afm-1 BB-Mismatched AFMs NSA MN
BB-AFM software version mismatch NSA MN
BB-AFM cross coupling failure NSA MN
afm-1-{15-16} BB-AFM pack failed (protected) NSA MN
<afm-1-{1-2}> BB-AFM pack failed (unprotected, if reportable) SA CR
<afm-1-{25-26}> BB-AFM pack not responding to poll NSA MN
BB-AFM pack removed NSA MN
BB-Pack unlatched NSA MN
afm-1-{15-16}-1 or BB-All timing sources failed, AFM free running SA CR
afm-1-16-{1-8} or
comdac-{1-2}
<afm-1-{1-2}-1> or
<afm-1-{25-26}-1> or BB-Timing source failed NSA MN
afm-1-1-{1-8} or
afm-1-25-{1-8} or
comdac-{1-2}
afm-1 BB-Failure profile changed NSA Info
BB-Alarm severity update for alarm NSA Info

Application pack alarms

The following table shows the ATM xDSL system alarm defaults related to application
packs.

GSI Identifier Message Impact on Default

Service Severity
Application Pack Alarms
....................................................................................................................................................................................................................................
363-211-586 6-155
Issue 6, July 2007
System planning and engineering for ATM xDSL services Alarm severity and GSI ATM xDSL identifiers tables

GSI Identifier Message Impact on Default

Service Severity
ap-1-{1-15} BB-Pack is removed SA MJ
subap-{1-7}-{1-8} BB-Pack not responding to AFM poll requests SA MN
<ap-1-{2-24}> BB-Non-service affecting failure on AP NSA MN
<ap-1-{26-43}> BB-Tip/Ring cable disconnect detected 1
SA MJ
<subap-{1-12}-{1-8}> BB-Download of software to AP from AFM SA MJ
failed
BB-Download of software to AP from AFM NSA MN
failed
BB-Service affecting failure on AP SA MJ
1
BB-Network timing reference failed NSA MN

Notes:
1. Not applicable for E1IMA AP.

ADSL alarms
The following table shows the ATM xDSL system alarm defaults related to ADSL.

GSI Identifier Message Impact on Default

Service Severity
ADSL Alarms
ap-1-{1-15}-{1-32} BB-Dying gasp NSA no report
subap-{1-7}-{1-8}- BB-Dying gasp SA no report
{1-32}
BB-Loss of Signal NSA no report
<ap-1-{2-24}-{1-32}>
BB-Loss of Signal SA no report
<ap-1-{26-43}-{1-
32}> BB-Loss of Frame NSA no report

<subap-{1-12}-{1-8}- BB-Loss of Frame SA no report

{1-32}> BB-High Bit Error Ratio NSA no report
BB-High Bit Error Ratio SA no report
BB-Far End - Loss of Signal NSA no report
BB-Far End - Loss of Signal SA no report
BB-Remote Failure Indication NSA no report
BB-Remote Failure Indication SA no report
BB-Far End - High Bit Error Ratio NSA no report
BB-Far End - High Bit Error Ratio SA no report

SHDSL alarms
The following table shows the ATM xDSL system alarm defaults related to SHDSL.

GSI Identifier Message Impact on Default

Service Severity
SHDSL Alarms
ap-1-{1-15}-{1-32} BB-Upstream - Loss of Sync Word NSA no report
subap-{1-7}-{1-8}- BB-Upstream - Loss of Sync Word SA no report
{1-32}
BB-High Bit Error Ratio upstream NSA no report
<ap-1-{2-24}-{1-32>
BB-High Bit Error Ratio upstream SA no report
<ap-1-{26-43}-{1-32>
BB-Downstream - Loss of Sync Word NSA no report
<subap-{1-12}-{1-8}-
{1-32}> BB-Downstream - Loss of Sync Word SA no report
BB-High Bit Error Ratio downstream NSA no report
BB-High Bit Error Ratio downstream SA no report

E1 port alarms
The following table shows the ATM xDSL system alarm defaults related to E1 ports.

GSI Identifier Message Impact on Default

Service Severity
E1 Port Alarms
ap-1-(1-14)-(1-8) BB-E1 - Loss of Signal (SA) SA no report
<ap-1-(3-24)-(1-8)> BB-E1 - Loss of Signal (NSA) NSA no report
<ap-1-(27-43)-(1-8)> BB-E1 - Loss of Frame (SA) SA no report
BB-E1 - Loss of Frame (NSA) NSA no report
BB-E1 - Alarm Indication Signal (SA) SA no report
BB-E1 - Alarm Indication Signal (NSA) NSA no report
BB-E1 - Remote Alarm Indication (SA) SA no report
BB-E1 - Remote Alarm Indication (NSA) NSA no report
BB-E1 - HBER (SA) SA no report
BB-E1 - HBER (NSA) NSA no report
BB-E1 - Equipment Failure (SA) SA no report
BB-E1 - Equipment Failure (NSA) NSA no report

Virtual connection alarms

The following table shows the ATM xDSL system alarm defaults related to virtual
connections.
....................................................................................................................................................................................................................................
363-211-586 6-157
Issue 6, July 2007
System planning and engineering for ATM xDSL services Alarm severity and GSI ATM xDSL identifiers tables

GSI Identifier Message Impact on Default

Service Severity
Virtual Connection Alarms
vp-1-{1-255} BB-F4 End-to-end AIS Detected SA CR
BB-F4 End-to-end RDI Detected SA CR
BB-F4 End-to-end LOC Detected SA CR
BB-F4 Segment AIS Detected SA CR
BB-F4 Segment RDI Detected SA CR
BB-F4 Segment LOC Detected SA CR
vc-1-{1-255}-{32-64} BB-F5 End-to-end AIS Detected NSA MN
BB-F5 End-to-end RDI Detected NSA MN
BB-F5 End-to-end LOC Detected NSA MN
vc-1-{1-255}-{33- BB-F5 Segment AIS Detected SA MN
9723} BB-F5 Segment RDI Detected SA MN
BB-F5 Segment LOC Detected SA MN

ATM feeders

Overview of ATM feeders

Overview
The AnyMedia ® Access System provides ATM feeder multiplexers for the following
ATM feeder types:
• E3 feeder
• DS3 feeder
• E1 feeder
• STM-1/OC-3c feeder
The following table shows the feeder specifications in an overview. For orderable
cables see the Ordering Guide.

Technical Interface
data
E3 DS3 E1 STM-1/OC3c
Bit rate 34.368 Mbps ± 20 44.736 Mbps ± 20 2.048 Mbps 155.52 Mbps
ppm according to ppm according to
ITU-T G.703 Telcordia
specification
GR-499
Framing Direct cell Direct cell direct cell mapping ATM cell mapping
mapping mapping or PLCP according to ITU according
framing according G.804 GR253/ITU G.707
to G.832
Line code HDB3 code B3ZS code HDB3 code binary Non-Return
to Zero (NRZ)
optical receive n.a n.a n.a -34 dBm min.,
sensitivity -10 dBm max
Cell format UNI 3.1/4.0 as defined in the ATM Forum
Cabling Unbalanced coaxial lines in each 26-gauge separate single-
direction (0.404 mm) and mode fiber for
22-gauge each direction
(0.644 mm) ″Y″
cable balanced
cable in each
direction

Technical Interface
data
E3 DS3 E1 STM-1/OC3c
Max. cable 86 m using 735A 26-gauge (0.404 mm) 198 m using long haul,
length coaxial cable, 180 m using 734A multipair 26 AWG ≤ 40 km
20-gauge (0.812 mm) coaxial cable cable with 120-
ohm termination

ATM E3/DS3 feeder

Overview
The AnyMedia ® Access System interfaces to the ATM network via port 1 of the
AFME3/DS3. This section describes the following attributes of the E3/DS3 feeder
interface to the ATM network:
• E3/DS3 connections
• E3/DS3 framing and synchronization
• Daisychaining using protected AFME3s or AFMDS3s
• E3/DS3 cable selection.
The following table shows a summary of the E3/DS3 feeder specifications. For
orderable cables see the Ordering Guide.

Technical data Interface

E3 DS3
Bit rate 34.368 Mbps ± 20 ppm 44.736 Mbps ± 20 ppm
according to ITU-T G.703 according to Telcordia
specification GR-499
Framing Direct cell mapping Direct cell mapping or PLCP
according to ITU-T G.804, framing according to G.832
G.832
Line code HDB3 code B3ZS code
Cell format UNI 3.1/4.0 as defined in the ATM Forum
Cabling Unbalanced coaxial lines in each direction
Max. cable length 86 m using 735A 26-gauge (0.404 mm) coaxial cable,
180 m using 734A 20-gauge (0.812 mm) coaxial cable

E3/DS3 connections
The AnyMedia ® Access System E3/DS3 feeder interface on the AFME3 or AFMDS3
has the following connections:
• Two E3/DS3 ports
– Port 1 used to interface toward the ATM network.
– Port 2 used to connect to any other AnyMedia ® Mainshelf that may be
daisy-chained.
• Each E3/DS3 carries the xDSL service ATM payload cells. The transmission rates
of the applicable interface are listed in the table above.

• The network E3/DS3 may terminate directly on an E3/DS3 interface of an ATM

switch or may be transported over a synchronous optical network transmission
system.
• The network E3/DS3 provides a user network interface cell format toward the
network, as defined in the ATM Forum 3.1/4.0.

Simplex mode; no daisy-chain

For a shelf containing a single AFME3 operating in simplex mode with no
daisychaining, the E3 connections are shown in the following figure.

E3/DS3 connections to the ATM backbone network when using

a...................................................................................................................................................................................................................................
single AFME3/DS3 in simplex mode with no daisychaining
Duplex mode; no daisy-chain
For a shelf containing two AFME3s operating in duplex mode with no daisychaining,
the E3 connections are shown in the following figure.

This duplex configuration uses external combiners/splitters, along with on-board

automatically controlled transmit relays in the AFME3 and the AFMDS3.
Between the ATM feeder network and the AnyMedia ® Mainshelf, each AFME3’s or
AFMDS3’s TX1 cable connects to a combiner. This combiner receives the signal only
from the active AFM, whose relay enables feeding; the standby AFM’s relay disables
feeding. The signal then travels on toward the ATM feeder network. The transmitted
signal coming from the ATM feeder network travels into a splitter. The signal is split
and one signal travels to each AFM’s RX1 connector.

E3/DS3 connections to the ATM backbone network when using

two AFME3/DS3s in duplex mode with no daisychaining
...................................................................................................................................................................................................................................

E3/DS3 framing and synchronization

For E3 framing direct cell mapping is used. For DS3 framing format is provisionable
for direct cell mapping or PLCP. The AFME3 LPA911 or AFMDS3 LPA901 transmit
clock is provisionable either to be synchronized to the network’s incoming E3/DS3
port 1 receive line or to be free running (see “ATM xDSL synchronization and timing
” (p. 6-193)). The status of the E3 (DS3) ports is provided by LEDs on the AFM as
well as at the GSI display. Refer to the AFME3/AFMDS3 sections in the Data Sheet
Book 363-211-251 for a brief description of the AFME3/AFMDS3 LEDs.

E3/DS3 cable selection

The cable assemblies are connectorized on both ends and are available in various
lengths. The daisy chain cable assemblies have right angle coaxial connectors on both
ends and are used to connect two AFME3/DS3 in separate shelves. The ATM network
cable assemblies, which have either right angle coaxial connectors on both ends or
right angle connectors on one end and straight connectors on the other end, are used to
connect the AFM to the Metropolis ® ADM or DS3 cross-connect panel or equivalent
DS3 equipment.
Important! Regarding the ATM network cable assemblies, the maximum cable
length for the AFME3/AFMDS3 is 86 m using 735A 26-gauge (0.404 mm) coaxial
cable or 180 m) using 734A 20-gauge (0.812 mm) coaxial cable.
When protected AFME3 or AFMDS3 packs are used in both non-daisy-chained and
daisy-chained applications, cables with one right-angle connector and one straight
connector are required; the right-angle connector mates with the AFM faceplates and
the straight connector mates with the applicable splitter or combiner.

E3/DS3 Daisychaining capability

Background
To increase the fill of the interface that connects to the ATM network, AnyMedia ®
Mainshelf daisychaining is provided. Daisychaining makes use of both feeder ports on
each AnyMedia ® Mainshelf, except for the last AnyMedia ® Mainshelf in a daisy-chain.
This configuration enables transfer of ATM cells from each AnyMedia ® shelf onto a
common connection to the ATM network.
The two BB subsystems of an AnyMedia ® LAG 4300 Shelf can be daisy-chained in
the same way as two independent AnyMedia ® Mainshelves, whereas the first BB
subsystem may be located either in the lower row or in the upper row of the shelf.

Simplex mode; daisychaining

Collocated AnyMedia ® Mainshelves are daisy-chained as shown in the next figure. The
AnyMedia ® Access System has two ATM feeder interfaces per AFME3/DS3 pack. One
of these interfaces (port 1) connects toward the ATM network and the other (port 2)
connects to an AFME3/DS3 in another AnyMedia ® Mainshelf. In the example shown
in the following figure, four shelves share the same connection to the network. The
DS3 signals are connected as follows:
• Shelf 1: E3 port 1 to network, E3 port 2 to E3 port 1 on Shelf 2
• Shelf 2: E3 port 1 to E3 port 2 on Shelf 1, E3 port 2 to E3 port 1 on Shelf 3
• Shelf 3: E3 port 1 to E3 port 2 on Shelf 2, E3 port 2 to E3 port 1 on Shelf 4
• Shelf 4: E3 port 1 to E3 port 2 on Shelf 3, E3 port 2 disabled and not connected.
The following figure shows E3 interfaces with daisychaining (example)

The connection to the ATM backbone network can be made to several different types
of elements. Here are some examples:
• Connection directly to an ATM switch
• Connection directly to an ATM interface on a router
• Connection to an ATM switch or to a router via an SDH multiplexer (ring or linear
configuration).
When AnyMedia ® Mainshelves are remotely located, they can be connected via an
SDH ring as shown in the next figure. If an external SDH ring interface is provided,
the ATM signals are carried in an E3/DS3 via a C-3 container of an STM-N signal.
The number of AnyMedia ® Mainshelves that can be in a daisy-chain is discussed in
“ATM xDSL system capacity” (p. 6-5).
The following figure shows the daisychaining of non-collocated AnyMedia ®
Mainshelves (with AFME3 installed) via SDH ring.

Duplex mode; daisychaining

Daisychaining is also fully supported when each shelf has two AFMs operating in
duplex (protected) mode, providing increased daisy-chain reliability.
Daisychaining using an E3/DS3 feeder interface and protected AFMs is shown in the
following figure.

This duplex configuration uses external combiners/splitters, along with on-board

feeding. The signal then travels on toward the ATM feeder network. The transmitted
signal coming from the ATM feeder network travels into a splitter. The signal is split
and one signal travels to each AFM’s RX1 connector.
Between the first and second shelves in the daisy-chain, the TX2 cable of each AFM in
the first shelf connects to a combiner; again, the combiner receives the signal from
only the active AFM. From this combiner, the signal travels to a splitter, where it is
split into two signals. One of these signals travels to each RX1 connector of the duplex
AFMs in the second shelf. Between these two shelves, the TX1 cable of each AFM in
the second shelf connects to a combiner. The signal of the active AFM travels to this
combiner, then to a splitter where it is split into two signals. One of these signals
travels to each RX2 connector of the duplex AFMs in the first shelf.

ATM E1 feeder (Background on IMA)

Background on inverse multiplexing for ATM

Existing feeder plant in telecommunications network comprises, to a considerable
extent, facilities with E1 rate interfaces. To facilitate achieving ATM connectivity
through these E1-based feeders, the ATM Forum Technical committee developed a
standard called the Inverse Multiplexing for ATM (IMA) Specification. Version 1.1 of
this standard was issued in March 1999, and is the entire basis for the IMA
functionality of the AFME1 LPA941. Essentially, the IMA protocol breaks apart an
ATM signal at one end of the feeder and distributes the cells among the various E1
feeder ports; at the far end the several E1-fed signal components are reassembled into
the original ATM cell stream. On the AFME1 LPA941 the IMA protocol is
provisionable for V1.0 and V1.1 as specified per ATM Forum Standards. If provisioned
for V1.1 the AFME1 LPA941 will automatically fall back to V1.0 if the counterpart at
the far end does not support it.
The IMA Specification calls for several groups with each group consisting of several
links, where each link is associated with and depends upon an E1 feeder. The AFME1
is designed to support up to eight links/feeders making up one group. Since the
AFME1 has eight ports, its maximum cell rate is almost 36224 cells per second (the
maximum cell rate correlates with the maximum available bandwidth of eight E1
interfaces). The IMA concept of multiple links comprising an IMA group is illustrated
in “Background on inverse multiplexing for ATM” (p. 6-170).
The following figure shows inverse multiplexing and de-multiplexing of ATM cells via
IMA group (downstream direction shown)

IMA Terminal AFME1

IMA E1 E1 IMA
Group Port Link #1 Port Group
#1 #1

E1 E1
Link #4
Port Port
Single ATM cell stream #4 #4 Original ATM cell stream
from ATM layer to ATM layer
E1 Link #8 E1
Port Port
#8 #8

IMA Virtual Link

Tx direction: cells distributed across links in round robin sequence

Rx direction: cells recombined into single ATM stream

Note that the AnyMedia ® Access System uses IMA links also for cascading shelves,
that means connecting the AFME1 in a cascaded shelf to the E1IMA AP in a host
shelf.
...................................................................................................................................................................................................................................
6-170 363-211-586
Issue 6, July 2007
System planning and engineering for ATM xDSL services

ATM E1 feeder
...................................................................................................................................................................................................................................

IMA using the AFME1

The AFME1 allows for the creation of only one IMA group. The IMA group is defined
to contain at least one IMA link. Each of the AFME1’s eight E1 network feeder
interfaces can be assigned a link number, and so there can be up to eight links in the
AFME1 group. Use of the AFME1 requires that the link and feeder port numbers have
a direct, one-to-one, correspondence (that is, with the lowest numbered port always
associated with the lowest numbered link). However, the GSI screens for IMA
activities show the link numbers over a range of 0 to 7, while the ports shown on the
feeder screens are numbered 1 to 8.
When an IMA group is created, the selected UNI feeder automatically becomes the
first active link in the IMA group. Before deleting an IMA group, all IMA links except
one must be deleted. When deleting the IMA group, the pack switches to UNI mode
with a maximum Shelf PCR = 4,528 ATM cells per second. The latest provisioned
UNI mode link (before having switched to IMA mode), will become the UNI mode
link.
IMA performance monitoring is carried out at both the link and group levels.

Operating an AFME1 without IMA multiplexing

For AFME1 applications using only a single E1, the system can also operate without
IMA. This mode of operation is called UNI mode. Until an IMA group is created,
when an AFME1 is initialized, the AFME1 assumes UNI mode. (See “Background on
inverse multiplexing for ATM” (p. 6-170) for information on IMA groups). UNI mode
cannot be used with multiple E1s, and is available only when an IMA group does not
exist.
In UNI mode, the user selects the E1 port (1–8) and provisions the E1 parameters,
including performance management thresholds.
In this mode, ATM cells are mapped directly onto the selected E1 interface per ATM
Forum, ″E1 Physical Layer Specification″, AF-PHY-0064.000. The AFME1’s entire
processing capability is dedicated to the support of ATM transport over one feeder link.

ATM E1 feeder overview

The AnyMedia ® Access System interfaces to the E1 ATM network via one E1
connector on the faceplate of the AFME1 circuit pack which comprises cabling of all
eight E1 interfaces (8 × 2 pairs). This section describes the following attributes of the
E1 feeder interface to the ATM network:
• E1 connections
• E1 framing and synchronization.
Important! The AFME1 circuit pack does not provide daisychaining capability.

The following figure shows a summary of the E1 Feeder specifications. For orderable
cables see the Ordering Guide.

Technical data E1 Interface

Bit rate 2.048 Mbps
Framing according ITU-T G.704 using direct cell
mapping according to ITU-T G.804
Line code HDB3 code
Cell format UNI 3.1/4.0 as defined in the ATM Forum
″ATM User-Network Interface (UNI)
Specification″
Cell scrambling Enabled
Cabling 26-gauge (0.404 mm) and 22-gauge
(0.644 mm) ″Y″ cable balanced cable in each
direction
Max. cable length to the E1 interface 198 m using multipair 22 AWG cable with
120-ohm termination

E1 connections
The AnyMedia ® Access System E1 feeder interface on the AFME1 circuit pack has the
following features:
• Eight E1 ports toward the ATM network
• Each E1 has a 2.048 Mbps transfer rate for transport of ATM cells and carries the
ATM xDSL service ATM payload cells.
• The interface supports a UNI 3.1/4.0 cell format toward the network, as defined in
the ATM Forum, ″ATM User-Network Interface (UNI) Specification″, Version 3.1.
The E1 feeder may terminate directly on an E1 interface of an ATM switch or may be
transported to the switch over an SDH transmission system.

E1 framing and synchronization

The E1 IMA framing according ITU-T G.704 uses direct cell mapping according to
ITU-T G.804. The AFME1 transmit clock is provisionable either to be synchronized to
one of eight network E1 receive lines or to be free running (see “Synchronization and
timing for E1 ATM network feeder interface” (p. 6-196)). The status of the E1
connections is provided by one CLF LED on the AFME1 as well as by the GSI
display. Refer to the AFME1 section in the Data Sheet Book 363-211-251 for a brief
description of the AFME1 LEDs.
When AnyMedia ® Mainshelves are remotely located, they can be connected via an
SDH ring. If an external SDH ring interface is provided, the ATM signals are carried
in an E1 via a C-12 container of an STM-N signal.

E1 cable selection
An ED7C849-30 G10 Y-cable connects to the faceplate of the AFME1 pack. The
Y-cable splits the 8 E1 signals into Transmit and Receive paths for connections to the
E1 panel.
The Transmit and Receive ends of the Y-cable are extended onto the E1 panel by
means of additional cables, one for each direction. The lengths of these cables are
based on the engineered distance to the E1 panel. The cables are ED7C849-30 G11,
G11A, G11B, or G11C, the lengths of which are 15 m, 30 m, 61 m, and 91 m (all
26-gauge (0.404 mm), respectively. ED7C849-30 G11D is 22-gauge (0.644 mm) and
has a length of 198 m.

ATM STM-1/OC-3c feeder

Overview
The AnyMedia ® Access System interfaces to the ATM network via an STM-1/OC-3c
port on the AFMO circuit pack. This section describes the following attributes of the
STM-1/OC-3c feeder interface to the ATM network:
• STM-1/OC-3c connections
• STM-1/OC-3c framing and synchronization
• Daisychaining capability
• AFMOs in duplex mode
• Special considerations for DBSF protection mode
• Daisychaining using protected AFMOs
• STM-1/OC-3c optic cable selection
• Optical couplers
• Optical AFM attenuation design.
The following figure shows a summary of STM-1/OC-3 feeder specifications. For
orderable cables see the Ordering Guide.

Technical data STM-1/OC3c Interface

Bit rate 155.52 Mbps ± 20 ppm
Framing according to ITU-T G.707 or Telcordia
GR-253 with ATM cell mapping into
C4/STS3c-SPE
Line code Binary NRZ optical
Cell format UNI 3.1/4.0 as defined in the ATM Forum
Cabling Separate single-mode fiber for each direction
Max. cable length to the 40 km
STM-1/OC-3c interface
Maximum transmit power 0 dBm
Minimum transmit power -5 dBm
Maximum receive power -10 dBm
Minimum receive power -34 dBm

STM-1/OC-3c connections
The AnyMedia ® Access System STM-1/OC-3c feeder interface on the AFMO has the
following connections:
• Two STM-1/OC-3c ports
– Port 1 used to interface toward the ATM network.
– Port 2 used to connect to any other AnyMedia ® Mainshelf that may be
daisy-chained.
• Each STM-1/OC-3c has a 155.52 Mbps transmission rate and carries the ATM
xDSL service ATM payload cells.
• The network STM-1/OC-3c may terminate directly on an STM-1/OC-3c interface
of an ATM switch or may be transported over a synchronous optical network
transmission system.
• The network STM-1/OC-3c supports a UNI 3.1/4.0 cell format toward the network,
as defined in the ATM Forum.

Simplex mode; no daisy-chain

For a shelf containing a single AFMO operating in simplex mode with no
daisychaining, the STM-1 connections are shown in the following figure.

Simplex mode; with daisychaining

For a shelf containing a single AFMO operating in simplex mode with daisychaining,
see “Simplex mode; daisychaining” (p. 6-178).

Duplex mode; no daisy-chain

For a shelf containing two AFMOs operating in duplex mode (and DBSF protection
mode has been selected) with no daisychaining, see “DBSF protection mode”
(p. 6-180).

For a shelf containing two AFMOs operating in duplex mode (and Duplex 1+1
protection mode has been selected) with no daisychaining, see “Duplex 1+1 protection
mode” (p. 6-181).

Duplex mode; with daisychaining

For a shelf with daisychaining containing two AFMOs operating in duplex mode (and
DBSF protection mode has been selected), see “Duplex 1+1 protection mode”
(p. 6-181).
For a shelf with daisychaining containing two AFMOs operating in duplex mode (and
Duplex 1+1 protection mode has been selected), see “Duplex 1+1 protection mode;
daisychaining” (p. 6-184).
Note that in a daisy-chain the protection modes selected for port 1 and port 2 may be
different.

STM-1/OC-3c framing and synchronization

STM-1/OC-3c interface uses the frame structure according to ITU-T G.707 or
Telcordia GR-253 with ATM cell mapping into C4/STS3c-SPE. The AFMO transmit
clock is provisionable either to be synchronized to the network’s incoming
STM-1/OC-3c port 1 receive line or to be free running (see “Synchronization and
timing for STM-1/OC-3c ATM network feeder interface” (p. 6-198)). The status of the
STM-1/OC-3c ports is provided by LEDs on the AFMO as well as by the GSI display.
Refer to the AFMO section in the Data Sheet Book 363-211-251 for a brief description
of the AFMO LEDs.

STM/1/OC-3c optic cable selection

Single-mode optical fiber jumpers are used for connecting the AFMO toward the ATM
network (separate jumpers are used for the transmit and receive directions).
Single-mode optical fiber jumpers are also used for connecting between daisy-chained
AFMOs (again, separate jumpers are used for the transmit and receive directions).
Important! Regarding the ATM network cable assemblies, the maximum cable
length to the STM-1/OC-3c is 40 km.

STM-1/OC-3c Daisychaining capability

Background
To increase the fill of the STM-1/OC-3 that connects to the ATM network, AnyMedia ®
Mainshelf daisychaining is provided. Daisychaining makes use of both feeder ports
on each AnyMedia ® Mainshelf, except for the last AnyMedia ® Mainshelf in a
daisy-chain. This configuration enables transfer of ATM cells from each AnyMedia ®
shelf onto a common STM-1/OC-3c connection to the ATM network.
The two BB subsystems of an AnyMedia ® LAG 4300 Shelf can be daisy-chained in
the same way as two independent AnyMedia ® Mainshelves, whereas the first BB
subsystem may be located either in the lower row or in the upper row of the shelf.

Simplex mode; daisychaining

AnyMedia ® Mainshelves whether collocated or at multiple physical locations, can be
directly daisy-chained without multiplexers, as shown in the next figure. The
AnyMedia ® Access System has two ATM feeder interfaces per AFMO pack. One of
these interfaces (port 1) connects toward the ATM network and the other (port 2)
connects to an AFMO in another AnyMedia ® Mainshelf. In the example shown in the
next figure, four shelves share the same connection to the network. The feeder
interfaces are connected as follows:
• Shelf 1: STM-1/OC-3c port 1 to network, STM-1/OC-3c port 2 to STM-1/OC-3c
port 1 on Shelf 2
• Shelf 2: STM-1/OC-3c port 1 to STM-1/OC-3c port 2 on Shelf 1, STM-1/OC-3c
port 2 to STM-1/OC-3c port 1 on Shelf 3
• Shelf 3: STM-1/OC-3c port 1 to STM-1/OC-3c port 2 on Shelf 2, STM-1/OC-3c
port 2 to STM-1/OC-3c port 1 on Shelf 4
• Shelf 4: STM-1/OC-3c port 1 to STM-1/OC-3c port 2 on Shelf 3, STM-1/OC-3c
port 2 disabled and not connected.
The following figure shows STM-1/OC-3c interfaces in simplex mode, with shelf
daisychaining and LBOs.

The connection to the ATM backbone network can be made to several different types
of elements. Here are some examples:
• STM-1/OC-3c connection directly to an ATM switch
• STM-1/OC-3c connection directly to an ATM interface on a router
• Connection to an ATM switch or to a router via an SDH multiplexer (ring or linear
configuration).
When AnyMedia ® Mainshelves are remotely located, they can be connected via an
SDH ring. If an external SDH ring interface is provided, the ATM signals are carried
in the C-4 container of an STM-1 signal.
The number of AnyMedia ® Mainshelves that can be in a daisy-chain is discussed in
“ATM xDSL system capacity” (p. 6-5).
The following figure shows daisychaining of non-collocated AnyMedia ® Mainshelves
(with AFMO installed) via SDH ring.

AFMOs in duplex mode

Overview
The AFMO supports two protection modes:
• Pack protection only, in the Double Board Single Fiber protection mode (DBSF
protection mode)
• Pack protection combined with feeder facility protection (Duplex 1+1 protection
mode).

DBSF protection mode

When provisioned in DBSF protection mode, pack protection is supported, while both
AFMOs use a single optical feeder pair as shown in the next figure.

The fiber pair is connected to the duplex AFMOs via a pair of optical couplers, used to
split the receive signal to both AFMOs and to couple the active transmit signal of
either AFMO to the transmit fiber. In transmit direction per logical port the laser of
one pack is switched off while the laser of the other pack is switched on. Only one of
the lasers is on at a time. This is controlled by the active AFM. Per logical port the
working pack selects the received signal from either its own or from the mate receiver.
The active AFMO has access to the standby AFMO via the 995 A cross couple
connector. Only one of the two lasers will be on at the same time.
...................................................................................................................................................................................................................................
6-180 363-211-586
Issue 6, July 2007
System planning and engineering for ATM xDSL services AFMOs in duplex mode

Duplex 1+1 protection mode

When provisioned in Duplex 1+1 protection mode, facility protection as well as pack
protection is supported, as shown in the next figure“Duplex 1+1 protection mode”
(p. 6-181).

The two facilities are connected to the active AFMO and the standby AFMO,
respectively. However, the actual termination of the interfaces occurs on the active
AFMO. The active AFMO has access to the facility connected to the standby AFMO
via the 995 A cross couple connector. Both lasers per port are active.

Special considerations for DBSF protection mode

For DBSF protection mode the following has to be considered:
• Optical couplers
For this protection mode optical couplers have to be installed. For the requirements
refer to “Optical couplers” (p. 6-187)).
• Daisy-Chaining in DBSF protection mode
For AFMO applications the protection mode can be provisioned separately for port
1 and port 2 which means that the protection mode can differ between network
interface and daisy-chain interface. When DBSF protection mode is supported
within the daisy chain, optical couplers have to be connected between the two
adjacent shelves.
• Provisioning of physical feeder ports
The physical feeder ports of the AFMOs have to be provisioned to the same values
when the related logical feeder port is in DBSF protection mode.

Duplex mode; daisychaining - Overview

Daisychaining is also fully supported when each shelf has two AFMs operating either
in DBSF or Duplex 1+1 protection mode, providing increased daisy-chain reliability.
(Protection for AFMO and facility is non-revertive.) Daisychaining using a single
optical feeder interface and protected AFMs (DBSF protection mode) is shown in
“DBSF protection mode; daisychaining” (p. 6-183), while daisychaining using a duplex
optical feeder interface and protected AFMs (Duplex 1+1 protection mode) is shown in
“Duplex 1+1 protection mode; daisychaining” (p. 6-184). Note that in a daisy-chain the
protection modes selected for port 1 and port 2 may be different i.e. both protection
modes may be used within one daisy-chain (see “DBSF mode and Duplex
1+1protection; daisychaining” (p. 6-185)).

DBSF protection mode; daisychaining

The following figure shows shelf daisychaining using a single optical feeder interface,
optical couplers, protected AFMOs, and LBOs (DBSF protection mode).

“DBSF mode and Duplex 1+1protection; daisychaining” (p. 6-185) shows a

configuration example where ports 1 of the AFMOs nearest to the ATM network are
provisioned in DBSF protection mode while the ports inside the daisy-chain are
provisioned in Duplex 1+1 protection mode.
....................................................................................................................................................................................................................................
363-211-586 6-183
Issue 6, July 2007
System planning and engineering for ATM xDSL services AFMOs in duplex mode

Duplex 1+1 protection mode; daisychaining

The following figure shows shelf daisychaining using a duplex optical feeder interface,
protected AFMs, and LBOs (Duplex 1+1 protection mode)

DBSF mode and Duplex 1+1protection; daisychaining

The following figure shows shelf daisychaining with duplex AFMOs, using DBSF
protection mode towards the ATM network and Duplex 1+1 protection mode inside the
daisy-chain.

In duplex mode, the AFMOs use special hardware, including a cross couple that
connects the two AFMs and allows for the transfer of transmission data between them.
This hardware allows signals in the transmit direction (both upstream toward the
network and downstream toward other shelves in the daisy chain) to be transmitted
from the active AFM to the standby AFM as well. These signals then travel out the
transmit connectors of both AFMs. In the receive direction, signals are received by
both AFMs, but hardware logic guarantees that only the active pack terminates the
signals and selects one of the two for traffic. The internal selector function is managed
by the active AFM. Thereby, both pack protection and facility protection, if applicable,
are achieved. If the active pack fails, a protection switch to the standby AFM includes
....................................................................................................................................................................................................................................
363-211-586 6-185
Issue 6, July 2007
System planning and engineering for ATM xDSL services AFMOs in duplex mode

an action by the selector function whereby the receive signals of the standby (now
active) pack are selected for use. In another scenario (Duplex 1+1 protection mode
only), if the network fiber connected to the active AFM fails, the selector function
selects for use the receive signals coming from the standby pack, which still has its
network fiber intact. Note, that when the following two failure situations ″AFM
crosscoupling failure″ and a failure present on port 1 and/or port 2 of the standby AFM
are present in parallel a non-service affecting protection switch is not possible.
Therefore a manual protection switch will be denied.

Optical couplers
...................................................................................................................................................................................................................................

Optical Couplers
Optical couplers are used in DBSF protection mode only, to connect the fiber pair to
the duplex AFMOs. In receive direction, one optical coupler splits the signal to both
AFMOs and in transmit direction, the other couples the active transmit signal of either
AFMO to the transmit fiber. Only one of the lasers is on at a time. Optical couplers,
which are used with the AnyMedia ® Access System, are small devices (about 85 mm ×
17.5 mm × 7.5 mm) with 3 single mode fibers coming out of two sides. The lead
length is 1 m. The optical couplers are connected to the feeder fibers via optical
connectors of type SC. They are operating at a wavelength of 1310 nm. The split ratio
of the coupler is 50:50. The insertion loss of the coupler does not exceed 3.7 dB,
while the excess loss of the coupler does not exceed 0.4 dB.

Optical AFM Attenuation Design

Recommendations
The optical AFM transmit and receive power must be attenuated to the level of the
transmit and receive power of the OLIU to which it is connected. Since the AFMs and
OLIUs do not have gain or loss adjustments, attenuation occurs through the
combination of fiber cable and splice losses, optical couplers. Optical couplers are
applicable for DBSF protection mode only and lightguide build-out (LBO) networks
externally connected. A similar attenuation is required between the two optical AFMs
installed in a daisy chain. (For detailed ordering information on LBOs, see the
Ordering Guide 363-211-144.)
Four total calculations, two for the upstream and two for the downstream legs of the
connection, are required to determine the size of the two LBOs:
1. Calculate the minimum loss for the AFM transmit to network receive (upstream)
direction
2. Calculate the maximum loss for the AFM transmit to network receive (upstream)
direction
3. Calculate the minimum loss for the network transmit to AFM receive (downstream)
direction
4. Calculate the maximum loss for the network transmit to AFM receive (downstream)
direction.
Calculations 2 and 4 assure that the highest transmit power at one end does not exceed
the maximum power allowed at the receive end. Calculations 1 and 3 check that the
lowest possible transmit power arrives at the receive end at a high enough level to
assure the minimum receive power level (receiver sensitivity).
Data required
From the data for the AFM and the network OLIU, complete the next table, noting and
retaining positive and negative values in the table and calculations in the two tables
after:
Data required for optical attenuation calculations:

Power Network AFM

Trans max (a)________ (e)________
Trans min (b)________ (f)________
Receive max (c)________ (g)________
Receive min (d)________ (h)________

This data should be added to the ATM xDSL engineering work orders, see Appendix.

Calculation for the AFM transmit to network receive (upstream) direction:

Minimum Loss Upstream (e)_ - (c)_ = (x)

Maximum Loss Upstream (f)_____ - (d)_____ = (y)

The loss must be at least (x) dB and no more than (y) dB in the AFM transmit to
network receive direction.
Calculation for the network transmit to AFM receive (downstream) direction:

Minimum Loss Downstream (a)_ - (g)_ = (z)

Maximum Loss Downstream (b)_____ - (h)_____ = (w)

The loss must be at least (z) dB and no more than (w) dB in the network transmit to
AFM receive direction.
Loss (attenuation) factors
The following contributions to loss should be identified for each connection:
• Fiber cable loss (0.4 dB per kilometer)
• Fiber cable splice (0.2 dB per splice)
• LBO device (select from 0, 5, 10, 15, 20 dB)
• Connectors (0.25 dB per connector)
• Optical coupler insertion loss (3.7 dB bidirectional). Optical couplers are applicable
for DBSF protection mode only.
The LBO loss should be chosen to be the smallest loss that meets the two criteria in
each direction.

Examples
Two examples below illustrate the selection of the needed LBOs given the following
data. One example is calculated without optical couplers, the other calculation includes
optical couplers:
• AFMO LPA920 in AnyMedia ® Mainshelf
• Multiplexer type DDM 22G3-U OLIU in Network (SONET interface)
• 20 km between the OLIU and the AFM
• 5 fiber cable splices (no connectors)
• Example 2 includes additionally one optical coupler per direction19.
Fill out a table for the AFM and OLIU:

Data required for optical attenuation calculations:

Power Network AFM

Trans max (a) 0 dBm (e) 0 dBm
Trans min (b) -5 dBm (f) -5 dBm
Receive max (c) 0 dBm (g) -10 dBm
Receive min (d) -34 dBm (h) -34 dBm

Calculation for the AFM transmit to network receive (upstream) direction:

Minimum Loss Upstream (e) 0 - (c) 0 = (x) 0

Maximum Loss Upstream (f) -5 - (d) -34 = (y) 29

The loss must be at least 0 dB and no more than 29 dB in the AFM transmit to
network receive direction.
Calculation for the network transmit to AFM receive (downstream) direction:

Minimum Loss Downstream (a) 0 - (g) -10 = (z) 10

Maximum Loss Downstream (b) -5 - (h) -34 = (w) 29

The loss must be at least 10 dB and no more than 29 dB in the network transmit to
AFM receive direction.
Loss calculations Example 1 (no optical couplers)
Cable loss: 20 km × 0.4 dB/km = 8 dB
Splice loss: 5 splices × 0.2 dB/splice = 1 dB
Loss without LBO : 9 dB
Connector loss: 0.25 dB per connector.
LBO calculation upstream
From the upstream calculation above, the loss must be at least 0 dB and no more than
29 dB in the AFM transmit to network receive direction.
Cable loss is 9 dB > × = 0 dB, -> 0 dB LBO (upstream) is sufficient
Cable loss is 9 dB + 0 dB (LBO-up) = 9 dB < y = 29 dB, -> Minimum signal strength
is okay)
So 0 dB LBO in the upstream direction should be used.
LBO calculation downstream
From the downstream calculation above, the loss must be at least 10 dB and no more
than 29 dB in the network transmit to AFM receive direction.
....................................................................................................................................................................................................................................
6-190 363-211-586
Issue 6, July 2007
System planning and engineering for ATM xDSL services Optical AFM Attenuation Design

Cable loss is 9 dB < z = 10 dB, → 5 dB LBO (downstream) is needed to increase loss

above 10 dB
Cable loss is 9 dB + 5 dB (LBO-down) = 14 dB< y = 29 dB (minimal signal strength
is okay) → So 5 dB LBO in downstream direction should be used.
Engineering work order
The work order should specify the following:
• LBO-up: 0 dB
• LBO-down: 5 dB
Loss calculations Example 1 (with optical couplers)
Cable loss: 20 km × 0.4 dB/km = 8 dB
Splice loss: 5 splices × 0.2 dB/splice = 1 dB
Loss without LBO : 9 dB
Optical coupler 3.7 dB (Applicable for DBSF protection mode only)
Connector loss: 0.25 dB per connector.
LBO calculation upstream
From the upstream calculation above, the loss must be at least 0 dB and no more than
29 dB in the AFM transmit to network receive direction.
Cable loss is 9 dB + 3.7 dB (optical coupler) > x = 0 dB, → 0 dB LBO (upstream) is
sufficient
Cable loss is 12.7 dB + 0 dB (LBO-up) = 12.7 dB < y = 29 dB, → Minimum signal
strength is okay)
So 0 dB LBO in the upstream direction should be used.
LBO calculation downstream
From the downstream calculation above, the loss must be at least 10 dB and no more
than 29 dB in the network transmit to AFM receive direction.
Cable loss is 9 dB + 3.7 dB (optical coupler) > z = 10 dB, → 0 dB LBO
(downstream) is sufficient
Cable loss is 12.7 dB + 0 dB (LBO-down) = 12.7 dB < y = 29 dB (minimal signal
strength is okay)
So 0 dB LBO in downstream direction should be used.
Engineering work order
The work order should specify the following:
• LBO-up: 0 dB
• LBO-down: 0 dB

Daisychain LBO calculation

The calculations for the co-located daisychaining of an AFMO LPA920 to another
LPA920 AFMO are similar to those above, but due to the missing cable attenuation a
15 dB LBO is required in both upstream and downstream legs of the daisy chain. If
optical couplers are installed according to “DBSF protection mode; daisychaining”
(p. 6-183), a 10 dB LBO is sufficient for upstream and downstream. These values
should be entered into the EWO. The calculations are usually not required if the
daisy-chain is confined to within a single building.

ATM xDSL synchronization and timing

Purpose
This section describes synchronization and timing for the different AFM types and for
the APs the BB subsystem of the AnyMedia ® Access System.

Contents

Synchronization and timing for E3/DS3 ATM network feeder interface 6-194
Synchronization and timing for E1 ATM network feeder interface 6-196
Synchronization and timing for STM-1/OC-3c ATM network feeder 6-198
interface
ATM xDSL timing 6-200
Synchronization and timing for the AnyMedia ® LAG 4300 Shelf 6-201

Synchronization and timing for E3/DS3 ATM network feeder

interface
...................................................................................................................................................................................................................................

E3/DS3 timing
The E3/DS3 timing source is used for the following:
• Timing the transmit signals for the feeder ports
• Sourcing the network timing reference for ATM xDSL APs (see “ATM xDSL
timing” (p. 6-200)).
The timing source used by the AFME3 LPA911 and the AFMDS3 LPA901 is
provisionable. The choices are as follows:
• Line-timed from the input of E3/DS3 port 1 (default value for AFME3)
• Free-running (default value for AFMDS3). If free-running is chosen, the xDSL APs
attempt to get the network timing reference from the COMDAC. If there is no
COMDAC, the AP does not send a traceable network timing reference to the
customer modem.
When the timing mode is set to line-timed, the AFME3 LPA911 and the AFMDS3
LPA901 recover timing from the E3/DS3 input that connects toward the ATM network
(E3/DS3 port 1). They distribute the recovered timing to the E3/DS3 port 2
(downstream) interface and also to the output of E3/DS3 port 1 (that means, the
E3/DS3 port 1 output is line-timed). The AFME3 LPA911 and the AFMDS3 LPA901
recover and distribute timing in this fashion regardless where they are in a daisy-chain,
or if they are operating alone. Therefore, the AFME3 LPA911 and the AFMDS3
LPA901 recover timing from E3/DS3 port 1 regardless of whether E3/DS3 port 1 is
connected to the ATM transport network or to E3/DS3 port 2 of another AFME3
LPA911 or AFMDS3 LPA901.
When the timing mode is set to free-running, all E3/DS3 timing is derived from an
internal crystal oscillator with an accuracy of ± 20 parts per million (ppm).
When duplex AFME3s LPA911 or AFMDS3s LPA901 are used, the timing source
(whether line-timed or free-running) is that of the active AFM.

E3/DS3 timing failures

When the timing mode is set to line-timed, the AnyMedia ® Access System uses the
following external criteria to determine if E3/DS3 port 1 has failed for synchronization
purposes:
• Loss of signal (LOS).
• Loss of frame (LOF).
• HBER (10 consecutive severely errored seconds [SESs]).
If the E3/DS3 port 1 signal fails, all E3/DS3 timing is derived from the same timing
source used when the AFME3 LPA911 or AFMDS3 LPA901 is provisioned for
free-running. When the E3/DS3 port 1 failure clears, the timing source automatically
changes back to line-timed.
...................................................................................................................................................................................................................................
6-194 363-211-586
Issue 6, July 2007
System planning and engineering for ATM xDSL services Synchronization and timing for E3/DS3 ATM network
feeder interface

When the timing mode is set to free-running, all E3/DS3 is derived from the internal
oscillator regardless of the health of the E3/DS3 port 1 signal.

Synchronization and timing for E1 ATM network feeder

E1 timing
The E1 timing sources are used for the following:
• Timing the transmit signals of the feeder ports
• Sourcing the network timing reference for ATM xDSL APs (see “ATM xDSL
timing” (p. 6-200)).
The timing mode used by the AFME1 feeder transmitter is provisionable. The choices
are as follows:
• Line-timed from one E1 receive line out of eight lines (default value)
In this mode all 8 E1s are line-timed from one E1 receive line. The user selects a
primary and secondary source. Default primary source is feeder port 1, default
secondary source is feeder port 2.
If the active timing source fails, a non-revertive switch to the second provisioned
timing source is performed. If both fail, a revertive switch to the free-running
oscillator occurs.
In the line-timed mode the operator can perform a manual switch of the timing
source by selecting the primary or secondary timing source as the active source.
• Free-running
When the timing mode is set to free-running, all E1 transmit timing is derived from
an internal crystal oscillator with an accuracy of ± 32 parts per million (ppm).
In IMA mode the IMA links can be provisioned in the following Tx clocking modes:
• Independent transmit clock (ITC) mode
In this transmit clock mode each feeder and its associated link is independently
timed from its own input.
• Common transmit clock (CTC) mode.
In this transmit clock mode all feeders and their associated links are timed from the
same source (line-timed or free-running) as described above.
Note that, for a group of E1 lines, all timing source provisioning is entered once and
applies to all lines (that means, it is not possible to provision 4 E1s as free-running and
4 as line-timed).
In both IMA timing modes, the xDSL network timing reference is also taken from the
provisioned primary or secondary feeder port. Only if both of these ports have detected
a failure on their receive signals does the network timing reference source shift to the
local clock.

E1 timing failures
When the timing mode is set to line-timed, the AnyMedia ® Access System uses the
following external criteria to determine if E1 line providing the timing source has
failed for synchronization purposes:
• Loss of signal (LOS)
• Loss of frame (LOF)
• Alarm Indication Signal (AIS)
• HBER.
The user can provision each of the eight E1 ports as primary and secondary timing
source. Default primary source is feeder port 1, default secondary source is feeder port
2.
If the active timing source fails, a non-revertive switch to the second provisioned
timing source is performed. If both fail, a revertive switch to the free-running oscillator
occurs.

Synchronization and timing for STM-1/OC-3c ATM network

feeder interface
...................................................................................................................................................................................................................................

STM-1/OC-3c timing
The STM-1/OC-3c timing source is used for the following:
• Timing the transmit signals for the feeder ports
• Sourcing the network timing reference for ATM xDSL APs (see “ATM xDSL
timing” (p. 6-200)).
The timing source used by the AFMO is provisionable. The choices are as follows:
• Line-timed from the input of STM-1/OC-3c port 1 (default value)
• Free-running. If free-running is chosen, the xDSL APs attempt to get the network
timing reference from the COMDAC. If there is no COMDAC, the AP does not
send a traceable network timing reference to the customer modem.
When the timing mode is set to line-timed, the AFMO recovers timing from the
STM-1/OC-3c input that connects toward the ATM network (STM-1/OC-3c port 1). It
distributes the recovered timing to the STM-1/OC-3c port 2 (downstream) interface and
also to the output of STM-1/OC-3c port 1 (that means, the STM-1/OC-3c port 1
output is line-timed). The AFMO recovers and distributes timing in this fashion
regardless where it is in a daisy-chain, or if it is operating alone. Therefore, the AFMO
recovers timing from STM-1/OC-3c port 1 regardless of whether STM-1/OC-3c port 1
is connected to the ATM transport network or to STM-1/OC-3c port 2 of another
AFMO.
When the timing mode is set to free-running, all STM-1/OC-3c timing is derived from
an internal crystal oscillator with an accuracy of ± 20 parts per million (ppm).
When duplex AFMOs are used, the timing source selected (whether line-timed or
free-running) will be that of the active AFMO. Use of duplex AFMOs assumes the use
of duplex feeders. Because of the AFMO cross-couple feature, it is possible for either
of the two feeders to be active for a given active AFMO; which feeder is active is
independent of which AFMO is active. When set to line-timing, the AFMO receives
timing from whichever feeder is active.

STM-1/OC-3c timing failures

When the timing mode is set to line-timed, the AnyMedia ® Access System uses the
following external criteria to determine if STM-1/OC-3c port 1 has failed for
synchronization purposes:
• Loss of signal (LOS).
• Loss of frame (LOF).
• Line/MS AIS (AIS-L/MS-AIS)

If the STM-1/OC-3c port 1 signal fails, all STM-1/OC-3c timing is derived from the
same timing source used when the AFMO is provisioned for free-running. When the
STM-1/OC-3c port 1 failure clears, the timing source automatically changes back to
line-timed.
When the timing mode is set to free-running, all STM-1/OC-3c timing is derived from
the internal oscillator regardless of the health of the STM-1/OC-3c port 1 signal.
When duplex AFMOs are used, and the active AFM’s timing mode is set to line-timed,
then in the event of a timing failure, that AFM will receive timing from the other
feeder.

ATM xDSL timing

ADSL timing
Timing for each ADSL interface is derived from an internal crystal oscillator in the
ADSL AP. This timing reference is used regardless of the status of the ATM feeder
signal from the network.
Also, the ADSL16p, ADSL32p, ADSL16i, ADSL32i, and P32A32 support network
timing reference (NTR) as specified in ANSI T1.413. Network timing reference is
required in addition to internal oscillator timing for certain voice and data applications.
When the AFM is line-timed, these APs get their timing from the AFM. When the
AFM is free-running, these APs attempt to get the network timing reference from the
COMDAC If there is no COMDAC, the AP does not send a traceable network timing
reference to the customer modem.

SHDSL timing
The SHDSL AP LPS702 supports NTR as the ADSL APs. Timing for each SHDSL
interface is derived from an internal crystal oscillator in the SHDSL AP. This timing
reference is used regardless of the status of the ATM feeder signal from the network.

Timing for an E1IMA AP

Timing for an E1IMA AP is derived from an internal crystal oscillator on the AP. The
E1IMA AP does not receive the distribution clock from the AFM.
Network timing reference is not provided to a cascaded shelf.

Synchronization and timing for the AnyMedia ® LAG 4300

Shelf
...................................................................................................................................................................................................................................
Both rows of the AnyMedia ® LAG 4300 Shelf form one single NB subsystem, while
the BB subsystem in the upper row is logically completely separated from that in the
lower row. That is why BB timing references can only be distributed to the COMDAC
by the BB subsystem in the upper row. However, NB timing references can be
distributed to both BB subsystem and there is no difference between the two
subsystems in terms of utilization of timing references and provisionable timing modes.

Miscellaneous

Purpose
This section comprises additional high-level information on various topics, e.g. product
reliability, ATM xDSL powering and on the work order.

Contents

ATM xDSL product reliability 6-203

ATM xDSL system powering 6-204
Testing of drops on ATM xDSL application packs 6-205

ATM xDSL product reliability

Definition
ATM xDSL loop access downtime is consistent with the expected values published in
TA-NWT-000909.
(There are no published Telcordia Technologies, Inc. reliability requirements on xDSL
access. Reliability estimates of xDSL hardware based on TR-NWT-000332 are
comparable to the FITL reliability estimates in TA-NWT-000909.)
The ATM xDSL loop access downtime for any individual subscriber line caused by the
AnyMedia ® Access System is expected to be less than an average of 95 minutes per
year. This corresponds to an availability of 99.98193%. The line downtime caused by
hardware failures is expected to be less than an average of 72 minutes per year, while
downtime due to software and procedural errors is expected to be less than 23 minutes
per year. The maintenance rate due to hardware faults is comparable with that of a
fiber in the loop (FITL) system - less than three maintenance actions per 100 lines per
year as required by TR-NWT-000418.

ATM xDSL system powering

Overview
Powering for the ATM xDSL feature requires positioning of the AFM in the preferred
AFM slot or in the AFM protection slot (in duplex mode) where it has access to both
power feeds. If configured for an ATM xDSL services -only system (no POTS
services), there is no need to provide the ringing input.
Refer to the Applications and Planning Guide Overview (363-211-585) for more details
on powering.
Important! If you are upgrading an AnyMedia ® shelf in an already existing DC
rack of type J1C283B-1List1 with high-capacity ADSL packs - including 16 ports
or more - and the shelf is equipped with a PFU500, don’t insert more than a total
of 11 ADSL APs at a maximum per AnyMedia ® shelf because of the higher power
consumption.

Testing of drops on ATM xDSL application packs

Overview
This section describes the metallic line test capabilities of drops on ATM xDSL
application packs. The AnyMedia ® Access System supports integrated testing with test
application pack, manual test access, and external test head access according to
GR-834 on the following ATM xDSL application packs:
• LPA416
• LPA417
• LPA432
• LPA434
• LPA832
• LPS702
• LPS716.

Integrated testing
The integrated testing capability uses the same test application pack (TAP10x/LPZ200)
as used for the narrowband subscriber line testing. It provides basic measurements also
for the ATM xDSL subscriber lines, see “Test capabilities overview” (p. 3-118).

Manual testing
The manual testing capability provides metallic test access to the subscriber line via
the faceplate jack on the CIU. This test access can be used with external test
equipment for example time domain reflectometry (TDR) testing.

External test head testing

As for narrowband subscriber lines, the system supports GR-834 compliant test access
for external test head for ATM xDSL subscriber lines. See “AP test access capabilities”
(p. 3-155), which metallic test access can be provided by ATM xDSL application
packs.

Assumption
The AnyMedia ® Access System supports metallic drop testing of an ADSL circuit only
if there is a NB circuit carried on the same metallic pair as the ADSL circuit. In
addition, the system supports GR-834 test access on drops that carry both POTS and
ADSL and on loops that carry only ATM xDSL services. This metallic access is
compatible with remote test units that support wide band loop testing (e.g., tests in the
ADSL transmission band). Refer to the Applications and Planning Guide Overview
(363-211-585) for drop testing setup.
Important! The COMDAC and CIU must be installed if GR-834 testing of ATM
xDSL lines is required.

Cross-connecting the low-frequency output from the splitter on an ADSL-only AP with

test access relays (e.g., LPA416) can disrupt a POTS call when the ADSL line is
tested. Follow the procedure below to avoid this disruption:
The testing OS (automated testing) or tester (manual testing) should do the following:
1. Obtain the telephone number (automated testing) or ATD (manual testing) of the
POTS line that is cross-connected to the ADSL line from the appropriate data
bases.
2. Get bridging test access to this POTS line.
3. Check for a busy signal.
4. If the POTS line is not busy, access the ADSL line for testing.

Overview
...................................................................................................................................................................................................................................
ATM xDSL turn-up and service activation on an AnyMedia Access System depend on
provisioning of site-specific information. The following are examples of ATM xDSL
Work Orders that can be used by a technician to complete initial turn-up and activate
service on such a system. The shelf may be ATM only or mixed ATM and narrowband.
The ATM feeder may be DS3, E3, STM-1/OC-3c, or E1 IMA. If DS3, E3 or
STM-1/OC-3c, it may also be daisy-chained with other shelves. If daisy-chained, the
new shelf is always added at the end of the chain. For clarity and simplicity, a separate
work order is given for each of the three simplex feeder types and two duplex feeder
types.
Important! The following ATM xDSL Work Orders are examples for BB
subsystems housed in an AnyMedia Mainshelf (including subshelves). Work Orders
for BB subsystems housed in an AnyMedia LAG Shelf would be similar, but the
slot numbers would be different.
The Simplex Work Orders are divided into the following parts:
• Part 1, Preliminary Information, covers general information about the system
• Part 2, Installation/Cabling/Connection Information/Software Information, covers
information about the cables and their respective connections
• Part 3, Turn-Up Parameters, identifies the details for all applicable turn-up
procedures
• Part 4, System Activation Parameters, identifies the details for all applicable system
activation procedures.
The Duplex Work Orders are divided into the following parts:
• Part 1, Preliminary Information, covers general information about the system
• Part 2, Installation/Software Information/Turn-Up Parameters, identifies the details
for all applicable turn-up procedures
• Part 3,Cabling/Connection Information, covers information about the cables and
their respective connections
• Part 4, Subshelf Information
• Part 5, System Activation Parameters, identifies the details for all applicable system
activation procedures.

These templates can be modified as needed and adapted to suit individual applications.
They cover a range of cases, from the simple addition of a new ATM virtual
connection on an existing port to complete turn-up and service activation of a new
shelf. For multiple packs and subscribers, copy the forms as needed.
These forms provide information the technician needs when provisioning the system
using the Commands and Procedures turn-up and service activation documentation. The
documentation refers the technician to these forms as needed. Representative
procedural flowcharts from the documentation are included here for convenience.
Finally, depending on the level of technician training and experience, the engineer may
choose to include the following supplementary attachments:
• A list of tools, cables, and circuit packs needed
• Screen shots of at least the more complex GSI screens showing the parameter
values to be entered.
The ATM xDSL Engineering Work Orders for AFMDS3 are:
• “Work Order for ATM xDSL Services — Simplex AFMDS3” (p. A-3)
• “Work Order for ATM xDSL Services — Duplex AFMDS3” (p. A-27).

Work Order for ATM xDSL Services — Simplex AFMDS3

Part 1. Preliminary Information - Simplex AFMDS3

Type of System: AnyMedia Access System

Location
Rack ___________________ Shelf __________________________
Street Address ___________________________________________________
If the shelf already has been turned up, proceed to Part 2B, GSI Connection.
Is shelf being added to a daisy-chain (circle one)? No Yes
If the shelf is not being added to a daisy-chain, skip to
Part 2, Cabling/Connection Information.
If the shelf is being added to a daisy-chain, you need the location of the last shelf in the daisy-chain
so that you can connect AFM Port 1 of the new shelf to AFM Port 2 of this shelf.

Location of Last Shelf in Daisy-Chain

Rack ___________________ Shelf __________________________
Street Address __________________________________________________

ATM xDSL Simplex AFMDS3 Turn-up Procedures Flowchart (Part 1)

Begin of Turn-Up Procedures with simplex AFME3/DS3

TU-605
AFM Installation

TU-610 Verify/Update
AFM Software Load

Shelf connected Shelf connected

directly to ATM Transport Network to a previous shelf (Daisy-Chain)

TU-620a TU-625a
(Single Shelf) (Daisy-Chain)
AFME3/DS3 Cabling AFME3/DS3 Cabling

TU-630 TU-630
(AFME3/DS3 Installed)
Provision Main Shelf Provision Main Shelf

TU-640 Update
Daisy-Chain VPIs

TU-650 Provision
AFME3/DS3 Feeder Port

ATM xDSL Simplex AFMDS3 Turn-up Procedures Flowchart (Part 2)

1
Broadband-only or
a mixed system
xDSL APs required in Mainshelf

TU-660 xDSL AP
no xDSL APs
Installation / Growth
required in Mainshelf

ONU Subshelves
with xDSL APs required

TU-655 OAP
no ONU Subshelves Installation Growth
with xDSL APs required

TU-656
Provision Subshelf

TU-660a xDSL APs

Installation / Growth (ONU)

TU-670a Verify Proper

AFME3/DS3 SystemTurn-Up

End of Turn-Up Procedures with simplex AFME3/DS3

*) To activate the ATM xDSL subscriber services,

follow the next chapter “Activate Service and Test”.

Part 2. Installation/Cabling/Connection/ Software Information - Simplex AFMDS3

A. AFM Installation TU-605

If there is already a circuit pack in Slot 16, does it need to be replaced (circle one)? Yes No

B. GSI Connection OP-610

The following information is needed to connect the GSI to the shelf.
GSI Connection (circle one): Console Port 10BaseT Port LAN
Select Link
PC Port (circle one): COM1 COM2 COM3 COM4 LAN
Log In
Security ID( 1) ________________________________
IP Address: ________ - ________ - ________ - ________ 192.168.160.160

Notes:
1. The initial default setting is ″public″.

Important! If only performing Service Activation, skip to Part 4, Service

Activation Parameters.

C. Verify AFM Software TU-610

Software Version Required ______________________

D. Cabling TU-620
The following information is needed only if a new shelf or AFM pack is to be installed.
Feeder Cabling Source (check one of the following)
_____ If not daisy-chained, ATM Feeder ID _______________________________
_____ If daisy-chained, the cable source is last shelf listed above in Part 1, Preliminary Information.

Is the AFM to be connected to a LAN for remote operations (circle one)? Yes No
If the AFM is to be connected to a LAN, connect 10BaseT cable assembly to _________________

Part 3. Turn-up Parameters - Simplex AFMDS3

E. Communications TU-630
Security ID: _______________________
IP Configuration

IP Interfaces IP Address Subnet Mask

10BaseT: ____________ _____________
ATM: ____________ _____________
Console: ____________ Default: 192.168.0.1 _____________
Default Router (circle one):
10BaseT ____________
ATM
Autonomous Messages Destination
Selected Address: (list as many addresses as needed)
______________________
______________________
______________________
______________________
______________________
______________________
Note: Neither the IP addresses of the GSI and/or the EMS should be entered here because they will
be entered automatically, nor the IP address of the COMDAC although the OAM&P information of
the COMDAC may be routed via the AFM.

F. System Identification TU-630

Select to Set: AFM
New Value: (0-255 characters) ______________________________________

G. System Configuration TU-630

Protection Mode: Simplex
Distribution Port Numbering Mode (circle Physical Logical
one):
AFM Configuration: xDSL
Customer Configuration: 1 2
Main Shelf Type: AnyMedia AS AnyMedia AS 800
High BER Algorithm: Fixed CRC Threshold Fixed BER Threshold

H. System Information TU-630

Contact (0-255 characters) _____________________________
Location (0-255 characters) _____________________________

Main Shelf Misc. Information (0-100 characters) _____________________________

I. Global ATM Parameters TU-630

VPI VCI F5 EtoE CC
(1 - 255) (32 - 64)
ATM Operations Channel: _____________ _____________ _____________
default: 254 default: 32 default: Disabled

Upstream Downstream
Shelf PCR (cps): _____________ _____________

Service Category
CBR rt-VBR nrt-VBR
Shelf Overbooking Factor _________ _________ ________
Guaranteed BW US - weight _________ _________ ________
Admissible BW Upstream (cps): _________ _________ ________
Admissible BW Downstream (cps): _________ _________ ________
Cell Loss Ratio (10-9) _________ _________ ________

J. Daisy-Chain upstream VP Information TU-630

(Note: These VPs are all those in use on upstream shelves of the daisy-chain and their VP type on
the new shelf is upstream.)
VPI VP Type Service Category
_______________ upstream _______________
_______________ upstream _______________
_______________ upstream _______________
_______________ upstream _______________
_______________ upstream _______________

K. Shelf VP Information TU-630

The default Shelf VP must be changed if 255 is already in use on another shelf in the daisy chain.
VPI VP Type Service Highest VCIAllowed F4 VP Segment
Category (circle one)

255 Shelf UBR 1999 - LPA901 Disabled Endpoint

1023 - LPA900
________ Shelf ________ ________ Disabled Endpoint
________ Shelf ________ ________ Disabled Endpoint
________ Shelf ________ ________ Disabled Endpoint
________ Shelf ________ ________ Disabled Endpoint

L. Shelf Level Traffic Thresholds TU-630

Note, that the TCA for a given parameter is inhibited by setting the threshold to ″0″.
15-min interval 24-hour interval
(0 to 318000 cells/frames) (0 to 30.6 x 106
cells/frames)
Cells dropped due to PPD _____________ _____________
Cells dropped due to EPD _____________ _____________
Cells dropped due to buffer overflow _____________ _____________
AAL5 Frames dropped due to EPD _____________ _____________

M. Daisy-Chain Information TU-640

Update the VP Information for the other shelves in the daisy-chain to include the new VPs
provisioned on this shelf. They are all of VP type downstream on the other shelves, regardless of
their type on the new shelf.
First Shelf in Daisy-Chain
Location
Rack _______________________ Shelf _________________________
Street Address ___________________________________________________

GSI Connection (circle Local at Console Port Local at 10BaseT Port Remote LAN
one):
IP Address _______________________________
Security ID _______________________________

Downstream VP Information
VPI VP Type Service Category F4 VP Segment
(circle one)

Downstream ___ Disabled Endpoint

__________ Downstream _____________ Disabled Endpoint
__________ Downstream _____________ Disabled Endpoint
__________ Downstream _____________ Disabled Endpoint
__________ Downstream _____________ Disabled Endpoint
Repeat above information for all shelves in the daisy-chain.

N. Feeder Port 2 Parameters TU-640

In a daisy-chain, you must enable and provision Port 2 of the existing shelf that feeds the new shelf.
Use the following parameters:
Administrative State: Enable Disable
Cell Scrambling (circle one): Enable Disable
Single Bit Error Correction (circle one): Enable Disable
Frame Format (circle one): HEC PLCP
Line Length (circle range): 0-224’ 225-450’

O. Feeder Port 1 Parameters TU-650

Timing Source (circle one): Free-running Line-timed
Cell Scrambling (circle one): Enable Disable
Single Bit Error Correction (circle one): Enable Disable
Frame Format (circle one): HEC PLCP
Line Length (circle range): 0-224’ 225-450’

P. Subshelf TU-655, TU-656

OAP slot
ONU
Shelf number (1-7) ____________________________________
Subsite ID ____________________________________
Physical ID ____________________________________
Contact ____________________________________
Location ____________________________________
Parent slot (OAP slot; 2-14) ____________________________________
Configured State ____________________________________

ATM ADSL Service Activation Procedures Flowchart

ATM SDSL Service Activation Procedures Flowchart

ATM SHDSL Service Activation Procedures Flowchart

E1IMA Shelf Cascading Procedures Flowchart

Begin of Shelf Cascading Procedures

Slot not equipped Slot equipped

TU-698
LPA941 Upgrade to R1.25

TU-660
AP Installation/Growth

SA-301
SA-302 Wiring the E1 feeder Initiate E1IMA
connections for E1IMA AP Cascading

Provision/Retrieve E1 port
parameters (set further ports
in service and assign FRP)

IMA mode Required Change to UNI mode required

Provision/Retrieve
Add/Delete IMA Links
UNI Mode

Provision ATM
Virtual Connection

SA-321 Verify
Transmission Continuity

End of Shelf Cascading Procedures

Part 4. Service Activation Parameters - Simplex AFMDS3

Repeat for as many packs, ports, and cross-connects as required for the Mainshelf.

A. Customer Information
Name ____________________________ Phone Number_____________________
Street Address ________________________________________________________
If adding a subscriber on new, uncabled port on an existing, provisioned pack, go to Part 4C Cabling
Information. If only adding an ATM virtual connection on an existing cabled port, go to Part 4F,
ATM Traffic Parameters.

B. Pack Provisioning Information SA-300; SA-301 TU-660; TU-660a

ATM xDSL Slot in AP-1 AP-2 AP-3 AP-4 AP-5 AP-6 AP-7 AP-8
Mainshelf (circle
one):
AP-9 AP-10 AP-11 AP-12 AP-13 AP-14 AP-15( 1)
Pack Type (circle ADSL SDSL SHDSL
one):
If E1IMA AP, complete additionally the following:
Î PM Enable all E1 Ports (✓)
Interval (circle one): 15 Minutes 24 Hours

Notes:
1. Not applicable for an E1IMA AP

C. Cabling Information SA-300; SA-302; TU-660; TU-660a

NOTE: In a mixed narrowband and ATM xDSL configuration it is assumed that the NB subsystem
has already been installed and turned up before turning up the BB subsystem.

Case 1a: ADSL plus existing NB using an ADSL4p, ADSL8p, ADSL16p, ADSL4i, or ADSL16i AP
(telephone company allows common side connections at the FDI/MDF)
ATM xDSL Slot ____________ ATM xDSL Port ___________

From NB AP Cable _ Pair __

NB Circuit Input to ADSL AP Cable _________ Pair __________
NB+ADSL Output of ADSL AP Cable _________ Pair __________
FDI/MDF Distribution Pair Cable _________ Pair __________

Case 1b: Adding ADSL only using an ADSL4p, ADSL8p, ADSL16p, ADSL4i AP, or ADSL16i (at
FDI/MDF)
ATM xDSL Slot ____________ ATM xDSL Port ________________

From ADSL AP Cable _ Pair __

FDI/MDF Distribution Pair Cable _________ Pair __________

Case 1c: Adding ADSL and POTS using a P32A32 AP (at the FDI/MDF)
ATM xDSL Slot ____________ ATM xDSL Port ________________

From combo AP Cable _ Pair __

FDI/MDF Distribution Pair Cable _________ Pair __________

Case 1d: Adding ADSL and POTS using a POTSZF and ADSL32p or ADSL32i AP (at the FDI/MDF)
POTS/ISDN Slot __________ POTS/ISDN Port ________________
ATM xDSL Slot ____________ ATM xDSL Port ________________

From POTS/ISDN AP Cable _ Pair __

From ADSL AP Cable _________ Pair __________

FDI/MDF Distribution Pair Cable _ Pair __

Case 1e: Adding SDSL using a SDSL16 AP (at the FDI/MDF)

ATM xDSL Slot ____________ ATM xDSL Port ________________

From SDSL16 AP Cable _ Pair __

FDI/MDF Distribution Pair Cable _________ Pair __________

Case 1f: Adding SHDSL using an SHDSL16 AP (at the FDI/MDF)

ATM xDSL Slot ____________ ATM xDSL Port ______________

From SHDSL16 AP Cable _ Pair __

FDI/MDF Distribution Pair Cable _________ Pair __________

Case 2: Adding ADSL to NB using protector blocks (ADSL4p, ADSL8p, ADSL16p, ADSL4i AP, or
ADSL16i)
Protector Block Jack Locations
These locations are determined by the engineer from either of the following:
— cable and pair
— shelf, slot, port
Single plug end of the patch cord:
Subscriber loop Jack Location________
Double plug end of the patch cord:
NB circuit input to ADSL AP Jack Location________
NB+ADSL output of ADSL AP Jack Location________

Case 3: Cabling the E1IMA AP to the DDF

E1IMA AP DDF
1 -------------------->

2 -------------------->

3 -------------------->

4 -------------------->
Tx
5 .

6 .

7 .

4
Rx
5

D. Transmission Parameters SA-300

Pack Type (circle one): ADSL SDSL SHDSL

Case 1a: ADSL Transmission Parameters

Type of Rate Adaptation (circle one): Flexible Explicit

If you selected Flexible, complete Part A. If you selected Explicit, complete Part B. After completing
Part A or Part B, continue with Additional ADSL Transmission Parameters.

Part A.
Maximum Upstream Bit Rate _________kbps (any multiple of 32 from 64 to 1440 kbps)
Maximum Downstream Bit Rate _________kbps (any multiple of 32 from 64 to 13120 kbps)
Minimum Upstream Bit Rate _________kbps (any multiple of 32 from 64 to 1440 kbps)
Minimum Downstream Bit Rate _________kbps (any multiple of 32 from 64 to 13120 kbps)

Part B.
Downstream, Option 1 ___________ (Multiples of 32, from 64 to 8160 kbps)
Downstream, Option 2 ___________ (Multiples of 32, from 64 to 8160 kbps)
Downstream, Option 3 ___________ (Multiples of 32, from 64 to 8160 kbps)
Downstream, Option 4 ___________ (Multiples of 32, from 64 to 8160 kbps)
Upstream, Option 1 ___________ (Multiples of 32, from 64 to 1440 kbps)
Upstream, Option 2 ___________ (Multiples of 32, from 64 to 1440 kbps)
Upstream, Option 3 ___________ (Multiples of 32, from 64 to 1440 kbps)
Upstream, Option 4 ___________ (Multiples of 32, from 64 to 1440 kbps)

Additional ADSL Transmission Parameters

Upstream SNR margin in dB (integer from 0 to 15) _________________________
Downstream SNR margin in dB (integer from 0 to 15) _________________________

Upstream Interleave Depth (circle one) 1 2 4 8 16

Downstream Interleave Depth (circle one) 1 2 4 8 16 32 64
Upstream Latency (circle one): Fast Interleaved
Downstream Latency (circle one): Fast Interleaved
Upstream Parity Bytes per R-S code word (circle one): 0 2 4 6 8 10 12 14 16
Downstream Parity Bytes per R-S code word (circle 0 2 4 6 8 10 12 14 16
one):

Upstream DMT Symbols per R-S code word (circle one): 1 if interleaved depth =1
If latency = interleaved: 1 2 4 8 16 32 64
Downstream DMT Symbols per R-S code word (circle one): 1 if interleaved depth =1
If latency = interleaved: 1 2 4 8 16 32 64

PSDM in –dBm/Hz (integer from 40 to 60) _____________________________

Case 1b: ADSL2/ADSL2+ Transmission Parameters

Additional ADSL2/ADSL2+ Transmission Parameters

Type of Rate Adaptation: Flexible Flexible, Dynamic(1)

SNR Margin, dB US ________dB (0 to 15, in steps of 1)

DS ________dB (0 to 15, in steps of 1)

Upshift SNR Margin, dB US ________dB (0 to 31, in steps of 0.1)

DS ________dB (0 to 31, in steps of 0.1)

Upshift SNR Margin Time, sec US ________sec (0 to 16383, in steps of 1)

DS ________sec (0 to 16383, in steps of 1)

Downshift SNR Margin, dB US ________dB (0 to 31, in steps of 0.1)

DS ________dB (0 to 31, in steps of 0.1)

Downshift SNR Margin Time, sec US ________sec (0 to 16383, in steps of 1)

DS ________sec (0 to 16383, in steps of 1)

Min SNR Margin, dB US ________dB (0 to 31, in steps of 0.1)

DS ________dB (0 to 31, in steps of 0.1)

Max SNR Margin, dB US ________dB (0 to 31, in steps of 0.1)

DS ________dB (0 to 31, in steps of 0.1)

Max Aggregate Tx Power, dBm (3) US ________dBm (0 to 25.5, in steps of 0.1)

DS ________dBm (0 to 25.5, in steps of 0.1)

Max Tx PSD, dBm/Hz US ________dBm/Hz -60 to -38

DS ________dBm/Hz -60 to -40

Max Data Rate, kbps US ________kbps 64 to 2048, in steps of 32

DS ________kbps 64 to 30016, in steps of 32

Min Data Rate, kbps US ________kbps 64 to 2048, in steps of 32

DS ________kbps 64 to 24000, in steps of 32

Interleave, msec US ________msec 0 to 254, in steps of 1
DS ________msec 0 to 254, in steps of 1

Latency US ________ interleaved, fast

DS ________ interleaved, fast
2
Minimum INP ( ) US auto auto, no-symbol, half-symbol,
one-symbol, two-symbols
DS auto

PSD Mask US ________ Default, Mask1 to Mask9 ( 4)

DS ________ Default

Enable/Disable READSL2 DS ________ Disabled, Enabled

Enable/Disable automatic Power Mgmt (2) DS Disabled Disabled, Wide Band, Narrow Band
2
Min L0 time, sec ( ) DS ________sec 0 to 255, in steps of 1
Min L2 time, sec (2) DS ________sec 0 to 255, in steps of 1
2
Max Aggregate Tx Power Reduc. ( ) DS ________dBm 0 to 31, in steps of 0.1

Notes:
1. The Type of rate adaptation Dynamic is supported only by LPA833.
2. Not supported by LPA420 and LPA833.
3. The only supported value by LPA420 and LPA833 is 10.0 dbm.
4. Mask1 to Mask9 in upstream direction are used when the line is operating in Annex M mode (requires a
compatible modem at the other end). Not supported by LPA438.

Case 2: SDSL Transmission Parameters

___Existing Profile ID ______________
Name: _______________________________

_New Profile ID ____________ Existing profile used to create new profile

Name: _______________________________
Name: _______________________________
ID ______________ New profile (Technician fills in the ID supplied by
the GSI)
Type of Rate Adaptation (circle one): Flexible Explicit
If you selected Flexible, complete Part A. If you selected Explicit, complete Part B. After completing
Part A or Part B, continue with Additional SDSL Transmission Parameters.

Part A.
Maximum Bit Rate ________________kbps (144, 272, 400, 528, 784, 1168, 1552, 2320)
Minimum Bit Rate ________________kbps (144, 272, 400, 528, 784, 1168, 1552, 2320)
Upstream and downstream SNR margin in dB (0 to 15): ________________

Part B.
Explicit Bit Rate ________________kbps (144, 272, 400, 528, 784, 1168, 1552, 2320)

Additional SDSL Transmission Parameters

TX/RX Scramble (circle one): Enable Disable
ATM Cell Scramble (circle one): Enable Disable
COSET (circle one): Enable Disable

Case 3: SHDSL Transmission Parameters

___Existing Profile ID ______________
Name: _______________________________
___New Profile ID ______________ Existing profile used to create new profile
Name: _______________________________
Name: _______________________________
ID ______________ New profile (Technician fills in the ID
supplied by the GSI.)
Type of Rate Adaptation (circle one): Flexible Explicit
If you selected Flexible, complete Part A. If you selected Explicit, complete Part B.
After completing Part A or Part B, continue with Additional SHDSL Transmission Parameters.

Part A.
Maximum Bit Rate ________________kbps (Multiples of 64, from 192 to 2304 kbps)
Minimum Bit Rate ________________kbps (Multiples of 64, from 192 to 2304 kbps)

Part B.
Explicit Data Rate ________________kbps (Multiples of 64, from 192 to 2304 kbps)

E. Port Provisioning Information SA-300

ATM xDSL Slot AP-1 AP-2 AP-3 AP-4 AP-5 AP-6 AP-7 AP-8
(circle one):
AP-9 AP-10 AP-11 AP-12 AP-13 AP-14 AP-15( 1)
ATM xDSL Port (1 to 32): ___________

Notes:
1. Not applicable for E1IMA AP.

If ADSL, complete the Start Up Mode:

Start Up Mode (circle one): Multimode G994.1 (G.hs) T1.413 adsl2 adsl2+

xDSL Transmission Profile ID _________________________

(If a new profile was created in Part 5D, enter that ID.)
PM Profile: ___________________________
1
DMT Profile( ): ___________________________
Failure Report Profile: ___________________________
Î Enable AIS (✓)

Notes:
1. Only for ADSL2/ADSL2+

If SHDSL, complete additionally the following:

Î Bonding (✓)
SNR Margin Threshold: _______________________ dB (integer from 0 to 15)
Loop Attenuation Threshold: _______________________ dB (integer from 0 to 127)
Annex Mode (circle one): Annex A Annex B

If E1IMA AP, complete additionally the following:

Loopback (circle one): No Loop Line Loop

Failure Report Profile: _______________________________

F. IMA Provisioning for E1IMA AP only TU-650a

IMA Mode (circle one): IMA UNI
If UNI, UNI Mode Link (circle one): 1 2 3 4 5 6 7 8
Î PM Enable (✓)
Î AIS Enable (✓)
Go to Part G.- E1 Feeder Provisioning Information TU-650a

If IMA, fill out the remainder of Part G: IMA Group Configuration

Î Inhibit IMA Group (✓)
Provisioned Protocol (circle one): V1.0 V1.1
Symmetry Mode (check one): Î Symmetric Configuration & Operation
Î Symmetric Configuration & Asymmetric Operation

IMA Mode (circle one): IMA UNI

Sufficient Tx Link (circle one): 1 2 3 4 5 6 7 8
Sufficient Rx Link (circle one): 1 2 3 4 5 6 7 8
Tx Frame Length (circle one): 32 64 128 256
Tx Amas IMA ID Î 0 (0 to 256)
Tx Clocking Mode (check one): Î Common
Î Independent
Maximum Differential Delay (5 to 45 msec, 10ms increments): 25 msec _____________
Failure Report Profile
Synchronization Parameters
Alpha (circle one): 1 2
Beta (circle one): 1 2 3 4 5
Gamma (circle one): 1 2 3 4 5
IMA Links (circle selections): 1 2 3 4 5 6 7 8

G. ATM Traffic Parameters SA-300

___ Existing Profile ID ___________________
Name ________________

G. ATM Traffic Parameters SA-300

___ New Profile ID ___________________
Name ________________ Existing profile used to create new
profile
Name ________________ New Profile
ID ___________________ New profile (Technician fills in the ID
supplied by the GSI.)
Service Category CBR rt-VBR nrt-VBR UBR
(circle one):
Profile Name: _______________________________ (0 - 64 characters)
The specific profile parameters needed will depend on the service category.

Case 1: CBR
Peak Cell Rate Upstream _________________cells/sec (150 to 108,940)
Peak Cell Rate Downstream _________________cells/sec (150 to 108,940)
PCR Cell Delay Variation Tolerance _________________ms (0.000680 to 1330)
(CDVT)

Case 2: rt-VBR, nrt-VBR

Peak Cell Rate Upstream _________________cells/sec (150 to 108,940)
Peak Cell Rate Downstream _________________cells/sec (150 to 108,940)
PCR CDVT _________________ms (0.000680 to 1330)

Sustainable Cell Rate Upstream _________________cells/sec (150 to 108,939)

Sustainable Cell Rate Downstream _________________cells/sec (150 to 108,939)
SCR CDVT _________________ms (0.000680 to 1330)

Maximum Burst Size Upstream _________________cells (1 to 100)

Maximum Burst Size Downstream _________________cells (1 to 210)

Cell Loss Priority (circle one): CLP (0) CLP (0 + 1)

Cell Tagging (circle one): True False
Frame Discard (circle one): True False

Case 3: UBR

Peak Cell Rate Upstream _________________cells/sec (150 to 108,940)

Peak Cell Rate Downstream _________________cells/sec (150 to 108,940)
PCR (CDVT) _________________ms (0.000680 to 1330)

Cell Tagging (circle one): True False

Frame Discard (circle one): True False

H. Cross-Connect Provisioning SA-300

If the Shelf VPI (see Part 4c above) is used for the Feeder VPI, then a feeder VCI must be specified
as well. Complete Part A; otherwise, complete Part B.

Part A. Virtual Channel Cross-Connect

Feeder VPI ________________________
Feeder VCI ________________________
F5 Segment (circle one): Disabled Endpoint

Slot Number in AP-1 AP-2 AP-3 AP-4 AP-5 AP-6 AP-7 AP-8
Mainshelf (circle
one):
AP-9 AP-10 AP-11 AP-12 AP-13 AP-14 AP-15
ATM xDSL Port (1 to 32): ________
Subscriber VPI ________________
Subscriber VCI ________________
ATM Traffic Profile Name ________________
Traffic Statistics Profile ________________
Circuit ID ________________

Part B. Virtual Path Cross-Connect

Feeder VPI ___________________________
F4 Segment (circle one): Disabled Endpoint
Slot Number (circle AP-1 AP-2 AP-3 AP-4 AP-5 AP-6 AP-7 AP-8
one):
AP-9 AP-10 AP-11 AP-12 AP-13 AP-14 AP-15
ATM xDSL Port (1 to 32): ________
Subscriber VPI ________________
Subscriber VCI ________________
...................................................................................................................................................................................................................................
363-211-586 A-25
Issue 6, July 2007
ATM xDSL Engineering Work Orders for AFMDS3 Work Order for ATM xDSL Services — Simplex AFMDS3

Part B. Virtual Path Cross-Connect

ATM Traffic Profile Name ________________
Traffic Statistics Profile ________________
Circuit ID ________________

SA-300; TU-640
If this shelf is in a daisy-chain, you must update the VP list on the other shelves in the daisy-chain
with the feeder VP used in the new cross-connect. The following information is needed for each shelf
in the daisy-chain.
Location
Rack _______________________ Shelf _________________________
Street Address _________________________________________________________

GSI Connection (circle one): Console Port 10BaseT Port LAN

IP Address _______________________________
Security ID _______________________________

Work Order for ATM xDSL Services — Duplex AFMDS3

Part 1. Preliminary Information - Duplex AFMDS3

Type of System: AnyMedia Access System

Location of Last Shelf in Daisy-Chain

Rack ___________________ Shelf __________________________
Street Address __________________________________________________

ATM xDSL Duplex AFMDS3 Turn-up Procedures Flowchart (Part 1)

Begin of Turn-Up Procedures with duplex AFME3/DS3

TU-605
AFM Installation

TU-610 Verify/Update
AFM Software Load

TU-630
(AFME3/DS3s Installed)
Provision Main Shelf

Shelf connected directly Shelf connected

to ATM Transport Network to a previous shelf (Daisy-Chain)

TU-640 Update
Daisy-Chain VPIs

TU-2605 Installation
of Second AFM

TU-2610 Provision Main

Shelf for Duplex Mode

TU-650 Provision
AFME3/DS3 Feeder Port

Shelf connected directly Shelf connected

to ATM Transport Network to a previous shelf (Daisy-Chain)

TU-2620a Duplex TU-2625a Duplex

(Single Shelf) (Daisy-Chain)
AFME3/DS3 Cabling AFME3/DS3 Cabling

ATM xDSL Duplex AFMDS3 Turn-up Procedures Flowchart (Part 2)

1
Broadband-only or
a mixed system

xDSL APs required in Mainshelf

TU-660 xDSL AP
no xDSL APs
Installation / Growth
required in Mainshelf

ONU Subshelves
with xDSL APs required

TU-655 OAP
no ONU Subshelves Installation Growth
with xDSL APs required

TU-656
Provision Subshelf

TU-660a xDSL APs

Installation / Growth (ONU)

TU-670a Verify Proper

AFME3/DS3 SystemTurn-Up

End of Turn-Up Procedures with duplex AFME3/DS3

*) To activate the ATM xDSL subscriber services,

follow the next chapter “Activate Service and Test”.

Part 2. Installation/Software Information/Turn-up Parameters - Duplex AFMDS3

A. Install First AFM TU-605

If there is already a circuit pack in Slot 16, does it need to be replaced (circle one)? Yes No

B. GSI Connection OP-610

The following information is needed to connect the GSI to the shelf.
GSI Connection (circle one): Console Port LAN
Select Link
PC Port (circle one): COM1 COM2 COM3 COM4 LAN
Log In
Security ID( 1) ________________________________
IP Address: ________ - ________ - ________ - ________ 192.168.160.160

Notes:
1. The initial default setting is ″public″.

Important! If only performing Service Activation, skip to Part 4, Service Activation

Parameters.

C. Verify AFM Software TU-610

Software Version Required ______________________

D. Communications TU-630
Security ID: _______________________
IP Configuration
IP Interfaces IP Address Subnet Mask
10BaseT: ____________ _____________
ATM: ____________ _____________
Console: ____________ Default: 192.168.0.1 _____________
Default Router (circle one):
10BaseT ____________
ATM
Autonomous Messages Destination
Selected Address: (list as many addresses as needed)
______________________
______________________

______________________
______________________
______________________
______________________
Note: Neither the IP addresses of the GSI and/or the EMS should be entered here because they will
be entered automatically, nor the IP address of the COMDAC although the OAM&P information of
the COMDAC may be routed via the AFM.

E. System Identification TU-630

Select to Set: AFM
New Value: (0-255 characters) ______________________________________

F. System Configuration TU-630

1
Protection Mode: Simplex ( )
Distribution Port Numbering Mode (circle Physical Logical
one):
AFM Configuration: xDSL
Customer Configuration: 1 2
Main Shelf Type: AnyMedia AS AnyMedia AS 800
High BER Algorithm: Fixed CRC Threshold Fixed BER Threshold

Notes:
1. You will set the Protection Mode to Duplex in a later step.

G. System Information TU-630

Contact (0-255 characters) _____________________________
Location (0-255 characters) _____________________________
Main Shelf Misc. Information (0-100 characters) _____________________________

H. Global ATM Parameters TU-630

VPI VCI F5 EtoE CC
(1 - 255) (32 - 64)
ATM Operations Channel: _____________ _____________ _____________
default: 254 default: 32 default: Disabled

Upstream Downstream
Shelf PCR (cps): _____________ _____________

I. Daisy-Chain upstream VP Information TU-630

J. Shelf VP Information TU-630

The default Shelf VP must be changed if 255 is already in use on another shelf in the daisy chain.
VPI VP Type Service Highest VCI F4 VP Segment
Category Allowed (circle one)
255 Shelf UBR 1999 - LPA901 Disabled Endpoint
1023 - LPA900
________ Shelf ________ ________ Disabled Endpoint
________ Shelf ________ ________ Disabled Endpoint
________ Shelf ________ ________ Disabled Endpoint
________ Shelf ________ ________ Disabled Endpoint

K. Shelf Level Traffic Thresholds TU-630

Note, that the TCA for a given parameter is inhibited by setting the threshold to ″0″.

15-min interval 24-hour interval

(0 to 318000 cells/frames) (0 to 30.6 x 106
cells/frames)
Cells dropped due to PPD _____________ _____________
Cells dropped due to EPD _____________ _____________
Cells dropped due to buffer overflow _____________ _____________
AAL5 Frames dropped due to EPD _____________ _____________

L. Daisy-Chain Information TU-640

GSI Connection (circle Local at Console Port Local at 10BaseT Port Remote LAN
one):
IP Address _______________________________
Security ID _______________________________

Downstream VP Information
VPI VP Type Service Category F4 VP Segment
(circle one)

Downstream ___ Disabled Endpoint

__________ Downstream _____________ Disabled Endpoint
__________ Downstream _____________ Disabled Endpoint
__________ Downstream _____________ Disabled Endpoint
__________ Downstream _____________ Disabled Endpoint
__________ Downstream _____________ Disabled Endpoint
Repeat above information for all shelves in the daisy-chain.

M. Feeder Port 2 Parameters TU-640

In a daisy-chain, you must enable and provision Port 2 of the existing shelf that feeds the new shelf.
Use the following parameters:
Administration State: Enabled Disabled
Timing Source (circle one): Free Running Line-time
Cell Scrambling (circle one): Enable Disable
Single Bit Error Correction (circle one): Enable Disable
Frame Format (circle one): HEC PLCP
Line Length (circle range): 0-224’ 225-450’

N. Install 2nd AFM TU-2605

If there is already a circuit pack in Slot 15, does it need to be replaced (circle Yes No
one)?

O. Provision Duplex AFM Mode TU-2610

Software Version Required ______________________

P. Feeder Port 1 Parameters TU-650

Timing Source (circle one): Free-running Line-time
Cell Scrambling (circle one): Enable Disable
Single Bit Error Correction (circle one): Enable Disable
Frame Format (circle one): HEC PLCP
Line Length (circle range): 0-224’ 225-450’

Part 3. Cabling/Connection Information - Duplex AFMDS3

A. AFMDS3 Cabling in Duplex Mode (Daisy Chain) TU-2620a; TU-2625a

The following information is needed only if a new shelf or AFM packs are to be installed.
Feeder Cabling Source (check one of the following)
_____ If not daisy-chained, ATM Feeder ID _______________________________
_____ If daisy-chained, the cable source is the last shelf listed above in Part 1, Preliminary
Information.

Are the AFMs to be connected to a LAN for remote operations Yes No

(circle one)?

A. AFMDS3 Cabling in Duplex Mode (Daisy Chain) TU-2620a; TU-2625a

If the AFMs are being connected to a LAN for remote operations,

what type of cable assembly is being used (circle one)?
Special Assembly Hub and 3 Straight Cables
If the AFM is to be connected to a LAN,
connect 10BaseT cable assembly to ________________________________

Part 4. Subshelf Information - Duplex AFMDS3

A. Subshelf TU-655, TU-656

ATM ADSL Service Activation Procedures Flowchart

ATM SDSL Service Activation Procedures Flowchart

ATM SHDSL Service Activation Procedures Flowchart

E1IMA Shelf Cascading Procedures Flowchart

Begin of Shelf Cascading Procedures

Slot not equipped Slot equipped

TU-698
LPA941 Upgrade to R1.25

TU-660
AP Installation/Growth

SA-301
SA-302 Wiring the E1 feeder Initiate E1IMA
connections for E1IMA AP Cascading

Provision/Retrieve E1 port
parameters (set further ports
in service and assign FRP)

IMA mode Required Change to UNI mode required

Provision/Retrieve
Add/Delete IMA Links
UNI Mode

Provision ATM
Virtual Connection

SA-321 Verify
Transmission Continuity

End of Shelf Cascading Procedures

Part 5. Service Activation Parameters - Duplex AFMDS3

Repeat for as many packs, ports, and cross-connects as required for the Mainshelf.

B. Pack Provisioning Information SA-300; SA-301; TU-660; TU-660a

ATM xDSL Slot AP-1 AP-2 AP-3 AP-4 AP-5 AP-6 AP-7 AP-8
in Mainshelf
(circle one):
AP-9 AP-10 AP-11 AP-12 AP-13 AP-14 AP-15( 1)
Pack Type (circle ADSL SDSL SHDSL
one):
If E1IMA AP, complete additionally the following:
IMA PM Configuration
Î PM Enable all E1 Ports (✓)
Interval (circle one) 15 Minutes 24 Hours

Notes:
1. Not applicable for an E1IMA AP

C. Cabling Information SA-300; SA-303; TU-660; TU-660a

NOTE: In a mixed narrowband and ATM xDSL configuration it is assumed that the NB subsystem
has already been installed and turned up before turning up the BB subsystem.

From NB AP Cable _ Pair __

NB Circuit Input to ADSL AP Cable _________ Pair __________
NB+ADSL Output of ADSL AP Cable _________ Pair __________
FDI/MDF Distribution Pair Cable _________ Pair __________

Case 1b: Adding ADSL only using an ADSL4p, ADSL8p, ADSL16p, ADSL4i AP, or ADSL16i (at
FDI/MDF)
ATM xDSL Slot ____________ ATM xDSL Port
________________

From ADSL AP Cable _ Pair __

FDI/MDF Distribution Pair Cable _________ Pair __________

Case 1c: Adding ADSL and POTS using a P32A32 AP (at the FDI/MDF)
ATM xDSL Slot ____________ ATM xDSL Port
________________

From combo AP Cable _ Pair __

FDI/MDF Distribution Pair Cable _________ Pair __________

From POTS/ISDN AP Cable _ Pair __

From ADSL AP Cable _________ Pair __________

FDI/MDF Distribution Pair Cable _ Pair __

Case 1e: Adding SDSL using a SDSL16 AP (at the FDI/MDF)

ATM xDSL Slot ____________ ATM xDSL Port ________________

From SDSL16 AP Cable _ Pair __

FDI/MDF Distribution Pair Cable _________ Pair __________

Case 1f: Adding SHDSL using an SHDSL16 AP (at the FDI/MDF)

ATM xDSL Slot ____________ ATM xDSL Port ______________

From SHDSL16 AP Cable _ Pair __

FDI/MDF Distribution Pair Cable _________ Pair __________

Case 3: Cabling the E1IMA AP to the DDF

E1IMA AP DDF
1 -------------------->

2 -------------------->

3 -------------------->

4 -------------------->
Tx
5 .

6 .

7 .

4
Rx
5

D. Transmission Parameters SA-300

Pack Type (circle one): ADSL SDSL SHDSL

Case 1a: ADSL Transmission Parameters

— Existing Profile ID ______________
Name: _______________________________
— New Profile ID ______________ Existing profile used to create new profile
Name: _______________________________
Name: _______________________________
ID ______________ New profile (Technician fills in the ID supplied by
the GSI)
Type of Rate Adaptation (circle one): Flexible Explicit
If you selected Flexible, complete Part A. If you selected Explicit, complete Part B. After completing
Part A or Part B, continue with Additional ADSL Transmission Parameters.

Part A.
Maximum Upstream Bit Rate ______________kbps (any multiple of 32 from 64 to 1440
kbps)
Maximum Downstream Bit ______________kbps (any multiple of 32 from 64 to 13120
Rate kbps)
Minimum Upstream Bit Rate ______________kbps (any multiple of 32 from 64 to 1440
kbps)
Minimum Downstream Bit ______________kbps (any multiple of 32 from 64 to 13120
Rate kbps)

Part B.
Downstream, Option 1 ________________ (Multiples of 32, from 64 to 8160 kbps)
Downstream, Option 2 ________________ (Multiples of 32, from 64 to 8160 kbps)
Downstream, Option 3 ________________ (Multiples of 32, from 64 to 8160 kbps)
Downstream, Option 4 ________________ (Multiples of 32, from 64 to 8160 kbps)
Upstream, Option 1 ________________ (Multiples of 32, from 64 to 1440 kbps)
Upstream, Option 2 ________________ (Multiples of 32, from 64 to 1440 kbps)
Upstream, Option 3 ________________ (Multiples of 32, from 64 to 1440 kbps)
Upstream, Option 4 ________________ (Multiples of 32, from 64 to 1440 kbps)

Additional ADSL Transmission Parameters

Upstream SNR margin in dB (integer from 0 to 15) _________________________

Downstream SNR margin in dB (integer from 0 to 15) _________________________

Upstream Interleave Depth (circle one) 1 2 4 8 16

PSDM in –dBm/Hz (integer from 40 to 60) _____________________________

Case 1b: ADSL2/ADSL2+ Transmission Parameters

Additional ADSL2/ADSL2+ Transmission Parameters

Type of Rate Adaptation: Flexible Flexible, Dynamic(1)

SNR Margin, dB US ________dB (0 to 15, in steps of 1)

DS ________dB (0 to 15, in steps of 1)

Upshift SNR Margin, dB US ________dB (0 to 31, in steps of 0.1)

DS ________dB (0 to 31, in steps of 0.1)

Upshift SNR Margin Time, sec US ________sec (0 to 16383, in steps of 1)

DS ________sec (0 to 16383, in steps of 1)

Downshift SNR Margin, dB US ________dB (0 to 31, in steps of 0.1)

DS ________dB (0 to 31, in steps of 0.1)

Downshift SNR Margin Time, sec US ________sec (0 to 16383, in steps of 1)

DS ________sec (0 to 16383, in steps of 1)

Min SNR Margin, dB US ________dB (0 to 31, in steps of 0.1)

DS ________dB (0 to 31, in steps of 0.1)

Max SNR Margin, dB US ________dB (0 to 31, in steps of 0.1)

DS ________dB (0 to 31, in steps of 0.1)

Max Aggregate Tx Power, dBm (3) US ________dBm (0 to 25.5, in steps of 0.1)

DS ________dBm (0 to 25.5, in steps of 0.1)

Max Tx PSD, dBm/Hz US ________dBm/Hz -60 to -38

DS ________dBm/Hz -60 to -40

Max Data Rate, kbps US ________kbps 64 to 2048, in steps of 32

DS ________kbps 64 to 30016, in steps of 32
Min Data Rate, kbps US ________kbps 64 to 2048, in steps of 32

DS ________kbps 64 to 24000, in steps of 32

Interleave, msec US ________msec 0 to 254, in steps of 1
DS ________msec 0 to 254, in steps of 1

Latency US ________ interleaved, fast

DS ________ interleaved, fast
Minimum INP (2) US auto auto, no-symbol, half-symbol,
one-symbol, two-symbols
DS auto

PSD Mask US ________ Default, Mask1 to Mask9 ( 4)

DS ________ Default

Enable/Disable READSL2 DS ________ Disabled, Enabled

2
Enable/Disable automatic Power Mgmt ( ) DS Disabled Disabled, Wide Band, Narrow Band
Min L0 time, sec (2) DS ________sec 0 to 255, in steps of 1
2
Min L2 time, sec ( ) DS ________sec 0 to 255, in steps of 1

Max Aggregate Tx Power Reduc.(2) DS ________dBm 0 to 31, in steps of 0.1

Notes:
1. The Type of rate adaptation Dynamic is supported only by LPA420 and LPA833.
2. Not supported by LPA420 and LPA833.
3. The only supported value by LPA420 and LPA833 is 10.0 dbm.
4. Mask1 to Mask9 in upstream direction are used when the line is operating in Annex M mode (requires a
compatible modem at the other end). Not supported by LPA438.

Case 2: SDSL Transmission Parameters

___Existing Profile ID __________
Name: _______________________________
___New Profile ID __________ Existing profile used to create new profile
Name: _______________________________
Name: _______________________________
ID __________ New profile (Technician fills in the ID supplied by the
GSI.)
Type of Rate Adaptation (circle one): Flexible Explicit
If you selected Flexible, complete Part A. If you selected Explicit, complete Part B. After completing
Part A or Part B, continue with Additional SDSL Transmission Parameters.

Part B.
Explicit Bit Rate ________________kbps (144, 272, 400, 528, 784, 1168, 1552, 2320)

Additional SDSL Transmission Parameters

TX/RX Scramble (circle one): Enable Disable
ATM Cell Scramble (circle one): Enable Disable
COSET (circle one): Enable Disable

Case 3: SHDSL Transmission Parameters

If you selected Flexible, complete Part A. If you selected Explicit, complete Part B. After completing
Part A or Part B, continue with Additional SHDSL Transmission Parameters.

Part A.
Maximum Bit Rate ________________kbps (Multiples of 64, from 192 to 2304 kbps)
Minimum Bit Rate ________________kbps (Multiples of 64, from 192 to 2304 kbps)

Part B.
Explicit Data Rate ________________kbps (Multiples of 64, from 192 to 2304 kbps)

E. Port Provisioning Information SA-300

ATM xDSL Slot AP-1 AP-2 AP-3 AP-4 AP-5 AP-6 AP-7 AP-8
(circle one):
AP-9 AP-10 AP-11 AP-12 AP-13 AP-14 AP-15( 1)
ATM xDSL Port (1 to 32): ___________

Notes:
1. Not applicable for E1IMA AP.

If ADSL, complete the Start Up Mode:

Start Up Mode (circle one): Multimode G994.1 (G.hs) T1.413 adsl2 adsl2+

xDSL Transmission Profile ID _________________________

(If a new profile was created in Part 5D, enter that ID.)
PM Profile: ___________________________
DMT Profile( 1): ___________________________
Failure Report Profile: ___________________________
Î Enable AIS (✓)

Notes:
1. Only for ADSL2/ADSL2+

If SHDSL, complete additionally the following:

Î Bonding (✓)
SNR Margin Threshold: _______________________ dB (integer from 0 to 15)

Loop Attenuation Threshold: _______________________ dB (integer from 0 to 127)

Annex Mode (circle one): Annex A Annex B

If E1IMA AP, complete additionally the following:

Loopback (circle one): No Loop Line Loop
Failure Report Profile: _______________________________

F. IMA Provisioning for E1IMA AP only TU-650a

IMA Mode (circle one): IMA UNI
If UNI, UNI Mode Link (circle one): 1 2 3 4 5 6 7 8
Î PM Enable (✓)
Î AIS Enable (✓)
Go to Part G.- E1 Feeder Provisioning Information TU-650a.

If IMA, fill out the remainder of Part G: IMA Group Configuration

Î Inhibit IMA Group (✓)
Provisioned Protocol (circle one): V1.0 V1.1
Symmetry Mode (check one): Î Symmetric Configuration & Operation
Î Symmetric Configuration & Asymmetric Operation

IMA Mode (circle one): IMA UNI

G. ATM Traffic Parameters SA-300

___ Existing Profile ID ___________________
Name ________________
___ New Profile ID ___________________
Name ________________ Existing profile used to create new
profile
Name ________________ New Profile
ID ___________________ New profile (Technician fills in the ID
supplied by the GSI.)
Service Category CBR rt-VBR nrt-VBR UBR
(circle one):
Profile Name: _______________________________ (0 - 64 characters)
The specific profile parameters needed will depend on the service category.

Case 2: rt-VBR, nrt-VBR

Peak Cell Rate Upstream _________________cells/sec (150 to 108,940)
Peak Cell Rate Downstream _________________cells/sec (150 to 108,940)
PCR CDVT _________________ms (0.000680 to 1330)

Sustainable Cell Rate Upstream _________________cells/sec (150 to 108,939)

Sustainable Cell Rate Downstream _________________cells/sec (150 to 108,939)
SCR CDVT _________________ms (0.000680 to 1330)

Cell Loss Priority (circle one): CLP (0) CLP (0 + 1)

Cell Tagging (circle one): True False
Frame Discard (circle one): True False

Case 3: UBR
Peak Cell Rate Upstream _________________cells/sec (150 to 108,940)

Peak Cell Rate Downstream _________________cells/sec (150 to 108,940)

PCR (CDVT) _________________ms (0.000680 to 1330)

Cell Tagging (circle one): True False

Frame Discard (circle one): True False

H. Cross-Connect Provisioning SA-300

If the Shelf VPI (see Part 3e above) is used for the Feeder VPI, then a feeder VCI must be specified
as well. Complete Part A; otherwise, complete Part B.

Part A. Virtual Channel Cross-Connect

Feeder VPI ________________________
Feeder VCI ________________________
F5 Segment (circle one): Disabled Endpoint

Part B. Virtual Path Cross-Connect

Feeder VPI ___________________________
F4 Segment (circle one): Disabled Endpoint
Slot Number (circle AP-1 AP-2 AP-3 AP-4 AP-5 AP-6 AP-7 AP-8
one):
AP-9 AP-10 AP-11 AP-12 AP-13 AP-14 AP-15
ATM xDSL Port (1 to 32): ________
Subscriber VPI ________________
ATM Traffic Profile Name ________________
Traffic Statistics Profile ________________
...................................................................................................................................................................................................................................
A-50 363-211-586
Issue 6, July 2007
ATM xDSL Engineering Work Orders for AFMDS3 Work Order for ATM xDSL Services — Duplex AFMDS3

Part B. Virtual Path Cross-Connect

Circuit ID ________________

SA-300; TU-640; OP-610

If this shelf is in a daisy-chain, you must update the VP list on the other shelves in the daisy-chain
with the feeder VP used in the new cross-connect. The following information is needed for each shelf
in the daisy-chain.
Location
Rack _______________________ Shelf _________________________
Street Address _________________________________________________________

GSI Connection (circle one): Console Port 10BaseT Port LAN

IP Address _______________________________
Security ID _______________________________

These templates can be modified as needed and adapted to suit individual applications.
They cover a range of cases, from the simple addition of a new ATM virtual
connection on an existing port to complete turn-up and service activation of a new
shelf. For multiple packs and subscribers, copy the forms as needed.
These forms provide information the technician needs when provisioning the system
using the Commands and Procedures turn-up and service activation documentation. The
documentation refers the technician to these forms as needed. Representative
procedural flowcharts from the documentation are included here for convenience.
Finally, depending on the level of technician training and experience, the engineer may
choose to include the following supplementary attachments:
• A list of tools, cables, and circuit packs needed
• Screen shots of at least the more complex GSI screens showing the parameter
values to be entered.
The ATM xDSL Engineering Work Orders for AFME3 are:
• “Work Order for ATM xDSL Services — Simplex AFME3” (p. B-3)
• “Work Order for ATM xDSL Services — Duplex AFME3” (p. B-28).

Work Order for ATM xDSL Services — Simplex AFME3

Part 1. Preliminary Information - Simplex AFME3

Type of System: AnyMedia Access System

Location of Last Shelf in Daisy-Chain

Rack ___________________ Shelf __________________________
Street Address __________________________________________________

ATM xDSL Simplex AFME3 Turn-up Procedures Flowchart (Part 1)

Begin of Turn-Up Procedures with simplex AFME3/DS3

TU-605
AFM Installation

TU-610 Verify/Update
AFM Software Load

Shelf connected Shelf connected

directly to ATM Transport Network to a previous shelf (Daisy-Chain)

TU-620a TU-625a
(Single Shelf) (Daisy-Chain)
AFME3/DS3 Cabling AFME3/DS3 Cabling

TU-630 TU-630
(AFME3/DS3 Installed)
Provision Main Shelf Provision Main Shelf

TU-640 Update
Daisy-Chain VPIs

TU-650 Provision
AFME3/DS3 Feeder Port

ATM xDSL Simplex AFME3 Turn-up Procedures Flowchart (Part 2)

1
Broadband-only or
a mixed system
xDSL APs required in Mainshelf

TU-660 xDSL AP
no xDSL APs
Installation / Growth
required in Mainshelf

ONU Subshelves
with xDSL APs required

TU-655 OAP
no ONU Subshelves Installation Growth
with xDSL APs required

TU-656
Provision Subshelf

TU-660a xDSL APs

Installation / Growth (ONU)

TU-670a Verify Proper

AFME3/DS3 SystemTurn-Up

End of Turn-Up Procedures with simplex AFME3/DS3

*) To activate the ATM xDSL subscriber services,

follow the next chapter “Activate Service and Test”.

Part 2. Installation/Cabling/Connection/ Software Information - Simplex AFME3

A. AFM Installation TU-605

If there is already a circuit pack in Slot 16, does it need to be replaced (circle one)? Yes No

B. GSI Connection OP-610

The following information is needed to connect the GSI to the shelf.
GSI Connection (circle one):
Console Port 10BaseT Port LAN
Select Link
PC Port (circle one): COM1 COM2 COM3 COM4 LAN
Log In
Security ID( 1) ________________________________
IP Address: ________ - ________ - ________ - ________ 192.168.160.160

Notes:
1. The initial default setting is ″public″.

Important! If only performing Service Activation, skip to Part 4, Service Activation

Parameters.

C. Verify AFM Software TU-610

Software Version Required ______________________

D. Cabling TU-620a
The following information is needed only if a new shelf or AFM pack is to be installed.
Feeder Cabling Source (check one of the following)
_____ If not daisy-chained, ATM Feeder ID _______________________________
_____ If daisy-chained, the cable source is last shelf listed above in Part 1, Preliminary Information.

Is the AFM to be connected to a LAN for remote operations (circle one)? Yes No
If the AFM is to be connected to a LAN, connect 10BaseT cable assembly to _________________

Part 3. Turn-up Parameters - Simplex AFME3

E. Communications TU-630
Security ID: _______________________

IP Configuration
IP Interfaces IP Address Subnet Mask
10BaseT: ____________ _____________
ATM: ____________ _____________
Console: ____________ Default: 192.168.0.1 _____________
Default Router (circle one):
10BaseT ____________
ATM

Autonomous Messages Destination

Selected Address: ______________________
Addresses stored in ______________________
memory: ______________________
______________________
______________________
______________________
Note: Neither the IP addresses of the GSI and/or the EMS should be entered here because they will
be entered automatically, nor the IP address of the COMDAC although the OAM&P information of
the COMDAC may be routed via the AFM.

F. Site ID TU-630
Select to Set: AFM
New AFM_SID: (0-255 characters) ______________________________________

G. System Configuration TU-630

H. System Information TU-630

Contact (0-255 characters) _____________________________

Location (0-255 characters) _____________________________

Main Shelf Misc. Information (0-100 characters) _____________________________

I. System Identification TU-630

System Identification (0-20 characters) ___________________________________

J. Global ATM Parameters TU-630

VPI VCI F5 EtoE CC
(1 - 255) (32 - 64)
ATM Operations Channel: _____________ _____________ _____________
default: 254 default: 32 default: Disabled

Upstream Downstream
Shelf PCR (cps): _____________ _____________

K. Daisy-Chain upstream VP Information TU-630

L. Shelf VP Information TU-630

The default Shelf VP must be changed if 255 is already in use on another shelf in the daisy chain.
VPI VP Type Service Highest VCI Allowed F4 VP Segment
Category (circle one)
255 Shelf UBR 1999 - LPA901 Disabled Endpoint
1023 - LPA900
________ Shelf ________ ________ Disabled Endpoint
________ Shelf ________ ________ Disabled Endpoint
________ Shelf ________ ________ Disabled Endpoint
________ Shelf ________ ________ Disabled Endpoint

M. Shelf Level Traffic Thresholds TU-630

Note, that the TCA for a given parameter is inhibited by setting the threshold to ″0″.
15-min interval (0 to 24-hour interval (0 to 30.6 x
318000 cells/frames) 106 cells/frames)
Cells dropped due to PPD _____________ _____________
Cells dropped due to EPD _____________ _____________
Cells dropped due to buffer overflow _____________ _____________
AAL5 Frames dropped due to EPD _____________ _____________

N. Daisy-Chain Information TU-640

GSI Connection (circle Local at Console Port Local at 10BaseT Port Remote LAN
one):
IP Address _______________________________
Security ID _______________________________

Downstream VP Information

VPI VP Type Service Category F4 VP Segment

(circle one)

Downstream ___ Disabled Endpoint

__________ Downstream _____________ Disabled Endpoint
__________ Downstream _____________ Disabled Endpoint
__________ Downstream _____________ Disabled Endpoint
__________ Downstream _____________ Disabled Endpoint
__________ Downstream _____________ Disabled Endpoint
Repeat above information for all shelves in the daisy-chain.

O. Feeder Port 2 Parameters TU-640

In a daisy-chain, you must enable and provision Port 2 of the existing shelf that feeds the new shelf.
Use the following parameters:
Set the Configured State (or Status) of Port 2 to Enabled.
Cell Scrambling (circle one): Enable Disable
Single Bit Error Correction (circle one): Enable Disable
Expected API AMAS TTI
Transmitted API AMAS TTI
Trailtrace Alarm Enable True

P. Feeder Port 1 Parameters TU-650

Timing Source (circle one): Free-running Line-timed
Cell Scrambling (circle one): Enable Disable
Single Bit Error Correction (circle one): Enable Disable
Expected API AMAS TTI
Transmitted API AMAS TTI
Trailtrace Alarm Enable True

Q. Subshelf TU-655, TU-656

OAP slot
ONU
Shelf number (1-7) ____________________________________
Subsite ID (0-255 chars) ____________________________________
Physical ID ____________________________________

Contact (0-255 chars) ____________________________________

Location (0-255 chars) ____________________________________
Parent slot (OAP slot; 2-14) ____________________________________

ATM ADSL Service Activation Procedures Flowchart

ATM SDSL Service Activation Procedures Flowchart

ATM SHDSL Service Activation Procedures Flowchart

E1IMA Shelf Cascading Procedures Flowchart

Begin of Shelf Cascading Procedures

Slot not equipped Slot equipped

TU-698
LPA941 Upgrade to R1.25

TU-660
AP Installation/Growth

SA-301
SA-302 Wiring the E1 feeder Initiate E1IMA
connections for E1IMA AP Cascading

Provision/Retrieve E1 port
parameters (set further ports
in service and assign FRP)

IMA mode Required Change to UNI mode required

Provision/Retrieve
Add/Delete IMA Links
UNI Mode

Provision ATM
Virtual Connection

SA-321 Verify
Transmission Continuity

End of Shelf Cascading Procedures

Part 4. Service Activation Parameters - Simplex AFME3

Repeat for as many packs, ports, and cross-connects as required for the Mainshelf.

B. Pack Provisioning Information SA-300; SA-301 TU-660; TU-660a

Notes:
1. Not applicable for an E1IMA AP

C. Cabling Information SA-300; TU-660; TU-660a

NOTE: In a mixed narrowband and ATM xDSL configuration it is assumed that the NB subsystem
has already been installed and turned up before turning up the BB subsystem.

From NB AP Cable _ Pair __

NB Circuit Input to ADSL AP Cable _________ Pair __________
NB+ADSL Output of ADSL AP Cable _________ Pair __________
FDI/MDF Distribution Pair Cable _________ Pair __________

Case 1b: Adding ADSL only using an ADSL4p, ADSL8p, ADSL16p, ADSL4i AP, or ADSL16i (at
FDI/MDF)
ATM xDSL Slot ____________ ATM xDSL Port ________________

From ADSL AP Cable _ Pair __

FDI/MDF Distribution Pair Cable _________ Pair __________

Case 1c: Adding ADSL and POTS using a P32A32 AP (at the FDI/MDF)
ATM xDSL Slot ____________ ATM xDSL Port ________________

From combo AP Cable _ Pair __

FDI/MDF Distribution Pair Cable _________ Pair __________

From POTS/ISDN AP Cable _ Pair __

From ADSL AP Cable _________ Pair __________

FDI/MDF Distribution Pair Cable _ Pair __

Case 1e: Adding SDSL using a SDSL16 AP (at the FDI/MDF)

ATM xDSL Slot ____________ ATM xDSL Port ________________

From SDSL16 AP Cable _ Pair __

FDI/MDF Distribution Pair Cable _________ Pair __________

Case 1f: Adding SHDSL using an SHDSL16 AP (at the FDI/MDF)

ATM xDSL Slot ____________ ATM xDSL Port ______________

From SHDSL16 AP Cable _ Pair __

FDI/MDF Distribution Pair Cable _________ Pair __________

Case 3: Cabling the E1IMA AP to the DDF

E1IMA AP DDF
1 -------------------->

2 -------------------->

3 -------------------->

4 -------------------->
Tx
5 .

6 .

7 .

4
Rx
5

D. Transmission Parameters SA-300

Pack Type (circle one): ADSL SDSL SHDSL

Case 1a: ADSL Transmission Parameters

— Existing Profile ID ______________
Name: _______________________________
— New Profile ID ______________ Existing profile used to create new profile
Name: _______________________________
Name: _______________________________
ID ______________ New profile (Technician fills in the ID supplied by
the GSI)
Type of Rate Adaptation (circle one): Flexible Explicit
If you selected Flexible, complete Part A. If you selected Explicit, complete Part B.
After completing Part A or Part B, continue with Additional ADSL Transmission Parameters.

Part A.
Maximum Upstream Bit Rate ______________kbps (any multiple of 32 from 64 to 1440 kbps)
Maximum Downstream Bit ______________kbps (any multiple of 32 from 64 to 13120
Rate kbps)
Minimum Upstream Bit Rate ______________kbps (any multiple of 32 from 64 to 1440 kbps)
Minimum Downstream Bit ______________kbps (any multiple of 32 from 64 to 13120
Rate kbps)

Part B.
Downstream, Option 1 ________________ (Multiples of 32, from 64 to 8160
kbps)
Downstream, Option 2 ________________ (Multiples of 32, from 64 to 8160
kbps)
Downstream, Option 3 ________________ (Multiples of 32, from 64 to 8160
kbps)
Downstream, Option 4 ________________ (Multiples of 32, from 64 to 8160
kbps)
Upstream, Option 1 ________________ (Multiples of 32, from 64 to 1440
kbps)
Upstream, Option 2 ________________ (Multiples of 32, from 64 to 1440
kbps)
Upstream, Option 3 ________________ (Multiples of 32, from 64 to 1440
kbps)

Upstream, Option 4 ________________ (Multiples of 32, from 64 to 1440

kbps)

Additional ADSL Transmission Parameters

Upstream SNR margin in dB (integer from 0 to 15) _________________________
Downstream SNR margin in dB (integer from 0 to 15) _________________________

Upstream Interleave Depth (circle one) 1 2 4 8 16

PSDM in –dBm/Hz (integer from 40 to 60) _____________________________

Case 1b: ADSL2/ADSL2+ Transmission Parameters

Additional ADSL2/ADSL2+ Transmission Parameters

Type of Rate Adaptation: Flexible Flexible, Dynamic(1)

SNR Margin, dB US ________dB (0 to 15, in steps of 1)

DS ________dB (0 to 15, in steps of 1)

Upshift SNR Margin, dB US ________dB (0 to 31, in steps of 0.1)

DS ________dB (0 to 31, in steps of 0.1)

Upshift SNR Margin Time, sec US ________sec (0 to 16383, in steps of 1)

DS ________sec (0 to 16383, in steps of 1)

Downshift SNR Margin, dB US ________dB (0 to 31, in steps of 0.1)

DS ________dB (0 to 31, in steps of 0.1)

Downshift SNR Margin Time, sec US ________sec (0 to 16383, in steps of 1)

DS ________sec (0 to 16383, in steps of 1)

Min SNR Margin, dB US ________dB (0 to 31, in steps of 0.1)

DS ________dB (0 to 31, in steps of 0.1)

Max SNR Margin, dB US ________dB (0 to 31, in steps of 0.1)

DS ________dB (0 to 31, in steps of 0.1)

3
Max Aggregate Tx Power, dBm ( ) US ________dBm (0 to 25.5, in steps of 0.1)
DS ________dBm (0 to 25.5, in steps of 0.1)

Max Tx PSD, dBm/Hz US ________dBm/Hz -60 to -38

DS ________dBm/Hz -60 to -40

Max Data Rate, kbps US ________kbps 64 to 2048, in steps of 32

DS ________kbps 64 to 30016, in steps of 32
Min Data Rate, kbps US ________kbps 64 to 2048, in steps of 32

DS ________kbps 64 to 24000, in steps of 32

Interleave, msec US ________msec 0 to 254, in steps of 1
DS ________msec 0 to 254, in steps of 1

Latency US ________ interleaved, fast

DS ________ interleaved, fast
2
Minimum INP ( ) US auto auto, no-symbol, half-symbol,
one-symbol, two-symbols
DS auto

PSD Mask US ________ Default, Mask1 to Mask9 ( 4)

DS ________ Default

Enable/Disable READSL2 DS ________ Disabled, Enabled

Enable/Disable automatic Power Mgmt (2) DS Disabled Disabled, Wide Band, Narrow Band
2
Min L0 time, sec ( ) DS ________sec 0 to 255, in steps of 1

Min L2 time, sec (2) DS ________sec 0 to 255, in steps of 1

2
Max Aggregate Tx Power Reduc. ( ) DS ________dBm 0 to 31, in steps of 0.1

Notes:
1. The Type of rate adaptation Dynamic is supported only by LPA420 and LPA833.
2. Not supported by LPA420 and LPA833.
...................................................................................................................................................................................................................................
363-211-586 B-21
Issue 6, July 2007
ATM xDSL Engineering Work Orders for AFME3 Work Order for ATM xDSL Services — Simplex AFME3

3. The only supported value by LPA420 and LPA833 is 10.0 dbm.

4. Mask1 to Mask9 in upstream direction are used when the line is operating in Annex M mode (requires a
compatible modem at the other end). Not supported by LPA438.

Case 2: SDSL Transmission Parameters

___Existing Profile ID ______________
Name: _______________________________
___New Profile ID ______________ Existing profile used to create new profile
Name: _______________________________
Name: _______________________________
ID ______________ New profile (Technician fills in the ID supplied by
the GSI)
Type of Rate Adaptation (circle one): Flexible Explicit
If you selected Flexible, complete Part A. If you selected Explicit, complete Part B. After completing
Part A or Part B, continue with Additional SDSL Transmission Parameters.

Part A.
Maximum Bit Rate ________________kbps (144, 272, 400, 528, 784, 1168, 1552, 2320)
Minimum Bit Rate ________________kbps (144, 272, 400, 528, 784, 1168, 1552, 2320)

Part B.
Explicit Bit Rate ________________kbps (144, 272, 400, 528, 784, 1168, 1552, 2320)

Additional SDSL Transmission Parameters

TX/RX Scramble (circle one): Enable Disable
ATM Cell Scramble (circle one): Enable Disable
COSET (circle one): Enable Disable

Case 3: SHDSL Transmission Parameters

___Existing Profile ID ______________
Name: _______________________________
___New Profile ID ______________ Existing profile used to create new profile
Name: _______________________________
Name: _______________________________
ID ______________ New profile (Technician fills in the ID
supplied by the GSI.)
...................................................................................................................................................................................................................................
B-22 363-211-586
Issue 6, July 2007
ATM xDSL Engineering Work Orders for AFME3 Work Order for ATM xDSL Services — Simplex AFME3

Case 3: SHDSL Transmission Parameters

Type of Rate Adaptation (circle one): Flexible Explicit
If you selected Flexible, complete Part A. If you selected Explicit, complete Part B. After completing
Part A or Part B, continue with Additional SHDSL Transmission Parameters.

Part A.
Maximum Bit Rate ________________kbps (Multiples of 64, from 192 to 2304 kbps)
Minimum Bit Rate ________________kbps (Multiples of 64, from 192 to 2304 kbps)

Part B.
Explicit Data Rate ________________kbps (Multiples of 64, from 192 to 2304
kbps)

E. Port Provisioning Information SA-300

ATM xDSL Slot AP-1 AP-2 AP-3 AP-4 AP-5 AP-6 AP-7 AP-8
(circle one):
AP-9 AP-10 AP-11 AP-12 AP-13 AP-14 AP-15( 1)
ATM xDSL Port (1 to 32): ___________

Notes:
1. Not applicable for E1IMA AP.

If ADSL, complete the Start Up Mode:

Start Up Mode (circle one): Multimode G994.1 (G.hs) T1.413 adsl2 adsl2+

xDSL Transmission Profile ID _________________________

Notes:
1. Only for ADSL2/ADSL2+

If SHDSL, complete additionally the following:

If E1IMA AP, complete additionally the following:

Loopback (circle one): No Loop Line Loop
Failure Report Profile: _______________________________

F. IMA Provisioning for E1IMA AP only TU-650a

IMA Mode (circle one): IMA UNI
If UNI, UNI Mode Link (circle one): 1 2 3 4 5 6 7 8
Î PM Enable (✓)
Î AIS Enable (✓)
Go to Part G.- E1 Feeder Provisioning Information TU-650a

If IMA, fill out the remainder of Part G:

IMA Group Configuration
Î Inhibit IMA Group (✓)
Provisioned Protocol (circle one): V1.0 V1.1
Symmetry Mode (check one): Î Symmetric Configuration & Operation
Î Symmetric Configuration & Asymmetric Operation

IMA Mode (circle one): IMA UNI

Sufficient Tx Link (circle one): 1 2 3 4 5 6 7 8
Sufficient Rx Link (circle one): 1 2 3 4 5 6 7 8
Tx Frame Length (circle one): 32 64 128 256
Tx Amas IMA ID Î 0 (0 to 256)
Tx Clocking Mode (check one): Î Common
Î Independent
Maximum Differential Delay (5 to 45 msec, 10 ms increments): 25 msec _____________
Failure Report Profile
Synchronization Parameters
Alpha (circle one): 1 2
Beta (circle one): 1 2 3 4 5

Gamma (circle one): 1 2 3 4 5

IMA Links (circle selections): 1 2 3 4 5 6 7 8

G. ATM Traffic Parameters SA-300

___ Existing Profile ID ___________________
Name ________________
___ New Profile ID ___________________
Name ________________ Existing profile used to create new
profile
Name ________________ New Profile
ID ___________________ New profile (Technician fills in the ID
supplied by the GSI.)
Service Category (circle one): CBR rt-VBR nrt-VBR UBR
Profile Name: _______________________________ (0 - 64 characters)
The specific profile parameters needed will depend on the service category.

Case 2: rt-VBR, nrt-VBR

Peak Cell Rate Upstream _________________cells/sec (150 to 108,940)
Peak Cell Rate Downstream _________________cells/sec (150 to 108,940)
PCR CDVT _________________ms (0.000680 to 1330)

Sustainable Cell Rate Upstream _________________cells/sec (150 to 108,939)

Sustainable Cell Rate Downstream _________________cells/sec (150 to 108,939)
SCR CDVT _________________ms (0.000680 to 1330)

Maximum Burst Size Upstream _________________cells (1 to 100)

Maximum Burst Size Downstream _________________cells (1 to 210)

Cell Loss Priority (circle one): CLP (0) CLP (0 + 1)

Cell Tagging (circle one): True False

Frame Discard (circle one): True False

Case 3: UBR
Peak Cell Rate Upstream _________________cells/sec (150 to 108,940)
Peak Cell Rate Downstream _________________cells/sec (150 to 108,940)
PCR (CDVT) _________________ms (0.000680 to 1330)

Cell Tagging (circle one): True False

Frame Discard (circle one): True False

H. Cross-Connect Provisioning SA-300

If the Shelf VPI (see Part 4c above) is used for the Feeder VPI, then a feeder VCI must be specified
as well. Complete Part A; otherwise, complete Part B.

Part A. Virtual Channel Cross-Connect

Feeder VPI ________________________
Feeder VCI ________________________
F4 Segment (circle one): Disabled Endpoint
F4 Segment CC (circle one): Disabled Endpoint

Slot Number in AP-1 AP-2 AP-3 AP-4 AP-5 AP-6 AP-7 AP-8
Mainshelf (circle
one):
AP-9 AP-10 AP-11 AP-12 AP-13 AP-14 AP-15
ATM xDSL Port (1 to 32): ________
Subscriber VPI ________________
Subscriber VCI ________________
ATM Traffic Profile ________________
Thrshold Profile ________________
Circuit ID ________________

Part B. Virtual Path Cross-Connect

Feeder VPI ___________________________
F4 Segment (circle one): Disabled Endpoint

Part B. Virtual Path Cross-Connect

Slot Number (circle AP-1 AP-2 AP-3 AP-4 AP-5 AP-6 AP-7 AP-8
one):
AP-9 AP-10 AP-11 AP-12 AP-13 AP-14 AP-15
ATM xDSL Port (1 to 32): ________
Subscriber VPI ________________
ATM Traffic Profile Name ________________
Traffic Statistics Profile ________________
Circuit ID ________________

GSI Connection (circle one): Console Port 10BaseT Port LAN

IP Address _______________________________
Security ID _______________________________

Work Order for ATM xDSL Services — Duplex AFME3

Part 1. Preliminary Information - Duplex AFME3

Type of System: AnyMedia Access System

Location of Last Shelf in Daisy-Chain

Rack ___________________ Shelf __________________________
Street Address __________________________________________________

ATM xDSL Duplex AFME3 Turn-up Procedures Flowchart (Part 1)

Begin of Turn-Up Procedures with simplex AFME3/DS3

TU-605
AFM Installation

TU-610 Verify/Update
AFM Software Load

Shelf connected Shelf connected

directly to ATM Transport Network to a previous shelf (Daisy-Chain)

TU-620a TU-625a
(Single Shelf) (Daisy-Chain)
AFME3/DS3 Cabling AFME3/DS3 Cabling

TU-630 TU-630
(AFME3/DS3 Installed)
Provision Main Shelf Provision Main Shelf

TU-640 Update
Daisy-Chain VPIs

TU-650 Provision
AFME3/DS3 Feeder Port

ATM xDSL Duplex AFME3 Turn-up Procedures Flowchart (Part 2)

1
Broadband-only or
a mixed system

xDSL APs required in Mainshelf

TU-660 xDSL AP
no xDSL APs
Installation / Growth
required in Mainshelf

ONU Subshelves
with xDSL APs required

TU-655 OAP
no ONU Subshelves Installation Growth
with xDSL APs required

TU-656
Provision Subshelf

TU-660a xDSL APs

Installation / Growth (ONU)

TU-670a Verify Proper

AFME3/DS3 SystemTurn-Up

End of Turn-Up Procedures with duplex AFME3/DS3

*) To activate the ATM xDSL subscriber services,

follow the next chapter “Activate Service and Test”.

Part 2. Installation/Software Information/Turn-up Parameters - Duplex AFME3

A. Install First AFM TU-605

If there is already a circuit pack in Slot 16, does it need to be replaced (circle one)? Yes No

B. GSI Connection OP-610

The following information is needed to connect the GSI to the shelf.
GSI Connection (circle one):
Console Port 10BaseT Port LAN
Select Link
PC Port (circle one): COM1 COM2 COM3 COM4 LAN
Log In
Security ID( 1) ________________________________
IP Address: ________ - ________ - ________ - ________ 192.168.160.160

Notes:
1. The initial default setting is ″public″.

Important! If only performing Service Activation, skip to Part 4, Service

Activation Parameters.

C. Verify AFM Software TU-610

Software Version Required ______________________

Selected Address: ______________________

Addresses stored in ______________________

memory: ______________________
______________________
______________________
______________________
Note: Neither the IP addresses of the GSI and/or the EMS should be entered here because they will
be entered automatically, nor the IP address of the COMDAC although the OAM&P information of
the COMDAC may be routed via the AFM.

E. Site ID TU-630
Select to Set: AFM
New AFM_SID (0-255 characters) ___________________________________

F. System Configuration TU-630

Notes:
1. You will set the Protection Mode to Duplex in a later step.

G. System Information TU-630

Contact (0-255 characters) _____________________________
Location (0-255 characters) _____________________________
Main Shelf Misc. Information (0-100 characters) _____________________________

H. System Identification TU-630

System Identification (0-20 characters) ________________________________

I. Global ATM Parameters TU-630

VPI VCI F5 EtoE CC
(1 - 255) (32 - 64)

ATM Operations Channel: _______ _ _______

default: 254 default: 32 default: Disabled

Upstream Downstream
Shelf PCR (cps): _____________ _____________

J. Daisy-Chain upstream VP Information TU-630

K. Shelf VP Information TU-630

Shelf Disabled Endpoint

L. Shelf Level Traffic Thresholds TU-630

Note, that the TCA for a given parameter is inhibited by setting the threshold to ″0″.
15-min interval (0 to 318000 24-hour interval (0 to 30.6 x
cells/frames) 106 cells/frames)
Cells dropped due to PPD _____________ _____________
Cells dropped due to EPD _____________ _____________
Cells dropped due to buffer overflow _____________ _____________
AAL5 Frames dropped due to EPD _____________ _____________

M. Daisy-Chain Information TU-640

GSI Connection (circle Local at Console Port Local at 10BaseT Port Remote LAN
one):
IP Address _______________________________
Security ID _______________________________

Downstream VP Information
VPI VP Type Service Category F4 VP Segment
(circle one)

Downstream ___ Disabled Endpoint

__________ Downstream _____________ Disabled Endpoint
__________ Downstream _____________ Disabled Endpoint
__________ Downstream _____________ Disabled Endpoint
__________ Downstream _____________ Disabled Endpoint
__________ Downstream _____________ Disabled Endpoint
Repeat above information for all shelves in the daisy-chain.

N. Feeder Port 2 Parameters TU-640

In a daisy-chain, you must enable and provision Port 2 of the existing shelf that feeds the new shelf.
Use the following parameters:
Set the Configured State (or Status) of Port 2 Enabled Disabled
Cell Scrambling (circle one): Enabled Disabled
Single Bit Error Correction (circle one): Enable Disable
Expected API AMAS TTI
Transmitted API AMAS TTI
Trailtrace Alarm Enable True

O. Install 2nd AFM TU-2605

If there is already a circuit pack in Slot 15, does it need to be replaced (circle Yes No
one)?

P. Provision Duplex AFM Mode TU-2610

Software Version Required ______________________

Q. Feeder Port 1 Parameters TU-650

Timing Source (circle one): Free-running Line-time
Cell Scrambling (circle one): Enable Disable
Single Bit Error Correction (circle one): Enable Disable
Expected API AMAS TTI
Transmitted API AMAS TTI
Trailtrace Alarm Enable True

Part 3. Cabling/Connection Information - Duplex AFME3

A. AFME3 Cabling in Duplex Mode (Daisy Chain) TU-2620a; TU-2625a

Are the AFMs to be connected to a LAN for remote operations Yes No
(circle one)?

If the AFMs are being connected to a LAN for remote operations,

what type of cable assembly is being used (circle one)?
Special Assembly Hub and 3 Straight Cables

If the AFM is to be connected to

a LAN, connect 10BaseT cable assembly to ________________________

Part 4. Subshelf Information - Duplex AFME3

A. Subshelf TU-655, TU-656

ATM ADSL Service Activation Procedures Flowchart

ATM SDSL Service Activation Procedures Flowchart

ATM SHDSL Service Activation Procedures Flowchart

E1IMA Shelf Cascading Procedures Flowchart

Begin of Shelf Cascading Procedures

Slot not equipped Slot equipped

TU-698
LPA941 Upgrade to R1.25

TU-660
AP Installation/Growth

SA-301
SA-302 Wiring the E1 feeder Initiate E1IMA
connections for E1IMA AP Cascading

Provision/Retrieve E1 port
parameters (set further ports
in service and assign FRP)

IMA mode Required Change to UNI mode required

Provision/Retrieve
Add/Delete IMA Links
UNI Mode

Provision ATM
Virtual Connection

SA-321 Verify
Transmission Continuity

End of Shelf Cascading Procedures

Part 5. Service Activation Parameters - Duplex AFME3

Repeat for as many packs, ports, and cross-connects as required for the Mainshelf.

B. Pack Provisioning Information SA-300; SA-301; TU-660; TU-660a

ATM xDSL Slot in AP-1 AP-2 AP-3 AP-4 AP-5 AP-6 AP-7 AP-8
Mainshelf (circle
one):
AP-9 AP-10 AP-11 AP-12 AP-13 AP-14 AP-15( 1
)
Pack Type (circle ADSL SDSL SHDSL
one):
If E1IMA AP, complete additionally the following:
IMA PM Configuration
Î PM Enable all E1 Ports (✓)
Interval (circle one) 15 Minutes 24 Hours

Notes:
1. Not applicable for an E1IMA AP

C. Cabling Information SA-300; SA-303; TU-660; TU-660a

NOTE: In a mixed narrowband and ATM xDSL configuration it is assumed that the NB subsystem
has already been installed and turned up before turning up the BB subsystem.

From NB AP Cable _ Pair __

NB Circuit Input to ADSL AP Cable _________ Pair __________
NB+ADSL Output of ADSL AP Cable _________ Pair __________
FDI/MDF Distribution Pair Cable _________ Pair __________
...................................................................................................................................................................................................................................
363-211-586 B-41
Issue 6, July 2007
ATM xDSL Engineering Work Orders for AFME3 Work Order for ATM xDSL Services — Duplex AFME3

Case 1b: Adding ADSL only using an ADSL4p, ADSL8p, ADSL16p, ADSL4i AP, or ADSL16i (at
FDI/MDF)
ATM xDSL Slot ____________ ATM xDSL Port _________________

From ADSL AP Cable _ Pair __

FDI/MDF Distribution Pair Cable _________ Pair __________

Case 1c: Adding ADSL and POTS using a P32A32 AP (at the FDI/MDF)
ATM xDSL Slot ____________ ATM xDSL Port ________________

From combo AP Cable _ Pair __

FDI/MDF Distribution Pair Cable _________ Pair __________

From POTS/ISDN AP Cable _ Pair __

From ADSL AP Cable _________ Pair __________

FDI/MDF Distribution Pair Cable _ Pair __

Case 1e: Adding SDSL using a SDSL16 AP (at the FDI/MDF)

ATM xDSL Slot ____________ ATM xDSL Port ________________

From SDSL16 AP Cable _ Pair __

FDI/MDF Distribution Pair Cable _________ Pair __________

Case 1f: Adding SHDSL using an SHDSL16 AP (at the FDI/MDF)

ATM xDSL Slot ____________ ATM xDSL Port ______________

From SHDSL16 AP Cable _ Pair __

FDI/MDF Distribution Pair Cable _________ Pair __________

Case 3: Cabling the E1IMA AP to the DDF

E1IMA AP DDF
1 -------------------->

2 -------------------->

3 -------------------->

4 -------------------->
Tx
5 .

6 .

7 .

4
Rx
5

D. Transmission Parameters SA-300

Pack Type (circle one): ADSL SDSL SHDSL

Case 1a: ADSL Transmission Parameters

Part A.
Maximum Upstream Bit Rate ______________kbps (any multiple of 32 from 64 to 1440 kbps)
Maximum Downstream Bit ______________kbps (any multiple of 32 from 64 to 13120
Rate kbps)
Minimum Upstream Bit Rate ______________kbps (any multiple of 32 from 64 to 1440 kbps)
Minimum Downstream Bit ______________kbps (any multiple of 32 from 64 to 13120
Rate kbps)

Part B.
Downstream, Option 1 ________________ (Multiples of 32, from 64 to 8160
kbps)
Downstream, Option 2 ________________ (Multiples of 32, from 64 to 8160
kbps)
Downstream, Option 3 ________________ (Multiples of 32, from 64 to 8160
kbps)
Downstream, Option 4 ________________ (Multiples of 32, from 64 to 8160
kbps)
Upstream, Option 1 ________________ (Multiples of 32, from 64 to 1440
kbps)
Upstream, Option 2 ________________ (Multiples of 32, from 64 to 1440
kbps)
Upstream, Option 3 ________________ (Multiples of 32, from 64 to 1440
kbps)

Upstream, Option 4 ________________ (Multiples of 32, from 64 to 1440

kbps)

Additional ADSL Transmission Parameters

Upstream SNR margin in dB (integer from 0 to 15) _________________________
Downstream SNR margin in dB (integer from 0 to 15) _________________________

Upstream Interleave Depth (circle one) 1 2 4 8 16

PSDM in –dBm/Hz (integer from 40 to 60) _____________________________

Case 1b: ADSL2/ADSL2+ Transmission Parameters

Additional ADSL2/ADSL2+ Transmission Parameters

Type of Rate Adaptation: Flexible Flexible, Dynamic(1)

SNR Margin, dB US ________dB (0 to 15, in steps of 1)

DS ________dB (0 to 15, in steps of 1)

Upshift SNR Margin, dB US ________dB (0 to 31, in steps of 0.1)

DS ________dB (0 to 31, in steps of 0.1)

Upshift SNR Margin Time, sec US ________sec (0 to 16383, in steps of 1)

DS ________sec (0 to 16383, in steps of 1)

Downshift SNR Margin, dB US ________dB (0 to 31, in steps of 0.1)

DS ________dB (0 to 31, in steps of 0.1)

Downshift SNR Margin Time, sec US ________sec (0 to 16383, in steps of 1)

DS ________sec (0 to 16383, in steps of 1)

Min SNR Margin, dB US ________dB (0 to 31, in steps of 0.1)

DS ________dB (0 to 31, in steps of 0.1)

Max SNR Margin, dB US ________dB (0 to 31, in steps of 0.1)

DS ________dB (0 to 31, in steps of 0.1)

3
Max Aggregate Tx Power, dBm ( ) US ________dBm (0 to 25.5, in steps of 0.1)
DS ________dBm (0 to 25.5, in steps of 0.1)

Max Tx PSD, dBm/Hz US ________dBm/Hz -60 to -38

DS ________dBm/Hz -60 to -40

Max Data Rate, kbps US ________kbps 64 to 2048, in steps of 32

DS ________kbps 64 to 30016, in steps of 32
Min Data Rate, kbps US ________kbps 64 to 2048, in steps of 32

DS ________kbps 64 to 24000, in steps of 32

Interleave, msec US ________msec 0 to 254, in steps of 1
DS ________msec 0 to 254, in steps of 1

Latency US ________ interleaved, fast

DS ________ interleaved, fast
2
Minimum INP ( ) US auto auto, no-symbol, half-symbol,
one-symbol, two-symbols
DS auto

PSD Mask US ________ Default, Mask1 to Mask9 ( 4)

DS ________ Default

Enable/Disable READSL2 DS ________ Disabled, Enabled

Enable/Disable automatic Power Mgmt (2) DS Disabled Disabled, Wide Band, Narrow Band
2
Min L0 time, sec ( ) DS ________sec 0 to 255, in steps of 1

Min L2 time, sec (2) DS ________sec 0 to 255, in steps of 1

2
Max Aggregate Tx Power Reduc. ( ) DS ________dBm 0 to 31, in steps of 0.1

Notes:
1. The Type of rate adaptation Dynamic is supported only by LPA420 and LPA833.
2. Not supported by LPA420 and LPA833.
...................................................................................................................................................................................................................................
B-46 363-211-586
Issue 6, July 2007
ATM xDSL Engineering Work Orders for AFME3 Work Order for ATM xDSL Services — Duplex AFME3

3. The only supported value by LPA420 and LPA833 is 10.0 dbm.

4. Mask1 to Mask9 in upstream direction are used when the line is operating in Annex M mode (requires a
compatible modem at the other end). Not supported by LPA438.

Case 2: SDSL Transmission Parameters

___Existing Profile ID ______________
Name: _______________________________
___New Profile ID ______________ Existing profile used to create new profile
Name: _______________________________
Name: _______________________________
ID ______________ New profile (Technician fills in the ID supplied by
the GSI.)
Type of Rate Adaptation (circle one): Flexible Explicit
If you selected Flexible, complete Part A. If you selected Explicit, complete Part B. After completing
Part A or Part B, continue with Additional SDSL Transmission Parameters.

Part A.
Maximum Bit Rate ________________kbps (144, 272, 400, 528, 784, 1168, 1552, 2320)
Minimum Bit Rate ________________kbps (144, 272, 400, 528, 784, 1168, 1552, 2320)

Part B.
Explicit Bit Rate ________________kbps (144, 272, 400, 528, 784, 1168, 1552, 2320)

Additional SDSL Transmission Parameters

TX/RX Scramble (circle one): Enable Disable
ATM Cell Scramble (circle one): Enable Disable
COSET (circle one): Enable Disable

Case 3: SHDSL Transmission Parameters

___Existing Profile ID ______________
Name: _______________________________
___New Profile ID ______________ Existing profile used to create new profile
Name: _______________________________
Name: _______________________________
ID ______________ New profile (Technician fills in the ID supplied
by the GSI.)
...................................................................................................................................................................................................................................
363-211-586 B-47
Issue 6, July 2007
ATM xDSL Engineering Work Orders for AFME3 Work Order for ATM xDSL Services — Duplex AFME3

Case 3: SHDSL Transmission Parameters

Part A.
Maximum Bit Rate ________________kbps (Multiples of 64, from 192 to 2304 kbps)
Minimum Bit Rate ________________kbps (Multiples of 64, from 192 to 2304 kbps)

Part B.
Explicit Data Rate ________________kbps (Multiples of 64, from 192 to 2304
kbps)

E. Port Provisioning Information SA-300

ATM xDSL Slot AP-1 AP-2 AP-3 AP-4 AP-5 AP-6 AP-7 AP-8
(circle one):
AP-9 AP-10 AP-11 AP-12 AP-13 AP-14 AP-15( 1)
ATM xDSL Port (1 to 32): ___________

Notes:
1. Not applicable for E1IMA AP.

If ADSL, complete the Start Up Mode:

Start Up Mode (circle one): Multimode G994.1 (G.hs) T1.413 adsl2 adsl2+

xDSL Transmission Profile ID _________________________

Notes:
1. Only for ADSL2/ADSL2+

If SHDSL, complete additionally the following:

If E1IMA AP, complete additionally the following:

Loopback (circle one): No Loop Line Loop
Failure Report Profile: _______________________________

F. IMA Provisioning for E1IMA AP only TU-650a

IMA Mode (circle one): IMA UNI
If UNI, UNI Mode Link (circle one): 1 2 3 4 5 6 7 8
Î PM Enable (✓)
Î AIS Enable (✓)
Go to Part G.- E1 Feeder Provisioning Information TU-650a

If IMA, fill out the remainder of Part G:

Sufficient Tx Link (circle one): 1 2 3 4 5 6 7 8

Sufficient Rx Link (circle one): 1 2 3 4 5 6 7 8
Tx Frame Length (circle one): 32 64 128 256
Tx Amas IMA ID Î 0 (0 to 256)
Tx Clocking Mode (check one): Î Common
Î Independent
Maximum Differential Delay (5 to 45 msec, 10ms increments): 25 msec _____________
Failure Report Profile
Synchronization Parameters
Alpha (circle one): 1 2
Beta (circle one): 1 2 3 4 5
Gamma (circle one): 1 2 3 4 5

IMA Links (circle selections): 1 2 3 4 5 6 7 8

G. ATM Traffic Parameters SA-300

Case 2: rt-VBR, nrt-VBR

Peak Cell Rate Upstream _________________cells/sec (150 to 108,940)
Peak Cell Rate Downstream _________________cells/sec (150 to 108,940)
PCR CDVT _________________ms (0.000680 to 1330)

Sustainable Cell Rate Upstream _________________cells/sec (150 to 108,939)

Sustainable Cell Rate Downstream _________________cells/sec (150 to 108,939)
SCR CDVT _________________ms (0.000680 to 1330)

Maximum Burst Size Upstream _________________cells (1 to 100)

Maximum Burst Size Downstream _________________cells (1 to 210)

Maximum Burst Size Upstream _________________cells (1 to 100)

Maximum Burst Size Downstream _________________cells (1 to 210)

Case 3: UBR
Peak Cell Rate Upstream _________________cells/sec (150 to 108,940)
Peak Cell Rate Downstream _________________cells/sec (150 to 108,940)
PCR (CDVT) _________________ms (0.000680 to 1330)

Cell Tagging (circle one): True False

Frame Discard (circle one): True False

H. Cross-Connect Provisioning SA-300

If the Shelf VPI (see Part 3e above) is used for the Feeder VPI, then a feeder VCI must be specified
as well. Complete Part A; otherwise, complete Part B.

Part A. Virtual Channel Cross-Connect

Feeder VPI ________________________
Feeder VCI ________________________
F5 Segment (circle one): Disabled Endpoint

Part B. Virtual Path Cross-Connect

Feeder VPI ___________________________
Slot Number (circle AP-1 AP-2 AP-3 AP-4 AP-5 AP-6 AP-7 AP-8
one):
AP-9 AP-10 AP-11 AP-12 AP-13 AP-14 AP-15

Part B. Virtual Path Cross-Connect

ATM xDSL Port (1 to 32): ________
Subscriber VPI ________________
ATM Traffic Profile ________________
Traffic Statistics Profile ________________
Circuit ID ________________

SA-300; TU-640; OP-610

GSI Connection (circle one): Console Port 10BaseT Port LAN

IP Address _______________________________
Security ID _______________________________

These templates can be modified as needed and adapted to suit individual applications.
They cover a range of cases, from the simple addition of a new ATM virtual
connection on an existing port to complete turn-up and service activation of a new
shelf. For multiple packs and subscribers, copy the forms as needed.
These forms provide information the technician needs when provisioning the system
using the Commands and Procedures turn-up and service activation documentation. The
documentation refers the technician to these forms as needed. Representative
procedural flowcharts from the documentation are included here for convenience.
Finally, depending on the level of technician training and experience, the engineer may
choose to include the following supplementary attachments:
• A list of tools, cables, and circuit packs needed
• Screen shots of at least the more complex GSI screens showing the parameter
values to be entered.
The ATM xDSL Engineering Work Orders for AFMO are:
• “Work Order for ATM xDSL Services — Simplex AFMO” (p. C-3)
• “Work Order for ATM xDSL Services — Duplex AFMO” (p. C-28).

Work Order for ATM xDSL Services — Simplex AFMO

Part 1. Preliminary Information - Simplex AFMO

Type of System: AnyMedia Access System

Location of Last Shelf in Daisy-Chain

Rack ___________________ Shelf __________________________
Street Address __________________________________________________

ATM xDSL Simplex AFMO Turn-up Procedures Flowchart (Part 1)

Begin of Turn-Up Procedures with simplex AFMO

TU-605
AFM Installation

TU-610 Verify/Update
AFM Software Load

Shelf connected directly Shelf connected

to ATM Transport Network to a preceeding shelf (Daisy-Chain)

TU-620c TU-625c
(Single Shelf) (Daisy-Chain)
AFMO Cabling AFMO Cabling

TU-630 TU-630
(AFMO Installed)
Provision Main Shelf Provision Main Shelf

TU-640 Update
Daisy-Chain VPIs

TU-650b Provision
AFMO Feeder Port

ATM xDSL Simplex AFMO Turn-up Procedures Flowchart (Part 2)

1
Broadband-only or
a mixed system

xDSL APs required in Mainshelf

TU-660 xDSL AP
no xDSL APs
Installation / Growth
required in Mainshelf

ONU Subshelves
with xDSL APs required

TU-655 OAP
no ONU Subshelves Installation Growth
with xDSL APs required

TU-656
Provision Subshelf

TU-660a xDSL APs

Installation / Growth (ONU)

TU-670c Verify Proper

AFMO SystemTurn-Up

End of Turn-Up Procedures with simplex AFMO

*) To activate the ATM xDSL subscriber services,

follow the next chapter “Activate Service and Test”.

Part 2. Installation/Cabling/Connection/ Software Information - Simplex AFMO

A. AFM Installation TU-605

If there is already a circuit pack in Slot 16, does it need to be replaced (circle one)? Yes No

B. GSI Connection OP-610

Notes:
1. The initial default setting is ″public″.

C. Verify AFM Software TU-610

Software Version Required ______________________

D. AFMO - Not Daisy-Chained: Cabling / Optical Attenuation TU-620c

The following information is needed only if a new shelf or AFMO pack is to be installed.
Feeder Cabling Source (check one
of the following)
ATM Feeder ID _______________________________
The following information is needed to calculate the optical attenuation.
Power Network OLIU AFMO
Receive Max _____________ __________
Receive Min _____________ __________

Is the AFMO to be connected to a LAN for remote operations (circle one)? Yes No
If the AFMO is to be connected to a LAN, connect 10BaseT cable assembly to _______________

E. AFMO - Daisy-Chained: Cabling TU-625c

The cable source is the last shelf listed in Part 1, Preliminary Information.

E. AFMO - Daisy-Chained: Cabling TU-625c

Is the AFMO to be connected to a LAN for remote operations (circle one)? Yes No
If the AFMO is to be connected to a LAN, connect the 10BaseT cable assembly to ____________

Part 3. Turn-up Parameters - Simplex AFMO

F. Communications TU-630
Security ID: _______________________
IP Configuration
IP Interfaces IP Address Subnet Mask
10BaseT: ____________ _____________
ATM: ____________ _____________
Console: ____________ Default: 192.168.0.1 _____________
Default Router (circle one):
10BaseT ____________
ATM

Autonomous Messages Destination

G. System Identification TU-630

Select to Set: AFM
New Value: (0-255 characters) ______________________________________

H. System Configuration TU-630

Transmission Mode (circle one) Sonet SDH
Protection Mode: Simplex
Timing Source (circle one) Line-Timed Free Running
...................................................................................................................................................................................................................................
363-211-586 C-7
Issue 6, July 2007
ATM xDSL Engineering Work orders for AFMO Work Order for ATM xDSL Services — Simplex AFMO

H. System Configuration TU-630

Distribution Port Numbering Mode (circle Physical Logical
one):
AFM Configuration: xDSL
Customer Configuration: 1 2
Main Shelf Type: AnyMedia AS AnyMedia AS 800
High BER Algorithm: Fixed CRC Threshold Fixed BER Threshold

I. System Information TU-630

Contact (0-255 characters) _____________________________
Location (0-255 characters) _____________________________
Main Shelf Misc. Information (0-100 characters) _____________________________

J. Global ATM Parameters TU-630

VPI VCI F5 EtoE CC
(1 - 255) (32 - 64)
ATM Operations Channel: _____________ _____________ _____________
default: 254 default: 32 default: Disabled

Upstream Downstream
Shelf PCR (cps): _____________ _____________

K. Daisy-Chain upstream VP Information TU-630

(Note: These VPs are all those in use on upstream shelves of the daisy-chain and their VP type on
the new shelf is upstream.)

K. Daisy-Chain upstream VP Information TU-630

VPI VP Type Service Category
_______________ upstream _______________
_______________ upstream _______________
_______________ upstream _______________
_______________ upstream _______________
_______________ upstream _______________

L. Shelf VP Information TU-630

The default Shelf VP must be changed if 255 is already in use on another shelf in the daisy chain.
VPI VP Type Service Highest VCI Allowed F4 VP Segment
Category (circle one)
255 Shelf UBR 1999 - LPA920 Disabled Endpoint
________ Shelf ________ ________ Disabled Endpoint
________ Shelf ________ ________ Disabled Endpoint
________ Shelf ________ ________ Disabled Endpoint
________ Shelf ________ ________ Disabled Endpoint

M. Shelf Level Traffic Thresholds TU-630

N. Daisy-Chain Information TU-640

GSI Connection (circle one): Console Port 10BaseT Port Remote LAN
IP Address _______________________________
Security ID _______________________________

Downstream VP Information
VPI VP Type Service Category F4 VP Segment
(circle one)

Downstream ___ Disabled Endpoint

__________ Downstream _____________ Disabled Endpoint
__________ Downstream _____________ Disabled Endpoint
__________ Downstream _____________ Disabled Endpoint
__________ Downstream _____________ Disabled Endpoint
__________ Downstream _____________ Disabled Endpoint
Repeat above information for all shelves in the daisy-chain.

In a daisy-chain, you must enable and provision Port 2 of the existing shelf
that feeds the new shelf. Use the following parameters:
Configured State (or Status) of Port 2: Enable Disable
Transmission Mode (circle one): SONET SDH SDH - Japan
Section Trace Monitoring (circle one): Disabled Enabled
Expected Section Trace (15 characters): _________________________
Transmitted Section Trace (15 characters): _________________________
Path RDI Code (circle one): One bit RDI-P code Enhanced RDI-P
code

O. Feeder Port 2 Parameters TU-640

Logical Feeder
Administrative State: In Service
Path RDI Code (circle one): One-bit Path RDI Code Enhanced Path RDI Code
Physical Feeder
Section Trace
- Trace Mode (circle one): Unspecified API
- Transmitted API (circle one): AnyMedia_Access 15-character text string

- Expected API (circle one): AnyMedia_Access 15-character text string

- API Monitor (circle one): Disabled Enabled

P. Feeder Port 1 Parameters TU-650b

Logical Feeder: Free-running Line-timed
Path RDI Code (circle one) One-bit Path RDI Code Enhanced Path RDI Code
Physical Feeder: Enable Disable
Loopback No Loop
Section Trace
- Trace Mode: Unspecified API
- Transmitted API: AnyMedia_Access 15-character text string
- Expected API: AnyMedia_Access 15-character text string
- API Monitor: Disabled Enabled
BER Threshold
- Line Signal Degrade Threshold (circle 10-5 10-6 10-7 10-8 10-9 Disabled
one):
- Line Signal Fail Threshold (circle one): 10-3 10-4 10-5 -- -- Disabled

Q. Subshelf TU-655, TU-656

OAP slot
ONU
Shelf number (1-7) ____________________________________
Subsite ID (0-255 chars) ____________________________________
Physical ID ____________________________________
Contact (0-255 chars) ____________________________________
Location (0-255 chars) ____________________________________
Parent slot (OAP slot; 2-14) ____________________________________

ATM ADSL Service Activation Procedures Flowchart

ATM SDSL Service Activation Procedures Flowchart

ATM SHDSL Service Activation Procedures Flowchart

E1IMA Shelf Cascading Procedures Flowchart

Begin of Shelf Cascading Procedures

Slot not equipped Slot equipped

TU-698
LPA941 Upgrade to R1.25

TU-660
AP Installation/Growth

SA-301
SA-302 Wiring the E1 feeder Initiate E1IMA
connections for E1IMA AP Cascading

Provision/Retrieve E1 port
parameters (set further ports
in service and assign FRP)

IMA mode Required Change to UNI mode required

Provision/Retrieve
Add/Delete IMA Links
UNI Mode

Provision ATM
Virtual Connection

SA-321 Verify
Transmission Continuity

End of Shelf Cascading Procedures

Part 4. Service Activation Parameters - Simplex AFMO

Repeat for as many packs, ports, and cross-connects as required for the Mainshelf.

B. Pack Provisioning Information SA-300; SA-301 TU-660; TU-660a

ATM xDSL Slot in AP-1 AP-2 AP-3 AP-4 AP-5 AP-6 AP-7 AP-8
Mainshelf (circle
one):
AP-9 AP-10 AP-11 AP-12 AP-13 AP-14 AP-15( 1)
Pack Type (circle ADSL SDSL SHDSL E1IMA
one):
If E1IMA AP, complete additionally the following:
Î PM Enable all E1 Ports (✓)
Interval (circle one): 15 Minutes 24 Hours

Notes:
1. Not applicable for an E1IMA AP

C. Cabling Information SA-300; TU-660; TU-660a

NOTE: In a mixed narrowband and ATM xDSL configuration it is assumed that the NB subsystem
has already been installed and turned up before turning up the BB subsystem.

From NB AP Cable _ Pair __

NB Circuit Input to ADSL AP Cable _________ Pair __________
NB+ADSL Output of ADSL AP Cable _________ Pair __________
FDI/MDF Distribution Pair Cable _________ Pair __________

Case 1b: Adding ADSL only using an ADSL4p, ADSL8p, ADSL16p, ADSL4i AP, or ADSL16i (at
FDI/MDF)
ATM xDSL Slot ____________ ATM xDSL Port ________________

From ADSL AP Cable _ Pair __

FDI/MDF Distribution Pair Cable _________ Pair __________

Case 1c: Adding ADSL and POTS using a P32A32 AP (at the FDI/MDF)
ATM xDSL Slot ____________ ATM xDSL Port ________________

From combo AP Cable _ Pair __

FDI/MDF Distribution Pair Cable _________ Pair __________

From POTS/ISDN AP Cable _ Pair __

From ADSL AP Cable _________ Pair __________

FDI/MDF Distribution Pair Cable _ Pair __

Case 1e: Adding SDSL using a SDSL16 AP (at the FDI/MDF)

ATM xDSL Slot ____________ ATM xDSL Port ________________

From SDSL16 AP Cable _ Pair __

FDI/MDF Distribution Pair Cable _________ Pair __________

Case 1f: Adding SHDSL using an SHDSL16 AP (at the FDI/MDF)

ATM xDSL Slot ____________ ATM xDSL Port ______________

From SHDSL16 AP Cable _ Pair __

FDI/MDF Distribution Pair Cable _________ Pair __________

Case 3: Cabling the E1IMA AP to the DDF

E1IMA AP DDF
1 -------------------->

2 -------------------->

3 -------------------->

4 -------------------->
Tx
5 .

6 .

7 .

4
Rx
5

D. Transmission Parameters SA-300

Pack Type (circle one): ADSL SDSL SHDSL

Case 1a: ADSL Transmission Parameters

— Existing Profile ID ______________
Name: _______________________________
— New Profile ID ______________ Existing profile used to create new profile
Name: _______________________________
Name: _______________________________
ID ______________ New profile (Technician fills in the ID supplied by
the GSI)
Type of Rate Adaptation (circle one): Flexible Explicit
If you selected Flexible, complete Part A. If you selected Explicit, complete Part B.
After completing Part A or Part B, continue with Additional ADSL Transmission Parameters.

Part A.
Maximum Upstream Bit Rate ______________kbps (any multiple of 32 from 64 to 1440 kbps)
Maximum Downstream Bit ______________kbps (any multiple of 32 from 64 to 13120
Rate kbps)
Minimum Upstream Bit Rate ______________kbps (any multiple of 32 from 64 to 1440 kbps)
Minimum Downstream Bit ______________kbps (any multiple of 32 from 64 to 13120
Rate kbps)

Part B.
Downstream, Option 1 ________________ (Multiples of 32, from 64 to 8160
kbps)
Downstream, Option 2 ________________ (Multiples of 32, from 64 to 8160
kbps)
Downstream, Option 3 ________________ (Multiples of 32, from 64 to 8160
kbps)
Downstream, Option 4 ________________ (Multiples of 32, from 64 to 8160
kbps)
Upstream, Option 1 ________________ (Multiples of 32, from 64 to 1440
kbps)
Upstream, Option 2 ________________ (Multiples of 32, from 64 to 1440
kbps)
Upstream, Option 3 ________________ (Multiples of 32, from 64 to 1440
kbps)

Upstream, Option 4 ________________ (Multiples of 32, from 64 to 1440

kbps)

Additional ADSL Transmission Parameters

Upstream SNR margin in dB (integer from 0 to 15) _________________________
Downstream SNR margin in dB (integer from 0 to 15) _________________________

Upstream Interleave Depth (circle one) 1 2 4 8 16

PSDM in –dBm/Hz (integer from 40 to 60) _____________________________

Case 1b: ADSL2/ADSL2+ Transmission Parameters

Additional ADSL2/ADSL2+ Transmission Parameters

Type of Rate Adaptation: Flexible Flexible, Dynamic(1)

SNR Margin, dB US ________dB (0 to 15, in steps of 1)

DS ________dB (0 to 15, in steps of 1)

Upshift SNR Margin, dB US ________dB (0 to 31, in steps of 0.1)

DS ________dB (0 to 31, in steps of 0.1)

Upshift SNR Margin Time, sec US ________sec (0 to 16383, in steps of 1)

DS ________sec (0 to 16383, in steps of 1)

Downshift SNR Margin, dB US ________dB (0 to 31, in steps of 0.1)

DS ________dB (0 to 31, in steps of 0.1)

Downshift SNR Margin Time, sec US ________sec (0 to 16383, in steps of 1)

DS ________sec (0 to 16383, in steps of 1)

Min SNR Margin, dB US ________dB (0 to 31, in steps of 0.1)

DS ________dB (0 to 31, in steps of 0.1)

Max SNR Margin, dB US ________dB (0 to 31, in steps of 0.1)

DS ________dB (0 to 31, in steps of 0.1)

3
Max Aggregate Tx Power, dBm ( ) US ________dBm (0 to 25.5, in steps of 0.1)
DS ________dBm (0 to 25.5, in steps of 0.1)

Max Tx PSD, dBm/Hz US ________dBm/Hz -60 to -38

DS ________dBm/Hz -60 to -40

Max Data Rate, kbps US ________kbps 64 to 2048, in steps of 32

DS ________kbps 64 to 30016, in steps of 32
Min Data Rate, kbps US ________kbps 64 to 2048, in steps of 32

DS ________kbps 64 to 24000, in steps of 32

Interleave, msec US ________msec 0 to 254, in steps of 1
DS ________msec 0 to 254, in steps of 1

Latency US ________ interleaved, fast

DS ________ interleaved, fast
2
Minimum INP ( ) US auto auto, no-symbol, half-symbol,
one-symbol, two-symbols
DS auto

PSD Mask US ________ Default, Mask1 to Mask9 ( 4)

DS ________ Default

Enable/Disable READSL2 DS ________ Disabled, Enabled

Enable/Disable automatic Power Mgmt (2) DS Disabled Disabled, Wide Band, Narrow Band
2
Min L0 time, sec ( ) DS ________sec 0 to 255, in steps of 1

Min L2 time, sec (2) DS ________sec 0 to 255, in steps of 1

2
Max Aggregate Tx Power Reduc. ( ) DS ________dBm 0 to 31, in steps of 0.1

Notes:
1. The Type of rate adaptation Dynamic is supported only by LPA420 and LPA833.
2. Not supported by LPA420 and LPA833.
...................................................................................................................................................................................................................................
363-211-586 C-21
Issue 6, July 2007
ATM xDSL Engineering Work orders for AFMO Work Order for ATM xDSL Services — Simplex AFMO

3. The only supported value by LPA420 and LPA833 is 10.0 dbm.

4. Mask1 to Mask9 in upstream direction are used when the line is operating in Annex M mode (requires a
compatible modem at the other end). Not supported by LPA438.

Case 2: SDSL Transmission Parameters

___Existing Profile ID ______________
Name: _______________________________
___New Profile ID ______________ Existing profile used to create new profile
Name: _______________________________
Name: _______________________________
ID ______________ New profile (Technician fills in the ID supplied by
the GSI)
Type of Rate Adaptation (circle one): Flexible Explicit
If you selected Flexible, complete Part A. If you selected Explicit, complete Part B. After completing
Part A or Part B, continue with Additional SDSL Transmission Parameters.

Part A.
Maximum Bit Rate ________________kbps (144, 272, 400, 528, 784, 1168, 1552, 2320)
Minimum Bit Rate ________________kbps (144, 272, 400, 528, 784, 1168, 1552, 2320)

Part B.
Explicit Bit Rate ________________kbps (144, 272, 400, 528, 784, 1168, 1552, 2320)

Additional SDSL Transmission Parameters

TX/RX Scramble (circle one): Enable Disable
ATM Cell Scramble (circle one): Enable Disable
COSET (circle one): Enable Disable

Case 3: SHDSL Transmission Parameters

___Existing Profile ID ______________
Name: _______________________________
___New Profile ID ______________ Existing profile used to create new profile
Name: _______________________________
Name: _______________________________
ID ______________ New profile (Technician fills in the ID
supplied by the GSI.)
...................................................................................................................................................................................................................................
C-22 363-211-586
Issue 6, July 2007
ATM xDSL Engineering Work orders for AFMO Work Order for ATM xDSL Services — Simplex AFMO

Case 3: SHDSL Transmission Parameters

Part A.
Maximum Bit Rate ________________kbps (Multiples of 64, from 192 to 2304 kbps)
Minimum Bit Rate ________________kbps (Multiples of 64, from 192 to 2304 kbps)

Part B.
Explicit Data Rate ________________kbps (Multiples of 64, from 192 to 2304
kbps)

E. Port Provisioning Information SA-300

ATM xDSL Slot AP-1 AP-2 AP-3 AP-4 AP-5 AP-6 AP-7 AP-8
(circle one):
AP-9 AP-10 AP-11 AP-12 AP-13 AP-14 AP-15( 1)
ATM xDSL Port (1 to 32): ___________

Notes:
1. Not applicable for E1IMA AP.

If ADSL, complete the Start Up Mode:

Start Up Mode (circle one): Multimode G994.1 (G.hs) T1.413 adsl2 adsl2+

xDSL Transmission Profile ID _________________________

Notes:
1. Only for ADSL2/ADSL2+

If SHDSL, complete additionally the following:

If E1IMA AP, complete additionally the following:

Loopback (circle one): No Loop Line Loop
Failure Report Profile: _______________________________

F. IMA Provisioning for E1IMA AP only TU-650a

IMA Mode (circle one): IMA UNI
If UNI, UNI Mode Link (circle one): 1 2 3 4 5 6 7 8
Î PM Enable (✓)
Î AIS Enable (✓)
Go to Part G.- E1 Feeder Provisioning Information TU-650a

If IMA, fill out the remainder of Part G:

IMA Mode (circle one): IMA UNI

Sufficient Tx Link (circle one): 1 2 3 4 5 6 7 8
Sufficient Rx Link (circle one): 1 2 3 4 5 6 7 8
Tx Frame Length (circle one): 32 64 128 256
Tx Amas IMA ID Î 0 (0 to 256)
Tx Clocking Mode (check one): Î Common
Î Independent
Maximum Differential Delay (5 to 45 msec, 10 ms increments): 25 msec _____________
Failure Report Profile
Synchronization Parameters
Alpha (circle one): 1 2
Beta (circle one): 1 2 3 4 5

Gamma (circle one): 1 2 3 4 5

IMA Links (circle selections): 1 2 3 4 5 6 7 8

G. ATM Traffic Parameters SA-300

___ Existing Profile ID ___________________
Name ________________
___ New Profile ID ___________________
Name ______________ Existing profile used to create new profile
Name ______________ New Profile
ID ________________ New profile (Technician fills in the ID
supplied by the GSI.)
Service Category (circle one): CBR rt-VBR nrt-VBR UBR
Profile Name: _______________________________ (0 - 64 characters)
The specific profile parameters needed will depend on the service category.

Case 2: rt-VBR, nrt-VBR

Peak Cell Rate Upstream _________________cells/sec (150 to 108,940)
Peak Cell Rate Downstream _________________cells/sec (150 to 108,940)
PCR CDVT _________________ms (0.000680 to 1330)

Sustainable Cell Rate Upstream _________________cells/sec (150 to 108,939)

Sustainable Cell Rate Downstream _________________cells/sec (150 to 108,939)
SCR CDVT _________________ms (0.000680 to 1330)

Maximum Burst Size Upstream _________________cells (1 to 100)

Maximum Burst Size Downstream _________________cells (1 to 210)

Cell Loss Priority (circle one): CLP (0) CLP (0 + 1)

Cell Tagging (circle one): True False
...................................................................................................................................................................................................................................
363-211-586 C-25
Issue 6, July 2007
ATM xDSL Engineering Work orders for AFMO Work Order for ATM xDSL Services — Simplex AFMO

Frame Discard (circle one): True False

Case 3: UBR
Peak Cell Rate Upstream _________________cells/sec (150 to 108,940)
Peak Cell Rate Downstream _________________cells/sec (150 to 108,940)
PCR (CDVT) _________________ms (0.000680 to 1330)

Cell Tagging (circle one): True False

Frame Discard (circle one): True False

H. Cross-Connect Provisioning SA-300

If the Shelf VPI (see Part 4c above) is used for the Feeder VPI, then a feeder VCI must be specified
as well. Complete Part A; otherwise, complete Part B.

Part A. Virtual Channel Cross-Connect

Feeder VPI ________________________
Feeder VCI ________________________
F4 Segment (circle one): Disabled Endpoint
F4 Segment CC (circle one): Disabled Endpoint

Subscriber
Slot Number in AP-1 AP-2 AP-3 AP-4 AP-5 AP-6 AP-7 AP-8
Mainshelf (circle
one):
AP-9 AP-10 AP-11 AP-12 AP-13 AP-14 AP-15
ATM xDSL Port (1 to 32): ________
Subscriber VPI ________________
Subscriber VCI ________________
ATM Traffic Profile ________________
Thrshold Profile ________________
Circuit ID ________________

Part B. Virtual Path Cross-Connect

Feeder VPI ___________________________
F4 Segment (circle one): Disabled Endpoint

Part B. Virtual Path Cross-Connect

Work Order for ATM xDSL Services — Duplex AFMO

Part 1. Preliminary Information - Duplex AFMO

Type of System: AnyMedia Access System

Location of Last Shelf in Daisy-Chain

Rack ___________________ Shelf __________________________
Street Address __________________________________________________

ATM xDSL Duplex AFMO Turn-up Procedures Flowchart (Part 1)

Begin of Turn-Up Procedures with duplex AFMO

TU-605
AFM Installation

TU-610 Verify/Update
AFM Software Load

TU-630
(AFMOs Installed)
Provision Main Shelf

Shelf connected directly Shelf connected

to ATM Transport Network to a previous shelf (Daisy-Chain)

TU-640 Update
Daisy-Chain VPIs

TU-2605 Installation
of Second AFM

TU-2610 Provision Main

Shelf for Duplex Mode

TU-650b Provision
AFMO Feeder Port

Shelf connected directly Shelf connected

to ATM Transport Network to a previous shelf (Daisy-Chain)

Duplex 1+1 DBSF Duplex 1+1 DBSF

Protection Protection Protection Protection

(Duplex 1+1 (DBSF (Duplex 1+1 (DBSF

Single Shelf) Single Shelf) Daisy-chain) Daisy-Chain)
TU-2620c Duplex TU-2620d Duplex TU-2625c Duplex TU-2625d Duplex
AFMO Cabling AFMO Cabling AFMO Cabling AFMO Cabling

ATM xDSL Duplex AFMO Turn-up Procedures Flowchart (Part 2)

Broadband-only or
a mixed system

xDSL APs required in Mainshelf

TU-660 xDSL AP
no xDSL APs
Installation / Growth
required in Mainshelf

ONU Subshelves
with xDSL APs required

TU-655 OAP
no ONU Subshelves Installation Growth
with xDSL APs required

TU-656
Provision Subshelf

TU-660a xDSL APs

Installation / Growth (ONU)

TU-670c Verify Proper

AFMO SystemTurn-Up

End of Turn-Up Procedures with duplex AFMO

*) To activate the ATM xDSL subscriber services,

follow the next chapter “Activate Service and Test”.

Part 2. Installation/Software Information/Turn-up Parameters - Duplex AFMO

Install First AFM TU-605

A. AFM Installation TU-605

If there is already a circuit pack in Slot 16, does it need to be replaced (circle one)? Yes No

B. GSI Connection OP-610

The following information is needed to connect the GSI to the shelf.
GSI Connection (circle one):
Console Port 10BaseT Port LAN
Select Link
PC Port (circle one): COM1 COM2 COM3 COM4 LAN
Log In
Security ID( 1) ________________________________
IP Address: ________ - ________ - ________ - ________ 192.168.160.160
NOTE: If only performing Service Activation, skip to Part 4, Service Activation Parameters.

Notes:
1. The initial default setting is ″public″.

C. Verify AFM Software TU-2610

Software Version Required ______________________

Selected Address: ______________________

Addresses stored in ______________________
memory: ______________________

______________________
______________________
______________________
Note: Neither the IP addresses of the GSI and/or the EMS should be entered here because they will
be entered automatically, nor the IP address of the COMDAC although the OAM&P information of
the COMDAC may be routed via the AFM.

E. System Identification TU-630

Select to Set: AFM
New Value: (0-255 characters) ___________________________________

F. System Configuration TU-630

Transmission Mode (circle one): Sonet SDH
1
Protection Mode: Simplex ( )
Timing Source (circle one): Line-Timed Free Running
Distribution Port Numbering Mode (circle one): Physical Logical
AFM Configuration: xDSL
Customer Configuration: 1 2
Main Shelf Type: AnyMedia AS AnyMedia AS 800
High BER Algorithm: Fixed CRC Threshold Fixed BER Threshold

Notes:
1. You will set the Protection Mode to Duplex in a later step.

G. System Information TU-630

Contact (0-255 characters) _____________________________
Location (0-255 characters) _____________________________
Main Shelf Misc. Information (0-100 characters) _____________________________

H. Global ATM Parameters TU-630

VPI VCI F5 EtoE CC
(1 - 255) (32 - 64)
ATM Operations Channel: _____________ _____________ _____________
default: 254 default: 32 default: Disabled

Upstream Downstream
Shelf PCR (cps): _____________ _____________

I. Daisy-Chain upstream VP Information TU-630

J. Shelf VP Information TU-630

The default Shelf VP must be changed if 255 is already in use on another shelf in the daisy chain.
VPI VP Type Service Highest VCI F4 VP Segment
Category Allowed (circle one)
255 Shelf UBR 1999 - LPA920 Disabled Endpoint
________ Shelf ________ ________ Disabled Endpoint
________ Shelf ________ ________ Disabled Endpoint
________ Shelf ________ ________ Disabled Endpoint
________ Shelf ________ ________ Disabled Endpoint

K. Shelf Level Traffic Thresholds TU-630

Note, that the TCA for a given parameter is inhibited by setting the threshold to ″0″.

15-min interval (0 to 318000 24-hour interval (0 to 30.6 x

cells/frames) 106 cells/frames)
Cells dropped due to PPD _____________ _____________
Cells dropped due to EPD _____________ _____________
Cells dropped due to buffer overflow _____________ _____________
AAL5 Frames dropped due to EPD _____________ _____________

L. Daisy-Chain Information TU-640

GSI Connection (circle one): Console Port 10BaseT Port Remote LAN
IP Address _______________________________
Security ID _______________________________

Downstream VP Information
VPI VP Type Service Category F4 VP Segment (circle one)

Downstream ___ Disabled Endpoint

__________ Downstream _____________ Disabled Endpoint
__________ Downstream _____________ Disabled Endpoint
__________ Downstream _____________ Disabled Endpoint
__________ Downstream _____________ Disabled Endpoint
__________ Downstream _____________ Disabled Endpoint
Repeat above information for all shelves in the daisy-chain.

M. Feeder Port 2 Parameters TU-640

In a daisy-chain, you must enable and provision Port 2 of the existing shelf that feeds the new shelf.
Use the following parameters:
Logical Feeder
Administrative State: In Service

M. Feeder Port 2 Parameters TU-640

Facility Protection Mode Duplex 1+1 DBSF
Path RDI Code (circle one): One-bit Path RDI Code Disabled
Physical Feeder Information Enabled Disabled
Line Name 16 - 2 Working 16 - 2 Protection
15 - 2 Protection 15 - 2 Working
SLOT 16
Section Trace
- Trace Mode (circle one): Unspecified API
- Transmitted API (circle one): AnyMedia_Access 15-character text string
- Expected API (circle one): AnyMedia_Access 15-character text string
- API Monitor (circle one): Disabled Enabled
SLOT 15
Section Trace
- Trace Mode (circle one): Unspecified API
- Transmitted API (circle one): AnyMedia_Access 15-character text string
- Expected API (circle one): AnyMedia_Access 15-character text string
- API Monitor (circle one): Disabled Enabled

N. Install 2nd AFM TU-2605

If there is already a circuit pack in Slot 15, does it need to be replaced (circle Yes No
one)?

O. Provision Duplex AFM Mode TU-2610

Software Version Required ______________________

P. Feeder Port 1 Parameters TU-650

Logical Feeder
Path RDI Code (circle one): One-bit Path RDI Code Enhanced Path RDI Code
Physical Feeder Information
Line Name 16 - 1 Working 16 - 1 Protection
15 - 1 Protection 15 - 1 Working
SLOT 16
External Conditions
- Loopback: No Loop

P. Feeder Port 1 Parameters TU-650

Section Trace
- Trace Mode (circle one): Unspecified API
- Transmitted API (circle one): AnyMedia_Access 15-character text string
- Expected API (circle one): AnyMedia_Access 15-character text string
- API Monitor (circle one): Disabled Enabled
SLOT 15
External Conditions
- Loopback: No Loop
Section Trace
- Trace Mode (circle one): Unspecified API
- Transmitted API (circle one): AnyMedia_Access 15-character text string
- Expected API (circle one): AnyMedia_Access 15-character text string
- API Monitor (circle one): Disabled Enabled

BER Threshold
- Line Signal Degrade Threshold (circle 10-5 10-6 10-7 10-8 10-9 Disabled
one):
- Line Signal Fail Threshold (circle 10-3 10-4 10-5 -- -- Disabled
one):

Part 3. Cabling/Connection Information - Duplex AFMO

A. AFMO Cabling in Duplex Mode TU-2620c

(Daisy Chain)
The following information is needed only if a new shelf or AFM packs are to be installed.
Feeder Cabling Source (check one of the following)
ATM Feeder ID _______________________________
The following information is needed to calculate the optical attenuation:
Power Network OLIU AFMO
Slot 16 Receive Max __________ __________
Receive Min __________ __________
Slot 15 Receive Max __________ __________
Receive Min __________ __________
Is the AFMO to be connected to a LAN for remote operations? (circle one) Yes No
If the AFMs are being connected to a LAN for remote operations, what type of cable assembly is
being used? (circle one)
...................................................................................................................................................................................................................................
C-36 363-211-586
Issue 6, July 2007
ATM xDSL Engineering Work orders for AFMO Work Order for ATM xDSL Services — Duplex AFMO

A. AFMO Cabling in Duplex Mode TU-2620c

(Daisy Chain)
Special Assembly Hub and 3 Straight Cables
If the AFMO is to be connected to a LAN,
connect the 10BaseT cable assembly to __________________________

B. AFMO - Daisy-Chained: Cabling TU-2625c

The cable source is the last shelf listed in Part 1, Preliminary Information.
Is the AFMO to be connected to a LAN for remote operations (circle Yes No
one)?
If the AFMs are being connected to a LAN for remote operations, what type of cable assembly is
being used? (circle one)
Special Assembly Hub and 3 Straight Cables
If the AFMO is to be connected to a LAN,
connect the 10BaseT cable assembly to ____________________________

Part 4. Subshelf Information - Duplex AFMO

A. Subshelf TU-655, TU-656

ATM ADSL Service Activation Procedures Flowchart

ATM SDSL Service Activation Procedures Flowchart

ATM SHDSL Service Activation Procedures Flowchart

E1IMA Shelf Cascading Procedures Flowchart

Begin of Shelf Cascading Procedures

Slot not equipped Slot equipped

TU-698
LPA941 Upgrade to R1.25

TU-660
AP Installation/Growth

SA-301
SA-302 Wiring the E1 feeder Initiate E1IMA
connections for E1IMA AP Cascading

Provision/Retrieve E1 port
parameters (set further ports
in service and assign FRP)

IMA mode Required Change to UNI mode required

Provision/Retrieve
Add/Delete IMA Links
UNI Mode

Provision ATM
Virtual Connection

SA-321 Verify
Transmission Continuity

End of Shelf Cascading Procedures

Part 5. Service Activation Parameters - Duplex AFMO

Repeat for as many packs, ports, and cross-connects as required for the Mainshelf.

B. Pack Provisioning Information SA-300; SA-301; TU-660; TU-660a

ATM xDSL Slot in AP-1 AP-2 AP-3 AP-4 AP-5 AP-6 AP-7 AP-8
Mainshelf (circle
one):
AP-9 AP-10 AP-11 AP-12 AP-13 AP-14 AP-15( 1
)
Pack Type (circle ADSL SDSL SHDSL
one):
If E1IMA AP, complete additionally the following:
Î PM Enable all E1 Ports (✓)
Interval (circle one) 15 Minutes 24 Hours

Notes:
1. Not applicable for an E1IMA AP

C. Cabling Information SA-300; TU-660; TU-660a

NOTE: In a mixed narrowband and ATM xDSL configuration it is assumed that the NB subsystem
has already been installed and turned up before turning up the BB subsystem.

From NB AP Cable _ Pair __

NB Circuit Input to ADSL AP Cable _________ Pair __________
NB+ADSL Output of ADSL AP Cable _________ Pair __________
FDI/MDF Distribution Pair Cable _________ Pair __________

Case 1b: Adding ADSL only using an ADSL4p, ADSL8p, ADSL16p, ADSL4i AP, or ADSL16i (at
FDI/MDF)
ATM xDSL Slot ____________ ATM xDSL Port _________________

From ADSL AP Cable _ Pair __

FDI/MDF Distribution Pair Cable _________ Pair __________

Case 1c: Adding ADSL and POTS using a P32A32 AP (at the FDI/MDF)
ATM xDSL Slot ____________ ATM xDSL Port ________________

From combo AP Cable _ Pair __

FDI/MDF Distribution Pair Cable _________ Pair __________

From POTS/ISDN AP Cable _ Pair __

From ADSL AP Cable _________ Pair __________

FDI/MDF Distribution Pair Cable _ Pair __

Case 1e: Adding SDSL using a SDSL16 AP (at the FDI/MDF)

ATM xDSL Slot ____________ ATM xDSL Port ________________

From SDSL16 AP Cable _ Pair __

FDI/MDF Distribution Pair Cable _________ Pair __________

Case 1f: Adding SHDSL using an SHDSL16 AP (at the FDI/MDF)

ATM xDSL Slot ____________ ATM xDSL Port ______________

From SHDSL16 AP Cable _ Pair __

FDI/MDF Distribution Pair Cable _________ Pair __________

Case 2: Adding ADSL to NB using protector blocks (ADSL4p, ADSL8p, ADSL16p, ADSL4i AP, or
ADSL16i)
Protector Block Jack Locations
These locations are determined by the engineer from either of the following:
— cable and pair
— shelf, slot, port
Single plug end of the patch cord:
Subscriber loop Jack Location ________
Double plug end of the patch cord:
NB circuit input to ADSL AP Jack Location ________
NB+ADSL output of ADSL AP Jack Location ________

Case 3: Cabling the E1IMA AP to the DDF

E1IMA AP DDF
1 -------------------->

2 -------------------->

3 -------------------->

4 -------------------->
Tx
5 .

6 .

7 .

4
Rx
5

D. Transmission Parameters SA-300

Pack Type (circle one): ADSL SDSL SHDSL

Case 1a: ADSL Transmission Parameters

Part A.
Maximum Upstream Bit Rate ______________kbps (any multiple of 32 from 64 to 1440 kbps)
Maximum Downstream Bit ______________kbps (any multiple of 32 from 64 to 13120
Rate kbps)
Minimum Upstream Bit Rate ______________kbps (any multiple of 32 from 64 to 1440 kbps)
Minimum Downstream Bit ______________kbps (any multiple of 32 from 64 to 13120
Rate kbps)

Part B.
Downstream, Option 1 ________________ (Multiples of 32, from 64 to 8160
kbps)
Downstream, Option 2 ________________ (Multiples of 32, from 64 to 8160
kbps)
Downstream, Option 3 ________________ (Multiples of 32, from 64 to 8160
kbps)
Downstream, Option 4 ________________ (Multiples of 32, from 64 to 8160
kbps)
Upstream, Option 1 ________________ (Multiples of 32, from 64 to 1440
kbps)
Upstream, Option 2 ________________ (Multiples of 32, from 64 to 1440
kbps)
Upstream, Option 3 ________________ (Multiples of 32, from 64 to 1440
kbps)

Upstream, Option 4 ________________ (Multiples of 32, from 64 to 1440

kbps)

Additional ADSL Transmission Parameters

Upstream SNR margin in dB (integer from 0 to 15) _________________________
Downstream SNR margin in dB (integer from 0 to 15) _________________________

Upstream Interleave Depth (circle one) 1 2 4 8 16

PSDM in –dBm/Hz (integer from 40 to 60) _____________________________

Case 1b: ADSL2/ADSL2+ Transmission Parameters

Additional ADSL2/ADSL2+ Transmission Parameters

Type of Rate Adaptation: Flexible Flexible, Dynamic(1)

SNR Margin, dB US ________dB (0 to 15, in steps of 1)

DS ________dB (0 to 15, in steps of 1)

Upshift SNR Margin, dB US ________dB (0 to 31, in steps of 0.1)

DS ________dB (0 to 31, in steps of 0.1)

Upshift SNR Margin Time, sec US ________sec (0 to 16383, in steps of 1)

DS ________sec (0 to 16383, in steps of 1)

Downshift SNR Margin, dB US ________dB (0 to 31, in steps of 0.1)

DS ________dB (0 to 31, in steps of 0.1)

Downshift SNR Margin Time, sec US ________sec (0 to 16383, in steps of 1)

DS ________sec (0 to 16383, in steps of 1)

Min SNR Margin, dB US ________dB (0 to 31, in steps of 0.1)

DS ________dB (0 to 31, in steps of 0.1)

Max SNR Margin, dB US ________dB (0 to 31, in steps of 0.1)

DS ________dB (0 to 31, in steps of 0.1)

3
Max Aggregate Tx Power, dBm ( ) US ________dBm (0 to 25.5, in steps of 0.1)
DS ________dBm (0 to 25.5, in steps of 0.1)

Max Tx PSD, dBm/Hz US ________dBm/Hz -60 to -38

DS ________dBm/Hz -60 to -40

Max Data Rate, kbps US ________kbps 64 to 2048, in steps of 32

DS ________kbps 64 to 30016, in steps of 32
Min Data Rate, kbps US ________kbps 64 to 2048, in steps of 32

DS ________kbps 64 to 24000, in steps of 32

Interleave, msec US ________msec 0 to 254, in steps of 1
DS ________msec 0 to 254, in steps of 1

Latency US ________ interleaved, fast

DS ________ interleaved, fast
2
Minimum INP ( ) US auto auto, no-symbol, half-symbol,
one-symbol, two-symbols
DS auto

PSD Mask US ________ Default, Mask1 to Mask9 ( 4)

DS ________ Default

Enable/Disable READSL2 DS ________ Disabled, Enabled

Enable/Disable automatic Power Mgmt (2) DS Disabled Disabled, Wide Band, Narrow Band
2
Min L0 time, sec ( ) DS ________sec 0 to 255, in steps of 1

Min L2 time, sec (2) DS ________sec 0 to 255, in steps of 1

2
Max Aggregate Tx Power Reduc. ( ) DS ________dBm 0 to 31, in steps of 0.1

Notes:
1. The Type of rate adaptation Dynamic is supported only by LPA420 and LPA833.
2. Not supported by LPA420 and LPA833.
...................................................................................................................................................................................................................................
363-211-586 C-47
Issue 6, July 2007
ATM xDSL Engineering Work orders for AFMO Work Order for ATM xDSL Services — Duplex AFMO

3. The only supported value by LPA420 and LPA833 is 10.0 dbm.

4. Mask1 to Mask9 in upstream direction are used when the line is operating in Annex M mode (requires a
compatible modem at the other end). Not supported by LPA438.

Case 2: SDSL Transmission Parameters

___Existing Profile ID ______________
Name: _______________________________
___New Profile ID ______________ Existing profile used to create new profile
Name: _______________________________
Name: _______________________________
ID ______________ New profile (Technician fills in the ID supplied by
the GSI.)
Type of Rate Adaptation (circle one): Flexible Explicit
If you selected Flexible, complete Part A. If you selected Explicit, complete Part B. After completing
Part A or Part B, continue with Additional SDSL Transmission Parameters.

Part A.
Maximum Bit Rate ________________kbps (144, 272, 400, 528, 784, 1168, 1552, 2320)
Minimum Bit Rate ________________kbps (144, 272, 400, 528, 784, 1168, 1552, 2320)

Part B.
Explicit Bit Rate ________________kbps (144, 272, 400, 528, 784, 1168, 1552, 2320)

Additional SDSL Transmission Parameters

TX/RX Scramble (circle one): Enable Disable
ATM Cell Scramble (circle one): Enable Disable
COSET (circle one): Enable Disable

Case 3: SHDSL Transmission Parameters

___Existing Profile ID ______________
Name: _______________________________
___New Profile ID ______________ Existing profile used to create new profile
Name: _______________________________
Name: _______________________________
ID ______________ New profile (Technician fills in the ID supplied
by the GSI.)
...................................................................................................................................................................................................................................
C-48 363-211-586
Issue 6, July 2007
ATM xDSL Engineering Work orders for AFMO Work Order for ATM xDSL Services — Duplex AFMO

Case 3: SHDSL Transmission Parameters

Part A.
Maximum Bit Rate ________________kbps (Multiples of 64, from 192 to 2304 kbps)
Minimum Bit Rate ________________kbps (Multiples of 64, from 192 to 2304 kbps)

Part B.
Explicit Data Rate ________________kbps (Multiples of 64, from 192 to 2304
kbps)

E. Port Provisioning Information SA-300

ATM xDSL Slot AP-1 AP-2 AP-3 AP-4 AP-5 AP-6 AP-7 AP-8
(circle one):
AP-9 AP-10 AP-11 AP-12 AP-13 AP-14 AP-15( 1)
ATM xDSL Port (1 to 32): ___________

Notes:
1. Not applicable for E1IMA AP.

If ADSL, complete the Start Up Mode:

Start Up Mode (circle one): Multimode G994.1 (G.hs) T1.413 adsl2 adsl2+

xDSL Transmission Profile ID _________________________

Notes:
1. Only for ADSL2/ADSL2+

If SHDSL, complete additionally the following:

If E1IMA AP, complete additionally the following:

Loopback (circle one): No Loop Line Loop
Failure Report Profile: _______________________________

F. IMA Provisioning for E1IMA AP only TU-650a

IMA Mode (circle one): IMA UNI
If UNI, UNI Mode Link (circle one): 1 2 3 4 5 6 7 8
Î PM Enable (✓)
Î AIS Enable (✓)
Go to Part G.- E1 Feeder Provisioning Information TU-650a

If IMA, fill out the remainder of Part G: IMA Group Configuration

Î Inhibit IMA Group (✓)
Provisioned Protocol (circle one): V1.0 V1.1
Symmetry Mode (check one): Î Symmetric Configuration & Operation
Î Symmetric Configuration & Asymmetric Operation

Sufficient Tx Link (circle one): 1 2 3 4 5 6 7 8

IMA Links (circle selections): 1 2 3 4 5 6 7 8

G. ATM Traffic Parameters SA-300

Case 2: rt-VBR, nrt-VBR

Peak Cell Rate Upstream _________________cells/sec (150 to 108,940)
Peak Cell Rate Downstream _________________cells/sec (150 to 108,940)
PCR CDVT _________________ms (0.000680 to 1330)

Sustainable Cell Rate Upstream _________________cells/sec (150 to 108,939)

Sustainable Cell Rate Downstream _________________cells/sec (150 to 108,939)
SCR CDVT _________________ms (0.000680 to 1330)

Maximum Burst Size Upstream _________________cells (1 to 100)

Maximum Burst Size Downstream _________________cells (1 to 210)

Cell Loss Priority (circle one): CLP (0) CLP (0 + 1)

Cell Tagging (circle one): True False

Frame Discard (circle one): True False

Case 3: UBR
Peak Cell Rate Upstream _________________cells/sec (150 to 108,940)
Peak Cell Rate Downstream _________________cells/sec (150 to 108,940)
PCR (CDVT) _________________ms (0.000680 to 1330)

Cell Tagging (circle one): True False

Frame Discard (circle one): True False

H. Cross-Connect Provisioning SA-300

If the Shelf VPI (see Part 4c above) is used for the Feeder VPI, then a feeder VCI must be specified
as well. Complete Part A; otherwise, complete Part B.

Part A. Virtual Channel Cross-Connect

Feeder VPI ________________________
Feeder VCI ________________________
F5 Segment (circle one): Disabled Endpoint

Slot Number in AP-1 AP-2 AP-3 AP-4 AP-5 AP-6 AP-7 AP-8
Mainshelf (circle
one):
AP-9 AP-10 AP-11 AP-12 AP-13 AP-14 AP-15
ATM xDSL Port (1 to 32): ________
Subscriber VPI ________________
Subscriber VCI ________________
ATM Traffic Profile ________________
Traffic Statistics Profile ________________
Circuit ID ________________

Part B. Virtual Path Cross-Connect

Feeder VPI ___________________________
F4 Segment (circle one): Disabled Endpoint

Part B. Virtual Path Cross-Connect

Slot Number (circle AP-1 AP-2 AP-3 AP-4 AP-5 AP-6 AP-7 AP-8
one):
AP-9 AP-10 AP-11 AP-12 AP-13 AP-14
ATM xDSL Port (1 to 32): ________
Subscriber VPI ________________
ATM Traffic Profile ________________
Traffic Statistics Profile ________________
Circuit ID ________________

GSI Connection (circle one): Console Port 10BaseT Port LAN

IP Address _______________________________
Security ID _______________________________

Work Order for ATM xDSL Services — Simplex AFME1

Part 1. Preliminary Information - Simplex AFME1

Type of System: AnyMedia Access System

ATM xDSL Simplex AFME1 Turn-up Procedures Flowchart (Part 1)

Begin of Turn-Up Procedures with AFME1

TU-605
AFM Installation

TU-610 Verify/Update
AFM Software Load

TU-620b
AFME1 Cabling

TU-630a
(AFME1 Installed)
Provision Main Shelf

TU-650a Provision
AFME1 Feeder Port

ATM xDSL Simplex AFME1 Turn-up Procedures Flowchart (Part 2)

1
Broadband-only or
a mixed system
xDSL APs required in Mainshelf

TU-660 xDSL AP
no xDSL APs
Installation / Growth
required in Mainshelf

ONU Subshelves
with xDSL APs required

TU-655 OAP
no ONU Subshelves Installation Growth
with xDSL APs required

TU-656
Provision Subshelf

TU-660a xDSL APs

Installation / Growth (ONU)

TU-670b Verify Proper

AFME SystemTurn-Up

End of Turn-Up Procedures with AFME1

*) To activate the ATM xDSL subscriber services,

follow the next chapter “Activate Service and Test”.

Part 2. Installation/Cabling/Connection/ Software Information - Simplex AFME1

A. AFM Installation TU-605

If there is already a circuit pack in Slot 16, does it need to be replaced (circle one)? Yes No

B. GSI Connection OP-610

The following information is needed to connect the GSI to the shelf.
GSI Connection (circle one):
Console Port 10BaseT Port LAN
Select Link
PC Port (circle one): COM1 COM2 COM3 COM4 LAN
Log In
Security ID( 1) ________________________________
IP Address: ________ - ________ - ________ - ________ 192.168.160.160

Notes:
1. The initial default setting is ″public″.

Important! If only performing Service Activation, skip to Part 4, Service

Activation Parameters.

C. Verify AFM Software TU-610

Software Version Required ______________________

D. Cabling TU-620b
ATM Feeder ID _______________________________
Is the AFME1 to be connected to a LAN for remote operations (circle Yes No
one)?
If the AFME1 is to be connected to a LAN, connect 10BaseT cable assembly to _______________

Part 3. Turn-up Parameters - Simplex AFME1

A. Communications TU-630a
Security ID: _______________________
IP Configuration
IP Interfaces IP Address Subnet Mask
10BaseT: ____________ _____________
ATM: ____________ _____________
...................................................................................................................................................................................................................................
D-6 363-211-586
Issue 6, July 2007
ATM xDSL Engineering Work Order for AFME1 Work Order for ATM xDSL Services — Simplex AFME1

Console: Default: 192.168.0.1 _

Default Router (circle one):
10BaseT ____________
ATM

Autonomous Messages Destination

B. System Identification TU-630

Select to Set: AFM
New Value: (0-255 characters) ______________________________________

C. System Configuration TU-630

Distribution Port Numbering Mode (circle Physical Logical
one):
Customer Configuration: 1 2
Main Shelf Type: AnyMedia AS AnyMedia AS 800
High BER Algorithm: Fixed CRC Threshold Fixed BER Threshold

D. System Information TU-630

Contact (0-255 characters) _____________________________
Location (0-255 characters) _____________________________
Main Shelf Misc. Information (0-100 characters) _____________________________

E. Global ATM Parameters TU-630

VPI VCI F5 EtoE CC
(1 - 255) (32 - 64)

ATM Operations Channel: _______ _ _______

default: 254 default: 32 default: Disabled

Upstream Downstream
Shelf PCR (cps): _____________ _____________

F. Shelf VP Information TU-630a

The default Shelf VP must be changed if 255 is already in use on another shelf in the daisy chain.
VPI VP Type Service Highest VCI Allowed F4 VP Segment
Category (circle one)
255 Shelf UBR 1999 - LPA941 Disabled Endpoint
________ Shelf ________ ________ Disabled Endpoint
________ Shelf ________ ________ Disabled Endpoint
________ Shelf ________ ________ Disabled Endpoint
________ Shelf ________ ________ Disabled Endpoint

G. E1 Feeder Provisioning Information TU-650a

Feeder Port Parameters (provision each feeder port SEPARATELY, then go to Timing Source
Parameters below)
Feeder Port 1 Administrative State: OOS IS
Feeder Port 2 Administrative State: OOS IS
Feeder Port 3 Administrative State: OOS IS
Feeder Port 4 Administrative State: OOS IS
Feeder Port 5 Administrative State: OOS IS
Feeder Port 6 Administrative State: OOS IS

G. E1 Feeder Provisioning Information TU-650a

Feeder Port 7 Administrative State: OOS IS
Feeder Port 8 Administrative State: OOS IS
Timing Source Parameters
Primary Timing Source (circle one): 1 2 3 4 5 6 7 8
Secondary Timing Source (circle one): 1 2 3 4 5 6 7 8

H. IMA Provisioning for AFME1 TU-650a

IMA Mode (circle one): IMA UNI
If UNI, UNI Mode Link (circle one): 1 2 3 4 5 6 7 8
Go to Part G.- E1 Feeder Provisioning Information TU-650a

If IMA, fill out the remainder of Part G:

Sufficient Tx Link (circle one): 1 2 3 4 5 6 7 8

Sufficient Rx Link (circle one): 1 2 3 4 5 6 7 8
Tx Frame Length (circle one): 32 64 128 256
Tx Amas IMA ID Î 0 (0 to 256)
Tx Clocking Mode (check one): Î Common
Î Independent
Maximum Differential Delay (5 to 45 msec, 10 ms increments): 25 msec _____________
Synchronization Parameters
Alpha (circle one): 1 2
Beta (circle one): 1 2 3 4 5
Gamma (circle one): 1 2 3 4 5
IMA Links (circle selections): 1 2 3 4 5 6 7 8

I. Subshelf TU-655, TU-656

OAP slot
ONU

Shelf number (1-7) ____________________________________

Subsite ID (0-255 chars) ____________________________________
Physical ID ____________________________________
Contact (0-255 chars) ____________________________________
Location (0-255 chars) ____________________________________
Parent slot (OAP slot; 2-14) ____________________________________

ATM ADSL Service Activation Procedures Flowchart

ATM SDSL Service Activation Procedures Flowchart

ATM SHDSL Service Activation Procedures Flowchart

E1IMA Shelf Cascading Procedures Flowchart

Begin of Shelf Cascading Procedures

Slot not equipped Slot equipped

TU-698
LPA941 Upgrade to R1.25

TU-660
AP Installation/Growth

SA-301
SA-302 Wiring the E1 feeder Initiate E1IMA
connections for E1IMA AP Cascading

Provision/Retrieve E1 port
parameters (set further ports
in service and assign FRP)

IMA mode Required Change to UNI mode required

Provision/Retrieve
Add/Delete IMA Links
UNI Mode

Provision ATM
Virtual Connection

SA-321 Verify
Transmission Continuity

End of Shelf Cascading Procedures

Part 4. Service Activation Parameters - Simplex AFME1

Repeat for as many packs, ports, and cross-connects as required for the Mainshelf.

B. Pack Provisioning Information SA-300; SA-301 TU-660; TU-660a

Notes:
1. Not applicable for an E1IMA AP

C. Cabling Information SA-300; TU-660; TU-660a

NOTE: In a mixed narrowband and ATM xDSL configuration it is assumed that the NB subsystem
has already been installed and turned up before turning up the BB subsystem.

From NB AP Cable _ Pair __

NB Circuit Input to ADSL AP Cable _________ Pair __________
NB+ADSL Output of ADSL AP Cable _________ Pair __________
FDI/MDF Distribution Pair Cable _________ Pair __________

Case 1b: Adding ADSL only using an ADSL4p, ADSL8p, ADSL16p, ADSL4i AP, or ADSL16i (at
FDI/MDF)
ATM xDSL Slot ____________ ATM xDSL Port ________________

From ADSL AP Cable _ Pair __

FDI/MDF Distribution Pair Cable _________ Pair __________

Case 1c: Adding ADSL and POTS using a P32A32 AP (at the FDI/MDF)
ATM xDSL Slot ____________ ATM xDSL Port ________________

From combo AP Cable _ Pair __

FDI/MDF Distribution Pair Cable _________ Pair __________

From POTS/ISDN AP Cable _ Pair __

From ADSL AP Cable _________ Pair __________

FDI/MDF Distribution Pair Cable _ Pair __

Case 1e: Adding SDSL using a SDSL16 AP (at the FDI/MDF)

ATM xDSL Slot ____________ ATM xDSL Port ________________

From SDSL16 AP Cable _ Pair __

FDI/MDF Distribution Pair Cable _________ Pair __________

Case 1f: Adding SHDSL using an SHDSL16 AP (at the FDI/MDF)

ATM xDSL Slot ____________ ATM xDSL Port ______________

From SHDSL16 AP Cable _ Pair __

FDI/MDF Distribution Pair Cable _________ Pair __________

Case 3: Cabling the E1IMA AP to the DDF

E1IMA AP DDF
1 -------------------->

2 -------------------->

3 -------------------->

4 -------------------->
Tx
5 .

6 .

7 .

4
Rx
5

D. Transmission Parameters SA-300

Pack Type (circle one): ADSL SDSL SHDSL

Case 1: ADSL Transmission Parameters

— Existing Profile ID ______________
Name: _______________________________
— New Profile ID ______________ Existing profile used to create new profile
Name: _______________________________
Name: _______________________________
ID ______________ New profile (Technician fills in the ID supplied by
the GSI)
Type of Rate Adaptation (circle one): Flexible Explicit
If you selected Flexible, complete Part A. If you selected Explicit, complete Part B.
After completing Part A or Part B, continue with Additional ADSL Transmission Parameters.

Part A.
Maximum Upstream Bit Rate ______________kbps (any multiple of 32 from 64 to 1440 kbps)
Maximum Downstream Bit ______________kbps (any multiple of 32 from 64 to 13120
Rate kbps)
Minimum Upstream Bit Rate ______________kbps (any multiple of 32 from 64 to 1440 kbps)
Minimum Downstream Bit ______________kbps (any multiple of 32 from 64 to 13120
Rate kbps)

Part B.
Downstream, Option 1 ________________ (Multiples of 32, from 64 to 8160
kbps)
Downstream, Option 2 ________________ (Multiples of 32, from 64 to 8160
kbps)
Downstream, Option 3 ________________ (Multiples of 32, from 64 to 8160
kbps)
Downstream, Option 4 ________________ (Multiples of 32, from 64 to 8160
kbps)
Upstream, Option 1 ________________ (Multiples of 32, from 64 to 1440
kbps)
Upstream, Option 2 ________________ (Multiples of 32, from 64 to 1440
kbps)
Upstream, Option 3 ________________ (Multiples of 32, from 64 to 1440
kbps)

Upstream, Option 4 ________________ (Multiples of 32, from 64 to 1440

kbps)

Additional ADSL Transmission Parameters

Upstream SNR margin in dB (integer from 0 to 15) _________________________
Downstream SNR margin in dB (integer from 0 to 15) _________________________

Upstream Interleave Depth (circle one) 1 2 4 8 16

PSDM in –dBm/Hz (integer from 40 to 60) _____________________________

Case 2: SDSL Transmission Parameters

___Existing Profile ID ______________
Name: _______________________________
___New Profile ID ______________ Existing profile used to create new profile
Name: _______________________________
Name: _______________________________
ID ______________ New profile (Technician fills in the ID supplied by
the GSI)
Type of Rate Adaptation (circle one): Flexible Explicit
If you selected Flexible, complete Part A. If you selected Explicit, complete Part B. After completing
Part A or Part B, continue with Additional SDSL Transmission Parameters.

Part A.

Maximum Bit Rate ________________kbps (144, 272, 400, 528, 784, 1168, 1552, 2320)
Minimum Bit Rate ________________kbps (144, 272, 400, 528, 784, 1168, 1552, 2320)

Part B.
Explicit Bit Rate ________________kbps (144, 272, 400, 528, 784, 1168, 1552, 2320)

Additional SDSL Transmission Parameters

TX/RX Scramble (circle one): Enable Disable
ATM Cell Scramble (circle one): Enable Disable
COSET (circle one): Enable Disable

Case 3: SHDSL Transmission Parameters

___Existing Profile ID ______________
Name: _______________________________
___New Profile ID ______________ Existing profile used to create new profile
Name: _______________________________
Name: _______________________________
ID ______________ New profile (Technician fills in the ID
supplied by the GSI.)
Type of Rate Adaptation (circle one): Flexible Explicit
If you selected Flexible, complete Part A. If you selected Explicit, complete Part B. After completing
Part A or Part B, continue with Additional SHDSL Transmission Parameters.

Part A.
Maximum Bit Rate ________________kbps (Multiples of 64, from 192 to 2304 kbps)
Minimum Bit Rate ________________kbps (Multiples of 64, from 192 to 2304 kbps)

Part B.
Explicit Data Rate ________________kbps (Multiples of 64, from 192 to 2304 kbps)

E. Port Provisioning Information SA-300

ATM xDSL Slot AP-1 AP-2 AP-3 AP-4 AP-5 AP-6 AP-7 AP-8
(circle one):
AP-9 AP-10 AP-11 AP-12 AP-13 AP-14 AP-15( 1)
ATM xDSL Port (1 to 32): ___________

Notes:
1. Not applicable for E1IMA AP.

If ADSL, complete the Start Up Mode:

Start Up Mode (circle one): Multimode G.994.1 (G.hs) T1.413

xDSL Transmission Profile ID _________________________

(If a new profile was created in Part 5D, enter that ID.)
PM Profile: ___________________________
Failure Report Profile: ___________________________
Î Enable AIS (✓)

If SHDSL, complete additionally the following:

If E1IMA AP, complete additionally the following:

Loopback (circle one): No Loop Line Loop
Failure Report Profile: _______________________________

F. IMA Provisioning for E1IMA AP only TU-650a

IMA Mode (circle one): IMA UNI
If UNI, UNI Mode Link (circle one): 1 2 3 4 5 6 7 8
Î PM Enable (✓)
Î AIS Enable (✓)
Go to Part G.- E1 Feeder Provisioning Information TU-650a

If IMA, fill out the remainder of Part G: IMA Group Configuration

Î Inhibit IMA Group (✓)
Provisioned Protocol (circle one): V1.0 V1.1
Symmetry Mode (check one): Î Symmetric Configuration & Operation
Î Symmetric Configuration & Asymmetric Operation

IMA Mode (circle one): IMA UNI

Sufficient Tx Link (circle one): 1 2 3 4 5 6 7 8
Sufficient Rx Link (circle one): 1 2 3 4 5 6 7 8
Tx Frame Length (circle one): 32 64 128 256
Tx Amas IMA ID Î 0 (0 to 256)
Tx Clocking Mode (check one): Î Common
Î Independent
Maximum Differential Delay (5 to 45 msec, 10 ms increments): 25 msec _____________
Failure Report Profile
Synchronization Parameters
Alpha (circle one): 1 2
Beta (circle one): 1 2 3 4 5
Gamma (circle one): 1 2 3 4 5
IMA Links (circle selections): 1 2 3 4 5 6 7 8

G. ATM Traffic Parameters SA-300

___ Existing Profile ID ___________________
Name ________________
___ New Profile ID ___________________
Name ________________ Existing profile used to create new
profile
Name ________________ New Profile
ID ___________________ New profile (Technician fills in the ID
supplied by the GSI.)
Service Category (circle one): CBR rt-VBR nrt-VBR UBR
Profile Name: _______________________________ (0 - 64 characters)
The specific profile parameters needed will depend on the service category.

Case 2: rt-VBR, nrt-VBR

Peak Cell Rate Upstream _________________cells/sec (150 to 108,940)

Peak Cell Rate Downstream _________________cells/sec (150 to 108,940)
PCR CDVT _________________ms (0.000680 to 1330)

Sustainable Cell Rate Upstream _________________cells/sec (150 to 108,939)

Sustainable Cell Rate Downstream _________________cells/sec (150 to 108,939)
SCR CDVT _________________ms (0.000680 to 1330)

Maximum Burst Size Upstream _________________cells (1 to 100)

Maximum Burst Size Downstream _________________cells (1 to 210)

Cell Loss Priority (circle one): CLP (0) CLP (0 + 1)

Cell Tagging (circle one): True False
Frame Discard (circle one): True False

Case 3: UBR
Peak Cell Rate Upstream _________________cells/sec (150 to 108,940)
Peak Cell Rate Downstream _________________cells/sec (150 to 108,940)
PCR (CDVT) _________________ms (0.000680 to 1330)

Cell Tagging (circle one): True False

Frame Discard (circle one): True False

H. Cross-Connect Provisioning SA-300

If the Shelf VPI (see Part 4c above) is used for the Feeder VPI, then a feeder VCI must be specified
as well. Complete Part A; otherwise, complete Part B.

Part A. Virtual Channel Cross-Connect

Feeder VPI ________________________
Feeder VCI ________________________
F4 Segment (circle one): Disabled Endpoint
F4 Segment CC (circle one): Disabled Endpoint

Slot Number in AP-1 AP-2 AP-3 AP-4 AP-5 AP-6 AP-7 AP-8
Mainshelf (circle
one):
AP-9 AP-10 AP-11 AP-12 AP-13 AP-14 AP-15
ATM xDSL Port (1 to 32): ________
Subscriber VPI ________________
Subscriber VCI ________________
ATM Traffic Profile ________________
Thrshold Profile ________________
Circuit ID ________________

Part B. Virtual Path Cross-Connect

Numerics

0dBr-Point
0dBr-Point is a defined digital reference point. This point is located on the digital signal
side in a local exchange (LE).

1N / 3N
Formats of packs which define the height according to the One GPN standard hardware
requirement.

2B1Q
2 Binary 1 Quartenary Line Code

3 kHz flat filter

The 3 kHz flat filter for noise measurements allows low frequency noise to be passed
while still restricting the high frequencies above 3 kHz. Its characteristic shape is that of
a 3 kHz low pass filter. If a noise source is suspected to be mostly low frequencies it
can be detected by taking a measurement with the 3 kHz flat filter and then the
C-message filter. A lower noise reading with the C-message filter will indicate noise
from 20/25 Hz ringing, 50/60 Hz power line induction or some other low frequency
interference.

4B3T
4 Binary, 3 Ternary Line Code

10BaseT
Ethernet with 10 Mbps (IEEE 802.3)

10BaseT
IEEE 802.3 standard for Ethernet transmission over unshielded twisted pair.

995A cross couple connector

A 40-pin micro-strip connector to join 2 AFMOs in duplex AFM mode via the faceplates
in order to enable transfer of transmission data between the active and the standby
AFMO

A A&IP
Alarm and Interconnection Panel

a-wire
One of the two wires of a twisted a/b copper pair. The a/b copper pairs are used for
subscriber lines connected for example with Z interfaces, U interfaces, HDSL interfaces
or ADSL interfaces. The a-wire is sometimes called tip-wire.

AAL
ATM adaptation layer - A set of internationally standardized protocols and formats that
define support for circuit emulation, packet video and audio, and connection-oriented
and connectionless data services. There are four standard protocols defined for AAL:
AAL1, AAL2, AAL3/4, and AAL5.
AAL5 is used for bursty LAN traffic and uses the conventional five-byte ATM header.
AAL5 does not support cell multiplexing.

AAL1
ATM adaptation layer 1 - An AAL that supports constant bit rate (CBR) traffic.

AAL5
ATM adaptation layer 5 - An AAL that supports variable bit rate (VBR) traffic both for
real time (rt) as well as for non real time (nrt) applications and variable packet length
traffic.

AC
Alternating Current

AC fail alarm
A power supply option which monitors the input voltage and provides an isolated logic
output signal when there is a loss of line voltage.

Accelerated alignment
The accelerated alignment procedure is the capability to block/unblock all user ports
(PSTN, ISDN BRA and ISDN PRA) via common control protocol at V5.2 interface. The
block accelerated alignment procedure is requested by the 2nd edition of the V5.2
specification.

Access digital section

The concept used to allow a functional and procedural description and a definition of the
network requirements from V1 reference point and T reference point.

ACO
Alarm cut-off

ACP
Alarm Connection Panel

Activated state
The state where transmission of data over the U interface is possible. In the activated
state data can be transmitted in both directions between the user terminal and the LT.
...................................................................................................................................................................................................................................
GL-2 363-211-586
Issue 6, July 2007
Glossary

The U interface and the S/T interface are activated. While in the activated state, the
deactivation can only be initiated in the downstream direction.

Activation State
The activation state gives information if a port is enabled or disabled for service.

Active alarm message

Each alarm message contains alarm attributes, including access identifier, condition type,
severity level, service-affecting characteristics, and condition description. Currently
active alarms are listed in order of severity and chronologically within each severity
classification.

Active image
The peripheral image which is intended to be executed whenever it is functional.
Initially it is installed on the peripheral packs in the factory and may be overwritten by
peripheral SW download. There are active images for peripheral processors and for field
programmable gate arrays (FPGAs).

Active pack
Identifies the pack which is currently responsible for handling the service in a protected
configuration. An active pack may also be in a state where no service is possible, for
example faulty or moved to OOS by the operator.

Active protection physical channel

A protection physical channel (timeslot) which is currently carrying a V5 logical
communication channel. See also standby protection physical channel.

Active provisioning variant

The provisioning variant label which is used for the V5 interface for the next V5
start-up procedure. Every V5.x interface has an active provisioning variant.

Active status condition message

Each status condition message contains access identifier, condition type, condition effect,
and condition description. Currently active status conditions are listed chronologically
(see also status condition).

ACU
Alarm Control Unit

ADM
Add/Drop Multiplexer

Administrative primary service state

Primary service state which is provisioned by the craft. Administrative primary service
state is used on the PACKS- and the LINES-layer but not on SLOT-, EQUIPMENT- and
SERVICE-layer. See also service state.

Admissible Bandwidth
The amount of bandwidth allocated to a service category in the upstream and
downstream directions, except for UBR. The sum of the effective bandwidths allocated
to all connections supported by a service category, divided by the overbooking factor of

that service category, must not exceed the admissible bandwidth of this service category.
The admissible bandwidth of a service category may not exceed Shelf PCR.

ADSL
Asynchronous Digital Subscriber Line

ADSL (Full-rate ADSL)

Asymmetric digital subscriber line - A method of data transmission over unloaded copper
loops. The data rate transmitted toward the end user is typically much higher (e.g.
6.144 Mbps) than the data rate transmitted by the end user (e.g. 640 kbps).

ADSL AP
Asymmetrical Digital Subscriber Line application pack (ATU-C) that transmits and
receives a broadband signal to/from ATU-R customer premises equipment (CPE), and if
so connected, diplexes a voice frequency signal on to the same tip and ring pair carrying
the broadband signal.

ADSL subscriber
Asymmetric digital subscriber line - The subscriber lines that terminate on ADSL APs.

ADSL superframe
An ADSL superframe is composed of 68 data frames transmitted/received on an ADSL
port. ADSL superframes are transmitted every 17 ms. This rate applies regardless of
trained bit rate.

ADSL-lite (Universal)
A version of asymmetric digital subscriber line (ADSL) that is less expensive than
full-rate ADSL and that operates at a lower bit rate than full-rate ADSL. This version of
ADSL is specified in ITU-T G.992.2.

ADSL2/ADSL2+
ADSL2 and ADSL2+ are two new standards for asymmetric digital subscriber line
(ADSL) technology specified in ITU-T G.992.3 to ITU-T G.992.5. These standards are
specifically designed to improve the rate and reach of ADSL largely by achieving better
performance on long lines in the presence of narrowband interference. ADSL2 achieves
downstream and upstream data rates of about 12 Mbps and 1 Mbps respectively,
depending on loop length and other factors. ADSL2 accomplishes this by improving
modulation efficiency, reducing framing overhead, achieving higher coding gain,
improving the initialization state machine, and providing enhanced signal processing
algorithms. As a result, ADSL2 mandates higher performance for all standard-compliant
devices. Compared with standard ADSL, ADSL2/ADSL2+ provides doubled bandwidth
in downstream direction.

AFM
ATM Feeder Multiplexer

AFM
Asynchronous transfer mode feeder multiplexer - The AFM serves as the sole common
control and feeder interface unit for AnyMedia ® Access System ATM xDSL services.

AFMDS3
Electrical DS3 ATM Feeder Multiplexer (45 Mbps)

AFME1
Multiple E1 ATM Feeder Multiplexer

AFME3
Electrical E3 ATM Feeder Multiplexer (34 Mbps)

AFMO
Optical ATM Feeder Multiplexer (155 Mbps)

AID
Access identifier - AID is the address within a TL1 command that is used to identify the
physical or logical entity (or entities) within a network element to which the command
applies. It has the format of a unique component identifier followed by hierarchical
addresses of components. For example, drop-{1}-{3}-{8} is an object representing the
physical subscriber line #8 of the application pack in slot #3 in the AnyMedia Shelf #1.

AIP
Access interface platform - The access interface platform is a set of packs that can be
used in local exchanges (LE) or in access applications to provide services to subscribers.
These services include narrowband services (for example POTS, ALL, ISDN, DLL,...) as
well as ATM xDSL services such as ADSL.

AIP-1
Access interface platform 1 - Access interface platform system configuration with a
backplane for narrowband services only.

AIP-2
Access interface platform 2 - Access interface platform system configuration with a
backplane for narrowband and ATM xDSL services.

AIS
Alarm indication signal - A signal that replaces the normal traffic signal on an E1 link
or on an E3 feeder when a maintenance alarm indication has been activated. AIS is
defined as an unframed all ones signal (at scope of the AnyMedia ® Access System in
direction to the far end).

ALL
Analog leased line - Service using a 2-wire Z interface for analog subscriber terminals
without out-band signaling and without DC feeding (normally for uses other than
telephony, for example data transmission).

AN
Access Network

Ancillary equipment
Ancillary equipment refers to equipment included in the system site that is no integrated
into the system’s internal communication network. There are not assigned CLEI codes
but any associated inventory data with this equipment would include a barcode that can

be electronically scanned and interpreted. It typically includes power and cabling

material and hardware such as battery shelves, fan shelves, batteries etc. Ancillary
equipment is not included in any TL1 messages to retrieve inventory information.

ANE
Access network element - An access network element is a system, implemented between
service node (for example local exchange LE) and user, replacing part or the whole of
the local line distribution network.

Anomaly
An anomaly is a discrepancy between the actual and desired characteristics of an item.
The desired characteristics may be expressed in the form of a specification. An anomaly
may or may not affect the ability of an item to perform a required function. This
definition applies to No Cell Delineation and Header Error Control anomalies for ADSL
services.

ANSI
American National Standards Institute

AnyMedia ® Access System

The AnyMedia ® Access System is an access network element which supports various
narrowband and ATM xDSL services, digital as well as analog.

AnyMedia ® ETSI V5 Shelf

The AnyMedia Mainshelf consists of a metal mechanical structure that serves to guide
and fasten packs, locate and mount a multi-layer backplane. It allows mounting into
supporting structures such as racks and provides an interface for internal and external
connections. One AnyMedia Mainshelf houses up to 16 physical E1 links and up to 16
subscriber distribution application packs.

AnyMedia ® LAG 1900 Shelf

The AnyMedia ® LAG 1900 Shelf is a specific LAG Shelf. It contains seven 1N high
slots for 1N-sized common packs and 17 3N high slots for common packs (COMDAC,
CIU, IPFM, AFM) and application packs with subscriber interfaces. The AnyMedia ®
LAG 1900 Shelf can house narrowband services, ATM xDSL services and/or IP-based
services.

AnyMedia ® LAG 200 Shelf

The AnyMedia LAG 200 Shelf consists of a high speed IP spoke architecture that serves
up to three IP-based application packs for supporting Ethernet, VDSL and VoIP services.
The shelf provides three 3N high slots (3 APs or 2 APs and one controller) and three 1N
double wide slots. The LAG 200 Shelf with door could be deployed in LAG 200 cabinet
as well as in the customer supplied cabinet with 19”, ETSI or 23” racks. It provides
interfaces for internal and external connections and can operate in controlled mode with
combined uplink and stand-alone mode with separate uplinks.

AnyMedia ® LAG 4300 Shelf

The AnyMedia ® LAG 4300 Shelf is a double row shelf. The upper row contains six 1N
high slots and 22 3N high slots. The lower row contains 24 3N high slots. The 1N high
slots are designated for circuit packs with network interfaces, while certain of the 3N
high slots are designated for control (COMDAC, CIU, ..) and the other 3N high slots are
...................................................................................................................................................................................................................................
GL-6 363-211-586
Issue 6, July 2007
Glossary

designated for circuit packs with subscriber interfaces.

AnyMedia LAG 4300 System

The AnyMedia LAG 4300 System is housed in an EMI protected indoor cabinet and can
be delivered in three configurations equipped with
• one AnyMedia ® LAG 4300 Shelf
• two AnyMedia ® LAG 4300 Shelves
• two AnyMedia ® LAG 4300 Shelves and two AnyMedia ® ETSI V5 Shelves.
The Power Filter Units, Passive Clock Distributions, Ringing Filter Units, Alarm
Connection Panels and fan units are also housed in the indoor cabinet.

AP
Application pack

APOG
Applications and Planning Guide

APP
Apparatus code

Apparatus code
The apparatus code is an 8-byte item of ASCII information stored in the nonvolatile data
storage (NVDS) of a pack (for example LPZ100, DTP500,...). It is a unique identifier
which specifies the function of the pack.

Application interface
An interface at the user side to provide ISDN PRA or n × 64 kbps digital leased lines
services. Examples for application interfaces are G. 703, V.35, V.36, ...

Application mode
See HDSL application mode.

Application pack
A circuit pack which is located in any of the AP slots and supports subscriber interfaces
for certain services. Some examples for application packs are LPZ100, LPA416,
LPU430.

AP_ E1 port
An AP based E1 port, currently available on SHDSL AP (LPS510) supporting
unstructured services.

AR
Action Request

Asymmetric digital subscriber line (ADSL)

A method of data transmission over unloaded copper loops. The data rate transmitted
toward the end user is typically much higher (e.g., 6 Mbps) than the data rate
transmitted by the end user (e.g., 640 Kbps).

ATM
Asynchronous transfer mode - A high-speed connection-oriented multiplexing and
switching method that utilizes fixed-length cells to support multiple types of traffic.
Transmission is synchronized at the start and end of each character, allowing different
types of services to be carried over one system.

ATM adaptation layer (AAL)

A set of internationally standardized protocols and formats that define support for circuit
emulation, packet video and audio, and connection-oriented and connectionless data
services. There are four standard protocols defined for AAL—AAL1, AAL2, AAL3/4,
and AAL5.
AAL5 is used for bursty LAN traffic and uses the conventional five-byte ATM header.
AAL5 does not support cell multiplexing.

ATM feeder
The connection from the AFM to the ATM transport network. This connection may be
either E3, DS3, E1, STM-1 or OC-3c. The ATM feeder may connect directly to an ATM
switch or access concentrator device. In addition, the connection between the AFM and
the switch or access concentrator may incorporate a multiplexer. In daisy-chained
configurations, the ATM feeder for each AFM, except the one closest to the switch or
access concentrator, connects to the previous AFM in the chain. This connection may be
direct or through a multiplexer. Note that daisy-chaining is available only with E3, DS3,
STM-1 and OC-3c AFMs.

ATM switch
The ATM switch is a general term for ATM network elements performing ATM switching
functions. The ATM access concentrators and ATM edge switches are special types of
them.

ATM technology
Asynchronous transfer mode technology - Asynchronous transfer mode is a data
communications format in which transmission is synchronized at the start and end of
each character, allowing different types of services to be carried over one system.

ATM traffic statistics

For the AnyMedia Access System, ATM traffic statistics refers to the performance
monitoring function for ATM cell counts. ATM traffic statistics can be collected either at
the shelf level, or for specific connections. At the connection level, the technician may
choose to activate ATM traffic statistics for all connections on an AP, for all connections
on an end-user port, or for an individual connection, including the ATM Operations
Channel.

ATM xDSL services

High speed data and asynchronous transfer mode services.

ATS
Access transmission system - Refers to the line system using metallic pairs, optical
fibers, or radio systems. The line transceivers of the U port and of the HDSL port are
also part of the access transmission system. The concept of ATS is used to describe the
characteristics of an implementation, using a specific medium to support ISDN BRA,
ISDN PRA, DLL or n × 64 kbps digital leased lines.
...................................................................................................................................................................................................................................
GL-8 363-211-586
Issue 6, July 2007
Glossary

Attenuation of ADSL line

The difference in dB between the power received at the far end and the power
transmitted by the near end.

AUC
Awaiting unblocking complete (a secondary service state) - The system is waiting until
the switch sets the V5 subscriber or link in service; that is, until it sends an ″unblock″.

Authentication
Process used to verify the integrity of transmitted data, especially that of a message.

AUXID
Auxiliary ID code - The AUXID facilitates distinguishing of packs that have identical
main ID codes. The AUXID is 2 characters long. Currently not used in the AnyMedia ®
Access System.

Availability
The probability that a system is in operable state at a given instant in time.

Available time
For a digital transmission channel, a new period of available time begins with the first
second of a period of 10 consecutive seconds, each of which has a bit error ratio (BER)
of better than 10 -3. These 10 seconds are considered to be available time (see also
unavailable time).

AWG
American Wire Gauge
....................................................................................................................................................................................................................................

B B-channel
An ISDN bearer service channel that can carry either voice or data at a speed of 64
kbps.

b-wire
One of the two wires of a twisted a/b copper pair. The a/b copper pairs are used for
subscriber lines connected for example with Z interfaces, U interfaces, [S]HDSL inter-
faces or ADSL interfaces. The b-wire is sometimes called ring-wire.

Backup image
The peripheral image which is intended to be executed when no active image is
functional. It is installed on the peripheral packs in the factory and normally cannot be
overwritten by peripheral SW download. It is not of the latest SW version but is
intended to provide basic services and features as much as possible. Additionally it
provides the functions of the boot program. There are backup images for peripheral
processors and for field programmable gate array (FPGAs).

Backward direction
The direction that is opposite to that followed by monitored user cells. Unlike the
definition of upstream and downstream direction, the forward and backward directions
are relative to a reference point (e.g., the point where a failure occurs).

Battery backup
In addition to a power plant a battery pack is supplied to provide power backup in cases
of AC power failures.

Bay alarm summary LED

This is an alarm indication LED visible with closed cabinet doors for AnyMedia LAG
Systems. Each indoor cabinet bay has a related alarm indication LED, so a cabinet has
two alarm indication LEDs, one on the front side bay and another one on the rear side
bay. The bay alarm summary LED is operated if a failure in any system housed in the
related cabinet side’s bay is detected.

BB subsystem
The AnyMedia ® Access System components that are needed to provide ATM xDSL
services. That is, the AFM,, ADSL AP, SDSL AP and SHDSL AP. Components that only
carry narrowband service (e.g., the COMDAC) are not included in the broadband
subsystem. One AnyMedia LAG Shelf may contain up to two independent BB
subsystems.

BCC protocol
Bearer channel connection protocol - This is a V5.2 protocol which allocates bearer
channels on demand.

Bearer channel
A 64-kbps timeslot within the V5.x interface allocated for a B-channel of an ISDN user
port or a channel from a POTS user port.

BER
Bit error ratio - The quality of transmission is measured in the number of errored bits
per number of bits received.

BHCA
Busy hour call attempts - BHCA indicates the number of call attempts by one subscriber
during the busy hour time.

BHCC
Busy hour completed calls - BHCC indicates the number of successfully completed calls
during the busy hour time.

BIS
Battery Isolation Switch

BIST
Built-in Self-Test - The BIST is a procedure executed by a pack either after power-up or
on demand. The task is to check the functions of the hardware.

BLK
Blocked (a secondary service state) - The switch forces the V5 subscriber to go in
blocked status. For example if a V5 subscriber is administratively set to OOS in the
switch.

BMAN
Board metallic access network - Connects or disconnects the line pack bus (LPB) to the
test in or test out bus on the backplane. An ISDN AP and an HDSL AP contain one
BMAN.

Boot program
A program providing some basic communication and error handling functions. It is long
term stable and version independent.

BORSCHT
BORSCHT is an abbreviation for interface functions provided by Z ports for POTS.
• Battery (Subscriber loop feeding)
• Overvoltage/Overcurrent protection
• Ringing (Ringing signal provided for subscriber’s terminal)
• Supervision (Loop signaling)
• Coding/Decoding (PCM)
• Hybrid (2- to 4-wire conversion)
• Test (provide a test access to subscriber’s line and line circuit).

BRA
Basic Rate Access

Bridge
A network layer device that passes packets between two or more network segments that
use the same data link communications protocol (OSI layer 2). The network segments
appear as one segment to protocol levels higher than the data link layer.

Bridging
Port and subscriber line are connected during a test session.

Broadband subsystem
That part of the AnyMedia ® Access System which supports ATM xDSL services.

BVPT
Bearer Virtual Path Termination

Byte integrity
The assurance, that the digital information contained in n 64 kbps timeslots arrives at
the output in the same order as it was introduced at the input.
....................................................................................................................................................................................................................................

C C-message filter
The C-message filter for noise measurements greatly attenuates low frequencies such as
60 Hz and its harmonics as well as frequencies above 3200 Hz. From 600 to 3000 Hz it
is relatively flat and therefore very useful in measuring the noise that will affect voice
band frequencies most.

C-message notch filter

The C-message notch filter is the same as the C-message filter with a notch at 1004 Hz.
This notch filters the 1004 Hz holding tone inserted by additional test equipment at the
far end of the subscriber line.

CAC
Connection Admission Control

Call processing
Summarizes all actions to establish a transmission path for telephony between the
subscriber and the LE. This includes the transfer of signaling information too. In
addition to call build-up, all functions for tearing down a call are also included.

CARES
Customer Assistance Requests Entry System

CASTL
Customer Advocate System Test Lab

CBR
Constant Bit Rate

CC
Communication Channel

CCN
Customer Change Notice

CDP
Clock Distribution Panel

CDV
Cell Delay Variation

CDVT
Cell Delay Variation Tolerance

CE
Communauté Européenne

Cell
A fixed-length 53-octet packet used in ATM. The ATM cell has a 5-octet header and a
48-octet payload.

Cell delay variation (CDV)

The amount of difference between a cell’s expected arrival time and its actual arrival
time. Also called ″jitter″

Cell delay variation tolerance (CDVT)

A parameter which, in CBR transmissions, determines the level of jitter (i.e., cell delay
variation). The upper bound on the jitter measurement is the CDVT.

Cell Delineation
The cell delineation function permits the identification of cell boundaries in the payload.
It uses the HEC field in the cell header of ADSL frames.

Cell header
A 5-octet header that defines control information used in processing, multiplexing, and
switching cells.

Cell loss priority (CLP)

A field in the ATM cell header showing two levels of priority for ATM cells. CLP=0
cells are a higher priority than CLP=1 cells and may be discarded if there is a
congestion to preserve the cell loss ratio of CLP=0 cells.

Cell loss ratio (CLR)

The value the network agrees to offer as an objective over the lifetime of the
connection. This value is specified per service class at the turn-up.

Cell transfer delay (CTD)

The transit delay of an ATM cell successfully passed between two designated boundaries
on the AnyMedia Access System, when the system is loaded conservatively.

Cells received
The total number of cells that the AnyMedia ® Access System received from the CPE.

Centralized powering
The AnyMedia ® Access System is powered by a central DC power plant. This power
plant normally feeds other telecommunication equipment as well.

CES
Circuit emulation service - An ATM configuration that allows the ATM network to act as
a transparent transport pipe for constant bit-rate circuits.

Circuit
See port.

Circuit pack
A general term for any plug-in unit that is determined to be inserted into the slot of a
shelf, regardless of the slot size (1N-sized or 3N-sized) and the functionality. Common
packs and application packs are subsets of circuit packs.

Circuit testing
Verifies the ability of an AP port to provide proper transmission and signaling. The
actual circuit tests needed depend on the particular service being provided; that is,
POTS, and ISDN need different circuit tests. In the AnyMedia ® Access System only the
self-test capability of the AP is used. (See also drop testing.)

CIT
Craft Interface Terminal - The Craft Interface Terminal is used to enter and receive TL1
(Transaction Language 1) messages. A CIT emulation is running on the GSI.

CIT interface
Interface for the Craft Interface Terminal - A serial EIA-232C interface (9-pin Dsub) on
the faceplate of the communication interface unit (CIU) where a craft interface terminal
(CIT) or a graphical system interface (GSI) is connected to the AnyMedia ® Access
System.

CIU
Communication interface unit - This is a pack used to provide several OAM&P interface
terminations to the AnyMedia ® Access System.

CL
Clear Condition

CL channel
Used to transfer information concerning operation, maintenance and
activation/deactivation of the access transmission system (ATS) in both directions
between the LT and the NT.

CLEI
Common Language Equipment Identifier

CLEI
Common language equipment ID code - The CLEI is a 10-character code assigned by
Bellcore identifying each pack. The CLEI information relates to the function of the pack,
the condition of use, the source document used in creating the CLEI code etc. If two
packs have the same first seven characters in the CLEI code, then the packs are
electrically and mechanically interchangeable. Knowledge of CLEI is useful in planning,
engineering and provisioning.

CLIP
Calling line identification presentation - A supplementary service which provides the
called party with the possibility of receiving identification of the calling party.

CLP
Cell Loss Priority

CLR
Cell Loss Ratio

CN
Change Notification

CO
Central Office

Coding violation (CV)

A coding violation is observed when a CRC violation occurs in an ADSL superframe.

Cold start
Recovery of the AFM due to a soft reset or a SW upgrade with database evolution is
called ″warm start″. For all other types of AFM recovery ″cold start″ applies. In both
cases the user will be informed by a status condition report.
...................................................................................................................................................................................................................................
GL-14 363-211-586
Issue 6, July 2007
Glossary

Collocation
Grouping entities in the same physical location.

COM501

Comcode
The comcode is a unique nine-digit code with the ECI being represented by the digits 2
through 7. The comcode is used by various Alcatel-Lucent organizations for the ordering
of components.

COMDAC
Common data and control - Pack which provides the central control and transmission
fabric for the AnyMedia ® Access System. The COMDAC supports multiple system
applications, including V5.x switched services and analog and digital leased lines (ALL
and DLL) and a variety of application packs.

Command/Indication
An interface to control the ISDN echo cancellation circuit. In downstream direction
commands can be issued, in upstream direction indications are received.

Common control protocol

This protocol provides the necessary procedures for:
• Coordinated re-provisioning
• Checks of identification parameters, commonly used with the LE
• Coordinated restart of the PSTN FSMs.

Common pack
A circuit pack providing system functionality that is not limited to a specific application
like POTS or ADSL. All circuit packs that are not defined as application packs, are
common packs. Some examples for common packs are COMDAC, CIU, AFM, RGUs.

Communication channel
A group of one or more communication paths, all of different types. A communication
channel is associated to a 64-kbps timeslot on a V5.x interface. This association may be
changed by a protection switch (only V5.2).

Communication path
A communication path carries any one of the following information types:
• layer 2 data links carrying the control protocol, link control protocol, PSTN protocol,
protection protocol and BCC protocol,
• all the ISDN Ds-type data (ISDND) (signaling), ISDN p-type data (ISDNP) and ISDN
f-type data (ISDNF) from one or more user ports.
It should be noted that this definition includes the possibility that there is more than one
communication path of the same information type, each allocated to a different logical
communication channel.

Component
See device.

Concentration ratio
The ratio between the number of required 64-kbps channels for ISDN and POTS
subscribers and the available number of bearer channels.

Configuration management
Consists of a set of functions to exercise control over elements in the network, including
initialization, parameter setting, starting and stopping, and collection of information
about the configuration.

Connection admission control (CAC)

CAC is a set of actions taken by the network during the call set-up phase to determine
whether a connection request can be accepted, should be rejected, or may be re-allocated
based on QoS definitions.

Constant Bit Rate service (CBR)

A type of telecommunication service characterized by a service bit rate specified by a
constant value.

Controlling entity
A controlling entity has a control relationship to another entity where the operational
condition of the other (controlled) entity depends on the operational condition of the
entity concerned.

COSET
The header error co-setting (55 hex by ATM standards) is used to maintain a value other
than zero in the header error code (HEC) field. If the first four bytes in the header are
zero, the HEC derived from these bytes is also zero. When this occurs and there are a
string of zeros in the data, the receiver cannot determine the cell boundaries. Therefore,
it is recommended that the value 55 hex be added to the HEC before transmission.

Coverage factor c
The coverage factor c is the probability that a protection switch successfully restores
service.

Coverage factor d
The coverage factor d is the probability that a failure in the standby unit is detected.

CPE
Customer premises equipment - CPE covers the subscriber’s installation and the
subscriber’s terminal.

CPS
Cabinet Power System

CR
Critical

CRC
Cyclic Redundancy Check

CRC-4 multiframe
Cyclic redundancy check-4 multiframe - The CRC-4 multiframe is composed of 16
alternating basic frames numbered 0 to 15. It is divided into two eight-frame
sub-multiframes (SMF), designated SMF I and SMF II, which signifies their respective
order of occurrence within the CRC-4 multiframe structure. The SMF is the CRC-4
block size (that is 8 frames x 256 bits/frame = 2048 bits).

CRC-4 procedure
Cyclic redundancy check-4 procedure - A multiplication/division process, specified in
ITU-T G.704, to provide additional protection against simulation of the frame alignment
signal and capability for enhanced error monitoring.

Cross-connection
A term for a logical association between two objects, for example between a subscriber
port and a network interface. A physical cross-connection may additionally be
established in the case of a network interface where bandwidth allocation is done on a
provisioning basis (V5.1). In the case of V5.2 the bearer channel allocation is done on a
per-call basis by the BCC protocol.

Cross-connection object
A provisioning object which reflects a logical association necessary for establishing a
cross-connection.

CSA
Carrier Serving Area

CTD
Cell Transfer Delay

CTS
Clear To Send

Customer key code

The provisionable customer key code defines which customer specific settings are used
by the AnyMedia ® Access System.

Customer- specific settings

These parameters are only valid for specific configurations for one customer (for
example line termination impedances, signaling timings etc.).

Customer-specific
Reflects the particular configuration needs of a customer. Customer-specific
configuration of the system is achieved by constant data which is part of the code. For
example customer-specific application pack data or PSTN protocol data belong to this
kind of configuration data. Colloquially customer-specific is sometimes called
country-specific.

CVC
Control Virtual Channel

CVP
Control Virtual Path

CVPT
Control Virtual Path Termination

D D filter
A filter according to IEEE 743-1995 consisting of a high pass filter of 300 Hz and a low
pass filter of 3400 Hz with an attenuation of 3 dB.

D-channel
The ISDN out-of-band (16 kbps in BRA) signaling channel that carries the ISDN user
signals or can be used to carry packet-mode data.

DACS
Digital Access Cross Connect System

Data communications (or circuit termination) equipment (DCE)

A modem or network communications interface device.

Data Service
It is a broadband service which AnyMedia ® Access System supports by ATM transport
and switching (PVCs) only. It’s used for example for internet access via IP over ATM.
The data service’s protocols are terminated outside the AnyMedia ® Access System and
therefore the system is transparent to these services.

Data terminal equipment (DTE)

Data processing equipment that interfaces to the communications network (DCE).

Database evolution
When AFM software is upgraded to provide new features, it is usually necessary to
adapt or extend the database structure to accommodate these features. This is done
automatically as part of software activation and is termed database evolution.

Database transformation
The transformation of database entries from one database structure to another. The aim
of the transformation of database entries between different database structures is to
completely retain a site-specific configuration when upgrading a system.

DBSF
Double Board Single Fiber

DC
Direct Current

DCC
Data Communications Channel

DCE
Data Communications Equipment

DCN
Data Communications Network

DDF
Digital Distribution Frame

Default configuration
The configuration that is achieved by initially programming the COMDAC’s nonvolatile
data storage (NVDS). With a ″default configuration″ the system should be able to
recover with default values in the system database.

Defaults
Defaults are the parameter values built into the AnyMedia ® Access System when it is
shipped from the factory. The sum of all defaults forms the default configuration.
(Default values are restored upon execution of an Initialize-System command.) For TL1
commands there are defined defaults for parameter values used for parameters not given
in the command line.

Defect
A defect is a limited interruption in the ability of an item to perform a required function.
It may or may not lead to maintenance action depending on the results of additional
analysis. The system ’detects’ a defect. This definition applies to the ADSL performance
management parameter Loss of Cell Delineation.

Degrowth
The removal of circuit packs or traffic from a system via a provisioning operation (may
be accompanied by the physical removal of associated equipment, but this is not
required).

DELT
Dual-ended loop test

Design life
The design life is the length of time that a maintained system is expected to operate
with a declining or constant failure rate.

Device
Any electrical part (IC, diode, capacitor, resistor, etc.) with distinct electrical
characteristics. This term is used interchangeably with component.

Diagnosis
The pack diagnosis includes the sanity check performed autonomously by the pack and
the built-in self test (BIST).

Digital local line

A metallic local line that is able to simultaneously carry bidirectional digital
transmission providing ISDN BRA subscribers and leased lines subscribers, between LT
and NT1/NTU.

Digital transmission system

The concept used to describe the characteristics of an implementation, using a specific
medium, in support of the access digital section.

Disable information
Disable information is sent by the lines layer. The information is relevant for HDSL
payload timeslots and POTS, ISDN and HDSL ports.

Discarded Cells
Cells that are dropped to avoid exceeding a particular connection’s traffic contract.

Distance-to-open
For deciding whether a line is broken (open), a distance-to-open measurement is to be
implemented. Such a measurement could be based upon several techniques: capacitance
or impedance measurement, or even pulse-reflection. TAP10x/LPZ200 may produce
parameters, with which the operator can decide on the location of the cable-fault (based
on the operator’s knowledge of the applied cable type).

DLL
Digital leased line - Used for point to point connections. The DLL bypasses the LE. The
transmission rate of DLL is n × 64 kbps (n=1,2) using U interface as transmission
medium.

DMT
Discrete Multi-tone

DOTS
Digital office timing supply

Double board single fiber (DBSF) protection mode

A protection mode which can be used for optical AFMs (AFMOs). This protection mode
provides pack protection and feeder facility protection for the feeder section between the
AFMO and an external optical coupler. The optical coupler is splitting the received
signal to two physical feeders and in transmit direction it is combing the two transmit
signals to one.

Download
A binary data transfer from the GSI to the AnyMedia ® Access System.

Download a load image

Refers to transferring software (load image) via the GSI or the EMS.

Downloadable pack
Any peripheral pack which is designed for download of the peripheral SW image. For
example peripheral SW download via COMDAC.

Downstream
The bitstream direction from the network towards the NT or the customer.

Downstream direction
Transmission direction from ATM data network or telephony switch to customer.

Downstream VP
In a daisy chain, a VP that terminates on a shelf that is farther away from the ATM
transport network than the shelf being addressed. ″Downstream″ here does not refer to
the direction of transmission.

Downtime
Used to describe the time during which a system is not available for service. In
engineering applications downtime is associated with unavailability.

Downtime per port

Downtime, in minutes per year, for a single bidirectional path terminating on an
interface port on an add/drop multiplexer or a digital cross connect system. Any service
interruption longer than 50 milliseconds contributes to this measure.

Drop
See subscriber loop.

Drop testing
Checks for opens, shorts, leakages to ground, foreign voltages, or other faults on the
subscriber loop.

Dropped cells
The number of cells that are dropped as a result of exceeding either a particular
connection’s traffic contract or the total allowable bandwidth of the system.

DS3 cabling

DSL
Digital subscriber line - Provides full duplex service on one or two metallic pairs at bit
rates which are capable of supporting ISDN BRA, ISDN PRA, DLL or n × 64 kbps
digital leased lines and additional framing, timing recovery and operations and
maintenance functions.

DTE
Data Terminal Equipment

DTP500
Communication interface unit (CIU)

Duplex 1+1 protection mode

A protection mode which can be used for optical AFMs (AFMOs). This protection mode
provides pack protection as well as feeder facility protection, i.e., both, the feeder and
the AFMO are doubled. For SDH it applies to unidirectional 1+1 linear Multiplex
Section Protection (MSP) per ITU-T G.841, for SONET it applies to unidirectional 1+1
line protection per Telcordia, GR-253.

Duplex mode
A facility protection scheme in which two identical facilities (packs or feeders) are
installed on a shelf; one is running in the active mode, the other is in the standby mode.
The standby facility takes over when the active one fails or on an external command.
Such a take-over (″protection switch″) guarantees that a facility failure does not disrupt

the services.

Dying gasp
A message the CPE transmits to the ADSL AP when its electrical power is being shut
off. The message indicates to a service technician or an administrator that an interruption
on an ADSL line was caused by a power interruption at the CPE and not caused by a
transmission failure or an AnyMedia ® Access System failure.
....................................................................................................................................................................................................................................

E E1
E1 is the standard acronym for the 2.048-Mbps interface defined in the ITU standards
G.703/G.704.

E1 link
Link between the AnyMedia ® Access System and a service node.

E3 cabling

Early Packet Discard (EPD)

The EPD function ensures that the ATM equipment discards entire AAL5 packets during
periods of congestion. This is especially important when a relatively large number of
Transmission Control Protocol (TCP) sources contend for particular bottleneck.

EB
Errored Block

ECI
Equipment catalog item - Equipment catalog item code is a 6-character code assigned by
Bellcore identifying each pack. This code corresponds to the bar-coded label on the
faceplate of the pack, and is uniquely equivalent to the CLEI code - for a given CLEI
there is a unique ECI. It is used internally in the databases of external inventory systems
for cataloging of equipment and is useful in accounting and inventory control.

ECM
External condition mismatch (a secondary service state) - Connected subscriber
equipment, for example the HDSL NTU does not match the provisioning of the
AnyMedia ® Access System.

EFaddr
Envelope function address - An EFaddr is an address used in the LAPV5-EF frame to
identify different V5-enveloping function sublayer connections, each of them used to
support a relaying mechanism for the LAPD/LAPF frames of each of the ISDN user port
or messages corresponding to the V5.x-layer 3 protocols (for example PSTN protocol,
control protocol). It is present in every LAPV5-EF frame and its purpose is to provide a
common envelope in frames in which either the LAPV5-EF information field is
terminated by the AnyMedia ® Access System (for example LAPV5-DL frames used by
the PSTN protocol and control protocol) or those where the payload is terminated
outside the AnyMedia ® Access System (ISDN LAPD/LAPF frames from the ISDN user
ports).

Effective bandwidth
A measure of the amount of bandwidth a connection uses. It is PCR for CBR
connections. It is a function of PCR, SCR, MBS and CLR for VBR connections. This
measure for VBR connections is defined differently for different congestion points on
the same connection. The CAC algorithm uses this measure at potential congestion
points when determining whether to admit a new connection.

EIA-232C
American Standard for Serial Interface (the same as EIA-RS-232C; similar to V.24)

EIDR
Enhanced inventory data record - Enhanced inventory data record is a set of parameters
that are stored in the non-volatile memory of packs. The parameters relate to the
function performed by the pack, the manufacturing information, ordering information etc.
that is of importance in provisioning a new service, maintaining the service, and in
restoring the service quickly in event of a failure.

EMC
Electromagnetic Compatibility

EMS
Element Management System (SW)

Enable information
Enable information is sent by the lines layer. The information is relevant for HDSL
payload timeslots and POTS, ISDN and HDSL ports.

End of life
The instant when a device parameter reaches a specified failure threshold. The failure
threshold is device-dependent. For instance, an aluminum electrolytic capacitor reaches
its end of life when its equivalent series resistance (ESR) exceeds twice its initial value.

Engineering work order

In order to build up a system on site or to grow or degrow a running system, an
engineering work order is necessary. By means of this order, the installation group can
plan and carry out the construction. The engineering work order is made out of the site
survey with the installation group and agreement to the customer. The engineering work
order contains for example floor plan data sheet, application schematic, interconnections.

Entity
The term entity or object represents an entry in a TL1 administrative view, that is an
entity (or object) may be entered, changed, deleted or retrieved by a TL1 command.

Envelope function address

Used for addressing the different ISDN user ports within the V5.x protocols (for
example BCC, Control Protocol etc.).

EOC
Embedded operations channel - Twenty four bits of the maintenance channel frame of
the U interface (see maintenance channel).

EPD
See early packet discard

Equipment layer
Represents in the layered structure of the AnyMedia ® Access System services the layer
for a port. It reflects the physical status of a port. A port can be for example an
HDSL port, a U port, a Z port or an E1 port.

Equipment pair
The equipment pair of the TAP-B interface consists of the 2 wires towards the customer
premises equipment (outward direction).

Error correction (EC)

An error correction is observed whenever the FEC algorithm indicates that at least one
bit error has been corrected in an ADSL superframe.

Errored cells
Cells received with an invalid header field after HEC procedures are completed.

Errored cells received

The number of cells that the system received from the CPE with detected errors.

ES
Errored Seconds

ESF
Extended Superframe

ETR
ETSI Technical Report

ETS
European Telecommunication Standard

ETSI
European Telecommunication Standards Institute

External interface
Any operations or user interface system connected locally or remotely to the AnyMedia ®
Access System. For example: CIT, GSI, EMS.
....................................................................................................................................................................................................................................

F FAC500/FAC500B
Quad E1 Interface pack (IO_E1)

Facility pair
The facility pair of the TAP-B interface consists of the 2 wires towards the application
pack circuitry (inward direction).

Facility protection
The capability for a system to choose which signal from two facilities to pass along to
the internal, unprotected transmission paths. A system switches from one facility to the
...................................................................................................................................................................................................................................
GL-24 363-211-586
Issue 6, July 2007
Glossary

other, for example, when the facility being used fails or when an administrator issues an
OAM&P command.

Failure
A condition in which the system is not performing its intended function, either in part or
in whole.

Fall back
The act of switching over from the active image to the backup image on a peripheral
pack.

Far end
The transmission termination or network element terminating the remote end of a feeder
connected to the system. Examples include the edge switch and another AnyMedia shelf
within a daisy chain. The far end is also referred to as remote end.

FAS
Frame alignment signal - The distinctive signal inserted in every frame or once in every
n frames on an E1 link, always occupying the same relative position within the frame,
and used to establish and maintain frame alignment.

Fault isolation
The task of identifying and isolating a faulty unit so that other operational units are not
affected and the faulty unit can be replaced without service interruption for the other
units not concerned.

Fault isolation bus

The fault isolation bus allows the AFM in AnyMedia Mainshelf applications to
individually reset any ATM xDSL AP, and to retrieve status indications from the ATM
xDSL APs. The bus consists of a clock driven by the AFM and a bidirectional serial data
signal and is also called I2C Bus.

Fault management
Consists of a set of functions, such as testing, that enable the detection, isolation, and
correction of abnormal operation of the telecommunications network and its
environment.

FDI
Feeder Distribution Interface

FE
Far End

FEAC
Far End Alarm Code

Feature packaging
Customization mechanism where a subset of the overall set of software packages is
selected and incorporated in a load image to support a certain functionality (for example
POTS-only, ISDN-only, V5.2-only). Feature packaging allows to sell exclusively the
functionality requested by a customer as opposed to the complete functionality the

system can provide.

FEBE
Far end block errors - Bit errors in the downstream direction from the LTU to the NTU
in case of a 2B1Q U interface and in case of an HDSL interface. They are reported via
FEBE bit in the maintenance channel to the LTU.

FEF
Family of equipment failed (a secondary service state) - A whole group is not accessible.

FEF
Family of Equipment Failed

FFCU
Fan Filter and Clock Unit

FFU
Fan Filter Unit

FIT
Failures in time - A unit of failure rate used in reliability analysis. One FIT is equivalent
to one failure per 10 +9 operating hours.

FITL
Fiber In The Loop

Flag monitoring
The flag monitoring function requires that flags, sent on V5 communication channels
towards the ANE by the LE, must be monitored in the ANE. Flag monitoring is
mandatory for V5.2 interfaces and optional for V5.1 interfaces; flag sending is
mandatory in any case for both directions, that is ANE to LE and LE to ANE.

FLT
Fault (a secondary service state) - Hardware fault detected, for example a circuit pack
has a fault condition.

FLT
Fault

FMECA
Failure modes, effects and critically analysis - identifies potential design weaknesses
(silent failures, unprotected failures, etc.) through a systematic documentation of all
likely ways in which a component can fail, causes of failure, and the effects of each
failure.

Forced mode
Refers to the mode of changing to administrative primary service state OOS. In forced
mode the resources are freed immediately and the administrative primary service state
OOS is entered.

Forward direction
The direction followed by monitored user cells. Unlike the definition of upstream and
downstream direction, the forward and backward directions are relative to a reference
point (e.g., the point where a failure occurs).

FPGA
Field programmable gate array - A hardware device which is (re)programmable in the
field; for example hardware configuration may be changed by reprogramming this
device.

Frame
A cyclic set of consecutive timeslots in which the relative position of each timeslot can
be identified.

Frame relay function

The statistical multiplexing of frames, for example ISDN D-channel frames from an
access layer 2 into a V5-communication channel and demultiplexing for ISDN D-channel
frames received on a V5-communication channel.

Frame slot integrity

The assurance that multiple 64 kbps time slots contained in one 125 ms frame at the
input arrive in one 125 ms frame at the output.

Framed path termination group

A framed path termination group is a collection of four framed path terminations based
on the hardware architecture. The hardware architecture allows only either the mutually
exclusive connection of such a group of framed path terminations to the timeslot
interchange or the connection of a (related) IO slot to the timeslot interchange.

FTP
File Transfer Protocol

FU
Fan Unit

Full split
With full-split test access, transmission is interrupted in both the transmit and receive
directions at the test access point and the tester is allowed to inject and look at the
transmitted and received signals both in the equipment (towards the end-customer) and
in the facility (towards the network) directions simultaneously.

Full-rate ADSL (Classic)

The version of asymmetric digital subscriber line (ADSL) defined by ANSI T1.413.

Function code
Function code (sometimes called entity type) is the ’pet name’ of a pack. It is a set of
11 characters stored in the nonvolatile data storage (NVDS) of a pack that identifies a
pack, backplane, or a software package (for example COMDAC, CIU,...).

FW
Firmware

G G.Lite
G.Lite is a special type of ADSL line where no splitters are used. In comparison to
ADSL it provides a reduced transmission rate.

GA
General Availability

GCRA
Generic Cell Rate Algorithm

General settings
These are parameters which are valid for all customer-specific configurations (for
example loop-start function for all Z ports which are assigned for POTS service or
suppression of out-band signalings for Z ports which are assigned for ALL
(transmission-only) service).

General user
User login allows access to all TL1 commands except those for security management
that affect other users such as login creation and deletion, and password modification for
all user classes.

Generic cell rate algorithm (GCRA)

For each cell arrival the GCRA determines whether the cell conforms to the traffic
contract of the connection. The GCRA is defined with two parameters: the increment (I)
and the limit (L).

GLL
n × 64 kbps leased lines service via G.703 interface

GLL service
An n × 64 kbps digital leased line service via G.703 interface (n=1, ..., 31). This
interface is provided by means of an NTU which is the far end equipment of an HDSL
link.

Global ATM parameters

Includes the AnyMedia Mainshelf VPI and the ATM operations channel VPI and VCI
(also known as ATM permanent virtual connection [PVC] for OAM&P purposes).

GND
Ground - Synonym for electrical potential of 0V.

GNE
Gateway Network Element

GPB
General purpose bus - The general purpose bus is an AnyMedia ® Access System internal
12-wire connection between any of the APs in the AnyMedia Mainshelf and the CIU.
Each AP can connect any of its circuits to the GPB via relays. The GPB is situated on
the backplane of the AnyMedia Mainshelf.

GPB
General Purpose Bus

GSI
Graphical System Interface

GSI
Graphical System Interface - A user friendly front-end for communicating with a system.
In the AnyMedia ® Access System the GSI is installed on a Windows based Personal
Computer and used for entering and receiving TL1 (Transaction Language 1) messages
for narrowband applications and SNMP messages for ATM xDSL applications. The GSI
provides support for managing the AnyMedia ® Access System in the following functional
areas:
• Configuration management
• Fault management
• Performance management
• Security management
• Inventory management.

Guaranteed Bandwidth
The portion of the feeder throughput (feeder bandwidth) made available to a service
category to be used during periods of sustained congestion. Guaranteed bandwidth is
explicitly specified for CBR, rt-VBR, and nrt-VBR by means of provisioning the weights
for the Weighted Round Robin (WRR) Scheduler. The sum of all guaranteed bandwidths
may not exceed the feeder bandwidth.
....................................................................................................................................................................................................................................

H Half split
With half-split test access, transmission is interrupted in both the transmit and receive
directions at the test access point, exactly as in full-split access. However, the tester is
allowed to inject and look at the transmitted and received signals either in the equipment
(towards the end-customer) direction or in the facility (towards the network) direction,
but not in both directions simultaneously.

HBER
High bit error rate - A U interface, E1 interface, HDSL interface or 2 Mbps payload
failure. The bit error ratio for a certain amount of time is greater than 10 -3. HBER is
sometimes also called excessive bit error ratio.

HDB3
High Density Bipolar of Order 3 Code

HDLC
High Level Data Link Control

HDLC D16 termination position

High level data link control termination position - Gives the position of a D16 HDLC
termination within a HDLC termination block. It corresponds to the quarter timeslot #
used on ISDN APs which are multiplexed on D-channel packer into one 64 kbps
...................................................................................................................................................................................................................................
363-211-586 GL-29
Issue 6, July 2007
Glossary

timeslot. It’s range is 1 to 4.

HDLC termination block

High level data link control termination block - A term used for specifying configuration
capabilities of HDLC terminations. It provides one or more HDLC terminations. It’s
bandwidth is 64 kbps and it either can be configured as one D64 HDLC termination or
four D16 HDLC terminations.

HDSL
High-Bit-Rate Digital Subscriber Line

HDSL AP
High bit rate digital subscriber line application pack - An application pack containing
HDSL ports that provide service to ISDN PRA subscribers and n × 64 kbps digital
leased lines subscribers.

HDSL application mode

High bit rate digital subscriber line application mode - The mode in which an HDSL
module operates. The application mode defines how data is handled and transported by
the HDSL interface. The provisionable application modes supported by an HDSL AP are:
• Single pair mode (SP): Only one HDSL port (pair) is used. 16 HDSL logical timeslots are
provided including timeslot 16. Only one NTU is connected. HDSL logical timeslots 1 to
16 are mapped as provisioned one by one to the user timeslots 1 to 16 at the NTU.
• Point-to-point mode (PP): Two HDSL ports (pairs) are used in parallel. 31 HDSL logical
timeslots are provided including timeslot 16, but timeslot 16 normally is reserved for use
by G.703 (PRA or leased lines) services. Only when more than 30 timeslots are
provisioned, HDSL logical timeslot 16 can also be used by other services, for example
V.35. Only one NTU is connected. HDSL logical timeslots 1 to 31 are mapped as
provisioned one by one to the user timeslots 1 to 31 at the NTU.
• V3 point-to-point mode (V3PP): Two HDSL ports (pairs) are used in parallel. 32 logical
timeslots are provided including timeslots 0 and 16. All 32 timeslots are used for V3 ISDN
PRA service. One NTU is connected to the HDSL AP, which provides the interface for
connecting an ISDN PRA subscriber (PABX).
• Point-to-multipoint mode (PM): Two HDSL ports (pairs) are used, but are connected to
two different NTUs. 32 HDSL logical timeslots are provided, but only 2x15 bearer
channels are available. HDSL logical timeslots 1 to 15 are mapped as provisioned one by
one to the user timeslots 1 to 15 at the first NTU. HDSL logical timeslots 17 to 31 are
mapped as provisioned one by one to the user timeslots 17 to 31 at the second NTU.
HDSL logical timeslots 1 to 15 correspond to HDSL pair 1 and HDSL logical timeslots 17
to 31 to HDSL pair 2.
• Unstructured point-to-point mode (UPP): Two HDSL ports (pairs) are used in parallel to
provide an unstructured E1 service via the IO_E1 pack. All 32 timeslots are used. Only
one NTU is connected.

The provisionable application modes supported by an SHDSL AP are:

• Point-to-point single pair mode (PPS): In this mode, the SHDSL port operates in structured
mode. 32 logical timeslots are available including timeslot 0 and 16. The timeslot 16 is
allocated only for G.703 (PRA or leased line) or 31×64 kbps leased line services.
• V3 point-to-point single pair mode (V3PPS): In this mode, the SHDSL port operates in
structured mode. 32 logical timeslots are available including timeslot 0 and 16. All 32
timeslots are used for V3 ISDN PRA service.
• Multi-rate single pair mode (MRS): This mode enables greater transmission distance at the
expense of maximum subscriber data rate (3×64 kbps to 31×64 kbps). The number of
multi-rate timeslots ″N″, is specified in the ENT-HDSL TL1 command and the SHDSL
logical interface creates N + 1 logical timeslots ranging from 0 to N. There are N payload
timeslots available on the SHDSL link to carry user data. V.35, V.36, X.21 and G.703
leased line services are supported in this mode. There is no support for multiple services.
• Unstructured point-to-point single pair mode (UPPS): In this mode the SHDSL AP is used
to provide an unstructured 2Mbps service via the AP_E1 port or the IO_E1 port. All 32
timeslots are used.

HDSL drop
High bit rate digital subscriber line drop - HDSL drop is the physical line. It is also
used as AID to identify an HDSL port and the location of loopbacks or line tests.

HDSL interface
High bit rate digital subscriber line interface - Includes all functions to realize HDSL
transmission. This includes the HDSL transceivers and the digital subscriber line (DSL).
The 2 Mbps payload is transmitted within the HDSL frames. HDSL interface failures are
LOF, HBER and LBER.

HDSL link
High bit rate digital subscriber line link - Connection between an HDSL module (LTU)
and a network termination unit (NTU). Only one HDSL link between an HDSL module
and a certain NTU is possible. According to this definition the following statements
apply:
• In single pair mode only one HDSL link exists
• In point-to-point mode only one HDSL link exists
• In point-to-multipoint mode two HDSL links exist.
See also HDSL application mode.

HDSL logical interface

High bit rate digital subscriber line logical interface - The provisioning entity providing
the logical view of an HDSL module. See also HDSL application mode.

HDSL logical timeslots

High bit rate digital subscriber line logical timeslots - The logical resources an HDSL
module provides. The transmission rate of such an HDSL logical timeslot is 64 kbps.
Note that this is only a logical view of resources. It neither reflects the user timeslots
for example bearer channels of an ISDN PRA) nor the timeslots used in the internal
HDSL frame. The latter ones are hidden to the operator. HDSL logical timeslots are
visible at the LINES-layer.
...................................................................................................................................................................................................................................
363-211-586 GL-31
Issue 6, July 2007
Glossary

HDSL module
High bit rate digital subscriber line module - Provides the HDSL transmission system
and consists of up to two HDSL ports. Depending on the number of HDSL ports used it
provides 17 or 32 HDSL logical timeslots. It’s properties depend on the provisioned
HDSL application mode. The provisioning entity corresponding to the HDSL module is
called HDSL logical interface. The term HDSL module is a term used by the current
supplier of HDSL technology.

HDSL overhead bits

High bit rate digital subscriber line overhead bits - The HDSL overhead bits (HOH) are
embedded in the HDSL frame, which is 6ms long. Besides the synchron word, eoc-,
frame and stuffing bits are included.

HDSL pair
High bit rate digital subscriber line pair - The copper pair connected to an HDSL port. It
provides duplex transmission on 2-wire metallic local lines with a transmission rate of
1168 kbps.

HDSL payload timeslots

High bit rate digital subscriber line payload timeslots - Physical resources provided by
an HDSL interface. The transmission rate of an HDSL payload timeslot is 64 kbps. The
HDSL payload timeslots are assigned to HDSL logical timeslots, when the operator
provisions an ISDN PRA or n × 64 kbps digital leased line subscriber.

HDSL port
High bit rate digital subscriber line port - Refers to the devices and functions built on or
provided by an HDSL AP to support HDSL transmission. Each HDSL port refers to one
HDSL pair. Two HDSL ports are mounted on one HDSL interface to enable a
transmission rate of 2×1168 kbps.

Header Error Control interleaved (HEC) anomaly

An HEC anomaly occurs when an ATM cell header error check fails on the interleaved
or fast data.

HEC
Header Error Control

HEC anomaly
A Header Error Control (HEC) anomaly occurs when an ATM cell header error check
fails. HEC anomalies are reported once per ADSL superframe.

High BER on upstream SDSL line

The SDSL signal received from the CPE is considered to be in a high-BER condition
when ten consecutive SESs have occurred. The high-BER condition is cleared when ten
consecutive seconds have occurred that are not SESs. The system tracks SESs for the
SDSL signal received from the CPE. An SES for upstream SDSL transmission is
observed when either of the following conditions exists during a given clock second:
- If the number of HEC errors (corrected and uncorrected) divided by the number of
cells received is greater than or equal to 0.3, then SES occurs.
- If at least one los or lof occurs, then SES occurs.
If an auto change in bit rate occurs, start over in both cases.
...................................................................................................................................................................................................................................
GL-32 363-211-586
Issue 6, July 2007
Glossary

High bit rate digital subscriber line (HDSL)

A method of transmitting T1 over twisted-pair copper lines. Unlike other DSL types,
HDSL uses four wires (two pairs). HDSL supports 1.544 Mbps full-duplex transmission.

High-impedance state
This state refers to the Z interface and implies that the physical Z port circuit is
disabled. Consequently no feeding current can flow from the Z interface to the
subscriber’s terminal, no loop scanning will be performed and no AC signal transmission
is possible.

Hold-up time
The time during which a power supplies output voltage remains within specification
following the loss of input power.

Hook flash
Hook flash is a signal of POTS. A hook flash signal is a short interruption of
subscriber’s loop, which is generated at subscriber’s terminal. Hook flash signals are
used to request additional service features (for example establishing a three party
telephone conference).

HW
Hardware
....................................................................................................................................................................................................................................

I ICC
Interchangeability code - The ICC is of the form Sm:n, where ″m″ is the issue number
and ″n″ is the series number. This is used to accurately indicate the interchangeability
among packs with the same pack name and apparatus code, but different manufacturing
versions. In general, a pack can be replaced by another pack that has the same apparatus
code and the same issue number regardless of the series number. Because Transaction
Language 1 (TL1) uses the ″:″ as a delimiter, for inventory retrieval using TL1 the ″:″ is
replaced with a ″-″. For example, an ICC will appear as S1:1 on a pack and will appear
as S1-1 when retrieved using a TL1 command.

ICLE
Initial Customer Laboratory Evaluation

ID
Identification

ID return
The ID return is an autonomous UART message (AX_UPRESET) from AP to COMDAC
which is sent after a power-up condition or a HW-RESET. This message includes 4 data
bytes (pack class, pack subclass, number of circuits on AP and front cable presence
information).

IDC500/IDC500B
High Level data Link Control Pack (IO_HDLC)

IEEE
Institute of Electrical and Electronic Engineers
...................................................................................................................................................................................................................................
363-211-586 GL-33
Issue 6, July 2007
Glossary

IM
Installation Manual

IMA
Inverse Multiplexing for ATM

IMA group
An operational collection of IMA links that functions to multiplex and de-multiplex ATM
cells in a cyclical fashion among the links, to form a higher bandwidth logical path
between a pair of IMA terminals separated by multiple feeders. The AFME1 pack uses
one group and up to eight links, with a direct, one-to-one mapping between the links and
feeders.

IMA link
A circuit path within the AFME1 that connects its feeder interface with a circuit that
combines the link’s broadband payload (ATM cells) with the payload of other links, in
the downstream direction, and distributes the composite ATM payload cells among the
links in the upstream direction.

IMF
Infant mortality factor - Ratio of the expected number of failures in the first year of
service to the expected number of failures in a later, steady-state year. The system infant
mortality factor should be computed using methods consistent with the definition of the
first year multiplier given in TR-332.

In-band signaling
The transfer of signaling data inside the same frequency band with a defined bandwidth
as used for voice or voice grade data transmission. The bandwidth for analog subscriber
services is defined between 300 Hz and 3400 Hz.

INIT
Initialization (a secondary service state) - Initialization, for example during self-test of a
circuit pack after insertion.

INIT-SYS command
The INIT-SYS command is used to clear the database and to restore the AnyMedia ®
Access System to default values set at factory.

Initial ring
Initial ring is sent from LE to the AnyMedia ® Access System. It indicates, that LE wants
to transfer CLIP information in the a/b path to the CPE.

INP
Impulse noise protection - Mechanism to protect against interference from fans, engines
and similar disturbers of impulse noise.

Inrush current
Inrush current is the current flowing at the moment when the power is switched on.

Installation time
The period of time beginning when the transfer of software to the peripheral pack starts.
The interval ends at the point when the transfer of the peripheral image to the pack is
completed for both peripheral processors and field programmable gate array (FPGAs).
Peripheral SW version switch over is not included.

Interface Id
A unique number of a V5.x interface of an access network element (ANE) which is used
by the common control protocol.

Internal frame relaying

V5 frames carrying the Control-, Link control-, PSTN-, Protection- and BCC protocol
where layer 2 is terminated in the COMDAC are concentrated within a single physical
channel between the COMDAC and the IO_HDLC which is called the internal frame
relay channel.

Inventory
Inventory is the summary of data stored on a pack in the NVDS during manufacturing
which is used to identify the pack and its functionality.

Inventory management
Consists of a set of functions to track, report, and ensure adequate supplies of
equipment.

Inward direction
See facility pair.

IO_E1
Quad E1 Interface Pack

IO_E1
Quad E1 interface unit - A circuit pack which terminates four E1 signals.

IO_E1P
IO_E1 Protection Pack

IO_E1P
Quad E1 interface unit protection - An IO_E1 pack used as protection unit.

IO_HDLC
High level data link control pack - The pack which performs the frame relaying function
necessary for ISDN subscribers. Additionally internal frame relaying for V5 layer 3
messages is performed.

IP
Internet Protocol

IP-AFM
IP ATM feeder multiplexer

IPFM
IP feeder multiplexer
...................................................................................................................................................................................................................................
363-211-586 GL-35
Issue 6, July 2007
Glossary

IS
In Service

ISDN
Integrated Services Digital Network

ISDN AP
Integrated services digital network application pack - A pack containing 2B1Q or 4B3T
U ports (defined below) that provide service to ISDN BRA subscribers and leased lines
subscribers.

ISDN BRA
Integrated services digital network basic rate access - The requested bandwidth at the V5
network interface is two bearer channels plus a frame relay over a communication
channel for the 16-kbps signaling channel (that is a 2×64-kbps bearer channel connection
plus a 16-kbps D-channel). The following type of ISDN BRA subscriber is implemented
in the AnyMedia ® Access System:
• NT1 outside the AnyMedia ® Access System at the CPE.

ISDN BRA service

Integrated services digital network basic rate access service - Connects ISDN BRA
subscribers to the network via dial up connection.

ISDN BRA subscriber

Integrated services digital network basic rate access subscriber - Narrowband digital
subscriber.

ISDN dial up ROC

An ISDN dial-up ROC is a 64-kbps channel terminating within the COMDAC which
may be established by normal call build-up procedures (dialing) form outside the ANE.
This is achieved by realizing a virtual ISDN port which terminates layer 2 and layer 3
ISDN protocols within the COMDAC. For this reason an additional physical channel
between the COMDAC and the IO_HDLC is provided, where Ds-data frames for this
dedicated ISDN subscriber are transported in both directions. This channel is called ROC
support D-channel.

ISDN port
Integrated Services digital network port - The definition covers both ISDN BRA and
ISDN PRA ports.

ISDN PRA service

Integrated services digital network primary rate access service - Connects ISDN PRA
subscribers via V5.2 interface to the network. An ISDN PRA service may have up to 30
bearer channels and one 64 kbps D-channel.

ISDN PRA subscriber

Integrated services digital network primary rate access subscriber - An ISDN PRA
subscriber has the transmission capability of up to 30 B-channels (30×64 kbps) and one
D-channel (64 kbps) and is connected to a V5.2 interface.

ISDN user port

Integrated services digital network user port - Delivers digital telephony and data
services to an ISDN subscriber. It is addressed by a logical 13 bit address (envelope
function address) used in the relevant protocols on the V5.x interface. With respect of
V5.x interface the envelope function address uniquely identifies one ISDN user port.

ISP
Internet Service Provider

IT
IT is the synonym for a power distribution system having no direct connection to earth,
the exposed conductive parts of the electrical installation are connected to a local earth.

ITE
Intermediate transmission element - Transmission equipment which connects the DSL to
the NT or LT in order to extend the ISDN BRA or DLL services beyond the maximum
distance of the standard DSL. The ITE can be based on the scheme which converts the
information and signal carried over the DSL into a format that can be transmitted over
another transmission system (for example E1 facilities) and converts it back into the
DSL format at the remote location. The number of ITE between LT and NT is limited to
six.

ITU
International Telecommunication Union
....................................................................................................................................................................................................................................

J Jitter
Short-term noncumulative variations of the significant instants of a digital signal from
their ideal positions in time.The most significant form of jitter arises from imperfections
in the circuitry, for example quantizing distortions in phase locked loops (PLL).
....................................................................................................................................................................................................................................

L LAG
Line Access Gateway

LAN
Local Area Network

Latency
The minimum amount of time it takes for a token to circulate around the LAN token
ring or FDDI ring in the absence of a data transmission. Latency is selected when
provisioning data service in the AnyMedia ® Access System.

Layer 3 address
Used for addressing PSTN ports within the V5.x protocols.

LBER
Low bit error rate - A U interface, E1 interface, HDSL interface or 2 Mbps payload
failure. The bit error ratio for a certain amount of time is greater than 10 -6. If LBER
happens the upperlying service on this U interface or on this HDSL interface is

degraded.

LBO
Lightguide Build Out

LCD
Loss of Cell Delineation

LCS
Local Customer Support

LE
Local Exchange

LED
Light Emitting Diode

LFP
Logical Feeder Port

LIF
Link ID check failed (a secondary service state) - The defined V5 link IDs on
AnyMedia ® Access System side and on switch side are different.

Lightguide build out (LBO)

An attenuation network for optical signals between ATM circuit packs in an ATM switch
or multiplexer and the AFMOs in an AnyMedia Mainshelf, or between separate AFMOs
in multiple AnyMedia Mainshelves in a daisy chain. LBO guarantees the proper signal
level.

Line state
The current state of the U interface or of the HDSL interface.
The most important states of the U interface are the deactivated state, activated state
(U interface and S/T interface) and U interface activated only. Other states are
loopback 1 or LOF/LOS. The line state of the U interface depends on
• the progress of the activation/deactivation procedure
• the state of the LMAN
• loopbacks and tests
• the maintenance bits.
The most important states of the HDSL interface are inactive and active-Tx/Rx state.
Other states are loopback 1 or LOF. The line state of the HDSL interface depends on
• the progress of the HDSL start-up procedure
• the state of the LMAN
• loopbacks and tests
• the HDSL overhead bits.

Link
In the V5 context a 2.048-Mbps interface to the local exchange whose physical and
electrical characteristic comply with ITU recommendation G.703 and whose functional
characteristics are according to ITU G.704 and G.706.

Link control protocol

This protocol provides the necessary procedures for performing a coordinated LINK
management at both sides of the V5.2 interface. It provides the following mechanisms:
• Coordinated 2 Mbps links blocking: Required to perform link administrative operations in
both NEs (AN and LE) with a minor impact in the subscriber service, and also to assure a
synchronized link failure recovery in case of misalignment of the failure recovery
persistency detectors at both ends of the Network Interface.
• Coordinated 2Mbps links unblocking: Required to start, in an orderly way, the link
operation, after either an administrative operation or after recovery of a link failure.
• Coordinated Link identification and continuity verification: Required, for example, at
installation and after failure recovery to verify, by TS0 continuity check mechanisms, the
correct link interconnection.

LL
Leased line - A permanent established connection between a user port and a separate
permanent leased line service network. Leased lines bypass the LE.

LMAN
Line circuit metallic access network - Part of the line circuit on the ISDN AP and on the
HDSL AP. On the ISDN AP the LMAN connects or disconnects the a- and b-wire with
the line circuit or the line pack bus (LPB). On the HDSL AP the LMAN connects or
disconnects one HDSL pair with the line circuit or the line pack bus (LPB). Each U port
and each HDSL port include one LMAN.

LOA
Loss Of Alignment

Load
The total number of call attempts offered to a telecommunication system during a given
interval of time.

Load A
0.7 Erlang average occupancy on all V5.2 bearer channels; represents the normal upper
mean level of traffic load, as defined in ITU Recommendation Q.543.

Load B
1.2 * Load A = 0.84 Erlang average occupancy on all V5.2 bearer channels; represents
an increased level beyond the normal upper mean traffic load level as defined in ITU
Recommendation Q.543.

Load image
The site-independent COMDAC software. It includes customer/country-specific constant
data. The load image resides in the COMDACs program storage.

Load set
The load image plus the site-dependent configuration data.

Local login
Login into the AnyMedia ® Access System via the CIT or External System LAN 10BaseT
interface from the collocated GSI or dumb terminal.

Local powering
The AnyMedia ® Access System is supplied from a power plant (which covers -48V DC
power and ringing generator) delivered with the AnyMedia ® Access System.

Local VP
A VP that is cross-connected at the VP level on the AFM.

LOF
Loss of frame - A LOF condition is declared when an out of frame (OOF) condition
persists for t seconds.

LOF on ADSL line

ADSL frame synchronization has been lost at the ADSL for at least 2.5 seconds.

LOF on upstream SDSL line

The SDSL signal from the CPE is considered to be in a LOF condition after 2.5 0.5
seconds of contiguous lof defect. The LOF condition is cleared when 10 0.5 seconds
have occurred that do not have the lof defect. The loss of cell delineation (LOCD) event
counter data is mapped to lof. The firmware collects this 0.5-second interval data. If
there are 2.5 seconds of contiguous lof, it is considered to be LOF. This LOCD event
counter data is accumulated and reported on a 15-minute and 1-day basis.

Logical feeder port

An entity used to address an SDH or SONET path or a protection group. The logical
feeder port concept allows addressing of attributes or entities that are common to all
physical feeder ports associated with the logical feeder port and that are independent of
simplex or duplex mode. The AFME3/DS3 and the AFMO have two logical feeder ports.

Logical line identity

For logical addressing of an end-customer termination either associated to a V5.1 or a
V5.2 interface.

Logical link
A logical entity providing 31 64-kbps timeslots which is associated to a 2.048-Mbps
interface. One (V5.1) or more links (only V5.2) may be related to a V5.x interface.

Loop timed
The AnyMedia ® Access System is synchronized by the clock derived from the E1 link.

LOP
Loss of pointer - A LOP is declared when a valid pointer can not be obtained using the
pointer interpretation rules for SONET/SDH.

LOS
Loss of signal - E1/E3 LOS condition is declared if N consecutive no pulses are
received. Station clock (SC) LOS condition is declared if N consecutive no pulses are
received.

LOS on ADSL line

Received power has dropped to 6 dB below the reference power. The timing threshold is
as follows:
• Downstream: 1.5 seconds
• Upstream: 2.5 seconds.

LOS on upstream SDSL line

The loss of signal interrupts are timed, accumulated, and stored and are mapped to los.
The loss of signal timeout (LOST) is used to time the los. If the LOST bit is set, then it
is a LOS condition. The firmware collects this data, accumulates it, and reports the
number of los occurrences on a 15-minute and 1-day basis. The LOS failure parameter is
the accumulated los.

LPA400
Apparatus Code of one ADSL application pack with 4 ADSL subscriber ports and POTS
splitters

LPA400B
Apparatus Code of one ADSL application pack with 4 ADSL subscriber ports and POTS
splitters

LPA408
Apparatus Code of one ADSL application pack with 8 ADSL subscriber ports and POTS
splitters

LPA414
Apparatus Code of one ADSL application pack with 4 ADSL subscriber ports and ISDN
splitters

LPA416
Apparatus Code of one ADSL application pack with 16 ADSL subscriber ports and
POTS splitters

LPA417
Apparatus Code of one ADSL application pack with 16 ADSL subscriber ports and ISDN
splitters

LPA420
Apparatus Code of one ADSL application pack with 16 ADSL2+ subscriber ports and
POTS splitters

LPA432
Apparatus Code of one ADSL32p application pack with 32 ADSL-interfaces and 32 high
pass filters for Z ports; G.992.1, Annex A

LPA434
Apparatus Code of one ADSL32i application pack with 32 ADSL-interfaces and 32 high
pass filters for Z ports; ANSI T1.413 Issue 2 Annex B and ITU-T G.992.1, Annex B

LPA438
Apparatus Code of one ADSL32i application pack with 32 ADSL subscriber ports. The
LPA438 supports ADSL standards ADSL2 (ITU-T G.992.3 Annex B) and ADSL2+
(ITU-T G.992.5 Annex B).

LPA832
Apparatus Code of one P32A32 application pack with 32 subscriber ports for POTS and
ADSL simultaneously, as well as POTS only or ADSL only

LPA833
Apparatus Code of one P32A32 application pack with 32 subscriber ports for POTS and
ADSL simultaneously, as well as POTS only or ADSL only (with internal splitter on
board). The LPA833 supports also the ADSL2 and ADSL2+.

LPA900
Apparatus Code of one ATM Feeder Multiplexer for DS3

LPA901
Apparatus Code of one ATM Feeder Multiplexer for DS3; Duplex-capable

LPA910
Apparatus Code of one ATM Feeder Multiplexer for E3

LPA911
Apparatus Code of one ATM Feeder Multiplexer for E3; Duplex-capable

LPB
Line pack bus - The physical part between the board metallic access network (BMAN)
and the line circuit metallic access network (LMAN) on the ISDN AP and on the HDSL
AP. It can connect the LMAN with the BMAN. The LPB exists one time on an ISDN AP
and on an HDSL AP.

LPBK
Loop Back

LPBK
Loopback (a secondary service state) - A loopback for E1, HDSL, or ISDN is initiated.

LPP100
A per port programmable POTS application pack with 24 Z ports supporting 24 analog
subscriber lines. The LPP100 supports periodic pulse metering.

LPS501
Apparatus Code of one HDSL application pack

LPS503
Apparatus Code of one HDSL application pack; Supports V3

LPS504
Apparatus Code of one HDSL application pack; Supports V3 and Unstructured Leased
Lines

LPS510
Apparatus Code of one SHDSL application pack

LPS702
Apparatus Code of one SHDSL application pack with 16 SHDSL ports for ATM based
services (with 16PAM Coding)

LPS716
Apparatus Code of one SDSL application pack

LPU112
An ISDN application pack with 12 line circuits per pack. It supports 12 U interfaces
with 2B1Q line coding and remote power.

LPU112
Apparatus Code of one ISDN application pack with 12 U Ports

LPU430
An ISDN application pack with 16 line circuits per pack. It supports 16 U interfaces
with 4B3T line coding and remote power.

LPU430
Apparatus Code of one ISDN application pack with 16 U Ports

LPZ100
A per pack programmable POTS application pack with 32 Z ports supporting 32 analog
subscriber lines.

LPZ100
Apparatus Code of one POTS application pack with 32 Z-interfaces

LPZ110
Apparatus Code of one POTS application pack with 32 Z-interfaces and 32 Low Pass
Filters for Z Ports; G.992.1, Annex A

LT
Line termination - The equipment that terminates the access transmission system on the
network side.

LTU
Line termination unit - The LTU is located at the network side of an HDSL link and acts
as the master.

LTU
Line Termination Unit

LVD
Low Voltage Disconnect
...................................................................................................................................................................................................................................
363-211-586 GL-43
Issue 6, July 2007
Glossary

M M-channel
Maintenance-channel - Comprises 48 bits of a superframe on the 2B1Q U interface. The
duration of a superframe is 12 ms. 24 Bits are used for EOC channel, 12 bits for
overhead bits and 12 bits for check sum. In case of a 4B3T U interface the M-channel
consists only of one bit, which is transported with a bit rate of 1 kbps.

MAC
Media Access Control

Mainshelf
See AnyMedia Mainshelf.

Maintenance condition
An entity with a maintenance condition is insane. The maintenance condition is reflected
in the secondary service state.

Managed NTU
A 2B1Q ISDN digital subscriber line network termination unit which is fully managed
by the AnyMedia ® Access System. The NTU provides the subscriber a single channel
operating at one of many speeds, depending on the NTU type and configuration, from
1.2 kbps through to 128 kbps.

Management information base (MIB)

See “MIB” (p. GL-45)

Management Interface
The Management Interface is a package of software that is used for managing traditional
DLC services and ATM xDSL services.The Management Interface allows the user to
provision a single NE at a time through its GSI, while simultaneously monitoring alarms
of multiple NEs through its Network Maintenance Manager. It is installed on a personal
computer running under the Windows operating system.

Manual switch
Refers to an EMS or GSI initiated TL1 command that instructs the system to perform a
protection switch only if the protection pack is functional.

Manual switch back

Refers to an EMS or GSI initiated TL1 command that instructs the system to perform a
switch back to the service pack (only 1:N protection).

Maximum burst size (MBS)

Specifies the largest burst of data above the insured rate that will be allowed temporarily
on an ATM PVC, but will not be dropped at the edge by the traffic policing function,
even if it exceeds the maximum rate.
In the signaling message, the burst tolerance is conveyed through the MBS, which is
coded as a number of cells. The burst tolerance together with the sustainable cell rate
and the generic cell rate algorithm determine the MBS that may be transmitted at the
peak rate and still be in conformance with the generic cell rate algorithm.

MBS
Maximum Burst Size

MCU
Monitor and Control Unit

MDF
Main Distribution Frame

MEA
Mismatched equipment assignment (a secondary service state) - Pack type mismatch;
that is provisioning and equipped circuit pack do not match.

mesh-BN
Meshed Bonding network

mesh-IBN
Meshed isolated Bonding network

Metropolis ® ADM
Compact and cost-effective SDH multiplexer. The Metropolis ® ADM (former product
designation ADM 155 C) can be used in different configurations such as terminal
multiplexer, add/drop multiplexer and repeater, and can be used in the dual terminal
mode. It has a wide range of tributary interfaces. The Metropolis ® ADM multiplexes 2,
34, 45 Mbps, and STM-1 signals into an STM-1 or STM-4 line signal. Cross-connects
can be made at VC-12 level.

MIB
Management information base - Declaration of a collection of objects that defines the
network or network element for a given interface protocol. For example, there is a MIB
defined for access using the simple network management protocol (SNMP) and a
different MIB defined for access using the protocol of the GR-303 Embedded Operations
Channel (EOC).

Minimum bit rate

The minimum rate at which the ADSL, SDSL, and SHDSL link will train, upstream and
downstream. This rate is used to in determining whether a new connection can be
admitted to the shelf.

Mismatch of equipment and attributes (MEA) alarm

This alarm signals that the equipped pack and its provisioning do not match. The alarm
is cleared either by deleting the cross-connect or by replacing the pack with one that
supports the service category.

Mixed ISDN/POTS mode

An operation mode of the AnyMedia ® Access System where ISDN and POTS service is
possible. Because of ISDN subscribers are provided, the frame relay function has to be
performed. Therefore at least one IO_HDLC pack is necessary (optionally a second one
for protection). V5 communication channel information is frame relayed on the
IO_HDLC pack and routed towards ISDN subscribers (for ISDN D-channel information)
and to the COMDAC (for V5 layer 3 protocols) respectively.

Mixed service
The capability to split the 2-Mbps payload of the HDSL interface at the NTU to a G.703
for ISDN PRA service and to a leased line port (V.35/V.36/X.21) for VLL/GLL service.
The used timeslots of the G.703 port are routed to the V5.2 interface, while the 64 kbps
timeslots used for VLL/GLL service are routed to 2-Mbps leased line links.

MJ
Major

MN
Minor

MNI
Multiple Network Interface

MON
Monitoring (a secondary service state) - For ISDN or HDSL subscribers; external error.
For example layer1 not possible to activate or HBER.

MON
Monitoring

Monitoring
The operator can hear to the subscriber while the circuit is still operational and in
bridged state. Additionally a speech connection can be established to allow to talk to the
customer.

MRS
Multi-Rate Single pair

MSP
Multiplex Section Protection

MTBF
Mean time between failures - The average time that the system remains operational
between consecutive failures. The MTBF is usually expressed in years. In general,
MTBF = MTTF + MTTR where MTTF is the mean time to failure, and MTTR is the
mean time to repair.

MTIE
Maximum time interval error - The maximum peak-to-peak delay variation of a given
timing signal with respect to an ideal timing signal within a particular time period.

MTTF
Mean time to failure -The average time that the system remains operational between
consecutive failures, outage duration for repair or maintenance activities takes not into
consideration. The MTTF is usually expressed in years.

MTTR
Mean time to repair - The average time that the system remains out of service until it is
repaired. MTTR is usually expressed in hours.

Multi-link
A collection of more than one 2.048-Mbps link which together make up a V5.2 interface
(although a V5.2 interface needs not to have more than one 2.048-Mbps link).

Multiframe
A cyclic set of consecutive frames in which the relative position of each frame can be
identified.
....................................................................................................................................................................................................................................

N NAC
Not accessible (a secondary service state) - The entity is not accessible, for example if a
pack is faulty or unequipped, then all related drops are not accessible.

NAM
Navis AnyMedia Element Management System (SW) - Represents computing facilities,
specialized software and data storage facilities used to administer and maintain multiple
network elements (NEs) distributed over a wide geographical area from a centralized
location. Communication in both directions is accomplished via TL1 messages.

Narrowband services
Narrowband services typically include POTS services, permanent leased line (PLL) and
ISDN as well as n-times 64 kbps to 2 Mbps services.

Narrowband subsystem
That part of the AnyMedia ® Access System which supports narrowband services.

NAS
Not associated (a secondary service state) - The line termination on the AnyMedia ®
Access System side is provisioned but the cross-connection to a network interface (V5,
LL,...) is not provisioned yet.

NCD
No Cell Delineation

NCD anomaly
An No Cell Delineation (NCD) anomaly occurs immediately after ATM cell start-up
when ATM data are allocated to the buffer and as long as the cell delineation process
operating on these data is not in the SYNC state. Once cell delineation is acquired,
subsequent losses of cell delineation shall be considered LCD defects. The performance
management parameter NCD is applicable for ADSL.

NCP
Network connection point - NCP is the point at subscriber site on which subscriber’s
installation and subscriber’s line are connected.

NE
Network Element

NE name
The network element (NE) name is a unique provisioned name given to an AnyMedia
shelf. This name is identified by the GSI as the site ID.
...................................................................................................................................................................................................................................
363-211-586 GL-47
Issue 6, July 2007
Glossary

Near end
Termination of an external link at the access network element (ANE) site.

NEBE
Near end block errors - Bit errors in the upstream direction from the NTU to the LTU.
They are recognized with the help of the CRC checksum in the maintenance channel or
in the HDSL overhead channel received from the NTU.

Network failure
A network failure (NF) is a failure within the network side. This includes failures within
the NTU. After a failure happened, a ″Block message″ is sent via V5 interface to the
LE. Afterwards the failure/failure combination is analyzed and mapped to either a
network failure or user failure and reported via V5 interface to the LE. See also user
failure.

Network maintenance manager

The network maintenance manager is part of the management interface package of
software that is used to monitor alarms over multiple NEs. The network maintenance
manager allows a user to choose which NEs to monitor, to filter viewed alarms, and to
manage the display of these alarms.

NIC
New Installation Concept - NIC makes use of small module containers on the MDF
equipped with very compact application specific modules which are connected via
system cables to the AnyMedia Access System.

Non-real time variable bit rate (nrt-VBR)

A service category for data traffic that has no fixed timing relationships but has a
guaranteed QoS. Statistical multiplexing is provided to make optimum use of network
resources.

Non-revertive mode
A certain protected system resource which has become faulty and thus caused a switch
to or a replacement by a certain other (standby) resource is NOT reused automatically if
the (temporarily) faulty resource returns back to operation. Instead of this the standby
resource is used further on. A switch back may take place later on, but is independent
from the recovery of the (temporarily) faulty resource.
Examples:
a) If a reference clock switch between COMDAC phase locked loop (PLL) reference
clock inputs has occurred due to a failure condition, the will not automatically return to
the primary reference, even if the failure condition has cleared.
b) V5.2 protection switching of communication channels.

Non-service-affecting
Refers to a condition not affecting the service (for example telephony) at the time it is
detected.

NOP
Not operational (a secondary service state) - The entity is not operational because a
failure condition on a lower layer exists, for example a circuit pack failure.

Normal mode
Refers to the mode of changing to administrative primary service state OOS.In normal
mode service functions are possible as long as the resources provided for service are still
busy. If the resources get idle the service state OOS is entered automatically.

Normal polarity
Customer-specific definition of the feeding polarity. Some customers define normal
polarity as a-wire is more negative with respect to b-wire. Other customers define
normal polarity as b-wire is more negative with respect to a-wire.

NOS
Network Out Of Service

nrt-VBR
Non-real time variable bit rate

NSA
Non-Service Affecting

NSF
Network side failed (a secondary service state) - The related network interface (V5, LL,
...) has a failure and is not operational.

NT
Network termination - The equipment that terminates the access transmission system on
the customer side. The most known network termination device is the NT1, that provides
only physical layer functionality. Other network termination devices with more
functionality are NT-N or NT-a/b.

NT1
Network Termination Type 1

NTP
Network Time Protocol

NTR
Network Timing Reference

NTU
Network termination unit - The NTU is located at the customer side of an HDSL link
and acts as the slave. The NTU terminates the HDSL access transmission system on the
customer side.

NVDS
Nonvolatile data storage - NVDS refers to that part of the database which is retained
even after a power failure, for example provision parameters.

NVPS
Nonvolatile program storage - NVPS refers to nonvolatile memory on COMDAC and on
AFM used to store the load image.

O OAM
Operations, Administration, Maintenance

OAM&P
Operations, Administration, Maintenance, and Provisioning

Object
See entity.

OC-3
Optical Carrier Level 3 (155.52 Mbps)

OCD
Out Of Cell Delineation

Off-hook
In the off-hook state the telephone is picked up. The off-hook state indicates the busy
state.

OLIU
Optical Line Interface Unit

On-demand tests
On-demand tests will be executed only by an operator TL1 command.

On-hook
In the on-hook state the telephone is not picked up. The on-hook state indicates the idle
state.

OOF
Out of frame - The OOF condition is assumed, when three consecutive incorrect frame
alignment signals have been received.

OOS
Out Of Service

Operational condition
Reflects whether the entity concerned is able to take over operation or not. It depends on
the service state and may be one of the following:
• An entity is operational if the service state of the entity is IS (without any secondary
service state), IS-SHD or OOS-SHD, that means, no failure is present.
• An entity is not operational in all other cases.

Originating call
Originating call is the type of call initiated at the subscriber side of the network user
interface. It comprises the build-up, speech and the tear-down phase. For a POTS call
for example it starts with the recognition of an off-hook by the application pack (AP)
and sending a seizure message to the LE.

OSP
Outside Plant

Out-band signaling
For transferring of signaling information bandwidth beside the voice transmission band
(300 ... 3400 Hz) of the same transmission path is used.

Outage
The state of a system typically characterized by loss of traffic or the ability to control or
reconfigure the system.

Outage duration
The length of time an outage exists.

Outage frequency
The average number of outages the system experiences per unit time.

Outward direction
See equipment pair.

Overload
Any load which is greater than the nominal load for which the system is required to
work without any performance degradation.
....................................................................................................................................................................................................................................

P P-AIS
Path Alarm Indication Signal

Pack
See circuit pack

Pack class
Pack class defines the general class of APs. This code is an 1 byte NON-ASCII code
which maps for example to POTS AP (Z interface packs), ISDN AP (U interface packs),
etc. The pack class is hard coded in the pack FW and is not visible for the operator. See
also pack subclass.

Pack subclass
Pack subclass defines the specific type of a pack. This code is an 1 byte NON-ASCII
code which maps for example to LPZ100 or LPP100. The pack subclass is hard coded in
the pack FW and is not visible for the operator. See also pack class.

Pack type
Different pack types can be plugged in the AP slots of the AnyMedia ® Access System:
• ISDN AP (LPU112 for 2B1Q U interface, LPU430 for 4B3T U interface)
• POTS AP (LPZ100, LPP100)
• ATM xDSL pack (AFME3, AFMDS3, AFME1, AFMO, ADSL4 AP, ADSL8p AP, ADSL4i
AP, ADSL16p AP, SDSL16)
• TEST AP (TAP10x)
• HDSL AP (LPS501, LPS503, LPS504)
...................................................................................................................................................................................................................................
363-211-586 GL-51
Issue 6, July 2007
Glossary

Partial packet discard (PPD)

In severe ATM traffic congestion, the traffic manager discards packets arriving from any
connection, regardless of whether or not the traffic on the connection is exceeding its
bandwidth. The traffic manager discards all remaining cells in the packet, even if the
severe congestion clears in the meantime.

Password
Character string used to authenticate the identity of a user. The password should consist
of 6 to 10 case sensitive alphanumeric characters, it should be changed frequently, it is
stored and transmitted in an encrypted form.

Payload
Interface rate minus frame overhead. This is the net capability for information transfer
provided for the next lowest level of the digital signal hierarchy.

PCD
Passive Clock Distribution

PCM
Pulse Code Modulation

PCR
Peak Cell Rate

PDH
Plesiochronous Digital Hierarchy

Peak cell rate (PCR)

A traffic parameter measured in cells per second that specifies the maximum number of
cells that can be transmitted on an ATM network. PCR defines the shortest period
between two cells.

Performance management
Consists of a set of functions to evaluate and report on the behavior of telecommunica-
tion equipment and the effectiveness of the network and/or network elements (NEs).

PFC
Power factor correction - Standard AC/DC converters draw line current in pulses around
the peaks in line voltage. This may be undesirable for several reasons. PFC circuits
ensure that the line current is drawn sinusoidally and in phase with the sinusoidal line
voltage.

PFP
Physical Feeder Port

PFU
Power Filter Unit - A PFU is a pack accommodating two internal filters for dual power
distribution to the AnyMedia Mainshelf.

PFU501
Apparatus Code of a Power Filter Unit

Physical feeder link

An E1 link between the AnyMedia ® Access System and a service node.

Physical feeder port

Corresponds to the physical termination of the optical feeder. The physical feeder port
concept allows the addressing of SDH physical medium, regenerator section, and
multiplex section layer entities (or SONET physical medium, section, and line layer
entities). An AnyMedia shelf has two physical feeder ports when using one AFMO in
simplex mode and four physical feeder ports when using 2 AFMOs in duplex mode.

Physical layer convergence protocol (PLCP)

The IEEE 802.6 standard that defines the physical layer that adapts the actual
capabilities of the underlying physical network to provide the services required by the
ATM layer.

PID
Program identification code - Identifies the version of firmware on one or more devices
on the pack.

Platform
Items and functions in SW, HW and FW which are independent of the application.

PLCP
Physical Layer Convergence Protocol

PLL
Permanent leased line - These lines may be analog (ALL) or digital (DLL). They are not
switched services and are not carried to the LE through V5 interface but on special
separate 2-Mbps links.

PM
Point-to-Multipoint

Port
Refers to the devices and functions built on or provided by a pack for one subscriber or
line interface; sometimes referenced as circuit.

Port control protocol

This protocol provides the necessary procedures for a coordinated PSTN and ISDN user
port management. It includes the following mechanisms:
• Coordinated user port blocking with the responsibility at the LE to support the service,
because LE has the knowledge about the port call state. Therefore the AnyMedia ® Access
System shall only perform hard blocking of user ports in case of failure conditions.
• Coordinated user port unblocking is a symmetrical procedure (unlike blocking).

POTS
Plain old telephone service - Analog telephony service via a copper pair.

POTS AP
Plain old telephone service application pack - A pack containing Z ports that provide
service to analog subscriber interfaces.
...................................................................................................................................................................................................................................
363-211-586 GL-53
Issue 6, July 2007
Glossary

POTS subscriber
Plain old telephone service subscriber - Analog telephony subscriber.

POTS-only mode
An operation mode of the AnyMedia ® Access System where only POTS service is
possible. Since no ISDN subscribers are provided, no frame relay function has to be
performed. Therefore no IO_HDLC pack is necessary. V5 communication channels via
TSI are connected directly to the COMDAC where they are terminated.

PP
Point-to-Point

PPD
Partial Packet Discard

ppm
parts per million

PPM
Periodic pulse metering - The LE provides the transmission of charging information to
subscriber’s home meter equipment. Charging information will be carried as periodic
pulses via subscriber’s line.

PPS
Point-to-Point Single pair

PRA
Primary Rate Access

PRC
Primary Reference Clock

Pre-defined
When a parameter is stated as being pre-defined the parameter is not required to be
provisioned via the TL1 interface. The parameter is either intrinsically provided within
the AnyMedia ® Access System or within the customer specific data set. A pre-defined
parameter may take one of several values depending on the operator.

Pre-provisioning
The ability of provisioning the complete system without the existence of the complete
system hardware. Only the basic equipment is required.

Primary link
The 2.048-Mbps link in a multi-link V5.2 interface whose physical communication
channel in timeslot 16 carries a communication path for the protection protocol and, on
V5.2 initialization, also the communication path for the control protocol, link control
protocol, and the BCC protocol. Other communication paths may also be carried in the
timeslot 16.

Primary reference signal

The AnyMedia ® Access System can use two timing inputs to synchronize the COMDAC
phase locked loop (PLL). The preferred reference is called primary reference and the
...................................................................................................................................................................................................................................
GL-54 363-211-586
Issue 6, July 2007
Glossary

alternate reference is called secondary reference.

Privileged user
User login allows access to all TL1 commands and GSI capabilities.

Procedural errors
Man made operation failures.

Protected configuration
The protection pack is provisioned but may be faulty or moved to OOS by the operator.

Protected pack
A pack for which there is a backup. Protection may be one-to one, or it may be
one-to-more-than-one (1:n).

Protection group 1
This is the standard group of physical communication channels consisting of the
protected logical communication channel on the primary link and the protecting standby
channel on the secondary link of a V5.2 interface, each located in timeslot 16.

Protection group 2
This is an optional protection group of a V5.2 interface, consisting of up to 3 standby
communication channels, serving as protecting channels for all logical communication
channels, not included in protection group 1.

Protection pack
Identifies the pack which is responsible for providing protection for the service pack(s).
In 1:N protection configuration it is a dedicated pack providing protection for the service
packs. In 1:1 protection configuration it is the pack currently not carrying the service.

Protection permission
An indication for a service pack which reflects whether the pack concerned is allowed to
perform an automatic protection switch or not (inhibited).

Protection physical channel

A physical timeslot used for carrying a logical communication channel or used for
protection of these logical communication channels. In the first case the protection
physical channel is active and in the second case the protection physical channel is
standby.

Protection protocol
This protocol provides the procedures for protecting the communication channels, that is
those TSs carrying the signaling paths, that are established between the LE and the AN
(but it does not provide any mechanism to protect the subscriber payload paths).

The protocol offers to the LE mechanisms to

• command, after a failure detection, the switch-over of a protected communication channel
unit (logical CC) to a protecting one (physical CC).
• command by operator request the switch-over of a protected communication channel unit
(logical CC) to a protecting one or protected (by pre-emption of the hosted logical
C-channel) one. This operation is only applicable to PG2.
• reset the transmission sequence number, upon detecting a misalignment of state variables
or at system start-up.
and allows the AnyMedia ® Access System to perform the following operations:
• request, after a failure detection, the switch-over of a protected communication channel
unit (logical CC) to a protecting one (physical CC).
• reset the transmission sequence number, upon detecting a misalignment of state variables.

Protection status
An indication which reflects the actual state of the pack protection.

Protection switch
A switch of the service from the service pack to the protection pack. A protection switch
can be requested manually or driven by pack fault.

Protection switch disabled

Protection pack is in administrative primary service state OOS.

Protection switching
A reliability feature that causes service to switch to the backup equipment during faults
or testing.

Provisioning
The process of providing the system with parameters needed to realize a specific
customer and site specific behavior.

Provisioning variant
The provisioning variant is a unique label of a complete provisioning data set applied
via the TL1 interface. These provisioning data sets must be provisioned and if necessary
changed (on ANE side by TL1 commands) consistently at both sides LE and ANE. These
changes have no impact on the provisioning variant. Switching over from one to another
provisioning variant (and thus changing the provisioning data set) is done by using the
common control protocol.

PRU
Power Rectifier Unit

PSD of ADSL transmission

The actual ADSL transmit power level. This value may be lower than the provisioned
PSDM.

PSDM
Power Spectral Density Mask

PSDM of ADSL transmission

A provisionable value representing the maximum allowed ADSL transmit power level.
The ADSL transceiver may choose a lower power level based on line conditions.

PSES
P-bit Severely Errored Seconds

PSTN
Public Switched Telephone Network

PSTN user port

Public switched telephone network - Delivers analog telephony and data services to a
POTS subscriber. It is addressed by a logical layer 3 address used in the relevant
protocols on the V5.x interface. With respect of V5.x interface the layer 3 address
uniquely identifies one PSTN user port.

PVC
Permanent virtual connection - A logical dedicated connection between two user ports in
a point-to-point configuration.
....................................................................................................................................................................................................................................

Q QMC
QUICC Multi-channel Controller

QMS
Quality Management System

Quality of service (QoS)

An indicator of the performance of a transmission system on the Internet and other
networks. QoS is measured in transmission rate, error rates, latency, and other
characteristics.

QUICC
Quad Integrated Communications Controller
....................................................................................................................................................................................................................................

R RADSL
Rate Adaptive Digital Subscriber Line

RAI
Remote alarm indication (a secondary service state) - The far end reports that it has
detected a failure in its downstream direction.

RAM
Random Access Memory

RBL
Remote blocked (a secondary service state) - Same as BLK, but used for V5 links.

RCP
Rack Connection Panel
...................................................................................................................................................................................................................................
363-211-586 GL-57
Issue 6, July 2007
Glossary

RDI
Remote defect indication - Indicates that the far end has detected an incoming failure of
an interface.

RDS
Running digital sum - An error counter which counts the frames with at least one line
code violation. It counts the errors which are detected in upstream as well as in
downstream direction.

READSL
Reach Extended ADSL (according to G.992.3, Annex L). READSL improves the range
of ADSL over very long lines, perhaps beyond the coverage of traditional ADSL. Since
higher-frequency downstream bins have higher attenuation at longer loops, READSL
focuses a higher power density within a constricted downstream and upstream
bandwidth, resulting in extending the ADSL reach to longer subscriber loops. Note, that
seamless rate adaption may be used in the READSL mode as well.

Real-time variable bit rate (rt-VBR)

A service category with strict cell transfer and delay variation demands and cell loss
requirements.

Regenerator
A transmission device between LT and NT. It enhances the transmission distance
between LT and the NT. The regenerator is remote powered from the LT and is powering
the NT. In ETR080 the number of regenerator between LT and NT is due to reasons of
powering limited to one.

Relationship
A dependence between two entities concerning the operational condition where the
operational condition of one entity depends on the operational condition of another
entity. The relationship may be of two types:
• hierarchical relationship according to the provisioning and resource view where upperlying
entities depend on underlying entities; that is underlying entities have to be provisioned
first. This also implies that the operational condition of an upperlying entity depends on the
operational condition of an underlying entity. If a pack is in a protected configuration, the
EQUIPMENT-layer entity has more than one relationship to underlying PACKS-layer
entities. The operational condition of the upperlying EQIPMENT layer entity is
″operational″, if at least one underlying entity is also ″operational″ and available for a
protection switch.
• control relationship not necessarily a relationship between entities of different layers as the
hierarchical relationship. It is a relationship of two entities where the operational condition
of one of the entities (controlled entity) depends on the operational condition of the other
(controlling) entity in such a way that the operational condition of the controlled entity is
only ″operational″ if the operational condition of the controlling entity is also
″operational″.

Remote login
Login into the AnyMedia ® Access System via LAN, ROC, or External System LAN
(over TCP/IP DCN) from EMS or GSI.

Remote power feeding

Refers to the power feeding of the NT/REG by the ISDN AP. Normal powering and
restricted powering mode are distinguished. In the restricted powering mode the polarity
of the feeding voltage at the S/T interface is reverse.
Normal powering mode:
• In the normal powering mode, the NT (and an optional regenerator) receive power from
the ISDN AP. The power for all subscriber terminals on the subscriber side of the
S/T interface is supplied from a mains-operated power supply unit at the CPE.
Restricted powering mode:
• The restricted powering mode occurs, when the main power at the CPE is lost. In this case
the ISDN AP must provide power for the NT (and an optional regenerator) and also to a
single designated restricted mode terminal on the subscriber side of the S/T interface.

Reports-only user - ATM xDSL

User login that allows access to GET messages for retrieving system information and
traps. Reports-only users do not have access to any SNMP messages that create, change
or remove service or to any security messages that affect other users.

Reports-only user - narrowband

User login allows access to a limited set of TL1 commands for retrieving system
information and autonomous messages. Reports-only users do not have access to any
TL1 commands that create, change or remove service or to any security commands that
affect other users.

Resistibility
The ability of telecommunication equipment or a network to withstand the effects of
certain electrical, magnetic and electromagnetic phenomena.

Retrofit procedures
Migrating from an old AnyMedia ® Access System configuration to a new one may lead
to changes in the database. Since the content of the old database should be kept after
migration the database is transformed after recovery of the new configuration. This is
done by transformation procedures, also called database evolution.

Reverse polarity
Defined as opposite to normal polarity, that means the feeding polarity is reverse.

RFCP
Subrack for Fuse Panel and Connection Panel

RFI
Remote Failure Indication

RFI notching
Radio frequency interference. This capability allows the definition of frequency
breakpoints for insertion of notches in the standard ADSL2+ transmit power spectral
mask. It is applicable only to the signal transmitted by the ATU-C.

RFI on ADSL line

ADSL frame synchronization has been lost at the CPE for at least 1.5 seconds.

RFP
Rack Fuse Panel

RFU
Ringing Filter Unit

RGP
Ringing Generator Pack - The RGP is a dual slot ringing generator pack, which may be
plugged in slot 40/41 and slot 42/43 of the AnyMedia LAG Shelf. The RGP in slot
40/41 drives ringing bus 0, while the RGP in slot 42/43 drives ringing bus 1.

RGU
Ringing Generator Unit - A pack providing the ringing voltage needed for POTS
applications.

Ringing protection mode

Two ringing sources (external or internal) on the AnyMedia LAG System are working in
active/active protection mode. Each one provides a ringing voltage to a separate ringing
bus. The power ringing is taken by the POTS APs from the ringing bus according to the
load sharing scheme. If one ringing voltage on one ringing bus fails, all POTS AP take
the ringing voltage from the remaining operational ringing bus.

RMS
Root mean square - The root mean square value of an electrical measured quantity.

ROC
Remote operations channel - A bearer channel over a leased-line 2.048-Mbps link or
over V5.x interface that conveys management information for a remote system
(AnyMedia ® Access System). The ROC is expected to be used when the system is
installed at locations where no separate network (for example LAN Ethernet) exists.

ROC support D-channel

The channel which carries the ISDN D-channel signalling Information for
(de-)establishing the ISDN dial-up ROC.

Router
A LAN/WAN device that operates at OSI layers 1 (physical), 2 (data link), and 3
(network). Distinguished from a bridge by its capability to switch and route data based
upon network protocols such as IP.

Routine switch
Refers to an internally initiated non service affecting switch that instructs the system to
perform a switch only if the protection pack is in service and has no known faults. The

switch, which is done for preventive maintenance, is performed on a provisionable time

schedule.

RRG
Ring-wire for Ringing Voltage

RS-232C
Serial Interface

rt-VBR
real time Variable Bit Rate

RTU
Remote Test Unit - An RTU is a testing equipment for subscriber lines. An RTU-2 is
collocated to the system and performs test functions (application of test signals and
measurements) under the control of a test system controller. An RTU-1 is collocated to
the central office and not used in the 30 channel market.

RTU interface
A serial EIA-232C interface (9-pin Dsub) in the shelf connection panel of the AnyMedia
Mainshelf served by the communication interface unit (CIU) for a collocated RTU-2.

RTU test session

An RTU test session is initiated and started by the RTU with a CONN-LPACC-MET TL1
command via the control link. It is terminated from the RTU with a DISC-TACC,
RST-TAP-MET or REPT-INITZN command or autonomously by the system if any
involved equipment on the test session fails. An RTU test session is different from a test
session using integrated test and measurement equipment. These two types of test
sessions use different commands for test setup, test control and test stop.
....................................................................................................................................................................................................................................

S SA
Service Affecting

SC
Station clock - An external 2048 kHz synchronization signal, according to ITU-T G.703.

SC
Station Clock

SCC
Serial communication controller - Part of the communication processor module of the
micro-controller MPC860. The SCC can be configured to implement different protocols.
For most protocols, this corresponds to portions of the link layer (OSI layer 2). For a
ROC (64-kbps timeslot of an E1 link), the SCC is configured to implement HDLC
protocol in QMC-mode (QUICC multichannel controller mode).

SCI
Station Clock Interface

SCP
Shelf Connection Panel

SCR
Sustainable Cell Rate

SDH
Synchronous Digital Hierarchy

SDSL
Symmetric Digital Subscriber Line

Sealing current
5 mA current used (historically) to prevent oxidation buildup on a/b pairs.

Seamless Rate Adaptation

Crosstalk from adjacent line drops, AM radio disturbers, temperature changes and water
in the cable binder can cause an ADSL link to degrade or force a retrain. Seamless rate
adaption (SRA) allows a link to change the data rate, transmit power and bin selection
of the connection in order to adapt to the new line condition without retraining and
excessive errors.

SEC
SDH Equipment Clock

Secondary link
A distinguished V5.2 link with some special characteristics: timeslot 16 serves as
protection physical channel for the communication channel related to timeslot 16 of the
primary link. Both timeslots form protection group 1. The protection protocol is also
associated to timeslot 16 of the secondary link.

Secondary reference signal

The AnyMedia ® Access System can use two timing inputs to synchronize the COMDAC
phase locked loop (PLL). The preferred reference is called primary reference and the
alternate reference is called secondary reference.

Security management
Consists of a set of functions that protect telecommunications networks and systems
from unauthorized access by persons, acts, or influences, and to track and report access
attempts.

SELT
Single-ended loop test

Semi-permanent leased line

A V5.x service where bearer channels for certain user ports are pre-connected on
provisioning base. Semi-permanent leased lines pass through the V5.x interface and are
established under control of the LE by use of the BCC protocol after recovery of the
V5.2 interface (V5.1 bearer connections are established anyway). No on-demand
signaling is possible.
Semi-permanent leased lines are supported for both, POTS and ISDN subscribers.

Serial number
The serial number is a 12-character code uniquely identifying each pack and indicating
the date and place of manufacture.

Service pack
Identifies the pack(s) which are responsible for handling the service. In 1:N protection
configuration there are dedicated pack(s) which are protected by a protection pack. In
1:1 protection configuration it is the pack currently carrying the service.

Service state
Each unit in the system at any time has a defined service state. This service state is
system driven and shows the usability of the unit. The normal service state is a read
only value and can not be changed by the operator. Each service state consists of two
parts: a primary service state displaying the general usability [in service (IS) or out of
service (OOS)] and a secondary service state displaying in case of a failure the failure
reason [for example not operational (NOP)]. The secondary service state is not used in
all cases. For some objects there is an administrative service state, whose primary
service state is changeable via TL1 commands. The operator can set the desired mode
for operation: IS or OOS. In this case the current availability is expressed in the
secondary state which is controlled and changed automatically by the system.

Service-affecting
Refers to a condition affecting the service (for example telephony) at the time it is
detected.

SES
Severely error second - An SES is a second in which the bit error rate (BER) is greater
than 10-3 due to all causes of degradation.

SET
The simple network management protocol (SNMP) operation used by the OS to change
the value of specified information such as a MIB variable.

SHD
Shutting down (a secondary service state) - SHD is a special state triggered by the
operator. A circuit pack is administratively set to OOS and the system is waiting until all
established services are terminated.

SHDSL
Single-Pair High-Bit-Rate Digital Subscriber Line

SHDSL data link

The SHDSL data link is transported over the EOC bits of the SHDSL frame. It
transports maintenance and configuration messages between the SHDSL AP and the
NTU.

SHDSL drop
The SHDSL drop is the physical line. It is also used as an AID to identify an SHDSL
port and the location of loopbacks or line tests.

SHDSL interface
The SHDSL interface (I/F) includes all functions to realize SHDSL transmission. This
includes the SHDSL transceivers and the digital subscriber line.

SHDSL link
The SHDSL link is a connection between an SHDSL port and an NTU.

SHDSL overhead bits

The SHDSL overhead bits (HOH) are embedded in the SHDSL frame together with the
payload timeslots. The SHDSL overhead consists of synchronization word, CRC, EOC,
stuff bits, and fixed indicator bits.

SHDSL pair
The SHDSL pair is the copper pair connected to an SHDSL port. It provides duplex
transmission on 2-wire metallic local lines with a transmission rate of up to 2312 kbps
in 2-wire mode or up to 4608 kbps in 4-wire mode.

SHDSL payload timeslots

The SHDSL payload timeslots are physical resources provided by an SHDSL port. The
transmission rate of an SHDSL payload timeslot is 64 kbps. The SHDSL payload
timeslots are assigned to logical timeslots, when the operator provisions a V5 ISDN PRA
subscriber or an n × 64 DLL subscriber.

SHDSL port
The SHDSL port refers to the devices and functions provided by an SHDSL AP to
support SHDSL transmission.

Shelf daisy-chain
Connecting AnyMedia Mainshelves to daisy-chain AFMs together for ADSL services
only. This can be done locally by connecting the AFM ports directly or remotely via an
SDH transport network.

Shelf overbooking factor

Overbooking means allocating bandwidth to connections on a port, where their total
bandwidth allocation is greater than bandwidth minus CAC Reserve. Booking can exceed
bandwidth and also the bandwidth of the port, but traffic throughput can never exceed
bandwidth.

Shelf PCR
The amount of bandwidth allocated by provisioning to a shelf.

Shelf VP
A feeder VP for which the BB subsystem supports VC cross-connects.

SID
System Identification

Side select switch

An action performed on peripheral packs in case of a COMDAC protection switch in
order to receive/transmit information from/to the COMDAC which is currently active.

Side switch
The operation of deactivating the active COMDAC and activating the stand-by
COMDAC.

Silent failure
A silent failure is defined to be any equipment failure that results in a loss of service or
a loss of protection that does not trigger an office alarm or generate an OS autonomous
message. Typically, these failures arise from circuit packs or a portion of circuit packs
whose performance cannot be monitored by alarm circuitry (Section 2.4.3 of TR-418).

Simplex mode
A mode in which an entity is not protected: only one entity is installed and its failure
disrupts the services it provides.

Single-pair high speed digital subscriber line (SHDSL)

A physical layer technology used to transport digital bit stream over one or two pairs of
nonloaded existing copper distribution cable. SHDSL provides equal transmission bit
rates for both the upstream and downstream directions ranging from 192 to 2312 kbps in
2-wire mode or from 384 to 4608 kbps in 4-wire mode. SHDSL is based on use of the
TC-PAM line coding scheme. TC-PAM is a baseband line coding scheme that does not
allow the option to share the copper loop from a baseband POTS signal.

Site ID
A unique provisioned name given to an AnyMedia Mainshelf. This name is identified by
the AnyMedia Element Manager as the NE name.

Site-specific
Reflects the particular configuration of the site. Site-specific configuration is achieved
by provisioning.

SN
Serial Number

SNMP
Simple network management protocol - Used by the GSI/EMS for the AnyMedia ®
Access System ATM xDSL system for accessing the MIB objects.

SNMP
Simple Network Management System

SNMP TRAP
See TRAP.

SNR
Signal-to-Noise Ratio

SNR margin of ADSL line

The increase in noise, relative to the current received noise power, that can occur with a
BER of 10-7 still being met.

SNR margin of [S]HDSL line

The SNR margin is defined as the maximum dB increase in equalized noise or the
maximum dB decrease in equalized signal that a system can tolerate and maintain a BER
of 10-7.

SNRM
Signal to Noise Ratio Margin

Software factory
The software factory is responsible for the pre-configuration and pre-installation of the
system software. The software factory also creates installation files (for example CD,
diskettes etc.) for delivery to the customer.

Software package
At the architectural level, software packages are the primary vehicle for functional
partitioning of the system. Software packages are configuration units of the system.

Software upgrade
Installing newer system software.

SONET
Synchronous Optical Network

SP
Single-Pair

SPE
Synchronous Payload Equivalent

SPLL ROC
Semi-Permanent Leased Line Remote Operations Channel - A permanent established
connection between a ROC transported via V5.x interface and routed through to the LE.
See also ROC.

SRA
See Seamless Rate Adaptation

SSU
Synchronization Supply Unit

Standby
A backup pack or system entity that may be activated during a equipment failure or
testing.

Standby pack
Identifies the pack which is currently responsible for providing the protection in a
protected configuration. A stand-by pack may also be in a state where no service is
possible, for example faulty or moved to OOS by the operator.

Standby protection physical channel

A protection physical channel (timeslot) which is not carrying a logical communication
channel, but is used for protection. See also active protection physical channel.
...................................................................................................................................................................................................................................
GL-66 363-211-586
Issue 6, July 2007
Glossary

Standby provisioning variant

A provisioning variant label, which is not used for next V5 interface start-up. The LE
and AN may switch via the control protocol between active and standby provisioning
variant label.

Status condition
Report of a type of standing condition that reflects abnormal conditions or other
anomalies that are not assigned a severity. Status conditions are necessary to indicate to
the EMS or the operator that the system is in an unusual state, or is performing an
action that may interfere with system operations, such as loop-back, software
installation, or a forced or inhibited protection switch. A status condition is reported via
a report-event TL1 message or an SNMP trap. Two kinds of status conditions are
supported: Set/clear status conditions, which are active as long as the abnormal condition
persists, and transient status conditions, which indicate a single abnormal event which is
already cleared again.

Status condition report

Autonomous report that is not an alarm. A status condition report is part of a report
sequence (status condition set/status condition cleared). Additionally, it is possible to
retrieve whether the status condition is set or cleared.

Steady state
Time of constant failure rate between the infant mortality factor period and the end of
life period. This time represents the design life.

STM-1
Synchronous Transport Module Level 1 (155.52 Mbps)

Structured leased line

A structured leased line provides byte and timeslot information for the 2Mbps bitstream.
This information is given via the framing information in timeslot 0 (see also
unstructured leased line).

Structured mode
In structured mode timeslot 0 (TS0) of the 2 Mbps-bit stream according to G.704 can be
identified. Also location of TS0 within the HDSL frame is known (see also unstructured
mode).

STS-3c
155 Mbps signal according to SONET standards.

Subscriber
Represents one customer entity on the LINES-layer.

Subscriber line
The a/b copper pair between a local exchange (LE) or access network system (AN) and
the network connection point (NCP) (see ITU G.101).

Subscriber loop
Contains subscriber’s line, subscriber’s installation and subscriber’s terminal; sometimes
referenced as drop.

Subscriber loop feeding

Subscriber loop feeding will be provided for POTS to supply subscriber’s terminal with
power and for supervisioning of subscriber’s loop.

Sustainable cell rate (SCR)

The average cell transmission rate in ATM, measured in cells per second and converted
internally to bits per second. Usually, SCR is a fraction of the peak cell rate.

SVC
Service Channel Access

SVGA
Super Video Graphics Adapter

SW
Software - Software is program data which is downloadable into the system.

SWDL
Software download (a secondary service state) - Software download is in progress.

SWDL
SoftWare DownLoad

Symmetric digital subscriber line (SDSL)

A physical layer technology used to transport digital bit stream over one pair of
nonloaded existing copper distribution cable. SDSL provides equal transmission bit rates
for both the upstream and downstream directions ranging from 144 to 2320 kbps. SDSL
is based on use of the 2B1Q line coding scheme. 2B1Q-SDSL is a baseband line coding
scheme that does not allow the option to share the copper loop from a baseband POTS
signal.
....................................................................................................................................................................................................................................

T T/R
Transmit/Receive

TA
Terminal Adapter

Tagged Cell
A lower-priority cell, i.e., a cell whose CLP bit is set to 1. A cell may be tagged by the
system because it violates the traffic contract on its connection or by its source.

TAP
Test access path - Two metallic test access paths, one consisting of two pairs (TAP-B)
and the other of six pairs (TAP-A), provide both internal and external metallic test
access to the ports and drops of the application packs.

TAP-B
Test Access Path B

TAP10x
Test Application Pack - TAP10x (that is TAP100, TAP100B, or TAP101) is the internal
test head executing the measurements required for the drop.

TC
TAP Connected

TCA
Threshold Crossing Alert

TCP/IP
Transmission control protocol/Internet protocol - The combination of a network and
transport protocol developed by ARPANET for internetworking IP-based networks.

TDM
Time Division Multiplexing

TE
Terminal Equipment

TELNET
A remote terminal interface protocol which allows remote login capability into a system
on a network from any other node on that network that is also running TELNET.
TELNET is a TCP/IP application.

Terminating call
Terminating call is the type of call initiated at the network side of the network user
interface. It comprises the build-up, speech and the tear-down phase. For a POTS call
for example it starts with a message from the LE to the AnyMedia ® Access System to
seize a given subscriber and to supply ringing current.

Test session
A test session is the procedure including all necessary functions to test a subscriber. This
includes the setup of the test path as well as the release of the test equipment. The test
session runs in the AnyMedia ® Access System.

Threshold crossing alert

A threshold is a value assigned by the system user to a certain desired level (for
example errored seconds); when the level is exceeded, a threshold crossing alert is
issued.

TID
Target Identifier

Tier 2 NMS
A generic term for a network management system (NMS) that can manage multiple kinds
of network elements as a connected network. Tier 3 refers to element managers and Tier
1 refers to customer service support systems.

Timeslot
See TS.

Timeslot number
A timeslot number identifies a timeslot of 64 kbps within the 2048-kbps V5.x link. The
range shall be 1 to 31. It may be used as a bearer channel, communication channel or
protection physical channel. Timeslot 0 is reserved and not used for the purposes
described above.

Timeslot sequence integrity

The assurance that the digital information contained in the n timeslots of a multislot
connection arrives at the output in the same sequence as it was introduced.

TL1
Transaction Language 1 - A Bellcore standard message language. It is the primary means
of operating and maintaining the AnyMedia ® Access System. A TL1 message session
supports bidirectional message transmission and when a TL1 link is established, the
system can initiate autonomous messages to monitor alarms and changes in system
status. This is the message protocol used on the EMS and CIT interfaces.

TL1 defaults
Transaction Language 1 defaults - TL1 defaults are the parameter values built into the
AnyMedia ® Access System when it is shipped from the factory. A TL1 default parameter
for example stands for none given TL1 parameters.

TL1 interface
Transaction Language 1 interface - The message interface which is based on TL1 and
used by the operator for system input and output on the EMS and CIT interfaces.

TL1SI
TL1 System Interface

TN
TN is the synonym for a power distribution system having one point directly earthed, the
exposed conductive parts of the electrical installation are connected to that point by
protective earth conductors.

Total system downtime

Downtime during which the entire system (or, NE) is out of service. This includes all
failure modes that result in a service outage of greater than 50 milliseconds. Failure
modes that may result in a total system outage often include the synchronization or
timing packs, cross-connect matrices, and matrix power supplies.

TRAP
An autonomous report in the simple network management protocol (SNMP), sent out by
a network element towards an SNMP network manager, indicating an exceptional event.

TRG
Tip-wire for Ringing Voltage

Trunk processing
The act of placing a call processing finite state machine in a null state. The connection
between the subscriber and the network interface is disconnected and an idle pattern is
sent towards the subscriber.

TS
Timeslot - Any cyclic time interval that can be recognized and defined uniquely. For
example a 64-kbps channel of a V5 interface that can be used either as bearer channel
(carrying subscriber payload information) or as communication channel (carrying both
subscriber and network element signaling information).

TSC
Test System Controller

TSI
Timeslot interchanger - This is a switch able to route any timeslot on the subscriber side
to any timeslot on the feeder side and vice versa. There is a limited loopback capacity
for cross-connections on either subscriber or feeder side.

TST
Test active (a secondary service state) - Test is in progress (TAP10x/LPZ200).

TT
TT is the synonym for a power distribution system having one point directly earthed, the
exposed conductive parts of the electrical installation are connected to a local earth.

Turn-up
The process of bringing the system or a system component to an operational state (it
includes HW and SW installation as well as self diagnostics). After that the system can
be provisioned for service and other operational functionality.
....................................................................................................................................................................................................................................

U U activated only
Only the access transmission system (ATS) is activated. The U line signal is
synchronized and the transmission of maintenance bits over the U interface is possible.
The S/T interface is not activated.

UADSL
Universal Digital Subscriber Line (G.lite, splitterless DSL)

UART
Universal Asynchronous Receiver/Transmitter

UAS
Unavailable Second

UAT
Unavailable Time

UBR
Unspecified Bit Rate

UDT
Unstructured Data Transfer

UEQ
Unequipped (a secondary service state) - The hardware is not present.

UGLL
An unstructured 2 Mbps digital leased line service via G.703 interface. This interface is
provided by means of an NTU which is the far end equipment of an HDSL link.

ULL
Unstructured Leased Line

Unavailability
In general, steady-state unavailability is defined as the fraction of time that the system is
not available, or equivalently as the average downtime per year. Unavailability is often
expressed in minutes per year of downtime. In engineering applications, unavailability is
frequently expressed in terms of its complement, that is the availability. For a digital
channel, unavailability or downtime begins when the first 10 consecutive severely error
seconds (SESs) occur, and it ends when the first of 10 consecutive non-SESs occur.

Unavailable time
A digital transmission channel is considered unavailable, or in a complete downtime
condition, when its error performance falls below a given threshold. According to
Recommendation G.821, a period of unavailable time begins when the bit error rate
(BER) in each second is worse than 10 -3 for a period of 10 consecutive seconds. These
10 seconds are considered unavailable time.The unavailable time is counted from the
first faulty (severely error) second in the sequence. The period of unavailable time
terminates when the BER in each second is better than 10 -3 for a period of 10
consecutive seconds.

Unbundling
Connections to multiple switches from a single AnyMedia ® Access System. Every switch
can be owned by a different provider, then the AnyMedia ® Access System subscribers
can be connected to several providers.

UNI
User network interface - The point at which the user accesses the network.

Universal termination unit

A universal termination unit (UTU) is an HDSL line termination unit, which can be used
as LTU or NTU. The default configuration for an UTU is NTU.

Unknown provisioning variants

All provisioning variant labels, which are not the active or standby provisioning variant
label.

Unprotected configuration
No protection pack is provisioned.

Unspecified bit rate (UBR)

An ATM service category where traffic is allocated whatever bandwidth is available at
any given time. UBR does not have a pre-connection negotiated bandwidth and there are
no guarantees in terms of cell loss rate and delay.

Unstructured leased line

An unstructured leased line provides no byte and timeslot information for the 2Mbps
bitstream. The whole 2Mbps is considered as an continuos bitstream (see also structured
leased line).

Unstructured mode
The data stream is defined by the bit rate only. There exists no knowledge about certain
frames or timeslots within the data stream.

UPC
Usage Parameter Control

Upload
A binary data transfer from the AnyMedia ® Access System to the GSI.

UPP
Unstructured Point-to-Point

UPPS
Unstructured Point-to-Point Single pair

Upstream
The bitstream direction from the NT towards the network.

Upstream direction
Transmission direction from customer to ATM network or telephony switch.

Upstream VP
In a daisy chain, a VP that is passed through to a shelf that is closer to the ATM
transport network than the shelf being addressed. ″Upstream″ here does not refer to the
direction of transmission. Upstream VPs are not provisioned in an AFM, but are
recorded in it to help prevent errors in provisioning daisy chains.

User failure
A user failure (UF) Is a failure within the transmission path at the user side. After a
failure happened, a ″Block message″ is sent via V5 interface to the LE. Afterwards the
failure/failure combination is analyzed and mapped to either a network failure or user
failure and reported via V5 interface to the LE. See also network failure.

User identifier (login)

A unique character string consisting of up to 20 alphanumeric characters (ASCII) used
by the system to identify a particular person or user.

User security class

Refers to the different user groups, each assigned with certain system access privileges.

User timeslots
Those timeslots which are to be seen at the G.703 application interface at the NTU. It
depends on the HDSL application mode how the HDSL logical timeslots which are
provisioned by a certain service are mapped to the user timeslots. The use of these user
timeslots depends on the service. For an ISDN PRA they may be used for example as
bearer channels or timeslot 16 as D64 signaling channel. See also HDSL application
...................................................................................................................................................................................................................................
363-211-586 GL-73
Issue 6, July 2007
Glossary

mode.

User-to-network interface (UNI)

The point at which the user accesses the network.

USM
User Service Manual

UTU
Universal Transmission Unit

UVLL
Unstructured 2 Mbps leased lines service via V.35, V.36 or X.21 interface

UVLL service
An unstructured 2 Mbps digital leased line service via V.35, V.36 or X.21 interface. This
interface is provided by means of an NTU which is the far end equipment of an HDSL
link.

U interface
A 2-wire digital subscriber interface. It is used for connection of NT equipments and
will carry digital signals. In addition the U interface must provide the DC feeding of
NTs.

U port
Refers to the devices and functions built on or provided by an ISDN AP to support
ISDN BRA or DLL service. The U ports can be distinguished between 2B1Q and 4B3T
U ports. 12 2B1Q U ports are housed on one LPU112, 16 4B3T U ports are housed on
one LPU430.
....................................................................................................................................................................................................................................

V V3 ISDN PRA service

Integrated services digital network primary rate access service via V3 interface -
Connects ISDN PRA subscribers via V3 interface to the network. A V3 ISDN PRA
service has 32 timeslots of one E1 port located on an IO_E1 pack.

V3PP
V3 Point-to-Point

V3PPS
V3 Point-to-Point Single pair

V5.x interface
An ETSI defined interface between a local exchange and an access network element. A
V5.1 interface consists of one single 2-Mbps (E1) link containing communication and
bearer channels. A V5.2 interface consists of up to sixteen 2-Mbps (E1) links containing
communication and bearer channels. The term V5.x interface is used for clarification
that certain facts, a certain description or requirements are relevant for both V5.1 and
V5.2 interface.

V5DLaddr
V5 data link address - A V5DLaddr is an address used in the LAPV5-DL frames to
identify different V5-data link sublayer connections, each of them used to support a
particular V5.x-layer 3 protocol (for example PSTN protocol, control protocol). It is
present in every LAPV5-DL frame and is a direct copy of the EFaddr. The V5DLaddr
field has been included within the LAPV5 frames for structural compatibility with other
protocols (for example recommendations Q.920 and Q.921).

Validity of a peripheral image

A peripheral image is determined to be valid if it is not corrupted and it’s SW version
matches with those stored in the COMDAC for the pack type concerned (applies only to
active images).

Variable bit rate (VBR)

A service category that supports variable bit rate data traffic with average and peak
traffic parameters.

VBR
Variable bit rate

VC
Virtual channel - One of several logical connections defined within a virtual path (VP)
between two ATM devices; provides sequential, unidirectional transport of ATM cells.

VC CEP
Virtual channel connection end point - A point located at the boundary between the VC
level and the AAL where the level service is provided to the AAL or to the management
plane. A VC CEP provides the VC-connection termination functions.

VCC
Virtual Channel Connection

VCI
Virtual channel identifier - A field within the ATM cell header that provides a unique
identifier for the virtual channel (VC) within a virtual path (VP) that carries a particular
cell stream.

VF
Voice Frequency

Virtual channel connection (VCC)

The sum of all the unidirectional virtual channel links traveled by an ATM payload from
its originating point to its user destination

Virtual connection
A connection between end-users in which data may be passed over various circuit
configurations during a single period of communication. Virtual circuits are generally set
up on a per-call basis and are disconnected when the call is terminated.

Virtual ISDN port

A functionality located in COMDAC which terminates layer 2 and layer 3 ISDN
protocols transported via the ROC support D-channel. The Virtual ISDN port is
responsible for (de-)establishing the ISDN dial-up ROC.

VLL
n × 64 kbps leased lines service via V.35, V.36 or X.21 interface

VLL service
An n × 64 kbps digital leased line service via V.35, V.36 or X.21 interface (n=1, ..., 31).
This interface is provided by means of an NTU which is the far end equipment of an
HDSL link.

Voltage dips
Voltage dips are short voltage reductions or fluctuations.

Voltage gaps
Voltage gaps are short voltage interruptions.

VP
Virtual path - A unidirectional logical connection between two ATM devices; consists of
a set of virtual channels (VC). The VCs are associated by a common identifier value, the
virtual path identifier (VPI).

VPC
Virtual Path Connection

VPI
Virtual path identifier - A field within the ATM cell header that indicates the virtual path
(VP) to which a cell belongs.

VPT
Virtual path termination - An entity located at the boundary between the VP level and
the VC level where the level service is provided to the VC level or to the management
plane. A VPT provides the VP-connection termination functions. The standards call this
point virtual path connection end point (VP CEP).

VPTGrp
Virtual Path Termination Group
....................................................................................................................................................................................................................................

W WAN
Wide area network - A network that operates over a large region and commonly uses
carrier facilities and services.

Wander
Long-term noncumulative variations of the significant instants of a digital signal from
their ideal positions in time.

Warm start
Recovery of the AFM due to a soft reset or a SW upgrade with database evolution. For
all other types of AFM recovery a cold start applies. In both cases the user will be
informed by a status condition report.

WaveStar ADM 4/1

Compact and cost-effective SDH multiplexer. The WaveStar ADM 4/1 (former product
designation ADM 155 C) can be used in different configurations such as terminal
multiplexer, add/drop multiplexer and repeater, and can be used in the dual terminal
mode. It has a wide range of tributary interfaces. The WaveStar ADM 4/1 multiplexes 2,
34, 45 Mbps, and STM-1 signals into an STM-1 or STM-4 line signal. Cross-connects
can be made at VC-12 level.

WRR
Weighted Round-Robin
....................................................................................................................................................................................................................................

X xDSL
Refers to a variety of DSL services, such as HDSL, HDSL2, SDSL, SHDSL, and ADSL.

Z Z interface
A 2-wire analog subscriber interface. It is used for connection of analog subscriber lines
and will carry signals such as speech, voice-band analog data and multi-frequency push
button signals, etc. In addition the Z interface must provide the DC feeding of
subscriber’s terminal and ordinary functions such as DC signaling, ringing, metering,
etc., where appropriate (see ITU Q.551 2.1.1).

Z port
A Z port is circuitry built on a POTS AP to provide a Z interface for analog
subscribers. Note that more than one Z port is housed on an AnyMedia ® Access System
POTS AP, for example the LPZ100 provides 32 Z ports.

Numerics ADSL-lite Alarm classification, 4-28

1+1 MSP mode, 6-180 Interface, 2-22 Alarm output relays, 3-106
10BaseT LAN interface, 2-15 ADSL2 / ADSL2+ Alarm reporting and
For ATM xDSL services, retrieval, 3-108, 4-33
Interface, 2-22
2-28 Application pack fault LED
ADSL2/ADSL2+
............................................................. behavior, 4-10
DELT test, 4-38
Common alarms, 3-92
A AC voltage measurement, 3-122
Forced power state, 4-39
Equipment alarms, 3-93,
Access security, 3-172
SELT test, 4-39 4-28
Administrative state, 6-90
AFMDS3 External alarm collector
Admissible bandwidth, 6-58 box, 2-18, 3-102
Work order, A-1
ADSL Facility alarms, 3-99, 4-28
AFME1
ADSL interface transmission Host terminal interface,
Work order, D-1
specifications, 6-144 3-100
AFME3
ADSL modem self-test, 4-38 IMA group/link alarms,
Work order, B-1 4-29, 6-151, 6-152
ADSL-lite, 1-23
AFMO Local alarm and status
ADSL2, 1-23
Work order, C-1 indicators, 3-107
ADSL2+, 1-23
Alarm collector box, 2-18, Miscellaneous alarm inputs,
Full-rate ADSL, 1-23 3-102
3-102
Interface, 2-22 Remote terminal interface,
Alarm interfaces, 2-18
POTS + ADSL with LPZ110 3-100
Alarms via external alarm
and LPA432, 5-36 Remote terminal link, 3-100
collector box, 2-18, 3-102
POTS to ADSL upgrade, Alarms and events, 3-90, 4-27
Local alarm and status
6-35
indicators, 2-18 Analog leased line service, 1-11
Predefined ADSL port
Miscellaneous alarm closure AnyMedia ® ETSI V5 Shelf
failure report profiles,
inputs, 2-18
6-139 Ringer configuration, 5-91
Office alarm outputs, 2-18
Technology, 1-23 AnyMedia ® LAG 4300 Shelf
Alarm signaling paths, 3-101
Transmission rates, 6-100, Ringer configuration, 5-90
6-100 Alarms
AP port
ADSL over ISDN, 6-39 ACO function, 3-106
Protection, 3-63

Apparatus Code, 4-20 ATM security management, Blocking probability, 5-19

4-73
Applications Busy hour call attempt
ATM traffic statistics, 4-68 (BHCA), 5-43
Mixed services, 1-17
Connection-level, 4-68 .............................................................
AP_E1 link faults on SHDSL
AP, 3-96 Shelf level, 4-68 C CAC, 6-14
Asymmetric subscriber line ATM xDSL Connection admission
Metallic drop testing, 6-205 Configuration options, 1-17 control, 6-56

ATM Installation and connection Initialization control, 6-56

recommendations, 6-27 Call capacity evaluations, 5-43,
Cell transfer, 1-17
Interfaces, 2-20 5-43
Connections, 4-13
Port numbering, 6-52 Capacitance measurement,
Feeder, 6-159 3-123
Providing services, 1-18
Network failure reporting, Capacity
4-34 Services, 1-16
ADSL2_32i (LPA438), 6-11
System planning and Shelf cascading via E1-IMA
engineering, 6-159 APs, 6-83 E1-IMA AP, 6-10

Traffic profiles, predefined, Shelf cascading via E1IMA Narrowband system

6-65 AP, 1-21 capacity, 5-11

ATM cell traffic Status conditions, 4-27 Remote terminal

applications, 5-6, 5-9, 5-13
ATM traffic statistics, 4-68 System capacity, 6-5, 6-6
System capacity ETSI V5
ATM configuration System powering, 6-204 Shelf, 5-11
management, 4-3
ATM xDSL performance System capacity LAG 1900
ATM connections, 4-13 management, 4-51 Shelf, 5-5
Cross-connect provisioning, ADSL performance System capacity LAG 4300
4-13 management, 4-60 Shelf, 5-8
Inventory management, 4-20 ATM traffic statistics, 4-68 CBR, 1-20, 6-72
Memory administration, 4-4 E1-IMA performance ATM traffic parameters,
management, 4-67 6-111
Pack provisioning, 4-12
Feeder performance Cell delay variation, 6-60
Port provisioning, 4-12
management, 4-52
Service activation, 4-7 Cell loss priority, 6-65
SHDSL performance
Shelf daisychaining, 4-19 management, 4-65 Cell loss ratio, 6-59

Shelf provisioning, 4-8 ............................................................. Cell tagging, 6-65

Shelf VPI, 4-14 Cell transfer delay, 6-60

B Bandwidth
Software management, 4-5 CIT port, 2-14
Admissible bandwidth, 6-58
Turn-up, 4-7 CLEI, 4-20
Guaranteed bandwidth, 6-59,
ATM fault management, 4-23 6-62 Clock synchronization, 3-49,
6-194, 6-196, 6-198, 6-201
Alarms and events, 4-27 BB ATM Operations Channel,
2-29 COMDAC
Maintenance, 4-24
Interfaces for ATM xDSL Duplex mode, 3-56
ATM payload loopbacks, 4-47 services, 6-50
Protection, 3-56
...................................................................................................................................................................................................................................
IN-2 363-211-586
Issue 6, July 2007
Index

COMDAC load measurement, Connection admission control, Special considerations,

3-166 6-14, 6-56 6-181
Common alarms, 3-92 Provisioning cross-connects, DC voltage measurement,
6-67 3-122
Configuration data
Console port Default parameters, 6-116
ALL services, 5-57
For ATM xDSL services, Degrowth scenarios
DLL services, 5-63
2-27
Degrowth from mixed
ISDN BRA services, 5-62
CPE, xx ISDN/POTS to
n × 64 kbps GLL services, POTS-only, 5-17
Interfaces, 2-24
5-81
Migrating from duplex to
CPE routing - remote access to
n × 64 kbps VLL services, simplex AFM mode, 6-25
CPEs, 4-49
5-82
Narrowband services, 5-16
Craft interface terminal port,
POTS services, 5-56
2-14 Removing an ATM xDSL
UGLL services, 5-83 AP, 6-23
Cross-connect provisioning,
UVLL services, 5-84 4-13 Removing ATM xDSL
services from a shelf, 6-23
V3 ISDN PRA services, Customer configuration, 4-10
5-80 DELT test, 4-38
Customer documentation, xxi
V5 ISDN PRA services, Detection of faults, 4-24
How to order, xxiii
5-79
Digital leased line service
.............................................................
Configuration limits affecting
Via HDSL, 1-12
the system traffic, 5-45 D Daisy-chaining
Via U interface, 1-11
Configuration management, 3-5, Local shelf daisy-chaining,
4-3, 4-3 1-33 Distance to open measurement,
3-124
ROC, 3-36 Remote shelf daisy-chaining
via SDH ring, 1-34 DMT symbols per
ROC for remote terminal,
Reed-Solomon codeword,
3-37 Daisychaining, 4-19 6-102
Configuration options Daisychaining capability, Double board single fiber
ATM xDSL, 1-17 6-165, 6-177 protection mode, 4-36, 6-180,
Mainshelf addition, 6-20 6-181
Customer configuration,
4-10 Provisioning, 6-62 Daisy-chaining, 6-181
Configurations Database management, 3-8, 4-4 Feeder loopback, 4-44
Mixed shelf configuration, Dataset extension, 3-45 Protection status, 6-94
1-26
DBSF mode, 6-180, 6-180 Double board single fibre
With V5.1 interfaces, 5-23 mode
DBSF protection mode, 4-36
With V5.2 interfaces, 5-25 DBSF mode, 6-180, 6-180
Daisy-chaining, 6-181
Congestion management, 1-25 Downtime, 5-93
Daisychaining, 6-182
Congestion management Draw and break dial tone test,
schemes, 6-70 DBSF mode, 6-180 3-126
Connection admission Feeder loopback, 4-44 DS3 feeder, 6-161
Initialization control, 6-56 Protection status, 6-94 Duplex mode, 6-163, 6-167

Migrating from duplex to Migrating from simplex to Fault management, 3-84, 4-23,
simplex AFM mode, 6-25 duplex AFM mode, 6-24 4-23
Simplex mode, 6-162 Migrating from simplex to Customer configuration,
duplex AFM mode in 4-10
DTMF, pulse character or
daisy-chain, 6-24
register recall (hook flash) Detection, 4-24
test, 3-127 Engineering
Isolation strategy, 4-24
Duplex 1+1 protection mode, BB ATM Operations
Loopback tests for ATM
4-36, 6-180, 6-180 Channel for shelves
xDSL services, 4-45
cascaded via E1IMA APs,
Feeder loopback, 4-44
6-40 Proactive maintenance, 4-25
Protection status, 6-93
Mixed POTS/ISDN Recovery, 4-25
Duplex mode configuration, 5-26 Reporting, 4-25
COMDAC, 3-56 PLLs, 5-33 Testing, 4-37
............................................................. POTS + ADSL service, 5-36 Flexible rate adaptation, 6-100
E E1 feeder, 6-170 POTS-only configurations, Forced power state, 4-39
5-19
E1 interface, 5-85 Free-running mode, 3-49, 3-51
Engineering for ADSL over
E1 interface on E1IMA AP, ISDN AFME1, 6-196
2-23
ISDN to ADSL, 6-39 AFME3/DS3, 6-164, 6-194
Network side, 2-3
Environmental alarms, 2-18, AFMO, 6-198
Remote terminal link, 1-15, 3-102
2-11 Function Code, 4-21
Equipment alarms, 3-93 .............................................................
E1-IMA cascading, 1-21
Equipment Catalog Item, 4-21
E1IMA AP, 6-109 G Growth scenarios
Explicit rate adaptation, 6-100
Predefined E1 port failure ATM xDSL services, 6-18
report profile, 6-140 Extension of dataset, 3-45
Mainshelf addition
Predefined IMA group External alarm collector box, (daisy-chain), 6-20
failure report profile, 6-141 2-18, 3-102
Mainshelf addition
Predefined IMA link failure External synchronization mode, (standalone), 6-20
report profile, 6-140 3-49
Mainshelf expansion, 6-20
E1IMA AP settings, 6-109 .............................................................
Migrating from simplex to
E3 feeder, 6-161 F F4/F5 cells duplex AFM mode, 6-24

Daisychaining capability, Initiating loopbacks, 4-45 Narrowband services, 5-16

6-165 Pack upgrade, 6-20
Reporting AnyMedia ®
Duplex mode, 6-163, 6-167 Access System failures to Shelf cascading via E1-IMA
the ATM transport network, APs, 6-21
Migrating from duplex to
4-33
simplex AFM mode, 6-25 Guaranteed bandwidth, 6-59,
F4/F5 loopbacks, 4-45 6-62
Simplex mode, 6-162
Failure report profiles .............................................................
E3/DS3 feeder
See: Profiles
Migrating from duplex to H HDSL
simplex AFM mode in
AP fault conditions, 3-95
daisy-chain, 6-25
Application modes, 5-69
...................................................................................................................................................................................................................................
IN-4 363-211-586
Issue 6, July 2007
Index

Interface, 2-9, 5-66 Interleave depth, 6-102 DC voltage measurement,

3-122
Interface fault conditions, Interoperability, 6-34
3-95 Distance to open
Inventory data, 3-78, 4-20
measurement, 3-124
Network termination units,
Inventory management, 3-77,
5-67 Feeding voltage
4-20
measurement for LPU430,
Transmission range, 5-66
IO_E1 (FAC500B) 3-122
.............................................................
Protection, 3-61 Insulation resistance
I IMA, 1-20 measurement, 3-123
IO_HDLC (IDC500B)
Applications, 1-20 Memory administration, 4-4
Protection, 3-59
Loopback test, 4-42 Metallic drop testing, 6-205
IP address, 3-81
Tx clocking modes, 6-196 MIB, 4-65
ISDN BRA service, 1-4
IMA applications, 1-20 Migrating from duplex to
ISDN PRA service, 1-4, 1-9
simplex AFM mode, 6-25
Inband messages Isolation strategy, 3-86, 4-24
See: BB ATM Operations Migrating from simplex to
............................................................. duplex AFM mode, 6-24
Channel
Insulation resistance L Latency, 6-102 Miscellaneous alarm closure
measurement, 3-123 inputs, 2-18
Leased line service, 1-14
Interchangeability Code, 4-20 Mismatch of provisioning
Line loopbacks, 3-142
between host and remote
Interface configurations, 5-53 Logical feeder port, 6-85 terminal, 3-40
Interfaces Loop timed mode, 3-49 Mixed services applications,
AnyMedia ® ETSI V5 Shelf Loopbacks, 3-142, 4-47, 4-48
1-17
interfaces, 2-1 Moving subscribers between
LPU430
ATM feeder and xDSL interfaces (Dual homing),
interfaces, 2-20 Feeding voltage 3-47
measurement, 3-122
ATM feeder interfaces, 2-21 ............................................................
.............................................................
Narrowband interfaces, 2-3 N Nailed-up IP-routed ROC, 3-38
M Main shelf miscellaneous
OAM&P interfaces for ATM Nailed-up leased line link
information, 4-11
xDSL services, 2-26 timeslot ROC, 3-38
Main shelf type, 4-11
OAM&P interfaces for Narrowband performance
narrowband services, 2-13 Mainshelf addition, 6-20, 6-20 management, 3-157
Service interfaces, 2-3 Mainshelf expansion, 6-20 Performance management
Service interfaces for ATM data, 3-160
Maintenance, 3-86, 4-24
xDSL services, 2-22 Performance management
Managed NTU provisioning
Service interfaces for operations, 3-162
data, 5-64
narrowband services, 2-3 V5.2 protocol error
Management capabilities, 3-172
Synchronization interfaces logging, 3-163
Measurement
for ATM xDSL services, NB to ADSL upgrade, 6-35
2-25 AC voltage measurement,
Non-switched services, 1-11,
3-122
Synchronization interfaces 1-14
for narrowband services, Capacitance measurement,
2-12 3-123
...................................................................................................................................................................................................................................
363-211-586 IN-5
Issue 6, July 2007
Index

nrt-VBR, 1-20, 6-72 Performance management Predefined SHDSL

narrowband, 3-157 transmission profiles,
ATM traffic parameters,
6-132
6-111 Performance management
operations, 3-160, 3-162 Transmission effect on
NT1 detection test, 3-132
quality of service, 6-64
Performance management
NTU
parameters, 3-160 Protection switching, 3-54,
Configuration data, 5-67 4-35, 6-180
V5.2 protocol error logging,
Fault condition, 3-94 3-163 1+1 MSP mode, 6-180
Inventory data, 3-83 Physical data label, 3-79, 4-21 AFM, 4-35
Provisioning, 3-42 Physical feeder port, 6-85 Characteristics, 3-75
NVDS, 4-4 Port numbering, 6-52 COMDAC, 3-54
NVPS, 4-5 Port provisioning, 4-12 DBSF mode, 4-36, 6-180
............................................................. POTS service, 1-4 Duplex 1+1 protection
mode, 4-36, 6-180, 6-180
O OAM&P, 4-49 Powering, 6-204
IO_E1, 3-54
OAM&P management, 2-13, Proactive maintenance, 3-88,
2-26, 4-1 4-25 IO_HDLC, 3-54

Ordering Product reliability, 5-92, 6-203 STM-1/OC-3c feeder

facility, 4-35
Ordering Guide for the Profiles, 6-96
AnyMedia Access System, Synchronization source for
Effect on quality of service,
xxii ATM xDSL, 4-35
6-64
Overbooking factor, 6-69 Synchronization sources NB,
MIB, 4-65
3-54
Overload control, 5-52 Performance management,
V5.2 communication
............................................................. 6-134
channels, 3-54
P Pack provisioning, 4-12 Predefined ADSL port
Provisioning
failure report profiles,
Pack upgrade, 6-20 6-139 Analog leased lines, 3-23
Parity bytes per Reed-Solomon Predefined ATM traffic Customer configuration,
codeword, 6-102 profiles, 6-135 4-10
Peak cell rate, 6-57 Predefined ATM traffic Daisychaining, 6-62
Performance management ATM profiles for ADSL, 6-135
Digital leased lines, 3-24
xDSL, 4-51 Predefined ATM traffic
ISDN BRA subscriber, 3-16
ADSL performance profiles for SHDSL, 6-135
Main shelf miscellaneous
management, 4-60 Predefined E1 port failure
information, 4-11
ATM traffic statistics, 4-68 report profile, 6-140
Main shelf type, 4-11
E1-IMA performance Predefined IMA group
failure report profile, 6-141 Mismatch between host and
management, 4-67
remote terminal, 3-40
Feeder performance Predefined IMA link failure
report profile, 6-140 Model, 3-31
management, 4-52
Predefined SHDSL port n × 64 kbps leased lines,
SHDSL performance
failure report profiles, 3-26
management, 4-65
6-139 POTS subscriber, 3-15

Provisioning a rt-VBR, 1-20 Reporting, 4-25

cross-connect, 6-67
Shelf overbooking factor, Strategy, 3-87
Quality of service, 6-55 6-57
Ringing Generator Pack
Shelf cascading via E1-IMA Shelf peak cell rate, 6-57, (RGP100)
APs, 6-83 6-62
Protection, 3-66, 3-73
Unstructured leased line Traffic profiles, predefined,
ROC for remote terminal, 3-38
subscriber via AP_E1, 3-30 6-65
rt-VBR, 1-20, 6-72
Unstructured leased line Traffic shaping, 6-72
subscriber via IO_E1, 3-28 ATM traffic parameters,
UBR, 1-20
6-111
V3 ISDN PRA subscriber,
VP, 6-113
3-19 RTU
xDSL transmission profiles,
V5 ISDN PRA subscriber, Application pack test
6-64
3-17 access capabilities, 3-155
.............................................................
Provisioning and service ............................................................
activation, 3-11, 6-116 R Rate adaptation
S Security management, 3-171,
Provisioning mismatch, 3-40 Explicit, 6-100, 6-107 4-73
PSDM, 6-102 Flexible, 6-107 SELT test, 4-39
............................................................. Re-provisioning scenario Sending a test tone for POTS
CPE, 3-128
Q QoS Extension of dataset, 3-45
Serial Number, 4-20
Congestion management Moving subscribers between
schemes, 6-70 interfaces (Dual homing), Service activation, 3-11, 4-7,
3-47 6-81, 6-116, 6-116
Quality of service
Recovery, 4-25 ATM ADSL services
Admissible bandwidth, 6-58
flowchart, A-6, A-35, B-6,
Strategy, 3-88
ADSL transmission profile, B-36, C-7, C-37, D-6
6-64 Reference loads, 5-42, 5-42
ATM SDSL services
ATM functions, 1-24 Related documentation, xxi flowchart, A-6, A-35, B-6,
Release upgrade B-36, C-7, C-37, D-6
CBR, 1-20
Release upgrade, 6-19 ATM SHDSL services
Cell delay variation, 6-60
flowchart, A-6, A-35, B-6,
Cell loss priority, 6-65 Remote operations channel B-36, C-7, C-37, D-6
(ROC), 2-16, 2-17, 3-36
Cell loss ratio, 6-59 Parameters for duplex
ROC for remote terminal, AFMDS3, A-39
Cell tagging, 6-65
3-37
Parameters for duplex
Cell transfer delay, 6-60
Remote semipermanent V5.2 AFME3, B-40
Data priority, 6-72 ROC, 3-38
Parameters for duplex
Guaranteed bandwidth, 6-59, Remote terminal AFMO, C-41
6-62 interconnection, 1-15
Parameters for simplex
nrt-VBR, 1-20 Remote terminal link, 1-15, AFMDS3, A-14
2-11
Overbooking factor, 6-69 Parameters for simplex
Reportable database changes, AFME1, D-14
Provisioning, 6-55
3-82, 4-21
Provisioning a Parameters for simplex
cross-connect, 6-67 AFME3, B-15
...................................................................................................................................................................................................................................
363-211-586 IN-7
Issue 6, July 2007
Index

Parameters for simplex Main shelf miscellaneous ATM xDSL sychronization

AFMO, C-15 information, 4-11 and timing for E1, 6-196
Service provisioning, 3-11 Main shelf type, 4-11 ATM xDSL sychronization
and timing for E3/DS3,
Service state Overbooking factor, 6-57
6-194
Administrative state, 6-90 Provisioning, 4-8
ATM xDSL sychronization
Service state model, 3-34 Shelf peak cell rate, 6-62 and timing for
STM-1/OC-3c, 6-198,
Services, 1-2 Virtual path identifiers, 4-14
6-201
Non-switched services, 1-11, VPI, 4-14
E1IMA AP, 6-200
1-14
Shelf cascading via E1-IMA
External from composite
Remote terminal APs, 6-83
clock signal, 3-50
interconnection, 1-15
Shelf cascading via E1IMA
External from DCS signal,
ROC, 3-36 APs, 6-109
3-50
ROC for remote terminal, Shelf virtual path identifiers,
External from DOTS E1
3-37 4-14
signal, 3-50
V3 switched services, 1-9, Shelf VPI, 4-14
Fault conditions, 3-51
1-10
SNR margin, 6-102
Free-running mode, 3-51,
V5.x switched services, 1-4,
Software management, 3-9, 4-5 6-194, 6-196, 6-198
1-6
SPALL service, 1-4 Loop timed, 3-49
SHDSL
SPDLL service, 1-5 Protection, 3-50
AP fault conditions, 3-95
Status conditions, 4-27 Source protection, 3-57
Application modes, 5-74
STM-1/OC-3c feeder, 6-174 System capacity, 6-5, 6-6
ATM payload loopbacks,
4-47 Daisychaining capability, ETSI V5 Shelf, 5-11
6-177
CPE routing - remote access System degrowth, 5-16
to CPEs, 4-49 Duplex mode, 6-180
System growth, 5-16, 6-18
Interface, 2-23 Migrating from duplex to
System planning and
simplex AFM mode, 6-25
Interface fault conditions, engineering
3-95 Migrating from duplex to
ADSL interface transmission
simplex AFM mode in
Network termination units, specifications, 6-144
daisy-chain, 6-25
5-67
ADSL over ISDN, 6-39
Migrating from simplex to
Payload bit rate range, 5-66
duplex AFM mode, 6-24 ATM xDSL installation and
Predefined SHDSL port connection
Migrating from simplex to
failure report profiles, recommendations, 6-27
duplex AFM mode in
6-139
daisy-chain, 6-24 ATM xDSL turn-up and
SHDSL loopback test, 4-48 service provisioning
Subscriber loop dimensioning,
scenarios and parameters,
Technology, 1-23 5-58
6-74
Transmission rates, 6-107 Switched services, 1-6, 1-7,
Engineering the LAN
1-9, 1-10, 1-16
SHDSL loopback test, 4-48 connection, 6-45
Synchronization, 2-12
Shelf External test head testing,
ATM xDSL APs, 6-200 6-205
Cell loss ratio, 6-59

Integrated testing, 6-205 Narrowband services, 3-10 Feeder loopbacks, 4-41,

4-41
Interface configurations, NB system turn-up, 3-10
5-53 Forced power state, 4-39
Parameters for duplex
Interoperability, 6-34 AFMDS3, A-27, A-29 Integrated test capabilities,
3-118
Manual testing, 6-205 Parameters for duplex
AFME3, B-28, B-30 Integrated testing, 3-115
Powering, 6-204
Parameters for duplex Integrated tests for analog
Product reliability ATM
AFMO, C-28, C-30 drops, 3-121
xDSL, 6-203
Parameters for simplex Loopback tests for ATM
Product reliability
AFMDS3, A-6 xDSL services, 4-45
narrowband, 5-92
Parameters for simplex Loopbacks, 3-141
System capacity, 5-11, 6-5,
AFME1, D-6
6-6 Loopbacks at the E1 link
Parameters for simplex side, 3-142
System planning, 5-3, 5-3
AFME3, B-6
Manual testing, 3-115
Testing drops on ATM xDSL
Parameters for simplex
APs, 6-205 Monitoring, 3-115, 3-155
AFMO, C-7
xDSL data transfer On-demand tests using
.............................................................
performance, 6-15 integrated capabilities,
T Target identifier (TID), 3-80 3-114
System turn-up
Test Ringing test for POTS
ATM configuration
CPE, 3-129
management, 4-7 Metallic drop testing, 6-205
SELT test, 4-39
ATM xDSL services, duplex Testing, 4-37, 4-38, 4-39, 4-39
AFMDS3, A-27, A-27, Sending a single pulse,
A-29, A-29 ADSL modem self-test, 4-38 3-131
ATM xDSL services, duplex ADSL port self test, 4-37 Sending of test tone for
AFME3, B-28, B-28, B-30, ATM payload loopbacks, POTS CPE, 3-128
B-30 4-47 SHDSL loopback test, 4-48
ATM xDSL services, duplex Bidirectional corrupt CRC Subscriber line test via
AFMO, C-28, C-28, C-30, testing, 4-38 external test head, 3-155
C-30
Built-in self tests, 3-109, Testing interfaces, 2-19
ATM xDSL services, 4-37
simplex AFMDS3, A-3, Testing requirements, 6-205
Circuit, 3-115
A-3 Wiring, 3-115
CRC tests for ISDN
ATM xDSL services, Tests using integrated
application packs, 3-130
simplex AFME1, D-3, D-3 capabilities, 3-114
DELT test, 4-38
ATM xDSL services, Traffic engineering, 5-41,
simplex AFME3, B-3, B-3 Detection test of a test 5-41, 5-46
termination, 3-125
ATM xDSL services, Traffic shaping, 6-72
simplex AFMO, C-3, C-3 Draw and break dial tone
test, 3-126 Traffic statistics, 3-166
ATM xDSL turn-up and
service provisioning DTMF, pulse character or Traffic values, 5-46
scenarios and parameters, register recall (hook flash) Transmission profiles
6-74 test, 3-127 See: Profiles
Default parameters, 6-116 Tx clocking modes, 6-196
...................................................................................................................................................................................................................................
363-211-586 IN-9
Issue 6, July 2007
Index

............................................................. Voltage measurement

U U interface, 2-6 AC, 3-122

ISDN BRA and DLL DC, 3-122

services, 5-61 VP quality of service, 6-113
UBR, 1-20, 6-72 VPI, 4-13
ATM traffic parameters, .............................................................
6-111
W Work order
Universal transmission unit
(UTU), 5-67 AFMDS3, A-1

Unstructured leased line service AFME1, D-1

Network side, 1-14 AFME3, B-1

Subscriber side, 1-13 AFMO, C-1

Upgrade .............................................................

ISDN to ADSL, 6-39 Z Z interface, 2-4

POTS to ADSL, 6-35, 6-37
Usage parameter control, 1-24
.............................................................

V V3

ISDN PRA service, 1-9

Switched services, 1-9, 1-10
V5
Frame relaying, 3-21
ISDN PRA service, 1-4
Parameters, 5-89
Re-provisioning, 3-44
V5.1
Call capacity data, 5-43
Switched services, 1-6, 3-12,
3-13
V5.2
Call capacity data, 5-43
Communication channel
protection, 3-58
Switched services, 1-7, 3-12,
3-13
VCI, 4-13
Virtual connections, 4-13

Programarea Centralei Tel PDF
100% (1)
Programarea Centralei Tel PDF
417 pages
1850 TSS 320 1850 TSS 160 R 4 1 Ce
No ratings yet
1850 TSS 320 1850 TSS 160 R 4 1 Ce
1,772 pages
3HH-11287-BAAA-TQZZA-04-System Description For FD 100 - 320Gbps NT and FX NT R4 - 5 - X
No ratings yet
3HH-11287-BAAA-TQZZA-04-System Description For FD 100 - 320Gbps NT and FX NT R4 - 5 - X
706 pages
BS en 20898-1-1992
100% (4)
BS en 20898-1-1992
26 pages
Memco 450 857 GB Memcom Reference Manual
100% (1)
Memco 450 857 GB Memcom Reference Manual
18 pages
Software Patterns Made Easy
From Everand
Software Patterns Made Easy
Justice Nanhou
No ratings yet
AnyMedia Access System PDF
No ratings yet
AnyMedia Access System PDF
382 pages
The Linux Terminal for Advanced Users - The Command Line Made Easy: First Edition
From Everand
The Linux Terminal for Advanced Users - The Command Line Made Easy: First Edition
Michael Basler
No ratings yet
IHub Interface Guide
No ratings yet
IHub Interface Guide
66 pages
Alcatel-Lucent 1830 PSS CPB
No ratings yet
Alcatel-Lucent 1830 PSS CPB
148 pages
3HE10380AAADTQZZA - V1 - 7210 SAS M T MXP SX OS Quality of Service Guide (Release 8.0R6)
No ratings yet
3HE10380AAADTQZZA - V1 - 7210 SAS M T MXP SX OS Quality of Service Guide (Release 8.0R6)
494 pages
Es-16 r2.6 CT Operator HB
No ratings yet
Es-16 r2.6 CT Operator HB
594 pages
MS3600plus r9
No ratings yet
MS3600plus r9
2 pages
ALU BSS Portfolio Presentation - v3
No ratings yet
ALU BSS Portfolio Presentation - v3
89 pages
Turn-Up and Comissioning R32
No ratings yet
Turn-Up and Comissioning R32
214 pages
Top30003r2 0 SG en Ul PDF
100% (1)
Top30003r2 0 SG en Ul PDF
356 pages
3KC29562AAAATQZZA - V1 - 1850 Transport Service Switch 5R (TSS-5R) Release 4.0 Installation and System Turn-Up Guide PDF
No ratings yet
3KC29562AAAATQZZA - V1 - 1850 Transport Service Switch 5R (TSS-5R) Release 4.0 Installation and System Turn-Up Guide PDF
234 pages
ALU Manual
No ratings yet
ALU Manual
886 pages
MPR Configuration File Management PDF
No ratings yet
MPR Configuration File Management PDF
190 pages
1662smc 2.7 Oper - HDBK - Ed04
No ratings yet
1662smc 2.7 Oper - HDBK - Ed04
580 pages
8DG61258GAAATBZZA Vol1 Alcatel-Lucent 1830 Photonic Service Switch PSS Release 7.0 Commissioning and Power Balancing Too
No ratings yet
8DG61258GAAATBZZA Vol1 Alcatel-Lucent 1830 Photonic Service Switch PSS Release 7.0 Commissioning and Power Balancing Too
156 pages
Isa-Es16 2.5 Oper - HDBK - Ed05
100% (1)
Isa-Es16 2.5 Oper - HDBK - Ed05
560 pages
Alcatel Telecom Product Catalogue 1998
100% (1)
Alcatel Telecom Product Catalogue 1998
49 pages
Alcatel-Lucent 9353: Title Page
No ratings yet
Alcatel-Lucent 9353: Title Page
30 pages
7750 SR 9.0 Product Overview CE
No ratings yet
7750 SR 9.0 Product Overview CE
54 pages
5529 APC Release 9.3.10 Installation and Customization Guide PDF
No ratings yet
5529 APC Release 9.3.10 Installation and Customization Guide PDF
92 pages
SAM IP-MPLS Service Provisioning PDF
No ratings yet
SAM IP-MPLS Service Provisioning PDF
152 pages
1646 PDF
No ratings yet
1646 PDF
244 pages
02 5060 MGC10 System Description - 3FL12593ACAAWBZZA - 02c
No ratings yet
02 5060 MGC10 System Description - 3FL12593ACAAWBZZA - 02c
154 pages
1354rm-Phm r7 5 SRD 8dg60488aaaafmzza
0% (1)
1354rm-Phm r7 5 SRD 8dg60488aaaafmzza
55 pages
Hilti
No ratings yet
Hilti
36 pages
Dslam Manual - An2000b 100
No ratings yet
Dslam Manual - An2000b 100
2 pages
Brocas Nachi
No ratings yet
Brocas Nachi
83 pages
Victor EDGE Outfits & Regulators Range Brochure (65-1104) - Mar2011l
No ratings yet
Victor EDGE Outfits & Regulators Range Brochure (65-1104) - Mar2011l
6 pages
5.1 Iso
No ratings yet
5.1 Iso
43 pages
1350 Installation Guide
100% (1)
1350 Installation Guide
232 pages
Manual 5020MGC 01 04
No ratings yet
Manual 5020MGC 01 04
51 pages
AEG Cross Reference
No ratings yet
AEG Cross Reference
2 pages
Sanitary Installation Material
No ratings yet
Sanitary Installation Material
5 pages
Rectangular Connectors: FCN360 Series
No ratings yet
Rectangular Connectors: FCN360 Series
32 pages
Triple-Lok 37° Flared Tube Fittings: Fluidconnectors
No ratings yet
Triple-Lok 37° Flared Tube Fittings: Fluidconnectors
51 pages
Extension Forces 10 N To 100 N: End Fitting Standard Dimensions End Fitting
No ratings yet
Extension Forces 10 N To 100 N: End Fitting Standard Dimensions End Fitting
9 pages
Victor EDGE Outfits & Regulators Range Brochure (65-1104) - Mar2011l
No ratings yet
Victor EDGE Outfits & Regulators Range Brochure (65-1104) - Mar2011l
6 pages
Printcom Uv Lamp 101Z TDS en
No ratings yet
Printcom Uv Lamp 101Z TDS en
2 pages
Manual 5020MGC 04 04
No ratings yet
Manual 5020MGC 04 04
54 pages
7600 SERIES 4 de 4
No ratings yet
7600 SERIES 4 de 4
73 pages
Manual 5020MGC 02 04
No ratings yet
Manual 5020MGC 02 04
51 pages
Alcatel 7510
No ratings yet
Alcatel 7510
154 pages
3 Parte Manual 3900 Series HardInstGuide
No ratings yet
3 Parte Manual 3900 Series HardInstGuide
40 pages
Ece512 2nd Exam Topics Telephony1
No ratings yet
Ece512 2nd Exam Topics Telephony1
55 pages
BSNL Services
No ratings yet
BSNL Services
3 pages
Panasonic: Panasonic KX-TA624 / 824 Telephone System
No ratings yet
Panasonic: Panasonic KX-TA624 / 824 Telephone System
4 pages
Ewsd Platform
No ratings yet
Ewsd Platform
20 pages
AN2000 MSAN Presentaation
No ratings yet
AN2000 MSAN Presentaation
23 pages
Introduction To Cryptography
No ratings yet
Introduction To Cryptography
34 pages
Mobile Telephone Number Codes For India
No ratings yet
Mobile Telephone Number Codes For India
13 pages
Avaya IP Office Platform Solution Description - En-Us
No ratings yet
Avaya IP Office Platform Solution Description - En-Us
154 pages
Surallah 1 Memo Sports Meeting
No ratings yet
Surallah 1 Memo Sports Meeting
3 pages
Mitel 420 430
No ratings yet
Mitel 420 430
10 pages
Connectivity Screening Form
No ratings yet
Connectivity Screening Form
3 pages
Quick Start Guide Cisco 7911 IP Telephone: More User Manuals On
No ratings yet
Quick Start Guide Cisco 7911 IP Telephone: More User Manuals On
18 pages
Interworking of IP Telephony With Legacy Networks
No ratings yet
Interworking of IP Telephony With Legacy Networks
12 pages
JA-63k-User Manual
No ratings yet
JA-63k-User Manual
8 pages
SS7 Probe Advanced Configuration: Golan Elmadvi Professional Technical Services
No ratings yet
SS7 Probe Advanced Configuration: Golan Elmadvi Professional Technical Services
30 pages
EOW
No ratings yet
EOW
24 pages
sn2400 Datasheet
No ratings yet
sn2400 Datasheet
2 pages
1
No ratings yet
1
3 pages
DTMF/TouchTone Tele-Controller (TeleSwitch)
100% (1)
DTMF/TouchTone Tele-Controller (TeleSwitch)
1 page
SV9100 Programming Manual 9.0
No ratings yet
SV9100 Programming Manual 9.0
992 pages
MOBILE ETIQUETTES Notes
No ratings yet
MOBILE ETIQUETTES Notes
4 pages
PSTN and ISDN
No ratings yet
PSTN and ISDN
29 pages
Best Western Asia PABX Guideline: Revision April 2019
No ratings yet
Best Western Asia PABX Guideline: Revision April 2019
8 pages
crystal-inspire-308 (1)
No ratings yet
crystal-inspire-308 (1)
2 pages
Marketing Strategy of MTNL: Presented by Hareram Kumar ENR-15033 Sec-A (Marketing)
No ratings yet
Marketing Strategy of MTNL: Presented by Hareram Kumar ENR-15033 Sec-A (Marketing)
59 pages
Tveli
No ratings yet
Tveli
18 pages
Voip 2 GSM
No ratings yet
Voip 2 GSM
46 pages
Tekelec SIP Sigmnaling
No ratings yet
Tekelec SIP Sigmnaling
28 pages

Manual Anymedia

Uploaded by

Manual Anymedia

Uploaded by

AnyMedia® Access System

See “How to order” (p. xxiii).

About this information product

Reason for reissue ................................................................................................................................................................... xvii

Intended audience ................................................................................................................................................................ xviii

Conventions used ................................................................................................................................................................... xviii

Related documentation ........................................................................................................................................................... xxi

How to order ........................................................................................................................................................................... xxiii

How to comment .................................................................................................................................................................... xxiv

Overview ...................................................................................................................................................................................... 1-1

Overview ...................................................................................................................................................................................... 1-2

Overview ...................................................................................................................................................................................... 1-3

V5.x (switched) services / Subscriber side .................................................................................................................... 1-4

V5.x (switched) services / Network side ........................................................................................................................ 1-6

V3 switched services / Subscriber side ........................................................................................................................... 1-9

V3 switched services / Network side ............................................................................................................................ 1-10

Non-switched services / Subscriber side ...................................................................................................................... 1-11

Non-switched services / Network side .......................................................................................................................... 1-14

Host/remote terminal interconnection service ............................................................................................................ 1-15

ATM xDSL-based services and configurations

Overview ................................................................................................................................................................................... 1-16

ATM xDSL services ............................................................................................................................................................. 1-17

Quality of service for ATM xDSL services ................................................................................................................ 1-24

Configuration options for the ATM xDSL subsystem ............................................................................................ 1-26

Daisychaining of AnyMedia ® LAG Shelves ............................................................................................................... 1-32

Local shelf daisychaining ................................................................................................................................................... 1-33

Remote shelf daisychaining via SDH ring ................................................................................................................ 1-34

Overview ...................................................................................................................................................................................... 2-1

Physical interfaces related to narrowband services

E1 interface (network side) .................................................................................................................................................. 2-3

Z interface (subscriber side) ................................................................................................................................................ 2-4

U interface (subscriber side) ................................................................................................................................................ 2-6

HDSL interface (subscriber side) ...................................................................................................................................... 2-9

Physical E1 interface (remote terminal link) .............................................................................................................. 2-11

Synchronization interfaces for narrowband services ............................................................................................... 2-12

OAM&P interfaces for narrowband services ............................................................................................................. 2-13

Craft interface terminal port .............................................................................................................................................. 2-14

10BaseT LAN interface ...................................................................................................................................................... 2-15

Remote operations channel (ROC) ................................................................................................................................. 2-16

Remote operations channel (ROC) for remote terminal ........................................................................................ 2-17

Alarm interfaces ..................................................................................................................................................................... 2-18

Testing interfaces ................................................................................................................................................................... 2-19

Physical interfaces related to ATM xDSL services

ATM feeder and xDSL interfaces ................................................................................................................................... 2-20

ATM feeder interfaces ......................................................................................................................................................... 2-21

ATM xDSL interfaces .......................................................................................................................................................... 2-22

CPE Interfaces ........................................................................................................................................................................ 2-24

Synchronization interfaces for ATM xDSL services ............................................................................................... 2-25

ATM OAM&P interfaces for xDSL services ............................................................................................................. 2-26

Console port ........................................................................................................................................................................... 2-27

10BaseT port ............................................................................................................................................................................ 2-28

BB ATM Operations Channel ........................................................................................................................................... 2-29

Communication with the AFM over the ROC .......................................................................................................... 2-30

ATM xDSL CPE interfaces ............................................................................................................................................... 2-32

3 OAM&P for narrowband services

Overview ...................................................................................................................................................................................... 3-1

Overview ...................................................................................................................................................................................... 3-5

Configuration management .................................................................................................................................................. 3-7

Database management ............................................................................................................................................................ 3-8

Software management ............................................................................................................................................................ 3-9

System turn-up ........................................................................................................................................................................ 3-10

Provisioning and service activation ................................................................................................................................ 3-11

POTS subscriber ..................................................................................................................................................................... 3-15

ISDN BRA subscriber .......................................................................................................................................................... 3-16

V5 ISDN PRA subscriber .................................................................................................................................................. 3-17

V3 ISDN PRA subscriber .................................................................................................................................................. 3-19

V5 frame relaying (ISDN) ................................................................................................................................................. 3-21

POTS/ISDN operation modes ........................................................................................................................................... 3-22

Analog leased lines ............................................................................................................................................................... 3-23

Digital leased lines ................................................................................................................................................................ 3-24

N × 64 kbps leased lines .................................................................................................................................................... 3-26

Unstructured leased line subscriber via IO_E1 ......................................................................................................... 3-28

Unstructured leased line subscriber via AP_E1 ........................................................................................................ 3-30

Provisioning model ............................................................................................................................................................... 3-31

Service state model ............................................................................................................................................................... 3-34

Remote operations channel (ROC) ................................................................................................................................. 3-36