Evolium A9140 RNC Evolution Description 211310000e05

Alcatel UMTS
Evolium A9140 RNC Evolution

Description
RNC Document
Sub-System Description
Release R5 from MR3
3BK 21131 AAAA TQZZA Ed.05
BLANK PAGE BREAK
Status
RELEASED
Short title
N/A
All rights reserved. Passing on and copying of this document, use
and communication of its contents not permitted without written
authorization from Alcatel.
2 / 100
Contents
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1
Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.2
Interface Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.2.1
External Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.2.2
Internal Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.2.3
Reference Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.3
RNC Ev Function Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.3.1
Processing Function Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.3.2
Interface Function Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.3.3
Telecom Function Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.3.4
Miscellaneous Function Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Rack Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.1
Rack Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.1.1
RNC Ev MINI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.1.2
RNC Ev 1000HD Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.1.3
RNC Ev 3000HD Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.1.4
RNC Ev 1000HSD Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.1.5
RNC Ev 3000HSD Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.2
Rack Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.2.1
Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.2.2
Side View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.2.3
Top View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.2.4
Dimensions and Weight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.2.5
Environmental Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.3
Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.4
M-FFTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.4.1
Front Panel View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.4.2
2.4.3
Power Supply Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.5
M-FILT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.5.1
M-FILT View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.5.2
Shelf Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.1
M-CONT Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3.1.1
M-CONT Shelf Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3.1.2
3.2
M-L1L2 Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.2.1
M-L1L2 Shelf Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.2.2
3.3
Shelf IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.3.1
Shelf ID Jumper Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.3.2
Jumper Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Hardware Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4.1
M-CP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.1.1
Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.1.2
M-CP Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
4.1.3
M-CP Operation and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
4.1.4
4.2
M-OMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4.2.1
Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4.2.2
M-OMP Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
3 / 100
Contents
4.2.3
M-OMP Operation and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.4
Dimensions and Weight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3
M-CM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.1
Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.2
M-CM Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.3
M-CM Operation and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.4
4.4
M-XWY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.1
4.4.2
M-XWY Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.3
M-XWY Operation and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.4
4.5
M-SIFMB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.1
4.5.2
M-SIFMB Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.3
M-SIFMB Operation and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.4
4.6
M-XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.1
4.6.2
M-XP Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.3
M-XP Operation and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.4
4.7
M-FANU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.1
4.7.2
M-FANU Top View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.3
M-FANU Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.4
Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1
Control Part Software Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.1
Control Part Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.2
Platform Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.3
Application Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2
Application Part Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.1
Operation and Maintenance Functional Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.2
Telecom Functional Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3
Software Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.1
Downloaded Software (D-SW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.2
Office Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4
PLD and FPGA Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operation and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.1
OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.2
NEM-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2
Equipment Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.1
Fault Detection and Reporting Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.2
Board State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.3
Board Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.4
Fault Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.5
Board Lock Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3
Diagnosis and Health Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1
Power-up Diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.2
Automatic Diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.3
Manual Diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.4
Health Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.4
Hard Disk Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5
System Defence Mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 / 100
46
47
47
47
49
50
50
51
51
53
54
55
55
55
57
58
59
59
59
62
63
63
64
64
64
65
65
67
68
68
69
70
71
72
73
74
74
74
75
77
78
78
79
80
80
81
81
82
83
83
83
83
84
84
85
86
Contents
6.6
6.7
6.8
6.9
6.10
6.11
6.12
6.13
6.14
6.15
Performance Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
RNC Ev Start-Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Security between RNC Ev and OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
6.8.1
Protection by SSH/SFTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
6.8.2
Protection by SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Load RNC Ev Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Emergency Reset of M-OMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Replace Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Maintenance Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
6.12.1
M-CONT Shelf IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
6.12.2
M-L1L2 #0 Shelf IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
6.13.1
Hardware Inventory Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
6.13.2
Rack Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Hardware Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
6.14.1
Board Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
6.14.2
Board Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
DIP Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
5 / 100
Figures
Figures
Figure 1: RNC Ev Rack Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Figure 2: RNC Ev Rack Side View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Figure 3: RNC Ev Rack Top View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6 / 100
Preface
Preface
Purpose
Note:
Whats New
This document describes the functions and hardware of the Evolium A9140
RNC Evolution (RNC Ev).
Your system may not have all the features described in this document.
In Edition 05
The configurations of RNC Ev 1000HSD and RNC Ev 3000HSD were modified.
The following sections are impacted:
RNC Ev 1000HSD Configuration (Section 2.1.4)
RNC Ev 3000HSD Configuration (Section 2.1.5)
M-L1L2 #0 Shelf IP Address (Section 6.12.2)
The interface security between the RNC Ev and the OMC/NEM-R was
improved. Refer to Security between RNC Ev and OMC-R (Section 6.8)
The defence mechanism for the M-XP and M-SIF board was added. Refer to
System Defence Mechanism (Section 6.5)
In Edition 04
The reference of boards were added. Refer to Board Name (Section 6.14.1).
Overall document quality was improved following an editorial review.
In Edition 03
First official release of document for R5 MR1.
In Edition 02
The IPCONFIG.WRF file was added as the final solution setting the IP
address.
The following sections were impacted:
M-CONT Shelf IP Address (Section 6.12.1)
M-L1L2 #0 Shelf IP Address (Section 6.12.2).
7 / 100
Preface
In Edition 01
First official release of document.
Audience
The guide is intended for:

Commissioning personnel
Support and service engineers
OMC-R operators
Training personnel.
Assumed Knowledge
8 / 100
The reader must have a general knowledge of UMTS.
1 Functional Description
This section describes the general architecture and each function of the
Evolium A9140 RNC Evolution.
9 / 100
1.1 Introduction
The RNC Ev is based on UMTS technology as defined for third-generation (3G)
mobile telephone systems. The RNC Ev complies R99/R5.
The main role of the RNC Ev is to manage radio resources within the Evolium
UTRAN system.
The RNC Ev exchanges information with the Core Network and the Node
Bs while controlling:
Call origination
Call termination
Call clearing
Diversity handover
Other call processing.
The position of the RNC Ev within the RNS is illustrated below:
NMS
(OMCR)
IP network
Network
management
system
Router
Node B
Router
UE
Uu
Iub
Node B
RNC Ev
Iub
Iu(PS)
Iur
Node B
Iu(CS)
Iub
Iu(PS)
RNC Ev
Uu
UE
Node B
Core
Network
Internet,
PSTN
Iu(CS)
Iub
Radio Access Network (RAN)
revd044
The RNC Ev supports multiple Node Bs and is connected to the Core Network
and the OMC-R. An RNC Ev can be connected to up to 256 Node Bs. More
than one RNC Ev can be connected to the same OMC-R. The RNC Ev can
handle up to 768 cells and up to 9 cells per the Node B.
The RNC Ev consists of rack that contains:
M-CONT shelf
M-L1L2 shelf.
There are six types of boards for the RNC Ev. Up to 26 boards can be mounted
on each shelf.
10 / 100
The connection diagram of the RNC Ev is illustrated below.

RNC Ev
ML1L2 shelf
Node B
MXP
[MMUX]
MSIFMB
Core
Network
MXP
[MSU]
MXWY
MXP
[ESU]
MXP
[DHT]
MXP
[SPU]
MCONT shelf
MCP
OMCR
MXWY
MOMP
MCM
revd056
1.2 Interface Architecture

1.2.1 External Interfaces
The external RNC Ev interfaces are illustrated below:
OMCR
Transmission
system
Node B
O&M interface
(STM1/Ethernet)
Iub
Iu (STM1)
(E1)
(STM1)
Core
Network
RNC Ev
Iub
Iur (STM1)
Node B
(STM1)
Local Iur (STM1)
Iub
IMA
Node B
Iur (STM1)
(E1)
(STM1)
RNC Ev
Iu (STM1)
Iub
Node B
(E1)
(STM1)
O&M interface
(Ethernet)
LMT
(NEMR)
revd046
11 / 100
The following table describes each external interface:

External
Interface
RNC Ev-Node B
interface
Description
The interface between the RNC Ev and the Node B (the Iub interface) uses ATM.
The RNC Ev supports an STM-1 optical interface. The Node B supports an E1 link
with/without IMA and an STM-1 optical interface. A transport system is required
for interworking in case of an E1 link.
Control signal and user information (voice and data) is sent and received in an
ATM cell.
RNC Ev-Core
Network interface
The interface between the RNC Ev and the Core Network (the Iu interface) uses
ATM. The RNC Ev supports an STM-1 optical interface.
ATM cell.
RNC Ev-RNC Ev
interface
The interface between two RNC Evs (the Iur interface) uses ATM. The RNC Ev
supports an STM-1 optical interface.
ATM cell.
There are two Iur connection types:
Through the Core Network via STM-1
Direct connection between RNC Evs via STM-1 (local Iur).
RNC Ev-LMT
interface
The interface between the RNC Ev and the LMT uses an Ethernet link. The RNC
Ev can be connected to the LMT either locally or remotely.
RNC Ev commissioning and local maintenance are performed using the LMT.
RNC Ev-OMC-R
interface
The OMC-R and the RNC Ev are connected via the:

M-SIFMB STM-1 interface
M-XWY 10 / 100BaseT interface.
12 / 100
1.2.2 Internal Interfaces

1.2.2.1 I/O Bus Interface
The I/O bus between boards communicates in the TCP/IP layer of the Ethernet.
The TCP link setting and the IP address setting of each board are processed
on system restart. The I/O bus of the Ethernet network operates using I/O
messages.
Ethernet technology is used for the RNC Ev internal data highway. The M-XWY
board performs a layer 2 role, switching communications between RNC Ev
boards.
The I/O bus is used to:
Exchange the control/response packets between M-CPs/M-OMPs and
other RNC Ev boards
Send the reporting packets to the M-CPs/M-OMPs.
ML1L2 Shelf
MXP
#0#7
I/O bus
(Serdes 1.08Gbps)
MSIFMB
#10
MXWY
#P
MXWY
#R
I/O bus
(Ethernet 10Gbps)
MCONT Shelf
MCP
#0#9
MSIFMB
#15
MXP
#18#25
I/O bus
(Ethernet 10Gbps)
I/O bus
(Serdes 1.08Gbps)
MOMP
#P
MXWY
#P
MCM
#P
MCM
#R
MXWY
#R
MOMP
#R
MCP
#16#25
revd041
1.2.2.2 ATM Cell Interface

ATM cells are also used to send and receive user data. However, to transfer
this information through the Ethernet together with the I/O bus data, one ATM
cell is encapsulated in one Ethernet frame. U plane traffic routing does not
use the TCP/IP layer. To perform the I/O bus communication, private MAC
addresses are used within the RNC Ev.
13 / 100
1.2.2.3 SV Bus Interface

The SV bus collects the status of boards and controls boards using resets and
ACT instructions. Board status provides information on:
Condition
Inventory
Faults.
The SV bus is located in the M-CONT shelf and in the M-L1L2 shelf. Each shelf
has two M-XWY boards and two SV bus lines as illustrated in the following
figure. One SV bus line of the ACT M-XWY board works as a master and the
other SV bus line is in SBY mode and works as a slave.
The status information collected in the M-L1L2 shelf is carried to the ACT
M-XWY board in the M-CONT shelf through the I/O bus line between the
M-L1L2 and the M-CONT shelves. The information collected from the boards is
carried to the ACT M-OMP board in the M-CONT shelf, via an I/O message
through the I/O bus line between the ACT M-XWY and M-OMP boards.
ML1L2 shelf
SV bus
MXP
#0#7
#18#25
MXWY
(ACT)
MSIFMB
#10, #15
MXWY
(SBY)
SV bus
MCONT shelf
SV bus
MXWY
(ACT)
I/O message
MOMP
(ACT)
MOMP
(SBY)
MCP
#0#9
#16#25
MCM
#P, #R
MXWY
(SBY)
SV bus
revd042
14 / 100
1.2.2.4 G Bus Interface

The G bus is the duplicated point-to-point bus between the M-CPs/M-OMPs
and the M-CM. Each M-CP and M-OMP has two G bus ports:
One connected to CM#P
One connected to CM#R.
The G bus is used to access shared resources on the M-CM, such as a global
memory for example.
G bus
MCM #R
MCP #0
MCM #P
MCP #1
MCP #25
MOMP #P
MOMP #R
revd045
15 / 100
1.2.3 Reference Clock

The M-XWY performs RNC Ev reference clock management:
ACT M-OMP has all the selection information of the external reference clock
on the M-SIFMB / M-XWY boards. This information is transmitted from the
ACT M-OMP board to each M-XWY / M-SIFMB board as an I/O message.
The M-SIFMB software selects one line used for the reference clock from
among four STM-1 lines according to the I/O message from ACT M-OMP,
and transmits it to M-XWY.
The M-XWY software selects an M-SIFMB board used for the external
STM-1 reference clock according to the I/O message from ACT M-OMP,
and the M-XWY board transmits the timing to M-XWY in the M-CONT
shelf. M-XWY in the M-L1L2 shelf distributes the timing to each M-XP
/ M-SIFMB board.
If the external STM-1 reference clock fails, an available, registered STM-1
reference line is selected. The local clock is used only if every registered
STM-1 reference line fails.
Reference clock
ML1L2 shelf
Core
Network
MSIFMB
Node B
RNC
MXWY #P
MXWY #R
MXWY #P
MXWY #R
OMCR
MOMP
(ACT)
MCONT shelf
: Reference clock collection
: Reference clock distribution
: I/O message
16 / 100
revd043
1.3 RNC Ev Function Blocks

The RNC Ev is managed on a function block basis. The following figure
illustrates the relationship between the function blocks and the hardware:
The RNC Ev reports the status of the function blocks to the OMC/NEM-R.
RNC Ev
Processing FB
CallPRC
[MCP]
Ethernet Switching
ETHSW
[MXWY]
Clock Distribution Interface

DCI
[MXWY]
OAMPRC
[MOMP]
GM
[MCM]
Interface FB
CNIF
[MSIFMB]
CN
RNCIF
[MSIFMB]
RNC Ev
Node BIF
[MSIFMB]
Node B
OMCIF
[MSIFMB]
[MXWY]
OMCR
Telecom FB
ESU
[MXP]
RNSO&M Routing
MSU
[MXP]
ROUTING
[MXP]
MMUX
[MXP]
DHT
[MXP]
SPU
[MXP]
revd036
1.3.1 Processing Function Blocks

Function
Block Name
Supported by
Description
Call-PRC
M-CP in M-CONT shelf
Processing capability for RNC Ev call control functions.
OAM-PRC
M-OMP in M-CONT shelf
Processing capability for RNC Ev operation and

maintenance control functions
Configuration function support via Office Data
management
Storage capability for performance measurement, trace,
and diagnostics files.
GM
M-CM in M-CONT shelf
Global memory for the:

Call processing
Operation and maintenance processing.
17 / 100
1.3.2 Interface Function Blocks

Function
Block Name
Supported by
Description
CN-IF
M-SIFMB in M-L1L2 shelf
ATM access over STM-1 to the Core Network.
Node B-IF
ATM access over STM-1 to all Node Bs.
RNC-IF
ATM access over STM-1 to all RNC Evs.
OMC-IF
ATM access over STM-1 to a router for RNS (RNC Ev and

all Node Bs) operation and maintenance traffic.
M-XWY #P in M-CONT
IP interface for RNS operation and maintenance traffic.
1.3.3 Telecom Function Blocks

Function
Block Name
Supported by
ESU
M-XP (ESU role) in M-L1L2 shelf
Description
MTP3b and SAAL NNI for an interface to the
circuit-switched Core Network.
MTP3b and SAAL NNI for an interface to other
RNC Evs.
Layer 2 links (SAAL-UNI): One for ALCAP and
one for NBAP for all Node Bs connected to the
RNC Ev.
MSU
M-XP (MSU role) in M-L1L2 shelf
MMUX
M-XP (MMUX role) in M-L1L2 shelf
RLC/MACd for UE-dedicated signaling functions.

MACc/sh protocol handling for all cells controlled
by the RNC Ev and the RLC for common channel
handling.
Frame clock management
Handling of the paging function transport
channels (PCH).
DHT
M-XP (DHT role) in M-L1L2 shelf
The MACd diversity handover function for DTCH

and DCCH channels
SPU
M-XP (SPU role) in M-L1L2 shelf
DTCH (PS) and GTP for a packet interface to SGSN.
18 / 100
1.3.4 Miscellaneous Function Blocks

Function Block
Name
Supported by
Description
ETH-SW
M-XWY in:
Ethernet switching function.
M-L1L2 shelf
M-CONT shelf.
DCI
M-XWY in M-L1L2 shelf
RNS-O&M-RoutingM-XP (ESU role) in M-L1L2

shelf
Clock distribution interface.

Routing function for RNS (RNC Ev and all Node Bs)
operation and maintenance traffic.
19 / 100
20 / 100
2 Rack Description
2 Rack Description
This section describes the RNC Ev rack including its configuration, layout
and power supply.
21 / 100
2 Rack Description
2.1 Rack Configuration

The basic configuration consists of one rack that contains:
One M-CONT shelf
One M-L1L2 shelf.
Basic Configuration
MFFTU#0
MFFTU#0
ML1L2 #1
shelf
(Note)
MFANU
MFANU MFANU MFANU
ML1L2 #0
shelf
MFANU
MFANU MFANU MFANU
MCONT
shelf
MFANU
MFANU MFANU MFANU
Basic Rack
Note: The ML1L2#1 shelf is not
mounted in a basic configuration.
revd001
A rack can contain up to three shelves. The maximum configuration consists of:
Two racks with one M-CONT shelf
Five M-L1L2 shelves.
Maximum Configuration
MFFTU#0
22 / 100
MFFTU#0
MFFTU#0
MFFTU#0
ML1L2 #1
shelf
ML1L2 #4
shelf
MFANU MFANU MFANU MFANU
ML1L2 #0
shelf
ML1L2 #3
shelf
MCONT
shelf
ML1L2 #2
shelf
Basic Rack
Extension Rack
revd009
2 Rack Description
2.1.1 RNC Ev MINI Configuration

MFFTU #0
MFFTU #1
MBLSH
MXP #0
MXP #1
MXP #2
MXP #3
MXP #4
MBLPL
MBLPL
MBLPL
MBLPL
MBLPL
MSIFMB #10
MXWY #P
MBLPL
MBLPL
MXWY #R
MBLPL
MBLPL
MBLPL
MBLPL
MBLPL
MBLPL
MBLPL
MBLPL
MBLPL
MBLPL
MBLPL
00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
MFANU
MFANU
MFANU
MFANU
MCP #0
MCP #1
MBLPL
MBLPL
MBLPL
MBLPL
MBLPL
MBLPL
MBLPL
MBLPL
MOMP #P
MXWY #P
MCM #P
MBLPL
MXWY #R
MOMP #R
MBLPL
MBLPL
MBLPL
MBLPL
MBLPL
MBLPL
MBLPL
MBLPL
MBLPL
MBLPL
00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
MFANU
MFANU
MFANU
MFANU
revd004
Note:
Empty board slots (M-BLPL) and empty shelf positions (M-BLSH) appear in
gray.
23 / 100
2 Rack Description
2.1.2 RNC Ev 1000HD Configuration

MFFTU #0
MFFTU #1
MBLSH
MXP #0
MXP #1
MXP #2
MXP #3
MXP #4
MXP #5
MXP #6
MXP #7
MBLPL
MBLPL
MSIFMB #10
MXWY #P
MBLPL
MBLPL
MXWY #R
MSIFMB #15
MBLPL
MBLPL
MXP #18
MXP #19
MBLPL
MBLPL
MBLPL
MBLPL
MBLPL
MBLPL
00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
MFANU
MFANU
MFANU
MFANU
MCP #0
MCP #1
MCP #2
MCP #3
MCP #4
MCP #5
MBLPL
MBLPL
MBLPL
MBLPL
MOMP #P
MXWY #P
MCM #P
MCM #R
MXWY #R
MOMP #R
MBLPL
MBLPL
MBLPL
MBLPL
MBLPL
MBLPL
MBLPL
MBLPL
MBLPL
MBLPL
00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
MFANU
MFANU
MFANU
MFANU
revd005
Note:
24 / 100
gray.
2 Rack Description
2.1.3 RNC Ev 3000HD Configuration

MFFTU #0
MFFTU #1
MBLSH
MXP #0
MXP #1
MXP #2
MXP #3
MXP #4
MXP #5
MXP #6
MXP #7
MBLPL
MBLPL
MSIFMB #10
MXWY #P
MBLPL
MBLPL
MXWY #R
MSIFMB #15
MBLPL
MXP #17
MXP #18
MXP #19
MXP #20
MXP #21
MXP #22
MXP #23
MXP #24
MBLPL
00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
MFANU
MFANU
MFANU
MFANU
MCP #0
MCP #1
MCP #2
MCP #3
MCP #4
MCP #5
MCP #6
MCP #7
MCP #8
MCP #9
MOMP #P
MXWY #P
MCM #P
MCM #R
MXWY #R
MOMP #R
MCP #16
MCP #17
MCP #18
MCP #19
MBLPL
MBLPL
MBLPL
MBLPL
MBLPL
MBLPL
00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
MFANU
MFANU
MFANU
MFANU
revd006
Note:
gray.
25 / 100
2 Rack Description
2.1.4 RNC Ev 1000HSD Configuration

MFFTU #0
MFFTU #1
MBLSH
MXP #0
MXP #1
MXP #2
MXP #3
MXP #4
MXP #5
MXP #6
MXP #7
MBLPL
MBLPL
MSIFMB #10
MXWY #P
MBLPL
MBLPL
MXWY #R
MSIFMB #15
MSIFMB #16*
MXP #17
MXP #18
MXP #19
MXP #20
MXP #21
MXP #22
MXP #23
MXP #24
MXP #25
00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
MFANU
MFANU
MFANU
MFANU
MCP #0
MCP #1
MCP #2
MCP #3
MCP #4
MCP #5
MCP #6
MCP #7
MBLPL
MBLPL
MOMP #P
MXWY #P
MCM #P
MCM #R
MXWY #R
MOMP #R
MBLPL
MBLPL
MBLPL
MBLPL
MBLPL
MBLPL
MBLPL
MBLPL
MBLPL
MBLPL
00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
MFANU
* : Optional
Note:
26 / 100
MFANU
MFANU
MFANU
revd052
gray.
MCP #0
MCP #1
MCP #2
MCP #3
MCP #4
MCP #5
MCP #6
MCP #7
MCP #8
MCP #9
MOMP #P
MXWY #P
MCM #P
MCM #R
MXWY #R
MOMP #R
MCP #16
MCP #17
MCP #18
MCP #19
MCP #20
MCP #21
MBLPL
MBLPL
MBLPL
MBLPL
MXP #0
MXP #1
MXP #2
MXP #3
MXP #4
MXP #5
MXP #6
MXP #7
MXP #8
MXP #9
MSIFMB #10
MXWY #P
MBLPL
MBLPL
MXWY #R
MSIFMB #15
MSIFMB #16*
MXP #17
MXP #18
MXP #19
MXP #20
MXP #21
MXP #22
MXP #23
MXP #24
MXP #25
2 Rack Description
2.1.5 RNC Ev 3000HSD Configuration

MFFTU
MFANU
MFANU
* : Optional
Note:

MFFTU
MBLSH
00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
MFANU
MFANU
MFANU
MFANU
MFANU
00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
MFANU
revd053
Slots of empty boards (M-BLPL) appear in gray.
27 / 100
2 Rack Description
2.2 Rack Layout

2.2.1 Front View
MFFTU#0
MFFTU#1
Protective earth
Power terminal
Eyebolt
Circuit breaker
SG
Wrist strap
terminal
C
L
A
S
S
UL1L
UPO
L
AL
O
PUW
SL
PUO
W
EPO
E
W
PEW
ERRR:
RERTP:
RRXT:
:
RTXO
RTXD01
XU2
C3
T
Shelf
Door
Fan unit
Air intake
Air filter
revd002
Figure 1: RNC Ev Rack Front View
28 / 100
2 Rack Description
2.2.2 Side View

Cable duct
Air exhaust
1234567890123
1234567890123
1234567890123
1234567890123
1234567890123
Eyebolt
Evo
liu
Door
revd048
Figure 2: RNC Ev Rack Side View
2.2.3 Top View
Cable
duct
12345678901234567
12345678901234567
12345678901234567
12345678901234567
12345678901234567
12345678901234567
12345678901234567
12345678901234567
12345678901234567
12345678901234567
Air
exhaust
Eyebolt
Door
revd003
Figure 3: RNC Ev Rack Top View
29 / 100
2 Rack Description
2.2.4 Dimensions and Weight

The following table lists the dimensions and weight for the RNC Ev rack:
Item
Specification
Dimensions
1800 mm (H) x 900 mm (W) x 600 mm (D)
Weight
268 kg / rack or less (Including board weight and maximum

configuration of basic rack)
2.2.5 Environmental Conditions

The following table lists the environmental conditions for the RNC Ev rack:
Type
Description
Operating temperature
-5 to 45 deg. Celsius, complies with ETSI EN 300 019-1-3 Class 3.2.
Humidity
5 to 90%, complies with ETSI EN 300 019-1-3 Class 3.2.
Vibration tolerance
Complies with ETSI ETS300 019-1-3 A1
Fire resistance
Materials used for units, backboards, connectors, and other components must
have an ATSM D2863-77 oxygen index of 28 percent or higher and satisfy UL94
94V-1 or stricter requirements.
Surge protection circuit
Complies with IEC 364-5-54
Fireproof
Opening of external surface complies with the EN/IEC safety standard
Packing
Complies with IEC 60529 (IP20)
2.3 Power Supply

The RNC Ev rack meets the power requirements is listed in the table below:
Item
Requirement
Remarks
Guaranteed range of voltage
-38.4 V to -60 V
Absolute rating
0 V to 60 V
Basic rack
4,053 W
Max. configuration
Extension rack
3,528 W
Max. configuration
Power supply system
6 systems
Per frame
Breaker capacity
60 A
Per power system
Main power
Power consumption
30 / 100
2 Rack Description
2.4 M-FFTU
The M-FFTU unit is mounted with the circuit breaker for a DC -48 V power
supply. It also mounts a noise filter per line. The power supply terminal
is assigned to each shelf.
2.4.1 Front Panel View

The following figure illustrates the front panel view of M-FFTU:
To MCONT
48V
To ML1L2#0
0V
48V
To ML1L2#1
48V
0V
0V
2
MFFTU #0, MFFTU #1
#0
Basic Rack
#1
ML1L2
shelf
ML1L2
shelf
MCONT
shelf
revd008
Item
Specification
Dimensions
120 mm (H) x 315 mm (W) x 211.5 mm (D)
Weight
Less than 4.2 kg
31 / 100
2 Rack Description
2.4.3 Power Supply Distribution

Two M-FFTUs are mounted on the upper side of the rack. One M-FFTU
interface has three power lines, and provides the power supply to each shelf.
Each line has its own circuit breaker and noise filter in the M-FFTU. The
current rating for each breaker is 60 A.
The following figure illustrates the power distribution route from the M-FFTU:
MFFTU
FG
(00)
SG
(10)
(01)
0V
48V
0V
48V
0V
FIL
10
FIL
10
FIL
20
FIL
20
FIL
30
FIL
30
BK
BK
CN10
V1
(20)
48V
V1 V2 V2
CONT Shelf
CN20
FG
SG
V1 ALM V1 ALM V1 ALM V1 ALM
BK
(21)
0V
48V
0V
48V
0V
FIL
11
FIL
11
FIL
21
FIL
21
FIL
31
FIL
31
BK
CN30
V1 V1
(11)
48V
BK
CN11
V2 V2 FG
L1L2#0 Shelf
SG
BK
CN21
V1
CN31
V1 V2 V2 FG
L1L2#1 Shelf
SG
V1 ALM V1 ALM V1 ALM V1 ALM
V1 ALM V1 ALM V1ALM V1ALM
V1ALM V1ALM
V1ALM V1ALM
V1ALM V1ALM V1 ALM V1ALM
V1ALM V1ALM V1ALM V1ALM
FAN FAN
FAN FAN
FAN
FAN FAN
FAN
FAN FAN
FAN
FAN
revd007
2.5 M-FILT
The M-FILT unit is an air filter that removes dust in the forced-air cooling
system. M-FILT is mounted in the air filter slot located above the air intake of
the RNC Ev rack. Refer to Front View (Section 2.2.1) for the mount position.
2.5.1 M-FILT View
12345678901234
12345678901234
12345678901234
12345678901234
12345678901234
12345678901234
12345678901234
12345678901234
12345678901234
12345678901234
12345678901234
12345678901234
12345678901234
12345678901234
12345678901234
12345678901234
12345678901234
12345678901234
12345678901234
12345678901234
12345678901234
12345678901234
12345678901234
12345678901234
revd047
32 / 100
2 Rack Description
Item
Specification
Dimensions
33 mm (H) x 751 mm (W) x 309.5 mm (D)
Weight
Less than 0.5 kg
33 / 100
2 Rack Description
34 / 100
3 Shelf Description
3 Shelf Description
This section describes the RNC Ev shelf configurations and provides functional
information on the shelves.
35 / 100
3 Shelf Description
3.1 M-CONT Shelf

3.1.1 M-CONT Shelf Configurations
The M-CONT shelf fulfills the following roles in the RNC Ev system:
Call processing:
Location registration
Call origination and termination
Other control signal transfers with resource management.
Monitoring:
System startup
Restart
Board status monitoring
Board control.
The M-CONT shelf is equipped with:
2 M-XWY boards
2 M-CM boards
2 M-OMP boards
Up to 20 M-CP boards depending on the system capacity requirements.
The following figure illustrates the M-CONT shelf configuration:
MFANU
MFANU
MFANU
MCP #25
MCP #24
MCP #23
MCP #22
MCP #21
MCP #20
MCP #19
MCP #18
MCP #17
MCP #16
MOMP #R
MXWY #R
MCM #R
MCM #P
MXWY #P
MOMP #P
MCP #9
MCP #8
MCP #7
MCP #6
MCP #5
MCP #4
MCP #3
MCP #2
MCP #1
MCP #0
00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
MFANU
revd010

The following table lists the dimensions and weight for the M-CONT:
36 / 100
Item
Specification
Dimensions
430.7 mm (H) x 751 mm (W) x 356.55 mm (D)
Weight
Less than 52.5 kg (including boards)
3 Shelf Description
3.2 M-L1L2 Shelf

3.2.1 M-L1L2 Shelf Configurations
The M-L1L2 shelf provides the following roles in the RNC Ev system:
Signaling protocol processing
Termination of various protocols related to layer 1 and layer 2
Accommodation of external interfaces to the Core Network, RNC Ev, Node
B and OMC-R.
The M-L1L2 shelf is equipped with:
2 M-XWY boards (used for both ATM and Ethernet switching)
1 to 6 M-SIFMB boards depending on the transmission requirements
1 to 22 M-XP boards depending on the transmission requirements. It is
possible to use unused M-SIFMB slots to mount additional M-XP boards in
the shelf.
MFANU
MFANU
MFANU
MXP #25
MXP #24
MXP #23
MXP #22
MXP #21
MXP #20
MXP #19
MXP #18
MXP #17 / MSIFMB #17
MXWY #R
MBLPL
MBLPL
MXWY #P
MXP #9 / MSIFMB #9
MXP #8 / MSIFMB #8
MXP #7
MXP #6
MXP #5
MXP #4
MXP #3
MXP #2
MXP #1
MXP #0
00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
MFANU
revd012

The following table lists the dimensions and weight for the M-L1L2 shelf:
Item
Specification
Dimensions
430.7 mm (H) x 751 mm (W) x 356.55 mm (D)
Weight
Less than 45.64 kg (including boards)
37 / 100
3 Shelf Description
3.3 Shelf IDs

3.3.1 Shelf ID Jumper Position
Both the M-CONT and M-L1L2 backplanes contain jumpers that give the frame
ID and shelf ID of the boards mounted on the shelf.
The following figure illustrates the position of the frame ID and shelf ID:
00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
MFANU
MFANU
MFANU
MFANU
Backplane
FRAME ID 0
FRAME ID 1
SHELF ID 0
SHELF ID 1
revd038
3.3.2 Jumper Settings

The following table lists the shelf ID and frame ID settings:
Shelf
FRAME ID0
FRAME ID1
SHELF ID 0
SHELF ID 1
Remarks
M-CONT
Close
Close
Close
Close
The shelf ID is set at the

factory.
M-L1L2 #0
Close
Close
Open
Close

factory.
M-L1L2 #1
Close
Close
Close
Open

factory.
M-L1L2 #2
Open
Close
Close
Close

factory.
M-L1L2 #3
Open
Close
Open
Close

factory.
M-L1L2 #4
Open
Close
Close
Open

factory.
Note:
38 / 100
Whenever you add a shelf to a rack, you must set the shelf ID for the shelf.
4 Hardware Modules
4 Hardware Modules
This section describes the functions of the hardware modules in the RNC Ev.
39 / 100
4 Hardware Modules
4.1 M-CP
4.1.1 Functional Description
The main function of the M-CP board is to perform call processing. A maximum
of twenty M-CP boards can be mounted in the M-CONT shelf. The call
processing capacity increases in proportion to the number of boards mounted.
The M-CP boards form a load sharing configuration. All M-CP boards operate
in ACT state and there is no SBY M-CP.
The following figure illustrates the M-CP board:
I/O bus
SV bus
Processor
module
I/O bus
SV bus
Power
supply module
Processor
module
G bus interface module
G bus 1
G bus 2
revd013
Function
Description
Processor
module
The processor module is a sub-board with a:

CPU
Chip set that includes:
Field Programmable Gate Array (FPGA) and Programmable Logic Device (PLD)
chips
RAM chips
Flash memory chips.
Programmable CPU firmware runs on the sub-board.
Programmed logic in the firmware determines how the sub-board controls its processes
and resources.
G bus interface
module
The G-bus interface module is:

The interface at which the M-CPs connect to the redundantly paired M-CMs over
point-to-point buses.
Used for access to common resources on the M-CM.
The transmission rate is 1.08 Gbps.
40 / 100
4 Hardware Modules
CP
4.1.2 M-CP Front View
Ejector
LOCK
ALM
ACT
SBY
Lamps
MP0
MP1
Reset switch
Ejector
revd014
41 / 100
4 Hardware Modules
4.1.3 M-CP Operation and Maintenance

4.1.3.1 Lamps
Lamp
Color
Description
LOCK
Amber
Board in blocked state. It is ready to be removed from the shelf.
Amber
Board undergoing diagnosis.
(blinking)
ALM
Red
Board malfunctioning due to an internal fault.
ACT
Green
Board is in service and is running normally.
Green
Board is in normal operating state, but does not accept the allocation of new
services. When the current services on the board are terminated, the board
switches to LOCK state (the LOCK lamp lights up).
(blinking)
SBY
Amber
The SBY lamp is not used.
4.1.3.2 Connector
Connector
Indication
Interface
Connector
Type
MP0
10 / 100BaseT
RJ-45
Connect the PC to the M-CP board for collecting

the data of CPU #0.
MP1
10 / 100BaseT
RJ-45
Connect the PC to the M-CP board for collecting

the data of CPU #1.
Used to ...
4.1.3.3 Switch
Switch Function
Description
Reset switch
Pressing this switch, turns off all lamps and resets all hardware/software in the board.
Board reset should be performed when the:
ALM or LOCK lamp lights
Board is unstable.
42 / 100
4 Hardware Modules

The following table lists the dimensions and weight for M-CP:
Item
Specification
Dimensions
294 mm (H) x 330.85 mm (W) x 26 mm (D)
Weight
Less than 1.27 kg
4.2 M-OMP
M-OMP is a processor board used for OAM processing only. Two M-OMP
boards are mounted on M-CONT in Present and Reserve (P/R) switching
mode. The M-OMP board has the following functions:
RNC Ev system management
System restart
Fault information collection and storage
Board state supervision
Reset control
Logging (stored on hard disk).
43 / 100
4 Hardware Modules
The following figure illustrates the block diagram of the M-OMP board:
I/O bus
SV bus
Processor
module
Hard Disk
Power
supply module
G bus interface
module
G bus
revd015
Function
Description
Processor module

CPU
FPGA and PLD chips
RAM chips
Flash memory chips.
Programmed logic in the firmware determines how the sub-board controls
its processes and resources.
G Bus interface module
The G-bus interface module is:

The interface at which the M-OMPs connect to the redundantly
paired M-CMs over point-to-point buses.
Used for access to common resources on the M-CM.
The transmission rate is 1.08 Gbps.
Hard disk
The following are stored on this hard disk:

RNC Ev software
Logging data
Traffic data.
44 / 100
4 Hardware Modules
OMP
4.2.2 M-OMP Front View
Ejector
LOCK
ALM
ACT
SBY
Lamps
PLEASE PULL OUT THIS UNIT AFTER LOOK LAMP ON.
ATTENTION
THIS UNIT IS EQUIPPED WHIH A HDD
MP
Reset switch
Ejector
revd016
45 / 100
4 Hardware Modules
4.2.3 M-OMP Operation and Maintenance

4.2.3.1 Lamps
Lamp
Color
Description
LOCK
Amber
Amber
(blinking)
ALM
Red
ACT
Green
Green
The M-OMP starts flashing its ACT lamp when it detects that it does
not have the necessary software on its hard disk. The ACT lamp keeps
blinking up to the moment just before the D-SW is downloaded to the hard
disk in the early commissioning stage.
(blinking)
SBY
Amber
Board is in service and in standby state. It is ready for switch-over to

operating state.
4.2.3.2 Connector
Connector
Indication
Interface
Connector
Type
MP
10 / 100BaseT
RJ-45
Used to ...
Connect the PC to the M-OMP board for collecting the
data.
4.2.3.3 Switch
Switch Function
Description
Reset switch
Board is unstable.
46 / 100
4 Hardware Modules

The following table lists the dimensions and weight for M-OMP:
Item
Specification
Dimensions
294 mm (H) x 330.85 mm (W) x 26 mm (D)
Weight
Less than 1.15 kg
4.3 M-CM
The M-CM board fulfills a shared memory function (global memory part) for the
M-CP/M-OMP boards in the M-CONT shelf, which connect to the M-CM board
via the G bus. Its role includes a:
Semaphore function
Timer function
Calendar function.
The M-CM board also connects to the M-XWY board via the I/O bus to transfer
I/O packets and via the SV bus to control and monitor board status.
The following figure illustrates the block diagram of the M-CM board:
I/O bus
SV bus
Processor
module
Power
supply module
G bus 1
G bus 2
Common
memory module
G bus 22
Synchronization interface
revd017
47 / 100
4 Hardware Modules
Function
Description
Processor
module

CPU
FPGA and PLD chips
RAM chips
Flash memory chips.
Programmed logic in the firmware determines how the sub-board controls its processes
and resources.
Common
memory
module
G bus1 to 22
Connects the M-CM board to the M-CP and M-OMP boards.
Controls access to global memory from 20 M-CP boards and 2 M-OMP boards
Transient state control function
The G-bus interface chip sends or receives data over an 8-bit point-to-point data
channel at a bit rate of 480 Mbps (60 MHz x 8 bits).
Maintains consistency between the global memory on system #P and on system #R
via the synchronization interface.
Common memory
The common memory mounts 1 GB of DDR-SDRAM to support an Error Correcting
Code (ECC) function.
In normal mode, M-CP updates this common memory on the ACT and SBY M-CM
boards.
Stores temporary data shared between the M-CP and the M-OMP.
Synchronization interface
The hardware continuously performs data synchronization from ACT M-CM to SBY M-CM
via the dedicated line.
48 / 100
4 Hardware Modules
CM
4.3.2 M-CM Front View
Ejector
LOCK
ALM
ACT
SBY
Lamps
MP
Reset switch
Ejector
revd018
49 / 100
4 Hardware Modules
4.3.3 M-CM Operation and Maintenance

4.3.3.1 Lamps
Lamp
Color
Description
LOCK
Amber
Amber
(blinking)
The Lock lamp also blinks (ten minutes) during the GM copy phase of the
CM board.
ALM
Red
ACT
Green
Board is in service and running normally.
SBY
Amber
Board is in service and in standby state. It is ready for switch-over to

operating state.
4.3.3.2 Connector
Connector
Indication
Interface
Connector
Type
Used to ...
MP
10 / 100BaseT
RJ-45
Connect the PC to the M-CM board for collecting the data.
4.3.3.3 Switch
Switch Function
Description
Reset switch
Board is unstable.

The following table lists the dimensions and weight for M-CM:
50 / 100
Item
Specification
Dimensions
294 mm (H) x 330.85 mm (W) x 26 mm (D)
Weight
Less than 1.39 kg
4 Hardware Modules
4.4 M-XWY
M-XWY is the common board for the M-CONT and M-L1L2 shelves.
It has the following functions:
ATM cell interface and inter-shelf ATM interface
Ethernet highway switch function between Ethernet data and I/O bus data
I/O bus and SV bus interface
Clock distribution
I/O bus debugging function
OMC-R interface
P/R redundancy.
Note:
ATM is not used when the M-XWY in the M-CONT shelf communicates with the
M-XWY in the M-L1L2 shelf.
The following figure illustrates the M-XWY:
I/O bus
SV bus
Processor
module
Gigabit
Ethernet
Power
supply module
Ethernet
switch
I/O bus 146
SV bus
master
SV bus 146
Fast
Ethernet
Clock
Interface
Clock
distribution
SIF 16
revd019
Function
Description
Processor module

CPU
FPGA and PLD chips
RAM chips
Flash memory chips.
Programmed logic in the firmware determines how the sub-board controls its
processes and resources.
51 / 100
4 Hardware Modules
Function
Ethernet switch
Description
I/O bus signal and U plane information are switched on the Ethernet frame.
Conversion between Ethernet and ATM.
SV bus master
Monitors the bus for faults while managing slave boards.
Clock distribution
Distributes EMA reset, M-XWY ACT, and clock for system synchronization.
52 / 100
4 Hardware Modules
XWY
4.4.2 M-XWY Front View
Ejector
LOCK
ALM
ACT
SBY
Lamps
CU
CL
ET1
ET2
MON
MP
GbEU
GbEL
Reset switch
Ejector
revd020
53 / 100
4 Hardware Modules
4.4.3 M-XWY Operation and Maintenance

4.4.3.1 Lamps
Lamp
Color
Description
LOCK
Amber
Amber (blinking)
ALM
Red
ACT
Green
SBY
Amber
Board is in service and is in the standby state. It is ready for switch-over to

the operating state.
4.4.3.2 Connector
Connector
Indication
Interface
Connector
Type
Used to ...
CU
3V CMOS differential
RJ-45 (*)
For clock and EMARST distribution.

Connects to CL of the shelf with shelf ID
N+1.
CL
3V CMOS differential
RJ-45 (*)
For clock and EMARST distribution.

Connects to CU of the shelf with shelf ID
N-1 if it is not the one at the bottom of the
rack.
ET1, ET2
10 / 100BaseT
RJ-45
For OMC-R/CBC/GPS
GbEU
10G Ethernet
XAUI
For inter-shelf I/O bus connection.

Connects to GbEL with shelf ID N+1.
GbEL
10G Ethernet
XAUI
For inter-shelf I/O bus connection.

Connects to GbEU of the shelf with shelf
ID N-1 if it is not the one at the bottom of
the rack.
MP
10 / 100BaseT
RJ-45
Connect the PC to the M-XWY board for

collecting the data.
MON
10 / 100BaseT
RJ-45
For I/O bus tracing
(*)
54 / 100
: Even though the connector type is RJ-45, DO NOT connect an Ethernet cable here. If you connect an Ethernet
cable by mistake, the board is not damaged but does not work properly.
4 Hardware Modules
4.4.3.3 Switch
Switch Function
Description
Reset switch
Board is unstable.

The following table lists the dimensions and weight for M-XWY:
Item
Specification
Dimensions
294 mm (H) x 330.85 mm (W) x 26 mm (D)
Weight
Less than 1.45 kg
4.5 M-SIFMB
The M-SIFMB board is responsible for the following functions:
Termination of 4 STM-1 optical interfaces
Support of VC4
Clock selection and generation
AAL2 and AAL5 processing
Band control.
55 / 100
4 Hardware Modules
The following figure illustrates the M-SIFMB board:

I/O bus
SV bus
Power
Supply
Module
Processor
Module
BWC Control Module
VC4
STM1
Interface
STM1
Interface
Clock
STM1
Interface
STM1
Interface
4 STM1 Optical Signals
Function
Description
Processor module
Clock
Interface
revd021
CPU
FPGA and PLD chips
RAM chips
Flash memory chips.
BWC control module
Implements the following functions:

Bandwidth control
Shaping and QoS control
VP/VC-based OAM control.
VC4
Supports STM-1 in the non-channeled format.

VC4 cross connect for STM-1.
STM-1 interface
STM-1 line control and alarm detection.
Clock
STM-1 clock transfer to the 'CLOCK distribution block' in the M-XWY board.
56 / 100
4 Hardware Modules
SIF
4.5.2 M-SIFMB Front View
Ejector
LOCK
ALM
ACT
SBY
Lamps
CLASS 1
LASER
PRODUCT
UPPER:TX0
LOWER:RX0
UPPER:TX1
LOWER:RX1
UPPER:TX2
LOWER:RX2
UPPER:TX3
LOWER:RX3
MP
Reset switch
Ejector
revd022
57 / 100
4 Hardware Modules
4.5.3 M-SIFMB Operation and Maintenance

4.5.3.1 Lamps
Lamp
Color
Description
LOCK
Amber
The board is in blocked state. It is ready to be removed from the shelf.
Amber (blinking)
The board is undergoing diagnosis.
ALM
Red
The board malfunctions due to an internal fault.
ACT
Green
The board is in service and running normally.
Green (blinking)
The board is in normal operating state, but does not accept the allocation
of new services.
When the current services on the board are terminated, the board
switches to LOCK state (LOCK lamp lights up).
SBY
Amber
Not used.
4.5.3.2 Connector
Connector
Indication
Interface
Connector Type
Used to ...
TX0, RX0,
TX1, RX1,
TX2, RX2,
TX3, RX3
STM-1 optical interface
LC duplex receptacle
For Iu, Iub and Iur optical connection
MP
10 / 100BaseT
RJ-45
Connect the PC to the M-SIFMB board

for collecting the data.
4.5.3.3 Switch
Switch Function
Description
Reset switch
Board is unstable.
58 / 100
4 Hardware Modules

The following table lists the dimensions and weight for M-SIFMB:
Item
Specification
Dimensions
294 mm (H) x 330.85 mm (W) x 26 mm (D)
Weight
Less than 1.29 kg
4.6 M-XP
The M-XP board is responsible for signaling protocol processing. It has a
CPU and DSPs. Depending on the firmware installed, this board performs
different roles as follows:
ESU role:
Implements SAAL functions to send/receive the following to/from the
M-CONT:
Core Network control signals
Node B control signals
RNC Ev communication signals.
It also has a relay function to communicate with the M-CONT shelf.
MSU role:
Terminates the DCCH in UE, AAL2, and RLC. It has a ciphering/deciphering
function as well as integrity functions.
DHT role:
On Diversity Handover, DHT chooses and composes the identical data
(frame data with the same CFN) from UE sent through different branches. It
copies and distributes data to send the same data to UE through different
branches.
MMUX role:
Multiplex and demultiplex Unit for transport channel termination
Multiplexes or demultiplexes MAC layer information in RACH or FACH
at the radio interface. This information is used to exchange signaling
data and user data.
SPU role:
Terminates the protocol of packet data communicated between the Node
B and the Core Network.
59 / 100
4 Hardware Modules
The following figure illustrates the M-XP board:

SV bus
I/O bus
Processor
module
Power
supply module
PCI interface
AAL
SAR
DSP1
RAM
DSP2
RAM
DSP8
RAM
UTOPIA interface
Gbit Ethernet
interface
I/O bus
I/O bus
revd023
Function
Description
Processor module

CPU
FPGA and PLD chips
RAM chips
Flash memory chips.
AAL5-SAR
AAL5-SAR perform the following functions:

Ends the AAL5 cell sent from XWY-Inf FPGA through the UTOPIA layer 1
interface, and assembles it into a packet to send to the CPU.
Disassembles the packet sent from the CPU into an AAL5 cell, and sends it
to XWY-Inf FPGA through the UTOPIA layer 1 interface.
60 / 100
4 Hardware Modules
Function
DSP
Description
The DSP block has 8 DSPs. As a hardware interface, each DPS has a
UTOPIA Layer 2 interface and a PCI bus interface. The UTOPIA layer 2
works between XWY Inf FPGAs and the PCI bus interface works between
PCI bridges.
DSP firmware processes each protocol, audio and packet data between radio
terminals capsulated in an AAL2 cell.
The M-XP board can change its function via a change to the DSP firmware.
With no change to the hardware of board, you can configure the firmware
to have the board perform the following functions:
DHT
MMUX
SPU
MSU
ESU.
PCI interface
The PCI bus transmits/receives:

Signal processing data (C plane/U plane)
AAL2 type packet data
XWY-Inf FPGA
The AAL5 SAR block.
UTOPIA interface
AAL5-type information is transmitted to the AAL5 SAR block (AAL5 SAR LSI)
through the UTOPIA layer 1 interface.
AAL2-type information is transmitted to the DSP block through the UTOPIA
layer 2 interface.
Gbit Ethernet interface
The Gigabit Ethernet interface that connects the M-XP to the I/O bus to send or
receive ATM cells to or from the M-XWYs.
61 / 100
4 Hardware Modules
XP
4.6.2 M-XP Front View
Ejector
LOCK
ALM
ACT
SBY
Lamps
MP
Reset switch
Ejector
62 / 100
revd024
4 Hardware Modules
4.6.3 M-XP Operation and Maintenance

4.6.3.1 Lamps
Lamp
Color
Description
LOCK
Amber
Amber
(blinking)
ALM
Red
ACT
Green
Green
Board is in normal operating state, but does not accept the allocation of new
services. When the current services on the board are terminated, the board
switches to LOCK state (the LOCK lamp lights up).
(blinking)
SBY
Amber
Board is in service and in standby state. It is ready for switch-over to operating state.
4.6.3.2 Connector
Connector
Interface
Interface
Connector
Type
Used to ...
MP
10 / 100BaseT
(RJ-45)
Connect the PC to the M-XP board for collecting the data.
4.6.3.3 Switch
Switch Function
Description
Reset switch
Board is unstable.

The following table lists the dimensions and weight for M-XP:
Item
Specification
Dimensions
294 mm (H) x 330.85 mm (W) x 26 mm (D)
Weight
Less than 1.03 kg
63 / 100
4 Hardware Modules
4.7 M-FANU
M-FANU contains two fans and provides a forced air cooling system. Four fan
units are mounted in the bottom of each shelf. Each fan has its own ALM lamp
and a fuse for maintenance purposes.
4.7.2 M-FANU Top View
revd025
64 / 100
4 Hardware Modules
4.7.3 M-FANU Front View

0
1
FAN ALM
F0
F1
1.0A
revd026

The following table lists the dimensions and weight for the M-FANU:
Item
Specification
Dimensions
87.5 mm (H) x 178.0 mm (W) x 331.2 mm (D)
Weight
Less than 2.2 kg
65 / 100
4 Hardware Modules
66 / 100
5 Software
5 Software
This section describes the platform software structure, application functional
block and firmware.
67 / 100
5 Software
5.1 Control Part Software Architecture

The following figure describes the main parts of the control software
architecture.
Inside of CP
Application
Platform
Boot
ROM
VxWorks
(BOS)
EOS
Layer
I/O bus
EOS
Layer
FIRM
Hardware
revd054
The control parts of software consists of :

The application part
The platform part
A Boot ROM
VxWorks (Operating System)
EOS Layer
Firmware
Hardware.
Each part communicates to control the RNC Ev.
The application part is separated from the platform part, which means that an
update to the platform part does not impact the application part.
5.1.1 Control Part Roles

There are some roles of the control part.
Four roles in the platform level
Four roles in the application level.
The roles are assigned to specific board of the M-CP and the M-OMP board.
68 / 100
5 Software
5.1.2 Platform Level

CP Role
Description
MCP (Master CP)
All the M-CP and the M-OMP boards boot up simultaneously at the RNC Ev restarting,
One of the M-OMP board is always first started central processing unit and becomes
the MCP.
The MCP is responsible for the initialization of common resources:
GM memory area initialization
OD distribution from the SDM memory onto the GM memory.
After that, other central processing unit in the M-CPs and the M-OMP board can
perform the platform initialization process.
OMP (Operation
and Maintenance
CP)
An M-OMP board is in charge of operation and maintenance functions.

The two M-OMP boards are given the OMP role, one being the "Active OMP" and
the other one being the "Standby OMP".
These two M-OMP boards are always the CP #0 and CP #1. Usually at system
restart, CP #1 becomes the Active OMP whereas CP #0 is the Standby OMP (on
the standby OMP, only booting and platform tasks initialization are performed, the
application software is not started.)
CLP (Call
Processing CP)
The call processing function is ensured by the M-CP boards having the "CLP role".
And each M-CP board has 2 central processing units.
The central processor units have number from #2 to #41.
HCP (Hook
Method CP)
The HCP role is allocated to only one M-CP board, which is the CLP having the
smallest CP number.
The HCP is in charge of distributing the call processing to the appropriated CLP
based on load sharing mechanisms.
In case the CP having the HCP role is in failure or in case it has been locked for
maintenance purpose, the standby HCP takes immediately the HCP role without
any service outage.
69 / 100
5 Software
5.1.3 Application Level

CP Role
MCP (Master CP)
Description
Launches Iub initialization for all Nodes Bs at the RNC Ev restarting.
Establishes all VC routing paths for Iu, Iur and Iub.
Reaches the minimum number of the M-CP boards defined in the OD.
Triggers the application part of software to start the interface initialization.
Receives the 'MTP user signal receive start' and the 'MTP primitive receive start'.
Triggers the Node B Reset procedures.
OMP (Operation
and Maintenance
CP)
An M-OMP board is in charge of operation and maintenance functions.

The two M-OMP boards are given the OMP role, one being the "Active OMP" and
the other one being the "Standby OMP".
The "Active OMP" for AP is the only CPU that:
Receives Node B Restart messages
Performs the Logical O&M on Iub
Receives MTP RESUME messages and performs Iu and Iur interfaces initialization
Communicates with OMC/NEM-R
Is in charge of Operation & Maintenance functions.
DSP
The call processing function is performed by M-CP boards having the DSP role.
RCP
Among all central processing units of the M-OMP and M-CP boards, one is given the
responsibility to manage resource congestion.
This central processing unit is named RCP. It knows the central processing unit
overload for each M-OMP/M-CP board and used these information to launch or not
an Audit.
70 / 100
5 Software
5.2 Application Part Function

Application
O&M functional blocks
ACC
(Access Control)
ESV
(Equipment SuperVisor)
TFO
(TraFfic Observation)
TST (Test)
RPC
(Restart Procedure Control)
RMT
(Remote data Transfer)
ADT (AuDiT)
RACLOAM
(RAC Logical OAM)
OPI
(OPS Interface)
Telecom functional blocks

RAC
(Radio Access Control)
QAAL2
(QAAL2 protocol control)
RANAP
(RANAP protocol control)
RRC
(RRC protocol control)
NBAP
(NBAP protocol control)
RNSAP
(RNSAP protocol control)
revd055
71 / 100
5 Software
5.2.1 Operation and Maintenance Functional Blocks

Functional Block
Description
ESV (Equipment Supervisor)
This function block provides:

RNC equipment supervision
RNC control management
Node B emergency control
Diagnosis.
OPI (OPS Interface)

OMC-R Corba interface: Manager's requests &
responses/notifications to the Manager
OPI/FB's interface: Reception of requests
FB's/OPI interface: Reception of responses
Invalid data files management.
ACC (Access Control)

RAC interface: system information update requests/responses
System Information update procedure OPI interface:
requests/responses/notifications
Access restriction management SIB1(3) update on Iu link failure
SIB1/SIB3/SIB5/SIB11/SIB18 update for Outage Reduction
SIB3 update on CPU overload.
TFO (Traffic Observation)
This function block provides the traffic measurement:

Data collection
Data aggregation
Reporting to the Manager.
RMT (Remote Data Transfer)

File operation
Directory operation
Pack operation.
72 / 100
5 Software
Functional Block
Description
RPC (Restart Procedure Control)

AP initialization
Control of RNC restart
Control of Node B restart
Phase difference measurement
AP SW errors handling
Global mechanism for online OD update.
ADT (Audit)

Audit of the resources associated to calls
Audit control and supervision.
TST
This function block provides the loopback tests on Iu, Iur and Iub
for NEM-R.
RACLOAM (RAC Logical OAM)

Cell Management Iu link supervision
BTS control channel monitoring
Paging list management.
5.2.2 Telecom Functional Blocks

Functional Block
Description
RAC (Radio Access Control)

Ability of each protocol management processing
Call handling
Take a traffic
Connect a radio link.
RRC (RRC Protocol Control)
Provides encoding/decoding of Uu protocol messages.
NBAP (NBAP Protocol Control)
Provides encoding/decoding of NBAP protocol messages.
RANAP (RANAP Protocol Control)
Provides encoding/decoding of RANAP protocol messages.
RNSAP (RNSAP Protocol Control)
Provides encoding/decoding of RNSAP protocol messages.
QAAL2 (QAAL Protocol Control)
Provides encoding/decoding of ALCAP protocol messages.
73 / 100
5 Software
5.3 Software Files

5.3.1 Downloaded Software (D-SW)
There are two types of software. One is O-SW (Origin software). Other is
D-SW (Downloaded software.)
The O-SW has been installed in each board at factory and is not updated
usually. The role of the O-SW is initial set up of the each board such as boot.
There are two types of the D-SW.
Load Module
Firmware.
The D-SW is necessary to operate the RNC Ev.
5.3.1.1 Load Module

The Load Module contains the executable software of the processor board.
The Load Module is installed on the following boards:
M-CP
M-OMP.
5.3.1.2 Firmware
Firmware is software installed in boards to perform basic hardware control. It is
possible to replace firmware as necessary to add or upgrade functions.
Firmware is installed on the following boards:
M-CM
M-XWY
M-SIFMB
M-XP.
5.3.2 Office Data

The Office Data file contains information on:
Network Element configuration
Transport configuration
Radio configuration.
74 / 100
5 Software
5.4 PLD and FPGA Configuration

All boards integrate a 'Configuration NGISL interface Reset controlProgrammable Logical Device' (CNR-PLD). The PLD is a programmable
logic-gate chip, which can be considered a small-scale Field Programmable
Gate Array (FPGA). The PLD can provide various capabilities via programming.
Unlike FPGA, the PLD needs a special programming tool.
FPGA is provided with rewritable programs and can control them. CPU
software boots up first on the CPU daughter board, and then the software
configures FPGAs on the motherboard by sending the data to each FPGA
through CNR-PLD.
The following table summarizes the main hardware requirements for PLD
and FPGA:
Name
Type
CNR
PLD
Functions
Used on ...
FPGA configuration interface
M-CP
Nectar Gate Array Internal Serial Link Version3 (NGISL3)

ASIC interface (bus protocol conversion)
M-OMP
Reset control
EMA function (S-WDT).
M-CM
M-XWY
M-XP
M-SIFMB.
CPGIF
FPGA
G bus interface on M-CP side
M-CP
Bus protocol conversion (device bus <-> G bus)
M-OMP.
G bus access arbitration between two CPUs.

CMGIF
FPGA
G bus interface on M-CM side
M-CM
Global memory access arbitration

Flags.
RAMCNT
FPGA
BWC-MUX
FPGA
Global memory (DDR333 SDRAM) interface (SSTL-2)

Line interface egress processing
M-CM
M-SIFMB
PF cell -> composite cell conversion

QoS classification and shaping
Cell header conversion
Packet discard control (EPD / PPD)
Statistics.
75 / 100
5 Software
Name
Type
BWC-DMUX
FPGA
Functions
Used on ...
M-SIFMB
Line interface ingress processing

Composite cell -> PF cell conversion
OAM F4/F5 control
Cell header conversion
Statistics.
XWYINF
FPGA
I/O bus interface
M-CP
ATM cell encapsulation / decapsulation with Ethernet frames
M-OMP
Data multiplexing / demultiplexing for I/O plane and U plane
M-XP
Switch plane selection
M-SIFMB.
UTOPIA interface for DSPs

Health cell generation/termination
Lamp control
System timing, and frame number reception.
MISC
FPGA
Clock generation / selection
M-XWY
Board status collection

SV bus gating control.
76 / 100
6 Operation and Maintenance

This section describes how to handle the problems that can occur in RNC Ev
equipment during operation and maintenance of the system.
77 / 100
6.1 Overview
6.1.1 OMC-R
The OMC-R is the central supervision and configuration tool for a UTRAN
network or subnetwork. Its management functions cover the following areas:
Cell and network topology management
Radio network evolution and optimization
Transport configuration management
Network level software management
Supervision at network level (state supervision, lock/unlock the network
elements, etc.)
Network alarm management
Network performance and radio trace management
Network time management
RNC Ev OD file replacement.
Other
OMCRs
RNP
Other O&M
systems
OMCR
Itfr
Itfb
RNC Ev
Node B
LMT
(NEMR)
LMT
(NEMB)
SNMP,
Telnet
Switch
revd027
78 / 100
6.1.2 NEM-R
The NEM-R provides equipment management services for the RNC Ev.
It can perform its monitoring and control functions remotely from the OMC-R or
locally from the LMT. The services offered by the NEM-R depend on whether
the RNC Ev is in offline or online mode.
OMCR
OMCR Client
NM Server
NEMR
OMCR Router
DCN
LMT
NEMR
RNC Ev
revd028
6.1.2.1 Local Mode

The NEM-R can access the RNC Ev locally via the maintenance port of the
ACT M-OMP board on the front of the RNC Ev.
Connection with the M-OMP board is used for supervision/control, software
and configuration replacement, and system reset.
6.1.2.2 Remote Mode

The NEM-R on a remote site can access the RNC Ev in one of the following
ways:
Via the ATM interface of the Port #0 on M-SIFMB #10 in M-L1L2 #0
Via the Ethernet interface of M-XWY #P in M-CONT.
Connection with each board is used for supervision and control services and
system reset. Configuration replacement does not support remote mode.
79 / 100
6.2 Equipment Management

6.2.1 Fault Detection and Reporting Route
The RNC Ev supervises the RNC Ev itself always. The RNC Ev detects a
fault automatically.
Faults detected in each board are collected by M-XWY through the SV
bus and then reported to M-OMP through the I/O bus. The following figure
illustrates the fault reporting route:
OMCR
MCP
MCP
MCP
MOMP
NEMR
SV bus
I/O bus
MXWY
MCONT shelf
ML1L2 shelf
MXWY
I/O bus
SV bus
ALM
MXP
MSIFMB
MSIFMB
MXP
revd029
The M-OMP identifies the fault and reports it to OMC-R.

The M-XWY boards collect the FAN and power supply alarms, and send
them to M-OMP.
When M-OMP identifies a board alarm, it resets the faulty board and
performs a diagnosis on that board.
If the board diagnosis confirms a fault on the board, M-OMP lights up the
ALM lamp for the board.
If M-OMP does not receive a health check response from a duplicated I/O
bus, it considers that the board has a fault and lights up the ALM lamp
for that board through the SV bus.
80 / 100
6.2.2 Board State

The following lamps indicate the board state:
ACT (active):
When lit, the ACT lamp on the front of the board indicates the board is
in service and operating.
SBY (standby):
When lit up, the SBY lamp on the front of the board indicates:
The board is in service, operating and in standby.
The SBY board is ready to switch over to ACT state.
LOCK:
When lit up, the LOCK lamp on the front of the board indicates the board is
locked. It is possible to remove the board without additional operations.
Fault processing for this board does not operate in ALM state.
DIAG (diagnosis):
The LOCK lamp on the front panel of the board blinks while the board is
undergoing diagnosis.
Diagnosis is underway for the board to check its availability.
ALM (alarm):
When lit, the ALM lamp indicates a board fault. The board is out-of-service.
6.2.3 Board Configuration

Shelf
Board
RNC Ev MINI
Other RNC Types
M-CONT
M-CP
Load sharing
Load sharing
M-OMP
P/R
P/R
M-CM
Non redundant
P/R
M-SIFMB
Non redundant
Non redundant
M-XP (DHT role)
Non redundant
N+1
M-XP (MMUX role)
Non redundant
N+1
M-XP (SPU role)
Non redundant
Load sharing
M-XP (MSU role)
Non redundant
Load sharing
M-XP (ESU role)
Non redundant
Load sharing
M-XWY
P/R
P/R
M-L1L2
Common
Other RNC
Types
: RNC Ev 1000HD / 3000HD / 1000HSD / 3000HSD.
81 / 100
6.2.4 Fault Processing

6.2.4.1 Redundancy Configuration
In a redundancy configuration, a board fault is processed as described below:
P/R Configuration
N+1 Configuration (*)
Normal
Normal
#0
#1
#N
+1
ACT
SBY
ACT
ACT
ACT
SBY
#0
#1
#N
+1
ALM
ACT
ALM
ACT
ACT
ACT
SBY
ACT
Fault
Fault
recovery
Fault
Fault
recovery
#0
#1
#N
+1
SBY
ACT
ACT
ACT
(*): Load sharing with protection (+1)
revd033
6.2.4.2 Non-Redundancy Configuration

In a non-redundancy configuration, a board fault is processed as described
below:
Load Sharing
NonRedundant
Normal
Normal
#0
#1
#N
ACT
ACT
ACT
#0
#1
#N
ALM
ACT
ACT
#0
#1
#N
ACT
ACT
ACT
Fault
Fault
recovery
ACT
Fault
ALM
Fault
recovery
ACT
revd032
82 / 100
6.2.5 Board Lock Processing

6.2.5.1 Redundancy Configuration
The following figure illustrates the board lock operation with a redundancy
configuration:
P/R Configuration
N+1 Configuration (*)
Normal
Normal
#0
#1
#N
+1
ACT
SBY
ACT
ACT
ACT
SBY
ACT
ACT
#0
#1
#N
+1
LOCK
ACT
LOCK
ACT
ACT
ACT
Shutting
down
Locked
Shutting
down
#0
#1
#N
+1
ACT
ACT
ACT
ACT
Locked
(*): Load sharing with protection (+1)
revd033
6.2.5.2 Non-Redundancy Configuration

The following figure illustrates the board lock operation with a non-redundancy
configuration:
Load Sharing
NonRedundant
Normal
Normal
#0
#1
#N
ACT
ACT
ACT
#0
#1
#N
ACT
ACT
ACT
#0
#1
#N
LOCK
ACT
ACT
Shutting
down
Locked
ACT
Shutting
down
ACT
Locked
LOCK
revd034
6.3 Diagnosis and Health Check

6.3.1 Power-up Diagnosis
Power-up diagnosis is executed on power up of each board. If the result is
OK, then the board switches to ACT or SBY state. If it is not OK, the board
switches to ALM state.
6.3.2 Automatic Diagnosis

If a fault is detected in a board, M-OMP declares an ALM state for that board
and executes a detailed diagnosis. M-OMP turns on the ALM lamp of the board
when the diagnosis determines a fault on the board.
If the diagnosis result is not OK, the test information is stored in the hard disk of
the RNC Ev. The stored result information can be obtained using the NEM-R.
83 / 100
6.3.3 Manual Diagnosis

The operator can perform a diagnosis on an individual hardware board using
the NEM-R. When the diagnosis is started from the NEM-R, the corresponding
board is in LOCK state. The diagnosis result is logged in the file specified
by the operator.
6.3.4 Health Check

The health check monitors the I/O bus condition between target boards.
To ensure that you can use the SBY side of the highway in case of switch-over,
the health check mechanism is implemented as illustrated in the following figure:
ML1L2 #0 shelf
Health
check
MXWY
(ACT)
MXP
MXP
MXP
MSIFMB
Health
check
MXWY
(SBY)
MCONT shelf
Health
check
MXWY
(ACT)
MOMP
(ACT)
MOMP
(SBY)
CPU #1
Result
CPU #0
Result
MCP
MCM
Health
check
MXWY
(SBY)
Result
revd035
I/O messages are exchanged between M-XWY and subordinate boards.

The health check operation is performed between the M-XWY board and the
associated boards on the shelf. All health check results gathered by the
M-XWY board are sent to ACT M-OMP.
84 / 100
6.4 Hard Disk Operation

The M-OMP board hard disk integrates a mirroring redundancy system.
The files in the hard disk of the ACT and SBY M-OMP boards are synchronized
via a software operation. The hard disk of the SBY M-OMP board is overwritten
with the contents of the ACT M-OMP board via mirroring operation. However, a
part of the directory is not subject to mirroring. If one M-OMP board becomes
LOCKED, hard disk mirroring is stopped, which means that hard disk mirroring
is not always performed continuously.
Mirroring is classified into two types:
Per-file synchronization (COPY and DELETE) in ACT M-OMP
Batch file monitoring in a non-active M-OMP undergoing restoration:
LMT
HD
HD
(SFTP)
Active
Board
Standby
(SFTP) OMCR
MOMP #P
MCP
MOMP #R
MCM
MOMP#P
a
\hd0
(5GB)
MOMP#R
\hd0
(5GB)
FTP
FILE
FILE
COMMISS
COMMISS
ACCEPT
ACCEPT
TRAFFIC
TRAFFIC
\hd1
(5GB)
HISTORY
d
\hd2
(10GB)
FTP
\hd1
(5GB)
HISTORY
RESTART
RESTART
DIAGNOSIS
DIAGNOSIS
VENDOR
TRACE
\hd2
(10GB)
VENDOR
TRACE
Legend
: Nonmirroring
: Mirroring
revd039
The following table lists the file types stored on the hard disk:
Name of Directory
File Type
Allocation Size
/hd0/a/FTP
D-SW and OD file for upload and download
5 GB
/hd0/b/FILE
D-SW and OD file update and rack inventory file
/hd0/f/COMMISS
Commissioning file and rack inventory file
/hd0/g/ACCEPT
Accepted OD file
(directory space is shared)
85 / 100
Name of Directory
File Type
Allocation Size
/hd1/c/TRAFFIC
Traffic data
5 GB
/hd1/c/HISTORY
History of equipment supervision
/hd1/c/RESTART
Restart data
/hd1/c/DIAGNOSIS
Diagnosis
/hd2/d/VENDOR
Trouble analysis information
/hd2/e/TRACE
Trace data
10 GB
6.5 System Defence Mechanism

The total usage rate of the call processing units in the RNC Ev is measured
periodically.
The RNC Ev detects overload state on the M-CP board when the usage rate
exceeds the predetermined thresholds.
The RNC Ev performs an access classes restriction according to the overload
ratio to solve the overload status. The access class restriction means to restrict
originating/terminating call from UE.
In addition to the defence mechanism for the M-CP board, the RNC Ev has
overload detection and handling mechanism for the M-XP(DHT, MMUX and
SPU function) board and SIF board.
For the DHT function on the M-XP board, overload is prevented with an
admission control based on the number of simultaneous channels. The
admission control is performed each time when resources for the DHT on the
M-XP board are required.
For the SPU function on the M-XP board, overload is prevented an admission
control based on:
the number of simultaneous connections
the requested bandwidth.
For the MMUX function on the M-XP board, FACH and PCH overload are
detected.
The MMUX overload actions are
the new paging requests is ignored while a PCH overload is detected.
excess FACH data frames are discarded while a FACH overload is detected.
For SIF board, overload is prevented by a connection admission control on Iub,
Iur, Iu-CS and Iu-PS, called at each new ALCAP request.
86 / 100
6.6 Performance Measurement

One performance measurement (PM) task per the RNC Ev is activated at
the RNC initialization.
The PM counters are recorded every hour except the RNC restart period.
The PM counters are saved in files on the M-OMP board. The saved files
are kept during 24 hours.
The OMC-R collects the PM data from the RNC Ev per every hours.
For more information of the PM counters, refer to the PM Counters Dictionary.
6.7 RNC Ev Start-Up

In the initial stage of the commissioning procedure, Downloaded Software
(D-SW) is not stored on the local SDM board, so this procedure does not work.
Origin Software (O-SW, similar to a boot file), however, is stored on a protected
area of each board. When O-SW is operating, the LMT can use FTP protocol.
In short, it is possible to download D-SW and OD to the hard disk manually.
The system restarts after completing the D-SW and OD download, and the
RNC Ev system starts up.
6.8 Security between RNC Ev and OMC-R

The RNC Ev and the OMC-R is usually connected via the DCN.
The RNC Ev supports the following security solutions between the RNC Ev
and the OMC-R / NEM-R:
The Secure SHell (SSH) / Secure File Transfer Protocol (SFTP) is used to
secure file transfer and the remote shell commands.
The Secure Sockets Layer (SSL) is used to secure Internet Inter-ORB
Protocol (IIOP) exchanges.
6.8.1 Protection by SSH/SFTP

The following protections are provided via the SSH/SFTP:
Authentication of the OMC-R and the RNC Ev, when achieving:
File transfer by STFP
Remote shell commands.
Authentication of the NEM-R and the RNC Ev when achieving file transfer
via the SFTP.
87 / 100
The following figure illustrates the protection via the SSH/SFTP:
The following table lists SSH/SFTP users of the Evolium UTRAN:

User
OMC SSH defense
user
Role
This system user can be used to control updating
the security key in the RNC Ev.
It can be activated or deactivated inside the RNC Ev
from the OMC-R with dedicated command.
It must be activated before all the security update
operations and also at initial installation.
The associated configuration file must be installed
only once in order to avoid the risk to install a
corrupted configuration file during a key update.
The exchanges of this system user are encrypted.
The key of this system user is not changeable.
OMC SSH user
It is used for launching remote commands (SSH or

SFTP) from the OMC-R to the RNC Ev.
The key of this system user can be changed.
The exchanges of this system user are encrypted.
OMC SFTP user

NEM-R SFTP user
They can launch SFTP command from the OMC-R

or the NEM-R to the RNC Ev.
The exchanges of these system users are not
encrypted because the NEM-R is regarded as
unsecured.
The NEM-R SFTP user is protected with the
passphrase (encrypted).
88 / 100
6.8.2 Protection by SSL

The following protections are provided via the SSL:
Authentication of the OMC-R and the RNC Ev when achieving IIOP
exchanges
Authentication of the NEM-R and the RNC Ev when achieving IIOP
exchanges.
6.9 Load RNC Ev Software

The D-SW (firmware/Load Module) and OD are download from:
LMT to RNC Ev via FTP before the commissioning.
OMC-R / NEM-R to the RNC Ev via SFTP after the commissioning.
89 / 100
The user flash ROM on the CPU daughter board of the M-OMP board stores
the LM and OD, and the M-OMP transfers them to the global memory on M-CM
board for distribution. All M-CP boards retrieve the LM and OD on the global
memory for the telecom processing.
ACT MOMP
OMCR
Each Board
Do
wn
Hard Disk
lo
ad
(S
sdram
FT
P)
hd0/a/FTP
Ed: n
Ed: n
)
TP
DSW
(S
ad
o
nl
ow
Loading
Move File
Update
sdmwork
hd0/b/FILE
Ed: n
Ed: n
Update
LMT
revd040
OMCR
ACT MOMP
Dow
Hard Disk
nlo
ad
(SF
TP)
P)
hd0/a/FTP
Ed: n
OD
FT
ad
lo
wn
Do
(S
Update
Move File
MCM
MOMP
Ed: n
hd0/b/FILE
LMT
Ed: n
Update
Global
memory
Loading OD
MCP
revd051
6.10 Emergency Reset of M-OMP

The M-OMP board has a Super-Watchdog Timer (S-WDT).
RNC Ev software resets S-WDT so that the timer never expires while the
RNC Ev operates normally.
When S-WDT in the ACT M-OMP board exceeds the allotted time period (5
min), the board starts an EMA emergency reset process.
The hardware saves information on the cause of the reset (=EMA) in the
reset cause register in CNR-PLD and starts a safety boot reset. The ACT
M-OMP board switches to SBY, and at the same time the SBY M-OMP board
switches to ACT.
After the safety boot reset, the ACT M-OMP board reports the EMA event to
the M-XWY board in the same shelf via SV bus and requests that the M-XWY
board broadcasts the XWY EMA signal.
All boards in the shelf are reset by the XWY EMA signal from the M-XWY board.
90 / 100
6.11 Replace Parts

The RNC Ev parts replacement procedure applies to the following parts:
Board
Fan
Fan unit fuse
Air filter
M-FFTU.
Refer to the RNC Ev Maintenance Handbook for details on the replacement
procedure.
FAN unit fuse (2 fuses / FAN unit, 24 fuses / Rack,
1.0A / fuse)
FFTU Unit
F0
MFFTU #0
MFFTU #1
F1
Fan Unit
Board
Air Filter Unit
12345
123456
12345
12345
12345
123456
12345123456
123456
123456
123456
revd049
6.12 Maintenance Port

The Maintenance Port (MP) is used for debugging each board. The IP address
of the MP for each board is set at the commissioning of the RNC Ev.
First part of the IP address can be changed to avoid conflict of the IP address
between Evolium UTRAN and other IP network. The remaining parts of the IP
address are fixed for each board.
The changing of the IP address of the MP is defined in IPCONFIG.WRF file
saved in the M-OMP board.
91 / 100
6.12.1 M-CONT Shelf IP Address

The following table lists the IP addresses of the boards in the M-CONT shelf:
Note:
The value of 'a' for in the IP address is the same one in the IPCONFIG.WRF
file (default is '31').
Board
Slot
MP
IP Address
M-CP #0
a.33.0.0
a.34.0.0
a.33.0.1
a.34.0.1
a.33.0.2
a.34.0.2
a.33.0.3
a.34.0.3
a.33.0.4
a.34.0.4
a.33.0.5
a.34.0.5
a.33.0.6
a.34.0.6
a.33.0.7
a.34.0.7
a.33.0.8
a.34.0.8
a.33.0.9
a.34.0.9
M-CP #1
M-CP #2
M-CP #3
M-CP #4
M-CP #5
M-CP #6
M-CP #7
M-CP #8
M-CP #9
M-OMP #P
10
a.33.0.10
M-XWY #P
11
a.33.0.11
M-CM #P
12
a.33.0.12
M-CM #R
13
a.33.0.13
M-XWY #R
14
a.33.0.14
92 / 100
Board
Slot
MP
IP Address
M-OMP #R
15
a.33.0.15
M-CP #16
16
a.33.0.16
a.34.0.16
a.33.0.17
a.34.0.17
a.33.0.18
a.34.0.18
a.33.0.19
a.34.0.19
a.33.0.20
a.34.0.20
a.33.0.21
a.34.0.21
a.33.0.22
a.34.0.22
a.33.0.23
a.34.0.23
a.33.0.24
a.34.0.24
a.33.0.25
a.34.0.25
M-CP #17
M-CP #18
M-CP #19
M-CP #20
M-CP #21
M-CP #22
M-CP #23
M-CP #24
M-CP #25
17
18
19
20
21
22
23
24
25
93 / 100
6.12.2 M-L1L2 #0 Shelf IP Address

The following table lists the IP addresses of the boards in the M-L1L2 #0 shelf:
Note:
The value of 'a' for in the IP address is the same one in the IPCONFIG.WRF
file (default is '31').
Board
Slot
MP
IP Address
M-XP #0
a.33.1.0
M-XP #1
a.33.1.1
M-XP #2
a.33.1.2
M-XP #3
a.33.1.3
M-XP #4
a.33.1.4
M-XP #5
a.33.1.5
M-XP #6
a.33.1.6
M-XP #7
a.33.1.7
M-XP #8
a.33.1.8
M-XP #9
a.33.1.9
M-SIFMB #10
10
a.33.1.10
M-XWY #P
11
a.33.1.11
M-XWY #R
14
a.33.1.14
M-SIFMB #15
15
a.33.1.15
M-SIFMB #16
16
a.33.1.16
M-XP #17
17
a.33.1.17
M-XP #18
18
a.33.1.18
M-XP #19
19
a.33.1.19
M-XP #20
20
a.33.1.20
M-XP #21
21
a.33.1.21
M-XP #22
22
a.33.1.22
M-XP #23
23
a.33.1.23
M-XP #24
24
a.33.1.24
M-XP #25
25
a.33.1.25
94 / 100
6.13 Inventory
6.13.1 Hardware Inventory Information
RNC Ev provides hardware inventory for each board. This includes the
following hardware information:
Year of manufacture
Serial number
Drawing number.
The RNC Ev manages the hardware inventory data in the EEPROM of each
board.
You can confirm the hardware inventory information stored in the EEPROM
of board with the NEM-R.
The following table lists the format of the hardware inventory:
6.13.1.1 Hardware-Specific Information

Item
Format
Example
Board ID
4-digit BCD
0001
Remarks
M-CP: 0001
M-OMP: 0002
M-XWY: 0003
M-CM: 0004
M-XP: 0005
M-SIFMB: 0006.
Board Name
8-digit ASCII
M-CP
If a board name is shorter

than 8 characters, the
remaining fields contain
spaces.
Board Drawing No.

(Fujitsu format)
14-digit ASCII
M18B-6006-H500
Board Drawing No.

(Alcatel format)
10-digit ASCII
3BK26764AA
Production Date
8-digit BCD
20041120
YYYYMMDD
Serial No.
8-digit BCD
00000025
Serial number identifying

each board uniquely.
Factory ID
4-digit BCD
0064
Board manufacture location

Fujitsu Nasu Factory: 0064
Factory Test Date
8-digit BCD
20041210
YYYYMMDD
95 / 100
Item
Format
Example
Remarks
Test Personnel ID
4-digit BCD
3407
No specific rule for numbering

if it can uniquely identify the
test personnel in the factory.
Global MAC Address

for debug port CPU
#0
12-digit HEX
0e00571229e3
Global MAC Address

for debug port CPU
#1
12-digit HEX
0e00571229e4
Valid for M-CP only. Contains

zeros for other boards.
ET1- MAC Address
12-digit HEX
0e00571229e9
Valid for M-XWY only
ET2- MAC Address
12-digit HEX
0e00571229ea
Valid for M-XWY only
First Commissioning
Date
8-digit BCD
20050201
YYYYMMDD
End Warranty Date
8-digit BCD
20050512
YYYYMMDD
Last Repair Date
8-digit BCD
20081001
YYYYMMDD
Board Hardware
Version (Fujitsu
format)
3-digit ASCII
03B
First 2 digits are taken from

the working version number
and the last digit is taken from
the functional version.
Board Hardware
Version (Alcatel
format)
4-digit ASCII
AA01
First 2 digits are taken from

the working version number
and the last 2 digits are taken
from the functional version.
Checksum
8-digit HEX
0B3F9721
Sum of the hardware

inventory data values.
96 / 100
This field contains the valid

date during commissioning.
At the factory, it contains 0s.
6.13.1.2 Hardware Version Information

Item
Format
Example
Remarks
First Commissioning
Date
8-digit BCD
20050201
YYYYMMDD
End Warranty Date
8-digit BCD
20050512
YYYYMMDD
Last Repair Date
8-digit BCD
20081001
YYYYMMDD
Board Hardware
Version (Fujitsu
format)
3-digit ASCII
03B
First 2 digits are taken from the working version

number and the last digit is taken from the functional
version.
Board Hardware
Version (Alcatel
format)
4-digit ASCII
AA01
First 2 digits are taken from the working version

number and the last 2 digits are taken from the
functional version.
Checksum
8-digit HEX
0B3F9721
Sum of the hardware inventory data values.
This field contains the valid date during

commissioning. At the factory, it contains 0s.
6.13.2 Rack Inventory

The RNC Ev provides inventory data per rack as well as additional information
relating to the site. The RNC Ev manages rack inventory data based on a file in
the hard disk of the M-OMP board.
You can confirm the rack inventory information file stored on the hard disk of
M-OMP using the NEM-R.
The following tables list the format of the rack inventory:
6.13.2.1 Rack-Specific Information

Item
Format
Example
Remarks
RNC Type
2-digit ASCII
EV
EV: RNC Ev
Configuration Type
2-digit BCD
01
01: Basic rack

02: Basic rack and 1st extension rack
st
03: Basic rack, 1 extension rack and

nd
2 extension rack.
RNC ID
4-digit BCD
0001
Value from 0000 to 9999
Rack ID
4-digit BCD
0001
Rack Name
8-digit ASCII
M-CBS
Drawing Number
14-digit ASCII
M18B-1021-J010
(Fujitsu format)
97 / 100
Item
Format
Example
Remarks
Drawing Number
10-digit ASCII
3BK25763AA
Production Data
8-digit BCD
20041220
Serial Number
8-digit BCD
00000025
Factory ID
4-digit BCD
0064
Factory Test Data
8-digit BCD
20050212
Year Month Day =YYYYMMDD
Test Personnel ID
4-digit BCD
3407
(Alcatel format)
6.13.2.2 Rack Version Information

Item
Format
Example
Remarks
First Commissioning
8-digit BCD
20050520
End Warranty Date
8-digit BCD
20080520
Last Repair Date
8-digit BCD
20051220
Hardware Version
3-digit ASCII
05A
4-digit ASCII
AE01
Date
(Fujitsu format)
Hardware Version
(Alcatel format)
Site Information
199-digit
ASCII
Location identification
User-defined text
Network identifier.
End of Site
Information
Characters Length
3-digit BCD
001
Value from 000 to 999. This

information is for the operator only.
98 / 100
6.14 Hardware Information

6.14.1 Board Name
The following table lists the RNC Ev board name and drawing number:
Board Mnemonic
Full Name
Reference (Fujitsu
Format)
Reference (Alcatel
Format)
M-CP
Control processor board
M18B-6006-H500
3BK 26764 AA
M18B-6006-H610 (*)
M-OMP
M-XWY
Operation and maintenance

processor board
M18B-6006-H510
Extra highway board
M18B-6006-H520
3BK26765 AA
M18B-6006-H620 (*)
3BK26767 AA
M18B-6006-H630 (*)
M-CM
Common memory board
M18B-6006-H530
3BK26766 AA
M18B-6006-H640 (*)
M-XP
Extra processing board
M18B-6006-H540
3BK26768 AA
M18B-6006-H650 (*)
M-SIFMB
STM-1 interface board
M18B-6006-H471
3BK26769 AA
M18B-6006-H661 (*)
(*)
: These boards comply with the Restriction of Hazardous Substances (RoHS).
6.14.2 Board Label

The following figure describes the information on the RNC Ev board front label:
123456789012345678901
123456789012345678901
123456789012345678901
123456789012345678901
123456789012345678901
123456789012345678901
123456789012345678901
123456789012345678901
123456789012345678901
123456789012345678901
123456789012345678901
123456789012345678901
123456789012345678901
123456789012345678901
123456789012345678901
123456789012345678901
123456789012345678901
123456789012345678901
123456789012345678901
123456789012345678901
123456789012345678901
ICS
(Item Change
Status)
RV
(Realization
Variant)
Mnemonic
(board name)
J2031200004
LOCK
ALM
ACT
SBY
QR
Code
MXP
3BK 26768 AAAB01
J2031200004
MXP
3BK xxxx
zoom
Serial
Number
3BK Code
revd037
99 / 100
6.15 DIP Switch

DIP switches are mounted on the component side of boards for debugging
purposes. The default settings of the DIP switches, which are set at the factory,
are all OFF as shown in the following figure:
Board
Location
MCP
SW9H
Setting
1 2
OFF
MOMP
SW9H
1 2
OFF
MCM
SW1F
1 2
OFF
MSIFMB
SW2M
1 2 3 4
OFF
MXP
SW1K(SW1)
1 2 3 4
OFF
revd050
100 / 100

Evolium A9140 RNC Evolution Description 211310000e05

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Evolium A9140 RNC Evolution Description 211310000e05

Încărcat de

Drepturi de autor:

Formate disponibile

Alcatel UMTS

Evolium A9140 RNC Evolution

3BK 21131 AAAA TQZZA Ed.05

BLANK PAGE BREAK

3BK 21131 AAAA TQZZA Ed.05

3BK 21131 AAAA TQZZA Ed.05

3BK 21131 AAAA TQZZA Ed.05

3BK 21131 AAAA TQZZA Ed.05

3BK 21131 AAAA TQZZA Ed.05

3BK 21131 AAAA TQZZA Ed.05

The guide is intended for:

The reader must have a general knowledge of UMTS.

3BK 21131 AAAA TQZZA Ed.05

3BK 21131 AAAA TQZZA Ed.05

Radio Access Network (RAN)

3BK 21131 AAAA TQZZA Ed.05

The connection diagram of the RNC Ev is illustrated below.

1.2 Interface Architecture

3BK 21131 AAAA TQZZA Ed.05

The following table describes each external interface:

The OMC-R and the RNC Ev are connected via the:

3BK 21131 AAAA TQZZA Ed.05

1.2.2 Internal Interfaces

1.2.2.2 ATM Cell Interface

3BK 21131 AAAA TQZZA Ed.05

1.2.2.3 SV Bus Interface

3BK 21131 AAAA TQZZA Ed.05

1.2.2.4 G Bus Interface

3BK 21131 AAAA TQZZA Ed.05

1.2.3 Reference Clock

3BK 21131 AAAA TQZZA Ed.05

1.3 RNC Ev Function Blocks

Clock Distribution Interface

1.3.1 Processing Function Blocks

M-CP in M-CONT shelf

Processing capability for RNC Ev call control functions.

M-OMP in M-CONT shelf

Processing capability for RNC Ev operation and

M-CM in M-CONT shelf

Global memory for the:

3BK 21131 AAAA TQZZA Ed.05

1.3.2 Interface Function Blocks

M-SIFMB in M-L1L2 shelf

ATM access over STM-1 to the Core Network.

M-SIFMB in M-L1L2 shelf

ATM access over STM-1 to all Node Bs.

M-SIFMB in M-L1L2 shelf

ATM access over STM-1 to all RNC Evs.

M-SIFMB in M-L1L2 shelf

ATM access over STM-1 to a router for RNS (RNC Ev and

IP interface for RNS operation and maintenance traffic.

1.3.3 Telecom Function Blocks

M-XP (ESU role) in M-L1L2 shelf

M-XP (MSU role) in M-L1L2 shelf

M-XP (MMUX role) in M-L1L2 shelf

RLC/MACd for UE-dedicated signaling functions.

M-XP (DHT role) in M-L1L2 shelf

The MACd diversity handover function for DTCH

M-XP (SPU role) in M-L1L2 shelf

DTCH (PS) and GTP for a packet interface to SGSN.

3BK 21131 AAAA TQZZA Ed.05

1.3.4 Miscellaneous Function Blocks

Ethernet switching function.