DSL Expresse

User Interface Guide

http://www.assia-inc.com/

2012 ASSIA, Inc. Adaptive Spectrum and Signal Alignment, Inc. (ASSIA) is the owner of this publication (the
Copyrighted Material). You are permitted to use the Copyrighted Material subject to the following conditions: ASSIAs
Copyrighted Material must be used solely for you and/or your companys informational purpose, and not resold or
transferred in any way with or without consideration to any third party. No Copyrighted Material may be copied,
reproduced, republished, uploaded, downloaded, duplicated, broadcast, posted, transmitted, or otherwise distributed
without ASSIAs prior written authorization, except that you may retain one electronic copy of the Copyrighted Material on
any single computer for your individual use only. PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Page 2 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Executive Summary

This user guide describes the graphical user interface (GUI) of DSL Expresse . The GUI provides
access to DSL service analysis and optimization. Specifically, the GUI includes the following
analysis and reporting features:
Per Line
o Line Summary
o Performance Analysis
o Real-Time Performance Analysis
o Diagnostics Analysis
o Real-Time Diagnostics Analysis
o Single-ended Line Testing (SELT) Diagnostics Analysis
o Profile Optimization Recommendations (scheduled and real-time)
o Historical Data Trends
o Service Product Recommendations
o Multiple Line Comparison

Per Neighborhood
o Overview of DSL Performance
o Summary of Performance and Diagnostics of all lines in the neighborhood
o Address-based pre-qualification

Per DSLAM
o Summary of Performance and Diagnostics of all lines in DSLAM

Reports
o Statistics and results of the Diagnostics Analysis
o Statistics and results of the Profile Optimization process
o Reconciliation for current data in DSL Expresse
o Network Statistics
o Dynamic Reports

Ability to search DSL Services by phone number/line ID, DSLAM and/or neighborhood.
Tools to allow each GUI user to manage their profile.
Administrative tools to manage DSLAM and lines in DSL Expresse.
Administrative tools to manage all user accounts in DSL Expresse.
Administrative tools to monitor the DSL Expresse overall system and individuals modules.
Important note: ASSIA plans a major upgrade of the GUI for Releases 3.3 and 3.5. Changes are
expected for both the functionality and the look-and-feel. This transition shall be closely
coordinated with current DSL Expresse customers.

ASSIA, Inc. Confidential and Proprietary Page 3

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Revision History
Part Date Comments
PD-E1-0103-01-00-0000-03 N/A First version
PD-E1-0103-01-09-0000-01 N/A Updated document to reflect most recent
changes and content.
PD-E1-0103-01-09-0001 June 16, 2009 Changed version to correct numbering
Updated with new changes:
Compare lines
Zoom in Line Performance Analysis page
Drop-down boxes in PE detail
Menu updates for direct access to PE
Detail page
PD-E1-0103-01-11-0001 September 8, 2009 Added following new features:
Service Recommender
Real-Time Analysis
Updated Diagnostics and PO reports
Minor modifications to other sections
related to syntax or content clarification.
PD-E1-0103-01-13-0001 April 19, 2010 GUI enhancements
Line summary
Pre-qualification
PD-E1-0103-02-01-0001 October 22, 2010 GUI enhancements
VDSL support
Bonding support
Network Statistics
PD-E2-0103-02-03-0001 April 15, 2011 ADSL Per Tone support
Neighborhood analysis support
Real-time PE
Updated for R2.3
PD-E2-0103-02-05-0001 October 6, 2011 Dynamic Reports, Service
Recommendation, Historical Data trends, ,
Per Line Diagnostics Analysis, Per
DSLAM Diagnostics Analysis, Per
Neighborhood Diagnostics Analysis,
Comparison of Multiple Lines.
PD-E2-0103-07-00 March 28, 2012 Added descriptions for the following:
Real-time PO
SELT Diagnostics Analysis
New diagnostics flags for time-variation

Page 4 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

flags and missing micro-filter

Made updates for the real-time
performance analysis and real-time
diagnostics pages, including options for
including performance and per-tone
parameters
PD-E3-0103-01-00 October 15, 2012 Added descriptions for the following:
G.INP support
Vectoring support
Enhancements to dynamic reporting

ASSIA, Inc. Confidential and Proprietary Page 5

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Abbreviations, Acronyms and Symbols

DBLoader Database Loader (DSL Expresse module)
DcPc Data Collection and Profile Change (DSL Expresse module)
G.inp ITU-T Recommendation G.998.4 (G.inp)
GUI Graphical User Interface
kbps Kilo (1000) bits per second
NAPI Northbound API (DSL Expresse module)
PE Performance Evaluator (DSL Expresse module)
PO Profile Optimizer (DSL Expresse module)
UIWS User-Interface Web-Services
UI User Interface

Page 6 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Contents
Executive Summary ......................................................................................................................... 3
Revision History ............................................................................................................................... 4
Abbreviations, Acronyms and Symbols ........................................................................................... 6
Introduction ...................................................................................................................................... 9
1 User Access ........................................................................................................................... 11
1.1 Login Screen..................................................................................................................... 11
1.2 Navigating the GUI ........................................................................................................... 11
1.3 User Account Management .............................................................................................. 13
1.3.1 View Account Profile ............................................................................................ 13
1.3.2 Change Profile ..................................................................................................... 14
1.3.3 Change Password ............................................................................................... 15
1.4 Logout ............................................................................................................................... 15
2 Analysis .................................................................................................................................. 16
2.1 Search Interface ............................................................................................................... 17
2.2 Line Summary................................................................................................................... 18
2.3 Line Performance Analysis ............................................................................................... 27
2.4 Real-Time Line Performance Analysis ............................................................................. 33
2.5 Diagnostics Analysis ......................................................................................................... 37
2.6 Real-Time Diagnostics Analysis ....................................................................................... 43
2.7 SELT Diagnostics Analysis ............................................................................................... 44
2.8 Historical Data Trends ...................................................................................................... 48
2.9 Lines in the DSLAM .......................................................................................................... 51
2.10 Lines in the Neighborhood ......................................................................................... 56
2.10.1 Specifying a neighborhood search ...................................................................... 56
2.10.2 Pre-defined neighborhood search ....................................................................... 62
2.10.3 Neighborhood search results .............................................................................. 64
2.10.4 Neighborhood Analysis........................................................................................ 69
2.11 Profile Optimization.................................................................................................... 76
2.12 Compare Lines .......................................................................................................... 83
2.13 Service Recommendation.......................................................................................... 84
3 Reports ................................................................................................................................... 88
3.1 Diagnostics ....................................................................................................................... 89
3.1.1 Statistics Report .................................................................................................. 89
3.1.2 Detail Report ........................................................................................................ 92
3.2 Profile Optimization .......................................................................................................... 93
3.2.1 Statistics Report .................................................................................................. 93
3.2.2 Detail Report ........................................................................................................ 94
3.2.3 Active Requests ................................................................................................... 95
3.2.4 Completed Requests ........................................................................................... 96
3.3 Reconciliation File ............................................................................................................ 97
3.4 Network Statistics ............................................................................................................. 99
3.5 Dynamic Reports ............................................................................................................ 100
3.5.1 Manage Reports ................................................................................................ 101
3.5.2 Generated Reports ............................................................................................ 110
4 Administration ....................................................................................................................... 112
4.1 Identity Management ...................................................................................................... 112
4.1.1 User/Role Overview........................................................................................... 112
4.1.2 Manage Users ................................................................................................... 112
4.1.3 Manage Roles ................................................................................................... 117
4.2 System Health ................................................................................................................ 121
4.2.1 Module Status .................................................................................................... 121
4.3 Provisioning .................................................................................................................... 123
4.3.1 DSLAM Provisioning .......................................................................................... 123
4.3.2 Line Provisioning ............................................................................................... 124

ASSIA, Inc. Confidential and Proprietary Page 7

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

5 Data Report Fields ............................................................................................................... 126

Page 8 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Introduction

This user guide describes the graphical user interface (GUI) of DSL Expresse . The GUI provides
access to DSL service analysis and optimization. Specifically, the GUI includes the following
analysis and reporting features:
Per Line
o Line Summary
o Performance Analysis
o Real-Time Performance Analysis
o Diagnostics Analysis
o Real-Time Diagnostics Analysis
o Single-ended Line Testing (SELT) Diagnostics Analysis
o Profile Optimization Recommendations (scheduled and real-time)
o Historical Data Trends
o Service Product Recommendations
o Multiple Line Comparison

Per Neighborhood
o Overview of DSL Performance
o Summary of Performance and Diagnostics of all lines in the neighborhood
o Address-based pre-qualification

Per DSLAM
o Summary of Performance and Diagnostics of all lines in DSLAM

Reports
o Statistics and results of the Diagnostics Analysis
o Statistics and results of the Profile Optimization process
o Reconciliation for current data in DSL Expresse
o Network Statistics
o Dynamic Reports

Ability to search DSL Services by phone number/line ID, DSLAM and/or neighborhood.
Tools to allow each GUI user to manage their profile.
Administrative tools to manage DSLAM and lines in DSL Expresse.
Administrative tools to manage all user accounts in DSL Expresse.
Administrative tools to monitor the DSL Expresse overall system and individuals modules.

Important note: ASSIA plans a major upgrade of the GUI for Releases 3.3 and 3.5. Changes are
expected for both the functionality and the look-and-feel. This transition shall be closely
coordinated with current DSL Expresse customers.

ASSIA, Inc. Confidential and Proprietary Page 9

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

This document is divided into the following five main sections:

Section 1 - (User Access)
This section provides information on accessing and using the DSL Expresse GUI application
using a Web browser from the operator's network. It provides information on managing the users
account, including changing the user profile and password.
Section 2 - (Analysis Interfaces)
This section provides a detailed overview of each analysis-related screen in the GUI.
Each section provides an example of the particular Web page as seen by a user, an explanation
of all data fields that can be entered by the user and all data fields that are returned by DSL
Expresse.
Section 3 - (Report Interfaces)
This section goes over the various types of reports that are available in DSL Expresse for each of
the analysis features. In addition, any fields or data displayed are more thoroughly defined in
Section 5, Data Fields.
Section 4 - (Administration Interfaces)
This section provides details on the Administration management of the DSL Expresse GUI. This
includes creation, modification and deletion of user accounts, role management, permission
assignments and overall and per module system monitoring.
Section 5 - (Data Fields)
This section contains a table that defines all displayed data fields in any of the screens. Each field
has a row in the table. The columns indicate the name of the field and a description of the
meaning of the values.

Page 10 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

1 User Access
1.1 Login Screen
Login requires a user name and password.

The default account user name and password shipped with DSL Expresse are:
User Name: administrator
Password: assia
ASSIA recommends either removing this account or changing the password.
The user name and initial password should be created and assigned by the operators DSL
network operations center or IT department. Contact the same for forgotten credentials or
difficulty logging in.
Several languages are supported in DSL Expresse. To choose a language, select the appropriate
flag before logging into the system. The default language is English.

1.2 Navigating the GUI

After login, all screens display a menu bar at the top. Selecting a menu item opens a new screen
or menu.

ASSIA, Inc. Confidential and Proprietary Page 11

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Detailed Description:
My Account: The users name is displayed on upper right corner of the screen after
Welcome as a link. Clicking it opens the View Profile screen.
Analysis: By selecting Analysis, the user is placed at the Analysis screen. Sub-menus
provide direct access to each of the following Analysis screens:
o Line Summary
o Line Performance Analysis
o Real-Time Line Performance Analysis
o Diagnostics Analysis
o Real-Time Diagnostics Analysis
o SELT Diagnostics Analysis
o Historical Data Trends
o Lines in the DSLAM
o Lines in the Neighborhood
o Profile Optimization Analysis
o Compare Lines
o Service Recommendation
Reports: Places the user at the Reports screen. Sub-menus provide direct access to each of
the following Reports screens:
o Diagnostics Summaryt
Statistics Report
Detail Report
o Profile Optimization
Statistics Report
Detail Report
Active PO Requests
Completed PO Requests
o Reconciliation File
o Network Statistics
o Dynamic Reports
Manage Reports
Generated Reports
Administration: Selecting a sub-menu under Administration, places the user at one of the
following screens:
o Identity Management
User/Role Overview
Manage Users
Manage Roles
o System Health
Module Status
o Provisioning
DSLAM Provisioning
Line Provisioning

Page 12 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Logout: Exits DSL Expresse and returns to the Login screen.

Help: Displays an online index of help topics.

1.3 User Account Management

To view or change personal account information, the user clicks the users name displayed as
underlined on the upper right corner of the screen. This section describes the various screens
related to account management.

1.3.1 View Account Profile

This screen displays the current account information. Users see this screen when they click on
the users name displayed as underlined on the upper right corner of the screen.

Detailed Description:
User Name: The users account User Name.
First name: The users first name.
Last name: The users last name.
E-mail: The users email address.
Phone number: The users phone number.
The user can modify their account information or change their password.
Selections:
To make changes to the above information, the user selects Change Profile and is placed at
the Change Profile screen.
To change account password, the user selects Change Password and is placed at the
Change Password screen.

ASSIA, Inc. Confidential and Proprietary Page 13

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

1.3.2 Change Profile

This screen allows the user to modify DSL Expresse account information.

Detailed Description:
Selecting Change Profile from the View Profile screen, places the user at the screen shown
above. The current account information is displayed and some of the fields can be modified to
display new information.
User Name: This field cannot be changed.
First name: The users first name.
Last name: The users last name.
E-mail: The users email address.
Phone number: The users phone number.
Selections:
Save: The new information is saved and the user is placed back at the View Profile screen
where the new profile information is displayed.
Cancel: The transaction is terminated without changes and the user is placed back at the
View Profile screen.

Page 14 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

1.3.3 Change Password

This screen allows a user to change their DSL Expresse account password. It is displayed by
selecting Change Password from the View Profile screen.

Detailed Description:
User Name: This field cannot be changed.
Old password: This field is automatically populated with the users old password.
New password: The user enters their new password here.
Confirm new password: The user must re-enter their new password here
Selections:
Save: If the new password is legal and matches the Confirm New Password field, the
password is changed and the user is placed back at the View Profile screen. If the new
password is not legal for any reason, an error message is produced and the user is prompted
to enter the correct information.
Password rules are operator dependent, but some possible password errors are as follows:
Password is too short. Passwords must be at least six characters.
Password must include characters from different predefined character sets (example:
numbers, lower case, upper case and special characters).
Password cannot contain the user name.
Previously used passwords cannot be used again.
Password must be significantly different from previously used passwords.

1.4 Logout
Selecting Logout above the navigation menu bar logs the user out of DSL Expresse and displays
the Login screen.

ASSIA, Inc. Confidential and Proprietary Page 15

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

2 Analysis
Data collected by DSL Expresse can be easily displayed by Line ID, DSLAM or neighborhood.
This section describes how collected data can be accessed and interpreted through the DSL
Expresse GUI. When the user successfully logs into DSL Expresse they are placed at the Search
screen.

Line Summary: Entering a valid Line ID and selecting Submit places the user at the Line
Summary Page screen where the DSL Expresse summary of the lines stability and rate are
displayed. If the Line ID is invalid because it is not found in the database, the user is placed at the
Line Summary Page screen and receives an error alert to submit a valid Line ID.
Note: Line ID is operator-dependent and can be anything from a unique line identifier to a
customers real telephone number.

Search by Line ID: Entering a valid Line ID and selecting Submit places the user at the Line
Performance Analysis screen and displays the DSL Expresse analysis for that particular line. If
the Line ID is invalid because it is not found in the database, the user is placed at the Line
Performance Analysis screen and receives an error alert to submit a valid Line ID.
Note: Line ID is operator dependent and can be anything from a unique line identifier to a
customers real telephone number.

Search by DSLAM: Entering a valid DSLAM name and selecting Submit places the user at the
Lines in the DSLAM screen and displays the analysis of lines served by that particular DSLAM. If
the DSLAM name is invalid because it is not found in the database, the user is placed at the
Lines in the DSLAM screen and receives an error alert to submit a valid DSLAM name.

Page 16 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Search by Neighborhood: Entering a valid Line ID and selecting Submit places the user at the
Lines in the Neighborhood screen and displays the analysis for all lines in the same
neighborhood as the one identified by the provided Line ID. If the Line ID is invalid because it is
not found in the database, the user is placed at the Lines in the Neighborhood screen and
receives an error alert to submit a valid Line ID.
Note: The definition of a neighborhood is operator dependent. Example of neighborhoods are
lines on the same street with similar street numbers (difference smaller than 100), or lines with
the same zip-code, or lines sharing cable segments.

2.1 Search Interface

Many of the screens in the DSL Expresse GUI contain the following search field.

This field is used when performing specific searches for Line ID or DSLAMs based on exact
criteria or using wildcards. When the user clicks on the magnifying glass on the right side of the
search box, the following screen appears where various search criteria can be selected or
entered.

The current wildcard character supported is: %

When a search is performed, a list of results is displayed.
For queries that allow only a single result to be selected, this result can be selected by
double-clicking.
For queries that allow multiple results to be selected:
o If the desired results are located on the same page, select the check box next to the
result and then click Select and Close. This collects the lines selected and displays them.
o If the desired results are located on different pages, then use the following steps:
1. On the current results page, mark the check box next to the desired results and then
click Select.
2. To view other pages, click Next Page or Previous Page.
3. On these new pages, again mark the check box next to the desired results. If more
selections are necessary, click Select.and then move to the new page.
4. For the last set of desired results, click Select and Close to capture all the previous
and current selected results. Results are displayed.

ASSIA, Inc. Confidential and Proprietary Page 17

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

2.2 Line Summary

This screen provides a summary of the status of a specific DSL line. Important note: With
Release 3.3 or 3.5, this page shall be replaced by an improved page containing
recommendations for corrective actions.

Page 18 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Detailed Description:
This screen displays a summary of the selected line status in terms of stability and rate. It shows
how the current rate of the line compares to the maximum service rate and whether the line is
operating stably at this rate. The page also provides the operator with recommendations for fixing
detected issues on the line.
Note: Various fields referenced below are defined with more detail in the section titled Data
Report Fields, which is located at the end of this document. For each field, the following
information is displayed: Field Name, Description and Usage, and Screens which contain the field.
Line Information:
Line ID: This field provides the identification information for the line information being
displayed. Line ID is operator dependent and can represent anything from a unique
identifying number to a real telephone number.
DSLAM: The name of the DSLAM in which the Line ID or DSL line is located.

ASSIA, Inc. Confidential and Proprietary Page 19

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Port: The logical port number in the DSLAM on which the particular service is supported. This
can be formatted in multiple ways, from shelf-slot-port (x-y-z) to rack-shelf-slot-port (w-x-y-z).
This field is DSLAM dependent.
Service Product: Indicates the service product that is provisioned on the line. Clicking on the
service product name produces a pop-up window that displays information about the
maximum rate, service recommendation rate and minimum rate of the service product for
both the downstream and upstream directions.
Line Status: Indicates the status of the line.
Links to related screens:
The following links navigate the user to various screens with information related to either the Line
ID or DSLAM that is currently being examined:
Line Summary | Line Performance Analysis | Real-Time Performance Analysis
Diagnostics Analysis | Real-Time Diagnostics Analysis | SELT Diagnostics Analysis | Historical Data Trends
Lines in the DSLAM | Lines in the Neighborhood | Profile Optimization Analysis | Service Recommendation
Line Summary: Places the user at this screen.
Line Performance Analysis: Places the user at the Line Performance Analysis screen,
which displays a performance analysis for the selected line using historical data.
Real-Time Performance Analysis: Places the user at the Real-Time Performance Analysis
screen, which displays a performance analysis for the selected line using real-time data.
Diagnostics Analysis: Places the user at the Diagnostics Analysis screen, which displays a
diagnostics analysis for the selected line using historical data.
Real-Time Diagnostics Analysis: Places the user at the Real-Time Diagnostics Analysis
screen, which displays a diagnostics analysis for the selected line using real-time data.
SELT Diagnostics Analysis: Places the user at the SELT Diagnostics Analysis screen,
which displays a diagnostics analysis for the selected line using real-time data.
Historical Data Trends: Places the user at the Historical Data Trends screen. This screen
allows the user to plot various attributes or the bit distribution for various timeframes.
Lines in DSLAM: Places the user at the Lines in the DSLAM screen, which displays a
summary of the performance and diagnostics analysis for all lines in the same DSLAM as the
selected line.
Lines in the Neighborhood: Places the user at the Lines in the Neighborhood screen,
which displays a summary of the performance and diagnostics analysis for all lines in the
same neighborhood as the selected line.
Profile Optimization Analysis: Places the user at the Profile Optimization Analysis screen,
which displays information related to the PO process for the selected line.
Service Recommendation: Places the user at the Service Recommendation screen, which
displays service product recommendations for the selected line.

Step1 - Stability and Rate

This section displays the status of the line in terms of stability and rate. A summary of the line
status is displayed in a color-coded status box at the top. The summary may report one of the
following problems associated with a line:
Stability problem

Page 20 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Downstream rate problem

Upstream rate problem
A warning message is displayed in the case of unknown status for stability or rate problems.
The color-coded status box uses the following colors to indicate a different warning level:
The box is displayed in green if no stability or rate problem is detected.
The box is displayed in yellow if one of the stability status or rate status is unknown due to
lack of data, and there is no problem detected for the other one. The box is also displayed in
yellow if both stability and rate status are unknown.
The box is displayed in red if either a stability problem or a rate problem is detected.
The line is declared to have a stability problem if any of the following conditions holds:
The latest stability analysis shows the line is UNSTABLE or VERY UNSTABLE.
The stability analysis over the past 10 days shows the line is UNSTABLE or VERY
UNSTABLE on average.
If there is not enough data for stability analysis (both items above are unknown), the line stability
status remains unknown.
The line is declared to have an upstream (US) or downstream (DS) rate problem if the latest data
rate or the average data rate over the past 10 days for the given direction satisfy at least one of
the following conditions:
The latest rate or the average rate is less than the service product minimum acceptable rate.
The latest rate or the average rate is less than the service product plan rate.
Note: The service product minimum acceptable rate and plan rate are fully configurable for each
service product and can be customized to meet different network and customer requirements.
If the data rate for the given direction is not available for the past 10 days (both items above are
unknown), the line rate status remains unknown.
More details on the stability and rate status are provided in the two tables below the status
summary in this section.

Stability: This table provides the stability analysis for the latest date and also over the past 10
days.
Table Data:
Average stability for the past 10 days: The line stability can be:
o VERY STABLE (mapped to 0)
o STABLE (mapped to 1)
o UNSTABLE (mapped to 2)
o VERY UNSTABLE (mapped to 3)
o UNKNOWN (mapped to 9)
The average stability is the average of stability values over the past 10 days on which the
stability is not UNKNOWN. The stability column is colored in yellow for UNSTABLE lines and
in red for VERY UNSTABLE lines.
Latest stability and date: The date of the latest stability analysis is also displayed in the table.
The stability column is colored in yellow for UNSTABLE lines and in red for VERY
UNSTABLE lines.

ASSIA, Inc. Confidential and Proprietary Page 21

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Selecting the Show chart link below the table displays a graph with the history of the stability
analysis of the line over the past 10 days.

Rate: This table provides the current rate, and MABR of the line for the latest date and also over
the past 10 days. If support for G.inp is enabled, and the line operates in G.inp mode then Daily
EFTR is also displayed.
Table Data:

Average rate for the past 10 days: The average current rate for the past 10 days is displayed
for both the upstream and downstream directions. The average rate column is colored based on
the following rules:
Red: average rate < service product minimum acceptable rate
Yellow: service product minimum acceptable rate <= average rate < service product plan
rate
Green: service product plan rate <= average rate
Average MABR for the past 10 days: The average MABR for the past 10 days is displayed for
both the upstream and downstream directions. The average MABR column is colored based
on the following rules:
Red: average MABR < service product minimum acceptable rate
Yellow: service product minimum acceptable rate <= average MABR < service product
plan rate
Green: service product plan rate <= average MABR
Note: For the upstream direction and for ADSL lines, the reported US MABR value from the
DSLAM is used for the analysis. For VDSL lines, the DSL Expresse estimated US MABR is
used. For the downstream direction, for both ADSL and VDSL lines, the DSL Expresse
estimated DS MABR is used for analysis.
Average Daily EFTR for the past 10 days: The average Daily EFTR for the past 10 days is
displayed for the downstream direction. The average Daily EFTR column is not currently
colored.
Latest rate and date: The latest available current rate and the corresponding date are
displayed for both the upstream and downstream directions. The latest rate column is colored
based on the following rules:
Red: latest rate < service product minimum acceptable rate
Yellow: service product minimum acceptable rate <= latest rate < service product plan
rate
Green: service product plan rate <= latest rate
Latest MABR and date: The latest available MABR and the corresponding date are displayed
for both the upstream and downstream directions. The latest MABR column is colored based
on the following rules:
Red: latest MABR < service product minimum acceptable rate
Yellow: service product minimum acceptable rate <= latest MABR < service product plan
rate
Green: service product plan rate <= latest MABR
Note: For the upstream direction and for ADSL lines, the reported US MABR value from the
DSLAM is used for the analysis. For VDSL lines, the DSL Expresse estimated US MABR is
used. For the downstream direction, for both ADSL and VDSL lines, the DSL Expresse
estimated DS MABR is used for analysis.

Page 22 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Latest Daily EFTR and date: The latest available Daily EFTR and the corresponding date are
displayed for the downstream direction. The average Daily EFTR column is not currently
colored.
Selecting the Show chart link below the table displays two graphs encompassing the history of
the rate and MABR values for both directions over the past 10 days.

Step 2 Profile Optimization

This section displays the status of profile optimization on the line. An informative summary of
profile optimization on the line is displayed in a color-coded status box at the top in the following
format:

Status Box:
Color: The profile optimization status is indicated by a color following the conventions below:
o The box is displayed in green if Step 1 indicates a stability or rate problem and a PO has
started on the line and has not completed yet.
o The box is displayed with no color for other cases. The PO status is indicated by
comments in the box as described below.
Comment: The comment in the box indicates
o Whether Profile Optimization has been enabled for this specific line.
o Whether Profile Optimization is currently in progress or completed for this specific line.
o When the last Profile Optimization was completed.
o The stability status of the line after profile optimization.

If the profile optimization has been enabled and completed on this line, the latest profile
optimization status is also displayed in the Last Optimization Record table.
Last Optimization Record
Table Data:
Request Date: Date when the PO was requested/kicked off.
Source of Request: Who or what requested the PO (examples are Call Center or New Line)
Completion Date: Date when the most recent PO process finished.
Status Code: Status of the most recent PO process upon completion. This outputs a number
which can then be correlated to a specific status definition. This definition displays in a pop-
up window when this field is populated.
Before and after stability and the average upstream and downstream data rates.
Selecting the link Click here to see Profile Optimization page places the user at the Profile
Optimization Analysis screen which displays complete information related to the PO process for
the selected line.

Step 3 Diagnostics
This section displays the diagnostics status of the line. A summary of diagnostics analysis of the
line is displayed in a color-coded status box at the top following the format below:
Status Box:

ASSIA, Inc. Confidential and Proprietary Page 23

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Color: The diagnostics results are indicated by a color following the conventions below:
o The box is displayed in red if Step 1 indicates a stability or rate problem and some
diagnostics faults are detected.
o The box is displayed with no color if there is no stability or rate problem detected in Step
1. Any detected diagnostics fault is indicated by the comment in the box.
Comment: The comment in the box indicates:
o Whether there is a fault detected on the line.
o The type of fault found on the line.
o The frequency of occurrence for the fault (the number times the fault was found)
o Technician dispatch recommendation and the likelihood that a dispatch can improve
stability and rate.
The fault types that are displayed in the box are explained in the following:
Bad-splice: It is declared if a Bad Splice is detected on the last date of diagnostics analysis or
detected for more than 25 percent of the time in the Bad Splice overall column in the
Diagnostics Analysis page.
Wiring defect: It is declared if at least one of High Power Noise, High Power Noise in High
Frequency (only for ADSL linesy) or Unbalanced Wiring is detected for more than 50 percent
of the time in the overall column, or at least two of them are detected for more than 25
percent of the time in the overall columns in the Diagnostics Analysis page.
Significantly low MABR compared to other lines with similar lengths: It is declared if a
Downstream MABR in the lowest 1 percent or Upstream MABR in the lowest 1 percent for
the given loop length is detected on the last date of diagnostics analysis or detected for more
than 25 percent of the time in the overall columns in the Diagnostics Analysis page.
Abnormal change in attenuation, MABR or impulse noise: It is declared if at least one of the
following degradation flags is detected on the last date of diagnostics analysis or detected for
more than 25 percent of the time in the overall columns in the Diagnostics Analysis page.
o Abnormal increase in US Attenuation (more than 5dB).
o Abnormal increase in DS Attenuation (more than 5dB).
o Abnormal decrease in US MABR (more than 40 percent).
o Abnormal decrease in DS MABR (more than 40 percent).
o Increase in Code Violations (increase in the number of 15 minute intervals with greater
than 500 Code Violations by a factor of five or more)
If a Bad-splice or a Wiring defect is detected, more details on the diagnostics analysis are
provided in a table below the summary box.
Table Data:
Detected faults: Summarizes the problems detected on the line. A brief description for the
faults is provided as a pop-up window when clicking on the information button next to the
detected fault.
Typical impact: Displays the typical impact of the detected problem on stability, US and DS
data rates.
Possible fixes by field technicians: Provides guidelines to field technician for fixing the
detected problems.
Selecting the link Click here to see Diagnostics Analysis page places the user at the
Diagnostics Analysis screen which displays complete diagnostics related data for the selected
line.

Page 24 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Bonded Lines
For a bonded line, the line information lists the ports that form the bonded group (constituent
ports) as shown below.

ASSIA, Inc. Confidential and Proprietary Page 25

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

A summary of the line status is displayed in a color-coded status box at the top of the stability and
rate section, and has the same format as in the unbonded case with the following modifications:
The bonded line is declared to have a stability problem if any of the following conditions hold:
o The latest stability analysis shows that any of the constituent ports within the bonded
group is UNSTABLE or VERY UNSTABLE
o The stability analysis over the past 10 days shows that any of the constituent ports within
the bonded group is UNSTABLE or VERY UNSTABLE on average.
o If there is not enough data for stability analysis on any constituent port within the bonded
group, the stability analysis for the bonded group is unknown.
The line is declared to have an US or DS rate problem if the latest data rate or the average
data rate over the past 10 days for the given direction satisfy at least one of the following
conditions:
o Each of the constituent port latest data rates or each of the constituent port average data
rates is less than 55 percent of the service product max rate.
o The sum of the constituent port latest data rates or the sum of the constituent port
average data rates is less than service product minimum acceptable rate + 0.3 x (service
product maximum rate service product minimum acceptable rate).

Page 26 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

o In the above two conditions, if the lines are running in ADSL standards and the service
product maximum rate for the US direction is greater than 1500kbps, 1500kbps will be
used instead of the service product maximum rate. Similarly, if the lines are running in
ADSL standards and the service product maximum rate for the DS direction is greater
than 30000kbps, 30000kbps will be used instead of the service product max rate.
Note: the 55 percent and 30 percent thresholds above as well as the service product
maximum rates are fully configurable to meet different network/customer requirements.
oIf the port data rate for the given direction is not available for the past 10 days for any of
the constituent ports in the bonded group, the bonded line rate status will be unknown.
More details on the stability and rate status are provided in the two tables below the status
summary. Details are given for all constituent ports within the bonded group.

2.3 Line Performance Analysis

The following screen displays a performance analysis of a specific DSL line using historical data:

ASSIA, Inc. Confidential and Proprietary Page 27

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Page 28 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Detailed Description:
When this screen is entered for a specific line, results from the most recently collected data are
initially displayed. As explained below, results from older data collections can also be selected to
be displayed. For displaying results using real-time data collection, see Real-Time Line
Performance Analysis.
Note: Various fields referenced below are defined with more detail in the section titled Data
Report Fields, which is located at the end of this document. For each field, the following
information is displayed: Field Name, Description and Usage, and Screens which contain the field.
Line Information:
Line ID: This field provides the identification information for the line information being
displayed. Line ID is operator dependent and can represent anything from a unique
identifying number to a real telephone number.

ASSIA, Inc. Confidential and Proprietary Page 29

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

DSLAM: The name of the DSLAM in which the Line ID or DSL line is located.
Port: The logical port number in the DSLAM on which the particular service is supported. This
can be formatted in multiple ways, from shelf-slot-port (x-y-z) to rack-shelf-slot-port (w-x-y-z).
This field is DSLAM dependent.
Service Product: Indicates the service product that is provisioned on the line. Clicking on the
service product name produces a pop-up window that displays information about the
maximum rate, service recommendation rate and minimum rate of the service product for
both the downstream and upstream directions.
Line Status: Indicates the status of the line.
Links to related screens:
The following links navigate the user to various screens with information related to either the Line
ID or DSLAM that is currently being examined:
Line Summary | Line Performance Analysis | Real-Time Performance Analysis
Diagnostics Analysis | Real-Time Diagnostics Analysis | SELT Diagnostics Analysis | Historical Data Trends
Lines in the DSLAM | Lines in the Neighborhood | Profile Optimization Analysis | Service Recommendation

Analysis Result:
History Check:
This pull-down menu allows the user to select one of multiple data collection times. Data from the
most recent data collection time are displayed by default. Selecting another time produces a
display of the corresponding historical data. This pull-down menu controls the data displayed in
the Analysis Result section, in the Bit Distribution section and in the Line Code Violation and FEC
Corrections section (see below for detailed explanations of the latter two sections).
Profile in Use:
This table shows the profile name and settings that were in use for this Line ID at the end of the
selected timeframe.
Min Rate (kbps)
Max Rate (kbps)
Planned Rate (kbps)
Min Margin (dB)
Target Margin (dB)
Max Margin (dB)
Max Power (dBm)
Max PSD (dBm/Hz)
Delay (ms)
INP (symbols)
Supported Standards
Interleaving
Trellis Coding
If support for G.inp is enabled, and the profile contains G.inp settings, then the following settings
are also displayed:

Page 30 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

G.Inp Mode
INP REIN
leftr Thres.
SHINE Ratio
SHINE Ratio
If support for vectoring is enabled, and the profile contains vectoring settings, then the following
setting is also displayed:
Is FEXT Cancellation Enabled
Line Attributes:
This table shows the line state for the respective Line ID at the time of the last measurement
period.
Current Rate (kbps)
Current ETR (kbps)
MABR (kbps)
Margin (dB)
Attenuation (dB)
Power (dBm)
Running Standard
Actual INP (symbols)

Actual Delay (ms)

Tx ModeIf support for G.inp is enabled, and the line is operating in G.inp mode, then the following
quantity is also displayed:
Actual INP REIN (symbols)

Bit Distribution:
This graph displays the current Bit Distribution for the respective Line ID. For reasons related to
the history of DSL standards, bit distribution is displayed even when the per-tone data displayed
in the next section are not available or not collected.

Per Tone Charts:

These charts are displayed only for DSLAMs that are able to report per-tone data (also known as
per-subcarrier data), and only if such data collection is configured on the DSL Expresse system.
These charts display the HLOG, PSD, QLN, Bits and SNR quantities for both the Upstream and
Downstream directions. The Bits quantity has the same definition as the Bit Distribution quantity
of the previous section
This section has its own Collection Date pull-down menu for selecting to display per-tone data
from a specific collection time.
For each of the plots, the user is able to zoom-in to specific frequency ranges by specifying a
Start Tone and an End Tone. By default, all tones are displayed. The user is also able to select

ASSIA, Inc. Confidential and Proprietary Page 31

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

the quantities displayed on each plot. By default, all relevant quantities are displayed. After
making a selection, the user must click on the Submit button for the plot to refresh.

Vendor ID:
This table shows information collected through the DSLAM about the Customer Premises
Equipment (CPE) connected to the line. The following fields are reported:
CPE Vendor ID
CPE Firmware Version Number
CPE Serial Number
Other Info
This section has its own Collection Date pull-down menu for selecting to display Vendor ID data
from a specific collection time.

Line Code Violation and FEC Corrections:

This section contains tables and plots of the lines error counters. These represent counts of the
respective errors in 15 minute intervals. The following types of errors are reported:
Downstream Line Code Violations
Upstream Line Code Violations
Downstream Error Seconds
Upstream Error Seconds
Downstream FEC Corrections
Upstream FEC Corrections
Retrain Counts
If support for G.inp is enabled, and line is operating in G.inp mode, then the following settings are
also displayed:
Downstream leftr Seconds
Upstream leftr Seconds
Downstream Average EFTR
Upstream Average EFTR

Selecting one of the Show History links below the counter tables displays a graph encompassing
the entire history of the error counts displayed in the table immediately above the link. By default,
each graph displays the error counts from the earliest available time interval up to the most
recently available. Also available is a feature that allows the user to zoom into any specific
date/time period and view only that time periods error count. Note that if a start date or end date
or time period is selected for which there is no data available, the zoom feature automatically
builds the graph with the closest days data as the reference point.
An example of the zoom feature is shown below.

Page 32 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Bonded Lines
The performance analysis of only one constituent port within the bonded group is shown on this
page. To see the performance analysis of another constituent port, click on the port of interest in
the Bonded Ports column of the Line Information section (displayed in bold blue color in the
example shown below).

2.4 Real-Time Line Performance Analysis

This screen displays a performance analysis of a specific DSL line using real-time data. (The
example page shown below assumes that support for g.inp and vectoring are disabled.)

ASSIA, Inc. Confidential and Proprietary Page 33

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Page 34 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

ASSIA, Inc. Confidential and Proprietary Page 35

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Detailed Description:
When this screen is entered for a specific line, the DSLAM is queried in real-time to obtain the
most up-to-date data to display. As a consequence, displaying this screen may require more time
compared to other non-real-time screens. For displaying results using previously collected data
(historical), see Line Performance Analysis.
The information displayed on this screen is nearly identical to the information displayed on Line
Performance Analysis. Only the differences between these screens are here explained.
Collection Options:
This screen allows the user to specify the types of data to collect in real-time. There are three
data categories:

Page 36 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Operational Data: used to generate the Analysis Result and the Bit Distribution sections
of the screen.
Per-Subcarrier Data: used to generate the Per Tone Charts section of the screen.
Vendor ID Data: used to generate the Vendor ID section of the screen.
Performance Monitoring Data: used to generate the Line Code Violation and FEC
Corrections section of the screen.
The Operational Data and the Vendor ID Data are always collected so there is no corresponding
option. By default, only the Operational Data and Vendor ID Data are collected, so the Analysis
Result, Bit Distribution and Vendor ID sections are only displayed. The user can choose to
additionally collect the Per-Subcarrier Data (to view the Per Tone Charts), and the Performance
Monitoring Data (to view the Line Code Violation and FEC Corrections section of the screen).
Selecting additional data for collection lengthens the DSLAM response time, and consequently
increases the time for displaying the results on the screen.
The Real-Time Line Performance Analysis screen does not include the History Check or the
Collection Date pull-down menus that are included in the Line Performance Analysis screen. All
displayed results are based on the real-time data collection. However, data collected using the
Real-Time Line Performance Analysis screen are stored, and are then visible from the Line
Performance Analysis screen.

2.5 Diagnostics Analysis

This screen displays a diagnostics analysis of a specific DSL line using historical data.

ASSIA, Inc. Confidential and Proprietary Page 37

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Detailed Description:
When this screen is entered for a specific line, diagnostics results based on the most recently
collected data are initially displayed. As explained below, results based on older data collections
can also be selected to be displayed. For displaying results using real-time data collection, see
Real-Time Line Diagnostics Analysis.
Note: Various fields referenced below are defined with more detail in the section titled Data
Report Fields, which is located at the end of this document. For each field, the following
information is displayed: Field Name, Description and Usage, and Screens which contain the field.
Line Information:

Page 38 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Line ID: This field provides the identification information for the line information being
displayed. Line ID is operator dependent and thus this can represent anything from a unique
identifying number to a real telephone number.
DSLAM: The name of the DSLAM in which the Line ID or DSL line is located.
Port: The logical port number in the DSLAM on which the particular service is supported. This
can be formatted in multiple ways, from shelf-slot-port (x-y-z) to rack-shelf-slot-port (w-x-y-z).
This field is DSLAM dependent.
Service Product: Indicates the service product that is provisioned on the line. Clicking on the
service product name produces a pop-up window that displays information about the
maximum rate, service recommendation rate and minimum rate of the service product for
both the downstream and upstream directions.
Line Status: Indicates the status of the line.
Links to related screens:
The following links navigate the user to various screens with information related to either the Line
ID or DSLAM that is currently being examined:
Line Summary | Line Performance Analysis | Real-Time Performance Analysis
Diagnostics Analysis | Real-Time Diagnostics Analysis | SELT Diagnostics Analysis | Historical Data Trends
Lines in the DSLAM | Lines in the Neighborhood | Profile Optimization Analysis | Service Recommendation

Analysis Result:
History Check:
This pull-down menu allows the user to select one of multiple days with data collected.
Diagnostics results from the most recent day with data collected are displayed by default.
Selecting another day produces a display of the corresponding historical results.
Data Source:
This field displays the source of data that are used for producing the diagnostics analysis results
of the line. There are two such sources of data:
POP_O: Operational data
PER_TONE: Per-tone data (also known as per-subcarrier data)
It is possible for results generated with one type of data to differ from results generated with the
other type of data. The per-tone data typically produce more accurate results. Collection of per-
tone data is possible only for DSLAMs that are able to support it, and only if such data collection
is configured on the DSL Expresse system.
In addition to the above data types, this screen also relies on Performance Monitoring Data for
producing the displayed analysis results.
Loop Length and MABR Analysis:
This table provides diagnostics information regarding Loop Length and Maximum Attainable Bit
Rate (MABR).
Table Format:
Type of result (first column from the left): The type of diagnostics analysis results presented
on the row.
Data sample (second column from the left): The numerical value of the analysis result or a
flag indicating the detection result (red means that the corresponding condition exists, and

ASSIA, Inc. Confidential and Proprietary Page 39

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

green means that it does not). The date on the header of this column indicates the day on
which the data were collected.
Comment (third column from the left): Information related to the results or the calculations is
given here.
Table Data:
Loop Length: The equivalent electrical loop length as estimated by DSL Expresse.
First detected Bridged Tap Length: The equivalent electrical length of the first detected
bridged tap as estimated by DSL Expresse. This is only evaluated when per-tone data are
available. If no bridged tap is detected, 0 is displayed. If not enough information is available
for detection or length estimation, N/A is displayed.
Second detected Bridged Tap Length: The equivalent electrical length of the second detected
bridged tap as estimated by DSL Expresse. This is only evaluated when per-tone data is
available. If no second bridged tap is detected, 0 is displayed. If not enough information is
available for detection or length estimation, N/A is displayed.
US MABR (kbps): The upstream MABR. For ADSL lines, the value is the US reported MABR.
For VDSL lines, the value is the US estimated MABR.
DS MABR (kbps): The DS estimated MABR (estimated by DSL Expresse).
US MABR in the lowest 1 percent: When this condition is detected, then this lines US MABR
ranks at the bottom 1 percent among all lines in the network with a similar loop length.
DS MABR in the lowest 1 percent: When this condition is detected, then this lines DS MABR
ranks at the bottom 1 percent among all lines in the network with a similar loop length.
US MABR Percentile: The value represents the lines US MABR percentile ranking when
compared to all lines in the network with a similar loop length.
DS MABR Percentile: The value represents the lines DDS MABR percentile ranking when
compared to all lines in the network with a similar loop length.
US MABR FEXT Mitigated (kbps): When vectoring support is enabled, this value represents
the lines US MABR assuming that the FEXT present on the line can be eliminated. This
value is estimated by DSL Expresse.
DS MABR FEXT Mitigated (kbps): When vectoring support is enabled, this value represents
the lines DS MABR assuming that the FEXT present on the line can be eliminated. This
value is estimated by DSL Expresse.

Stability Analysis:
This table provides information regarding the line stability.
Table Format:
Type of result (first column from the left): The type of diagnostics analysis results presented
on the row.
Data sample (second column from the left): The numerical value of the analysis result or a
flag indicating the detection result (red means that the corresponding condition exists, and
green means that it does not). The date on the header of this column indicates the day on
which the data were collected.
Comment (third column from the left): Information related to the results or the calculations is
given here.

Page 40 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Table Data:
Stability: This is the lines stability as evaluated by DSL Expresse. There are four stability
levels: VERY STABLE, STABLE, UNSTABLE and VERY UNSTABLE. A line evaluated as
one of the first two is categorized as a stable line, and a line evaluated as one of the last
two is considered an unstable line. If there is not enough data to evaluate the stability,
UNKNOWN is displayed.
Instability reason: When the line is evaluated as UNSTABLE or VERY UNSTABLE, this field
provides the reason using a three-bit code. Each digit of the code corresponds to a condition
of the line that may contribute to instability. There are three possible conditions and their
mapping to the three-bit code is explained next:
o Excessive DS Code Violations: The first bit from the left of the three-bit code is set to one
when DS CVs are detected as the cause of instability.
o Excessive US Code Violations: The second bit from the left of the three-bit code is set to
one when US CVs are detected as the cause of instability.
o Large average Retrain Count per day: The third bit from the left of the three-bit code is
set to one when a large number of retrains per day is detected as the cause of instability.
Note: If the line is evaluated as VERY STABLE or STABLE, the instability reason is displayed
as 000. If there is not enough data to evaluate stability (stability is UNKNOWN), the
instability reason is displayed as -1.
Daily Periodic Impairment: When this condition is detected, then the lines stability is
periodically degraded and this degradation starts at approximately the same time every day.
An estimate of the start time is displayed in the Comment column.
US Average EFTR (kbps): When support for g.inp is enabled, and the line operates in g.inp
mode, this quantity is the averageaverage error-free throughput rate over the past 24 hours in
the upstream direction. The percentage represents the error-free throughput rate relative to
the throughput of a line with no errors.
DS Average EFTR (kbps): When support for g.inp is enabled, and the line operates in g.inp
mode, this quantity is the average error-free throughput rate over the past 24 hours in the
downstream direction. The percentage represents the error-free throughput rate relative to
the throughput of a line with no errors.

Noise Analysis:
This table provides diagnostics information regarding noise detected on the line.
Table Format:
Type of result (first column from the left): The type of diagnostics analysis results presented
on the row.
Data sample (second and third columns from the left): The second column is the flag
indicating the detection result (red means that the corresponding condition exists, and green
means that it does not). The date on the header of this column indicates the day on which the
data were collected for producing this result. The third column shows the number of days
during which this condition has been detected. The header of this column shows the date
range for this evaluation.
Comment (fourth column from the left): Information related to the results or the calculations is
given here.
Table Data:
High Power Noise: The received noise is at an abnormally high level and can affect the data
rate performance of the line.

ASSIA, Inc. Confidential and Proprietary Page 41

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

High Power Noise in High Frequency: The received noise is at an abnormally high level at the
higher frequencies of the ADSL band. This condition is evaluated and displayed only for
ADSL lines.
AM or AM like Noise: AM signal ingress is having an effect on transmission. The particular
tone affected is indicated.
HAM Noise: Noise from HAM amateur radio is detected. This condition is evaluated and
displayed only for VDSL lines and only when per-tone data is available.
Noise Fluctuation: The received noises power spectral density is changing significantly.
Low Frequency Crosstalk: The received noise is at an abnormally high level at the lower
frequencies and is resembling crosstalk generated by symmetric DSL systems. This condition
is evaluated and displayed only for ADSL lines.
ADSL FEXT: ADSL FEXT detected. This condition is evaluated and displayed only for VDSL
lines and only when per-tone data is available.
VDSL FEXT: VDSL FEXT detected. This condition is evaluated and displayed only for VDSL
lines and only when per-tone data is available.
Performance Degradation Flags:
This table provides a number of performance degradation flags that can reveal a developing
performance issue.
Table Format:
Type of result (first column from the left): The type of diagnostics analysis results presented
on the row.
Data sample (second and third columns from the left): The second column is the flag
indicating the detection result (red means that the corresponding condition exists, and green
means that it does not). The date on the header of this column indicates the day on which the
data were collected for producing this result. The third column shows the number of days
during which this condition has been detected. The header of this column shows the date
range for this evaluation.
Comment (fourth column from the left): Information related to the results or the calculations is
given here.
Table Data:
Abnormal Increase in US Attenuation: An increase in US Attenuation greater than 5dB is
observed. This may impact performance and is a strong indication that the DSL line was
physically changed in a negative way.
Abnormal Increase in DS Attenuation: An increase in DS Attenuation greater than 5dB is
observed. This may impact performance and is a strong indication that the DSL line was
physically changed in a negative way.
Abnormal Decrease in US MABR: A decrease in US MABR greater than 40 percent is
observed. This may impact performance and is a strong indication that the DSL line was
physically changed in a negative way.
Abnormal Decrease in DS MABR: A decrease in DS MABR greater than 40 percent is
observed. This may impact performance and is a strong indication that the DSL line was
physically changed in a negative way.
Increase in Code Violations: The number of 15-minute intervals with greater than 500 Code
Violations increased by a factor of five or more. This is a strong indication that that DSL lines
performance experienced an abrupt degradation.

Page 42 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Other Analysis:
This table provides diagnostics analysis for various common conditions.
Table Format:
Type of result (first column from the left): The type of diagnostics analysis results presented
on the row.
Data sample (second and third columns from the left): The second column is the flag
indicating the detection result (red means that the corresponding condition exists, and green
means that it does not). The date on the header of this column indicates the day on which the
data were collected for producing this result. The third column shows the number of days
during which this condition has been detected. The header of this column shows the date
range for this evaluation.
Comment (fourth column from the left): Information related to the results or the calculations is
given here.
Table Data:
Bad-splice: Indicates whether a bad splice has been detected on the loop.
Unbalanced Wiring: Indicates whether unbalanced wiring is affecting DSL performance.
DS Impulse Noise: Indicates whether impulse noise is affecting DSL performance in the
downstream direction.
US Impulse Noise: Indicates whether impulse noise is affecting DSL performance in the
upstream direction.
Bridged Tap: Indicates whether a bridged tap has been detected on the loop.
Potential Missing Microfilter: Indicates that at least one DSL microfilter may be missing or
may be improperly installed.
CPE Interoperability Issue: Indicates if a CPE interoperability issue is detected. This field
currently applies only to the case when vectoring support is enabled. If the line is connected
to a vector-capable line-card and is using a vectored profile, this field indicates if the CPE is
not vector-capable and therefore unable to achieve a connection in vectored mode.
Bonded Lines
For bonded lines, the diagnostics analysis of only one constituent port within the bonded group is
shown on the screen. To see the diagnostics analysis of another constituent port, click the port of
interest in the Bonded Ports column of the Line Information section.

2.6 Real-Time Diagnostics Analysis

This screen displays a diagnostics analysis of a specific DSL line using real-time data.

ASSIA, Inc. Confidential and Proprietary Page 43

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Detailed Description:
When this screen is entered for a specific line, the DSLAM is queried in real-time to obtain the
most up-to-date data for producing the diagnostics results to display. As a consequence,
displaying this screen may require more time compared to other non-real-time screens. For
displaying diagnostics results using previously collected data (historical), see Diagnostics
Analysis.
The information displayed on this screen is nearly identical to the information displayed on
Diagnostics Analysis. Only the differences between these screens are here explained.
Collection Options:
This screen allows the user to specify the types of diagnostics analysis results to display, which
determines the data to collect in real-time. There are three types of diagnostics analysis:
Default Diagnostics: used to generate the Loop Length and MABR Analysis table, the
Noise Analysis table and the Other Analysis table, using Operational Data.
Advanced Diagnostics: used to generate the same tables as with Default Diagnostics,
but using Per-Subcarrier (or per-tone) Data .
Stability Analysis: used to generate the same tables as with Default Diagnostics, but
also generating the Stability Analysis table using Performance Monitoring Data..
By default, the Default Diagnostics results are displayed, based on the real-time collection of
Operational Data. The user can choose to display the Advanced Diagnostics, in which case the
results are based on the real-time collection of Per-Subcarrier Data. Finally, the user can choose
to display the Stability Analysis, in which case Performance Monitoring Data must be additionally
collected in real-time. Selecting to display Advanced Diagnostics or Stability Analysis results
requires the collection of additional data, which lengthens the DSLAM response time, and
consequently increases the time for displaying the results on the screen.
The Real-Time Diagnostics Analysis screen does not display the Performance Degradation Flags
table that is displayed on the Diagnostics Analysis screen.
The Real-Time Diagnostics Analysis screen does not include the History Check pull-down menu
that is included in the Diagnostics Analysis screen. All displayed results are based on the real-
time data collection. Data collected using the Real-Time Diagnostics Analysis screen are not
stored, and cannot be retrieved at a later time through the Diagnostics Analysis screen.

2.7 SELT Diagnostics Analysis

This screen displays a Single-Ended Line Testing (SELT) diagnostics analysis for a specific DSL
line. The analysis is produced after initiating a real-time collection of SELT data. Initiating such
collection interrupts the DSL service.

Page 44 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

ASSIA, Inc. Confidential and Proprietary Page 45

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Detailed Description:
When this screen is accessed for a specific line, one of the following situations may occur:
1. SELT is available: In this case, the user is given the option to start a new SELT data
collection and analysis. If there are any past analysis results, the most recent ones are
displayed.( as shown in the screenshot above)
2. SELT is not available: In this case, the following message will be displayed.

Note: Various fields referenced below are defined with more detail in the section titled Data
Report Fields, which is located at the end of this document. For each field, the following
information is displayed: Field Name, Description and Usage, and Screens which contain the field.
Line Information:
Line ID: This field provides the identification information for the line information being
displayed. Line ID is operator dependent and thus this can represent anything from a unique
identifying number to a real telephone number.
DSLAM: The name of the DSLAM in which the Line ID or DSL line is located.
Port: The logical port number in the DSLAM on which the particular service is supported. This
can be formatted in multiple ways, from shelf-slot-port (x-y-z) to rack-shelf-slot-port (w-x-y-z).
This field is DSLAM dependent.
Service Product: Indicates the service product that is provisioned on the line. Clicking on the
service product name produces a pop-up window that displays information about the
maximum rate, service recommendation rate and minimum rate of the service product for
both the downstream and upstream directions.
Line Status: Indicates the status of the line. This field is not updated based on real-time data
collection results.
Links to related screens: These links display more information related to the Line ID or DSLAM.

Page 46 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Click one for a description.

Line Summary | Line Performance Analysis | Real-Time Performance Analysis
Diagnostics Analysis | Real-Time Diagnostics Analysis | SELT Diagnostics Analysis | Historical Data Trends
Lines in the DSLAM | Lines in the Neighborhood | Profile Optimization Analysis | Service Recommendation

Analysis Result:
History Check:
This pull down menu allows the user to select one of multiple data collection times. SELT
diagnostics results from the most recent data collection are displayed by default. Selecting
another data collection time produces a display of the corresponding historical results.
Analysis Type:
This field indicates the source of data that are used for producing the SELT diagnostics analysis
results of the line. There are three possibilities:
SELT: The analysis is based only on SELT data.
SELT + DELT: The analysis is based on both SELT and Double-Ended Line Testing (DELT)
data.
NOT SUFFICIENT DATA: Sufficient data were not available to produce the analysis results.
Estimated Fault Locations:
This figure illustrates the results of the SELT diagnostics analysis.
Figure Format:
DSLAM: Indicates the location of the DSLAM.
CPE: Indicates location of the Customer Premises Equipment (CPE).
Twisted Pair: Indicates the DSL loop.
Vertical Bar: Indicates the estimated location of the fault on the line.
Length Under Double-Ended Arrows: Indicates length of the corresponding segment.
Fault Type: Indicates the type of the detected fault.
Severity: Indicates the severity of the fault. The severity is also represented by a color code.
Bridged-Tap Length: Indicates the estimated bridged-tap length.
Fault Type:
Series: Any fault that can be modeled as an impedance connected in series with the twisted
pair.
Shunt: Any fault that can be modeled as an impedance connected in parallel with the twisted
pair.
Bridged Tap: An extension or branch of the twisted pair.
Severity:
Moderate: Affects the DSL performance moderately. This is the weakest fault that is
detectable by DSL Expresse.
Severe: Affects the DSL performance severely.
Critical: Can disrupt the service and requires immediate action, e.g. a technician dispatch.

ASSIA, Inc. Confidential and Proprietary Page 47

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Normalized Time-Domain Reflection:

This plot illustrates the normalized time-domain reflection which is estimated from the
uncalibrated echo response (UER) by DSL Expresse.
HLOG Dist:
Displays actual Hlog as gathered by DSL Expresse.

2.8 Historical Data Trends

This screen allows the user to display plots of the historical behavior of performance parameters
of a specific DSL Line.

Page 48 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Detailed Description:
Note: Various fields referenced below are defined with more detail in the section titled Data
Report Fields, which is located at the end of this document. For each field the following
information is displayed: Field Name, Description and Usage, and Screens which contain the field.
Line Information:
Line ID: This field provides the identification information for the line information being
displayed. Line ID is operator dependent and thus this can represent anything from a unique
identifying number to a real telephone number.
DSLAM: The name of the DSLAM in which the Line ID or DSL line is located.
Port: The logical port number in the DSLAM on which the particular service is supported. This
can be formatted in multiple ways, from shelf-slot-port (x-y-z) to rack-shelf-slot-port (w-x-y-z).
This field is DSLAM dependent.
Service Product: Indicates the service product that is provisioned on the line. Clicking on the
service product name produces a pop-up window that displays information about the
maximum rate, service recommendation rate and minimum rate of the service product for
both the downstream and upstream directions.
Line Status: Indicates the status of the line.

ASSIA, Inc. Confidential and Proprietary Page 49

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Links to related screens:

The following links navigate the user to various screens with information related to either the Line
ID or DSLAM that is currently being examined:
Line Summary | Line Performance Analysis | Real-Time Performance Analysis
Diagnostics Analysis | Real-Time Diagnostics Analysis | SELT Diagnostics Analysis | Historical Data Trends
Lines in the DSLAM | Lines in the Neighborhood | Profile Optimization Analysis | Service Recommendation

Plot of Line Attributes:

This section allows the user to plot various parameters of the line in question over the collected
data timeframe.
The following parameters can be plotted:
Reported Mabr US: Upstream reported MABR
Reported Mabr DS: Downstream reported MABR
Estimated Mabr US: Upstream estimated MABR
Estimated Mabr DS: Downstream estimated MABR
Current Rate US: Upstream Current Rate
Current Rate DS: Downstream Current Rate
Power US: Upstream Power
Power DS: Downstream Power
Margin US: Upstream Margin
Margin DS: Downstream Margin
Attenuation US: Upsteam Attenuation
Attenuation DS: Downstream Attenuation
Average EFTR US: Average EFTR US
Average EFTR DS: Average EFTR DS

Plot of Bit Distribution:

This section allows the user to plot the bit distribution of the line over time. The user can plot all
available bit distribution information or can select individual timeframes. The user must select
between a bit distribution chart and a bit loading contour (heat-map).

Bonded Lines
For bonded lines the historical data trends of only one constituent port within the bonded group is
shown on this screen. To see the historical data trends of another constituent port click on the
port of interest in the Bonded Ports column of the Line Information section.

Page 50 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

2.9 Lines in the DSLAM

This screen provides a summary of the diagnostics information for all lines connected to the same
DSLAM.
The Lines in the DSLAM page allows the selection of running standards to be displayed: ALL
(denotes displaying both ADSL and VDSL lines), ADSL, or VDSL. Depending on the running
standard selection, ADSL-specific or VDSL-specific diagnostics columns will be displayed, see
the three screenshot below.

ASSIA, Inc. Confidential and Proprietary Page 51

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Detailed Description:
Note: Various fields referenced below are defined with more detail in the section titled Data
Report Fields, which is located at the end of this document. For each field the following
information is displayed: Field Name, Description and Usage, and Screens which contain the field.
Line Information:
Line ID: This field provides the identification information for the line information being
displayed. Line ID is operator dependent and thus this can represent anything from a unique
identifying number to a real telephone number.
DSLAM: The name of the DSLAM in which the Line ID or DSL line is located.
Port: The logical port number in the DSLAM on which the particular service is supported. This
can be formatted in multiple ways, from shelf-slot-port (x-y-z) to rack-shelf-slot-port (w-x-y-z).
This field is DSLAM dependent.
Service Product: Indicates the service product that is provisioned on the line. Clicking on the
service product name produces a pop-up window that displays information about the
maximum rate, service recommendation rate and minimum rate of the service product for
both the downstream and upstream directions.
Line Status: Indicates the status of the line.
Links to related screens:
The following links navigate the user to various screens with information related to either the Line
ID or DSLAM that is currently being examined:
Line Summary | Line Performance Analysis | Real-Time Performance Analysis
Diagnostics Analysis | Real-Time Diagnostics Analysis | SELT Diagnostics Analysis | Historical Data Trends
Lines in the DSLAM | Lines in the Neighborhood | Profile Optimization Analysis | Service Recommendation
History Check:
Estimation Date:
This menu allows the user to retrieve DSLAM-wide data specific to any collection date. The most
recently collected data is displayed by default.
Analysis Result:
Lines in the DSLAM:
The pull-down menus allow the user to select a particular combination of rack, shelf and card with
in the DSLAM. Note that certain DSLAM types may not allow for a rack to be specified. If no
values are selected, the screen will display all DSL Ports connected to the DSLAM.

Page 52 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Selecting a combination of rack, shelf, and/or card shows only those ports that satisfy the
selected criteria for identification within the DSLAM.
Export CSV: This creates a .csv (comma separated value) file of the data presented in the table
and saves it to the local computer. This file contains a tabular listing of the data that can be
examined using a spreadsheet application such as Microsoft Excel.
Bonded Lines
Note that for bonded lines each constituent port within the bonded group is shown as a separate
row in the Lines in the DSLAM table.
Lines in the DSLAM Table:
This table provides a summary of diagnostics information for all lines in the selected DSLAM
which meet the criteria selected for Rack, Shelf and Card, and the Running Standard selection.
Each row contains information for an individual line.
Table Data:
Line ID: This is the unique identifier for this line. Line ID is operator dependent and therefore
can represent anything from a unique identifying number to a real telephone number. This
Line ID is a hyperlink that leads to the Line Performance Analysis screen for that selected line.
Port: The logical port number in the DSLAM on which the particular service is supported. This
can be formatted in multiple ways, from shelf-slot-port (x-y-z) to rack-shelf-slot-port (w-x-y-z).
This field is DSLAM dependent.
Line-card type: The type of the line-card that is connected to this line.
Line-card version: The version of the line-card that is connected to this line. This field is not
available for all DSLAM and line-card types.
Estimation Date: Date when the estimation was performed by DSL Expresse.
Date of Collection: Date when the data was collected by DSL Expresse.
Data Source: Source of data (POP_O or PER_TONE) that is used for performance
estimation.
Running Standard: Operating DSL standard on the line.
Loop Length: The equivalent electrical loop length as estimated by DSL Expresse.
US MABR (kbps): The upstream MABR. For ADSL lines, the value is the US reported MABR.
For VDSL lines, the value is the US estimated MABR.
DS MABR (kbps): The DS estimated MABR (estimated by DSL Expresse).
US MABR in the lowest 1 percent: When this condition is detected, then this lines US MABR
ranks at the bottom 1 percent among all lines in the network with a similar loop length.
DS MABR in the lowest 1 percent: When this condition is detected, then this lines DS MABR
ranks at the bottom 1 percent among all lines in the network with a similar loop length.
US MABR Percentile: The value represents the lines US MABR percentile ranking when
compared to all lines in the network with a similar loop length.
DS MABR Percentile: The value represents the lines US MABR percentile ranking when
compared to all lines in the network with a similar loop length.
Bad-splice: Indicates whether a bad splice has been detected on the loop.
Unbalanced Wiring: Indicates whether unbalanced wiring is affecting DSL performance.

ASSIA, Inc. Confidential and Proprietary Page 53

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

First detected Bridged Tap Length: The equivalent electrical length of the first detected
bridged tap as estimated by DSL Expresse. This is only evaluated when per-tone data are
available. If no bridged tap is detected, 0 is displayed. If not enough information is available
for detection or length estimation, N/A is displayed.
Second detected Bridged Tap Length: The equivalent electrical length of the second detected
bridged tap as estimated by DSL Expresse. This is only evaluated when per-tone data is
available. If no second bridged tap is detected, 0 is displayed. If not enough information is
available for detection or length estimation, N/A is displayed.
US Impulse Noise: Indicates whether impulse noise is affecting DSL performance in the
upstream direction.DS Impulse Noise: Indicates whether impulse noise is affecting DSL
performance in the downstream direction.
Stability: This is the lines stability as evaluated by DSL Expresse. There are four stability
levels: VERY STABLE, STABLE, UNSTABLE and VERY UNSTABLE. A line evaluated as
one of the first two is categorized as a stable line, and a line evaluated as one of the last
two is considered an unstable line. If there is not enough data to evaluate the stability,
UNKNOWN is displayed.
Instability reason: When the line is evaluated as UNSTABLE or VERY UNSTABLE, this field
provides the reason using a three-bit code. AM or AM like Noise: AM signal ingress is having
an effect on transmission.High Power Noise: The received noise is at an abnormally high
level and can affect the data rate performance of the line.
High Power Noise in High Frequency: The received noise is at an abnormally high level at the
higher frequencies of the ADSL band. This condition is evaluated and displayed only for
ADSL lines.
Low Frequency Crosstalk: The received noise is at an abnormally high level at the lower
frequencies and is resembling crosstalk generated by symmetric DSL systems. This condition
is evaluated and displayed only for ADSL lines.
HAM Noise: Noise from HAM amateur radio is detected. This condition is evaluated and
displayed only for VDSL lines and only when per-tone data is available.
ADSL FEXT: ADSL FEXT detected. This condition is evaluated and displayed only for VDSL
lines and only when per-tone data is available.
VDSL FEXT: VDSL FEXT detected. This condition is evaluated and displayed only for VDSL
lines and only when per-tone data is available.
Noise Fluctuation: The received noises power spectral density is changing significantly.
Potential Missing Microfilter: Indicates that at least one DSL microfilter may be missing or
may be improperly installed.
Daily Periodic Impairment: When this condition is detected, then the lines stability is
periodically degraded and this degradation starts at approximately the same time every day.
An estimate of the start time is displayed in the Comment column.
US Average EFTR (kbps): When support for g.inp is enabled, and the line operates in g.inp
mode, this quantity is the average error-free throughput rate over the past 24 hours in the
upstream direction. The percentage represents the error-free throughput rate relative to the
throughput of a line with no errors.
DS Average EFTR (kbps): When support for g.inp is enabled, and the line operates in g.inp
mode, this quantity is the average error-free throughput rate over the past 24 hours in the
downstream direction. The percentage represents the error-free throughput rate relative to
the throughput of a line with no errors.

Page 54 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

CPE Interoperability Issue: Indicates if a CPE interoperability issue is detected. This field
currently applies only to the case when vectoring support is enabled. If the line is connected
to a vector-capable line-card and is using a vectored profile, this field indicates if the CPE is
not vector-capable and therefore unable to achieve a connection in vectored mode.
US MABR FEXT Mitigated (kbps): When vectoring support is enabled, this value represents
the lines US MABR assuming that the FEXT present on the line can be eliminated. This
value is estimated by DSL Expresse.
DS MABR FEXT Mitigated (kbps): When vectoring support is enabled, this value represents
the lines DS MABR assuming that the FEXT present on the line can be eliminated. This
value is estimated by DSL Expresse.

ASSIA, Inc. Confidential and Proprietary Page 55

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

2.10 Lines in the Neighborhood

The DSL Expresse Neighborhood functionality provides a means to search for and select a group
of lines according to search criteria on line attributes and inventory data. Various analyses can be
conducted on the selected group of lines with the following main goals:
To identify and localize diagnostics faults and to estimate potential performance
improvements after the fix in the case the line or lines of interest in the group are offered a
DSL service. This use-case is usually referred to as neighborhood diagnostics.
To predict possible data rates that can be offered to the line or lines of interest in the case
they are not already offered a DSL service. This use-case is usually referred to as
neighborhood pre-qualification.
To enable the neighborhood feature and to be able to search for lines based on various criteria,
appropriate line attributes and inventory information must be made available to the system.
The search criteria for neighborhood analyses, referred to as neighborhood filters hereafter, are
completely configurable in DSL Expresse. These filters can be customized based on the
customers needs as well as availability of various inventory data. In general, neighborhood filters
and the corresponding line attributes or inventory data can be categorized in the following three
groups:
Address filters: These filters act upon the address information of existing or potentially new
customers, e.g., street numbers and names, city names, states and Zip codes. Customer
address information is required for these filters to work.
Cable make-up filters: These filters act upon the cable information of existing or new lines,
e.g., Central office names, cable codes and binder numbers for different segments of the
cable make-up, distribution box and service terminal names. Cable inventory information is
required for these filters to work.
Distance filter: This filters acts upon the geographical location of existing or potentially new
customers, e.g., latitudes and longitudes. Customer geodata is required for this filter to work.

2.10.1 Specifying a neighborhood search

The DSL Expresse neighborhood feature offers two different methods to search for lines and
conduct analysis:
Reference-based search: In this kind of search, the attributes and information of a given line,
referred to as the reference line hereafter, are used as basis for the search. Lines are selected
according to the attributes from the reference line. This kind of search is useful for analyzing
existing lines with DSL services. The reference line can be compared to similar lines in the
selected group for diagnostics fault identification and localization, and for rate improvement
estimation after the fix. As is explained later, a reference-based search is identified as a search
that includes line ID as one of the filters for specifying the reference line ID.
Arbitrary search (without a reference): In this kind of search, the attributes and information are
specified directly and not through a reference line. This kind of search is particularly useful for
neighborhood pre-qualification when the line of interest does not exist in the system and only the
line attributes and inventory information, e.g., address of the new customer, are available. An
arbitrary search does not include line ID as one of the filters.
To specify a neighborhood search, the user can either directly put together a list of neighborhood
filters to create a customized search, or he/she can use one of the pre-defined searches in the
system. In the following, each approach is described in detail.

Page 56 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Custom search:
The custom search option offers the users the ability to customize the neighborhood definitions
and specify new searches. With the custom search option, the users add various filters to
implement specialized neighborhood definitions.
The custom search option is accessible by first clicking on Lines in the Neighborhood under the
Analysis drop-down menu, and then selecting the Custom option from the Neighborhood
Definition drop-down menu. These steps are shown in the figures below.

1. Selecting the Lines in the Neighborhood page from the Analysis menu:

2. Selecting the Custom option:

ASSIA, Inc. Confidential and Proprietary Page 57

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Adding filters:
Any neighborhood search, or definition, is a set of neighborhood filters. Each filter is identified by
the name of the data field that it is operating upon. A new filter can be selected from the Select a
Filter drop-down menu as shown in the figure below:

Additional filters can be added by clicking on the Add Filter button and following the same
procedure as above. Existing filters can be removed by clicking on the Remove Filter button on
the right side of each filter input box.
In general, neighborhood filters are operating on two types of line attributes or data: String data
and numerical data. Similarly, neighborhood filters can be categorized into filters that operate on
string data types, or string filters, and filters that operate on numerical data types, or numerical
filters.
Each neighborhood filter, except for the distance filter that will be discussed later, includes a
number of search options that specify how the filter acts on data. The filter is completely
characterized by the search option and the value entered by the user in the filters input box.
String filters have SAME and EQUAL as search options while numerical filters have DELTA and
RANGE in addition to SAME and EQUAL. The distance filter is an exception and it does not have
a search option.
Availability and function of each search option depends on whether the filter belongs to a
reference-based search or an arbitrary search. In other words, depending on whether the line ID
filter is included in the list of neighborhood filters or not, different search options are available for
a given filter. Before getting into the function of each search option, it is shown below how to
define a reference-based or an arbitrary neighborhood search.
Defining a reference-based or an arbitrary search:
Both reference-based and arbitrary searches can be defined under custom search. Because
search options depend on the search type, the differentiation between a reference-based and an
arbitrary search is done at the first stage of specifying a new neighborhood definition. To define a
reference-based search, the line ID filter is added to the list of filters as the first filter. The line ID
filter can only be added to the list as the first filter. If filters other than line ID are added as the first
filter, the search is defined as an arbitrary search and the line ID filter is from the list of available
filters under the Select a Filter drop-down menu for the rest of filters (i.e., line ID cannot be added
later to the set of filters).
The line ID filter has only EQUAL as the search option and it accepts the reference line ID for the
search as an input. In a reference-based search, the line ID entered in the box is used to identify
the reference line whose attributes are used for the search. However, to complete the

Page 58 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

neighborhood definition, the user must specify at least one more filter to be used for searching as
shown in the figure below.

Additional filters are added by clicking Add Filter and selecting the appropriate filter from the list
under the Add a Filter menu.
If line ID is not selected as a filter, the search is an arbitrary search. In the following, the
functionality of search options is described. Search options together with the values entered by
the user in the corresponding input boxes completely characterize the neighborhood filters.
Search options:
Different search options are available for each filter depending on the search type and filter type.
The function of each search option is described in this section. The distance filter does not have a
search option and is explained in the next section.
Reference-based searches:
Numerical filters: In a reference-based search, only SAME and DELTA search options are
available for numerical filters as explained below:
SAME: When SAME is used as the search option, the input box for the filter is disabled and
the user is not be able to enter a value. A line is declared to be in the neighborhood if the line
and the reference line have the same value for the numerical data field specified by the filter.
DELTA: When DELTA is used as the search option, the input box for the filter is enabled and
the users input is used in specifying the filter. A line is declared to be in the neighborhood if
the absolute difference between the values of the numerical data field specified by the filter
for the line and the reference line is less than or equal to the users input value.
String filters: In a reference-based search, only SAME search option is available for string filters.
Similar to above, the input box for the filter is disabled and the user is not be able to enter a value.
A line is declared to be in the neighborhood if the line and the reference line have the same value
for the string data field specified by the filter.
The figure below provides an example for a reference-based search. The provided line ID
identifies the reference line to be used for the search. All lines that satisfy the following three
conditions are declared to be in the neighborhood:
They have the same city name as the city name of the reference line (note that the input box
is disabled for SAME).
They have the same street name as the street name of the reference line (note that the input
box is disabled for SAME).

ASSIA, Inc. Confidential and Proprietary Page 59

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

They have street numbers within 100 of the street number of the reference line (note that
the input box is enabled for DELTA to accept the bound on street numbers).

Arbitrary search:
Numerical filters: In an arbitrary search, only EQUAL and RANGE search options are available for
numerical filters as explained below:
EQUAL: When EQUAL is used as the search option, the input box for the filter is enabled and
the users input is used in specifying the filter. A line is declared to be in the neighborhood if
the value of the numerical data field specified by the filter is equal to the users input value.
RANGE: When RANGE is used as the search option, the input box for the filter is enabled
and the users input is used in specifying the filter. A line is declared to be in the
neighborhood if the value of the numerical data field specified by the filter is within the
numeric range provided by the user. The user should input the range in min value/max value
format.
String filters: In an arbitrary search, only EQUAL search option is available for string filters.
Similar to above, the input box for the filter is enabled and the users input is used in specifying
the filter. A line is declared to be in the neighborhood if the value of the string data field specified
by the filter is equal to the users input value.
The figure below provides an example for an arbitrary search. All lines that satisfy the following
three conditions are declared to be in the neighborhood:
They have city names equal to CITY_1 (note that the input box is enabled for EQUAL to
accept the city name)
They have street names equal to STREET_1 (note that the input box is enabled for EQUAL
to accept the street name)
They have street numbers between 100 and 200 (note that the input box is enabled for
RANGE to accept the range of street numbers)

Page 60 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

The following table summarizes the availability of each search option for different search types
and filter types:
Search Input box Reference-based search Arbitrary search
options
Numerical String filters Numerical String filters
filters filters
SAME Disabled Available Available Not available Not available
EQUAL Enabled Not available Not available Available Available
DELTA Enabled Available Not available Not available Not available
RANGE Enabled Not available Not available Available Not available

Distance filter:
The distance filter is used to search for lines using their geographical locations and their
distances from a reference point. The distance filter does not have a search option. In an arbitrary
search and without a reference line, the distance filter accepts three inputs from the user as
shown in the figure below:

The user inputs the latitude and longitude of the reference point in degrees and decimal fractions
(not minutes and seconds), and the distance from the reference point. The distance must be in
the units specified in the filter (feet in the above example). This unit is the same length unit (meter
or feet) that is configured in the GUI. In the example above, all the lines that are within 1000 ft
distance of the reference point (latitude: 43.621361, longitude: -111.923417) are considered to be
in the neighborhood.
When the distance filter is used in a reference-based search, the latitude and longitude of the
reference line are used as the reference point and the filter only accepts the distance as an input
from the user.
Modifying a search or starting a new one:
As mentioned earlier, a new filter can be added by clicking Add Filter, and an existing filter can
be removed by clicking Remove Filter. Also, an existing filter can be modified to another filter by
selecting a different filter from the drop-down filter menu.
If the line ID filter is removed from a reference-based search, the search is automatically
converted to an arbitrary search. The other filters are kept in the list. However, resulting from this
change, all DELTA search options are changed to RANGE and all SAME search options are
converted to EQUAL. The user still needs to update the values in the input search boxes.
A new search or definition can be started by clicking Reset.

ASSIA, Inc. Confidential and Proprietary Page 61

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Filter hierarchy:
It is possible to define hierarchies and dependencies among the line attributes. For example, the
following is a reasonable hierarchy to define among the address fields:
City Street name Street number
In other words, the street number field is dependent on the street name field and should be used
only in conjunction with this field; similarly, the street name field is dependent on the city field and
should only be used together with this field. Defining hierarchies or dependencies among the line
attributes is done based on customers inputs and requests, and also based on their inventory
structure at the time of deploying the product.
If a hierarchy is defined among some line attributes, the same hierarchy is also applied to the
neighborhood filters operating on them. For example, for the above hierarchy on address fields,
the street number filter is dependent on the street name filter, and the street name filter is
dependent on the city filter. During addition of a new filter, if a filter with lower in the hierarchy is
added to the list, the software automatically adds all the filters higher in the hierarchy. For the
example above, if the street number filter is added, then both the street name and city filters are
also added to the filters set. Similarly, if a filter higher in thehierarchy is removed from the set, all
the filters lower in the hierarchy are also removed.
Conducting the search:
After completing the neighborhood definition, the search is conducted by clicking on the Submit
button. The list of lines in the neighborhood together with the individual diagnostic results are then
produced. The user is able to run further neighborhood analysis from this page. The results page
is described later in this section.

2.10.2 Pre-defined neighborhood search

The pre-defined neighborhood search options or definitions are pre-configured sets of
neighborhood filters. These filter sets can be either a reference-based or an arbitrary (without a
reference line) search. The pre-defined neighborhood definitions are completely configurable and
can be customized based on the customers needs and inputs received during the product
deployment phase.
A pre-defined search option can be selected by the two approaches described below.
Lines in the Neighborhood from Analysis menu:
A pre-defined search can be chosen by clicking on Lines in the neighborhood under the
Analysis menu (the same as the first step of selecting Custom search) and then selecting one of
the available options under the Neighborhood Definition drop-down menu. This is shown in the
figure below.

Page 62 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

1. From the Analysis menu, select the Lines in the neighborhood page:

2. Select a pre-defined neighborhood search:

If a pre-defined arbitrary search (without a reference) is selected from the drop-down menu, a list
of neighborhood filters together with already configured search options and user inputs are
displayed on a new page. Like the custom search case, the search results are available by
clicking on the submit button. On this page, the user is allowed to switch to custom search and
modify the search as described in the custom search section.
If a pre-defined reference-based search is selected from the drop-down menu, then the list of
filters defining the neighborhood is displayed together with the Line ID field for entering the line
ID of the reference line. The user is not able to modify any of the filters (except for entering line
ID) at this stage as the filters are listed only to illustrate the neighborhood definition.

ASSIA, Inc. Confidential and Proprietary Page 63

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

An address-based neighborhood definition is shown in the figure below as an example.

By entering the line ID of the reference line and clicking Submit, the search results are produced.
Lines in the Neighborhood from GUI per-line pages:
When the Lines in the Neighborhood link in the Line Information table is clicked from any of
the GUI pages, such as the Line Performance Analysis page shown in the example below, the
default reference-based definition configured in the system is used for neighborhood search. The
line ID displayed in the Line Information table is used in the neighborhood search as the
reference line.

The default reference-based search is one of the pre-defined neighborhood definitions and is
configurable.
After entering the page, the list of lines in the neighborhood (lines that are satisfying the search
criteria) together with the individual diagnostic results are displayed.

2.10.3 Neighborhood search results

The neighborhood search results for both types of reference-based and arbitrary searches are
next explained. The results pages for the two types of seaches are almost identical. For a
reference-based search, the page includes the inventory information of the reference line as well
as the list of lines in the neighborhood and their individual diagnostics results. For an arbitrary
search, there is no reference line and consequently, the inventory data table is not displayed.

Page 64 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Neighborhood search results with a reference line (results of a reference-based search):

Detailed Description:
Note: Various fields referenced below are defined with more detail in the section titled Data
Report Fields, which is located at the end of this document. For each field the following
information is displayed: Field Name, Description and Usage, and Screens which contain the field.
Lines in the Neighborhood:
This part displays the neighborhood definition or the set of filters that was used for the search. A
new search can be initiated by choosing a pre-defined neighborhood from the Neighborhood
Definition menu, or by clicking Reset.
The current list of filters can also be modified for another search as was described in the Custom
search section. However, it is not possible to directly change the reference line of the current
reference-based search. The reference line can only be modified by clicking Reset and starting a
new search. The current reference-based search can be converted to an arbitrary search by
removing the line ID filter. When removing the line ID filter, the list of filters is maintained, SAME
and DELTA search options are replaced by EQUAL and RANGE, respectively, and the input
boxes of the filters are updated with information from the recently removed reference-line.
Line Information:
Export CSV: This creates a .csv (comma separated value) file of the data presented in the table
and saves it to the local computer. This file contains a tabular listing of the data that can be
examined using an application such as Microsoft Excel.
Line ID: This field provides the identification information for the line information being
displayed. Line ID is operator dependent and thus this can represent anything from a unique
identifying number to a real telephone number.
DSLAM: The name of the DSLAM in which the Line ID or DSL line is located.
Port: The logical port number in the DSLAM on which the particular service is supported. This
can be formatted in multiple ways, from shelf-slot-port (x-y-z) to rack-shelf-slot-port (w-x-y-z).
This field is DSLAM dependent.
Service Product: Indicates the service product that is provisioned on the line. Clicking on the
service product name produces a pop-up window that displays information about the

ASSIA, Inc. Confidential and Proprietary Page 65

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

maximum rate, service recommendation rate and minimum rate of the service product for
both the downstream and upstream directions.
Line Status: Indicates the status of the line.
Links to related screens:
The following links navigate the user to various screens with information related to either the Line
ID or DSLAM that is currently being examined:
Line Summary | Line Performance Analysis | Real-Time Performance Analysis
Diagnostics Analysis | Real-Time Diagnostics Analysis | SELT Diagnostics Analysis | Historical Data Trends
Lines in the DSLAM | Lines in the Neighborhood | Profile Optimization Analysis | Service Recommendation
Analysis Result:
Inventory information of the Line:
This table displays the inventory information including the address, cable information and
geographical location of the reference line. The set of line attributes and inventory data that are
configured in the system and are used for neighborhood search are displayed in this table.
History Check:
This pull-down menu allows the user to select one of multiple data collection times. Data from the
most recent data collection time are displayed by default. Selecting another time produces a
display of the corresponding historical data.
Report Type:
The user can specify how to display the neighborhood search results by using this drop-down
menu. This menu is set to Detail Report by default. For the Detail Report option, the
neighborhood search results is displayed in the Lines in the Neighborhood table as described
below.
For the Statistics Report option, statistical measures for DSL performance of the lines in the
neighborhood are generated. These statistics are displayed on a new page and can be used for
neighborhood diagnostics and neighborhood pre-qualification purposes. This page is described in
full detail in the Neighborhood Analysis section.
Running Standard:
By choosing ADSL, VDSL or ALL from this drop-down menu, only ADSL lines, only VDSL lines or
all the lines in the neighborhood are displayed in the Line in the Neighborhood table. The list of
diagnostics results displayed in the table is also updated according to the selected DSL
standards: ADSL-specific diagnostics for ADSL lines and VDSL-specific diagnostics for VDSL
lines. This feature is described in detail in the Lines in the DSLAM section.
Lines in the Neighborhood Table:
This table provides a summary of diagnostics information for all lines in the neighborhood of the
selected line. Each row contains information on a specific line.
Table Data:
Line ID: This is the unique identified for this line. Line ID is operator dependent and therefore
can represent anything from a unique identifying number to a real telephone number. Line ID
is a hyperlink that leads to the Line Performance Analysis screen for that selected line.
Geodata: The geographical location (latitude and longitude) for the customer premise where
the line terminates (if available and configured in the system).
Cable: The make-up information of the cable that feeds the customer premises where the line
terminates (if available and configured in the system).

Page 66 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Address: The address for the customer premises where the line terminates.
DSLAM: The name of the DSLAM in which the Line ID or DSL line is located.
Port: The logical port number in the DSLAM on which the particular service is supported. This
can be formatted in multiple ways, from shelf-slot-port (x-y-z) to rack-shelf-slot-port (w-x-y-z).
This field is DSLAM dependent.
Estimation Date: Date when the estimation was performed by DSL Expresse.
Date of Collection: Date when the data was collected by DSL Expresse.
Data Source: Source of data (POP_O or PER_TONE) that is used for performance
estimation.
Running Standard: Operating DSL standard on the line.
Loop Length: The equivalent electrical loop length as estimated by DSL Expresse.
US MABR (kbps): The upstream MABR. For ADSL lines, the value is the US reported MABR.
For VDSL lines, the value is the US estimated MABR.
DS MABR (kbps): The DS estimated MABR (estimated by DSL Expresse).
US MABR in the lowest 1 percent: When this condition is detected, then this lines US MABR
ranks at the bottom 1 percent among all lines in the network with a similar loop length.
DS MABR in the lowest 1 percent: When this condition is detected, then this lines DS MABR
ranks at the bottom 1 percent among all lines in the network with a similar loop length.
US MABR Percentile: The value represents the lines US MABR percentile ranking when
compared to all lines in the network with a similar loop length.
DS MABR Percentile: The value represents the lines US MABR percentile ranking when
compared to all lines in the network with a similar loop length.
Bad-splice: Indicates whether a bad splice has been detected on the loop.
Unbalanced Wiring: Indicates whether unbalanced wiring is affecting DSL performance.
First detected Bridged Tap Length: The equivalent electrical length of the first detected
bridged tap as estimated by DSL Expresse. This is only evaluated when per-tone data are
available. If no bridged tap is detected, 0 is displayed. If not enough information is available
for detection or length estimation, N/A is displayed.
Second detected Bridged Tap Length: The equivalent electrical length of the second detected
bridged tap as estimated by DSL Expresse. This is only evaluated when per-tone data is
available. If no second bridged tap is detected, 0 is displayed. If not enough information is
available for detection or length estimation, N/A is displayed.
US Impulse Noise: Indicates whether impulse noise is affecting DSL performance in the
upstream direction.DS Impulse Noise: Indicates whether impulse noise is affecting DSL
performance in the downstream direction.
Stability: This is the lines stability as evaluated by DSL Expresse. There are four stability
levels: VERY STABLE, STABLE, UNSTABLE and VERY UNSTABLE. A line evaluated as
one of the first two is categorized as a stable line, and a line evaluated as one of the last
two is considered an unstable line. If there is not enough data to evaluate the stability,
UNKNOWN is displayed.
Instability reason: When the line is evaluated as UNSTABLE or VERY UNSTABLE, this field
provides the reason using a three-bit code. AM or AM like Noise: AM signal ingress is having
an effect on transmission.High Power Noise: The received noise is at an abnormally high
level and can affect the data rate performance of the line.

ASSIA, Inc. Confidential and Proprietary Page 67

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

High Power Noise in High Frequency: The received noise is at an abnormally high level at the
higher frequencies of the ADSL band. This condition is evaluated and displayed only for
ADSL lines.
Low Frequency Crosstalk: The received noise is at an abnormally high level at the lower
frequencies and is resembling crosstalk generated by symmetric DSL systems. This condition
is evaluated and displayed only for ADSL lines.
HAM Noise: Noise from HAM amateur radio is detected. This condition is evaluated and
displayed only for VDSL lines and only when per-tone data is available.
ADSL FEXT: ADSL FEXT detected. This condition is evaluated and displayed only forADSL
lines and only when per-tone data is available.
VDSL FEXT: VDSL FEXT detected. This condition is evaluated and displayed only for VDSL
lines and only when per-tone data is available.
Noise Fluctuation: The received noises power spectral density is changing significantly.
Potential Missing Microfilter: Indicates that at least one DSL microfilter may be missing or
may be improperly installed.
Daily Periodic Impairment: When this condition is detected, then the lines stability is
periodically degraded and this degradation starts at approximately the same time every day.
An estimate of the start time is displayed in the Comment column.
US Average EFTR (kbps): When support for g.inp is enabled, and the line operates in g.inp
mode, this quantity is the average error-free throughput rate over the past 24 hours in the
upstream direction. The percentage represents the error-free throughput rate relative to the
throughput of a line with no errors.
DS Average EFTR (kbps): When support for g.inp is enabled, and the line operates in g.inp
mode, this quantity is the average error-free throughput rate over the past 24 hours in the
downstream direction. The percentage represents the error-free throughput rate relative to
the throughput of a line with no errors.
CPE Interoperability Issue: Indicates if a CPE interoperability issue is detected. This field
currently applies only to the case when vectoring support is enabled. If the line is connected
to a vector-capable line-card and is using a vectored profile, this field indicates if the CPE is
not vector-capable and therefore unable to achieve a connection in vectored mode.
US MABR FEXT Mitigated (kbps): When vectoring support is enabled, this value represents
the lines US MABR assuming that the FEXT present on the line can be eliminated. This
value is estimated by DSL Expresse.
DS MABR FEXT Mitigated (kbps): When vectoring support is enabled, this value represents
the lines DS MABR assuming that the FEXT present on the line can be eliminated. This
value is estimated by DSL Expresse.
Bonded Lines:
For bonded lines the line in the neighborhood of only one constituent port within the bonded
group is shown on this page. To see the lines in the neighborhood of another constituent port,
simply click the port of interest in the Bonded Ports column of the Line Information section.

Page 68 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Neighborhood search results without a reference line (results of an arbitrary search):

As mentioned earlier, the contents of this page is almost identical to the result page of a
reference-based search. (For this example, g.inp support is disabled.) The Line Information
table, the links underneath and the table for the reference lines inventory data are not displayed.

2.10.4 Neighborhood Analysis

The contents of the neighborhood statistics report depend on the neighborhood search type. As
reference-based searches and arbitrary searches have different neighborhood use-cases
(diagnostics vs. pre-qualification), different statistics are generated for each of the two
neighborhood search types.

Neighborhood analysis for a reference-based search:

The following figures provide examples of the Statistics Reports page for cases where the
reference line is ADSL or VDSL.

ASSIA, Inc. Confidential and Proprietary Page 69

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

ADSL reference line:

Page 70 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

VDSL reference line:

ASSIA, Inc. Confidential and Proprietary Page 71

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Detailed Description:
Note: Various fields referenced below are defined with more detail in the section titled Data
Report Fields, which is located at the end of this document. For each field the following
information is displayed: Field Name, Description and Usage, and Screens which contain the field.
Neighborhood definition and filters:
This part displays the neighborhood definition or the set of filters that was used for the search. It
is identical to the one in the Detail Report page. A new search can be initiated by choosing a pre-
defined neighborhood from the Neighborhood Definition drop-down menu, or by clicking on the
reset button, or by modifying the current list of filters.
Line Information:
Line ID: This field provides the identification information for the line information being
displayed. Line ID is operator dependent and thus this can represent anything from a unique
identifying number to a real telephone number.
DSLAM: The name of the DSLAM in which the Line ID or DSL line is located.
Port: The logical port number in the DSLAM on which the particular service is supported. This
can be formatted in multiple ways, from shelf-slot-port (x-y-z) to rack-shelf-slot-port (w-x-y-z).
This field is DSLAM dependent.
Service Product: Indicates the service product that is provisioned on the line. Clicking on the
service product name produces a pop-up window that displays information about the
maximum rate, service recommendation rate and minimum rate of the service product for
both the downstream and upstream directions.
Line Status: Indicates the status of the line.
Links to related screens:
The following links navigate the user to various screens with information related to either the Line
ID or DSLAM that is currently being examined:
Line Summary | Line Performance Analysis | Real-Time Performance Analysis
Diagnostics Analysis | Real-Time Diagnostics Analysis | SELT Diagnostics Analysis | Historical Data Trends
Lines in the DSLAM | Lines in the Neighborhood | Profile Optimization Analysis | Service Recommendation
Report Type:
The drop-down menu is the same as the one in Detail Report. The user can switch back to the
Detail Report page by selecting the page from this menu.
MABR Statistics:
This table contains statistics on the MABR distribution of all ADSL and VDSL lines in the
neighborhood. The DSL Expresse estimated US MABR and estimated DS MABR are used for all
the analyses except for the upstream direction of ADSL lines.
The rows identify the following MABR statistics:
The total number of ADSL/VDSL lines in the neighborhood.
The number of ADSL/VDSL lines in the neighborhood for which the US/DS MABR is less
th
than the 50 percentile of lines in the network with similar loop length.
The number of ADSL/VDSL lines in the neighborhood for which the US/DS MABR is less
th
than the 10 percentile of lines in the network with similar loop length.
The number of ADSL/VDSL lines in the neighborhood for which the US/DS MABR is less
st
than the 1 percentile of lines in the network with similar loop length.

Page 72 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Maximum US/DS MABR of all ADSL/VDSL lines in the neighborhood in kbps.

Average US/DS MABR of all ADSL/VDSL lines in the neighborhood in kbps.
Loop Length Statistics:
This table lists the number of lines in the neighborhood that are operating with the same standard
as the reference line (ADSL or VDSL) and have similar loop length to this line. Only ADSL lines
are counted if the reference line is ADSL, and only VDSL lines are counted if the reference line is
VDSL.
The rows identify the following:
The loop length range including the loop length of the reference line and the configured range.
The number of ADSL/VDSL lines in the neighborhood that have loop lengths in the specified
range.
MABR comparison of similar loop length lines:
This table contains a comparison between the MABR of the reference line and the MABR of all
the lines in the Neighborhood with similar loop length and the same DSL standard. Only the lines
that are counted in the Loop Length Statistics table above are considered for comparison. The
DSL Expresse estimated US MABR and estimated DS MABR are used for all the analyses
except for the upstream direction of ADSL lines.
The rows identify the following MABR comparisons:
The estimated US MABR and estimated DS MABR of the reference line.
All other rows represent the Average MABR for lines in the neighborhood without various
noise, disturbers or faults present. If no line is found in the neighborhood without a given fault
e.g., no lines without High Power Noise, N/A is displayed.
Noise Analysis Statistics:
This table lists the number of lines in the neighborhood that are running with the same standard
as the reference line (ADSL or VDSL), and for which DSL Expresse has detected impairment due
to various noise conditions. The specific conditions for which a count is kept in this table are
defined in the Data Report Fields section.
High Power Noise
High Power Noise in High Frequency (evaluated and displayed only for an ADSL reference
line)
AM or AM like Noise
Low Frequency Crosstalk (evaluated and displayed only for an ADSL reference line)
HAM Noise (evaluated and displayed only for a VDSL reference line and when per-tone data
is available)
ADSL FEXT (evaluated and displayed only for a VDSL reference line and when per-tone data
is available)
VDSL FEXT (evaluated and displayed only for a VDSL reference line and when per-tone data
is available)
Other Statistics:
This table lists the number of lines in the neighborhood that are running with the same standard
as the reference line (ADSL or VDSL) and for which DSL Expresse has detected impairment due
to various conditions. The specific conditions for which a count is kept in this table are defined in
the Data Report Fields section.

ASSIA, Inc. Confidential and Proprietary Page 73

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Bad Splice
Unbalanced Wiring
DS impulse Noise
US impulse Noise
Bridged tap (evaluated and displayed only when the per-tone data is available)
Bonded Lines
For bonded lines, the neighborhood analysis of only one constituent port within the bonded group
is shown on this page. To see the neighborhood analysis of another constituent port, simply click
the port of interest in the Bonded Ports column of the Line Information section.
Note that the neighborhood analysis treats each constituent port within a bonded group as a
separate line. Since ports within a bonded group terminate at the same address, they are
considered neighbors. Any field which counts the total number of DSL lines in the neighborhood
counts individual ports, so e.g. a neighborhood with 20 bonded lines with 2 ports within each
bonded group is counted as having a total of 40 DSL lines in the neighborhood.
Neighborhood analysis for an arbitrary search (without a reference line): The following
figure shows the Statistics Report page for an arbitrary search. Without a reference line, the Line
Information table and the line underneath are not displayed.

Page 74 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Since there is no reference line, the MABR Comparison table is omitted and the Loop Length
Analysis table shows some statistics on all the lines in the neighborhood.
Loop Length Statistics:
This table provides some statistics on the loop length of the lines in the neighborhood.
The rows identify the following:
The average loop length of all ADSL/VDSL lines in the neighborhood.
The minimum loop length of all ADSL/VDSL lines in the neighborhood.
The maximum loop length of all ADSL/VDSL lines in the neighborhood.
Also, without a reference line, the Noise Analysis Statistics and the Other Statistics tables are
shown for both ADSL and VDSL lines in the neighborhood.

ASSIA, Inc. Confidential and Proprietary Page 75

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

2.11 Profile Optimization

This screen provides information about the state of the line in the Profile Optimization (PO)
process.

Detailed Description:
This screen allows the user to request an analysis of the information on a particular line (or
bonded group of lines) and to recommend a new profile for the line(s). The algorithms invoked
use the gathered historical information about the line to generate a suggested new profile.
Schedules:
Profile optimization can start at a scheduled time, or start immediately depending on the user
request.
Nightly scheduled optimization: Profile Optimization starts at a scheduled time (e.g. 2:00 AM)
and continues for multiple days until the line reaches its optimal profile.
Real-time optimization: Profile Optimization starts immediately, and all the optimization
processes including profile change complete within a few minutes. Users may choose real-
time optimization if it is desired to make an immediate profile change to the line in case the
lines condition has changed and its current profile is believed to be not optimal. Once real-

Page 76 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

time optimization is completed, a nightly optimization process is scheduled to keep

monitoring the line and find the optimal profile with additional data.

Note: Various fields referenced below are defined with more detail in the section titled Data
Report Fields, which is located at the end of this document, where the following information is
displayed: Field Name, Description and Usage, and Screens that contain the fields.
Line Information:
Line ID: This field provides the identification information for the line being displayed. Line ID
is operator dependent and the operator can choose any number that can uniquely identify
each line, such as a real telephone number or an arbitrarily chosen number.
DSLAM: The name of the DSLAM in which the Line ID or DSL line is located.
Port: The logical port number in the DSLAM on which the particular line (or service) is
supported. This can be formatted in multiple ways, from shelf-slot-port (x-y-z) to rack-shelf-
slot-port (w-x-y-z). This field is DSLAM dependent.
Service Product: The service product that is associated with the line. Clicking on the service
product name pops up a window that displays information about the maximum rate, service
recommendation rate and minimum rate of the service product for both the downstream and
upstream directions.
Line Status: The status of the line (e.g., active or de-activated).
Links to related screens:
The following links allow the user to navigate to various screens with information related to either
the Line ID or DSLAM that is currently being examined:
Line Summary | Line Performance Analysis | Real-Time Performance Analysis
Diagnostics Analysis | Real-Time Diagnostics Analysis | SELT Diagnostics Analysis | Historical Data Trends
Lines in the DSLAM | Lines in the Neighborhood | Profile Optimization Analysis | Service Recommendation
History Check:
This pull-down menu allows the user to select one of multiple times when profile optimization was
requested. The most recent profile optimization is displayed by default. Selecting another time
produces information about the corresponding past profile optimization. This pull-down menu
includes time for both real-time and nightly scheduled optimization processes, and real-time
optimization times are labeled with real-time for easier distinction.
Status:
This table shows the following:
If Profile Optimization is enabled for this specific line.
If a real-time or nightly scheduled Profile Optimization is currently in progress for this specific
line. It also allows the user to start or stop Profile Optimization.
When the last Profile Optimization was completed.
Note: the ability to start and stop the Profile Optimization for a specific line via the GUI is a
per-user configurable option.
Options for profile optimizations:
When the user starts Profile Optimization, the pop-up window displays three options for
optimization (depending on customer configuration).

ASSIA, Inc. Confidential and Proprietary Page 77

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Real-time PO with real-time data ONLY: Start real-time PO with real-time data ONLY for
optimization. This option is selected if the line condition has changed significantly and old
data must be ignored (e.g. a technician has fixed the line recently)
Real-time PO with real-time and old data: Start real-time PO with both old data and real-time
data for optimization if old data (e.g. previous 5 days) can be included for analysis
Nightly PO: Schedule nightly PO. Optimization for the line will start at a scheduled time (e.g.
2:00AM) and continue for multiple days until the line reaches the optimal profile.

Status of Past Profile Optimization:

This table shows detailed information related to the last Profile Optimization performed.
Table Data:
Request Date: Date when the PO process was requested/kicked off.
Source of Request: The origin of the PO request (e.g., Call Center or New Line)
Service Product: Service Product associated with the specific line.
Original Profile: Name of the original profile associated with this line.
Final Profile: Name of the final profile associated with this line after the most recent PO
process.
Completion Date: Date when the most recent PO process finished.
Status Code: Status of the most recent PO process upon completion. This outputs a number
which maps to a specific status definition. If this field is populated, this definition can be
obtained through a pop-up window.
Total Number of Profile Change Requests: The total number of profile changes that occurred
during the most recent PO process.
Total Number of Successful Profile Changes: The total number of successful profile changes
that were completed in the most recent PO process.
Total Number of Profile Optimization Iterations: The total number of PO iterations during the
most recent PO process.
Details of Historical Profile Change Recommendation:
This table shows the number of recommendations made by the PO engine, as well as the specific
profile (name) that was recommended.
Line Statistics:
This table shows the before and after stability and the average upstream and downstream data
rates. This allows for a comparison to be made before and after line optimization.
Bonded Lines
The profile optimization analysis of only one constituent port for bonded lines within the bonded
group is shown on this page. To see the profile optimization analysis of another constituent port
simply click the port of interest in the Bonded Ports column of the Line Information section.

Page 78 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

The constituent ports within a bonded group enter and exit profile optimization as one. For this
reason, clicking Start PO for a bonded line starts profile optimization for all ports on that line.
Similarly, clicking the Stop PO button for a bonded line stops profile optimization for all ports on
that line.
Note that the History Check pull-down menu shows the history of profile optimization on the port
being viewed. There may be a slight difference in the optimization times of the different
constituent ports within a bonded group.
Manual Profile Roll-back:
Manual profile roll-back provides the capability to roll-back any lines to the original profile after the
optimization of the line is complete. Roll-back button is enabled next to original profile of the
status of past profile optimization table if the following conditions are met:
The original profile is different from the final profile in the optimization record.
A line is not currently under optimization. If a line is currently under optimization, users should
stop profile optimization by clicking the Stop PO button.
The current service product and line card information of the line are consistent with those of
optimization records. For example, if the service product of the line changed in the past, roll-
back is not allowed for any optimization records prior to the service change date.
By clicking the Rollback button, a profile change request will be sent immediately to the profile
change system and a message will show whether the request was submitted successfully or not.
However, it doesnt check whether the profile change is actually successful or not. Profile change
may not happen immediately depending on the profile change system, so users should check the
Real-Time Performance Analysis page to confirm the profile change result.

Real-time Profile Optimization:

Real-time profile optimization is part of the profile optimization Analysis Result window, and it
provides additional information as shown below.

Status of Real-time Optimization:

This table shows whether each step in real-time optimization is successful or not, and how long it
takes to complete each step.

ASSIA, Inc. Confidential and Proprietary Page 79

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Table entries:
First Real-time Data Collection: Real-time PO triggers the first real-time data collection to
obtain the latest condition of the line.
Profile Optimization: After the real-time data collection is completed, profile optimization starts
immediately, and recommends profile change(s) if the line condition can be improved.
Profile Change: If the profile optimization algorithm produces a recommendation for a new
profile for the line, a profile change is immediately made to the line.
Second Real-time Data Collection: After the profile change is made, the second real-time
data collection is triggered to check the new condition of the line.
Overall: Real-time PO consists of multiple steps listed above, and the overall status is
successful when every step is successful.

First Real-time Data Collection

The first real-time data collection shows the line condition before starting the profile optimization.
This step is similar to Real-Time Performance Analysis except that Bit distribution, Vendor ID, and Line
Counter plots are minimized on the GUI by default.

Profile in Use:
This table shows the current profile name and parameter settings that are in use for the line. The
fields of the table are listed below.
Min Rate (kbps)
Max Rate (kbps)
Planned Rate (kbps)
Min Margin (dB)
Target Margin (dB)
Max Margin (dB)
Max Power (dBm)
Max PSD (dBm/Hz)
Delay (ms)
INP (symbols)
Supported Standards
Interleaving
Trellis Coding

Line Attributes:
This table shows the current line state for the line. The fields of the table are listed below:
State of the Current Line
Current Rate (kbps)
MABR (kbps)

Page 80 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Margin (dB)
Attenuation (dB)
Power (dBm)
Running Standard
Actual INP
Actual Delay

Bit Distribution:
This graph displays the current bit distribution for the line.

Vendor ID:
This table shows information collected by the DSLAM related to specifically to the CPE currently
connected to the line. The fields of the table are listed below:
CPE Vendor ID
CPE Firmware Version Number
CPE Serial Number
Other

Line Counters:
This section contains tables with various incremental error counters. These counters display
counts of the respective errors in 15 minute intervals.The fields of the table are listed below.
Downstream CVs
Upstream CVs
Downstream ES
Upstream ES
Downstream FEC
Upstream FEC
Retrain Count
Downstream leftr Seconds
Upstream leftr Seconds
Downstream Average EFTR
Upstream Average EFTR

Profile optimization and profile change:

This section includes the profile recommendation and the result of the profile change. The fields
of the table are listed below.

ASSIA, Inc. Confidential and Proprietary Page 81

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Original Profile: Name of the original profile associated with this line before the
optimization.
Next Profile: Name of the next profile that is recommended by PO.

Second Real-time Data Collection

The second real-time data collection shows the line condition after profile changes. This step is
similar to Real-Time Performance Analysis except that Bit distribution, Vendor ID, and Line Counter plots
are minimized on the GUI by default.

Status of Profile Optimization:

This table shows detailed information related to the profile optimization performed as a part of
real-time optimization. This table is the same as the status of Past Profile Optimization. The
fields of the table is listed below.
Request Date: Date when the PO was requested/kicked off.
Source of Request: the origin of the PO request (e.g., Call Center or New Line)
Service Product: Service Product associated with the line.
Original Profile: Name of the original profile associated with this line.
Final Profile: Name of the final profile associated with this line after the most recent PO
process.
Completion Date: Date when the most recent PO process is completed.
Status Code: Status of the most recent PO process upon completion. This outputs a
number which maps to a specific status definition. If this field is populated, this definition
can be obtained through a pop-up window.
Total Number of Profile Change Requests: The total number of profile changes that
occurred during the most recent PO process. In real-time optimization, only one profile
change is requested, so this does not exceed 1.
Total Number of Successful Profile Changes: The total number of successful profile
changes that were completed in the most recent PO process. In real-time optimization, a
successful profile change can be confirmed by the second real-time data collection.
Note: If the operators profile change system is used in lieu of DcPc, the second data
collection may happen before the actual profile change because of possible latency of the
operators system. In that case, this field may display 0 even when the profile change
turns out to be successful.
Total Number of Profile Optimization Iterations: The total number of PO iterations during
the most recent PO process. In real-time optimization, this can be either 0,1, or 2. After
the successful second data collection, real-time PO may complete one more iteration of
optimization to finalize the analysis of the line without making any profile recommendation.
Thus, two iterations do not lead to more than one profile change.

Page 82 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

2.12 Compare Lines

This screen allows multiple lines to be listed and directly compared to each other.

Detailed Description
Compare Lines: This text box displays multiple lines separated by commas and a summary of
relevant information on each for comparison.
Line Operation Comparison: This table lists a summary of the current lines being compared
and their respective current line operational statistics. The statistics being displayed for each line
are the operational statistics of the line at the time of the last measurement period.
The Line ID is a hyperlink that takes the user to the Line Performance Analysis screen.
Performance Evaluation Comparison: This table lists a summary of current lines being
compared and their respective performance evaluations. This is a summary of the possible faults
that are present on the line at the time of the last measurement period.
The Line ID is a hyperlink that takes the user to the Diagnostics Analysis screen.

ASSIA, Inc. Confidential and Proprietary Page 83

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

2.13 Service Recommendation

This screen provides Service product Recommendations (including up-sell opportunities) for
individual lines.

Page 84 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Detailed Description:
Line Information:
Line ID: This field provides the identification information for the line information being
displayed. Line ID is operator dependent and can represent anything from a unique
identifying number to a real telephone number.
DSLAM: The name of the DSLAM in which the Line ID or DSL line is located.
Port: The logical port number in the DSLAM on which the particular service is supported. This
can be formatted in multiple ways, from shelf-slot-port (x-y-z) to rack-shelf-slot-port (w-x-y-z).
This field is DSLAM dependent.
Service Product: Indicates the service product that is provisioned on the line. Clicking on the
service product name produces a pop-up window that displays information about the
maximum rate, service recommendation rate and minimum rate of the service product for
both the downstream and upstream directions.
Line Status: Indicates the status of the line.
Links to related screens:
The following links navigate the user to various screens with information related to either the Line
ID or DSLAM that is currently being examined:
Line Summary | Line Performance Analysis | Real-Time Performance Analysis
Diagnostics Analysis | Real-Time Diagnostics Analysis | SELT Diagnostics Analysis | Historical Data Trends
Lines in the DSLAM | Lines in the Neighborhood | Profile Optimization Analysis | Service Recommendation
Current Service:
This table shows the current service provisioned on the respective line.
Service Product: The current service product designated for this line

ASSIA, Inc. Confidential and Proprietary Page 85

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Profile: The current profile assigned to this line

DS Current Rate (kbps)
US Current Rate (kbps)
Stability: Evaluation of stability observed on this line at the time of execution of the Service
Recommendation algorithm
Running Standard: Operating DSL standard on the line
Loop Length: The equivalent electrical loop length as estimated by DSL Expresse

History Check:
This pull down menu displays results from the selected Service Recommendation timeframe. The
most recently available timeframe information is displayed by default.
Duration:
This pull-down menu allows the user to select a duration in weeks, which represents the length of
observation that is applied to produce the aggregate service recommendation.

Service Recommendation: Service recommendation per group for the given duration. If multiple
service groups are present (e.g. DATA or IPTV or VDSL), this table shows a recommended
service product for each group. Otherwise, this table shows a single recommendation for the
given duration (in weeks). A service recommendation for duration of more than one week is
obtained by combining the weekly service recommendations calculated for duration of one week.
Service Group: A service group consists of services that have similar characteristics, and
SR generates a recommendation per service group (e.g. DATA or IPTV). This column can be
disabled if only one service group exists.
DS MABR (kbps): Downstream MABR range for the given duration. MABR can vary
depending on the service group because each service group may require different DSL
parameters, which can affect MABR estimations (margin, power, minimum INP etc.)
US MABR (kbps): Upstream MABR range for the given duration. MABR can vary depending
on the service group because each service group may require different DSL parameters,
which can affect MABR estimations (margin, power, minimum INP etc.)
Recommended Service Product: A recommended service product for the given service
group. If a line is not qualified for any of the services of the service group, No service
recommended is displayed.
Actual Duration (Weeks): A service recommendation is typically produced once per week,
and users can choose different duration to combine (aggregate) multiple weeks of
recommendations. The displayed value is the actual number of single-week results that were
combined, and it may be smaller than the duration that the user selected when data are not
available for certain weeks.
The aggregation capability to combine service recommendations from multiple weeks was
added with Release 2.5. When upgrading from Release 2.3 to Release 2.5, aggregation is not
performed for dates before the time of upgrade. For those past dates, weekly service
recommendations are still shown for each service product.
Show Details: This is a mechanism to hide other useful but not frequently needed reports:
Equipment Upgrade and Service Recommendation for all services. If there is an equipment
upgrade suggestion then the message Equipment Upgrade is suggested is displayed right
before the Show Details message. When the user clicks on Show Details, Service

Page 86 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Recommendation for all Services will be displayed, and if there is an equipment upgrade
suggestion, that equipment upgrade report is also displayed.
Service Recommendation for each service:
This shows detailed information on service recommendation results and statistics of past weeks
for each service product.
Service Group: Service Group to which this service product belongs.
Service Products: A list of all applicable service products offered by the provider.
Recommendation for the Selected Date: Indicates if the service product is recommended
for the given line.
Recommendation code: Code indicating the reason for the Service Recommendation.
Recommendations for the last 30 days: The number of recommendations made in the last
30 days for the line.
Recommendations for the last 90 days: The number of recommendations made in the last
90 days for the line.
Equipment Upgrade: This table shows the recommendation of the services that can be
supported only with equipment upgrade (e.g., upgrade from ADSL1 to ADSL2+ CPE or linecard).
It is displayed only if there is an equipment upgrade suggestion for the selected date and duration.
Service Group: A service group consists of services that have similar characteristics, and
SR generates a recommendation per service group (e.g. DATA or IPTV). This column can be
disabled if there exists only one service group.
Equipment Upgrade: DSL standard that is used to evaluate the equipment upgrade.
Equipment or profiles should support this standard for this line to be qualified for the
recommended service product.
DS MABR(kbps): Downstream MABR range for the given duration. MABR can vary
depending on the service group because each service group may require different DSL
parameters, which can affect MABR estimations (margin, power, minimum INP etc.)
US MABR(kbps): Upstream MABR range for the given duration. MABR can vary depending
on the service group because each service group may require different DSL parameters,
which can affect MABR estimations (margin, power, minimum INP etc.)
Recommended Service Product: A recommended service product for the given service
group. If a line is not qualified for all the services of the service group, No service
recommended will be displayed.
Actual Duration(Weeks): A service recommendation is typically produced once per week,
and users can choose different duration to combine (aggregate) multiple weeks of
recommendations. The displayed value is the actual number of single-week results that were
combined, and it may be smaller than the duration that the user selected when data are not
available for certain weeks.
Bonded Lines
Service recommendations for bonded lines are made for the entire bonded group, based on the
individual capacities of the constituent ports. For each bonded service product, the service
recommendation page shows whether the service product is recommended, along with any
associated recommendation codes and statistics.
Other constituent ports within the bonded group can be selected from the Bonded Ports column
of the table in the Line Information section. However, since service recommendations are
conducted for the entire bonded group, this has no effect on the displayed recommendations

ASSIA, Inc. Confidential and Proprietary Page 87

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

3 Reports
This screen offers a high level description of each of the Report types available in DSL Expresse.
By selecting one of the Report types, either by choosing the Report from this screen or from the
submenus on the navigation bar, the respective Report screen is displayed.

Page 88 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

3.1 Diagnostics
3.1.1 Statistics Report
This screen allows the user to generate a diagnostics summary report of all lines managed by
DSL Expresse.

ASSIA, Inc. Confidential and Proprietary Page 89

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Page 90 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Detailed Description
Date: This menu allows the user to select the desired report date. If the date selected has a
report available, the report is displayed. If not, an error message indicating that the report is
unavailable is displayed. The default date shown is the most recent with results. Selecting Query
generates the report.
Diagnostics Table: This table presents the user with statistics about diagnostics faults found on
the lines during the selected report date.
Table Format:
Switch report type. This menu allows the user to select either the default display of the
diagnostics summary in tabular format or to display the same information formatted as a bar
chart.
Export CSV This creates a .csv (comma separated value) file of the data presented in the
table and saves it to the local computer. This file contains a tabular listing of the data that can
be examined using an application such as Microsoft Excel.
Categorization. This indicates the type of disturber or impairment.
Number of Lines. This gives the number of lines experiencing the particular condition
compared to the total number of lines analyzed for that condition. Each number in this column
is a hyperlink that takes the user to the Diagnostics List of Lines screen which shows a
complete list of all the individual lines that are diagnosed with that specific disturber.
Stability:
This section displays a pie chart of the number of lines in each stability level: VERY STABLE,
STABLE, UNSTABLE, VERY UNSTABLE or UNKNOWN.
Loop Length:
This section displays the distribution of lines versus the equivalent electrical loop length . The
loop length units and assumed cable types are configurable per customer.
Bonded Lines
Each constituent port for bonded lines is treated individually when the diagnostics summary
report is generated. A bonded group consisting of two ports is counted as two lines in the reports
results.

ASSIA, Inc. Confidential and Proprietary Page 91

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

3.1.2 Detail Report

This screen shows the user the diagnostics results for individual lines for the selected date.

Detailed Description:
This screen can be accessed either by going to the Diagnostics Summary Report page and
selecting a specific Impairment Categorization that shows an issue, or by using the sub-menu
Detailed Reports under the Report > Diagnostics menu on the navigation bar.
From this screen, users can search lines with any impairment based on several criteria available
in the drop-down boxes.
Date: This allows any date with diagnostics data to be selected.
Checking Field: This allows the user to search data by impairment category. The list contains all
the possible types of impairment for the lines.
Field Value: This selects to view the lines that have the specified impairment present (Yes) or do
not have the specified impairment present (No).
Export CSV This creates a .csv (comma separated value) file of the data presented in the table
and saves it to the local computer. This file contains a tabular listing of the data that can be
examined using an application such as Microsoft Excel.
Line ID: This hyperlink brings the user to the Line Performance Analysis screen for that specific
line and date.
Bonded Lines
Each constituent port for bonded lines within the bonded group is listed as a separate row in the
Diagnostics List of Lines table.

Page 92 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

3.2 Profile Optimization

3.2.1 Statistics Report
This screen allows the user to generate a report with statistics with Profile Optimization results for
all lines managed by DSL Expresse.

ASSIA, Inc. Confidential and Proprietary Page 93

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Detailed Description
Date: The start and end dates can be used to select a specific date or a range of dates to display
the Profile Optimization related data. Selecting Query updates the screen with information for the
selected dates.
Profile Optimizer Statistics:
This table shows the number of lines that are PO enabled or are currently active in the PO
process. It also shows the total number of lines that entered the PO process. The values
presented in this table are hyperlinks to the Profile Optimization List of Lines screen. The list can
be used to search or access directly each of the following request types: Active Requests or
Completed Requests. Each of these screens show the per-line Profile Optimization details and
can be accessed via the statistics report page as explained above or using the sub-menus under
the PO Optimization tab on the navigation bar.
Completed Lines Statistics:
This table shows the total number of lines that completed the PO process, the average number of
profile iterations, the average number of requested profile changes, and the average number of
successful profile changes.
Completed Lines - Before and After Comparison:
These tables show a statistical comparison of lines before and after Profile Optimization.
Specifically, they show the total number of lines in the various stability categories and the total
number of lines in different data rate ranges (separately for DS and US). The output of these
tables can be presented in a table, pie chart or bar chart format as selected by the Switch report
type menu.
Bonded Lines
Note that each constituent port for bonded lines is treated individually when the profile
optimization report is generated. A bonded group consisting of two ports is counted as two lines
in the statistics that are shown.

3.2.2 Detail Report

This screen allows the user to search for specific lines in the PO process using various criteria.

Detailed Description
The report displays individual lines that are active in the Profile Optimization process, or have
completed it.
Start Date: The earliest date to be used in the search.
End Date: The latest date to be used in the search.

Page 94 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Checking Field: Search for lines using this specified criterion. The values of this field can be
either of the following:
Stability based: The stability designation at the start or at the end of the PO process.
Data-rate based: The Data Rate range at the start or at the end of the PO process, for either
the downstream or the upstream direction.
Field Value: This provides the specific search criterion based on the above Checking Field.
Bonded Lines
Note that each constituent port for bonded lines within the bonded group is listed as a separate
row in the Profile Optimization List of Lines table.

3.2.3 Active Requests

This screen shows detailed Profile Optimization information on a per-line basis for lines currently
in Profile Optimization.

Detailed Description:
The results displayed are for individual lines still in the Profile Optimization process.
Export CSV This creates a .csv (comma separated value) file of the data presented in the table
and saves it to the local computer. This file contains a tabular listing of the data that can be
examined using an application such as Microsoft Excel.
Line ID: Click to open the Profile Optimization Analysis screen for that specific line and date.

ASSIA, Inc. Confidential and Proprietary Page 95

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

3.2.4 Completed Requests

This screen shows detailed Profile Optimization information on a per-line basis for completed
requests.

Detailed Description:
The results displayed are for individual lines that have completed the Profile Optimization process.

Page 96 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Export CSV This creates a .csv (comma separated value) file of the data presented in the table
and saves it to the local computer. This file contains a tabular listing of the data that can be
examined using an application such as Microsoft Excel.
Line ID: Click to display the Profile Optimization Analysis screen for that specific line and date.

3.3 Reconciliation File

This screen allows the user to download reports containing data stored in DSL Expresse. The
main purpose of these reports is for reconciling data stored in DSL Expresse with data stored in
other systems deployed by the service provider.

Detailed Description:
These reports can be filtered to show specific data. Each type of report that is available via this
screen is described below:

DSLAM INFO - Contains the following fields:

o DSLAM Name
o DSLAM IP Address
o DSLAM Type
o Interface Type
o NMS Name
SNMP1 INFO Contains the following fields:
o DSLAM Name
o SNMP Port
o SNMP Read Community
o SNMP Read/Write Community
SNMP3 INFO Contains the following fields:
o IP Port
o Context Name
o Context Engine ID
o Engine ID
o Privacy Protocol
o Privacy Pass-phrase
o Auth. Protocol
o Security Name
o Auth. Pass-phrase
LINE INFO - Contains the following fields:

ASSIA, Inc. Confidential and Proprietary Page 97

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

o Line ID
o Port
o DSLAM Name
o Service Product
o PE Enabled
o PO Enabled
NEIGHBORHOOD INFO - Contains the following fields:
o Line ID
o All other fields configured according to the neighborhood definition
PROFILE INFO - Contains the following fields:
o Profile Name
o Min DS Rate(kbps)
o Min US Rate (kbps)
o Max DS Rate (kbps)
o Max US Rate (kbps)
o Min Margin DS (dB)
o Min Margin US (dB)
o Target Margin DS (dB)
o Target Margin US (dB)
o Max Margin DS (dB)
o Max Margin US (dB)
o Max Interleave Delay DS (ms)
o Max Interleave Delay US (ms)
o Min INP DS
o Min INP US
o DSL Standards Enabled
o Supported DSLAM Types
PE DATA Contains the following fields:
o Line ID
o DS MABR (kbps)
o US MABR (kbps)
o DS Rate (kbps)
o US Rate (kbps)
o Profile
o Data Collection Date
o DS Stability Definition #1 (definition configurable)
o DS Stability Definition #2 (definition configurable)
o US Stability Definition #1 (definition configurable)
o US Stability Definition #2 (definition configurable)
o Retrains
o Estimation Date
LINE OPERATION DATA Contains the following fields:
o Line ID
o DS MABR (kbps)

Page 98 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

o US MABR (kbps)
o DS Rate (kbps)
o US Rate (kbps)
o Profile
o Data Collection Date

3.4 Network Statistics

This screen allows the user to plot various statistics for the lines in the network.

ASSIA, Inc. Confidential and Proprietary Page 99

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Detailed Description:
Report For: Contains the list of reports that are available for the network statistics.
o DS Estimated MABR (kbps)
o DS Reported MABR (kbps)
o DS Synch Rate (kbps)
o US Estimated MABR (kbps)
o US Synch Rate (kbps)
o Stability

Once Report For is chosen, a filter for the selected statistics is enabled to specify the ranges of
values for the derivation of statistics. For the rate-related reports (DS/US
Estimated/Reported/Synch MABR/Rate), pre-configured rate ranges are shown in the drop-down
menu. For stability, VERY_STABLE, STABLE, UNSTABLE, VERY_UNSTABLE, UNKNOWN is
shown in the drop-down menu. In each case, the drop-down menu includes the ALL option.
Region: Contains the list of regions that can be used as a filter. The region information is
available only when properly configured based on address information.
DSLAM Type: Can be used to select a specific DSLAM type supported by DSL Expresse. If the
user wants to retrieve the report for all DSLAM types, the user can choose ALL as DSLAM type.
Line Card Type: Can be used to select a specific line card type of the specified DSLAM type.
This filter is enabled only after the user selects DSLAM type. If the user chooses ALL as a
DSLAM type, line card type filter is not enabled.
Service Product: Can be used to select a specific service product supported by DSL Expresse.
Date: Can be used to select a specific date or range of dates for which to display the network
statistics data. If one single date is chosen, a pie chart shows the statistics. If a range of dates is
chosen by specifying From and To, a stacked area chart or time series chart is displayed. The
stacked area chart is shown when the user chooses a report with all values (no filtering). The time
series chart is shown when the user chooses a report for a specific value (i.e. narrow to a
specified stability level, or narrow to a specified rate range).
Switch Report Type: The user can choose report types. A table shows the raw numbers of each
report in a table format while a chart shows percentage numbers in a chart format.

3.5 Dynamic Reports

This screen allows the user to manage the export of specified data from DSL Expresse. Two
types of reports are supported:
DATA_EXPORT: This report is defined by one or multiple SQL statements to retrieve data from
the DSL Expresse system. The rules to create a DATA_EXPORT report definition are:
1. If more than one SQL statements are required in a DATA_EXPORT report, each SQL
statement must be on a separate line of the file, and must end with a semicolon ;.
2. Each SQL statement must start with the SELECT word.
3. The parameters can be defined in an SQL statement using the notation
$PARAM{PARAM_NAME, TYPE, DEFAULT_VALUE, DESCRIPTION, FORMAT}.
PARAM_NAME is the name for the parameter, and it is mandatory. The field positions in
the parameter declaration are fixed and they are separated by comma.
a. Type can be any of STRING, BOOLEAN, INTEGER, FLOAT and DATE.

Page 100 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

b. The default type is STRING and the default date format is yyyy/mm/dd. Leading
zeros have significance, i.e., when mm or dd are used as date types, values
such as 3 should be represented as 03.
c. Format is applicable only for Date types. For dates, if the user queries a date, the
date format can be used to explain the user date value. The date format used
should be of valid Simple Date Formats used by Java.
Example 1: SELECT * FROM PORT_INFO where creation_date =
'$PARAM(dt,DATE,2012/03/02)'. Parameter name dt is of type Date with a
default value of 2012/03/02.
Example 2: SELECT * FROM PORT_INFO where creation_date =
'$PARAM(dt,DATE,03/02/12,,mm/dd/yy)'. In this example, the description is
empty.
d. When a parameter is repeated, it has to be defined consistently. It should not be
defined with different type, default values or formats.
Example: Select * from PORT_INFO where Service_product =
'$PARAM(SERVICE_PRODUCT, STRING, ASSIA_MAX)' and
PORT = '$PARAM(PORT, STRING, ASSIA_MAX)' and
LINE_ID ='$PARAM(LINE_ID, INTEGER, 0000010716)' and
CIRCUIT_ID = '$PARAM(LINE_ID, INTEGER, 0000010716)'
BIRT: The Eclipse BIRT (Business Intelligence and Reporting Tools) provides a framework for
defining and generating custom reports. A BIRT report definition must first be developed using
the Eclipse BIRT designer tool. This designer tool is a free product but not included in the DSL
Expresse release. The designer tool can be downloaded from:
http://www.eclipse.org/downloads/download.php?file=/birt/downloads/drops/R-R1-3_7_1-
201109131734/birt-rcp-report-designer-3_7_1.zip
Once a report definition is created, it must then be uploaded to DSL Expresse.
For more information on using BIRT, please refer to the BIRT web site:
http://www.eclipse.org/birt/phoenix/

3.5.1 Manage Reports

A user with the appropriate privileges can manage and schedule the generation of dynamic
reports.

ASSIA, Inc. Confidential and Proprietary Page 101

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Detailed Description:
Report Name: The name used to search for reports. Use % as a wildcard to search for similarly
named reports.
Create New Report: Displays the New Dynamic Report screen.
Manage Schedule: Displays the Manage Report Schedules screen
Manage Definition: Displays the Manage Report Definition screen.
Table Data:
The rows of the table correspond to reports defined in DSL Expresse.
Dynamic Report: The elements of this column are hyperlinks that take the user to the Update
Dynamic Report screen to update or reschedule the corresponding report.
Description: Contains a description of the dynamic report.
Report Definition: This hyperlink takes the user to the Update Report Definition screen to update
the definition of the corresponding report.
Category: This shows the report category DATA_EXPORT or BIRT.
Last Update: This shows the time-stamp for the most recent report update.
Updated By: This shows the last user that updated the report.
Schedule: This shows the run schedule of the report.
Run Now: This hyperlink executes the corresponding report immediately.
Separated Output(s): This checkbox when selected provides an option to select to export to
individual files (one per query). When unselected provides an option to export to a single file. This
option is available only when the report category is DATA_EXPORT.
Run History: This hyperlink takes the user to the Run History screen to see the historical results
for the corresponding report.
Disable/Enable: This hyperlink allows the user to disable or enable a report.
Delete: This hyperlink allows the user to delete a report.

Page 102 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

3.5.1.1 New Dynamic Report

This screen allows the user to create a new dynamic report.

Detailed Description:
Name: The name for the new report. This is a required field.
Description: The description for the new report. This is a required field.
Definition: The definition can be created from the Manage Report Definition screen. The
contents of the definition show in a text box. This is a required field.
Parameters: The parameter values for the report. This field is displayed only if parameters are
defined for the selected report. This is a required field. The parameter description is visible as a
context help icon, which is present only when a description is associated with a parameter. The
default parameter value appears in the textbox, which can be changed by the user. The
parameter value entered in the textbox is validated to confirm that its type matches the parameter
type during submission.
Run Schedule: The schedule for the new report to run. The user can specify an existing
schedule from the pull-down list. If it is not a built-in schedule, the user can update the schedule
by selecting the Update check box.

ASSIA, Inc. Confidential and Proprietary Page 103

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

The user can add a new schedule using Add New Schedule.

The new schedule can be created using the options Every day, Every Week, Every Month, or
Custom. When using Custom, the user must specify the cron definition and also provide a
schedule description.
Run Schedule is a required field.
Subscribers: A list of GUI users can be added to receive emails with the report results when the
report is executed successfully. Use  to search for users.
Run Now: Select the check box to execute the report immediately upon creation.
Separate Outputs: Select the check box to separate SQL query results into separate output files.
By default, results from queries in a DATA EXPORT report will be in one single output file.
Submit: Submit to create the new report.
Cancel: Cancel the creation of the new report.

3.5.1.2 Update Dynamic Report

This screen allows the user to edit existing report definitions.

Page 104 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Detailed Description:
This screen is same as the New Dynamic Report screen, except the report name cannot be
edited. Also, an option is available to clean up previous report results.
Delete previous generated reports: Check to clean up all previous report results.

3.5.1.3 Manage Report Schedules

This screen displays the reports that are assigned to a particular schedule. It allows the user to
reassign a report to a different schedule.

ASSIA, Inc. Confidential and Proprietary Page 105

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Detailed Description:
Schedules: The pull-down list displays all schedules that have reports assigned.
Table Data
The results displayed are reports assigned to the listed schedule.
Dynamic Report: The elements of this column are hyperlinks that take the user to the
Update Dynamic Report screen to update or reschedule the corresponding report.
Description: Contains a description of the dynamic report.
Report Definition: This hyperlink takes the user to the Update Report Definition screen to
update the definition of the corresponding report.
Category: This shows the report category DATA_EXPORT or BIRT.
Last Update: This shows the time-stamp for the most recent report update.
Updated By: This shows the last user that updated the report.
Schedule: This shows the run schedule of the report.
Run Now: This hyperlink executes the corresponding report immediately.
Run History: This hyperlink takes the user to the Run History screen to see the historical
results for the corresponding report.
Disable/Enable: This hyperlink allows the user to disable or enable a report.
Delete: This hyperlink allows the user to delete a report.
Update Schedule for above reports: Select the check box to reassign the selected reports to a
different schedule. Use Add New Schedule and Update to add a new schedule or to edit an
existing one respectively.
Manage Reports: Display the Manage Reports screen.
Submit: Submit to reschedule the reports.

Page 106 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

3.5.1.4 Manage Report Definition

Detailed Description:
Definition Name: The name used to search for reports. Use % as a wildcard to search for
similarly named reports.
Create New Dynamic Report Definition: Opens the Create Report Definition screen.
Manage Reports: Opens the Manage Reports screen.
Table Data
The results displayed are report definitions in DSL Expresse.
Report Definition: This hyperlink takes the user to the Update Report Definition screen to
update the definition of the corresponding report.
Category: This shows the report category DATA_EXPORT or BIRT.
Last Update: This shows the time-stamp for the most recent report update.
Updated By: This shows the last user that updated the report.
Delete: This hyperlink allows the user to delete a report definition.
Create Report from this definition: This hyperlink displays the New Dynamic Report screen
to create a new report based on the selected definition.

ASSIA, Inc. Confidential and Proprietary Page 107

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

3.5.1.5 Create Report Definition

Detailed Description:
Definition Name: The name for the new report definition.
Select a SQL/TXT/BIRT Definition file: Browse the client computer to locate aa definition file. It
can be either an SQL file or a TXT file for Data Export Report or a BIRT file (the
latterlaterlatterlater has the .rptdesign extension) for BIRT Report. If the definition has non-ASCII
characters The definition file should be in UTF-8 encodingIencodingpreferably. If a definition file is
not in UTF-8 encoding, the system attemptswillattemptswill to convert it to UTF-8 before it is
stored in the database. If the conversion fails, a message isbeisbe shown and the definition file
isbeisbe rejected.
Report Definition Type: Choose between Data Export Report and BIRT Report.
Submit: Create the new report definition.
Cancel: Cancel the creation of the new report definition.

Page 108 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

3.5.1.6 Update Report Definition

Detailed Description:
Definition Name: The name of the report definition (cannot be edited).
Select a SQL/TXT Definition file: Browse the local computer to locate the new definition file.
If the type of definition is Data Export Report, the user can select the Edit Definition check
box to enable the text box and update the SQL statements.
If the type of definition is BIRT report, a hyperlink is displayed to allow the user to download
the current report definition.
Parameters: Displays the parameter names in the current definition.
Report Definition Type: Displays Data Export Report or BIRT Report (cannot be edited).
Submit: Update the report definition.
Cancel: Cancel the update of the report definition.

ASSIA, Inc. Confidential and Proprietary Page 109

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

3.5.2 Generated Reports

This screen allows the user to view the latest results for each dynamic report in DSL Expresse.

Detailed Description:
Report Name: The name used to search for reports. Use % as a wildcard to search for similarly
named reports.
Table Data:
Dynamic Report: The reports name.
Description: The description for the report.
Category: This shows the report category DATA_EXPORT or BIRT.Last Run Time: The most
recent time the report was executed.
Run Status: The status message from the last execution of the report.
Download: Click to download the result (if generated). It is a zipped CSV for DATA_EXPORT, or
anan HTML and a PDF for a BIRT report. The HTML result isbeisbe displayed in a pop-up
window.
Run Now: Click to execute the report now.
Run History: Click to display the Run History screen and see the historical results for a report.
Subscribe/Unsubscribe: Click to subscribe or unsubscribe for email notification when the report
is executed successfully.

3.5.2.1 Run History

This screen displays the historical results for a report in DSL Expresse.

Detailed Description:

Page 110 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Back: Back to the previous page.

Table Data:
Dynamic Report: The report name.
Run Time: The time of report execution.
Run Status: The status message from the report execution .
Download: Click one of the links to download or view the report result. For DATA_EXPORT
reports, the link is CSV, which is a zip archive of query output (one consolidated output file, or
multiple output files for individual queries). For BIRT reports, the links areis areisHTML andor
andorPDF. The HTML result isbeisbe displayed in a pop-up window.

ASSIA, Inc. Confidential and Proprietary Page 111

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

4 Administration
4.1 Identity Management
This section describes the actions a system administrator can take to manage user accounts in
the GUI. This functionality is accessed via the Administration tab in the navigation bar that is
visible only for administrator users.
All actions associated with User Account management are only available to users with
Administrative privileges.

4.1.1 User/Role Overview

This screen allows a user with administrative privileges to quickly verify all the user accounts that
are configured to access the DSL Expresse GUI.

Detailed Description:
Each user account is associated with one or more Roles that describe and assign privileges in
the system.
This screen shows for each account the User Name, First Name, Last Name, E-mail, Phone
Number and Roles assigned. Each listed User Name and Role is a hyperlink that takes the user
to the Manage Users or Manage Roles screen for that respective account or role.
Note: Administrative privileges are required to access this screen.

4.1.2 Manage Users

This screen allows a user with administrative privileges to create new user accounts, modify
existing accounts, reset passwords and delete user accounts.

Page 112 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Detailed Description:
Selecting Manage Users from the Administration navigation menu brings the user to this screen.
Note: Administrative privileges are required to access this screen.
Create User: Places the user at the Create User screen where a new user account can be
created.
User Name: The User Name for the given account.
First name: The users given name.
Last name: The users last name.
E-mail: The users email address.
Phone number: The users phone number.
Update User: Places the user at the Update User screen where the account information can
be updated.
Delete User: Allows the selected account to be deleted.
Reset password: Places the user at the Reset Password screen where the account
password can be reset.

4.1.2.1 Create User

This screen allows a user with administrative privileges to enter information for defining a new
DSL Expresse GUI account user.

ASSIA, Inc. Confidential and Proprietary Page 113

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Detailed Description:
Selecting Create User from the Manage Users screen brings the user to this screen.
Notes:
o Administrative privileges are required to access this screen.
o In certain versions of Firefox, some fields may be populated with invalid data when the
Remember Password feature is enabled.
All fields are required.
User Name: Enter a User Name for the given account.
First name: Enter the users first name.
Last name: Enter the users last name.
E-mail: Enter the users email address.
Phone number: Enter the users phone number.
Password setting: Check this box to require the user to change the password at the time of
first login.
New password: Enter the users password.
Confirm password: Re-enter the users password. The New Password and Confirm
Password must match.
Note: Password rules are configurable per customer.
Role: Check the appropriate Roles based on the permissions to be given to the user. A
Description and Role Type are provided for each role.
Save: The new account is created and ready for use. An email is sent to the email address
entered above letting the user know that an account has been created. This email also includes
the URL to the DSL Expresse GUI.
Cancel: The account creation action is terminated and no account is created. No email is sent
out.

Page 114 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

4.1.2.2 Update User

This screen allows a user with administrative privileges to modify the information in an already
existing DSL Expresse GUI user account.

Detailed Description:
Selecting Update User for a particular user listed in the Manage Users screen brings the user to
this screen.
Notes:
o Administrative privileges are required to access this screen.
o In certain versions of Firefox, some fields may be populated with invalid data when the
Remember Password feature is enabled.

User Name: The User Name for the given account. This field cannot be changed.
First Name: The users first name.
Last name: The users last name.
E-mail: The users email address.
Phone number: The users phone number.
Password setting: Check this box to require the user to change the password at the next
login.
Role: Check the appropriate Roles based on the permissions to be given to the user. A
Description and Role Type are provided for each role.
Save: By selecting Save the account information is updated and saved.
Cancel: By selecting Cancel the account update action is terminated and no updated information
is saved.
Specific Permissions: By selecting Specific Permissions the user is placed at the Manage
Resource Permissions screen which allows the enabling or disabling of individual permissions for
the account.

ASSIA, Inc. Confidential and Proprietary Page 115

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

4.1.2.3 Reset Account Password

This screen allows a user with administrative privileges to reset the password for the respective
DSL Expresse GUI user account.

Detailed Description:
Selecting Reset Password for a particular user listed in the Manage Users screen brings the user
to this screen.
Note: Administrative privileges are required to access this screen.
User Name: The User Name for the given account. This field is populated based on the
selection of the account from the previous screen. This field cannot be changed.
New password: Enter the new password here.
Confirm new password: Re-enter the new password here. The New Password and Confirm
Password must match.
Note: Password rules are configurable per customer. Typical password rules are as follows:
o Password must have a minimum number of characters.
o Password must include characters from different pre-defined characters sets (example
sets: number, lower-case, upper-case and special characters).
o Password must be significantly different from previously used passwords.
o Password must not contain the username.

Save: The new password is saved. An email is sent to the email address in the account profile
letting the user know that their password has been reset. This email includes the new password
and the URL of the DSL Expresse GUI.
Cancel: The password reset action is terminated and the password is not reset. No email is sent
out.

Page 116 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

4.1.3 Manage Roles

This screen allows a user with administrative privileges to create a new role, update an already
existing role or delete an existing role.

Detailed Description:
Once a role has been defined, that role can be assigned to a user account either during user
account creation or user account updating
Note: Administrative privileges are required to access this screen.
Create Role: Places the user at the Create Role screen where a new Role can be created.
Role: The name of the Role.
Description: A short description of the Role.
Role Type: The type of the Role Normal or Built-in.
View/Update Role: For Normal roles, the user can click the button to go to the Update Role
screen where the Role information can be updated. For Built-in roles, the user can click the
button to go to the Update Role screen where the Role information can be viewed but not
updated.
Delete Role: Allows the selected Role to be deleted.

ASSIA, Inc. Confidential and Proprietary Page 117

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

4.1.3.1 Create Roles

This screen allows a user with administrative privileges to create a new Role with specific
permissions.

Detailed Description:
Note: Administrative privileges are required to access this screen.
Role: The name of the new Role.
Description: A short description of the Role.
Save: The new Role is created and saved.
Cancel: The action to create the new Role is terminated and no new Role is created.

4.1.3.2 Update Roles

This screen allows a user with administrative privileges to update an already existing Role.

Detailed Description:
Note: Administrative privileges are required to access this screen.
Role: The name of the Role. This field cannot be changed.
Description: A short description identifying the nature of the Role.
Save: The Role information is updated and saved.
Cancel: The Role update action is terminated and no updated information is saved.
Specific Permissions: By selecting Specific Permissions the user is placed at the Manage
Resource Permissions screen that allows enabling or disabling specific individual permissions for
the Role.

Page 118 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

4.1.3.3 Manage Resource Permissions

This screen allows a user with administrative privileges to change specific individual permissions
for the respective Role or User Account.

ASSIA, Inc. Confidential and Proprietary Page 119

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Detailed Description:
Note: Administrative privileges are required to access this screen.
Module Name: The name of the module which generically identifies the type. Usually similar
to the Resource Name.
Resource Type: Type of resource for this permission.
Resource Name: The real name of the resource type. This name identifies the actual
type/action.
Description: A short description of the resource indicating its function.
Specific Permission: Checking the box enables the specific permission for this account or
role.
Permission from Role: Shows if the permission is already assigned to the account and
through which Role. (This column is displayed only when changing directly the permission of
a User Account).
Save: The specific permission information is updated and saved.
Cancel: The specific permission action is terminated and no updated information is saved.

Page 120 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

4.2 System Health

This screen allows a user with administrative privileges to monitor each specific module of the
system.

This screen displays a list of the modules that are currently running on the DSL Expresse
server(s), along with the servers Host Address, the current module status and the time the
module was started.
When active, the Module Name is a hyperlink that displays the Module Status screen.
This specific example screen shows all modules running except the Profile Optimizer. When
modules are not running, they are not listed as a hyperlink.

4.2.1 Module Status

This screen gives a user with administrative privileges specific monitoring information on the
respective module selected in the previous System Monitoring screen.

ASSIA, Inc. Confidential and Proprietary Page 121

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

This screen provides detailed information such as system up-time, start time of the module,
number of requests generated from the respective module, and specific run-time information.
Each modules status page contains information specific to that module.

Page 122 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

4.3 Provisioning
These screens enable the user to make DSLAM and line provisioning changes, including
additions, deletions and updates. They are not intended for use in a production environment,
where provisioning changes must only be handled through the provisioning NAPI, or through the
flat-file provisioning application of DSL Expresse. They are only intended for use in a staging
environment, where they can be useful for easy provisioning of lines in a lab setting. These
screens are by default disabled for all accounts.

4.3.1 DSLAM Provisioning

This screen allows the user to add/update/delete a DSLAM. To update or delete:
1. Type or select a DSLAM name into the input box.
2. Click one of the action buttons: update, delete.
To add, click Add.
Note that iIf a DSLAM name has been entered into the input box, and the add action is selected,
then the information of the selected DSLAM is copied over for the new DSLAM to be added. The
Validate Connectivity button can be used to check the connectivity.

ASSIA, Inc. Confidential and Proprietary Page 123

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

4.3.2 Line Provisioning

This screen allows the user to add/update/delete a line. To update or delete:
1. Type or select a line ID into the input box.
2. Click one of the action buttons: update, delete.
To add, click Add button.
Note that if a line ID has been entered into the input box, and the add action is selected,
information about the selected line is copied over for the line to be added. The
Validate Connectivity button can be used to check the connectivity.
Note that the port field for bonded lines contains ports in the form of
port1|port2
For example. assume that line 9999000001 is a bonded line with ports:
1-1-1-1
1-1-1-2
Then the port field appears as follows:
1-1-1-1|1-1-1-2

Page 124 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

ASSIA, Inc. Confidential and Proprietary Page 125

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

5 Data Report Fields

The following table provides a summary of fields displayed in the DSL Expresse GUI. For each
field the following information is displayed: Field Name, Description and Usage, and Screens
which contain the field.

Field Name Description and Usage Screens that display the

Parameter
Line ID Line ID is operator dependent and can Analysis
represent anything from a unique identifying Line Summary
number to a real telephone number. It is the Performance Analysis
index for information about a particular DSL Real-Time Performance
service and is ultimately derived from the Analysis
operator's inventory and service Diagnostics Analysis
management systems. Real-Time Diagnostics
Analysis
SELT Diagnostics Analysis
Historical Data Trends
Lines in the DSLAM
Lines in the Neighborhood
Profile Optimization
Compare Lines
Service Recommendation
Diagnostics/Detail Report
Profile Optimization/Detail
Report
Profile Optimization/Active
Requests
Profile
Optimization/Completed
Requests

Page 126 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

DSLAM The Operator ID or name of a specific Analysis

DSLAM. Line Summary
It is derived from the operator's inventory Performance Analysis
databases. Real-Time Performance
Analysis
Diagnostics Analysis
Real-Time Diagnostics
Analysis
SELT Diagnostics Analysis
Historical Data Trends
Lines in the DSLAM
Lines in the Neighborhood
Profile Optimization
Compare Lines
Service Recommendation
Diagnostics/Detail Report
Profile Optimization/Detail
Report
Profile Optimization/Active
Requests
Profile
Optimization/Completed
Requests
Port The ID or number of the specific port on the Line Summary
DSLAM that supports a particular service. Performance Analysis
This is derived from the operator's inventory Real-Time Performance
databases. The specific number scheme is Analysis
dependent on the particular DSLAM Diagnostics Analysis
supported (Rack-Shelf-Slot-Port or Shelf- Real-Time Diagnostics
Slot-Port). Analysis
SELT Diagnostics Analysis
Historical Data Trends
Lines in the DSLAM
Lines in the Neighborhood
Profile Optimization
Compare Lines
Service Recommendation
Diagnostics/Detail Report
Profile Optimization/Detail
Report
Profile Optimization/Active
Requests
Profile
Optimization/Completed
Requests

ASSIA, Inc. Confidential and Proprietary Page 127

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Service Service Product is a name for describing the Line Summary

Product type of service that the DSL consumer has Performance Analysis
purchased. Most service providers offer Real-Time Performance
multiple service products that are typically Analysis
differentiated based on the data rate speeds Diagnostics Analysis
that are guaranteed, or based on whether Real-Time Diagnostics
applications beyond high-speed internet Analysis
(e.g. IPTV or Voice-over-IP) are included. SELT Diagnostics Analysis
DSL Expresse requires that a Service Historical Data Trends
Product be assigned to each line. This
Lines in the DSLAM
information is used for both analysis and
Lines in the Neighborhood
optimization purposes.
Profile Optimization
Compare Lines
Service Recommendation
Line Status The display of the Line Status information Line Summary
depends on the type of screen. Performance Analysis
For screens displaying previously collected Real-Time Performance
data, Line Status displays the following: Analysis
When the line is disabled (which means that Diagnostics Analysis
the line is deleted from DSL Expresse), a Real-Time Diagnostics
red bullet is shown. When the line is Analysis
activated (which means that the line is SELT Diagnostics Analysis
managed by DSL Expresse), a green bullet Historical Data Trends
is shown. Lines in the DSLAM
Lines in the Neighborhood
For screens displaying real-time data, Line
Profile Optimization
Status displays the following: When the line
is disabled, a red bullet is shown together Compare Lines
with DISABLED. When the line is not Service Recommendation
provisioned in the DSLAM, a grey bullet is
shown together with DEACTIVATED.
When the line is out-of-service, an orange
bullet is shown together with OUT-OF-
SERVICE. When the line is in-service, a
green bullet is shown together with IN-
SERVICE.

Profile in Use A profile is a group of predefined Performance Analysis

configuration parameters that are applied to Real-Time Performance
a DSL. Typically, a large set of profiles can Analysis
be created on a DSLAM and each of them Profile Optimization
is identified by an ID or name. A profile Service Recommendation
created on a DSLAM can then be applied to
a specified port.

Min. Rate The configured Minimum Allowable bit rate Performance Analysis
(kbps)
in the specified direction. Part of the Real-Time Performance
parameters in a Profile. Analysis

Max. Rate The configured Maximum Allowable bit rate Performance Analysis
(kbps)
in the specified direction. Part of the Real-Time Performance
parameters in a Profile. Analysis

Page 128 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Plan Rate The configured Planned bit rate in the Line Performance Analysis
(kbps)
specified direction. This parameter is not Real-Time Performance
supported by all DSLAMs. Part of the Analysis
parameters in a Profile.

Min. Margin The configured Minimum Allowable Margin Line Performance Analysis
(dB)
in the specified direction. Part of the Real-Time Performance
parameters in a Profile. Analysis

Target Margin The configured Target Margin in the Line Performance Analysis
(dB)
specified direction. Part of the parameters in Real-Time Performance
a Profile. Analysis

Max. Margin The configured Maximum Margin in the Line Performance Analysis
(dB)
specified direction. Part of the parameters in Real-Time Performance
a Profile. Analysis

Max. Power The configured Maximum Power in the Line Performance Analysis
(dBm)
specified direction. Part of the parameters in Real-Time Performance
a Profile. Analysis

Max. PSD The configured Maximum Power Spectral Line Performance Analysis
(dBm/Hz)
Density in the specified direction. Part of the Real-Time Performance
parameters in a Profile. Analysis

Delay The configured Maximum Interleaving Delay Line Performance Analysis

(ms)
in the specified direction. Part of the Real-Time Performance
parameters in a Profile. Analysis

INP The configured Minimum Impulse Noise Line Performance Analysis

(symbols)
Protection in the specified direction, Real-Time Performance
expressed in units of DMT symbols. Part of Analysis
the parameters in a Profile.

Supported The configured DSL Standards allowed for Line Performance Analysis
Standards the line, represented by a standardized Real-Time Performance
numeric format. Clicking on the Analysis
information button next to the numeric
values produces a more detailed
explanation. Part of the parameters in a
Profile.

Interleaving Indicates whether interleaving is enabled in Line Performance Analysis

the specified direction. Part of the Real-Time Performance
parameters in a Profile. Analysis
Interleaving provides additional protection
against certain noises but increases
transmission delay.

Trellis Coding Indicates if Trellis Coding is enabled in the Line Performance Analysis
specified direction. Part of the parameters in Real-Time Performance
a Profile. Analysis

ASSIA, Inc. Confidential and Proprietary Page 129

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

State The DSL line status at the time of data Line Performance Analysis
collection. Real-Time Performance
Analysis
Current Rate The DSL sync rate in the specified direction Line Performance Analysis
(kbps)
at the time of data collection (as reported by Real-Time Performance
the DSL equipment). Analysis
Historical Data Trends
Profile Optimization
Analysis
Service Recommendation
Current ETR The Expected Throughput Rate at the time Line Performance Analysis
(kbps)
of collection for the given configuration of Real-Time Performance
g.inp for protection against SHINE and Analysis
REIN impulse events.

MABR The Maximum Attainable Bit Rate of the line Line Performance Analysis
(kbps)
in the specified direction at the time of data Real-Time Performance
collection (as reported by the DSL Analysis
equipment or as estimated by DSL Historical Data Trends
Expresse). Lines in the DSLAM
Lines in the Neighborhood
Service Recommendation
Daily EFTR Error-Freefree ThroughputFreefree Line Summary
Throughput Ratethroughput over the past
24 hours

Margin The Signal-to-Noise-Ratio Margin in the Line Performance Analysis

(dB)
specified direction at the time of data Real-Time Performance
collection. Analysis
Historical Data Trends
Attenuation The Line Attenuation in the specified Line Performance Analysis
(dB)
direction at the time of data collection. Real-Time Performance
Analysis
Historical Data Trends
Power The Transmitted Power in the specified Line Performance Analysis
(dBm)
direction at the time of data collection. Real-Time Performance
Analysis
Historical Data Trends
Tx Mode The mode of operation of the line. Defines if Line Performance Analysis
PHY-R retransmission, g.inp retransmission Real-Time Performance
or vectoring is used by the line. Possible Analysis
modes are:
No Retransmission
PhyR
G.inp
Vectored
Vectored + PhyR
Vectored + G.inp

Page 130 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Running The operating DSL Standard on the line, Line Performance Analysis
Standard represented by a standardized numeric Real-Time Performance
format. Clicking on the information button Analysis
next to the numeric value produces a more Lines in the DSLAM
detailed explanation. Lines in the Neighborhood
Service Recommendation
Actual INP The actually implemented Impulse Noise Line Performance Analysis
(symbols)
Protection in the specified direction at the Real-Time Performance
time of data collection. It is expressed in Analysis
units of DMT symbols.

Actual REIN The actually implemented Impulse Noise Line Performance Analysis
INP Protection again REIN events in the Real-Time Performance
specified direction at the time of data Analysis
(symbols)
collection. It is expressed in units of DMT
symbols. It applies only for lines operating
with g.inp mode.

Actual Delay The actually implemented Interleaving Line Performance Analysis

(ms)
Delay in the specified direction at the time of Real-Time Performance
data collection. Analysis

Leftr Thresh. Threshold for declaring a leftr defect (low Line Performance Analysis
error-free throughput rate). Real-Time Performance
Analysis
INP REIN The configured Minimum Impulse Noise Line Performance Analysis
(symbols)
Protection against REIN impulse events in Real-Time Performance
the specified direction, expressed in units of Analysis
DMT symbols. Part of the parameters in a
profile only when g.inp is enabled.

SHINE Ratio The configured retransmission overhead Line Performance Analysis

reserved for SHINE impulse events. Part of Real-Time Performance
the parameters in a profile only when g.inp Analysis
is enabled.

G.inp Mode The G.inp mode of the line which can be Line Performance Analysis
either PREFERRED FORBIDDEN Real-Time Performance
FORCEDPREFERRED, FORBIDDEN, Analysis
FORCED or TESTTEST mode.

Is FEXT Indicates if FEXT cancellation (vectoring) is Line Performance Analysis

Cancellation enabled in the profile. The possible values Real-Time Performance
Enabled are YES and NO. Analysis

ASSIA, Inc. Confidential and Proprietary Page 131

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Bit Distribution The per-tone bit distribution in both the Line Performance Analysis
upstream and downstream directions. Real-Time Performance
The bit distribution shows how different Analysis
frequencies are used by the DSL to transmit Historical Data Trends
data. A particular frequency (tone or sub-
carrier) in a DSL signal can be assigned
from 0 to 15 bits. A larger number of bits
means that the corresponding tone is used
to transmit a larger amount of data. Tones
with fewer bits (compared to other tones)
may be receiving noise that interferes with
the signal on that tone, or may be
experiencing attenuation because of loop
faults.

HLOG HLOG is the magnitude of the channel Line Performance Analysis

(dB)
characteristic function in logarithmic scale. It Real-Time Performance
represents the channel attenuation on each Analysis
of the frequency tones (also known as sub- SELT Diagnostics Analysis
carriers). The measurement of this quantity
occurs during initialization of the line.

PSD PSD is the Power Spectral Density of the Line Performance Analysis
(dBm/Hz)
transmitted signal. It is reported for each of Real-Time Performance
the frequency tones (also known as sub- Analysis
carriers).

QLN QLN is the Quiet Line Noise of the line Line Performance Analysis
(dBm/Hz)
measured at the receiver. It is measured as Real-Time Performance
the RMS level of the received signal when Analysis
no transmission is taking place in either the
downstream or upstream directions. It is
reported for each of the frequency tones
(also known as sub-carriers). The
measurement of this quantity occurs during
initialization of the line.

SNR The SNR is the Signal to Noise Ratio Line Performance Analysis
(dB)
measured at the receiver. It is reported for Real-Time Performance
each of the frequency tones (also known as Analysis
sub-carriers).

Page 132 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Downstream The number of Line Code Violations (CV) Line Performance Analysis
Line Code per fifteen minute interval in the Real-Time Performance
Violations downstream direction. Analysis
Code violations are also known as incorrect
Cyclic Redundancy Checks (CRC).
A CV is recorded when there is at least one
byte containing an error within a specified
accumulation period. The accumulation
period depends on the DSL technology.
CVs are an important measure of stability
because a large CV count correlates highly
with low throughput and unstable
connectivity at higher layers.

Upstream Line The number of Line Code Violations (CV) Line Performance Analysis
Code per fifteen minute interval in the Real-Time Performance
Violations downstream direction. Analysis
Code violations are also known as incorrect
Cyclic Redundancy Checks (CRC).
A CV is recorded when there is at least one
byte containing an error within a specified
accumulation period. The accumulation
period depends on the DSL technology.
CVs are an important measure of stability
because a large CV count correlates highly
with low throughput and unstable
connectivity at higher layers.

Downstream The number of Errored Second per fifteen Line Performance Analysis
Error Seconds minute interval in the downstream direction. Real-Time Performance
Errored seconds are defined as the count of Analysis
1-second intervals with one or more CVs or
other defects. (See the corresponding DSL
standards for exact definition of defect.)

Upstream Error The number of Errored Second per fifteen Line Performance Analysis
Seconds minute interval in the upstream direction. Real-Time Performance
Errored seconds are defined as the count of Analysis
1-second intervals with one or more CVs or
other defects. (See the corresponding DSL
standards for exact definition of defect.)

ASSIA, Inc. Confidential and Proprietary Page 133

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Downstream The Forward Error Code (FEC) Correction Line Performance Analysis
FEC counts per fifteen minutes in the Real-Time Performance
Corrections downstream direction. Analysis
The FEC Correction count is the number of
corrected codewords within a specified
accumulation period. The accumulation
period depends on the DSL technology.
Large counts indicate that noise is affecting
transmission, but that the FEC code is
preventing the errors from being passed to
higher layers.

Upstream FEC The Forward Error Code (FEC) Correction Line Performance Analysis
Corrections counts per fifteen minutes in the upstream Real-Time Performance
direction. Analysis
The FEC Correction count is the number of
corrected codewords within a specified
accumulation period. The accumulation
period depends on the DSL technology.
Large counts indicate that noise is affecting
transmission, but that the FEC code is
preventing the errors from being passed to
higher layers.

Retrain Counts The number of line retrains per fifteen Line Performance Analysis
minutes. Real-Time Performance
Line retrains are also known as line Analysis
reinitializations or resynchornizations.

Downstream Number of seconds in which a leftr defect is Line Performance Analysis

leftr Seconds present in the downstream direction Real-Time Performance
Analysis
Upstream leftr Number of seconds in which a leftr defect is Line Performance Analysis
Seconds present in the upstream direction Real-Time Performance
Analysis
Downstream Average error-free downstream bits Line Performance Analysis
Average EFTR throughput over the past 24 hours Real-Time Performance
Analysis
Lines in the Neighborhood
Diagnostics Analysis
Real-Time Diagnostics
Analysis
Upstream Average error-free upstream bits throughput Line Performance Analysis
Average EFTR over the past 24 hours Real-Time Performance
Analysis
Lines in the Neighborhood
Diagnostics Analysis
Real-Time Diagnostics
Analysis

Page 134 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Loop Length This is the estimated equivalent electrical Diagnostics Analysis

(meter or feet
loop length. The estimate is based on the Real-Time Diagnostics
configured cable make-up. An often-used Analysis
customer
dependent)
cable make-up is a mixture of 50% 0.4mm Lines in the DSLAM
and 50% 0.6mm cable. Another example Lines in the Neighborhood
make-up is AWG26. Equivalent electrical Service Recommendation
loop length can differ significantly from
physical loop length, when the loop contains
faults, or when physical loop length records
are not accurate.
The loop length is not reported when a bad-
splice is detected.

Detected This is the estimated bridged tap length. Diagnostics Analysis

Bridged Tap The estimate is based on the same Real-Time Diagnostics
Length configured cable make-up as for Loop Analysis
(meter or feet
Length. The algorithm can detect up to two Lines in the DSLAM
customer
bridged taps. Lines in the Neighborhood
dependent) Bridged tap detection is available only when
per-tone data is available.

Upstream The Maximum Attainable Bit Rate in the Line Performance Analysis
MABR upstream direction. Diagnostics Analysis
(kbps) To determine an upgrade recommendation Real-Time Diagnostics
or optimal profile to use, MABR is an Analysis
important parameter and accurate MABR is Historical Data Trends
a basic requirement for sound operation. Lines in the DSLAM
However, the MABR reported by the Lines in the Neighborhood
DSLAM can be inaccurate for various Service Recommendation
reasons.

Upstream The DSL Expresse Estimated Maximum Diagnostics Analysis

MABR Attainable Bit Rate in the upstream Real-Time Diagnostics
direction. This estimate is only available for Analysis
(estimated)
VDSL lines. Lines in the DSLAM
(kbps)
To determine an upgrade recommendation Lines in the Neighborhood
or optimal profile to use, MABR is an Service Recommendation
important parameter and accurate MABR is
a basic requirement for sound operation.
However, the MABR reported by the
DSLAM can be inaccurate for various
reasons.
To solve this problem, DSL Expresse
estimates the MABR from multiple collected
data.

ASSIA, Inc. Confidential and Proprietary Page 135

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Upstream This condition means that the DSL line has Diagnostics Analysis
MABR in the an upstream MABR that is in the lowest 1% Real-Time Diagnostics
lowest 1% among all lines in the network with a similar Analysis
loop length. This flag of poor performance is Lines in the DSLAM
indicated with a red bullet in the GUI. A Lines in the Neighborhood
green bullet indicates that the situation does
not occur for the line.

Upstream The value denotes the upstream MABR Diagnostics Analysis

MABR percentile ranking of the DSL line when Real-Time Diagnostics
percentile compared to all lines in the network with a Analysis
similar loop length. Lines in the DSLAM
Lines in the Neighborhood
Downstream The Maximum Attainable Bit Rate in the Line Performance Analysis
MABR downstream direction. Diagnostics Analysis
(kbps) To determine an upgrade recommendation Real-Time Diagnostics
or optimal profile to use, MABR is an Analysis
important parameter and accurate MABR is Historical Data Trends
a basic requirement for sound operation. Lines in the DSLAM
However, the MABR reported by the Lines in the Neighborhood
DSLAM can be inaccurate for various Service Recommendation
reasons.

Downstream The DSL Expresse Estimated Maximum Diagnostics Analysis

MABR Attainable Bit Rate in the downstream Real-Time Diagnostics
direction. Analysis
(estimated)
To determine an upgrade recommendation Lines in the DSLAM
(kbps)
or optimal profile to use, MABR is an Lines in the Neighborhood
important parameter and accurate MABR is Service Recommendation
a basic requirement for sound operation.
However, the MABR reported by the
DSLAM can be inaccurate for various
reasons.
To solve this problem, DSL Expresse
estimates the MABR from multiple collected
data.

Downstream This condition means that the DSL line has Diagnostics Analysis
MABR in the a downstream MABR that is in the lowest Real-Time Diagnostics
lowest 1% 1% among all lines in the network with a Analysis
similar loop length. This flag of poor Lines in the DSLAM
performance is indicated with a red bullet in Lines in the Neighborhood
the GUI. A green bullet indicates that the Neighborhood Analysis
situation does not occur for the line.

Downstream The value denotes the downstream MABR Diagnostics Analysis

MABR percentile ranking of the DSL line when Real-Time Diagnostics
percentile compared to all lines in the network with a Analysis
similar loop length. Lines in the DSLAM
Lines in the Neighborhood
Neighborhood Analysis

Page 136 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

Upstream The DSL Expresse Estimated Maximum Diagnostics Analysis

MABR FEXT Attainable Bit Rate in the upstream direction Real-Time Diagnostics
Mitigated under the assumption of FEXT mitigation. Analysis
(estimated)
FEXT mitigation is achieved when vectoring Lines in the DSLAM
is enabled. This quantity can be calibrated Lines in the Neighborhood
(kbps) to include residual FEXT or other noise Neighborhood Analysis
resulting from imperfect cancellation.

Downstream The DSL Expresse Estimated Maximum Diagnostics Analysis

MABR FEXT Attainable Bit Rate in the downstream Real-Time Diagnostics
Mitigated direction under the assumption of FEXT Analysis
(estimated)
mitigation. FEXT mitigation is achieved Lines in the DSLAM
when vectoring is enabled. This quantity Lines in the Neighborhood
(kbps) can be calibrated to include residual FEXT Neighborhood Analysis
or other noise resulting from imperfect
cancellation.

Stability Line stability is a metric of the DSL service Line Summary

reliability that can be used to measure Diagnostics Analysis
quality of service. DSL Expresse evaluates Lines in the DSLAM
the line stability based on US and DS Lines in the Neighborhood
historical performance monitoring counters, Profile Optimization
including US and DS code violations and Service Recommendation
retrain counts. Four different stability levels
are defined as VERY STABLE, STABLE,
UNSTABLE and VERY UNSTABLE. The
criteria for categorizing a line into each level
are completely configurable and can be
customized per service product. If there is
not enough data for stability evaluation, the
line stability status is UNKNOWN.

Daily Periodic This condition means that the lines stability Diagnostics Analysis
Impairment is periodically degraded and that this Lines in the DSLAM
degradation starts at approximately the Lines in the Neighborhood
same time every day. This is typically a
strong indication that the source of the
degradation is related to a daily activity, and
is not always present. An example source
that exhibits such behavior is an improperly
connected alarm system. This information is
useful for further diagnosing the instability
source.

High Power When detected, a large rate increase may Diagnostics Analysis
NoiseNoise be achieved by installing a splitter at the Real-Time Diagnostics
NID, in order to avoid an in-house wiring Analysis
problem. This is very likely to improve Lines in the DSLAM
performance when neighboring lines are Lines in the Neighborhood
showing better data rate performance than
the line of interest.

ASSIA, Inc. Confidential and Proprietary Page 137

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

High Power When detected, a large rate increase may Diagnostics Analysis
Noise in High be achieved by installing a splitter at the Real-Time Diagnostics
FrequencyFreq NID, in order to avoid an in-house wiring Analysis
uency problem. This is very likely to improve Lines in the DSLAM
performance when neighboring lines are Lines in the Neighborhood
showing better data rate performance than
the line of interest.

AM or AM like Noise from AM transmission can affect a Diagnostics Analysis

Noise number of tones that have frequencies Real-Time Diagnostics
overlapping with the AM radio band. The Analysis
algorithm identifies the tones affected by Lines in the DSLAM
such noise. AM noise is often caused by Lines in the Neighborhood
poorly grounded cable or faulty in-house
wiring. If many lines in a neighborhood
exhibit AM noise, a bonding/grounding
review of the corresponding cable should be
scheduled.

HAM Noise Noise from HAM (amateur radio) signals Diagnostics Analysis
can affect a number of tones that have Real-Time Diagnostics
frequencies overlapping with the HAM radio Analysis
bands. HAM radio bands do not overlap Lines in the DSLAM
with the ADSL. The algorithm identifies the Lines in the Neighborhood
tones affected by such noise only for VDSL
lines and only when per-tone data is
available. HAM noise is often caused by
poorly grounded cable, or faulty in-house
wiring. If many lines in a neighborhood
exhibit HAM noise, a bonding/grounding
review of the corresponding cable should be
scheduled.

Noise The algorithm identifies that the line is Diagnostics Analysis

FluctuationFlu affected by noise whose power spectral Real-Time Diagnostics
ctuation density is changing significantly over time. Analysis
Lines in the DSLAM
Lines in the Neighborhood
Low Frequency Symmetric DSL systems (e.g. HDSL) can Diagnostics Analysis
Crosstalk generate crosstalk over the lower Real-Time Diagnostics
frequencies of the ADSL band. Tones 32 to Analysis
100 of the ADSL band are especially Lines in the DSLAM
susceptible to such crosstalk. This algorithm Lines in the Neighborhood
can identify lines for which this effect is
strong, occurring for example when HDSL
services are in the same cable/binder as the
ADSL service. If low frequency crosstalk is
confirmed to be caused by such
cable/binder sharing, it is recommended to
move the ADSL or the HDSL lines to a
separate cable/binder.

Page 138 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

ADSL FEXT This algorithm examines DMT tones Diagnostics Analysis

between 32 and 350 to detect far-end Real-Time Diagnostics
crosstalk (FEXT) from ADSL lines. This Analysis
algorithm is only available for VDSL lines Lines in the DSLAM
and only when the per-tone data is Lines in the Neighborhood
available. If strong ADSL crosstalk is
detected, the VDSL lines and ADSL lines
should be moved to different binders.
Alternatively, power management should be
applied on the ADSL lines.

VDSL FEXT This algorithm examines DMT tones Diagnostics Analysis

between 32 and 869 (i.e. the DS1 band in Real-Time Diagnostics
the 998 VDSL band plan) to detect far-end Analysis
crosstalk (FEXT) from VDSL lines. This Lines in the DSLAM
algorithm is only available for VDSL lines Lines in the Neighborhood
and when the per-tone data is available. If
strong VDSL FEXT is detected, either the
density of VDSL lines in the binder should
be reduced, or power management should
be applied, or the DSLAM should be
upgraded to support vectoring.

Bad- Corroded splices, or poor-contacts at Diagnostics Analysis

splicesplice splices and other connections can seriously Real-Time Diagnostics
affect DSL performance. This algorithm Analysis
detects such faults. Lines in the DSLAM
When a bad-splice detected on a line, the Lines in the Neighborhood
loop connections should be checked
starting from the NID and moving towards
the DSLAM. It is recommended to check if
neighboring lines have bad splices, so that
a dispatch can efficiently fix all of them.

Unbalanced The copper lines used for DSL can act like Diagnostics Analysis
WiringWiring antennas at times and pick noise and Real-Time Diagnostics
disturbance from various electrical fields Analysis
present. This undesired signal behavior can Lines in the DSLAM
cause stability and performance issues for Lines in the Neighborhood
DSL. It may also signify an issue such as a
third wire being present.

ASSIA, Inc. Confidential and Proprietary Page 139

PD-E2-0103-07-00
User Interface Guide DSL Expresse II

Impulse Impulse noise is defined as noise of short Diagnostics Analysis

NoiseNoise duration that is observed on a DSL line. It Lines in the DSLAM
can be isolated or it can occur repetitively Lines in the Neighborhood
over a period of time. The repetition rate
may be random or periodic (for example at
the 50/60Hz electric mains frequency.)
When impulse noise is affecting a DSL line,
the lines throughput and stability can be
severely degraded unless proper
adjustments in the configuration settings of
the line are made. Impulse noise can affect
transmission in the upstream, or
downstream, or both directions.

Bridged A bridged tap is an extension or branch of Diagnostics Analysis

TapTap the copper pair and it can affect DSL Real-Time Diagnostics
performance. The effect depends on the Analysis
extension length, the termination, the Lines in the DSLAM
distance from the DSL transceiver, the DSL Lines in the Neighborhood
technology and the DSL equipment. DSL
Expresse can detect up to two bridged taps
and estimate their lengths. Bridged tap
detection is available only when either per-
tone data or SELT data are available.

Series A fault that can be modeled as an SELT Diagnostics Analysis

FaultFault impedance connected in series with the
twisted pair. Examples of series faults
include bad or corroded
splices/connections, and wire cuts.

Shunt A fault that can be modeled as an SELT Diagnostics Analysis

FaultFault impedance connected in parallel with the
twisted pair. Examples of shunt faults
include short-circuits (between wires or
between wire and ground) and water-in-the-
cable.

Potential A missing or improperly installed microfilter Diagnostics Analysis

Missing can have a very adverse effect on DSL Real-Time Diagnostics
MicrofilterMicr performance during times when a telephone Analysis
ofilter device goes off-hook or on-hook. Such Lines in the DSLAM
devices include alarm systems and set-top- Lines in the Neighborhood
boxes that require a telephone connection.
This algorithm identifies performance
problems that appear to be caused by
telephone calls generated by humans, or
by alarm systems and set-top-boxes.

Page 140 ASSIA, Inc. Confidential and Proprietary

PD-E2-0103-07-00
DSL Expresse II User Interface Guide

CPE A CPE interoperability issue contributes to Diagnostics Analysis

Interoperability degraded performance and in some cases Real-Time Diagnostics
IssueIssueIssu to connection failures. Currently, the Analysis
eIssue algorithm identifies CPEs that are unable to Lines in the DSLAM
connect in vectored mode, even though the Lines in the Neighborhood
line-card supports vectoring and vectoring is
enabled on the line.

ASSIA, Inc. Confidential and Proprietary Page 141

PD-E2-0103-07-00