Professional Documents
Culture Documents
MLLN and Non MLLNN
MLLN and Non MLLNN
MLLN OVERVIEW
(E3-E4 E&WS)
23-03-11
AGENDA
Introduction to MLLN
MLLN Hardware configurations
TVARIT
What is MLLN?
The MLLN is a Managed Leased Line Network system,
which can provide leased line connectivity.
MLLN is capable of supporting two type of leased line.
1.Point to Point Circuit
2.Point to Multi Point Circuit
Bandwidth of a Managed Leased Line can be 64Kbps or
n x 64 Kbps up to a maximum of 2Mbps.
The MLLN comprises of the following building blocks
1. Digital Cross Connect (DXC)
2. Versatile MUltipleXer (VMUX)
3. Network Termination Units (NTU)
4. Network Management System (NMS)
MLLN Features
The MLLN is an integrated, fully managed, multi-service
digital network platform , through which service
providers can offer a wide range of services at an
optimal cost to Business Subscribers .
Using the NMS, with powerful diagnostics and
maintenance tools, the MLLN can provide high-speed
leased lines with improved QOS (Quality of Service),
high availability and reliability.
MLLN Advantages
24 Hours performance monitoring of the circuit
Circuit fault reports generated proactively
On demand the bandwidth can be increased
Low lead time for new circuit provisioning
Protection against the failure of the circuit
Long drive on single pair copper wire
Centrally managed from ROT connected to the Network
Management System
Central Node
2nd Stage
3 rd Stage
Installed at Secondary
switching Area (SS-DXC)
VMUXs are also installed
for circuit provisioning
13
DXC Architecture
X-Bus Cable
E1
Interfaces
E1
Interfaces
Slave1
Slave2
Slave8
E1
Interfaces
Slave7
E1
Interfaces
Slave6
E1
Interfaces
Slave5
E1
Interfaces
Cluster
Master
E1
Interfaces
E1
Interfaces
Slave3
Slave4
C-Bus Cable
14
VMUX Architecture
-48v BUS
-48V DC
PFU-A
NTU
Interfaces
OMH-HCO
NTU
Interfaces
OMH-HCO
NTU
Interfaces
OMH-HCO
XCG
QMH-G703
E1
Interfaces
QMH-G703
E1
Interfaces
X-BUS
16
VMUX-1
VMUX-2
VMUX-1
BLOCK-1(E1)
VMUX-1
BLOCK-2(NTU)
VMUX-2
BLOCK-1(E1)
DDF-1
DDF-2
VMUX-2
BLOCK-2(NTU)
VMUX-3
BLOCK-1(E1)
VMUX-3
BLOCK-2(NTU)
VMUX-3
3 in 1 Rack
Front View !
No modification
allowed here
17
N*64K
E1
VMUX Type-I A
40
12
VMUX Type-2 A
24
16
16
18
CTU-S
CTU-R
iii) Diagnostic
NTU Connectivity
DXC
Trunk
642240 Kbps
P
F
U
A
CTU-S
O O
M M
H H
H H
C C
O O
O
M
H
H
C
O
VMUX
M
H
G
7
0
3
X
C
G
Trunk
CTU-S DTE Interfaces
V.35, V.36, X.21,G.703
CTU-R
642240 Kbps
P
F
U
A
21 9 1 52 4
7
32 11 71 22
9
54 10 91 62
83
6 1 82
20 0
-
95
61
1 72
01 8
3
1 4
20
is
possible
to
manage
the
entire
network
Network Plan
1.
2.
3.
Nomenclature
DXCs at metros (Delhi, Mumbai, Kolkata & Chennai) four
maintenance regions are designated as Regional DXCs (R-DXC).
DXCs of maintenance regions apart from Regional DXCs as above
are called sub-regional DXCs (SR-DXC).
DXCs in the SSAs will be called SS-DXC.
Multiplexers will be designated as VMUXs
Remote Operator Terminals will be called ROTs.
Connectivity
Various types of connectivity will be required to be established in
the network which are explained in the next slides.
The size of connectivity described is for initial set up only.
Additional capacities can be added by the BSNL officials when
ever situation arise
Redundancy Requirements
MLLN has to provide high reliability service and it proposed to offer
SLA for 99.5 % or better efficiency. Therefore, all the E1 links
should be provided as rings wherever available.
In long distance network, E1 between same stations can be split
into alternate physical path of rings to the extent feasible.
50002
50003
50004
50005
VMUX-II
VMUX-II
VMUX-II
VMUX-II
VMUX-II
RTTC Ahmedabad
RTTC Bhubaneshwar
RTTC Chennai
RGMTTC Chennai
RTTC Guwahati
VMUX ALTTC
VMUX-II
50011
50014
60001/60002
RTTC Mysore
VMUX-II
RTTC Rajpura
500
VMUX-II
DXC-64P
50012
BRBRAITT Jabalpur
RTTC Nagpur
VMUX-II
RTTC Pune
50013
VMUX-II
50015
RTTC Ranchi
VMUX-II
50016
RTTC
Thiruvananthapuram
VMUX-II
VMUX-II
VMUX-II
VMUX-II
VMUX-II
RTTC Hyderabad
RTTC Jabalpur
RTTC Jaipur
RTTC Kalyani
RTTC Lucknow
50006
50007
50008
50009
50010 24
TVARIT USERS
As per Workflow, the users are :
Commercial Officer ( CO_cityname)
Accounts officer ( Aocash_cityname)
Nodal Officer ( NO_cityname)
Ld users ( LD_WTR/NTR/ETR/STR)
LD_Region_Dgmm_Station
SDEMUX_station
Admin User
CGM / GM / DGM / CIRCLE
FEATURES
UNIQUE-ID Generation for each leased circuit
X X X X / X X XXX /
X X
/ X X X X
LLA-STDCODE / SERIAL NUM / CKT CODE / LLB-STDCODE
( Total 15 Digits )
Generates Advice note / Demand note for new registration
Keeps track of progress of provisioning of the circuit till
it is commissioned
Cancellation / Shifting
R & G circuit provisioning
Generates Accounting information and reports
Migration of existing circuits
Issue of recurring bills (Annual or quarterly)
Provides cost estimator for rough estimates to the subscriber
All the transactions can be viewed by the user at any time.
Tariff changes can be incorporated immediately.
For 5 digit SDCA code, for JKLMN = 00001 to 99999, the circuit
number will be
ABC#/JKL/XY/EFGH
CO
Registration
Payment
AO (cash)
Issue of prov
advice/demand
note
Feasibility
LLA
A end
CO
Feasibility
Feasibility
REGION
LD
Payment of prov
demand note
AO (cash)
Issue of final
advice/demand note
CO
LLB
B end
NO
TASKS of CO
New registration /
Migration
Issue of provisional / final
advice note
Issue of provisional / final
demand note
Shifting / Cancellation / deallocation
User administration
Commissioning of circuits
MIS Reports
ADDITIONAL REPORTS
Closure /Cancellation
Co_LLA will initiates the process click on Cancellation
request)
Co_LLA Issues the cancellation request to the concerned
users ie.
Both Nos, LDNos/LD concerned will give the
expenditure incurred if
any, on the circuit.
Once expenditure report is received, CO will issue the
cancellation demand note/advice note.
Nos and LD will disconnect the circuit and deallocate the
channel.
Billing & accounting
Generates recurring bills
Quarterly/Yearly
Customized Billing
Accounting
Sub-ledger records
Service tax report
Revenue outstanding
others