NN 20500 302

Proprietary Use pursuant to Company instruction
Title page
Alcatel-Lucent 9353
Wireless Management System | UA08.1
Activation of QChat (Push-to-Talk) over W-CDMA network
NN-20500-302
Issue 2.07 | January 2013
Alcatel-Lucent Internal
Legal notice
Legal notice
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective
owners.
The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.
Copyright 2013 Alcatel-Lucent. All rights reserved.
Contains proprietary/trade secret information which is the property of Alcatel-Lucent and must not be made available to, or copied or used by anyone outside
Alcatel-Lucent without its written authorization.
Not to be used or disclosed except in accordance with applicable agreements.
Trademarks
Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
Alcatel-Lucent Internal
Contents
About this document

Purpose ............................................................................................................................................................................................. ix
ix
Reason for reissue ........................................................................................................................................................................ ix

ix
New in this release ....................................................................................................................................................................... ix

ix
Intended audience ......................................................................................................................................................................... ix

ix
Supported systems ......................................................................................................................................................................... x

x
How to use this document ........................................................................................................................................................... xx
Prerequisites ..................................................................................................................................................................................... xx
Conventions used ........................................................................................................................................................................... x

x
Related information ..................................................................................................................................................................... xi

xi
Document support ........................................................................................................................................................................ xi

xi
Technical support .......................................................................................................................................................................... xi

xi
How to order ................................................................................................................................................................................. xii

xii
How to comment ......................................................................................................................................................................... xii

xii
1 Roadmap to Configuration Management documentation
Overview ...................................................................................................................................................................................... 1-1

1-1
Roadmap to Configuration Management documentation .......................................................................................... 1-2

1-2
2 QChat overview
Overview ...................................................................................................................................................................................... 2-1

2-1
QChat in UTRAN ..................................................................................................................................................................... 2-2

2-2
3 Qchat call setup
Overview ...................................................................................................................................................................................... 3-1

3-1
Initiating a QChat call ............................................................................................................................................................. 3-2

3-2
....................................................................................................................................................................................................................................
Alcatel-Lucent 9353 WMS Alcatel-Lucent Internal iii
NN-20500-302 UA08.1 Proprietary Use pursuant to Company instruction
Issue 2.07 January 2013
Contents
....................................................................................................................................................................................................................................
Terminating a QChat call ....................................................................................................................................................... 3-5
3-5
4 QChat Configuration Information
Overview ...................................................................................................................................................................................... 4-1

4-1
Configuration parameters at the UTRAN ....................................................................................................................... 4-2

4-2
5 Procedure preparation
Overview ...................................................................................................................................................................................... 5-1

5-1
Prerequisites ................................................................................................................................................................................ 5-2

5-2
Procedures ................................................................................................................................................................................... 5-3

5-3
6 QChat activation over W-CDMA access network
Overview ...................................................................................................................................................................................... 6-1

6-1
Activating QChat directly using WMS ............................................................................................................................. 6-2

6-2
Activating QChat using WPS and WMS ......................................................................................................................... 6-3

6-3
7 QChat activation procedures
Overview ...................................................................................................................................................................................... 7-1

7-1
Performing checks before QChat activation ................................................................................................................... 7-2

7-2
Activating QChat under WMS ............................................................................................................................................. 7-4

7-4
Performing reverse engineering ........................................................................................................................................ 7-11

7-11
Configuring QChat parameters in WPS ......................................................................................................................... 7-13

7-13
Exporting workorders online .............................................................................................................................................. 7-18

7-18
Exporting workorders offline ............................................................................................................................................. 7-20

7-20
Activating workorder in WMS .......................................................................................................................................... 7-22

7-22
Performing checks after QChat activation .................................................................................................................... 7-26

7-26
8 Reverse Procedure (Fallback method)
Overview ...................................................................................................................................................................................... 8-1

8-1
Performing reverse procedure with WPS Access workorder .................................................................................... 8-2

8-2
Index
....................................................................................................................................................................................................................................
iv Alcatel-Lucent Internal Alcatel-Lucent 9353 WMS
Proprietary Use pursuant to Company instruction NN-20500-302 UA08.1
List of tables
4-1 RadioAccessService ................................................................................................................................................. 4-2

4-2
4-2 QChatConfClass ........................................................................................................................................................ 4-4

4-4
4-3 QChatArpAttribute ................................................................................................................................................... 4-5

4-5
4-4 AlwaysOnConf ........................................................................................................................................................... 4-5

4-5
4-5 RabInactivity ............................................................................................................................................................... 4-6

4-6
4-6 PreemptionAllowedInfo .......................................................................................................................................... 4-7
4-7 UlRbSetConf ............................................................................................................................................................... 4-8

4-8
4-8 EdchParameters .......................................................................................................................................................... 4-8

4-8
4-9 ulRbList ......................................................................................................................................................................... 4-9

4-9
4-10 DlRbSetConf ............................................................................................................................................................... 4-9

4-9
4-11 dlRbList ...................................................................................................................................................................... 4-10

4-10
4-12 HsdpaUserService ................................................................................................................................................... 4-10

4-10
4-13 ulInnerLoopConf ..................................................................................................................................................... 4-10

4-10
4-14 FDDCell ...................................................................................................................................................................... 4-11

4-11
4-15 SCCPCH ..................................................................................................................................................................... 4-13

4-13
4-16 DxChConf .................................................................................................................................................................. 4-13

4-13
4-17 RACH .......................................................................................................................................................................... 4-13

4-13
4-18 RemoteFDDCell ...................................................................................................................................................... 4-14

4-14
4-19 NeighbouringRNC .................................................................................................................................................. 4-14

4-14
5-1 Activating QChat directly under WMS ............................................................................................................. 5-3
5-2 Activating QChat using WPS ................................................................................................................................ 5-3
7-1 Troubleshooting - Activate QChat under WMS ............................................................................................. 7-9
7-2 Activating workorder troubleshooting actions ............................................................................................. 7-24
....................................................................................................................................................................................................................................
Alcatel-Lucent 9353 WMS Alcatel-Lucent Internal v
List of tables
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
vi Alcatel-Lucent Internal Alcatel-Lucent 9353 WMS
List of figures
1-1 Roadmap to Configuration Management documentation ........................................................................... 1-3
3-1 Initiating a QChat call (UE in URA_PCH / Cell_PCH state) ................................................................... 3-2
....................................................................................................................................................................................................................................
Alcatel-Lucent 9353 WMS Alcatel-Lucent Internal vii
List of figures
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
viii Alcatel-Lucent Internal Alcatel-Lucent 9353 WMS
About this document
About this document
Purpose
The purpose of this document is to explain the activation of the QChat feature in
W-CDMA access network, emphasizing the configuration provisioning impact on the
UTRAN subsystem.
Reason for reissue

Reasons for reissue are:
Issue number Issue date Reason for reissue

2.07 January 2013 Standard issue
2.06 November 2012 Standard issue
2.05 October 2012 Standard issue
2.04 March 2012 Preliminary issue
2.03 September 2011 Preliminary issue
2.02 August 2011 Preliminary issue
2.01 June 2011 Draft issue
New in this release

New features:
None
Other changes:
References updated
Updated the roadmap.
Intended audience
The audience for this document is configuration management personnel.
...................................................................................................................................................................................................................................
Alcatel-Lucent 9353 WMS Alcatel-Lucent Internal ix
About this document
....................................................................................................................................................................................................................................
Supported systems
This document applies to Alcatel-Lucent W-CDMA UA08.1 system release.
This document covers the following systems:
NodeB
9370 RNC
QAS (QChat Application server)
WMS
How to use this document

Start with the first chapter and work through the manual to the end. Once you have
completed this activity, you will have carried out the feature activation procedure in the
proper sequence
Prerequisites
A good knowledge of UTRAN configuration principles as well as Microsoft Windows NT
4.0, Windows 2000 or Windows XP edition are required before reading this procedure.
It is also recommended that readers become familiar with the following documents:
Alcatel-Lucent 9370 RNC - Technical Description, NN-20500-021
Alcatel-Lucent 9353 Wireless Management System - User Guide, NN-20500-032
Alcatel-Lucent 9952 Wireless Provisioning System - User Guide, NN-20500-036
Alcatel-Lucent 9353 Wireless Management System Parameters Reference Guide,
NN-20500-027
Conventions used
Vocabulary conventions
None.
Typographical conventions
The following typographical conventions are used in this document:
Appearance Description
italicized text File and directory names
Emphasized information
graphical user interface text Text that is displayed in a graphical user interface or in
a hardware label
variable A value that the user supplies
key name The name of a key on the keyboard
....................................................................................................................................................................................................................................
x Alcatel-Lucent Internal Alcatel-Lucent 9353 WMS
About this document
....................................................................................................................................................................................................................................
Appearance Description
command-syntax Command names that the user types
input text Text that the user types or selects as input to a system
output text Text that a system displays or prints
IP reference, reference number Related document that is referenced in the document
Related information
For information on subjects related to the content of this document, refer to the
documents listed in the following table:
Refer to this document At this location For more

information on
Alcatel-Lucent 9353 Wireless http://support.alcatel- Using the
Management System - User Guide, lucent.com Alcatel-Lucent 9353
NN-20500-032 Wireless Management
System
Alcatel-Lucent 9370 RNC - Technical http://support.alcatel- Radio Network
Description, NN-20500-021 lucent.com Controller
Alcatel-Lucent 9353 Wireless http://support.alcatel- Configuration
Management System - Parameters lucent.com parameters for
Reference Guide, NN-20500-027 UTRAN.
Alcatel-Lucent 9952 Wireless http://support.alcatel- Using the
Provisioning System - User Guide, lucent.com Alcatel-Lucent 9952
NN-20500-036 Wireless Provisioning
System
Document support
For support in using this document or any other Alcatel-Lucent document, contact
Alcatel-Lucent at one of the following telephone numbers:
1-888-582-3688 (for the United States)
1-630-224-2485 (for all other countries)
Technical support
For technical support, contact your local Alcatel-Lucent customer support team. See the
Alcatel-Lucent Support web site (http://www.alcatel-lucent.com/support/) for contact
information.
....................................................................................................................................................................................................................................
Alcatel-Lucent 9353 WMS Alcatel-Lucent Internal xi
About this document
....................................................................................................................................................................................................................................
How to order
To order Alcatel-Lucent documents, contact your local sales representative or use Online
Customer Support (OLCS) (http://support.alcatel-lucent.com).
How to comment
To comment on this document, go to the Online Comment Form (http://infodoc.alcatel-
lucent.com/comments/) or e-mail your comments to the Comments Hotline
(comments@alcatel-lucent.com).
....................................................................................................................................................................................................................................
xii Alcatel-Lucent Internal Alcatel-Lucent 9353 WMS
1 1oadmap to Configuration
R
Management
documentation
Overview
Purpose
This chapter provides the roadmap for Configuration Management documentation.
Contents
Roadmap to Configuration Management documentation 1-2
...................................................................................................................................................................................................................................
Alcatel-Lucent 9353 WMS Alcatel-Lucent Internal 1-1
Roadmap to Configuration Management documentation Roadmap to Configuration Management documentation
....................................................................................................................................................................................................................................
Roadmap to Configuration Management documentation

Overall roadmap
For the roadmap relating to the full documentation collection, see:
Alcatel-Lucent W-CDMA System - Document Collection Overview, NN-20500-050
For the Access Network Management Overview, see:
Alcatel-Lucent W-CDMA System - Access Network Management Overview,
NN-20500-031
....................................................................................................................................................................................................................................
1-2 Alcatel-Lucent Internal Alcatel-Lucent 9353 WMS
....................................................................................................................................................................................................................................
Figure 1-1 Roadmap to Configuration Management documentation
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
2 QChat overview
2
Overview
Purpose
This chapter provides an overview of the QChat feature introduced in UTRAN. QChat
facilitates the mobile users (QChat users) to have an instantaneous group communication
using Voice over Internet Protocol (VoIP) service.
Contents
QChat in UTRAN 2-2
...................................................................................................................................................................................................................................
QChat overview QChat in UTRAN
....................................................................................................................................................................................................................................
QChat in UTRAN
QChat overview
QChat is an enhanced VoIP based communication service, which uses the W-CDMA
access network to communicate between two or more mobile stations. QChat requires
Quality of Service (QoS) support to manage the signalling and voice data traffic at the
various network components. QChat facilitates the users to communicate within virtual
groups, where the voice of a user is broadcast to number of listeners.
To use the QChat service, a QChat enabled UE is needed along with the support of QChat
in service provider's network. The UE (handset) should have the PTT (Push-to-Talk)
facility to initiate the QChat communication. A QChat call is initiated by pressing the
PTT button. Once the call is setup, the user can broadcast the voice to various other
QChat users.
An optimal Radio Bearer service is introduced to enhance the QChat service in W-CDMA
access network. This Radio Bearer service optimizes the network load and enables the UE
to switch from dormant state (CELL_PCH or URA_PCH) to active state (CELL_DCH).
QChat Operation
The QChat technology comprises of:
QChat Clients (running on the UE): The QChat Clients enable the users to initiate
and receive QChat voice calls.
QChat Application Server (QAS): The QAS manages all the operations required for
the QChat call setup and keeps a record of the QChat associated data.
QChat service can be activated only when the RNC and NodeB support the QChat
application for packet data service. This activity of enabling the QChat service on the
RNC and NodeB is done by the operator. QChat service requires a high speed data access,
so the users who opted for high QoS can utilize this facility.
RNC and NodeB identify the QChat supported UE from the QoS parameter called
Allocation/Retention Priority (ARP), configured for the UE, in the core network. This
parameter defines the priority level assigned for the QChat traffic in UTRAN sub-system.
The call originator presses the PTT button available on the UE to initiate a floor request
with the QAS (QChat Application Server).
Once the floor is granted to the call originator, the call originator can broadcast the voice
to the number of listeners. Eventually, If a listener wants to respond, the listener can press
the PTT button on the UE to get the floor. Once the floor is granted, the listener can
broadcast the voice.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
QChat enabled mobile equipment state
When the UE (QChat enabled) is switched on, it is connected to the network but is in idle
state. When the user initiates a call or a session, the UE switches to Cell_DCH state,
where a dedicated channel is allocated to the UE. During packet data transfer, there are
idle periods between the bursts of data traffic. When this idle period increases and crosses
the inactivity timer value, the UE moves to URA_PCH state, where it is still connected to
the network but no dedicated channels assigned to it. Sometimes, the UE moves to
Cell_FACH state, where it has no dedicated air interface but the communication can
happen through common channels.
Note: A QChat call can be initiated only when the UE is in Cell_PCH/URA_PCH
state.
Limitations
The limitations of the QChat service are as follows:
QChat is a delay sensitive service, as the delay occurs due to unavailability of
dedicated physical channel during network congestion.
QChat is a half duplex service. Unlike the full duplex service, where two separate
channels are provided to make or receive a call, half duplex service has only single
channel to make or receive a call. This limitation allows only a single QChat user to
transfer the voice data, at a time.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
3 Qchat call setup
3
Overview
Purpose
This chapter describes how a Qchat call is initiated and terminated between the Qchat call
originator and the QChat call receiver or number of QChat call receivers.
Contents
Initiating a QChat call 3-2

Terminating a QChat call 3-5
...................................................................................................................................................................................................................................
Qchat call setup Initiating a QChat call
....................................................................................................................................................................................................................................
Initiating a QChat call

Purpose
This topic describes the various steps involved in establishing a QChat session.
QChat call
The following figure shows an end-to-end QChat call connection with one QChat
originator and one QChat receiver.
Figure 3-1 Initiating a QChat call (UE in URA_PCH / Cell_PCH state)
When the QChat originator initiates a QChat call, the QChat UEs operate in one of the
following states: CELL_DCH, CELL_FACH, URA_PCH, or CELL_PCH. For more
information, seeQChat in UTRAN (p. 2-2)
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
The end-to-end signaling for the QChat call setup (URA_PCH or CELL_PCH state)
includes the following steps:
1. When the QChat originator presses the PTT button to initiate a QChat call, the UE in
URA_PCH or CELL_PCH state transitions to CELL_FACH state
2. The QChat UE (source) transmits the CellUpdate message to the source UTRAN
through RACH, and requests the source UTRAN to transition the UE to the
CELL_DCH state.
3. The source UTRAN transmits the CellUpdateConfirm message with
Post-verification period = TRUE, RRC state Indicator = CELL_DCH, the QChat
UE (source) performs the synchronization procedure using post verification period
and transitions to CELL_DCH state.
4. The QChat UE (source) transmits the CellUpdateConfirmResponse message to the
source UTRAN on the E-DCH to indicate the reconfiguration of the RBs.
5. Subsequently, the UE transmits the Call Request message on QChat RB#2 (mapped
with E-DCH) to the source UTRAN.
Note: CellUpdateConfimResponse is used to refer any of the following RRC
messages: RADIO BEARER RECONFIGURATION COMPLETE, TRANSPORT
CHANNEL RECONFIGURATION COMPLETE, or PHYSICAL CHANNEL
RECONFIGURATION COMPLETE that the QChat UE sends to the UTRAN ,based
on the IEs included in the CellUpdateConfirm message.
6. The source UTRAN forwards the Call Request message (received from the QChat
UE) over the Iub and QChat RAB#2 to the SGSN/GGSN. This activity occurs even if
the completion of dedicated physical channel setup at the UTRAN is in progress.
7. The SGSN/GGSN forwards the Call Request message to the QAS.
8. The QAS generates the Announce Call message, and transmits it through the core
network to the target UTRAN, serving the QChat UE (target).
9. The target UTRAN pages the QChat UE by sending PagingType1 message over the
PCH at the nearest paging DRX cycle.
10. The QChat UE demodulates the page and transitions to the CELL_FACH state to
respond to the page.
11. The QChat UE (target) transmits the CellUpdate message with Cell update cause
Paging Response to target UTRAN
12. The target UTRAN identifies that the paging is due to the DL data activity on QChat
RB#2 and transitions the UE directly into the CELL_DCH state through the
CellUpdateConfirm message.
Note: In CellUpdateConfirm message, Post-verification period = TRUE, RRC
state Indicator = CELL_DCH. Here, the QChat UE (target) performs the
synchronization procedure using post verification period and transitions to
CELL_DCH state.
13. The QChat UE (target) transmits the CellUpdateConfirmResponse message to the
target UTRAN.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
14. The target UTRAN transmits the Announce Call message on the HS-DSCH to QChat
UE (target).
15. The QChat UE (target) transmits the Accept Call message on the E-DCH to the target
UTRAN.
16. The target UTRAN forwards the Accept Call message to the QAS.
17. Once the Accept Call message is received from the target UTRAN, the QAS
generates the floor for the QChat UE (source) and forwards the Floor Grant message
to source SGSN/GGSN.
18. The SGSN/GGSN forwards the Floor Grant message to the QChat UE (source)
through source UTRAN.
19. A tone is played on the QChat UE (source) indicating that the QChat call is
established.
....................................................................................................................................................................................................................................
Qchat call setup Terminating a QChat call
....................................................................................................................................................................................................................................
Terminating a QChat call

Purpose
This topic describes the UTRAN configurations that occur automatically when the Qchat
call is terminated.
UTRAN reset during QChat call termination

A QChat call can terminate either from the originator end or from the receivers end. A
Qchat call drop can happen even due to number of reasons such as user equipment power
off, QAS disconnection, and so on. When the QChat call is established, a physical
dedicated channel is allocated to the QChat Originator to communicate with the n called
parties (Qchat call receivers). During QChat call termination, the UTRAN releases the
dedicated physical channel resources allocated for the QChat call originator based on
inactive state of the dedicated physical channel. The idea behind releasing the dedicated
physical channel is to increase the efficiency of the Qchat feature and to facilitate
availability of physical channel for the other QChat users.
....................................................................................................................................................................................................................................
Qchat call setup Terminating a QChat call
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
4 4 Chat Configuration
Q
Information
Overview
Purpose
This chapter describes the configuration objects and parameters related to QChat
application.
Contents
Configuration parameters at the UTRAN 4-2
...................................................................................................................................................................................................................................
QChat Configuration Information Configuration parameters at the UTRAN
....................................................................................................................................................................................................................................
Configuration parameters at the UTRAN

UTRAN Objects and parameters involved
QChat service
The involved objects are:
RadioAccessService
Table 4-1 RadioAccessService
Parameter Class Description Setting

Name
Location: RNC <RNC Name> > RadioAccessService
isQChatAllowed 3-A2 Allow the QChat activation TRUE
Next at RNC level
HSPA/
Qchat call
establish-
ment
isMpdpExtend- 3 This parameter is used to TRUE
edRabCombsAl- enable/disable the sub feature
lowed code for supporting extended
RAB combinations with
MPDP feature 34170. This
feature includes: All
combinations with three PDP
contexts, All combinations
with 2, 3 x HS/32,8, 384kbps
UL, All combinations with
CS Speech + 1, 2 x 64kbps
I/B + Streaming, and All
combinations with 3x0/0
isThreeRa- 3 This parameter is used to TRUE
bAllowed enable/disable MPDP feature
34170 code, and it
determines whether three I/B
RABs or two I/B + one
Streaming RABs are allowed
to be set up.
isGbrOnHsd- 3 To allow OA controllable TRUE
paAllowed activation/deactivation of the
feature 29804 "GBR on
HSDPA"
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Table 4-1 RadioAccessService (continued)

Name
isSr- 3 Activation flag for support of TRUE
bOverHspaEn- SRB on HSxPA
abled
isSrbOnEdchAl- 3 Enable the possibility to map TRUE
lowedWhenTr- SRB on E-DCH in the UL for
bOnEdch Cat 6 UE, while the call is
handling RAB(s) over
E-DCH
isSrbOnEdch- 3 SRB on E-DCH for all TRUE
ForAllEdchCat- E-DCH categories. FALSE:
egory E-DCH cat 6 UE only.
TRUE: All E-DCH
categories.
ForAllMinSf NodeB minSF .FALSE: 2
SF2 + 2 SF4 minSF only.
TRUE: All NodeB minSF
ForAllEdchTti E-DCH TTI. FALSE: 2 ms
TTI only and 2 ms supported
on NodeB. TRUE: 2 ms and
10 ms allowed.
isSr- 3 Activation flag for support of TRUE
bOverHspaEn- SRB on HSxPA with PS I/B
abledForPsIb Rab
pchRrcStates 3 Definition of RRC states CellPchEnabled
usage
supportEstab- 3 Activation flag for support of TRUE
CauseAndTraf- estab cause and Traffic
ficVolInd Volume indicator.
isUlRbRateAd- 3 Indicates if the feature uplink FALSE
aptationAllowed RB rate adaptation is
allowed. This parameter is
used to activate / de-activate
the UL RB adaptation" on
an RNC basis.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Table 4-1 RadioAccessService (continued)

Name
isDlRbRateAd- 3 Indicates if the feature FALSE
aptationAllowed downlink RB rate adaptation
is allowed. This parameter is
used to activate / de-activate
the DL RB adaptation" on
an RNC basis.
QChatConfClass
Table 4-2 QChatConfClass

Name
Location: RNC <RNC Name> > RadioAccessService > QChatConfClass
minBR 3-A2 The minimum bit rate set for Engineering value, up to field
Qchat service. optimization
Default 8 kbps
Integer [0..2048] in kbps
QChatDorman- 3-A2 QChatDormancyTimer for Engineering value, up to field
cyTimer The event QChat RAB. optimization
is "taken Integer [1..3600] in seconds,
into Default value: 5 seconds
account on
next
measure-
ment.
utranDrxCy- 3-A2 Qchat UTRAN DRX cycle Engineering value, up to field
cLngCoef It is taken length coefficient. optimization
into UTRAN DRX cycle length K= 5, 320 ms default
account on = 2^ UtranDrxCynLngCoef
next expressed in 10 ms radio
transition frames
to
CELL_
PCH or
URA_
PCH
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
QChatArpAttribute
Table 4-3 QChatArpAttribute

Name
Location: RNC <RNC Name> > RadioAccessService > QChatConfClass >
QChatArpAttribute
priorityLevel 3-A2 This attribute provides the Engineering value, up to field
Next RAB allocation/retention optimization
HSPA/ priority for QChat call. Integer [1..15]
QChat call Highest Priority 1 is the
establish- default value.
ment
preemptionVul- 3-A2 PreemptionVulnerability: Need to match the Core
nerability Next enum {Vulnerability of the Network Configuration.
HSPA/ service;
QChat call enum: not_preemptable(0),
establish- preemptable(1)}
ment
preemptionCa- 3-A2 QChat preemptionCapabil- Need to match the Core
pability Next ity: enum {shall not trigger Network Configuration.
HSPA/ preemption, may trigger
QChat call preemption}
establish-
ment
queuingAl- 3-A2 This parameter indicates TRUE
lowed Next whether the request can be Core Network configuration
HSPA/ placed into a resource should match this setting.
QChat call allocation queue or not (that
establish- is Queuing of the RAB is
ment allowed).
AlwaysOnConf
Table 4-4 AlwaysOnConf

Name
Location: RNC <RNC Name> > RadioAccessService > AlwaysOnConf
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Table 4-4 AlwaysOnConf (continued)

Name
mpdpInactivityI- 3 This parameter is used when FALSE
uRelease the UE has multiple I/B PS
RABs present (Without
streaming) to determine
whether the RNC releases a
RAB after a period of
releaseTimerMpdpChannel-
Type on the RAB (FALSE),
or whether it releases the
whole Iu based upon
inactivity on all of the RABs
(TRUE). In addition,
parameter
releaseTimerMpdpChannel-
Type describes the behavior
when it is set to FALSE, and
parameter timer T2 describes
the behavior when this is set
to TRUE.
isAlwaysOnAl- 3-A2 This parameter determines TRUE
lowedForSigIn- the behavior of each PS I/B
dOnRab Radio Bearer when the
always on signaling is
triggered.
RabInactivity
Table 4-5 RabInactivity

Name
Location: RNC <RNC Name> > RadioAccessService > AlwaysOnConf > AlwaysOnTimer >
RabInactivity
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Table 4-5 RabInactivity (continued)

Name
releaseTimerM- 3 This parameter is the RAB less than QChatDormancy-
pdpHsdpaAnd- inactivity time applied when Timer value.
Dch multiple I/B RABs exist to Recommended value is 1s.
release a RAB. Upon
detection of inactivity, the
RNC requests the release of
the inactive RAB. A setting
of 0 means that the timer is
disabled. There is one
specific value for each of the
OLS levels (Gold, Silver,
Bronze), and in case there
are multiple RABs mapped
with different OLS, the timer
for the most stringent OLS is
used. This inactivity timer is
applied when the UE is
mapped onto HSDPA/DCH
channel. A setting of 0
means that the timer is
disabled. There is one
specific value for each of the
OLS levels (Gold, Silver,
Bronze), and in case there
are multiple RABs mapped
with different OLS, the timer
for the most stringent OLS is
used. This inactivity timer is
applied when the UE is
mapped onto HSDPA/DCH
channel.
PreemptionAllowedInfo
Table 4-6 PreemptionAllowedInfo

Name
Location: RNC <RNC Name> > RadioAccessService > PreemptionAllowedInfo
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Table 4-6 PreemptionAllowedInfo (continued)

Name
isPreemption- 3 Activate/deactivate TRUE
Allowed preemption process for DCH
and HSDPA/HSUPA
UlRbSetConf
Table 4-7 UlRbSetConf

Name
Location: RNC <RNC Name> > RadioAccessService > UlRbSetConf
isAlwaysOnAl- Class 3-A2 This parameter is used to Degraded2AlwaysOnOnly
lowed activate/de-activate the
Always On features. It is
available for each uplink
Radio Bearer configuration.
The possible values are:
Disabled
Degraded2AlwaysOnOnly
ReleaseOnly
EdchParameters
Table 4-8 EdchParameters

Name
Location: RNC <RNC Name> > RadioAccessService > UlRbSetConf > PS_EDCH >
EdchParameters
iubEdchDe- 3-A2 The optional Iub delay jitter Engineering value, up to field
layJitterBud- budget for delay-sensitive optimization
get type of services. This is 0...50ms
introduced by voice over
HSPA.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
ulRbList
Table 4-9 ulRbList

Name
Location: RNC <RNC Name> > RadioAccessService > UlRbSetConf > ulRbList
UlRbPduSi- 3 UL RB PDU size. For each 336
zeList RB of the RBSet.
DlRbSetConf
Table 4-10 DlRbSetConf

Name
Location: RNC <RNC Name> > RadioAccessService > DlRbSetConf
isAlwaysOnAl- Class 3-A2 This parameter is used to Degraded2AlwaysOnOnly
lowed activate/de-activate the
Always On features. It is
available for each downlink
Radio Bearer configuration.
The possible values are:
Disabled
Degraded2AlwaysOnOnly:
downgrade to
CELL_FACH is
allowed; further
downgrade to PCH and
release to idle mode is
allowed.
ReleaseOnly: downgrade
to CELL_FACH it not
allowed; further
downgrade to PCH and
release to idle mode is
allowed.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
dlRbList
Table 4-11 dlRbList

Name
Location: RNC <RNC Name> > RadioAccessService > DlRbSetConf > dlRbList
dlRbPduSi- 3 DL RB PDU size. For each Default value is 656 bit.
zeList RB of the RBSet.
HsdpaUserService
Table 4-12 HsdpaUserService

Name
Location: RNC <RNC Name> > RadioAccessService > DlRbSetConf > PS_QChat_
HSDSCH > HsdpaUserService
timerT1 3 Used by the NodeB to stop the Recommended value is 50ms.
re-transmission of the
corresponding MAC-hs PDU.
discardTimer 3 This parameter defines the Recommended value is 80ms.
time to live for a MAC-hs
SDU starting from the instant
of its arrival into an HSDPA
Priority Queue.The NodeB
shall use this information to
discard out-of-data MAC-hs
SDUs from the HSDPA
Priority Queues.
macHsWin- 3 This parameter provides the Recommended value is 32 ms.
dowSize duration of the CQI feedback
cycle.
ulInnerLoopConf
Table 4-13 ulInnerLoopConf

Name
Location: RNC <RNC Name> > RadioAccessService > DedicatedConf > PowerCtrlConf-
Class > ulInnerLoopConf
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Table 4-13 ulInnerLoopConf (continued)

Name
dpcchPower- 3 TS 25.331. DPCCH Power Engineering value, up to field
Offset offset this quantity corrected optimization
by CPICH RSCP corresponds
to the initial power used by
the UE for the initial
transmission of the DPCCH.
pcPreamble 3 TS 25.331. PC Preamble 4
Number of power control
preamble frames. PC
Preamble is absent in
HANDOVER TO UTRAN
COMMAND. Otherwise, it is
present. It precise the number
of power control preamble
slots, which the UE must be
used for the initial
transmission of the DPCCH.
srbDelay 3 TS 25.331. After the 0
establishment of the uplink
physical channel, the mobile
must not send any data on
signaling radio bearers RB0 to
RB4 during the number of
frames indicated in the IE
"SRB delay". It is given in
number of frames.
FDDCell
Table 4-14 FDDCell
Parameter Name Class Description Setting

Location: RNC <RNC Name> > NodeB <NodeB Name> > FDDCell
isQChatAllowed 3-A2 Allow the QChat activation on TRUE
FDDCell for Packet Switched (PS)
network.
isHsdpaCellHighPerfor- 3-A2 Allows the use of PDU size 656 bits TRUE
mance on this cell for HSDPA
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Table 4-14 FDDCell (continued)
Parameter Name Class Description Setting

MaxNumberOfVoiceH- 3-A2 Maximum amount of voice over Engineering
spaUsers HSPA users per cell. value, up to
field
optimization
isDlPowerSelfTuning- 3 Allows RNC to send MAC-hs GBR TRUE
ForPsIbOnHsdpaEnabled (based on minBR configurable value)
to the drift RNC in order to activate
the Dl Power self-tuning for PS I/B
RAB on HSDPA
2 Allows ability to share resources (DL
isHsxpaR99ResourcesSharingOnCellAllowed TRUE
power, OVSF codes) between
HS-DSCH and R99 calls in this cell.
Allows the RNC to itself determine
the sharing or resources in certain
situations.
powerCtrlConfId 3 Identifier of the powerCtrlConfclass Engineering
instance value, up to
field
optimization
maxTxPower 3 TS 25.433. Maximum transmission Engineering
power for all downlink channels value, up to
added together allowed on the cell on field
average, applied to the local cell optimization
Power. MaxTxPower must
imperatively be smaller than
MaxDlPowerCapability which is
calculated and given by the NodeB
through the message NBAP
Resource Status Indication, where
MaxDlPowerCapabilmity=
PaRatio*MaxPowerAmplification +
Tx Losses such as DDM Tx losses,
Tx Splitter losses, and so on.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
SCCPCH
Table 4-15 SCCPCH

Name
Location: RNC <RNC Name> > NodeB <NodeB Name> > FDDCell > SCCPCH/1
sccpchClassId 2 The sccpchClassId is either 3 RadioAccessService/0
(without CBS support) or 5 SccpchClass/3
(with CBS support) depending
on the network configuration.
DxChConf
Table 4-16 DxChConf

Name
Location: RNC <RNC Name> > RadioAccessService > SccpchClass/3 > DxChConf/3
cmChPIused 0 This parameter (if set to TRUE
True), indicates that the
fachClassId provisioned for
this instance of DxChConf
must be taken into account
by the Mac-D.
RACH
Table 4-17 RACH

Name
Location: RNC <RNC Name> > NodeB <NodeB Name> > FDDCell > RACH
constantValue 3 TS 25.331. This constant Engineering value, up to field
value is used by the UE to optimization
calculate the initial output
power on PRACH according
to the Open loop power
control procedure.
powerOffsetPO 3 TS 25.331. Power step when Engineering value, up to field
no acquisition indicator is optimization
received in dB
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
RemoteFDDCell
Table 4-18 RemoteFDDCell

Name
Location: RNC <RNC Name> > UmtsNeighbouring > RemoteFDDCell
isQChatAl- 3-A2 Allow the QChat activation on TRUE
lowed Neighboring cell FDD Cell for
Packet Switched (PS)
network.
NeighbouringRNC
Table 4-19 NeighbouringRNC

Name
Location: RNC <RNC Name> > UmtsNeighbouring > NeighbouringRNC
isQChatAl- 3-A2 Allow QChat mode on this Iur TRUE
lowed link (either as serving RNC or
as drift RNC).
....................................................................................................................................................................................................................................
5 Procedure preparation
5
Overview
Purpose
This chapter describes the procedures and preparation required to activate QChat in
UTRAN.
Contents
Prerequisites 5-2
Procedures 5-3
...................................................................................................................................................................................................................................
Procedure preparation Prerequisites
....................................................................................................................................................................................................................................
Prerequisites
Purpose
This topic provides the prerequisites for activating QChat in UTRAN.
Overview
Always ON
The Iu-PS signaling connection, QChat RAB#2, and, QChat RB#2 must be in Always
ON state, even after the QChat call termination. During QChat call termination, the
dedicated physical channel allocated to the QChat originator is released. This state is
called as data inactivity state. In order to achieve an efficient QChat service, it is required
to have Iu-PS signaling connection, QChat RAB#2, and, QChat RB#2 in Always ON
state during data inactivity state so as to accommodate other QChat sessions. This enables
the PS core network and UTRAN to continuously support the QChat service and avoids
the re-activation of QChat for every consecutive call.
RRC Connected mode
The Iu-PS signaling connection, QChat RAB#2, and, QChat RB#2 for QChat UEs must
always be in RRC Connected mode from the UTRAN end.
Note: Even without RRC Connected mode, the Iu-PS signaling connection can be
maintained from UTRAN but to provide an efficient QChat service, it is always
required to make the dedicated physical channel resources available for the QChat
users. To achieve this physical channel availability, the RRC Connected mode is
recommended.
User Equipment
User Equipment for test must be QChat enabled with a PTT button to initiate the QChat
call.
....................................................................................................................................................................................................................................
Procedure preparation Procedures
....................................................................................................................................................................................................................................
Procedures
Purpose
This topic provides an overview of the procedures required to activate Qchat over
W-CDMA access network.
The activation performed under WMS requires the WMS to be properly configured with
the operator's network. If the conditions for WMS configuration with operator's network
are not fulfilled, then the activation cannot be properly done under WMS.
Overview
The QChat service can be activated using WPS and WMS. QChat activation directly
under WMS is recommended for a small set of cells.
Table 5-1 Activating QChat directly under WMS
Step Feature
1 Performing checks before QChat activation
2 Activating QChat under WMS
3 Performing checks after QChat activation
Table 5-2 Activating QChat using WPS
Step Feature
1 Performing Reverse Engineering
2 Configuring QChat parameters in WPS
3 Exporting Workorders Online / Exporting Workorders Offline
4 Performing checks before QChat activation
5 Activating Workorder in WMS
6 Performing checks after QChat activation
....................................................................................................................................................................................................................................
Procedure preparation Procedures
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
6 6 Chat activation over
Q
W-CDMA access network
Overview
Purpose
This chapter describes how to activate QChat in W-CDMA access network.
Contents
Activating QChat directly using WMS 6-2

Activating QChat using WPS and WMS 6-3
...................................................................................................................................................................................................................................
QChat activation over W-CDMA access network Activating QChat directly using WMS
....................................................................................................................................................................................................................................
Activating QChat directly using WMS

Purpose
This topic describes the procedure to activate QChat directly using WMS.
Prerequisite
For QChat activation, all the RNCs and NodeBs must be of UA08.1 release.
Procedure
...................................................................................................................................................................................................
1 Perform the required checks before activating QChat over W-CDMA access network, see
Performing checks before QChat activation (p. 7-2).
...................................................................................................................................................................................................
2 Activate QChat under WMS, see Activating QChat under WMS (p. 7-4).
...................................................................................................................................................................................................
3 Perform the required checks after activating QChat over W-CDMA access network, see
Performing checks after QChat activation (p. 7-26).
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
QChat activation over W-CDMA access network Activating QChat using WPS and WMS
....................................................................................................................................................................................................................................
Activating QChat using WPS and WMS

Purpose
This topic describes the procedure to configure QChat using WPS tool and activate the
generated workorder using WMS.
Prerequisite
For QChat activation, all the RNCs and NodeBs must be of UA08.1 release.
Procedure
...................................................................................................................................................................................................
1 (Optional) Perform a reverse Engineering, see Performing reverse engineering

(p. 7-11).
...................................................................................................................................................................................................
2 Configure the QChat parameters under WPS Access, see Configuring QChat parameters
in WPS (p. 7-13).
...................................................................................................................................................................................................
3 Export workorders, see Exporting workorders online (p. 7-18) or Exporting

workorders offline (p. 7-20).
...................................................................................................................................................................................................
4 Perform checks before QChat activation, see Performing checks before QChat
activation (p. 7-2).
...................................................................................................................................................................................................
5 Activate workorder in WMS, see Activating workorder in WMS (p. 7-22).

...................................................................................................................................................................................................
6 Perform checks after QChat activation, see Performing checks after QChat activation
(p. 7-26).
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
QChat activation over W-CDMA access network Activating QChat using WPS and WMS
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
7 7 Chat activation
Q
procedures
Overview
Purpose
This chapter lists all the procedures required for QChat activation over W-CDMA access
network.
Contents
Performing checks before QChat activation 7-2

Activating QChat under WMS 7-4
Performing reverse engineering 7-11
Configuring QChat parameters in WPS 7-13
Exporting workorders online 7-18
Exporting workorders offline 7-20
Activating workorder in WMS 7-22
Performing checks after QChat activation 7-26
...................................................................................................................................................................................................................................
QChat activation procedures Performing checks before QChat activation
....................................................................................................................................................................................................................................
Performing checks before QChat activation

Purpose
This topic describes the checks that need to be performed before activating QChat in
UTRAN.
Use this procedure to verify that:
the Network and the OMC are up and running without any problems (alarm, OMC
MIB state, synchronization state, and so on),
the QAS should be up and normal.
data transfer can be achieved on the impacted RNC and NodeB.
This procedure has to be repeated for each impacted RNC.
This procedure is a recommendation and is not mandatory if all the states given by the
checks described above are well known.
Procedure
...................................................................................................................................................................................................
1 Check that no impacting alarms exist. For more information on analyzing alarms, refer to
the section Analyzing alarms and faults in Alcatel-Lucent 9353 Wireless Management
System - User Guide, (NN-20500-032).
...................................................................................................................................................................................................
2 Check the OMC MIB states (semantic checks, synchronization states, and so on).
Especially check the OMC MIB states on the impacted RNC(s), see Alcatel-Lucent 9353
Wireless Management System - User Guide, (NN-20500-032).
...................................................................................................................................................................................................
3 Perform an audit of the impacted RNC(s), see "Auditing a MIB" procedure in

Alcatel-Lucent 9353 Management System documentation - User Guide, (NN-20500-032).
...................................................................................................................................................................................................
4 Check that the Iu-PS interface between the impacted RNC and the core network is
normal. Perform the data transfer on the impacted RNC to verify if the Iu-PS interface is
normal.
...................................................................................................................................................................................................
5 Check the IuB interface between UTRAN and QAS to ensure if QAS is normal and
accepting the data traffic from UTRAN.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
QChat activation procedures Performing checks before QChat activation
....................................................................................................................................................................................................................................
Final status
The Network and the OMC are up and running without any problems (alarm, OMC MIB
state, synchronization state, and so on). The impacted RNC(s) and NodeB(s) are up and
running, and the QAS is up and normal.
....................................................................................................................................................................................................................................
QChat activation procedures Activating QChat under WMS
....................................................................................................................................................................................................................................
Activating QChat under WMS

Purpose
The procedure details how to proceed with WMS to set the parameters that activate the
QChat service.
This procedure can be divided into 3 steps:
Configuration flag settings - Step 1 to 14
Session Creation - Step 15
Node Validation - Step 16
Activation status check - Step 17
Input parameters
All Design parameters regarding the QChat service need to be provided to the Application
Engineer by the Network Designers, i.e.
RNC(s) and NodeBs on which the QChat has to be activated
The QAS to be enabled
Note: It is recommended to keep the initial values in case reverse steps are required.
Initial status
The WMS runs the actual (initial) configuration.
The activation performed directly at the WMS Graphical interface requires the WMS to
be configured with the operator's network. If the conditions for the WMS configuration
with operator's network are not fulfilled, then the activation cannot be properly done
under WMS.
Step duration
It takes a few seconds per "Set On-line" command.
Impact on service
None
Procedure
...................................................................................................................................................................................................
1 Launch the WMS application and select the appropriate Network Layout
...................................................................................................................................................................................................
2 Select the RNC <RNC Name> on which QChat is to be activated.

....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
3 From the Configuration menu, select Equipment Monitor.

...................................................................................................................................................................................................
4 In the Object Tree view; right-click RadioAccessService object, and select Configuration
> Object Editor.
...................................................................................................................................................................................................
5 In RadioAccessService set :
isQChatAllowed to TRUE.
...................................................................................................................................................................................................
6 Configure SRB#1 over HSPA with fixed RB PDU size.

In the Object Tree view, under RadioAccessService;
1. Right-click UlRbSetConf object, and select Configuration > Object Editor.
2. In UlRbSetConf:
Select rlcConfClass > ulRlcUMode and set the configuration flag
isAlternativeEbitAllowed to false.
3. Right-click dlRbSetConf object, and select Configuration > Object Editor.
4. In dlRbSetConf:
Select rlcConfClass > dlRlcUMode and set the configuration flag
isAlternativeEbitAllowed to false.
...................................................................................................................................................................................................
7 Configure QCHAT RB#2 with fixed RB PDU size.

In the Object Tree view; right-click RadioAccessService object, and select Configuration
> Object Editor:
Set the configuration flag isUlRbRateAdaptationAllowed to FALSE.
Set the configuration flag isDlRbRateAdaptationAllowed to FALSE.
In the Object Tree view, under RadioAccessService;
1. Right-click UlRbSetConf object, and select Configuration > Object Editor.
2. In UlRbSetConf:
Select ulRbList, and set the configuration flag UlRbPduSizeList to 336.
3. Right-click dlRbSetConf object, and select Configuration > Object Editor.
4. In dlRbSetConf:
Select dlRbList, and set the configuration flag DlRbPduSizeList to 656.
...................................................................................................................................................................................................
8 Allow individual RAB release for QCHAT RAB#1.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
In the Object Tree view;
1. Right-click RadioAccessService object, and select Configuration > Object Editor.
2. In RadioAccessService:
Set the configuration flag isMpdpExtendedRabCombsAllowed to TRUE.
Set the configuration flag isThreeRabAllowed to TRUE.
Select AlwaysOnConf and set the configuration flag mpdpInactivityIuRelease to
FALSE.
Select AlwaysOnConf > AlwaysOnTimer > RabInactivity, and set the
configuration flag releaseTimerMpdpHsdpaAndDch to less than
QChatDormancyTimer value.
The parameter releaseTimerMpdpHsdpaAndDch has one specific value for
each of the OLS levels (Gold, Silver, Bronze). In case there are multiple RABs
mapped with different OLS, the timer for the most stringent OLS is used. This
inactivity timer is applied when the UE is mapped onto HSDPA/DCH channel.
...................................................................................................................................................................................................
9 Set the cell state transition parameters for Cell_PCH state to Cell_DCH state transition.
Note: Ensure that the Post Verification Period is set to TRUE in the impacted RNC.
1. In the Object Tree view, navigate to RadioAccessService > DedicatedConf >
PowerCtrlConfClass > ulInnerLoopConf.
Right-click ulInnerLoopConf and select Configuration > Object Editor
Set the configuration flag dpcchPowerOffset to <the Engineering value based on
field optimization>. This configuration flag setting depends on the field
optimization to accommodate both QCHAT and non-QCHAT UE.
Set the configuration flag pcPreamble to 4.
Set the configuration flag srbDelay to 0.
2. Select the impacted NodeB <NodeB Name> from the Equipment Monitor and
perform the following:
a. In the Object Tree view, right-click FDDCell object, and select Configuration >
Object Editor
b. Set the configuration flag powerCtrlConfId to <the Engineering value based on
field optimization>
...................................................................................................................................................................................................
10 Configure the SCCPCH channel parameters for defining the SCPCCH class.
Select the impacted NodeB <NodeB Name> from the Equipment Monitor and perform
the following:
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1. Select FddCell > SCCPCH/1 .
2. Right-click SCCPCH/1 and select Configuration > Object Editor, and perform the
following:
Set the configuration flag sccpchClassId to RadioAccessService/0 SccpchClass/3.
The sccpchClassId would be either RadioAccessService/0 SccpchClass/3 (without
CBS support) or RadioAccessService/0 SccpchClass/5 (with CBS support)
depending on the network configuration.
...................................................................................................................................................................................................
11 Add CMCH-PI 3 for QCHAT RB#2 to allocate a higher priority over conventional PS I/B
for the QChat traffic (particularly the signalling traffic on the RAB #2).
1. Select RadioAccessService/0 > SccpchClass/3 > DxChConf/3
Note: The SccpchClass (SccpchClass/3) is the one defined in Step 10 for
sccpchClassId. If SccpchClass/5 is defined for sccpchClassId, then SccpchClass/5
needs to be selected.
2. Right-click DxChConf/3 object, and select Configuration > Object Editor.
3. Set the configuration flag cmChPIused to True.
...................................................................................................................................................................................................
12 Configure the RACH channel parameters to enable UE to send CellUpdateMessage in

time.
Select the impacted NodeB <NodeB Name> from the Equipment Monitor and perform
the following:
1. Navigate to FddCell > RACH .
2. Right-click RACH and selectConfiguration > Object Editor, and perform the
following:
Set the config flag constantValue to <the Engineering value based on field
optimization>. This configuration flag is set to balance the UL Interference
measured by NodeB and the path loss reported by the UE . The UL interfence is
sent in SIB 7 periodically.
Set the config flag powerOffsetPO to <the Engineering value based on field
optimization>. This configuration flag is set to reduce the number of RACH
pre-ambles.
Set the config flag maxTxPower to <the Engineering value based on field
optimization>. This configuration flag is set to match the cells power capability.
MaxTxPower(Cell) = min { maxTxPower; MaxDlPowerCapability reported by
NodeB}
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
13 Configure the default configuration parameters which are required as a part of QChat
activation in UTRAN.
1. Right-click FddCell object, and select Configuration > Object Editor.
2. In FddCell:
Set the configuration flag isHsxpaR99ResourcesSharingOnCellAllowed to TRUE.
Set the configuration flag isDlPowerSelfTuningForPsIbOnHsdpaEnabled to
TRUE.
Set the configuration flag isHsdpaCellHighPerformance to TRUE.
3. Right-click RadioAccessService object, and select Configuration > Object Editor.
4. In RadioAccessService:
Set the configuration flag isGbrOnHsdpaAllowed to TRUE.
Select preemptionAllowedInfo, and set the configuration flag isPreemptionAl-
lowed to TRUE.
Set the configuration flag isSrbOnEdchAllowedWhenTrbOnEdch to TRUE.
Set the configuration flag isSrbOnEdchForAllEdchCategory to TRUE.
Set the configuration flag isSrbOnEdchForAllMinSf to TRUE.
Set the configuration flag isSrbOnEdchForAllEdchTti to TRUE.
Set the configuration flag isSrbOverHspaEnabled to TRUE.
Set the configuration flag isSrbOverHspaEnabledForPsIb to TRUE.
Set the configuration flag pchRrcStates to CellPchEnabled.This configuration
flag must not be selected as none.
Set the configuration flag supportEstabCauseAndTrafficVolInd to TRUE.
Select AlwaysOnConf, and set the configuration flag isAlwaysOnAllowedForSig-
IndOnRab to TRUE.
...................................................................................................................................................................................................
14 Check if all the configuration changes (as performed in the above steps) are saved in
WMS.
In the Object Editor:
Select Show: Changes Only in order to view all the modifications.
Select Apply type: Offline
Click Apply All Changes
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
15 Automatically the Activation Session manager is opened with a session named <session
name>, which consists of a workorder containing all the changes performed through the
Object Editor.
...................................................................................................................................................................................................
16 In the Sessions Manager window:

Click Summary for <session name> and check the status of the nodes: RNC nodes
should be in "validated" state.
Check the validation report of each node in the summary section:
Click Summary for <session name>; select an RNC in the table, and click the
hyperlink to display the HTML validation report.
...................................................................................................................................................................................................
17 In the Actions for <session name> tab, click Activation:

Select all the impacted RNC(s), and click Launch
When all tasks are completed, click Summary for <session name> to check that all
nodes are activated
Result: QChat service is activated in UTRAN.
E...................................................................................................................................................................................................
N D O F S T E P S
Troubleshooting
Table 7-1 Troubleshooting - Activate QChat under WMS
Failed Node Status Action

Step
Step 1 to N.A In case of errors in setting parameters, return to same step and
Step 14 re-apply the configuration settings.
Step 15 "Excluded" In case of errors in session creation, analyze logs or contact your
local support or Network Designers. Abort then terminate the
session and return to step 1.
Step 16 "Validation In case of errors in session validation, analyze logs or contact your
Failed" local support or Network Designers, Abort then terminate the
session and return to step 1.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Table 7-1 Troubleshooting - Activate QChat under WMS (continued)
Failed Node Status Action

Step
Step 17 "Activation In the Command Manager window, check the status of impacted
Partly RNCs:
realized" If the Status is Completed with errors:
Fallback ALL the RNC C-Nodes (see document [R9]).
Check the Fallback status:
If the Fallback is completed : Terminate the session
If the Fallback failed: Abort then terminate the session and
restore the initial configuration.
Final status
At this step, the desired QChat service is activated in the UTRAN for the RNCs specified
in the input list.
....................................................................................................................................................................................................................................
QChat activation procedures Performing reverse engineering
....................................................................................................................................................................................................................................
Performing reverse engineering

Purpose
The purpose of this procedure is to import an up-to-date view of the network
configuration into WPS workspace.
Once the CM XML export is performed, no online modifications can take place on the
target NE(s) until the end of the overall procedure. This ensures that the initial view, on
which the procedure is based, is synchronous with the Main server MIB.
This is an optional, but recommended procedure. You can bypass it, if you are sure that
your WPS Access view is synchronized with the network. In this case, go directly to
Activating QChat using WPS and WMS (p. 6-3) procedure.
Input parameters
None
Initial status
WPS and WMS are installed and ready to be used. The template files are uploaded in
WPS.
Duration
The procedure duration depends on the number of NEs available on the network.
For a network with 7 RNCs, 860 NodeBs, and 2540 cells, step duration is as follows:
Step 1: less than 20 minutes
Step 2 to step 4: less than 10 minutes
Impact on service
None
Procedure
...................................................................................................................................................................................................
1 Export the XML file that describes the network from the Main server (Global UTRAN
export). If required, transfer the file to the appropriate user data directory.
....................................................................................................................................................................................................................................
QChat activation procedures Performing reverse engineering
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Under WPS:
1. Open a new Workspace, see "Opening a workspace" procedure in Alcatel-Lucent 9952
Provisioning System - User Guide, (NN-20500-036).
2. From the File menu, launch Import and Export..., and perform the following steps:
a. Select Import Snapshot (form the Local file system / Live server repository) and
click Next.
b. Select Replace initial snapshot and discard existing workorders, and click
Next.
c. Click Browse local (if the snapshot is on the local file system) or Browse
repository (to import the snapshot directly from the live server (WMS)).
d. Select the CM XML file exported in Step 1, and click Open.
e. Click Next.
f. If a part of the snapshot needs to be excluded, click Edit Filter... ; choose Objects
to import; and then click Next, otherwise click Next directly.
g. Select No, proceed without saving (cancel available), and click Start.
...................................................................................................................................................................................................
3 After import completion, check the report and close it.

...................................................................................................................................................................................................
4 Save your Workspace, see "Saving a workspace" procedure in Alcatel-Lucent 9952

Provisioning System - User Guide, (NN-20500-036).
E...................................................................................................................................................................................................
N D O F S T E P S
Final status
A workspace is available with an initial snapshot, which describes the current network.
Troubleshooting
Stop the global procedure and redo this procedure.
....................................................................................................................................................................................................................................
QChat activation procedures Configuring QChat parameters in WPS
....................................................................................................................................................................................................................................
Configuring QChat parameters in WPS

Purpose
This procedure details how to proceed with WPS Access to set QChat related parameters
for an RNC.
Input parameters
The network designers must provide all design parameters regarding the QChat to the
application engineer:
The FDD cells on which the QChat must be enabled.
The recommended values of all the parameters related to the QChat activation (see
Configuration parameters at the UTRAN (p. 4-2)).
Initial status
The Network runs in a configuration in which the QChat is not yet activated for all the
FDD cells in the input list.
Under WPS Access, a Workspace is opened with an initial snapshot, which describes your
current network.
Duration
The procedure duration depends on the number of FDD cells on which the QChat must be
activated:
About 1 minute for 3 FDD cells.
About 5 minutes for 332 FDD cells.
Impact on service
None
Procedure
...................................................................................................................................................................................................
1 From WPS Access, create a new workorder (if needed) and rename it (for example:
"QChat Activation on RNC <RNC Name>"). For information on how to create a
workorder, see Alcatel-Lucent 9952 Wireless Provisioning System - User Guide,
NN-20500-036.
...................................................................................................................................................................................................
2 Set the parameters of RadioAccessService managed object and the associated child
objects.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
In the Network tree:
Select the RNC/<RNC name> on which QChat is to be activated
Set the parameters to the expected or recommended value as described in
Configuration parameters at the UTRAN (p. 4-2) section. See Table 4-1,
RadioAccessService (p. 4-2) to Table 4-13, ulInnerLoopConf (p. 4-10).
...................................................................................................................................................................................................
3 Create a dataset containing all the NodeBs on which QChat is to be activated.

In the Network tree:
1. Select all the NodeBs of the input list.
2. Right click Add to dataset, and select New dataset.
3. Enter a new dataset name (for example: QChatNodeB), and click OK.
...................................................................................................................................................................................................
4 Create a dataset containing all the FDDCells on which QChat is to be activated and
configure the FDDCell parameters.
In the Datasets tree, select the dataset containing the NodeBs (QChatNodeB) and
perform the following steps:
1. In the Dataset Conversion tab:
a. In Navigators, select [Generic] Children
b. In Outputs type, select RNC/NodeB/FDDCell [*/RNC]
c. In Output dataset, type a new dataset name (for example: QChatFDDCell)
d. Click Apply
e. Close the report window
2. Remove the unexpected FDDCells from the dataset (QChatFDDCell) so as to retain
only the required FDDCells on which the QChat feature is to be activated.
In the Datasets tree, select the dataset containing the FDDCells (QChatFDDCell)
and perform the following steps.
a. Select all the FDDCells which are not in the input list (the FDDCells on which the
feature must not be activated)
b. Right-click Remove From Dataset, and click Yes
3. Select the generated Dataset (QChatFDDCell) containing the FDDCells of the Input
list:
a. Select an FDDCell.
b. In the Edition tab, set the parameters to the expected or recommended value as
described in Table 4-14, FDDCell (p. 4-11).
c. Repeat step a and step b for all the FDDCells of the input list
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
5 Create a dataset containing all the SCCPCH parameters and set the SCCPCH/3
parameters.
1. In the Datasets tree, select the dataset containing the FDDCells (QChatFDDCell)
b. In Outputs type, select RNC/NodeB/FDDCell/SCCPCH[*/RNC]
c. In Output dataset, type a new dataset name (for example: QChatSCCPCH)
d. Click Apply
3. In the Dataset tree, select the dataset (QChatSCCPCH) containing the SCCPCH
object:
a. Select the SCCPCH/3 object .
b. In the Edition tab, set all the parameter of SCCPCH/3 object to the expected value
or the recommended value as described in Table 4-15, SCCPCH (p. 4-13).
...................................................................................................................................................................................................
6 Set the CMCH-PI parameter to the recommended value as described in Table 4-16,
DxChConf (p. 4-13).
...................................................................................................................................................................................................
7 Create a dataset containing all the RACH parameters and set the RACH parameters.
1. In the Datasets tree, select the dataset containing the FDDCells (QChatFDDCell)
b. In Outputs type, select RNC/NodeB/FDDCell/RACH[*/RNC]
c. In Output dataset, type a new dataset name (for example: QChatRACH)
d. Click Apply
3. In the Dataset tree, select the dataset (QChatRACH) containing the RACH object:
a. Select the RACH object .
b. In the Edition tab, set all the parameters of RACH object to the expected value or
the recommended value as described in Table 4-17, RACH (p. 4-13).
...................................................................................................................................................................................................
8 Create a dataset containing all the RemoteFDDCells on which QChat is to be activated

and configure the RemoteFDDCell parameters..
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
In the Network tree
1. Select all the RemoteFDDCells of the input list.
3. Enter a new dataset name (for example: QChatRemoteFDDCell), and click OK.
4. Select the generated Dataset (QChatRemoteFDDCell) containing the
RemoteFDDCells of the Input list:
a. Select a RemoteFDDCell.
described in .Table 4-18, RemoteFDDCell (p. 4-14).
c. Repeat step a and step b for all the RemoteFDDCells of the input list
...................................................................................................................................................................................................
9 Create a dataset containing all the NeighbouringRNCs on which QChat is to be activated

and configure the NeighbouringRNCs parameters..
In the Network tree
1. Select all the NeighbouringRNCs of the input list.
3. Enter a new dataset name (for example: QChatNeighbouringRNCs), and click OK.
4. Select the generated Dataset (QChatNeighbouringRNCs) containing the
NeighbouringRNCs of the Input list:
a. Select a NeighbouringRNC.
described in Table 4-19, NeighbouringRNC (p. 4-14).
c. Repeat step a and step b for all the NeighbouringRNCs of the input list
...................................................................................................................................................................................................
10 Launch checks. For information on how to launch checks, see Alcatel-Lucent 9952
Wireless Provisioning System - User Guide, NN-20500-036.
...................................................................................................................................................................................................
11 Check that no errors appear in the status window.

...................................................................................................................................................................................................
12 Save your Workspace. For information on how to save your workspace, see
Alcatel-Lucent 9952 Wireless Provisioning System - User Guide, NN-20500-036.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Final status
The QChat is configured on all of the NodeBs from the input list.
The workorder is error-free and the final configuration is error-free.
Troubleshooting
In case of errors, contact your local engineering representative and correct errors or delete
the workorder and redo this procedure.
....................................................................................................................................................................................................................................
QChat activation procedures Exporting workorders online
....................................................................................................................................................................................................................................
Exporting workorders online

Purpose
This procedure details how to generate the workorder (CM XML) file, which describes
only the modified NEs in comparison with your current network configuration.
This procedure facilitates speeding up the whole process, by exporting only the relevant
applicable modifications on the Main Server.
With this online procedure, you need to be able to connect to WMS. If you want to export
workorders offline, see Exporting workorders offline (p. 7-20).
Input parameters
None
Initial status
All the parameters, used to activate the QChat, are set under WPS Access in a Workspace
by an error-free workorder based on an initial snapshot representing the current view of
your network.
Impact on service
None
Procedure
...................................................................................................................................................................................................
1 Under WPS, from the Workorders tab, right-click the workorders folder and select Merge
Network Changes.
...................................................................................................................................................................................................
2 Iin the Workorders folder, right-click the Merge workorder, and select Export workorder
-> on live server repository.
Result: The Export workorder '<workorder name>' (Live server repository)
window appears.
...................................................................................................................................................................................................
3 In the Export workorder '<workorder name>' (Live server repository), click define
repository.
....................................................................................................................................................................................................................................
QChat activation procedures Exporting workorders online
....................................................................................................................................................................................................................................
Result: The Transfer Connection Parameters window appears.
...................................................................................................................................................................................................
4 In the Transfer Connection Parameters window, enter the repository information and
click Connect.
Result: The message "Status: This value is correct" appears.
You are connected to WMS.
...................................................................................................................................................................................................
5 Click Close.
Result: The Transfer Connection Parameters window closes.
...................................................................................................................................................................................................
6 In the Export workorder '<workorder name>' (Live server repository) window, select
the appropriate directory from the list of directories displayed; enter the workorder name
in the Filename field, and click OK.
Result: The <filename>-<sub-network name>.xwo and <filename>-<sub-network
name>_reverse.xwo workorder files are saved in the selected directory on WMS.
E...................................................................................................................................................................................................
N D O F S T E P S
Final status
The selected directory contains the workorder (CM XML) file, named <filename>-<sub-
network name>.xwo, which describes only the modified NEs between the initial and the
final network configuration.
This file is used for the activation. If the reverse procedure needs to be applied, the file
named <filename>-<sub-network name>_reverse.xwo available in the selected directory
is used.
Troubleshooting
In case of trouble during generation of workorder file redo this procedure.
....................................................................................................................................................................................................................................
QChat activation procedures Exporting workorders offline
....................................................................................................................................................................................................................................
Exporting workorders offline

Purpose
This procedure details how to generate the workorder (CM XML) file, which describes
only the modified NEs in comparison with your current network configuration.
This procedure facilitates speeding up the whole process, by exporting only the relevant
applicable modifications on the Main Server.
With this offline procedure, you do not need to be connected to WMS. You store the
modifications locally. You will need to transfer the workorder to WMS repository to
perform theActivating workorder in WMS (p. 7-22) procedure.
With this online procedure, you need to be able to connect to WMS. If you want to export
workorders online, see Exporting workorders online (p. 7-18).
Input parameters
None
Initial status
All the parameters, used to activate the QChat, are set under WPS Access in a Workspace
by an error-free workorder based on an initial snapshot representing the current view of
your network.
Impact on service
None
Procedure
...................................................................................................................................................................................................
1 Under WPS, from the Workorders menu, select Merge Network Changes.
...................................................................................................................................................................................................
2 Right-click the Merge workorder, and select Export workorder -> on local file system.
Result: The Select an output directory window appears.
...................................................................................................................................................................................................
3 In the Select an output directory window, select a local folder to place the workorder
files.
...................................................................................................................................................................................................
4 Click Select.
....................................................................................................................................................................................................................................
QChat activation procedures Exporting workorders offline
....................................................................................................................................................................................................................................
Result: The Select filename for workorder files window appears.
...................................................................................................................................................................................................
5 Enter the filename and click OK.

Result: The on local file system... window appears.
...................................................................................................................................................................................................
6 If the operations have to be tracked, click Save report... and save it in a proper folder.
...................................................................................................................................................................................................
7 Click Close.
Result: The on local file system... window is closed. The <filename>-<sub-network
name>.xwo and <filename>-<sub-network name>_reverse.xwo workorder files are
saved locally.
E...................................................................................................................................................................................................
N D O F S T E P S
Final status
The local folder contains the workorder (CM XML) file named <filename>-<sub-
network name>.xwo, which describes only the modified NE between the initial and the
final network configuration. Later, this file is used for the activation of those procedures.
So, this file must be transferred to a WMS repository.
If the reverse procedure needs to be applied, the file used is the one named
<filename>-<sub-network name>_reverse.xwo..
Troubleshooting
In case of trouble during generation of workorder file redo this procedure.
....................................................................................................................................................................................................................................
QChat activation procedures Activating workorder in WMS
....................................................................................................................................................................................................................................
Activating workorder in WMS

Purpose
Use this procedure to activate the workorder for all the impacted RNCs with WMS.
Input parameters
The workorder file <filename>-<sub-network name>.xwo generated by WPS Access is
in the result main server directory.
When you performed the Exporting workorders online (p. 7-18) / Exporting
workorders offline (p. 7-20)
on live server repository, the <filename>-<sub-network name>.xwo is already in the
result main server directory.
on local file system, you must transfer the <filename>-<sub-network name>.xwo to
the result main server directory.
Initial status
state, synchronization state, etc.).
All the workorder files (<filename>-<sub-network name>.xwo and <filename>-<sub-
network name>_reverse.xwo) generated by WPS Access have been transferred to a
/<Result_folder>/ main server directory as described in Alcatel-Lucent 9353 Wireless
Management System - Configuration Management, NN-20500-169.
Duration
Procedure duration: about 5 minutes for 3 FDD cells.
Impact on service
During activation, impacted FDD cells are locked then unlocked.
Reminder: The load per cell (increased noise level) decreases the capacity of
communication for the mobiles.
Procedure
...................................................................................................................................................................................................
1 From the WMS client menu bar, select Configuration -> Sessions Manager.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Result: The Sessions Manager window appears.
...................................................................................................................................................................................................
2 From the Sessions Manager window, either:

in Session Tasks pane, click Create new session, or
in Available Sessions pane, right-click Sessions list and select New.
Result: The Create Session window appears.
...................................................................................................................................................................................................
3 In the Create Session window - Creation parameters pane, enter a <Session Name>.
...................................................................................................................................................................................................
4 From the Create Session window - Workorder(s) Selection pane, in the

cmXML/<Result_folder> folder, select the workorder file <filename>-<sub-network
name>.xwo you want to activate.
...................................................................................................................................................................................................
5 Click Add to list.

Result: The Workorder is added in the right pane.
...................................................................................................................................................................................................
6 Click Next to list the impacted nodes.

Result:
The Create Session window - Excluded Nodes pane appears and details, for each
impacted node, activation details and impacted objects.
Select the node(s) to be excluded, if needed.
...................................................................................................................................................................................................
7 Click Launch.
Result: The Create Session window closes and the details of the created session are
displayed in the Sessions Manager window.
...................................................................................................................................................................................................
8 From the Sessions Manager window - session <session name> pane, click Summary for
<session name> and check the status of the nodes.
Result: RNC node(s) must be in "validated" state
...................................................................................................................................................................................................
9 Check the validation report of each node, in the Summary for <session name>:
Select an RNC in the table and click the here hyperlink to display the HTML
Validate Report.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
10 From the Sessions Manager window - session <session name> pane, click Actions for
<session name>.
...................................................................................................................................................................................................
11 Click Activation.
...................................................................................................................................................................................................
12 Select all the impacted RNC(s) and click Launch.

...................................................................................................................................................................................................
13 When all tasks are completed, check in the Summary for <session name> pane that all
nodes are activated.
E...................................................................................................................................................................................................
N D O F S T E P S
Final status
The QChat is data-filled at the OMC and activated for the RNC ( for the specified
NodeBs in the input list).
Troubleshooting
All commands are logged in the Command Manager, see Alcatel-Lucent 9353 Wireless
Management System - User Guide, (NN-20500-032).
Table 7-2 Activating workorder troubleshooting actions
Failed Node status Action

step
7 "Excluded" In case of errors in session creation:
1. Analyze logs or contact your local support or Network
Designers to correct the XML file.
2. Abort the session.
3. Terminate the session.
4. Go back to Step 1.
9 "Validation Failed" In case of errors in session validation:
1. Analyze logs or contact your local support or Network
Designers to correct the XML file.
2. Abort the session.
3. Terminate the session.
4. Go back to Step 1.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Table 7-2 Activating workorder troubleshooting actions (continued)
Failed Node status Action

step
13 "Activation In the Command Manager window check the Status of
partly impacted RNC(s):
realized" If the Status is "Completed with errors":

1. Fallback all the RNC(s), see Alcatel-Lucent 9353 Wireless
2. If the Fallback is completed:
Terminate the session.
If the Fallback is failed:
Terminate the session.
Abort the session.
Go to reverse procedure listed in Chapter 8, Reverse
Procedure (Fallback method)to restore the initial
configuration.
....................................................................................................................................................................................................................................
QChat activation procedures Performing checks after QChat activation
....................................................................................................................................................................................................................................
Performing checks after QChat activation

Purpose
This topic describes the checks that need to be performed after activating QChat in
UTRAN.
Use this procedure to verify that:
The Network and the OMC are up and running without any problems (alarm, OMC
MIB state, synchronization state, and so on).
The QChat service is activated.
This procedure has to be repeated for each impacted RNC.
This procedure is a recommendation and is not mandatory if all the states given by the
checks described above are well known.
Procedure
...................................................................................................................................................................................................
1 Check that no impacting alarms exist. For more information on analyzing the alarms,
refer to the section Analyzing alarms and faults in Alcatel-Lucent 9353 Wireless
...................................................................................................................................................................................................
2 Check the OMC MIB states (semantic checks, synchronization states, and so on).
Especially check the OMC MIB states on the impacted RNC(s), see Alcatel-Lucent 9353
Wireless Management System - User Guide, (NN-20500-032).
...................................................................................................................................................................................................
3 Measure the noise generated in absence of any calls on cells for which the QChat service
has been activated.
...................................................................................................................................................................................................
4 Check if the dedicated physical channel for QChat Service is available for the Qchat
originator. To perform this, verify that the QAS is normal and the Iub interface between
UTRAN and QAS is active.
E...................................................................................................................................................................................................
N D O F S T E P S
Final status
state, synchronization state, etc.).
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
The impacted RNC(s) and NodeB(s) are up and running.
The QChat service is activated.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
8 8everse Procedure
R
(Fallback method)
Overview
Purpose
This chapter describes the fallback procedure to obtain initial WMS configuration. The
initial WMS configuration is the configuration settings available in WMS prior
configuring QChat service.
Contents
Performing reverse procedure with WPS Access workorder 8-2
...................................................................................................................................................................................................................................
Reverse Procedure (Fallback method) Performing reverse procedure with WPS Access workorder
....................................................................................................................................................................................................................................
Performing reverse procedure with WPS Access workorder

Purpose
The procedure details how to restore the initial WMS configuration. The initial WMS
configuration is the configuration settings available in WMS prior configuring QChat
service.
Input parameters
The workorder file <filename>-<sub-network name>_reverse.xwo generated by WPS
Access is in the result main server directory.
When you performed the Exporting workorders online (p. 7-18) / Exporting
workorders offline (p. 7-20)
on live server repository, the <filename>-<sub-network name>_reverse.xwo is
already in the result main server directory.
on local file system, you must transfer the <filename>-<sub-network
name>_reverse.xwo to the result main server directory.
Initial status
The QChat service is configured under WMS and is activated in UTRAN.
The fallback performed directly at the WMS Graphical interface requires the WMS to be
configured with the operator's network. If the conditions for the WMS configuration with
operator's network are not fulfilled, then the fallback cannot be properly done under
WMS.
Step duration
It takes a few seconds per "Set On-line" command.
Impact on service
None
Procedure
...................................................................................................................................................................................................
1 From the WMS client menu bar, select Configuration -> Sessions Manager.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Result: The Sessions Manager window appears.
...................................................................................................................................................................................................
2 From the Sessions Manager window, either:

in Session Tasks pane, click Create new session, or
in Available Sessions pane, right-click Sessions list and select New.
Result: The Create Session window appears.
...................................................................................................................................................................................................
3 In the Create Session window - Creation parameters pane, enter a <reverse session
name>.
...................................................................................................................................................................................................
4 From the Create Session window - Workorder(s) Selection pane, in the

cmXML/<Result_folder> folder, select the reverse workorder file <filename>-<sub-
network name>_reverse.xwo you want to activate.
...................................................................................................................................................................................................
5 Click Add to list.

Result: The reverse workorder is added in the right pane.
...................................................................................................................................................................................................
6 Click Next to list the impacted nodes.

Result: The Create Session window - Excluded Nodes pane appears and details, for
each impacted node, activation details and impacted objects.
...................................................................................................................................................................................................
7 Click Launch.
Result: The Create Session window closes and the details of the created session are
displayed in the Sessions Manager window.
...................................................................................................................................................................................................
8 From the Sessions Manager window - session <reverse session name> pane, click
Summary for <reverse session name> and check the status of the nodes.
Result: RNC node(s) must be in "validated" state
...................................................................................................................................................................................................
9 Check the validation report of each node, in the Summary for <reverse session name>:
1. Select the impacted RNC in the table.
2. Click the here hyperlink to display the HTML Validate Report.
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
10 From the Sessions Manager window - session <reverse session name> pane, click
Actions for <reverse session name>.
...................................................................................................................................................................................................
11 Click Activation.
...................................................................................................................................................................................................
12 Select all the impacted RNC(s) and click Launch.

...................................................................................................................................................................................................
13 When all tasks are completed, check in the Summary for <reverse session name> pane
that all nodes are activated.
E...................................................................................................................................................................................................
N D O F S T E P S
Final status
The QChat service is de-activated in the UTRAN for the RNCs specified in the input list.
....................................................................................................................................................................................................................................
Index
A activate QChat procedure, 7-13 .............................................................
post-checks, 7-26 ............................................................. F FDDCell

pre-checks, 7-2 D dlRbList parameters, 4-11
activate workorder in WMS, 7-22 parameters, 4-10 .............................................................
input parameters, 7-22 DlRbSetConf H how to comment, xii
troubleshoot, 7-24 parameters, 4-9 how to order, xii
activating QChat, 7-4 document HsdpaUserService
activating QChat directly under how to use, x parameters, 4-10
WMS, 5-3
references, xi .............................................................
activating QChat using WMS
revision history, ix
prerequisites, 6-2 I initiating a QChat call
document support, xi
procedure, 6-2 QChat service, 3-2
documentation roadmap, 1-2
activating QChat using WPS, 5-3 input parameters
DxChConf
prerequisites, 6-3 activate workorder in WMS,
parameters, 4-13 7-22
procedure, 6-3
............................................................. configuring QChat parameters
additional information, xi in WPS, 7-13
E EdchParameters
Always ON, 5-2 QChat, 7-4
parameters, 4-8
AlwaysOnConf QChat Fallback, 8-2
export workorders offline
parameters, 4-5 intended audience, ix
procedure, 7-20
............................................................. .............................................................
troubleshoot, 7-21
C configure QChat parameters in N NeighbouringRNC
WPS export workorders online
parameters, 4-14
troubleshoot, 7-17 procedure, 7-18
new in this release, ix
configuring QChat parameters in troubleshoot, 7-19
WPS
input parameters, 7-13
....................................................................................................................................................................................................................................
Alcatel-Lucent 9353 WMS Alcatel-Lucent Internal IN-1
Index
....................................................................................................................................................................................................................................
............................................................. prerequisites for user equipment, reason for revision, ix
5-2
O objects related information, xi
.............................................................
QChat service, 4-2 RemoteFDDCell
Q QChat parameters, 4-14
UTRAN, 4-2
activating, 7-4 reverse engineering
.............................................................
activating QChat directly under procedure, 7-11
P parameters
WMS, 5-3
troubleshoot, 7-12
AlwaysOnConf, 4-5 activating QChat using WPS,
5-3 roadmap
dlRbList, 4-10
input parameters, 7-4 documentation, 1-2
DlRbSetConf, 4-9
objects and parameters, 4-2 RRC Connected mode, 5-2
DxChConf, 4-13
.............................................................
EdchParameters, 4-8 Performing reverse procedure,
8-2 S SCCPCH
FDDCell, 4-11
troubleshoot, 7-9 parameters, 4-13
HsdpaUserService, 4-10
QChat activation procedures, 5-3
NeighbouringRNC, 4-14 supported systems, x
QChat Fallback .............................................................
PreemptionAllowedInfo, 4-7
input parameters, 8-2
QChat service, 4-2 T technical support, xi
QChat in UTRAN
QChatArpAttribute, 4-5 terminating a QChat call, 3-5
limitations, 2-3
QChatConfClass, 4-4 troubleshoot QChat, 7-9
QChat enabled mobile
RabInactivity, 4-6 equipment state, 2-3 troubleshoot QChat activation,
7-17
RACH, 4-13 QChat Operation, 2-2
troubleshoot reverse engineering,
RadioAccessService, 4-2 QChat service, 2-2 7-12
RemoteFDDCell, 4-14
QChat prerequisites, 5-2 troubleshoot workorder activation
SCCPCH, 4-13 in WMS, 7-24
QChatArpAttribute
ulInnerLoopConf, 4-10 troubleshoot workorder export,
parameters, 4-5
7-19, 7-21
ulRbList, 4-9
QChatConfClass
.............................................................
UlRbSetConf, 4-8
parameters, 4-4
UTRAN, 4-2 U ulInnerLoopConf
.............................................................
Performing reverse procedure, 8-2 parameters, 4-10
R RabInactivity
PreemptionAllowedInfo ulRbList
parameters, 4-6
parameters, 4-7 parameters, 4-9
RACH
prerequisite knowledge, x UlRbSetConf
parameters, 4-13
prerequisites for QChat, 5-2, 5-2, parameters, 4-8
5-2 RadioAccessService
user equipment prerequisites, 5-2
parameters, 4-2
....................................................................................................................................................................................................................................
IN-2 Alcatel-Lucent Internal Alcatel-Lucent 9353 WMS
Index
....................................................................................................................................................................................................................................
UTRAN
objects and parameters, 4-2
.............................................................
W WMS
activate workorder, 7-22

workorders
export offline, 7-20
export online, 7-18
....................................................................................................................................................................................................................................
Alcatel-Lucent 9353 WMS Alcatel-Lucent Internal IN-3
Index
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
IN-4 Alcatel-Lucent Internal Alcatel-Lucent 9353 WMS

NN 20500 302

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

NN 20500 302

Enviado por

Direitos autorais:

Formatos disponíveis

Proprietary Use pursuant to Company instruction

About this document

Reason for reissue ........................................................................................................................................................................ ix

New in this release ....................................................................................................................................................................... ix

Intended audience ......................................................................................................................................................................... ix

Supported systems ......................................................................................................................................................................... x

How to use this document ........................................................................................................................................................... xx

Conventions used ........................................................................................................................................................................... x

Related information ..................................................................................................................................................................... xi

Document support ........................................................................................................................................................................ xi

Technical support .......................................................................................................................................................................... xi

How to order ................................................................................................................................................................................. xii

How to comment ......................................................................................................................................................................... xii

1 Roadmap to Configuration Management documentation

Overview ...................................................................................................................................................................................... 1-1

Roadmap to Configuration Management documentation .......................................................................................... 1-2

Overview ...................................................................................................................................................................................... 2-1

QChat in UTRAN ..................................................................................................................................................................... 2-2

3 Qchat call setup

Overview ...................................................................................................................................................................................... 3-1

Initiating a QChat call ............................................................................................................................................................. 3-2

4 QChat Configuration Information

Overview ...................................................................................................................................................................................... 4-1

Configuration parameters at the UTRAN ....................................................................................................................... 4-2

Overview ...................................................................................................................................................................................... 5-1

Prerequisites ................................................................................................................................................................................ 5-2

Procedures ................................................................................................................................................................................... 5-3

6 QChat activation over W-CDMA access network

Overview ...................................................................................................................................................................................... 6-1

Activating QChat directly using WMS ............................................................................................................................. 6-2

Activating QChat using WPS and WMS ......................................................................................................................... 6-3

7 QChat activation procedures

Overview ...................................................................................................................................................................................... 7-1

Performing checks before QChat activation ................................................................................................................... 7-2

Activating QChat under WMS ............................................................................................................................................. 7-4

Performing reverse engineering ........................................................................................................................................ 7-11

Configuring QChat parameters in WPS ......................................................................................................................... 7-13

Exporting workorders online .............................................................................................................................................. 7-18

Exporting workorders offline ............................................................................................................................................. 7-20

Activating workorder in WMS .......................................................................................................................................... 7-22

Performing checks after QChat activation .................................................................................................................... 7-26

8 Reverse Procedure (Fallback method)

Overview ...................................................................................................................................................................................... 8-1

Performing reverse procedure with WPS Access workorder .................................................................................... 8-2

4-1 RadioAccessService ................................................................................................................................................. 4-2

4-2 QChatConfClass ........................................................................................................................................................ 4-4

4-3 QChatArpAttribute ................................................................................................................................................... 4-5

4-4 AlwaysOnConf ........................................................................................................................................................... 4-5

4-5 RabInactivity ............................................................................................................................................................... 4-6

4-6 PreemptionAllowedInfo .......................................................................................................................................... 4-7

4-7 UlRbSetConf ............................................................................................................................................................... 4-8

4-8 EdchParameters .......................................................................................................................................................... 4-8

4-9 ulRbList ......................................................................................................................................................................... 4-9

4-10 DlRbSetConf ............................................................................................................................................................... 4-9

4-11 dlRbList ...................................................................................................................................................................... 4-10

4-12 HsdpaUserService ................................................................................................................................................... 4-10

4-13 ulInnerLoopConf ..................................................................................................................................................... 4-10

4-14 FDDCell ...................................................................................................................................................................... 4-11

4-15 SCCPCH ..................................................................................................................................................................... 4-13

4-16 DxChConf .................................................................................................................................................................. 4-13

4-17 RACH .......................................................................................................................................................................... 4-13

4-18 RemoteFDDCell ...................................................................................................................................................... 4-14

4-19 NeighbouringRNC .................................................................................................................................................. 4-14