IP/MPLS Physical Topology

On the basis of prospective subscriber density, these cities can be classified a

s follows:
PCC (Primary Core City) Total number x
SCC (Secondary Core City) Total number x'
TCC (Tertiary Core City) Total number x''
TT (Tertiary Town) Total number x"
IP/MPLS backbone will be formed by interconnecting these cities in a hierarchica
l fashion over underlying transport such as DWDM, Dark Fiber, Microwave Radio (M
WR), wherever it is appropriate. Within each city, MEN with appropriate hierarch
y of rings shall ensure the backhaul of all eNodeBs traffic. Basically, each cit
y will have its central PoP aggregating MEN rings within that city. The structur
e (and also number) of city central PoPs shall vary depending on the significanc
e of the city (with reference to subscriber density)
Transport and Routing Requirements
1) Choice for underlying transport can be dark fiber or DWDM/ASON.
2) The physical topology can be ring or mesh.
3) All the PoP sites need to be in the mesh topology.
4) Every PoP location should have a minimum of three entry/exit points to h
ave multiple fiber cut redundancy.
5) Secondary/layer 3 PoP location needs to be in the ring/mesh network.
6) Commonality in physical routes should be avoided as far as possible.
7) BER should be 10E-15 for 10G/40G/100G.
8) Various types of protection techniques need to be explained at the trans
port and control plane level along with their switching/restoration time.
9) Router interface requirements:
· ECN/EAN routers with 1/10/40/100GE support
· ESN routers with 1/10GE support
· PCC/SCC central PoPs with 1/10/40/100GE support
10) Logical topology architecture (control plane and control protocols) should
be discussed in the design:
· Interior Gateway Protocol (IGP): IS-IS (with justification)
· MPLS: LDP/RSVP protocols,
· BGP: IPv4/VPNv4 route reflectors
11) QoS model shall support 4 numbers of CoS in the core.
12) High availability network design shall include:
· In-service software upgrades (ISSU),
· Non-stop routing,
· Non-stop service and graceful restart helper mode,
· MPLS FRR, BFD, VRRP,
· Multi-chassis LAG and multi-chassis synchronization (MCS),
· Control plane management and service verification, and
· Proactive SLA testing.
13) LTE backhaul shall support Layer 3 MPLS VPN as the first option and L2/
L3 MPLS VPN as the second option.
14) The design shall recommend the protection techniques for various QoS.
15) The design shall recommend the appropriate switching mechanism to be us
ed.
16) IP core network architecture for inter-circle VoIP traffic along with b
andwidth (Lambda requirement) between all 22 circles shall be covered.
17) End-to-end delay for voice and video calls shall be less than 60 ms. Tr
ansport and IP network shall satisfy this criterion.
18) Physical topology shall specify DWDM and ROADM locations and reasons fo
r selecting those locations.
19) Transport network design for data-center to data-center and CDN-to-CDN conn
ectivity shall be mentioned.
20) Instead of adding and dropping lambda, data traffic add-drop based on VLAN
or MPLS-tag shall be considered in design.
21) Migration of protection mechanism to WSON shall be mentioned very clearly.