0 Dimensioning Rules
2008-08-29
2008-08-29
ii
Table of Contents
2.1 Node B V100R010 Macro Node B BTS3812E/BTS3812AE .................................................................................6
2.1.2 Transport Module Configuration ................................................................................................................9
2.1.3 Baseband Subsystem Configuration ..........................................................................................................11
2.1.4 RF Subsystem Configuration .....................................................................................................................12
2.1.5 Control Subsystem Configuration .............................................................................................................13
2.1.6 BTS3812E/BTS3812AE Typical Configurations .......................................................................................13
2.1.7 BTS3812E/BTS3812AE Capacity ..............................................................................................................16
2.2 Distributed Node B DBS3800 System Description .............................................................................................17
2.2.2 Baseband Module Configuration ...............................................................................................................18
2.2.3 RRU Configurations...................................................................................................................................19
2.2.4 DBS3800 Typical Configurations...............................................................................................................19
2.2.5 DBS3800 Capacity......................................................................................................................................21
2.3 Node B V200R010...............................................................................................................................................22
2.3.1 Baseband Module Configuration ...............................................................................................................25
2.3.2 RF Module Configurations ........................................................................................................................28
2.3.3 3900 Series Node B typical configuration ..................................................................................................29
2.4 UMTS Capacity Dimensioning Procedure .........................................................................................................37
2.4.1 Introduction ................................................................................................................................................37
2.4.2 CS Capacity Dimensioning Principle .......................................................................................................38
2.4.3 PS Capacity Dimensioning Principle........................................................................................................41
2.4.4 HSDPA Capacity Dimensioning ...............................................................................................................41
2.4.5 HSUPA Capacity Dimensioning ...............................................................................................................42
2.4.6 MBMS Capacity Dimensioning.................................................................................................................43
2.4.7 Mixed Services Capacity Dimensioning...................................................................................................45
2.5 UMTS CE Dimensioning Procedure ..................................................................................................................45
2.5.1 Introduction ................................................................................................................................................45
2.5.2 CE Dimensioning for CS Service .............................................................................................................47
2.5.3 CE Dimensioning for PS service ..............................................................................................................49
2.5.4 CE Dimensioning for HSDPA ...................................................................................................................49
2.5.5 CE Dimensioning for HSUPA ...................................................................................................................51
2.5.6 CE Dimensioning for MBMS.....................................................................................................................52
2.5.7 Total Number of Channel Elements.........................................................................................................53
2.6 UMTS Iub Dimensioning Procedure..................................................................................................................54
2.6.1 Introduction ................................................................................................................................................54
2.6.2 Iub Bandwidth Dimensioning for Traffic...................................................................................................55
2.6.2.1 CS Peak Iub Bandwidth.........................................................................................................................56
2.6.2.2 CS Average Iub Bandwidth.................................................................................................................58
2.6.2.3 PS Iub Bandwidth.................................................................................................................................58
2.6.2.4 HSPA Iub Bandwidth ...........................................................................................................................59
2.6.2.5 MBMS Iub Bandwidth ..........................................................................................................................60
2.6.3 Iub Bandwidth Dimensioning for Others ..................................................................................................61
2.6.3.1 Iub Bandwidth for Common Channel ...............................................................................................61
2.6.3.2 Iub Bandwidth for Signaling...............................................................................................................61
2.6.3.3 Iub Bandwidth for O&M.......................................................................................................................61
2008-08-29
iii
2008-08-29
iv
Revision Record
Date
Revision
Description
Author
2008-03-03
1.0
Initial release
Tang wenqing,
Zhang hua, Li
hong, Hu guang
2008-03-21
1.1
Tang wenqing
2008-08-21
1.2
Zhang jianhua,
Guanwei
2008-08-29
Confidential
Introduction
This document is to introduce the Dimensioning rules for Huaweis RAN product
including Node B (Macro and DNBS) and RNC. It is based on release RAN10.0
including the introduction of capacity of baseband board and transmission of Node B,
the traffic processing capability of RNC and interface capability (Iub, Iur, Iu-CS and
Iu-PS).
Node B
Transport Subsystem
Baseband Subsystem
RF Subsystem
Control Subsystem
Antenna Subsystem
Heat Dissipation
Commercial in Confidence
Page 6, Total 88
Confidential
Commercial in Confidence
Confidential
Full Spelling
HBBI
EBBI
EBOI
2008-8-29
Commercial in Confidence
Page 8, Total 88
Confidential
Full Spelling
Interface Unit
HDLP
HULP
EULP
MAFU
MTRU
WRFU
NCCU
NFAN
NMON
NMPT
NUTI
Board type
Interface
T1
Number
8 pairs
Rate
1.5Mbit/s
Standard
Remark
ETS300 420
E1 and
ITU G.703/704
T1
ANSI-G.703/704
share
ETS300 420
the
ITU G.703/704
same
ANSI-G.703/704
ports.
NUTI
E1
8 pairs
2Mbit/s
100 M Fast
2
100Mbit/s
IEEE 802.3
Ethernet
2008-8-29
Commercial in Confidence
Page 9, Total 88
Board type
Interface
T1
Number
16 pairs
Rate
1.5Mbit/s
NUTI with E1
sub board
E1
16 pairs
2Mbit/s
Confidential
Standard
Remark
ETS300 420
E1 and
ITU G.703/704
T1
ANSI-G.703/704
share
ETS300 420
the
ITU G.703/704
same
ANSI-G.703/704
ports.
100 M Fast
2
100Mbit/s
IEEE 802.3
Ethernet
T1
8 pairs
1.5Mbit/s
ETS300 420
E1 and
ITU G.703/704
T1
ANSI-G.703/704 share
E1
8 pairs
2 Mbit/s
NUTI with
un-channelized
100 M Fast
STM-1 sub
Ethernet
100Mbit/s
board
ETS300 420
the
ITU G.703/704
same
ANSI-G.703/704
ports.
IEEE 802.3
ANSI
T1.105-1995
un-channelized
ITU I.432.2
2
155Mbit/s
STM-1/ OC3
G.703
ITU G.957
ANSI T1.105
NUTI with
channelized
T1
8 pairs
STM-1 sub
2008-8-29
Commercial in Confidence
1.5Mbit/s
ETS300 420
E1 and
ITU G.703/704
T1
ANSI-G.703/704
share
Board type
Interface
Number
Rate
board
E1
8 pairs
2Mbit/s
Confidential
Standard
Remark
ETS300 420
the
ITU G.703/704
same
ANSI-G.703/704
ports.
100 M Fast
2
100Mbit/s
IEEE 802.3
Ethernet
ANSI
T1.105-1995
channelizd
ITU I.432.2
1
STM-1/OC3
155Mbit/s
G.703
ITU G.957
ANSI T1.105
2008-8-29
Commercial in Confidence
Confidential
One BTS3812E/BTS3812AE provides up to 6 slots for HULP or EULP. HULP and EULP
share the 6 slots.
The HULP has the following functions:
Commercial in Confidence
Confidential
The WRFU supports RF signal processing for 2 receiving channel and 1 transmitting
channel, including duplex filter, one receiving filter, and Low Noise Amplifiers (LNAs).
One module supports 1 sector and 4 carriers, 80W output power, the output power is
measured at the NodeB RF module antenna ports.
Providing Boolean signal ports for external alarms and output control
Transmit Diversity
1x1
Optional
3x1
Optional
3x2
Optional
3x3
Optional
3x4
Optional
6x1
Optional
6x2
Optional
Note:
N x M = sector x carrier
3 x 1 indicates that each of the three sectors has one carrier.
sector
supports
maximum
of
four
carriers.
The
2008-8-29
Commercial in Confidence
Confidential
For some RAN sharing scenario, one NodeB shall support more carriers, for
example3 x 6 (sector x carrier). The WRFU should be configured. One
WRFU supports 4 carriers and 80 W output power at the NodeB RF module
antenna port. No additional RF modules are required when 1-carrier
configuration is upgraded to 4-carrier configuration. With 6 WRFU, one
BTS3812E/BTS3812AE can support 3 x 8 (sector x carrier) configuration.
Any combination of the two frequency bands (850 MHz, 900 MHz, 1800 MHz,
1900 MHz, and 2100 MHz) can be supported in one Node B. The Node B
with shared baseband boards only requires RF modules at different bands.
The Node B configuration with supporting HSUPA phase 1 is listed below (with MTRU):
configur
MTRU
MAFU
WRFU
NMPT
NUTI
NMON
HBBI
HULP
HDLP
NA
NA
NA
1+1
NA
NA
NA
2+2
NA
NA
NA
1+1+1
NA
NA
NA
2+2+2
NA
NA
NA
3+3+3
NA
4+4+4
NA
ation
The Node B configuration with supporting HSUPA phase 2 is listed below (with MTRU):
configur
2008-8-29
MTRU
MAFU
WRFU
NMPT
Commercial in Confidence
NUTI
NMON
EBBI
EULP
HDL
Confidential
ation
NA
NA
NA
1+1
NA
NA
NA
2+2
NA
NA
NA
1+1+1
NA
NA
NA
2+2+2
NA
NA
NA
3+3+3
NA
NA
NA
4+4+4
NA
The Node B configuration with supporting HSUPA phase 1 is listed below (with WRFU):
configur
MTRU
MAFU
WRFU
NMPT
NUTI
NMON
HBBI
HULP
HDLP
NA
NA
1+1
NA
NA
2+2
NA
NA
1+1+1
NA
NA
2+2+2
NA
NA
3+3+3
4+4+4
6+6+6
ation
The Node B configuration with supporting HSUPA phase 2 is listed below (with WRFU):
configur
MTRU
MAFU
WRFU
NMPT
NUTI
NMON
EBBI
EULP
ation
HDL
P
NA
NA
1+1
NA
NA
2+2
NA
NA
1+1+1
NA
NA
2+2+2
NA
NA
3+3+3
NA
NA
2008-8-29
Commercial in Confidence
Confidential
4+4+4
6+6+6
The diagram for connection of S111, S222 and S333 configurations are shown below.
Dual
Dual
Polarization
Polarization
Rx: f1,f2
Rx: f1
Rx:
Rx:
Tx:
Duplexer
Rx: f1,f2,f3
Rx: f1,f2,f3
Duplexer
Duplexer
f1,f2
Duplexer
MAFU
Splitter
PA
MTRU
PA
TRX
PA
TRX
1 Carrier
Splitter
Splitter
Splitter
TRX
2 Carriers
PA
TRX
3 Carriers
configuration. With 2 EBBI boards, 6 HULP and 2 HDLP configuration, the Capacity listed
in the following table.
Capacity Type
Quantity of CEs
Uplink capacity
1536
Downlink capacity
1792
HSDPA capacity
2008-8-29
360
HS-PDSCH codes
HSUPA PH1
1536
HSUPA PH2
1536
Commercial in Confidence
Confidential
The BBU3806 (indoor unit) and the BBU3806C (outdoor unit) have a similar logical
structure. In RAN10.0, EBBC and EBBM are introduced as enhanced base band card
for BBU3806 and BBU3806C. Using BBU3806+EBBC or BBU3806C+EBBM can realize
the larger capacity of base band.
Figure below shows the functional modules in the BBU.
Transport subsystem
Baseband subsystem
Control subsystem
Interface modules
2008-8-29
Commercial in Confidence
Confidential
Interface module. The interface module receives downlink baseband data from the
BBU, transmits uplink baseband data to the BBU, and forwards data from the
cascaded RRUs.
MTRX. The MTRX has two RX channels and one TX channel for RF signals. The
RX channel down-converts the receive signals into Intermediate Frequency (IF)
signals and performs amplification, analog-to-digital (A/D) conversion, digital
down-conversion, matched filtering, and Digital Automatic Gain Control (DAGC).
The TX channel performs shape filtering of downlink spreading signals,
digital-to-analog (D/A) conversion, and up-conversion of RF signals into transmit
band signals.
PA. The Power Amplifier (PA) implements the DPD and E-Doherty technologies to
amplify low-power RF signals from the MTRX.
Duplexer. The duplexer multiplexes receive signals and transmit signals, which
enables the receive signals and transmit signals to share the same antenna path.
The duplexer also filters receive signals and transmit signals.
Commercial in Confidence
Confidential
One BBU3806 provides 2 FE interface and 8 E1/T1 interface for the Iub connections.
One BBU3806 provides 3 optical CPRI interface for RRU connections.
One BBU3806 supports 3 cells, 192CE in uplink and 256CE in downlink. One BBU also
provides 1 slot for extension card EBBC. One BBU3806 with EBBC supports 6 cells,
384CE in uplink and 512CE in downlink.
One 40W RRU can support 2 continuous carriers in 1 sector. DBS3900 can support
smooth capacity expansion from 1 x 1 to 1 x 2 without adding RF module.
Two 40W RRUs in parallel connection within one sector can support the 1 x 4
configuration.
One 60W RRU can support 4 continuous carriers in 1 sector. With 20W per carrier
configuration, it can support 3 non continuous carriers (for example 1101, 1011),
which is applicable to RAN sharing with 2 operators has non continuous carriers.
Two 60W RRUs in parallel connection within one sector can support the 1 x 8
configuration.
Two RRUs in parallel connection within one sector can support transmit diversity and
4-way receive diversity.
Qty. of
Qty. of
BBUs
EBBC/EBB
Qty. of RRU3801C
M
No TX
TX Diversity
Diversity
1x1
1x2
2x1
2008-8-29
Commercial in Confidence
Confidential
2x2
3x1
3x2
3x3
Not supported
3x4
Not supported
6x2
Not supported
Qty. of
Qty. of
BBUs
EBBC/EBB
Qty. of RRU3804s
M
No TX
TX
Diversity
Diversity
1x1
1x2
2x1
2x2
3x1
3x2
3x3
6x2
Not
supported
Qty. of
Qty. of
BBUs
EBBC/EBB
Qty. of RRU3801C
M
No TX
TX Diversity
Diversity
1x1
1x2
2x1
2x2
3x1
3x2
3x3
Not supported
3x4
Not supported
6x2
Not supported
Commercial in Confidence
Confidential
phase2.
Configuration
Qty. of
Qty. of
Qty. of RRU3804s
BBUs
EBBC/EBB
M
No TX
TX
Diversity
Diversity
1x1
1x2
2x1
2x2
3x1
3x2
3x3
6x2
Not
supported
Configuration
Uplink R99 CE
Downlink
HSDPA Capacity
R99 CE
1 BBU
192
256
45 HS-PDSCH codes
2 BBUs
384
512
90 HS-PDSCH codes
768
1024
Configuration
Uplink R99/HSUPA CE
Downlink R99 CE
HSDPA Capacity
1 BBU
128
256
45 HS-PDSCH codes
2 BBUs
256
512
90 HS-PDSCH codes
2 BBUs with
1024
EBBC
Configuration
2008-8-29
Uplink R99 CE
Downlink R99 CE
Commercial in Confidence
HSDPA Capacity
Page 21, Total 88
Confidential
Configuration
Uplink R99 CE
Downlink R99 CE
HSDPA Capacity
1 BBU
192
256
45 HS-PDSCH codes
384
512
90 HS-PDSCH codes
Configuration
Uplink R99/HSUPA
CE
Downlink R99
CE
HSDPA Capacity
1 BBU
128
256
45 HS-PDSCH codes
512
90 HS-PDSCH codes
1 BBU
EBBM
with
Value
Value
Flexible combinations of the three units and auxiliary devices can provide different
NodeBs that apply to different scenarios such as indoor centralized installation, outdoor
centralized installation, outdoor distributed installation, site sharing of multiple network
systems, and multi-mode application. Figure 2-7 shows the three units and auxiliary
devices and Figure 2-8 shows the different application scenarios.
2008-8-29
Commercial in Confidence
Confidential
2008-8-29
Commercial in Confidence
Confidential
The cabinet macro NodeB, integrating the BBU3900 and the WRFU, consists of the
2008-8-29
Commercial in Confidence
Confidential
indoor BTS3900 and the outdoor BTS3900A. The cabinet macro Node B applies to
centralized installation, where the BTS3900 and the BTS3900A, as mentioned above,
are recommended for indoor application and outdoor application respectively.
Distributed Node B
The distributed NodeB, known as the DBS3900, consists of the BBU3900 and the RRU.
For the distributed installation, the RRU is placed close to the antenna. This can reduce
feeder loss and improve Node B performance.
The compact mini Node B is also of two types, which is applies to the new outdoor 3G
sites where no equipment room exists, hot spots, marginal networks, and blind spots
such as tunnels.
2008-8-29
Commercial in Confidence
Confidential
Board
Slot 0
Slot 1
Slot 2
Slot 3
Slot 4
Slot 5
WMPT
UTRP
available
available
available
available
WBBP
available
available
available
available
UELP
available
available
available
UFLP
available
available
available
Slot 6
Slot 7
available
available
available
available
available
available
available
available
available
available
available
available
available
available
One WMPT is mandatory configuration. And one WBBP also must be configured as
BBU realizes baseband processing. Others such as UTRP, UELP and UFLP are
optional depended on requirements.
I. WMPT
The WMPT integrated the control and transport subsystem manages the entire Node
System. The subsystem performs operation and maintenance, processes various types
of signaling, provides system clocks, and provides transport interfaces. One BBU3900
can hold up to two WMPTs for 1+1 redundancy.
One WMPT provides 4 E1, 1 electrical FE and 1 optical FE interfaces. For one Node B,
2 WMPT can provide 8 E1 and 2 electrical FE and 2 optical FE interfaces.
II. UTRP
With the UTRP, the BBU can provide extra E1 interface. UTRP3 supports 8 E1 for ATM
and UTRP4 supports 8 E1 for IP. So the UTRP is regarded as extension transmission
Processing unit.
Maximum 5 UTRP can be supported in one BBU3900.
Commercial in Confidence
2008-8-29
E1 for ATM
E1 for IP
Type
WMPT
Confidential
Ethernet
Ethernet
10/100
10/100
electrical
optical
UTRP3
UTRP4
Board Type
Cell
Uplink
Downlink R99
HSDPA
R99/HSUPA CE
CE
Capacity
45 HS-PDSCH
WBBPa
3 cells
128
256
WBBPb1
3 cells
64
64
codes
45 HS-PDSCH
codes
45 HS-PDSCH
WBBPb2
3 cells
128
128
codes
90 HS-PDSCH
WBBPb3
6 cells
256
256
codes
90 HS-PDSCH
WBBPb4
6 cells
384
384
codes
CCH R99 included, 16CE for downlink and 6 CE for uplink for 3 cells
TX diversity is no impact for CE consumption for both uplink and downlink direction.
2008-8-29
Commercial in Confidence
Confidential
enough for capacity expansion, only license file need to be upgraded. Uplink and
downlink capacity expansion could be implemented separately. Otherwise, new
board and new license need to be added to meet the new requirement of capacity
expansion. Uplink and downlink capacity expansion could also be implemented
separately. The step of license expansion is 16 CEs according to the customers
I. WRFU Configurations
The WRFU is divided into two types according to output power and carries:
Two 40W WRFUs in parallel connection within one sector can support the 1 x 4
configuration.
Two 80W WRFUs in parallel connection within one sector can support the 1 x 8
configuration.
Two WRFUs in parallel connection within one sector can support transmit diversity
and 4-way receive diversity.
One 80W WRFU can support 4 continuous carriers in 1 sector and it also can
support non continuous carriers (for example 1101, 1011, 1001, 1010, 1100), which
can be applicable to RAN sharing with 2 operators has non continuous carriers.
2008-8-29
Confidential
carriers
One 40W RRU can support 2 continuous carriers in 1 sector. DBS3900 can support
smooth capacity expansion from 1 x 1 to 1 x 2 without adding RF module.
Two 40W RRUs in parallel connection within one sector can support the 1 x 4
configuration.
One 60W RRU can support 4 continuous carriers in 1 sector. With 20W per carrier
configuration, it can support 3 non continuous carriers (for example 1101, 1011),
which is applicable to RAN sharing with 2 operators has non continuous carriers.
Two 60W RRUs in parallel connection within one sector can support the 1 x 8
configuration.
Two RRUs in parallel connection within one sector can support transmit diversity and
4-way receive diversity.
Commercial in Confidence
Confidential
Minimum # of
Minimum # of
Minimum # of
Minimum # of
20W
Indoor Cabinet
WMPT
WBBPb4
80W WRFU
1 1
1 2
1 3
1 4
3 1
3 2
3 3
3 4
6 1
6 2
3 6
3 8
6 3
6 4
Commercial in Confidence
Confidential
Per carrier
Minimum # of
Minimum # of
Minimum # of
Minimum # of
20W
Indoor Cabinet
WMPT
WBBPb2
40W WRFU
1 1
1 2
3 1
3 2
6 1
6 2
2008-8-29
Commercial in Confidence
Confidential
Minimum # of
Minimum # of
Minimum # of
Minimum # of
20W
Cabinet
WMPT
WBBPb4
80W WRFU
1 1
1 2
1 3
One APM30,
1 4
One 3RF
3 1
cabinet with
3 2
internal battery
3 3
3 4
2008-8-29
Commercial in Confidence
Confidential
Per carrier
Minimum # of
Minimum # of
Minimum # of
Minimum # of
20W
Cabinet
WMPT
WBBPb4
80W WRFU
6 1
One APM30,
6 2
One 6RF
3 6
cabinet
3 8
One battery
6 3
cabinet
6 4
Minimum # of
Minimum # of
Minimum # of
Minimum # of
20W
Cabinet
WMPT
WBBPb2
40W WRFU
1 1
One APM30,
1 2
One 3RF
3 1
cabinet with
3 2
internal battery
6 1
One APM30,
One 6RF
cabinet
6 2
One battery
cabinet
III. DBS3900 typical configuration
The BBU and RRU are the main parts of DBS3900. The two units support
independent
2008-8-29
Commercial in Confidence
Confidential
Minimum # of
Minimum # of
WMPT
WBBPb4
RRU3804
1 1
1 2
1 3
3 1
3 2
3 3
6 1
6 2
3 6
3 8
6 3
2008-8-29
Commercial in Confidence
Confidential
Minimum # of
Minimum # of
Minimum # of
WMPT
WBBPb2
RRU3801C
1 1
1 2
3 1
3 2
6 1
6 2
Commercial in Confidence
Confidential
Minimum # of
Minimum # of
WMPT
WBBPb2
RRU3804
1 1
1 2
1 3
Minimum # of
Minimum # of
WMPT
WBBPb2
RRU3801C
1 1
1 2
2008-8-29
Commercial in Confidence
Confidential
2008-8-29
Commercial in Confidence
Confidential
Dimensioning Start
Multidimensional ErlangB
calculate Peak load of CS
Calculate average
load of PS
Calculate load of
HSDPA
Calculate load of
HSUPA
Calculate
average load of CS
No
=Target Cell Load?
Yes
Dimensioning End
Section 2.4.4 introduces the main principle for HSDPA capacity dimensioning
Section 2.4.5 introduces the main principle for HSUPA capacity dimensioning
Section 2.4.7 presents us the principle about mixed services capacity dimensioning.
Load CS peak
Commercial in Confidence
Confidential
multiservice
Calls
completion
Blocked
calls
Multidimensional Erlang B model makes it possible to utilize the cell capacity effectively.
The resource is shared by all services in multidimensional ErlangB model, which makes
use of the fact that the probability of simultaneous bursts from many independent traffic
sources is very small. This idea is that according to the law of large numbers the
statistical fluctuation decreases in an aggregated flow of many burst and fluctuating
traffic flows when the number of combined flows increases. The following figure
illustrates the gain when resource is shared compared to the partitioned resource.
ErlangB - Partitioning Resources
Commercial in Confidence
GoS requirements of
various CS services
Confidential
MDE
2.
Load CS avg
(3)
Uplink:
(4)
Downlink:
(5)
Where,
2008-8-29
Commercial in Confidence
Confidential
Load PS Avg
(6)
Where
N channels i
Calculation of PS average cell load for DL is almost same as that for UL except that the
impact on the load due to SHO should be considered in DL.
2008-8-29
Commercial in Confidence
Confidential
Cell coverage
radius
Simulation
Power and
Code for
HSDPA
Ior/Ioc distribution
Ec/Io distribution
Ec/Io =>throughput
Cell average
throughput
2008-8-29
Commercial in Confidence
Cell Radius
Confidential
User rate at
Ec/N0
Ec/N0R
distance R
HSUPA cell
throughput
Uplink load
HSUPA actual
Maximum rate of
cell load
single user
HS-DPCCH load
R99 load
A-DCH load
2008-8-29
Commercial in Confidence
Confidential
Power consumption for each MBMS channel at air interface can be calculated by
the following formula:
Commercial in Confidence
Confidential
Load
Total Load
CS Peak Load
Load occupied by PS
CS Average Load
Load occupied by CS
Time
Figure 2-23 Resource Shared by CS and PS
According to the previous calculation we can obtain the actual total cell load by the
formula:
Load cell total _ UL max{Load CS peak , Load CS avg Load PS avg Load HSUPA }
Load cell total _ DL max{Load CS peak , Load CS avg Load PS avg Load HSDPA } Load CCH Load MBMS
When the actual total cell load Load cell total equals to the cell target load, the number
of subscribers here is the maximum capacity of one cell.
2.5
2.5.1 Introduction
CE (Channel Element) is defined as a fundamental base band processing element.
Generally, one channel element can be considered as the resources consumed by one
12.2kbps AMR service channel and one 3.4kbps signaling channel. CEs are pooled per
Node B, no additional CE are needed for either CCH or for signaling channels.
2008-8-29
Commercial in Confidence
Confidential
The number of channel elements is determined by three factors: traffic model, radio
bearers and CE factors.
Traffic models like Erlang B, Erlang C, etc., are established models which can model
single service, for instance, circuit-switched traffic. However, there are no established
ways for modeling multi-service traffic in UMTS. Huawei has done thorough research in
the field of multi-service capacity dimensioning and introduces multidimensional ErlangB
model as the approach to estimate the CE of circuit switched (CS) multi-service.
The figure below shows procedure of CE dimensioning.
Dimensioning Start
Subscribers per NodeB
Traffic model
Multidimensional ErlangB
calculate Peak CE of CS
Calculate
average CE of CS
Calculate average CE
of PS
Calculate CE for
A-DCH of HSDPA
Total Channel
Elements
Dimensioning End
2008-8-29
Commercial in Confidence
Confidential
Note:
CE factors means: The number of CEs needed by one connection for each specific radio
bearer.
1.
N users )
CECS _ Peak
Commercial in Confidence
Confidential
CECS _ Average
(1)
2008-8-29
Commercial in Confidence
Confidential
CE Consumption on UL
CE Consumption on DL
AMR 12.2kbps
CS 64kbps
PS 64kbps
PS 128kps
PS 144kps
PS 384kbps
10
CEPS _ Average
(2)
2008-8-29
Commercial in Confidence
CE HSDPA _UL
)
Page 49, Total 88
Confidential
On the uplink, uplink A-DCH (associated DCH) can be used for signalling and
transmission of HSDPA uplink traffic. A-DCH has variable SF of 4, 8 and 16 and its
corresponding data transmission rate is 384kbps, 128k and 64k, respectively.
Usually the UL total traffic model of R99 includes the HSDPA users, therefore the
number of CEs consumed by HSDPA users in uplink (
CE HSDPA _UL
) is already included
CE HSDPA _UL
HSDPA users (
N HSDPA _ Links
bearing rate of UL A-DCH is 64kbps which requires 3 CEs according to CE factors, then
the number of CEs required by HSDPA users in uplink will be
2.
CE HSDPA _ DL
N HSDPA _ Links 3
The SF of A-DCH is 256 on downlink, with the rate of 3.4 kbps. When an HSDPA
subscriber accesses the network, a downlink A-DCH is set up, which consumes one CE.
Therefore CE resource consumed by HSDPA DL A-DCH depends on the number of
simultaneously connected HSDPA users, which can be calculated according to the
following formula:
ThroughputPerUserHSDPA N users
GBRHSDPA
(3)
Commercial in Confidence
Confidential
HSUPA Rate
MinSF
(kbps)
HSUPA Phase1
HSUPA Phase2
SF64
<35.4
SF32
~69
3.5
1.5
SF16
~169.8
SF8
~337.8
SF4
~709.2
12
10
2*SF4
~1448.4
22
20
2*SF2
Not Support
32
2*SF2 + 2*SF4
Not Support
48
Notes:
Commercial in Confidence
Links HSUPA
Confidential
* (1 Burstratio)
MBMS Bearer
16kbps
32kbps
64kbps
128kbps
256kbps
OVSF
SF128
SF64
SF32
SF16
SF8
CE
consumption
2008-8-29
Commercial in Confidence
Confidential
Where,
CEMBMS is the total CE consumption for all MBMS channels per Node B.
N links _ j is the MBMS channel number for each Node B, this is the sum of all the
MBMS channels at each cell within Node B.
Total CE
CE Peak for CS
CE occupied by PS
CE Average for CS
CE occupied by CS
Time
Figure 2-27 CE resource shared by PS and CS service
Therefore, according to the previous calculation we can obtain the number of R99 CEs
in uplink and downlink respectively by the same formula as shown in the following:
(4)
Finally, the total number of channel elements per Node B for both R99 and HSDPA can
be written as:
2008-8-29
Commercial in Confidence
Confidential
(5)
2.6
(6)
2.6.1 Introduction
Iub, as shown in Figure 2-28 figure, is the interface between RNC and Node B.
Core Network
Iu
Iu
RNS
RNS
UTRAN
Iur
RNC
Iub
Node B
RNC
Iub
Iub
Node B
Node B
Iub
Node B
2008-8-29
Commercial in Confidence
Input
Confidential
Iub Dimensiong
Output
CS Traffic
Voice Traffic
CS data Traffic
GoS Requirements
CS Iub
Bandwidth
Bandwidth
for Traffic
Subscribes
Subs. per NodeB
PS Traffic
PS64 throughput
PS128 throughput
PS384 throughput
PS retransmission
Iub
Bandwidth
PS Iub
Bandwidth
HSDPA Iub
Bandwidth
HSDPA Traffic
Common Channel
Bandwidth
Signalling
Bandwidth
O&M Bandwidth
2008-8-29
Commercial in Confidence
Confidential
Therefore, the total Iub bandwidth for traffic can be obtained which is:
(7)
blocking
probability,
which
depends
on
its
Iub
bandwidth
usage.
multiservice
Calls
completion
Blocked
calls
Commercial in Confidence
Confidential
Multidimensional ErlangB model makes it possible to utilize the Iub bandwidth effectively.
The resource is shared by all services in multidimensional ErlangB model, which makes
use of the fact that the probability of simultaneous bursts from many independent traffic
sources is very small. This idea is that according to the law of large numbers the
statistical fluctuation decreases in an aggregated flow of many burst and fluctuating
traffic flows when the number of combined flows increases. The following figure
illustrates the gain when the resource is shared compared to when the resource is
partitioned.
ErlangB - Partitioning Resources
Once the Gos requirement of CS services, the CS traffic per NodeB, the Iub factors are
known, CS peak Iub bandwidth can be calculated using multidimensional ErlangB (MDE)
model. This idea is shown in Figure 2-33following figure.
Note:
Iub factors means Iub bearer bandwidth including FP, AAL2 and ATM overhead for
service i.
2008-8-29
Commercial in Confidence
Confidential
Traffic of every CS
service per NodeB;
Iub factors
GoS requirements of
various CS services
MDE
Figure 2-33 Estimate CS peak Iub Bandwidth with Multidimensional Erlang B Model
IubCS _ Average is the average Iub bandwidth for CS services, which does not guarantee
the GoS requirements. The formula below is used to calculate CS average bandwidth:
(8)
Where:
(9)
IubPS _ Average is the PS Iub bandwidth, it is almost the same to the CS average Iub
bandwidth except that some PS characteristics, e.g. PS burstiness, retransmission need
2008-8-29
Commercial in Confidence
Confidential
to be considered during the dimensioning. The formula below is used to calculate PS Iub
bandwidth:
(10)
Where:
IubTrafficPerUseri
(11)
(12)
Where:
HSDPA_Overhead is the difference between Iub bandwidth occupation of each HSDPA
service and the service bearer, for example, 1Mbps HSDPA service will use 1.35Mbps
2008-8-29
Commercial in Confidence
Confidential
(13)
IubMBMS =
links _ i
*RMBMS _ i
Where,
RMBMS _ i is the Iub bandwidth consumption for each MBMS bearer, this value is
different with different Iub transmission technology from ATM to IP.
N links _ i is the MBMS channel number for each kind of MBMS bearer per Node B
(Not per cell). Because to maximize saving of Iub bandwidth, the latest 3GPP
provides FACH transmission sharing for MBMS solution to share transport bearers.
RNC transports only single FACH data. Node B transport module performs data
duplication and distributes them to different FACH Channels in different cells, as
shown in the following figure, where the common transport bearer is shared over Iub.
Thus, two-third of Iub bandwidth is saved by the improved Iub transport.
CN
CRNC
MBMS stream
Node B
Iub transport bearer
2008-8-29
Commercial in Confidence
Confidential
ATM
IP
60 kbps
50 kbps
73 kbps
70 kbps
The Iub bandwidth for common channel based on ATM is a little bigger than that based
on IP.
RNC
3.1
The BSC6800 is Huawei RNC product name. The BSC configuration models are described in
following table:
2008-8-29
Commercial in Confidence
#
RNC Type
# Cell
Confidential
Throughput
STM-1
(Mbps/Erl)
Cabinet
# E1 Ports
Node B
RNC Type 1
100
300
126
64
60/2500
RNC Type 2
200
600
252
64
120/5000
RNC Type 3
300
900
384
64
180/7500
RNC Type 4
400
1,200
507
64
240/10k
RNC Type 5
500
1,500
630
64
300/12.5k
RNC Type 6
600
1,800
756
64
360/15k
RNC Type 7
700
2,100
882
64
420/17.5k
RNC Type 8
800
2,400
1, 008
64
480/20k
RNC Type 9
900
2,700
1, 134
64
540/22.5k
RNC Type10
1,000
3,000
1, 260
64
600/25k
RNC Type11
1,100
3,300
1, 386
64
660/27.5k
RNC Type12
1,200
3,600
1, 512
64
720/30k
RNC Type13
1,300
3,900
1, 638
64
780/32.5k
RNC Type14
1,400
4,200
1, 764
64
840/35k
RNC Type15
1,500
4,500
1, 890
64
900/37.5k
RNC Type16
1,600
4,800
2, 016
64
960/40k
WRSS is the ATM switching platform of BSC6800, which also provides Iu/Iur interfaces. Only 1
WRSS is configured for 1 BSC6800. The internal hardware components for 1 WRSS are fixed for
any model configuration.
WRBS is responsible for ATM frame processing and provides Iub interface. The internal hardware
components of 1 WRBS are fixed.
Their internal configurations are shown below
2008-8-29
Commercial in Confidence
Confidential
WRSS
W W WW
W W W W
W W
W W
WW
WW
M M L L
L N
H H
F F
M M
S S
P P P P
P E
P P
M M
U U
P P
U U
R
c
R R
c c
X X
b b
U U
b b
R
c
WW
WW
WW
F F
M M
S S
M M
U U
P P
R
c
R R
c c
X X
b b
U U
b b
R
c
W W
WW
W W
F F
M M
S S
M M
U U
P P
R
c
R R
c c
X X
b b
U U
b b
R
c
U U U U
U T
c
T
c
WRBS
LAN switch-3
LAN switch-2
LAN Switch
KVM
WRBS
WW
WW
WW
F F
M M
S S
M M
U U
P P
R R
c c
R
c
X X
b b
U U
b b
R
c
WRBS
GRU suite
LAN switch-1
LAN switch-0
BAM server
WRBS
BAM server
WRSR
WRBR
Notes
- The WOSE in WRBS supports channelized STM-1.
- The WLPU in WRSS supports unchannelized STM-1.
Even we use unchannelized STM-1, the WOSE must be configured because Iub frame processing
is terminated on this board.
WRBS content:
- one WOSE board and one WFIE board are inserted in the two slots of WINT per WRBS subrack:
the WOSE and WFIE are configured in slot 0 and 15, or vice versa. WOSE used in the configuration
2008-8-29
Commercial in Confidence
Confidential
and 30 cells.
and 50 cells.
WFMRb
WFMRc
WRBS
Therefore, in RAN10.0 up to 4 WFMRc boards are needed to support one WRBS capacity. One
WFMRc can support HSDPA 14.4Mbps per user or per cell. And 2 WFMRb boards can support
HSDPA 14.4Mbps per cell, but 14.4Mbps per user with WFMRb board is not supported.
Huawei BSC6800 supports mix configuration of WFMRc and WFMRb boards, the capacity of mix
configuration can be caculated as the following formular:
Capacity = Min{One WRBS capacity, (WFMRb number * One WFMRb capacity + WFMRc number *
One WFMRc capacity )}
WRSS content:
-
One WLPU provides 16 unchannelized STM-1 ports and the configuration principle is 1+1. 2
WLPUs are
configured for all RNC model configurations (RNC_01, RNC_02, RNC_03, RNC_04, RNC_05
and RNC_06). The 2 WLPU are plugged in slot 2 and 3. It is possible to use the 32 ports of the
2 WLPU without redundancy (Redundancy is optional).
The WHPU configuration principle is N+1. 1 WHPU supports 4 WRBS. 3 WHPUs (2+1) are
configured for all RNC model configurations (RNC_01, RNC_02, RNC_03, RNC_04, RNC_05
and RNC_06). The 3 WHPU are plugged in slots 10, 11 and 12.
2008-8-29
Commercial in Confidence
Confidential
WRSR content:
-
2 BAM Servers with 1:1 redundancy solution are configured for each RNC model configuration.
2 LAN Switches (Huawei Quidway S3928P) with 1+1 redundancy solution are configured for
each RNC model configuration.
The KVM is configured for each RNC model configuration, which is used for RNC local
maintenance for BAM
The LAN Switch allows to switch the KVM on the different BAM server; it is configured for each
RNC configuration
- For each cabinet, there is one Power distribution Box to do the Board power supply.
WRSS
WRBS
BAM
Cabinet 1
2008-8-29
Commercial in Confidence
Confidential
WRSS
WRBS
WRBS
WRBS
WRBS
WRBS
WRBS
WRBS
WRBS
WRBS
WRBS
WRBS
BAM
WRBS
WRBS
WRBS
WRBS
WRBS
Cabinet 1
Cabinet 2
Cabinet 3
Cabinet 4
Cabinet 5
Cabinet 6
3.2
The BSC6810 is Huawei RNC product name. The BSC6810 uses the all-IP Platform of Advanced
Radio Controller (PARC) developed by Huawei. The BSC6810 configuration models are
described in following table:
RNC Type
#Node B
Throughput (UL+DL)
BHCA
(Mbps/Erl)
(k)
# Cell
# Cabinet
RNC Type 1
100
300
192/3000
80
RNC Type 2
200
600
384/6000
160
RNC Type 3
300
900
576/9000
240
RNC Type 4
400
1,200
768/12k
320
RNC Type 5
500
1,500
960/15k
400
RNC Type 6
600
1,800
1152/18k
480
RNC Type 7
700
2,100
1344/21k
560
RNC Type 8
800
2,400
1536/24k
640
RNC Type 9
900
2,700
1728/27k
720
RNC Type10
1,000
3,000
1920/30k
800
2008-8-29
Commercial in Confidence
Confidential
RNC Type11
1,100
3,300
2112/33k
880
RNC Type12
1,200
3,600
2304/36k
960
RNC Type13
1,300
3,900
2496/39k
1040
RNC Type14
1,400
4,200
2688/42k
1120
RNC Type15
1,500
4,500
2880/45k
1200
RNC Type16
1,600
4,800
3072/48k
1280
RNC Type17
1,700
5,100
3264/51k
1360
The RSS is the central switching subrack of the BSC6810. Only 1 RSS is configured for 1
BSC6810.
2008-8-29
Commercial in Confidence
Confidential
R R
I I
N N
T T
R
I
N
T
R
I
N
T
R R R
I I I
N N N
T T T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R R
I I
N N
T T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R R
I I
N N
T T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
S
P
U
a
S
P
U
a
S
P
U
a
S
P
U
a
S
C
U
a
S
C
U
a
D D
P P
U U
b b
D
P
U
b
D
P
U
b
D
P
U
b
D
P
U
b
S
P
U
a
S
P
U
a
S
P
U
a
S
P
U
a
S
P
U
a
S
P
U
a
S
C
U
a
S
C
U
a
D D
P P
U U
b b
D
P
U
b
D
P
U
b
D
P
U
b
D
P
U
b
R R
I I
N N
T T
R
I
N
T
R
I
N
T
R R R
I I I
N N N
T T T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R R
I I
N N
T T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R R
I I
N N
T T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
S
P
U
a
S
P
U
a
S
P
U
a
S
P
U
a
S
P
U
a
S
C
U
a
D D
P P
U U
b b
D
P
U
b
D
P
U
b
D
P
U
b
D
P
U
b
S
P
U
a
S
P
U
a
S
P
U
a
S
P
U
a
S
P
U
a
S
P
U
a
S
C
U
a
S
C
U
a
D D
P P
U U
b b
D
P
U
b
D
P
U
b
D
P
U
b
D
P
U
b
R R
I I
N N
T T
R
I
N
T
R
I
N
T
R R
I I
N N
T T
O
M
U
a
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R R
I I
N N
T T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
S
P
U
a
S
P
U
a
S
P
U
a
S
P
U
a
D D
P P
U U
b b
D
P
U
b
D
P
U
b
G
C
U
a
G
C
U
a
S
P
U
a
S
P
U
a
S
P
U
a
S
P
U
a
S
P
U
a
S
C
U
a
S
C
U
a
D D
P P
U U
b b
D
P
U
b
D
P
U
b
D
P
U
b
D
P
U
b
RBS
RBS
S
P
U
a
S
P
U
a
RBS
RBS
S
P
U
a
S
C
U
a
O
M
U
a
RSS
RBS
S
P
U
a
S
P
U
a
S
C
U
a
S
C
U
a
RSR
S
P
U
a
RBR
Notes
The RINT refers to the interface board of the BSC6810. Physically, there is no board named RINT.
The interface boards are configured according to the transmission mode (ATM or IP) and types of
transmission port including E1/TI, unchannelized STM-1/OC-3c, channelized STM-1/OC-3, FE and
GE.
Commercial in Confidence
14
15
16
17
18
19
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
S
P
U
a
S
P
U
a
S
P
U
a
S
P
U
a
S
P
U
a
S
P
U
a
S
C
U
a
S
C
U
a
D
P
U
b
20
21
22
24
25
26
27
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
D
P
U
b
D
P
U
b
D
P
U
b
G
C
U
a
G
C
U
a
10
11
12
13
23
O
M
U
a
O
M
U
a
Confidential
14
15
16
17
18
19
20
21
22
23
24
25
26
27
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
R
I
N
T
S
P
U
a
S
P
U
a
S
P
U
a
S
P
U
a
S
P
U
a
S
P
U
a
S
C
U
a
S
C
U
a
D
P
U
b
D
P
U
b
D
P
U
b
D
P
U
b
D
P
U
b
D
P
U
b
10
11
12
13
- Two SCUa boards are permanently configured both in RSS and RBS.
- Two GCUa or GCGa boards (GCGa boards are configured to replace the GCUa when GPS is
required) are permanently configured in RSS.
- Two OMUa board are permanently configured in RSS.
- SPUa can be configured both in RSS and RBS.
- DPUa can be configured both in RSS and RBS.
- RINT can be configured both in RSS and RBS.
RSR content
2008-8-29
Commercial in Confidence
Confidential
RBR content
- One to Three RBSs
Minimum Configuration
The minimum configuration diagram is shown as below:
Empty
Empty
RSS
RSR
Maximum Configuration
The maximum configuration diagram is shown as below:
RBS
RBS
RBS
RBS
RSS
RBS
RSR
RBR
2008-8-29
Commercial in Confidence
3.3
Confidential
Function Upgrade
The HSDPA Ph4 (DL 14.4Mbps per user) and HSUPA Ph2 (UL 5.76Mbps per user) are supported
in Huawei UMTS RAN10.0 release, and the dependency on hardware are as below.
Board
WFMRb
WFMRc
HSDPA Ph4
Not support
Support
HSUPA Ph2
Support
Support
3.3.3 IP Upgrade
In RAN10.0, all IP transmission, that is Iub/Iu/Iur over IP, is supported.
BSC6800
Commercial in Confidence
Confidential
BSC6810
The BSC6810 is hardware and software ready for Iub/Iu/Iur over IP.
Compared with BSC6810V200R009 in RAN6.1, IP over E1/T1 over SDH (CPOS) and IP over
SDH (POS) are added in RAN10.0 for BSC6810V200R010.
The CPOS is supported by interface board POUa, the new interface board provided
since RAN10.0. That means, when upgrade from RAN6.1 to RAN10.0 to support
CPOS, new interface board POUa is required.
The POS is supported by interface board UOIa, the interface board provided since
RAN6.1. That means only software upgrade from RAN6.1 to RAN10.0 is needed to
support POS.
2008-8-29
Commercial in Confidence
3.4
Confidential
Network Parameter
Service Bit Rate
IUUP usage factor
AAL2 usage factor
2008-8-29
Commercial in Confidence
Unit
CS Voice
12.2kbps
88.57%
90.19%
Value*
CS Data
64kbps
90.91%
91.67%
Page 73, Total 88
Confidential
90.6%
72.37%
1.38
90.6%
75.50%
1.32
Notes
Subtotal of usage factor = IUUP usage factor * AAL2 usage factor * ATM
usage factor.
Iu-CS interface protocol stack (IP over Ethernet) can be illustrated in following
figure:
Network Parameter
Service Bit Rate
IUUP usage factor
MAC usage factor
subtotal of protocol usage factor
Extension Ratio
Unit
CS Voice
12.2kbps
88.57%
43%
38%
2.63
Value*
CS Data
64kbps
90.91%
69.3%
63%
1.44
2008-8-29
Commercial in Confidence
Confidential
2.
2008-8-29
Commercial in Confidence
Confidential
The protocol stack and overhead in Iu-PS interface under IP over Ethernet can be
2008-8-29
Commercial in Confidence
Confidential
Payload (Bytes)
GTP-U
GTP-U
UDP
IP
UDP
IP
20
MAC
18
Total
56
MAC
Bit Rate
under IP over E1/T1
PHY
The throughput on Iu-PS interface can be divided into two parts that are throughput of
control plane and throughput of user plane as shown in following figure:
2.
3.
Packet size
4.
Peak ratio
2008-8-29
Commercial in Confidence
Confidential
2008-8-29
Commercial in Confidence
Confidential
Traffic Model
Message
(Trans per
Length
Att. Sub./BH)
(Bytes)
Attach
0.75
424
318
Detach
0.75
159
119.25
Service Request
2.7
159
429.3
1.5
424
636
1.5
265
397.5
0.15
424
63.6
Iu Release
2.94
106
311.64
1.1
265
291.5
Paging
1.4
106
148.4
Bytes/BH/Sub.
Total (Bytes)
2715.19
6.03
2008-8-29
Commercial in Confidence
Confidential
2008-8-29
Commercial in Confidence
Confidential
UTRAN OMC
4.1
Server(s)
Client(s)
Alarm box(es)
Using a dial-up server, you can operate and maintain the M2000 system
through the Public Switched Telephone Network (PSTN).
The physical architecture of M2000 single server system is illustrated below.
2008-8-29
Commercial in Confidence
Confidential
PSTN
Alarm box
Client 1
Dial-up server
Client 2
Server
4.2
Management capacity
Server hardware
OMC Type 1
OMC Type 2
OMC Type 3
OMC Type 4
NEs)
OMC Type 5
NEs)
OMC Type 6
NEs)
2008-8-29
Commercial in Confidence
Confidential
Configuration
Management capacity
Server hardware
OMC Type 7
NEs)
CPUs)
4.2.2 Bandwidth
The bandwidth requirement between the M2000 and managed RNCs and
NodeBs (Each Node B covers three cells.) is listed below.
Number of
NodeBs
RNC
100
384
200
512
400
768
600
832
800
1024
1000
1152
Configuration Level
Sever Configuration
Performance Database
Space(MB)
Middle configuration
2008-8-29
Netra2402*73G HD)
10,000
Netra2402*146G HD)
25,000
Commercial in Confidence
Large configuration
Super configuration
Confidential
V890 SE33208*73G HD
92,160
V890 SE614016*146G HD
286,720
E4900 SE614014*73G HD
153,600
E4900 SE614016*146G HD
286,720
1.26 million
4.68 million
9 million
12.6 million
17.28 million
21.6 million
27 million
Event alarms
Event alarms report the current status of the system during the system
operation.
2008-8-29
Commercial in Confidence
Confidential
Shielded alarms
Operator can shield alarms as required. The shielded alarms are not
displayed on the client.
The M2000 stores the alarms for at least three months. The number of
managed NEs and the storage capacity depend on the server model.
Server
Event alarm
hardware
History fault
Current fault
Shielded
alarm
alarm
alarm
Sun Netra240
800 000
800 000
100 000
100 000
5 000 000
5 000 000
600 000
600 000
Sun Fire
7 000 000
7 000 000
800 000
800 000
E4900
2008-8-29
Server
20
30
50
55
90
100
125
Commercial in Confidence
Confidential
4.3
Server configuration
Number of clients
25
30
40
50
60
80
80
12
1.5
1.8
1.8
1.8
1.8
1.8
1.8
CPUs
Main
Frequency
of the CPU
2008-8-29
Commercial in Confidence
Confidential
(GHz)
Memory
16
32
16
32
48
2 x 146
6 x 146
2 x 146
None
1 x 6140
1 x 6140
disks.)
hard disks)
(GB)
Hard disk
(GB)
Disk array
(GB)
Accessorie
DVD/Ethernet
DVD/Ethernet
DVD/Ethernet
adapter/DATA
adapter/DATA72 tape
adapter/DATA72 tape
72 tape
drive/English
drive/English
drive/English
documentation
documentation
documentation
Operating
Solaris 10
Solaris 10 /English
Solaris 10 /English
system
/English
documentation
documentation
Sybase 15.0
/English
documentation
documentation
documentation
Database
documentation
Application
M2000 server
software
application
software
software
software
Commercial in Confidence
Item
Confidential
Configuration
Quidway AR46-40
Quidway R28-10
Router
Quidway R28-10
Quidway S3928P-EI
Switch and Hub
Quidway S2016HI
Timeslot cross multiplexer
Mercury 3600
Configuration
CPU
P4/2.8 GHz
Memory
512 MB
Hard disk
80 GB
CDROM/Floppy Drive/Ethernet Adapter/Sound
Accessories
Card/17 LCD Display
Operating system
Application
M2000 client application software
software
2008-8-29
Commercial in Confidence