HUAWEI TECHNoLOGIES CO., LTD.

HUAWEI Technologies CO., LTD.

www.huawei.com
DBS3900 & BTS3900 & BTS3900A &
BTS3900L LTE V100R003C00
Material for Parameter Changes


2010-12-30
Contents
Overview of parameter changes
Changes of northbound interface parameters are listed as follows:
1. Added parameters
2. Optimized parameter value ranges
Modified sequence of enumeration values
Expanded parameter value ranges
Narrowed parameter value ranges
3. Modified parameter units
4. Modified parameter default values
Modified parameter default values because of optimized
algorithms
5. Optimized parameter IDs and names




Overview of Parameter Changes
Number of added parameters: 48
Number of deleted parameters: 6
Number of modified parameters: 22
Number of parameters with modified IDs and names: 95

Page 4
Change Reason:
The RscGroup and NODETORSCGRP MOs are associated by key parameters. In
this version, three key parameters are added to the RscGroup MO. Accordingly,
three parameters are also added to the NODETORSCGRP MO to ensure the
accurate association between the two MOs. Note that the three added parameters
in the NODETORSCGRP MO are not key ones. PT and SBT are mandatory
parameters.
Change Description (Three Examples):
Added Parameters
MOC MOC Change
Type
Parameter ID Parameter
Change Type
Value Range Default Value
NODETORSCGRP

Added
PN

Added
0~15 0
NODETORSCGRP Added
PT
Added
PPP~6, MPGRP~8, ETH~9,
ETHTRK~10
N/A
NODETORSCGRP Added
SBT
Added
BASE_BOARD~0,
E1_COVERBOARD~3
N/A
Change Reason:
According to the protocol, the sequence of enumeration values 480ms and 512ms
for the TimeToTrigger parameter in the CellDLIcicMcPara MO must be modified.
After the modification, 480ms is placed ahead of 512ms. In this version, the
sequence of enumeration values for altogether five parameters are modified.
Change Description (Two Examples):
MOC MOC Change
Type
Parameter ID Parameter
Change Type
Actual Value Range (New) Actual Value Range (Old)
CellDLIcicMcPara Modified
TimeToTrigger
Modified
0ms, 40ms, 64ms, 80ms, 100ms,
128ms, 160ms, 256ms, 320ms,
480ms, 512ms, 640ms, 1024ms,
1280ms, 2560ms, 5120ms
0ms, 40ms, 64ms, 80ms, 100ms,
128ms, 160ms, 256ms, 320ms,
512ms, 480ms, 640ms, 1024ms,
1280ms, 2560ms, 5120ms
CellULIcicMcPara Modified
TimeToTrigger

Modified
0ms, 40ms, 64ms, 80ms, 100ms,
128ms, 160ms, 256ms, 320ms,
480ms, 512ms, 640ms, 1024ms,
1280ms, 2560ms, 5120ms

0ms, 40ms, 64ms, 80ms, 100ms,
128ms, 160ms, 256ms, 320ms,
512ms, 480ms, 640ms, 1024ms,
1280ms, 2560ms, 5120ms
Modified Sequence of Enumeration Values

Page 6
Change Reason:
In the earlier versions, the UL and DL data rates at the logical port are set to 300 Mbit/s and
450 Mbit/s respectively. Due to the addition of transmission overhead, the UL or DL data rate at
the MAC layer over the air interface is lower than that at the logical port. The LTE, however,
requires the UL and DL data rates at the MAC layer to reach 300 Mbit/s and 450 Mbit/s
respectively. Therefore, the rate at the logical port must be higher than that at the MAC layer.
Consider the peak rate case: The average packet size is 500 bytes and the UL and DL data
rates at the MAC layer are 300 Mbit/s and 450 Mbit/s respectively. In this case, if the
transmission overhead is 20%, the UL and DL data rates at the logical port must be 360 Mbit/s
and 540 Mbit/s respectively.
Change Description (Four Examples):
Expanded Parameter Value Ranges
MOC Parameter ID Parameter Name Value Type
GUI Value Range
(New)
GUI Value Range
(Old)
Actual Value Range
(New)
Actual Value Range
(Old)
RscGroup RXBW Rx Bandwidth Interval values 32~540000 32~450000 32~540000 32~450000
RscGroup RXCIR
RX Commited
Information Rate
Interval values 64~540000 64~450000 64~540000 64~450000
RscGroup RXPIR
RX Peak Information
Rate
Interval values 64~540000 64~450000 64~540000 64~450000
RscGroup TXBW Tx Bandwidth Interval values 32~360000 32~300000 32~360000 32~300000

Page 7
MOC
Parameter
ID
Parameter Name Value Type GUI Value Range (New) GUI Value Range (Old)
Actual Value
Range (New)
Actual Value
Range (Old)
OMCh RT Route Type Enumeration values NEXTHOP(Next Hop)
NEXTHOP(Next Hop),
IF(Exit Interface)
NEXTHOP NEXTHOP, IF
OMCh SBT Subboard Type Enumeration values BASE_BOARD(Base Board)
BASE_BOARD(Base Board),
E1_COVERBOARD(E1 Cover
Board)
BASE_BOARD
BASE_BOARD
,
E1_COVERBO
ARD
Change Reason:
For one parameter, its enumeration values in the associated MO are different from
those in the associated MML commands. Therefore, the GUI value range of the
parameter is modified by deleting unnecessary enumeration values to ensure the
consistency.

Change Description (Two Examples):
Narrowed Parameter Value Ranges
Change Reason:
The unit of the PreAllocationWeight parameter in the ExtendedQci MO is
incorrectly written as none in the earlier versions. In this version, the unit is
modified to 0.1. The unit of only one parameter is modified in this version. The
modification has no impact on the interconnection at the northbound interface.

Change Description:
Modified Parameter Units
MOC MOC Change Type Parameter ID Parameter Change Type Unit (New) Unit (Old)
ExtendedQci Modified

PreAllocationWei
ght
Modified 0.1 none
Change Reason:
The GbrRbUsedHighThd and GbrRbUsedLowThd parameters in the
CellRacThd MO are used to limit resources used by GBR services. In the earlier
versions, the two parameters are set to relatively large values to prevent the
eNodeB from limiting the resources used by GBR services. In this version, a
dedicated switch is added to disable this limitation. Therefore, the default values of
the parameters are optimized, which meet the requirements of various scenarios.
The modifications have no impact on the interconnection at the northbound
interface.
Change Description
Modified Parameter Default Values Because of
Optimized Algorithms
MOC MOC Change
Type
Parameter ID Parameter
Change Type
Default Value
(New)
Default Value
(Old)
CellRacThd Modified GbrRbUsedHighThd Modified 95 100
CellRacThd Modified GbrRbUsedLowThd Modified 90 99
Change Reason:
Names of some parameters are too brief and difficult for users to understand.
Therefore, the names of altogether 95 parameters are modified. The modifications
have no impact on the interconnection at the northbound interface.

Change Description (Two Examples):
Optimized Parameter Names
MOC MOC Change
Type
Parameter ID Parameter
Change Type
Parameter Name
(New)
Parameter Name
(Old)
ServiceIrHoCfgGro
up
Modified

InterRatHoState Modified Inter-RAT handover
state
InterRatHoState
RatFreqPriorityGro
up
Modified RatFreqPriorityGro
upId
Modified RAT frequency
priority group ID
RatFreqPriorityGro
upId
Change Reason:
The Access attribute of these parameters is Read Only. If user want to modify
these parameters, it need to be deleted first and then added. These parameters
are not included in the last parameter list document, and Huawei provide these
parameters in this version in order to provide the enhancement operation via
northbound interface.

Change Description (Two Examples):
Added Parameters
MOC MOC Change
Type
Parameter ID Parameter
Change Type
Value Range Default Value
RscGroup Modified OID Added 0~3 0
IPPath Modified CN Added 0~7 0
Change Reason:
The current version supports the function that is used to automatically establish an
IPSec tunnel between the eNodeB and the Mobility Management Entity (MME).
However, the actual application scenario only require the system to establish
IPSec tunnel between the eNodeB and the Security Gateway (Se-GW). Therefore
the parameters related to MME are deleted.

Change Description (Two Examples):
Deleted Parameters
MOC MOC Change
Type
Parameter ID Parameter
Change Type
MME Modified FirstIKEPeerName Deleted
MME Modified FirstIPSecFlag Deleted
Change Reason:
To simplify creating an eNodeB or a cell via the northbound interface, eNodeB and
cell templates are introduced in the northbound interface.

Change Description (Two Examples):
Added Parameters
NBI MOC MOC Change
Type
NBI Parameter ID Parameter
Change Type
Value Range
CELL Modified TEMPLATENAME Added 1~255
ENODEB Modified TEMPLATENAME Added 1~255
Thank You
www.huawei.com