RAN2376 Smartphone Profiling

1 © Nokia Siemens Networks 2011For internal use

NWS LTA RA E2E SA Network Engineering / Bartosz Maciejak

Network Engineering Info (NEI)Feature Deep Dive RAN2376 Smartphone Profiling

Bartosz MaciejakMBB CS Network Engineering

The latest version of this NEI can be found here

https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/D435836926



Change History

Issue Number Date of Issue Reason for Update

0.1 21.09.2011 Draft version

1.0 29.09.2011 Approved 1.0 version



Agenda

General Introduction

Smartphone identification

Smartphone handling

Interdependencies

Technical Details

Network Parameters

KPIs and Counters



General IntroductionRAN2376 Smartphone Profiling



• UEs are identified by amount of data and frequency of data transmission.• Those UEs which seldom send a small amount of data are preferably be served

on common channels instead of dedicated channels• Separate Cell_DCH triggers are introduced to handle those UEs which need to

send bigger amount of data• New measurements and statistics supported by configurable floating window time

period and short time data sample collection

Brief Introduction & Benefits of RAN2376 (1/2)

Dedicated channel

Common channel

High traffic volumes

Keep-alives and small data amounts



• This feature reduces control plane load caused by sending of small data packets, such as keep-alive or push-notification messages.

• Less users in Cell_DCH state increases the capacity for those users which need to be served in Cell_DCH state better user experience for high data volume users.

• Cell_FACH state is preferred to Cell_DCH state for Smartphones sending small data amounts.

• Usage of Cell_DCH state resources are saved in Air interface, Iub/Iur baseband, BTS and RNC.

• Channel selection for keep-alive messages can be optimized for UEs not using Fast Dormancy or UEs following 3GPP REL-8 Fast Dormancy.

Brief Introduction & Benefits of RAN2376 (2/2)



General Release Information on RAN2376

Common O&M Platform Feature No

BSW/ASW ASW

RAS SW Component RAN

License Control RNC LK

Licence Control in Network Element

Long-term On/Off license

WCDMA Release RU40 EP1

I-HSPA System I-HSPA Rel5 EP1

RNC Release RN7.0

mcRNC Release mcRNC2.0

BTS (Flexi) -

NetAct -

HW Requirements -

UE Release -

Supplementary O&M InformationRelease Information



With and Without RAN2376

RAN2376 Activated

Nor feature Activated

RAN2136 Activated

RAN2451 Activated

• No intelligent handling of smartphones

• Depending on size, each keep-alive or user message cause either Cell_DCH or Cell_FACH UE state entrance

• After each message, it is required to expire the T1 and T3 timers before going to Cell_PCH or to Idle state.

System impact:• High Signalling load• Long dedicated

resources occupation• Short Battery Lifetime

RAN2136 Fast Dormancy

• RAN2136 is an implenentation of 3GPP Rel.8 Fast Dormancy

• Utilizes T323 timer and SIGNALLING CONNECTION RELEASE INDICATION (SCRI) with cause value “UE Request PS Data session end”

• If RNC receives SCRI with this cause value, it moves an UE to the Cell_PCH/URA_PCH

System impact:• Legacy Fast Dormancy

UEs are moved to Cell_PCH/URA_PCH faster

• Less signalling• Long Battery life

RAN2451 Fast Dormancy Profiling

• Feature extends the usage of RAN2136

• UEs, which send SIGNALLING CONNECTION RELEASE INDICATION (SCRI) with any cause value are profiled as Smartphone

• For this UE, higher TVM thresholds and shorter inactivity timers are applied.

System impact:• Profiled Ues are moved

to Cell_PCH/URA_PCH faster

• UE doesn’t enter Cell_DCH as often as legacy UE


• RAN2376 Smartphone Profiling

• RAN2376 implements new profiling method based on real behaviour of UEs and the traffic profile in Cell_DCH state

• Duration of activity and the amount of data will be measured in order to identify Smartphones.

System impact:• Profiled Ues are moved

to Cell_PCH/URA_PCH faster

• UE doesn’t enter Cell_DCH as often as legacy UE




InterdependenciesRAN2376 Smartphone Profiling



Requirements of RAN2376

Features Requirements:

• RAN2451 - Fast Dormancy Profiling• Feature RAN2376 Smartphone Profiling requires RAN2451 as it uses network parameters defined in RAN2451

• RAN2454 - Cell level parameters for better UL load control• Feature RAN2376 Smartphone Profiling requires RAN2454 as it uses network parameters defined in RAN2454

RAN2451 Fast Dormancy

Profiling

RAN2376Smartphone

Profiling

RAN2454 Cell level parameters

for better UL load control



Technical DetailsRAN2376 Smartphone Profiling



RAN2376 – Smartphone Profiling Smartphone identification – High level principle

Cell_DCH state requested for NRT RAB

UE sends data in UL or CN sends data in DL

L3 configures Smartphone profiling parameters to L2

UE is not Smartphone

L2 starts MAC-d throughput measurements

L2 starts “Short activity” timer when activity detected

UE is SmartphoneL2 sends indication to L3

“Short Activity” timer expires

Inactivity in DL and UL

0<Data amount<“Low_data_threshold

Higher TVM thresholds and shorter inactivity timers used

Legacy TVM thresholds and inactivity timers used



RAN2376 – Smartphone ProfilingSmartphone identification (1/3)

Keep-alivepacket

SmartProfDataThrUL

Data UL

timeSmartProfActivityTime Smart indication

Data Rx startData Rx stop, Inactivity start

ACK

SmartProfDataThrDL

Data DL


Data Tx start

Keep-alivepacket

Data Rx stop, Inactivity start

1. When Cell_DCH resources are reserved for a UE, MAC entity starts “SmartProfActivityTime” after receiving/sending the first packet

2. After “SmartProfActivityTime” timer expiration, inactivity check is performed in order to check, if RAB is inactive (in both directions, UL and DL)

3. If the above condition is true, then the throughput measurements (for both, UL and DL) within the “SmartProfActivityTime” period are checked and compared to the SmartProfDataThrUL and SmartProfDataThrDL values

4. If condition mentioned in step 5 are not met, then the indications are sent to L3 with smartphone indication flag set to “false”

5. If the throughput values are <= thresholds, then the indications are sent to L3 with smartphone indication flag set to “true”

Smartphone profiling




L2/MAC measurement for Smartphone Profiling:

• Are performed for every single PS NRT RAB independently, irrespective of other simultaneous RABs

L2/MAC measurements for Smartphone Profiling:• Are used when UE is in Cell_DCH state, has

PS NRT RAB established, which is mapped to the following transport channels:

• HS-DSCH & E-DCH• HS-DSCH & UL DCH• DL DCH & UL DCH

Smartphone Profiling is performed:• If UE has PS NRT RAB established, irrespective

of other simultaneous RABs• Every time UE enters Cell_DCH state

Smartphone Profiling is not performed• For CS RABs, PS RT RABs (Conversational,

Streaming)• When the UE is already defined as Smartphone

according to the RAN2451 Fast Dormancy Profiling feature

• When there is no data sent in UL and DL in Cell_DCH state

Smart-phone

Profiling

If any RAB of the UE does not meet the Smartphone criteria, UE is not

considered as Smartphone




IDLE_Mode

Cell_DCH/Rel99

Cell_FACH

Cell_PCH

L2 measurements L2 measurements

Smartphone Profiling Smartphone Profiling

SmartProfActivityTime SmartProfActivityTime

Each time UE enters Cell_DCH, L2 measurements for Smartphone Profiling start

If UE is has been identified as Smartphone in Cell_DCH, L3 classifies UE as Smartphone, when UE is transferred to the Common Chanel.

If UE is classified as Smartphone, Smartphone-specific TVM thresholds and inactivity timers are taken into use

If UE is classified as Smartphone, Smartphone-specific TVM thresholds and inactivity timers are taken into use

21 4

1

3

2

2 3

4



RAN2376 – Smartphone ProfilingSmartphone identification – Scenario 1

CS AMR RAB

PS NRT RAB 1

PS NRT RAB 2

“Smartphone Profiling” applicable

UE is not classified as Smartphone by RAN2376

• Scenario assumptions:• UE has established 3 simultaneous RABs:

• 1x CS AMR RAB• 2x PS NRT RAB

• Both PS NRT RABs meet Smartphone Profiling Criteria:• UE Activity duration in Cell_DCH state below SmartProfActivityTime threshold• Amount of data sent / received during activity below SmartProfDataThrDL and • SmartProfDataThrDL thresholds

UE is not considered as Smartphone



RAN2376 – Smartphone ProfilingSmartphone identification – Scenario 2

CS AMR RAB

PS NRT RAB 1

PS NRT RAB 2

“Smartphone Profiling” applicable

UE is not classified as Smartphone by RAN2376

UE is classified as Smartphone by RAN2376

• Scenario assumptions:• UE has established 3 simultaneous RABs:

• 1x CS AMR RAB• 2x PS NRT RAB

• Both PS NRT RABs meet Smartphone Profiling Criteria:• UE Activity duration in Cell_DCH state below SmartProfActivityTime threshold• Amount of data sent / received during activity below SmartProfDataThrDL and • SmartProfDataThrDL thresholds

UE is considered as Smartphone, when CS AMR RAB ends



RAN2376 – Smartphone ProfilingDifferent Smartphone handling - example

IDLE_Mode

Cell_DCH/Rel99

Cell_FACH

Cell_PCH

Transmission

InactivityTimerUplinkDCH= 5s

TrafVolThresholdULLow = 128 B

UL_DL_activation_timer = 2s

IDLE_Mode

Cell_DCH/Rel99

Cell_FACH

Cell_PCH

Transmission

SmartInactivityTimerFACH= 1s

SmartTrafVolThrUL = 256 B

Assumption:• UE sends keep-alive

message = 150 BWith legacy parameters:• each time keep-alive is

sent, UE enters Cell_DCH • after transmission, long

inactivity timers are applied

For Smartphone – clasified UE:• Shorter inactivity timers are

used for moving smartphones to Cell_PCH state - saving UE battery

• Higher traffic volume thresholds are used for moving smartphones to Cell_DCH state

• Much less signalling load• Lower resource utilization

Legacy UE

Smartphone



RAN2376 – Smartphone ProfilingSmartphone and legacy parameters – default values comparison

NameDefault Value

NameDefault Value

SmartHSPATputAveWin 1s MACdflowthroughputAveWin 3sSmartHSPATimeToTrigger 0.2s MACdflowutilTimetoTrigger 0sSmartHSPATputAveWin 1s EDCHMACdFlowThroughputAveWin 3sSmartHSPATimeToTrigger 0.2s EDCHMACdFlowThroughputTimetoTrigger 5s

InactivityTimerDownlinkDCH 5sInactivityTimerUplinkDCH 5s

Rel-99 FACH inactivity

SmartInactivityTimerFACH 1s UL_DL_activation_timer 2s

SmartInactivityTimerDCH 0.2s

New shorter inactivity timers Legacy inactivity timers

HS-DSCH Inactivity

E-DCH Inactivity

DCH Inactivity

NameDefault Value

NameDefault Value

Rel-99 FACH & RACH UL SmartTrafVolThrUL 256 bytes TrafVolThresholdULLow 128 bytes

Rel-99 FACH & RACH DL SmartTrafVolThrDL 256 bytes TrafVolThresholdDLLow 128bytes

HS-FACH & Rel-99 RACH SmartTrafVolThrUL 256 bytes TrafVolThresholdULLow 128 bytes

New higher traffic volume thresholds Legacy traffic volume thresholds



RAN2376 – Smartphone Profiling Impact on Network Performance – Less Signaling related to Smartphones

PS Call setup1. RRC Connection Request (RRC)2. Radio Link Setup (NBAP)3. Radio Link Setup Response (NBAP)4. Establish Requests (ALCAP)5. Establish Confirm (ALCAP)6. RRC Connection Setup (RRC)7. NBAP Synchronization (NBAP)8. RRC Connection Setup Complete (RRC)9. Initial Direct Transfer (GPRS) (RRC)10. Initial UE Message (RANAP)11. Common Id (RANAP)12. Security Mode Command (RANAP)13. Security Mode Command (RRC)14. Security Mode Complete (RRC) 15. Security Mode Complete (RANAP)16. Downlink Direct Transfer (P-TMSI) (RRC)17. Uplink Direct Transfer (P-TMSI) (RRC)18. RAB Assignment Req (RANAP)19. GTP Tunnel Setup (RANAP)20. RB Setup (RRC)21. Radio Link Setup (NBAP)22. Radio Link Setup Response (NBAP)23. Establish Requests (ALCAP)24. Establish Confirm (ALCAP)25. Establish Requests (ALCAP)26. Establish Confirm (ALCAP)27. RB Setup Complete (RRC)28. RANAP:RAB Assignment Resp (RANP)29. Measurement Control (HO) (RRC)30. Measurement Control (TVM) (RRC)

PCH to DCH1. Cell update with TVM (RRC)2. Radio Link Setup (NBAP)3. Radio Link Setup Response (NBAP)4. Establish Requests (ALCAP)5. Establish Confirm (ALCAP)6. Establish Requests (ALCAP)7. Establish Confirm (ALCAP)8. CU confirm with RB reconfig (RRC) 9. NBAP Synchronization (NBAP)10. RB reconfiguration complete (RRC)11. Measurement Control (HO) (RRC)12. Measurement Control (TVM) (RRC)

PCH to FACH1. Cell update (RRC)2. Cell update confirm (RRC)3. UMI confirm (RRC)

From idle Large packet from PCH Small packet from PCH

RRC NBAP RANAP ALCAPFrom Idle_mode to Cell_DCH 12 5 7 6From Cell_PCH to Cell_DCH 5 3 0 4

Number of messages



• Lower resources utilization by Smartphone UEs due to shorter inactivity timers

• Higher amount of data could be sent via Cell_FACH/HS-Cell_FACH state for identified Smartphone Ues

• Less signalling load – Cell_PCH Cell_FACH/HS-Cell_Fach channel type switches instead of Idle/Cell_PCH Cell_DCH

• Longer battery life due to lower battery consumption – shorter time in state with high power requirements

RAN2376 – Smartphone ProfilingNetwork performance and capacity impact - summary



Network ParametersRAN2376 Smartphone Profiling



RAN2376 Smartphone Profiling Activation parameter

Abbreviated name

SmartProfEnabled

Parameter name Smartphone Profiling Enabled

Data type Enumeration

Description SmartProfEnabled parameter enables / disables the use of Smartphone Profiling feature in the RNC.

Parameter group ACConfiguration

Classification Telecom

Range and step 0 (Disabled), 1 (Enabled)

Default value 0



RAN2376 Smartphone ProfilingNew network parameters

Abbreviated name

SmartProfActivityTime

Parameter name Activity Time for Smartphone Profiling

Data type Number

Description Parameter defines the period for Smartphone profiling. If activity of the UE in Cell_DCH state lasts longer than the value defined by the parameter, UE is not considered as Smartphone. Activity measurement starts in the beginning of data transmission and reception in Cell_DCH state.

Parameter group PSParameters


Range and step 0..4000 ms, step 100 ms

Default value 600 ms

DL/UL Message

transmission

SmartProfDataThrUL





Abbreviated name

SmartProfDataThrDL

Parameter name DL data threshold for Smartphone Profiling

Data type Number

Description Parameter defines the maximum data amount in downlink in order to consider UE as Smartphone. If the data amount, measured by MAC-d in downlink, is less than or equal to the threshold defined by this parameter, UE can be considered as Smartphone. Data amount is measured during the time period defined by the SmartProfActivityTime parameter.



Range and step 10..1000 byte, step 10 byte

Default value 300 byte

DL Messagetransmission

SmartProfDataThrDL





Abbreviated name

SmartProfDataThrUL

Parameter name UL data threshold for Smartphone Profiling

Data type Number

Description Parameter defines the maximum data amount in uplink in order to consider UE as Smartphone. If the data amount, measured by MAC-d in uplink, is less than or equal to the threshold defined by this parameter, UE can be considered as Smartphone. Data amount is measured during the time period defined by the SmartProfActivityTime parameter.



Range and step 10..1000 byte, step 10 byte

Default value 300 byte

UL Messagetransmission

SmartProfDataThrUL




RAN2376 Smartphone Profiling Modified network parameters

Abbreviated name SmartHSPATputAveWinParameter name Window size for Smartphone throughput measurement

Data type Number

Description

Parameter defines the HS-DSCH and E-DCH sliding averaging window sizes of the throughput measurements for the identified Smartphone instead of the MACdflowthroughputAveWin and EDCHMACdFlowThroughputAveWin parameters.

The throughput measurement measures the number of bits transmitted by MAC-d entity during the sliding measurement window defined by this parameter. Value 0 means that the MAC-d flow throughput measurement is not activated.

Parameter group PSParametersClassification Radio Resource Utilisation

Range and step 0.5..10 s, step 0.5 sDefault Value 1sSpecial value 0

Special value description Throughput measurement not active




Abbreviated name SmartHSPATimeToTriggerParameter name Time-to-trigger for Smartphone throughput measurement

Data type Number

Description

Parameter defines the time-to-trigger values of the HS-DSCH MAC-d flow low utilisation measurement and E-DCH MAC-d flow low throughput measurement for the identified Smartphone instead of the MACdflowutilTimetoTrigger and EDCHMACdFlowThroughputTimetoTrigger parameters


Range and step 0..300 s, step 0.2 sDefault Value 0.2s




Abbreviated name SmartInactivityTimerDCHParameter name Inactivity timer for Smartphone DCH

Data type Number

Description

The time indicating how long the radio and transmission resources are reserved for Smartphone after inactivity detection on DCH. The parameter is used for the identified Smartphone instead of the InactivityTimerDownlinkDCH and InactivityTimerUplinkDCH parameters.This parameter defines the value for each DCH bit rate in downlink and uplink. Parameter value 255 means that Smartphone specific DCH inactivity timers are not used.


Range and step 0..20 s, step 0.2 sDefault Value 0.2sSpecial value 255

Special value description Smartphone specific inactivity timer not used




Abbreviated name SmartTrafVolThrDLParameter name DL traffi c volume threshold for Smartphone


Description

The parameter defines, in bytes, the threshold of data in the RLC buffers of SRB3, SRB4 and all NRT RBs that trigger the downlink traffi c volume measurement report (capacity request) on MAC, when UE is in Cell_FACH state. Otherwise, RNC sends data on FACH. The parameter is used for the identified Smartphone instead of the TrafVolThresholdDLLow parameter.


Range and step 0 (0 bytes), 8 (8 bytes), 16 (16 bytes), 32 (32 bytes), 64 (64 bytes), 128 (128 bytes), 256 (256 bytes), 512 (512 bytes), 1024 (1 KB)

Default Value 256 bytes




Abbreviated name SmartTrafVolThrULParameter name UL traffi c volume threshold for Smartphone


Description

The parameter defines, in bytes, the threshold of data in the RLC buffers of SRB3, SRB4 and all NRT RBs that trigger the uplink traffi c volume measurement report (capacity request) on MAC, when UE is in Cell_FACH state. Otherwise, RNC sends data on FACH. The parameter is used for the identified Smartphone instead of the TrafVolThresholdULLow parameter.


Range and step 0 (0 bytes), 8 (8 bytes), 16 (16 bytes), 32 (32 bytes), 64 (64 bytes), 128 (128 bytes), 256 (256 bytes), 512 (512 bytes), 1024 (1 KB)

Default Value 256 bytes




Abbreviated name SmartInactivityTimerFACHData type Number

Description

This timer is used on MAC -c to detect the idle periods on data transmission (NRT RBs and SRBs) for the LFD phones in CELL_FACH state. Based on this timer the MAC -c shall give No_Data indication to RRC, which further can change the state of the UE from Cell_FACH state to the Cell_PCH state (or URA_PCH state).

Classification TelecomRange and step 1..120 s, step 1 sDefault Value 1 s



Counters and KPIs RAN2376 Smartphone Profiling



RAN2376 – Smartphone ProfilingNew Counters – number of Smartphone identifications

Measurement M1006 RRCSignalling

Identifier Cxx1, Cxx2, Cxx3

Description Cxx1: Number of times when a UE was classified as Smartphone based on data transfer profiling, while previously being non-Smartphone.Cxx2: Number of times when a UE was classified as non-Smartphone based on data transfer profiling, while previously being Smartphone.Cxx3: Number of times when a UE is re-classified as Smartphone, when it already holds Smartphone status.

Measured object WBTS-WCELL of the main cell of the connection

Trigger events Cxx1: When a UE does not have classification as Smartphone, and data transfer profiling classifies it as Smartphone. This includes also initial classificationsCxx2: When a UE has previously been classified as Smartphone, and data transfer profiling classifies it as non-Smartphone.Cxx3: When a UE has previously been classified as Smartphone, and data transfer profiling is done again for it and still results in Smartphone status. This counter can be utilized to detect too easy transition to Cell_DCH state.

Remarks



RAN2376 – Smartphone ProfilingNew Counters – operating time in FACH

Measurement M1006 RRCSignalling

Identifier Cxx4, Cxx5

Description Cxx4: Sum of operating time in Cell_FACH when the UE holds Smartphone status. (unit=1 second).Cxx5: Number of times when Smartphone leaves Cell_FACH state. This is the denominator for Cxx3.

Measured object WBTS-WCELL of the main cell of the connection

Trigger events Cxx4: The counter is updated when a Smartphone leaves Cell_FACH state. The value to be updated is the amount of time that the UE spent in Cell_FACH state, counting is not stopped if the UE makes cell reselections. Both RAN2376 (data transfer behaviour) and RAN2451 (fast dormancy) identified Smartphones are included.Cxx5: Updated by value 1 when a Smartphone leaves Cell_FACH state and the operating time is summed to counter Cxx3.

Remarks



Thank you for your attention.

Documents

RAN2376 Smartphone Profiling