Documentos de Académico
Documentos de Profesional
Documentos de Cultura
www.huawei.com
Objectives
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
List the counters of the PTT feature. Explain the design and implementation method of the PTT feature.
Page3
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
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.
Page7
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.
Page8
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
The wideband code division 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#1PDP#1 RB#1establish
Page10
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 requestand set corresponding parameter for Qchat User QChat-specific UTRAN
DRX cycle
RAB#1PDP#1 RB#1delete
The user state is changed only after the Qchat service is activated or another service is established.
Page11
Page12
Early Transmission
Page13
Application Scenarios
Networking solution
Page14
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
Page15
The implementation of the walkie-talkie service is simple. PTT requires support from the WCDMA radio network, core
Page16
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
The PTT service type is specified as Interactive in RAB assignment, but the RNC considers it as a conversational
When configuring TRMMAP, map it to a real-time path; otherwise, the corresponding path cannot be found.
Page18
The rate of the PTT service is 8K. If the RAB assignment rate exceeds 8K, the RNC returns a failure (in future, the RNC
Run the following command to configure the guaranteed bit rate (GBR) of the PTT service.
Page19
The PTT caller in the PCH state proactively initiates a cell update message where the cause is uplink data transmission, and the
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 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.
Page22
Page23
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
Page25
Page26
Page27
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
Page28
Involved network elements (NEs): RNC, BBU/RRU of the NodeB, and core network NEs
Networking requirements
None.
Hardware requirements
None.
Software requirements
Page29
Data Planning
Plan all the data related to this feature. The data includes the following:
BTS data: NA
Negotiation data
Page30
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
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.
PTTStateTransSwitch: PTT state transition switch used to transit the state of PTT users
between CELL_DCH, CELL_FACH, and CELL_PCH.
Page32
Page33
6. Change the NPCP and SRB delay (of the cell level) used for L1 rapid synchronization.
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
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.
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.
Page37
Page38
Page39
Page40
Page41
Page42
Page43
Page44
Page45
Page46
tab, click UESTATETRANS. The UESTATETRANS table is displayed in the right pane.
Page47
Properties tab, click UESTATETRANSTIMER. The UESTATETRANSTIMER table is displayed in the right
pane.
Page48
Page49
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
Page38
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
Possible impacts (especially adverse effects) of the key parameters on the network
None. None.
Page40
Verification or Assessment
Verification method
1. Observe the dedicated PTT procedure. 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.
Page41
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
Workaround that needs to be taken for this feature in certain versions and certain situations
Page43
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
Page44
References
The reference documents include but are not limited to the following:
Page45
Page46
Thank you
www.huawei.com