âWires-onlyâ VDSL2 Modem Test Plan - NICC

NICC ND 1436 V1.1.2 (2013-09) 

NICC Document 

“Wires-only” VDSL2 Modem Test Plan 

NICC Standards Limited 

Michael Faraday House, 

Six Hills Way, 

Stevenage 

SG1 2AY 

Tel.: +44(0) 20 7036 3636 

Registered in England and Wales under number 

6613589

2 


NOTICE OF COPYRIGHT AND LIABILITY 

© 2013 NICC Standards Limited 

The present document may be made available in more than one electronic version or in print. In any case of existing or 

perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). 

In case of dispute, the reference shall be that printing on NICC printers of the PDF version kept on a specific network 

drive within the NICC. 

Users of the present document should be aware that the document may be subject to revision or change of status. 

Information on the current status of this and other NICC documents is available at: 

Copyright 

http://www.niccstandards.org.uk/publications/ 

If you find errors in the present document, please send your comments to: 

mailto :help@niccstandards.org.uk 

All right, title and interest in this document are owned by NICC Standards Limited (“NICC”) and/or the contributors to the 

document (unless otherwise indicated that copyright is owned or shared with a third party). Such title and interest is 

protected by United Kingdom copyright laws and international treaty provisions. 

The contents of the document are believed to be accurate at the time of publishing, but no representation or warranty is 

given as to their accuracy, completeness or correctness. You may freely download, copy, store or distribute this 

document provided it is not modified in any way and it includes this copyright and liability statement. 

You may not modify the contents of this document. You may produce a derived copyright work based on this document 

provided that you clearly indicate that it was created by yourself and that it was derived from this document and 

provided further that you ensure that any risk of confusion with this document is avoided. 

Liability 

Whilst every care has been taken in the preparation and publication of this document, neither NICC, nor any working 

group, committee, member, director, officer, agent, consultant or adviser of or to, or any person acting on behalf of NICC, 

nor any member of any such working group or committee, nor the companies, entities or organisations they represent, 

nor any other person contributing to the contents of this document (together the “Generators”) accepts liability for any 

loss or damage whatsoever which may arise from the use of or reliance on the information contained in this document or 

from any errors or omissions, typographical or otherwise in the contents. 

Nothing in this document constitutes advice. Nor does the transmission, downloading or sending of this document create 

any contractual relationship. In particular no licence is granted under any intellectual property right (including trade and 

service mark rights) save for the above licence to download copy, store and distribute this document and to produce 

derived copyright works. 

The liability and responsibility for implementations based on this document rests with the implementer, and not with any 

of the Generators. If you implement any of the contents of this document, you agree to indemnify and hold harmless 

each Generator in any jurisdiction against any claims and legal proceedings alleging that the use of the contents by you 

or on your behalf infringes any legal or other right of any of the Generators or any third party. 

None of the Generators accepts any liability whatsoever for any direct, indirect or consequential loss or damage arising 

in any way from any use of or reliance on the contents of this document for any purpose. 

The NICC Standards Web site contains the definitive information on the IPR Policy and Anti-trust Compliance Policy 

If you have any comments concerning the accuracy of the contents of this document, please write to: 

The Technical Secretary, NICC Standards Ltd., 

Michael Faraday House, 

Six Hills Way, 

Stevenage 

SG1 2AY 

NICC Standards Limited

3 


Contents 

Intellectual Property Rights ........................................................................................................................................ 5 

Foreword .................................................................................................................................................................... 5 

Introduction ............................................................................................................................................................... 5 

1 Scope ................................................................................................................................................................. 6 

2 References ......................................................................................................................................................... 6 

2.1 Normative references ........................................................................................................................................ 6 

2.2 Informative references ...................................................................................................................................... 7 

3 Definitions, symbols and abbreviations.............................................................................................................. 7 

3.1 Definitions ......................................................................................................................................................... 7 

3.3 Abbreviations .................................................................................................................................................... 8 

4 Test Methodology .............................................................................................................................................10 

4.1 Reference DSLAMs........................................................................................................................................... 10 

4.2 Performance Requirements ............................................................................................................................. 10 

4.3 ADSL Fall-back ................................................................................................................................................. 10 

5 Conditions of Test .............................................................................................................................................11 

5.1 Environment for tests ...................................................................................................................................... 11 

5.2 Power supply .................................................................................................................................................. 11 

5.3 Test point ......................................................................................................................................................... 11 

6 Requirements ....................................................................................................................................................11 

6.1 VDSL2 Layer ..................................................................................................................................................... 11 

6.1.1 G.993.2 Requirements ................................................................................................................................ 11 

6.1.2 Handshake .................................................................................................................................................. 11 

6.1.3 Bandplan ..................................................................................................................................................... 12 

6.1.4 ANFP............................................................................................................................................................ 12 

6.1.5 Bit Swap ...................................................................................................................................................... 12 

6.1.6 Seamless Rate Adaption. ............................................................................................................................ 13 

6.1.7 Retransmission. ........................................................................................................................................... 13 

6.1.8 Upstream PSD Calculation. ......................................................................................................................... 13 

6.1.9 17MHz Vectoring ........................................................................................................................................ 14 

6.1.10 Virtual Noise ........................................................................................................................................... 14 

6.1.11 Monitoring Diagnostics and Test ............................................................................................................ 14 

6.2 Ethernet OAM .................................................................................................................................................. 14 

6.3 Additional Requirements ................................................................................................................................. 15 


4 


Annex A (normative): ................................................................................................................................................16 

Generic Test Methods ................................................................................................................................................... 16 

A.1 Bit swap .................................................................................................................................................................. 16 

A.2 Seamless Rate Adaption ......................................................................................................................................... 17 

A.3 Vectoring ................................................................................................................................................................ 18 

Annex B (normative):.................................................................................................................................................19 

Access Node Operator Specific Requirements .............................................................................................................. 19 

B.1 Openreach .............................................................................................................................................................. 19 

B.1.1 CPE Modem Requirements ............................................................................................................................. 19 

B.1.2 Test Configuration .......................................................................................................................................... 19 

B.1.2.1 Band Profiles ................................................................................................................................................ 19 

B.1.2.2 Loops ............................................................................................................................................................ 19 

B.1.2.3 Crosstalk ....................................................................................................................................................... 20 

B.1.2.4 Network Equipment ..................................................................................................................................... 21 

B.1.2.5 Test Equipment ............................................................................................................................................ 21 

B.1.2.6 Test Requirements ....................................................................................................................................... 21 

B.1.2.7 Initial Gating Tests ....................................................................................................................................... 22 

B.1.2.7.1 Synchronisation ........................................................................................................................................ 22 

B.1.2.7.2 Network Interference ............................................................................................................................... 23 

B.1.2.8 BT SIN 498 Modem Compatibility Tests ....................................................................................................... 23 

B.1.2.8.1 Physical Layer ............................................................................................................................................ 23 

B.1.2.8.2 VDSL2 Layer .............................................................................................................................................. 23 

B.1.2.8.3 Ethernet, WAN and OAM .......................................................................................................................... 36 

B.1.2.9 NGA testing .................................................................................................................................................. 37 

B.1.2.9.1 Transmission Performance Testing ........................................................................................................... 37 

B.1.2.9.2.Verification of Hlog and QLN (T2R Capability) .......................................................................................... 41 

B.1.2.9.3 Verification of “Router Only” Functionality .............................................................................................. 43 

B.1.3 Details of Impedance matching network ........................................................................................................ 44 

B.1.4 Reference DSLAMs .......................................................................................................................................... 45 

Annex C (normative): .................................................................................................................................................46 

MPF Provider Specific Requirements ............................................................................................................................ 46 

C.1 Openreach .............................................................................................................................................................. 46 

C.1.1 Handshake ...................................................................................................................................................... 46 

C.1.2 ANFP ................................................................................................................................................................ 47 

C.1.3 AELEM ............................................................................................................................................................. 48 

History .......................................................................................................................................................................50 


5 


Intellectual Property Rights 

IPRs essential or potentially essential to the present document may have been declared to NICC. 

Pursuant to the NICC IPR Policy, no investigation, including IPR searches, has been carried out by 

NICC. No guarantee can be given as to the existence of other IPRs which are, or may be, or may 

become, essential to the present document. 

Foreword 

This NICC Document (ND) has been produced by NICC Standards TSG Digital Subscriber Line 

Task Group. 

Introduction 

This document specifies the test requirements for modems intended to connect to the VDSL2 

‘wires-only’ service provided by Ethernet Active Line Access (ALA) networks at the ‘wires-only’ 

UNI as described in the NICC Standards document “ND1031: Active Line Access: ALA UNI 

Specification”. 

The minimum test requirements are described including generic test requirements and the specific 

test requirements of the Access Node Operators and MPF providers that constitute ALA networks. 

For the purposes of this document, VDSL2 is the technology defined in ITU-T Recommendation 

G.993.2 “Very high speed digital subscriber line transceivers 2 (VDSL2)”. 


6 


1 Scope 

ND1436 is a test plan for a VDSL2-based modem device intended for connection in the UK to a 

wires-only UNI, as described in part in ND1031[11]. The test plan details tests which, if passed, 

will give a high degree of confidence that the attachment of the device will: a) not cause network 

harm and b) will deliver the necessary Test and Diagnostic (T&D) functionality, and c) 

interoperate with VDSL2 DSLAMs in use by appropriate CPE Modem Providers. This will allow 

the Access Node Operators, MPF Providers and CPE Modem Providers to continue to operate 

an efficient and scalable service, with minimal impact on Trouble To Resolve (T2R) processes 

designed for the fully managed install variant. ND1436 draws on requirements defined in 

ND1031 and other Access Node Operator and MPF Provider specific requirements to define the 

minimal set of tests. ND1436 does not define the expected level of Layer 1 transmission 

performance for VDSL2 lines deployed according to wires-only operation. 

2 References 

For the particular version of a document applicable to this release see ND1610 [1]. 

2.1 Normative references 

The following referenced documents are indispensable for the application of this document. For 

dated references, only the edition cited applies. For non-specific references, the latest edition of 

the referenced document (including any amendments) applies. 

[1] NICC ND1610 Next Generation Networks, Release Definition, V.3.1.z 

[2] BT SIN 498, Version 5, July 2013: “Generic Ethernet Access Fibre to the Cabinet 

(GEA-FTTC) Service and Interface Description” 

[3] ITU-T Recommendation G.993.2: “Very high speed digital subscriber line 

transceivers 2 (VDSL2)” 

[4] Broadband Forum Technical Report TR-114 Issue 2, November 2012 “VDSL2 

Performance Test Plan” 

[5] Broadband Forum Technical Report TR-115 Issue2, July 2012: “VDSL2 

Performance Test Plan” 

[6] NICC ND1602 : Specification of the Access Network Frequency Plan (ANFP) 

Applicable to Transmission Systems Used on the BT Access Network. 

http://www.niccstandards.org.uk/files/current/ND1602-2011- 

09_v5.1.1.pdf?type=pdf 

[7] ETSI TS 101 270-1 : Transmission and Multiplexing (TM);Access transmission 

systems on metallic access cables; Very high speed Digital Subscriber Line 

(VDSL);Part 1: Functional requirements 

[8] ITU-T Recommendation G.994.1: “Handshake procedures for digital subscriber 

line (DSL) transceivers” 


7 


[9] ITU-T Recommendation G.993.5: incorporating Amendments 1 and 2 : “Self- 

FEXT cancellation (vectoring) for use with VDSL2 transceivers”. 

[10] ITU-T Recommendation G.997.1: Physical layer management for digital 

subscriber line (DSL) transceivers 

[11] NICC ND1031: Active Line Access: ALA UNI Specification, v.1.2.1 

[12] NICC KCH ANFP issue 3, ND1604, June 2012 

[13] ITU-T Recommendation G.994.1: Handshake procedures for digital subscriber 

line transceivers 

[14] “Improved Impulse Noise Protection for DSL Transceivers”, ITU-T 

Recommendation G.998.4 

[15] “Ethernet ALA Service Definition”, NICC ND1030, December 2010 

[16] Access network xDSL splitters for European Deployment; Part 1: Generic 

specification of xDSL over POTS splitters, ETSI TS 101-952-1 (v1.1.1), June 

2009 

[17] Access network xDSL splitters for European Deployment; Part 3 Generic 

specification of static distributed filters for xDSL over POTS, ETSI TS 101-952-3 

(v1.1.1), February 2012 

[18] Broadband Forum Technical Report TR-138, Issue 1, “Accuracy Tests for Test 

Parameters” 

[19] Broadband Forum Technical Report TR-101, Issue 2, “ Migration to Ethernet- 

Based Broadband Aggregation” 

[20] NICC ND1436-2013-09_v1.1.2-1.xlsx Microsoft Excel Spreadsheet of 

“Stockholm Noise Reference Data”. 

[21] NICC ND1436-2013-09_v1.1.2-2.xlsx Microsoft Excel Spreadsheet of “HLOG 

evaluation”. 

[22] NICC ND1436-2013-09_v1.1.2-3.xlsx Microsoft Excel Spreadsheet of “QLN 

evaluation template”. 

2.2 Informative references 

None. 

3 Definitions, symbols and abbreviations 

3.1 Definitions 

For the purposes of the present document, the following terms and definitions apply: 


8 


Access Node Operator (ANO) : The provider of the network access communications equipment 

including head-end equipment such as DSLAMs and MSANs. 

CPE Modem Provider : The provider of the CPE modem to the end-user to enable connection to 

the “wires–only” VDSL2 service. 

End-User : The end customer being served by the “wires-only” service. 

MPF provider : The provider responsible for the provision and maintenance of the access cable 

and related cable infrastructure. 

Self-install : Refers to an install process where equipment is delivered to and installed by the end 

user to enable their service without a CPE modem provider or Access Node Operator fitting the 

equipment. 

Wires-only : Refers to an install process where the Access Node Operator doesn’t supply, fit or 

configure equipment at the end user premise. This is carried out by the CPE modem provider or 

end user. 

3.3 Abbreviations 

For the purposes of the present document, the following abbreviations apply: 

ADSL Asymmetric Digital Subscriber Line 

AELEM Alternative Electrical Length Estimation Method 

ALA Active Line Access 

ANFP Access Network Frequency Plan (BT or KCH) 

ANO Access Node Operator 

BRAS Broadband Remote Access Server 

CAL Cabinet Assigned Loss (Also referred to as ESEL) 

CP 

Communications Provider(s) 

CPE Customer Premises Equipment 

DHCP Dynamic Host Control Protocol 

DPBO Downstream Power Back Off 

DSLAM Digital Subscriber Line Access Multiplexer. 

ELE-M1 Electrical Length Estimation Method 1 

ESEL E-Side Electrical Length 

FTTC Fibre To The Cabinet 

MPF Metallic Path Facility 

NGA Next Generation Access 

NTP Network Termination Point 

OAM Operations Administration and Maintenance 

PPP Point-to-Point Protocol 

PSD Power Spectral Density 

REIN Repetitive Electrical Impulse Noise 

SIN Supplier Information Note 

SRA Seamless Rate Adaption 

UNI User Network interface 

UPBO Upstream Power Back-Off 


9 


US0 Upstream Band 0 

VDSL2 Very High Speed Digital Subscriber Line 2 

WAN Wide Area Network 


10 


4 Test Methodology 

4.1 Reference DSLAMs 

Tests referenced from TR-114 [4] and TR-115 [5] require the CPE modem to interoperate with a 

DSLAM. The deployment of particular DSLAMs and their configuration vary between ANOs and so 

the type of DSLAM to be used for the tests defined in this document is determined by the ANO for 

which the CPE modem is intended to be deployed. 

See the relevant annexes to this document for ANO-specific details and configurations. 

4.2 Performance Requirements 

This test plan does not specify rate versus reach performance requirements. CPE Modem 

Providers should satisfy themselves that appropriate levels of transmission performance have 

been achieved for the deployment scenarios that they intend to use. Recommended performance 

tests are specified in TR-114 [4] and TR-115 [5]. 

4.3 ADSL Fall-back 

ADSL fall-back is not part of the current solution. This will be addressed in the ANO specific 

Annexes to this document where required. 


11 


5 Conditions of Test 

5.1 Environment for tests 

All tests shall be performed in the following conditions : 

- an ambient temperature in the range 15° C to 35° C; 

- a relative humidity in the range 5 % to 75 %. 

5.2 Power supply 

All tests shall be carried out within ± 5 % of the normal United Kingdom operating voltage. 

5.3 Test point 

The CPE modem connection topology is defined in [11] section 5.1. This defines the Distributed 

Filter Topology and the Centralised Filter Topology. All tests shall be carried out at the physical 

network termination point (NTP) defined in these cases depending on which topology is required 

by the deployment scenario. 

If the CPE modem utilises the Distributed Filter Topology then a CPE VDSL filter must be provided 

for the tests. Regardless of the CP deployment scenario, tests specified in this document must be 

performed using the Distributed Filter Topology as a minimum. Tests for alternative topologies are 

for further study. 

6 Requirements 

6.1 VDSL2 Layer 

6.1.1 G.993.2 Requirements 

Requirement 

ND1031 [11] Reference : 5.2.1.1 

The CPE modem shall fully comply with the VDSL2 mandatory requirements of G.993.2 [3]. 

Test 

Compliance with the VDSL2 mandatory requirements shall be confirmed to the ANO by the CPE 

Modem Provider. 

6.1.2 Handshake 

Requirement 

ND1031 [11] Reference : 5.2.1.2 

The CP provided modem shall support operating with cabinet based VDSL2. This involves 

supporting the appropriate handshake parameters (as defined in G.994.1 Amendment 1 [8]), plus 


12 


downstream PSD shaping and upstream power back-off as defined in G.997.1 [10] and G.993.2 

[3]. 


Compliance shall be determined by the tests defined in the ANO and MPF provider-specific 

annexes to this document. 

6.1.3 Bandplan 

Requirement 

ND1031 [11] Reference : 5.2.1.3. 

The CP provided modem shall support operation that complies with the current MPF provider 

ANFPs [6], [12]. 


Compliance shall be determined by the tests defined in the ANO and MPF provider-specific 

annexes to this document. 

6.1.4 ANFP 

Requirement 

ND1031 [11] Reference : 5.2.1.3. 

The CPE modem shall comply with the relevant requirements of the current MPF provider-specific 

ANFP documents [6], [12] in VDSL2 operating mode. 

Note : The tests specified in the ANFPs currently cover static UPBO only. Tests for dynamic UPBO 

are defined in the MPF Provider-specific annexes to this document if required. 


Compliance shall be determined by the tests defined in the MPF provider-specific annexes to this 

document. 

6.1.5 Bit Swap 

Requirement 

ND1031 [11] Reference : 5.2.1.4. 

The CP provided modem shall support bit swap as defined in G.993.2 [3]. 


Compliance shall be determined by the test specified in Annex A.1. 


13 


6.1.6 Seamless Rate Adaption. 

Requirement 

ND1031 [11] Reference : 5.2.1.5. 

The CPE modem shall support seamless rate adaptation (SRA) as defined in Section 13.1 of 

G.993.2 [3]. 



6.1.7 Retransmission. 

Requirement 

ND1031 [11] Reference : 5.2.2. 

The CPE modem shall support downstream DSL layer retransmission as specified in G.998.4 [14]. 


Compliance shall be determined by the test specified in TR-114 [4] Annex-E or the ANO-specific 

annexes. 

6.1.8 Upstream PSD Calculation. 

Requirement 

ND1031 [11] Reference : 5.2.3. 

The CPE modem must support an algorithm that calculates the upstream transmit PSD correctly, 

regardless of the quality of installation. A suitable algorithm to ensure this requirement is met is 

the optional ELE-M1 (also known as AELEM) as detailed in G.993.2 [3] – VDSL2 wires-only 

equipment shall support ELE-M1. 

As described in [11], where microfilters are used, in-home wiring could distort the frequency 

response of the transmission channel. Such distortions could lead an algorithm that is not 

compliant to ELE-M1 to incorrectly estimate the upstream electrical distance to the DSLAM, and 

hence, incorrectly select the upstream transmit PSD. 


Compliance shall be determined by tests defined in the ANO-specific annexes or TR-115 [5] 

section 5.7.5, “Upstream Power Back-off Test” using the ELE-M1 mode for determining electrical 

length as defined in G.993.2 [3] and using the ANO-specific VDSL2 profiles. 


14 


6.1.9 17MHz Vectoring 

Requirement 

ND1031 [11] Reference : 5.2.4. 

Alien crosstalk, if not intelligently managed, can have negative effects on groups of vectored 

VDSL2 lines. To prevent alien interference into vector groups, VDSL2 equipment that the CP 

provider connects to the VDSL2-UNI, shall fully support vectoring as described in G.993.5. 



6.1.10 Virtual Noise 

Requirement 

ND1031 [11] Reference : 5.2.5. 


Compliance shall be determined by tests defined in TR-115 [5] section 5.9, “Virtual Noise Test”. 

6.1.11 Monitoring Diagnostics and Test 

Requirement 

ND1031 [11] Reference : 5.2.6. 

Parameters specified in G997.1 [10] and G993.2 [3] for reporting inventory information, and 

performance and operational monitoring information shall be supported by the CPE modem. To 

support remote diagnostics and test for lines, loop diagnostics specified in G993.2 [3] and G997.1 

[10] shall be supported. Diagnostics shall meet the accuracy requirements described in TR-138 

[18]. 

Parameter requirements are specified in the ANO-specific annexes to this document. 


Compliance tests are specified in the ANO-specific annexes. 

6.2 Ethernet OAM 

Requirement 

ND1031 [11] Reference : 5.3. 

The wires-only ALA VDSL2 UNI shall be capable of transporting Ethernet OAM as specified in the 

NICC Ethernet ALA Service Definition [15]. In order to be able to use OAM functionality across the 

UNI, the CPE modem needs to support the OAM functionality requirements of section 7.3.1 in 

Broadband Forum TR-101 [19]. 


15 



Compliance tests are specified in the ANO-specific annexes. 

6.3 Additional Requirements 

Additional requirements may have been specified in the operator-specific annexes. Consult these 

annexes for further information. 


16 


Annex A (normative): 

Generic Test Methods 

NOTE : Where the test methods refer to a DSLAM, the DSLAM should be of a type specified by 

the relevant ANO for which compliance is intended to be demonstrated. 

A.1 Bit swap 

Compliance shall be determined by the following test : 

Noise Generator/ 

Injector 

Function 

Generator 

DSLAM 

Line Simulator 

CPE 

PC 

PC 

Figure A.1 : Test Configuration for Checking Bit Swap 

1) Configure the DSLAM to implement an ESEL value of 30dB and the operator-specific band 

profile. 

1) Connect the CPE modem to the DSLAM using the Test Configuration shown in Figure A.1. 

2) Set the line simulator to a loop length of 500m of TP-100 cable with ANO-specific crosstalk 

injected at each end of the system. 

3) Ensure that the CPE modem has attained synchronisation. 

4) Capture bit allocation tables (both upstream and downstream) from the DSLAM element 

manager. 

5) Inject a narrow band RFI source using the function generator – this simulates a broadcast 

AM transmission. Set the frequency to 3MHz and set the power at -50dBm and increase over 1 

minute to -20dBm in 2dB steps. 

6) Recapture the bit allocation table (both upstream and downstream) from the element 

manager. 

7) Compare both bit allocation tables. 

8) Repeat for a 10MHz tone. 

9) If bit swap is implemented then there should be differences between the two sets of bit 

allocation table captured from steps 5 and 7, especially around the frequencies used for the RF 

tones. 

10) The system should not retrain during this test. 


17 


Expected Outcome – “Pass” if bit swap is observed in the upstream and downstream directions 

and modem does not lose synchronisation, else “Fail”. 

A.2 Seamless Rate Adaption 


Variable 

Attenuator 


Injector 

Variable 

Attenuator 

DSLAM 


CPE 

PC 

PC 

Figure A.2 : Test Configuration for Checking Seamless Rate Adaptation 

1) Configure the DSLAM to implement an ESEL value of 30dB and the operator-specific SRA 

profile. 

2) Connect the CPE modem to the DSLAM using the test configuration shown in Figure A.2. 

3) Set the line simulator to a loop length of 500m of TP-100 cable with ANO-specific crosstalk 

injected at each end of the system. 


5) Record the upstream and downstream margins and data rates as reported by the DSLAM. 

6) Reduce the crosstalk injected at the CPE end of the link (i.e. downstream) by 1dB and record 

the downstream rate and noise margin. 

7) Reduce the downstream crosstalk in 1dB steps, recording the downstream margin and data 

rates for each step. After an x+1 dB reduction in crosstalk (i.e. an x+1 dB improvement in 

margin), the upper margin threshold value, x (as defined in the ANO-specific SRA profile) will be 

exceeded and the data rate should change. 

8) Repeat for the upstream direction. 

9) The CPE should not lose synchronisation during this test. 

Expected Outcome – This test will be a “Pass” if the system is found to change data rate in each 

direction when the noise margin improves by x+1 dB without losing synchronisation. If the rate 

does not change or if the system retrains, then the result will be a “Fail”. 


18 


A.3 Vectoring 


Vectored 

DSLAM 

48 interferers 

16 

Vectored 

CPE 


16 

Vectored 

CPE 


16 

Vectored 

CPE 

PC 

200m 300m 400m 

500m 

900m 

Figure A.3 : Test Configuration for Checking Vectoring 

Configure the DSLAM with an operator-specific VDSL2 profile. 

The vectoring test configuration shown in Figure A.3 comprises three lengths of TP-100 100-pair 

cable (200m, 300m and 400m 1 ) which are connected in series to form a 500m length (i.e. 200m + 

300m) and a 900m length (i.e. 200m + 300m + 400m) of cable 1,2 . 

16 vectored CPE modems are located 200m from the DSLAM, another 16 vectored CPE modems 

are located 500m from the DSLAM and a final 16 vectored CPE modems are located 900m from 

the DSLAM. The same cable segments are used to construct the 200m, 500m and 900m lengths. 

This means that there are 48 (i.e. 3 x 16) interferers present in the 200m length, 32 (2 x 16) 

interferers in the 300m length and 16 interferers in the 400m length. 

1) Capture the performance data of the 48 CPE modems both with vectoring disabled and with 

vectoring enabled. This enables the performance to be benchmarked. 

2) Replace one of the modems located 200m from the DSLAM with the CPE under test. 

3) Measure the non-vectored performance and then the vectored performance (assuming that 

the CPE supports vectoring). 

4) Repeat for 500m and 900m cable lengths. 

5) Compare the results obtained using the CPE at each cable length against those obtained 

using the 48 vectored CPE. Note whether the CPE under test supports vectoring and whether 

there is any significant drop in performance either to the modem or the rest of the vector group 

when vectoring is enabled 

Expected Outcome – “Pass” if the CPE modem is capable of supporting vectoring and does not 

adversely affect the performance of the vector group, “Fail” if not. 

1 These loops are selected as being representative of typical lengths encountered in the UK access network. Other lengths can be substituted. 

2 Alternatively a suitable crosstalk emulator & loop simulator for vectored VDSL2 can be substituted. 


19 


Annex B (normative): 

Access Node Operator Specific Requirements 

B.1 Openreach 

B.1.1 CPE Modem Requirements 

The CPE modem requirements are specified in Section 3 of BT SIN 498 [2]. 

B.1.2 Test Configuration 

B.1.2.1 Band Profiles 

The following default band profile shall be used for all tests unless otherwise specified: 

sfaD800_001_00_00U200_001_00_00 

This differs from the band profile defined in TR-114 [4] in that it permits the use of a 17MHz band 

plan that supports use of the upstream 0 (US0) band between 25kHz and 138kHz. The band plans 

defined in TR-114 currently do not support the use of US0. 

This profile defines the following parameters: 

sfaD800_001_00_00U200_001_00_00 

Parameter Downstream Setting Upstream Setting 

Maximum Data Rate 80Mbit/s 20Mbit/s 

Minimum Data Rate 128kbit/s 128kbit/s 

Minimum Noise Margin 0dB 0dB 

Target Noise Margin 6dB 6dB 

Maximum Noise Margin 31dB 31dB 

Dmax 0 0 

INP min 0 0 

Adaption Mode Adapt at start up Adapt at start up 

Operating Mode 

G.993.2 

Band Plan 998ADE17 (Plan B8-11) [3]. 

Table B.1 : NGA Profile Definition 

B.1.2.2 Loops 

European VDSL test loop #1 (0.5mm Cu) [7] shall be used for all tests. Note that 0.5mm gauge 

cable is also referred to as TP-100 – the two terms are interchangeable. 

B.1.2.2a Plain Old Telephony Service 

It should be noted that POTS shall be connected onto the line via the splitter in the DSLAM on all 

test lines. The status of the line (off hook, on hook etc.) should not have any impact on 


Level (dBm/Hz) 

Level (dBm/Hz) 

20 


performance if the splitter filters used at each of the line are compliant with ETS 101 952-1 [16] or 

ETS 101 952-3 [17]. 

B.1.2.3 Crosstalk 

The VDSL2 “Stockholm Lite” noise model shall be used as it includes the US0 band whereas the 

noise models defined in TR-114 do not currently include this frequency band (25 to 138kHz). This 

is representative of the noise ensemble that can be expected in a typical NGA cable binder. 

A separate pair of noise files (upstream and downstream) is generated for each distance. In 

addition, a set of noise files is required for each of the 27 CAL (Cabinet Assigned Loss) values 

defined in the ANFP [6] as the DPBO shaping impacts the transmit PSD of the VDSL2 signal 

launched at the cabinet. The noise files for a 500m length of 0.5mm copper cable (equivalent to an 

electrical loss of 10dB measured at 1MHz) are shown below for CAL values of 10, 30 and 50dB. 

-80 

Downstream NGA Noise (kl0=10dB) 

-90 

-100 

-110 

CAL=10dB 

CAL=30dB 

CAL=50dB 

-120 

-130 

-140 

10,000 100,000 1,000,000 10,000,000 100,000,000 

Frequency (Hz) 

Figure B.1 : Downstream NGA Noise Spectrum (500m) 

-80 

Upstream NGA Noise (kl0=10dB) 

-90 

-100 

-110 

CAL=10dB 

CAL=30dB 

CAL=50dB 

-120 

-130 

-140 

10,000 100,000 1,000,000 10,000,000 100,000,000 

Frequency (Hz) 

Figure B.2 : Upstream NGA Noise Spectrum (500m) 

These noise files can be generated and injected using a noise generator/injector unit. 


21 


The PSD data required to generate and calibrate the noise files for CAL values of 10, 30 and 50dB 

over a range of lengths of 0.5mm gauge cable are contained in an accompanying spreadsheet 

[20]. 

B.1.2.4 Network Equipment 

Currently Openreach uses network equipment from two strategic vendors (namely ECI and 

Huawei) in its NGA FTTC network. This means that any CPE modem must be able to operate 

across a variety of DSLAM chassis types and line cards. 

The test procedures described in this document shall be performed using the current firmware 

versions of network equipment deployed in the Openreach FTTC NGA network. 

B.1.2.5 Test Equipment 

Table B.2 shows examples of test equipment that can be used to perform the tests specified in this 

annex : 

Test Equipment 

Baluns (x2) 

TP-100/0.5mm Line Simulator 

Noise Generator/Injector 

Function Generator 

Arbitrary Waveform generator 

RMS/Peak Voltmeter 

Spectrum Analyser 

Example 

North Hills 0320BF 

Spirent DLS8235 

Telebyte 458-LM-E1-30-TP100 

Spirent DLS5500/5504 

Telebyte 4901 

Agilent 33250B 

Sony Tektronix AWG2021 

Rhode and Schwartz URE3 

HP3585A 

Loss Pad Custom Built (see Annex B.1.3 ) 

Crosstalk Emulator & Loop Simulator 

Telebyte VxT-48 

Table B.2 – Example Test Equipment 

B.1.2.6 Test Requirements 

The test requirements are split into the following three sections: 

Initial Gating 

SIN 498 Compliance 

NGA Testing 


22 


The details of the various tests are defined in the following sub-sections. 

B.1.2.7 Initial Gating Tests 

The purpose of these tests is to check that the CPE modem can synchronise with a NGA field 

configuration and will not cause network harm. It is necessary for a CPE modem to “Pass” both of 

these tests before full SIN 498 testing can commence. If either of these tests results in a “Fail”, the 

CPE modem provider will be informed by Openreach and asked to resolve the issue. 

B.1.2.7.1 Synchronisation 

Description – The CPE modem shall achieve synchronisation to a reference NGA DSLAM and can 

achieve end-to-end-connectivity with an external server. 

Test Procedure – Connect the CPE modem to a port on the DSLAM via a 100m length of 

simulated TP-100 gauge cable and ensure that it trains up and reaches synchronisation. Following 

this, attempt to set up an end-to-end connection between a PC connected to the CPE modem and 

an external server. 

Server 

BRAS 

DSLAM 


CPE 

PC 

EMS PC 

PC 

Figure B.3 : Test Configuration for Checking Basic Synchronisation 

1) Configure the DSLAM to implement an ESEL value of 30dB and ensure that the default band 

profile is loaded onto a port. 

2) Set the Line Simulator to a loop length of 100m of TP-100 cable with noise injection disabled 

(i.e. noise free) 

3) Connect the CPE modem to that port and check that it reaches synchronisation within 60 

seconds. 

4) If synchronisation is attained, check that the CPE modem stays in synchronisation for a 

minimum of 120 seconds. 

5) Check that end-to-end connectivity has been achieved by launching an Internet session 

using the PC connected to the CPE modem. This will confirm whether the modem has 

established a DHCP or PPP session with the server. 


23 


Expected Outcome – This test will be deemed a “Pass” if the modem attains synchronisation within 

60 seconds stays trained up for a minimum of 120 seconds and can achieve an end to end 

connection with the external server, else the test will be deemed a “Fail”. This test also verifies 

that the physical layer interface on the CPE modem is wired correctly. 

B.1.2.7.2 Network Interference 

Description – The CPE modem shall not cause adverse interference to other systems operating in 

the same cable binder. In order to validate this, the Modem shall only implement the A43 or A43c 

tone sets defined in G.994.1 [8] demonstrate that it does not cause adverse interference to other 

lines operating in a vectored group and comply with the requirements of Part C of the BT Access 

Network Frequency Plan [6]. 

Test Procedure – The tests are defined in the Openreach MPF Provider Annex, C.1.1 and C.1.2. 

B.1.2.8 BT SIN 498 Modem Compatibility Tests 

B.1.2.8.1 Physical Layer 

R.PHY.1 Physical Connection 

Description – The socket on the CPE modem connecting to the Openreach UNI (i.e. WAN port) 

shall be either a RJ11 or RJ45 type to enable it to be connected to the VDSL2 filter using standard 

leads. The VDSL2 connection is presented on the middle two pins – i.e. pins 3&4 (RJ11) or pins 

4&5 (RJ45). The other pins are not connected. Pin numbering is from the left, looking into the 

socket with the contacts uppermost. Polarity is unimportant. 

Test Procedure – Visual inspection. 

Expected Outcome – The basic synchronisation and network interference tests will confirm 

whether the DSL socket on the CPE modem has been wired correctly. 

B.1.2.8.2 VDSL2 Layer 

R.VDSL2.1 Support of Mandatory Requirements of G.993.2 

REMOVED – Test now in main body of document. 

R.VDSL2.2 Support of Profile 17a 

Description – The CPE modem shall support VDSL2 Profile 17a as defined in G.993.2 [3]. 

Test Procedure – Measure the downstream PSD on a short line (100m) to check that the full 

17MHz bandwidth is being utilised 3 and that the downstream transmit power does not exceed that 

defined for Profile 17a. 

3 Currently the Huawei system will only use up to 17.1MHz whereas the ECI system will use the full 17.664MHz. 


24 


Power Meter 

Baluns 

Spectrum 

Analyser 

PC 

DSLAM 

Match 

Pad 


CPE 

PC 

PC 

Figure B.4 : Test Configuration for Measuring Downstream PSD 

Details of the impedance matching pad used are contained in Annex B.1.3 . 

1) Configure the DSLAM to implement an E-side electrical length (ESEL) 4 value of 30dB and 

configure a port with the default band profile. 

2) Set the line simulator to a loop length of 100m of TP-100 cable with noise injection disabled 

(i.e. noise free). 

3) Connect the CPE modem to the DSLAM using the Test Configuration shown in Figure B.4. 


5) Capture the downstream PSD and wideband power and compare against Part B of the BT 

ANFP [6]. 

6) Check that the full 17MHz spectrum is used. 

Note that this test can be performed as part of requirement R.VDSL2.5. 

Expected Outcome – This test will be deemed a “Pass” if the full 17MHz spectrum is observed (i.e. 

use of downstream band between 12 and 17.664MHz) and that the downstream transmit power 

does not exceed 14.5dBm. If these criteria are not met, then the result is a “Fail”. 

R.VDSL2.3 

This requirement has been removed from the current revision of SIN 498. 

R.VDSL2.4 Compliance with UK ANFP Part C 

Refer to Annex C. 

R.VDSL2.5 Support of 998ADE17 Band Plan 

4 The ITU-T G.993.2 Recommendation uses the term E-side Electrical Length (or ESEL) to refer to the loss of the cable connecting the exchange to 

the cabinet. The UK ANFP uses the term Cabinet Assigned Loss (or CAL) to describe the same parameter. In both cases, the insertion loss is 

measured at a frequency of 300kHz. 


25 


Description – The CPE modem shall support 17MHz operation using band plan B8-11 (i.e. plan 

998ADE17) as defined in Annex B of G.993.2 [3]. 

Test Procedure – For each value of ESEL to be evaluated, measure the downstream PSD on a 

short line (100m) to check that the full 17MHz bandwidth is being utilised and that the downstream 

transmit power does not exceed that defined for Profile 17a. The setup shown in Figure B.4 shall 

be used for this test. 

1) Configure the DSLAM to implement an E-side electrical length (ESEL) value of 30dB and the 

default band profile. 

2) Connect the CPE modem to the DSLAM using the Test Configuration shown in Figure B.4. 


(i.e. noise free) 


5) Capture the downstream PSD and wideband power and compare against Part B of the ANFP 

[6] for that value of ESEL. 

6) Check that the full 17MHz spectrum is used. 

7) Repeat for a minimum of two other ESEL values (nominally 10dB and 50dB). 

Note that this test also covers requirement R.VDSL2.2. 

Expected Outcome – This test will be deemed a “Pass” if the transmit spectra does not exceed the 

limit mask defined Part B of the ANFP [6] for each ESEL value evaluated. If these criteria are not 

met, then the result is a “Fail”. 

R.VDSL2.6 Support of Cabinet based VDSL2 Operation 

Compliance shall be determined by the following test. 


26 


Carrier Set Designation 

Upstream Carrier Sets 

Tone 

Numbers 

Maximum 

power 

level/carrier 

(dBm) 

Downstream Carrier Sets 

Tone 

Numbers 

Maximum 

power 

level/carrier 

(dBm) 

A43 9 17 25 -1.65 40 56 64 -3.65 

A43c 9 17 25 -1.65 257 293 337 -3.65 

Table B.4 : Carrier Sets A43 and A43c 

Note that the use of additional tone-sets (B43, B43c, V43 etc.) is not permitted as these may cause 

the spectral limits defined in Parts B and C of the BT ANFP [6] to be breached. 

Test Procedure – The Test Configuration shown in Figure B.4 shall be used for this test. 

1) Set the spectrum analyser for a start frequency of 10kHz and a stop frequency of 5MHz. 



3) Connect the CPE modem to DSLAM using the Test Configuration shown in Figure B.4. 



5) During train-up, capture the handshake tones generated by each end of the transmission 

system. 

6) Compare the tones against those defined for A43 and A43c. 


Expected Outcome – This test will be deemed a “Pass” only if A43/A43c tone sets are being used. 

R.VDSL2.7 Support of UPBO 

Description – The CPE modem shall support Upstream Power Back Off (UPBO) as defined in 

G.993.2 [3]. 

Test Procedure – See R.VDSL2.4. 

Expected Outcome – If the upstream transmit spectrum complies with Part C of the BT ANFP [6] 

over the various loop lengths tested then this will be deemed a “Pass” as this requires UPBO to be 

implemented correctly, else the result will be a “Fail”. 

R.VDSL2.8 Support of U0 Band 

Description – The CPE modem shall support the use of the upstream band (US0) between 25kHz 

and 138kHz. 


27 


Test Procedure – 

1) Configure the DSLAM to implement a CAL value of 30dB and the default band profile. 

2) Connect the CPE modem to the DSLAM using the Test Configuration shown in Figure 

C.2. 

3) Set the line simulator to a loop length of 2000m of TP-100 cable with noise injection 

disabled (i.e. noise free). 


5) Capture the upstream PSD and wideband power and compare against Part C of the BT 

ANFP [6]. 

6) Check that the US0 band is used. 

Expected Outcome – This test will be deemed a “Pass” if the U0 band is observed (i.e. use of 

upstream band between 25 and 138kHz). If this band is not seen then the result is a “Fail”. 

R.VDSL2.9 Support of Seamless Rate Adaptation 

See the test specified in Annex A. 

Note that this will require a dedicated profile (SRAD800_001_00_00U200_001_00_00) which is 

basically the same as the default profile but with SRA enabled and the following additional 

parameters defined as shown in Table B.5 

Parameter Downstream Upstream 

Minimum upshift time (s) 10 0 

Minimum downshift time (s) 10 0 

Upper threshold margin 

(dB) 

Lower threshold margin 

(dB) 

9 9 

3 3 

Table B.5 : Settings for Seamless Rate Adaptation Profile 

R.VDSL2.10 Support of Downstream Retransmission 

Description – The modem shall support downstream PHY layer retransmission as defined in 

G.998.4 [14]. 

Test Procedure - 


28 


AWG 


Injector 

DSLAM 


CPE 

PC 

PC 

Figure B.5 : Test Configuration for Verifying Downstream Retransmission 

1. Configure DSLAM to implement an ESEL value of 30dB and retransmission profile 

sfaD800_400R16_04U200_100R08_04 (see Table B.6 & Table B.7). 

2. Connect CPE to DSLAM using the Test Configuration shown in Figure B.5. 

3. Set line simulator to a loop length of 200m with no crosstalk injected at either end of the 

system. 

4. Ensure that CPE has attained synchronisation, check whether downstream retransmission 

is implemented and then leave the system running for 20 minutes. 

5. Capture 15 minute performance data from element manager and check that key 

parameters are reported. 

6. Now turn crosstalk noise on at each end of system, resynch the line and repeat test. Note 

that level of crosstalk noise should be attenuated by 6dB in both upstream and downstream 

for this test. 

7. Capture 15 minute performance data and compare with that recorded previously. 

8. Check that reported data rate, maximum attainable line rate and noise margin have 

changed in each direction. 

9. Now configure the arbitrary waveform generator (AWG) to generate VDSL2 shaped REIN 

comprising 100 μs bursts every 10 ms at an amplitude of -110dBm/Hz (measured at 1MHz) 

and repeat steps 7 and 8. 

10. The 15 minute data should now show a number of parameters including Actual INP, 

RTX_USED_ds, uptime, number of retrains, errored seconds , severely errored seconds 

and/or FEC seconds. The error counts should NOT exceed 900 for any given 15 minute 

period. 

11. Now configure the arbitrary waveform generator (AWG) to generate VDSL2 shaped 

Repetitive Electrical Impulse Noise (REIN) comprising 9 ms bursts every second at an 

amplitude of -110dBm/Hz (measured at 1MHz) and repeat steps 7 and 8. 

12. Once again the 15 minute data should show a number of parameters including Actual INP, 

RTX_USED_ds, uptime, number of retrains, errored seconds , severely errored seconds 

and/or FEC seconds. The error counts should NOT exceed 900 for any given 15 minute 

period. 

13. Now reconfigure the DSLAM to use the equivalent interleaved profile for the cable length 

and repeat steps 4 to 12. Note that the system may retrain during this test when operating 

in interleaved mode – this behaviour is expected. 

14. Repeat for each of the loop lengths and associated profiles defined in Table B.6. 


29 


TP-100 

Length 

(m) 

Retransmission profile 

Interleaved profile 

200 sfaD800_400R16_04U200_100R08_04 sfaD800_400_08_03U200_100_08_04 

500 sfaD800_400R16_04U170_080R08_04 sfaD800_400_08_03U170_080_08_04 

1000 sfaD540_270R16_06U072_036R08_04 sfaD540_270_16_06U072_036_08_04 

1500 sfaD250_125R16_08U027_013R08_04 sfaD250_125_16_08U027_013_08_04 

2000 sfaD131_065R16_08U020_010R08_04 sfaD131_065_16_08U020_010_08_04 

Table B.6 : Profiles Used for Retransmission Testing 

Note: If the modem performance exceeds the upper or lower rates in the interleaved banded 

profiles (i.e. excessive margin or failure to reach synchronisation) then an alternative profile should 

be selected with different rates. 

The retransmission parameters used in these profiles are defined in Table B.7. 


D/S 

U/S 

D/S 

U/S 

D/S 

U/S 

D/S 

U/S 

sfaD800_400R16_04U200_100R08_04 

sfaD540_270R16_06U072_036R08_04 

sfaD250_125R16_08U027_013R08_04 

sfaD131_065R16_08U020_010R08_04 

30 


Parameter 

RTX_MODE 1 1 1 1 1 1 1 1 

MAXNDR_RTX 80000 20000 54000 7200 80000 20000 54000 7200 

MAXETR_RTX 80000 20000 54000 7200 80000 20000 54000 7200 

MINETR_RTX 40000 10000 27000 3600 40000 10000 27000 3600 

DELAYMIN_RTX 0 0 0 0 0 0 0 0 

INPMIN_REIN_RTX 1 1 1 1 1 1 1 1 

INPMIN8_REIN_RTX N/A N/A N/A N/A N/A N/A N/A N/A 

DELAYMAX_RTX 18 18 18 18 18 18 18 18 

INPMIN_SHINE_RTX 32 32 32 32 32 32 32 32 

INPMIN8_SHINE_RTX N/A N/A N/A N/A N/A N/A N/A N/A 

SHINERATIO_RTX 5 5 5 5 5 5 5 5 

IAT_REIN_RTX 0 0 0 0 0 0 0 0 

LEFTR_THRESH 0 0 0 0 0 0 0 0 

Table B.7 : Parameters Used For Retransmission Profiles 

Expected Outcome – The CPE shall implement downstream retransmission. In addition, with 

retransmission enabled, during any 15 minute period the system should report

31 


seconds and no retrains in the downstream direction. If both these criteria are met, then this will 

be deemed a “Pass”, else the modem will be deemed to have failed the test. In general, the error 

performance of the modem with retransmission enabled should be better (i.e. fewer errors and 

retrains) that that using an interleaved profile. 

R.VDSL2.11 Support of Upstream Retransmission (optional) 

Typically a system would not just implement upstream retransmission so this test is designed to 

verify the operation of downstream and upstream retransmission running concurrently. 

Note that if upstream retransmission is supported, the test described in Section R.VDSL2.10 is not 

required. 

Description – The modem shall support downstream and should support upstream PHY layer 

retransmission as defined in G.998.4 [14]. 

Test Procedure - 

Arbitrary 

Waveform 

Generator 


Injector 

DSLAM 


CPE 

PC 

PC 

Note – Outputs from AWG connected 

to both the DSLAM side and Modem side 

Noise Injector 

Figure B.6 : Test Configuration for Verifying Downstream and Upstream Retransmission 

1. Configure DSLAM to implement an ESEL value of 30dB and retransmission profile 

sfaD800_400R16_04U200_100R08_04. 

2. Connect CPE to DSLAM using the Test Configuration shown in Figure B.6. 

3. Set line simulator to a loop length of 200m with no crosstalk injected at either end of the 

system. 

4. Ensure that CPE has attained synchronisation, check whether downstream and upstream 

retransmission are implemented and then leave the system running for 20 minutes. 

5. Capture 15 minute performance data from element manager and check that key 

parameters are reported 

6. Now turn crosstalk noise on at each end of system, resynch line and repeat test. Note that 

level of crosstalk noise should be attenuated by 6dB in both upstream and downstream for 

this test. 


8. Check that reported data rate, maximum attainable line rate and noise margin have 



32 



comprising 100 μs bursts every 10 ms at an amplitude of -110dBm/Hz (measured at 1MHz) 

on both channels and repeat steps 7 and 8. 

10. The 15 minute data should now show a number of parameters including Actual INP, 

RTX_USED_ds, RTX_USED_us, uptime, number of retrains, errored seconds , severely 

errored seconds and/or FEC seconds. The error counts should NOT exceed 900 for any 

given 15 minute period. 


comprising 9 ms bursts every second at an amplitude of -110dBm/Hz (measured at 1MHz) 

and repeat steps 7 and 8. 

12. Once again the 15 minute data should show a number of parameters including Actual INP, 

RTX_USED_ds, RTX_USED_us, uptime, number of retrains, errored seconds , severely 

errored seconds and/or FEC seconds. The error counts should NOT exceed 900 for any 

given 15 minute period. 

13. Now reconfigure the DSLAM to use the equivalent interleaved profile for the cable length 

and repeat steps 4 to 12. Note that the system may retrain during this test when operating 

in interleaved mode – this behaviour is expected. 

14. Repeat for each of the loop lengths and associated profiles defined in Table B.6. 

Note: If the modem performance exceeds the upper or lower rates in the interleaved banded 

profiles (i.e. excessive margin or failure to reach synchronisation) then an alternative interleaved 

profile should be selected. 

The retransmission parameters used in these profiles are defined in Table B.7. 

Expected Outcome – The CPE shall implement downstream and should implement upstream 

retransmission. In addition, with retransmission enabled, during any 15 minute period the system 

should report

33 


R.VDSL2.16 Correct Reporting of Vendor Information 

Description – The CPE modem shall support the correct reporting of Vendor ID, Version Number 

and Serial Number as described in section 11.2.3.6 of G.993.2 [3]. 

Test Procedure – The CPE modem provider shall provide the information shown in Table B.8 and 

Table B.9 to Openreach prior to the start of any testing. This will be achieved using a 

questionnaire which will be included as part of the formal Openreach modem acceptance process. 

CPE Manufacturer 

CPE Product Name/Model 

CPE Software Release Number 

CPE Serial Number 

System Vendor ID 

Chipset Manufacturer 

Chipset Hardware Version 

Chipset Firmware Version 

Table B.8 : CPE Information 

Splitter Manufacturer 

Product Name/Model 

CPE Software Release Number 

Version Number 

Serial Number 

Type (Centralised/Distributed) 

Table B.9 : CPE Splitter Information 

The element manager on the DSLAM will be used to validate the CPE modem Information. This 

should reflect the information provided in Table B.8. CPE splitter information will be verified visually 

if possible against the information provided in Table B.9. 

Expected Outcome – If the reported data matches the information provided in Table B.8 then this 

will be deemed a “Pass”, else the CPE modem will be deemed to have failed the test. 

R.VDSL2.17 Correct Reporting of Key Test and Diagnostic Parameters 

Description – The CPE modem shall support the correct reporting of key VDSL2 test and 

diagnostic parameters according to G.997.1[10]. These parameters are shown in Table B.10. 


34 


Equipment Metric Name (/G.997.1) 

xTU-R Vendor ID, xTU-R G.994.1 Vendor ID 7.4.2/G.997.1 

xTU-R system vendor ID, 7.4.4/G.997.1 

xTU-R version number, 7.4.6/G.997.1 

xTU-R serial number, 7.4.8/G.997.1 

FEC seconds-line far end (downstream), FECS-LFE (7.2.1.2.1/G.997.1) 

Errored second-line far end (downstream), ES-LFE (7.2.1.2.2/G.997.1) 

Severely errored second-line far end (downstream), SES-LFE (7.2.1.2.3/G.997.1) 

Upstream line attenuation, LATNus 7.5.1.10/G.997.1 

Downstream line attenuation, LATNds 7.5.1.9/G.997.1 

Upstream signal-to-noise (SNR) ratio margin, SNRMus 7.5.1.16/G.997.1 

Downstream signal-to-noise ratio margin, SNRMds 7.5.1.13/G.997.1 

Upstream data rate 

Downstream data rate 

Upstream maximum attainable data rate, ATTNDRus 7.5.1.20/G.997.1 

Downstream maximum attainable data rate, ATTNDRds 7.5.1.19/G.997.1 

Upstream traffic count 

Downstream traffic count 

Upstream Actual Aggregate Transmit Power, ACTATPus 7.5.1.25/G.997.1 

INMINPEQ downstream, 7.2.1.5.1/G.997.1-200711-Amd2 

INMIIAT Downstream, 7.2.1.5.3/G.997.1-200711-Amd2 

INMME downstream, 7.2.1.5.3/G.997.1-200711-Amd2 

Actual INP Upstream, ACTINP 7.5.2.4/G.997.1 

Actual INP Downstream, ACTINP 7.5.2.4/G.997.1 

Downstream H(f) logarithmic subcarrier group size, HLOGGds 7.5.1.26.5/G.997.1 

Downstream H(f) logarithmic representation, HLOGpsds 7.5.1.26.6/G.997.1 

Downstream QLN(f) subcarrier group size, QLNGds 7.5.1.27.2/G.997.1 

Downstream QLN(f) , QLNpsds 7.5.1.27.3/G.997.1 

Downstream SNR(f) subcarrier group size, SNRGds 7.5.1.28.2/G.997.1 

Downstream SNR(f), SNRpsds 7.5.1.28.3/G.997.1 

Downstream bits allocation, BITSpsds 7.5.1.29.1/G.997.1 

Forward error correction – Channel far-end, FEC-CFE 7.2.2.2.2/G.997.1 

Table B.10 : Key Test and Diagnostic Parameters (taken from G.997.1[10]) 


35 


Test Procedure – 

AWG 


Injector 

DSLAM 


CPE 

PC 

PC 

Figure.B.7 : Test Configuration for Checking Parameters 

1. Configure the DSLAM to implement a CAL value of 30dB and the default band profile. 

2. Connect the CPE modem to the DSLAM using the Test Configuration shown in Figure B.7. 

3. Set the line simulator to a loop length of 500m of TP-100 cable with no crosstalk injected at 

either end of the system. 

4. Ensure that the CPE modem has attained synchronisation and then leave the system 

running for 20 minutes. 

5. Capture the 15 minute performance data from the element manager and check that the 

key parameters are reported. 

6. Now turn the crosstalk noise on at each end of system and repeat the test. 


8. Check that the reported data rate, maximum attainable line rate and noise margin have 


9. Configure the noise generator to inject a 5ms micro-interrupt onto the CPE end of the link 

every 10 seconds. 

10. The 15 minute data should now show a number of errored seconds (~90), severely errored 

seconds and/or FEC seconds. 


comprising 100μs bursts every 10ms at an amplitude of -110dBm/Hz (measured at 1MHz). 

12. The 15 minute data should now show a number of errored seconds (ES), severely errored 

seconds (SES) and/or forward error correction (FEC) seconds. The individual error counts 

should NOT exceed 900 for any given 15 minute period. If no SES are observed, the 

amplitude of the signal should be increased until SES are observed. Note that depending 

on the equipment used, the system may retrain during this test – this behaviour is 

expected. 

13. Configure the DSLAM with an interleaved profile ( sfaD440_220_08_03U150_075_08_04) 

and repeat Steps 9 through 12. 

14. The 15 minute data should now report interleaver settings (INPmin and Dmax) for each 

direction in addition to errored second (ES), severely errored seconds (SES) and.or FEC 

seconds. 

Expected Outcome – If the reported data matches the information provided in Table B.10 then this 

will be deemed a “Pass”, else the CPE will be deemed to have failed the test. 


36 


B.1.2.8.3 Ethernet, WAN and OAM 

NOTE : Additional Test requirements are for further study. 

R.VDSL2.18 R.OAM.4 Support of “Dying gasp” 

Description – The Modem should support “dying gasp” as defined in Section 11.3.3.2 of G.993.2 

[3] and Section 7.1.1.2.3 of G.997.1 [10]. 

Note: “Dying gasp” is not a mandatory requirement in SIN 498 but CPE providers are encouraged 

to implement this in their modems as it will enable the Openreach Test & Diagnostic systems to 

differentiate between a modem being turned off by the end user (loss of power) or a loss of signal 

(loss of connectivity) caused by a potential network or home wiring issue. This will support CPE 

providers in their diagnostic approach to ensure that their End Users have checked relevant setup 

prior to submitting a fault to Openreach and thus ensure the correct cause of action and avoiding 

an unnecessary cost due to potential chargeable visits due to End User issues. 

Test procedure – 


Injector 

DSLAM 


NTE5 + 

iSSFP 

CPE 

PC 

PC 

Figure B.8 : Test Configuration for verifying “Dying Gasp” 

1) Configure DSLAM to implement an ESEL value of 30dB and configure a port with the 


2) Connect the DSLAM and the CPE using the Test Configuration shown in Figure B.8. 

3) Set line simulator to simulate a loop length of 100m with noise injection disabled (i.e. 

noise free). 

4) Once the CPE has attained synchronisation, verify that no additional alarms have been 

raised on the EMS. 

5) Disconnect the plug from the power socket on the CPE. The modem should now power 

off. 

6) Check and record the EMS alarm messages. 

7) Replace power plug in socket and allow modem to resynchronise. 

8) Repeat steps 5 and 6 but this time switch off the power at the mains socket (or 

disconnect PSU from socket). 

9) Check and record the EMS alarm messages. 


37 


10) Repeat steps 3 to 9 for a loop length of 1000m of TP-100. 

Expected Outcome – If “dying gasp is supported, the alarm message will show “Loss of Power”. If 

“dying gasp” is not supported, the EMS alarm will show “Loss of Frame or Loss of Sync”. 

B.1.2.9 NGA testing 

B.1.2.9.1 Transmission Performance Testing 

In addition to the SIN 498 tests defined above, the transmission performance of the CPE modem 

will also be measured against the current Live NGA reference models. This will involve the modem 

performance being evaluated with the DSLAM configured to implement both fast and interleaved 

profiles. These follow the generic syntax shown in Table B.11 . 

sfaDAAA_BBB_CC_DDUEEE_FFF_GG_HH 

Parameter Downstream Setting Upstream Setting 

Maximum Data Rate AAA/10 Mbit/s EEE/10 Mbit/s 

Minimum Data Rate BBB/10 Mbit/s FFF/10 Mbit/s 

Minimum Noise Margin 0dB 0dB 

Target Noise Margin 6dB 6dB 

Maximum Noise Margin 31dB 31dB 

Dmax CC ms GG ms 

INP min DD symbols HH symbols 

Adaption Mode Adapt at start up Adapt at start up 

Operating Mode 

G.993.2 

Band Plan 998ADE17 (Plan B8-11) [3]]. 

Table B.11 : Generic NGA Profile Syntax 

Deployment Scenario 1 : SSFP with no home wiring 

Description – This test gives an indication of how a CPE modem would perform if connected to the 

Openreach NGA network as part of a SSFP based deployment (i.e. no home wiring). It is also 

used to record a bench-mark of the CPE modem’s performance against the current (i.e. LIVE) 

network firmware which can then be used to check whether the transmission performance of the 

CPE modem is adversely affected by future network upgrades. Testing should be performed using 

both FAST and INTERLEAVED operation. 

Test Description (FAST) – 

1) Configure the DSLAM to implement an ESEL value of 30dB and the default band 

profile. 

2) Connect the CPE modem to the DSLAM using the test setup shown in Figure B.9. 

3) Set the line simulator to a loop length of 200m of TP-100 cable with the appropriate 

crosstalk injected at each end of the system. 


38 


4) Record time taken for the CPE to attained synchronisation. This shall be

39 


CAL value Length Interleaved Profile 

200m 

sfaD490_250_08_03U200_100_08_04 

500m 

sfaD440_220_08_03U150_075_08_04 

10dB 

1000m 

1500m 

sfaD250_125_08_03U060_030_08_04 

sfaD165_082_08_03U023_011_08_04 

2000m 

sfaD100_050_08_03U013_005_08_04 

2500m 

sfaD047_023_08_03U013_005_08_04 

200m 

sfaD440_220_08_03U200_100_08_04 

500m 

sfaD440_220_08_03U150_075_08_04 

30dB 

1000m 

1500m 

sfaD224_112_08_03U060_030_08_04 

sfaD150_075_08_03U023_011_08_04 

2000m 

sfaD100_050_08_03U013_005_08_04 

2500m 

sfaD034_017_08_03U013_005_08_04 

200m 

sfaD490_250_08_03U200_100_08_04 

500m 

sfaD440_220_08_03U150_075_08_04 

50dB 

1000m 

1500m 

sfaD250_125_08_03U050_025_08_04 

sfaD180_090_08_03U023_011_08_04 

2000m 

sfaD131_065_08_03U013_005_08_04 

2500m 

sfaD079_039_08_03U013_005_08_04 

Table B.12 : Banded Profiles for Interleaved Testing 

Expected Outcome – This test will provide an indication on how the CPE modem performs when 

connected to the current Openreach NGA network for both fast and interleaved operation. 


40 


Deployment Scenario 2 : Microfilter with home wiring 

Description – This test gives an indication of how a CPE modem would perform if connected to the 

Openreach NGA network as part of a microfilter based deployment (i.e. with home wiring). 

Comparing the results against those obtained from the previous deployment scenario will give an 

indication on how the CPE performance is affected by bridged taps caused by telephony 

extensions in the customer’s premise. In this configuration, the three lengths of cable (7m, 12m 

and 20m) connected to the NTE5 (the demarcation point in the customer’s premise where the 

Openreach network terminates) are representative of telephony wiring extensions and are 

specifically chosen to introduce notches in the VDSL downstream and upstream frequency bands. 

Testing should be performed using both FAST and INTERLEAVED operation. 

Test Description (FAST) – 


2) Connect the CPE modem to the DSLAM using the test setup shown in Figure B.10. 

3) Set the line simulator to a loop length of 200m of TP-100 cable with the appropriate 

crosstalk injected at each end of the system. 

4) Record time taken for the CPE to attained synchronisation. This shall be

41 


Expected Outcome – This test will provide an indication on how the CPE modem performs when 

connected to the current Openreach NGA network for both fast and interleaved operation. 

B.1.2.9.2.Verification of Hlog and QLN (T2R Capability) 

SSFP with no home wiring – Test of Hlog/QLN accuracy (GENERIC) 

Description – This test is defined to test whether a CPE modem interworks with the DSLAMs 

sufficiently well to report Hlog and QLN data back to the DSLAM. This data is used for test and 

diagnostic purposes to reduce time to repair (T2R). 

Test Procedure – Configure the noise generator to add AWGN at each end of the simulated loop. 

Connect the CPE modem to a port on the DSLAM via a length of simulated 0.5mm gauge cable 

and ensure that it trains up and reaches synchronisation. Allow one minute to pass, for Hlog/QLN 

data to be transferred from CPE modem to DSLAM. Record Hlog and QLN data from the DSLAM 

element manager. 


Injector 

DSLAM 


NTE5 + 

iSSFP 

CPE 

PC 

PC 

Figure B.11 : Test Configuration for Checking Hlog/QLN Functionality (SSFP with no home 

wiring) 

1) Configure DSLAM to implement an ESEL value of 0dB and ensure that the default 

band profile is loaded onto a port. A fully rate adaptive, open profile without FEC 

should be used. 

2) Set line simulator to the loop length with closest loss (referred to 100 Ohm interfaces) 

to the loss shown in the table below (AWGN disabled during this measurement). Note 

that the loss is measured t either 1MHz or 6MHz depending on the cable length. 

3) Enable AWGN generation at the CPE end of the loop using the noise level defined in 

Table B.13. 

4) Connect the CPE modem to that port and check that it has attained synchronisation. 

5) Allow one minute to pass after the link has reached synchronisation for the CPE Hlog 

and QLN data to be transferred back to the DSLAM. 

6) Collect the Hlog and QLN data from the DSLAM element manager. 

7) Repeat Steps 2 to 6 for each of the test cases shown in in the table below 


42 



case 

Loop Length 

/m (0.5mm) 

Loss at 

1 MHz / dB 

Loss at 

6 MHz / dB 

AWGN PSD 

/ dBm/Hz 

1 200 N/A 9.36 -100 

2 500 N/A 23.41 -110 

3 1000 N/A 46.81 -120 

4 2000 36.07 N/A -130 

Table B.13 : AWGN Settings for Hlog/QLN Verification (SSFP with no home wiring) 

Expected Outcome – This test will be deemed a “Pass” if all of the following conditions are 

satisfied: 

The Hlog data is recorded over all of the available upstream and downstream bands (ie no 

gaps appear in the reported data). 

The Hlog data recorded for both upstream and downstream is within 1.5 dB of the model for 

a loop of the stated loss, for all frequencies where the received PSD is at least 10 dB above 

the noise PSD injected. 

The QLN data is within 2dB of the AWGN PSD specified in the test, in the downstream 

bands only. 

Accompanying template spreadsheets [21], [22] are provided to assist with this evaluation. 

Microfilter With Home Wiring – Qualitative Test of Hlog/QLN reporting 

Description – This test is defined to test whether a CPE modem interworks with the DSLAMs 

sufficiently well to report Hlog and QLN back to the DSLAM in a deployment scenario using microfilters 

and home wiring. This data is used for test and diagnostic purposes to reduce time to repair. 

The presence of the extension wiring in this case should cause deep nulls to appear in the Hlog 

data. 

Test Procedure – Configure the noise generator to add AWGN at -110 dBm/Hz at the CPE end of 

the simulated loop. Connect the CPE modem to a port on the DSLAM via a 500m length of 

simulated 0.5mm gauge cable and a home network as shown in the diagram below. Ensure that 

the CPE trains up and reaches synchronisation. Allow one minute to pass for Hlog/QLN data to be 

transferred from CPE to DSLAM. Record Hlog/QLN data from the DSLAM element manager. 


43 



Injector 

20m 

uF 

DSLAM 


NTE5 

7m 

uF 

CPE 

12m 

PC 

PC 

uF 

uF 

Internal wiring (e.g. CW1308) 

Micro-filter + extension socket 

Figure B.12 : Test Configuration for Checking Hlog/QLN Functionality (Microfilter with home 

wiring) 


case 

Loop Length 

/m (TP-100) 

Loss at 

6 MHz / dB 

AWGN PSD 

/ dBm/Hz 

1 500 23.41 -110 

Table B.14 : AWGN Settings for Hlog/QLN Verification (Microfilter with home wiring) 

Expected Outcome – This test will be deemed a “Pass” if the deep nulls are present in the Hlog 

data at roughly the expected frequencies and with roughly the expected depth and that Hlog data 

is recorded over all of the available upstream and downstream bands (ie no gaps appear in the 

reported data) and that the QLN data is aligned with the PSD template specified, in the 

downstream bands only 

Note that getting an exact match is not necessary for this test, due to the practical difficulty in 

getting the ‘Q’ and the resonant frequency of the extension wiring exactly in alignment with the 

simulated network. 

The 500m templates contained in [21] and [22] allow comparison of the Hlog and QLN data 

captured against the expected result. 

B.1.2.9.3 Verification of “Router Only” Functionality 

Description – This test is defined to test whether a CPE modem can achieve end-to-endconnectivity 

with an external server when connected directly to the Ethernet UNI on the Openreach 

modem i.e. when operating in “Router Only” mode. 

Test Procedure – Connect the Openreach modem to a port on the DSLAM via a 100m length of 

simulated 0.5mm gauge cable and ensure that it trains up and reaches synchronisation. Connect 


44 


the CPE modem to the Ethernet port on the Openreach modem and attempt to establish a 

connection with the remote server. 

Server 

BRAS 

DSLAM 


Openreach 

Modem 

CPE 

PC 

EMS PC 

PC 

Figure B.13 : Test Configuration for Checking “Router Only” Functionality 

1) Configure the DSLAM to implement an ESEL value of 30dB and ensure that the default 

band profile is loaded onto a port. 

2) Set the line simulator to a loop length of 100m with noise injection disabled (i.e. noise 

free). 

3) Connect the Openreach modem to that port and check that it has attained 

synchronisation. 

4) Connect the CPE modem to the Ethernet UNI on the Openreach modem. Following this, 

attempt to set up an end-to-end connection between a PC connected to the CPE and an 

external server. 

5) Check that end-to-end connectivity has been achieved by launching an Internet session 

using the PC connected to the CPE modem. This will confirm whether the modem has 

established a DHCP or PPP session with the server. 

Expected Outcome – This test will be deemed a “Pass” if the CPE modem can achieve an end to 

end connection with the external server through the Openreach modem, else the test will be 

deemed a “Fail”. 

B.1.3 Details of Impedance matching network 

In order to measure the transmit power spectral density (PSD) of the VDSL2 system under test an 

impedance matching network is needed to correct the impedance of the simulated loop to as close 

as possible to the 100 Ohm reference impedance. Such a matching network is shown in Figure 

B.14 below. 


45 


Figure B.14 : VDSL2 PSD matching pad and balun tap 

The output of the balun tap for this matching network has a loss from the device under test of 

20.7 dB, and in addition a further 0.4dB loss must be allowed for the balun. The loss of this path 

must be taken into account when calculating the PSD. 

B.1.4 Reference DSLAMs 

Currently Openreach uses network equipment from two strategic suppliers (namely ECI and 

Huawei) in its UK FTTC NGA network. Any CP provided VDSL2 modem must be able to operate 

across the following DSLAM chassis types and line cards: 

Vendor DSLAM Chassis Line Card 

ECI 

Huawei 

M41 

M41 

MA5603T 

MA5616T 

MA5616T 

V2 (64-port) 

V3 (64-port) 

VDMF (48-port) 

VDSH (24-port) 

VDLF (32-port) 

Table B.15: Openreach NGA Reference DSLAMs 

For the Openreach ANO, VDSL2 modem testing according to ND1436 shall be performed using 

the above NGA reference models at the current live build level. 


46 


Annex C (normative): 

MPF Provider Specific Requirements 

C.1 Openreach 

C.1.1 Handshake 

Compliance shall be determined by the following test . 

Carrier Set Designation 

Upstream Carrier Sets 

Tone 

Numbers 

Maximum 

power 

level/carrier 

(dBm) 

Downstream Carrier Sets 

Tone 

Numbers 

Maximum 

power 

level/carrier 

(dBm) 

A43 9 17 25 -1.65 40 56 64 -3.65 

A43c 9 17 25 -1.65 257 293 337 -3.65 

Table C.1 : Carrier Sets A43 and A43c 

Note that the use of additional tone-sets (B43, B43c, V43 etc.) is not permitted as these may cause 

the spectral limits defined in Parts B and C of the BT ANFP [6] to be breached. 

Power Meter 

Baluns 

Spectrum 

Analyser 

PC 

DSLAM 

Match 

Pad 


CPE 

PC 

PC 

Figure C.1 : Test Configuration for Measuring Downstream PSD 

Test Procedure – The Test Configuration shown in Figure C.1 shall be used for this test. 

1) Set the spectrum analyser for a start frequency of 10kHz and a stop frequency of 5MHz. 




47 


3) Connect the CPE to DSLAM using the Test Configuration shown in Figure C.1. 



5) During train-up, capture the handshake tones generated by each end of the transmission 

system. 

6) Compare tones against those defined for A43 and A43c. 

7) Plot the captured downstream tones against the BT ANFP [6] Part B spectral limit to check 

that PSD shaping has been applied to the tones and that tones other than A43/A43c are NOT 

being used. 


Expected Outcome – This test will be deemed a “Pass” only if A43/A43c tone sets are being used 

and that the correct amount of downstream PSD shaping is being applied to the tone to ensure 

compliance with the appropriate limit masks defined in Part B of the UK ANFP [6] for each value of 

ESEL evaluated. If these criteria are not met, then the result is a “Fail”. 

C.1.2 ANFP 

Description – The CPE modem shall comply with the requirements of Part C of the BT Access 

Network Frequency Plan [6]. This applies to all operating modes, operating states and profiles 

required by the ANO. 

Test Procedure – Measure downstream PSD on three different line lengths (100m, 500m and 

1300m) to check that system complies with Part C of the BT ANFP [6] and that upstream transmit 

power does not exceed that defined for Profile 17a. 

Power Meter 

B 

Spectrum 

Analyser 

PC 

DSLAM 


Match 

Pad 

CPE 

PC 

PC 

Figure C.2 : Test Configuration for Measuring Upstream PSD 

Details of the impedance matching pad used are contained in Annex A. 

1) Configure the DSLAM to implement an ESEL value of 30dB and the default band profile. 

2) Connect the CPE to the DSLAM using the Test Configuration shown in Figure C.2. 


48 




4) Ensure that the CPE has attained synchronisation. 

5) Capture the upstream PSD and wideband power and compare against Part C of the BT 

ANFP [6]. 

6) Repeat for 500m and 1300m loop lengths. 

Note : the KL0 value of each loop length (required to establish the appropriate mask in Part C of 

the ANFP) shall be established by measuring the insertion loss of each loop at 1MHz. 

Expected Outcome – If the upstream transmit spectrum complies with the spectrum limits defined 

in Part C of the BT ANFP [6] over the various loop lengths tested and the upstream transmit power 

does not exceed 14.5dBm then this will be deemed a “Pass”, else the result will be a “Fail”. 

C.1.3 AELEM 

Description – The CPE modem shall support the alternate electrical length estimation methodology 

(AELEM) for estimating the electrical length of the connection between the CPE modem and the 

DSLAM (mode ELE-M1) as defined in G.993.2 [3]. 

Test Procedure – AELEM is not currently supported on the BT NGA platform therefore it not 

possible to perform this testing on Live build level network elements. However, an indication of 

how well a CPE modem estimates loop length in the presence of bridged taps caused by internal 

wiring in a self-install scenario can be obtained using the following test procedure. 

Test Description – 


2) Connect the CPE modem to the DSLAM using the test setup shown in Figure C.3 

3) Set the line simulator to a loop length of 500m of TP-100 cable with the appropriate crosstalk 

injected at each end of the system. This equates to a kl0 value of ~10dB measured at 1MHz. 

4) Ensure that the CPE has attained synchronisation. 

7) Wait 2 minutes for the system to stabilise and then record reported kl0 values for each band 

(DS1, DS2, DS3, U1, U2 etc.) from EMS. 

8) Capture the upstream transmit PSD spectrum. 

9) Compare the PSD against the BT ANFP [6] Part C PSD mask for the kl0 value of 10dB. 

10) Compare the reported kl0 values for each band with the ranges defined in Table C.2. 

11) Repeat this for a 100m loop (kl0 ~ 2dB @ 1MHz). 


49 


PC 

Spectrum 

Analyser 

uF 


Injector 

B 

20m 

DSLAM 


Match 

Pad 

NTE5 

7m 

uF 

CPE 

12m 

PC 

PC 

uF 

uF 

Internal wiring (e.g. CW1308) 

Micro-filter + extension socket 

Figure C.3 : Test Configuration for Measuring Transmission Performance (Self-Install) 

Frequency Band 

Estimated kl0 for 100m 

(dB @ 1MHz) 

Estimated kl0 for 500m 

(dB @ 1MHz) 

DS1 (138kHz to 3.75MHz) 2 - 2.5 9 - 10 

US1 (3.75 to 5.2MHz) 2 - 2.5 9 - 10 

DS2 (5.2 to 8.5MHz) 2 - 2.5 9 - 10 

US2 (8.5 to 12MHz) 2 - 2.5 9 - 10 

DS3 (12 to 17MHz) 2 - 2.5 9 - 10 

Table C.2 : Estimated kl0 Values for Band Plan 998ADE17 

Expected Outcome – If AELEM is implemented correctly, then the BT ANFP [6] mask shall not be 

violated and the reported kl0 values for each band should not exceed the limits defined in Table 

C.2. 


50 


History 

Document history 

Version Date Milestone 

1.1.1 27 th August 2013 Initial publication 

1.1.2 23rd September 2013 Editorial correction of auto reference and typographical errors.

âWires-onlyâ VDSL2 Modem Test Plan - NICC

Create successful ePaper yourself

Delete template?

Save as template?

âWires-onlyâ VDSL2 Modem Test Plan - NICC