Chalk talk on FID-15023.

0:

QoS - Miscellaneous Improvements

System Engineer: Elliott Baral

January 19, 2010

1 All Rights Reserved © Alcatel-Lucent 2008

Agenda
• High level feature description
• High-level requirements
• Impacted resource areas
• Feature activation & control
• OA&M
• Standards impact
• 3 -Party dependencies
rd

• Scenarios
• Other areas to consider
• Technical assumptions, concerns risks
• SpE team

2 | January 19, 2010 All Rights Reserved © Alcatel-Lucent 2007

Feature Summary
• This standard feature includes one call processing
improvement, and one OA&M improvement:
1. Optional support for QoS over the Best Effort (BE) Flow.

PTT Speech, Already

Conversational Speech (eHRPD/HRPD) estimated!

Conversational Video (eHRPD/HRPD)

2. Optional support for Provisioning Idle Timers for

VoIP & PTT

PTT LLMCS (Low Latency Media Control Signaling),

CMCS (Conversational Media Control Signaling)

3 | January 19, 2010 All Rights Reserved © Alcatel-Lucent 2007

Provisionable Dormancy Timers
• Prior to this feature

Service providers were able to set a session dormancy timer via the

GUI -- but only for the “Best Effort” and “PTT Conversational

Speech” service categories. Typically, these are set to 7 seconds.

Other service categories are shown on the GUI, but are grayed out

so that they cannot be changed.

Some mobiles have a 10-second ping-timer, intended to keep the

mobile connected. With a 7 second dormancy timer, they get stuck

in timeout/wakeup cycle.

A special script, provided by ALU, lets the service provider
provision a dormancy timer for the PTT LLMCS service category
that aligns better with the ping-timer, thus reducing the frequency
of the timeout/wakeup cycle.

4 | January 19, 2010 All Rights Reserved © Alcatel-Lucent 2007

Provisionable Dormancy Timers
Here is the script’s README file
from ALU’s Customer Center download site:
QosCatLLMCSInactivityTimer script installation and Examples:
usage information
Date: June 26, 2009 $ QosCatLLMCSInactivityTimer check
===================================================== Queries all RNC DBs and prints the value of the
inactivityTimer attribute
1. Obtain script (QosCatLLMCSInactivityTimer) from
LED server and transfer the script to the OMP $ QosCatLLMCSInactivityTimer update on
2. Login as root on OMP Queries all RNC DBs and prints the value of the
3. copy the QosCatLLMCSInactivityTimer script to inactivityTimer attribute AND updates each
/omp/bin/ RNC DB with a value of 20 (10sec)
4. chmod 755 /omp/bin/QosCatLLMCSInactivityTimer
5. See command description including command options $ QosCatLLMCSInactivityTimer update off
below Queries all RNC DBs and prints the value of the
inactivityTimer attribute AND updates each
NAME: QosCatLLMCSInactivityTimer RNC DB with a value of -1 which corresponds
to disabled
DESCRIPTION: This script provides an ability to update
PTT Signaling LLMCS flow InactivityTimer
to 20 (10sec) for R31, R32, and R33 RNCs.

This script should only be run as directed

by WTSC.

COMMAND USAGE:
QosCatLLMCSInactivityTimer check
QosCatLLMCSInactivityTimer update on
QosCatLLMCSInactivityTimer update off

5 | January 19, 2010 All Rights Reserved © Alcatel-Lucent 2007

High-level requirements
• This feature makes the existing PTT LLMCS dormancy timer dynamically
provisionable on the GUI. Service providers can set this to 10 seconds, as
the script does. Or to any other valid value (1 – 3,600 seconds, in 0.5-
second increments).
• Similarly, this feature makes the CMCS service category provisionable on
the GUI. This is applicable to non-PTT services. Valid values: 1 – 3,600
seconds, in 0.5-second increments.
• By default, both timers are ignored (represented on the GUI as a blank).
• Both dormancy timers are dynamic (and do not require a reboot).
• There are no L2 checks.
• The service provider can set either or both timer intervals to 10 seconds (or
any other valid value).
• In other words, this feature can be used to accomplish the same thing as
the script did. And the script can be retired.
6 | January 19, 2010 All Rights Reserved © Alcatel-Lucent 2007
Scenarios
 Retrofit-1: In R35, both timers had been defaulted and
ignored.

During retrofit to R36, both timers must remain defaulted and
ignored.
 Retrofit-2: In R35, the service provider had used the
script to set the PTT LLMCS timer to 10 seconds.

During retrofit to R36, the PTT LLMCS timer must remain set to 10
seconds.

During retrofit to R36, the CMCS timer must remain defaulted and
ignored.

7 | January 19, 2010 All Rights Reserved © Alcatel-Lucent 2007

Scenarios (continued)
 During R36, the PTT LLMCS timer is changed from its
default value to 10 seconds:

PTT sessions, which had been timing out after seven seconds,
should no longer time out after seven seconds.
 During R36, the PTT LLMCS timer is changed from 10
seconds to blank (i.e., back to its default value):

PTT sessions, which had *not* been timing out after seven seconds,
should now time out after seven seconds.
 During R36, the CMCS timer is changed from its default
value to 10 seconds:

Non-PTT sessions should not time-out any earlier than before.

Not clear what other affect if any this will have on individual non-
PTT sessions, on system capacity, or on user experience.

8 | January 19, 2010 All Rights Reserved © Alcatel-Lucent 2007

Scenarios (continued)
 The CMCS service category is applicable to EMFPA (e.g.,
with eHRPD) and to MFPA.

Run tests with both personalities
 At present, MMPA does not use QoS, so there is no need
to test this with MMPA.
 Check whether the timer is updated in-session vs.
session-to-session

9 | January 19, 2010 All Rights Reserved © Alcatel-Lucent 2007

Feature Specifics
 Impacted Resource Areas:

OMC-RAN GUI

EMS & bulk provisioning

CP

Customer documentation
 Feature Activation:

This is a base feature, and the two GUI items become active with
R36 retrofit; no other explicit feature activation is needed.
 OA&M:

Activate these two items on the EVDO GUI:

PTT LLMCS dormancy timer

CMCS dormancy timer

No new commands or alarms.

10 | January 19, 2010 All Rights Reserved © Alcatel-Lucent 2007

More Feature Specifics
 Standards impact:

None

 3rd-Party dependencies:

None

 Other areas to consider:

The QosCatLLMCSInactivityTimer script should not be made
available in R36 from ALU’s Customer Center download site.

 Technical assumptions, concerns, risks:

None

11 | January 19, 2010 All Rights Reserved © Alcatel-Lucent 2007

More Feature Specifics
 SpE team:

Elliott Baral

Chris Mooney

 FID 39111.1’s 1st-Pass Document with details on

QoS over BE:
 http://mobility.ih.lucent.com/~ebaral/eRNC/39111.1/1st-pass-v3.pdf

12 | January 19, 2010 All Rights Reserved © Alcatel-Lucent 2007