3fl11829acaawbzza 02

EVOLIUM Introduction to GPRS and EGPRS QoS Monitoring - B10
3FL11829ACAAWBZZA2 Issue 02
STUDENT GUIDE
All Rights Reserved Alcatel-Lucent 2008
All rights reserved Alcatel-Lucent 2008 Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel-Lucent
All Rights Reserved Alcatel-Lucent 2008 Introduction to GPRS and E-GPRS QoS Monitoring - B10 - Page 1
Empty page
Switch to notes view!
2
EVOLIUM Introduction to GPRS and E-GPRS QoS Monitoring - B10
This page is left blank intentionally
Terms of Use and Legal Notices

1. Safety Warning Switch to notes view!
Both lethal and dangerous voltages may be present within the products used herein. The user is strongly advised not to wear conductive jewelry while working on the products. Always observe all safety precautions and do not work on the equipment alone. The equipment used during this course may be electrostatic sensitive. Please observe correct anti-static precautions.
2. Trade Marks
Alcatel-Lucent and MainStreet are trademarks of Alcatel-Lucent. All other trademarks, service marks and logos (Marks) are the property of their respective holders, including AlcatelLucent. Users are not permitted to use these Marks without the prior consent of Alcatel-Lucent or such third party owning the Mark. The absence of a Mark identifier is not a representation that a particular product or service name is not a Mark. Alcatel-Lucent assumes no responsibility for the accuracy of the information presented herein, which may be subject to change without notice.
3. Copyright
This document contains information that is proprietary to Alcatel-Lucent and may be used for training purposes only. No other use or transmission of all or any part of this document is permitted without Alcatel-Lucents written permission, and must include all copyright and other proprietary notices. No other use or transmission of all or any part of its contents may be used, copied, disclosed or conveyed to any party in any manner whatsoever without prior written permission from Alcatel-Lucent. Use or transmission of all or any part of this document in violation of any applicable legislation is hereby expressly prohibited. User obtains no rights in the information or in any product, process, technology or trademark which it includes or describes, and is expressly prohibited from modifying the information or creating derivative works without the express All Rights Reserved Alcatel-Lucent 2008 3 written consent of Alcatel-Lucent.
All rights reserved Alcatel-Lucent 2008
4. Disclaimer
In no event will Alcatel-Lucent be liable for any direct, indirect, special, incidental or consequential damages, including lost profits, lost business or lost data, resulting from the use of or reliance upon the information, whether or not AlcatelLucent has been advised of the possibility of such damages. Mention of non-Alcatel-Lucent products or services is for information purposes only and constitutes neither an endorsement, nor a recommendation. This course is intended to train the student about the overall look, feel, and use of Alcatel-Lucent products. The information contained herein is representational only. In the interest of file size, simplicity, and compatibility and, in some cases, due to contractual limitations, certain compromises have been made and therefore some features are not entirely accurate. Please refer to technical practices supplied by Alcatel-Lucent for current information concerning Alcatel-Lucent equipment and its operation, or contact your nearest Alcatel-Lucent representative for more information. The Alcatel-Lucent products described or used herein are presented for demonstration and training purposes only. AlcatelLucent disclaims any warranties in connection with the products as used and described in the courses or the related documentation, whether express, implied, or statutory. Alcatel-Lucent specifically disclaims all implied warranties, including warranties of merchantability, non-infringement and fitness for a particular purpose, or arising from a course of dealing, usage or trade practice. Alcatel-Lucent is not responsible for any failures caused by: server errors, misdirected or redirected transmissions, failed internet connections, interruptions, any computer virus or any other technical defect, whether human or technical in nature
5. Governing Law
The products, documentation and information contained herein, as well as these Terms of Use and Legal Notices are governed by the laws of France, excluding its conflict of law rules. If any provision of these Terms of Use and Legal Notices, or the application thereof to any person or circumstances, is held invalid for any reason, unenforceable including, but not limited to, the warranty disclaimers and liability limitations, then such provision shall be deemed superseded by a valid, enforceable provision that matches, as closely as possible, the original provision, and the other provisions of these Terms of Use and Legal Notices shall remain in full force and effect.
Blank Page
4
Course Outline
1. This QoS AboutEGPRS Course
4. Topic/Section is Positioned Here
Course outline of the BSS in GPRS QoS Monitoring 1. Role Technical support on the Main BSS GPRS Telecom Procedures 2. Recalls 5. Topic/Section is Positioned Here Course objectives
3. Description of the Main BSS GPRS QoS Counters and Indicators 5. Analysis of the Main BSS GPRS QoS Problems 6. Appendix
4. Detection of the Main BSS 6. Topic/Section is Positioned Here 1. Topic/Section is Positioned Here GPRS QoS Problems
Xxx Xxx Xxx
7. Topic/Section is Positioned Here
2. Topic/Section is Positioned Here 3. Topic/Section is Positioned Here
5
Course Outline [cont.]

6
Course Objectives
Welcome to Introduction to GPRS and E-GPRS QoS Monitoring - B10
Upon completion of this course, you should be able to:
Describe the scope of work of BSS GPRS QoS monitoring Interpret the BSS GPRS QoS indicators attached to each BSS GPRS procedure or algorithm having an impact on QoS Interpret the BSS GPRS PM counters used in the computation formulae of QoS indicators Detect the main BSS QoS problems Analyse the main BSS QoS problems Correlate with BSS GSM QoS problems List the probable causes of BSS GPRS QoS degradation
7
Course Objectives [cont.]

8
About this Student Guide

Conventions used in Switch to notes view! this guide
Note
Provides you with additional information about the topic being discussed. Although this information is not required knowledge, you might find it useful or interesting.
Technical Reference
(1) 24.348.98 Points you to the exact section of Alcatel-Lucent Technical Practices where you can find more information on the topic being discussed.
Warning
Alerts you to instances where non-compliance could result in equipment damage or personal injury.
Where you can get further information

If you want further information you can refer to the following: Technical Practices for the specific product Technical support page on the Alcatel website: http://www.alcatel-lucent.com
About this Student Guide [cont.]

10
Self-assessment of Objectives
Contract number : Course title :
At the end of each section you will be asked to fill this questionnaire Please, return this sheet to the trainer at the end of the training to notes view!
Dates from : Location : to :
Client (Company, Center) : Language : Switch
Number of trainees : Surname, First name :
Did you meet the following objectives ? Tick the corresponding box Please, return this sheet to the trainer at the end of the training
Yes (or globally yes) No (or globally no)
Instructional objectives 1 To be able to XXX
Comments
2
11
EVOLIUM Introduction to GPRS and E-GPRS QoS Monitoring - B10 All Rights Reserved Alcatel-Lucent 2008
Self-assessment of Objectives [cont.]

Instructional objectives Yes (or Globally yes) No (or globally no) Comments
12
Other comments
Thank you for your answers to this questionnaire
11
Do not delete this graphic elements in here:
Section 1 EGPRS QoS

3JK10237AAAAWBZZA Issue 02
Module 1 Role of the BSS in GPRS QoS Monitoring
EVOLIUM Introduction to GPRS and E-GPRS QoS Monitoring - B10 3FL11829ACAAZZZZA2 Issue 02
All Rights Reserved Alcatel-Lucent 2008 3JK10237AAAAWBZZA Issue 01 Section 1 Module 1 Page 1
Blank Page
112
EGPRS QoS Role of the BSS in GPRS QoS Monitoring EVOLIUM Introduction to GPRS and E-GPRS QoS Monitoring - B10
Document History Edition 01 Date YYYY-MM-DD Author Last name, first name Remarks First edition
Module Objectives
Upon completion of this module, you should be able to:
Describe the role of the BSS in the End-user GPRS QoS and the dependencies between Global (BSS+GSS) and BSS GPRS QoS on one hand and between BSS GSM and GPRS QoS on the other hand
113
Module Objectives [cont.]
114
Table of Contents
1 2 3 4 5 6 Distinction between BSS/BSS+GSS/End-user GPRS QoS Implementation of GPRS QoS Profiles at BSS Level Source of Information for GPRS QoS Monitoring Dependencies between BSS GSM and GPRS QoS Impact of GMM/SM Signaling on BSS QoS Interpretation Indicators Classification Page 7 13 26 36 39 43
115
Table of Contents [cont.]

116
1 Distinction between BSS/BSS+GSS/End-user GPRS QoS
117
Different Levels of QoS BSS

BTS BSC MFS
GPRS Backbone
SGSN
GGSN
Packet Data Network
TE
Um
Abis
Ater
Gb
Gn
Gi
BSS QoS BSS+GSS QoS End-user QoS

118
EGPRS QoS Role of the BSS in GPRS QoS Monitoring EVOLIUM Introduction to GPRS and E-GPRS QoS Monitoring - B10 All Rights Reserved Alcatel-Lucent 2008
3 types of QoS are involved in the overall analysis of the GPRS QoS : Radio QoS It must be considered from the R interface to the Gb interface. It belongs mainly to the radio environment as well as the proper functioning of the PCU implemented inside the BSS. It is defined in terms of throughput, service precedence, RLC reliability mode, transfer delay. GPRS QoS It must be considered from the R interface (MS access to the GPRS) to the Gi interface (exit from the GPRS Network). It includes the Radio QoS and the GSS QoS. It is defined in terms of service precedence, transfer delay, mean and peak throughputs and reliability. End-User QoS This is the QoS as the user feels it. It includes the GPRS QoS as well as the QoS of the external networks and their connection to the GPRS GSS. Even if it does not belong to the operator, it should still be monitored as it can generate customer complaints.
Dependencies between QoS Levels
End-user QoS BSS+GSS QoS BSS QoS
119
A bad BSS GPRS QoS (Radio QoS) will lead to a bad GPRS QoS and a bad End-user QoS. A bad End-user performance can be due to a bad GSS behaviour without any BSS GPRS QoS degradation. A bad End-user QoS can also be due to a bad PDN performance.
Impact of UE
Different data applications are multiplexed over the GPRS radio layers: FTP, WEB/HTTP, WAP, MMS, etc. Data applications have very different traffic characteristics (amount of data, duration between LLC PDUs) leading to different ways of triggering radio layers algorithms Therefore Parameters setting in the GPRS network will lead to different performance according to the service
1 1 10
A bad end-user QoS can also be due to the setting of TE protocol layers parameters which can not have optimal values to get the best GPRS performance.
Impact of UE: Example

Data applications use TCP/IP protocol layers which have a great impact on the end-user QoS
FTP above TCP/IP layers
FTP TCP IP PPP PPP relay SNDCP P LLC RLC MAC RF RLC MAC RF SNDCP P LLC BSSGP NS L1 BSSGP NS L1 relay GTP UDP IP-Gn L2 L1 IP GTP UDP First IP router IP-Gn L2 L1 Last IP router relay IP IP relay IP IP relay
relay
(*)
BSS TE (PC ,PDA ) MS R Um Gb SGSN Gn
GGSN Gi
TCP data segment Possible repartition on the end to end path of the TCP flight size TCP acknowledgement
1 1 11
(*) this graphical representation is used to express the fact that many data segments are currently waiting to be transmitted on the represented link and are stored in buffers of the device handling the link . It doesnt mean that simultaneous segments are being transmitted. All Rights Reserved Alcatel-Lucent 2008
A bad end-user QoS can also be due to the setting of TE protocol layers parameters which can not have optimal values to get the best GPRS performance.
Understand BSS GPRS QoS

GPRS QoS is not an isolated topic:
It is necessary to use GSM indicators in order to complete the analysis of GPRS QoS It is necessary to use GSM counters in order to complete the analysis of the impact of GPRS traffic on GSM QoS
The BSS QoS does not allow to have a complete understanding of the end to end QoS seen by the user
Indeed, upper protocol layers (TCP for example) have a great impact on the global QoS The GSS also has a great impact on the global QoS
1 1 12
2 Implementation of GPRS QoS Profiles at BSS Level
1 1 13
Data Services
Media
Directories Mobile Office
Voice (!) E-mail Agenda IntraNet/InterNet Corporate Applications Database Access Yellow/White Pages International Directories Operator Services
Always-on
Fun
Games (Hangman, Poker, Quiz, ) Screen Saver Ring Tone Horoscope Biorhythm
Music Transportation
Flight/train Schedule reservation Downloading of music files or video clips
News (general/specific)
International/National News Local News Sport News Weather Lottery Results Finance News Stock Quotes Exchange Rates
Location services
Traffic Conditions Itineraries Nearest Restaurant, Cinema, Chemist, Parking, ATM, etc..
Vertical application
Traffic Management Automation Mobile branches Health
M-commerce
Physical
on-line shopping on-line food
Non physical
on-line Banking Ticketing Auction Gambling Best Price e-Book
1 1 14
Different services can be found in the 3 categories: Teleservices provide the full capabilities for communications by means of a terminal equipment, network functions and possibly functions provided by dedicated centers. Multimedia teleservices support the transfer of several types of information. M-commerce: Non-physical = electronic goods (e-banking, e-flight ticketing, etc). Physical = electronic payment of physical goods (food, supplies, hardware, etc). Retrieval services Provide the capability of accessing information stored in data base centers. The information is sent to the user on demand only. An example of one such service in the Internet's World Wide Web (WWW). Messaging services Offer user-to-user communication between individual users via storage units with store-and-forward mailbox, and/or message handling (e.g., information editing, processing and conversion) functions; Conversational services Provide bi-directional communication by means of real-time (no store-and-forward) end-to-end information transfer from user to user. An example of such a service is the Internet's Telnet application; Tele-action services Characterized by low data-volume (short) transactions, for example credit card validations, lottery transactions, utility meter readings and electronic monitoring and surveillance systems. Distribution services Characterized by the unidirectional flow of information from a given point in the network to other (multiple) locations. Examples may include news, weather and traffic reports, as well as product or service advertisements; Dispatching services Characterized by the bi-directional flow of information from a given point in the network (dispatcher) and other (multiple) users. Examples include taxi and public utility fleet services; Conferencing services Provide multi-directional communication by means of real-time (no store-and-forward) information transfer between multiple users.
QoS Requirements - Exercise

Different applications require different QoS
Exercise: find qualitatively the QoS requirements of the following data services
Service web video streaming ftp location based advertising audio streaming email wap fax e-commerce interactive games SMS Transfer Delay Throughput Reliability
+: low sensitivity, ++: medium, +++: high
1 1 15
Data applications have very different traffic characteristics (amount of data, duration between LLC PDUs) leading to different ways of triggering radio layers algorithms. This has a direct impact on the follow-up of some QoS indicators at OMC-R level: number of DL/UL TBF establishment requests, DL/UL TBF duration, coding scheme distribution.
GPRS QoS Profile

2 R97/98 GPRS QoS attributes supported in the Alcatel-Lucent BSS
Precedence Class: relative importance of service under congestion; 3 values are defined Reliability Class: mainly linked to Ack / Not Ack modes at RLC and LLC levels and within the backbone network; 5 values are defined
4 R99 GPRS QoS attributes supported in the Alcatel-Lucent BSS

Traffic Class: Conversational, Streaming, Interactive, Background Traffic Handling Priority: From 1 (highest priority) to 3 (lowest priority) Guaranteed bit rate for Uplink: From 0 to 8640 kbps Guaranteed bit rate for Downlink: From 0 to 8640 kbps
1 1 16
Precedence classes: high, normal, low Delay classes: class 1 (average delay<0.5 s, 95% delay<1.5 s) class 2 (average delay<5 s, 95% delay<25 s) class 3 (average delay<50 s, 95% delay<250 s) class 4: not specified = best effort The Mean Throughput class range is smaller than the Peak Throughput class one because: The later is considered per interface (the purpose being to maximize the use of the transmission capacity over each interface according to its physical characteristics). The former is considered end to end and must take into account the weaker interface characteristics, the air interface one. Reliability: Five classes are defined according to the tolerable BER (from 1 = lowest BER required to 5 = highest tolerated BER and no acknowledgement or error checking).
ETSI Principles
ETSI R97 principles:
GPRS QoS is negotiated between the MS and the SGSN, at PDP context activation The BSS is not involved in QoS negotiation
But the BSS should be able to do its best...
No absolute QoS can be guaranteed by the BSS The SGSN and the GGSN play the main role in QoS management
ETSI R99 principles

As in R97, the QoS negotiation is initiated by the MS at the PDP context activation The BSS is involved in this negotiation if EN_PFC_FEATURE= Enabled
Then a Packet Flow Context is created
The BSS can guarantee the required QoS or downgrade to Best Effort
E.g. in case of lack of resource
1 1 17
QoS Profile at BSS Level BSS

BTS BSC MFS
GPRS Backbone
SGSN
GGSN
Packet Data Network
TE
Um
Abis
Ater
Gb
Gn
Gi
Radio QoS GPRS QoS End-user QoS

1 1 18
Throughput: not managed by Alcatel-Lucent BSS. Best effort is supported. Service precedence: partly managed by Alcatel-Lucent BSS. RLC reliability mode: managed by the BSS. Transfer delay: not managed by Alcatel-Lucent BSS. Best effort is supported. See next pages for details.
Precedence
Precedence:
Defines the priority for maintaining service in a congestion situation Specified on:
The DL path: in the DL BSSGP PDU header The UL path: radio priority in Packet resource request (2-phase access)
If EN_PFC_FEATURE=Disabled
Not managed in the Alcatel-Lucent BSS, but the operator can configure, in case of GPRS cell configured with a Master PDCH the persistence level of each radio priority and therefore control the uplink TBF establishment delay
If EN_PFC_FEATURE=Enabled
The precedence is taken into account for the Interactive and Background classes It impacts the way of scheduling the RLC data blocks at MS and TRX level (Weighted Round Robin algorithm)
1 1 19
Service precedence: The management of the persistence levels in the Alcatel-Lucent BSS is the following. When there is a PBCCH allocated in the cell, the MFS broadcasts on the PBCCH four persistence levels P(i), defined by O&M, each of them corresponding to a given radio priority i (i = 1, 2, 3, 4), where P(i) {0, 1, 14, 16}. For each access attempt, the MS draws a random value R in the set {0, 1, 14, 15}. The MS is allowed to send a Packet Channel Request message only if the P(i), where i is the radio priority of the TBF being established, is lower or equal to R. This method allows the operator to differentiate the access probability of the MSs as a function of their radio priority. There is no preemption of an on-going TBF to establish a new one with a higher service precedence level.
Reliability
Reliability:
Defines the transmission characteristics that are required by an application in terms of SDU loss probability, duplication of SDU, mis-sequencing of SDU or corruption of SDU Implemented at BSS level as RLC Acknowledged (Ack) mode or RLC Not acknowledged (Nack) mode Specified on
The DL path: in the DL BSSGP PDU header The UL path: in Packet resource request (2-phase access)
Default mode: Ack
1 1 20
Traffic class with EN_PFC_FEATURE=Enabled

Conversational class (not supported)
Video conference
Streaming class
Live video retransmission The MFS reserves radio and transmission resources at the PFC creation
+
Delay sensitive
Data Integrity sensitive
Interactive class
Web browsing No resource reservation RLC data blocks are scheduled with a certain priority
Background class
email, FTP No resource reservation RLC data blocks are scheduled with a low priority
1 1 21
Conversational class: The most well known use of this scheme is telephony speech (e.g., GSM). But with the Internet and multimedia, a number of new applications will require this scheme, for example voice over IP and video conferencing tools. Real-time conversation is always performed between peers (or groups) of live (human) end users. This is the only scheme where the required characteristics are strictly given by human perception. Streaming class: When the user is looking at (listening to) real time video (audio) the scheme of real time streams applies. The real time data flow is always aiming at a live (human) destination. It is a one way transport. Interactive class: When the end user, that is either a machine or a human, is on line requesting data from a remote equipment (e.g., a server), this scheme applies. Examples of human interaction with the remote equipment are: web browsing, data base retrieval, server access. Examples of machines interaction with the remote equipment are: polling for measurement records and automatic data base enquiries (tele-machines). Background class: When the end user, that typically is a computer, sends and receives data files in the background, this scheme applies. Examples are background delivery of E-mails, SMS, download of databases and reception of measurement records.
Traffic Handling Priority

THP:
From 1 (highest priority) to 3 (lowest priority)
THP1 THP2 THP3
The THP is associated only with the Interactive class (if EN_PFC_FEATURE=Enabled)
1 1 22
According to 3GPP TS 23.107, the Traffic Handling Priority specifies the relative importance for handling of all SDUs belonging to the bearer compared to the SDUs of other bearers.
Guaranteed Bit Rate

UL/DL Guaranteed bit rate (R99)
From 0 to 8640 kbps 3 ranges are usable with 3 different step sizes
Min 0 kbps 64 kbps 576 kbps Max 63 kbps 568 kbps 8640 kbps Step size 1 kbps 8 kbps 64 kbps
The Guaranteed Bit Rate (GBR) is associated with the Streaming class, if
EN_PFC_FEATURE = Enabled at BSC level and EN_STREAMING = Enabled at cell level
1 1 23
According to 3GPP TS 23.107, the Traffic Handling Priority specifies the relative importance for handling of all SDUs belonging to the bearer compared to the SDUs of other bearers.
Alcatel-Lucent QoS Offer - R97/98 QoS Compliance
ETSI R97/98 QoS attributes

Delay class
(4) Best Effort 1, 2 or 3 1,. 2 or 3 1,. 2 or 3 1,. 2 or 3
Alcatel-Lucent Offer
Resulting QoS class Best-Effort Best-Effort Best-Effort Normal Premium
Precedence class
any (3) Low priority Normal, High priority (2) Normal priority (1) High priority
Mean throughput class

any any Best Effort specified, except BE specified, except BE
Reliability class:
as required by the MS
BE = Best-Effort
1 1 24
The QoS attributes are associated with a PDP context performed by an R97/98 MS. The five QoS parameters of the standard define more than 60 combinations! This is too much and must be simplified: Too complex to implement, Many of the combinations have no meaning! The standard "allows" simpler QoS implementations. - = any value. In green, the main criterion for the definition of the resulting QoS. Alcatel-Lucent implementation: 3 QoS classes are defined: Best effort: Inexpensive, comparable to the Internet (no commitment). Ideal for foraging on the internet. Normal: Comparable to an intranet. Premium: Expensive, high performance.
Alcatel-Lucent QoS Offer - R97/98 QoS Mapping into R'99 QoS

There is a mapping between R'99 Traffic class and Alcatel-Lucent QoS class
R'99 Traffic class Conversational Streaming Interactive Interactive Interactive Background
Traffic handling priority 1 2 3 -
R97/98 Bearer QoS class Premium Premium Premium Normal Normal Best Effort
1 1 25
The mapping of R97/98 QoS attributes to R'99 QoS is applicable in the following cases: hand-over of PDP context from GPRS R97/R'98 SGSN to GPRS R'99 or UMTS SGSN. when an R'99 MS performs a PDP context activation in an R'99 SGSN with an R'97/98 GGSN. When GGSN responds to the PDP Context Activation, mapping of the changed R97/98 QoS attributes received from the GGSN to R99 QoS attributes is performed in the serving SGSN. when the SGSN has received an R97/98 QoS subscribed profile, but the MS is R'99. The mapping of R'99 QoS attributes to R'97/98 QoS is applicable in the following cases: the PDP context is handed over from GPRS R'99 to R'97/R'98. when an R'99 MS performs a PDP context activation in an R'99 SGSN while the GGSN is R'97/98. In this case the SGSN shall perform mapping of the R99 QoS attributes to the R97/98 QoS attributes; when the SGSN sends user data to the BSS for an R'99 MS. when the SGSN has received R'99 QoS subscribed profile but the MS is R'97/98. in the new SGSN, during an inter-SGSN RA_update procedure, or an inter-system change, on receipt of the R'99 QoS attributes from the old SGSN.
3 Source of Information for GPRS QoS Monitoring
1 1 26
PM Counters
COUNTERS
BSC
MFS
Gb
HLR
SGSN
GPRS Backbone
Packet Data Network
GGSN
1 1 27
PM counters retrieval and post-processing is the cheapest solution.
Trace User Data Transfer

Transmission plane
Application IP / X.25 SNDCP LLC RRM RLC MAC GSM-RF SNDCP LLC RRM RLC MAC GSM-RF
Relay Relay
IP / X.25 GTP UDP/TCP IP L2 L1 GTP UDP/TCP IP L2 L1
Air traces
Gb traces
BSSGP NS L1bis
BSSGP NS L1bis
MS
Um
BSS
Gb
SGSN
Gn
GGSN
GCH traces
RRM RLC MAC L2-(M)EGCH L1-GCH Ater(mux)
Relay
BSSGP NS L1bis
Relay
GSM-RF
L2-(M)EGCH L1-GCH BTS
Abis
MFS
1 1 28
Interfaces traces are of good complementary information but expensive: used for problem investigation used when lack of PM counters
Trace Signaling
Signaling plane with CCCH use
GMM/SM GMM/SM
Relay
GTP UDP IP L2 L1
GTP UDP IP L2 L1
Air traces
Gb traces
LLC
LLC BSSGP NS L1bis
Relay
BSSGP NS
RRM
BSCGP / RRM
GSM-RF
GSM-RF
L1bis
MS
Um
BSS
Gb
SGSN
Gn
GGSN
GCH traces
BSC Relay
GSL traces
BSSGP NS
Relay
BSCGP
RR L2-RSL L1-RSL BSC
BSCGP L2-GSL L1-GSL
Relay
GSM-RF
L2-RSL L1-RSL BTS
L2-GSL L1-GSL MFS
L1bis
Abis
Ater(mux)
1 1 29
2 GSL at 64Kbit/s per GPU RSL: refer to the Dimensioning rules for GSM
End-User QoS
End-user performances are obtained through measurements carried out for different end-user services:
Ping FTP WAP WEB (HTTP)
Traces must be performed at both Air interface and Application levels
These performances must be interpreted with a maximum of information concerning the context of the measurements
Use of a database to register performance results
1 1 30
FTP tests: Static cell measurements: DL transfer of an uncompressible file of 500 KB size UL transfer of an uncompressible file of 200 KB size Drive measurements: DL transfer of an uncompressible file of 1MB minimum size UL transfer of an uncompressible file of 200 KB minimum size PING Tests: Series of 100 pings HTTP tests: Static cell and drive measurements: HTTP browsing of an html page of 400 KB minimum size
End-User QoS Measurements Principles

GPRS performance tests performed
with PDN (real end-user QoS) without PDN (BSS+GSS QoS: use of a local server on the Gi interface just after the GGSN)
Use of a too old or too new mobile can be risky

Reference mobiles are Nokia N95 for B10 features
Use of the NEMO software (Anite)

to pick up the transferred frames to calculate the throughput at RLC layer to monitor lower layers
Use of Wireshark software

to detect IP retransmissions, TCP lost frames, to monitor application layers (IP, FTP, etc.)
Use of database to register performance results
1 1 31
NOKIA 6220 and 6230 are EDGE mobiles. Tests configuration set-up needs some specific data for like: APN of the operator to be declare in the Properties of the Modem connection on client PC (the one with Agilent NITRO installed) IP address of the Internet/WAP gateway or of the Application server connected to GGSN DNS server address if necessary user name and password for GPRS connection Name or the URL of the WEB page to be downloaded for HTTP tests
End-User QoS Measurements Results

Applications server accessibility (PING)
Server accessibility success rate Round Trip Time (RTT) in seconds per ping command
FTP
FTP session success rate Application layer throughput in kbit/s per file
WAP
WAP gateway access time WAP page download success rate Application throughput
HTTP (WEB)
WEB page download success rate Application throughput
1 1 32
MMS tests: MMS emission success rate MMS notification success rate MMS reception success rate MMS time to send Time to receive the MMS notification Time to retrieve the MMS Optional RLC/MAC statistics during end-user QoS tests: CS distribution : % of CSx RLC blocks and total time of CSx usage CS changes: number of CS changes per minute Retransmissions: % of RLC blocks retransmitted BLER: % of RLC blocks in error Usually QoS indicators giving throughput or time values are provided with 4 detailed indicators: minimum maximum average standard deviation
GSS QoS
Counters:
in the SGSN in the GGSN in the HLR
Traces:
BSS-SGSN interface (Gb) GGSN-PDN interface (Gi) intra-GSS interface (Gn)
1 1 33
BSS QoS
Counters:
in the MFS (specific to GPRS) in the BSC (in relation to GSM)
Tool chain = OMC-R + NPO
Traces:
Air interface (Um) Ater interface (GCH) MFS-BSC interface (GSL) BSS-SGSN interface (Gb)
Trace MS + NEMO
Protocol analyzer + COMPASS

(K12 Viewer)
1 1 34
BSS QoS Measurements Principles

OMC-R network statistics with OMC-R network counters
Packet domain
BTS
Abis
Other PLMN
FireFire wall
BSC
Ater
MFS
Gb
SGSN SGSN
Gn
GGSN GGSN
Core network Internet/ Internet / Intranet
Application layer GPRS Air Interface Statistics

EGPRS MS NOKIA N95
SERVER e.g. FTP, HTTP
Application Presentation Session Transport Network
IP layer LLC layer RLC/MAC layer Physical layer

AMI Compass GNNettest Protocol Analyzer K1205
Measurement Trace SW Anite NEMO
Data Link Physical OSI Layers
Gb Statistics
1 1 35
For the Air interface trace: Use of a too old or too new mobile can be risky Reference mobiles are Sagem (OT290), Motorola (T280), NOKIA ( 6230) Use of a PC preferably with Windows 2000 Use of the Agilent software E6474A Nitro Use of end-user QoS monitoring tool (DEUTRIP, DMS) For the GCH, GSL, Gb interface trace: Use of a protocol analyzer with the Alcatel-Lucent BSCGP stack The reference analyzer is Tektronix K1205 v2.40 Use of a post-processing tool The reference tool is COMPASS GPRS
4 Dependencies between BSS GSM and GPRS QoS
1 1 36
Impacts
GSM QoS
GPRS QoS
1 1 37
Bad radio conditions like coverage or interference problems degrading GSM QoS also provoke BSS GPRS QoS problems. Bad BSS GPRS performance is not always correlated to GSM QoS problems: Congestion can be due to a lack of resource specific to GPRS. A low throughput can be due to a bad setting of radio algorithms specific to GPRS. On the other hand GPRS traffic can induce or worsen GSM QoS performance: PS traffic can increase CS congestion. PS signaling using CCCH channels can induce a PS AGCH and/or PCH overload and eventually an SDCCH congestion.
Exercise
Among the following list of typical problems in a GSM network, find the ones having an impact on BSS GPRS QoS
Typical BSS GSM problem Coverage Interference path unbalanced at cell fringe TRX HW degradation Abis MW problem A interface congestion SDCCH congestion TCH congestion Rate of LU/call too high Handover failure too high Impact on BSS GPRS QoS
Time allowed: 10 minutes
1 1 38
5 Impact of GMM/SM Signaling on BSS QoS Interpretation
1 1 39
GPRS Protocol Layers
IP
User data in IP packets
GMM signaling messages
SNDCP
SM
GMM
SM signaling messages
GMM
SM
SNDCP
LLC RLC
LLC frames
LLC PCU
relay
RLC
BSSGP
BSSGP
Frame relay Physical layer SGSN
MAC Physical layer

MS
relay
Physical layer L2-GCH L1-GCH BTS
MAC
L2-GCH L1-GCH
Frame relay Physical layer
Um
1 1 40
Abis/Ater
MFS
Gb
For a PS service the BSS simply relays the LLC frames between the MS and the SGSN. GPRS GMM/SM signaling messages are transferred through the BSS as User data. Therefore a BSS Data transfer procedure (called TBF) is carried out either to transfer user data or to transmit MS-SGSN signaling message. BSS GPRS QoS indicators have to be carefully interpreted especially in the case of a high load of GPRS signaling. BSS GPRS Protocol (BSSGP) Its function is to relay LLC frames over the Gb interface, with no guarantee of integrity (relaying user data and GMM / SM messages: session, RA_update and paging procedures). There is 1 BSSGP frame for 1 LLC frame.
GMM/SM Signaling Load

There are a lot of GPRS signaling message in case of:
cell update RA update (Normal, Periodic)
There are less GPRS signaling message in case of:

GPRS attach GPRS detach PDP context activation PDP context de-activation
1 1 41
BSS GPRS QoS indicators must be carefully interpreted knowing that TBFs are used for both data and signaling transfer. Gb traces might be needed for a better understanding of QoS problems.
6 Indicators Classification
1 1 42
QoS Family
Traffic Load Quality Of Service Evaluation of the rate of success or failure per interface:
(Radio, AterMux, Gb)
or per telecom procedure:

TBF UL/DL establishment, UL/DL Data transfer, radio resource allocation or re-allocation
Resource Availability and Usage

Abis interface (abis nibbles) AterMux interface (GCH, LapD) Gb interface (PVC, Bearer Channel) GPU object (CPU and DSP usage)
1 1 43
QoS Sub-families
GPU
1 1 44
Self-assessment on the Objectives

Please be reminded to fill in the form Self-Assessment on the Objectives for this module The form can be found in the first part of this course documentation
1 1 45
Exercise
A customer complains about the fact that transferring a file from his laptop to his home computer using GPRS connected to internet takes too much time. What will you do if you have to investigate this customer complaint?
1 1 46
End of Module Role of the BSS in GPRS QoS Monitoring
1 1 47
12
Section 1 EGPRS QoS

Module 2 Recalls on the Main BSS GPRS Telecom Procedures
Blank Page
122
EGPRS QoS Recalls on the Main BSS GPRS Telecom Procedures EVOLIUM Introduction to GPRS and E-GPRS QoS Monitoring - B10
Module Objectives
Describe the main BSS GPRS procedures and algorithms having an impact on QoS
123
124
Table of Contents
1 GPRS Logical Channels 2 TBF: Data Transfer Procedure between the MS and the BSS 3 Gb: BSSGP Protocol and Frame Page 7 9 17
125

126
1 GPRS Logical Channels
127
1 GPRS Logical Channels
Organization
physical channel control channel logical channel traffic channel signaling associated control channel logical channel category
PDCH
Master PDCH
Slave PDCH
Primary MPDCH
Secondary MPDCH
PBCCH
PCCCH
PTCH
PTCCH
PPCH
128
PAGCH
PDTCH
PACCH
2 TBF: Data Transfer Procedure between the MS and the BSS
129
Radio Resources
PDCH 1
B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 B11
PDCH 2
B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 B11
PDCH 3
B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 B11
TBF with TFI = 5
TBF with TFI = 17
TBF with TFI = 24
Temporary Block Flow (TBF): unidirectional flow of data between the MS and the MFS for the transfer of one or more LLC PDUs Radio resources allocated to a TBF are:
DL TBF UL TBF
1 2 10
A Temporary Block Flow is a temporary, unidirectional physical connection across the Um interface, between one mobile and the BSS. The TBF is established when data units are to be transmitted across the Um interface. It is released as soon as the transmission is completed.
TBF Phases
The TBF procedure can be split as represented below
establishment
progress
release
Radio resources to be used during the data transfer are reserved by the BSS and are assigned to the MS
Data transfer through RLC blocks transmission
Radio resources are freed
During an on-going TBF (progress) in one direction, a TBF in the other direction can be established quicker than usually
1 2 11
EGPRS QoS Recalls on the Main BSS GPRS Telecom Procedures EVOLIUM Introduction to GPRS and E-GPRS QoS Monitoring - B10 All Rights Reserved Alcatel-Lucent 2008
UL TBF, Delayed Final PUAN without Extended UL TBF

In order to establish a DL TBF faster the release of a UL TBF can be delayed
T_DELAYED_FINAL_PUAN is the time during which a DL TBF can be established using the UL TBF radio resources before they are freed
T_DELAYED_FINAL_PUAN
UL TBF
establishment
progress
release default: 400ms
1 2 12
UL TBF, Delayed Final PUAN with extended UL TBF

Extended UL TBF mode
T_MAX_EXTENDED_UL default : 2 seconds
UL TBF
TBF establishment
TBF active
TBF extended
release
UL TBF is maintained during T_MAX_EXTENDED_UL after the last block ( CV=0) has been acknowledged
1 2 13
DL TBF, Delayed DL TBF Release

The release of a DL TBF is delayed after all the DL RLC blocks have been transferred in order to be able to:
establish a UL TBF faster resume the DL data transfer (new LLC PDU coming from the SGSN) without having to establish a new DL TBF
T_NETWORK_RESPONSE_TIME default : 1.6 seconds
DL TBF
TBF active
TBF delayed
progress
1 2 14
release
DL TBF, Fast Establishment

A DL TBF can be re-established faster during a short time after a DL TBF release using the radio resources of the previous TBF
It is possible because the MS still monitors the radio resources during timer T3192 after the DL TBF has been released
T3192 default : 500ms Fast DL TBF establishment on PACCH possible
DL TBF
TBF active
TBF delayed
release
1 2 15
DL TBF, Establishment in DRX Mode

After T3192, a DL TBF has to be established on Control Channels:
faster during DRX_TIMER_MAX when the MS is in Non-DRX mode slower afterwards when the MS is in DRX mode
DRX_TIMER_MAX T3192 default : 2 seconds
DL TBF
TBF active
DL TBF establishment possible TBF delayed TBF release on AGCH, or PCH of MS paging group
on PCH of MS paging group
1 2 16
3 Gb: BSSGP Protocol and Frame
1 2 17
L1bis
Bearer Channels: consecutive n timeslots of a 2Mb/s link
with n = 0 31
Gb interface MFS BSSGP NS (NSC) NS (SNS)

PCM BC i BC x PCM
SGSN BSSGP NS (NSC) NS (SNS) L1

BC j BC y
L1
1 2 18
The Gb physical interface is made up of one or more 64-Kbit/s channels on one or more physical lines at 2048 Kbit/s. Both individual 64-Kbit/s and n*64-Kbit/s channels are supported by the MFS. A Bearer Channel (BC) is an n*64-Kbit/s channel (1 n 31). NB: among the 16 PCM links offered per PCU, only 8 are dedicated to the Gb interface, 4 for the upload and 4 for the download. The maximum point-to-point transfer capacity over the Gb interface in one direction is then 31*64 Kbit/s*4 = 8192 Kbit/s.
Network Service
The Sub-Network Service (SNS):
Routing of the BC onto the Frame Relay, thanks to Permanent Virtual Connections (PVC) Only 1 PVC per BC
Gb interface
MFS BSSGP
Frame Relay Network
SGSN BSSGP
PVCa DLCIx PVCm DLCI
NS (NSC) NS (SNS)
L1
NS (NSC) NS (SNS)
L1
PVCb DLCIy
1 2 19
PVCn DLCI
Concept of PVC: A PVC is a synchronous access line, semi-permanent connection. The PVC allows the multiplexing on a BC. It is not an end to end link between the MFS and the SGSN. At MFS side a PVC is identified by its Data Link Connection Identifier (DLCI) which is independent from the one defined at SGSN side. DLCI 0 is used for signaling. There is one PVC per BC. The SNS layer, layer 2.1 in the OSI model, offers the Frame Relay technology. The NSC layer, layer 2.2 in the OSI model, offers the point to point data transfer in both directions. The PVC standards are not specific to GPRS. Please refer to the Frame Relay Forum organization, the ITU-T and ANSI (T1S1.1 workshop) specifications.
Network Service [cont.]

The Network Service Control (NSC)
Manages n Virtual Connections (NS-VCs) per GPU, with 2 n < 120 Share the load within 1 GPU
Gb interface
MFS BSSGP
NSVC NSVCi=11
SGSN BSSGP
NS (NSC) NS (SNS)
L1
NSVC NSVCi=12
NS (NSC) NS (SNS)
L1
1 2 20
Concept of NS-VC: A NS-VC is an end to end logical link between the MFS and the SGSN. Each NS-VC is identified by its NSVCI which has an end to end significance on the Gb interface. There is a one to one relation between one NS-VC and one PVC. Sub-network service function: ordered data transfer. The main functions of the NSC layer (2.2 layer) are: sequencing of the data transmission, flow control, lost frame management. When a MS performs a GPRS ATTACH, it is allocated on one NS-VC and only one. There is no change of NSVC afterwards, until cell reselection or GPRS DETACH.
Network Service [cont.]

Concept of Network Service Entity (NSE):
1 NSE groups several NS-VCs ( 2 NS-VCs per NSE) 1 NSE = 1 GPU The NSE is identified by an NSEi which has an end-to-end significance over the Gb interface Load sharing: the NS-VCs of the NSE are shared among the BVC's associated to the NSE
NSE NSEi = 1
BSSGP NS (NSC)
PCU
NSVC NSVCi=11
NS (SNS) L1
NSVC NSVCi=12
1 2 21
Note: for MM purposes, the SGSN needs a 1:1 correspondence between the NSEI and the RAI.
BSS Cell Cell Cell Cell
BSSGP layer
BVC
BVC
BVC
BVC
NSC sub-layer NS-VC
NSE NS-VC NS-VC
NSE NS-VC
SNS sub-layer
PVC
PVC
PVC
PVC
BC Physical layer 2 Mbit/s
BC
BC
BC
2 Mbit/s
BSSGP
BSSGP Virtual Connection (BVC)
End-to-end link between the MFS and the SGSN 1 BVC = 1 cell n BVC within 1 GPU
BVCi=2 BVCi=1 BVCi=n BVCi=2 BVCi=1 BVCi=n
Gb interface
BSSGP NSC SNS L1 MFS

1 2 22
BSSGP NSC
NSVC
SNS L1 SGSN
Two types of BVC: point-to-point BVC dedicated to the PS traffic of one cell (BVCi 0). signaling BVC (BVCi=0) which is the signaling circuit of all the point to point BVCs of one NSE (GPU). For NM reason, the duplet BVCi/NSEi must be unique within an SGSN.
To activate a new cell in an SGSN, it is only needed to add a new BVCi in an NSEi. No update of the NSEi information is necessary.
Gb Interface - Manageable Entities

BSS side GPRS Core Network side
BVCI=2
BVCI=2 BVCI=1 BVCI=3
PCM BC
NSVC1
PCM PVC BC NSE1
BVCI=1
BSC1
NSE1 PCM BC NSVC2 PCM PVC BC
BVCI=3
F.R Network
PCM BC
BVCI=4 BVCI=6
BVCI=5 BVCI=4 NSE2
BVCI=5
NSVC3
PCM PVC BC
BSC2
NSE2 PCM BC NSVC4 PCM PVC BC
BVCI=6
SGSN
1 2 23
Number of PDCH per GP board in the MFS Evolution B10:
(note 1 and note 2: with Gb over IP only)
Gb Interface - Protocol Model and Entities

BSS side GPRS Core Network side
BSC1
BSS GPRS Protocol BVC BSS GPRS Protocol
(BSSGP)
(BSSGP)
BSC2
Network Service Control
(NSC)
Sub-Network Service
NSE
Network Service Control NS-VC
(NSC)
Sub-Network Service
(SNS) Physical layer

Packet Control Unit function (PCU)
1 2 24
BC
PVC
(SNS) Physical layer
Frame Relay
SGSN
Dimensioning rules MFS Evolution B10:
Note 1:Both maximum number of E1 and maximum number of GP for stand-alone MFS cannot be reached simultaneously. The operator has to make the following choice at commissioning: - 16 E1 with up to 8 GP with one shelf and up to 16 GP with two shelves. - 12 E1 with up to 9 GP for the first shelf and up to 21GP with two shelves. Note 2: In case of MFS in centralized clock mode, two 2 E1 ports are reserved for clock distribution. In this case the maximum number of E1 is reduced to 14.
BSSGP Frame
One BSSGP PDU includes one and only one LLC PDU
BSSGP frame LLC frame
BVCI
BSSGP header
TLLI
GPRS Traffic or signaling
LLC header
LLC payload
1 2 25
In case of data traffic the LLC PDU contains an SNDCP PDU. In case of signaling, the LLC PDU contains a GMM or an SM message.

1 2 26
End of Module Recalls on the Main BSS GPRS Telecom Procedures
1 2 27
13
Section 1 EGPRS QoS

Module 3 Description of the Main BSS GPRS QoS Counters and Indicators
Blank Page
132
EGPRS QoS Description of the Main BSS GPRS QoS Counters and Indicators EVOLIUM Introduction to GPRS and E-GPRS QoS Monitoring - B10
Module Objectives
Interpret the BSS GPRS QoS indicators attached to each BSS GPRS procedure or algorithm having an impact on QoS Interpret the BSS GPRS PM counters used in the computation formulae of QoS indicators
133
134
Table of Contents
1 2 3 4 5 6 7 Data Transfer Establishment Data Transfer Progress Data Transfer Release MS Sessions / Transfers Resource Usage CS and MCS Adaptation Cell Reselection Page 7 56 88 118 127 165 179
135

Page
136
1 Data Transfer Establishment
137
TBF Establishments
Data Transfer establishment
UL TBF establishment
DL TBF establishment
MS in MM Ready state
MS in MM Standby state PS Paging
MS in PIM
MS in PTM (DL TBF)
MS in PIM
MS in PTM (UL TBF)
on CCCH
on PACCH
on CCCH
on PACCH UL TBF running
1-Phase
or
2-Phase
138
DL TBF running
DRX
or
Non-DRX
or
T3192 running
There are 3 types of UL TBF establishment: 1-phase access on CCCH : when the MS is in Packet Idle Mode and the MS does not need more than 1 PDCH and wants to transfer blocks in RLC acknowledge mode. 2-phase access on CCCH : when the MS is in Packet Idle Mode and the MS needs more than 1 PDCH or wants to transfer blocks in RLC unacknowledge mode. During a DL TBF: when the MS is in Packet Transfer Mode in DL. There 4 types of DL TBF establishment: On CCCH DRX mode: when the MS is in Packet Idle Mode and the MS is listening to all PCH channels of its CS paging group. On CCCH Non-DRX mode: when the MS is in Packet Idle Mode and the MS is listening to all AGCH channels. During a UL TBF: when the MS is in Packet Transfer Mode in UL. When T3192 is running: when a DL TBF has been released at the MS side and before the previously used radio resources are released (at T3192 expiry).
UL TBF Establishment 1-Phase Access on CCCH, Success

MS (EGPRS Packet) Channel request RACH BTS Channel required (TA) TA calculation BSC MFS
GPRS EGPRS
Channel request (TA)

GCH allocation
P62c
P62d
Immediate assignment MS switches AGCH on assigned PDCH USF Scheduling PDTCH RLC data block PDTCH
Imm. assign. command Channel assignment UL (IA)

PDCH, TFI, USF, TAI, TA, CS (MCS, EGPRS window size)
P49
USF Scheduling
T_USF_Scheduling_AGCH expiry T_GPRS_ASSIGN_AGCH
Contention resolution
RLC data block TLLI, TFI Packet UL Ack/Nack TLLI, TFI
P30c
GPRS
P30d
EGPRS
Packet UL Ack/Nack PACCH

139
In case a Channel Request or an EGPRS Packet Channel Request is received from the mobile station, an Immediate Assignment message is sent to the MS assigning the radio resources (the PDCH id, the USF value, the TFI value, the TAI value). In case a Channel Request is received on a RACH, the BSS does not know the multislot class of the MS. Consequently, the Alcatel BSS assigns only one PDCH to the MS. In case an EGPRS Packet Channel Request message is received from the mobile station, the EGPRS multislot class of the MS is known by the BSS. However only one PDCH is allocated due to the limitation of the Immediate Assignment message: If the PDCH is allocated on a non-EGPRS capable TRX an Immediate Assignment message in GPRS mode is sent to the MS including the PDCH id, the USF value, the TFI value, the TAI value, the TA value, and the GPRS coding scheme to be used. If the PDCH is allocated on an EGPRS capable TRX, an Immediate Assignment message in EGPRS mode TA value and the EGPRS modulation and coding scheme to be used. Timers T_USF_scheduling_AGCH: Time between the sending of the Assignment Command message to the BTS and the scheduling of the first UL block on the PDCH. This internal MFS timer is always expiring in order to leave time to the MS to switch from a CCCH to a PDCH time slot. T_GPRS_ASSIGN_AGCH T_USF_scheduling_AGCH: Started at T_USF_scheduling_AGCH expiry, stopped when receiving the first UL block from the MS. T_GPRS_ASSIGN_AGCH = 0.8 s (default value) but computed as a function of the CCCH configuration in the cell. It cannot be set at the OMC-R level. T_USF_scheduling_AGCH = 0 ms (default value). It cannot be set at OMC-R level. T_GPRS_ASSIGN_AGCH" is the HMI name of "T_ul_assign_ccch" present in BSS telecom parameters catalogue A contention resolution procedure is used in order to avoid that two MSs sending a Channel Request at the same time use the same allocated radio resource to send data: Each MS sends its TLLI in the first RLC Data Block. The TLLI of the MS chosen by the BSS is present in the Packet UL Ack/Nack from the MFS. The other MS will stop using the radio resource when receiving the Packet UL Ack/Nack with another TLLI.
UL TBF Establishment 2-Phase Access on CCCH, Success

MS (EGPRS Packet) Channel request RACH BTS Channel required (TA) TA calculation BSC MFS GPRS EGPRS
P62c P62d
Channel request (TA)

GCH allocation
Channel assignment UL (IA) P49 Imm. assign. command PDCH id, TBF starting time, Immediate assignment MS switches TA, 1 (multiple) block(s) AGCH on allocated T_GPRS_ASSIGN_AGCH RLC block(s) Packet resource request Packet resource request PACCH TLLI, MS Radio Access Capability, QoS Contention (Additional Radio Access Capability)
resolution T3168
GCH allocation
MS switches on assigned PDCHs
Packet UL assignment PACCH USF Scheduling PDTCH RLC data block PDTCH
Packet UL assignment TLLI, PDCHs, USFs, TFI, TAI, TA, CS (MCS, EGPRS window size) USF Scheduling RLC data block
T_ACK_WAIT
P30c
GPRS
P30d
EGPRS
1 3 10
A 2-phase access is initiated in one of the following cases: When a GPRS MS wants to use the TBF to send user data in RLC unacknowledged mode. When a GPRS or EGPRS MS wants to precise QoS parameters (e.g., Peak_Throughput_Class, Radio_Priority). When a GPRS MS wants to provide the BSS with its multislot class in case of an uplink access done on CCCH. When an GPRS MS wants to establish the TBF to send user data in RLC acknowledged mode and the amount of data to send takes more than 8 RLC/MAC blocks (Note 1 and Note 2). If the EGPRS PACKET CHANNEL REQUEST is not supported in the cell (Note: the Alcatel BSS always supports the EGPRS PACKET CHANNEL REQUEST), when an EGPRS MS wishes to send user data or signaling data. If the EGPRS PACKET CHANNEL REQUEST is supported in the cell, when an EGPRS MS wants to use the TBF to send user data in RLC unacknowledged mode. If the EGPRS PACKET CHANNEL REQUEST is supported in the cell, when an EGPRS MS wants to establish the TBF to send user data in RLC acknowledged mode and the amount of data to send takes more than 8 RLC/MAC blocks (Note 3 and Note 4). Note 1: The number of blocks must be calculated assuming channel coding scheme CS-1. Note 2: The mobile station can also request a 1-phase access. Note 3: The number of blocks must be calculated assuming modulation and channel coding scheme MCS-1. Note 4: If the cell is EGPRS capable, the mobile station can also request 1-phase access. The MS Radio Access Capability IE includes the Multislot class of the MS as well as the QoS required for the transfer Timers T_GPRS_ASSIGN_AGCH, controls the duration between (EGPRS Packet) Channel Request message and the UL radio block allocated to the MS. T_ACK_WAIT: Started when the first UL block is scheduled to the MS, stopped when receiving the first UL block. T_ACK_WAIT = 1.2 s (default value). It cannot be set at OMC-R level. T3168: MS timer started when sending the Packet Resource Request message and stopped when receiving the Packet UL Assignment. It is broadcast in the SI13 message. T3168 = 1 s (default value). It can be set at the OMC-R level but 1 s is the minimum value.
UL TBF Establishment 1-Phase Access on PCCCH, Success

MS
(EGPRS) Packet Channel request
BTS
BSC
(EGPRS) (EGPRS) Packet Channel request Packet Channel request (TA) (TA)
MFS
GPRS EGPRS
PRACH (4 A.B.)
TA calculation
(EGPRS) Multislot class

GCH allocation
P62a
P62d
Packet UL assignment Packet UL assignment PDCHs, USFs, TFI, TAI, TA, CS (MCS, EGPRS window PAGCH size) USF Scheduling PDTCH RLC data block PDTCH USF Scheduling RLC data block TLLI, TFI Packet UL Ack/Nack TLLI, TFI
T_ACK_WAIT
P30a
GPRS
P30d
EGPRS
Contention resolution
Packet UL Ack/Nack PACCH

1 3 11
Possible causes for the one phase access for GPRS: 1-phase access (MS multislot class provided) Short access (less than 8 RLC blocks) Paging response Cell update MM procedures (GPRS Attach, GPRS Detach, RA update) Single block without TBF establishment Note: The access indicating Single Block Without TBF Establishment is supported by the Alcatel BSS: such an access is used by the MS to report a Packet Measurement Report message or a Packet Cell Change Failure message in Packet Idle Mode Possible causes for the one phase access for EGPRS: 1-phase access Short access Signaling
A EGPRS mobile provides both its GPRS multislot class and its EGPRS multislotclass. If the TBF can not be established in EGPRS mode it will then be established in GPRS mode if possible. In this case the EGPRS multislot class is used by the BSS to allocate the corresponding number of PDCHs. If the GPRS multislot class is higher than the EGPRS one then the TBF is a candidate for a subsequent radio resource re-allocation to extend the number of PDCHs.
UL TBF Establishment 2-Phases Access on PCCCH, Success

MS
(EGPRS) (EGPRS) (EGPRS) BTS BSC MFS GPRS Packet Channel request Packet Channel request Packet Channel request (TA) (TA) PRACH (4 A.B.)
EGPRS
TA calculation
(EGPRS) Multislot class
P62a
P62d
Packet UL assignment PAGCH MS switches on allocated RLC block(s) Packet resource request PACCH
Packet UL assignment PDCH id, TBF starting time, TA, 1 (multiple) block(s)
T_UL_Assign_PCCCH
Contention resolution T3168
Packet resource request TLLI, MS Radio Access Capability, QoS (Additional Radio Access Capability)
PDCH & GCH allocation
Packet UL assignment PACCH USF Scheduling PDTCH RLC data block PDTCH
Packet UL assignment TLLI, PDCHs, USFs, TFI, TAI, TA, CS (MCS, EGPRS window size) USF Scheduling RLC data block
T_ACK_WAIT
P30a
GPRS
P30d
EGPRS
1 3 12
Timer T_UL_ASSIGN_PCCCH controls the duration between (EGPRS) Packet Request message and the UL radio block allocated to the MS. T_UL_ASSIGN_PCCCH = 0.4 s (default value). It can be set at the OMC-R level. 2-phase access is used when the MS wants specific QoS attribute values to be taken into account (e.g., RLC Nack mode).
UL TBF Establishment during a DL TBF, Success

MS BTS DL transfer RLC data block PDTCH Packet DL Ack/Nack PACCH
T3168
BSC
MFS
RLC data block, polling

GPRS EGPRS
(EGPRS) Packet DL Ack/Nack with Channel request P62b

GCH allocation
Packet UL assignment Packet UL assignment PDCHs, USFs, TFIUL,TAI, CS (MCS, EGPRS window size) PACCH USF Scheduling PDTCH RLC data block PDTCH USF Scheduling
T_ACK_WAIT
RLC data block
P30b
GPRS
EGPRS
1 3 13
This scenario corresponds to a UL TBF establishment in PTM without re-allocation of the on-going DL TBF. The Packet UL Assignment message is repeated N_SIG_REPEAT times because if the MS has not decoded the Packet UL Assignment then the MS tries again to establish the UL TBF only after T3168 expiry. N_SIG_REPEAT = 1 (default value). It cannot be set at the OMC-R level. Therefore the Packet UL Assignment is sent 2 times in a row.
UL TBF Establishment, Exercise

Exercise 1: Identify the type of UL TBF establishment procedure among the provided traces 1, 2, 3, 9 Exercise 2: Using the trace 2 , find how many TBFs are established and when? Exercise 3: Using the trace 2, identify the values of:
TFIUL TFIDL PDCHs allocated for the UL TBF
1 3 14
UL TBF Establishment, Failures

UL TBF Establishment Success Rate
TBF Establishment Efficiency
TBF Establishment Preparation Success TBF Estab Congestion Rate Radio Congestion Duration
Radio Congestion TBF Establishment Failure BSS TBF Establishment Failure Gb TBF Establishment Failure Radio Abis Congestion Ater Congestion GPU congestion DSP Congestion DSP in load/overload CPU Congestion Too many TBF
1 3 15
Note: GPU congestion means that the maximum capacity of at least one DSP on the GPU is reached in terms of resources GCH and/or PDCH. A lack of Ater resources occurs when there is not enough Ater nibbles to serve the UL TBF request. A lack of Abis transmission resources occurs when there is not enough Abis nibbles to serve the UL TBF request. The GPU is split into two sub-units : the Packet Management Unit (PMU) and the Packet Traffic Unit (PTU). The functions managed by the PMU are implemented on the PowerPC (CPU) processor The functions managed by the PTU are implemented on 4 Digital Signalling Processors (DSP) for a GPU board
UL TBF Establishment, Failures, Congestion

Radio Congestion
1. maximum number of MSs per slave PDCH in uplink is reached 2. no TAI or TFI left in the MFS 3. no PDCH are granted to MFS due to a CS congestion and max_pdch_high_load=0
Too Many TBF's

UL TBF establishment fails due to a too low number of available GCH, compared to the number of TBF's.
DSP Congestion
maximum capacity of at least one DSP on the GPU is reached in terms of resources GCH and/or PDCH.
Abis Congestion
UL TBF establishment fails due to a lack of Abis resources
DSP in load/overload state

UL TBF establishment fails due to the internal cause CPU_DSP_LOAD
Ater Congestion
UL TBF establishment fails due to a lack of Ater resources
CPU Congestion
UL TBF cannot be established due to CPU processing power limitations of the GPU
1 3 16
This slide is also valid for the description of the different causes of congestion during a DL TBF establishment.
UL TBF Establishment, Failures, Congestion [cont.]

MS (EGPRS Packet) Channel request RACH BTS BSC MFS
Channel required (TA)
Channel request (TA) Channel assignment UL (Imm. assign. Reject)

Wait indication
Imm. assign. command Immediate assignment reject (Imm. assign. Reject) AGCH (EGPRS) Packet Channel request
No resource available (radio+Abis+Ater+Too many TBF+DSP+ GPU+GPU-CPU)
(EGPRS) (EGPRS) 5l+P204+P105d+P105f Packet Channel request Packet Channel request (TA) (TA) or Packet resource request Packet resource request or or Packet resource request or or or Packet DL Ack/Nack with Packet DL Ack/Nack with Packet DL Ack/Nack with No resource available Channel request Channel request Channel request (radio+Abis+Ater+Too Packet access reject PACCH Packet access reject Packet access reject
Wait indication
P27+P105j+P105h+P10
many TBF+DSP+ GPU+GPU-CPU)
1 3 17
The first scenario corresponds to: the impossibility to allocate the resources for a UL TBF establishment 1-phase access on CCCH. the impossibility to allocate the UL block(s) for a UL TBF establishment 2-phase access on CCCH. The second scenario corresponds to: the impossibility to allocate the resources for a UL TBF establishment 2-phase access on CCCH. the impossibility to allocate the resources for a UL TBF establishment during a DL TBF.
UL TBF Establishment on CCCH, Failures, Radio

MS (EGPRS Packet) Channel request RACH Immediate assignment AGCH USF Scheduling PDTCH RLC data block PDTCH BTS BSC MFS
Channel request + TA Channel required (TA) Channel assignment UL (IA) Imm. assign. command PDCH, TFI, USF, TAI, TA, CS
(MCS, EGPRS window size)
USF Scheduling
T_GPRS_ASSIGN_AGCH expiry P28
Packet UL assignment PACCH USF Scheduling PDTCH
Packet UL assignment TLLI, PDCHs, USFs, TFI, TAI, TA, CS (MCS, EGPRS window size) USF Scheduling
T_ACK_WAIT expiry P28
1 3 18
The first scenario corresponds to a radio failure occurring during a UL TBF establishment 1-phase access on CCCH. The second scenario corresponds to a radio failure occurring during a UL TBF establishment 2-phase access on CCCH. If the contention resolution fails, the MS will try to establish the UL TBF up to 4 times. The radio problems counted are usually due to interference or bad coverage but Abis microwave transmission problems or some BSS problems (RSL overload) can be counted as radio problems.
UL TBF Establishment on PCCCH, Failures, Radio

MS BTS BSC MFS (EGPRS) (EGPRS) (EGPRS) Packet Channel request Packet Channel request Packet Channel request PRACH (4 A.B.) (TA) (EGPRS) Multislot class Packet UL assignment Packet UL assignment PDCHs, USFs, TFI, TAI, TA, CS (MCS, EGPRS window size) PAGCH USF Scheduling USF Scheduling PDTCH RLC data block PDTCH
T_ACK_WAI T expiry P28
Packet UL assignment PACCH USF Scheduling PDTCH
Packet UL assignment TLLI, PDCHs, USFs, TFI, TAI, TA, CS (MCS, EGPRS window size) USF Scheduling
T_ACK_WAI T expiry
P28
1 3 19
The first scenario corresponds to a radio failure occurring during a UL TBF establishment 1-phase access on PCCCH. The second scenario corresponds to a radio failure occurring during a UL TBF establishment 2-phase access on PCCCH. The radio problems counted are usually due to interference or bad coverage but Abis microwave transmission problems or some BSS problems (RSL overload) can be counted as radio problems.
UL TBF Establishment during a DL TBF, Failures, Radio

MS BTS BSC MFS
DL transfer / Active or Delayed phase
RLC data block PDTCH Packet DL Ack/Nack PACCH

T3168
RLC data block, polling
(EGPRS) Packet DL Ack/Nack with Channel request
Packet UL Assignment Packet UL assignment PACCH PDCHs, USFs, TFIUL,TAI, CS (MCS, EGPRS window size) USF Scheduling PDTCH USF Scheduling
T_ACK_WAIT expiry
P28
1 3 20
If a DL TBF re-allocation is triggered upon a UL TBF establishment and if the DL TBF re-allocation fails due to a radio problem then counter P28 is also incremented. The radio problems counted are usually due to interference or bad coverage but Abis microwave transmission problems or some BSS problems (RSL overload) can be counted as radio problems.
UL TBF Establishment, Failures, Gb, BSS

Problem at Gb interface level
When the CELL is in the operational state disabled in the BSS
O&M problem
MS
<< UL
MFS
establishment request
Cell identity
>>
SGSN
Cell BVC unavailable

P66
Problem at BSS level

which is not linked to Congestion, Radio, Gb
no specific counter
1 3 21
A problem at BSS level can be linked to a Hardware or a Software failure.
DL TBF Establishment on CCCH, MS in Ready State

MS BTS BSC
GCH allocation
MFS
LLC PDU
P91f, P91c P91g P53c, P49
GPRS EGPRS
Immediate assignment
Imm. assign. command
Channel assignment DL (IA) PDCH, TFI, TAI, (EGPRS)
PCH/AGCH (DRX/Non-DRX) MS switches on assigned PDCH

T3190
t_assign_agch_pacch t_assign_pch_pacch
Packet DL assignment PACCH Packet control Ack PACCH (4 A.B.) TA / PC PACCH RLC data block PDTCH
Packet DL assignment, polling PDCHs, TFI, TAI, (EGPRS window size) TA calculation
expiry & restart
Packet control Ack

P90f, P90c
GPRS EGPRS
Timing Advance / Power control
P90g
1 3 22
If the MFS does not receive the Packet Control Ack message from the MS: it sends again the Packet Downlink Assignment message up to MAX_GPRS_ASSIGN_PCH_RETRANS if the MS is in DRX mode or up to MAX_GPRS_ASSIGN_AGCH_RETRANS if the MS is in Non-DRX mode. if the Maximum number of retransmission of Packet Downlink Assignment message is reached then the MFS restarts the whole DL TBF establishment procedure up to MAX_DL_RETRANS times. MAX_GPRS_ASSIGN_PCH_RETRANS = 3 (default value) MAX_GPRS_ASSIGN_AGCH_RETRANS = 3 (default value) MAX_DL_RETRANS = 3 (default value) The other establishment attempts of the same TBF are not counted, only the first attempt is counted. Timers T_GPRS_ASSIGN_AGCH: controls the reception of the Packet Control Ack message from the MS in Non-DRX mode. T_GPRS_ASSIGN_AGCH = 0.8 s (default value) but computed as a function of the CCCH configuration in the cell. It cannot be set at the OMC-R level. T_GPRS_ASSIGN_AGCH" is the HMI name of "T_ul_assign_ccch" described in the BSS telecom parameters catalogue. T_GPRS_ASSIGN_PCH: controls the reception of the Packet Control Ack message from MS in DRX mode. T_GPRS_ASSIGN_PCH = 1.4 s (default value) but computed as a function of the BS_PA_MFRMS CCCH parameter in the cell. It cannot be set at the OMC-R level. T_GPRS_ASSIGN_PCH" is the HMI name of "T_dl_assign_ccch" described in the BSS telecom parameters catalogue. t_assign_agch_pacch: is the time the MFS waits for the Packet Control Ack message after having sent the Packet Downlink Assignment message to the MS in Non-DRX mode before repeating the Packet Downlink Assignment message. Its value is computed as T_GPRS_ASSIGN_AGCH / (MAX_GPRS_ASSIGN_AGCH_RETRANS + 1). t_assign_pch_pacch: is the time the MFS waits for the Packet Control Ack message after having sent the Packet Downlink Assignment message to the MS in DRX mode before repeating the Packet Downlink Assignment message. Its value is computed as T_GPRS_ASSIGN_PCH / (MAX_GPRS_ASSIGN_PCH_RETRANS + 1). T3190: if this timer expires, the MS returns into Packet Idle Mode. T3190 = 5s (default value).
DL TBF Establishment on PCCCH, MS in Ready State

MS BTS BSC
GCH allocation
MFS
LLC PDU
P91d, P91a P91g
GPRS EGPRS
Packet DL assignment PPCH (first/paging group) MS switches on assigned PDCH
Packet DL assignment, polling PDCHs, TFI, TAI, (EGPRS window size)

T_ACK_WAIT
T_ACK_WAIT_DRX_PCCCH
Packet control Ack PACCH (4 A.B.) TA / PC PACCH RLC data block PDTCH
TA calculation
Packet control Ack

P90d, P90a
GPRS EGPRS
Timing Advance / Power control
T3190
P90g
1 3 23
If the MFS does not receive the Packet Control Ack message from the MS: the MFS restarts the whole DL TBF establishment procedure up to MAX_DL_RETRANS times. MAX_DL_RETRANS = 3 (default value) The other establishment attempts of the same TBF are not counted, only the first attempt is counted. Timers T_ACK_WAIT: controls the reception of the Packet Control Ack message from the MS in Non-DRX mode. T_ACK_WAIT = 1.2 s (default value). It cannot be set at the OMC-R level. T_ACK_WAIT_DRX_PCCCH: controls the reception of the Packet Control Ack message from the MS in DRX mode. T_ACK_WAIT_DRX_PCCCH = 2.5 s (default value). It cannot be set at the OMC-R level. T3190: if this timer expires, the MS returns into Packet Idle Mode. T3190 = 5 s (default value)
DL TBF Establishment during a UL TBF

MS BTS BSC MFS
UL transfer
GCH allocation
LLC PDU
P91b
RRBP + 40 ms
signmen Packet DL as PACCH

RRBP
T3190
Packet contro l Ack
lling signment, po Packet DL as window , TAI, (EGPRS PDCH(s), TFIDL size) ck RLC data blo PDTCH Packet contro l Ack
T_ACK_WAIT
P90b
1 3 24
This scenario corresponds to a DL TBF establishment in PTM without re-allocation of the on-going UL TBF.
DL TBF Establishment, Radio Resource Optimization

MFS n PDCHs allocated according to MS multislot class
8 octet 1 octet 2.2a octet 3-4 octet 5 7 6
SGSN BSSGP PDU (QoS profile, LLC PDU)
QoS Profile IE from BSSGP message

5 4 3 2 1
GSM 08.18
IEI Length Indicator Peak bit rate provided by the network, coded as the value part in Bucket Leak Rate/R IE/ GSM 08.18 a) SPARE C/R T A Precedence
T bit coding
coding semantic The SDU contains signaling (e.g., related to GMM) The SDU contains data
Only 1 PDCH allocated n PDCHs allocated according to MS multislot class

1 3 25
0 1
DL TBF Establishment, Exercise

Exercise 1: Identify the type of DL TBF establishment procedure among the provided traces 6, 6bis, 8 and 9 Exercise 2: identify trace 6bis if the DL TBF is established for data or signaling transfer
1 3 26
DL TBF establishment, Failures

DL TBF Establishment Success Rate
TBF Establishment Efficiency
TBF Establishment Preparation Success TBF Estab Congestion Rate Radio Congestion Duration
Radio Congestion TBF Establishment Failure BSS TBF Establishment Failure Gb TBF Establishment Failure Radio Abis Congestion Ater Congestion GPU congestion DSP Congestion DSP in load/overload CPU Congestion
Too many TBF

1 3 27
EGPRS QoS Description of the Main BSS GPRS QoS Counters and Indicators EVOLIUM Introduction to GPRS and E-GPRS QoS Monitoring - B10 All Rights Reserved Alcatel-Lucent 2008
DL TBF Establishment, Failures, Cong and Gb

BSS resource congestion: radio (PDCH, TAI, TFI), Ater, GPU
MFS
No resource available: (radio+Abis+Ater+DSP+CPU)+ CPU_LOAD + too many TBFs
P14+ P105i+ P105g+P105c+P105e+P203+ P105k
SGSN LLC PDUs LLC Discarded
Problem at Gb interface level

When the CELL is in the operational state disabled in the BSS
O&M problem
MFS LLC PDUs
Cell BVC unavailable
P65
SGSN
LLC Discarded
1 3 28
DL TBF Establishment, Failures, Radio

Radio problem
MS BTS Packet DL assignment PACCH or PPCH BSC Packet DL assignment, polling PDCHs, TFI, TAI, (EGPRS window size) MFS
Packet control Ack PACCH

t_assign_agch_pacch expiry or t_assign_pch_pacch expiry or T_ACK_WAIT expiry for the last attempt of the same DL TBF establishment
P15

what is not Congestion, Radio, Gb
no specific counter
1 3 29
If a UL TBF re-allocation is triggered upon a DL TBF establishment and if the UL TBF re-allocation fails due to a radio problem then counter P15 is also incremented. The radio problems counted are usually due to interference or bad coverage but Abis microwave transmission problems or some BSS problems (RSL overload) can be counted as radio problems.
Fast DL TBF Re-establishment, Success
MS
BTS
begin
BSC
DL transfer
end
MFS
T3192 & T3192n
T3192
signment Packet DL as CCH PA

RRBP
T3190
Packet contro l Ack
Same resources LLC PDU allocation P91e ent, polling signm Packet DL as window RRBP , TAI, (EGPRS (s), TFIDL + PDCH 40 ms ) size ck RLC data blo TCH PD T_ACK_WAIT
Packet contro l Ack
P90e
1 3 30
If the MFS does not receive the Packet Control Ack message from the MS: the MFS restarts the whole DL TBF establishment procedure up to MAX_DL_RETRANS times. MAX_DL_RETRANS = 3 (default value) The other establishment attempts of the same TBF are not counted, only the first attempt is counted. Timers T_ACK_WAIT: controls the reception of the Packet Control Ack message from the MS in Non-DRX mode. T_ACK_WAIT = 1.2 s (default value). It cannot be set at the OMC-R level. T3190: if this timer expires, the MS returns into Packet Idle Mode. T3190 = 5 s (default value)
Fast DL TBF Re-establishment, Failures

All types of failures are counted in the same counters as for other kinds of DL TBF establishment
BSS resource congestion
radio (PDCH, TAI, TFI): Abis: Ater: GPU DSP Congestion: GPU CPU processing power limitations: DSP Load/Overload: Too many TBFs: P14 P105i P105g P105c P105e P203 P105k
radio: Gb: BSS:
P15 P65 no specific counter
1 3 31
PS Paging
Identify the procedures 1 and 2 on the following diagram
MS BTS Paging Request/Packet Paging Request PCH/PPCH Channel Request/Packet Channel Request cause =?/cause =? RACH/PRACH Immediate Assignment/Packet Uplink Assignment AGCH/PAGCH USF Scheduling PDTCH Sending of an LLC PDU (RLC blocks) containing GMM Paging response message PDTCH BSC
PS
P53a/P61a P391b P53b/P61b
MFS
PS
P391a
SGSN LLC PDU PS Paging MS in Standby
CS
CS
Procedure 1 ?
MS Ready
Procedure 2 ?
1 3 32
DL UNITDATA PDU
A CS Paging Request can be sent by the SGSN to the MS through the GMM PS Paging message if the GS interface exists (GPRS network configured in NMO I). In the case a CS Paging Request sent on PCH or PPCH the MS performs a CS Radio Link Establishment procedure.
PS Paging, Exercise
Exercise: Using the trace 7, find the cell in which the MS is located
1 3 33
Reduction of the Ping Duration

MS BTS BSC DL transfer (delayed state) Packet DL Ack/Nack Packet UL assignment USF Scheduling RLC data block (EGPRS) Packet DL Ack/Nack with Channel request Packet UL assignment USF Scheduling RLC data block MFS
B10
SGSN
RLC data block
RLC data block LCC (Echo Req) LCC (Echo Rep)
RLC data block
RLC data block
RLC data block

1 3 34
RLC data block

Key Improvements, compared to B9: PDAN to PUAS delay reduction DL LLC PDU to DL RLC block delay reduction Last DL RLC block sent in the same radio block as the other blocks
Improvement for EDGE mobiles, with BSC/MFS Evolution Duration of Ping 32 bytes 0 second: B9: 255~247ms B10: 208~197ms
PS Paging, Exercise (Reduction of Ping Time) B10

Exercise: In the following trace measure the PING duration
Trace 18 Can you find the same case as in the previous slide? In which state is the UL TBF before the ping?
Exercise 2: Identify the length of the echo request message
1 3 35
TBF Establishments: Dual Transfer Mode

MS in dedicated mode
B10
UL TBF establishment
DL TBF establishment
MS in MM Standby state
TCH change
Same TCH
TCH change
Same TCH
PS Paging
MS in Dual Transfer Mode
1 3 36
UL TBF Establishment in Dedicated Mode

MS BTS BSC MFS
B10
Dedicated mode (TCH) (1)

[main DCCH] DTM Request (2) (TLLI, QoS, cause) T3148n (BSC) T3148
P507
BSCGP DTM Request (3) (IMSI, current TCH)
T3148n (MFS) (IMSI, PUAS)
BSCGP DTM Assign CMD (4) USF USF USF
T_ACK_WAIT Packet Assignment (5) [FACCH] (TFI, TAI, USFs, PDCHs) Assignment Complete (6) [PDCH] UL radio blocks (7)
MC927c
BSC Shared DTM Info Indication

P508
UL LLC PDUs
1 3 37
1. It is assumed that the MFS has been informed that the MS is in dedicated mode. 2. The MS requests the establishment of a PS session by sending a DTM Request message and starts timer
T3148. This message contains: TLLI of the MS Radio priority (four possible values) RLC mode associated with the packet transfer (RLC acknowledged mode or RLC unacknowledged mode) LLC frame type (whether or not the first LLC PDU is SACK or ACK) Establishment cause (User data, Page response, Cell update, or MM procedure) Peak Throughput Class and RLC_OCTET_COUNT field (indicating the number of RLC data volume to be transferred) Optionally the PFI
3. The BSC forwards the request to the MFS through a new message called BSCGP DTM Request. This
message contains the references of the MS (i.e., IMSI and BSC reference) and the identity of the radio timeslot currently allocated to the MS. The radio timeslot identity is used to know whether or not the TCH needs to be re-assigned.
4. The MFS sends to the BSC a new message called BSCGP DTM Assignment Command. This message
contains the references of the MS (i.e., IMSI), and the RR Packet Uplink Assignment IE that will be transparently sent in the 44.018 Packet Assignment message. This IE provides the MS with information required for the UL TBF allocation (TFI, TAI, USF and PDCHs). USF(s) are scheduled as soon as the BSCGP DTM Packet Assignment message is sent and the timer T_ACK_WAIT is started to monitor the beginning of the UL TBF.
5. The BSC builds the Packet Assignment message based on the information retrieved from the MFS and
sends it to the MS on the main DCCH. The BSC starts timer T3107 to monitor the receipt of the Assignment Complete message. On receipt of the 44.018 Packet Assignment message, the MS stops timer T3148.
6. On receipt of the Assignment Complete message, the BSC stops timer T3107 and sends a BSC Shared DTM
Info Indication message to the MFS, indicating the successful end of the DTM assignment procedure.
7. The MS starts sending UL RLC blocks on the new assigned PDCH(s).
UL TBF Establishment in Dedicated Mode TCH Change

MS BTS BSC MFS
B10

[old main DCCH] DTM Request (2) (TLLI, QoS, cause) T3148n (BSC) T3148
P507
BSCGP DTM Request (3) (IMSI, current TCH)
T3148n (MFS) (IMSI, TCH, PUAS)
BSCGP DTM Assign CMD (4) USF USF USF Chan. Act. (new TCH) Chan. Act. ACK DTM Assignment Command (5) (TCH, TFI, TAI, USFs, PDCHs) [new FACCH] [PDCH] Assignment Complete (6)
MC927a
T_ACK_WAIT T3107 BSC Shared DTM Info Indication

P508
UL radio blocks (7)
UL LLC PDUs
1 3 38
1. It is assumed that the MFS has been informed that the MS is in dedicated mode. 2. The MS requests the establishment of a PS session by sending a DTM Request message and starts timer
T3148. This message contains: TLLI of the MS Radio priority (four possible values) RLC mode associated with the packet transfer (RLC acknowledged mode or RLC unacknowledged mode) LLC frame type (whether or not the first LLC PDU is SACK or ACK) Establishment cause (User data, Page response, Cell update, or MM procedure) Peak Throughput Class and RLC_OCTET_COUNT field (indicating the number of RLC data volume to be transferred) Optionally the PFI
3. The BSC forwards the request to the MFS through a new message called BSCGP DTM Request. This
message contains the references of the MS (i.e., IMSI and BSC reference) and the identity of the radio timeslot currently allocated to the MS. The radio timeslot identity is used to know whether or not the TCH needs to be re-assigned.
4. The MFS sends to the BSC a new message called BSCGP DTM Assignment Command. This message
contains the reference of the MS (i.e. IMSI), the new TCH to be assigned to the MS, and the RR Packet Uplink Assignment IE that will be transparently sent in the 44.018 DTM Assignment Command message. This IE provides the MS with information required for the UL TBF allocation (TFI, TAI, USF and PDCHs). USF(s) are scheduled as soon as the BSCGP DTM Assignment Command is sent and the timer T_ACK_WAIT is started to monitor the beginning of the UL TBF.
5. The BSC activates the new TCH, builds the DTM Assignment Command message based on the information
retrieved from the MFS and sends it to the MS on the old main DCCH. The BSC starts timer T3107 to monitor the receipt of the Assignment Complete message. On receipt of the 44.018 DTM Assignment Command message, the MS stops timer T3148.
6. On receipt of the Assignment Complete message, the BSC stops timer T3107 and sends a BSC Shared DTM
Info Indication message to the MFS, indicating the successful end of the DTM assignment procedure.
7. The MS starts sending UL RLC blocks on the new assigned PDCH(s).
UL TBF Establishment in Dedicated Mode, Failures

DTM
DTM UL TBF establishment FAILURE
B10
Radio Resource Congestion
Radio failure
BSS pb

what is not Congestion, Radio
no specific counter
1 3 39
UL TBF Establishment in Dedicated Mode, Failure, Cong

MS BTS BSC MFS
B10
Dedicated mode (TCH)

[main DCCH] DTM Request (TLLI, QoS, cause) T3148n (BSC) T3148
P507
BSCGP DTM Request (IMSI, current TCH)
T3148n (MFS) BSCGP DTM Reject

P512
expiry
1 3 40
P507: Number of UL TBF establishment requests on DCCH for MS operating in DTM. P512: Number of UL TBF establishment failures on DCCH for MS operating in DTM due to a lack of radio resources.
UL TBF Establishment in Dedicated Mode, Failure, Radio

MS BTS BSC MFS
B10

P507
T3148n (MFS) (IMSI, PUAS)
BSCGP DTM Assign CMD USF USF USF Packet Assignment [FACCH] (TFI, TAI, USFs, PDCHs)
MC927c
T_ACK_WAIT
P28
UL RLC Block
expiry
1 3 41
P507: Number of UL TBF establishment requests on DCCH for MS operating in DTM. P28: Number of UL TBF establishment failures at the expiry of T_ACK_WAIT timer (typical UL TBF Establishment Failure due to Radio problems, not specific to DTM)
UL TBF Establishment in Dedicated Mode, Failure, Radio

With TCH change
MS BTS BSC MFS
B10

P507
T3148n (MFS) (IMSI,TCH, PUAS)
BSCGP DTM Assign CMD USF USF USF DTM Assignment Command (5) [FACCH] (TCH, TFI, TAI, USFs, PDCHs) T3107 DTM Assign Failure Establish Indication Data Indication (DTM Assign Failure)
MC927e
expiry
MC927c
T_ACK_WAIT
or
P28
BSCGP DTM Assign Failure
stop
1 3 42
P507: Number of UL TBF establishment requests on DCCH for MS operating in DTM. P28: Number of UL TBF establishment failures at the expiry of T_ACK_WAIT timer. MC927e: Number of UL TBF establishment in DTM with reallocation of the TCH with execution failures due to MS access problem.
DL TBF Establishment in Dedicated Mode

MS BTS BSC
BSCGP BSC Shared DTM Info Indication (IMSI's of all DTM MS's in dedicated mode) 8s. BSCGP BSC Shared DTM Info Indication
B10
MFS
DL LLC PDUs (2)

P505
(IMSI)
BSCGP DTM Assign CMD (3) (IMSI, PDAS)
[FACCH]
Packet Assignment (4) (TFI, TAI, PDCHs)
MC927d
T_DTM_ASSIGN
[PDCH]
DL radio blocks (5)
expiry T_ACK_WAIT
PDAN
P506
1 3 43
Note: the "Shared DTM Info Indication" is sent periodically to the MFS (every T_SHARED_DTM_INFO = 8s), to ensure the PS paging co-ordination for DTM MS in dedicated mode.
1. While the MS is in GMM ready state, the MFS receives a DL LLC PDU including the IMSI of the MS. 2. It is assumed here that the identity of the TCH used by the MS is known by the MFS (i.e. there is a TCH
assigned to the MS). The MFS first checks whether the TCH needs to be re-assigned. It prepares accordingly the radio (TCH and PDCH) and transmission (PDCH only) resources required to serve the DL request.The MFS sends to the BSC the new BSCGP DTM Assignment Command message. This message contains the references of the MS (i.e. IMSI and BSC reference) and the contents of the 44.018 Packet Assignment message. This IE provides the MS with information required for the DL TBF establishment (DL TFI, TAI, and PDCHs). The MFS also starts T_DTM_ASSIGN.
3. The BSC sends to the MS the 44.018 Packet Assignment message on the main DCCH. 4. At T_DTM_ASSIGN expiry, the MFS starts sending DL RLC data blocks and starts T_ACK_WAIT to monitor
DL TBF establishment (at the first occurrence of PACCH, the MFS polls the MS). Note that the MFS does not need to provide the MS with the GPRS timing advance since this value is ignored by the MS when the MS is in dual transfer mode. T_ACK_WAIT will be stopped at reception of the first PDAN.
DL TBF Establishment in Dedicated Mode TCH Change

MS BTS BSC MFS
B10

DL LLC PDUs (2)
P505
(IMSI)
BSCGP DTM Assign CMD (3) (IMSI, TCH, PDAS) Chan. Act. (new TCH) Chan. Act. ACK [old FACCH] [new FACCH] [PDCH] DTM Assignment Command (4) (TCH, TFI, TAI, PDCHs) Assignment Complete (5)
MC927b
T_DTM_ASSIGN
T3107 BSC Shared DTM Info Indication expiry T_ACK_WAIT
DL radio blocks (6)
PDAN
P506
1 3 44
1. The MS is in dedicated mode and in GMM ready state. 2. While the MS is in GMM ready state, the MFS receives a DL LLC PDU including the IMSI of the MS. 3. It is assumed here that the identity of the TCH used by the MS is known by the MFS (i.e. there is a TCH
assigned to the MS). The MFS first checks whether the TCH needs to be re-assigned. It prepares accordingly the radio (TCH and PDCH) and transmission (PDCH only) resources required to serve the DL request.The MFS sends to the BSC the new BSCGP DTM Assignment Command message. This message contains the references of the MS (i.e. IMSI and BSC reference), the identify of the new TCH, and the RR Packet Downlink Assignment IE that will be transparently sent in the 44.018 DTM Assignment Command message. This IE provides the MS with information required for the DL TBF establishment (DL TFI, TAI, and PDCHs).The MFS also starts T_DTM_ASSIGN.
4. The BSC activates the new TCH, builds the DTM Assignment Command message based in the information
retrieved from the MFS and sends it on the old main DCCH. The BSC starts timer T3107 to monitor the receipt of the Assignment Complete message.
5. On receipt of the Assignment Complete message, the BSC stops timer T3107, releases the old TCH and
sends a BSC Shared DTM Info Indication message to the MFS, indicating the successful end of the DTM assignment procedure.
6. At T_DTM_ASSIGN expiry, the MFS starts sending DL RLC data blocks and starts T_ACK_WAIT to monitor
DL TBF establishment (at the first occurrence of PACCH, the MFS polls the MS). Note that the MFS does not need to provide the MS with the GPRS timing advance since this value is ignored by the MS when the MS is in dual transfer mode.T_ACK_WAIT will be stopped at reception of the first PDAN.
DL TBF Establishment in Dedicated Mode, Failures

DTM
DL TBF establishment FAILURE
B10
Radio Resource Congestion

P511
Radio pb
MC927f
BSS pb

what is not Congestion, Radio
no specific counter
1 3 45
PS Paging in Dedicated Mode

MS BTS BSC MFS
B10

PS paging (2) (IMSI) BSCGP DTM Packet Notification (3) (CI, IMSI) [FACCH] Packet Notification (4) T_WAIT_DTM BSCGP DTM Packet Notification ACK (4)
Packet Paging Response (5)

UL LLC PDUs
1 3 46
1. The MS is in dedicated mode and in GMM standby state. 2. As the MS is in GMM Standby state, if the SGSN has something to send to the MS, the SGSN shall first page
the MS in the routing area where the MS is located.

3. Upon receipt of the PS paging, the MFS first checks whether the concerned MS is in dedicated mode
(based on information provided by the BSC). If this is the case, the MFS sends to the BSC a BSCGP DTM Packet Notification message providing the BSC with the cell identity, the references of the MS (i.e. IMSI and BSC reference) and the contents of the 44.018 Packet Notification message.
4. Then, the BSC forwards the 44.018 Packet Notification message to the MS on the main DCCH and sends a
BSCGP DTM Packet Notification ACK to the MFS for acknowledgement.

5. On receipt of the Packet Notification message, the MS shall answer to the notification with a cell update
procedure, i.e. by sending an LLC frame acting as a Packet Paging Response. Two cases can then occur: If the UL LLC frame does not convey user data information and is short enough (according to the value of the MAX_LAPDM parameter), the MS uses the GTTP to send the dummy UL LLC frame to the SGSN. Otherwise, the MS requests the establishment of an UL TBF with a 44.018 DTM Request message and sends the UL LLC PDU on the established UL TBF.
QoS Indicators
DL and UL TBF establishment:
Different cases: DL/UL: idle & transfer mode DL/UL: MPDCH or not DL: DRX & non-DRX DL: T3192 running DL/UL: MS EGPRS capable Congestion Radio TBF establishment end BSS Gb time
1 3 47
TBF establishment start
Number of requests Number of successes Success rate Allocation rate Failure causes
Radio Abis Ater DSP CPU
Distribution of number of TSs requested / obtained

The number of TBF establishment requests gives an idea of the GPRS traffic. It is therefore a KPI. Nb of Allocation successes = Nb of Requests - Nb of Congestions A radio pb can be specific to GPRS (no radio pb for GSM): it can be due to the MS behavior (bad handling of Polling from the BSS). Some tests on Ping have shown that RTT (Round Trip Time) is varying from one MS to another. Some MSs are considered to be slow, others to be fast. Round Trip Time is the time duration of data transmission from mobile to data server then back from server to mobile. Usually RTT is assessed using a PING command of 32 bytes data transmission. If the data server is connected to the Gi interface RTT will be a measurement of twice the time duration needed to send data across the GPRS network.
QoS Indicators, Request/Success

DL and UL TBF establishment: requests/successes
Transfer phase Fast DL TBF re-establishment T3192 Non-DRX mode DRX mode time
DL TBF establishment requests Transfer mode While T3192 running Idle mode + non-DRX mode + MPDCH Idle mode + non-DRX mode + no MPDCH Idle mode + DRX mode + MPDCH Idle mode + DRX mode + no MPDCH Idle mode + with / without MPDCH P91b P91e P91d P91f P91a P91c P91g DL TBF establishment successes Transfer mode While T3192 running Idle mode + non-DRX mode + MPDCH Idle mode + non-DRX mode + no MPDCH Idle mode + DRX mode + MPDCH Idle mode + DRX mode + no MPDCH Idle mode + with / without MPDCH P90b P90e P90d P90f P90a P90c P90g
GPRS/EGPRS request/success
Only EGPRS GPRS/EGPRS request/success Only EGPRS
UL TBF establishment requests Idle mode + MPDCH P62a Idle mode + no MPDCH P62c Transfer mode P62b P438c Idle mode + with / without MPDCH P62d
UL TBF establishment successes Idle mode + MPDCH P30a Idle mode + no MPDCH P30c Transfer mode P30b Idle mode + with / without MPDCH P30d
1 3 48
All other counters have been modified in order to take into account the TBFs established in EGPRS mode.
QoS Indicators, Failure

DL and UL TBF establishment: failures
% TBF establishment failures Downlink Congestion rate (radio-Abis- (P14 + P105g + P105c + P105e+P105i) / (P91a +P91b+ Congestion (radio-Abis-AterAter-GPU) P91c + P91d + P91e + P91f) GPU) rate Radio congestion rate P14 / (P91a + P91b + P91c + P91d + P91e + P91f) Radio congestion rate % of time during which (P13 / 10) / GP % of time during which PDCH allocation for DL TBF PDCH allocation for UL TBF is not possible due to is not possible due to congestion congestion Abis congestion rate (P105i) / (P91a + P91b + P91c + P91d + P91e + P91f) Abis congestion rate ATer congestion rate P105g / (P91a + P91b + P91c + P91d + P91e + P91f) ATer congestion rate DSP congestion rate P105c / (P91a + P91b + P91c + P91d + P91e + P91f) DSP congestion rate CPU congestion rate P105e / (P91a + P91b + P91c + P91d + P91e + P91f) CPU congestion rate Radio problem rate P15 / (P91a + P91b + P91c + P91d + P91e + P91f) Radio problem rate Gb problem rate P65 / (P91a + P91b + P91c + P91d + P91e + P91f) Gb problem rate BSS problem rate (P91a + P91b + P91c + P91d + P91e + P91f - P14 BSS problem rate P15 - P90a - P90b - P90c- P90d - P90e - P90f - P105e P105c - P105g - P105i - P203) / (P91a + P91b + P91c + P91d + P91e + P91f) Uplink (P27 + P105h + P105d + P105f+P105j) / (P62a + P62b + P62c) P27 / (P62a + P62b + P62c) (P26 / 10) / GP
(P105j) / (P62a + P62b + P62c - P438c)

P105h / (P62a + P62b + P62c) P105d / (P62a + P62b + P62c) P105f / (P62a + P62b + P62c) P28 / (P62a + P62b + P62c) P66 / (P62a + P62b + P62c) ((P62a + P62b + P62c - P438c - P27 - P28 - P30a P30b - P30c - P66 - P105h - P105f - P105d - P105j P204) / (P62a + P62b + P62c - P438c))
1 3 49
A CPU load state is managed per GPU. When the CPU load state reaches the maximum (crosses a high threshold) then no new TBF can be established on this GPU. Radio congestion is often low. When high, it is often linked to a GPU reset or to a problem at BSS level. Therefore Indicators based on distribution of nb of TSs allocated/requested give a better idea of the congestion situation. On DL TBF establishment failure: a RADIO STATUS message is sent to the SGSN.
QoS Indicators, KPI

DL and UL TBF establishment: success rate
TBF establishment requests and successes Indicator downlink uplink
nb of TBF establishment P91a + P91b + P91c + P91d + P91e + P91f + P62a + P62b + P62c - P438c + P507 requests P505
KPI
nb of TBF establishment P90a + P90b + P90c + P90d + P90e + P90f + P30a + P30b + P30c + P508 successes P506
TBF establishment success rate
KPI
TBF establishment allocated rate
(P90a + P90b + P90c + P90d + P90e + P90f + P506) / (P91a + P91b + P91c + P91d + P91e + P91f + P505) ((P91a + P91b + P91c + P91d + P91e + P91f + P505) - (P105c + P105e + P14 + P105g + P105i + P105k + P203 + P511)) / (P91a + P91b + P91c + P91d + P91e + P91f + P505)
(P30a + P30b + P30c + P508) / (P62a + P62b + P62c - P438c + P507)
((P62a + P62b + P62c - P438c + P507) - (P105d + P105f + P27 + P105h + P105j + P105l + P204 + P512) / (P62a + P62b + P62c - P438c + P507))
1 3 50
QoS Indicators, DL TBF Establishment, Graph

Downlink TBF Establishment
16000 14000 12000 10000 8000 6000 4000 2000 0
14 /0 8/ 20 03 16 /0 8/ 20 03 18 /0 8/ 20 03 20 /0 8/ 20 03 22 /0 8/ 20 03 24 /0 8/ 20 03 26 /0 8/ 20 03 28 /0 8/ 20 03 30 /0 8/ 20 03 01 /0 9/ 20 03 03 /0 9/ 20 03 05 /0 9/ 20 03 07 /0 9/ 20 03 09 /0 9/ 20 03 11 /0 9/ 20 03 13 /0 9/ 20 03
102 100 98 96 94 92 90
BSS fail Gb fail Radio fail Congestion Request % Allocated % Success
Thresholds:
Significant traffic is reached for 2000 DL TBF requests/cell/day (less when a Delayed downlink TBF release is activated) A UL/DL TBF establishment success rate is seen as good above 95% (except if CS2 is used at the beginning of a DL TBF)
1 3 51
Typical values of DL establishment success rate when CS2 is used at the beginning of DL TBF: 94%, 96%. TBF establishment indicators should be provided on a per DL and UL basis because the procedures are very different and QoS has to be assessed and interpreted differently. The UL TBF establishment can be degraded because of ghost Random Access messages. The amount of bytes transferred at RLC or LLC level should be considered as a significant traffic indicator (more Web browsing usage than WAP). The nb of DL TBF establishment requests can should be considered as a GPRS activity indicator.
QoS Indicators, DTM

DL and UL TBF establishment while MS is in dedicated mode:
TBF establishment start Number of requests Number of successes Success rate Allocation rate Failure causes Congestion Radio BSS TBF establishment end Radio
B10
time
1 3 52
QoS Indicators, TBF Establishment in Dedicated Mode

DL and UL TBF establishment while MS is in dedicated mode:
Indicator name
NB_DTM_DL_TBF_EST_REQ NB_DTM_DL_TCH_ASS_ATPT NB_DTM_DL_PACKET_ASS_ATPT NB_DTM_DL_TBF_EST_SUCC NB_DTM_UL_TBF_EST_REQ NB_DTM_UL_TCH_ASS_ATPT NB_DTM_UL_PACKET_ASS_ATPT NB_DTM_UL_TBF_EST_SUCC NB_DTM_MS_CONTEXT_CELL
B10
definition
Number of DL TBF establishment requests on DCCH for MS operating in DTM Number of DL TBF establishment attempts in DTM with reallocation of the TCH (sending of DTM Assignment Command with DL TBF) Number of DL TBF establishment attempts in DTM without reallocation of the TCH (sending of Packet Assignment Command with DL TBF) Number of DL TBF establishment successes on DCCH for MS operating in DTM Number of UL TBF establishment requests on DCCH for MS operating in DTM. Number of UL TBF establishment attempts in DTM with reallocation of the TCH (sending of DTM Assignment Command with UL TBF) Number of UL TBF establishment attempts in DTM without reallocation of the TCH (sending of Packet Assignment Command with UL TBF) Number of UL TBF establishment successes on DCCH for MS operating in DTM Number of DTM contexts created
Ref
P505 MC927a MC927d P506 P507 MC927a MC927c P508 P501
1 3 53
P505:This counter is incremented when the MFS receives the first DL LLC PDU for a MS in dedicated mode (and in GMM ready state). Note: This counter applies only to DTM capable mobiles. DL LLC PDU sent with BSCGP DTM GPRS information are not taken into account. P927a: this counter is incremented whenever the BSC sends (through the BTS) 44.018 DTM ASSIGNMENT COMMAND message that includes the "Description of the Uplink Packet Channel Assignment" optional IE P927d: this counter is incremented whenever the BSC sends (through the BTS) 44.018 PACKET ASSIGNMENT message that includes the "Description of the Downlink Packet Channel Assignment" optional IE. P506: This counter is incremented when the MFS receives the first Packet Downlink ack (following the reception of a DL LLC PDU for a MS in dedicated mode). This counter applies only to DTM capable mobiles. P508: This counter is incremented when the MFS receives the first UL RLC data block for a MS in dedicated mode. This counter applies only to DTM capable mobiles. P927a: This counter is incremented whenever the BSC sends (through the BTS) 44.018 DTM ASSIGNMENT COMMAND message that includes the "Description of the Uplink Packet Channel Assignment" optional IE. P927c: This counter is incremented whenever the BSC sends (through the BTS) 44.018 PACKET ASSIGNMENT message that includes the "Description of the Uplink Packet Channel Assignment" optional IE. P509: This counter is incremented for DTM capable MS with ongoing DL TBF established, when an abnormal DL TBF release, occurs: When the DTM mode is leaved ( release of the CS connection in DTM mode). When in DTM mode an intercell or an intracell handover occurs. When in PTM the dedicated mode is entered.
QoS Indicators, TBF Failure in Dedicated Mode

DL and UL TBF establishment failure while MS is in dedicated mode:
Indicator name
NB_DTM_DL_TBF_FAIL_CONG NB_DTM_DL_TCH_ASS_EXEC_FAIL_RADIO NB_DTM_UL_TBF_FAIL_CONG NB_DTM_UL_TCH_ASS_EXEC_FAIL_RADIO
B10
definition
Number of DL TBF establishment failures on DCCH for MS operating in DTM due to a lack of radio resources Number of DL TBF establishment in DTM with reallocation of the TCH - execution failures due to MS access problem Number of UL TBF establishment failures on DCCH for MS operating in DTM due to a lack of radio resources Number of UL TBF establishment in DTM with reallocation of the TCH - execution failures due to MS access problem
Ref
P511 MC927f P512 MC927e
1 3 54
P511: This counter is incremented when MFS has no suitable radio resources to enter in DTM mode. P927f: This counter is incremented: Whenever the BSC receives from the BTS a DATA INDICATION (DTM ASSIGNMENT FAILURE) message after having sent (through the BTS) 44.018 DTM ASSIGNMENT COMMAND message that includes the "Description of the Downlink Packet Channel Assignment" optional IE. After having sent (through the BTS) 44.018 DTM ASSIGNMENT COMMAND message that includes the "Description of the Downlink Packet Channel Assignment" optional IE, upon T3107 expiry, the BSC does not receive neither DTM ASSIGNMENT FAILURE (on the old channel) nor ASSIGNMENT COMPLETE (on the new channel) messages. P512: This counter is incremented when the MFS sends the BSCGP DTM reject message in case of lack of radio resources available. P927e: This counter is incremented: Whenever the BSC receives from the BTS a DATA INDICATION (DTM ASSIGNMENT FAILURE) message after having sent (through the BTS) 44.018 DTM ASSIGNMENT COMMAND message that includes the "Description of the Uplink Packet Channel Assignment" optional IE. After having sent (through the BTS) 44.018 DTM ASSIGNMENT COMMAND message that includes the "Description of the Uplink Packet Channel Assignment" optional IE, upon T3107 expiry, the BSC does not receive neither DTM ASSIGNMENT FAILURE (on the old channel) nor ASSIGNMENT COMPLETE (on the new channel) messages.
QoS Indicators, EDA Mode

UL TBF in EDA mode:
Indicator name
CUMULATED_TIME_ACTIVE_UL_CON NECTED_TIME_EDA_MODE NB_EDA_USED_UL_TBF NB_EDA_ALLOWED_UL_TBF NB_DA_EDA_REALLOC_UL_TBF
B10
definition
Cumulated overall time of UL TBF in active state operating in EDA mode Number of UL TBF that have used at least one time the EDA mode during their lifetime Number of UL TBF belonging to mobile stations allowed to use the EDA mode Number of reallocations between DA and EDA modes for UL TBF
Ref
P595 P596 P597 P598
1 3 55
Dual Transfer Mode (DTM), Exercise

In configuration GPRS_B10-2.s Open Scenario 2, Scenario 3, Scenario 4
B10
In each case, is this an UL or a DL TBF establishment ? In each case, is there a TCH change ?
1 3 56
2 Data Transfer Progress
1 3 57
TBF Progress
Data Transfer established
RLCs blocks transfer
Data transfer resumption (DL TBF and UL)
TBF resource re-allocation
Data Transfer released
1 3 58
A TBF is considered in progress after it has been allocated successfully and before a release of this TBF is triggered. When a TBF is in progress, the following processes are or can be performed: The transfer of data is on-going: useful RLC blocks. LLC dummy commands The TBF resources are re-allocated. The transfer of data is resumed
Data Transfer Resumption during a DL TBF in Delayed Phase

MS
DL transfer / Active phase
MFS one but last useful RLC data block last useful RLC data block, polling (EGPRS) Packet DL Ack/Nack
T_DELAYED_DL_TBF_POL_INITIAL
SGSN
start
DL transfer / Delayed phase
Dummy block, polling Packet DL Ack/Nack
P421
T_DELAYED_DL_TBF_POL
T_DELAYED_DL_TBF_REL = T_NETWORK_RESPONSE_TIME
Dummy block, polling Packet DL Ack/Nack new useful last RLC data block useful last RLC data block
DL transfer / Active phase
P421
P422
LLC PDU
stop stop
1 3 59
A data transfer resumption is not a real TBF establishment since the TBF established previously with the MS being in Delayed phase is re-activated. During the Delayed DL TBF phase, the BSS sends Dummy LLC UI commands to the MS leading to periodic sending of RLC blocks containing these dummy LLC data. As the application data transfer is burstly in a GPRS network (download of a web page made of a lot of components (text, pictures)), it is very important to provide the way to resume a DL transfer of LLC PDUs using the same radio resources already established rather than to re-establish again the DL TBF with the MS.
Timers T_DELAYED_DL_TBF_POL_INITIAL is the duration between the last useful RLC block sent to the MS (eventually completed with a Dummy UI command) and the first Dummy UI command block sent during the DL TBF delayed phase. T_DELAYED_DL_TBF_POL_INITIAL = 60 ms (default value). It cannot be set at the OMC-R level. The Min value of 60 ms is needed to ensure that T_DELAYED_DL_TBF_POL_INITIAL >= T_MIN_POLL T_DELAYED_DL_TBF_POL is the duration between the 2 consecutive Dummy UI command blocks sent during the DL TBF delayed phase. T_DELAYED_DL_TBF_ POL = 200 ms (default value). It cannot be set at the OMC-R level. t_delayed_dl_tbf_rel is the maximum time during which the DL TBF stays in Delayed phase before being actually released. It corresponds to the typical response time of a network server as seen from this MFS. t_delayed_dl_tbf_rel = T_NETWORK_RESPONSE_TIME = 1600 ms (default value). It can be set at the OMC-R level. T_MIN_POLL: Minimum time between two consecutive polling requests .
Data Transfer Resumption during a UL TBF in Extended Phase

The UL transfer can resume at any time during the extended phase
MS
Active UL data transfer
MFS RLC/MAC block (BSN=n, CV=0) LLC PDU (last LLC) P. UL Ack/Nack (FAI=0, SSN = n+1) start USF
SGSN
Extended UL data transfer
Dummy RLC data block USF Dummy RLC data block USF RLC/MAC block (BSN=n+1)
P462
T_MAX_EXTENDED_UL
P462
stop
Active UL data transfer
USF RLC/MAC block (BSN=n+2)
. . .
1 3 60
LLC PDU
TBF Resources Re-allocation

4 different TBF reallocations are permanently activated:
T1: reallocation to maintain a TBF alive despite the CS preemption of some RTSs or of some GCHs in the cell T2: reallocation of an on-going TBF when establishing a concurrent TBF T3: reallocation useful to
Establish a new M-EGCH link for one of the TRXs of the cell Perform a radio de-fragmentation process Provide a higher throughput, if it is possible, to a TBF
T4: reallocation to move a UL GPRS TBF sharing one PDCH with a DL EGPRS TBF onto PDCHs which do not support a DL EGPRS TBF. It concerns only GPRS TBFs
1 3 61
The scope of the T3 reallocation has been extended: To establish a new M-EGCH link for one of the TRXs of the cell. To perform a radio defragmentation process (i.e. to improve the TBFs radio resource usage in the cell. The goal is that the PDCHs supporting the TBFs in the cell are always the first (or left-most) allocated PDCHs of the cell). In particular, this will limit the risks that the TBFs are impacted by a CS preemption. To provide a higher throughput, if it is possible, to any TBF in the cell. A higher throughput can be provided to a TBF by just changing its PDCH allocation (even if its number of RTSs keeps the same). Typically, the throughput will be higher if the TBF is less multiplexed (with other TBFs) on the new PDCHs. But the T3 reallocation will also enable to increase the number of RTSs of a TBF in the following cases: for the MSs whose traffic type was signalling and has passed to data in RRM-PCC, or following the reception of an RR Allocation Indication message from the BSC allocating some new RTSs in the cell
TBF Re-allocation of the 2 UL and DL TBFs on-going

MS
UL and DL Data transfer (old resources)
MFS
RLC data block

PDTCHUL
T1
T3
DL:P403c UL:P404c DL:P405c UL:P406c
T4
DL:P403d UL:P404d DL:P405d UL:P406d
RLC data block

PDTCHDL
Packet timeslot reconfigure, polling

PACCHDL of DL TBF
DL:P403a UL:P404a DL:P405a UL:P406a
Packet control ack

PACCHUL of DL TBF
the MS switches to the new resources (max. 40 ms)

UL and DL Data transfer (new resources)
MS_TIME_TO_SWITCH_TO_NEW_PDCH + RRBP delay
RLC data block RLC data block
1 3 62
During the re-allocation procedure, the set of PDCHs allocated to the UL or/and DL TBF are modified. The following resources can be modified as well: the timing advance slot and index of the UL or/and DL TBFs, the PACCH slot of the UL or/and DL TBFs, the USFs allocated to the UL TBF, the UL or/and DL TFI. During the radio resource re-allocation procedure: the TBF mode can not be modified. the EGPRS window size cannot be decreased. However the EGPRS window size in the DL (resp. UL) must be increased in case the number of time slots allocated to the MS in the DL (resp. UL) increases. Timers MS_TIME_TO_SWITCH_TO_NEW_PDCH: the time a Mobile Station needs to switch to the assigned PDCHs after acknowledging a (re)assignment message (PACKET DOWNLINK ASSIGNMENT, PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE). MS_TIME_TO_SWITCH_TO_NEW_PDCH = 40 ms (default value). It cannot be set at the OMC-R level. The 3GPP standard mandates the MS to switch to the new resources in 40 ms but some MSs can take more time. Let us consider that an MS has 2 TBFs on-going in both UL and DL directions but is candidate for re-allocation in the UL direction only (T1 or T3 or T4): then the counter of re-allocation request in the DL direction is also incremented . At the end of the UL re-allocation procedure, the counter of DL re-allocation success is incremented whether the UL re-allocation has been successful or not because the counter of re-allocation request in the DL direction has been previously incremented. Same consideration can be done when an MS has 2 TBFs on-going in both UL and DL directions but is candidate for reallocation in the DL direction only (T1 or T3 or T4). The MFS starts timer T_ACK_WAIT after sending a Packet Timeslot Reconfigure message to wait for MS acknowledgement (Packet Control Ack message). If Packet Control Ack is not received, the MS resends the Packet Timeslot Reconfigure message. If after the MAX_RETRANS_DL+1 attempts the MS has not acknowledged the resource re-allocation then both DL and UL are released.
TBF Re-allocation of the Only TBF On-Going (DL or UL)

MS
DL/UL Data transfer (old resources)
MFS
RLC data block

PDTCHUL
T1
T3
DL:P403c UL:P404c DL:P405c UL:P406c
T4
DL:P403d UL:P404d DL:P405d UL:P406d
RLC data block

PDTCHDL
Packet downlink/uplink Assignment, polling

PACCHDL of DL TBF / PACCHDL of UL TBF
DL:P403a UL:P404a DL:P405a UL:P406a
Packet control ack

PACCHUL of DL TBF / PACCHUL of UL TBF
the MS switches to the new resources (max. 40 ms) MS_TIME_TO_SWITCH_TO_NEW_PDCH

+ RRBP delay
DL/UL Data transfer (new resources)
RLC data block RLC data block
1 3 63
The MFS starts timer T_ACK_WAIT after sending a Packet Downlink/Uplink Assignment message to wait for MS acknowledgement (Packet Control Ack message): If Packet Control Ack is not received the MS resends the Packet Downlink/Uplink Assignment message. If after the MAX_RETRANS_DL+1 attempts the MS has not acknowledged the resource re-allocation then the on-going DL/UL is released.
TBF Re-alloc of On-Going UL TBF on DL TBF Establishment

MS
UL Data transfer (old resources)
MFS
RLC data block

PDTCHUL
LLC PDU Packet timeslot reconfigure, polling

PACCHDL of UL TBF
P404b
T2
P406b
Packet control ack

PACCHUL of UL TBF

RLC data block

PDTCHUL
RLC data block

PDTCHDL
1 3 64
The MFS starts timer T_ACK_WAIT after sending a Packet Timeslot Reconfigure message to wait for MS acknowledgement (Packet Control Ack message): If Packet Control Ack is not received the MS resends the Packet Timeslot Reconfigure message. If after the MAX_RETRANS_DL+1 attempts the MS has not acknowledged the resource re-allocation then both DL and UL are released.
TBF Re-alloc of On-Going DL TBF on UL TBF Establishment

MS
DL Data transfer (old resources)
MFS
RLC data block

PDTCHDL
Packet DL Ack/Nack with Channel request

PACCHUL of DL TBF
Packet timeslot reconfigure, polling

PACCHDL of DL TBF
P403b
Packet control ack

PACCHUL of DL TBF
T2
P405b

RLC data block

PDTCHUL
RLC data block

PDTCHDL
1 3 65
The MFS starts timer T_ACK_WAIT after sending a Packet Timeslot Reconfigure message to wait for MS acknowledgement (Packet Control Ack message). If Packet Control Ack is not received the MS resends the Packet Timeslot Reconfigure message. If after the MAX_RETRANS_DL+1 attempts the MS has not acknowledged the resource re-allocation then both DL and UL are released.
Exercise
Exercise: Using the trace 3, find the time when the DL transfer is resumed
1 3 66
TBF Resource Re-allocation, Failures
TBF resource re-allocation FAILURE
no new PDCH allocation can be found
Radio pb
BSS pb
External TBF release request
Suspend
Cell reselection
1 3 67
TBF Resources Re-allocation, Failures, no New PDCH

T1 case
counter =
DL:P423a UL:P424a
if no new PDCH allocation can be found then the TBF marked for soft preemption will be released at T_PDCH_PREEMPTION expiry
T2/T3/T4 cases
counter =
DL:P423b/P423c/P423d UL:P424b/P424c/P424d
if no new PDCH allocation can be found then the on-going TBF continue with its current PDCH allocation
1 3 68
T3 re-allocation conditions
TBF Resources Re-allocation, Failures, Radio

MS
UL and/or DL Data transfer (old resources)
MFS
RLC data block

PDTCCHUL
RLC data block

PDTCHDL
Packet timeslot reconfigure, polling or, Packet downlink assignment or, Packet uplink assignment
Packet control ack

PACCHUL of DL TBF
T1
DL:P407a UL:P408a T_ACK_WAIT expiry
T2
DL:P407b UL:P408b
T3
DL:P407c UL:P408c
T4
DL:P407d UL:P408d
1 3 69
All these counters are incremented when the last MAX_DL_RETRANS+1 re-allocation attempt has failed (Packet Control Ack message not received from the MS). Re-allocation failures due to radio can be due to a problem on the DL path. In case of trigger T2, the re-allocation failure of the TBF also leads to an establishment failure due to radio of the TBF to be established in the opposite direction.
TBF Resources Re-alloc, Fail, External Req., BSS

External request
MS BSC MFS
T1
SGSN
T2
DL:P425b UL:P426b
UL and/or DL Data transfer (old resources)
RLC data block

PDTCCHUL
T3
DL:P425c UL:P426c
T4
DL:P425d UL:P426d
RLC data block

PDTCHDL
DL:P425a UL:P426a
Packet timeslot reconfigure, polling or, Packet downlink assignment or, Packet uplink assignment MS suspend
GSL
T_ACK_WAIT
"External Stop"
Flush-LL
OR

no specific counter
1 3 70
Re-allocation failures due to radio can be due to a problem on the DL path. In case of trigger T2, the re-allocation failure of the TBF also leads to an establishment failure due to radio of the TBF to be established in the opposite direction.
QoS Indicators
DL and UL TBF progress
TBF establishment
modified B10
TBF statistics: -duration, number, throughput, - distribution Delayed DL TBF: active/delayed phase, transfer resumption TBF resources re-allocation Triggers T1. T2. T3.T4 Number of candidate TBFs Number of successes and success rate
TBF release time

1 3 71
Failures: congestion, radio, BSS, external request

QoS Indicators, TBF Statistics

DL and UL TBF progress: TBF statistics
TBF statistics Downlink Uplink Average GPRS TBF duration (P52a / 10) / (P90a + P90b + Average GPRS TBF duration (P129a / 10) / (P30a + P30b + in ack mode P90c + P90d + P90e + P90f) in ack mode P30c) Average GPRS TBF duration (P52b / 10) / (P90a + P90b + Average GPRS TBF duration (P129b / 10) / (P30a + P30b + in nack mode P90c + P90d + P90e + P90f) in nack mode P30c) Average EGPRS TBF (P52c / 10) / (P90a + P90b + Average EGPRS TBF (P129c / 10) / (P30a + P30b + duration in ack mode P90c + P90d + P90e + P90f) duration in ack mode P30c) Average EGPRS TBF (P52d / 10) / (P90a + P90b + Average EGPRS TBF (P129d / 10) / (P30a + P30b + duration in nack mode P90c + P90d + P90e + P90f) duration in nack mode P30c) Maximum number of TBF p35 Maximum number of TBF p39 simultaneously established simultaneously established Average number of TBF p36 / 10 Average number of TBF p40 / 10 simultaneously established simultaneously established Average useful throughput CELL (P55a*160 + P55b*240 Average useful throughput in CELL (P57a*160 + P57b*240 + in kbit/s at RLC level per + P55c*288 + P55d*400 + kbit/s at RLC level per TBF P57c*288 + P57d*400 + TBF P55e*176 + P55f*224 + P57e*176 + P57f*224 +
KPI
P55g*296 + P55i*448 + (P55k*896 + P55m*1184)/2) p52c)*1000)
P55h*352 P55j*592 P55l*1088 / ((P52a
+ + + +
KPI
P57g*296 + P57h*352 + P57i*448 + P57j*592 (P57k*896 + P57l*1088 P57m*1184)/2)) / ((P129a P129c)*1000)
( + + +
1 3 72
The max nb of TBFs simultaneously established is meaningful per hour or per day. The average nb of TBFs simultaneously established is less reliable due to the difference between the gauge polling period and the average TBF duration. Note : The RLC blocks retransmissions are not counted in both directions.
QoS Indicators, TBF Statistics [cont.]

DL and UL TBF progress: TBF statistics
Indicator name
CUMULATED_TIME_PDCH_UL_TBF_CELL
B10
definition
Cumulated time during which an UL TBF uses one PDCH, for all PDCHs of the TBF, and for all TBFs of the cell (in GPRS or EGPRS mode). Cumulated time during which an DL TBF uses one PDCH, for all PDCHs of the TBF, and for all TBFs of the cell (in GPRS or EGPRS mode). Cumulated overall time of UL TBF connections (in active state or extended phase). Cumulated time during which a DL TBF established for GMM signalling purposes uses a PDCH (in GPRS or EGPRS mode), for all TBFs of the cell. Cumulated overall time of UL TBF in active state operating in EDA mode
Ref
P451a
CUMULATED_TIME_PDCH_DL_TBF_CELL
P451b
CUMULATED_ACT_EXT_UL_CONNECTION_TIME
P461
CUMULATED_TIME_PDCH_DL_TBF_GMM_SIG_CELL
P452
CUMULATED_TIME_ACTIVE_UL_CONNECTED_TIME_EDA_MODE
P595 new B10
1 3 73
P452: For a given DL TBF, this counter is started at the establishment of the DL TBFs established to carry GMM signaling traffic to the MS. It is stopped at the end of the active phase of the DL TBF or on receipt of a DL LLC PDU without the T-bit set. P451: Note: Active , delayed, extended phases of the TBF are taken into account (only).
QoS Indicators, Distributions

Distribution based on TBF duration
DL UL Definition Tenth interval of the distribution on duration of DL/UL TBFs. For DL It contains : number of DL TBFs whose duration is in duration band 10 Duration band 10 is defined by : PD_DL_TBF_DURATION_THR_9<= duration < PD_DL_TBF_DURATION_THR_10 Ninth cell of the duration on DL/UL TBF duration. Eighth cell of the duration on DL/UL TBF duration. Seventh cell of the duration on DL/UL TBF duration. Sixth cell of the duration on DL/UL TBF duration. Fifth cell of the duration on DL/UL TBF duration. Fourth cell of the duration on DL/UL TBF duration. Third cell of the duration on DL/UL TBF duration. Second cell of the duration on DL/UL TBF duration. First cell of the duration on DL/UL TBF duration.
P453b_10
P453a_10
P453b_9 P453b_8 P453b_7 P453b_6 P453b_5 P453b_4 P453b_3 P453b_2 P453b_1
P453a_9 P453a_8 P453a_7 P453a_6 P453a_5 P453a_4 P453a_3 P453a_2 P453a_1
1 3 74
Note: DL TBF in GPRS and EGPRS mode, in RLC acknowledged and in RLC unacknowledged mode are taken into account. Only the active phase of the TBF is taken into account. Default OMC-R parameter values in seconds: PD_DL_TBF_DURATION_THR_1 = 1639 PD_DL_TBF_DURATION_THR_2 = 3277.5 PD_DL_TBF_DURATION_THR_3 = 4916 PD_DL_TBF_DURATION_THR_4 = 6554.5 PD_DL_TBF_DURATION_THR_5 = 8193 PD_DL_TBF_DURATION_THR_6 = 9831.5 PD_DL_TBF_DURATION_THR_7 = 11470 PD_DL_TBF_DURATION_THR_8 = 13108.5 PD_DL_TBF_DURATION_THR_9 = 14747 PD_DL_TBF_DURATION_THR_10 = 16384 (cannot be modified at the OMC-R)
QoS Indicators, Distributions [cont.]

Distribution based on LLC volume
DL UL Definition Tenth interval of the distribution on volume of DL/UL TBFs. For DL It contains : number of DL TBFs whose LLC volume (in RLC ack mode only) is in LLC volume band 10. LLC volume band 10 is defined by : PD_DL_TBF_VOLUME_THR_8<= LLC volume < PD_DL_TBF_VOLUME_THR_9 Ninth cell of the distribution on volume of DL/UL TBF. Eighth cell of the distribution on volume of DL/UL TBF. Seventh cell of the distribution on volume of DL/UL TBF. Sixth cell of the distribution on volume of DL/UL TBF. Fifth cell of the distribution on volume of DL/UL TBF. Fourth cell of the distribution on volume of DL/UL TBF. Third cell of the distribution on volume of DL/UL TBF. Second cell of the distribution on volume of DL/UL TBF. First cell of the distribution on volume of DL/ULTBF.
P454b_10
P454a_10
1 3 75
Only the active phase of the TBF is taken into account. Default OMC-R parameter values in bytes: PD_DL_TBF_VOLUME_THR_1 = 10 000 000 PD_DL_TBF_ VOLUME _THR_2 = 20 000 000 PD_DL_TBF_ VOLUME _THR_3 = 30 000 000 PD_DL_TBF_ VOLUME _THR_4 = 40 000 000 PD_DL_TBF_ VOLUME _THR_5 = 50 000 000 PD_DL_TBF_ VOLUME _THR_6 = 60 000 000 PD_DL_TBF_ VOLUME _THR_7 = 70 000 000 PD_DL_TBF_ VOLUME _THR_8 = 80 000 000 PD_DL_TBF_ VOLUME _THR_9 = 90 000 000 PD_DL_TBF_ VOLUME _THR_10 = 100 000 000 (cannot be modified at the OMC-R)

Distribution based on GPRS LLC Throughput per session
DL UL Definition Tenth class of the distribution on number of GPRS DL/UL LLC throughput. It contains : 1) number of GPRS DL/UL LLC throughput whose throughput is in EGPRS LLC throughput class 10. GPRS LLC throughput class 10 is defined by : GPRS_LLC_throughput_THR_9<= LLC throughput < GPRS_LLC_throughput_THR_10 Ninth class of the distribution on number of GPRS DL/UL LLC throughput Eighth class of the distribution on number of GPRS DL/UL LLC throughput Seventh class of the distribution on number of GPRS DL/UL LLC throughput Sixth class of the distribution on number of GPRS DL/UL LLC throughput Fifth class of the distribution on number of GPRS DL/UL LLC throughput Fourth class of the distribution on number of GPRS DL/UL LLC throughput Third class of the distribution on number of GPRS DL/UL LLC throughput Second class of the distribution on number of GPRS DL/UL LLC throughput First class of the distribution on number of GPRS DL/UL LLC throughput
B10
P532b_10
P531a_10
1 3 76
Parameter values in kbits/s (cannot be modified at the OMC-R): GPRS_LLC_THROUGHPUT_THR_1= 10 GPRS_LLC_THROUGHPUT _THR_2 = 20 GPRS_LLC_THROUGHPUT _THR_3 = 30 GPRS_LLC_THROUGHPUT _THR_4 = 40 GPRS_LLC_THROUGHPUT _THR_5 = 50 GPRS_LLC_THROUGHPUT _THR_6 = 60 GPRS_LLC_THROUGHPUT _THR_7 = 70 GPRS_LLC_THROUGHPUT _THR_8 = 80 GPRS_LLC_THROUGHPUT _THR_9 = 90 GPRS_LLC_THROUGHPUT _THR_10 = 500

Distribution based on EGPRS LLC Throughput per session
DL UL Definition
B10
P531b_11
P531a_11
Eleventh class of the distribution on number of EGPRS DL/UL LLC throughput. It contains : 1) number of EGPRS DL/UL LLC throughput whose throughput is in EGPRS LLC throughput class 11. EGPRS LLC throughput class 11 is defined by : EGPRS_LLC_throughput_THR_10<= LLC throughput < EGPRS_LLC_throughput_THR_11 tenth class of the distribution on number of EGPRS DL/UL LLC throughput Ninth class of the distribution on number of EGPRS DL/UL LLC throughput Eighth class of the distribution on number of EGPRS DL/UL LLC throughput Seventh class of the distribution on number of EGPRS DL/UL LLC throughput Sixth class of the distribution on number of EGPRS DL/UL LLC throughput Fifth class of the distribution on number of EGPRS DL/UL LLC throughput Fourth class of the distribution on number of EGPRS DL/UL LLC throughput Third class of the distribution on number of EGPRS DL/UL LLC throughput Second class of the distribution on number of EGPRS DL/UL LLC throughput First class of the distribution on number of EGPRS DL/UL LLC throughput
P531b_10 P531b_9 P531b_8 P531b_7 P531b_6 P531b_5 P531b_4 P531b_3 P531b_2 P531b_1
1 3 77
P531a_10 P531a_9 P531a_8 P531a_7 P531a_6 P531a_5 P531a_4 P531a_3 P531a_2 P531a_1
Parameter values in kbits/s (cannot be modified at the OMC-R): EGPRS_LLC_THROUGHPUT_THR_1= 20 EGPRS_LLC_THROUGHPUT _THR_2 = 40 EGPRS_LLC_THROUGHPUT _THR_3 = 60 EGPRS_LLC_THROUGHPUT _THR_4 = 80 EGPRS_LLC_THROUGHPUT _THR_5 = 100 EGPRS_LLC_THROUGHPUT _THR_6 = 120 EGPRS_LLC_THROUGHPUT _THR_7 = 140 EGPRS_LLC_THROUGHPUT _THR_8 = 160 EGPRS_LLC_THROUGHPUT _THR_9 = 180 EGPRS_LLC_THROUGHPUT _THR_10 = 200 EGPRS_LLC_THROUGHPUT _THR_11 = 500

Distribution based on PDCH usage
DL UL Definition Tenth interval of the distribution on units of PDCH allocated to DL/UL TBFs. For DL It contains : number of DL TBFs whose number of PDCH allocated units is in PDCH units band 10. PDCH units band 10 is defined by : PD_DL_PDCH_UNIT_ALLOC_THR_9<= allocated PDCH units < PD_DL_PDCH_UNIT_ALLOC_THR_10 Ninth cell of the distribution on units of PDCH allocated to DL/UL TBFs. Eighth cell of the distribution on units of PDCH allocated to DL/UL TBFs. Seventh cell of the distribution on units of PDCH allocated to DL/UL TBFs. Sixth cell of the distribution on units of PDCH allocated to DL/UL TBFs. Fifth cell of the distribution on units of PDCH allocated to DL/UL TBFs. Fourth cell of the distribution on units of PDCH allocated to DL/UL TBFs. Third cell of the distribution on units of PDCH allocated to DL/UL TBFs. Second cell of the distribution on units of PDCH allocated to DL/UL TBFs. First cell of the distribution on units of PDCH allocated to DL/UL TBFs.
P455b_10
P455a_10
1 3 78
UL This distribution measures the number of PDCH units assigned to the MS in UL at the release of the UL TBF. An UL PDCH unit represents the percentage of the PDCHs that is used by the assigned UL TBF. This distribution is computed at the release of each UL TBF (i.e. indication of reception of acknowledgement of final PUAN). DL This distribution measures the number of PDCH units assigned to the MS in DL at the release of the DL TBF. A DL PDCH unit represents the percentage of the PDCHs that is used by the assigned DL TBF. This distribution is computed at the release of each DL TBF (i.e. at the expiry of timer T3192).
QoS Indicators, Delayed DL TBF

DL and UL TBF progress: Delayed DL TBF
Delayed DL TBF Cumulated time of active DL GPRS TBF P52a + P52b connections Cumulated time of active DL EGPRS TBF P52c + P52d connections Percentage of time during which the DL TBF (P52a+P52b+P52c+P52d) / P16 * 100 connections are in the active state Percentage of time during which the DL GPRS (P52a + P52b) / P16 *100 TBF connections are in the active state Percentage of time during which the DL EGPRS TBF connections are in the active state Number of DL TBF transfer resumptions in delayed release state Rate of DL TBF transfer resumptions per established DL TBF Number of DL RLC blocks containing only dummy LLC UI Command PDU on PDTCH Number of DL RLC blocks sent on PDTCH Rate of RLC blocks containing only dummy LLC UI commands on DL PDTCH (P52c + P52d) / P16 * 100
P422 P422 / (P90a + P90b + P90c + P90d + P90e + P90f) P421 P350a P421 / P350a
1 3 79
QoS Indicators, Other Throughput Statistics
INDICATOR DEFINITION FORMULA DOWNLINK FORMULA UPLINK THRESHOLD COMMENT REF NAME
AVERAGE USEFUL THROUGHPUT PER PDCH Average of useful throughput on DL or UL PDTCH at RLC level per PDCH in RLC acknowledged mode. CELL (P55a*160 + P55b*240 + P55c*288 + P55d*400 + P55e*176 + P55f*224 + P55g*296 + P55h*352 + P55i*448 + P55j*592 + (P55k*896 + P55l*1088 + P55m*1184)/2) / (P38e*1000) CELL (P57a*160 + P57b*240 + P57c*288 + P57d*400 + P57e*176 + P57f*224 + P57g*296 + P57h*352 + P57i*448 + P57j*592 + (P57k*896 + P57l*1088 + P57m*1184)/2) / (P38f*1000)
New formula in B9 to take into account the new coding schemes in UL.The RLC blocks retransmissions are not counted in both directions. Reference Time: Cumulated time during which the PDCHs are established.
TRPDDPDA, TRPDUPDA
UNIT
Kbits/second
INDICATOR DEFINITION FORMULA DOWNLINK FORMULA UPLINK THRESHOLD COMMENT
AVERAGE USEFUL THROUGHPUT PER CELL Average of useful throughput on DL or UL PDTCH at RLC layer CELL (P55a*160 + P55b*240 + P55c*288 + P55d*400 + P55e*176 + P55f*224 + P55g*296 + P55h*352 + P55i*448 + P55j*592 + (P55k*896 + P55l*1088 + P55m*1184)/2) / (PERIOD*1000) CELL (P57a*160 + P57b*240 + P57c*288 + P57d*400 + P57e*176 + P57f*224 + P57g*296 + P57h*352 + P57i*448 + P57j*592 + (P57k*896 + P57l*1088 + P57m*1184)/2)) / (PERIOD*1000)
New formulas in B9 to take into account the new coding schemes in UL. DL: The DL retransmitted blocks and blocks containing LLC dummy UI commands are not counted. UL: The UL retransmissions are not counted. RLC ack mode only is considered. TRPDDA, TRPDUA UNIT Kbits/second
REF NAME
1 3 80
QoS Indicators, DL TBF states, Graph
DL TBF state
50000 45000 40000 35000 30000 25000 20000 15000 10000 5000 0
14 /0 8/ 20 03 16 /0 8/ 20 03 18 /0 8/ 20 03 20 /0 8/ 20 03 22 /0 8/ 20 03 24 /0 8/ 20 03 26 /0 8/ 20 03 28 /0 8/ 20 03 30 /0 8/ 20 03 01 /0 9/ 20 03 03 /0 9/ 20 03 05 /0 9/ 20 03 07 /0 9/ 20 03 09 /0 9/ 20 03 11 /0 9/ 20 03 13 /0 9/ 20 03
80 70 60 50 40 30 20 10 0
Delay>Active Success % Efficiency % Active
On RNO graphs:
% Efficiency = Rate of DL TBF resumptions per DL TBF establishment % Active = Percentage of time during which the DL TBF connections are in the active state
1 3 81
The typical values of the Efficiency rate and Active rate: Efficiency rate = 40%, 60% Active rate = 15%, 20%
QoS Indicators, TBF Resources Re-allocation

TBF resource re-allocation for each trigger
Nb of TBF candidate resource re-allocations Resource re-allocation Request
Preparation efficiency rate Failures cause No PDCH can be found
Ratio of triggers
Resource re-allocation Attempt

Execution efficiency rate Failures causes Radio problems (real drop) External Stop BSS problem (real drop)
Resource re-allocation Success time

1 3 82
External requests: FLUSH_LL received from the SGSN, Suspended from the MS. Split between Preparation and Execution phases is driven by the fact that the problems to be interpreted during re-allocation are relating to the Trigger type. A TBF Re-allocation is analogue to an Intra cell HO in GPRS.
QoS Indicators, TBF Resources Re-allocation, Trigger T1

DL and UL TBF progress: Resources re-allocation T1
TBF resources re-allocation : trigger T1 Downlink Uplink Nb of TBF candidate for resource realloc P403a Nb of TBF candidate for resource realloc Resource realloc ratio due to trigger T1 P403a / (P403a + P403b + Resource realloc ratio due to trigger T1 P403c + P403d) Nb of resource realloc successes P405a Nb of resource realloc successes Resource realloc success rate P405a / P403a Resource realloc success rate Nb of resource realloc exec fail due to P407a Nb of resource realloc exec fail due to radio problems radio problems Resource realloc exec fail rate due to radio P407a / P403a Resource realloc exec fail rate due to radio problems problems Nb of resource realloc preparation failures P423a Nb of resource realloc preparation failures because no PDCH could be found because no PDCH could be found Resource realloc preparation fail rate due P423a / P403a Resource realloc preparation fail rate due to lack of radio resources to lack of radio resources Resource realloc prep efficiency rate (P403a - P423a) / P403a Resource realloc prep efficiency rate Nb of resource realloc failures due external P425a Nb of resource realloc failures due external request (suspension request or Flush request (suspension request or Flush message) during exec of the realloc message) during exec of the realloc procedure procedure Nb of resource realloc failures due to BSS P403a - P423a - P425a Nb of resource realloc failures due to BSS pb during exec of the realloc procedure P407a - P405a pb during exec of the realloc procedure Exec fail rate due to BSS pb (P403a - P423a - P425a Exec fail rate due to BSS pb P407a - P405a) / P403a Resource realloc exec efficiency rate P405a / (P403a - P423a) Resource realloc exec efficiency rate P404a P404a / (P404a + P404b + P404c + P404d) P406a P406a / P404a P408a P408a / P404a P424a P424a / P404a (P404a - P424a) / P404a P426a
P404a - P424a - P426a P408a - P406a (P404a - P424a - P426a P408a - P406a) / P404a P406a / (P404a - P424a)
1 3 83

TBF resources re-allocation : trigger T2 Downlink Uplink Nb of TBF candidate for resource realloc P403b Nb of TBF candidate for resource realloc Resource realloc ratio due to trigger T1 P403b/ (P403a + P403b + Resource realloc ratio due to trigger T1 P403c + P403d) Nb of resource realloc successes P405b Nb of resource realloc successes Resource realloc success rate P405b / P403b Resource realloc success rate Nb of resource realloc exec fail due to P407b Nb of resource realloc exec fail due to radio problems radio problems Resource realloc exec fail rate due to radio P407b / P403b Resource realloc exec fail rate due to radio problems problems Nb of resource realloc preparation failures P423b Nb of resource realloc preparation failures because no PDCH could be found because no PDCH could be found Resource realloc preparation fail rate due P423b / P403b Resource realloc preparation fail rate due to lack of radio resources to lack of radio resources Resource realloc prep efficiency rate (P403b - P423b) / P403b Resource realloc prep efficiency rate Nb of resource realloc failures due external P425b Nb of resource realloc failures due external request (suspension request or Flush request (suspension request or Flush message) during exec of the realloc message) during exec of the realloc procedure procedure Nb of resource realloc failures due to BSS P403b - P423b - P425b Nb of resource realloc failures due to BSS pb during exec of the realloc procedure P407b - P405b pb during exec of the realloc procedure Exec fail rate due to BSS pb (P403b - P423b - P425b Exec fail rate due to BSS pb P407b - P405b) / P403b Resource realloc exec efficiency rate P405b / (P403b - P423b) Resource realloc exec efficiency rate P404b P404b / (P404a + P404b + P404c + P404d) P406b P406b / P404b P408b P408b / P404b P424b P424b / P404b (P404b - P424b) / P404b P426b
P404b - P424b - P426b P408b - P406b (P404b - P424b - P426b P408b - P406b) / P404b P406b / (P404b - P424b)
1 3 84

TBF resources re-allocation : trigger T3 Downlink Uplink Nb of TBF candidate for resource realloc P403c Nb of TBF candidate for resource realloc Resource realloc ratio due to trigger T1 P403c / (P403a + P403b + Resource realloc ratio due to trigger T1 P403c + P403d) Nb of resource realloc successes P405c Nb of resource realloc successes Resource realloc success rate P405c / P403c Resource realloc success rate Nb of resource realloc exec fail due to P407c Nb of resource realloc exec fail due to radio problems radio problems Resource realloc exec fail rate due to radio P407c / P403c Resource realloc exec fail rate due to radio problems problems Nb of resource realloc preparation failures P423c Nb of resource realloc preparation failures because no PDCH could be found because no PDCH could be found Resource realloc preparation fail rate due P423c / P403c Resource realloc preparation fail rate due to lack of radio resources to lack of radio resources Resource realloc prep efficiency rate (P403c - P423c) / P403c Resource realloc prep efficiency rate Nb of resource realloc failures due external P425c Nb of resource realloc failures due external request (suspension request or Flush request (suspension request or Flush message) during exec of the realloc message) during exec of the realloc procedure procedure Nb of resource realloc failures due to BSS P403c - P423c - P425c Nb of resource realloc failures due to BSS pb during exec of the realloc procedure P407c - P405c pb during exec of the realloc procedure Exec fail rate due to BSS pb (P403c - P423c - P425c Exec fail rate due to BSS pb P407c - P405c) / P403c Resource realloc exec efficiency rate P405c / (P403c - P423c) Resource realloc exec efficiency rate P404c P404c / (P404a + P404b + P404c + P404d) P406c P406c / P404c P408c P408c / P404c P424c P424c / P404c (P404c - P424c) / P404c P426c
P404c - P424c - P426c P408c - P406c (P404c - P424c - P426c P408c - P406c) / P404c P406c / (P404c - P424c)
1 3 85

TBF resources re-allocation : trigger T4 Downlink Uplink Nb of TBF candidate for resource realloc P403d Nb of TBF candidate for resource realloc Resource realloc ratio due to trigger T4 P403d / (P403a + P403b + Resource realloc ratio due to trigger T4 P403c + P403d) Nb of resource realloc successes P405d Nb of resource realloc successes Resource realloc success rate P405d / P403d Resource realloc success rate Nb of resource realloc exec fail due to P407d Nb of resource realloc exec fail due to radio problems radio problems Resource realloc exec fail rate due to radio P407d / P403d Resource realloc exec fail rate due to radio problems problems Nb of resource realloc preparation failures P423d Nb of resource realloc preparation failures because no PDCH could be found because no PDCH could be found Resource realloc preparation fail rate due P423d / P403d Resource realloc preparation fail rate due to lack of radio resources to lack of radio resources Resource realloc prep efficiency rate (P403d - P423d) / P403d Resource realloc prep efficiency rate Nb of resource realloc failures due external P425d Nb of resource realloc failures due external request (suspension request or Flush request (suspension request or Flush message) during exec of the realloc message) during exec of the realloc procedure procedure Nb of resource realloc failures due to BSS P403d - P423d - P425d Nb of resource realloc failures due to BSS pb during exec of the realloc procedure P407d - P405d pb during exec of the realloc procedure Exec fail rate due to BSS pb (P403d - P423d - P425d Exec fail rate due to BSS pb P407d - P405d) / P403d Resource realloc exec efficiency rate P405d / (P403d - P423d) Resource realloc exec efficiency rate P404d P404d / (P404a + P404b + P404c + P404d) P406d P406d / P404d P408d P408d / P404d P424d P424d / P404d (P404d - P424d) / P404d P426d
P404d - P424d - P426d P408d - P406d (P404d - P424d - P426d P408d - P406d) / P404d P406d / (P404d - P424d)
1 3 86
QoS Indicators
DL and UL TBF progress for DTM capable MS
TBF establishment
B10
Cumulated time of DTM operation for DTM capable MS Cumulated time of dedicated mode operation for DTM capable MS
e vic ! ser tion M a DT netr pe
Cumulated time of PTM operation for DTM capable MS
TBF release time

1 3 87
QoS Indicators, Cumulated Time of Operation for DTM MS B10

DL and UL TBF progress for DTM capable MS
Indicator name
CUMULATED_DTM_TIME CUMULATED_DTM_DEDICATED_TIME CUMULATED_DTM_PTM_TIME
definition
Cumulated time during which a DTM capable MS is operating in DTM mode Cumulated time during which a DTM capable MS is operating in dedicated mode Cumulated time during which a DTM capable MS is operating in packet transfer mode
Ref
P502 P503 P504
1 3 88
P502: Starting: when in dedicated mode on the establishment of the first UL or DL TBF. (the first UL RLC data Blocks are received from the MS (case of UL TBF) or the first Packet downlink Ack/Nack message is received from the MS (case of DL TBF)). Stopping: when in DTM mode the CS session or PS session are , normally or abnormally, released. Note: The common duration during which a UL and a DL are established is counted as one duration (UL and DL common time durations are not cumulated). The time duration of all periods (active and delayed/extended) is taken into account. P503: Starting: when the indication of start of a CS session is received (first BSCGP BSC Shared DTM Info Indication with CS=1 received) or when, in DTM mode, PS session is, normally or abnormally, released. Stopping: when in dedicated mode, the first UL RLC data Blocks are received from the MS (case of UL TBF) or the first Packet downlink Ack/Nack message is received from the MS (case of DL TBF) or when in dedicated mode, an indication of stop of CS session is received (BSCGP BSC Shared DTM Info Indication with CS=0 received) or when in dedicated mode, an indication of stop of CS session is received. P504:Cumulated time duration of all UL / DL TBFs established over the Granularity period. Note: DTM capability of the MS is given in RA capabilities, which are known only: in case a DL LLC PDU has been received for this MS in case only an UL TBF exists, once the procedure for RA capability update is finished (provided EN_RA_CAP_UPDATE=1) Note 1: This counter applies only to DTM capable MS not in dedicated mode. Note 2: This counter applies to both GPRS and EGPRS TBFs and to both ACK or UNACK mode. Note 3 : The time duration of all periods (active and delayed/extended) is taken into account. Note 4 : UL and DL TBF duration are not cumulated. The time is provided in seconds with one significant value after the comma (i.e. ROUND(10x) / 10).
3 Data Transfer Release
1 3 89
TBF Release
TBF Release TBF Release
B10
Normal Release
Acceptable Release
Abnormal Release
Cell reselection Cell reselection Suspend Suspend PDCH Fast PDCH Fast Pre-emption Pre-emption Due to CS operation Due to CS operation in DTM in DTM new B10
Radio Radio Re-allocation Re-allocation execution failure execution failure Gb Gb BSS BSS Others Others
1 3 90
Normal TBF Release
Normal TBF release
UL TBF release
DL TBF release
Without Delayed Final PUAN
With Delayed Final PUAN
With extended UL TBF
With Delayed DL TBF release
Without DL TBF Extension
With DL TBF Extension
1 3 91
DL TBF is said to have been extended in case of an UL TBF establishment during the DL TBF delayed release; the DL delayed phase is extended up to the release of the UL TBF and restarted afterwards
UL TBF, Normal Release, without Delayed Final PUAN
MS
MFS
Active UL Data transfer
SGSN
one but last useful RLC data block (CV=1)

PDTCHUL
last useful RLC data block (CV=0) last LLC PDU Packet uplink ack/nack (FAI=1) polling (FAI=1), PACCHDL all blocks acknowledged Packet control ack
P22
In case no DL TBF is established, it is better to delay the UL TBF release to be able to establish quickly a subsequent DL TBF on the PACCHDL of the delayed UL TBF rather than on CCCH or PCCCH
1 3 92
UL TBF, Normal Release, with Delayed Final PUAN

MS MFS
SGSN

PDTCHUL
last useful RLC data block (CV=0) last LLC PDU

PACCHDL
Packet uplink ack/nack (FAI=0) last block not acknowledged
Packet uplink ack/nack (FAI=1), polling PACCHDL last block acknowledged Packet control ack
P22
T_DELAYED_FINAL_PUAN expiry
1 3 93
Timer T_DELAYED_FINAL_PUAN corresponds to the duration during which the UL is maintained alive in order to be able to establish a DL TBF on PACCH: T_DELAYED_FINAL_PUAN = 0.4 s (default value). It can be set at the OMC-R level. It should be long enough to let the server send its response to the uplink PDUs received from the MS, while remaining short enough in order not to jeopardize the sending of further uplink PDUs by the MS. Setting T_DELAYED_FINAL_PUAN = 0 s leads to disable this feature.
UL TBF, Normal Release, with Extended UL TBF

PDTCHUL
last useful RLC data block (CV=0) last LLC PDU

PACCHDL
Packet uplink ack/nack (FAI=0) last block not acknowledged

USF Dummy RLC data block USF Dummy RLC data block
Packet uplink ack/nack (FAI=1), polling PACCHDL last block acknowledged Packet control ack
P22
T_MAX_EXTENDED_UL expiry
1 3 94
DL TBF, Normal Release, Delayed DL TBF no Extension

MS
Active DL data transfer
MFS one but last useful RLC data block (FBI=0)

PDTCHDL
last useful RLC data block (FBI=0), polling

last block not mentioned
T_DELAYED_DL_TBF_POL_INITIAL T_DELAYED_DL_TBF_REL T_DELAYED_DL_TBF_POL
Packet downlink ack/nack (FAI=0)

PACCHUL
not last acknowledgement
Dummy UI command (FBI=0), polling Packet downlink ack/nack (FAI=0)

Delayed DL data transfer
Dummy UI command (FBI=0), polling Packet downlink ack/nack (FAI=0) Dummy UI command (FBI=1), polling
last block mentioned
Packet downlink ack/nack (FAI=1)

DL TBF released
T_DELAYED_DL_TBF_REL expiry P9
last acknowledgement
1 3 95
As soon as all the useful blocks have been transferred, the Delayed DL TBF release procedure is triggered in order to allow: to send a coming LLC PDU frame using the same radio resources without being obliged to establish the DL TBF again (T3192 running or not). the MS to establish a UL TBF on PACCH rather than on CCCH or PCCCH. The DL TBF goes from Active state to Delayed state. As the MS will trigger a local DL TBF release if it does not receive DL RLC data blocks (T3190 is running) the MFS is scheduling Dummy UI command blocks in DL according to the following timers: T_DELAYED_DL_TBF_POL_INITIAL is the duration between the last useful RLC block sent to the MS (eventually completed with a Dummy UI command) and the first Dummy UI command block sent during the DL TBF delayed phase. T_DELAYED_DL_TBF_POL_INITIAL = 60 ms (default value). It cannot be set at the OMC-R level. 2 timers are used to define the period between 2 DL Dummy UIs sent to the MS: T_MIN_POLL (=60ms), in case of the MS is alone on the PDCH which carries the PACCH T_DELAYED_DL_TBF_POL (=200ms) in case of the MS is multiplexed on the PDCH which carries the PACCH A global timer t_delayed_dl_tbf_rel monitors the whole Delayed DL TBF release procedure. At t_delayed_dl_tbf_rel expiry, the DL TBF stays in Delayed phase before being actually released. This timer corresponds to the typical response time of a network server as seen from this MFS. t_delayed_dl_tbf_rel = T_NETWORK_RESPONSE_TIME = 1600 ms (default value). It can be set at the OMC-R level.
DL TBF, Normal Release, Delayed DL TBF with Extension

MS
Delayed DL TBF release is on-going
MFS Dummy UI command (FBI=0), polling Packet downlink ack/nack (FAI=0) with Channel request Packet UL assignment USF Scheduling Dummy UI command (FBI=0), polling UL RLC data block Packet downlink ack/nack (FAI=0)
T_ACK_WAIT
UL TBF establishme nt
T_DELAYED_DL_TBF_REL is stopped T_DELAYED_DL_TBF_POL_UL
Delayed DL TBF release is extended
UL RLC data block
Dummy UI command (FBI=0), polling Packet downlink ack/nack (FAI=0) Packet uplink ack/nack (FAI=1), polling
UL TBF is released
T_DELAYED_DL_TBF_POL_UL
Packet control ack

Delayed DL TBF release is resumed from beginning
T_DELAYED_DL_TBF_REL is restarted
1 3 96
If a UL TBF is established during a Delayed DL TBF release phase then: the countdown of this Delayed DL TBF release phase is stopped (timer t_delayed_dl_tbf_rel). the Dummy UI command blocks are sent in the DL in order that the MS does not release the DL TBF. The Delayed DL TBF release phase is said to be extended. Two cases of UL TBF should be considered: question-answer traffic: corresponds to WAP services or WEB browsing where the UL command induced by the user are small and usually lead to a transfer of only one LLC PDU: The UL polling period induced by Dummy UI command scheduling is kept to T_DELAYED_DL_TBF_ POL. T_DELAYED_DL_TBF_POL_INITIAL = 60ms (default value). It cannot be set at the OMC-R level. Other cases: correspond to applications like UL FTP file transfer where a lot of LLC PDUs have to be transferred during the same TBF: The UL polling period induced by Dummy UI command sending is increased to T_DELAYED_DL_TBF_ UL in order to decrease the UL load due to the Delayed DL TBF release phase in favor of the UL FTP throughput . T_DELAYED_DL_TBF_POL_UL = 2 s (default value). It cannot be set at the OMC-R level. As soon as the UL TBF is released, the Delayed DL TBF: the countdown of the Delayed DL TBF release procedure is resumed from the beginning (t_delayed_dl_tbf_rel restarted). the scheduling period of Dummy UI command blocks for the Delayed DL TBF is set back to T_DELAYED_DL_TBF_ POL. At the end of a Delayed DL TBF procedure, the DL TBF is released and the counter P9 is incremented whether the Delayed DL TBF phase has been extended or not.
TBF Normal Release, Exercise

Exercise1: Using the trace 1, find the duration between two consecutive Dummy UI command blocks during the Delayed DL TBF release procedure Exercise 2: Using trace number 9, find duration of the extended phase
1 3 97
TBF Acceptable Release

Acceptable Release
new B10
B10
Cell reselection Cell reselection
Suspend Suspend
PDCH Fast PDCH Fast Pre-emption Pre-emption
CS operation CS operation in DTM in DTM
MS is reselecting MS is reselecting aaneighbor cell neighbor cell while in PTM while in PTM
MS is MS is establishing aaCS establishing CS connection connection while in PTM while in PTM
PDCH carrying PDCH carrying PACCH of the PACCH of the TBF is to be TBF is to be released released
CS connection CS connection while MS in PTM while MS in PTM
Intercell or Intercell or intracell HO intracell HO
Normal TCH Normal TCH release during release during DTM DTM
1 3 98
TBF Acceptable Release, Cell Reselection, NC0 Scenario 1

MS
DL transfer PDTCHDL
MFS serving cell

useful RLC data block useful RLC data block, polling useful RLC data block useful RLC data block, polling
MFS target cell
SGSN
Packet DL Ack/Nack
PACCHUL
The MS decides for cell reselection
N3105 ++
UL transfer establishment in the new cell UL transfer The MS sends an LLC PDU to warn the SGSN about its new cell location
LLC PDU
(TLLI,new BVCI)
P434c
UL
P434d
DL
FLUSH-LL
(TLLI,old BVCI)
FLUSH-LL ACK
(TLLI)
P396b
P396a
1 3 99
Counter P434d (resp.P434c) gives the number of DL (resp. UL) TBFs which have been released due to an NC0 reselection. It is therefore incremented in this scenario. In this scenario where the FLUSH-LL message is received before the Radio Link Supervision counter N3105 reaches the limit, N3105 is stopped when the FLUSH_LL message is received.Therefore the TBF release is not counted as an abnormal release due to radio. P302b_x (resp. P302c_x) is not incremented. Only P396a (resp. P396b) counting the number of TBF release due to the reception of a FLUSH_LL message is incremented.
TBF Acceptable Release, Cell Reselection, NC0 Scenario 2

MS
DL transfer PDTCHDL
MFS serving cell

MFS target cell
SGSN
Packet DL Ack/Nack
PACCHUL

UL transfer establishment in the new cell
N3105 ++
UL DL
T_WAIT_FLUSH
N3105 limit P302c_x
P302b_x
RADIO STATUS
UL transfer The MS sends an LLC PDU to warn the SGSN about its new cell location
LLC PDU
(TLLI,new BVCI)
UL
P434c
DL
P434d
FLUSH-LL
(TLLI,old BVCI)
FLUSH-LL ACK
(TLLI)
1 3 100
Counter P434d (resp.P434c) gives the number of DL (resp. UL) TBFs which have been released due to an NC0 reselection. It is therefore incremented in this scenario. In this scenario where the FLUSH-LL message is received after the Radio Link Supervision counter N3105 reaches the limit, the radio resources are released when N3105 reaches the limit. Therefore the TBF release is counted as an abnormal release due to radio. P302b_x (resp. P302c_x) is incremented whereas P396a (resp. P396b) is not. The timer T_WAIT_FLUSH is started when the abnormal TBF release is triggered. When the FLUSH_LL message is received while T_WAIT_FLUSH is running then T_WAIT_FLUSH is stopped and P434d (resp. P434c) is incremented. In case the FLUSH_LL message is received after T_WAIT_FLUSH has expired then P434d (resp. P434c) is not incremented but P302b_x (resp. P302c_x) is.
TBF Acceptable Release, Cell Reselection, NC2

MS
DL transfer PDTCHDL
MFS serving cell

MFS target cell
SGSN
T3158
Packet DL Ack/Nack
PACCHUL
Better cell
expiry T3158
The MS switches to the new cell
Packet measurement report

PACCHUL
PACCHDL T_ACK_WAIT
Packet cell change order, polling

new cell (BCCH,BSIC)
Packet control ack

MFS trigger cell reselection

Radio resources are released locally
T_WAIT_FLUSH
UL transfer MS sends an LLC PDU to warn the SGSN about its new cell location
LLC PDU
(TLLI,new BVCI)
P396a
DL
P396b
UL
FLUSH-LL
(TLLI,old BVCI)
FLUSH-LL ACK
(TLLI)
P434b
1 3 101
P434a
The chart above corresponds to the typical scenario of an NC2 reselection. The same P396a (resp. P396b) counter is incremented in case of a TBF release due to an NC0 reselection provided that the FLUSH-LL message is received before a TBF drop is detected. This should almost always happen in case of NC2 cell reselection since the Radio Link Supervision process is frozen after the BSS gets the Acknowledgment of the Packet Cell Change Order message sent to the MS. In case a TBF Abnormal Release is detected by the Radio Link Supervision process then P302b_x (resp. P302c_x) as well as P434b (resp. P434a) is incremented but P396a (resp. P396b) is not. T3158 = NC_REPORTING_PERIOD_T NC2 in PTM or NC_REPORTING_PERIOD_I in case of NC2 in PIM = measurement report interval timer
TBF Acceptable Release, Cell Reselection, Counters

Cell reselection NC0+NC2 P397 MS in PIM MS in PTM
No TBF release
TBF release
TBF release due to flush NC0+NC2 P396b / P396a
TBF release due to radio P302c_x / P302b_x
Flush before T_Wait_Flush expiry TBF release due to cell reselection
after expiry No counter incremented
NC2 P434a / P434b
NC0 P434c / P434d
counter UL TBF / DL TBF
1 3 102
The chart above concerns the PM counters incremented during a cell reselection procedure. P397 is incremented each time a FLUSH_LL is received by the MFS relating to a certain serving cell. P396a, P396b, P434a, P434b, P434c and P434d are incremented only for TBF release during a cell reselection procedure. P302b_x and P302c_x are global counters relating to TBF abnormal release due to radio. They are incremented when the TBF abnormal release is triggered due to a cell reselection or not.
TBF Acceptable Release, MS Suspend, Scenario 1

MS
DL transfer PDTCHDL
BSC
useful RLC data block useful RLC data block, polling
MFS
SGSN
MSC/VLR
Packet DL Ack/Nack
PACCHUL
useful RLC data block useful RLC data block
The MS enters the CS dedicated mode Suspend MS Suspend

P98c
DL DL TBF Release due to Suspend DL UL
Suspend PDU
P98d
UL
P98a P98e
1 3 103
P98b P98f
The counter(s) P98c and/or P98d are incremented counts the number of MS SUSPEND messaged received for a DL (resp UL) TBF. If the TBF is released due to the reception of MS SUSPEND message then the counter P98a and/or P98b is incremented, The difference between P98a and P98e in DL (resp P98b and P98f in UL): see next slide.
TBF Acceptable Release, MS Suspend, Scenario 2

MS
DL transfer PDTCHDL
BSC
MFS
SGSN
MSC/VLR
Packet DL Ack/Nack
PACCHUL
useful RLC data block useful RLC data block DL Abnormal DL TBF Release
P302b_x
RADIO STATUS
T_WAIT_FLUSH
Suspend
MS Suspend
P98c P98e
DL
P98d P98f
UL
1 3 104
If the TBF is released due to the reception of MS SUSPEND message then the counter P98e and/or P98f is incremented, even if the TBF has been released before the reception of the suspend in the previous T_WAIT_FLUSH seconds. When TBF is released before the MFS receives the MS SUSPEND message, in this case the MFS increments the Radio Problem related counter(s) P302b_x and/or P302c_x rather than the counter(s) P98a and/or P98b. In this case the Radio related counter(s) is(are) incremented. The counter(s) P98c and/or P98d are incremented in both cases since P98c (resp P98d) counts the number of MS SUSPEND messaged received for a DL (resp UL) TBF.
TBF Acceptable Release, Fast Preemption
MS
DL transfer PDTCHDL
MFS
Packet DL Ack/Nack
PACCHUL
useful RLC data block useful RLC data block
Traffic load
Packet TBF release

PACCHDL
P146 P147
The PDCH carrying the PACCH of the TBF is released
DL
UL
1 3 105
A PDCH de-allocation following a PDCH preemption procedure can lead to a TBF release before the normal end of the TBF if the PACCH of the related TBF is carried by the PDCH which is de-allocated. This can be avoided thanks to the TBF Re-allocation procedure on Trigger T1. However if radio resources are lacking the TBF Re-allocation can failed and the TBF is abnormally released.
TBF Acceptable Release, CS Connection while MS in PTM

MS BTS BSC MFS SGSN
B10
MSC
PTM (UL or/and DL TBF (1) PTM

Paging Request Packet Paging Request (3) CS paging Paging CS (2) IMSI T_WAIT_DTM
[PACCH]
Packet Paging Request (4)
SDCCH Assignment (5) Dedicated SCCP Connection (6)

BSC Shared DTM Info Indication (7)
P509 P510
DL UL
DTM Connection DTM

1 3 106
The DTM MS is in uplink or/and downlink packet transfer mode. The MFS receives a CS paging from the SGSN and checks whether or not the MS is in packet transfer mode. As the MS is in packet transfer mode, the MFS forwards the CS paging to the MS in a Packet Paging Request message on PACCH. The MFS starts the timer T_WAIT_DTM to monitor the MS access after the CS paging. At this stage, the MFS does not force the release of the UL TBF and lets the RLC layer detect the abnormal DL TBF release. On receipt of the Packet Paging Request message, the MS aborts its on-going UL TBF, leaves the packet transfer mode, and enters the dedicated mode. The MS requests a SDCCH resource. The BSC assigns to the MS a SDCCH resource. The BSC requests an SCCP connection and forwards the MS classmark to the MSC. As soon as the MSC knows the IMSI of the MS and that the MS is DTM capable, the MSC shall send the Common ID message to the BSC (assuming that the MSC supports DTM). On receipt of the Common ID, the BSC informs the MFS that the MS has just entered the dedicated mode (through the BSC Shared DTM Info Indication message). This message also includes the classmark of the MS. On receipt of the BSC Shared DTM Info Indication message, the MFS forces the release of the previous TBFs provided that they are still alive and stops T_WAIT_DTM timer.
TBF Acceptable Release, Intercell HO

MS Serving BTS Target BSC BTS MFS SGSN
B10
MSC
DTM
DTM (1)
HO execution (2)
HO Performed
Dedicated
BSC Shared DTM Info Indication (3) Old cell BSC Shared DTM Info Indication (4) New cell
P509 P510
DL UL
(incremented in the old cell)
DTM Connection in the new cell DTM
Cell Update or RA Update
1 3 107
The MS is in Dual Transfer Mode. The MS performs its access in the new cell. At reception of BSCGP BSC Shared DTM info indication (CS_flag = 0, CS cause intercell handover) in the old cell, the MFS deletes the MS context. At reception of BSCGP BSC Shared DTM info indication (CS_flag = 1, CS cause intercell handover) in the new cell, the MFS creates a new MS DTM context according to the information received from the BSC.
TBF Acceptable Release, TCH Release in DTM

MS BTS BSC MFS SGSN
B10
MSC
DTM (1) DTM

Clear Command (2) Channel Release (3)
PIM
BSC Shared DTM Info Indication (4)
P509 P510
DL UL
DL or UL TBF establishment
PTM
1 3 108
The MS is in Dual Transfer Mode. The BSC receives a 48.008 Clear Command message to release the CS connection. The BSC sends to the MS a 44.018 Channel Release message. On receipt of the Channel Release message, the MS starts timer T3110, disconnects the main signaling link, aborts its on-going TBFs and returns to the packet idle mode (listening to the (P)CCCH). At this stage, the MFS does not force the release of the on-going TBFs and lets the RLC layer detect the abnormal TBF releases. At the transition from the dual transfer mode to the packet idle mode, the MS shall enter the Transfer non-DRX mode period. Through the BSC Shared DTM Info Indication message, the BSC indicates to the MFS that the MS has left just the dual transfer mode. This message is also used by the MFS to indicate that the MS has entered the Transfer non-DRX period. On receipt of the BSC Shared DTM Info Indication message, the MFS forces the release of the previous TBFs provided that they are still alive.
TBF Abnormal Release

Acceptable Release
Radio Radio
BSS BSS
Gb Gb
Others Others
Re-allocation execution failure
new B10
Real radio link failure

N3105 Tx Efficiency N3101
Blocking Blocking Situation Situation Stagnating Stagnating window window
Radio Link Radio Link Failure Failure
N3103 N Polling EUTM
Some Suspend Some Suspend

Real radio problems
1 3 109
Some cell reselection Some cell reselection

Real radio problems corresponds to: TBF release due to a radio resource reallocation failure TBF release due to the Suspend or Cell reselection cases which are counted as a TBF release due to radio problem
TBF, Abnormal Release, Radio

Radio link failure:
DL
P302b_x
UL
P302c_x
Real Radio link failure:

Coverage Interference Too low efficiency of RLC blocks transmission
Some Suspend :
DL
P98c-P98a
DL
UL
P98d-P98b
UL
Some Cell reselection :
P434b+P434d-P396a
P434a+P434c-P396b
Re-allocation execution failure:
P407a+P407b+P407c+P407d
UL DL
P408a+P408b+P408c+P408d
1 3 110
A radio link failure can be due to a real radio problem like coverage, interference but also to undetected problems at BSS level like bad hardware components, Abis microwave link transmission. After a radio link failure, a RADIO STATUS message is sent to the SGSN on Gb interface with one of the following causes: radio contact lost with the MS: when the radio block transfer has been interrupted. radio link quality insufficient to continue the communication: when the radio block transfer is not efficient enough. Reminder: N3105 is the counter monitoring the radio link during a DL TBF. It is incremented each time a Packet Downlink Ack/Nack message scheduled by the MFS is not received from the MS. N3101 is the counter monitoring the radio link during a UL TBF. It is incremented each time an up-link RLC block scheduled by the MFS is not received from the MS. N3103 is the counter monitoring the normal end of a UL TBF. It is incremented each time the Final Packet Control Ack message scheduled by the MFS at the end of the UL TBF is not received from the MS.
TBF, Abnormal Release, Gb, BSS, Others

Gb:
P11 P24
DL
UL
BSS: no specific counter
Other abnormal release cases:

Blocking situation (MS error, too high UL traffic) Stagnating transmission window (MS error, radio problem)
P303a
DL
P303b
UL
P385a
P385b
1 3 111
Exercise
Exercise 1: Using the trace 11, find which kind of TBF release is observed Exercise 2: Using the trace 13, find which kind of TBF release is observed
1 3 112
QoS Indicators
DL and UL TBF release
TBF establishment TBF end Normal release rate Acceptable release rate Radio Drop causes Cell reselection
B10
PDCH fast preemption Suspend procedure CS operation in DTM

new B10
Radio fail during resource re-alloc exec BSS
time
modified B10
Gb Other problems: blocking situation + N_stagnating window
1 3 113
QoS Indicators, KPI

A MODIFIER
B10
DL and UL TBF release: Drop rate

TBF releases and drops Downlink Normal release rate Uplink Normal release rate P9 / (P90a + P90b + P90c + P90d + P90e + P90f + P506) (P146 + P98c + P434b + P434d + P509) / (P90a + P90b + P90c + P90d + P90e + P90f + P506) (P90a + P90b + P90c + P90d + P90e + P90f - P9 - P146 - P98c - P434b P434d - P509) / (P90a + P90b + P90c + P90d + P90e + P90f + P506) P146 / (P90a + P90b + P90c + P90d + P90e + P90f + P506) P98a / (P90a + P90b + P90c + P90d + P90e + P90f + P506) (P434b + P434d) / (P90a + P90b + P90c + P90d + P90e + P90f + P506) P509 / (P90a + P90b + P90c + P90d + P90e + P90f + P506) P22 / (P30a + P30b + P30c + P508) (P147 + P98d + P434a + P434c + P510) / (P30a + P30b + P30c + P508) (P30a + P30b + P30c + P508 - P22 P147 - P98d - P434a - P434c - P510) / (P30a + P30b + P30c + P508) P147 / (P30a + P30b + P30c + P508) P98b / (P30a + P30b + P30c + P508) (P434a + P434c) / (P30a + P30b + P30c + P508) P510 / (P30a + P30b + P30c + P508)
KPI KPI
KPI KPI
Acceptable release rate
Acceptable release rate
Drop rate
Drop rate
KPI
Release rate due to PDCH fast pre-emption Release rate due to suspend procedure from MS Release rate due to cell reselection Release rate due to CS operation in DTM
KPI
Release rate due to PDCH fast pre-emption Release rate due to suspend procedure from MS Release rate due to Flush message Release rate due to CS operation in DTM
new B10
new B10
1 3 114
QoS Indicators, TBF Abnormal Release

DL and UL TBF release: TBF drops
TBF drop causes Downlink Radio problem : radio link failure Real radio drop rate P302b_1 + P302b_2 / (P90a + P90b + P90c + P90d + P90e + P90f + P506) P302b_1 + P302b_2 - (P98c - P98a) - (P434b + P434d - P396a) + P407a +P407b + P407c + P407d) / (P90a + P90b + P90c + P90d + P90e + P90f + P506) Radio problem : real radio pb + reselections Real radio drop rate Uplink
B10
P302c_1 + P302c_2 + P302c_3 + P302c_4/ (P30a + P30b + P30c + P508) (P302c_1 + P302c_2 + P302c_3 + P302c_4/ (P98d - P98b) - (P434a + P434c - P396b) + P408a +P408b + P408c + P408d) / (P30a + P30b + P30c + P508)
Radio failure during radio resource realloc execution Gb problem N_StagnatingWindow Blocking situation BSS problem
(P407a + P407b + P407c + P407d) / (P90a + P90b Radio failure during (P408a + P408b + P408c + P408d) / (P30a + P30b + P90c + P90d + P90e + P90f + P506) radio resource realloc + P30c + P508) execution P11 / (P90a + P90b + P90c + P90d + P90e + P90f + P506) P385a / (P90a + P90b + P90c + P90d + P90e + P90f + P506) P303a / (P90a + P90b + P90c + P90d + P90e + P90f + P506) (GPRS_DL_TBF_drop GPRS_DL_TBF_real_drop_radio GPRS_DL_TBF_drop_GB GPRS_DL_TBF_drop_N_stagnatingWindow GPRS_DL_TBF_drop_blocking) / GPRS_DL_TBF_success Gb problem N_StagnatingWindow Blocking situation BSS problem P24 / ( P30a + P30b + P30c + P508) P385b / (P30a + P30b + P30c + P508) P303b / (P30a + P30b + P30c + P508) (GPRS_UL_TBF_drop GPRS_UL_TBF_real_drop_radio GPRS_UL_TBF_drop_GB GPRS_UL_TBF_drop_N_stagnatingWindow GPRS_UL_TBF_drop_blocking) / GPRS_UL_TBF_success
1 3 115
P302b and P302c have been removed in B10 and replaced by (P302b_1 + P302b_2) and (P302c_1 + P302c_2 + P302c_3 + P302c_4). On a DL TBF: Radio problem: N3105 exceeds the limit (6) or too low TX efficiency (<10%). Blocking situation: no reception of the PDAN with Final indicator = 1 at the end of the Downlink TBF during T_TBF_BCK_REL = 3 seconds (MS error) OR the transmission window of the MFS is stalled during T_TBF_BCK_REL = 3 seconds (radio problem). Stagnating window: the RLC counter N_StagnatingWindowDL is incremented when the Same oldest RLC data block in the transmittion window is not acknowledged by the received bitmap of the last Packet Downlink Ack/Nack message. The DL TBF is released because the RLC counter N_Stagnating WindowDL exceeds the system parameter N_STAGNATING_ WINDOW_DL_LIMIT =8 (MS error). On a UL TBF: radio problem: N3101 or N3103 exceeds the limits (48 and 1) or too low TX efficiency (<10%). Blocking situation: Reception of N_UL_Dummy_Limit = 15 dummy UL RLC blocks (MS error or radio problem) OR no reception of the Packet Control Ack at the end of the Uplink TBF during T_TBF_BCK_REL = 3 seconds (MS error). Stagnating window: the RLC counter N_StagnatingWindowUL is incremented provided that the receive window is stalled whenever a UL RLC data block whose BSN is different from the receive window state variable V(Q) and is received a round trip delay after the previous sending of a Packet Uplink Ack/Nack message. The UL TBF is released because the RLC counter N_StagnatingWindowUL exceeds the system parameter N_STAGNATING_WINDOW_UL_LIMIT = 8 (MS error or radio problem).
QoS Indicators, TBF Abnormal Release [cont.]

DL and UL TBF release: TBF radio drops
Indicator name
NB_DL_TBF_REL_DUE_TO_RADIO_FAILURE_N3105
B10
definition
Number of times a DL TBF is released because of a radio failure. Considered radio failure is: - a radio link lost due to N3105 (N3105 exceeds its limit) Number of times a DL TBF is released because of a radio failure. Considered radio failure is: - too low TX efficiency. Number of times a UL TBF is released because of a radio failure. Considered radio failure is: - a radio link lost due to N3101 (N3101 exceeds its limit) Number of times a UL TBF is released because of a radio failure. Considered radio failure is: - a radio link lost due to N3103 (N3103 exceeds its limit) Number of times a UL TBF is released because of a radio failure. Considered radio failure is: - too low TX efficiency. Number of times a UL TBF is released because of a radio failure. Considered radio failure is: - a radio link lost due to N_POLLING_EUTM (N_POLLING_EUTM exceeds its limit)
Ref
P302b_1
NB_DL_TBF_REL_DUE_TO_RADIO_FAILURE_TX_EFF
P302b_2
NB_UL_TBF_REL_DUE_TO_RADIO_FAILURE_N3101
P302c_1
NB_UL_TBF_REL_DUE_TO_RADIO_FAILURE_N3103
P302c_2
NB_UL_TBF_REL_DUE_TO_RADIO_FAILURE_TX_EFF
P302c_3
NB_UL_TBF_REL_DUE_TO_RADIO_FAILURE_N_POLLING_EUTM
P302c_4
1 3 116
QoS Indicators, TBF Drops, Graph
Downlink Data Transfer

BSS pb
500 450 400 350 300 250 200 150 100 50 0
14 /0 8/ 20 03 16 /0 8/ 20 03 18 /0 8/ 20 03 20 /0 8/ 20 03 22 /0 8/ 20 03 24 /0 8/ 20 03 26 /0 8/ 20 03 28 /0 8/ 20 03 30 /0 8/ 20 03 01 /0 9/ 20 03 03 /0 9/ 20 03 05 /0 9/ 20 03 07 /0 9/ 20 03 09 /0 9/ 20 03 11 /0 9/ 20 03 13 /0 9/ 20 03
120 100 80 60 40 20 0
Gb drop Blocking drop Stagnat drop Radio pb % Acc Release % Norm Release
Uplink Data Transfer

BSS pb
350 300 250 200 150 100 50 0 120 100 80 60 40 20 0
Gb drop Blocking pb Stagnat pb Radio pb % Acc Release % Norm Release
1 3 117
The causes of drop during a DL data transfer are mainly radio problems. The causes of drop during a UL data transfer are radio problems + blocking problems (MS error suspected because seen on every network).
14 /0 8/ 20 03 16 /0 8/ 20 03 18 /0 8/ 20 03 20 /0 8/ 20 03 22 /0 8/ 20 03 24 /0 8/ 20 03 26 /0 8/ 20 03 28 /0 8/ 20 03 30 /0 8/ 20 03 01 /0 9/ 20 03 03 /0 9/ 20 03 05 /0 9/ 20 03 07 /0 9/ 20 03 09 /0 9/ 20 03 11 /0 9/ 20 03 13 /0 9/ 20 03
QoS Indicators, TBF Drops, Graph [cont.]

Thresholds
When the Delayed DL TBF release is not activated and CS2 is not used at the beginning of the TBF:
the UL/DL TBF normal release rate is seen as good above 98%
When the Delayed DL TBF release is activated or CS2 is used at the beginning of the TBF (default value):
The threshold of the DL TBF normal release rate should be lower
1 3 118
The QoS threshold values assume that the MS mobility (reselection) is negligible. The typical values for a DL TBF normal release rate: When a Delayed DL TBF release is activated: 95% When a Delayed DL TBF release is activated and CS2 is activated at the beginning of the TBF: 90% The longer the TBF duration the higher the probability to drop. There is a high probability to be in CS2 during the Delayed phase. The typical values for UL TBF normal release rate: When CS2 is activated at the beginning of the TBF: 98.3%, 98.9% A UL TBF is often short. The Coding Scheme is always CS1 during the MS contention resolution (based on TLLI) for security. RLS procedures are active during the delayed phase.
4 MS Sessions / Transfers
1 3 119
Definitions
Transfer
Exchange of RLC data blocks between the MS and the BSS The bias of a transfer is the main direction of the transfer in terms of number of bytes transferred
Session
Uninterrupted sequence of data transfers between the MS and the BSS
begin: a UL or DL TBF is established for an MS in PIM on-going: at least one TBF is established end: the last on-going UL or DL TBF is released
1 3 120
During a transfer the MS and the BSS exchange some RLC blocks either in UL only or in DL only or in the two directions. A transfer can correspond to: One complete TBF Part of one TBF Part of two TBFs One complete TBF together with part of one TBF in the other direction The first transfer of a session corresponds to the start of the first TBF of the session. Then the Alcatel BSS regularly determines the bias of the on-going transfer of the MS. The number of octets transferred in both directions is counted and averaged for that purpose. If disabled, the bias remains the one chosen at the establishment of the TBF. By default, a transfer is deemed downlink biased (at first establishment), except in case the MS context is created upon receipt of a 2-phase access UL establishment request, in which case the bias is set to uplink. As soon as the bias of the transfer is about to change the ongoing transfer terminates and a new transfer begins. A session never ends when a DL TBF is released but at the expiry of timer T3192, in case there is no UL TBF on-going in the meantime.
Example
A session made up of:
5 TBFs (1 DL, 4 UL) 3 transfers (1 DL biased, 2 UL biased)
change of bias change of bias
DL TBFs
active
delayed
UL TBFs Bias UL Xfer 1 DL Xfer 2 Session

1 3 121
UL Xfer 3
Transfers
Transfer 1 and 3 are UL biased. Transfer 2 is DL biased.
Exercise
B10
Exercise 1: Using the trace 2bis, find bias direction along transfer
1 3 122
QoS Indicators
Sessions and transfers
Session Number of sessions Average duration Average number of DL/UL TBF per session
Transfer
Cumulated time an MS is engaged in DL/UL biased transfers % of time DL/UL TBF are granted the maximum nb of PDCHs they support and the corresponding MSs are engaged in DL/UL biased transfers
1 3 123
QoS indicators, MS Sessions

MS Sessions
GPRS/EGPRS sessions
Number of GPRS and EGPRS sessions Average duration of a session Downlink Average number of DL ( (P90a + P90b + P90c + P90d Average number of TBF established per + P90e + P90f + P506) / UL TBF established per session session (P413)) P413 (P419+ P420) / P413 Uplink ( (P30a + P30b + P30c + P508) / (P413))
1 3 124
QoS Indicators, MS Transfers

MS Transfers
Bias of the ongoing transfers
Downlink Cumulative time MS are engaged in DL biased transfers Donwlink biaised ratio Cumulative time MS are served by DL TBF and engaged in DL biased transfers P419 P419 / (P419 + P420) Uplink Cumulative time MS are engaged in UL biased transfers Uplink biaised ratio Cumulative time MS are served by UL TBF and engaged in UL biased transfers Cumulative time UL TBF are granted the maximum number of PDCH they support and the corresponding MS are engaged in UL biased transfers % of time UL TBF are granted the maximum number of PDCH they support and the corresponding MS are engaged in UL biased transfers P420 P420 / (P419 + P420)
P411
P412
Cumulative time DL TBF are granted the maximum number of PDCH they support and the corresponding MS are engaged in DL biased transfers % of time DL TBF are granted the maximum number of PDCH they support and the corresponding MS are engaged in DL biased transfers
P409
P410
P409 / P411
P410 / P412
1 3 125
Determination of the Bias: Uplink: when a first UL TBF is established using the 2-phase access on a CCCH or PCCCH Downlink: in any other case
QoS Indicators, MS Transfers, Example

change of bias PDCH preemption of 2 TS active DL TBFs
3TS 4TS 4TS 2TS
change of bias delayed

2TS 2TS
UL TBFs Bias
2TS
1TS
1TS
1TS
2TS
UL Xfer 1
DL Xfer 2 Session
UL Xfer 3
Transfers
time P419
DL
P411 P409 P420 P412 P410

1 3 126
UL
Transfer 1 and 3 are UL biased. Transfer 2 is DL biased.
QoS Indicators, Graph
DL session
250000 200000 150000 100000 50000 0
14 /0 8/ 20 03 16 /0 8/ 20 03 18 /0 8/ 20 03 20 /0 8/ 20 03 22 /0 8/ 20 03 24 /0 8/ 20 03 26 /0 8/ 20 03 28 /0 8/ 20 03 30 /0 8/ 20 03 01 /0 9/ 20 03 03 /0 9/ 20 03 05 /0 9/ 20 03 07 /0 9/ 20 03 09 /0 9/ 20 03 11 /0 9/ 20 03 13 /0 9/ 20 03
102 100 98 96 94 92 90 88 86
Time Opt alloc DL Time bias Time bias %Time Opt Alloc
UL session
6000 5000 4000 3000 2000 1000 0
14 /0 8/ 20 03 16 /0 8/ 20 03 18 /0 8/ 20 03 20 /0 8/ 20 03 22 /0 8/ 20 03 24 /0 8/ 20 03 26 /0 8/ 20 03 28 /0 8/ 20 03 30 /0 8/ 20 03 01 /0 9/ 20 03 03 /0 9/ 20 03 05 /0 9/ 20 03 07 /0 9/ 20 03 09 /0 9/ 20 03 11 /0 9/ 20 03 13 /0 9/ 20 03
120 100 80 60 40 20 0
Time Opt alloc UL Time bias Time bias %Time Opt Alloc
1 3 127
The typical values of the DL TBF optimal allocation time rate (without resource re-allocation): Without congestion (GSM+GPRS): 93%, 94%, 95%, 96% With congestion: 79.5% The UL TBF optimal allocation time rate can be biased, due to the restriction on P29. However, on small area, it can give typical values: Without congestion (GSM+GPRS): 68.5%, 76%, 92%, 98% With congestion: 98% These typical values are highly dependent on the penetration rate of class 9 or class 10 mobiles (mobiles able to use 2 TSs on the UL path).
5 Resource Usage
1 3 128
5 Resource Usage
BSS Resources, Air Interface

The BSS uses several resources to transfer data between the MS and the GPRS core network Air interface resources
Physical channels: MPDCH, SPDCH logical channels:
control channels
without MPDCH: BCCH, AGCH, PCH, RACH with MPDCH: PBCCH, PAGCH, PPCH, PRACH
traffic channels: PDTCH associated signaling channel: PACCH
1 3 129
5 Resource Usage
BSS Resources, GPU

The GPU resource (BSS internal resource)
The GPRS traffic of a group of cells is handled by the GPU function mapped on a hardware component: the GPU board
Ater G P
Gb
BSC
8 PCM
U 8 PCM
SGSN
in MFS equipment
UL
1 3 130
Each GPU handles the GPRS traffic of cells belonging to the same BSS. There is a maximum number of GPUs to monitor the traffic of one BSS. Up to 240 PDCHs can be active at the same time on the same GPU.
5 Resource Usage
BSS Resources, Abis/Ater Interface

The Abis resources can be seen as a pool of Abis nibbles shareable between all TREs of a given sector (basic Abis nibbles) or all the TREs of a given BTS (extra and bonus Abis nibbles). An M-EGCH organizes the transmission resources (pool of Abis nibbles and Ater nibbles) given to a TRX for its PS traffic.
TRX 3
M-EGCH 3 TRX 2
Abis
TRX 1
M-EGCH 2
Ater
M-EGCH 1
1 3 131
For EGPRS traffic, an EGCH physical channel is allocated per PDCH which is a set of n GCHs, n depending on the maximum CS or MCS number that can be used on the PDCH:
Scheme CS-1 CS-2 CS-3 CS-4 MCS-1 MCS-2 MCS-3 MCS-4 MCS-5 MCS-6 MCS-7 MCS-8 MCS-9
Modulation GMSK GMSK GMSK GMSK GMSK GMSK GMSK GMSK 8-PSK 8-PSK 8-PSK 8-PSK 8-PSK
Raw data rate (in kbit/s) 8 12 14.4 20 8.8 11.2 14.8 13.6 17.6 22.4 29.6 27.2 44.8 54.4 59.2
Number of GCH 1 1 2 2 1 1 2 2 2 2 3 3 4 4 5
5 Resource Usage
BSS Resources, Gb Interface

Gb interface resource
A BVC is the logical identifier to which is linked the traffic of a cell carried over the Gb interface The traffic of all the BVCs controlled by the same GPU is multiplexed and carried by the 64 Kbit/s PCM time slots on the Gb interface
Gb
BSC1
GPU
SGSN
8 PCM
BSC2
1 3 132
5 Resource Usage
BSS Resources, BSC - MFS Exchanges

BSC MFS messages
RR Allocation Indication
BSC RR Usage Indication
MFS
1 3 133
Thanks to the Autonomous Packet Resource Allocation feature, the MFS no longer needs to request the BSC for additional SPDCHs (as in B8); as all the usable PS-capable radio timeslots are explicitly allocated to the MFS through the RR Allocation Indication message. However, the RRM-PRH entity has the responsibility for handling the RR Allocation Indication and RR Usage Indication messages, especially for the following tasks: interpretation of the SPDCHs_Allocation bitmap contained in the RR Allocation Indication message (in particular, if a SPDCH is removed in the bitmap, then a preemption process may have to be started, cf. section 4 for more details), building and sending of the SPDCHs_Confirmation bitmap, the SPDCHs_Usage bitmap, the SPDCHs_RadioUsage bitmap and the DTM_TCH bitmap, through the RR Usage Indication message.
5 Resource Usage
BSS Resources, BSC - MFS Exchanges, GTTP UL
B10
MS
BSC
MFS
Dedicated mode (SDCCH/TCH) (1)

[main DCCH] GPRS Information [UL LLC PDU] (2) BSCGP DTM GPRS Info UL [1st segment](3)
BSCGP DTM GPRS Info UL [2nd segment](3) UL LLC PDUs (4)

P513
1 3 134
1. The MS is in dedicated mode and required to send GPRS signaling information to the SGSN (for
instance to perform a cell update).

2. Provided that the GPRS signaling information can be encoded in the MAX_LAPDm LAPDm frames,
the MS sends on the main DCCH the GPRS Information message to the BTS. The BTS assembles the LAPDm frames received in the GPRS Information message and forwards it to the BSC on RSL.
3. The BSC forwards the GPRS information to the MFS through a BSCGP DTM GPRS Information UL
message. This message contains the 44.060 GPRS Information and the references of the MS (i.e., the IMSI and the BSC reference).
4. The MFS decodes the 44.060 GPRS Information message and builds accordingly the UL LLC PDU.
Then, the MFS sends the UL LLC PDU towards the SGSN. P513: Number of bytes received from the MS with the GTTP protocol. This counter is incremented by the number of bytes of the UL LLC PDU carried in the BSCGP DTM GPRS information messages received in MFS.
5 Resource Usage
BSS Resources, BSC - MFS Exchanges, GTTP DL

MS BSC MFS
B10
Dedicated mode (SDCCH/TCH) (1)

DL LLC PDUs (2)
BSCGP DTM GPRS Info DL (3) [main DCCH] GPRS Information [DL LLC PDU] (4) BSCGP DTM GPRS Info DL ACK (4)
P514
T_WAIT_DTM
1 3 135
1. The MS is DTM capable and in dedicated mode. 2. The MFS receives a DL LLC PDU with the T-bit set in the QoS Profile IE (for instance if the MS is
performing a RA update to send the RA Update Accept message).

3. As the MFS is aware that the MS is in dedicated mode, it checks whether the DL LLC PDUs can be
encoded in the MAX_LAPDm LAPDm frames available. If this is the case, the MFS builds the 44.060 GPRS Information message containing the DL LLC PDU and sends it to the BSC in the BSCGP DTM GPRS Information DL message. In addition, the BSCGP DTM GPRS Information message contains the references of the MS (i.e., the IMSI and the BSC reference) and possibly the SDCCH/TCH identity of the CS connection.
4. The BSC forwards the message to the BTS on RSL. Then, the BTS possibly segments the message
and sends it to the MS on the main DCCH. The BSC acknowledges to the MFS the sending of DL LLC PDU through the message DTM GPRS Information DL ACK. P514: Number of bytes sent to the MS with the GTTP protocol. This counter is incremented by the number of bytes of the DL LLC PDU carried in the BSCGP DTM GPRS information messages sent by MFS. Note: Possible repetitions of the messages are not taken into account i.e only the DL_LLC_PDU acknowledged by BSCGP DTM GPRS information ack message are take into account.
5 Resource Usage
BSS Resources, Scenario for GCH Establishment

MFS
Selection of the Ater and Abis nibbles (1) (2) Abis-Nibbles-Allocation (All the BTS Abis nibble ids) (3) Those two messages are sent in sequence by the MFS Transmission-Allocation-Request (Ater nibble ids, BSC Abis nibble ids, MFS connection references) (6) Ater to Abis nibble switching (7) Transmission-Allocation-Confirm (Ater and BSC Abis nibble ids, MFS and BSC connection references) (8) RSL-Allocate-Abis-Nibbles (All the BTS Abis nibble ids) (4)
BSC
BTS
Abis nibble allocation to the TRE (5)
64K Ater TS crossconnection to DSP (9) Activate (TRE-Id) (10)
Activate-Ack (11)
As many as the number of new GCHs in the MEGCH link
The established GCHs can carry PS traffic
1 3 136
This GCH establishment scenario is valid if there are free ABIS and Ater resources (nibbles).
5 Resource Usage
BSS Resources, Scenario for GCH Release

MFS BSC
Release (1) As many as the number of GCHs to remove from the MEGCH link RSL-Allocate-Abis-Nibbles (All the remaining BTS Abis nibble ids) (4)
BTS
Release-Ack (2)
Abis-Nibbles-Allocation (All the remaining BTS Abis nibble ids) (3) Those two messages are sent in sequence by the MFS Transmission-Deallocation-Command (BSC connection references) (6)
Abis nibble deallocation from the TRE (5)
Ater to Abis nibble deswitching (7) Transmission-Deallocation-Complete
(Ater nibble ids, MFS connection references) (8)

,) 64K Ater TS decrossconnection from DSP (9)
Release of the Ater and Abis nibbles (10) (11)
1 3 137
This GCH establishment scenario is valid if there are free ABIS and Ater resources (nibbles).
5 Resource Usage
Exercise
Exercise 1: using trace 1 , identify the different messages for Abis and Ater resource allocation. Exercise 2 : using same trace find different messages for the de allocation of these resources
1 3 138
5 Resource Usage
QoS Indicators, PDCH

GPRS radio resources: PDCH
Smooth PDCH traffic adaptation Average, max, min number and reduction rate of MAX_SPDCH_LIMIT Cumulated time PDCHs: - use at least one DL/UL TBF - carry GMM traffic PDCH dynamic establishment success rate Soft preemption
PDCH usage
1 3 139
5 Resource Usage
QoS Indicators, MAX_SPDCH_LIMIT Follow-up

GPRS radio resources PDCH: MAX_SPDCH_LIMIT
INDICATOR DEFINITION FORMULA MAX_SPDCH_LIMIT AVERAGE VALUE Average value of allocated SPDCH over the observation period.
CELL
(P414bis) / (PERIOD)
INDICATOR DEFINITION FORMULA
MAX_SPDCH_LIMIT MAX VALUE Maximum value of allocated SPDCH in the whole granularity period.
CELL
(P415bis)
MAX_SPDCH_LIMIT MIN VALUE Minimum value of allocated SPDCH in the whole granularity period.
CELL
(P416bis)
MAX_SPDCH_LIMIT REDUCTION RATE Reduction rate of allocated SPDCH value integrated over the granularity period.
CELL
((P415bis*GP) P414bis) / (P415bis*GP))
1 3 140
5 Resource Usage
QoS Indicators, PDCH Usage
Counter number P451a P451b P452
Name CUMULATED_TIME_PDCH_UL_TBF_CELL CUMULATED_TIME_PDCH_DL_TBF_CELL CUMULATED_TIME_PDCH_DL_TBF_GMM_SIG_CELL
Definition Cumulated time during which an UL TBF uses one PDCH, for all PDCHs of the TBF, and for all TBFs of the cell (in GPRS or EGPRS mode). Cumulated time during which an DL TBF uses one PDCH, for all PDCHs of the TBF, and for all TBFs of the cell (in GPRS or EGPRS mode). Cumulated time during which a DL TBF established for GMM signalling purposes uses a PDCH (in GPRS or EGPRS mode), for all TBFs of the cell. Cumulated time during which a PDCH is used by at least one DL TBF (in GPRS or EGPRS mode), cumulated over all the PDCHs of the cell. Cumulated time during which a PDCH is used by at least one UL TBF (in GPRS or EGPRS mode), cumulated over all the PDCHs of the cell.
P38e P38f
CUMULATED_TIME_PDCH_USED_DL_CELL CUMULATED_TIME_PDCH_USED_UL_CELL
1 3 141
5 Resource Usage
QoS Indicators, PDCH Usage
formula P496 P495
Name MIN_NB_USED_SPDCH_CELL MAX_NB_USED_SPDCH_CELL Soft pre-emption
Definition Minimum number of used slave PDCHs in the . Maximum number of used slave PDCHs in the cell.
P417 (P403a + P404a) / P417
NB_PREEMPTED_PDCH
Number of PDCH released after having been marked by the soft pre-emption procedure Average number of UL+DL TBF candidates to a T1 reallocation per PDCH released after having been marked
1 3 142
5 Resource Usage
QoS Indicators, MPDCH

GPRS radio resources: MPDCH
MPDCH usage
MPDCH resource allocation is static no indicators
MPDCH signaling traffic
PPCH PRACH PAGCH PACCH
1 3 143
5 Resource Usage
QoS Indicators, MPDCH Signaling

GPRS radio resources: MPDCH signaling
MPDCH signalling traffic Dedicated PPCH signalling load on all the existing MPDCH P61 Number of PACKET PAGING REQUEST for PS paging sent P61a to the MS on PPCH Number of PACKET PAGING REQUEST for CS paging sent P61b to the MS on PPCH Number of Packet DL assignment messages on PPCH P61 - 0.5*P61a - 0.5*P61b Occupancy rate of PS paging messages on PPCH load 0.5 * P61a / P61 Occupancy rate of Packet DL assignment messages on PPCH (P61 - 0.5*P61a - 0.5*P61b) / P61 PRACH signalling load on all the existing MPDCH PRACH signalling load due to NC2 feature % PRACH load induced by NC2 feature Dedicated PAGCH signalling load on all the existing MPDCH UL PACCH signalling load on all the existing MPDCH P399 P438d (P438d / P399) * 100 P400 P401
1 3 144
The Factor of 0.5 comes from the fact that a PACKET PAGING REQUEST can contain 2 paging messages (like in GSM between Paging Commands and Paging Requests).
5 Resource Usage
QoS Indicators, CCCH

GPRS radio resources: CCCH
CCCH load
RACH PCH: PS paging, CS paging, Immediate assignment AGCH
1 3 145
5 Resource Usage
QoS Indicators, CCCH Load

GPRS radio resources: CCCH load
CCCH load P53a / MC8A Paging usage rate due to GPRS PCH use due to GPRS Immediat Assignment P53c Ratio PS/CS paging through SGSN P53a / (P53a+P53b) P62c / MC8C RACH usage rate due to GPRS (P49 + P27) / (MC8B + P49 + P27) AGCH usage rate due to GPRS
1 3 146
P53a = Number of (BSCGP) PAGING REQUEST for PS paging sent to the MS (through the BSC which manages the PCH resource). (used for instance for an MT picture transfer MMS service). P53b = Number of (BSCGP) PAGING REQUEST for CS paging sent to the MS (through the BSC which manages the PCH resource) -> Need of the Gs interface. P53c = Number of (BSCGP) IMMEDIATE ASSIGNMENT sent to the MS (through the BSC which manages the PCH resource) for a DL TBF establishment when the MS is in DRX mode. GSM Paging Command (one per Mobile) or GPRS (BSCGP) PAGING REQUEST are merged into PAGING REQUEST on the radio layer.
5 Resource Usage
QoS Indicators, CCCH, Graph

GPRS/GSM AGCH breakdown
450000 400000 350000 300000 250000 200000 150000 100000 50000 0
20 03 20 03 20 03 20 03 20 03 20 03 20 03 20 03 20 03 20 03 20 03 20 03 20 03 20 03 20 03 20 03
4.5 4 3.5 3 2.5 2 1.5 1 0.5 0
PS AGCH Tot AGCH % PS AGCH
CS AGCH
08 /
08 /
08 /
08 /
08 /
08 /
08 /
08 /
08 /
09 /
09 /
09 /
09 /
09 /
09 / 11 /
14 /
18 /
16 /
20 /
22 /
24 /
26 /
03 /
28 /
30 /
05 /
01 /
07 /
09 /
GPRS/GSM RACH breakdown

450000 400000 350000 300000 250000 200000 150000 100000 50000 0
20 03 20 03 20 03 20 03 20 03 20 03 20 03 20 03 20 03 20 03 20 03 20 03 20 03 20 03 20 03 20 03
13 /
09 /
4 3.5 3 2.5 2 1.5 1 0.5 0
Tot RACH % PS RACH
08 /
08 /
08 /
08 /
08 /
08 /
08 /
08 /
08 /
09 /
09 /
09 /
09 /
09 /
09 / 11 /
18 /
20 /
22 /
24 /
26 /
28 /
14 /
16 /
30 /
01 /
03 /
05 /
07 /
09 /
GPRS/GSM PCH breakdown

20000000 18000000 16000000 14000000 12000000 10000000 8000000 6000000 4000000 2000000 0
20 03 20 03 20 03 20 03 20 03 20 03 20 03 20 03 20 03 20 03 20 03 20 03 20 03 20 03 20 03 20 03
13 /
09 /
1 0.9 0.8 0.7 0.6 0.5 0.4 0.3 0.2 0.1 0
CS PAging PS Imm. As PS PAging %io PS Pag
08 /
08 /
08 /
08 /
08 /
08 /
08 /
09 /
09 /
09 /
09 /
09 /
08 /
08 /
09 / 11 /
14 /
16 /
18 /
22 /
20 /
24 /
01 /
26 /
03 /
07 /
28 /
30 /
05 /
09 /
1 3 147
13 /
09 /
5 Resource Usage
QoS Indicators, Abis Nibble

GPRS radio resources: Abis nibble
Abis nibble counters Number of free nibbles: - Minimum of free extra or bonus Abis nibble
Number of used nibble: - Maximum number extra or bonus used nibbles
Cumulated Time during which there are free Abis nibbles
1 3 148
5 Resource Usage
QoS Indicators, Abis Nibble

GPRS radio resources: Abis nibble usage
Abis interface - Abis nibble usage Cumulative time (in seconds), per BTS ,during which there are free extra and bonus Abis nibbles available. Cumulated time during which extra and bonus Abis nibbles are used in the cell, cumulated over all extra and bonus Abis nibbles. Minimum number of free extra and bonus Abis nibbles. Maximum number of extra and bonus Abis nibbles currently used in the cell (by a GCH channel)
P472
P466
P484 P465
1 3 149
Free Extra and bonus nibbles are given per BTS. Free extra and bonus nibbles are extra and bonus nibbles not currently used in a GCH.
5 Resource Usage
QoS Indicators, GPU

GPRS radio resources: GPU
B10
GPU counters
Overall traffic MS capabilities breakdown MS multislot class breakdown

modified B10
new B10
Processing limitation, GCH interface
1 3 150
5 Resource Usage
QoS Indicators, GPU Usage

GPRS radio resources: GPU usage and MS capabilities
GPU traffic Number of LLC PDU transferred (UL+ DL) Number of UL+DL TBF establishment requests per GPU Number of UL+DL TBF establishment successes per GPU (UL+DL) TBF success rate per GPU Number of PS PAGING request per GPU Number of CS PAGING request per GPU P104 P107 P106 (P106 / P107) * 100 P391a P391b
B10
MS capabilities Number of MS contexts created for Releases 1997 or 1998 mobile stations. Number of MS contexts created for non-EGPRS capable Release 1999 onwards mobile stations Number of MS contexts created for EGPRS capable Release 1999 onwards mobile stations. Number of MS contexts created Number of MS contexts created for MS supporting the Geran feature package 1 Number of MS context created for DTM capable mobiles stations. Number of EDA-capable GPRS and EGPRS MS contexts. Ratio of MS contexts created for Releases 1997 or 1998 mobile stations. Ratio of MS contexts created for non-EGPRS capable Release 1999 onwards mobile stations Ratio of MS contexts created for EGPRS capable Release 1999 onwards mobile stations.
1 3 151
P450a P450b P450c P450d P450e

new B10
P500 P594 P450a / ( P450a+P450b+P450c) P450b / ( P450a+P450b+P450c) P450c / ( P450a+P450b+P450c)
P450d is incremented the first time the MS Radio Access Capability is received for a given MS context. Note: This counter is incremented whatever the MS release or feature supported by the MS. A mobile station is assumed to be Rel-4-compliant if it supports the GERAN Feature Package 1 (theoretically it is not possible to precisely identify a Rel-4-compliant mobile station). Rel-4-compliant if it its GERAN Feature Package 1 bit is set to 1.
5 Resource Usage
QoS Indicators, GPU Usage [cont.]

GPRS radio resources: MS multislot class
Indicator name
NB_MS_MULTISLOT_CLASS_0_TO_10 NB_MS_MULTISLOT_CLASS_11_TO_12 NB_MS_MULTISLOT_CLASS_3X NB_MS_MULTISLOT_CLASS_4X
B10
definition
Number of MS contexts created for MS whose multislot class belongs to the set of multislot classes 0 to 10. Number of MS contexts created for MS whose multislot class belongs to the set of multislot classes 11 to 12. Number of MS contexts created for MS whose multislot class belongs to the set of multislot classes of type 3X . Number of MS contexts created for MS whose multislot class belongs to the set of multislot classes of type 4X .
Ref
P530a_1 P530a_2 P530a_3 P530a_4
1 3 152
5 Resource Usage
QoS Indicators, GPU Load

GPRS radio resources: GPU load: DSP and CPU
GPU load
DSP congestion duration (in seconds). Percentage of time during which the DSP is in congestion Cumulated time during which the GPU stays in the PMU CPU overload state due to PMU CPU power limitations. Percentage of time during which the GPU stays in the PMU CPU overload state due to PMU CPU power limitations. Average PMU CPU power budget of the GPU Maximum PMU CPU power budget of the GPU This counter cumulates the time during which at least a DSP is in CPU load state This counter cumulates the time during which at least a DSP is in CPU overload state P384 P384 / GP P402
P402 / GP P76a P77a P201
P202
1 3 153
PMU = Packet Management Unit, is responsible for the following tasks: RRM (Radio and Resource Management): for TBF, PDCH and MPDCH allocation/de-allocation, radio resource re-allocation of existing TBFs, PS paging, PDU queuing and Packet System Information BSCGP stack management (MFS-BSC interface) Gb stack management (MFS-SGSN interface) The PMU functions are supported by the PPC board (Power PC). The DSP board supports the Packet Transfer Unit (PTU) functions: RLC layer management MAC layer management L2EGCH layer management L1EGCH layer management
5 Resource Usage
QoS Indicators, GCH

GPRS radio resources: GCH usage
GCH counters
Cumulated time: Number of GCHs: max number of GCHs busy per GPU max number of GCHs busy per cell Min number of GCHs busy per GPU max number of GCHs in deficit cell GCHs are in excess in a cell GCHs are in deficit in a cell GCH is busy in a cell GPU is in Ater congestion GPU is in high Ater usage state
1 3 154
5 Resource Usage
QoS Indicators, GCH Load

GPRS radio resources: GCH load in time
Ater interface - GCH
Cumulative time (in seconds) during which a GCH (16k channel) is busy in the cell. The counter is integrated over all the GCH available in the cell. Cumulative time (in seconds) during which a GCH resource (16k channel) is available in the GPU Cumulative time (in seconds), per cell ,during which there is a excess of GCH resources (16k channel). Cumulative time (in seconds), per cell , during which there is a deficit of GCH resources (16k channel). Atermux congestion duration (in seconds) due to a lack of GCH transmission resources on the Atermux interface % of time the GPU is in Ater congestion state Time (cumulated over a granularity period) during which the GPU remains in "high" Ater usage % of time the GPU is in high Ater usage state P100c P101 P471 P470 P383a P383a / GP P383b P383b / GP
1 3 155
5 Resource Usage
QoS Indicators, GCH Load

GPRS radio resources: GCH load in number per cell and per GPU
Ater interface - GCH Maximum number of GCH in deficit reached in the cell. Maximum number of busy GCH (16k channel) in the GPU. Minimum number of busy GCH (16k channel) in the GPU. Maximum number of busy GCH (16k channel) in the cell. P469 P100f P100e P100d
1 3 156
For a DRFU BTS, a GCH is said busy when it is connected to a given PDCH. For an Evolium BTS, a GCH is said busy when it is connected to a given TRX (as part as an M-EGCH).
5 Resource Usage
QoS Indicators, Ater Nibble

GPRS radio resources: Ater nibble usage
Ater nibble counters Number of free nibbles: - Minimum of Ater - Minimum of free extra or bonus Ater nibbles
Number of used Nibble: - Maximum number extra or bonus used nibbles Cumulated Time during which there are free Ater nibbles given per GPU
1 3 157
5 Resource Usage
QoS Indicators, Ater Nibble

GPRS radio resources: Ater nibble usage
Ater interface Ater nibbles usage

Minimum number of free Ater nibbles. Minimum number of free extra and bonus Abis nibbles. Free extra and bonus nibbles are extra and bonus nibbles not currently used in a GCH. Maximum number of extra and bonus Abis nibbles currently used in the cell (by a GCH channel). Cumulative time (in seconds), per GPU ,during which there are free Ater nibbles. A free Ater nibble is an Ater nibble not currently used by a GCH. P465 P486 P484
P474
1 3 158
5 Resource Usage
QoS Indicators, Impact of EDGE Activation

Ater resources capacity must be increased for EDGE
Example for one GPU board with 2 AterMux for GPRS
Total_Ater_GIC_available 500 450 400 350 300 250 200 150 100 50 0 10,0% 0,0% 30,0% Ater_Cong_Rate 70,0%
464 GCHs
60,0%
348 GCHs
50,0% 40,0%
232 GCHs
20,0%
2 AterMux are not enough for EDGE traffic

1 3 159
4 AterMux are needed to avoid Ater congestion

Ater_Cong_Rate = P383a / GP = Percentage of time all GCHs are busy in the GPU Total_Ater_GIC_available = Number of GCHs available for traffic is not a counter but a configuration variable depending on the number of AterMux connected to the GPU and which available for traffic
5 Resource Usage
QoS Indicators, Impact of EDGE Activation [cont.]

DSP congestion can occur in the GPU even if enough Ater resources are available
Same GPU: EDGE is activated cell by cell
Total_Ater_GIC_available 500 450 400 350 300 250 200 150 100 50 0 0,0% 1,0% 0,5% GPU_Cong_Rate 3,0% 2,5%
464 GCHs
348 GCHs 232 GCHs
2,0% 1,5%
The more cells are EDGE capable the higher the GPU DSP congestion
1 3 160
GPU_Cong_Rate = (P384/10) / GP = Percentage of time the GPU is in DSP congestion Total_Ater_GIC_available = Number of GCHs available for traffic is not a counter but a configuration variable depending on the number of AterMux connected to the GPU and which available for traffic
5 Resource Usage
QoS Indicators, BVC

GPRS radio resources: BVC
BVC
Number of DL LLC bytes
Received from the SGSN Discarded due to congestion Not rerouted Well received from the SGSN Discarded due to a Suspend procedure Rerouted
Number of UL LLC bytes BVC availability

1 3 161
Received from the MS
5 Resource Usage
QoS Indicators, BVC, Traffic, Availability

GPRS radio resources: BVC traffic, BVC availability
BVC (cell) traffic Downlink Number of DL LLC bytes received from SGSN Number of DL LLC bytes received by MS in GPRS ACK mode Number of DL LLC bytes received by MS in GPRS NACK mode Number of DL LLC bytes received by MS in EGPRS ACK mode Number of DL LLC bytes received by MS in EGPRS NACK mode Number of DL LLC bytes discarded due to congestion Average DL useful throughput in kbit/s DL LLC congestion rate Number of DL LLC bytes discarded due to suspend procedure % of DL LLC bytes discarded due to suspend procedure Downlink LLC bytes well rerouted DL LLC bytes not rerouted DL LLC bytes well received DL LLC bytes well received rate P43 P43a P43b P43c P43d P10 ((P43 - P10) * 8) / (GP * 1000) P10 / P43 P99 P99 / P43 P95 P96 P43 - P10 - P96 Uplink Number of UL LLC bytes received from MS Number of UL LLC bytes received from MS in GPRS ACK mode Number of UL LLC bytes received from MS in GPRS NACK mode Number of UL LLC bytes received from MS in EGPRS ACK mode Number of UL LLC bytes received from MS in EGPRS NACK mode Number of UL LLC bytes discarded due to congestion at SNS level P44 P44a P44b P44c P44d P23
(P43 - P10 - P96) / P43 BVC (cell) unavailability Time during which the BVC associated to a cell is unavailable for traffic
P67
1 3 162
LLC bytes discarded: relating to the PDU LifeTime expiry or to the GPU buffer congestion (can be linked to degraded DL Flow Control algorithm). P99: The introduction of the Suspend-Resume mechanism between the MFS and the SGSN can generate GPRS QoS problems. If the suspend time exceeds the tolerable threshold for the distant server the MS is connected to, it can generate disconnection from the server. Even though, the disconnection does not mean that the PDP context is deactivated. It belongs to IP GSS feature (capacity to generate dummy IP blocks to keep the Gi link alive). P96 is likely to be sensitive to a lot of reselection problems an MS has to face in the GPRS network (no GPRS resources available in the selected cell, reselection of an MS in a new cell belonging to a new MFS or a new SGSN, etc).
5 Resource Usage
QoS Indicators, PVC and BC Unavailability

GPRS radio resources: BVC
PVC
Time unavailaibility
BC
Time unavailaibility
1 3 163
5 Resource Usage
QoS Indicators, PVC and BC Unavailability

GPRS radio resources: PVC, BC unavailability
Gb interface PVC, BC Percentage of time during which the PVC (Permanent Virtual Connection) is not available on Gb Interface.
P34/GP
Percentage of time during which the BC (Bearer Channel) is not available on Gb Interface
P33/GP
1 3 164
5 Resource Usage
QoS Indicators, Graph
Details of downlink LLC traffic

9000000 8000000 7000000 6000000 5000000 4000000 3000000 2000000 1000000 0 100.2 100 99.8 99.6 99.4 99.2 99 98.8 98.6 98.4
Blocked bytes Discarded bytes Not rerouted Rerouted bytes Received bytes %Well receiv
4000000 3500000 3000000 2500000 2000000 1500000 1000000 500000 0
14 /0 8/ 20 03 16 /0 8/ 20 03 18 /0 8/ 20 03 20 /0 8/ 20 03 22 /0 8/ 20 03 24 /0 8/ 20 03 26 /0 8/ 20 03 28 /0 8/ 20 03 30 /0 8/ 20 03 01 /0 9/ 20 03 03 /0 9/ 20 03 05 /0 9/ 20 03 07 /0 9/ 20 03 09 /0 9/ 20 03 11 /0 9/ 20 03 13 /0 9/ 20 03
Details of uplink LLC traffic
UL sent bytes
1 3 165
14 /0 8/ 20 03 16 /0 8/ 20 03 18 /0 8/ 20 03 20 /0 8/ 20 03 22 /0 8/ 20 03 24 /0 8/ 20 03 26 /0 8/ 20 03 28 /0 8/ 20 03 30 /0 8/ 20 03 01 /0 9/ 20 03 03 /0 9/ 20 03 05 /0 9/ 20 03 07 /0 9/ 20 03 09 /0 9/ 20 03 11 /0 9/ 20 03 13 /0 9/ 20 03
6 CS and MCS Adaptation
1 3 166
Modulations and Data Rates

Data rate per radio TS (RLC payload)
Scheme Modulation GPRS CS-4 CS-3 CS-2 CS-1 GMSK GMSK GMSK GMSK EGPRS MCS-9 8PSK 8PSK 8PSK 8PSK 8PSK GMSK GMSK GMSK GMSK 59.2 54.4 44.8 29.6 / 27.2 * 22.4 17.6 14.8 / 13.6 * 11.2 8.8 21.4 15.6 13.4 9.05 Maximum rate (kbps)
8PSK modulation to provide higher data rates
MCS-8 MCS-7 MCS-6 MCS-5
GMSK modulation to ensure a certain level of performance in case of poor radio conditions
MCS-4 MCS-3 MCS-2 MCS-1
1 3 167
DL CS Adaptation
AV_RXQUAL_LT 7
CS-1
CS_QUAL_DL_1_2_X_Y+ CS_HST_DL_LT CS_QUAL_DL_1_2_X_Y CS-1 or CS-2 (hysteresis)
CS-2
CS_QUAL_DL_2_3_X_Y + CS_HST_DL_LT CS_QUAL_DL_2_3_X_Y CS-2 or CS-3 (hysteresis) C S_QUAL_DL_3_4_X_Y
CS-3
0 0 CS-3 or CS-4 (hysteresis) CS_SIR_DL_3_4_X_Y
CS-4
AV_SIR 15 BLER
CS_SIR_DL_3_4_X_Y + CS_SIR_HST_DL CS_BLER_DL_4_3
100%
1 3 168
CS_BLER_DL_3_4
0%
The change from CS3 to CS4 is not only based on AV_RXQUAL_LT for the two following reasons: The RXQUAL range only goes down to 0.2%. However, the change of coding scheme from CS3 to CS4 will probably have to be done for even lower values. Indeed, when the coding scheme is CS4, in static (AWGN), a BLER of 0.1 (typical value of the BLER threshold to change from CS3 to CS4) is obtained for a raw BER of 1-(1-0.1)1/456 = 2.10-4. This raw BER would be larger in multipath channels but is likely to remain below 0.2%. This means that CS_QUAL_DL_3_4 should be close to 0 and that a condition based on RXQUAL is not sufficient to change the coding scheme from CS3 to CS4. If the changes from CS3 to CS4 and from CS4 to CS3 are based on different metrics, a Ping-Pong effect can occur. Indeed, it can happen that the conditions to change from CS3 to CS4 and CS4 to CS3 are simultaneously true in some situations. In case a TBF is established on PDCHs of a non-hopping BCCH TRX or on PDCHs using a FHS including the BCCH frequency a new algorithm is used for adaptation between CS3 and CS4 based on BLER computation and comparison to threshold. Indeed in these 2 cases most of the MS will not report any C/I measurements on idle frames.
UL CS Adaptation
GPRS CS adaptation in the UL
AV_RXQUAL_LT 7
CS1
CS_QUAL_UL_1_2_X_Y + CS_HST_UL_LT CS_QUAL_UL_1_2_X_Y CS1 or CS2 (hysteresis)
CS2
CS_QUAL_UL_2_3_X_Y + CS_HST_UL_LT CS_QUAL_UL_2_3_X_Y CS2 or CS3 (hysteresis)
CS3
CS_QUAL_UL_3_4_X_Y + CS_HST_UL_LT CS3 or CS4 (hysteresis) CS_QUAL_UL_3_4_X_Y
CS4
0 0
1 3 169
AV_SIR 15
In the up-link, the RXQUAL is available in CS4 and the SIR measurements are not reported by the BTS to the MFS so far. Therefore, it is possible to use also RXQUAL measurements to change the coding scheme from CS3 to CS4 or from CS4 to CS3, contrary to the downlink algorithm, for which the SIR is used.
DL MCS Adaptation
In RLC acknowledged mode, the MFS applies a given MCS taking into account:
Current MCS:
MCS-1 to MCS-4 in GMSK MCS-5 to MCS-9 in 8-PSK
Average Power Decrease: APD set = [0, 1, 3, 4, 5, 6, 8, 10] MS OUT OF MEMORY state
= Off then LA tables with IR are used = On then LA tables without IR (Type I ARQ) are used
In RLC unacknowledged mode, the MFS applies a given MCS taking into account:
Current MCS:
MCS-1 to MCS-4 in GMSK MCS-5 to MCS-9 In 8-PSK
Average Power Decrease: APD set = [0, 1, 3, 4, 5, 6, 8, 10]
Each combination of these criteria corresponds to a specific LA table

1 3 170
Extract of a table when APD=0dB, Type 1 ARQ, 8PSK table: if MCScurrent belongs to {5,6,7,8,9}
CV_BEP 0 0 1 2 3 4 5 6 7 8 9 10 11 12 13 MEAN_BEP 14 15 16 17 18 19 20 21 22 23 24 5 5 5 5 5 5 5 5 5 5 5 6 6 6 7 7 7 7 7 7 7 7 7 8 8 1 5 5 5 5 5 5 5 5 5 6 6 6 6 6 6 6 7 7 7 7 7 7 8 8 8 2 5 5 5 5 5 5 6 6 6 6 6 6 6 6 6 6 6 7 7 7 7 7 8 8 8 3 5 5 5 5 5 5 5 5 6 6 6 6 6 6 6 6 7 7 7 7 7 7 8 8 8 4 1 1 1 2 5 5 5 5 5 5 6 6 6 6 6 6 6 7 7 7 7 7 8 8 5 1 1 2 2 2 3 5 5 5 5 5 6 6 6 6 6 6 6 7 7 7 7 8 8 6 1 2 2 2 3 3 3 3 5 5 5 5 5 5 6 6 6 6 7 7 7 7 8 8 7 1 2 2 3 3 3 3 3 4 5 5 5 5 5 6 6 6 6 7 7 7 7 8 8
8 8 8 8 All Rights Reserved Alcatel-Lucent 2008 3JK10239AAAAWBZZA Issue 01 Section 1 Module 3 Page 170
UL MCS Adaptation
In RLC acknowledged mode, the MFS applies a given MCS taking into account:
Current MCS:
MCS-1 to MCS-4 in GMSK MCS-5 to MCS-9 in 8-PSK
APD of the MS: APD set = [0, 1, 3, 4, 5, 6, 8, 10] EN_IR_UL state

= enable then LA tables with IR are used = disable then LA tables without IR (Type I ARQ) are used
In RLC unacknowledged mode, the MFS applies a given MCS taking into account:
Current MCS:
MCS-1 to MCS-4 in GMSK MCS-5 to MCS-9 In 8-PSK
Average Power Decrease: APD set = [0, 1, 3, 4, 5, 6, 8, 10]
Each combination of those criteria corresponds to a specific LA table

1 3 171
In the up-link the same tables as in the down-link apply.
Exercise
Exercise 1: using trace 20 , find at what time the MCS is changed
1 3 172
QoS Indicators
CS and MCS adaptation
PDTCH RLC blocks Number of useful blocks, retransmitted blocks, lost bytes for GPRS CS1,2,3,4 for EGPRS MCS1, , MCS9 Retransmission rate, lost rate Useful CSx and MCSx distribution GPRS Coding Scheme increase and decrease Throughput per cell, per PDCH, per TBF PACCH RLC blocks
PDTCH occupancy PACCH occupancy
1 3 173
QoS Indicators, RLC Statistics, GPRS Mode

CS and MCS adaptation: RLC statistics in GPRS mode
RLC statistics Downlink Number of useful PDTCH RLC blocks acknowledged by the MS in GPRS ack mode CS1 : P55a CS2 : P55b CS3 : P55c CS4 : P55d CS1 : P20a CS2 : P20b CS3 : P20c CS4 : P20d CS1+CS2+CS3+CS4 : P72c Number of useful PDTCH RLC blocks acknowledged by the MS in GPRS ack mode Uplink CS1 : P57a CS2 : P57b CS3 : P57c CS4 : P57d CS1 : P21a CS2 : P21b CS3 : P21c CS4 : P21d
Number of retransmitted PDTCH RLC blocks in GPRS ack mode
Number of retransmitted PDTCH RLC blocks in GPRS ack mode
Number of lost PDTCH RLC bytes in GPRS nack mode
Number of lost PDTCH RLC bytes in CS1+CS2+CS3+CS4 : P72d GPRS nack mode PDTCH RLC block retransmission rate in GPRS ack mode PDTCH RLC block CSx / (CS1+CS2+CS3+CS4) ratio
PDTCH RLC block retransmission rate (P20a + P20b + P20c + P20d) / P350a in GPRS ack mode
KPI KPI KPI
KPI KPI KPI
(P21a + P21b + P21c + P21d) / P350b (P57x) / (P57a+P57b+P57c+P57d) (P21a*160+P21b*240+P21c*288+P21d* 400)/(P21a*160+P21b*240+P21c*288+P 21d*400+P57a*160+P57b*240+P57c*28 8+P57d*400) P336
PDTCH RLC block CSx / (CS1+CS2+CS3+CS4) ratio In RLC ack mode, rate of RLC retransmitted data bytes sent on PDTCH and encoded in CS-x Average TX_EFFICIENCY
P55x / (P55a+P55b+P55c+P55d)
(P20a*160+P20b*240+P20c*288+P20 In RLC ack mode, rate of RLC d*400)/(P20a*160+P20b*240+P20c*2 retransmitted data bytes sent on 88+P20d*400+P55a*160+P55b*240+P PDTCH and encoded in CS-x 55c*288+P55d*400) P335 Average TX_EFFICIENCY
1 3 174
The average TX_EFFICIENCY is equal to:
NB _ RECEIVED
TX _ EFFICIENCY = 100
Where: NB_SENT is the number of transmitted RLC data blocks,
i =1 NB _ SENT
i =1
i
ni
1 ni
NB_RECEIVED is the number of correctly received RLC data blocks (i.e., blocks for which a positive acknowledgment is reported), i is equal to the number of information bits in the i-th correctly received RLC data block divided by the number of bits per RLC data block with GMSK modulation (456 in GPRS). This ratio only depends on the coding scheme used for the i-th correctly received RLC data block and is between 0 and 1 in GPRS. The values of the number of information bits per RLC data block for each coding scheme are defined in 05.03 TS Specification document. CS1 CS2 CS3 CS4 0.40 0.59 0.68 0.94 ni is the number of RLC data blocks in the i-th radio block. Therefore, this number is always equal to 1 for GPRS, It is computed every TX_EFFICIENCY_PERIOD (=200) RLC data blocks. It is compared to TX_EFFICIENCY_ACK_THR (=10%) or TX_EFFICIENCY_NACK_THR (=15%) to trigger radio drop.
QoS Indicators, RLC Statistics, EGPRS Mode

CS and MCS adaptation: RLC statistics in EGPRS mode
RLC statistics
Downlink Number of useful RLC blocks sent in RLC acknowledged mode on PDTCH and encoded in MCS1/2//9. MCS1 : P55e MCS2 : P55f MCS9 : P55m MCS1 : P20f MCS2 : P20g MCS9 : P20n P72d Uplink Number of useful RLC blocks sent in RLC acknowledged mode on PDTCH encoded in MCS-1/2//9. MCS1 : P57e MCS2 : P57f ....... ....... MCS9 : P57m MCS1 : P21f MCS2 : P21g MCS9 : P21n P73d P57x/(P57e+P57f+P57g+P57 h+P57i+P57j+P57k+P57l+P5 7m) p21e/(p21e+((P57e*176+P5 7f*224+P57g*296+P57h*352+ (P57i*448+P57j*592+(P57k*8 96+P57l*1088+P57m*1184)/ 2)) / 8))
B10
Number of useful RLC blocks retransmitted in RLC acknowledged mode on PDTCH and encoded in MCS-1/2//9.
Number of useful RLC blocks retransmitted in RLC acknowledged mode on PDTCH and encoded in MCS-1/2//9.
new B10
MCS-x lost bytes In RLC ack mode, ratio of useful RLC blocks sent in RLC acknowledged mode on PDTCH and encoded in MCS-x
new B10
MCS-x lost bytes
KPI KPI
P55x/(P55e+P55f+P55g+P55 In RLC ack mode, ratio of useful h+P55i+P55j+P55k+P55l+P5 RLC blocks sent in RLC 5m) acknowledged mode on PDTCH and encoded in MCS-x
In RLC ack mode, rate of RLC P20e/(P20e+(P55e*176+P55 In RLC ack mode, rate of RLC retransmitted data bytes sent on f*224+P55g*296+P55h*352+P retransmitted data bytes sent PDTCH and encoded in MCS-x 55i*448+P55j*592+(P55k*89 on PDTCH and encoded in MCS-x 6+P55l*1088+P55m*1184)/2 )/ 8))
1 3 175
P20e respectively P21e have been removed. In acknowledged mode, number of DL respectively UL RLC data bytes (except RLC blocks containing LLC Dummy UI Commands only) on PDTCH encoded in MCS-x (with x = 1 to 9) retransmitted due to unacknowledgement of the MS respectively MFS.
QoS Indicators, CS Adaptation

CS and MCS adaptation: CS adaptation
Coding scheme adaptation
Downlink Number of CS adaptions from a given coding scheme to a less robust coding scheme. Does not apply to EGPRS TBFs P351a Uplink Number of CS adaptions P352a from a given coding scheme to a less robust coding scheme. Does not apply to EGPRS TBFs Number of CS adaptions P352b from a given coding scheme to a more robust coding scheme. Does not apply to EGPRS TBFs Average number of CS increase per TBF Average number of CS adaptions decrease per TBF P352a / (P30a + P30b + P30c) P352b / (P30a + P30b + P30c)
Number of CS adaptions P351b from a given coding scheme to a more robust coding scheme. Does not apply to EGPRS TBFs Average number of CS increase per TBF Average number of CS adaptions decrease per TBF P351a / (P90a + P90b + P90c + P90d + P90e + P90f) P351b/ (P90a + P90b + P90c + P90d + P90e + P90f)
1 3 176
QoS Indicators, DL CS Usage, Graph
GPRS DL useful RLC traffic

80000000 70000000 60000000 50000000 40000000 30000000 20000000 10000000 0 100 90 80 70 60 50 40 30 20 10 0
CS4 usef CS3 usef CS2 usef CS1 usef %io CSx usef
1 3 177
/3 1 1 1 /2 0 /0 0 5 2 1 1 /2 0 /0 0 5 4 1 1 /2 0 /0 0 5 6 1 1 /2 0 /0 0 5 8 1 1 /2 0 /1 0 5 0/ 11 20 /1 0 5 2 1 1 /2 0 /1 0 5 4 1 1 /2 0 /1 0 5 6 1 1 /2 0 /1 0 5 8 1 1 /2 0 /2 0 5 0 1 1 /2 0 /2 0 5 2 1 1 /2 0 /2 0 5 4 1 1 /2 0 /2 0 5 6 1 1 /2 0 /2 0 5 8 1 1 /2 0 /3 0 5 0 1 2 /2 0 /0 0 5 2/ 12 20 /0 0 5 4 1 2 /2 0 /0 0 5 6 1 2 /2 0 /0 0 5 8 1 2 /2 0 /1 0 5 0 1 2 /2 0 /1 0 5 2 1 2 /2 0 /1 0 5 4 1 2 /2 0 /1 0 5 6/ 20 05
10
QoS Indicators, DL MCS Usage
MCS1 MCS2 MCS3 MCS4 MCS5 MCS6 MCS7 MCS8 MCS9
B8 TRX class 2 & 4

100%
B9
(MaxMCS=9)
B9
(MaxMCS=8)
(MaxMCS=9)
80%
60%
40%
20%
0%
High proportion of MCS5 due to High Ater Usage
High usage of MCS9
Better usage of MCS8
Thanks to Dynamic Abis Statistical Multiplexing
1 3 178
Caution: animated slide (with hidden objects).
QoS Indicators, UL MCS Usage
B8 (GMSK only)
1 00 % 90 % 80 % 70 % 60 % 50 % 40 % 30 % 20 % 10 % 0%
B9 (8PSK in UL)
High Usage of MCS9 during UL FTP tests
MCS1 MCS2 MCS3 MCS4
MCS5 MCS6 MCS7 MCS8 MCS9
8PSK being used in UL right after B9 migration
Thanks to: Dynamic Abis Statistical Mux 8 PSK in UL
1 3 179
Caution: animated slide (with hidden objects).
7 Cell Reselection
1 3 180
7 Cell Reselection
NC0, Success
MS
DL transfer PDTCHDL
MFS serving cell

MFS target cell
SGSN
Packet DL Ack/Nack
PACCHUL
UL transfer establishment in the new cell UL transfer The MS sends an LLC PDU to warn the SGSN about its new cell location
RADIO STATUS LLC PDU

(TLLI,new BVCI)
P434c
UL TBF release
P434d
DL TBF release
P436
NC0 reselection success
FLUSH-LL
(TLLI,old BVCI)
FLUSH-LL ACK
(TLLI)
P396b
1 3 181
P396a
Counter P434c (resp.P434d) gives the number of UL (resp. DL) TBFs which have been released due to an NC0 reselection. These TBFs can have been previously counted as abnormally released or acceptably released due to the reselection depending on the occurrence time of the FLUSH-LL message: If the FLUSH-LL message is not received before T_WAIT_FLUSH expiry after the TBF was released due to radio link failure then the previous TBF release is considered as abnormal and counter P434c/P434d counting the number of DL/UL TBF acceptable release due to reselection is not incremented. Instead a TBF abnormal release due to Radio and counters P302b_x/P302c_x are incremented. If the FLUSH-LL message is received before T_WAIT_FLUSH expiry after the TBF was released due to radio link failure then the previous TBF release is considered as acceptable and P434c/P434d is incremented. If the FLUSH-LL message is received before the radio link failure occurs the TBF is released and P396b/P396a counter is incremented. P436 provides the number of successful NC0 cell reselection when the mobile was in Packet Transfer Mode in the old cell.
7 Cell Reselection
NC2, Request / Success

MS
DL transfer
MFS serving cell Packet measurement report
MFS target cell
SGSN
NC2 cell reselection request
T3158 expiry T3158
PACCHUL
P223
UL TBF
P226
DL TBF Radio resources are released locally
Packet cell change order, polling Packet control ack new cell (BCCH,BSIC)
UL transfer establishment in the new cell PACCHDL
P221
P222
T_ACK_WAIT
T_WAIT_FLUSH
LLC PDU FLUSH-LL

(TLLI,old BVCI) (TLLI,new BVCI)
NC2 cell reselection success
P227
UL TBF release
P224
DL TBF release
FLUSH-LL ACK
(TLLI)
1 3 182
If a PCCO is sent for a MS supporting a DL TBF and an UL TBF, then both P223 and P226 are incremented. If a FLUSH is received for a MS supporting a DL TBF and an UL TBF, then both P224 and P227 are incremented.
7 Cell Reselection
NC2, Request / Success per Causes

MS
DL transfer
MFS target cell
SGSN
T3158 expiry T3158
NC2 cell reselection request for cause:

P433d P433c P433a P433b
T_ACK_WAIT
PACCHUL
too bad uplink quality too bad downlink quality too low downlink level better neighbor cell

Packet control ack
PACCHDL
T_WAIT_FLUSH
LLC PDU
(TLLI,new BVCI)
P434a
UL TBF release
P434b
DL TBF release
P435d P435c P435a P435b
P396b
P396a
NC2 cell reselection success for cause: too bad uplink quality too bad downlink quality too low downlink level better neighbor cell
FLUSH-LL
(TLLI,old BVCI)
FLUSH-LL ACK
(TLLI)
1 3 183
7 Cell Reselection
NC2, Failure
MS
DL transfer
MFS target cell
SGSN
T3158 expiry T3158
PACCHUL
NC2 cell reselection request

PACCHDL T_ACK_WAIT

Packet control ack

UL transfer establishment in the new cell is impossible
Packet channel request

RACH
T_WAIT_FLUSH
Packet uplink assignment
AGCH
USF scheduling
PDTCH
Packet cell change failure

PACCH
P228
UL TBF DL TBF
P464
P437a
Target cell rejected
P437b
Target cell not rejected
P225
1 3 184
The above case assumes that MPDCH is configured in the cell. When receiving the PACKET CELL CHANGE FAILURE message, the MFS will increment either P437a or P437b according to the cause value reported by the MS in the message. Counter P464 aims to count rejection due to load in target cell Counter P228/P225 is incremented in case of the MS reports to the MFS a Packet Cell Change Failure message (PCCF) Counter P437a is incremented if the cause included in the PCCF reported is one of the following "Frequency not implemented "No response on target cell "Immediate Assign Reject or Packet Access Reject on target cell Counter P437a is incremented if the cause included in the PCCF reported is one of the following: "On going CS connection "MS in GMM Standby state Forced to the Standby state
7 Cell Reselection
QoS Degradation
QoS degraded due to cell reselection
Throughput [kbit/s]
1. CS change TBF 1 (Cell 1) Cell Re-Selection
Data Call Duration

1. CS change TBF 2 (Cell 2)
CS 2
Average Throughput Throughput

CS 1
4 sec
t0
1 3 185
t1
t2
t3
t4
t5
Time [s]
7 Cell Reselection
NACC and (P)SI Status

QoS improved with NACC and (P)SI status
Throughput [kbit /s]
1. CS change TBF 1 (Cell 1) Cell Re-Selection
Data Call Duration
1. CS change TBF 2 (Cell 2)
CS 2
Average Throughput Throughput

CS 1
1 sec
t0
1 3 186
t1
t2
t3
t4
t5
Time [s]
7 Cell Reselection
NACC and (P)SI Status [cont.]

In the source cell
NC0 MODE
P460c
Minimum Network Assisted cell reselection duration Maximum Network Assisted cell reselection duration.
MS UL or DL TBF
MFS Cell A
MFS Cell B
P460b
P458
Number of times the procedure of broadcast of neighbor (P)SI messages is invoked
Packet Cell Change Notification Retrieval of SI instances Packet Neighbor Cell Data (SI1)
P458
P459
Signaling load induced in the cell by the procedure of broadcast of neighbor (P)SI messages
Packet Neighbor Cell Data (SI3) Packet Neighbor Cell Data (SI13) Packet Cell Change Continue
P212 (time)
reception of FLUSH LL
1 3 187
The duration of a NACC cell reselection is measured in the source cell between the start of emission of Packet Neighbour Cell Data messages (following the reception of the Packet Cell Change Notification message) and the reception of the Flush-LL message. The source cell is the cell where the cell reselections are outgoing.
The duration of a NACC cell reselection is measured in the source cell between the start of emission of Packet Neighbour Cell Data messages and the reception of the Flush-LL message
7 Cell Reselection

MS On going UL or DL TBF Packet Measurement Report / PACCH Packet Neighbour Cell Data (S1) / PDCH Packet Neighbour Cell Data (SI3) / PDCH Packet Neighbour Cell Data (SI13) / PDCH Packet Cell Change Order / PACCH (4) Packet Control Acknowledgement / PACCH T_Ack_Wait T_Wait_Flush
P209 (time) P458
BSS Serving cell
BSS Target cell

NC2 MODE
SGSN
Packet Channel Request / PRACH Packet Uplink Assignment / PCCCH On going UL TBF (8)
UL LLC PDU [TLLI] FLUSH-LL PDU [TLLI, old BVCI] FLUSH-LL-ACK PDU [TLLI, deleted]
1 3 188
7 Cell Reselection

In target cell (P) SI status
P456
Number of times the procedure of broadcast of serving cell PSI for Packet PSI Status or the procedure of sending of Packet Serving Cell Data for Packet SI Status is invoked. Signaling load induced in the cell by the procedure of broadcast of (P)SI messages
MS
MFS Cell A UL or DL TBF
MFS Cell B
Packet SI Status (SI2, SI2bis, SI2ter msg type missing)
P457
P456
Packet Serving Cell Data (SI2) Packet Serving Cell Data (SI2bis) Packet Serving Cell Data (SI2ter)
P457
UL or DL TBF
1 3 189
This mechanism is applied in both NC0 and NC2 P457: Number of RLC blocks used: 1) To broadcast a PSI message for Packet PSI Status feature 2) To send a PACKET SERVING CELL DATA message for Packet SI Status feature.
7 Cell Reselection
Exercise
Exercise 1: What kind of cell reselection procedure ( NC0 or NC2 / with or without NACC) you can observe in Trace10,11, 12 and Trace13? Exercise 2: For each case of cell reselection,
Find specific messages to NACC (P)SI status if any find old and new cell identities.
Exercise 3 : looking the content of SI Status can you guess which SI where given during NACC procedure
1 3 190
7 Cell Reselection
QoS Indicators
NACC and (P)SI status reselection NCO reselection Number of successes, Nb of DL/UL TBF releases NC2 reselection
NC2 reselection start Number of requests Number of successes, Nb of DL/UL TBF releases Success rate Failure causes Target cell rejected Target cell not rejected Reselection time TBF establishment end time
1 3 191
Outgoing Incoming
Max Avg Min
7 Cell Reselection
QoS Indicators, NC0

Cell reselection: ALL = NC0+NC2
NC0+NC2 re-selection P397 NC0 re-selection Number of successful NC0 cell re-selection P436 Number of successful cell re-selection
1 3 192
7 Cell Reselection
QoS Indicators, NC2

Cell reselection: NC2
NC2 re-selection Number of NC2 cell re-selection request cause PT1 (too low downlink level) Number of NC2 cell re-selection request cause PT2 (better neighbour cell) Number of NC2 cell re-selection request cause PT3 (too bad downlink quality) Number of NC2 cell re-selection request cause PT4 (too bad uplink quality) Ratio of NC2 re-selection cause Emergency Ratio of NC2 re-selection cause Better Condition Number of NC2 cell re-selection success cause PT1 (too low downlink level) Number of NC2 cell re-selection success cause PT2 (better neighbour cell) Number of NC2 cell re-selection success cause PT3 (too bad downlink quality) Number of NC2 cell re-selection success cause PT4 (too bad uplink quality) Number of NC2 cell re-selection requests Number of NC2 cell re-selection successes NC2 cell re-selection success rate P433a P433b P433c P433d (P433a+P433c+P433d) / (P433a+P433b+P433c+P433d) * 100 (P433b) / (P433a+P433b+P433c+P433d) * 100 P435a P435b P435c P435d P433a+P433b+P433c+P433d P435a+P435b+P435c+P435d
KPI KPI
(P435a+P435b+P435c+P435d) / (P433a+P433b+P433c+P433d)
1 3 193
7 Cell Reselection
QoS Indicators, NC2 [cont.]
B10
P437a
Number of NC2 cell reselection failures reported by the MS which leads to reject the target cell for a while. Number of NC2 cell reselection failures reported by the MS which does not lead to reject the target cell for a while. Number of NC2 cell reselection failures reported by the MS due to load (cause : "immediate assign reject" or "packet access reject on target cell")
P437b
P464
(((P433a) + (P433b) + (P433c) +(P433d)) - ((P435a) + (P435b) + (P435c) + (P435d)) - (P437b) - (P437a) P464) / Rate of NC2 failures due to BSS problem ((P433a) + (P433b) + (P433c) +(P433d)) P432c P432b Minimum duration of successful incoming intra-RA intraMFS NC2 cell reselections (measured in the target cell). Maximum duration of successful incoming intra-RA intraMFS NC2 cell reselections (measured in the target cell). Average duration of successful incoming intra-RA intraMFS NC2 cell reselections (measured in the target cell). Minimum duration of successful outgoing NC2 cell reselections (measured in the source cell) Maximum duration of successful outgoing NC2 cell reselections (measured in the source cell) Average duration of successful outgoing NC2 cell reselections (measured in the source cell)
Removed B10
P432a P431c P431b
Removed B10
P431a
1 3 194
P432x counters are taking into account only the Cell Reselections for which Serving and Target cells belong to the same RA and the same MFS.
7 Cell Reselection
B10
Indicator name TIME_SOURCE_NC2_CELL_RESEL TIME_SOURCE_NACC_CELL_RESEL TIME_TARGET_NC2_CELL_RESEL NB_TARGET_NC2_CELL_RESEL GPRS_NC2_reselect_source_cell_ti me_avg GPRS_NC_reselect_NACC_avg_dur ation
definition Cumulated time duration of successful outgoing NC2 cell reselections (measured in the source cell). Cumulated time of the successful Network Assisted cell reselection duration in NC0 mode Cumulated time duration of successful incoming intraRA intra-MFS NC2 cell reselections (measured in the target cell). Number of successful incoming intra-RA intra-MFS NC2 cell reselections (measured in the target cell). Average duration of successful outgoing NC2 cell reselections (measured in the source cell). Cumulated time of the successful Network Assisted cell reselection duration in NC0 mode P209 P212 P210 P211
Ref
P209 / (P435a + P435b + P435c + P435d) (P212 / P213)*1000
1 3 195
P209: Within the granularity period, the MFS cumulates the duration of each successful outgoing NC2 cell reselections triggered by the BSS in the source cell. The duration of a NC2 cell reselection is measured in the source cell between the acknowledgement of the Packet Cell Change Order message and the reception of the Flush-LL message. The source cell is the cell where the NC cell reselections are outgoing. P210: Within the granularity period, the MFS cumulates the duration of the successful incoming intra-RA intraMFS NC2 cell reselections triggered by the BSS in the source cell. The duration of a NC2 cell reselection is measured in the source cells between the acknowledgement of the Packet Cell Change Order message and the reception of the Flush-LL message. These measures are forwarded to the target cell in the intra-MFS TLLI Rerouting Confirm message and then cumulated in the target cell. The source cells are the cells where the NC cell reselections are outgoing, whereas the target cell is the cell where the NC cell reselections are incoming. P211: Within the granularity period, the MFS counts the number of each successful outgoing NC2 cell reselections triggered by the BSS in the source cell. A NC2 cell reselection is successful when in the source cells after the acknowledgement of the Packet Cell Change Order message is received , the Flush-LL message is received. These measures are forwarded to the target cell in the intra-MFS TLLI Rerouting Confirm message and then cumulated in the target cell. The source cells are the cells where the NC cell reselections are outgoing, whereas the target cell is the cell where the NC cell reselections are incoming.
7 Cell Reselection
Counter number
P221
Name
NB_PCCO_ACK_UL_NC2_CELL_RESEL
Definition
Number of Packet Cell Change Order acknowledged by the MS while in UL transfer Number of Packet Cell Change Order acknowledged by the MS while in DL transfer Number of Packet Cell Change Order messages sent while in DL transfer. Number of FLUSH-LL PDU received after a Packet Cell Change Order has been sent to the MS while in DL transfer. Number of Packet Cell Change Failure received from the MS after a Packet Cell Change Order has been sent to the MS while in DL transfer Number of Packet Cell Change Order messages sent while in UL transfer. Number of FLUSH-LL PDU received after a Packet Cell Change Order has been sent to the MS while in UL Number of Packet Cell Change Failure received from the MS after a Packet Cell Change Order has been sent to the MS while in UL transfer.
P222
NB_PCCO_ACK_DL_NC2_CELL_RESEL
P223
NB_PCCO_NC2_CELL_RESEL_DL_TBF
P224
NB_FLUSH_NC2_CELL_RESEL_DL_TBF
P225
NB_PCCF_NC2_CELL_RESEL_DL_TBF
P226
NB_PCCO_NC2_CELL_RESEL_UL_TBF
P227
NB_FLUSH_NC2_CELL_RESEL_UL_TBF
P228
NB_PCCF_NC2_CELL_RESEL_UL_TBF
1 3 196
7 Cell Reselection
QoS Indicators, NACC (P)SI Status
B10
Counter number P456 NB_PSI_PROC
Name
Definition
Number of times the procedure of broadcast of serving cell PSI for Packet PSI Status or the procedure of sending of Packet Serving Cell Data for Packet SI Status is invoked.
P457 P458 P459 P460a P460b P460c
NB_PSI_MES NB_NEIGH_PSI_PROC NB_NEIGH_PSI_MES AV_SOURCE_NACC_CELL_RESEL_TIME MAX_SOURCE_NACC_CELL_RESEL_TIME MIN_SOURCE_NACC_CELL_RESEL_TIME
Signaling load induced in the cell by the procedure of broadcast of (P)SI messages Number of times the procedure of broadcast of neighbor (P)SI messages is invoked Signaling load induced in the cell by the procedure of broadcast of neighbor (P)SI messages Average Network Assisted cell reselection duration. Maximum Network Assisted cell reselection duration. Minimum Network Assisted cell reselection duration.
Removed B10
1 3 197
7 Cell Reselection
End-User QoS Improvement with NC2

Enhanced cell reselection can be easily tested and evaluated through drive test route
DL FTP transfer of a file In a bi-band network (GSM900,GSM1800) GSM1800 cells are favored in CS idle mode: CELL_RESELECT_OFFSET = 20dB Route length is about 1.150 Km Two 900 cells and two 1800 cells are covering MS is GPRS multi-slot class 8 (4+1)
1 3 198
7 Cell Reselection
End-User QoS Improvement with NC2 [cont.]

Gain in throughput
NC0 34,7 kbits/s NC2 + GPRS redirection 40,2 kbits/s
9 reselections during transfer

60 50 40 30 300 20 10 0 1 28 55 82 109 136 163 190 217 244 271 298 325 200 100 0 700 600 500
2 reselections during transfer

600 500 400 60 50 40 30 20 10 0 1 33 65 97 129 161 193 225 257 289 321 353 ServBCCH RLC_Throughp ut_DL
400
RLC_Throughput_DL Se rvBCCH
300 200 100 0
9 interruptions
1 3 199
2 interruptions

1 3 200
End of Module Description of the Main BSS GPRS QoS Counters and Indicators
1 3 201
14
Section 1 EGPRS QoS

Module 4 Detection of the Main BSS GPRS QoS Problems
Blank Page
142
EGPRS QoS Detection of the Main BSS GPRS QoS Problems EVOLIUM Introduction to GPRS and E-GPRS QoS Monitoring - B10
Module Objectives
Detect the main GPRS QoS problems of the Alcatel-Lucent BSS
143
144
Table of Contents
1 General Principles 2 Main BSS GPRS QoS Problems Page 7 12
145

146
1 General Principles
147
KPI, Warning Indicator

A lot of QoS indicators are computed from BSS GPRS counters QoS indicators that will be followed-up by management are called KPI: Key Performance Indicator Among all BSS GPRS QoS indicators some are used to detect QoS problems: they are called WARNING indicators
usually all KPIs other major indicators as from radio optimizer view
148
QoS Threshold, Sampling Indicator

A WARNING indicator is often attached a QoS threshold value to decide if the indicator value is bad or not In case a WARNING indicator value is considered as bad then another indicator called the SAMPLING indicator and attached to the WARNING indicator must be checked A SAMPLING indicator is attached a sample threshold value to decide if the WARNING indicator value is relevant or not
149
QoS Problem Detection

List of BSS QoS indicators I1. I2. I3. I4. I5, I6, I7, I8, etc
no
Are some Warning indicator values bad? yes
end
Check the related Sampling indicator value
no
Is the Warning indicator value relevant?
yes
Analyze QoS problem
1 4 10
QoS Problem Detection, Exercise

Exercise: Using analogy with BSS GSM QoS indicators find the Sampling indicator attached to each of the following GPRS Warning indicators:
TBF establishment success rate TBF drop rate NC2 Cell reselection success rate
1 4 11
2 Main BSS GPRS QoS Problems
1 4 12
Exercise 1: List Them

Exercise 1: List the main BSS QoS problems seen as a QoS degradation by the end user
BSS GPRS QoS problems are relating to Data transfer problems between the MS and the GPRS Core network, which are due to the BSS
1 4 13
Exercise 2: Find Warning and Sampling Indicators

Exercise 2: Find the Warning and Sampling indicators which will be used to detect each of these problems:
Data transfer Data transfer Data transfer Data transfer not established degraded interrupted dropped
1 4 14
Exercise 3: UL Data Transfer Establishment Degradation

Exercise 3: Find the Warning indicator degraded by difficulties to establish a UL TBF resulting in a TBF establishment after MS repetitions of channel request
Can this problem be identified through QoS indicators? If not, what must be done to find the cause of the UL data transfer establishment degradation?
1 4 15
Exercise 4: DL Data Transfer Establishment Degradation

Exercise 4: Find the Warning indicator degraded by difficulties to establish a DL TBF resulting in a TBF establishment after MFS repetitions of channel assignment
Can this problem be identified through QoS indicators? If not, what must be done to find the cause of the DL data transfer establishment degradation?
1 4 16

1 4 17
End of Module Detection of the Main BSS GPRS QoS Problems
1 4 18
15
Section 1 EGPRS QoS

Module 5 Analysis of the Main BSS GPRS QoS Problems
Blank Page
152
EGPRS QoS Analysis of the Main BSS GPRS QoS Problems EVOLIUM Introduction to GPRS and E-GPRS QoS Monitoring - B10
Module Objectives
Analyze the main GPRS QoS problems of the Alcatel-Lucent BSS
153
154
Table of Contents
Page
1 Find the causes of a BSS GPRS QoS problem 7 2 Characterize the QoS Indicators Used in the Analysis of a BSS GPRS QoS Problem10 3 What Kind of QoS Problem Is Recorded in the Trace? 16
155

156
1 Find the causes of a BSS GPRS QoS problem
157
1 Find the Causes of a BSS GPRS QoS Problem
Exercise 1a: Find the Probable Causes

Exercise 1a: Find the probable causes of a BSS GPRS QoS problem
158
Exercise 1a: Find the probable causes of a BSS GPRS QoS problem
For each of the 4 typical BSS GPRS QoS problems, mark the probable cause(s) each cause corresponding to a specific BSS PM counter
QoS problem probable cause MS suspend TBF establishment failure
(1)
TBF throughput degradation
TBF interruption
TBF drop
Gb
Radio
Cell reselection
Congestion
MS error (1) Fast PDCH pre-emption of the PDTCH carrying the PACCH of the TBF Fast PDCH pre-emption of the PDTCH carrying only a PDTCH of the TBF
(2)
BSS problem
Sub-optimal usage of radio resources
(3)
(1) MS error are not counted in a specific counter (2) any software or hardware failure, occuring in the BSS, provok ing a TBF problem not counted as another cause (3) any reason why a mobile involved in a TBF get a data throughput lower than its transfer capability
1 Find the Causes of a BSS GPRS QoS Problem
Exercise 1b: Find the more Detailed Reasons

Exercise 1b: Find a more detailed reason for some of the probable causes of a BSS GPRS QoS problem
1 5 10
Exercise 1b: Find a more detailed reason for some of the probable causes of a BSS GPRS QoS problem probable cause Fast PDCH Fast PDCH pre-emption pre-emption Sub-optimal of the of the usage of PDTCH PDTCH radio carrying carrying the resources only a PACCH of PDTCH of the TBF the TBF
Congestion
Radio
Gb
MS suspend
Cell reselection
reason Interference NC2 cell reselection not activated NC2 cell reselection not efficient Lack of PDCH resources
(1)
Lack of CCCH resources
Lack of Abis resources
Lack of Ater resources
Lack of GPU resources T_PDCH_PREEMPTION parameter value too low BSS SW or HW failure
GSS SW or HW failure Re-allocation trigger T1 is not efficient Abis MW problem System or protocol error between BSS and GSS Coverage
Abis signalling overload Bad setting of cell reselection parameters Bad setting of CS/MCS adaptation parameters High CS traffic
High PS traffic
(1) can be due to:
tow low MAX_PDCH parameter value, too high CS traffic, too high PS traffic, too long Delayed DL TBF Release phase, poor re-allocation algorithm efficiency All Rights Reserved Alcatel-Lucent 2008 BSS SW or HW failure
3JK10241AAAAWBZZA Issue 01 Section 1 Module 5 Page 11
2 Characterize the QoS Indicators Used in the Analysis of a BSS GPRS QoS Problem
1 5 12
Exercise 2a: TBF Establishment Failure

Exercise 2a: Characterize the QoS indicators used in the analysis of a TBF establishment failure
1 5 13
Exercise 2a: Characterize the QoS indicators used in the analysis of a TBF establishment failure Congestion % TBF establishment failure due to congestion Lack of PDCH resources % TBF establishment failure due to radio congestion bad MAX_PDCH parameter setting
Maximum nb of established SPDCH Average MAX_SPDCH_LIMIT value MAX_SPDCH_LIMIT reduction rate Check MAX_PDCH parameter value
high CS traffic
Average MAX_SPDCH_LIMIT value Nb of PDCH released after having been marked by soft pre-emption Average nb of TBF candidates to T1 re-allocation per PDCH released after having been marked by soft pre-emption
high PS traffic
Maximum nb of established SPDCH Average MAX_SPDCH_LIMIT value
Lack of Abis resources Lack of Ater resources Lack of GPU resources
MAX_SPDCH_LIMIT reduction rate too long Delayed DL TBF % of time established DL TBFs are release phase active Ratio of DL TBF resumptions per established DL TBF Average TBF duration Average MS session duration Average number of GPRS sessions per call Check T_NETWORK_RESPONSE_TIME parameter value poor re-allocation Average nb of TBF established per algorithm efficiency MS session Nb of TBF re-allocation requests Re-allocation success rate use GSM indicators and BSS BSS SW or HW failure equipement alarms use GSS indicators and/or GSS GSS SW or HW failure equipment alarms % TBF establishment failure due to Abis congestion % TBF establishment failure due to Ater congestion % TBF establishment failure due to (DSP+CPU) GPU congestion
Exercise 2a: Characterize the QoS indicators used in the analysis of a TBF establishment failure (suite) Radio % TBF establishment failure due to radio Coverage use GSM indicators Interference use GSM indicators use GSM indicators and Abis Abis MW problem transmission alarms use GSM indicators and BSS BSS SW or HW failure equipement alarms NC2 cell reselection not Number of NC2 cell activated reselection requests Lack of CCCH resources use GSM indicators
Gb
% TBF establishment failure due to Gb pb system or protocol error trace Gb interface between BSS and GSS GSS SW or HW failure
BSS
% TBF establishment failure due to BSS pb BTS, BSC or MFS use GPRS LAPD counters, software or hardware BSS indicators and alarms failure trace Abis, Ater interface system or protocol error trace Abis, Ater interface between BSS and MS
MS error
2 Characterize the QoS indicators used in the analysis of a BSS GPRS QoS Problem
Exercise 2b: TBF throughput degradation

Exercise 2b: Characterize the QoS indicators used in the analysis of a TBF throughput degradation
1 5 16
Exercise 2b: Characterize the QoS indicators used in the analysis of a TBF throughput degradation
% time MS engaged in a TBF in Sub-optimal usage the direction of the bias and they of radio resources are granted the maximum nb of TS they support in that direction Lack of PDCH resources % of partial TS allocation success bad MAX_PDCH parameter setting Maximum nb of established SPDCH Average MAX_SPDCH_LIMIT value MAX_SPDCH_LIMIT reduction rate Check MAX_PDCH parameter value high CS traffic Average MAX_SPDCH_LIMIT value Nb of PDCH released after having been marked by soft pre-emption Average nb of TBF candidates to T1 reallocation per PDCH released after having been marked by soft preemption high PS traffic Maximum nb of established SPDCH Average MAX_SPDCH_LIMIT value MAX_SPDCH_LIMIT reduction rate too long Delayed DL TBF % of time established DL TBFs are active release phase Ratio of DL TBF resumptions per established DL TBF Average TBF duration Average MS session duration Average number of GPRS sessions per call Check T_NETWORK_RESPONSE_TIME parameter value poor re-allocation algorithm efficiency Average nb of TBF established per MS session Nb of TBF re-allocation requests Re-allocation success rate BSS SW or HW failure GSS SW or HW failure use GSM indicators and BSS equipement alarms use GSS indicators and/or GSS equipment alarms
Exercise 2b: Characterize the QoS indicators used in the analysis of a TBF throughput degradation (suite) % time MS engaged in a TBF in the direction of the Sub-optimal usage bias and they are granted of radio resources the maximum nb of TS they support in that direction Lack of Abis resources % TBF establishment failure due to Abis congestion Cumulative time during a GCH resource is busy in the cell Cumulative time during which there is a deficit of GCH resources in the cell Maximum number of GCH in deficit reached in the cell % TBF establishment failure due to Ater congestion % of time the GPU is in GCH congestion % TBF establishment failure due to (DSP+CPU) GPU congestion % of time the SPDCH are degraded due to Ater congestion Ratio of RLC blocks transmitted on most robust CSx (or MCx) % of retransmission of RLC blocks for CS (or MCS) TBF_CS_INIT Check CS and MCS adaptation paramaters value Ratio of RLC blocks transmitted on most robust CSx (or MCx) % of retransmission of RLC blocks for CS (or MCS) TBF_CS_INIT Check CS and MCS adaptation paramaters value
Lack of Ater resources
Lack of GPU resources
Bad setting of CS (or MCS) adaptation parameters
Bad setting of CS (or MCS) adaptation parameters
Fast PDCH preNb of PDCH released after emption of the having been marked by soft PDTCH carrying only pre-emption a PDTCH of the TBF high CS traffic Average MAX_SPDCH_LIMIT value Average nb of TBF candidates to T1 reallocation per PDCH released after having been marked by soft pre-emption
Radio Ratio of RLC blocks Coverage / Interference transmitted on most robust CSx (or MCx) % of retransmission of RLC blocks for CS (or MCS) TBF_CS_INIT use GSM indicators
Exercise 2c: TBF Interruption

Exercise 2c: Characterize the QoS indicators used in the analysis of a TBF interruption
1 5 19
Exercise 2c: Characterize the QoS indicators used in the analysis of a TBF interruption CAUTION: % TBF acceptable release rate can increase be due to the modification of the duration of the delayed state phase of the Delayed DL TBF release procedure after parameter tuning. Therefore check evolution of the indicator : % TBF acceptable rele Fast pre-emption of the PDCH TBF release rate due to fast carrying the pre-emption PACCH of the TBF Re-allocation trigger T1 TBF re-allocation trigger T1 is not efficient success rate Check T_PDCH_PREEMPTION parameter value Lack of PDCH resource high PS traffic see previous cases MAX_SPDCH_LIMIT reduction rate % TBF establishment failure due to radio congestion MS Suspend TBF release rate due to MS suspend high CS traffic Average MAX_SPDCH_LIMIT value Nb of PDCH released after having been marked by soft pre-emption Average nb of TBF candidates to T1 re-allocation per PDCH released after having been marked by soft pre-emption Average number of GPRS sessions per call Cell reselection TBF release rate due to cell reselection NC2 cell reselection not activated NC2 cell reselection is not efficient
Number of NC2 cell reselection requests NC2 cell reselection success rate Number of NC2 cell reselection requests Check NC2 cell reselection parameters value
Exercise 2d: TBF drop

Exercise 2c: Characterize the QoS indicators used in the analysis of a TBF drop
1 5 21
Exercise 2d: Characterize the QoS indicators used in the analysis of a TBF drop CAUTION: % TBF abnormal release rate can increase be due to the modification of the duration of the delayed state phase of the Delayed DL TBF release procedure after parameter tuning. Therefore check evolution of the indicator : % TBF acceptable releas Radio TBF drop rate due to radio Coverage Interference Abis MW problem BSS SW or HW failure TBF drop rate due to stagnating TX window TBF drop rate due to blocking situation system or protocol error trace Abis, Ater interface between BSS and MS Gb TBF drop rate due to Gb system or protocol error trace Gb interface between BSS and GSS BSS TBF drop rate due to BSS BTS, BSC or MFS software or hardware failure
use GSM indicators use GSM indicators use GSM indicators and Abis transmission alarms use GSM indicators and BSS equipement alarms
MS error
use GPRS LAPD counters, BSS indicators and alarms trace Abis, Ater interface
Cell reselection
TBF drop rate due to radio NC2 cell reselection not activated and NC0 cell reselection takes long time
Number of NC2 cell reselection request Number of NC0 cell reselection success per call
3 What Kind of QoS Problem Is Recorded in the Trace?
1 5 23
3 What Kind of QoS Problem Is Recorded in the Trace?
Exercise
What kind of BSS GPRS QoS problem you can observed in the trace 20?
1 5 24

1 5 25
End of Module Analysis of the Main BSS GPRS QoS Problems
1 5 26
Exercise 2d: TBF Drop

Exercise 2d: Characterize the QoS indicators used in the analysis of a TBF drop
1 5 27
16
Section 1 EGPRS QoS

Module 6 Appendix
Blank Page
162
EGPRS QoS Appendix EVOLIUM Introduction to GPRS and E-GPRS QoS Monitoring - B10
Module Objectives
Describe List Explain Identify ...
163
164
Table of Contents
1 2 3 4 Real Radio Drop (P)SI Messages Details Exercises on NACC (P)SI STATUS KPIs 4.1 Main KPIs 4.2 Important KPIs 5 Whats New or Modified in B10 Page 7 10 13 15 16 17 20
165

166
1 Real Radio Drop
167
1 Real Radio Drop
Radio Drop and Reselection
Cell Reselection 397
Real Radio Drop

YES
PIM
= Counted Late = Counted (All On Time) = 302 (434 396)

No Release No Counter
NO (PTM) 3105 Overload NO YES
302
COUNTED
NO
FLUSH YES
FLUSH YES
NO
FLUSH ON TIME
396
FLUSH LATE = All - On Time
ALL FLUSHs
434
END
168
1 Real Radio Drop
Radio Drop and Suspend

VOICE CALL
Real Radio Drop

= Counted Late = Counted (All On Time) = 302 (98c 98a)
3105 Overload NO
YES
302
COUNTED
NO
SUSPEND
SUSPEND
NO
YES SUSPEND ON TIME 98a
YES SUSPEND LATE = All - On Time
ALL SUSPENDs
98c
END
169
2 (P)SI Messages Details
1 6 10
SI Messages Details
Coding of the SI typical message in PNCD/PSCD messages
SI SI SI SI SI SI SI SI SI SI SI SI SI SI 1 2 2 2 2 3 4 5 5 5 6 7 8 9 19 1A 02 03 07 1B 1C 1D 05 06 1E 1F 18 04
SI 13 00
bis ter quater
SI 14 SI 15 SI 16 SI 17 SI 18 SI 19 SI 20
01 44 3D 3E 40 41 42
bis ter
1 6 11
PSI Messages Details

Coding of the PSI typical message in PNCD messages
PSI1 PSI2 PSI3 PSI3 bis PSI3 ter PSI3 quater PSI4 PSI5 PSI6 PSI7 PSI8 PSI13 PSI14 PSI15 C4 C8 CC D0 F0 F4 D4 D8 C0 E0 E4 DC E8 F8
1 6 12
3 Exercises on NACC (P)SI STATUS
1 6 13
3 Exercises on NACC (P)SI STATUS
Exercise 1
A/ extracting Packet Neighbor Cell Data message trace 12 could you find what are the SI Message Type number sent to the mobile ? B/ extracting PSI status message in the same trace could find what are SI message missing for the Mobile?
For your help, please use the information in previous 2 pages
1 6 14
4 KPIs
1 6 15
4 KPIs
4.1 Main KPIs

Total number of TBF establishment requests TBF establishment success rate Drop rate Acceptable release rate Normal release rate In RLC ack mode, rate of RLC retransmitted data bytes sent on PDTCH and encoded in CS-x PDTCH RLC block CSx / (CS1+CS2+CS3+CS4) ratio PDTCH RLC block retransmission rate in GPRS ack mode In RLC ack mode, ratio of useful RLC blocks sent in RLC acknowledged mode on PDTCH and encoded in MCS-x In RLC ack mode, rate of RLC retransmitted data bytes sent on PDTCH and encoded in MCS-x Number of NC2 cell re-selection requests NC2 cell reselection success rate
1 6 16
EGPRS QoS Appendix EVOLIUM Introduction to GPRS and E-GPRS QoS Monitoring - B10 All Rights Reserved Alcatel-Lucent 2008
4 KPIs
4.2 Important KPIs
1 6 17
DL TBF Establishment Request % allocated Success % Success UL TBF Establishment Request % allocated Success % Success DL TBF Reallocation (DL TBF Estab) % DL Realloc Suc UL TBF Reallocation (UL TBF Estab) % UL Realloc Suc DL data transfert % Normal Release % Acc release % drop TBF DL UL data transfert % Normal Release % Acc release % drop TBF UL DL Coding scheme usage (and Partially DL RLC Traffic) CSx Useful Bytes MCSx Useful Bytes kbps per EGPRS TBF kbps per GPRS TBF UL Coding scheme usage (and UL RLC Traffic) CSx Useful Bytes MCSx Useful Bytes kbps per EGPRS TBF kbps per GPRS TBF GPRS_UL_useful_throughput_CSx_bytes_ack GPRS_UL_useful_throughput_MCSx_bytes_ack GPRS_UL_useful_throughput_radio_EGPRS_ TBF_avg GPRS_UL_useful_throughput_radio_GPRS_T BF_avg
GPRS_DL_TBF_Request GPRS_DL_TBF_estab_allocated_rate GPRS_DL_TBF_success GPRS_DL_TBF_success_rate
TRDTERQN QRDTEAPR TRDTESUN QRDTESUR
GPRS_UL_TBF_request GPRS_UL_TBF_estab_allocated_rate GPRS_UL_TBF_success GPRS_UL_TBF_success_rate
TRUTERQN QRUTEAPR TRUTESUN QRUTESUR
GPRS_DL_TBF_Realloc_Success_Rate
TRDRRSUR
GPRS_UL_TBF_Realloc_Success_Rate
TRURRSUR
GPRS_DL_TBF_normal_release_rate GPRS_DL_TBF_acceptable_release_rate GPRS_DL_TBF_drop_rate
QRDDTNRR QRDDTACR QRDDTARR
GPRS_UL_TBF_normal_release_rate GPRS_UL_TBF_acceptable_release_rate GPRS_UL_TBF_drop_rate
QRUDTNRR QRUDTACR QRUDTARR
GPRS_DL_useful_throughput_CSx_bytes_ack GPRS_DL_useful_throughput_MCSx_bytes_ack GPRS_DL_useful_throughput_radio_EGPRS_ TBF_avg GPRS_DL_useful_throughput_radio_GPRS_T BF_avg
TRPDDBYGAN TRPDDBYEAN TRPDDTBEGA TRPDDTBGPA
TRPDUBYGAN TRPDUBYEAN TRPDUTBEGA TRPDUTBGPA
DL RLC trafic % CSx Retrans CSx retrans MCSx retrans %MCSx Retrans UL RLC trafic % CSx Retrans CSx retrans MCSx retrans %MCSx Retrans PDCH Allocation (to be reviewed) DL Optimal Alloc %DL Optimal Alloc UL Optimal Alloc %UL Optimal Alloc GPRS_DL_biased_and_DL_optimal_allocation_ti me GPRS_DL_biased_and_DL_optimal_alloc_percent GPRS_UL_biased_and_UL_optimal_allocation_ti me GPRS_UL_biased_and_UL_optimal_alloc_percent QRDRRSUT QRDRRSUP QRURRSUT QRURRSUP GPRS_UL_RLC_CSx_PDTCH_retransmissing_ac k_rate GPRS_UL_RLC_bytes_PDTCH_CSx_retransmissi ng_ack GPRS_UL_RLC_bytes_PDTCH_MCSx_retransmi ssing_ack GPRS_UL_RLC_bytes_PDTCH_MCSx_retrans_a ck_ratio QRUDTRRR QRUDTRRBCN QRPDURMN QRPDURMO GPRS_DL_RLC_PDTCH_CSx_retransmissing_ac k_rate GPRS_DL_RLC_bytes_PDTCH_CSx_retransmissi ng_ack GPRS_DL_RLC_bytes_PDTCH_MCSx_retransmi ssing_ack GPRS_DL_RLC_bytes_PDTCH_MCSx_retrans_a ck_ratio QRDDTRRR QRDDTRRBCN QRPDDRMN QRPDDRMO
PDCH usage GPRS_PDCH_traffic_time
Definition Cumulative time during which the slave PDCHs are established and carry at least one UL or DL TBF.(established in GPRS mode or EGPRS mode). Cumulative time during which the slave PDCHs are established and carry at least one UL or DL TBF.(established in EGPRS mode) Percentage of time during which the established PDCHs in traffic are supporting EGPRS traffic.
Ref Name ARPDCUSBUT
GPRS_PDCH_EGPRS_traffic_time
ARPDCUSEGT
GPRS_PDCH_EGPRS_traffic_time_r atio
ARPDCUSEGO
5 Whats New or Modified in B10
1 6 20
5 Whats New or Modified in B10
Summary
Reduction of 32 bytes 0 second ping time (no specific counter) Dual Transfer Mode (simultaneous CS and PS traffic), new counters:
Establishment request / attempt / success Establishment failure (radio, congestion) cumulated time of operation for DTM MS Acceptable TBF drop due to CS operation GTTP usage
Extended Dynamic Allocation (more than 2 TS in UL)

New UL TBF usage counters
Distribution counters based on GPRS and EGPRS LLC throughput TBF radio drop counters more detailed New MS capabilities / multislot class breakdown Number of useful UL and DL RLC data blocks retransmitted per MCS NC2 reselection
Removed average duration counters New cumulated duration counters
1 6 21
EGPRS QoS Appendix EVOLIUM Introduction to GPRS and E-GPRS QoS Monitoring - B10 All Rights Reserved Alcatel-Lucent 2008

1 6 22
End of Module Appendix
1 6 23
Last But One Page

1
@@PRODUCT @@COURSENAME
All Rights Reserved Alcatel-Lucent @@YEAR
All Rights Reserved Alcatel-Lucent @@YEAR @@COURSENAME - Page 1
All rights reserved Alcatel-Lucent @@YEAR Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel-Lucent
All Rights Reserved Alcatel-Lucent @@YEAR @@COURSENAME - Page 2

3fl11829acaawbzza 02

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

3fl11829acaawbzza 02

Загружено:

Авторское право:

Доступные форматы

EVOLIUM Introduction to GPRS and EGPRS QoS Monitoring - B10

All Rights Reserved Alcatel-Lucent 2008

All Rights Reserved Alcatel-Lucent 2008

This page is left blank intentionally

Terms of Use and Legal Notices

All rights reserved Alcatel-Lucent 2008

All Rights Reserved Alcatel-Lucent 2008

This page is left blank intentionally

4. Topic/Section is Positioned Here

7. Topic/Section is Positioned Here

2. Topic/Section is Positioned Here 3. Topic/Section is Positioned Here

All Rights Reserved Alcatel-Lucent 2008

Course Outline [cont.]

All Rights Reserved Alcatel-Lucent 2008

This page is left blank intentionally

Welcome to Introduction to GPRS and E-GPRS QoS Monitoring - B10

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

All Rights Reserved Alcatel-Lucent 2008

Course Objectives [cont.]

All Rights Reserved Alcatel-Lucent 2008

This page is left blank intentionally

About this Student Guide

All Rights Reserved Alcatel-Lucent 2008

EVOLIUM Introduction to GPRS and E-GPRS QoS Monitoring - B10

Where you can get further information

About this Student Guide [cont.]

All Rights Reserved Alcatel-Lucent 2008

This page is left blank intentionally

Client (Company, Center) : Language : Switch

Number of trainees : Surname, First name :

Instructional objectives 1 To be able to XXX

Self-assessment of Objectives [cont.]

All Rights Reserved Alcatel-Lucent 2008

Thank you for your answers to this questionnaire

Do not delete this graphic elements in here:

Section 1 EGPRS QoS

Module 1 Role of the BSS in GPRS QoS Monitoring

All Rights Reserved Alcatel-Lucent 2008

All Rights Reserved Alcatel-Lucent 2008

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent 2008

Module Objectives [cont.]

All Rights Reserved Alcatel-Lucent 2008

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent 2008

Table of Contents [cont.]

All Rights Reserved Alcatel-Lucent 2008

This page is left blank intentionally

1 Distinction between BSS/BSS+GSS/End-user GPRS QoS

All Rights Reserved Alcatel-Lucent 2008

1 Distinction between BSS/BSS+GSS/End-user GPRS QoS

Different Levels of QoS BSS

Packet Data Network

BSS QoS BSS+GSS QoS End-user QoS

1 Distinction between BSS/BSS+GSS/End-user GPRS QoS

Dependencies between QoS Levels

End-user QoS BSS+GSS QoS BSS QoS

All Rights Reserved Alcatel-Lucent 2008

1 Distinction between BSS/BSS+GSS/End-user GPRS QoS

All Rights Reserved Alcatel-Lucent 2008

1 Distinction between BSS/BSS+GSS/End-user GPRS QoS

Impact of UE: Example