The test plans on this page may be downloaded and used for internal purposes only. The test plans may not be commercialized in any way without express permission of the UNH-IOL.
The Gfast testing service currently offers the following test plans. These documents are constantly being updated to improve readability and to reflect the current specifications. Please contact us if you would like more information or have questions about the Gfast testing service.
When testing based on the following test plans is performed, all reports generated will be digitally signed using an Adobe digital certificate. Upon reception of the report, the recipient can verify its authenticity using our document validation instructions.
Broadband Forum
Certification
- Status
- Fully Documented (Active)
- Revision
- Issue 3
- Testing Days Needed
- 3 days
- Last Modified
- 2021-02-23
- Abstract
This Broadband Forum Test Plan, TP-337, provides a set of functional, stability, and basic performance test cases and related pass/fail requirements for G.fast implementations according to ITU-T Recommendations G.9700 [1] and G.9701 [2].
The primary goal of TP-337 is to provide a set of test cases and framework to verify interoperability between a G.fast Transceiver Unit at the Optical Network Unit (FTU-O) (e.g., a Distribution Point Unit [DPU]) and one or more FTU at the Remote site (FTU-Rs) (e.g., Customer Premise Equipments [CPEs]).
TP-337 serves as the test plan, including pass/fail requirements for each test case, for the Broadband Forum G.fast Certification Program. Technical content in this test plan includes test setup information, equipment configuration requirements, test procedures, and pass/fail requirements for each test case.
For additional details about the G.fast Certification Program, including requirements for participation in the program or to view the list of currently certified devices, , please refer to: Gfast Interoperability and Certification Testing.
Issue 3 of the test plan adds additional test cases for iDTA, cDTA, and SHINE Type 4 noise.
- Notes
- Note, the test time refers to the duration of testing for one combination of CPE and DPU.
- Status
- Fully Documented (Active)
- Revision
- Issue 2
- Testing Days Needed
- 2 days
- Last Modified
- 2019-03-21
- Abstract
- IR-337 Issue 2 provides a set of functional, stability, and basic performance test cases and related pass/fail requirements for Gfast implementations according to ITU-T Recommendations G.9700 and G.9701. Test cases include requirements for vectoring, where applicable. Issue 2 specifically adds test requirements for the 212 MHz profiles, as well as support for the coax use case.
The primary goal of IR-337 is to provide a set of test cases and framework to verify interoperability between an FTU-O (e.g., a DPU or a DP-side Reference Design) and one or more FTU-Rs (e.g. CPEs or CP-side Reference Designs). The test cases are defined for a Device Under Test (DUT – either a DPU or CPE), tested against a Link Partner (either a CPE or DPU respectively). The DPU/CPE may be a reference design, however containing the necessary FTU-O/R and system functionality to execute this test plan (see e.g., section 4.2).
Issue 2 of IR-337 serves as the test plan, including pass/fail requirements for each test case, for the Broadband Forum Gfast Certification Program. Additional documentation is available from the Broadband Forum about the Gfast Certification Program, including program benefits, participation requirements, number and type of equipment to be tested against, and logo usage guidelines. For additional details about the Broadband Forum’s certification programs, please refer to: Gfast Interoperability and Certification Testing.
- Notes
- Note, the test time refers to the duration of testing for one combination of CPE and DPU.
- Status
- Fully Documented (Active)
- Revision
- Issue 1
- Testing Days Needed
- 2 days
- Last Modified
- 2017-06-13
- Abstract
- IR-337 provides a set of functional, stability, and basic performance test cases and related pass/fail requirements for Gfast implementations according to ITU-T Recommendations G.9700 and G.9701. Test cases include requirements for vectoring, where applicable.
The primary goal of IR-337 is to provide a set of test cases and framework to verify interoperability between an FTU-O (e.g., a DPU or a DP-side Reference Design) and one or more FTU-Rs (e.g. CPEs or CP-side Reference Designs). The test cases are defined for a Device Under Test (DUT – either a DPU or CPE), tested against a Link Partner (either a CPE or DPU respectively). The DPU/CPE may be a reference design, however containing the necessary FTU-O/R and system functionality to execute this test plan (see e.g., section 4.2).
Issue 1 of IR-337 serves as the test plan, including pass/fail requirements for each test case, for the Broadband Forum Gfast Certification Program. Additional documentation is available from the Broadband Forum about the Gfast Certification Program, including program benefits, participation requirements, number and type of equipment to be tested against, and logo usage guidelines. For additional details about the Broadband Forum’s certification programs, please refer to: Gfast Interoperability and Certification Testing.
- Notes
- Note, the test time refers to the duration of testing for one combination of CPE and DPU.
Conformance
- Status
- Fully Documented (Partially Implemented)
- Revision
- 2.0
- Testing Days Needed
- 10 days
- Last Modified
- 2010-01-04
- Abstract
- This test plan facilitates VDSL2 over POTS and ISDN functional testing. This test plan embodies operators' definitions of VDSL2 interoperability (between one DSLAM and one CPE at a time). The test plan focuses on physical layer testing, and also validation and verification of selected higher layer functionality. It does not replace operators' pre-deployment testing.
- Notes
- Implemented tests from this test suite
- Status
- Fully Documented (Active)
- Revision
- Issue 1
- Testing Days Needed
- 10 days
- Last Modified
- 2010-04-01
- Abstract
- This test plan facilitates ADSL2/2plus over POTS and ISDN functional testing. This test plan embodies operators' definitions of ADSL2/2plus interoperability (between one DSLAM and one CPE at a time). The test plan focuses on physical layer testing, and also validation and verification of selected higher layer functionality. It does not replace operators' pre-deployment testing.
Interoperability
- Status
- Fully Documented (Partially Implemented)
- Revision
- 1.0
- Testing Days Needed
- 1 day
- Last Modified
- 2005-03-16
- Abstract
- TR-067 is the ADSL Interoperability Test Plan designed by the Broadband Forum. The DSL Consortium can perform sections of this test and generate reports based on this Technical Report.
- Notes
- A.2.1
A.2.3.1
A.2.3.2
A.2.4.1 Fixed 832/192
A.2.4.1 Fixed 1504/320
A.2.4.1 Fixed 4832/640
- Status
- Fully Documented (Partially Implemented)
- Revision
- 1.0
- Testing Days Needed
- 1 day
- Last Modified
- 2005-03-16
- Abstract
- TR-067 is the ADSL Interoperability Test Plan designed by the Broadband Forum. The DSL Consortium can perform sections of this test and generate reports based on this Technical Report.
- Status
- Fully Documented (Partially Implemented)
- Revision
- 1.0
- Testing Days Needed
- 1 day
- Last Modified
- 2005-03-16
- Abstract
- TR-067 is the ADSL Interoperability Test Plan designed by the Broadband Forum. The DSL Consortium can perform sections of this test and generate reports based on this Technical Report.
- Status
- Fully Documented (Partially Implemented)
- Revision
- 2.0
- Testing Days Needed
- 1 day
- Last Modified
- 2007-03-30
- Abstract
- TR-100 is the ADSL Interoperability Test Plan designed by the Broadband Forum updated to specifically test ADSL2 and ADSL2+. The DSL Consortium can perform sections of this test and generate reports based on this Technical Report.
- Notes
- A.2.2.1
A.2.2.2
A.2.2.5
A.2.2.6 Class A
A.2.2.6 Class B
A.2.3.1
A.2.3.2
A.2.3.3
A.2.3.4
A.2.5.1
A.2.5.2
A.2.5.3
A.2.5.4
A.2.6.1
A.2.6.2
A.2.7.1
A.2.7.2
- Status
- Fully Documented (Partially Implemented)
- Revision
- 2.0
- Testing Days Needed
- 1 day
- Last Modified
- 2007-03-30
- Abstract
- TR-100 is the ADSL Interoperability Test Plan designed by the Broadband Forum updated to specifically test ADSL2 and ADSL2+. The DSL Consortium can perform sections of this test and generate reports based on this Technical Report.
- Status
- Fully Documented (Partially Implemented)
- Revision
- 2.0
- Testing Days Needed
- 1 day
- Last Modified
- 2007-03-30
- Abstract
- TR-100 is the ADSL Interoperability Test Plan designed by the Broadband Forum updated to specifically test ADSL2 and ADSL2+. The DSL Consortium can perform sections of this test and generate reports based on this Technical Report.
- Status
- Fully Documented (Active, see notes)
- Revision
- 2.0
- Testing Days Needed
- 1 day
- Last Modified
- 2012-11-29
- Abstract
- TR-100 is the ADSL Interoperability Test Plan designed by the Broadband Forum updated to specifically test ADSL2 and ADSL2+.
The DSL Consortium can perform sections of this test and generate reports based on this Technical Report.
- Notes
- Use this test selection to request testing of TR-100 Issue 2 Annex J, Sections J.5.1 through J.5.2.
- Status
- Fully Documented (Active)
- Revision
- 2.0
- Testing Days Needed
- 1 days
- Last Modified
- 2012-11-01
- Abstract
- Interoperability performance test cases for VDSL2 DSLAM and CPE products operating in Annex A mode.
- Status
- Fully Documented (Active)
- Revision
- 2.0
- Testing Days Needed
- 1 days
- Last Modified
- 2012-11-01
- Abstract
- Interoperability performance test cases for VDSL2 DSLAM and CPE products operating in Annex B mode.
- Status
- Fully Documented (Active)
- Revision
- Issue 1
- Testing Days Needed
- 10 days
- Last Modified
- 2014-09-19
- Abstract
- This Technical Report is intended to provide an interoperability test plan for ITU-T Recommendation G.993.5 titled "Self-FEXT cancellation (vectoring) for use with VDSL2 transceivers." Deployment scenarios in the scope of this technical report include deployments from the Central Office (CO) and Fiber-to-the-x (FTTx) remote deployments.
The scope of this Technical Report also covers validation of the functionality of the Control, Inventory, and Reported parameters defined in G.997.1 for the G.993.5.
Testing includes requirements and updates according to TR-249 Amendment 1.
- Status
- Fully Documented (Active)
- Revision
- 1.0
- Testing Days Needed
- 5 days
- Last Modified
- 2012-06-25
- Abstract
- TR-273 provides testing methodology of multiport xDSL systems which use pair bonding protocols, such as ITU G.998.1 (ATM), G.998.2 (Ethernet), and G.998.3 (TDM),. The bonded lines may include DSLs specified by ITU-T Recommendations G.992.1 (ADSL), G.992.3 (ADSL2), G.992.5 (ADSL2plus), G.993.2 (VDSL2), and G.991.2 (SHDSL).
Performance
- Status
- Fully Documented (Active)
- Revision
- 1.0
- Testing Days Needed
- 1 days
- Last Modified
- 2020-01-31
- Abstract
- Interoperability performance test cases for VDSL2 DSLAM and CPE products operating in Annex Q (35b) mode.
IOL
Certification
- Status
- Fully Documented (Active)
- Revision
- R10
- Testing Days Needed
- 5 days
- Last Modified
- 2014-02-04
- Abstract
- Testing of a DSL CPE device to meet the requirements of the Calix Compatible Program (https://portal.calix.com/portal/calix_compatible/). Test requirements include ADSL2+, VDSL2, single, and bonded-line performance, including Layer-2 traffic testing. For access to the formal test plan, please contact dslinterop@calix.com.
- Notes
- Test time is per combination of 1 CPE tested against 1 Calix DSLAM platform.
Interoperability
- Status
- Fully Documented (Active)
- Revision
- 1.20
- Testing Days Needed
- 2 days per DSLAM/CPE
- Last Modified
- 2008-03-24
- Abstract
- This test suite describes testing procedures that demonstrate basic connectivity and stability of the DUT in a VDSL2 system. The individual test cases determine the net data rate at which the DUT initializes with a specific VTU-R or VTU-O on various North American test loops in the presence of injected crosstalk. This test suite is valid for both single pair VDSL2 systems. For most VTU-Os, this test is automated via LASI.
- Status
- Fully Documented (Active)
- Revision
- 3.4.0
- Testing Days Needed
- 1 day per DSLAM/CPE
- Last Modified
- 2007-03-21
- Abstract
- This test suite describes testing procedures that demonstrate basic connectivity and stability of the DUT in an ADSL system. The individual test cases determine the net data rate at which the DUT initializes with a specific ATU-R or ATU-C on various North American and ETSI test loops in the presence of injected crosstalk. This test suite is valid for both single pair ADSL systems and multi-pair bonded ADSL systems.
- Notes
- A sample report for a multi-pair bonded ADSL system can be downloaded here . For most ATU-Cs, this test is automated via LASI.
- Status
- Fully Documented (Partially Implemented)
- Revision
- 2.0.0
- Testing Days Needed
- 1.5 days
- Last Modified
- 2006-08-14
- Abstract
- This test suite verifies the on-line reconfiguration capabilities of a DSL system. Presently the test suite offers a means to verify ADSL2 seamless rate adaptation (SRA) through the generation and injection of a varying white noise floor. The test suite also offers a means to verify ADSL bit swapping (BS) through the injection of specific interfering tones. A means to test dynamic rate repartitioning (DRR) is currently being investigated.
Key