05 Mn3515eu50mn 0001 Nodeb Operation

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

Fig

. 2 N

odeB

equ

ipm

ent c

onfig

urat

ion

(MN

3515

EU

50M

N_0

001

Nod

eB P

F2

oper

atio

n, 7

)

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

Fig

. 4 T

he N

amin

g T

ree

(MN

3515

EU

50M

N_0

001

Nod

eB P

F2

oper

atio

n, 1

3)

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)

1

3

4

5

2

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

6

7

8

9

10

Fig

. 9 E

dit w

indo

w o

f int

erna

l dat

abas

e ed

itor

(MN

3515

EU

50M

N_0

001

Nod

eB P

F2

oper

atio

n, 2

7)

Table 1value

NodeB_1=1; NodeB_2=2;

NodeB_3=3

NodeB_1=1; NodeB_2=2; NodeB_3=3

NodeB_1=1; NodeB_2=2; NodeB_3=3

60

440

0

Label (Parameter Name)General settingsEquipmentId

nodeBId

managedElementId

isAliveTimeIntervall

NodeBFddE

nodeBTypenumberOfServiceRacks

Remarks

to set in Mib Checker

Unique identifier per NodeB, determined by the operator. Set by nbDatabase.

Unique identifier within containment.

This attribute gives the time interval in seconds and is settable by the operator. value = 0: no ‘isAliveNotification’ is sent to OMC/RC value > 0: interval to send ‘isAliveNotification’ to OMC/RC

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

Additonally the unique value „SalesUniqueName“ is to be defined because this value is used for inventoryand 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)

1

3

4

5

2

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

6

7

8

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

Table 2 Label (Parameter Name)

Remarks value

localCellId Identifier for local cell managed by RNC sector #1 1234 searchRange 9 sector #2 1235 searchRange 9 sector #3 1236

searchRange 9 site-specific

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)

67

8

9

10

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 (ManagedElement.X).(NodeBFunctional.0).(Transport.0).(VpTTP.0).(VcCTP.3)

...(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 NodeB is included

0xffffff00 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)

4

3

2

15

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

Table 4 Label (Parameter Name)

Remarks value

VPI/VCI settings VCI link VPI PCR PId

ALCAP 34 0 0 150

NBAP 35 0 0 150

NodeSync 64 0 0 75

ftpOAndMCommand 37 0 0 500

AAL2 65 0 0 3652

AAL2 operator-specific

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

Inte

rcon

nect

ion

of V

pTT

P, V

cTT

P a

nd V

cCT

P a

nd T

raffi

c D

escr

ipto

r by

the

exam

ple

of th

e V

cCT

PId

=0

(ALC

AP

) (M

N35

15E

U50

MN

_000

1 N

odeB

PF

2 op

erat

ion,

47)

Table 5 Label (Parameter Name) Remarks value

additional RAN-Parameters

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]

crcForced

lineCircuitAddress Corresponds to the e1TTPId 0 up to 15

usedForFractionalAtm It marks whether Fractional ATM is used or not (yes=TRUE, no=FALSE). Default: FALSE

FALSE

fractionalAtmProfilePointer To 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)

54

3

2

1

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

Table 6 Label (Parameter Name) Remarks value object: imaGroup imaGroupId Indicates the IMA group id Depends on the no. of

groups, here: 0

imaGroupTxTimingRefLink Defines the E1 reference link (normally ImaLink = 0)

(ManagedElement.X).(NodeBFunctional.0).(Transport.0). (ImaGroup.0). here: (ImaLink.0)

imaLinkId Indicates the IMA link id 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)

(ManagedElement.X).(NodeBFunctional.0).(Transport.0). here: (E1TTP.0)

imaLinkGroupIndex Indicates the IMA group where the link belongs to

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)

1

2

4

3

65

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

Fig

. 30

Cro

ss r

efer

ence

s be

twee

n ra

dio

acce

ss n

etw

ork

para

met

ers

for

Nod

eB P

F 2

- R

NC

(M

N35

15E

U50

MN

_000

1 N

odeB

PF

2 op

erat

ion,

56)

Fig

. 31

Cro

ss r

efer

ence

s be

twee

n tr

ansp

ort n

etw

ork

laye

r pa

ram

eter

s fo

r N

odeB

PF

2 –

RN

C (

MN

3515

EU

50M

N_0

001

Nod

eB P

F2

oper

atio

n, 5

7)

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)