MICROWAVE NETWORKS

DCN DESIGN
DCN capacity dimensioning

DCN Bandwidth
Theoretical speed of downloading a 10 MB SW package*
Minutes
Minutes
25
25
20
20

20,8
20.8

15
15

Factor 200

10
10

6,9

6.9

55
2,3
2.3
0
0

Page 1

64 kbit/s

E0

192kbit/s
DCCR

576kbit/s
DCCM

64kbit/s

192kbit/s

576kbit/s

0,7
0.7
E1

0,1
0.1
10 10mbit/s
BaseT

2Mbit/s

10Mbit/s

2mbit/s

DCN channel

DCN bandwidth
Different DCN traffic :
Background keep alive traffic
Management sessions
- Software download
- Configuration
Alarms report
Engenering Order Wire ( service telephone)
if used between OMC and nodes

Page 2

OMC

Background keep alive traffic

A keep alive message is changed between OMC manager station and each NE
at regular intervalls.
The interval time between two consecutif request 1000 sec.
Depending to network size and Configurable in the management
OMCstation
From OMC to NE:
SNMP Get
payload = 300Byte = 2400bit
From NE to OMC:
SNMP Keep alive
payload = 300Byte = 2400bit
Average background BW [b/s] =
where:
n = number of NE
t = polling interval [sec]
Page 3

n x payload
t

Background keep alive traffic

Example

n x payload
Average background BW [b/s] =
t
where:
n = number of NE = 100
t = polling interval [sec] = 1000 sec to each NE

Average background BW =

100 x 2400
1000

Average background BW = 240 b/s

in each direction.

Page 4

Management sessions
O&M payload

Management station NE
Single parameter change
Single parameter view (FM/PM)
Single parameter view (other)
Multi parameter view (FM/PM)
Sofware upgrade single M-L TN

Page 5

M-L TN
5 15 kB
300 Byte
5 15 kB
550 Byte
9 12 MB

http
SNMP
http
SNMP
ftp

Management sessions
Response time / DCN BW

Required DCN BW depends on payload size, acceptable response time,

and number of simultaneous sessions.
Assumption for acceptable response time:
Software upgrade
approx. 10 min.
All other activities
approx. 2-3 sec.
These assumption will lead to the following BW requirements:
Software upgrade (payload up to 12 MB)
128 kbit/s
All other activities (payload up to 15kB)
32 kbit/s
Note: this is per session but for configuration and view activities
there will in practice be a statistical gain leading to less than 32 kbit/s
per session in a multisession scenario.

Page 6

Alarm BW
Worst case for alarm burst will be a performance
degradation to a hop that will impact all
southbound hops in the cluster.
Maximum required BW from a cluster to
the OMC can be estimated by the following formula:
Alarm BW [b/s] =

(n +(m x 4)) x o x p
t

where:
n = number of affected E1
m = number of affected radio hops
o = factor for lossed alarms (01)
p = alarm payload (365Byte = 2920bit)
t = duration of alarm peak (10sec or more)
Page 7

OMC

Feeder

Alarm BW, example

The feeder to the cluster is disturbed.
Each node terminates 2 E1
80% of the alarms are expected to reach the OMC
the alarm peak is estimated to last 10sec.
What is the required BW towards the OMC?
Alarm BW [b/s] =

OMC

(n +(m x 4)) x o x p
t
Feeder

Alarm BW [b/s] =

(40 +(20 x 4)) x 0.8 x 2920

Alarm BW = 28.032kbit/s

Page 8

Alarm BW?

10
20 affected nodes
= radio hops

EOW
Engineer order wire, Service telephone

In IP based DCN the EOW is realized with VoIP over regular DCN channels.
The service is generally not critical for BW but is a real time critical service
and puts thereby restrictions to other simultaneous sessions (SW download).
EOW BW : n x 20 kbit/s (per direction)
where n = number of simultaneous EOW calls
over the IP segment.

The BW available for SW download ftp sessions can need to be

restricted to allow the EOW service to work properly.

Page 9

DCN capacity vs direction

Dimensioning factors
Downlink (OMC to NE)
SW upgrade session
Uplink (NE to OMC)
Alarm

OMC

Alarm

Page 10

SUG

Page 11