ebc conference

http://www.btwholesale.com 1

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?

• Understand progress on other issues raised

• Outline BT’s plans


Scene Setting

• Why evolve EBC?

• What needs to be changed?

• New EBC files

• Security


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


EBC Solution –Routing Plan Database


EBC Solution –Routing Plan Database

• Contract

• Provisioning Manual

• Appendix 24


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


EBC Solution – Current Routing Plan Contents

• Spread sheet Routing Plans

• Operator details

• Number strings

• BT Switch Connections

• Catchment Areas


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, 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


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

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?

YES NO

Use the POC in the RoutingPlan 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

0646006,0646006,5200646006,0945010,521…0646006,1311001,5250646006,1311618,5250646006,1312997,525…0646006,1440182,5210646006,1441455,5210646006,1455134,5250646006,1460128,525…0646006,4012629,5250646006,4014559,5250646006,4015916,5250646006,4016350,525…0646006,5945021,521

Directly connected WATs

WATs tandemed with directly connected WATs

All SYSX DMSUs

ItselfMiddleton 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

…4073327,0723111,5244073327,0723118,5244073327,0724119,5234073327,0724166,523…4073327,1311001,5294073327,1311618,5294073327,1312997,529…4073327,1712241,5254073327,1712300,5254073327,1715359,525…4073327,4012629,5294073327,4014559,5294073327,4015916,529…4073327,5710060,5254073327,5710312,5254073327,5710360,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

0973004,0120671,5200973004,01206760,5200973004,01206761,520…0973004,01394380,5200973004,01394385,5200973004,01394389,5200973004,01394600,520…0973004,01473106,5200973004,0147321,5200973004,0147322,5200973004,01473230,5200973004,01473231,5200973004,01473232,520…0973004,0172845,5200973004,0172860,5200973004,01728633,520…0973004,01787220,5200973004,01787221,5200973004,01787222,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



•Most processes unchanged

•Preparation of Routing Plans

•Submission of DMAs

•Timing of DMAs

•Checking DMA Dates



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


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

ebc conference

Documents