TDM Access & TDM Backhaul PPC Forum June 12 th 2008

1. TDM Access & TDM Backhaul PPC ForumJune 12th 2008 Ian Boothman Spyros Christou

2. Please note • The information contained within these slides is indicative and provided for information purposes only. The information represents no commitment from BT. • All features discussed in these slides are subject to detailed design & successful testing.

3. Progress to date • Openreach has held a number of bilaterals, nine sessions with six CPs • Bilaterals have been run to capture/re-affirm CPs requirements and indicative volumes, where possible • Infrastructure pre-design has been undertaken by BT Design • A consolidated feedback document was shared with those who had taken part in bilaterals on 15th May and published on the Openreach website on 20th May 2008. • Openreach is currently focusing development on a 2Mb TDM Access product • Workshop held 29th May to discuss requirements.

4. TDM Access and Backhaul Product Requirements Feedback from Customer Bilaterals • Access • 2Mbs, 34Mbs and 155Mbs • Copper, fibre and radio access options • Aggregated hand-off options (IBH and ISH) • Shared or dedicated CP mux • VC12/3/4 switching granularity • Unprotected, RO1, RO2 and RO2 (different exchange) resilience • Future-proof and upgradeable • Share TDM and Ethernet on the same infrastructure

5. TDM Access and Backhaul Product Requirements Feedback from Customer Bilaterals • Backhaul • STM-4 and STM-16 (STM-64) • IBH / ISH / ISHe handover • Converged backhaul (Ethernet & TDM traffic mix)

6. Definitions • CP = Communications Provider • Mux = TDM multiplexer • XL: Low-Order (VC-12) TDM cross-connect • XH: High-Order (VC-4) TDM cross-connect • High-order aggregation: Reorganisation of traffic / mapping of circuits within several STM-n bearers into a single STM-m bearer using XH functionality (m ≥ n) • Low-order aggregation: Reorganisation of traffic / mapping of circuits on partially-filled STM-n bearers into a single, more heavily-loaded STM-m bearer, using XL functionality (m ≥ n) • Grooming: Any-to-any mapping of 2Mb/s circuits between multiple STM-n bearers, using XL functionality

7. BT serving site Customer site CP node 2Mb/s access service - Variant A Access Mux Mux Fibre / Copper n x 2Mb/s n x 2Mb/s CP1 • Access between customer site and BT serving site. • For simple point-to-point service only. • No aggregation or grooming. • Likely application: where n is low, e.g. 1 to 16.

8. BT serving site Customer site CP node 2Mb/s access service - Variant B Access CP1 Mux XL Fibre / Copper n x 2Mb/s • Access between one or more customer sites and BT serving site. • Provides a low-order aggregation service. • Option: grooming may also be provided as shown in lower example. • Likely application: where BT serving site is parent for several customers from the same Communications Provider • (CP1 shown here). Single STM-1/4/16 handoff CP1 CP1 • Offered either as: • n x 2Mb/s, or • channelised STM-1 CP1 Mux XL Fibre / Copper n x 2Mb/s CP1 CP1 Multiple STM-1/4handoff

9. TDM Access and Backhaul Product Requirements Feedback from Customer Bilaterals • Performance • Components must allow CPs to replicate the existing E2E customer experience • Network - availability, delay, jitter etc. • Service – SLA / SLG, TotalCare

10. TDM Access and Backhaul Product Requirements Feedback from Customer Bilaterals • Migration • Quick, easy and low cost – smooth customer journey • Little evidence of new demand • Avoid Excess Construction Charges • Defined migration paths from / to PPC, RBS, NS16 and Ethernet in the future • Managed bulk migration option • Openreach is developing a new TDM Access product on a new provide basis. It has no plan to develop a migration path.

11. 2008/09 Indicative Timeline – 2Mb box to box access solution Understand commercials with customers Start feasibility Bilaterals complete Share feasibility results, gather feedback Share initial product requirement document Q1 Q2 Q3 Q4 Customer definition workshop Agree and finalise initial product requirement document Complete solution design Implement feasibility feedback and start solution design Define 2Mb product offering Go/No Go on commercial grounds Not to scale Subject to internal Openreach agreement and sign off

12. 2009/10 Indicative Timeline – 2Mb box to box access solution Systems and infrastructure development(EMP platform etc) COMPLETESystems and infrastructure development(EMP platform etc) Share progress with industry Launch Q1 Q2 Q3 Q4 Testing/ trial Update customers, gain feedback, engage trialists etc Share progress with industry Not to scale Subject to internal Openreach agreement and sign off

13. Openreach Create PRD Commercial Analysis Product Development Communications Providers Provide target price and robust volumes to Openreach Next Steps for 2 Mb Access

14. AOB

16. BT serving site Customer site CP node 155Mb/s access service Access Mux Mux Fibre, STM- 4/16 n x STM-1 n x STM-1 • Interconnect service between BT serving site and CP node. • CSH (Customer-Sited Handover). • Provides a simple CP interconnect service. • Provides neither aggregation or grooming. • Likely application: Where n is low, e.g. 1 to 16. • Need to consider resilience options.

17. BT serving site BT serving site Customer site • This variant provides a simple service i.e. no aggregation • The service is relevant to new build only i.e. not by CPs migrating from PPCs • It is likely to apply in cases where n is low e.g. 1 to 16 • The service will run over shared infrastructure, owned & managed by BT Operate • Re-use of Orchid solution would require product upgrade to include TDM interfaces • Second diagram illustrates why this service is required: • Required by CPs with a presence at a serving site • But where the CP does not own network • connectivity to that site 155Mbps backhaul service Backhaul BT serving site BT serving site XH XH Fibre / WDM / STM-16 / Orchid n x STM-1/4/16 n x STM-1/4/16 CP1 Access Backhaul XH XH XL XH STM-1/4/16 Fibre / Copper Fibre / WDM / STM-16 / Orchid n x 2Mbps n x STM-1/4/16 CP1