1 / 45

EBC Workshop

EBC Workshop. Introduction and Welcome. Objectives of the day. Report progress since the November workshop Understand the EBC Solution Understand progress on other issues raised Outline BT’s plans Next steps. Agenda. 10.00 Arrive & Coffee 10.30 Welcome

cuyler
Télécharger la présentation

EBC Workshop

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 Workshop Introduction and Welcome

  2. Objectives of the day • Report progress since the November workshop • Understand the EBC Solution • Understand progress on other issues raised • Outline BT’s plans • Next steps

  3. Agenda • 10.00 Arrive & Coffee • 10.30 Welcome • 10.35 EBC Solution - Routing Plan Database • 11.20 EBC Solution - New Files • 12.05 Break • 12.20 EBC Solution & NTS • 12.50 EBC related activities • 13.30 Summary & Close • 13.45 Lunch

  4. EBC Workshop EBC Solution – Routing Plan Database

  5. EBC Solution – Changes to Routing Plans • The Contract • Prov Manual • “Forms” required for the exchange of information • Appendix 24 shows the Routing Plans

  6. EBC Solution – What we do now with Routing Plans • Routing of traffic to the POC • Agreed with the TAM • Data Management Amendment

  7. EBC Solution – Routing Plan manual activities • Not everyone is skilled in using spreadsheets • A consistent format is not always used • Human errors • Incorrect information • Ambiguous • Dates are not shown

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

  9. EBC Solution – Routing Plan Database (RPD) System • Routing Plan Database ( RPD )

  10. EBC Solution – Routing Plan Database (RPD) System • Benefits • Improved production and change control • Storage on a centralised date-stamped database • Replace spreadsheets for Ingress Routing Plans • Web-based interface • Opportunity to track changes • Provide agreed Exit POC information to the EBC system

  11. Data Validation TAM Fault Reception Read-Only Routing Plans Operator Routing Plan Database Intranet Network Implementation DMA Reception BT Wholesale Portal EBC Solution - Routing Plan Database (RPD) System - Interfaces

  12. EBC Solution - Routing Plan Database (RPD) System – Stages Initiated Submitted Rework Data Validation Agreed Raised Implemented

  13. EBC Solution - Routing Plan Database (RPD) System – Data entry • Look & Feel of the data entry will be similar to that of the existing spread sheets • Drop down lists will be provided to simplify choices • Validation will be provided where appropriate • On-line help will be provided

  14. EBC Solution - Routing Plan Database (RPD) System – Features • Routing Plan changes will be tracked • Routing Plan information will be provided to BT Fault Reception to aid network problem investigation • Automatic notification will be provided to the Operator and the TAM at key stage

  15. EBC Solution - Routing Plan Database (RPD) System – Change • Change in the current Routing Plan process • You will have to change how you submit Routing Plans • BT will have to change how we process the Routing Plans • Getting your Routing Plan requirements implemented on the BT network will be much improved • Using the DMA date stamps will improve the alignment of charging dates for EBC

  16. EBC Workshop EBC Solution – New Files

  17. EBC Solution – Routing Plans • Routing Plans and EBC • Operator issues from previous workshops • Ingress Points of Connection • Direct Feed from Routing Plans Database System • Relationship with BT PSTN Design • Visibility for Operators • Dates

  18. EBC Solution – Operators’ Perspective • Alignment of agreed Routing Plans and EBC charges • Charges that are more predictable • Closer alignment of EBC and NIPP • Clarity of how Number Ranges and Switches map to charges • Operators optimise routing with BT based on EBC

  19. EBC EBC Solution – System Relationships

  20. EBC Routing Plans (Agreed with Operator) EBC Solution – System Relationships

  21. EBC Solution – System Relationships Network Design (Policy) EBC Routing Plans (Agreed with Operator)

  22. NIPP (Current) Network Design (Policy) EBC Routing Plans (Agreed with Operator) EBC Solution – System Relationships

  23. Retained DISCs DMSU DMSU NGS DMSU DMSU NGS DMSU DMSU WAT or DLTE DJSU DLE DLE Conc DLE DLE UXD5 Conc Conc Conc EBC Solution - BT PSTN Structure Other Services & Platforms Main Tandem Connectivity Main Tandem Switch Types DSSC Stand alone DMSU 999 IN 192 ASU NGS (Hybrid or Big Bang Narrowband) Phased Unit NGS (Hybrid or Full Connectivity Main Narrowband) Tandem DMSU DMSU DMSU Switching Not all connections or services are shown in this diagram. Layer Local Switching Layer inc Local Tandem Switches

  24. EBC Solution - Network Description & NIPP • BT’s Network Description provides: • High Level description, including outline planned changes • Operators access and download BT’s network description from: • http://www.btwholesale.com/interconnect2bt/network_information/network_description • NIPP provides • Greater detail of planned changes including detailed data files • Details of traffic types that can be exchanged at different types of POI • Registered users can access NIPP at • http://www.btwholesale.com/index.jsp

  25. EBC Solution– Two New Files • Existing files will continue • BT Wholesale will publish two additional files: • A file showing switch to switch to EBC charge bands • Used for planning where to connect • Little variation between matrix builds • A file showing EBC Charge Bands against valid number blocks • Used for planning where to pass traffic • Non-Retarded Number Ranges

  26. File 1 – Planning Where to Connect to BT • From switch NNI, to switch NNI, EBC Charge Band • Only valid combinations shown • Contractually valid call routing • Transit or Non-Transit

  27. File 1 – Planning Connect to BT – Trunk Ipswich Morganite (NGS) 4073327,0973102,521 4073327,0974001,523 4073327,0974016,523 4073327,0984001,524 … 4073327,1311001,529 4073327,1311618,529 … 4073327,1712241,525 4073327,1715359,525 4073327,1772355,521 … 4073327,4012629,529 4073327,4014559,529 4073327,4015916,529 … 4073327,5710060,525 4073327,5973090,521 4073327,5975073,523 4073327,5982049,524 All SYSX DLEs and DLTEs All (non-paired) DMSUs All ASUs All NGSs All AXE10 DLEs and DLTEs

  28. File 1 – Planning Connect to BT – DLE Ipswich Unit B (DLE) Itself … 0973004,0973004,520 … 0973004,1311001,525 0973004,1311618,524 0973004,1374017,521 … 0973004,1472250,521 … 0973004,4012629,525 0973004,4014559,525 0973004,4015916,525 0973004,4073327,521 0973004,4075179,521 … All (unpaired) DMSUs Directly connected WATs All NGSs

  29. File 2 – Optimising Traffic Delivery to BT • NNI, number block, EBC Charge Band • Valid combinations only • How do you use this file? • Match number block • Find CB and NNI combination appropriate • Valid for the existing EBC matrix

  30. File 2 – Planning Traffic Delivery – DLE 0973004,0120671,520 0973004,01206760,520 0973004,01206761,520 … 0973004,01394380,520 0973004,01394385,520 0973004,01394389,520 0973004,01394600,520 … 0973004,01473106,520 0973004,0147321,520 0973004,0147322,520 0973004,01473230,520 0973004,01473231,520 0973004,01473232,520 … 0973004,0172845,520 0973004,0172860,520 0973004,01728633,520 … 0973004,01787220,520 0973004,01787221,520 0973004,01787222,520 Ipswich Unit B (DLE) Unretarded BT number ranges hosted on DLE

  31. File 2 – Planning Delivery – Trunk Ipswich Morganite (NGS) Numbers on DLE 0973102 4073327,014732830,521 4073327,014736162,521 … 4073327,01603212,523 4073327,01603213,523 4073327,016032140,523 4073327,016032141,523 4073327,016032142,523 … 4073327,0195345,523 4073327,0195342,523 … 4073327,0164223,524 4073327,0164224,524 4073327,01642256,524 4073327,0164226,524 4073327,01642621,524 … 4073327,0113212,529 4073327,0149166,528 Numbers on DLE 0974001 Numbers on DLE 0974016 Numbers on DLE 0984001 Numbers on Other Networks

  32. EBC Solution – EBC Modifications Summary • Routing Plans • These show agreed routing arrangements • DMAs • These effectively tell BT to put Routing Plans into effect • Dates • These are needed for any system that is going to feed into billing EBC will be modified to use the dates built into Routing Plans and DMAs from Summer 2004

  33. EBC Workshop EBC Solution & NTS

  34. EBC Evolution and NTS: INCA/CLI proposal • BT’s proposal (included in the response to the Oftel NTS con doc) for per-call EBC charging of NTS traffic is based on EBC evolution principles: exit POCs used for charging will be identified from the routing plans.

  35. EBC Evolution NTS Two new “planning” files RPD to identify exit POCs Planning files used to determine where to collect NTS traffic at least cost, update routing plans RPD to identify exit POCs Two new NTS charging files NTS: using EBC Evolution

  36. INCA/CLI NTS and EBC Evolution, detail • This presentation deals solely with identification of EBC charge bands • OLO-BT-OLO Transit, representation as currently, change to method of identifying exit POC. • EBC charge band is cheapest connectivity path from entry POC to the agreed exit POC identified in the routing plans for that entry POC and the destination number range

  37. INCA/CLI NTS: BT-OLO traffic • Two new EBC Files: • Destination number, linking key • Origin number, linking key, charge band • The charge band represents the retention to be used when calculating the BT outpayment. • If CLI in BT range, a BT-originated charge band will identified; exit POC used from routing plans • If CLI is in a non-BT range a single “transit” charge band will be identified, corresponding to ONO retention.

  38. BT-OLO NTS: TWIX verification • GenIUS will provide TNOs with data showing for incoming-to-BT NTS transit traffic, amongst other things: • TNO NTS range • Entry POC • Time period • Number of calls starting in this time period • Number of minutes in this time period • TNOs may use the entry POC and NTS range with the “normal” EBC matrix to verify the TWIX charged by BT.

  39. NTS and timeliness of POC inclusion in EBC • The use of the Routing Plan System reduces EBC build time. • Two new EBC files should reduce OLO EBC timescales. • In order to reduce time lag for POC changes to be reflected in charging data BT proposes a monthly EBC as this is now practical.

  40. EBC Workshop EBC related activities - CPL

  41. Key CPL Points from the EBC workshop Duplicate numbers EBC/CPL – different Operators Oftel and BT number range data synchronisation Historical CPL data on web site CPL Guidance Process for mid-period rate changes Browsable / Downloadable CPL Synchronization Process document for the CPL Relationship between bill references and BT products

  42. Completed and Planned Activities Audit of number ranges Timeliness of updates Notification of price changes Standardising formats in CPL entries Extra guidance and written process Price change registration Web site development

  43. EBC Workshop EBC Related Activities -Update

  44. EBC Workshop Summary & Close

  45. EBC Solution - Summary • Routing Plan Database • New Output Files • NTS alignment with the EBC Solution • Other Activities • CPL • NIPP • Communicate progress on delivery • Extend the principle to other developments

More Related