8.2.5 UA04.0 Features Planning Guide

UA04.
0 Access Network Feature Planning Guide

Document number:
Document issue:
Document status:
Date:
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
External document
Copyright 2001-2003 Nortel Networks, All Rights Reserved

Printed in France
NOTICE:
The information contained herein is the property of Nortel Networks and is strictly confidential. Except as
specifically authorized in writing by Nortel Networks, the holder shall keep the information contained herein
confidential, shall disclose it only to its employees with a need to know, and shall protect it, in whole or in part,
from disclosure and dissemination to third parties with the same degree of care it uses to protect its own
confidential information, but with no less than reasonable care.
The holder is granted no rights to use the information contained herein. This information is provided by Nortel
Networks AS IS and for information purposes only, and Nortel Networks accordingly disclaims any and all is
warranties, representations, and conditions relating to its contents. No license in the information or the intellectual
property incorporated herein is granted to the holder.
The contents of this document can be modified by Nortel Networks at all times and without notice to the holder.
UA04.0 Access Network Feature Planning Guide
TABLE OF CONTENTS
1.
2.
3.
INTRODUCTION .........................................................................................................................4
1.1.
OBJECT .............................................................................................................................4
1.2.
SCOPE ...............................................................................................................................4
1.3.
AUDIENCE ..........................................................................................................................5
1.4.
REFERENCE DOCUMENTS ....................................................................................................5
UA04.0 ACCESS OBJECTIVES .................................................................................................6

2.1.
OBJECTIVES/KEY DRIVERS ...................................................................................................6
2.2.
OPTIONAL SW PACKAGES ....................................................................................................7
UA04.0 FEATURES ....................................................................................................................8

3.1.
ARCHITECTURE / PORTFOLIO / HW ......................................................................................8
UMTS BTS 12020, version 2 DC

(29702) ............................................................................................ 8
3.2.
PERFORMANCE AND CAPACITY .............................................................................................9
UA04.0 performances
(24231).............................................................................................................. 9
3.3.
SERVICES ENABLER ..........................................................................................................12
Network Assisted GPS for CS Calls
(27003) ........................................................................................ 12
New RABs
(26694, 26695)................................................................................................................ 16
3.4.
RADIO MOBILITY ................................................................................................................18
2G to 3G Handover for CS Domain
(13448)........................................................................................ 18
Support of 32/48 Neighbouring cellS
(24441) ...................................................................................... 20
3.5.
RESOURCES MANAGEMENT AND OPTIMIZATION ....................................................................22
Event Triggered RRC Measurement Reporting (21135)........................................................................ 22
CELL FACH step 4 : Always On
(22651) ........................................................................................ 24
Enhanced Compressed Mode Management In CEM (24871)................................................................ 27
3.6.
OPERATIONAL EFFECTIVENESS ...........................................................................................29
RNC Upgrade by Online Build and Restart (20597).............................................................................. 29
Node B Software Upgrade without Reset
(20648) ................................................................................ 30
Remote electrical TILT automatic
(20599) .......................................................................................... 32
Monitoring of OEM eqt through CCM 10BT (13490 ).......................................................................... 34
Node B IP Filtering
(26736 ) ............................................................................................................. 36
Traffic counters evolution
(25565) ................................................................................................... 37
IU counters evolution
(25566) ......................................................................................................... 39
IU 3G-2G counters
(25567) ............................................................................................................ 41
Radio counters evolution
(25568)....................................................................................................... 43
Quality Counters Evolution
(25993).................................................................................................... 44
Cell Inactivity Detection
(26164) ....................................................................................................... 46
4.
DELTA FROM PREVIOUS EDITIONS ......................................................................................49
5.
ABBREVIATIONS .....................................................................................................................49
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page
3 /52
1.
INTRODUCTION
1.1.
OBJECT
The purpose of the UA04.0 Access Network Feature Planning Guide is to describe the
Access features that make up Release UA04.0 of Nortel Networks UMTS Access network.
The features described in the guide map to the features listed in the UMTS04 Baseline. The
Baseline provides a snapshot of all features in a release.
1.2.
SCOPE
The UA04.0 Access Network Feature Planning Guide provides a high-level description of
UA04.0 Access features. Chapter 1 introduces the guide. Chapter 2 summarizes the
objectives of UA04.0. Chapter 3 describes UA04.0 Access features.
The features in Chapters 3 are listed under the following UMTS Access Program Categories:
Performance and Capacity
Service Enabler
Radio Mobility
Resources Management and Optimization
Operational effectiveness
Each feature description includes the feature title, reference number, and the following
information :
Feature Description
Feature Benefits
Impacted Systems
Dependencies (Hardware, Software, Feature, Inter-Working, Devices, and

Standards)
Restrictions/Limitations
Engineering Impacts
Operational Requirements (Counters, Configuration

Parameters, Fault Management and Alarms)
Feature Type (either Basic or Optional). Basic features provide the base
software functionality of the release. Optional features provide extra
functionality and can be added to enhance a system or network. The Product
Equipment Code (PEC) is listed next to Optional features for ordering purposes.
Management
and
This document aims to focus on UA04.0 content.
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page
4 /52
1.3.
AUDIENCE
The UA04.0 Access Network Feature Planning Guide is intended for Nortel Networks
customers and functional groups.
1.4.
REFERENCE DOCUMENTS
[R1]
UMT/SYS/INF/9008
UMTS04 Baseline
[R2]
UMT/MKT/INF/30
NSS16/UMTS04 Circuit Core Network Feature Planning

Guide
[R3] UMT/SYS/INF/9585
Core Packet Feature Planning Guide
[R4] UMT/OAM/INF/8782
Preside for Wireless Internet, Feature Planning Guide

UMTS04
[R5] UMT/SYS/INF/7906
[R6]
UMT/SYS/DD/158
Location Services GPS based on UE positioning
[R7]
UMT/SYS/DD/54
UMTS radio mobility
[R8] UMT/SYS/DD/147
UTRAN measurements and triggered
[R9]
RRC states management
UMT/SYS/DD/130
[R10] UMT/SYS/DD/140
RNC upgrade
[R11] UMT/SYS/DD/136
UTRAN Node B Upgrade
[R12] UMT/BTS/DD/484
Site LAN
[R13] UMT/PLM/INF/4862
Nortel Networks RNC Capacity Roadmap
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page
5 /52
2.
UA04.0 ACCESS OBJECTIVES
2.1.
OBJECTIVES/KEY DRIVERS
UTRAN 4 needs to complete several objectives:
Stability, Quality and Operational Effectiveness

Stable network behaviour against stress and load in commercial context
unscheduled outages targets 99,995% / NE
Quality of Service from End-User Perception
improvement on E2E voice delay required (NE to contribute to E2E target
250ms)
Effectiveness, easiness and reduced impacts of network operations in

commercial context
patch delivery & installation improvement, parameters on-line
modifications, Call Trace enhancements, upgrade downtime reduction (Node
B 20 min, RNC 20 30 min)
Business Objective : Key content required to

Support our customers and early launchers network optimization phase
Enhance value proposition of Nortels UMTS offer
Performance Enhancement
Loaded KPI
UTRAN04 is split into two loads :
UA04.0 which brings stability improvement in 2004, needed base before

important new services introduction
UA04.1 which supports new services and important enhancement in terms of

operational effectiveness.
Voice\
Stable network improvement
behavior
Quality of Service for End-User
Effectiveness, easiness
Reduced impacts of network
operations
Stability, Quality
and Operational Effectiveness
Quality Improvement
Enabling Revenue Generation

Providing Operator Cost
Reduction
Creating End-User Loyalty
Network Optimization
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page
6 /52

UA04.0 allows a delivery of required features for 2004 end of year and contributes to
the UTRAN04 objectives :
2.2.
Some additional services with new RABs, Assisted GPS (UE based).
Performance improvement with Enhanced Compressed Mode Management

on CEM, Event triggered based RRC MR.
Operational Effectiveness with enhanced upgrade process, new counters and

RETA
Loaded KPI
OPTIONAL SW PACKAGES
A number of UA04.0 features compose optional SW packages.
Pm ID
13490
Feature Title
Monitoring of OEM eqt through CCM 10BT
PEC Code
NTM501ABDA
Page
32
20599
Remote Electrical Tilt Automatic
NTM501ABDA
30
22651
RRC States - Step 4 (Always On and CELL_FACH

integration)
NTM501AAVA
22
27003
Network Assisted GPS for CS calls
NTM501ABFA
10
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page
7 /52
3.
UA04.0 FEATURES
3.1.
ARCHITECTURE / PORTFOLIO / HW
UMTS BTS 12020, VERSION 2 DC
(29702)
Feature Description
From a customer point of view, it will allow to use or re-use an external -48V DC power supply
source to power the BTS. AC network is still required to activate heating feature of the cabinet
and AC maintenance plug option.
DC Power
Supply
BTS
Heaters
AC Plug
UCPS
DC
AC
From a product point of view, it is equivalent to connect an external battery cabinet to our BTS
when internal batteries and rectifiers have been removed and some alarms masked.
Feature Benefits
This feature will allow to customers to power the BTS with an external power supply source.
Impacted Systems
Node B
Dependencies
Hardware
None
Software
UA04.0
Feature
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page
8 /52

None
Interworking
N/A
Standards
CE Mark
Restriction/Limitation
Limitation associated to the start up of the cabinet: The DC power supply voltage must be
>52V to start-up the BTS.
Limitation associated to the LVD Threshold: The LVD Threshold is not changed from the AC
version and is set to -44VDC. The BTS will operate only if the DC power supply voltage is
higher than -44V at the entry of the BTS.
Engineering Impacts
None
Operational Requirements
Counters
None
Configuration Management and Parameters
None
Fault Management and Alarms
None
Feature Type
Basic
3.2.
PERFORMANCE AND CAPACITY

Nortel Networks RNC Capacity Roadmap is described in a dedicated external document
[R13]
UA04.0 PERFORMANCES
(24231)
Feature Description
This feature is intended for tracking/improving UTRAN performances, which are key
requirements for Wireless operators.
Video Telephony is seen as a key application for UMTS deployment, and will be tracked with
a particular attention in UA4.0.
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page
9 /52

In UA4.0, it is required that all KPIs are at least as good as in the previous release, under no
load conditions. Furthermore, it is expected that the network load will start becoming heavy
in UA4.0. Therefore, impairment due to load (both system load and RF load) will be tracked
in this release, and should stay in an acceptable range: it is expected that impairment due to
load would not exceed 10% of the no-load value for each KPI.
Feature Benefits
The feature goal is to improve Quality of Service.
Impacted Systems
UTRAN
Dependencies
Hardware
None
Software
UA04.0
Feature
None
Interworking
None
Devices
None
Standards
None
None
Engineering Impacts
The KPI have to be used in Quality of Services and performance predictions.
Counters
None
None
None
Feature Type
Basic
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 10 /52
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 11 /52
3.3.
SERVICES ENABLER
NETWORK ASSISTED GPS FOR CS CALLS
(27003)
Feature Description
UA04.0 delivers a first solution of Network Assisted GPS. This method provides
excellent location accuracy and can be used, for instance, in order to provide the
following services:
location of emergency calls (E911, E112, )
roadside assistance
taxi reservation and dispatch
location-based services through call servers (traffic info, nearest pharmacy, ..)FRS
contributors provide a high-level technical description of the feature from a customer
perspective. As features are often simply part of larger component, contributors can
describe the role it plays within the component or how it contributes to the components
functioning.FRS contributors provide a high-level technical description of the feature
from a customer perspective. As features are part of larger components, contributors
can describe the role it plays within the component or how it contributes to the
components functioning.
This feature enables Network Assisted GPS in the following conditions :
the UE is in Cell_DCH connected mode with a CS Radio Bearer assigned
the location request comes from the CS domain
the UE supports the UE-based A-GPS positioning method
About Network Assisted GPS :

GPS (Global Positioning System) is an existing satellite-based location system from
the US Department of Defense. The space segment consists of 24 satellites at high
orbit constantly circling the earth and transmitting low power signals. A GPS receiver
measures the time of arrival of those signals, and performs a trilateration to compute
its location. A minimum of four satellites are needed in that process, as there are four
unknowns (x, y, z, and clock error).
GPS main benefit is excellent accuracy as it provides a mean location error of about
10-20 meters with standard GPS and clear view of the sky. However, while providing
good accuracy in most cases, a conventional GPS suffers from a number of issues:
the GPS receiver needs near Line Of Sight to four satellites. Therefore a conventional
GPS does not work well indoors or in urban canyons.
takes a long time to compute a first fix
can be very power consuming, as it continuously monitors the satellite constellation
To dramatically improve the performance of the GPS, it is possible to provide the

receiver with GPS Assistance Data from the cellular network, which will:
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 12 /52
reduce the GPS receiver start-up and acquisition times; the search window can be
limited and the measurements sped up significantly;
increase the GPS receiver sensitivity; positioning assistance messages are obtained via
the cellular network so the GPS receiver can operate also in low SNR situations when
it is unable to demodulate GPS satellite signals;
allow the GPS receiver to consume much less handset power than with a standalone
GPS ; this is due to rapid start-up times as the GPS receiver can be in idle mode when
it is not needed.
In order to obtain the GPS Assistance Data, the UMTS Radio Access Network
(UTRAN) needs to rely on a continuously operating GPS Reference Network (GRN)
which has clear sky visibility of the same GPS constellation as the assisted receivers.
The assistance data signaled to the UE may include all of the following information or
just a selected subset: e.g. reference time, visible satellite list, satellite signal Doppler,
code phase, Doppler and code phase search windows. This data can be valid for a
few minutes (e.g., less than 5 minutes) or longer depending on the code phase and
Doppler search window size that can be accommodated by the UE.
There are two types of network-assisted GPS methods, namely UE-based and UEassisted, which differ according to where the actual position calculation is carried out.
In UE-assisted, the computation of the position fix is done in the network, while in UEbased, it is done in the mobile. This feature enables the UE-based method.
Network Assisted GPS architecture:

In order to maximize synergies with the GSM SMLC, the multi-mode GMLC and GRN,
as well as to provide a highly scalable solution, the Positioning Calculation Function
(PCF) is externalized and supported on a Standalone A-GPS SMLC (SAS), as
described in 3GPP R5. The SAS is connected to the RNC through the IuPC interface.
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 13 /52
Nortel Networks MLC for GSM-GPRS-UMTS

Abis
LMU
LMU
BTS
BTS
Um
BSC
BSC
2G-MSC
2G-MSC
Gb
proprietary
Lb
LMU
LMU
2G-SGSN
2G-SGSN
Lg
Nortel Networks
Mobile Location
Center
SMLC
SMLC
GRN
SAS
SAS
Iupc
Uu
Ls
Lg
Iu-ps
Node
Node B
B
RNC
RNC
Le
GMLC
GMLC
Iu-cs
(SMLC)
(SMLC)
Location
Location
Applications
Applications
Lg
3G-SGSN
3G-SGSN
3G-MSC
3G-MSC
NORTEL NETWORKS CONFIDENTIAL
UMTS RNC - 6
The SAS performs the following procedures:
it continuously polls the GRN to compute the GPS Assistance data for the whole
network
it provides on request GPS Assistance data to the RNC relative to the approximate
position of the UE
The Serving RNC remains the pivotal network element for the UE positioning process
and provides the following functionality:
admission control of positioning requests:
positioning method selection:
overall UE Positioning coordination and control
It should be noted that in this implementation, no costly LMUs are required. The only
hardware addition in the network is the SAS.
Feature Benefits
This feature enables the Network Assisted GPS positioning method for established
calls in the circuit domain. This method provides excellent location accuracy and can
be used, for instance, in order to provide the following services:
location of emergency calls (E911, E112, )
roadside assistance
taxi reservation and dispatch
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 14 /52
location-based services through call servers (traffic info, nearest pharmacy, ..)FRS
contributors provide a high-level technical description of the feature from a customer
perspective. As features are often simply part of larger component, contributors can
describe the role it plays within the component or how it contributes to the components
functioning.FRS contributors provide a high-level technical description of the feature
from a customer perspective. As features are part of larger components, contributors
can describe the role it plays within the component or how it contributes to the
components functioning.
Impacted Systems
UTRAN :
RNC
OMC
MLC (SAS)
Mobiles : Yes (see Dependencies section).
Dependencies
Hardware
The SAS required
Software
UA04.0
MLC4.1 as introduction version of SAS and support of A-GPS UTRAN feature
Features
None
Interworking
With Core network

With SAS
With Mobiles
Devices
This feature requires mobiles supporting the A-GPS UE-based location method.
Standards
Main reference documents : 3GPP specs
23.271 Functional Stage 2 description of LCS

25.305 Stage 2 functional specification of User Equipment (UE) positioning in UTRAN
25.331 - Radio Resource Control (RRC) protocol specification
25.453 PCAP protocol
This feature enables Network Assisted GPS in the following conditions :
the UE is in Cell_DCH connected mode with a CS Radio Bearer assigned
the location request comes from the CS domain
the UE supports the UE-based A-GPS positioning method
.
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 15 /52
Engineering Impacts
None
Counters
New counters linked with Network Assisted GPS Method :

o
Number of GPS satellites for which GPS assistance data are delivered to UE
List of UE positioning GPS assistance data the RNC is allowed to send to UE
New counters linked with time of data transfer
For details, refer to Functional Note [R6]

New parameters to configure the operator preferences (A-GPS assistance data type, number of
satellites, timers) and the Iu-PC interface
New alarm to monitor the Iu-PC interface link.
New QoS alarm is introduced to raise loss of A-GPS Services
Feature Type
Optional
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 16 /52
NEW RABS
(26694, 26695)
Feature Description
In order to enable new applications and optimize radio resource usage, additional RBs are
provided in that release.
Naming convention
Each RAB is identified by its name, made from the framework CN_Domain TC UL rate/DL
rate, where:
CN_Domain is the Core Network domain which can either be CS or PS
TC is the Traffic Class
Conv for Conversational
Str for Streaming
I/B for Interactive or Background
UL rate/DL rate are respectively the uplink and downlink data rates in kbit/s
Each new RABs is recorded separately :

26694
PS I/B UL:32 - DL:64
26695
PS I/B UL:32 - DL:128
Feature Benefits
Enable new services
Optimize radio resource usage
Impacted Systems
RNC
Node B
Dependencies
Hardware
None
Software
UA04.0
Feature
None
Interworking
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 17 /52

With mobiles
Devices
Mobiles should support these new RABs
Standards
TS34.108
25071 UE Radio Access capabilities in RAB to RB mapping is not included in UA04.0 but in
UA04.1.
Engineering Impacts
None
Counters
None
None
None
Feature Type
Basic
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 18 /52
3.4.
RADIO MOBILITY
2G TO 3G HANDOVER FOR CS DOMAIN
(13448)
Feature Description
The objective of this feature is to allow the 2G to 3G Handover for the CS domain.
The decision, to hand-off a Mobile Station from a GSM serving cell to another cell, whether a
GSM cell or a UTRAN cell, is under the control of the 2G BSC.
On the RNC side, the handover trigger is the receipt a RANAP Relocation Request message
from the CS core network domain.
The RNC then needs to
support the incoming relocation procedures (involving SCCP connections initiated by

the CN)
format the HANDOVER TO UTRAN message (as defined in the RRC specification)
start of security procedure (ciphering & integrity) at the end of the handover
execution at RRC level
The 2G to 3G CS handover is done in three steps:

(1) Handover preparation phase. When the handover decision is made, the serving BSC
sends a Handover Required message towards the 2G-MSC, containing the target RNC
ID (this IE allows the source MSC to route the message to the correct 3G-MSC/RNC).
The request is forwarded to the target 3G RNC which allocates resources to support the
call. The request sent from the source BSC identifies only one cell in one RNC. There is
no list of possible targets. The "Source RNC to target RNC transparent container"
information element which is transferred to the target RNC contains:
the UE capability
the pre-defined configuration status (i.e. which pre-defined configurations have

been read by the UE if exists)
(2) Handover execution phase. The HANDOVER TO UTRAN COMMAND RRC message is
sent from the target 3G to the UE via the MSC nodes and the serving BSC. The
handover command message contains the target cell resource description. The
handover is performed when the UE is successfully connected to the 3G system.
(3) Old resource release phase. Old radio link(s) in GSM system are released.
Feature Benefits
Most likely, 3G coverage will be limited for some time, and therefore mobiles could be
handed over to GSM cells. It may then be useful to be able to come back to the UMTS
network before the call ends, even for CS calls, voice or CS data (PS calls will return to 3G
through cell reselection procedure). For instance, operators may want to place the dualmode terminals on the UMTS layer when available, so that they can start or receive a PS call
in addition to the CS one. Additionally, the handover to 3G could be triggered on a load
criterion in order to alleviate the GSM layer.
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 19 /52
Impacted Systems
UTRAN RNC and OAM
Dependencies
Hardware
None
Software
UA04.0
Feature
None
Interworking
2G BSS, Core Network
Devices
Multimode UE supporting 2G - > 3G CS
Standards
None
Nortel 2G BSS dont support this feature.
All inter-working activity with infra supplier should be synchronized with Nortel Networks.
2G -> 3G CS is delivered in UA04.0 to inter-work with other infra suppliers. This feature is
tested at IOT level to secure it. Therefore, support activity is limited.
Nortel RNS builds a Handover message containing the explicit target resource description.
Engineering Impacts
RF: interference impact => impact on radio planning
ND: capacity impact on 3G network, especially at UMTS coverage frontiers: 3G network
must be dimensioned in order to be able to support additional 2G subscribers as well
NMO: necessity of a good collaboration between both 2G and 3G networks (no problem if
same operator) in order to avoid ping-pong handovers.
Counters
Successful / Fail incoming 2G handovers
FRS 25567 : 2G-3G Counters Evolution
For more details, refer to [R7]
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 20 /52

Relocation from 2G Allowed / Disabled.
None
Feature Type
Basic
SUPPORT OF 32/48 NEIGHBOURING CELLS
(24441)
Feature Description
UMTS networks are in a growth stage with new cells frequently added and a result demand
for new neighborhoods. The limitation of 16 neighbor cells per measurement object (intrafrequency, inter-frequency, inter-system) makes the addition of new neighbors as the
networks grow especially complex when the neighbor lists are already full.
This feature increases the neighbor list size for up to 48 UMTS neighbor cells (with a
maximum of 32 intra-frequency cells, and a maximum of 32 inter-frequency cells) and 32
inter-system cells for users in Cell_DCH Connected Mode.
Feature Benefits
Increase the overall quality of the connections thanks to an accurate delivery of the neighbor
lists. Facilitate the operational side of neighbor list addition in dense areas.
Impacted Systems
OMC
Dependencies
Hardware
None
Software
UA04.0
Feature
None
Interworking
None
Devices
None
Standards
None
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 21 /52
In idle mode or Cell_FACH connected mode, only the 16 first neighbors are broadcasted in
SIB11.
Engineering Impacts
Neighboring cells datafill
Counters
None
New configuration and upgrade checks.
To be documented in NTPs and ENG documents.
Warning in case of wrong or strange configuration.
Feature Type
Basic
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 22 /52
3.5.
RESOURCES MANAGEMENT AND OPTIMIZATION

EVENT TRIGGERED RRC MEASUREMENT REPORTING
(21135)
Feature Description
The Nortel event triggered measurement reporting feature relies on combination of:
Periodic reporting as defined in 3GPP specifications at call establishment and on

mobility change.
Event- triggered reporting as defined in 3GPP specifications when stable mobility

criterion is fulfilled.
The principle of this solution is:

1. A call always starts in periodic mode
On transition from Idle mode to CELL_DCH state (after RRC connection setup if
establishment is performed over CELL_DCH)
On transition from CELL_FACH to CELL_DCH state (either on RAB Assignment

Request or Always-On upsize)
2. A UE is moved from periodic to event-triggered mode when stability criterion is fulfilled
Reduce RRC measurement reports sent globally by UEs in stable conditions
Required events are configured to allow mobility decision in UTRAN, i.e. event
1A and events 1F
3. A UE is moved back to periodic mode when stability criterion is no more fulfilled

The stability criterion based on which the RNC decides to configure a UE in event-triggered
mode is:
During N measurement reports:

1. Only one cell in the active set
2. None of the mobility criteria is hit (i.e. inter-RAT or inter-frequency handover
criteria)
3.
RRC Connection
Cell-FACH to Cell-DCH
Relocation
During N reports:
1) Only one cell in the active set &
2) None of the mobility criteria is hit
Periodic Mode
Event Mode
Reception of an Event 1a or 1f
If a mobility criterion is hit
Event 1a on CPICH Ec/N0
Event 1f.1 on CPICH Ec/N0
Event 1f.2 on CPICH RSCP
Intra-freq Periodic
measurements
RRC event-triggered mode implementation

UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 23 /52

As shown in the picture above, the supported events are:
Event 1A: for active set update
Event 1F: 2 events, one on CPICH Ec/N0 and one on CPICH RSCP as these are the
criteria used to trigger inter-RAT and inter-frequency handovers
This solution has been designed in order to fulfill 4 requirements:
Ensure fine knowledge of UE radio conditions through regular measurement reporting

when UE is in mobility situation or unknown situation (e.g. at the setup), relying on
periodic reporting capabilities.
Avoid useless measurement load when UE is in stable conditions, relying on eventtriggered reporting. Events are setup so that any significant change in the UE
environment will be signaled to the network and trigs back periodic reporting.
Keep the same mobility decision process: decision in UTRAN based on mobility
algorithm already used for periodic.
Feature Benefits
Short reaction time to add 2nd leg in the active set, since reporting will be performed
when event occurs without waiting for a periodical message.
Decrease of RRC messaging load: in stable mobility conditions, no measurements

reports are sent.
Moreover this feature is compatible with the current mobility features.
Impacted Systems
RNC
Node B
Dependencies
Hardware
None
Software
UA04.0
Feature
None
Interworking
With mobiles
Devices
Support of both periodic and event-triggered type of reporting as specified in 3GPP.
Standards
TS 25.331
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 24 /52
None
Engineering Impacts
Tuning of parameters, refer to UPUG
Counters
Number of transition from periodic mode to event mode in a cell
Number of transition from event triggered mode to periodic mode in a cell
Average of modes used.

For details, refer to [R8]
One parameter to enable/disable the feature
One parameter to configure the number of measurement reports during which

stability criterion shall be fulfilled before switching mode to event-triggered
mode
None
Feature Type
Basic
CELL FACH STEP 4 : ALWAYS ON
(22651)
Feature Description
The CELL_FACH state basically serves two purposes:
Support of signalling only communications (such as SMS, LA update, call

establishment, etc.): already delivered in UA03.1
Support of PS services suitable to RACH/FACH constraints (e.g. some WEB

browsing sessions, WAP sessions, etc.): delivered in UA04.0
The diagram describes the general view of how CELL_FACH will be used. The principle is
that:
all the signalling only connections are supported on CELL_FACH (regardless of the
CN domain)
all the CS services are supported on CELL_DCH
PS services with real-time constraint (Conversational and Streaming) are supported

on CELL_DCH
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 25 /52
PS services without real-time constraints (Interactive or Background) are supported

on CELL_FACH or CELL_DCH
CS+PS calls need to be supported on CELL_DCH (because of CS constraint)
Idle mode
CELL_DCH
RRC connection Request.

Target state depends on
RRC establishment cause
current FACH load
CELL_FACH
call setup signalling phase
CELL_DCH
RAB assignment.
Target state is always CELL_DCH
CELL_FACH
RAB is assigned
During the call, depending on

the amount of user traffic on either UL or DL
current FACH load
support of simultaneous CS and PS services
Cell_FACH usage general view

Step 4 description
At RRC connection set-up (i.e. when receiving the RRC CONNECTION REQUEST
message), the RNC may set-up the call in either CELL_FACH or CELL_DCH state
depending on:
RRC establishment cause
the current FACH state
At RAB assignment request, the mobile is moved to CELL_DCH in any case.

Thanks to step 4, later on during the call, depending on user activity, FACH load and
whether UL/DL user traffic fits the RACH/FACH constraints or not, users may be moved from
CELL_DCH to CELL_FACH or the other way round, thus providing Always-On capability with
CELL_FACH state.
Downsizing
Tdownsize expiry
CELL_DCH
(Granted RB)
idle state transition

Tinactivity expiry
CELL_FACH
Idle Mode
Upsizing - Traffic
resumption
RB establishment Traffic resumption
Always-On transitions with CELL_FACH
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 26 /52
UL downsize/DL downsize conditions are based on the same algorithm as for

Always-On using CELL_DCH (i.e. DCH rate adaptation).
UL upsize/DL upsize conditions are based on RACH/FACH buffer occupancy, which

reflects the state of congestion of the transport channel
Downsizing is triggered if UL and DL user traffic falls below configured

throughput threshold during T1 timer
Upsizing is triggered as soon as UL or DL DTCH buffer is above configured

thresholds
UL release/DL release conditions (transition from/to idle) are based on the same
algorithm as for Always-On using CELL_DCH
RRC connection is released if UL and DL user traffic equal to 0 during T2

timer
Feature Benefits
Customer benefits from the feature are as follow:
Gain on radio capacity due to statistical multiplexing of user data on common resources
Integration of CELL_FACH in the existing Always-On mechanism results in resource

saving as dedicated resources (even low, e.g. PS I/B 8/8), are no more reserved for
inactive user
Impacted Systems
RNC and OMC
Dependencies
Hardware
None
Software
UA04.0
Feature
None
Interworking
With mobiles
Devices
Support of CELL_FACH
Standards
TS 25.331
There is no fallback downsized configuration. In case there is a FACH CAC failure (i.e.
FACH is already loaded at its maximum), the mobile is kept on its current DCH.
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 27 /52
Engineering Impacts
Impacts on UTRAN design and NUSCM.
Tuning of Always On parameters, refer to UPUG
Counters
Proposed list of CELL_FACH counters:
Number of transitions from CELL_FACH to idle
Number of transition attempts from CELL_FACH to CELL_DCH
Number of failed transitions from CELL_FACH to CELL_DCH
Number of transition attempts from CELL_DCH to CELL_FACH
Number of failed transitions from CELL_DCH to CELL_FACH
Number of cell updates
Number of CELL_FACH calls dropped because of UL congestion
Number of CELL_FACH calls dropped because of DL congestion

One parameter to enable/disable transition to CELL_FACH
Threshold on user rate for DL and UL transition from CELL_DCH to

CELL_FACH
Threshold on UL user data rate for transition from CELL_FACH to CELL_DCH

(i.e. part of event 4A)
Threshold on DL user data rate for transition from CELL_FACH to CELL_DCH
Timer T1 (can be defined per OLS) for downsizing

None
Feature Type
Optional
ENHANCED COMPRESSED MODE MANAGEMENT IN CEM
(24871)
Feature Description
With Enhanced Compressed Mode Management introduction, the Compressed Mode
algorithm may be enabled for handover using CEM Alpha for 384 and 256 kbps Radio
Bearers.
Feature Benefits
This feature introduces the required Software Enhancements for supporting Compressed
Mode on all Radio Bearers using CEM alpha boards
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 28 /52
Impacted Systems
Node B
Dependencies
Hardware
None
Software
UA04.0
Feature
None
Interworking
The enhanced Compressed Mode management shall operate either with homogeneous
or heterogeneous pool of CEM(s).
Devices
None
Standards
None
RAB PS 64/256 and PS 64/384 are not activated in Node B.
Engineering Impacts
Nortel does not recommend activating CM for high throughput data rates :
To ensure data continuity, the recommendation is to use the iRM scheduling to

downgrade to PS 64/128 or PS 64/64 before performing HO to 2G.
Once iRM scheduling is activated following recommendations, whether PS 64/256 or

PS 64/384 is activated or not in Compressed Mode has no importance.
Counters
None
None.
None
Feature Type
Basic
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 29 /52
3.6.
OPERATIONAL EFFECTIVENESS
RNC UPGRADE BY ONLINE BUILD AND RESTART
(20597)
Feature Description
For upgrade with MIB format change, it shall be possible to use a type 6 upgrade :
background download of new software and MIB structure,
on-line new MIB build N+1,
restart.
This is needed to reach the targeted service outage during software upgrade.
Feature Benefit
Release
Type of upgrade
UA02.1 -> UA03.1
RNC Impact
Comments
Cell Impact
use of Upgrade T3:

offline restart including CNode card flash(40mn) +
RNC upgrade with 60mm to 240mn 60mm to 240mn
offline MIB build (from 20mn to 200mn depending on
MIB change
outage
outage
the RNC configuration)
synchronized restart of CNode and INode
use of Upgrade T3:
RNC upgrade with 40mn to 70 mn 40mn to 70 mn offline restart (20mn) + offline MIB build (from 20mn
to 50mn depending on the RNC configuration)]
MIB change
outage
outage
RNC upgrade
use of Upgrade T7:
without MIB
20mn outage
20mn outage
change
Intra UA03.1
UA03.1 -> UA03.2
RNC upgrade with

MIB change
40mn to 70 mn
outage
40mn to 70 mn use of Upgrade T3

outage
UA03.1 -> UA04.0
RNC upgrade with

MIB change
40mn outage
40mn outage
UA03.2 -> UA04.0
RNC upgrade with

MIB change
40mn outage
40mn outage
intra UA04.0
RNC upgrade
without MIB
change
20mn outage
20mn outage
use of Upgrade T6
MIB build online + offline restart including CNode
card flash(40mn)
use of Upgrade T6
MIB build online + offline restart including CNode
card flash(40mn)
use of Upgrade T7
Impacted Systems
RNC
OMC
Dependencies
Hardware
None
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 30 /52

Software
UA04.0
Feature
None
Interworking
None
Devices
N/A
Standards
N/A
N/A
Engineering Impacts
N/A
Counters
N/A
N/A
N/A
Feature Type
Basic
NODE B SOFTWARE UPGRADE WITHOUT RESET
(20648)
Feature Description
When new software is activated in the BTS, this activation shall lead to a reset of the BTS
only when needed. This is important for new modules introduction.
This Node B software version will be activated on all Node Bs. The activation of this new
software shall not have any impact on service since the only changes are in file 0 and the
addition of a new file for the new module. The new file will be downloaded from OMC-B to
the Node B later, when the new module is introduced in the Node B.
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 31 /52

Here some example to precise some cases (but this is not exhaustive) corresponding to the
introduction of a new software that does not required the restart of the NodeB.
In all following cases, the reset of the Node B is not needed
Download of a new TIL applet on CCM
Download of a new File0, describing new boards not present in the NodeB .
Download of a new delivery, which does not imply to change software on all board
types.
Feature Benefits
Minimize service interruption in case of problem fix delivery.
Smooth introduction of new Node B software within a major version.
Impacted Systems
Node B, no impact on RNC and OMC
Dependencies
Hardware
None
Software
UA04.0
Feature
N/A
Interworking
None
Devices
None
Standards
None
None
Engineering Impacts
None
Counters
None
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 32 /52

None
None
Feature Type
Basic
REMOTE ELECTRICAL TILT AUTOMATIC
(20599)
Feature Description
This feature will provide the possibility to manage a Remote Electrical Tilt Automatic antenna
from the OMC-B.The operator should be able to manage (tilt modification and control) RETA
antennas from the OMCB (over IP) through the BTS.
Objective is to define an IP interface between OMC/BTS and OEM in order to manage
transparently different antenna manufacturers equipment. The operator should also be able
to create a high level application to perform automatic tilt change using input data file
N ortel N etw orks R ETA S olution

(R em o te E le ctric al T ilt Au to m atic)
N o d e B Site
hub
Antenna
control
O ther cell site
O EM
A n tenn a M anag em ent

S ystem (m ay be ho sted
by P reside)
RNC
E1
AT M
N etwork
E thernet
link
IP/E thernet
A TM or IP
NNetwork
etwork
IP
Routin g
S ystem
O EM M anagem ent
flo w m erged w ith
U TR A N
M anage m e nt F low
IP/A TM
IP/ATM
IP /A ny support
O E M M a nagem e nt Data : IP
N O R T E L N E T W O R K S C O N F ID E N T IAL
R AE DT V01.0 1- 1
Feature Benefits
Currently, optimizing wireless network coverage is very challenging due to a large number of
parameters that can affect it. Down-tilting is an important procedure often utilized by network
designers to help optimize performance. There are many factors that could require an
operator to change the tilt of an antenna system, including seasonal variations in weather
and foliage, area vehicular traffic patterns and new building construction.
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 33 /52

Now (with 2.5G) and 3G Networks, based on CDMA with capacity & coverage trade-offs,
performance optimizations are expected and down-tilting procedures would be more an
more necessary. As 60% of site antennas would be revisited during the optimization period
at least once to change the tilt. In addition, half of the sites would be impacted during
densification processes.
The RETA Solution would help operators to save operational expenses by adjusting
remotely the tilt of any antenna sector by entering the required parameters from a remote
management system.
Ultimately an operator could even run a program that automatically adjusts the tilts at
predetermined times and dates or a system that dynamically adjusts the tilt based on
changing conditions.
Further cost savings can be achieved by the operator: Future site costs are reduced by the
need to install only one antenna and by eliminating the need to swap one fixed electrical
down tilt model for a different down tilt model at a later date.
Other savings can be achieved by reduced inventory management costs since fewer
antenna models are required.
Impacted Systems
OMC-B
Dependencies
Hardware
An external 10base Tx Ethernet Hub must be available. This hub should have 8 ports
allowing thus to plug two CCM boards (when duplex management of CCM is available)
and up to 6 OEM devices. This hub must be able to operate in Outdoor condition i.e.
supporting an 48 VDC power supply and working in the thermal range 0 - 70 C
Software
UA04.0
Feature
FRS 13490 for OEM management through NodeB
This feature has an impact on the Duplex CCM feature.
Interworking
OEM
Devices
None
Standards
None
None
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 34 /52
Engineering Impacts
The introduction of this feature induced an additional effort on UTRAN s IP address
management that could be handled using OCAN.
Datafill impact = provisioning of cells electrical down-tilt
Counters
None
None
For details refer to [R12]
Feature Type
Optional
MONITORING OF OEM EQT THROUGH CCM 10BT
(13490 )
Feature Description
This feature allows to connect OEM equipment though the Ethernet port of the Node-B, and
to supervise them from a remote site. The Node-B and the RNC will route IP frames up to
the Management system, which will likely be co-located with the Preside Management
Platform. On the Iub interface, IP frames of OEM equipment will be carried on the same VCC
as the IP traffic for Node-B management traffic. Several equipments can be connected to the
Node-B 10-Base-T Ethernet port through a hub.
This feature can be used only for low volume traffic as those generated by Supervision
protocols (SNMP ...) : its not intended for providing an extension to a high bandwidth LAN.
Feature Benefits
OPEX Savings: it is possible to manage / supervise equipment on the Node-B site from a
remote location.
Impacted Systems
UTRAN, WG
Dependencies
Hardware
This feature is compatible with both CCM and iCCM. A hub may be needed if dual iCCM
are installed, or if more than one OEM is required.
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 35 /52

Software
UA04.0
RNC (RIP or OSPF introduction in the WG)
Feature
FRS 20957 : UTRAN transmission OAM features : cf. FPG OAM 03
FRS 24205 : OAM Remote Site LAN IP routing
Interworking
OEM device
Devices
None
Standards
None
Throughput for VCC OAM limited to 150 kbps
Engineering Impacts
For installation, it requires additional work on the applicable addressing plan. For a migration
of a Node B, this is to be studied. These studies shall be conducted for the In-band
management and for the Out-of-band management.
Counters
OAM counters which are specific to the OEM.
IP counters
To be addressed mainly in order to allow a smooth migration of a Node B.
Alarms specific to the OEM.
Wrong definition of Node-B IP subnet.
Feature Type
Optional
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 36 /52
NODE B IP FILTERING
(26736 )
Feature Description
The introduction of the Site Lan feature transforms the IP behavior of the NodeB. By
introducing a routing capability through the NodeB between two IP networks (Site Lan and IP
Backhaul), the NodeB becomes an IP router. In that perspective it is mandatory to control
and protect the forwarding of the IP datagrams between the two networks. Without such a
control datagams could be sent and received to the Operator Network.
Feature Benefits
This feature enables to improve the security behavior of the NodeB, by filtering the non
identified datagrams. This feature a step in the global security strategy of the NodeB, the
next step will provide security alarms enhancements.
Impacted Systems
Node B
Dependencies
Hardware
This feature is compatible with both CCM and iCCM.
Software
UA04.0
Feature
FRS 24205 : OAM Remote Site LAN IP routing
Interworking
None
Devices
None
Standards
None
N/A
Engineering Impacts
N/A
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 37 /52
Counters
N/A
N/A
N/A
Feature Type
Basic
TRAFFIC COUNTERS EVOLUTION
(25565)
Feature Description
This feature is used to enhance the operational effectiveness of the Access solution, it is to
permit the troubleshooting of the system and monitor its performance.
Counters
Activity Time for DL Transfer for CS
Activity Time for DL Transfer for PS
Activity Time for UL Transfer for CS
Activity Time for UL Transfer for PS
Average number of UL Access Stratum

Configuration established
UMT/SYS/INF/10063
01.07/ EN
Meaning
To give the time elapsed between the first
and the last PDU sent.
Screening Criteria :
DlAsConfId (DL Access Stratum
Configuration)
and the last PDU sent.
DlAsConfId (DL Access Stratum
Configuration)
and the last PDU received.
UlAsConfId (UL Access Stratum
Configuration)
and the last PDU received.
Configuration)
To indicate an average of the number of
UlAsConfId established per RNC, based on
time average over collection period.
Configuration)
Standard
23/December/2005
Page 38 /52
Feature Benefits
This feature allows the operators to activate and collect a set of Traffic counters. This will not
only enable operators troubleshoot the system and analyze the performance of each RNC or
Node B, but also monitor the traffic generated by the users.
Impacted Systems
RNC
Performance Server Access Data Interface.
Access Module (OMC-R/OMC-B)
Dependencies
Hardware
N/A
Software
UA04.0
Feature
None
Interworking
None
Devices
N/A
Standards
N/A
N/A
Engineering Impacts
Bandwidth required on the OAM link.
Counters
N/A
N/A
N/A
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 39 /52
Feature Type
Basic
IU COUNTERS EVOLUTION
(25566)
Feature Description
This feature is used to enhance the operational effectiveness of the Access Solution; it is
used permits the troubleshooting of the system and monitors its performance.
Counters
RAB Establishment Request per RAB Type
Meaning
Number of RAB establishment attempts.
Screening Criteria:
-
RAB Establishment Success per requested RAB

type
RAB (Traffic Class + combined UL/DL

Maximum bit rates)
Number of successful RAB establishment

per requested RAB type (to map the
successes with the requests).
Screening Criteria:
-
RAB Establishment Success per granted RAB

type
Requested RAB (Traffic Class

combined UL/DL Maximum bit rates)
Number of successful RAB establishment

per granted RAB type.
-
Iu Release Command
Granted RAB (Traffic Class + combined

UL/DL Maximum bit rates)
Number of RANAP Iu Release Command

messages received by the RNC
New screening :
-
Relocation Cancelled New
O&M Intervention
Unspecified Failure
User Inactivity
No Remaining RAB
Feature Benefits
This feature allows the operators to activate and collect a set of IU counters. These will not
only enable operators troubleshoot the system and analyze the performance in term of
network accessibility, but also monitor the traffic generated on those interfaces.
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 40 /52
Impacted Systems
RNC
Dependencies
Hardware
N/A
Software
UA04.0
Feature
None
Interworking
None
Devices
N/A
Standards
N/A
N/A
Engineering Impacts
Counters
N/A
N/A
N/A
Feature Type
Basic
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 41 /52
IU 3G-2G COUNTERS
(25567)
Feature Description
This feature is used to enhance the operational effectiveness of the Access solution, it is
used in conjunction with the Alarms on threshold feature to permit the troubleshooting of the
system and monitor its performance.
Counters
Iu Relocation Requests
Meaning
Number of RANAP Iu Relocation Requests
New Screening :
- CS 3G->3G
- PS 3G->3G
- CS 2G->3G
- PS 3G->3G
Iu Relocation Request Failures CS
Number of failed IU CS relocations.

New Screening :
- 3G->3G relocation timeout
- 3G->3G relocation failure in target system
- 3G->3G relocation unable to establish
- 3G->3G other relocation failure
Iu Relocation Request Failures PS
Number of failed IU PS relocations.

New Screening :
Feature Benefits
This feature allows the operators to activate and collect a set of IU 3G-2G counters. These
will not only enable operators troubleshoot the system and analyze the performance of the
network mainly in terms of Iu Relocation, but also monitor the traffic generated on those
interfaces.
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 42 /52
Impacted Systems
RNC
Dependencies
Hardware
N/A
Software
UA04.0
Feature
13448
Interworking
None
Devices
N/A
Standards
N/A
Nortel 2G BSS dont support 2G -> 3G CS.
2G -> 3G CS is delivered in UA04.0 to inter-work with other infra suppliers. This feature is
tested at IOT level to secure it.
Engineering Impacts
Counters
N/A
N/A
N/A
Feature Type
Basic
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 43 /52
RADIO COUNTERS EVOLUTION
(25568)
Feature Description
This feature is used to enhance the operational effectiveness of the Access solution, it is
used in conjunction with the Alarms on threshold feature to permit the troubleshooting of the
system and monitor its performance.
Counters
UEs with N Radio Link in Active Set
Meaning
Distribution of the number of mobiles
having N Radio-Links in their Active Set
Screening Criteria:
- Number of Radio-Links
Dropped Calls on Last RL failure
Number of calls that have been dropped

because the last RL of the Active Set has
failed.
- Dl As Conf
Measurement Control Failure
Number of RRC measurement control

failure messages received from the UE.
Feature Benefits
This feature allows the operators to activate and collect a set of new/updated Radio
counters. These will not only enable operators troubleshoot the system and analyze the
performance of the network, but also monitor the traffic generated on those interfaces.
Impacted Systems
RNC
Dependencies
Hardware
N/A
Software
UA04.0
Feature
None
Interworking
None
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 44 /52

Devices
N/A
Standards
N/A
N/A
Engineering Impacts
Counters
N/A
N/A
N/A
Feature Type
Basic
QUALITY COUNTERS EVOLUTION
(25993)
Feature Description
This feature is used to enhance the operational effectiveness of the Access solution, it is to
permit the troubleshooting of the system and monitor its performance.
The aim of this evolution is to count CSV/CSD/PS Transport Block Error Rate using the
CRCI check
The function of checking the CRCI of each RLC PDU lies with the I-Node for the purpose of
Outer Loop Power Control and to count the number of failed CRCI (ie. CRCI=1)
Also, it should be possible to screen existing counter #503 (Iu Release Request) based on
traffic channel.
Counters
CS Data Transport Block Rate
Meaning
Number of CS Data Blocks received with CRCI = 1.
Screening Criteria:
- UL AsConfId
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 45 /52

PS Data Transport Block Rate
Number of PS Data Blocks received with CRCI = 1.

Screening Criteria:
- UL AsConfId
CSV Transport Block Rate (good frames)
Number of CS voice Transport Blocks with Class A

bits received with CRCI = 0.
Screening Criteria:
- UL AsConfId (screenings related to AsConfIds that
do not include voice will remain equal to 0)
CSV Transport Block Rate (bad frames)
Number of CS voice Transport Blocks with Class A

bits received with CRCI = 1.
Screening Criteria:
- UL AsConfId (screenings related to AsConfIds that
do not include voice will remain equal to 0)
Abnormal CS Iu Release Request
Number of CS IU release request due to abnormal

conditions (i.e. excludes if last remaining RAB is
released by Core Network)
- DL AsConfId
Abnormal PS Iu Release Request
Number of PS IU release request due to abnormal

conditions (i.e. excludes Always on and if last
remaining RAB is released by Core Network)
- DL AsConfId
Feature Benefits
This feature allows the operators to activate and collect new Quality and Retain ability
counters.
Impacted Systems
RNC
Dependencies
Hardware
None
Software
UA04.0
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 46 /52

Feature
None
Interworking
None
Devices
None
Standards
None
None
Engineering Impacts
Counters
N/A
N/A
N/A
Feature Type
Basic
CELL INACTIVITY DETECTION
(26164)
Feature Description
This feature is used to enhance the operational effectiveness of the Access Solution, it is to
enable the troubleshooting of the system.
This feature consists of creation of a new set of counters at RNC level, for each cell and
leverage the new OAM alarm on threshold.
Counters
Paging Inactivity
UMT/SYS/INF/10063
Meaning
To count time elapsed since the last Successful RRC
connection setup with any of the MT causes on each cell.
01.07/ EN
Standard
23/December/2005
Page 47 /52

RACH Inactivity
To count time elapsed since the last Successful RRC

connection setup with any cause on each cell.
Traffic Inactivity
To count time elapsed since the last RL setup or RL addition

on each cell.
This features consists of creation of a new set of counters at RNC level, for each cell and leverage the
new OAM alarm on threshold.
Feature Benefits
This feature allows the operators to detect sleepy cells.
Experience has shown that despite standard Fault detection mechanisms, Sleepy cells
situations may happen, for various reasons which cannot be predicted in advance.
The goal of the solution proposed is to generate alarms when Sleepy cells symptoms are
detected whatever the cause.
The solution does not address slow traffic degradations, but inactivity situations
Impacted Systems
RNC, OAM
Dependencies
Hardware
None
Software
UA04.0
Feature
N/A
Interworking
None
Devices
None
Standards
None
None
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 48 /52
Engineering Impacts
None
Counters
None
None
None
Feature Type
Basic
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 49 /52
4.
DELTA FROM PREVIOUS EDITIONS

Version 01.01 is in line with the POR presented at UA04.0 BR
Version 01.02
Approved version after comments of IPT members
Version 01.03
A-GPS CS Calls only PmId 25028 Churned Out

RAB PS I/B 128/128 PmId 23058 Churned Out
Version 01.04
Node B IP filtering PmId 26736 Churned In
Version 01.05
Update of feature 24871
Version 01.06
A-GPS CS Calls only PmId 27003 Churned In

same as 25028 in UA03.2 1900Mhz
Version 01.07
3.1.
ARCHITECTURE / PORTFOLIO / HW section added
UMTS BTS 12020, version 2 DC - 29702
5.
ABBREVIATIONS
2G
3G
3GPP
A&S
AAL2
AAL5
AICH
AKA
Auc
BBU
BIT
BLER
BSIC
BSC
BSS
BSSMAP
BTS
CAC
CBR
CCM
CEM
CK
CES
CN
CORBA
CPICH
CR
CS Domain
CTCH
DCCH
DCH
DDM
DL
UMT/SYS/INF/10063
Second Generation
Third Generation
Third Generation PartnerShip Project
Applications and Services
ATM Adaptation Layer type 2
ATM Adaptation Layer type 5
Acquisition Indicator Channel
Authentication & Key Agreement
Authentication Center
Base Band Unit
Bit Error Rate
Block Error Rate
Base Station Identity Code
Base Station Controller
Base Station Sub-system
BSS Management Application part
Base Transceiver Station
Call Admission and Control
Constant Bit Rate
Core Control Module
Channel elements Modules
Ciphering Key
Circuit Emulation Service
Core Network
Common Object Request Broker Architecture
Common PIlot CHannel
Change Request
Circuit Switched Domain
Common Traffic Channel
Dedicated Control Channel
Dedicated CHannel
Dual Duplexer Module
Downlink
01.07/ EN
Standard
23/December/2005
Page 50 /52

DRF
DSCH
DSP
DTCH
DTM
FDD
FER
FRU
GGSN
GMLC
GRN
GSM
H/W
HLR
Ho
HPLMN
BTS
IOT
IP
IRM
RNC
LBS
L3
LCD
MAC
MCPA
MIB
MNC
MS
MSC
MUD
NBAP
NSP
NVIOT forum
O&M
OAM
OCAN
OLS
OSI
OSS
OTSR
PA
PCCPCH
PCM
PDP
PDU
PICH
PLMN
PMAN
PP7K
PRACH
PS
PS domain
p-SCH
PWI
QoS
RAB
RACH
RANAP
RB
UMT/SYS/INF/10063
Data Request File

Downlink Shared Channel
Digital signal Processor
Dedicated Traffic Channel
Dual Transfer Mode
Frequency Division Duplex
Frame Error Rate
Field Replaceable Units
Gateway GPRS Support Node
Gateway Mobile Location Center
GPS Reference Network
Global System for Mobile communications
Hardware
Home Location Register
Handover
Home PLMN
Base Transceiver Station
Interoperability testing
Internet Protocol
Intelligent Ressource Management
Radio Network Controller
Location Based Services
Layer 3
Long Constrained Data
Medium Access Control (protocol layering context)
Multi-Carrier Power Amplifier
Management Information Base
Mobile Network Code
Mobile Station
Mobile Switching Center
Multi User Detection
Node B Application Part
Network Services Platform
Network Vendor IOT forum
Operations and Maintenance
Operation, Administration and Maintenance
Off Line Configuration of Access Networks
Olympic Level Service
Open System Interconnection
Operator Specific Services
Omni Transmit Sector Receive
Power Amplifier
Primary Common Control Physical CHannel
Pulse Code Modulation
Packet Data Protocol
Packet Data Unit
Page Indicator Channel
Public Land Mobile Network
Performance Manager for Access Network
Passport 7400 product range
Physical Random Access Channel
Policy Services
Packet Switched Domain
Physical Shared Channel
Preside for Wireless Internet
Quality of Service
Radio Access Bearer
Random Access Channel
Radio Access Application Part
Radio Bearer
01.07/ EN
Standard
23/December/2005
Page 51 /52

RETA
RF
RLC
RNC
ROC
RRC
RRM
RSSI
SAI
SAS
SMLC
SCCP
SCCPCH
USGSN
SHO
SIB
SG
SIR
SRNC
SRNC
SS7
s-SCH
STSR
TML
TRAU
TRM
TS
TSG
UA04
UE
UL
UMTS
UTRAN
VCC
Vci
Vpi
VLR
VPC
VPLMN
VPT
WCDMA
WGAN
XML
Remote Electrical Tilt Automatic

Radio Frequency
Radio Link Control
Radio Network Controller
Regional operation Center
Radio-Resource Control
Radio Resource Management
Received Signal Strength Indication.
Service Area Interface
Standalone AGPS SMLC
Service Mobile Center Location
Signaling Connection Control Part
Secondary Common Control Physical CHannel
UMTS Serving GPRS Support Node
Soft Handover
System Info Block
SG SS7/IP Gateway
Signal-to-Interference Ratio
Serving RNC
Drift RNC
Signaling System 7
Secondary Synchronization Channel
Sector Transmit Sector Receive
Terminal de Maintenance Locale (Local Maint. Term.)
Transcoder and Rate Adaptation Unit
Transceiver module
Time Slot
Technical Specification Group
UMTS Access Release 04
User Equipment
Uplink (Reverse Link)
Universal Mobile Telecommunications System
Universal Terrestrial Radio Access Network
Virtual Channel Connection
Virtual Channel Identifier
Virtual Path Identifier
Visitor Location Register
Virtual
Visited PLMN
Virtual
Wideband Code Division Multiple Access
Wireless Gateway Aggregation Node
EXtended Mark-up Language
Z END OF DOCUMENT Y
UMT/SYS/INF/10063
01.07/ EN
Standard
23/December/2005
Page 52 /52

8.2.5 UA04.0 Features Planning Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

8.2.5 UA04.0 Features Planning Guide

Uploaded by

Copyright:

Available Formats

UA04.

0 Access Network Feature Planning Guide

Copyright 2001-2003 Nortel Networks, All Rights Reserved

UA04.0 Access Network Feature Planning Guide

REFERENCE DOCUMENTS ....................................................................................................5

UA04.0 ACCESS OBJECTIVES .................................................................................................6

OBJECTIVES/KEY DRIVERS ...................................................................................................6

OPTIONAL SW PACKAGES ....................................................................................................7

UA04.0 FEATURES ....................................................................................................................8

ARCHITECTURE / PORTFOLIO / HW ......................................................................................8

UMTS BTS 12020, version 2 DC

DELTA FROM PREVIOUS EDITIONS ......................................................................................49

UA04.0 Access Network Feature Planning Guide

Performance and Capacity

Resources Management and Optimization

Dependencies (Hardware, Software, Feature, Inter-Working, Devices, and

Operational Requirements (Counters, Configuration

This document aims to focus on UA04.0 content.

UA04.0 Access Network Feature Planning Guide

NSS16/UMTS04 Circuit Core Network Feature Planning

Core Packet Feature Planning Guide

Preside for Wireless Internet, Feature Planning Guide

UA04.1 Access Network Feature Planning Guide

Location Services GPS based on UE positioning

UMTS radio mobility

UTRAN measurements and triggered

RRC states management

UTRAN Node B Upgrade

Nortel Networks RNC Capacity Roadmap

UA04.0 Access Network Feature Planning Guide

UA04.0 ACCESS OBJECTIVES

Stability, Quality and Operational Effectiveness

Effectiveness, easiness and reduced impacts of network operations in

Business Objective : Key content required to

UTRAN04 is split into two loads :

UA04.0 which brings stability improvement in 2004, needed base before

UA04.1 which supports new services and important enhancement in terms of

Enabling Revenue Generation

UA04.0 Access Network Feature Planning Guide

Performance improvement with Enhanced Compressed Mode Management

Operational Effectiveness with enhanced upgrade process, new counters and

Remote Electrical Tilt Automatic

RRC States - Step 4 (Always On and CELL_FACH

Network Assisted GPS for CS calls

UA04.0 Access Network Feature Planning Guide

UA04.0 Access Network Feature Planning Guide

PERFORMANCE AND CAPACITY

UA04.0 Access Network Feature Planning Guide

UA04.0 Access Network Feature Planning Guide

UA04.0 Access Network Feature Planning Guide

NETWORK ASSISTED GPS FOR CS CALLS

location of emergency calls (E911, E112, )

taxi reservation and dispatch

the UE is in Cell_DCH connected mode with a CS Radio Bearer assigned

the location request comes from the CS domain

the UE supports the UE-based A-GPS positioning method

About Network Assisted GPS :

takes a long time to compute a first fix

can be very power consuming, as it continuously monitors the satellite constellation

To dramatically improve the performance of the GPS, it is possible to provide the

UA04.0 Access Network Feature Planning Guide

Network Assisted GPS architecture:

UA04.0 Access Network Feature Planning Guide

Nortel Networks MLC for GSM-GPRS-UMTS