1 EBC Conference Introduction and Welcome

2 Objectives of the day Report progress since the February workshop Understand the EBC Solution How would I use the Routing Plans Database System? How should I use the new files in EBC? What do I have to do? Understand progress on other issues raised Outline BT’s plans

3 Scene Setting Why evolve EBC? What needs to be changed? New EBC files Security

4 Agenda 09.30Coffee and Registration 10.00Introduction & Welcome 10.05EBC Solution - Routing Plan Database 11.05EBC Solution - Use of Exit POCs 11.35EBC Solution - Timeline 12.00Break EBC Solution – New files 12.45EBC Solution - Processes 13.05EBC and NIPP 13.20Summary & Close 13:30Lunch

5 EBC Solution –Routing Plan Database

6 EBC Solution –Routing Plan Database Contract Provisioning Manual Appendix 24

7 EBC Solution – What do we need ? We need a system with…… A uniform presentation and feel Ease of use Accessibility Validation of information DMA dates

8 EBC Solution – Current Routing Plan Contents Spread sheet Routing Plans Operator details Number strings BT Switch Connections Catchment Areas

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37 EBC Solution and Exit POCs

EBC & exit POCs: Current Process EBC currently uses a set of rules in conjunction with a list of exit POCs to derive the charge for: BT originated IA/CPS/118DQ Transit

New Solution: Agreed Exit POC No change to charging for BT-terminated traffic or BT- originated NTS The new solution will use Exit POCs shown in the routing plan database Least cost connectivity path to get to the agreed exit POC Changes to EBC algorithms, but not the use of EBC data

New Solution - Agreed Exit POCs (AEPs) Routing Plan data will directly drive EBC charge bands The Routing Plan data shows catchment area, number block and BT switch passing calls to CPs, e.g. Ipswich, , Ipswich Unit A The routing plan database will show: If/when DMA has been raised by the Operator Agreed date of change on DMA When DMA has been implemented by BT The exit POC for a given origin will be that agreed to be in place when the EBC data goes live

Use of Agreed Exit POCs, BT-originated Processing logic for each traffic type originating from a BT DLE: Is the DLE a POC? YESNO Use the POC in the Routing Plan for charging Select Tandem to use as AEP from Routing Plan Obtain EBC charge band from DLE to Agreed Exit POC

Use of Agreed Exit POCs, transit Processing logic for transit traffic at each BT tandem: Is the tandem an Exit POC? YESNO Use the POC in the Routing Plan for charging Obtain EBC charge band from tandem to Agreed Exit POC Identify the Agreed Exit POC from the Routing Plan

Benefits Transparency CP control Predictability Simplification

EBC Solution and Timeline

EBC Solution - Timeline - DMAs EBC Matrix ‘Y’ Build Start Date EBC Matrix ‘Y’ Effective Date EBC Matrix ‘X’ Effective Date EBC Matrix ‘X’ Build Start Date If DMA ‘A’ Agreed Implementation Date is during this period, then changes will be included in Matrix ‘Y’. DMA ‘A’ may be raised during this period for inclusion in Matrix ‘Y’. If DMA ‘A’ Agreed Implementation Date is during this period, then changes will NOT be included in Matrix ‘Y’.

EBC Solution and Two New Files

New Files – The Drivers Alignment with agreed routing Charging predictability Enabling routing optimisation Need for enhancements: Shows only existing points of connect Retardation of number ranges Exchange mapping Non-contractual traffic Effort

Two New Files A new file to assist CPs receiving traffic from BT A new file to assist CPs delivering traffic to BT Standard EBC file format Standard naming convention Standard header and trailers Comma-separated format data records

File 1 – Receiving Traffic from BT A BT-switch-to-BT-switch matrix, with charge band Any traffic type Valid call routing scenarios E.g. a DLE origin would be shown against the following destinations: For BT-originated traffic, the DLE itself and all switches that could be Exit POCs For transit traffic, nothing Each data record will contain: origin exchange NNI, destination exchange NNI, EBC charge band Transit / Non-transit charge bands

File 1 – DLE Example , , , ,521 … , , , , , ,525 … , , , , , , , ,525 … , , , , , , , ,525 … , ,521 Directly connected WATs WATs tandemed with directly connected WATs All SYSX DMSUs Itself Middleton Unit C (DLE) All NGS DMSUs Directly connected SYSX DLTEs Directly connected AXE10 DLTEs

File 1 – Trunk Example All SYSX DLEs and DLTEs All SYSX DMSUs All ASUs Ipswich Morganite (NGS DMSU) All NGS DMSUs … , , , , , , , ,523 … , , , , , ,529 … , , , , , ,525 … , , , , , ,529 … , , , , , ,525 … All AXE10 DLEs and DLTEs

File 1 – Benefits to CPs Transparency Trunk-to-trunk connectivity Routing plan applicability Mapping to catchment areas All possible points of connect covered

File 2 – Delivering Traffic to BT Point of connect to number block, with EBC charge band Full-length number blocks Valid call routing scenarios E.g. a WAT origin would be shown against the following destination number blocks: BT number blocks hosted on directly connected DLEs CP number blocks accepted at this WAT Each data record will contain: origin exchange NNI, destination number block (unretarded), EBC charge band

File 2 – DLE Example , , , , , ,520 … , , , , , , , ,520 … , , , , , , , , , , , ,520 … , , , , , ,520 … , , , , , ,520 Unretarded BT number blocks hosted on DLE Ipswich Unit B (DLE)

File 2 – Benefits to CPs Full length number blocks Only valid routing shown Route Optimiser-friendly No need to expand out retarded number blocks Invalid routings will not be shown

EBC Solution - Processes

EBC Solution - Processes Most processes unchanged Preparation of Routing Plans Submission of DMAs Timing of DMAs Checking DMA Dates

EBC Solution - Processes Use two new files to: Switch to switch file - where to receive calls POC to Number Block file - where to deliver calls to BT When published run checks Re-distribute traffic flow Open up new connections as necessary

EBC and NIPP

EBC and NIPP – Alignment of Data Worked on aligning Implication of Dates Dates to align Current data Planning data

EBC and NIPP – Rationalisation of Files Previously announced Duplicated files removal Both EBC and NIPP Web site for network Briefings Some Increased

62 EBC Workshop Summary & Close

EBC Solution - Summary Routing Plan Database Two New Output Files EBC and NIPP Communicate progress on delivery Thank you… and lunch