Fig.

1 NodeB equipment configuration (MN3515EU50MN_0001 NodeB PF2 operation, 6)

Fig. 2 NodeB equipment configuration (MN3515EU50MN_0001 NodeB PF2 operation, 7)

Fig. 3 Syntax of nbDatabase (MN3515EU50MN_0001 NodeB PF2 operation, 11)

Fig. 4 The Naming Tree (MN3515EU50MN_0001 NodeB PF2 operation, 13)

Fig. 5 NodeB Naming Tree - Equipment Containment (part A) (MN3515EU50MN_0001 NodeB PF2 operation, 15)

Fig. 6 NodeB Naming Tree - Transport Containment (part B) (MN3515EU50MN_0001 NodeB PF2 operation, 15)

Fig. 7 Tree structure of the NB-44x database as shown in XML-editor window (MN3515EU50MN_0001 NodeB PF2 operation, 23)

Fig. 8 Select XML Database File and press Edit button (MN3515EU50MN_0001 NodeB PF2 operation, 27)

7
8

10
Fig. 9 Edit window of internal database editor (MN3515EU50MN_0001 NodeB PF2 operation, 27)

Table 1
Label (Parameter
Name)
General settings
EquipmentId

Remarks

value

to set in Mib Checker

NodeB_1=1; NodeB_2=2;
NodeB_3=3

nodeBId

Unique identifier per NodeB, determined by the

operator. Set by nbDatabase.

NodeB_1=1; NodeB_2=2;
NodeB_3=3

managedElementId

Unique identifier within containment.

isAliveTimeIntervall

NodeB_1=1; NodeB_2=2;
NodeB_3=3
This attribute gives the time interval in seconds
60
and is settable by the operator.
value = 0: no isAliveNotification is sent to
OMC/RC
value > 0: interval to send isAliveNotification
to OMC/RC

NodeBFddE
nodeBType
Can be: 341 // 420/440/441 or 860/880/881
numberOfServiceRacks Indicates how many service racks the NodeB
consists of

440
0

Additonally the unique value SalesUniqueName is to be defined because this value is used for inventory
and licensing of optional features now!

Fig. 10 Example: TI NB-settings (MN3515EU50MN_0001 NodeB PF2 operation, 29)

Fig. 11 Example: Tree view of managedElementId = 1 and NodeB Id = 1. These values can be different. (MN3515EU50MN_0001 NodeB PF2 operation, 31)

Fig. 12 The edit window (MN3515EU50MN_0001 NodeB PF2 operation, 31)

Fig. 13 Starting upgrade of Id's in XML file (MN3515EU50MN_0001 NodeB PF2 operation, 33)

6
7

Fig. 14 Upgrade Id's in XML file (MN3515EU50MN_0001 NodeB PF2 operation, 33)

Table 2
Label
(Parameter
Name)
localCellId
sector #1
searchRange
sector #2
searchRange
sector #3
searchRange
site-specific

Remarks

value

Identifier for local cell managed by RNC

1234
9
1235
9
1236
9

Fig. 15 Setting the local cell IDs (MN3515EU50MN_0001 NodeB PF2 operation, 35)

Fig. 16 In an 1/1/1-configuration the XML-File contains three times the object class "LocalCellE" (MN3515EU50MN_0001 NodeB PF2 operation, 37)

7
8

10
9

Fig. 17 Change LocalCellId with LMT Database Editor (MN3515EU50MN_0001 NodeB PF2 operation, 37)

Table 3
Label (Parameter Name) Remarks

value

object: IP
Class IpNetToMedia
ipNetToMediaAtmPointer check the correct setting to
...(VpTTP.0).(VcCTP.3)
(ManagedElement.X).(NodeBFunctional.0).
(Transport.0).(VpTTP.0).(VcCTP.3)
ipNetToMediaNetAddress ATM address of Cisco router (gateway)
10.10.161.254
Class IpAddress
ipAddressAddress
IP address of NodeB
NB_1: 10.10.161.1
NB_2: 10.10.161.2
NB_3: 10.10.161.3
ipAddressNetMask
the netmask of the network, where the
0xffffff00
NodeB is included
equal to 255.255.255.0
Class IpRoute
ipRouteDest
IP address of OMP (Radio Commander) 10.10.108.80
ipRouteNextHop
ATM address of Cisco router (gateway)
10.10.161.254
ipRouteType
remote
ipRouteMask
0xffffff00
equal to 255.255.255.0
fixed
site-specific

Fig. 18 IP settings for RC connection (MN3515EU50MN_0001 NodeB PF2 operation, 39)

Fig. 19 The object class "IpNetToMedia" defines the UTRAN network parameters for the NodeB /Radio Commander connections
(MN3515EU50MN_0001 NodeB PF2 operation, 41)

2
3

4
1

Fig. 20 Change IP-configuration with LMT Database Editor (MN3515EU50MN_0001 NodeB PF2 operation, 41)

Table 4
Label (Parameter
Name)
VPI/VCI settings
ALCAP
NBAP
NodeSync
ftpOAndMCommand
AAL2
AAL2
operator-specific

Remarks

value
VCI
34
35
64
37
65

link
0
0
0
0
0

VPI
0
0
0
0
0

PCR
150
150
75
500
3652

PId

Fig. 21 VPI-/VCI settings for RC connection (MN3515EU50MN_0001 NodeB PF2 operation, 43)

Fig. 22 Used object classes for the VPI/VCI settings (MN3515EU50MN_0001 NodeB PF2 operation, 45)

Fig. 23 Interconnection of VpTTP, VcTTP and VcCTP and Traffic Descriptor by the example of the VcCTPId=0
(ALCAP) (MN3515EU50MN_0001 NodeB PF2 operation, 47)

Table 5
Label (Parameter Name)

Remarks

value

additional RANParameters
object: E1TTP
e1TTPId

Indicates the link number/line number

0 up to 15

e1LineCode

Defines the E1 line Code

e1HDB3

crcOperationMode

Determines the operation of the 2Mbits/s

trail termination [crcAutomatic]
Corresponds to the e1TTPId

crcForced

lineCircuitAddress

0 up to 15

usedForFractionalAtm

It marks whether Fractional ATM is used or FALSE

not (yes=TRUE, no=FALSE). Default:
FALSE
fractionalAtmProfilePointerTo be defined if usedForFractionalAtm = " "
TRUE. Default: empty
cableType

Indicates cable type in use: CoaxCable,

TwistedPair

TwistedPair

site-specific

Fig. 24 Additional RAN parameters (MN3515EU50MN_0001 NodeB PF2 operation, 49)

Fig. 25 E1-settings in the object class "E1TTP" for the first E1-line according to table 5 (MN3515EU50MN_0001 NodeB PF2 operation, 51)

2
3

4
5

Fig. 26 E1-settings (MN3515EU50MN_0001 NodeB PF2 operation, 51)

Table 6
Label (Parameter Name)
object: imaGroup
imaGroupId

Remarks

value

Indicates the IMA group id

Depends on the no. of

groups, here: 0

imaGroupTxTimingRefLink

Defines the E1 r eference link

(normally ImaLink = 0)

imaLinkId

Indicates the IMA link id

(ManagedElement.X).(NodeB
Functional.0).(Transport.0).
(ImaGroup.0).
here: (ImaLink. 0)
Depends on the no. of links,
here: 0

imaLinkPhysLine

Pointer to the physical line where

the IMA link is connected (e. g.
E1 link no. 0)
Indicates the IMA group where
the link belongs to

imaLinkGroupIndex

(ManagedElement.X).(NodeB
Functional.0).(Transport.0).
here: (E1TTP. 0)
Depends on the group id,
here: 0

site-specific

Fig. 27 Timing reference link (MN3515EU50MN_0001 NodeB PF2 operation, 53)

Fig. 28 Setting the timing reference link for IMA group 0 (MN3515EU50MN_0001 NodeB PF2 operation, 55)

4
6

Fig. 29 Setting the timing reference link for IMA group 0 (MN3515EU50MN_0001 NodeB PF2 operation, 55)

Fig. 30 Cross references between radio access network parameters for NodeB PF 2 - RNC
(MN3515EU50MN_0001 NodeB PF2 operation, 56)

Fig. 31 Cross references between transport network layer parameters for NodeB PF 2 RNC
(MN3515EU50MN_0001 NodeB PF2 operation, 57)

Fig. 32 Software management of NodeB PF2 (MN3515EU50MN_0001 NodeB PF2 operation, 59)

Fig. 33 Solution 1 (MN3515EU50MN_0001 NodeB PF2 operation, 70)

Fig. 34 Solution 1 (MN3515EU50MN_0001 NodeB PF2 operation, 71)

Fig. 35 Solution 1 (MN3515EU50MN_0001 NodeB PF2 operation, 72)

Fig. 36 Solution 1 (MN3515EU50MN_0001 NodeB PF2 operation, 73)

Fig. 37 Solution 1 (MN3515EU50MN_0001 NodeB PF2 operation, 74)

Fig. 38 Solution 1 (MN3515EU50MN_0001 NodeB PF2 operation, 75)

Fig. 39 Solution 1 (MN3515EU50MN_0001 NodeB PF2 operation, 76)

Fig. 40 Solution 1 (MN3515EU50MN_0001 NodeB PF2 operation, 77)

Fig. 41 Solution 1 (MN3515EU50MN_0001 NodeB PF2 operation, 78)

Fig. 42 Solution 1 (MN3515EU50MN_0001 NodeB PF2 operation, 79)

Fig. 43 Solution 1 (MN3515EU50MN_0001 NodeB PF2 operation, 80)