BSC6900 Data Configuration Issue 1

BSC6900 Data Configuration
In compliance with ISO-9001 Cost Effective Quality Training Manpower Services

Objectives
Upon completion this course, you will be able t
o:
– Master the procedure and methods of data
configuration of BSC6900
– Master global data configuration
– Master equipment data configuration
– Master the interface data configuration
– Master cell data configuration
Page 2
References
• 《 RNC System Description 》
• 《RNC Initial Configuration
Guide》
Page 3
Chapter 1 Data Configuration Overview
Chapter 2 Global Data Configuration
Chapter 3 Equipment Data Configuration
Chapter 4 Interface Data Configuration
Chapter 5 Cell Data Configuration
Page 4
Data Configuration Overview
• Scenario 1: st  Scenario 2: RNC is running and providing ser

vice
and alone RN
C during initi CN
al setup CN
RNC
RNC
Node B
Node B
Page 5
Data Configuration Overview
• Configuration Procedures of initial setup R

NC Start
UE UTRAN CN
Uu Iu
BSC6810
Global data
configuration Iub
Equipment dat NodeB

MSC Server
a
Iu-CS
configuration
Interface data Iur
configuration
MGW
NodeB
Iu-PS
Cell data configuration

Iub
NodeB SGSN
End BSC6810
Page 6
Page 7
Global Parameter Configuration
• Identify the RNC in a network.

ADD URNCBASIC
( offline command)
ADD UCNOPERATOR
(offline command)
CN 1 CN 2 SET SCTPSVRPORT
(optional)
RNC1 RNC2 RNC3
Page 8
• Adding OSP to the RNC
RNC2 is using SS7 and uniquely id

CN entify itself in a SS7 network with a
DPC2 n OPC,
MML: ADD OPC
RNC1 RNC2
STP
DPC1 OPC
Page 9
• Activating the License File
License file:
RNC ID
CS Capacity RNC FAM
PS Capacity
Functions
Etc.
ACT LICENSE
DSP LICENSE
LST LICENSE
Page 10
• Setting the Internal Subnet Number of the RNC (offline command)
WRBS
W
R
S
S SCU
BAM
80.x.x.x
SET SUBNET
Page 11
• Adding RNC Global Location Data
ADD ULAC
ADD URAC
ADD USAC
LAC1 ADD UURA
RAC2
RAC1
SAC2
SAC1 LAC2
Page 12
Configuring M3UA Local and Destination Entities
• ADD M3LE
• ADD M3DE
Page 13
• Adding SIB1 parameters

– SIB1 includes:
• CN domain NAS system information
• UE timers and constants in idle mode
• UE timers and constants in connected mode
– CN NAS system information (ADD UCNDOMAIN)
• CN domain NAS information includes CS domain NAS information
and PS domain NAS information. The information is compulsory
– CN Node information (ADD UCNNODE)
Page 14
Summary
• In the previous 2 chapters, we have learnt the procedures of data configurations

for the RNC, and the global data to be set.
• Global data includes the RNC basic information, location area information, RNC
subnet information and OPC information etc.
Page 15
Page 16
Equipment Data Configuration
• Equipment Data Configuration include:

– Setting RNC Equipment Description
– Modifying an RSS Subrack
– Adding an RBS Subrack
– Configuring RNC Clock Data
– Setting RNC Time
– Setting NodeB Time Sources
Page 17
• Setting RNC Equipment Description
BAM
RNC archive is only

saved in the BAM:
•System ID RNC FAM

•Contact information
•System location
•System services
•Etc.
MML: SET SYS
Page 18
• Modifying an RSS Subrack MOD SUBRACK

ADD BRD
14 15 16 17 18 19 20 21 22 23 24 25 26 27
Rear board R D RD RD RD RD RD O O R R R R
I P I P I P I P I P I P M M I I I I
NU NU NU NU NU NU U U N N N N
Tb Tb Tb Tb Tb Tb a a T T T T
Backplane
Backplane
S S S S S S S S DS DSDS DS G G
Front board P P P P P P C C P P PPPP PP C C
U U U U U U U U UU UUUU UU U U
a a a a a a a a ba ba ba ba a a
00 01 02 03 04 05 06 07 08 09 10 11 12 13
Page 19
Interface boards in ATM networking
• There are 3 boards support ATM networking:
– ATM over E1/T1（ AEUa）
– ATM over E1/T1 over SDH（channelized SDH）（ AO
Ua）
– ATM over SDH（unchannelized SDH）（UOI_ATM）
• There are 5 boards support IP networking:
– PEUa
– POUa
– UOI_IP(POSa)
– FG2a
– GOUa
Page 20
AEUa/PEUa board
• Support board level backup－binding mode

MML command:
ADD BRD: SRN=0, BRDTYPE=
AEU, SN=14, RED=YES;
This board and port active,
Service process in this way
Slot 14 Slot 15
If port or cable broken,
AEUa AEUa Swap to slot 15
31 31
24 24
E1 Y type cable
23 23
16 16 After swap, slot15/31
become active service
15 15
NodeB1 Service
Service Processed in this way
process 8 8process
7 7
E1 Y type cable 0 0
NodeB2
Page 21
AOUa/UOIa/POSa/POUaboard
• Support board and port backup－apart mode
Commands:
ADD SUBRACK:
ADD BRD: SRN=
Slot 14 active, port 0/14 active, 0, BRDTYPE=AO
Service processed in this way U,
SN=14, RED=YE
If this port broken, port swap to Slo 14 Slot 15 S;
Port 0/15, but active board remain in
slot 14, service processed in this way AOUa AOUa
0 0
E1*N 155M
Service
processing
NodeB 1 1
To DPU
Page 22
AOUa/UOIa board
• Support board and port backup－apart mode
Commands:
ADD SUBRACK:
ADD BRD: SRN=
0, BRDTYPE=AO
Slot 14 active, port 0/14 active, U,
Service processed in this way SN=14, RED=YE
S;
If active board swap to 15, active Slo 14 Slot 15
port in slot 15/0, service
Processed in this way AOUa AOUa
0 0
E1*N 155M
Service Service
processing processing
NodeB 1 1
To DPU
To DPU
Page 23
FG2a/GOUa
• Board and port backup binding ADD SUBRACK:

PIUT14=FG2_OTHER,
– Applied in layer 2 networking

REDT14=Backup_binding
DSP BRD:;
DSP EHTPORT:;
SWP BRD:;
slot14 slot15
FG2a FG2a
0 0 Before swap
Slot14/0 is
1 1 active, service
Data network
2 2 processed in
NodeB1 this way
3 3
4 4
after swap
5 5 Slot15/0 is
active, service
6 6 processed in
7 7 this way
NodeB2
Page 24
FG2a/GOUa
• Board and port backup apart

ADD BRD: SRN=0, BR
– Applied in layer 3 networking DTYPE=FG2, SN=14,
Port broken, s RED=YES;
wap to 15/0
slot14 slot15
FG2a FG2a Before swap
0 0 Slot14/0 is
active, service
1 1 processed in
Data network this way
NodeB1 2 2
3 3
4 IP 4
after swap
5 5 Slot15/0 is
IP active, service
6 6 processed in
7 7 this way
NodeB2
Page 25
FG2a/GOUa
• Board backup, port apart ADD BRD: SRN=0, BR

DTYPE=FG2, SN=14,
– Applied in layer 3 networking RED=YES;
Slot 14 Slot 15
FG2a FG2a
0 0
Slot 14 is active,
1 1 port is load
2 2 sharing
NodeB1 between 14/0
3 IP 3 IP 15/0
4 4
5 5 After swap, 15
Become active,
6 6 But port still in
7 7 Load sharing
mode
NodeB2
Page 26
• Adding an RBS Subrack ADD SUBRACK
14 15 16 17 18 19 20 21 22 23 24 25 26 27
Rear board R D RD RD RD RD RD R R R R R R R R
I P I P I P I P I P I P I I I I I I I I
NU NU NU NU NU NU N N N N N N N N
Tb Tb Tb Tb Tb Tb T T T T T T T T
Backplane Backplane
S S S S S S S S DS DS DSDS D D
Front board P P P P P P C C P P PP P P PP P P
U U U U U U U U UU U U U UU U U U
a a a a a a a a ba ba ba ba b b
00 01 02 03 04 05 06 07 08 09 10 11 12 13
Page 27
• Adding an RBS Subrack

– DIP switch is used to set the RBS subrack no.
Subrack Bit
Number
1 2 3 4 5 6 7 8
Subrack 0 ON ON ON ON ON ON ON OFF
Subrack 1 OFF ON ON ON ON OFF ON OFF
Subrack 2 ON OFF ON ON ON OFF ON OFF
Subrack 3 OFF OFF ON ON ON ON ON OFF
Subrack 4 ON ON OFF ON ON OFF ON OFF
Subrack 5 OFF ON OFF ON ON ON ON OFF
Page 28
• Configuring RNC Clock Data

GPS
BITS
GCK Output to RBS and other boards
CN 8Khz on backplane
or 2Mhz by cable ADD CLKSRC
UOI SET CLK
SET CLKMODE
IU interface
Page 29
• Configuring RNC Time
M2000 RNC NodeB
SNTP client
SNTP
SNTP server
server
BAM SNTP server SNTP client
SET TZ:;
SET SNTPCLTPARA:;
ADD SNTPSRVINFO:;
Page 30
Configuring EMS
• ADD EMSIP
Page 31
Summary
• In the previous chapter, we have learnt the equipment data.

• Equipment data includes the subrack, clock, time configuration etc.
Page 32
Page 33
Sector 1 Iub Interface Data Configuration
Sector 2 Iu-CS/PS Interface Data Configuration
Page 34
Iub Interface Data Configuration
Iub interface protocol
User Plane
Control Plane
HSDSCH FP
Radio
USCH FP
CPCH FP
RACH FP
TFCI2 FP
FACH FP
DCH FP
PCH FP
Network
Layer NBAP
NCP CCP CCP
Transport Network Layer Transport Network Layer

User Plane User Plane
A C
Transport
Network SCTP UDP
Layer
IP IP
Data Link Layer Data Link Layer
Physical Layer
Page 35
• Links on the Iub Interface
Page 36
• Adding Physical Layer Data on the External Interface
– The physical ports of the external interface over I
P consist of E1/T1 ports on the PEUa board and F
E/GE ports on the FG2a or GOUa board .
– The configuration of E1/T1 ports is not required.
– Adds the FE/GE port data.
• SET ETHPORT
• ADD ETHIP
• ADD DEVIP (layer 3 networking)
Page 37
•Configure Data Link Layer

–ADD PPPLNK
–ADD MPGRP
–ADD MPLNK
• Each PPP link and each MLPPP link in
an MLPPP group must have a unique
number.
• Each MLPPP group can bind up to
eight MLPPP links
Page 38
• Mapping Between Adjacent Nodes and Transmission Resources

–ADD TRMMAP
–ADD FACTORTABLE
–ADD ADJMAP
Page 39
 Configure Iub Control Plane

 ADD NODEB
 ADD NODEBALGOPARA
 ADD SCTPLNK
 ADD UNCP
 ADD UCCP
 ADD ADJNODE
Page 40
 Configure Iub User Plane

 ADD LGCPORT（Optional. Perform this step when th
e RAN sharing function is used ）
 ADD IPPATH
 ADD IPRT
Page 41
 Configure OM channel
 OM PATH through RNC
ADD UNODEBIP
ADD UNODEBESN（If NodeB uses DHCP）
Page 42
Sector 2 Iu-CS/PS Interface Data Configuration
Page 43
Iu-cs/Iu-ps Interface Data Configuration
Iu-cs interface protocol
Page 44
Iu-ps interface protocol
Page 45
• Links on the Iu-cs and Iu-ps Interface
Page 46
• Adding Physical Layer Data on the External Interf

ace
• Configure Data Link Layer
• Adding Mapping Between Adjacent Nodes and T
ransmission Resources
These steps are very similar to Iub IP interface conf

iguration.
Page 47
 Configure Iu-cs/Iu-ps Control Plane

− ADD SCTPLNK
− ADD N7DPC
− ADD M3LE
− ADD M3DE
− ADD M3LKS
− ADD M3RT
− ADD M3LNK
− ADD ADJNODE
− ADD CNDOMAIN
− ADD CNNODE
Page 48
 Configure Iu-cs/Iu-ps User Plane

− ADD IPPATH
− ADD IPRT
Page 49
Summary
• In the previous part, we have learnt the interface data configuration based on IP
transportation.
• We have learnt the IUB, IU-CS AND IU-PS interfaces.
Page 50
Sector 2 Iu-CS Interface Data Configuration
Sector 3 Iu-PS Interface Data Configuration
Page 51
Iub interface protocol
User plane
Control Plane
FACH FP
RACH FP
Radio
Network NBAP
Layer
NCP CCP CCP
Transport Transport Network Transport Network Transport Network
User Plane Control Plane User Plane
Network
Q.AAL2
Layer
Q.2630.1
Q.2150.2
A B C
SAAL UNI SAAL UNI

AAL2 PATH
ATM
Physical Layer
Page 52
• Links on the Iub interface (over ATM)
Page 53
•Configure Physical Layer
RNC NodeB
Application layer
Physical
layer Interface
board
AEU AOU UOI
Transmission
network
Page 54
•Configure Physical Layer

–MML Commands:
• SET E1T1
• ADD IMAGRP
• ADD IMALNK
• ADD UNILNK
• ADD TSCROSS
• SET OPT
• SET COPTLNK
Page 55
• Configure ATM Layer (ADD ATMTRF)

– In the BSC6900 system, the configuration of AT
M PVC attributes mainly refers to the configur
ation of ATM traffic resources
– After ATM traffic configuration is completed, t
he traffic resources can be directly referenced
through [Flow index] during the configuration
of SAAL, AAL2 PATH, IPoA
Page 56
ATM service types

Service type
Description
Full name Abbreviation
Constant Bit Rate CBR No error check, flow control, and other processing
Used to describe the service with variable data rates and stri
Real Time Variable
RT-VBR ct real time requirement, for example, interactive compress
Bit Rate
ed video such as videoconference
Used in timing transmission as E-mail transmission. In such a
Non-Real Time Var
NRT-VBR case, some delays and variations can be accepted by the ap
iable Bit Rate
plication
No commitment or feedback to congestion. It is suitable for

sending IP data. In case of congestion, UBR cells will be disca
Unspecified Bit Ra
UBR rded. However, neither relevant feedback nor the request fo
te
r slowing down the transmission speed will be returned to t
he sender
Page 57
ATM traffic descriptions
Parameter
Meaning
Full name Abbreviation
Peak cell rate PCR Max. cell transmission rate
Sustainable cell rate SCR Average cell transmission rate during a long term
Minimum cell rate MCR Min. cell transmission rate
Cell delay variation toleranc

CDVT Max. tolerable cell jitter (0.1 s)
e
Indicating which cells can be discarded (CLP=1), and w

Cell loss priority CLP hich cells had better not be discarded (CLP=0) in the ca
se of network congestion
Tag TAGGING Tagging the cells with CLP=0
Page 58
• Adding Mapping Between Transmissi

on and Traffic
Application ADD TRMMAP
Real time Non Real time
layer
service service
primary
Real time Non real time

AAL2 Path AAL2 Path secondary
Page 59
• Adding Factor Table

For this direction, active factor is 85%
12.2Kbps 0101010101010101010101010101010101010
bandwidth
0101 01 010
For this direction, active factor is 10%
ADD FACTORTABLE
 configure the TRM mapping and activity factor table for u

sers of specific priorities： ADD ADJMAP
Page 60
• Adding Control Plane Data on the Iub Inter

face
– Run the ADD SAALLNK command to add an SAAL link. Where, Interface type is se
t to UNI. Run this command repeatedly if multiple SAAL links are required.
– Run the ADD NODEB command to add basic data of the NodeB. Where, IUB tran
s bearer type is set to ATM_TRANS(ATM circuit transmission).
– Run the ADD NODEBALGOPARA command to add the algorithm parameters for t
he NodeB.
– Run the ADD ADJNODE command to add an adjacent node.
– Run the ADD UNCP command to add an NCP. Where, Bearing link type is set to S
AAL.
– Run the ADD UCCP command to add a CCP. Where, Bearing link type is set to SA
AL. Run this command repeatedly if multiple CCPs are required.
Page 61
• Add Iub interface user plane data:

– Run the ADD VP command to add an ATM virtual port（Optional. Perform this step when the AT
M traffic shaping and congestion control functions are enabled.）
– Run the ADD AAL2PATH command to add an AAL2 path. Run this command repeatedly if multiple
AAL2 paths are required.
– Run the ADD AAL2RT command to add an AAL2 route. Note that the value of Destination ATM add
ress must be consistent with the NodeB ATM address. Run this command repeatedly if multiple AA
L2 routes are required.
– Add the transmission resouce group by performing the following steps. Note that this step is optio
nal and that it is recommended when NodeBs are in cascaded connection.
• Run the ADD RSCGRP command to add the transmission resource group. Where, Resource Gr
oup Type is set to ATM.
• Run the ADD RSCGRPPATH command to add paths to the transmission resource group. Run t
his command repeatedly if multiple paths are required
Page 62
• Configure the O&M path: IPoA

dev ip:
12.13.1.254
12.13.1.0 80.168.3.0
NodeB 12.13.1.1
NodeB 12.13.1.2
RINT OMUa
NodeB 12.13.1.3 IPoA
NodeB 12.13.1.N
BSC6810
ADD DEVIP
ADD IPOAPVC
ADD NODEBIP
Page 63
Iub interface negotiation data
Service Ty PCR
Example
VPI VCI Traffic Description
Sub Item pe (cell/s)
Negotiation Item
NCP 7 60 CBR 1236 NOCLPNOSCR
CCP
Control plane 7 61 CBR 1236 NOCLPNOSCR
(with port No. of 1)
Q.AAL2 7 62 CBR 1236 NOCLPNOSCR
AAL2 PATH
NOCLPNOSCRCDVT
User Plane (with PATH to be 9 48 CBR 2473
(CDVT102400 s)
negotiated)
Management
IPoA PVC 9 49 CBR 1236 NOCLPNOSCR
Plane
Example
Negotiation Item
BSC6800 ATM Address0x4502030405060708090001020304050607080900

IPoA PVC
NodeB ATM Address0x4507070707070707070707070707070707070707
Others IP address & mas BSC6800 IP Address11.13.1.200, Mask255.255.255.0

k NodeB IP Address11.13.1.1, Mask255.255.255.0
NodeB local ID Local CellID0
Page 64
Page 65
Iu-CS Interface Data Configuration
Iu-CS interface protocol
Control Plane User plane
Radio
Network RANAP Iu UP
Layer

Network
Layer Q.AAL2
Q.2630.1
A Q.2150.1
SCCP B
A B C
MTP3-B MTP3-B
SAAL NNI SAAL NNI AAL2 PATH
ATM
Physical Layer
Page 66
• Links on the Iu-CS interface
Page 67
• Physical Layer configuration
• ATM Layer configuration
• Add the Mapping Between Adjacent Nodes and Trans
mission Resources
– ADDTRMMAP
– ADD FACTORTABLE
– ADD ADJMAP
The configuration of this items are the same as Iub interf
ace
User plane configuration is the same as Iub interface exce
pt VP configuration
Page 68
Subrack nu IUCS Signalling Li MTP3B link common para SCR mark

mber MTP3B nk Mask meter
Link number
1 2 B’1111 RTVBR, NOCLPSCRCDV SPM number* 1100 SAAL终结的SPU

T, kbps/ IUCS MTP3 子系统尽量在各
2 4 B’1111 CDVT=1024, B link numbers 框、各SPM平均
PCR=1.2 * SCR 分配，承载尽量
3 4 B’1111 在Iu-CS的所有端
口上平均分配
4 8 B’1111
5 8 B’1111
6 16 B’1111
Page 69
• Adding Control Plane Data on the Iu-cs interface

– ADD SAALLNK
– ADD N7DPC
– ADD MTP3BLKS
– ADD MTP3BRT
– ADD MTP3BLNK
– ADD ADJNODE
– ADD CNDOMAIN
– ADD CNNODE
Page 70
• Configure MTP3-b
– Configure DSP (ADD N7DPC )
• For the RNC, there are seven types of DSPs: IUCS, IUPS, IUR, IUCS_RANA
P, IUCS_ALCAP, STP and AAL2SWITCH
MSC BSC6800
STP MTP3B link set
MTP3B link set

STP
DSP DSP of MTP3B link set
Page 71
• Configure MTP3-b
– Adding MTP3B data includes the following:
• Adding signaling link set
• Adding signaling link
• Adding route data
• Setting MTP3B timer if needed
MSC BSC6800
STP MTP3B link set
MTP3B link set

STP
DSP DSP of MTP3B link set
Page 72
Iu-CS interface negotiation data

Example
Sub Item Service t PCR
Negotiation Item SLC VPI VCI Traffic description
ype (cell/s)
MTP3-b link 0 10 54 CBR 3708 NOCLPNOSCR
Control
plane MTP3-b link 1 10 55 CBR 3708 NOCLPNOSCR
AAL2 PATH
User pla (AAL2 PATH ID NOCLPNOSCRCDVT
None 7 51 CBR 7434
ne is to be (CDVT102400 s)
negotiated)
Negotiation Item Example

Other ATM addres RNC ATM Address0x4502030405060708090001020304050607080900
negoti s MSC ATM Address0x4507070707070707070707070707070707070707
ation it
Signaling po BSC6800 SPC0x900
ems
int code MSC DPC0xaa
Page 73
Page 74
Iu-PS Interface Data Configuration
IU-PS interface protocol
Control Plane User plane
Radio
Network RANAP Iu UP
Layer

Network
Layer
A B GTP-U
SCCP
A C UDP
MTP3-B
IP
SAAL NNI
AAL Type 5
ATM ATM
Physical Layer Physical Layer
Page 75
• Links on the Iu-PS Interface
Page 76
• Physical Layer configuration
• ATM Layer configuration
• Add the Mapping Between Adjacent Nodes an
d Transmission Resources
– ADDTRMMAP
– ADD FACTORTABLE
– ADD ADJMAP
• control plane configuration
The configuration of these items are the same as

Iu-cs interface.
Page 77
• The user plane configuration
 Configure IPoA PVC

Add devip Bind PVC SGSN SGSN IP
gateway IP
BSC6800
RBS/RSS
W
I PVC1 SGSN
N SGSN
gateway
T
 MML Commands：
− ADD DEVIP
− ADD IPOAPVC
− ADD IPPATH
− ADD IPRT
Page 78
Iu-PS interface negotiating data
Example Sub Item Service t PCR (cell/.
SLC VPI VCI Traffic description
Negotiation Item ype s)
Control
MTP3-b link 0 12 50 CBR 3708 NOCLPNOSCR
plane
NOCLPNOSCRCDVT
IPoA PVC None 13 60 UBR 351415
User pla (CDVT102400 s)
ne NOCLPNOSCRCDVT
IPoA PVC None 13 61 UBR 351415
(CDVT102400 s)
Negotiation Item Example

BSC6800 IP Address172.23.10.68, Mask255.255.255.0
IP address and ma BSC6800 IP Address172.23.10.69, Mask255.255.255.0
sk SGSN IP Address172.23.5.217, Mask255.255.255.0
Other negotia SGSN Gateway IP Address172.23.10.80, Mask255.255.255.0
tion items Signaling point co BSC6800 SPC0x900
de SGSN SPC0x1500
Network mode of
NMOMode1
operation
Page 79
Summary
• In the previous part, we have learnt the interface data configuration based on ATM
transportation.
• We have learnt the IUB, IU-CS AND IU-PS interfaces.
Page 80
Page 81
Cell Data Configuration
The model of logical cell configuration
Cell
Ce
ll-Id
1 1 1 1 1 1 1 1
-2 1
-2 1
-2
RRM
S yste
m P C
PIC
H P
SCH S
SCH P
CCP
CH P
ICH S
CCP
CH P
RACH AIC
H
alg
orithm
in
fo rmatio
n
p
arame te
rs
1 1 1 1 1 1
1-8 1 1 1 1 0
-1 0
-2 1 1
Accessre striction Me
a surem ent Neig
hbo ring
U
RA a ndse lectio n/ co n
tro l cell B
CH P
CH F
A C
H R
ACH
reselectio n in
fo rmatio n in
forma tio
n
in
form atio n
Page 82
Procedure of quick cell setup
Start ADD LOCELL
Local Cell Configuration

ADD QUICKCELLSET
UP
ACT CELL
Quick Cell Setup Configuration
Neighboring Cell Configuration
End
Page 83
•Common channel configuration
Common p Common physic Common tr Common transport ch Common p Common p

hysical cha al channel ansport ch annel hysical cha hysical cha
nnel ID annel ID nnel ID nnel
0 PSCH – – – –
1 SSCH – – – –
2 PCPICH – – – –
3 PCCPCH 0 BCH – –
4 PRACH 1 RACH 6 AICH
FACH – –
4
(bearing signaling)
8 SCCPCH 1 FACH – –
5
(bearing service)
3 PCH 10 PICH
Page 84
• Adding an Intra-Frequency Neighboring Cell

– intra-frequency neighboring cell that belongs to t
he local RNC
• ADD INTRAFREQNCELL
RNC1 RNC2
Cell1 Cell2 Cell3

F1 F1
Page 85
• Adding an Intra-Frequency Neighboring Cell
– intra-frequency neighboring cell that belongs to a
neighboring RNC
• ADD URNCURA
• ADD INTRAFREQNCELL
RNC1 RNC2
Cell1 Cell2 Cell3

F1 F1
Page 86
• Adding an Inter-Frequency Neighboring Cell

– inter-frequency neighboring cell that belongs to t
he local RNC
• ADD INTERFREQNCELL
RNC1 RNC2
Cell1 Cell2 Cell3

f2 f1
Page 87
• Adding an Inter-Frequency Neighboring Cell
– inter-frequency neighboring cell that belongs to a
neighboring RNC
• ADD URNCURA
• ADD INTERFREQNCELL
RNC1 RNC2
Cell1 Cell2 Cell3

f1 f2
Page 88
• Adding a GSM Neighboring Cell

• ADD UEXT2GCELL
• ADD UG2GNCELL
UMTS RNC GSC BSC
Cell1 Cell2 Cell3
Page 89
• Neighboring cell specifications
– A cell can have up to 32 intra-frequency neighboring c
ells (including the local cell).
– A cell can have up to 64 inter-frequency neighboring c
ells.
– A cell can have up to 32 GSM/GPRS/EDGE neighborin
g cells.
– An RNC can have up to 5100 cells in the local RNC (inc
luding intra-frequency cells and inter-frequency cells).
– An RNC can have up to 7,680 cells in the neighboring
RNCs (including intra-frequency cells and inter-freque
ncy cells).
– An RNC can have up to 9,600 GSM cells.
Page 90
Summary
• In the previous chapter, we have learnt the cell data configuration.

• cell data includes the locell setting, logical cell setup and neighbor cell information.
Page 91
Thank you
Page 92

BSC6900 Data Configuration Issue 1

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

BSC6900 Data Configuration Issue 1

Transféré par

Droits d'auteur :

Formats disponibles

BSC6900 Data Configuration

In compliance with ISO-9001 Cost Effective Quality Training Manpower Services

Chapter 2 Global Data Configuration

Chapter 3 Equipment Data Configuration

Chapter 4 Interface Data Configuration

Chapter 5 Cell Data Configuration

• Scenario 1: st  Scenario 2: RNC is running and providing ser

• Configuration Procedures of initial setup R

Equipment dat NodeB

Cell data configuration

Chapter 2 Global Data Configuration

Chapter 3 Equipment Data Configuration

Chapter 4 Interface Data Configuration

Chapter 5 Cell Data Configuration

• Identify the RNC in a network.

RNC1 RNC2 RNC3

• Adding OSP to the RNC

RNC2 is using SS7 and uniquely id

• Activating the License File

• Setting the Internal Subnet Number of the RNC (offline command)

• Adding RNC Global Location Data

• Adding SIB1 parameters

• In the previous 2 chapters, we have learnt the procedures of data configurations

Chapter 2 Global Data Configuration

Chapter 3 Equipment Data Configuration

Chapter 4 Interface Data Configuration

Chapter 5 Cell Data Configuration

• Equipment Data Configuration include:

• Setting RNC Equipment Description

RNC archive is only

•System ID RNC FAM

MML: SET SYS

• Modifying an RSS Subrack MOD SUBRACK

• Support board level backup－binding mode

• Board and port backup binding ADD SUBRACK:

– Applied in layer 2 networking

• Board and port backup apart

• Board backup, port apart ADD BRD: SRN=0, BR

• Adding an RBS Subrack ADD SUBRACK

• Adding an RBS Subrack

Subrack 1 OFF ON ON ON ON OFF ON OFF

Subrack 2 ON OFF ON ON ON OFF ON OFF

Subrack 3 OFF OFF ON ON ON ON ON OFF

Subrack 4 ON ON OFF ON ON OFF ON OFF

Subrack 5 OFF ON OFF ON ON ON ON OFF

• Configuring RNC Clock Data

GCK Output to RBS and other boards

• Configuring RNC Time

M2000 RNC NodeB

• In the previous chapter, we have learnt the equipment data.

Chapter 2 Global Data Configuration

Chapter 3 Equipment Data Configuration

Chapter 4 Interface Data Configuration

Chapter 5 Cell Data Configuration

Sector 2 Iu-CS/PS Interface Data Configuration

NCP CCP CCP

Transport Network Layer Transport Network Layer

Data Link Layer Data Link Layer

• Links on the Iub Interface

•Configure Data Link Layer

• Mapping Between Adjacent Nodes and Transmission Resources

 Configure Iub Control Plane

 Configure Iub User Plane

Sector 2 Iu-CS/PS Interface Data Configuration