For Consult21 use
briefing: C21-NS-004
Draft A, 29 April 2006
April 2006
Issued by: Tim Wright
Issue No: Draft A
Date: 11 May 2006
Page 1 of 16
For Consult21 use

For Consult21 use
Page
About this draft …
Draft A of the NIP comprises this top-level framework document only without the Annexes. The
Annexes will be made available in Draft B, currently scheduled for end May
Issued by: Tim Wright
Issue No: Draft A
Date: 11 May 2006
Page 2 of 16
For Consult21 use

For Consult21 use
This is a top-level framework document on information for use by CPs on BT ’s next generation network in the UK. The detailed information is published in a series of Annexes that will be periodically updated.
This document and its Annexes are referred to as the Network Information Publication (NIP). The purpose of the NIP is to provide CPs with information about BT’s network that CPs need to assist in their interconnect and deployment planning. The NIP is owned and produced by BT although its scope and level of detail has been steered by CPs under Consult21. The NIP will develop over time as the design and deployment of the BT NGN in the UK proceeds.
It is expected that the NIP data will be commercially relevant to CPs and might be referenced from new contracts for MSILs / NGN interconnect, etc in a similar was as the existing NIPP is used by SIA.
The NIP is the next generation equivalent of the existing Network Information Publication Principles
(NIPP) and recognises the multi-service nature of NGNs.
The NIP is in four main parts
1. Publication principles (contained in this framework document) – This covers the ownership, authority, update frequency, systems support (if any), distribution and access arrangements, etc of the NIP.
2. Network design and support of traffic types (given in outline in Section 3 and in detail in Annex
A) - This part describes the functional nodes, their generic names (eg Metro Node). It shows the signalling and media flow protocols. It gives a view of the resilience between each level of the topology for each network layer. It shows the functions for each type of functional node and, where appropriate, the mapping of functions into equipments. It shows topologically the points of handover. It also gives a view of how the media flows of the various traffic types are handled. It includes the entity model - ie the generic data model for describing the relationships between PoPs and functional nodes. This is relatively stable information. The first draft draws heavily on the material BT presented to CPs at the Network Design Event on 3 April 2006 and focuses on PSTN voice (although not exclusively). Future issues will be more comprehensive and will be more specific about how the various products are supported.
3. Network inventory (given in outline in Section 4 and in detail in Annex B) - This part lists the locations of the various types of functional nodes. It lists the PoP 1141 codes and the 1141 codes of the functional nodes (eg Metro, Tier 1 MSAN) located within the PoPs. It ensures consistency of these codes across the product areas. It will provide mappings of concentrators to DLEs, concentrators to MSAN, DSLAMs to MSANs, concentrator number ranges, MSAN type (ie Tier 1 or not), MSAN to primary Metro, MSAN to secondary Metro, Metro to NGS. It provides the service capabilities at the various locations. It also gives the various 1141 codes from which the postal addresses can be derived from the NISCC web site. The first draft draws heavily on the deployment plan issued by BT. The latest version of the deployment plan has reflects the new priorities and includes both broadband and PSTN migration. This part will be up-issued frequently
(possibly even monthly in the early days) as traffic grows, as new nodes are deployed, as nodes get reparented, as new points of handover are opened, etc.
4. Numbering and service addressing (given in outline in Section 5 and in detail in Annex C) – This part is the NGN equivalent of that part of the existing NIPP that essentially provides a matrix of
PSTN/ISDN number groups against actual interconnect locations. So, if a caller dials a number, the call will be routed to the defined interconnect location for handover. The data is derived from the Network Charge Data Base and is the basis of Element-Based Charging. CPs currently make use of this information to help plan and cost optimise their networks. This part has not yet been scoped. It is noted that, in an IP world, call routing will be different and some aspects of this are currently under consultation.
Issued by: Tim Wright
Issue No: Draft A
Date: 11 May 2006
Page 3 of 16
For Consult21 use

For Consult21 use
BT own the content of the NIP and will update it as necessary. Responsibility for updating the NIP rests with [John Baughan + contact details - to be confirmed]
The NIP will be made available free of charge to CPs that have or plan to have points of handover to
BT’s NGN. The NIP will be published on a number of web sites with access security mechanisms.
Requests for the access should be made to [BT contact details - to be provided].
Although the NIP is published in good faith, BT cannot accept liability (whether due to negligence or otherwise) for loss arising as a result of reliance upon any of the information it contains.
Issued by: Tim Wright
Issue No: Draft A
Date: 11 May 2006
Page 4 of 16
For Consult21 use

For Consult21 use
[Taken from the Network Design Event held on 3 April 2006]. Greater detail is given in Annex A.
References to the relevant NICC ND documents will be given in Annex A.
3.1.1 Points of Presence
The types of PoP and relationship with functional nodes is shown below.
3.1.2 Basic network topology
The basic physical topology is shown below.
3.1.3 Network inventory data model
1141 codes are used as the single location identifier for 21CN physical PoPs and the functional nodes
(eg CMSAN, Metro) located within the PoPs.
[Taken from Slides 32 to 56 of the Network Design Event]
Issued by: Tim Wright
Issue No: Draft A
Date: 11 May 2006
Page 5 of 16
For Consult21 use

For Consult21 use
The MSAN physical PoP types and the connectivity back to the parent Metro Node is shown below.
There are three types of MSAN physical PoPs:
1. Copper MSAN physical PoP

Provides copper line drive and switching/aggregation functions.

The backhaul transmission is SDH with Ethernet traffic encapsulated within GFP (Generic
Framing Protocol) and protected using either SNCP or higher layer protection.

Dual parenting to Fibre Access or WDM Access nodes unless impractical
2. Fibre MSAN physical PoP

Provides fibre/copper line drive and switching/aggregation functions.

The backhaul transmission is SDH with Ethernet traffic encapsulated within GFP (Generic
Framing Protocol) on dual homed routes.

Ethernet traffic encapsulated in GFP is protected using either SNCP or higher layer protection.
3. Tier 1 MSAN physical PoP (Also known as WDM MSAN physical PoP)

Provides WDM transmission functions, fibre/copper line drive and switching / aggregation functions to two Metro Nodes.

Ethernet traffic will be back-hauled using Gigabit Ethernet over CWDM (or DWDM if capacity demands) to the Metro node.

Ethernet LAG (Link Aggregation) is used for protection of Ethernet transported traffic.
[Taken from Slides 57 to 67 of the Network Design Event]
There are three types of Metro/Core physical PoPs:
1. Inner core physical PoP

8 PoPs

2 to 4 PoPs with direct Internet access

Fully meshed – 10Gbit/s links

Transmission layer resilience

Full service functionality (Ethernet, voice, broadband, TDM leased lines)

2 to 4 NMCs
2. Outer core physical PoP

12 PoPs

Triple parented or more off Inner Core

Partially meshed - 10Gbit/s links

Some sideways links

Transmission layer resilience

Full service functionality at most PoPs
3. Metro physical PoP
Issued by: Tim Wright
Issue No: Draft A
Date: 11 May 2006
Page 6 of 16
For Consult21 use


86 PoPs

Dual parented to core – 10Gbit/s links

Transmission layer resilience and MPLS FRR to Core

Some service functionality
The service components contained in an Inner Core physical PoP are shown below.
For Consult21 use
BT
’s Current
[Taken from Slides 70 to 76 of the Network Design Event]
The logical design for voice (PTSN emulation, customer VPN, internet voice) and multimedia services is shown below. All voice is supported as VoIP.
[Taken from Slides 77 to 96 of the Network Design Event]
Some examples are shown below
Issued by: Tim Wright
Issue No: Draft A
Date: 11 May 2006
Page 7 of 16
For Consult21 use

3.5.1 Voice
An NGN on-net call (to and from same CMSAN) is shown below.
For Consult21 use
An NGN to legacy PSTN call is shown below.
A voice IP interconnect is shown below. This is still subject to consultation.
Issued by: Tim Wright
Issue No: Draft A
Date: 11 May 2006
Page 8 of 16
For Consult21 use

For Consult21 use
3.5.2 Broadband IP access
A broadband IP traffic flow from BT NGN BRAS to the BT Internet Network is shown below.
3.5.3 Ethernet
Examples of a number of end user Ethernet flows are shown below.
Issued by: Tim Wright
Issue No: Draft A
Date: 11 May 2006
Page 9 of 16
For Consult21 use

For Consult21 use
3.5.4 TDM
An example of TDM circuits with aggregate presentation is shown below.
Examples of multi-service points of handover are shown below.
Issued by: Tim Wright
Issue No: Draft A
Date: 11 May 2006
Page 10 of 16
For Consult21 use

For Consult21 use
Issued by: Tim Wright
Issue No: Draft A
Date: 11 May 2006
Page 11 of 16
For Consult21 use

For Consult21 use
[Drawn from the network migration plan] The detail is given in Annex B.
This part lists the locations of the various types of functional node and the mappings between them. It provides the service capabilities at the various functional nodes. The scope of the various mappings is shown below. i-Node (secondary) i-Node (primary) Metro Node (primary)
Metro Node (secondary)
NGS (1) NGS (2)
Mappings between Metro Node and PoP 1141 codes and between i-Node and PoP 1141 codes are [to be held] in NISCC. Mappings of PoP 1141 codes to postal addresses are also [to be held] in NISCC.
These mappings draw heavily on the deployment plan [to be] issued by BT [in early May 2006]. This version of the deployment plan reflects the new priorities and includes both broadband and PSTN migration. This part of the NIP will be up-issued frequently (possibly even monthly in the early days) as traffic grows, as new nodes are deployed, as nodes are re-parented, as new points of handover are opened, etc.
Issued by: Tim Wright
Issue No: Draft A
Date: 11 May 2006
Page 12 of 16
For Consult21 use

[not yet scoped
For Consult21 use
Issued by: Tim Wright
Issue No: Draft A
Date: 11 May 2006
Page 13 of 16
For Consult21 use

For Consult21 use
3GPP
ACGF
ADM
ADQ
3rd Generation Partnership Project
Access Gateway Control Function
Add-drop Multiplexer [SDH]
Application-Driven Quality of service
ADSL
ASP
ATM
AWDM
BCM
BF
BFD
BGW
BRAS
BSS
BWM
CG
[BT]
Asymmetric Digital Subscriber Line
Application Service Provider
Asynchronous Transfer Mode
Access WDM
Business Continuity Management
Border Function
Bidirectional Forwarding Detection
Border Gateway
Broadband Remote Access Server
Business Support System
BandWidth Manager
Customer Gateway
CMSAN Copper Multi Service Access Node
COTS
CP
Commercial Off-The-Shelf
Communications Provider [BT]
CS
CSH
Call Server
Customer Sited Handover
C-VLAN Customer (inner) Virtual Local Area
Network
CWDM Coarse Wavelength Division
Multiplexing
DA
DASS
DB
DCN
Directory Assistance [BT]
Digital Access Signalling System
Data-Base
Data Communications Network
DLE
DNS
DPI
DPNSS
Digital Local Exchange [BT]
Domain Name System/Server [IETF]
Deep Packet Inspection
Digital Private Networking Signalling
System
Digital Subscriber Line
Digital Subscriber Line Access
DSL
DSLAM
DWDM
Multiplexer
DU LL ret Downstream Unsolicited Liberal
Label retention
Dense Wavelength Division
Multiplexing
DXC
E1
EEA
ENUM
EOI
ETSI
Digital Cross-connect
{Europe} 1 [ITU-T]
Ethernet Edge Aggregator
Electronic NUMbering
Equivalence of Input
European Telecommunications
Standards Institute
FMSAN Fibre Multi Service Access Node
FNET FeatureNet [BT]
FRR
FW
Fast Re-Route [MPLS]
Fire Wall
GbE
GE
Gigabit Ethernet
Gigabit Ethernet
Issued by: Tim Wright
Issue No: Draft A
Date: 11 May 2006
GFP
GR
HSS
HTTP
IC
ICT
IEEE
IETF
IMS
IN
INAP
IP
IPv4
IPv6
ISDN
ISH
ISP
ISUP
ITU
IUP
IVR
LAC
LAG
LAN
LDP
LL
MAC
MDF
MF
MGW
MM
MNO
MPLS
MS
MSAN
MSIL
NGN
NGS
NICC
NMC
NTE
OA
OAM
OCP
OSPF
OSS
P
PBT
Generic Framing Procedure
Graceful Restart
Home Subscriber Server
HyperText Transfer Protocol
Interconnect
Information and Communication
Technology
Institute of Electronic and Electrical
Engineers [USA]
Internet Engineering Task Force
IP Multimedia Subsystem
Intelligent Network
Intelligent Network Application
Protocol [C7]
Internet Protocol [IETF]
Internet Protocol Version 4 [IETF]
Internet Protocol Version 6 [IETF]
Integrated Services Digital Network
In Span Handover
Internet Service Provider
Integrated Services User Part [C7]
International Telecommunications
Union
Interconnect User Part [C7]
Interactive Voice Response
L2TP Access Concentrator [Cisco]
Link Aggregation
Local Area Network
Label Distribution Protocol [IETF]
Liberal Label
Medium Access Control
Main Distribution Frame
Multi-Frequency
Media Gateway
Multimedia
Mobile Network Operator
Multi-Protocol Label Switching [IETF]
Media Server
Multi-Service Access Node [BT]
Multi Service Interconnect Link
Next Generation Network
Next Generation Switch [BT]
Network Interoperability Consultative
Committee
Network Management Centre
Network Termination Equipment
Operator Assistance [BT]
Operations Administration and
Maintenance
Other Communications Provider [BT]
Open Shortest Path First protocol
[IETF]
Operational Support System
Provider (router)
Provider Backbone Transport
Page 14 of 16
For Consult21 use

For Consult21 use
PBX
PC
PDA
PDH
PE
PoP
POTS
PPC
Private Branch Exchange
Personal/Portable Computer
Personal Digital Assistant
Plesiochronous Digital Hierarchy
Provider Edge
Point of Presence
Plain Old Telephony Service
Partial Private Circuit
PPP
PPPoA
PPPoE
PSTN
PSU
PTA
PWE3
Point-to-Point Protocol [IETF]
Point-to-Point Protocol over ATM
Point-to-Point Protocol over EtherNet
[IETF]
Public Switched Telephone Network
Power Supply Unit
PPP Termination and Aggregation
Pseudo Wire Emulation Edge To
RCU
RDB
RFC
RIDE
ROMES Rationalisation Of Mobile Escalation
Sites [BT]
RR
RSVP
Edge Router
Remote Concentrator Unit
Routing Data Base
Request for Comment [IETF]
Recorded Information Distribution
Equipment
Route Reflector
Resource ReSerVation Protocol
[IETF]
SBC
SDH
SDP
Session Border Controller
Synchronous Digital Hierarchy [ITU-
T]
Service Delivery Platform [BT]
SDXC
SIP
SIP-I
SME
Synchronous Digital Cross Connect
Session Initiation Protocol
SIP with encapsulated ISUP
Small Medium Enterprise
SMP
SNCP
SPoF
SPR
Significant Market Power
Sub-Network Connection Protection
[SDH]
Single Point of Failure
Signalling Point Relay
SS7
STM-n
Signalling System No. 7 [ITU-T]
Synchronous Transport Module
(level) n [SDH]
Signalling Transfer Point [ITU-T] STP
S-VLAN Service (outer) Virtual Local Area
Network
TDM
TE
Time Division Multiplexing
Traffic Engineering
TISPAN Telecommunications and Internet
Services and Protocols for Advanced
Networks
TMF
TSR
URU
VAGW
TeleManagement Forum
Telecom Strategic Review [Ofcom]
“You are you”
VC-n
VIC
VLAN
VoIP
Virtual Access Gateway
Virtual Container (level) n [SDH]
Virtual Interconnect Circuit [BT]
Virtual Local Area Network
Voice over Internet Protocol
Issued by: Tim Wright
Issue No: Draft A
Date: 11 May 2006 vPE
VPN
VTGW
WDM
WES-B
WiFi
WiMAX xDSL
Voice Provider Edge Router
Virtual Private Network
Virtual Trunk Gateway
Wavelength Division Multiplexing
Wholesale Extension Service
Backhaul {BT]
Wireless Fidelity
Wireless Metropolitan Area X?
[WiMAX Forum]
ADSL, HDSL, SDSL, VDSL, etc.
Page 15 of 16
For Consult21 use

For use under Consult21
Issue No
Draft A
Date Author
11 May 2006 Tim Wright
Comments
Any comments relating to this document should be addressed to: tim.c.wright@bt.com
01977 594832
Issued by: Tim Wright
Issue No: Skeleton
Date: 29 April 2006
Page 16 of 16
For use under Consult21