Training Document WRAN13.0 BSC6900 (V900R013C00) PTT Feature Description-20110212-A-1.0

Security Level: Internal Use
WRAN13.0 BSC6900
(V900R013C00) PTT Feature
Description
Global Technical Support
Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.
www.huawei.com
Objectives
Upon completion of this course, you will be able to:
List the characteristics of the push to talk (PTT) feature.
Know how to configure (or enable) and verify the PTT feature.
Know the basic principles of the PTT feature.
Page2
Objectives
Upon completion of this course, you will be able to:
List the counters of the PTT feature.
Explain the design and implementation method of the PTT

feature.
Configure (or enable) and verify the PTT feature.
Know the impacts on the system (counters) and precautions

after the PTT feature is enabled.
Page3
About This Course
This course is based on RAN13. Before learning this

course, you should have lsned the following courses of
RAN12:
EFACH
PTT
Page4
Contents
1. Purpose and Application Scenarios of the PTT Feature
2. Principles and Implementation Method of the PTT
Feature
3. Hardware and Data Planning of the PTT Feature
4. Configuration and Commissioning of the PTT Feature
(Important)
5. References of the PTT Feature
Page5
Principle Overview
PTT allows a user to communicate immediately with one or

multiple users by pressing one key. PTT is similar to the
walkie-talkie service. The basic characteristics are as follows:
PTT uses half duplex mode. A user can connect calls simply
by pressing one key without dialing numbers.
The concept of PTT is derived form the walkie-talkie service.
The user experience of PTT is similar to that of the walkietalkie service, that is, simple and convenient communication
in half duplex mode.
Page6
Purpose
The available PTT solutions are Poc defined in third generation partnership project
(3GPP) and Qualcomm's proprietary solution Qchat PTT. Currently, Huawei adopts
Qchat PTT.
QChat is a voice over IP (VoIP) application and a half duplex dispatch call service
based on UTRA-FDD.
The characteristics of PTT are as follows:
In a dispatch call, one user speaks, and one or multiple users listen. This type of
single-instance communication is called the dispatch call service.
After presetting a call group, a user can speak to all the other members in the group
after pressing a specified key without dialing numbers.
Once the key is pressed, the user can speak. Call connection is complete
instantaneously.
Receivers can hear the speaker without any response.
The contract requires that a call between PTT users must be connected to a delay of
shorter than 1.4 seconds.
Page7
Functions of the NEs for PTT

Implementation
QChat UE: uses the initialized dispatch service and receives

QChat voices.
QAS: implements call control, OAM, and charging, and

sends QChat voice data to the group members in the QChat
service.
WCDMA: maintains IP sessions.
Page8
Principles of the PTT Feature

(PTT Service Bearer)
The PTT service bearer type and HSUPA TTI can be configured
independently.
Run the following commands:
SET UFRCCHLTYPEPARA: PTTChlType=HSPA;
SET UFRC: PTTHsupaTti=EDCH_TTI_2ms;
Page9

(PTT
WCDMA
The wideband
code divisionProcedure)
multiple access (WCDMA) procedure is the main
PTT service registration procedure. This RAB is not used for PTT identification
but used to bear the PTT registration procedure in the user plane.
SRBs establish
RAB#1 PDP#1
RB#1establish
Page10

(PTT WCDMA Procedure)
Set up service RAB#2. This RAB is used for PTT user identification and PTT service establishment, and the user is transited to the PCH state.
This step requires

UTRAN to distinguish
Qchat User from QoS
profile request and set
corresponding
parameter for Qchat
User QChat-specific
RAB#2 PDP#2
RB#2 establish
UTRAN DRX cycle
RAB#1 PDP#1
RB#1delete
RAB#2 PDP#2
RB#2 SRB reserve
Page11
The user state is

changed only after the
Qchat service is
activated or another
service is established.

(PTT
Procedure)
A user WCDMA
initiates a Qchat
call.
Fast L1
synchronization
procedure
PostVerificationPeriod = TRUE ,
RRC state Indicator = CELL_DCH
,
RADIO BEARER
RECONFIGURATION COMPLETE
Page12

(PTT
WCDMA
Procedure)
A user receives
a Qchat
paging.
Fast L1
synchronization
procedure
Early
Transmission
Page13
Application Scenarios
Networking solution
Page14
Contents
Feature
(Important)
Page15

(Differences from the Walkie-Talkie
Service)
The walkie-talkie service uses analog signals, and PTT uses
WCDMA digital signals.
The implementation of the walkie-talkie service is simple.

PTT requires support from the WCDMA radio network, core
network, and QAS server.
Page16

(PTT User Identification)
PTT user identification: The radio network controller (RNC) assigns the following quality of service
(QoS) information elements (IEs) in messages based on the RAB, and identifies the user as a
PTT user.
Traffic Class = interactive (default and not configurable)
Signaling Indication
Priority Level
Pre-Emption Capability
Pre-Emption Vulnerability
Queuing Allowed
Run the man-machine language (MML) command SET UFRC to set the following parameters.
PTTSigInd is a hidden parameter and its default value is TRUE.
SET UFRC: PTTArpPriorityLevel=9, PTTArpPreEmptCap=TRIGGER,

PTTArpPreEmptVuln=PRE_EMPTABLE, PTTArpQueuingAllowed=ALLOWED, PTTSigInd=TRUE;
Page17

(PTT Service Type)
The PTT service type is specified as Interactive in RAB

assignment, but the RNC considers it as a conversational
service during internal processing.
When configuring TRMMAP, map it to a real-time path;

otherwise, the corresponding path cannot be found.
Page18

(PTT
Service
Rate)
The rate of the PTT service is 8K. If the RAB assignment rate exceeds 8K, the RNC
returns a failure (in future, the RNC implements compatibility processing; then, even
if the rate exceeds 8K, the typical PTT parameter configuration is still used).
Run the following command to configure the guaranteed bit rate (GBR) of the PTT
service.
SET UUSERGBR: TrafficClass=PTT, UlGBR=D8, DlGBR=D8;
Page19
PTT Implementation: PTT User

State Transition
A PTT user does not proactively release the PTT service but is always in the
RRC connection state. If no call is connected, the PTT user needs to be
transited to the PCH state.
The state transition switch and state transition parameters of PTT users must
be set separately from those of common users. In this way, users use
different configurations and do not affect each other.
If a common user is to be transited form the PCH state to the DCH state, first
the P2F procedure is implemented, and then the F2D procedure is
implemented. A PTT user supports the one-step P2D procedure, that is, the
PTT user can be transited directly from the PCH state to the DCH state. In
this way, signaling connection delay is reduced.
Run the following command. PTTStateTransSwitch and PTTP2DSwitch are
hidden parameters and their default values are ON.
SET UPTTSTATETRANS: PTTStateTransSwitch=ON PTTP2DSwitch=ON;
SET UFRC: PTTHsupaTti=EDCH_TTI_2ms;
Page20
PTT Implementation: Determination

Conditions of the P2D Procedure
The PTT caller in the PCH state proactively initiates a cell update
message where the cause is uplink data transmission, and the
message carries the IE Traffic volume indicator. This IE indicates that
the UE is to transmit large amount of data. The 4A volume
determination condition is met. In this case, the RNC determines to
trigger the P2D cell update procedure.
For the PTT callee in the PCH state, after the RNC receives downlink
data, the RNC determines to trigger the P2D cell update procedure
and sends a paging to the UE. After the UE receives the paging, the
UE sends a cell update message where the cause is paging response.
Page21
PTT Implementation: Discontinuous

Reception Period
PTT users are in the PCH state even if no call is connected. The
discontinuous reception period DRX needs to be set
independently to accelerate PTT paging and to reduce the call
connection time.
The default discontinuous reception period

QChatDRXCycleLength configured for PTT users is 5, and the
paging message interval is 320 ms.
SET UFRC: PTTDrxCycleLenCoef=5;
Page22
PTT Implementation: Rapid L1

Synchronization
In the P2D and F2D procedures triggered for PTT users, the physicallayer parameters are adjusted to accelerate connection.
The values of the IEs SRB delay and Npcp are changed to 0 to 4
respectively. The SRB delay IE indicates that the UE enters the
CELL_DCH state and needs to wait a certain number (specified by
SRB delay) of TTIs before it can send a response.
The Npcp IE indicates the number of power control preambles to be
sent for power regulation.
Run the following command.
ADD UCELLCAC:CELLID=10011,PTTSRBDELAY=0,
PTTPCPREAMBLE=4;
Page23
PTT Implementation: Repeated

Paging Deliveries
Paging messages are delivered repeatedly so that the callee can be
paged quickly.
The paging interval of PTT users is MAX (320 ms, DRX of PTT
users).
Run the following hidden MML command to configure the number of
paging times for PTT users.
SET UPTTPARAM:PTTPAGEREPEATTIMES=2;
Page24
PTT Implementation: Improved Reliability of

the P2D Cell Update Procedure
Reliability is improved so that the callee can be quickly transited to
the CELL_DCH state.
PTT users can repeatedly deliver cell update acknowledgement
messages until receiving the cell update acknowledgement response
returned by the UE.
Run the following hidden MML command to configure the number of
paging times for PTT users.
SET UPTTPARAM:PTTCUCREPEATTIMER=320,
PTTCUCREPEATTIMES=2;
Page25
PTT Implementation: P2F Attempt

After P2D Failure
If the P2D procedure of a PTT user fails, the P2F procedure is
triggered if the user receives a cell update message after the failure.
PTT users can make calls in the CELL_FACH state but the call
quality cannot be guaranteed.
Page26
PTT Implementation: PTT User

Tracing by the IOS
The intelligent optimization system (IOS) can trace PTT users.
Page27
Contents
Feature
(Important)
Page28
Networking, Hardware, and Software

Planning
Involved network elements (NEs): RNC, BBU/RRU of the

NodeB, and core network NEs
Networking requirements
Hardware requirements
None.
None.
Software requirements
RNC: BSC6900V900R013C00 or later versions
NodeB: RAN13 or later versions
Page29
Data Planning
Plan all the data related to this feature. The data includes
the following:
Global data: NA
Device data: NA
Interface data: NA
BTS data: NA
Negotiation data
The RNC needs to negotiate PTT user identification parameters

with the SGSN.
Page30
Data Configuration Procedure (1)
1. Enable PTT user identification.
This switch must be on; otherwise, the RNC cannot identify PTT users.
SET UCORRMALGOSWITCH: CfgSwitch=CFG_PTT_SWITCH-1;
CFG_PTT_SWITCH-1: PTT feature switch
2. Configure PTT user identification.
The RNC identifies PTT users based on the Signaling Indication IE and the four ARP-related parameters. The four ARPrelated parameters must be consistent with the RAB#2 assignment request. The PTT user paging period is 5 (320 ms).
SET UFRC:PTTSigInd=TRUE, PTTArpPriorityLevel=9, PTTArpPreEmptCap=TRIGGER,

PTTArpPreEmptVuln=PRE_EMPTABLE, PTTArpQueuingAllowed=ALLOWED, PTTDrxCycleLenCoef=5;
3. Set the PS inactive timer.
Set T1 and T2 of the background service. After the PTT UE activates the PTT service, RAB#1 (used for PTT user
registration) and RAB#2 (used for PTT service establishment for PTT users) are established. After T1 expires, the RNC
quickly initiates RAB#1 release and keeps RAB#2 online (RAB#2 is not affected by the PS inactive timer). T2 is a check
timer configured to ensure that RAB#1 is deleted so that the length of the CELL UPDATE CONFIRM message during
PTT call establishment is reduced and the call establishment delay reduced.
SET UPSINACTTIMER: PsInactTmrForBac=5, ProtectTmrForBac=5;
Page31
4. Enable PTT state transition.
The state transition switch dedicated for PTT users is used to transit the states of PTT
users between CELL_DCH, CELL_FACH, and CELL_PCH/URA_PCH. The CELL_PCH
To CELL_DCH state transition switch is used to transit the state of a PTT user directly
from CELL_PCH to CELL_DCH. This can reduce the call establishment delay when the
caller and callee are both in the CELL_PCH/URA_PCH state.
SET UPTTSTATETRANS: PTTStateTransSwitch=ON, PTTP2DSwitch=ON;
PTTStateTransSwitch: PTT state transition switch used to transit the state of PTT users
between CELL_DCH, CELL_FACH, and CELL_PCH.
PTTP2DSwitch: CELL_PCH To CELL_DCH state transition switch for PTT users.
Page32
5. Set dedicated state transition parameters for PTT users.
This prevents frequent transitions of the UE between the CELL_DCH and CELL_FACH states during a PTT
call and ensures that the UE can transit from the CELL_FACH state to the CELL_PCH state after the PTT call
is complete. If RAB#1 of a PTT user is not released, that is, there are two RABs, the RNC considers the user
as a user using service combinations. The state transition parameters SET UPTTSTATETRANS and SET
UUESTATETRANS are set to largest values.
SET UPTTSTATETRANS: PTTDH2FStateTransTimer=10, PTTCpc2FStateTransTimer=3,

PTTDH2EFachStateTransTimer=3, PTTCpc2EFachStateTransTimer=3, PTTDH2FTvmThd=D8,
PTTDH2FTvmTimeToTrig=D1280, PTTDH2FTvmPTAT=D1000, PTTE2FThrouMeasPeriod=110,
PTTE2FThrouThd=1, PTTE2FThrouTimeToTrig=1, PTTE2FThrouPTAT=1, PTTF2PStateTransTimer=3,
PTTF2PTvmThd=D8, PTTF2PTvmTimeToTrig=D5000, PTTF2PTvmPTAT=D1000, PTTF2DHTvmThd=D32,
PTTF2DHTvmTimeToTrig=D0;
Note: In normal cases, a PTT user uses only one RB, that is RB#2. The state transition of RB# is controlled
only by the SET UPTTSTATETRANS command. The state transition of a common PS BE service is controlled
by the SET UUESTATETRANSTIMER command. If RB#1 of a PTT UE is not released or the PTT UE is using
multiple RBs for service combinations, the RNC traverses all service types and determines whether to perform
state transition based on the corresponding timer. State transition is performed only when each service meets
the conditions.
Page33
6. Change the NPCP and SRB delay (of the cell level) used for L1 rapid
synchronization.
MOD UCELLCAC: CellId=107,PTTSrbDelay=0,PTTPcPreamble=4;
7. Set the L1 rapid synchronization switch, number of paging retransmission times,

and cell update acknowledgement parameters.
The following is an internal command.
SET UPTTPARAM: PTTFastL1SyncSwitch=ON, PTTPageRepeatTimes=2,

PTTCUCRepeatTimer=320, PTTCUCRepeatTimes=2;
Page34
8. Optimize the typical RAB parameters used by PTT users.
Change the size and number of PDUs of the MAC-D corresponding to E-DCH and HS-DSCH
as follows. This ensures that the NodeB caches Announce Call messages and prevents
packet loss when the network early-onset feature is used. It is recommended that you query
and back up the original parameter values before modifying them.
MOD UTYPRABHSPA: RabIndex=14, TrchType=TRCH_EDCH_2MS,
EdchMacdPduSizeNum=D4, EdchMacdPduSize1=144, EdchMacdPduSize2=208,
EdchMacdPduSize3=336;
MOD UTYPRABHSPA: RabIndex=14, TrchType=TRCH_EDCH_10MS,
EdchMacdPduSizeNum=D3, EdchMacdPduSize1=144, EdchMacdPduSize2=208,
EdchMacdPduSize3=336;
MOD UTYPRABHSPA: RabIndex=14, TrchType=TRCH_HSDSCH, MACHST1=D60,
MACHSWINSIZE=D16, HsdschMacdPduSizeNum=D3, HsdschMacdPduSize1=208,
HsdschMacdPduSize2=336, HsdschMacdPduSize3=656,
MACHSDISCARDTIMEOPT=TRUE, MACHSDISCARDTIME=D500;
Page35
9. Enable the network early-onset feature and the RLC UM special LI function.
After the network early-onset feature is used, the RNC can send user-plane data
(Announce Call messages) to the NodeB before receiving the RB Recfg Cmp message.
After the special LI function is used, the UE can directly send the next received Announce
Call message to the RRC layer if the UE does not receive Announce Call messages with
consecutive RLC sequence numbers.
SET URRCTRLSWITCH: PROCESSSWITCH=PTT_EARLY_TRANS_SWITCH_OFF0&PTT_SPEC_LI_SWITCH_OFF-0;
Page36
10. Ensure that the PTT UEs in the CELL_PCH state can transit to the URA_PCH
state.
If the number of cell reselection times of a PTT UE that is in the CELL_PCH state is equal
to or larger than one in three seconds, the RNC transits the state of UE to URA_PCH in
the next cell update procedure.
SET UUESTATETRANS: CellReSelectCounter=1;
SET UUESTATETRANSTIMER: CellReSelectTimer=3;
11. Enable CDT tracing for the NodeB.
MOD UNODEB: NodeBId = 107, NodebTraceSwitch=ON;
Page37
Configuration Procedure on the CME I
(1) Set CFG_PTT_SWITCH.

The procedure for navigating to the CORRMALGOSWITCH table is as follows: On the Main View tab, rightclick an MBSC, and choose UMTS Radio Global Configuration Express from the shortcut menu. On the
Properties tab, click CORRMALGOSWITCH. The CORRMALGOSWITCH table is displayed in the right pane.
Page39

(2) Set PPTARPQUEUINGALLOWED to ALLOWED.
The procedure for navigating to the FRC table is as follows: On the Main View tab, right-click an MBSC, and choose UMTS Radio
Global Configuration Express from the shortcut menu. On the Properties tab, click FRC. The FRC table is displayed in the right pane.
Page40

(3) Set the PS inactive timer.
The procedure for navigating to the PSINACTTIMER table is as follows: On the Main View tab, right-click an
MBSC, and choose UMTS Radio Global Configuration Express from the shortcut menu. On the Properties
tab, click PSINACTTIMER. The PSINACTTIMER table is displayed in the right pane.
Page41
Configuration Procedure on the CME II

(4) Set PTTSTATETRANSSWITCH to ON and PTTP2DSWITCH to ON.
The procedure for navigating to the PTTSTATETRANS table is as follows: On the Main View tab, right-click an MBSC, and choose
UMTS Radio Global Configuration Express from the shortcut menu. On the Properties tab, click PTTSTATETRANS. The
PTTSTATETRANS table is displayed in the right pane.
Page42
Configuration Procedure on the CME III

(5) Set PTTSTATETRANS parameters.
The procedure for navigating to the PTTSTATETRANS table is as follows: On the Main View tab, right-click an
tab, click PTTSTATETRANS. The PTTSTATETRANS table is displayed in the right pane.
Page43
Configuration Procedure on the CME IV

(6) Run the following command to modify other NPCP and SRB DELAY cell-level parameters:
MOD UCELLCAC: CellId=107,PTTSrbDelay=0,PTTPcPreamble=4;
CME does not support hidden fields.
Page44
Configuration Procedure on the CME IV

(7) Set PTTFASTL1SYNCSWITCH, PTTPAGEREPEATTIMES, PTTCUCREPEATTIMER, and
PTTCUCREPEATTIMES.
The procedure for navigating to the PTTPARAM table is as follows: On the Main View tab, right-click an
tab, click PTTPARAM. The PTTPARAM table is displayed in the right pane.
Page45
Configuration Procedure on the CME V

(8) Optimize the typical RAB parameters for PPT UEs.
The procedure for navigating to the TYPRABHSPA table is as follows: On the Main View tab, right-click an MBSC,
and choose UMTS Radio Global Configuration Express from she shortcut menu. On the Properties tab, click
TYPRABHSPA. The TYPRABHSPA table is displayed in the right pane.
Page46
Configuration Procedure on the CME VI

(9) Set PTT_EARLY_TRANS_SWITCH_OFF and PTT_SPEC_LI_SWITCH_OFF.
The procedure for navigating to the RRCTRLSWITCH table is as follows: On the Main View tab, right-click an
tab, click RRCTRLSWITCH, and then click PROCESSSWITCH.
Page47
Configuration Procedure on the CME VII

(10) Ensure the PTT UEs in the CELL_PCH state can be switched to the URA_PCH state.
The procedure for navigating to the UESTATETRANS table is as follows: On the Main View tab, right-click an
tab, click UESTATETRANS. The UESTATETRANS table is displayed in the right pane.
Page48

(10) Ensure that the PTT UEs in the CELL_PCH state can be switched to the URA_PCH state.
The procedure for navigating to the UESATETRANSTIMER table is as follows: On the Main View tab, rightclick an MBSC, and choose UMTS Radio Global Configuration Express from the shortcut menu. On the
Properties tab, click UESTATETRANSTIMER. The UESTATETRANSTIMER table is displayed in the right
pane.
Page49

(11) Set NODEBTRACESWITCH to ON.
The procedure for navigating to the NODEB table is as follows: On the Main View tab, right-click a NodeB,
and choose NodeB Configuration Express from the shortcut menu. On the Properties tab, click NODEB.
The NODEB table is displayed in the right pane.
Page50
Contents
Feature
(Important)
Page38
Hardware Installation Procedure

(Optional)
The hardware installation procedure mainly refers to the

modification (addition or deletion) of hardware or networking
so that this feature can be used. Detailed installation
procedure is provided.
Page39
Description of Key Parameters of the

PTT Feature
Possible impacts (especially adverse effects) of the key

parameters on the network
None.
None.
Default values and recommended values of the key

parameters
Page40
Verification or Assessment
Verification method
1. Observe the dedicated PTT procedure.
Performance assessment method
Counters related to PTT service establishment and release:

VS.PTT.PCH.SingleRAB.CallReq.Succ: This counter measures the number of times that the users who establish single PTT service initiate or
respond to PTT calls in the CELL PCH or URA PCH state by means of the P2D procedure successfully in a cell.
VS.PTT.FACH.SingleRAB.CallReq.Att: This counter measures the number of times that the users who establish single PTT service attempt to
initiate or respond to PTT calls in the CELL FACH state in a cell.
VS.PTT.FACH.SingleRAB.CallReq.Succ: This counter measures the number of times that the users who establish single PTT service initiate or
respond to PTT calls in the CELL FACH state successfully in a cell.
VS.PTT.RAB.AbnormRel.DCH: This counter measures the number of times that RABs are abnormally released during PTT service calls in a cell.
Counters related to PTT service calls:
VS.PTT.FACH.MultRAB.CallReq.Succ: This counter measures the number of times that the users who establish multiple PTT services
initiate or respond to PTT calls in the CELL FACH state successfully in a cell.
VS.PTT.SuccPaging.First: This counter measures the number of times that the users who establish multiple PTT services initiate or respond to
PTT calls in the CELL FACH state successfully in a cell.
VS.PTT.SuccPaging.Second: This counter measures the number of times that the users who establish multiple PTT services initiate or respond
to PTT calls in the CELL FACH state successfully in a cell.
VS.PTT.SuccPaging.Third: This counter measures the number of times that PTT service paging succeeds after the RNC sends three PAGING
TYPE 1 messages in a cell.
VS.PTT.NormalRel: This counter measures the number of times that PTT calls are complete in a cell.
VS.PTT.SuccP2D.First: This counter measures the number of times that P2D state transition succeeds after the RNC sends one CELL UPDATE
CONFIRM message in a cell.
Page41
Verification or Assessment (Continued)

VS.PTT.SuccP2D.Second: This counter measures the number of times that P2D state transition succeeds after the RNC sends two
CELL UPDATE CONFIRM messages in a cell.
VS.PTT.SuccP2D.Third: This counter measures the number of times that P2D state transition succeeds after the RNC sends three
CELL UPDATE CONFIRM messages in a cell.
VS.PTT.FACH.MultRAB.CallReq.Att: This counter measures the number of times that the PTT users who establish multiple services
attempt to initiate or respond to PTT calls in the CELL_FACH state in a cell. This counter can be used to analyze the PTT service
access situation in the CELL_FACH state.
VS.PTT.PCH.SingleRAB.CallReq.Att: This counter measures the number of times that the users who establish single PTT
service attempt to initiate or respond to PTT calls in the CELL PCH or URA PCH state by means of the P2D procedure in a
cell.
VS.PTT.PCH.SingleRAB.CallReq.Fail.Cong: This counter measures the number of times that the users who establish
single PTT service fail to (due to cell resource congestion) initiate or respond to PTT calls in the CELL PCH or URA PCH
state by means of the P2D procedure in a cell.
VS.PTT.FACH.SingleRAB.CallReq.Fail.Cong: This counter measures the number of times that the users who establish
single PTT service fail to (due to resource restriction) initiate or respond to PTT calls in the CELL FACH state in a cell.
VS.PTT.FACH.MultRAB.CallReq.Fail.Cong: This counter measures the number of times that the users in the CELL FACH
state who establish multiple PTT services fail to (due to resource restriction) initiate or respond to PTT calls.
Number of times that PTT single service users fail to initiate or respond to PTT calls by means of the P2D
procedure
VS.PTT.PCH.SingleRAB.CallReq.Fail.Cong: This counter measures the number of times that the users who establish
single PTT service fail to (due to cell resource congestion) initiate or respond to PTT calls in the CELL PCH or URA PCH state
by means of the P2D procedure in a cell.
VS.PTT.FACH.SingleRAB.CallReq.Fail.Cong: This counter measures the number of times that the users in the CELL FACH
state who establish single PTT service fail to (due to resource restriction) initiate or respond to PTT calls.
VS.PTT.FACH.MultRAB.CallReq.Fail.Cong: This counter measures the number of times that the users in the CELL FACH
state who establish multiple PTT services fail to (due to resource restriction) initiate or respond to PTT calls.
Page42
Precautions
The precautions include but are not limited to the following:
Workaround that needs to be taken for this feature in certain

versions and certain situations
Mutual exclusiveness between this feature and other features
E-PCH and PTT binding
Page43
Contents
Feature
(Important)
Page44
References
The reference documents include but are not limited to the

following:
BSC6900V900R013 PTT Deployment Guide.doc
Page45
Acronyms and Abbreviations
PTT: Push To Talk
Page46
Thank you
www.huawei.com

Training Document WRAN13.0 BSC6900 (V900R013C00) PTT Feature Description-20110212-A-1.0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Training Document WRAN13.0 BSC6900 (V900R013C00) PTT Feature Description-20110212-A-1.0

Uploaded by

Copyright:

Available Formats

Security Level: Internal Use

Global Technical Support

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

Upon completion of this course, you will be able to:

List the characteristics of the push to talk (PTT) feature.

Know the basic principles of the PTT feature.

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

Upon completion of this course, you will be able to:

List the counters of the PTT feature.

Explain the design and implementation method of the PTT

Configure (or enable) and verify the PTT feature.

Know the impacts on the system (counters) and precautions

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

About This Course

This course is based on RAN13. Before learning this

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

PTT allows a user to communicate immediately with one or

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

Receivers can hear the speaker without any response.

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

Functions of the NEs for PTT

QChat UE: uses the initialized dispatch service and receives

QAS: implements call control, OAM, and charging, and

WCDMA: maintains IP sessions.

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

Principles of the PTT Feature

Run the following commands:

SET UFRCCHLTYPEPARA: PTTChlType=HSPA;

SET UFRC: PTTHsupaTti=EDCH_TTI_2ms;

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

Principles of the PTT Feature

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

Principles of the PTT Feature

This step requires

UTRAN DRX cycle

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

The user state is

Principles of the PTT Feature

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

Principles of the PTT Feature

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

Principles of the PTT Feature

WCDMA digital signals.

The implementation of the walkie-talkie service is simple.

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

Principles of the PTT Feature

Traffic Class = interactive (default and not configurable)

SET UFRC: PTTArpPriorityLevel=9, PTTArpPreEmptCap=TRIGGER,

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

Principles of the PTT Feature

The PTT service type is specified as Interactive in RAB

When configuring TRMMAP, map it to a real-time path;

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

Principles of the PTT Feature

SET UUSERGBR: TrafficClass=PTT, UlGBR=D8, DlGBR=D8;

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

PTT Implementation: PTT User

PTT Implementation: Determination

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

PTT Implementation: Discontinuous