1

April 2018

Process Guide for CPEe Modem Conformance Testing (VDSL) Issue 2.0

2

Contents

4

Overview

Introduction

Participants of MCT

5

6

MCT Exemption Process Flow

MCT Process Flow

7

11

12

MCT Gatekeeper Testing

MCT Gatekeeper Test Process Flow

Standby List

13

16

Openreach Network Regression Testing 17

MCT between Regression and Deployment 18

3

Contents

20

Formwise Submission

Frequently Asked Questions

Device Submission

20

21

Gatekeeper Tests

Testing & Updates

22

23

24

References

General Queries

Glossary of Terms

26

27

4

It is the responsibility of each CP to provide a MCT approved VDSL Modem/Router device to end users. If you are a new customer you will need to identify the device you will be using to support the launch of your GEA-FTTC product. You will do this as part of the registration and set up phases of Customer Establishment process. You have 2 options when selecting a device to use: 1. Select a device that has already passed Modem Conformance Testing. 2. Select a new device and request a slot for Modem Conformance Testing. For a new device you will need to complete Modem Conformance Testing (MCT) to ensure the device conforms to the mandatory requirements of BT SIN 498.

Introduction to MCT Modem Conformance Testing

5

The key objectives of Modem Conformance Testing (MCT) are: • To help ensure that devices connecting to the Openreach network do not cause network or service harm which would impact

other users of the network • To help verify that the parameters being fed by the modem into the Openreach network are correct. Please note that we count a CP device as both hardware and firmware. So a change of firmware will be counted as a new device and we will review to ascertain if testing is required. New firmware should not be made available without prior review from and approval by the MCT. Also note that the devices which you submit to Openreach should not have undergone any configuration changes or used in any internal/external test & trials. It is essential that you submit the devices in the form you receive it from your device manufacturers as you would supply to your end users. The device must also be configured to work against the testing parameters, Openreach will not configure the device in order for it to pass certain tests. If you have a device that you would like to have verified, you should speak with your technical engagement manager or sales and relationship manager who will provide the submission details and put you in touch with the test team. If you are not an existing customer consuming GEA-FTTC product, you would need to email your interests to customer.establishment@openreach.co.uk

Overview

6

•Any CP registered with Openreach can opt to have their devices verified against BT SIN 498 after completing the necessary Customer Establishment process. You will need to submit a formwize request to start of the MCT process.

• If you want to pick a device from the published list that has passed MCT process contact MCT Support team mct.front.door@openreach.co.uk

• If you are a reseller or a CPE Vendor and wish to have your devices verified, you will need to contact your GEA-FTTC service supplier who will engage with Openreach on your behalf. Please note that such requests to test your devices should be made by service providers and not by yourself

Communications Provider & Resellers

•If you are a new customer, the Openreach Customer Establishment Team will help you to complete initial registration, product familiarisation, connection to the Openreach platforms and integration onto our systems before directing you to the MCT CP Support team to get your devices tested

Customer Establishment Team

•Will act as the Openreach contact during your Modem Conformance Testing period

•Will act as bridge between you and the Openreach test team, providing updates on the status of testing

•Will be your single Point of Contact during MCT

MCT CP Support

•Validates your Formwize submissions and conducts necessary tests on your devices

•Provides you/MCT CP Support team with technical assistance & updates during testing

Test Team

Participants of MCT

7

Openreach publish a list of devices that have passed the MCT process and are therefore already approved.

Where a CPs require MCT Exemption for a device that they select from the MCT Approved list they should submit a formwize request, completing those sections relevant to confirm exemption from testing.

The MCT team will then validate the formwize and check that the device exists in the MCT Approved list

The MCT Support team will then provide the CPs with MCT Exemption for the selected device.

Important Note :

– CPs requiring the MCT Exemption Approval should be consuming GEA-FTTC product

MCT Exemption Approval Process For choosing an approved device

8

MCT Exemption Process Flow Diagram For choosing an approved device

Com

munic

ation

Pro

vid

er

Cust

om

er

Est

ablis

hm

ent

te

am

MCT

CP

Support

Modem

Confo

rmance

Test

te

am

Start Process

New Customer

Signs a contract with Openreach

CP Notified that device doesn’t exist in Approved list & suggest to choose

another device

Submit formwize to get MCT Exemption Approval

CP notified as device present in Approved list & provide a MCT Exemption

Contract Verified

Successfully?

Formwize verified

successfully?

Verify device exists in

Approved list ?

Y N

N Y

N

Y

N

Y

End Process

9

Where a CPs have made a change to an existing MCT approved device that they don’t believe should require MCT. Then they can submit a request for Exemption for the device.

This should be done using the formwize request and selecting MCT Exemption as the reason. Release notes will have to be included that show the differences between the device exemption is should from and the device wanting exemption.

MCT team will then validate the formwize and check that and exemption is appropriate.

The MCT Support team will then provide the CPs with MCT Exemption for the selected device.

Important Note :

– CPs requiring the MCT Exemption Approval should be consuming GEA-FTTC product

– MCT Exemption given to the devices with differences that don’t affect MCT like WIFI or GUI changes etc.

MCT Exemption Approval Process For changes not requiring MCT on an approved device

10

MCT Exemption Process Flow Diagram For changes not requiring MCT on an approved device

Com

munic

ation

Pro

vid

er

Cust

om

er

Est

ablis

hm

ent

te

am

MCT

CP

Support

Modem

Confo

rmance

Test

te

am

Start Process

New Customer

Signs a contract with Openreach

CP Notified that device requires full MCT Submit formwize to get MCT

Exemption Approval

CP notified that device will be given exemption.

Exemption given.

Contract Verified

Successfully?

Formwize verified

successfully?

Device to be given

exemption?

Y N

N Y

N Y

N

Y

Release notes and exemption path

verified

End Process

11

Modem Conformance Testing Process Flow Diagram

Com

munic

ation P

rovid

er

M

CT

CP

Support

Modem

Confo

rmance

Test

te

am

Start Process

New Customer

Signs a contract

with Openreach

Submit formwize request to Openreach

Formwize verified?

Modems received on time

?

Y

N

N

Y

N

Y

Receive testing slot/dates from

Openreach

CP couriers modems to Openreach

CP Notified of test results success

CP needs to resubmit formwize with new modem

Notified of test

results failure

CP notified of progress

on a weekly basis

Allocate/Reallocate & confirm the testing

slot/dates to CP

Start MCT

Provide weekly testing Updates

Notify CP on testing Progress

Complete MCT

Validate & publish test

results

End Process

Modem added to Modem Bank

MCT Test

Pass/Fail ?

Publish results to CP

Fail Pass

Contract Verified by Customer

Establishment Team

12

MCT Gatekeeper Test Process Flow Diagram

Com

munic

ation P

rovid

er

M

CT

CP

Support

te

am

Modem

Confo

rmance

Test

te

am

Start of Assigned Slot MCT

N

Y

Gatekeeper 1 Test

Pass/Fail

CP notified of the Result

and Next Step

CP notified of the Result

and Next Step

CP supplies 2 Devices with Fix in time for

Gatekeeper 2

CP notified of the standby List and

Next Step

Gatekeeper 2 Test

Pass/Fail

Add in queue to Standby

List

Notify CP of the Result

Notify CP of the Result

START Gatekeeper 2

Test of allocated Slot

START Gatekeeper 1

Test

Fail Fail

Pass

Pass

CP Sends 2 Devices for Gatekeeper

Confirms Devices and submits to test team

Start

Confirms Devices and submits to test team

Stop Resubmit for

new slot

CP notified of the Result and Next Step

Submitted to MCT Slot

13

Openreach will test a CPs device in advance of a full MCT testing to ensure it is able to pass a small number of key tests before entering in to a full test cycle. There will be 2 opportunities for a device to pass this test, so if a device fails first time around it can be re-presented for retest 1 further time. Openreach requires 3 devices from CP while running this tests. If it passes either test then it will be accepted into the full MCT test slot reserved for the CP. Openreach requires 2 additional CP devices along with 3 devices. In total 5 CP devices should be available during start of MCT. If it fails both attempts then a CP will need to request a new MCT test slot. Openreach have introduced this additional test to prevent devices from entering a full MCT cycle when it is unable to pass basic tests, therefore allowing the slot to be re-used for other CP devices that are ready. Openreach will carry out the following tests for the Gatekeeper testing:-

• Compliance to ANFP Part C

• Use of Tone-sets A43 and/or A43c

• Passive Peer OAM mode check

• Correct Reporting

• PPP or DHCP Session Establishment

• R.OAM.2 WAN Interface supports loopback messages

MCT Gatekeeper Testing

14

Openreach will conduct up to 2 gatekeeper checks per device ahead of the Main slot for MCT. • Gatekeeper1 Test : A CPE device will be tested for the mandatory parameters. This will usually be carried out on the Monday 2

weeks prior to full MCT. The devices must be with Openreach the Friday before Gatekeeper 1. The result will be presented to the CP by Tuesday.

• Gatekeeper2 Test : CPE device fix will be re-tested for all the mandatory parameters. If CPE device again fails then it will marked as failed device and will not be eligible to go for full cycle MCT.

Only Gatekeeper passed devices will be eligible for full cycle MCT testing. What an MCT Cycle looks like

MCT Gatekeeper Testing Continued Until April 2018

15

Openreach will conduct up to 2 gatekeeper checks per device ahead of the Main slot for MCT. • Gatekeeper1 Test : A CPE device will be tested for the mandatory parameters. This will usually be carried out on the Monday 2

weeks prior to full MCT. The devices must be with Openreach the Friday before Gatekeeper 1. The result will be presented to the CP by Tuesday.

• Gatekeeper2 Test : CPE device fix will be re-tested for all the mandatory parameters. If CPE device again fails then it will marked as failed device and will not be eligible to go for full cycle MCT.

Only Gatekeeper passed devices will be eligible for full cycle MCT testing. What an MCT Cycle looks like

MCT Gatekeeper Testing Continued From April 2018

16

• When a Formwize is received by Openreach a confirmation email informing the CP of the slot details will be sent. On this confirmation email the CP will be asked whether they would like to go onto a Standby List.

• This Standby List will enable CP’s to fill a slot where another device has either failed to be delivered to Openreach or has failed 2 Gatekeeper Checks.

• The device must be declared Ready for Test, which means the device will have no firmware upgrades up until the original slot that the CP will receive, and the device can be sent to Openreach immediately.

• Once Openreach receives the device a Gatekeeper check must be completed in order for the device to gain entry onto the Standby List.

• If the device fails the Gatekeeper check, the device will not gain entry to the Standby List but will keep it’s original slot. • The CP will then be advised that the device has failed it’s gatekeeper 1 test and will need to fix the issue before it’s original slot. • Each device will only get 2 Gatekeeper checks, so if the CPE fails it’s Gatekeeper for the Standby list, it will only get 1 more

Gatekeeper check for it’s original slot instead of 2. • If the device passes the Gatekeeper check for Standby List it will gain entry to it and the CP will be made aware of it’s position on the

list. • Once a space becomes available the CP will be informed that MCT is due to start, this could be at very short notice, hence why we

require 5 devices on site and with no firmware changes. • If a firmware change is made, the Gatekeeper 2 check will be used to confirm the device’s place on the standby list. If the device

does not have a gatekeeper 2 left, then it could lose its allotted MCT slot. • If the CP gets a slot from being on the standby list, the CP will then lose its original slotted slot.

Standby List

17

The Openreach GEA-FTTC (VDSL) network has equipment from two different suppliers. Each of those suppliers delivers major changes to their network components about twice per year. Openreach regression tests all these changes to help ensure they don’t introduce problems to the devices at an MCT level and to make sure the functionality delivered in the supplier release works properly. Regression testing is a subset of the tests run during MCT and does not test any services the CP may run over the device or non MCT functions. Once a modem has complete MCT if a CP chooses it will be added to the Openreach modem bank at which point we require to keep 3 working samples of the device. We will regression test the changes against the devices which are in the modem bank when we receive the new firmware from our suppliers. We will contact you when we receive the new firmware from our suppliers and provide you the test and roll-out plan so that you can make plans for any performance testing you might want to do in addition to our regression testing. While Openreach is regression testing a network change, if we find a problem or observe a difference in device behaviour, we will contact you via the contact details you have provided for the device to discuss what we’ve found. If the issue identified is with our vendor code, then we won’t pass the network upgrade for deployment if the issue is major. If a minor issue is identified we will only pass the upgrade to deployment if we’ve agreed a fix plan and let you know about it.

Openreach Network Regression Testing

18

As mentioned in the previous slide, the Openreach network suppliers deliver major changes to the network components about twice per year. For devices which are already in our Modem Bank, we will regression test all the network changes. Every time you approach us seeking MCT for your existing (upgraded) or new device, we will make a conscious decision whether to carry out MCT on the existing live code deployed in the live network or the upcoming code. This decision will be based on whether we have reached the SafeToConnect2 (STC2) stage of upcoming code which describe its readiness to be deployed on Live. Before we start the MCT on your device, we will inform you of the code against which your device will be tested. You will also be provided with the live release dates of the upcoming code up to three months in advance. • MCT against live code (n)

We will MCT your device against the live code (n) if we have not reached the STC2 on the upcoming code (n+1). As your device would not be in modem bank, and hence does not undergo the regression testing of the upcoming code, we strongly advice you to make use of our Performance Test Facility (PTF) to test your device against upcoming code (n+1) to check for any compatibility issues.

MCT between Regression & Deployment

19

• MCT against upcoming code (n+1)

We will MCT your device against the upcoming code (n+1) if we have reached the STC2 stage of its testing. Even after the STC2 stage of the upcoming code is reached, it will take several weeks for us to deploy it nationally. Hence we strongly advise you to make use of the Performance Test Facility (PTF) to test your device against the live code (n) to check for any compatibility issues.

Please note that CPs who want to use the Performance Test Facility must order GEA Cablelinks to the four Layer 2 switches, one each for the Live and Live+1 networks for each of Openreach’s suppliers, as well as order live GEA-FTTC services. More information about booking time and space in the facility and placing orders into the facility is available in the user guide available from the Customer Test Services page of the Openreach portal.

MCT between Regression & Deployment

20

• How do I submit my formwize request?

• To start the MCT process, you need to submit a formwize request online. This is available on the link http://www.formwize.com/run/survey3.cfm?idx=505d040c0e0a0e

• Will I receive a reference number once I submit the formwize?

• On successful submission of formwize, you will see an acknowledgement message on your screen and later you will receive an email from Openreach MCT Team confirming the receipt of your submission.

• How long will it take Openreach to confirm testing slots after receiving my formwize submission?

• It will take up to 2 working days to validate your formwize submission. If it contains all required details, we will attempt to confirm the testing slots within 24 hours of successful verification of your formwize.

• What happens if my formwize submission does not contain sufficient information?

• The Openreach MCT team will contact you and will request you to resubmit the formwize request with updated information.

• When the firmware is upgraded for my device, will it be sufficient if I only include the delta while submitting the release notes for the

newer version?

• No, it is important that you provide us with the full code history so that we can understand what the device is capable of.

Frequently Asked Questions Formwise Submission

21

• How many samples of my device are required to be submitted to Openreach?

• We require a minimum of three devices for Gatekeeper on the Friday before your Gatekeeper Check. If the device passes we will require an additional 2 devices to be sent to us immediately for MCT. If the device fails Gatekeeper 1 The CP will need to arrange collection of the device otherwise it will be destroyed. A new set of devices will be required for Gatekeeper 2. Openreach will not conduct firmware upgrades for the CP.

• When do I need to submit my devices to Openreach?

• Your devices should reach us by the cut off date provided in the slot confirmation email. • How should I need to submit my devices to Openreach and to which address?

• The devices needs to be couriered using a traceable service to the Openreach test facility at the address below.

MCT Test Facility Scheduling Team,

PP2, 5th Floor,

Orion Building, Adastral Park

Martlesham Heath

Ipswich IP5 3RE • What happens if I cannot get my device into Openreach by the dates provided.

• The CP will miss it’s slot and will need to resubmit for the next available slot. Please be aware this could be several months away. • Will I receive an acknowledgement from Openreach on receipt of my devices?

• Yes, Openreach MCT team will notify the nominated contacts once the sample devices are received.

Frequently Asked Questions Device Submission

22

• What are the time lines for the Gatekeeper testing before the full MCT cycle?

• Gatekeeper 1 test will start two weeks ahead of the full MCT start date.

• Gatekeeper 2 test will start on the Monday of the week immediately prior to full MCT start date. A CP can find the dates for testing in the slot confirmation email sent by the Openreach MCT front door team.

• If the device presented fails both Gatekeeper tests then what will be the next step for the CP?

• Every device will require to go through the gatekeeper tests to be eligible for the full MCT test. Openreach MCT team will not accept any device for full cycle MCT, if it does not pass the Gatekeeper tests.

• If a device passes all the test parameters in Gatekeeper 1 testing, will Openreach still perform Gatekeeper 2 testing?

• No, Then Gatekeeper 2 test will not be required if Gatekeeper 1 test finds that device presented satisfies the mandatory parameters.

• Can BT Openreach conduct customized testing during Gatekeeper test?

• No, The purpose of the Gatekeeper test is to identify if the device presented is in testable state or not. Openreach will only conduct very basic tests mandated into SIN498 document. We will test other detailed requirements in the Full MCT cycle. So Openreach will not perform customized Gatekeeper testing.

Frequently Asked Questions Gatekeeper Test

23

• How long will it take for Openreach to complete testing and provide me with the results?

• The testing will take up to four weeks to complete. However from April 2018 this will be reduced to two weeks. • Will I receive any interim updates on testing status of my devices?

• At 5pm on Friday of each week you will get an interim test matrix detailing the tests we’ve done and what’s in progress.

• What happens if Openreach detects problems with the device during testing?

• The CP will be informed of the issues at the end of each week with the weekly Test Matrix update. Openreach will complete it’s full cycle of testing to give the CP a view of all the issues seen. Openreach will not accept any firmware changes in the MCT window.

• If I have a new Firmware do I need to send Openreach another set of devices

• Yes, Openreach will not be flashing existing modems with new firmware. Openreach require new devices for each new firmware.

• If the device obtains a conditional pass, will it be added to the modem bank?

• This will be dependent on the test parameters which have failed. Openreach will inform you whether your device will be added to the modem bank or not.

• If the device obtains a conditional pass, can I use it to rollout my GEA-FTTC product in Live network?

• A device with a conditional pass will have certain restrictions placed on it depending on what issues it faces. A device will require a full pass in order to be able to be fully deployed.

Frequently Asked Questions Testing & Updates

24

• Do we need to go through the MCT process again if we make changes to a device which is in the Modem Bank?

• We will analyse the changes to your device using the release notes you provide us to decide whether your device needs MCT repeated.

• How many devices can I maintain in the Openreach Modem Bank?

• We will maintain up to 30 CP devices in total (NOT per CP). So we want to make sure that the devices in the Modem Bank represent the modems that are actually in the live network. If the modem bank is full, we’ll identify less used devices and discuss options with owning CPs.

• When will I be enabled on the EMP system to order GEA-FTTC services without an Openreach Modem?

• You must have obtained a “Full Pass” or “Conditional Pass” to connect a pre-production or production device to the live network, before you are enabled on EMP system.

• Is there a limit for the number of devices I can have tested by Openreach?

• Openreach will operate a fair use policy, there are no strict guidelines into how many devices a CP may submit, but if Openreach feel the schedule is being over-run with one or two devices from a CP then it will reject any further applications for MCT.

• Is there a limit for the number of times I can get my device tested to obtain a ‘Full Pass’?

• Yes, any repeat testing of a CP Device to obtain a test result of “Full Pass” will be limited to two (2) attempts (i.e. three attempts in total). Any additional testing would incur costs and will be tested in next available testing slot.

Frequently Asked Questions General Queries

25

• How do I pick a device from the Published List ?

• You need to submit a different formwize request online. Before submitting the request please ensure you have contacted the device manufacturer to confirm details such as CPE firmware, Chipset hardware, Chipset firmware, release notes & any additional information required. On receipt of the Formwize request the MCT team will review the submission. If all of the details match an existing device from the approved list an approval will be given from the MCT Front Door team.

• What happens if a device in the MCT modem bank develops a fault?

• In the hopefully rare case of the modem in the bank failing (e.g. PSU/hardware) the CP will be notified and asked to supply a replacement device to enable it to stay in the modem bank.

• What happens if my device fails MCT testing?

• Openreach will collect together the modems supplied and ask for the CP to arrange for a courier to collect the modems to be returned to the CP.

• Can I use this process for my G.Fast Device?

• G.Fast has a similar process if you are interested in G.Fast and currently do not consume G.Fast you should contact the customer establishment team. If you already consume G.Fast then you can contact MCT Front Door for the relevant G.Fast documentation and formwise. This guide only covers the GEA-FTTC (VDSL) MCT process.

Frequently Asked Questions General Queries

26

Please refer to product description and the contracts documents for the latest updates, • GEA-FTTC Product Description – https://www.openreach.co.uk/orpg/customerzone/products/super-

fastfibreaccess/fibretothecabinet/description/productdescription.do

• GEA Contract –

• https://www.openreach.co.uk/orpg/home/products/super-fastfibreaccess/contracts/sffacontracts.do

• CPE Enablement –

• https://www.openreach.co.uk/orpg/home/products/super-fastfibreaccess/cpeenablement/cpeenablement.do

• Performance Test Facility –

https://www.openreach.co.uk/orpg/customerzone/helpandsupport/cts/documentation/ctsdocumentation/downloads/AdastralParkTestFacilityGuide10.pdf

• SIN – http://www.sinet.bt.com/

• New Customers – https://www.openreach.co.uk/orpg/home/contactus/customerestablishment/customerestablishment.do

References

27

Acronym Meaning

CP Communications Provider

CPE Customer Premise Equipment

EMP Equivalence Management Platform

EU End User

FTTC Fibre to the Cabinet

GEA Generic Ethernet Access

MCT Modem Conformance Test (i.e. SIN-498 Device verification testing)

NGA Next Generation Access

PTF Performance Test Facility

SIN Supplier Information Note

STC2 Safe To Connect2

VDSL Very-high-bit-rate digital subscriber line

Glossary of Terms

The contents of this pack cannot be copied or reproduced in whole or in part without the written consent of Openreach.

© British Telecommunications plc