Contents

1 General Information
1.1 Revision Information
1.2 Introduction

2 Function
2.1 Overview
2.2 Background
2.3 Administration of GPRS Quality of Service Function
2.4 Packet Flow Management
2.5 ABQP Handling
2.6 Quality of Service for GPRS Packet Switched Handover
2.7 Quality of Service Evaluation per TBF
2.8 Examples of Quality of Service Evaluation and Weight Calculation

3 Operational Conditions
3.1 External Conditions
3.2 Application Parameters
3.3 Commands
3.4 Printouts
3.5 Capabilities

4 Concepts

Glossary

Reference List
1.2 Introduction
The function GPRS Quality of Service is a function in the Base Station Controller (BSC) which extracts and
distributes information for assigning and differentiating resources in accordance with the requested Quality
of Service (QoS). The function stores quality of service information negotiated with the Serving GPRS Support
Node (SGSN) per Mobile Station (MS) Temporary Logical Link Identifier (TLLI) in a routing area. Based on
this information and operator controlled parameters, GPRS Quality of Service evaluates the priority and
weight of a Temporary Block Flow (TBF) and distributes that to the Function GPRS Channel Utilization (see
Reference [2]) and to the function GPRS Packet Transfer (see Reference [6]).

The function administers GPRS Quality of Service activation and deactivation.

The function GPRS Quality of Service has two separate parts:

 Quality of Service and Scheduling containing R99 QoS and R97 QoS
 Quality of Service Admission Control

The both parts of function work interchangeably, it means if one is active the other must be inactive. Either
Quality of Service and Scheduling or Quality of Service Admission Control can be active in a BSC.

GPRS Channel Utilization (see Reference [2]) function takes the priority and weight of TBFs into account
when reserving Packet Data Channels (PDCHs) for a TBF.

GPRS Packet Transfer (see Reference [6]) prioritizes and schedules TBFs in accordance with the QoS priority
and weight.

Administration of BSC Exchange Properties (see Reference [1]) handles the BSC Exchange Properties which
controls GPRS Quality of Service.

The Gb Interface, GPRS Gb over FR (see Reference [3]) or GPRS Gb over IP (see Reference [4]), implements
and provides the Packet Flow Management service primitives as specified in Reference [16]. GPRS Quality of
service uses the primitives to negotiate quality of service with SGSN. The GB Interface also inquires the SGSN
for R99 QoS support status.

GPRS System Information and Access Control (see Reference [7]) distributes the IE PFC_FEATURE_MODE in
SI13 in accordance with GPRS Quality of Service activation status.

GPRS Packet Switched Handover (see Reference [5]) requests a list of active Packet Flow Contexts (PFCs) in a
source cell when preparing for a Handover, order a list of PFCs to be set up in the target cell and finally
requests a list of PFCs which were successfully set up in target cell.
Figure 1 Function Specification Connections

2 Function
2.1 Overview
The Function Specification is divided in the following parts:

 Background of the quality of service concepts including Packet Flow Contexts, addressing, and
relationships are explained.
 Administration of GPRS Quality of Service activation and deactivation. GPRS Quality of Service is
administered separately for R99 QoS and R97 QoS.
 Packet Flow Management (PFM) includes the procedures for negotiation of quality of service
between this function and SGSN via the Gb interface.
 Aggregate BSS QoS Profile (ABQP) Handling. This procedure stores quality of service
parameters related to PFCs for an MS. The ABQP holds the quality of service attributes of a PFC.
 Quality of service evaluation per TBF. For every TBF the QoS priority and weight is evaluated
and distributed to related functions. The quality of service evaluation uses the BSC exchange
properties and the related ABQPs.
 Examples of quality of service evaluation and weight calculation.

2.2 Background
The function GPRS Quality of Service evaluates a TBF QoS priority and weight.

2.2.1 Quality of Service and Scheduling

R99 QoS

It evaluates a TBFs QoS priority and weight from the ABQP attributes Traffic Class, Traffic Handling Priority
(THP), Maximum Bitrate (MBR), and Transfer Delay. When R99 QoS is supported by the Packet Control Unit
(PCU) and the SGSN, ABQPs can be negotiated with the SGSN by means of PFM.

R97 QoS

It might not be possible to negotiate an ABPQ for a Packet Flow because the PCU or the SGSN do not support
PFM or the MS is R97 which means it is not capable to negotiate the attributes Traffic Class, THP, and MBR. To
support quality of service even for those cases when an ABQP cannot be obtained from the SGSN, R97 QoS is
used:

The R97 QoS attributes 'Precedence' and 'Peak Bitrate' are mapped to the R99 ABQP attributes Traffic Class,
THP, and MBR. Once the ABQP attributes Traffic Class, THP and MBR are mapped, the function GPRS Quality
of Service evaluates the TBF's QoS priority and weight in the same way as for a TBF with PFM-negotiated R99
ABQPs.

2.2.2 Quality of Service Admission Control

During handling of requests for a TBF, the function Quality of Service Admission Control uses the Allocation
Retention Priority (ARP) information or radio priority levels to prioritize users with high priority. It allows
high priority users to set up TBF session also in case of congestion in a cell. The ARP attribute is a
subscription parameter which is not negotiated from the mobile terminal, but it is stored in the subscriber
profile in the network Home Location Register (HLR). If the function is activated with radio priority levels
support and the PCU has no available ARP information, then radio priority levels are mapped to ARP levels,
see Table 1.

Table 1 Radio Priority Levels Mapped to ARP Levels, Default Preemption Vulnerability and Capability for Radio Priority
Levels.

Radio Priority Level ARP Level Default Preemption Vulnerability

and Capability
1 1 Preemption capability and no
preemption vulnerability
2 6 No preemption vulnerability and no
preemption capability
3 11 Preemption vulnerability and no
preemption capability
4 Not applicable Preemption vulnerability and no
preemption capability

The SGSNs that support the function send for an MS the following information in ARP data in message
CREATE-BSS-PFC PDU:

 Priority level 1-14, received priority level 15 means no priority and it is treated as 14, the
lowest.
 Preemption vulnerability, specifies if the established TBF for such MS can be preempted by
another TBF.
  Preemption capability, specifies if the requested TBF by such MS can preempt another
established TBF.

If this function is active with radio priority levels support and the PCU has no available ARP information with
preemption vulnerability and capability but it has radio priority levels available, it uses them and the
preemption vulnerability and capability set according to the Table 1.

If the PCU has no available ARP information for an MS that requests a TBF, it uses the default values; priority
level set to 14, preemption vulnerability and no preemption capability.

TBFs requested by MSs are admitted depending on cell occupancy rate, ARP priority level of requested TBFs,
and ARP priority level of the TBFs established in the cell.

If radio priority levels support is active in the BSC, then in case of congestion, the BSC broadcasts in SI13 or
PSI14, in priority access threshold parameter, information about limited access for MSs due to ongoing
congestion in the cell. MSs having radio priority level lower than the actual priority access threshold
broadcast in the cell, should not try to set up TBFs in this cell.

In case of congestion in a cell, a TBF requested by a preemption capable MS can cause preemption of an
established TBF for a preemption vulnerable MS with lower APR priority level.

Signaling TBFs are always served as the highest priority, that is priority level 1, with preemption capability
and no preemption vulnerability.

To decrease load, during cell congestion, the requests for TBFs from MSs with lower priority are rejected and
the BSC orders to extend the backoff timer in MS for re-sending TBF request.

If the functionality IoT Load Control is activated in the cell then cell congestion levels, calculated by QoS
Admission Control based on cell occupancy rates and ARP information, are used by IoT Load Control cell
congestion detection mechanism, see Reference [2].

2.2.3 Packet Flow Contexts

As shown in Figure 2, one or several Packet Data Protocol (PDP) contexts can be activated between the MS
and the network, each PDP context having a specific quality of service and using a specific Network Service
Access Point Identifier (NSAPI). The PDP context activation may be initiated by the MS or the initiation may
be requested by the network for a specific quality of service using a specific NSAPI.

An MS can have a maximum of 11 PDP contexts active at one time. Each PDP context is associated with an
NSAPI, and each NSAPI at most maps to one primary or secondary PDP Context.

The SGSN can provide the PCU with quality of service information related to ongoing user data transmission.
The information related to one MS is stored in a PFC. Each PFC is identified by a Packet Flow Identifier (PFI),
assigned by the SGSN. The triplet Routing Area Identification (RAI), TLLI, PFI uniquely addresses a PFC. A PFC
is shared by one or more activated PDP contexts with identical or similar negotiated quality of service
profiles. The data transmission related to PDP contexts that share the same PFC constitutes a packet flow.
Figure 2 Quality of Service Addressing Relationships One MS (TLLI), Valid Uplink and Downlink.

The combined Base Station System (BSS) QoS profile for the PDP contexts that share the same packet flow is
called ABQP. It defines the quality of service that must be provided by the PCU for a given packet flow
between the MS and the SGSN. The ABQP consists of a set of parameters. The ABQPs are either negotiated or
predefined.

There are a number of predefined packet flows identified by reserved PFI values. The predefined PFCs are not
negotiated. Other PFCs are negotiated between the PCU and SGSN. The negotiation can be initiated from
either the PCU or SGSN.

The predefined PFCs are: PFI=0 (best-effort), PFI=1 (signaling), PFI=2 (SMS) and PFI=3 (TOM8).

In cases where the PFI is not defined it shall be set to zero and best-effort quality of service will be used.

2.3 Administration of GPRS Quality of Service Function

2.3.1 Quality of Service Admission Control Administration

The function Quality of Service Admission Control with or without radio priority levels support is activated
and deactivated by commands for the whole BSC. The status of the function can be printed.

2.3.2 Quality of Service and Scheduling Administration

2.3.2.1 Administration of GPRS R97 QoS

R97 QoS is administered, by setting the BSC exchange property QOSMAPPING for activation, change, and
deactivation of support for GPRS Quality of Service based on mapped R97 QoS profiles.

R97 QoS attributes are mapped to R99 attributes as shown in Table 2.

Table 2 Mapping of R97 Attributes

R97 Attributes R99 Attributes

Precedence Traffic Class, THP
Peak Bitrate Maximum Bitrate

MBR uplink and downlink attributes are restricted for the cell capability and the MS multislot capability.
MaxPDCH is the maximum number of PDCHs according to the multislot class of the MS. If the multislot class is
not known, the maximum possible number of PDCHs is presumed.

Table 3 MBR According to Combination of MS and Cell Capability (kbps)

MS Multislot Capability Cell Capability MBR DL MBR UL

EGPRS2-A EGPRS2-A 100 * MaxPDCH 80 * MaxPDCH
EGPRS2-A EGPRS 60 * MaxPDCH 60 * MaxPDCH
EGPRS2-A GPRS CS-1 to CS-4 20 * MaxPDCH 12 * MaxPDCH
EGPRS2-A GPRS CS-1 to CS-2 12 * MaxPDCH 12 * MaxPDCH
EGPRS EGPRS2-A 60 * MaxPDCH 60 * MaxPDCH
EGPRS EGPRS 60 * MaxPDCH 60 * MaxPDCH
EGPRS GPRS CS-1 to CS-4 20 * MaxPDCH 12 * MaxPDCH
EGPRS GPRS CS-1 to CS-2 12 * MaxPDCH 12 * MaxPDCH
GPRS EGPRS2-A 20 * MaxPDCH 12 * MaxPDCH
GPRS EGPRS 20 * MaxPDCH 12 * MaxPDCH
GPRS GPRS CS-1 to CS-4 20 * MaxPDCH 12 * MaxPDCH
GPRS GPRS CS-1 to CS-2 12 * MaxPDCH 12 * MaxPDCH

If the T-bit in R97 QoS indicates GPRS Mobility Management and Session Management (GMM/SM) signaling,
PFI=1 is used.

The support for R97 QoS can be activated in two different modes as shown in Table 4

Table 4 Mapping of R97 Attribute “Precedence” Depending on QOSMAPPING

Precedence High Precedence Normal Precedence Low

QOSMAPPING=1 Interactive, THP2 Interactive, THP3 Background
QOSMAPPING=2 Interactive, THP1 Interactive, THP2 Interactive, THP3
2.3.2.2 Activation GPRS R99 QoS Support

A prerequisite for the activation of R99 QoS support is the support for PFM in the SGSN (see Reference [16]).

In order to activate support for R99 QoS, the BSC exchange property PCUQOS shall be used. However, R99
QoS support remains deactivated if SGSN does not support PFM, but the R99 QoS support will be activated as
soon as the SGSN also supports PFM (see Reference [16]).
When PCUQOS is changed the Gb interface will be notified and will perform a BSSGP Virtual Connection (BVC)
reset procedure to query the R99 QoS support in the SGSN. The status is then relayed back to the function
GPRS Quality of Service.

When the R99 QoS function is activated:

 PFM, procedures (see Section 2.4) will be supported.

 The function GPRS System Information and Access Control (see Reference [7]) is requested to
broadcast that PFM is supported in all cells with GPRS support.
2.3.2.3 Deactivation of GPRS R99 QoS Support

To deactivate R99 QoS, the BSC exchange property PCUQOS shall be used.

When the GPRS R99 QoS is deactivated:

 PFM will not be supported.

 The function GPRS System Information and Access Control (see Reference [7]) will be notified
that PFM is not supported.
2.3.2.4 Synopsis of R97 QoS and R99 QoS

Table 5 shows an overview of Quality of Service.

Table 5 Support for R97 QoS and R99 QoS Overview

R99 QoS R97 QoS MS R97 or Undefined MS R99 or Later

(PCUQOS) (QOSMAPPING)
0 = deactivated 0 = deactivated QoS based on TBF reservation QoS based on TBF reservation
1 = activated R97 profile mapped to THP2, R97 profile mapped to THP2,
THP3, Background THP3, Background
(See Table 4)
2 = activated R97 profile mapped to THP1, R97 profile mapped to THP1,
THP2, THP3 THP2, THP3
(See Table 4)
1 = activated 0 = deactivated Best-effort ABQP R99 QoS
1 = activated R97 profile mapped to THP2, R99 QoS
THP3, Background
(See Table 4)
2 = activated R97 profile mapped to THP1, R99 QoS
THP2, THP3
(See Table 4)

When both R97 QoS and R99 QoS are deactivated the function GPRS Packet Transfer (see Reference [6]) is
informed to schedule the TBFs according to the number of reserved PDCHs.

2.4 Packet Flow Management

2.4.1 General
The packet flow management is handled by this function and uses the PFM service primitives provided by the
Gb interface. There are primitives for downloading, creating, modifying, and deleting PFCs. PFM procedures
for GPRS Packet Switched Handover are described in Reference [5] and the related PFC handling in Section
2.6.

2.4.2 Create BSS PFC Procedure

As shown in Figure 3, the SGSN may at any time request a creation of a BSS packet flow context, for example
due to the activation of a PDP context or when an MS moves to a new routing area.

Figure 3 Create BSS PFC Procedure, Initiated by the SGSN

On receiving a request to transmit an uplink or downlink Logical Link Control (LLC) Protocol Data Unit (PDU)
for which no BSS packet flow context exists in the PCU, the PCU will request the download of the BSS packet
flow context from the SGSN. This is shown in Figure 4.

Figure 4 Create BSS PFC Procedure, Quality of Service Negotiation Between PCU and SGSN.

1. The PCU receives a request to transfer an uplink or downlink user data LLC PDU for which it
currently does not have a BSS packet flow context. In the uplink case, TLLI and PFI are received
from the MS as defined in Reference [16]. In the downlink case, TLLI and PFI are received from
the SGSN as defined in Reference [15]. If the PFI is not among the predefined then the GPRS
Quality of Service function request the Gb interface to send a 48.018 DOWNLOAD-BSS-PFC (RAI,
TLLI, PFI) message to the SGSN. Until the GPRS Quality of Service function receives a 48.018
CREATE-BSS-PFC the default ABQP or ARP is used (see Section 2.5.1). If the MS does not
support the PFC feature (R99) and the PFI is undefined then the PFI is set to 0 giving a best-
effort service.
 2. The SGSN sends a 48.018 CREATE-BSS-PFC (IMSI, TLLI, PFI, ABQP Requested, BSS Packet Flow
Timer, ARP). The SGSN derives ABQP Requested from the QoS profile negotiated for the PDP
contexts.

The traffic class Conversational will be restricted according to the BSC Exchange Property QOSCONVPRIO.
GPRS Quality of Service creates a PFC and stores the negotiated (restricted) ABQP. The PCU returns a 48.018
CREATE-BSS-PFC-ACK (TLLI, PFI, negotiated ABQP) message to the SGSN.

The traffic class Streaming will be restricted and stored according to the BSC Exchange Property
QOSSTREAMPRIO and a 48.018 CREATE-BSS-PFC-ACK message is returned to the SGSN. If QOSSTREAMPRIO
indicates 'BLOCKED' a PFC is not created and the PCU returns a 48.018 CREATE-BSS-PFC-NACK message to
the SGSN.

The download procedure is time supervised with timer T6. After four successive download attempts which
fail with T6 time-out the download is abandoned and the default ABQP is used.

2.4.3 BSS Packet Flow Context Modification Procedures

2.4.3.1 SGSN-Initiated BSS Packet Flow Context Modification Procedure

As shown in Figure 5, the SGSN may at any time request a modification of the contents of an existing BSS
packet flow context, for example due to the activation, modification, or deactivation of a PDP context. A
48.018 CREATE-BSS-PFC message is used in this case, and GPRS Quality of Service will instead of creating a
BSS packet flow context overwrite the existing parameters with the modified parameters subject to
restriction with the same criteria as described above in Section 2.4.2.

Figure 5 Modify BSS PFC Procedure Initiated by the SGSN.

2.4.3.2 PCU-Initiated BSS Packet Flow Context Modification Procedure

GPRS Quality of Service will request a modification of the contents of an existing BSS packet flow context:

 When the MS moves to a cell, within the same routing area, with different capabilities.
 When the capabilities of the MS become known and this results in a limitation compared to the
negotiated PFC.
The BSS PFC modify procedure is used in these cases. GPRS Quality of Service will request the Gb interface to
send 48.018 MODIFY-BSS-PFC to SGSN and overwrite the existing parameters with the modified parameters
when receiving a 48.018 MODIFY-BSS-PFC-ACK in response. This is shown in Figure 6.

Figure 6 Modify BSS PFC Procedure, Initiated By GPRS Quality of Service (PCU).

The modify procedure is time supervised with timer T8. After four successive download attempts which fail
with T8 time-out the modify procedure is abandoned and the previously stored ABQP is used.

2.4.3.3 SGSN Ordered BSS Packet Flow Context Delete

GPRS Quality of Service will delete the PFC when a 48.018 DELETE-BSS-PFC is received from the SGSN. This is
shown in Figure 7.

If another procedure is ongoing, the DELETE-BSS-PFC takes precedence and the other procedure is aborted.

A new Download BSS PFC procedure will be initiated if the PFI for the deleted procedure appears again.

Figure 7 Delete BSS PFC Procedure.

2.5 ABQP Handling

2.5.1 ABQP Content and Storage

Each MS may have several PFCs associated with it, depending on the number of active PDP contexts and the
QoS profile of each PDP context. Each PFC is identified by the PFI which is assigned by the SGSN. For each MS,
GPRS Quality of Service will store the ABQPs for the PFCs of that MS and the ABQP may then be addressed by
the {RAI,TLLI,PFI}.
Note that the ABQP contains all the attributes as defined in Reference [13] but will only use the Traffic Class,
THP, MBR uplink and downlink. Therefore the other attributes are not mentioned any further in this
document.

The THP determines the scheduling weight for an interactive PFC. The THP can have the values THP1, THP2,
and THP3. THP3 is the lowest priority. THP1 cannot have lower priority than THP2 or THP3. THP2 cannot
have lower priority than THP3.

Table 6 Example ABQP for PFI=17

Traffic Class Interactive

THP 2
MBR DL 240 kbps
MBR UL 24 kbps
Table 7 Example ABQP for PFI=43

Traffic Class Background

THP -
MBR DL 240 kbps
MBR UL 64 kbps
2.5.2 Predefined ABQPs

The predefined ABQPs are stored and ready to be used for the predefined PFCs.

Table 8 Best-effort ABQP, PFI=0 or Undefined PFI

Traffic Class Background

THP -
MBR DL 480 kbps
MBR UL 96 kbps

PFI=1 is reserved for indication of GMM/SM signaling. There is no ABQP nor a Traffic Class associated with
PFI=1. See Section 2.7.

There is a Separate ABQP for PFI=2 which is Used for SMS.

Table 9 ABQP for SMS, PFI=2

Traffic Class Interactive

THP 3
MBR DL 480 kbps
MBR UL 96 kbps
Table 10 ABQP for TOM Protocol (TOM8), PFI=3

Traffic Class Interactive

THP 3
MBR DL 480 kbps
MBR UL 96 kbps

The default ABQP is used when a PFC DOWNLOAD has been requested until an ABQP is received with a PFC
CREATE message from SGSN.

Table 11 Default ABQP, any PFI Except Predefined PFIs

Traffic Class Interactive

THP 1
MBR DL 480 kbps
MBR UL 96 kbps

GPRS Quality of Service will store the non predefined ABQPs for a PFC until either the Packet Flow Timer
(PFT) per ABQP expires or the SGSN sends a delete ABQP message. The PFT is assigned by the SGSN at ABQP
creation. In the case where the assigned value is set to infinite time then GPRS Quality of Service will limit the
PFT value to one hour. The ABQP can also be deleted due to memory congestion.

2.6 Quality of Service for GPRS Packet Switched Handover

2.6.1 General

GPRS Packet Switched Handover (see Reference [5]) handles the PFM packet switched handover procedures
and directs the PFC related parts to this function. GPRS Packet Switched Handover requests a list of active
PFCs in the source cell. The list of PFCs is transferred to the target cell to be used for setup. In the process of
setting up a TBF in each direction in the target cell the PFCs which explicitly put resource demands will either
succeed or fail to be set up. GPRS Packet Switched Handover will request the list of PFCs that were set up in
the target cell.

2.6.2 List of Active PFCs in Source Cell

GPRS Quality of Service assembles the list of all PFCs in the source cell for a certain MS at request from the
function GPRS Packet Switched Handover.

2.6.3 List of PFCs to Be Set Up in Target Cell

Each PFC in the list is stored with its ABQP attributes and the highest priority PFC will be indicated to GPRS
Packet Switched Handover. The PFC with ABQP attributes is subject to the same handling as described in
Section 2.5 with the following exception: ABQP attributes are not negotiated during an ongoing packet
switched handover. Instead a modify BSS PFC procedure is initiated for each PFC setup in the target cell when
the packet switched handover has been completed.

2.6.4 List of PFCs That Were Set Up in Target Cell

List of setup PFCs that were set up is sent to GPRS Packet Switched Handover on request. PFCs that could not
be given required resources will not be included in the list. The BSC Exchange Property
STREAMABQPFULFILLED specifies if a Streaming PFC is set up even if ABQP requirements cannot be fulfilled.
2.7 Quality of Service Evaluation per TBF
GPRS Quality of Service evaluates and distributes the quality of service per TBF. The QoS priority and weight
evaluation for a TBF are based on determining which packet flows are active in the PCU. For every TBF GPRS
Channel Utilization (see Reference [2]) reserves PDCHs with regard to QoS priority and weight.

2.7.1 R99 QoS and R97 QoS

The quality of service evaluation uses the BSC exchange properties and the related ABQPs. The QoS priority is
an absolute priority. Within the priority Interactive the relative priority is given by the weight determined by
the THP. For other traffic classes the weight is set to “1” for a PFC.

RLC Protocol Handling, sub-function of the function GPRS Packet Transfer (see Reference [6]), prioritizes
which DL LLC-PDUs to be segmented next, according to which Traffic Class they belong to. The MAC Protocol
Handling, sub-function of the function GPRS Packet Transfer (see Reference [6]), schedules downlink and
uplink data according to the QoS priority and weight of the TBF. GPRS Quality of Service extracts the quality
of service characteristics per TBF based on the active PFCs in the TBF.

The following quality of service priorities exist:

 GMM/SM priority (highest priority)

 Interactive priority
 Background priority (lowest priority)

When a number of TPFs, in one or several TBFs, are contending for a resource then the TPFs with the highest
priority will use the resource. Lower priority TPFs await for all higher priority TPFs to be completed. Within
each priority the TBF has a relative priority according to its weight. The weight controls how often a TBF is
scheduled relative to the other TBFs with the same priority sharing the same PDCHs.

GPRS Quality of Service updates the GPRS Packet Transfer (see Reference [6]) and GPRS Channel Utilization
(see Reference [2]) functions whenever there is a change of QoS priority or weight for a TBF.

The quality of service for a TBF is summarized by the combined priority and combined weight of the
associated PFCs. The TBF will potentially carry data belonging to different PFCs during the lifetime of the
TBF.

 Downlink

Examine all PFCs related to the TBF. Set the TBF priority to the priority of the highest priority
PFC which has at least one downlink TPF. The TBF weight is the sum of weights of all PFCs of
the TBF priority which have downlink TPFs.

 Uplink

The priority and weight is set to the priority and weight of the PFC active uplink.

2.7.2 Quality of Service Admission Control

The following quality of service priorities exist:

  GMM/SM priority (highest priority)
 Interactive priority

The weight is given by the ARP level. There are 5 groups for ARP levels and all ARP levels in the group are
considered as equal when it comes to weight in reservation and scheduling:

 ARP 1-3
 ARP 4-6
 ARP 7-9
 ARP 10-12
 ARP 13-15

Signaling is scheduled with highest priority and its ARP value will not have an impact on the scheduling.

2.8 Examples of Quality of Service Evaluation and Weight

Calculation
2.8.1 Example of Quality of Service Evaluation for an Uplink TBF

In this example shown in Figure 8, there are two PFCs active during the TBF. There are two TPFs. All the PFCs
are negotiated before the TBF. There are three ABQPs accessed for the evaluation of QoS priority and weight.
The default ABQP is used until the PFI value is set when contention resolution is complete. The examples of
ABQP for PFI=17 (Interactive, THP2, weight=2) and PFI=43 (Background) given previously are used in this
example also. The BSC exchange properties values are the same as in the downlink example.

Figure 8 Uplink TBF QoS Priority and Weight.

3 Operational Conditions
3.1 External Conditions
To use this function, the optional feature GPRS must be available and activated in the BSC.

To use this function either the optional feature GPRS/EGPRS Quality of Service and Scheduling or the optional
feature Quality of Service Admission Control must be available and activated in the BSC.

This function works efficiently if all SGSNs connected to the BSC support the function.

This function with radio priority levels support works only if all SGSNs connected to the BSC support the
function Quality of Service Admission Control with radio priority levels support.

To use Packet Switched Handover the optional feature GPRS Packet Switched Handover must be available and
activated in the BSC.

In order to use IoT Load Control cell congestion detection mechanism, the optional feature IoT Load Control
must be available and activated in the cell.

The availability of optional features depends on commercial agreements.

3.2 Application Parameters

The following BSC Exchange Properties can be changed during operation by the Administration of BSC
Exchange Properties (Reference [1]) function:

PCUQOS Specifies if support for 3GPP TS 48.018 PFM in the PCU and support for
GPRS Quality of Service based on R99 QoS profiles is activated or not.

QOSCONVPRIO Specifies on which THP level the service class Conversational will be
handled.

QOSMAPPING Specifies the activation, change and deactivation of support for GPRS Quality
of Service based on mapped R97 QoS profiles.

QOSTHP1 Specifies the THP weight for THP1 PFCs.

QOSTHP2 Specifies the THP weight for THP2 PFCs.

3.3 Commands
The function GPRS Quality of Service includes the following commands:

 RFGQE

This command is used to deactivate function Quality of Service in a BSC.

 RFGQI

This command is used to activate function Quality of Service in a BSC.

  RFGQP

This command is used to print the status of the function GPRS Quality of Service for a BSC.

3.4 Printouts
The function GPRS Quality of Service includes the following answer printout:

 BSC GPRS QUALITY OF SERVICE DATA

The printout lists Quality of Service data.

3.5 Capabilities
The timer T6 duration is 2 seconds.

The timer T8 duration is 2 seconds.

4 Concepts
16/32 Quadrature Amplitude A modulation method where the phase of the carrier is shifted through 16 or
Modulation (16/32-QAM) 32 phase differences. Each symbol (carrier phase position) represents 4 data
bits for 16-QAM and 5 data bits for 32-QAM.

8 Phase Shift Keying (8-PSK) A modulation method where the phase of the carrier is shifted through 8 phase
differences. Each symbol (carrier phase position) represents 3 data bits.

active PFC A PFC is active when data is ready to be scheduled or is expected within a
short time.

Aggregate BSS QoS Profile The negotiated or predefined QoS profile for a PFC. It is used to determine
(ABQP) priority and weight at scheduling and PDCH reservation.

background class Used by applications without any requirements on bitrate or delay. The users
will get service when users of other traffic classes do not request it. Typical
applications are file transfers or email.

Basic GPRS PDCH (B-PDCH) An LCH used for transfer of GPRS (CS-1 and CS-2) packet data and control
signaling. A B-PDCH uses a 16 kbps Abis link.

best effort ABQP The best effort ABQP is used if the PFI indicates best-effort, that is, PFI=0, or
if the PFI is undefined.

contention resolution The contention resolution procedure is used to uniquely identify MSs during
MS originated access procedures. The procedure is completed in the network
at reception of the MS TLLI and PFI.

conversational class Used by applications having strong absolute requirements on bitrate or delay,
or both. A typical application is voice.
default ABQP The default ABQP is used when a download PFC request has been sent to the
SGSN but the ABQP for the PFC is yet unknown.

EGPRS PDCH (E-PDCH) An LCH used for the transfer of EGPRS (MCS-1 to MCS-9) and GPRS (CS-1
to CS-4) packet data and control signaling. An E-PDCH uses a 64 kbps Abis
link.

EGPRS Phase 2, Level A In the downlink direction, EGPRS2-A enables higher data rates through use of
(EGPRS2-A) additional coding schemes, DAS-5 to DAS-12, and additional modulations,
16-QAM and 32-QAM. In the uplink direction, EGPRS2-A enables higher
data rates through use of additional coding schemes, UAS-7 to UAS-11, and
additional modulation, 16-QAM.

Enhanced Data for Global An add-on to GSM. It uses different modulation (16/32-QAM, 8-PSK, or
Evolution (EDGE) GMSK) and coding schemes. This allows greater user data throughput and
thus provides greater spectral efficiency.

Enhanced GPRS (EGPRS) An enhanced GPRS service including support for EDGE, link adaptation and
incremental redundancy.

Gb interface The interface between the SGSN and the PCU. Each Gb link forms a
wideband connection, which is terminated in the PCU via different
transmission types.

GPRS PDCH (G-PDCH) An LCH used for transfer of GPRS (CS-1 to CS-4) packet data and control
signaling. A G-PDCH uses a 64 kbps Abis link.

maximum bitrate An attribute in the QoS profile in the PDP context (which is between MS and
SGSN) and the ABQP in the PFC (which is between the BSS and SGSN).

The maximum bitrate is specified separately for uplink and downlink

direction.

packet flow The data transmission related to PDP contexts that share the same packet flow
context, constitute one packet flow to one MS.

Packet Flow Context (PFC) A PFC is shared by one or more activated PDP contexts with identical or
similar negotiated QoS profiles for one MS.

PDCH Capability (PDCHCAP) PDCHCAP specifies the CS capability (for GPRS), the MCS capability (for
EGPRS), the DAS and the UAS capability (for EGPRS2-A) of a PDCH. The
capabilities are:
 B-PDCH, supports GPRS CS-1 and CS-2.
 G-PDCH, supports GPRS CS-1 to CS-4.
 E-PDCH, supports EGPRS MCS-1 to MCS-9 and GPRS CS-1 to CS-
4.
 RTTI PDCH, supports EGPRS MCS-0 to MCS-9 and GPRS CS-1 to
CS-4.
 RTTI and IAN PDCH, supports EGPRS MCS-0 to MCS-9 and
GPRS CS-1 to CS-4.
  E2A PDCH, supports EGPRS2-A (DAS-5 to DAS-12 DL and UAS-
7 to UAS-11 UL), EGPRS MCS-1 to MCS-9 and GPRS CS-1 to CS-
4.

PDP context One PDP context contains one QoS profile.

peak bitrate The peak bitrate is the R97 equivalent to the R99 maximum bitrate. peak
bitrate is part of the R97 QoS Profile IE as defined in 3GPP TS 48.018.

precedence Priority class. Precedence is part of the R97 QoS Profile IE as defined in
3GPP TS 48.018.

QoS priority The QoS priority controls how to share resources, queue data, and schedule
concurrent data flows. There are three QoS priorities:
 GMM/SM signaling (highest priority)
 Interactive
 Background (lowest priority)

QoS weight The QoS weight controls the quotient of scheduling a TBF will get relative to
other TBFs, with the same QoS priority and sharing the same PDCHs.

R97 QoS QoS based on R97 QoS Profiles that are mapped to R99 QoS Profiles.

R99 QoS QoS based on R99 QoS Profiles that are negotiated by means of PFM.

RLC data block An RLC data block is the part of an RLC/MAC block carrying user data or
upper layers' signaling data.

TBF mode Specifies whether a TBF is using GPRS, EGPRS or extended coverage. In the
PCU, there is a requested TBF mode which may be assigned values GPRS,
EGPRS or extended coverage and a response called established TBF mode
which may be assigned values EGPRS, restricted EGPRS, GPRS, basic
GPRS, or extended coverage. Restricted EGPRS may occur due to parameter
PSKONBCCH and limits the modulation to GMSK. Basic GPRS may handle
CS-1 and CS-2.

Temporary Block Flow (TBF) A logical connection between the MS and the PCU. A TBF is used for either
uplink or downlink transfer of GPRS packet data. The actual transfer is made
on PDCHs.

Temporary Packet Flow (TPF) A TPF for a PFC exists when there is data available to schedule for that PFC.

traffic class UMTS/GPRS bearer class 3GPP TS 23.107.

transfer delay The transfer delay, in the ABQP, specifies the delay tolerated by the
application. See 3GPP TS 23.107.
Glossary
16/32 QAM
16/32 Quadrature Amplitude Modulation

8-PSK
8 Phase Shift Keying

ABQP
Aggregate BSS QoS Profile

ARP
Allocation Retention Priority

BSC
Base Station Controller

BSS
Base Station System

BSSGP
Base Station System GPRS Protocol

BVC
BSSGP Virtual Connection

DAS
EGPRS2 Downlink Level A MCS

DL
Downlink

EDGE
Enhanced Data Rates for Global Evolution

EGPRS
Enhanced GPRS

EGPRS2-A
EGPRS Phase 2, Level A

Gb
Interface between SGSN and PCU

GMM/SM
GPRS Mobility Management and Session Management

GPRS
General Packet Radio Service

HLR
Home Location Register

IoT
Internet of Things

IP
Internet Protocol

LLC
Logical Link Control

MAC
Media Access Control

MBR
Maximum Bitrate

MS
Mobile Station

NSAPI
Network Service Access Point Identifier

PCU
Packet Control Unit

PDCH
Packet Data Channel

PDP
Packet Data Protocol

PDU
Protocol Data Unit

PFC
Packet Flow Context

PFI
Packet Flow Identifier

PFM
Packet Flow Management

PFT
Packet Flow Timer
QoS
Quality of Service

R97
Release 97 of the 3GPP Standard

R99
Release 99 of the 3GPP Standard

RAI
Routing Area Identification

RLC
Radio Link Control

SGSN
Serving GPRS Support Node

SI
System Information

SMS
Short Message Service

TBF
Temporary Block Flow

THP
Traffic Handling Priority

TLLI
Temporary Logical Link Identifier

TOM
Tunneling of Messages

TPF
Temporary Packet Flow

UAS
EGPRS2 Uplink Level A MCS

UL
Uplink

Reference List
Ericsson Documents
[1] ADMINISTRATION OF BSC EXCHANGE PROPERTIES, FUNCTION SPECIFICATION
[2] GPRS Channel Utilization, FUNCTION SPECIFICATION
[3] GPRS, Gb over FR, FUNCTION SPECIFICATION
[4] GPRS, Gb over IP, FUNCTION SPECIFICATION
[5] GPRS Packet Switched Handover, FUNCTION SPECIFICATION
[6] GPRS Packet Transfer, FUNCTION SPECIFICATION
[7] GPRS System Information and Access Control, FUNCTION SPECIFICATION
[8] BSC GPRS QUALITY OF SERVICE DATA, PRINTOUT DESCRIPTION
[9] RFGQE, COMMAND DESCRIPTION
[10] RFGQI, COMMAND DESCRIPTION
[11] RFGQP, COMMAND DESCRIPTION
Standards
[12] 3GPP TS 23.060, GSM SPECIFICATION
[13] 3GPP TS 23.107, GSM SPECIFICATION
[14] 3GPP TS 24.008, GSM SPECIFICATION
[15] 3GPP TS 44.060, GSM SPECIFICATION
[16] 3GPP TS 48.018, GSM SPECIFICATION
Legal | © Ericsson AB 2006-2010, 2012-2014, 2016, 2017