1 / 63

EBC Conference

EBC Conference. Introduction and Welcome. 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?

grace
Download Presentation

EBC Conference

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  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.30 Coffee and Registration • 10.00 Introduction & Welcome • 10.05 EBC Solution - Routing Plan Database • 11.05 EBC Solution - Use of Exit POCs • 11.35 EBC Solution - Timeline • 12.00 Break • 12.15 EBC Solution – New files • 12.45 EBC Solution - Processes • 13.05 EBC and NIPP • 13.20 Summary & Close • 13:30 Lunch

  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. EBC Solution and Exit POCs

  10. 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

  11. 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

  12. 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, 01473292, 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

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

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

  15. Benefits • Transparency • CP control • Predictability • Simplification

  16. EBC Solution and Timeline

  17. EBC Matrix ‘X’ Effective Date EBC Matrix ‘X’ Build Start Date EBC Matrix ‘Y’ Build Start Date EBC Matrix ‘Y’ Effective Date EBC Solution - Timeline - DMAs If DMA ‘A’ Agreed Implementation Date is during this period, then changes will NOT 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 be included in Matrix ‘Y’.

  18. EBC Solution and Two New Files

  19. 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

  20. 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

  21. 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

  22. File 1 – DLE Example • 0646006,0646006,520 • 0646006,0945010,521 • … • 0646006,1311001,525 • 0646006,1311618,525 • 0646006,1312997,525 • … • 0646006,1440182,521 • 0646006,1441455,521 • 0646006,1455134,525 • 0646006,1460128,525 • … • 0646006,4012629,525 • 0646006,4014559,525 • 0646006,4015916,525 • 0646006,4016350,525 • … • 0646006,5945021,521 Middleton Unit C (DLE) Itself Directly connected SYSX DLTEs All SYSX DMSUs Directly connected WATs WATs tandemed with directly connected WATs All NGS DMSUs Directly connected AXE10 DLTEs

More Related