Introduction

1
Introduction Welcome  
2
Objectives

• What we are going to do today?
• Review of EBC concepts
• Establish how EBC will be calculated for the
  following
• BT terminating
• BT Originating
• Transit
• Continued Local Exchange Segment Charging
• Use of the EBC Evolution Planning Files and NIPP

3
Agenda

• 1000 Introduction Welcome
• 10.05 PSTN Interconnect in a 21CN world
• 11.00 Break
• 11.15 Continued Local Exchange Segment
• 11.45 Discussion on use of Planning Files
• 12.15 Review of Discussion
• 12.25 Any other questions
• 12.30 Summary Close
• 12.45 13.00 Lunch

4
 PSTN interconnect In a 21CN World 
5
Legacy PSTN interconnect in the 21CN principles

• Maintain BT revenue status quo in line with the
  NCCN regime
• Legacy PSTN interconnect will continue to attract
  an EBC-based charge
• CPs will not be disadvantaged by legacy network
  changes as a result of BTs 21CN

6
Legacy PSTN interconnect in 21CN EBC concepts

• BTs internal connectivity will be frozen prior
  to 21CN rollout
• Call charging will be mapped to this frozen
  network model
• CP / BT connectivity will be dynamic EBC will
  continue to use agreed routeing plans to identify
  exit POC
• BT numbering will be dynamic, mapped to frozen
  DLE areas
• CP numbering will be dynamic in line with
  routeing plans

7
Legacy PSTN interconnect in 21CN EBC CP view

• No change to EBC file formats
• No change to publication frequency
• No new EBC charge bands
• Additional EBC file, to assist connectivity
  planning, showing how BT maps number ranges to
  frozen data
• Current plan is for bespoke CP EBC (BT
  terminating) matrices representing agreed LES
  override for CP migration from DLE to NGS

8
EBC models

• Those legacy interconnect call types subject to
  EBC are
• BT-terminating
• BT-originating
• Transit (sender pays TWIX)
• Transit (recipient pays TWIX)

9
Current EBC structure (internal) BT Terminating
10
Current EBC structure Transit and BT originated
11
 Any Questions? 
12
Legacy interconnect in 21CN EBC and BT
terminating

• The BT connectivity matrix prior to 21CN rollout
  will be kept static.
• This will be used as the core from which EBC
  charging data is constructed for all call types.
• BT terminating calls are simply charged according
  to the static connectivity between POC and legacy
  DLE.
• Legacy DLE will be identified from (current) BT
  number range using mapping process.

13
Legacy interconnect in 21CN treatment of number
ranges 1

• List of DLEs prior to 21CN kept static.
• Each DLE has retarded BT range associated,
  minimum NNG level
• Retarded Number Str. Parent Exchange NNI
• -------------------- -------
• 01473 0973102
• 014731 0973004
• 014732 0973067
• 0147323 0973004
• 01473237 0773116
• Each time an EBC data set is built, live BT
  ranges mapped to legacy DLE

14
Legacy interconnect in 21CN treatment of number
ranges 2

• New NNGs (e.g. 0203) will not match to retarded
  ranges
• If physically on a DLE the NNG ranges will be
  added to the static DLE data
• If physically on 21CN
• Assign the DLE closest to the retail charge point
  (NNG centre of gravity), or
• Create a logical Pseudo DLE covering NNG area,
  charging to be the cheapest of all DLEs in this
  area for the origin/destination in question. This
  then added to the static DLE and connectivity data

15
Legacy interconnect in 21CN routeing plans

• Routeing plans are used in EBC charging for
  transit and BT-originated traffic. The EBC charge
  band is the lowest cost connectivity path between
  the origin and the POC in the routeing plans
  agreed for that origin.
• CP number ranges in routeing plans may have
  legacy PSTN POCs or 21CN POCs.
• PSTN exit POC current format, PSTN catchment
  areas
• 21CN exit POC 21CN catchment or PSTN catchment
  (prior to 21CN origin)
• 21CN entries may be converted to legacy 21CN
  exit POCs will have associated NGSs (trunk
  catchment area). Where a PSTN catchment is not
  specified we will use the cheapest appropriate
  PSTN area.

16
Mapping 21CN entries in routeing plans to legacy
17
 Break 
18
Sender-pays-TWIX transit

• If the TCP has requested a PSTN POC then the
  charge band will be derived as today using the
  static BT connectivity data
• If the TCP has requested a 21CN exit POC
• Specifying PSTN catchment areas the EBC charge
  is that to get to the NGS associated with the
  21CN POC which results in the cheapest charge
• Specifying 21CN catchment areas (i.e. no PSTN
  entry) missing PSTN catchment areas will be
  created, with the charge from each the cheapest
  to get to any NGS associated with the 21CN POC.

19
Sender-pays-TWIX transit
20
Recipient-pays-TWIX transit

• Applies to 0845-type NTS, 118 services and GNPT.
• Reciprocal arrangement as sender pays TWIX
• The legacy PSTN entry POC used for charging the
  TCP will be the POC shown in the NTS transit
  statistics file for TCP verification (the TCP has
  no other source of identifying the entry POC).
  There is no analogy for 118 or GNPT CPs today
  do not know the entry POC.

21
Recipient-pays-TWIX transit
22
BT-originated EBC charging

• CPS, 1xxx IA, NTS and 118 services have an EBC
  charge band assigned for BT-originated traffic if
  the TCP has legacy PSTN interconnect
• The charge band will be identified using the same
  process as BT-originated, as to qualify for EBC
  charging the exit POC must be PSTN.

23
Number ranges

• As described earlier, live BT ranges mapped to
  legacy DLE via retarded numbers.
• CP numbers added to list of BT live ranges (with
  key into transit and BT-originated matrix data)
  and retardation process applied as today.
• BT will make available the BT retarded range to
  legacy DLE relationship to allow CPs to predict
  (in conjunction with the EBC planning file
  showing the charge between pairs of exchanges)
  how new number ranges will be charged and plan
  routeing accordingly.

24
Featurenet

• ASU (Featurenet) exchanges serve many
  geographically disparate NNGs.
• Featurenet (geographic) ranges are scattered
  amongst those hosted on the PSTN.
• The EBC connectivity matrix includes ASUs as one
  end of a charging path. The charge to an
  ASU-hosted range may be very different to
  DLE-hosted ranges in the same NNG due to the fact
  that the ASU may be geographically distant.
• Because of this featurenet ranges and exchanges
  cannot be included in the DLE mapping data
  (legacy DLE retarded BT range) or its use as
  spurious relationships would arise (PSTN ranges
  mapped to ASUs etc.)
• Parallel mapping data will therefore exist there
  will be a relationship between retarded
  featurenet ranges and ASUs, and live featurenet
  ranges will use this to allocate an ASU to be
  used for charging.
• This will then key into the static BT
  connectivity data via ASU.

25
VOIP and BBV

• VOIP ranges (055) and BBV ranges (056) are on two
  different platforms.
• EBC charges based on the connectivity path to get
  to these platforms.
• The static EBC data will contain stubs
  representing these platforms.
• Live VOIP ranges will be linked to the static VMP
  stub
• Live BBV (new services) ranges, including
  geographic ranges, will be matched to the
  Platform stub.
• This is possible as all the ranges are associated
  with a single platform no process is required to
  choose an associated exchange from a choice of
  many.

26
VOIP and BBV
27
Legacy interconnect (EBC) and Targeted Transit

• Legacy PSTN exchanges must be specified for entry
  and exit POCs, i.e. neither can be a 21CN POC.

28
Number Portability

• NGNP import to BT is not subject to EBC.
• NGNP export from BT will operate in the same
  manner as NTS (EBC charge based on agreed exit
  POC).
• GNP export from BT is not subject to EBC.
• GNP import to BT
• BT geographic prefixes are not retarded (they are
  not geographically organised). These and
  associated legacy DLE will remain static.
• Any new prefixes required for 21CN will be
  treated in the same way as a new NNG (closest
  exchange / logical exchange created covering area
  covered by the 21CN POC).

29
Points to note

• Virtual pairs will have been included in the
  static BT connectivity data
• (BT-originated) third party handover products
  using legacy PSTN POCs will operate as today
  using the static connectivity data

30
 Break 
31
 Continuation of Local Exchange Segment 
32
Continued LES charging

• The specifics of implementing continued LES
  charging have not been agreed
• the proposal below may change. Separate workshop
  to look at this.
• Two basic models, both of which use frozen EBC
  data.
• Partitioned routes at NGS
• Bundled routes
• There will be a lead time between ordering a
  virtual circuit and it in being used in EBC
• CP must select one option only
• Likely LES rate will apply for a whole month
• Separate proposals on VIEC and Port rental charges

33
Bundled Routes

• A CP will register one or more virtual DLE
  connections at an NGS these may be call type
  specific, but not route specific.
• Traffic using the NGS as a POC, to or from any of
  the above DLE areas will attract LES rate.
• For outgoing traffic the EBC data will be built
  showing LES rate for any originating DLE areas
  subject to the above arrangement.
• For BT-terminating traffic a bespoke matrix will
  be created for each CP. This will show LES rate
  for traffic delivered at an NGS destined for a
  DLE subject to the above arrangement.
• If insufficient virtual DLE connections have been
  purchased for the actual traffic volumes,
  mechanisms will be in place for BT to recover the
  appropriate costs.

34
Bundled Routes - Today
BT
CP
Route X
35
Bundled Routes - Tomorrow
BT
CP
Route X
36
Partitioned Routes at NGS

• A specific route at NGS will be associated with
  one or more DLE areas, to replicate a virtual DLE
  connection.
• The route may be call type specific e.g. NTS,
  IA, CPS
• Calls using this route will be charged as
  originating or terminating on frozen DLE areas.
• Outgoing traffic will have EBC data built using
  the cheapest of the network NGS POC and any DLEs
  associated with a specific route on this POC.
• Incoming traffic will be charged using bespoke
  CP-specific matrices, built assuming that traffic
  is delivered on the NGS route resulting in the
  cheapest charge.
• If a CP delivers traffic on the wrong route
  then the non-bespoke EBC matrix should be used
  for charging (LES rate will not be applied).
• This means CPs must use route as a key when
  verifying BTs bill.

37
Partitioned Routes 1 - Today
BT
CP
Route X
38
Partitioned Routes 1 - Tomorrow
BT
CP
Route X
Route Y
39
Partitioned Routes 1 - Tomorrow
Bespoke EBC file would show cheaper charge band
assuming route Z - LES
BT
CP
Route X
Route Y
Route Z
40
Partitioned Routes 1 - Tomorrow
Origin
Derived Origin
Destination
Charge Band
NGS A / Route Y
DLE A
0147321
LES
NGS A / Route Y
DLE A
0147322
DT
Bespoke EBC file would show cheaper charge band
assuming route Z - LES
BT
CP
Route X
Route Y
Route Z
0147321..
0147322..
0147322..
41
Partitioned Routes 2 - Today
BT
CP
Route X
42
Partitioned Routes 2 - Tomorrow
BT
CP
Route X
Route Y
43
Existing EBC Data Files
EBC File 21CN Changes
Incoming/Transit File Bespoke versions available
IA/CPS/118 File No changes
New CLI-based NTS Files No changes
Evolution Planning File 1 Exchange to Number Range Main file to include DLEs but not WATs Do CPs think bespoke versions should be made available?
Evolution Planning File 2 Exchange to Exchange ASUs (Featurenet), Platform, (BBV) and VMP (VOIP) will be shown Any new BT Pseudo exchanges will be shown
Exchange File Will additionally show ASUs, VMP, 21CN POCs ,Any BT Pseudo exchanges Do CPs think 21CN POCs should be shown for TCP pays NTS twix planning?
Non-EBC File No changes
EBC Band File No changes
Targeted Transit File No changes
Payphone Files No changes
44
New EBC File

• The Number Allocation File
• Will show static relationship between BT
  geographic number ranges and DLE/ASU areas
• Standard EBC file naming convention
  NAFltxxxgt.ltyyygt
• Standard EBC header and trailer records
• Data record format
• Retarded number range, Service Flag (P-PSTN,
  F-Featurenet), DLE/ASU NNI
• Example
• Name NAF033.001
• ALL NAF200510010000000000038
• 0207,F,1710001
• 0207,P,0912123
• 02071,P,0912456
• 02073,P,0912789
• 020734,P,0912999
• ALL 000000038000000724

45
NIPP

• NIPP shows BTs current and planned network.
• Operators may use this for route optimisation,
  but this will no longer be possible when static
  BT connectivity data is used.
• The planning files introduced with EBC Evolution
  must be used for planning any legacy interconnect
  with BT.

46
Discussion Topics

• What should be done with NIPP and planning files
  (overlap)?
• Currently assuming divorced from EBC charging as
  not frozen.

47
Summary

• NO SYSTEM CHANGES for usage
• Frozen EBC matrix
• Continuation of LES
• New EBC file
• Planning Files NIPP