Professional Documents
Culture Documents
Feature
Related instructions
14
DN09146788
Issue: 01
Table 1
Feature
Related instructions
Feature
RAN2243: Performance Monitoring
Based on ETH Service OAM
Related instructions
Activating RAN2243: Performance
Monitoring Based on ETH Service OAM
Feature
Related instructions
RAN2554: Transport Configuration Fall- This feature does not have any related
back
descriptions.
Issue: 01
DN09146788
15
RU50 features
Table 4
Feature
RAN3047: RTT Improvement to
enhance user experience
Related instructions
This feature does not have related
instructions.
Feature
RAN3017: Additional 6 WCDMA Cell
Activation
Related instructions
Activating RAN3017: Additional 6
WCDMA Cell Activation
1.8 Licensing
The application software features (ASW) are under license key management. A license
is a file that includes the feature information. Before a licensed feature can be activated,
the license file needs to be transferred to and installed in the IPA-RNC. For information
on transferring the license, see License management operations in RNC in WCDMA
RAN License Operation. For information on installing the license, see Installing licenses
in the network element in Managing License-based Features in IPA-RNC and Managing
License-based Features in Multicontroller RNC.
16
DN09146788
Issue: 01
Issue: 01
DN09146788
17
IP Configuration Plan Interface Parameters for Flexi Direct RNC Excel in WCDMA
RAN Operating Documentation, Parameters in NOLS PIC
Radio Network Parameters in Flexi Direct Excel in WCDMA RAN Operating
Documentation, Parameters in NOLS PIC
Reference Information Service in NOLS for RNC parameters
18
DN09146788
Issue: 01
2.1.1.1
Benefits
End-user benefits
This feature enables fast web browsing to the end user.
Operator benefits
This feature benefits the operator as follows:
2.1.1.2
Requirements
Software requirements
Table 6: Software requirements lists the software required for this feature.
RAS
Flexi Direct
IPA-RNC
mcRNC
Flexi Direct
RNC
OMS
BTS Flexi
RU50
Planned for
later release
RN8.0
Planned for
later release
Planned for
later release
OMS3.0
(RU50)
Support not
required
Table 6
Software requirements
Flexi Lite
BTS
BTS Flexi
10
NetAct
MSC
SGSN
MGW
UE
Support not
required
Support not
required
NetAct 8
EP1
Support not
required
Support not
required
Support not
required
Support not
required
Hardware requirements
This feature requires no new or additional hardware.
Issue: 01
DN09146788
19
2.1.1.3
Functional description
Functional overview
The RAN2963: Data Session Profiling feature aims to provide faster web browsing. This
is achieved by moving the terminal directly to the Cell_DCH, even though the initial data
amount suggests allocation to the Cell_FACH - the amount of data is below the RNPS TrafVolThresholdULLow parameter.
When the large data amount is identified in the session (the LargeDataThr parameter
value is exceeded), after the end of the session (when the UE is moved to the
Cell/URA_PCH state), the timer defined by the LargeDataTime parameter is started.
The UE, being in the Cell/URA_PCH state, starts next data session by sending the RRC:
CELL UPDATE message with cell update cause set as uplink data transmission. When
the time defined by the LargeDataTime parameter is not exceeded, the UE is moved
directly to the Cell_DCH state, with the RRC: CELL UPDATE CONFIRM message. After
successful procedure, when the RRC: RADIO BEARER RECONFIGURATION
COMPLETE message is successfully received from UE, the RNC updates the
M1006C309: SUCCESSFUL PCH TO DCH TRANS DUE TO DATA SESSION
PROFILING counter, if TVI is not set as TRUE in RRC: CELL UPDATE message.
The amount of data (LargeDataThr) and the time period (LargeDataTime) are the
parameters defined by the operator.
The fast state change is performed both for sending and receiving data.
For the UEs capable of using the HS-RACH, an RNPS- HSChaPrefInDataSesProf
parameter is used. It allows either a direct transfer the Cell_DCH state or staying in the
Cell_FACH state and using HS-RACH/FACH channels provided the data session
profiling conditions.
For proper functioning of the RAN2963 feature, please mind the following parameter
configuration:
2.1.1.4
System impact
Interdependencies between feature
Impact on interfaces
This feature has no impact on interfaces.
20
DN09146788
Issue: 01
Impact on commands
There are no commands related to this feature.
2.1.1.5
Alarms
There are no alarms related to this feature.
New counters
Counter ID
Counter name
Measurement
M1006C309
Table 8: Related existing counters lists existing counters related to this feature.
Table 8
Issue: 01
Counter ID
Counter name
Measurement
M1006C174
M1006C175
M1006C196
M1006C197
M1006C198
DN09146788
21
Parameters
Table 9: New parameters lists parameters introduced with this feature.
Table 9
New parameters
Full name
Abbreviated name
Managed object
DataSessionProfEnabled
RNFC
Large DataThreshold
LargeDataThr
RNPS
LargeDataTime
RNPS
HSChaPrefInDataSesProf
RNPS
22
Modified parameters
Full name
Abbreviated name
Managed object
RNCOptions
RncOptions
RNC
TrafVolThresholdULLow
RNPS
SmartTrafVolThrUL
WCEL
TrafVolThresholdDLLow
WCEL
SmartTrafVolThrDL
WCEL
NASsignVolThrDL
WCEL
DN09146788
Issue: 01
2.1.1.6
Sales information
Table 11
Sales information
BSW/ASW
SW component
ASW
RAN
RNC LK
for IPA-RNC:
ZW7M: FEA=4654:ON;
Issue: 01
DN09146788
23
24
DN09146788
Issue: 01
Issue: 01
DN09146788
25
2.2.1.1
Benefits
End-user benefits
With this feature, end-user benefits from increased coverage and throughput.
Operator benefits
With this feature, Dual Cell HSDPA benefits can be obtained even when no contiguous
10 MHz frequency allocation is available. Gains are obtained from additional frequency
band. Lower band provides coverage, while higher band provides increased capacity
and peak rate. BTS based scheduling enables dynamic resource sharing, so that faraway-UEs mainly use low frequency band, while close-by-UEs mainly use the high
frequency. This approach maximizes the sector coverage and capacity.
2.2.1.2
Requirements
Software requirements
Table 12: Software requirements lists the software required for this feature.
Table 12
Software requirements
RAS
mcRNC
Flexi
OMS
Direct RNC
RU50
Planned for
later
releases
RN8.0
WN9.0
Flexi Lite
BTS
Flexi 10
BTS
NetAct
MSC
UE
Not
planned
Planned for
later
releases
NetAct8
EP1
SGSN
MGW
Flexi BTS
Hardware requirements
For Flexi Multiradio BTS WCDMA this feature requires one of the following features:
2.2.1.3
Functional description
With the RAN2179: Dual Band HSDPA 42 Mbps feature data for capable UE is
scheduled on two distinct frequency bands in the downlink. With this feature, the
maximum peak rate is 42 Mbps when 64QAM is enabled and 15 codes are available on
both frequencies.
26
DN09146788
Issue: 01
The BTS uses proportional fair scheduling and optimizes the sector coverage and
capacity by favoring the low-frequency band for cell-edge-UEs and the high-frequency
band for UEs, that are closer to the BTS. This allows Dual Band HSDPA to combine the
gain of normal Dual Cell HSDPA scheduling and the benefits of low frequency band for
faraway users.
The carrier selection is based both on the UE distance and current load on both uplink
carriers. The RNC uses the RAN2172: Multi-Band Load Balancing feature for carrier
selection.
Figure 1
Table 13: Supported band combinations shows three band combinations supported by
the RAN2179: Dual Band HSDPA 42 Mbps feature.
Table 13
Issue: 01
UL Band
DL Band
I or VIII
I and VIII
II or IV
II and IV
I or V
I and V
DN09146788
27
g
2.2.1.4
System impact
Interdependencies between features
The RAN1906: Dual Cell HSDPA feature and all its preconditions are prerequisites
for this feature.
Use of 64QAM modulation requires the RAN1643: HSDPA 64QAM feature.
Licenses for two separate frequency bands in the same NodeB and RNC are
required.
Impact on interfaces
RNC and BTS NBAP interface including new IE's in messages:
(BTS -> RNC) Audit Response: BTS informs RNC on DualBand-HSDPA capability
(BTS -> RNC) Resource Status Indication: BTS informs RNC which cell will support
DualBand-HSDPA.
Following NBAP procedures are unchanged between DC-HSDPA and DB-HSDPA:
Changed NBAP procedures between DC-HSDPA and DB-HSDPA: Audit Response and
Resource Status Indication. These procedures are enhanced with new IE indicating that
NodeB has new DB-capability
2.2.1.5
Alarms
Table 14: Existing alarms lists alarms related to this feature.
28
DN09146788
Issue: 01
Table 14
Existing alarms
Alarm ID
Alarm name
3325
7795
New counters
Counter ID
Counter name
Measurement
M1001C728
Service Level
M1001C729
Service Level
M1001C730
Service Level
M1006C293
RRC signalling
M1006C294
RRC signalling
M1006C295
RRC signalling
M1006C296
RRC signalling
Parameters
Table 16: New parameters lists parameters introduced with this feature.
Table 16
Issue: 01
New parameters
Full name
Abbreviated name
Managed object
DBandHSDPAEnabled
WCEL
DN09146788
29
Table 16
Full name
Abbreviated name
Managed object
PFLDBHSDNRT
PFL
PFL
PFLDBHSDStr
PFL
PrefLayerDBHSDStr
PFL
PFLDBHSDAMR
PFL
PFL
PFL
PFLDBHSDAMRNRT
PFL
2.2.1.6
Full name
Abbreviated name
Managed object
DC HSDPA Enabled
DCellHSDPAenabled
WCEL
DCellVsMIMOPreference
RNC
Tcell
WCEL
Sales information
Table 18
30
Modified parameters
Sales information
BSW/ASW
SW component
ASW
RAN
RNC LK
DN09146788
Issue: 01
For the allowed band combinations for Dual Band HSDPA, see Table 19: Allowed band
combinations for Dual Cell and Dual Band HSDPA.
Table 19
Allowed band combinations for Dual Cell and Dual Band HSDPA
Uplink band
Downlink
band
I or VIII
I and VIII
II or IV
II and IV
I or V
I and V
The RAN2179: Dual Band HSDPA 42 Mbps feature is controlled by the capacity license
key. For more information on licensing, see Licensing.
Issue: 01
for IPA-RNC:
ZW7M:FEA=2118:ON;
No license is required in Flexi Direct RNC.
DN09146788
31
Go to the Topology.
Lock the WCEL where the RAN2179: Dual Band HSDPA 42 Mbps feature needs
to be activated:
a) Select the WCEL object.
b) Select the cell in the WCell(s) table.
c) From the drop-down menu select "State Change State: Lock".
32
DN09146788
Issue: 01
Perform the RRC connection setup with UE that supports Dual Band HSDPA
and send some data.
After the measurement data has been collected, use the RNW Measurement
presentation GUI to check if any of the following counters has value greater
than 0.
Expected outcome
Values of counters M1006C293 and M1006C294 are updated by a normal DB call setup,
and value of counter M1006C295 or M1006C296 is updated by related failure RB setup
scenarios.The approximate throughput is 42 Mbit/s. The RAN2179: Dual Band HSDPA
42Mbps feature has been activated successfully.
Issue: 01
DN09146788
33
Go to the Topology.
Lock the WCEL where the RAN2179: Dual Band HSDPA 42 Mbps feature needs
to be activated:
a) Select the WCEL object
b) Select the cell in the WCell(s) table.
c) From the drop-down menu select "Start Change state: Lock".
Further information
A restart of the RNC and the BTS is not required after the deactivation of this
feature.
34
DN09146788
Issue: 01
2.3.1.1
Benefits
End-user benefits
The end user benefits from an enhanced application experience because of higher
HSDPA DL throughput.
Operator benefits
The operator benefits from higher average DL throughput for HSDPA users, and thus
higher average cell throughput.
2.3.1.2
Requirements
Software requirements
Table 20: Software requirements lists software required for this feature.
Table 20
Software requirements
RAS
mcRNC
RU50
WN9.0
Flexi Lite
BTS
Flexi 10
BTS
NetAct
MSC
UE
Planned for
later
releases
Planned for
later
releases
NetAct 8
EP1
SGSN
MGW
Flexi BTS
Support
not
required
Hardware requirements
For Flexi Multiradio BTS WCDMA this feature requires one of the following features:
This feature also requires double Tx and double antenna lines per sector. For supported
BTS configurations, see Flexi Multiradio BTS WCDMA Supported and Planned
Configurations Excel in NOLS.
2.3.1.3
Functional description
Virtual Antenna Mapping (VAM) was introduced with the feature RAN1642: MIMO and it
can be used in cells with two Tx like in physical MIMO configuration. With the VAM the
cell area is covered with two physical antennas using virtual antenna mapping between
physical and virtual antennas. The mapping can be used for MIMO and non-MIMO
Issue: 01
DN09146788
35
2.3.1.4
System impact
Interdependencies between features
There is no interdependencies with other features.
Virtual Antenna Mapping (VAM) has to be configured in the cells prior to E-VAM
activation.
Impact on interfaces
This feature has no impact on interfaces.
2.3.1.5
Alarms
There are no alarms related to this feature.
36
DN09146788
Issue: 01
Parameters
Table 21: New parameters lists parameters introduced with this feature.
Table 21
2.3.1.6
New parameters
Full name
Abbreviated name
Managed object
EVAM in use
EVAMInUse
WCEL
Sweep time
EvamTSweep
WCEL
Keep time
EvamTKeep
WCEL
EvamNumPhaseOffset
WCEL
EvamDInit
WCEL
EVAM Capability
EVAMCapability
WCEL
Sales information
Table 22
Sales information
BSW/ASW
RAS SW component
ASW
RAN
RNC LK
Issue: 01
DN09146788
37
Start the WCDMA BTS Site Manager application and establish the connection
to the BTS.
Flexi Multiradio BTS WCDMA is able to autonomously request for missing license
file(s) from the NetAct License Manager during the RAN2131: Automatic Licence
Distribution to Flexi BTS feature activation.
Make sure that you have selected Automatic licensing in use checkbox in the
Automatic License Distribution Settings page.
Please note, that following this step allows to configure VAM only in one
specific cell. To configure VAM in multiple cells, run this step on each cell
separately.
Expected outcome
VAM is configured in chosen cells. Restart the BTS to make changes valid.
38
DN09146788
Issue: 01
The RAN2482: Enhanced Virtual Antenna Mapping feature is controlled by the long-term
capacity Enhanced Virtual Antenna mapping license key. Capacity license refers to the
number of cells. For more information on licensing, see Licensing.
for IPA-RNC:
ZW7M:FEA=3732:ON;
Go to the Topology.
Issue: 01
DN09146788
39
Go to the Topology.
Further information
40
A restart of the RNC and the BTS is not required after the deactivation of the
feature.
DN09146788
Issue: 01
2.4.1.1
Benefits
End-user benefits
The end-user benefits from fast HSPA inter-frequency handover and higher data
throughput during compressed mode.
Operator benefits
This feature benefits the operator as follows:
2.4.1.2
HSPA inter-frequency handover (HO) is done faster when channel type switching to
DCH is not needed first
The inter-system handover (ISHO) and redirection from HSPA to LTE becomes more
reliable when LTE cells are measured before ISHO or redirection.
This feature reduces signaling for RNC, Iub, BTS, and the UE as channel type
switching to DCH is not needed.
Requirements
Software requirements
Table 23: Software requirements lists the software required for this feature.
Table 23
Issue: 01
Software requirements
RAS
mcRNC
RU50
Planned for
later
releases
RN8.0
DN09146788
Flexi
OMS
Direct RNC
Flexi BTS
41
Flexi Lite
BTS
Flexi 10
BTS
NetAct
MSC
SGSN
MGW
UE
NetAct8
EP1
Hardware requirements
This feature requires the following features:
2.4.1.3
Functional description
The RAN1668: HSUPA Compressed Mode for LTE and Inter- frequency Handover
feature introduces HSUPA compressed mode (CM) for LTE and inter-frequency
measurements, without UL channel type switching to DCH.
HSUPA CM configuration for inter-frequency measurements is achieved using a singleframe method with 7 (or less)-slot transmission gap pattern (TGP). HSUPA CM
configuration for LTE measurements is achieved using a double-frame method with 7 (or
more)-slot TGP. In NSN implementation the TGP for single frame method is always fixed
to 7 slots and for double frame method, the TGP is fixed to 10 slots.
Compressed mode is supported while the radio bearers are mapped to E-DCH in uplink
and SRBs are mapped on DCH or E-DCH. This also includes the case where DL SRB is
mapped to DCH or HSDPA.
Avoiding the channel-type switch to UL DCH reduces the total handover execution time
up to 1.5s. Also, the high HSUPA throughput can be experienced during compressed
mode.
For inter-system handover to LTE, only the basic HSUPA compressed mode support is
covered in this feature. HSUPA compressed mode for LTE is used by the RAN2980:
Measurement based LTE Layering feature and the RAN2264: Smart LTE Handover
feature. All the control, signaling, and RRM decision making of measurement-based
redirection and PS HO to LTE are included in those features.
2.4.1.4
System impact
Interdependencies between features
The RAN1276: HSDPA Inter-frequency Handover feature is a prerequisite for using this
feature.
42
DN09146788
Issue: 01
The RAN1276: Inter-frequency Handover feature covers the following direct handover
cases:
DCH/HSDPA to DCH/HSDPA
DCH/HSDPA to HSUPA/HSDPA
DCH/HSDPA to DCH/DCH
DCH/DCH to DCH/HSDPA
DCH/DCH to HSUPA/HSDPA
With the RAN1668: HSUPA Compressed Mode For LTE and Inter-frequency Handover
feature the following direct handover cases are supported in addition:
HSUPA/HSDPA to DCH/HSDPA
HSUPA/HSDPA to HSUPA/HSDPA
HSUPA/HSDPA to DCH/DCH
Impact on interfaces
HSUPA CM is configured and activated using the following messages:
over Iub:
over Uu:
over Iub:
over Uu:
Issue: 01
DN09146788
43
HSPA IFHO is done faster, as channel type switching to DCH is not needed first.
ISHO and redirection from HSPA to LTE becomes more reliable, as the LTE cells can
be measured before ISHO or redirection.
The UL throughput is impacted since UE cannot transmit on each slot. The reduction
depends on the configured transmission time interval and whether the UE is
performing intra- or inter-system measurement.
2.4.1.5
Signaling for RNC, Iub, BTS, and UE is reduced, as channel type switching to DCH
is not needed for enabling CM.
In FSM3, a maximum 50% of the users with CM active can be supported, that is, a
maximum 50% of the users can have CM active at the same time.
Alarms
There are no alarms related to this feature.
44
New counters
Counter ID
Counter name
Measurement
M1002C676
Traffic (RNC)
M1002C677
Traffic (RNC)
M1002C678
Traffic (RNC)
M1002C692
Traffic (RNC)
M1002C693
Traffic (RNC)
M1006C312
RRC signalling
M1006C313
RRC signalling
M1008C294
DN09146788
Issue: 01
Table 24
Counter ID
Counter name
Measurement
M1008C295
Table 25: Related existing counters lists existing counters related to this feature.
Table 25
Counter ID
Counter name
Measurement
M1002C623
Traffic (RNC)
M1002C624
Traffic (RNC)
M1002C625
Traffic (RNC)
KPI ID
KPI name
RNC_5301a
There are no modified and existing key performance indicators related to this feature.
Parameters
Table 27: New parameters lists parameters introduced with this feature.
Table 27
New parameters
Full name
Abbreviated name
Managed object
TGPLHSPAInterFreq
RNHSPA
Issue: 01
DN09146788
45
Table 28
Modified parameters
Full name
Abbreviated name
Managed
object
BTSSupportForHSPACM
WBTS
MaxNumberUEHSPACmHO
WCEL
MaxNumberUEHSPACmNCHO
WCEL
Table 29: Related existing parameters lists existing parameters related to this feature.
Table 29
Full name
46
Abbreviated name
Managed
object
RNFC
GAPPositionSingleFrame
RNC
GAPPositionSingleFrame
RNMOBI
UplinkRecoveryPeriodPowerMode
RNAC
UplinkInitialTransmitPowerMode
RNC
DeltaSIRUplink
RNC
DeltaSIRUplink
WRAB
DeltaSIRDownlink
RNC
DeltaSIRDownlink
WRAB
DeltaSIRAfterUplink
RNC
DeltaSIRAfterUplink
WRAB
DeltaSIRAfterDownlink
RNC
DN09146788
Issue: 01
Table 29
2.4.1.6
Full name
Abbreviated name
Managed
object
DeltaSIRAfterDownlink
WRAB
AltScramblingCodeCM
WCEL
CmMasterSwitch
RNFC
Sales information
Table 30
Sales information
BSW/ASW
SW component
ASW
HSPA
RNC LK
Before activating this feature, activate the RAN1276: HSDPA Inter-frequency Handover
feature (see Activating RAN1276: HSDPA Inter-frequency Handover).
Before activating this feature make sure that basic HSUPA and HSDPA mobility are
enabled.
This feature is controlled by the long-term ON/OFF license key. For more information on
licensing, see Licensing.
g
Issue: 01
DN09146788
47
48
for IPA-RNC:
ZW7M:FEA=4783:ON;
DN09146788
Issue: 01
Go to the Topology.
Issue: 01
DN09146788
49
50
DN09146788
Issue: 01
Adjust the signal of BTS 1 CELL 1, so that it is lower than the threshold value
of the HHoEcNoThreshold parameter.
Adjust the signal of BTS 1 CELL 2, so that it is stronger than the signal of BTS
1 CELL 1.
Collect the log for "step 1", "step 2", "step 3", and "step 4" and analyze the log.
Verify that:
The UE sends out RRC: MEASUREMENT REPORT with Measured Results for
intra-frequency event 1f.
In NBAP message RADIO LINK RECONFIGURATION PREPARE the values of
IEs in Transmission Gap Pattern Sequence Information are as follows:
TGPS Identifier xx
tGSN xx
tGL1 7
tGD xx
tGPL1 5
uL/DL mode UL/DL
Downlink Compressed Mode Method sf/2
Uplink Compressed Mode Method sf/2
Downlink Frame Type xx
DeltaSIR1 xx
DeltaSIRafter1 xx
xx means that the value of the IE is not relevant for verifying this
feature.
Issue: 01
DN09146788
51
ul-DL-Mode ul-and-dl : {
ul sf-2,
dl sf-2 },
dl-FrameType dl-FrameTypeA,
deltaSIR1 xx,
deltaSIRAfter1 xx }}}
xx means that the value of the IE is not relevant for verifying this
feature.
Expected outcome
HSUPA compressed mode starts successfully and call release is normal. Logs data are
as specified above and counters are updated.
Go to the Topology.
Further information
After deactivating the feature, set the feature state to OFF.
52
DN09146788
Issue: 01
2.5.1.1
Benefits
End-user benefits
Ensuring a successful LTE camping improves end-user experience.
Operator benefits
Operator benefits from having two types of WCDMA to LTE redirections available: with
and without a measurement. Operator can choose if the trigger activates with- or withoutmeasurement-based redirection.
2.5.1.2
Requirements
Software requirements
Table 31: Software requirements lists the software required for this feature.
Table 31
Issue: 01
Software requirements
RAS
Flexi Direct
IPA-RNC
mcRNC
Flexi Direct
RNC
OMS
Flexi BTS
RU50
Planned for
later
releases
RN8.0
Planned for
later
releases
Planned for
later
releases
OMS3.0
(RU50)
WN9.0
DN09146788
53
Flexi Lite
BTS
Flexi 10
BTS
NetAct
MSC
SGSN
MGW
Planned for
later
releases
Planned for
later
releases
NetAct 8
EP1
UE
3GPP
Rel-8
Hardware requirements
For Flexi Multiradio BTS WCDMA this feature requires one of the following features:
2.5.1.3
Functional description
Functional overview
RRC connection release with redirection command to LTE can be used for moving LTEcapable UE to LTE, if compressed mode measurements indicate that LTE coverage is
available. Each of the following events triggers compressed mode measurements for
LTE:
First three of the above mentioned triggers are also used in the RAN2717: Smart LTE
Layering feature. The RAN2980: Measurement Based LTE Layering feature introduces
the fourth trigger for UEs keeping long Cell_DCH reservations for PS services. Note that
when the RAN2980: Measurement Based LTE Layering feature is active, all four triggers
are valid and there is no need to have the RAN2717: Smart LTE Layering feature
installed separately.
In uplink, DCH is used during compressed mode. HSPA compressed mode, also
including HSUPA compressed mode, is supported by the RAN1668: HSUPA
Compressed Mode for LTE and Inter-frequency Handover feature. If the RAN1668:
HSUPA Compressed Mode for LTE and Inter-frequency Handover feature is not
implemented in the network, the RAN2980: Measurement Based LTE Layering feature
supports HSDPA/DCH, and DCH/DCH. If there is HSUPA (E-DCH) in uplink, then it is
reconfigured to DCH, before initiating the compressed mode measurements.
54
DN09146788
Issue: 01
LTE-capable UEs are checked for their measurement capabilities. UEs with dual receiver
do not require compressed mode for creating gaps to listen to other frequencies. For
such UEs, compressed-mode-related information is not required and thus not sent to
them.
If WCDMA cell load is not high and users can be provided good enough experience
within WCDMA layer, measurements and redirection to LTE can be bypassed. RNC load
level parameter can be used to define if load is low enough for keeping UEs in WCDMA.
With the RAN2980: Measurement Based LTE Layering feature operator can:
2.5.1.4
enable LTE redirection without measurements for the first three redirection triggers
(also provided with the RAN2717: Smart LTE Layering feature) and measurementbased redirection to LTE for the periodic trigger
establish measurement-based redirection to LTE for all four redirection triggers
select the frequencies to which UEs in Cell_DCH state are redirected in LTE system
as well as define camping priorities for those frequencies
exclude some LTE carrier frequencies from LTE target camping layers
disable the WCDMA cell load check which will result in automatic LTE redirection
every time the LTE coverage is available
System impact
Interdependencies between features
The RAN2067: LTE Interworking feature provides support for LTE cell reselection in idle
mode Cell_PCH and URA_PCH states.
Impact on interfaces
This feature affects Uu and Iub interfaces and uses standard signaling procedures.
Impact on commands
There are no commands related to this feature.
2.5.1.5
Alarms
There are no alarms related to this feature.
Issue: 01
DN09146788
55
New counters
Counter ID
Counter name
Measurement
M1001C747
Service Level
M1001C748
Service Level
M1001C749
Service Level
M1001C750
Service Level
M1006C310
RRC signaling
M1010C237
M1010C238
M1010C239
Parameters
Table 33: New parameters lists parameters introduced with this feature.
Table 33
New parameters
Full name
Abbreviated name
Managed
object
FMCL Identifier
FMCLId
RNC
FMCL
56
FMCLChangeOrigin
FMCL
LTEMeasAveWindow
FMCL
LTEMaxMeasPeriod
FMCL
LTEMinMeasInterval
FMCL
DN09146788
Issue: 01
Table 33
Full name
Abbreviated name
Managed
object
FMCL
LTELayeringMeasAndHOActivatio
n
WCEL
LTEPeriodicTriggerTimer
RNC
AdjLSelectFreq
ADJL
WCDMACellLoadThreshold
WCEL
FMCL Identifier
FMCLIdentifier
WCEL
AdjLFreqPriority
HOPL
AdjLMinRSRPLevel
HOPL
AdjLMinRSRQLevel
HOPL
TGPLForLTEMeas
RNHSPA
Issue: 01
Modified parameters
Full name
Abbreviated name
Managed
object
RNC Options
RncOptions
RNC
SmartLTELayeringEnabled
WCEL
SmartLTELayeringRSCP
WCEL
SmartLTELayeringUA
WCEL
SmartLTELayeringServ
RNMOBI
SmartLTELayeringPrevT
RNMOBI
DN09146788
57
Table 34
2.5.1.6
Full name
Abbreviated name
Managed
object
SmartLTELayeringTSysSel
WCEL
Sales information
Table 35
Sales information
BSW/ASW
SW component
ASW
RAN
RNC LK
for IPA-RNC:
ZW7M:FEA=4839:ON;
58
DN09146788
Issue: 01
before starting the LTE measurements. The HSPA (HSUPA/HSDPA) compressed mode
measurements for LTE requires that the license of RAN1668: HSUPA Compressed Mode
for LTE and Inter-frequency Handover feature is ON and the value of the
BTSSupportForHSPACM parameter is set to 2.
Configure the following database objects and relevant parameters for the RAN2980:
Measurement Based LTE Layering feature and attach them to the WCDMA cell:
AdjLFreqPriority
AdjLMinRSRPLevel
AdjLMinRSRQLevel
LTEMeasAveWindow
LTEMaxMeasPeriod
LTEMinMeasInterval
LTENcarrFreqSearchPeriod
AdjLEARFCN
AdjLMeasBw
WCEL parameters for identifying the Measurement Control Parameter Set and
controlling redirection triggers:
FMCLIdentifier
LTELayeringMeasActivation
Note that the listed parameters are optional and have a default value. Only the
AdjLEARFCN ADJL parameter, for defining the E-UTRA Absolute Radio
Frequency Channel Number of the neighboring E-UTRA frequency, is
mandatory.
Redirection to LTE happens only when the cell has at least one Cell_DCH
adjacency defined with the AdjLSelectFreq RNC/WBTS/WCEL/ADJL
parameter. Operator can exclude chosen frequency from redirection target
using the AdjLSelectFreq parameter. In order to use redirection to LTE,
value 0 for the AdjLSelectFreq parameter must be used for at least one LTE
frequency configured in the cell.
Ensure that RSRP and RSRQ thresholds in both LTE and WCDMA networks
are aligned. Corresponding parameters related to this feature are
AdjLMinRSRPLevel and AdjLMinRSRQLevel.
Additionally, the following parameters can be used for tuning the RAN2980:
Measurement Based LTE Layering feature:
Issue: 01
DN09146788
59
0 for setting T1, T2, T3 as triggers for redirection without measurements and T4
as a trigger for redirection with measurements
1 for setting T1, T2, T3, T4 as triggers for redirection with measurements
Further information
SmartLTELayeringEnabled WCEL parameter enables triggers (T) for the RAN2980:
Measurement Based LTE Layering feature as follows:
60
DN09146788
Issue: 01
For more information on triggers, see Description of RAN2980: Measurement Based LTE
Layering.
The RAN2980: Measurement Based LTE Layering feature is supported for the following
PS QoS classes:
interactive (NRT)
background (NRT)
streaming (RT)
Note that for verification using counters, the end-user has to make a PS call.
Expected outcome
Redirection to LTE is successful and visible in the listed counters.
Unexpected outcome
Redirection to LTE is not successful and is visible in the following counter:
Further information
The following counter can be used for more detailed monitoring the
RAN2980: Measurement Based LTE Layering feature:
Issue: 01
DN09146788
61
2.6.1.1
Benefits
End-user benefits
Better subscriber experience because of less call setup delay.
Operator benefits
This feature helps to reduce call setup delay in case of congestion.
2.6.1.2
Requirements
Software requirements
Software requirements lists the software required for this feature.
62
DN09146788
Issue: 01
RAS
mcRNC
OMS
BTS Flexi
Flexi Lite
RU50
Planned for
later
releases
OMS3.0
(RU50)
Support not
required
Support
not
required
BTS Flexi 10
NetAct
MSC
SGSN
MGW
UE
Support not
required
NetAct 8 EP1
Support not
required
Support not
required
Support not
required
Support not
required
Hardware requirements
This feature does not require any new or additional hardware.
2.6.1.3
Functional description
Functional overview
The RAN 147: RRC Connection Setup Redirection feature enables to redirect an RRC
connection to another 3G frequency or GSM. The redirection happens if admission
control rejects the RRC connection request. The Figure 2: RRC connection setup
redirection illustrates the described situation.
Figure 2
The redirection info sent in the RRC message RRC CONNECTION REJECT depends on
the target system. If the target system is GSM, then the redirection info is a list of target
cells for the UE with release rel-6 or newer. If the UE release is older than rel-6, then the
redirection info is just the target system, for example, GSM.
Issue: 01
DN09146788
63
If the target system is 3G, then the redirection info is a target frequency (UTRA Absolute
Radio Frequency Channel Number). The inter-frequency neighbor cell AdjiUARFCN
parameter defines it for downlink. The RNC calculates it for uplink in legacy way from
value of the AdjiARFCN parameter and duplex distance used in the RF band.
RRC connection sets up on Cell_DCH state, when the redirection is triggered. RRC
connection can be setup also on common channels. For more information, see RAN1797
Common channel setup.
There is no Admission control in common channels thus it cannot fail, when RRC
connection is setup on common channels.
RRM decides about the target system on the basis of establishment cause of the RRC
Connection Request and the new management RRCReDirTargetSys parameter. The
RRCReDirTargetSys parameter defines the target system for each establishment
cause. Also, if the RNC tries to redirect the RRC connection into GSM but UE is not able
to camp to the new target cell in GSM, then the RNC is allowed to redirect the RRC
connection into 3G. Value for each parameter need to be planned based on functionality
of actual establishment cause and available radio access technologies. Especially need
to be considered if this certain functionality can be performed on GSM.
The RRCReDirBlockedCellAllowed parameter defines if cells, which are marked as
blocked in SLHO or MBLB procedure, should not be used as a target cell of an RRC
connection redirection. If MBLB load information is not available, then only SLHO
information (loaded or not loaded) is used. If both MBLB and SLHO load information is
not available, then SLHO and MBLB blocked cells are not reduced from the target cell
list, although the RRCReDirBlockedCellAllowed parameter indicates that the
blocked cells should not be used as a target cell of an RRC connection redirection.
The AdjiPriorityReDir parameter defines priority for each inter-frequency cell in the
neighbor cell list if congestion of Iub transmission or BTS causes the rejection.
The AdjiPriorityQuality parameter defines priority for cells in the neighbor cell list
if the RRC connection is rejected because of downlink power, uplink interference or
downlink spreading code congestion. The frequency of feasible target cell with the
highest priority is selected as the target frequency for redirection.
For more information, see the Figure 3: Selection process of redirection information.
Figure 3
64
DN09146788
Issue: 01
If the RNC signaling unit overload is the reason to reject the RRC Connection Request,
UE can be redirected to GSM network without target cell list.
2.6.1.4
System impact
Interdependencies between features
There are no interdependencies between this and any other feature.
Impact on interfaces
This feature has no impact on interfaces.
Impact on commands
There are no commands related to this feature.
2.6.1.5
Alarms
There are no alarms related to this feature.
New counters
Counter ID
Counter name
Measurement
M1006C305
RRC_CONN_REDIR_GSM_FAIL
Table 37: Related existing counters lists existing counters related to this feature.
Table 37
Issue: 01
Counter ID
Counter name
Measurement
M1006C70
RRC_CONN_REJ_DIR_SETUP
DN09146788
65
Table 37
Counter ID
Counter name
Measurement
M1001C618
Parameters
Table 38: New parameters lists parameters introduced with this feature.
Table 38
66
New parameters
Full name
Abbreviated name
Managed object
RRCReDirEnabled
RNFC
RRCReDirTargetSys
WCEL
TargetsystemConversationalC
all
WCEL
TargetsystemStreamingCall
WCEL
TargetsystemInteractiveCall
WCEL
TargetsystemBackgroundCall
WCEL
TargetsystemSubscribedTraffi
c
WCEL
TargetsystemEmergencyCall
WCEL
TargetsysteminterRATreselecti WCEL
on
TargetsysteminterRATchangeo WCEL
rder
Targetsystemregistration
DN09146788
WCEL
Issue: 01
Table 38
Full name
Abbreviated name
Managed object
TargetsystemDetach
WCEL
TargetsystemHighPrioritySign
alling
WCEL
TargetsystemLowPrioritySigna WCEL
lling
Targetsystemreestablishment
WCEL
Targetsystemunknown
WCEL
TargetsystemMBMSreception
WCEL
TargetsystemMBMSrbrequest
WCEL
RRCReDirBlockedCellAllowed RNMOBI
AdjiPriorityReDir
HOPI
Issue: 01
Modified parameters
Full name
Abbreviated name
Managed object
AdjiPriorityQuality
HOPI
AdjgPriorityCoverage
HOPG
RNC Options
RncOptions
IADA
DN09146788
67
2.6.1.6
Sales information
Table 40
Sales information
BSW/ASW
SW component
ASW
RAN
RNC LK
for IPA-RNC:
ZW7M: FEA=4780:ON;
68
DN09146788
Issue: 01
0 none,
1 GSM 3G,
2 3G GSM,
3 GSM none,
4 3G none.
2.6.2.2
Issue: 01
for IPA-RNC:
ZW7M: FEA=4780:ON;
DN09146788
69
0 none,
1 GSM 3G,
2 3G GSM,
3 GSM none,
4 3G none.
70
DN09146788
Issue: 01
Counters verification.
The counters are updated as follows:
Table 41
2.6.3.2
Counters verification
ID
Name
Value
Updated objects
M1006C70
RRC CONN
REJECT DUE TO
RRC
CONNECTION
SETUP
REDIRECTION
WBTS1 CELL-1
Make sure that there is very heavy CPU load in signaling unit (ICSU or USCP).
Counters verification.
The counters are updated as follows:
Issue: 01
DN09146788
71
Table 42
Counters verification
ID
Name
Value
Updated objects
M1001C618
RRC CONN
SETUP FAIL DUE
TO ICSU
OVERLOAD
WBTS1 CELL-1
M1006C70
RRC CONN
REJECT DUE TO
RRC
CONNECTION
SETUP
REDIRECTION
WBTS1 CELL-1
Application Launcher
72
DN09146788
Issue: 01
To set the feature state to OFF, set the value of the RRCReDirEnabled to 0.
To enable the signaling unit overload, set the value of the RRCReDirEnabled to
2.
2.6.4.2
Application Launcher
Issue: 01
DN09146788
73
To set the feature state to OFF, set the value of the RRCReDirEnabled to 0.
To enable the admission control modifications, set the value of the
RRCReDirEnabled to 1.
2.7.1.1
Benefits
End-user benefits
This feature maximizes end-users LTE experience.
Operator benefits
This feature assures smooth WCDMA-LTE interworking when in LTE network RSRQ
criteria are used for cell reselection.
2.7.1.2
Requirements
Software requirements
Table 43: Software requirements lists the software required for this feature.
74
DN09146788
Issue: 01
Table 43
Software requirements
RAS
mcRNC
RU50
Support
not
required
Flexi Lite
BTS
Flexi 10
BTS
NetAct
MSC
UE
Support not
required
Support not
required
NetAct 8
EP1
SGSN
MGW
Flexi BTS
3GPP
Rel-9
Hardware requirements
This feature does not require any new or additional hardware.
2.7.1.3
Functional description
Functional overview
In current system implementation the RAN2067: LTE Interworking feature supports
reference symbol received power (RSRP)-based LTE reselection. The RAN3069: RSRQbased LTE Reselection feature introduces an upgrade by including quality thresholds for
LTE priority-based cell reselection. These quality thresholds are specified in 3GPP Rel-9
and they include the UTRA serving cell Ec/N0 threshold and E-UTRA neighbor cell
RSRQ quality threshold. These thresholds are broadcast in the system information block
type 19 (SIB19).
2.7.1.4
System impact
Interdependencies between features
This feature requires the RAN2067: LTE Interworking feature.
Impact on commands
There are no commands related to this feature.
Issue: 01
DN09146788
75
2.7.1.5
Alarms
There are no alarms related to this feature.
Parameters
Table 44: New parameters lists parameters introduced with this feature and the
corresponding SIB19 parameters specified in 3GPP Rel-9.
Table 44
New parameters
Full name
Abbreviated name
SIB19 IE
Managed
object
Threshservlow2
Threshserving,low2
WCEL
AdjLQqualminEUTRA
QqualminEUTRA
HOPL
AdjLThreshigh2
Threshx,high2
HOPL
AdjLThreslow2
Threshx,low2
HOPL
2.7.1.6
Sales information
Table 45
Sales information
BSW/ASW
SW component
ASW1)
RAN
RNC LK
1)
the RAN2067: LTE Interworking feature license also controls the RAN3069: RSRQbased LTE Reselection feature
76
DN09146788
Issue: 01
Issue: 01
DN09146788
77
Further information
Note that the UE does not use Hierarchical Cell Structure (HCS) for interfrequency or inter-RAT reselection if absolute-priority-based cell reselection is
used.
There are no counters involved in cell reselection process. The UE reselects the
cell according to the parameters broadcast by the network in SIB19 message.
When the RAN3069: RSRQ-based LTE Reselection feature is active, it is visible in the
content of SIB19 message. After activating this feature and ascribing values to the
parameters listed in RAN3069: RSRQ-based LTE Reselection management data
section, the E-UTRA frequency and priority info list/E-UTRA frequency and priority
information elements will be broadcast in SIB19 message.
Content of SIB19 message can be monitored by using UE and network protocol
analyzer.
Further information
Camping on a desired layer is performed by the UE using SIB19 parameters. Cell
reselection algorithm is specified in 3GPP TS 25.304 User Equipment (UE) procedures
in idle mode and procedures for cell reselection in connected mode.
78
DN09146788
Issue: 01
In order to verify usage of the quality criteria for LTE absolute priority based cell
reselection, activation of the RAN2067: LTE Interworking feature was needed.
Therefore, for deactivating the RAN3069: RSRQ-based LTE Reselection
feature, instructions on the RAN2067: LTE Interworking feature deactivation are
also included. For more information, see
Deactivating RAN2067: LTE Interworking.
2.8.1.1
Benefits
End-user benefits
End user benefits from seamless WCDMA to LTE handover experience.
Operator benefits
Thanks to this feature WCDMA to LTE mobility becomes faster end more reliable, as
handover is preceded with compressed mode measurements.
Issue: 01
DN09146788
79
2.8.1.2
Requirements
Software requirements
Table 46: Software requirements lists the software required for this feature.
Table 46
Software requirements
RAS
mcRNC
RU50
Planned for
later
releases
RN8.0
WN9.0
Flexi Lite
BTS
Flexi 10
BTS
NetAct
MSC
UE
NetAct 8
EP1
Flexi
OMS
Direct RNC
SGSN
MGW
Flexi BTS
Hardware requirements
For Flexi Multiradio BTS WCDMA this feature requires one of the following features:
2.8.1.3
Functional description
The RAN2264: Smart LTE Handover feature introduces inter-system handover from
WCDMA to LTE.
Inter-RAT handover from WCDMA to LTE can be started if compressed mode
measurements indicate that LTE coverage is available. The following events can trigger
compressed mode measurements for LTE handover:
In uplink DCH is used during compressed mode. However, if HSUPA compressed mode
supported by the RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency
Handover feature is active, then HSUPA compressed mode is used in uplink.
80
DN09146788
Issue: 01
In cases when WCDMA cell load is not high and users can be provided with good
enough experience in WCDMA layer, measurements and handover to LTE can be bypassed. Cell level load parameters can be used to define if load is low enough for
keeping UEs in WCDMA.
The RAN2264: Smart LTE Handover feature supports inter-RAT handover from WCDMA
to both FDD-LTE and TDD-LTE.
2.8.1.4
System impact
Interdependencies between features
The RAN2067: LTE Interworking feature is a prerequisite for using this feature.
For HSUPA compressed mode measurements, the RAN1668: HSUPA Compressed
Mode for LTE and Inter-frequency Handover feature is required.
This feature requires also support from the UE, 3G core network, LTE core
network, and LTE eNB.
Impact on interfaces
This feature causes rise of signaling traffic on Uu, Iub, Iur, and IuPS interfaces
(compressed mode related signaling, LTE neighbor reporting over Iur, relocation related
signaling between RNC and core network).
New Managed Object Class (MOC): ADJE is introduced for defining E-UTRA (LTE)
neighbor cells.
New counters for monitoring outgoing LTE PS Handover are introduced.
2.8.1.5
This feature supports traffic steering and network load balancing scenarios.
Offloading WCDMA network during high load states via seamless handover to LTE
(resources are reserved in advance on LTE side in contrast to layering features)
increases available HSDPA power per user ratio in WCDMA cell.
This feature impacts the maximum number of UEs that are simultaneously in
compressed mode in the cell due to a non-critical handover measurement reason
(both DCH and HSPA compressed modes).
Alarms
There are no alarms related to this feature.
Issue: 01
DN09146788
81
Table 47
82
New counters
Counter ID
Counter name
Measurement
M1010C240
M1010C241
M1010C242
M1010C243
M1010C244
M1010C245
M1010C246
M1010C247
M1010C248
M1010C249
M1010C250
M1010C251
M1010C252
M1010C253
LTE NRT ISHO ATTEMPTS DUE TO HSPA Inter System Hard Handover
TO DCH
M1010C254
M1010C255
DN09146788
Issue: 01
Table 47
Issue: 01
Counter ID
Counter name
Measurement
M1010C256
M1010C257
M1010C258
M1010C259
M1010C260
M1010C261
M1010C262
M1010C263
M1010C264
LTE NRT ISHO UE LOST DUE TO DCH TO Inter System Hard Handover
CCH
M1010C265
M1010C266
LTE NRT ISHO UE LOST DUE TO CS RAB Inter System Hard Handover
RELEASE
M1010C267
M1010C268
M1019C0
AutoDef LTE
M1019C1
AutoDef LTE
M1036C0
LTE Relocation
M1036C1
LTE Relocation
M1036C2
LTE Relocation
DN09146788
83
Table 47
Counter ID
Counter name
Measurement
M1036C3
M1036C4
LTE Relocation
M1036C5
LTE Relocation
M1036C6
LTE Relocation
M1036C7
LTE Relocation
M1036C8
LTE Relocation
M1036C9
LTE Relocation
M1036C10
LTE Relocation
Table 48: Related existing counters lists existing counters related to this feature.
Table 48
Counter ID
Counter name
Measurement
M1010C239
Parameters
Table 49: New parameters lists parameters introduced with this feature.
Table 49
84
New parameters
Full name
Abbreviated name
Managed object
LTEHandoverEnabled
RNC/WBTS/WCEL
DN09146788
Issue: 01
Table 49
Full name
Abbreviated name
Managed object
LTEMinHoInterval
RNC/FMCL
ADJE Identifier
ADJEId
RNC/WBTS/WCEL
/ADJE
ADJEChangeOrigin
RNC/WBTS/WCEL
/ADJE
AdjePhysicalCellId
RNC/WBTS/WCEL
/ADJE
AdjeMCC
RNC/WBTS/WCEL
/ADJE
AdjeMNC
RNC/WBTS/WCEL
/ADJE
AdjeMNCLength
RNC/WBTS/WCEL
/ADJE
Macro eNB ID
AdjeENodeBId
RNC/WBTS/WCEL
/ADJE
Cell ID
AdjeCellId
RNC/WBTS/WCEL
/ADJE
AdjeTAC
RNC/WBTS/WCEL
/ADJE
ADJL Identifier
AdjLIdentifier
RNC/WBTS/WCEL
/ADJE
Issue: 01
Modified parameters
Full name
Abbreviated name
Managed object
RNC Options
RncOptions
RNC
BTSSupportForHSPACM
RNC/WBTS
MaxNumberUEHSPACmNCH
O
RNC/WBTS/WCEL
LTELayerCellHSLoad
WCEL
DN09146788
85
Table 50
2.8.1.6
Full name
Abbreviated name
Managed object
SmartLTELayeringUA
WCEL
SmartLTELayeringServ
RNMOBI
SmartLTELayeringTSysSel
WCEL
LTEPeriodicTriggerTimer
RNC
LTEMeasAveWindow
RNC/FMCL
LTEMaxMeasPeriod
RNC/FMCL
LTEMinMeasInterval
RNC/FMCL
RNC/FMCL
AdjLFreqPriority
RNC/HOPL
AdjLMinRSRPLevel
RNC/HOPL
AdjLMinRSRQLevel
RNC/HOPL
ADJLId
RNC/WBTS/WCEL
/ADJL
FMCL Identifier
FMCLIdentifier
RNC/WBTS/WCEL
MaxNumberUECmSLHO
RNC/WBTS/WCEL
Sales information
Table 51
Sales information
BSW/ASW
SW component
ASW
RAN
RNC LK
86
DN09146788
Issue: 01
Before activating this feature, activate the license of the RAN2067: LTE Interworking
feature (feature code 1755, see Activating RAN2067: LTE Interworking).
This feature is controlled by the long-term ON/OFF license key. For information on
managing licenses, see Licensing.
for IPA-RNC:
ZW7M: FEA=3414:ON;
Before activating this feature configure the following database objects and relevant
parameters and attach them to WCDMA cell:
AdjLEARFCN (mandatory)
HopLIdentifier (mandatory)
AdjLMeasBw (optional, default value exists)
Note that even though configuring AdjLMeasBw parameter is not
mandatory for creating ADJL-object, it is important for network planning.
Issue: 01
AdjePhysicalCellId (mandatory)
AdjeMCC (mandatory)
AdjeMNC (mandatory)
AdjeMNCLength (optional, default value exists for the 2 digit MNC)
DN09146788
87
AdjeENodeBId (mandatory)
AdjeCellId (mandatory)
AdjeTAC (mandatory)
AdjLIdentifier (mandatory)
Additionally, the following parameters can be used for tuning the RAN2264: Smart LTE
Handover feature:
Before activating this feature ensure the correctness of the following neighboring LTE
and CN configuration and identifier parameters:
ADJL-AdjLEARFCN
ADJL-AdjLMeasBw
ADJE-AdjePhysicalCellId
ADJE-AdjeMCC
ADJE-AdjeMNC
ADJE-AdjeMNCLength
ADJE-AdjeENodeBId
ADJE-AdjeCellId
ADJE-AdjeTAC
ADJE-AdjLIdentifier
88
DN09146788
Issue: 01
Go to Topology.
g
g
State of the licenses must not be changed after activating the feature.
Further information
WCEL parameter LTEHandoverEnabled enables triggers for the Smart LTE Handover
as follows:
where:
Issue: 01
DN09146788
89
The HSUPA compressed mode measurement support for LTE is provided by the
RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover feature. If
the feature is not available, E-DCH to UL DCH switch is needed before starting the LTE
measurements for handover.
For instructions on how to activate and configure DCH/DCH compressed mode (CM) and
HSDPA/DCH CM for LTE handover, see Activating RAN2980: Measurement Based LTE
Layering. For information on how to activate and configure HSPA CM for LTE handover,
see Activating RAN1668 HSUPA Compressed Mode for LTE and Inter-frequency
Handover.
The minimum required RSRP (AdjLMinRSRPLevel) and RSRQ (AdjLMinRSRQLevel)
levels of the cell under LTE carrier frequency should be aligned with the corresponding
thresholds in the LTE network.
Ensure that the UE is not redirected or handed over from WCDMA to LTE with the RSRP
or RSRQ levels, which are lower than the thresholds for the coverage (RSRP) or quality
(RSRQ)-based handover from LTE to WCDMA. For example, if the coverage (RSRP)
based handover from LTE to WCDMA is configured to trigger with RSRP level 115
dBm, then the recommended minimum RSRP threshold for the WCDMA to LTE
handover is 112 dBm (3 dB hysteresis) in order to avoid immediate handover back to
WCDMA. Correspondingly, if the quality (RSRQ)-based handover from LTE to WCDMA
is configured to trigger with RSRQ level - 15 dB, then the minimum RSRQ threshold for
the WCDMA to LTE handover should be set to - 12 dB (3 dB hysteresis).
Inter-RAT handover from WCDMA to LTE is supported for the following PS QoS classes:
Interactive (NRT)
Background (NRT)
Expected outcome
Outgoing inter-RAT LTE handover is successful and visible in the attempt and success
counters.
Further information
More detailed monitoring of the RAN2264: Smart LTE Handover feature can be
performed with the following counters:
90
DN09146788
Issue: 01
Issue: 01
DN09146788
91
Go to Topology.
2.9.1.1
Benefits
End-user benefits
This feature provides end-user higher data rates and faster response times.
Operator benefits
Introduced idle-mode traffic steering reduces the need for handovers and reselects the
best possible layer for the end-user. Operator controls the priorities of the layers.
2.9.1.2
Requirements
Software requirements
Table 52: Software requirements lists the software required for this feature.
92
DN09146788
Issue: 01
Table 52
Software requirements
RAS
mcRNC
RU50
Support
not
required
Flexi Lite
BTS
Flexi 10
BTS
NetAct
MSC
UE
Support not
required
Support not
required
NetAct 8
EP1
SGSN
MGW
Flexi BTS
3GPP
Rel-8
Hardware requirements
This feature does not require any new or additional hardware.
2.9.1.3
Functional description
Functional overview
The RAN2881: WCDMA and GSM Layer Priorities feature enables WCDMA and GSM
cell reselection based on layer/Radio Access Technology priorities. When layer-specific
absolute priority information is provided in the system information block type 19 (SIB19),
UE periodically measures higher priority layers. UE measurements are applicable when
the UE is in idle mode, Cell_PCH, or URA_PCH state. Also lower and equal priority
layers are measured by UE, if radio conditions in the camped frequency fall below
criteria defined with search thresholds.
Based on results of these measurements, UE performs priority-based cell reselection
using both coverage and quality thresholds broadcast in SIB19. For WCDMA and GSM
priority-based cell reselection these thresholds are specified in 3GPP Rel-8.
In addition to the priority number for the layer, signal strength and quality thresholds are
provided for cell reselection. Frequency band prioritization can be adjusted with
thresholds, for example, 900 MHz can be preferred for cell edge UEs and 2100 MHz - for
close by UEs. UEs above certain threshold move to higher priority layer, whereas cell
edge UEs prefer low priority layer as they are below the threshold. Figure 4: WCDMA
and GSM cell reselection based on layer priorities shows the mechanism of cell
reselection. The absolute priority mechanism is 3GPP Rel-8 feature.
Issue: 01
DN09146788
93
Figure 4
2.9.1.4
System impact
Interdependencies between features
Hierarchical Cell Structure cannot be used simultaneously with RAN2881: WCDMA and
GSM Layer Priorities feature.
Impact on commands
There are no commands related to this feature.
2.9.1.5
Alarms
There are no alarms related to this feature.
94
DN09146788
Issue: 01
Parameters
Table 53: New parameters lists parameters introduced with this feature and the
corresponding SIB19 parameters specified in 3GPP Rel-8.
Table 53
New parameters
Full name
Abbreviated name
SIB19 IE
Managed
object
WCDMACellReselection
N/A
WCEL
GSMCellReselection
N/A
WCEL
AdjiAbsPrioCellReselec
priority
HOPI
AdjiThreshigh
Threshx,high
HOPI
AdjiThreslow
Threshx,low
HOPI
AdjiQqualminFDD
QqualminFDD
HOPI
AdjiQrxlevminFDD
QrxlevminFDD
HOPI
AdjgAbsPrioCellReselec
priority
HOPG
AdjgThreshigh
Threshx,high
HOPG
AdjgThreslow
Threshx,low
HOPG
Threshservlow2
Threshserving,low2
WCEL
SIB19Compmask5
N/A
WCEL
SIB19Compmask6
N/A
WCEL
SIB19Compmask7
N/A
WCEL
Table 54: Modified parameters lists parameters modified by this feature and the
corresponding SIB19 parameters specified in 3GPP Rel-8.
Issue: 01
DN09146788
95
Table 54
Modified parameters
Full name
Abbreviated name
SIB19 IE
Managed
object
RNC Options
RncOptions
N/A
RNC
AbsPrioCellReselec
priority
WCEL
S prioritysearch1
Sprioritysearch1
Sprioritysearch1
WCEL
S prioritysearch2
Sprioritysearch2
Sprioritysearch2
WCEL
Threshservlow
Threshserving,low
WCEL
AdjiUARFCN
UARFCN
ADJI
RT HOPI Identifier
RtHopiIdentifier
N/A
ADJI
AdjgQrxlevMin
QrxlevminGSM
HOPG
RT HOPG Identifier
RtHopgIdentifier
N/A
ADJG
AdjLAbsPrioCellReselec
priority
HOPL
SIB19Priority
N/A
RNC
SIB19CompmaskInfo
N/A
WCEL
Block 19 Compmask 1
SIB19Compmask1
N/A
WCEL
SIB19Compmask2
N/A
WCEL
SIB19Compmask3
N/A
WCEL
SIB19Compmask4
N/A
WCEL
Table 55: Related existing parameters lists existing parameters related to this feature
and the corresponding SIB19 parameters specified in 3GPP Rel-8.
Table 55
Full name
Abbreviated name
SIB19 IE
Managed
object
BCCH ARFCN
AdjgBCCH
ADJG
96
DN09146788
Issue: 01
Table 55
Full name
Abbreviated name
SIB19 IE
Managed
object
2.9.1.6
AdjgBandIndicator
ADJG
Sales information
Table 56
Sales information
BSW/ASW
SW component
ASW
RAN
RNC LK
for IPA-RNC:
ZW7M: FEA=4781:ON;
Issue: 01
DN09146788
97
Further information
98
Note that the UE does not use Hierarchical Cell Structure (HCS) for interfrequency or inter-RAT reselection if absolute-priority-based cell reselection is
used.
DN09146788
Issue: 01
There are no counters involved in cell reselection process. UE reselects the cell
according to the parameters broadcast by the network in SIB19 message.
When the RAN2881: WCDMA and GSM Layer Priorities feature is active, it is visible in
the content of SIB19 message. After activating this feature and ascribing values to the
parameters listed in RAN2881: WCDMA and GSM Layer Priorities management data
section, the following information elements will be broadcasted in SIB19 message:
Issue: 01
DN09146788
99
3.1.1.1
Benefits
End-user benefits
This feature does not affect the end-user experience.
Operator benefits
This feature provides the maintenance hierarchy structure where the performance
measurements are performed between the MEPs of the same grade of hierarchy.
Different grades of hierarchy monitor different Ethernet network segments to find the
problems more efficiently.
3.1.1.2
Requirements
Software requirements
Table 57: Software requirements lists software required for this feature.
100
RAS
Flexi Direct
IPA-RNC
mcRNC
RU50
Not planned
DN09146788
Flexi BTS
WN9.0
Issue: 01
Table 57
Software requirements
Flexi Lite
BTS
Flexi 10
BTS
NetAct
MSC
SGSN
MGW
UE
Planned
for later
releases
Planned
for later
releases
NetAct 8 EP1 Support not Support not Support not Support not
(RU50)
required
required
required
required
Hardware requirements
This feature requires one of the following Flexi Multiradio BTS Transport Sub-Modules:
Flexi FTIA
Flexi FTJA
Flexi FTIB
Flexi FTLB
Flexi FTFB
This feature requires one of the following features for Flexi Multiradio BTS WCDMA:
3.1.1.3
Functional description
Functional overview
This feature enhances the RAN1880: Ethernet OAM in BTS feature to provide
performance monitoring (PM) functionality using Ethernet Service OAM frames. The
Ethernet OAM performance monitoring functions are defined by ITU-T Y.1731 standard.
The ITU-T Y.1731 standard sets up an L2 network on hierarchy, which conforms
maintenance domains. Different maintenance domains are assigned to the customer,
service providers or operators. The edges of each domain are Maintenance End Points
(MEPs). The ports within domains are Maintenance Intermediate Points (MIPs). The
maintenance hierarchy allows to monitor different segments of the Ethernet network,
which are under the responsibility of different hierarchy departments. The segmentation
of maintenance domains simplifies finding the problems on the L2 Ethernet network.
When the performance monitoring feature is not activated, the L2 (Ethernet)
performance monitoring functions are not possible to be performed.
Issue: 01
DN09146788
101
Figure 5
MEP
MEP
MEP
MEP
BTS
Eth
Ethernet
Ethernet
dual-ended (ETH-CCM)
single-ended (ETH-LMM / ETH-LMR)
This feature provides also configurable thresholds for triggering alarms for Frame Loss
Measurement and Frame Delay/Delay Variation Measurement. Thresholds are
configurable per measurement session.
The Frame Loss Measurements are obtained by means of counters for received and
transmitted data frames between a pair of MEPs. These counters are provided by the
performance monitoring feature. The Frame Loss Measurement can be calculated for
each direction. Far-end and near-end Frame Loss Measurements are supported. The
BTS supports both kinds of Frame Loss Measurements. The operator configures the
measurement nature.
g
3.1.1.4
Note that mesh, chain, tree, and circle topology should have point-to-point
Ethernet connections between MEPs to perform accurate Frame Loss
Measurement, whereas there are no similar conditions for Frame Delay/Delay
Variation Measurement.
System impact
Interdependencies between features
This feature does not need a separate license.
This feature needs the licenses of features:
102
DN09146788
Issue: 01
Impact on interfaces
This feature has no impact on interfaces.
The Service OAM can consume significant amount of bandwidth, particularly when
pro-active functions (ETH-CC) are activated simultaneously and using high
transmission rates. However, the Service OAM performance monitoring functions are
not meant to use high transmission rates. The feature standard recommends 10 fps.
The usage of these functions must be confined then.
The capacity demands for Service OAM performance monitoring functions is usually
not significant. With default settings, each ETH-CCM measurement consumes less
than 1 kbps, whereas ETH-LM and ETH-DM measurements - less than 0.1 kbps.
The default interval values for measurements are given below:
3.1.1.5
ETH-CCM measurement - 1 s
ETH-LM measurement - 10 s
ETH-DM measurement - 10 s
Faults
Table 58: New faults lists faults and reported alarms introduced with this feature.
Issue: 01
DN09146788
103
Table 58
New faults
Fault ID
Fault name
Reported alarms
61635
61636
61637
104
New counters
Counter ID
Counter name
Measurement
M5141C0
soamIngressFramesLost
M5141C1
soamIngressTotalFrames
M5141C2
soamNearEndFrameLossRatio
M5141C3
soamEgressFramesLost
M5141C4
soamEgressTotalFrames
M5141C5
soamFarEndFrameLossRatio
M5142C0
soamTwowayAverageDelay
M5142C1
soamTwowayMaxDelay
M5142C2
soamTwowayMinDelay
M5143C0
soamOnewayNearEnDelayVariation
M5143C1
soamOnewayFarEndDelayVariation
DN09146788
Issue: 01
Parameters
Table 60: New parameters lists parameters introduced with this feature.
Table 60
New parameters
Full name
Abbreviated name
Managed object
enableSoamPm
IPNO
enableSoamFrameLossMeas
OAMFLM
macAddr
OAMFLM
soamFrameLossAlarmThres
OAMFLM
soamFrameLossMeasInt
OAMFLM
soamFrameLossMeasMode
OAMFLM
enableSoamDelayMeasure
OAMDM
macAddr
OAMDM
soamDelayAlarmThresOneway
OAMDM
soamDelayAlarmThresTwoway
OAMDM
soamDmmPduSize
OAMDM
soamFrameDelayMeasInt
OAMDM
Commands
There are no commands related to this feature.
Issue: 01
DN09146788
105
3.1.1.6
Sales information
Table 61
Sales information
BSW/ASW
SW component
ASW
RAN
TRS LK
The activating procedure to activate the Ethernet Service OAM PM on the BTS needs:
The activating procedure to configure the PM measurement sessions on the BTS needs:
106
DN09146788
Issue: 01
3.1.2.1
The Ethernet Service OAM PM features can be set but they are not
operable.
The messages from the remote MEPs are discarded.
The PM measurements are not generated.
The activation must be confirmed using the Send button when using the
BTS Site Manager.
Expected outcome
The Ethernet Service OAM PM has been activated successfully on the BTS.
The Ethernet Service OAM PM statistics are cleared.
The BTS only answers to the incoming PM messages from the remote MEPs.
The PM measurement sessions are supported on the BTS:
Issue: 01
DN09146788
107
The PM measurement sessions with active status are automatically restarted on the
BTS.
g
3.1.2.2
The operator can set the BTS thresholds for triggering alarms.
The PM thresholds are set on the BTS for each measurement separately.
108
The Maintenance Association has zero or more than one remote MEP.
The Maintenance Association does not have the ETH-CC activated.
There are measurements under the same MEP with the same measurement
mode.
DN09146788
Issue: 01
The activation must be confirmed using the Send button when using the
BTS Site Manager.
Issue: 01
DN09146788
109
The OMS sends the measurement data to the NetAct ten minutes after every hour.
6
Expected outcome
The Frame Loss Measurement session has been activated on the BTS.
3.1.2.3
110
DN09146788
Issue: 01
c) Open the New drop-down menu and create Delay measurement session.
d) Mark on the Delay measurement in use checkbox.
3
The activation must be confirmed using the Send button when using the
BTS Site Manager.
Start the Soam Two Way Delay Statistics measurement (M5142) at OMS.
This step must be performed using:
Issue: 01
DN09146788
111
Start the Soam One Way Delay Variation Statistics measurement (M5143) at
OMS.
This step must be performed using:
Frame Loss Measurement session (make sure that there are any lost frames)
Frame Delay Measurement session
112
DN09146788
Issue: 01
After one minute verify that the proper PM counters are greater than zero.
This step must be performed one minute after measurement start.
The proper PM counters are (when performing the current step):
g
Issue: 01
M5142C0 - soamTwowayAverageDelay
M5142C1 - soamTwowayMaxDelay
M5142C2 - soamTwowayMinDelay
The Frame Delay counters must be always greater than zero at the present
moment.
DN09146788
113
Expected outcome
The Two-way Frame Delay counters are greater than zero.
The proper PM counters are presented during the one minute measurement.
The proper PM counters are updated after the completion of one minute
measurement.
5
Verify that the proper alarm has been raised when the threshold was reached.
This step must be performed one minute after measurement start.
The proper alarm can occur for (when performing the current step):
Expected outcome
The proper alarm has been raised when the threshold was reached.
The proper alarm does not occur when the threshold has been set to zero.
g
g
The proper alarms are presented as faults at the BTS Site Manager.
The proper alarm occurs only when the threshold has been reached after
the one minute measurement.
The proper alarms are reported from the BTS to the OMS / NetAct promptly.
The proper alarms can be monitored also using:
NetAct Monitor
OMS Fault Management
Further information
The proper alarms are canceled when the thresholds are not reached after the next
one minute measurement for:
After fifteen minutes verify that the proper PM counters are greater than zero.
This step must be performed fifteen minutes after measurement start.
The proper PM counters are (when performing the current step):
114
M5141C0 - soamIngressFramesLost
M5141C1 - soamIngressTotalFrames
M5141C2 - soamNearEndFrameLossRatio
DN09146788
Issue: 01
M5141C3 - soamEgressFramesLost
M5141C4 - soamEgressTotalFrames
M5141C5 - soamFarEndFrameLossRatio
g
g
M5143C0 - soamOnewayNearEndDelayVariation
M5143C1 - soamOnewayFarEndDelayVariation
Expected outcome
The One-way Frame Delay Variation counters are greater than zero.
The Two-way Frame Delay counters are greater than zero.
The Frame Loss counters are greater than zero.
Verify that the proper alarm has been raised when the threshold was reached.
This step must be performed fifteen minutes after measurement start.
The proper alarm can occur for (when performing the current step):
Expected outcome
The proper alarm has been raised when the threshold was reached.
Issue: 01
The proper alarm does not occur when the threshold has been set to zero.
The proper alarms are presented as faults at the BTS Site Manager.
The proper alarms occur only when the thresholds have been reached after
the fifteen minutes measurement.
DN09146788
115
The proper alarms are reported from the BTS to the OMS / NetAct promptly.
The proper alarms can be monitored also using:
NetAct Monitor
OMS Fault Management
Further information
The proper alarms are canceled when the thresholds are not reached after the next
fifteen minutes measurement for:
Expected outcome
The Frame Loss/Delay Measurement sessions have been activated successfully.
116
DN09146788
Issue: 01
The deactivating procedure to deactivate the Ethernet Service OAM PM (BTS) needs:
3.1.4.1
The Ethernet Service OAM PM features are stopped after one of the actions:
Issue: 01
DN09146788
117
The deactivation must be confirmed using the Send button when using the
BTS Site Manager.
Expected outcome
The Ethernet Service OAM PM has been deactivated successfully on the BTS.
The BTS discards the incoming PM messages from the remote MEPs.
The PM measurement sessions are not supported on the BTS.
The PM measurement sessions are stopped on the BTS and PM alarms are canceled.
The PM measurement sessions activation on the BTS does not have any effect.
The Frame Loss/Delay statistics are not cleared but they are not further updated.
g
3.1.4.2
The Frame Loss Measurement session (BTS) stops after one of the actions:
118
DN09146788
Issue: 01
The deactivation must be confirmed using the Send button when using the
BTS Site Manager.
Expected outcome
The Frame Loss Measurement session has been stopped on the BTS.
When Frame Loss Measurement session has been stopped on the BTS then:
Expected outcome
The Soam Frame Loss statistics measurement has been stopped at OMS.
The OMS stops sending the Frame Loss Measurement data to the NetAct.
3.1.4.3
Issue: 01
DN09146788
119
The Frame Delay Measurement session (BTS) stops after one of the actions:
The deactivation must be confirmed using the Send button when using the
BTS Site Manager.
Expected outcome
The Frame Delay Measurement session has been stopped on the BTS.
When Frame Delay Measurement session has been stopped on the BTS then:
120
DN09146788
Issue: 01
Stop the Soam Two Way Delay Statistics measurement (M5142) at OMS.
This step must be performed using:
Expected outcome
The Soam Two Way Delay Statistics measurement has been stopped at OMS.
The OMS stops sending the Two-way Frame Delay Measurement data to the NetAct.
4
Stop the Soam One Way Delay Variation Statistics measurement (M5143) at
OMS.
This step must be performed using:
Expected outcome
The Soam One Way Delay Variation Statistics measurement has been stopped at
OMS.
The OMS stops sending the One-way Frame Delay Variation Measurement data to
the NetAct.
Issue: 01
DN09146788
121
Operability features
4 Operability features
4.1 RAN2199: BTS Event Triggered Symptom Data
Collection
4.1.1 Description of RAN2199: BTS Event Triggered Symptom
Data Collection
Introduction to the feature
This feature introduces automatic fault-triggered BTS symptom data collection. The
triggering BTS faults are defined in the Site Configuration File (SCF) using the NetAct
Configurator.
4.1.1.1
Benefits
End-user benefits
This feature does not affect the end-user experience.
Operator benefits
This feature benefits the operator as follows:
4.1.1.2
Requirements
Software requirements
Software requirements lists the software required for this feature.
122
RAS
mcRNC
Flexi BTS
RU50
Planned for
later
releases
WN9.0
Flexi Lite
BTS
Flexi 10
BTS
NetAct
MSC
SGSN
MGW
UE
Planned for
later
releases
Planned for
later
releases
Support not
required
Support not
required
Support not
required
Support not
required
Support not
required
DN09146788
Issue: 01
Operability features
Hardware requirements
This feature requires one of the following features:
4.1.1.3
Functional description
The event triggered symptom data collection can be divided into following steps:
1.
2.
3.
4.
Figure 6: Symptom data collection from the BTS illustrates the log collection mechanism.
Figure 6
The list of BTS faults is available in the Flexi Multiradio BTS WCDMA Faults
document. The TRS faults (IDs within range 61000-61999) are not considered
as triggers for the symptom data collection.
A triggering threshold can be set - it defines how many times a certain fault should occur
for the same fault source to trigger the data collection. By default no triggers are defined.
Data collection after the selected faults occur
The log collection happens only when the fault occurs. The log consists of, for example:
Issue: 01
DN09146788
123
Operability features
HW configuration
alarm history
active SW version
transport configuration
black box data
performance data
auto-connection report
TSUPL: used by OMS to identify the file type as a symptom data file
<NE>: identifies the controller (for example, RNC)
<NEid>: the controller ID number
<BTSid>: the BTS ID number
<TRSHid>: identifies the troubleshooting task in the BTS
<date-time>: indicates when the file is created (using the OMS local time). The date
and time format is YYYYMMDDhhmmss.
The 71106 TROUBLESHOOTING DATA RECEIVED alarm indicates that the log
file has been transferred to OMS. The dwAlarmForUploadCompleted
parameter is used for disabling/enabling the alarm setting in OMS.
The 71129 TROUBLESHOOTING DATA CREATION OR UPLOAD FAILED
indicates that the data creation or upload to OMS has failed.
Old symptom data files are deleted automatically from the BTS (after being transferred to
OMS). When the clean up procedure starts in the OMS, the OMS deletes files older than
certain number of days (defined with the dwNELogDaysSpan parameter). By default,
files older than 10 days are removed. Additionally, the OMS monitors the disk space use
and if needed, performs additional clean up procedure.
With the dwBTSUploadEnabled parameter, the automatic data transfer to OMS can be
enabled/disabled.
Viewing the collected data
The files can be viewed using the Log Viewer in the OMS Element Manager. The Log
Viewer introduces the Troubleshooting data filter component to allow user to filter
troubleshooting files to show only those files not older than a defined period of days
(user can specify value from 1 to 30). When user logs in to OMS Element Manager, the
Troubleshooting data filter component contains the default value which is taken from the
124
DN09146788
Issue: 01
Operability features
4.1.1.4
System impact
Interdependencies between features
This feature is a part of generic troubleshooting data collection function that consists of
the following features:
Impact on interfaces
This feature has no impact on interfaces.
Impact on commands
There are no commands related to this feature.
4.1.1.5
Alarms
Table Related existing alarms lists existing alarms related to this feature.
Table 62
Issue: 01
Alarm ID
Alarm name
71106
DN09146788
125
Operability features
Table 62
Alarm ID
Alarm name
71129
Parameters
Table New parameters lists parameters introduced with this feature.
Table 63
New parameters
Full name
Abbreviated name
Managed object
symptomDataTriggerL
MRBTS
Table 64
Attribute
ClusterRoot/OMS/OMSPlatform/SS_SpringyUI/HideTRSFilesOlderThanDaysFilter
To make the new value effective, user needs to restart TomcatPlat using the following
command: fshascli -rn /TomcatPlat
Table 65: Related existing OMS LDAP parameters lists existing parameters related to
this feature.
Table 65
Attribute
ClusterRoot/OMS/OMSPlatform/SS_NELogManager/NELogManager/dwAlarmForUploadCom
pleted
ClusterRoot/OMS/OMSPlatform/SS_NELogManager/NELogManager/dwBTSUploadEnabled
ClusterRoot/OMS/OMSPlatform/SS_NELogManager/NELogManager/dwNELogDaysSpan
126
DN09146788
Issue: 01
Table 65
Operability features
Attribute
g
4.1.1.6
When the LDAP parameter value is changed, the new value immediately takes effect
(no additional action is necessary). It applies to all parameters in this table.
Sales information
Table 66
Sales information
BSW/ASW
SW component
BSW
RAN
Issue: 01
DN09146788
127
Operability features
Expected outcome
The RAN2199: BTS Event Triggered Symptom Data Collection feature is turned on.
Further information
It takes approximately 10 minutes to make the change effective in the OMS.
Expected outcome
The RAN2199: BTS Event Triggered Symptom Data Collection feature is turned off.
Further information
It takes approximately 10 minutes to make the change effective in the OMS.
128
DN09146788
Issue: 01
Operability features
4.2.1.1
Benefits
End-user benefits
This feature does not affect the end-user experience.
Operator benefits
This feature benefits the operator as follows:
4.2.1.2
Self healing reduces the effort for network management and maintenance and
increases the Flexi Multiradio BTS availability due to less outage.
Site visits can be avoided when a changed BTS transmission configuration prohibits
remote management connections.
Requirements
Software requirements
Table 67: Software requirements lists the software that is required for this feature.
RAS
RU50
Table 67
BTS Flexi 10
mcRNC
OMS
BTS Flexi
Flexi Lite
Planned for
later
releases
Software requirements
NetAct
Planned for
Support not
later releases required
MSC
SGSN
MGW
UE
Support not
required
Support not
required
Support not
required
Support not
required
Hardware requirements
For Flexi Multiradio BTS WCDMA this feature requires one of the following features:
Issue: 01
DN09146788
129
Operability features
4.2.1.3
Functional description
Autonomous fallback to previous configuration
A fallback to the previous configuration happens when the BTS fails to successfully
(re)connect the M-plane to the Network Management System after a remote
configuration update and activation. If the M-plane can be established with the old
configuration, a notification is sent to the Network Management System indicating that
the new configuration was not activated. If the old one fails as well, the received new one
is activated again and the BTS continues with the regular link failure mechanism.
The self healing recovery is initiated only after Transport Network Layer (TNL)
configuration changes via BTS Site Configuration file (SCF) activation. The TNL
configuration refers to the parameters defined in the Transport System (TRS) PDDB.
Figure 7
g
4.2.1.4
System impact
Interdependencies between features
There are no interdependencies between features.
130
DN09146788
Issue: 01
Operability features
Impact on interfaces
This feature has no impact on interfaces.
Impact on commands
There are no commands related to this feature.
4.2.1.5
Alarms
The following table lists alarms and faults, which are related to this feature.
Table 68
New fault
Alarm ID
Alarm name
7665
Parameters
Table 69
4.2.1.6
Full name
Abbreviated name
Managed object
enableTransportConfigF
allback
IPNO
Sales information
Table 70
Issue: 01
New parameter
Sales information
BSW/ASW
SW component
ASW
RAN
BTS LK
DN09146788
131
Operability features
4.2.2.1
4.2.2.2
132
DN09146788
Issue: 01
Operability features
1 Flexi Multiradio BTS WCDMA integrated to the network with FSMrel2 (excluding
FSIA and FSIB) or FSMrel3
NetAct integrated to the network.
RNC/mcRNC integrated to network
4.2.4.1
Issue: 01
DN09146788
133
Operability features
Connect to the WBTS locally, and monitor the O&M status of the WBTS.
Result
RNC IP has been modified to new target IP on WBTS IP configuration, and WBTS
OAM status is disconnected
Check the WBTS and WCELs status on target RNC on Netact GUI.
There will be no new target RNC because it is not a valid IP address.
Result
After the WBTS initiates re-establishment to the new target RNC for 10 connection
attempts, the WBTS falls back to the original RNC. Then DCNLinkStatus with
original RNC is Enabled, and the WCELs are alive.
Check the BTS status. Check the alarm on BTS, OMS, and NetAct.
Result
The WBTS modifies its RNC IP into the original RNC IP address, and O&M's
connection to the original RNC is established.
An alarm is issued indicating that the planned configuration changes are not
used in the WBTS --- 7665 BASE STATION TRANSMISSION ALARM is
present.
6
g
4.2.4.2
134
DN09146788
Issue: 01
Operability features
Result
The parameters are modified successfully in the plan.
2
Connect to WBTS locally, and monitor the O&M status of the WBTS.
Result
After the WBTS initiates re-establishment to the new target RNC for 10 connection
attempts, the WBTS falls back to the original RNC.
Check the BTS and WCELS status on a new target RNC on NetAct GUI.
Result
After WBTS initiates re-establishment to the new target RNC for ten connection
attempts, WBTS fall back to the original RNC
Result
The WBTS modifies its RNC IP to original RNC IP address, but WBTS will not be
able to connect because O&M is disabled on original RNC. After 10 times attempts,
the WBTS roll forward to the new target RNC once more.
6
Check the BTS status. Check the alarm on BTS, OMS, and NetAct.
Result
The O&M connection to both RNC is unestablished. In the WBTS site manager, the
RNC IP address should be the new target RNC. No RAN2554 alarm would be
present in the SEM.
Issue: 01
DN09146788
135
Operability features
4.2.5.1
4.2.5.2
136
DN09146788
Issue: 01
5.1.1.1
Benefits
End-user benefits
This feature provides better end user experience in terms of RTT delay.
Operator benefits
The feature provides faster data transfer for interactive applications and background
traffic.
5.1.1.2
Requirements
Software requirements
Table 71: Software requirements lists the software required for this feature.
RAS
mcRNC
RU50
Planned for
later
releases
OMS3.0
(RU50)
Support
not
required
MGW
UE
Table 71
RN8.0
Flexi BTS
Software requirements
Flexi Lite
BTS
Flexi 10
BTS
NetAct
MSC
SGSN
Support not
required
Support not
required
NetAct 8
EP1
3GPP
Rel-8
Hardware requirements
No hardware requirements. It is hardware independent.
5.1.1.3
Functional description
Functional overview
This feature enables faster data transfer for interactive applications and background
traffic by reducing delay in data handling, and push end to end HSPA RTT delay for a 32
Byte Ping to be comparable with LTE delay.
Issue: 01
DN09146788
137
Improvement in Round Trip Time (RTT) is achieved by reducing the delay components in
the data path between the network and UE. The feature focus to reduce RNC Delay in
HS(D)PA Downlink data path by using data arrival event to schedule data towards BTS
in Iub.
The data event trigger enables reduction of RTT, which further improves the response
times for interactive services and faster data transfer for background traffic, thereby
enhancing the user experience.
5.1.1.4
System impact
Interdependencies between features
This feature has no feature interdependencies.
Impact on interfaces
This feature has no impact on interfaces.
Impact on commands
There are no commands related to this feature.
5.1.1.5
Alarms
There are no alarms related to this feature.
Parameters
There are no key performance indicators related to this feature at this time.
138
DN09146788
Issue: 01
5.1.1.6
Sales information
Table 72
Issue: 01
Sales information
BSW/ASW
SW component
BSW
RAN
RNC LK
DN09146788
139
6.1.1.1
Benefits
End-user benefits
This feature does not affect the end-user experience.
Operator benefits
Increasing traffic, demand for multicarrier, multiband, and multi-sector sites leads
operator needs towards larger BTS site configurations, especially in hot spot areas. This
feature enables to build such configurations with simple SW configuration.
6.1.1.2
Requirements
Software requirements
Table 73: Software requirements lists the software required for this feature.
Table 73
Software requirements
RAS
Flexi Direct
IPA-RNC
mcRNC
Flexi Direct
RNC
OMS
Flexi BTS
RU50
Not planned
Support not
required
Support not
required
Not planned
Support not
required
WN9.0
MGW
UE
Flexi Lite
BTS
Flexi 10
BTS
NetAct
MSC
SGSN
Not relevant
WN9.1
NetAct 8
EP1
(RU50)
Hardware requirements
For Flexi Multiradio BTS WCDMA this feature requires one of the following features:
140
DN09146788
Issue: 01
For Flexi Multiradio 10 BTS this feature requires the following feature:
6.1.1.3
Functional description
Functional overview
Site configuration enables creation up to 12 cells without a license key. To activate
additional 6 cells in BTS configuration a license key (LK) is required.
Table 74
g
6.1.1.4
Number of cells
License keys
0 - 12
0 x LK
13 - 18
1 x LK
Need for license key(s) is checked based on the RNC cell setup.
System impact
Interdependencies between features
Currently, RAN2736 Extended BTS Site Capacity license key is needed if BTS site
configuration has more than 12 cells. RAN3017: Additional 6 WCDMA Cell Activation
replaces the existing solution.
Impact on interfaces
This feature has no impact on interfaces.
6.1.1.5
Alarms
There are no alarms related to this feature.
Issue: 01
DN09146788
141
Parameters
Table 75: Modified parameters lists parameters modified by this feature.
Table 75
6.1.1.6
Modified parameters
Full name
Abbreviated name
Managed object
extendedBtsSiteCapacity
BTSSCW
Sales information
Table 76
Sales information
BSW/ASW
SW component
ASW
RAN
BTS LK
Note that this feature is under license control. This feature requires a valid
license file. The feature code is 0000005171. See
WCDMA RAN License Operation document for details.
Start the WCDMA BTS Site Manager application and establish the connection
to the BTS.
Flexi Multiradio BTS WCDMA can autonomously request for missing license file(s)
from NetAct Licence Manager during feature activation (RAN2131: Automatic
Licence Distribution to Flexi BTS).
Make sure that you have selected Automatic licensing in use checkbox in the
Automatic License Distribution Settings page.
142
DN09146788
Issue: 01
Result
The feature RAN3017: Additional 6 WCDMA Cell Activation is activated.
Issue: 01
DN09146788
143
Start BTS Site Manager application and establish the connection to the BTS.
Start BTS Site Manager application and establish the connection to the BTS.
144
DN09146788
Issue: 01