GPRSEGPRS QoS

GBSS12.0
Feature Parameter Description

Issue 01

Date 2010-06-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2011. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.

Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: [email protected]
 GSM BSS
GPRS/EGPRS QoS Contents

Contents
1 Introduction ................................................................................................................................1-1
1.1 Scope ............................................................................................................................................ 1-1
1.2 Intended Audience ........................................................................................................................ 1-1
1.3 Change History.............................................................................................................................. 1-1

2 Overview .....................................................................................................................................2-1
3 Technical Description ..............................................................................................................3-1
3.1 PFM Procedures ........................................................................................................................... 3-1
3.1.1 PFC Establishment Procedure ............................................................................................. 3-1
3.1.2 PFC Modification Procedure ................................................................................................ 3-2
3.1.3 PFC Deletion Procedure ...................................................................................................... 3-4
3.2 Mapping From R97/R98 QoS Attributes to R99 QoS Attributes ................................................... 3-4
3.3 QoS based on service type ........................................................................................................... 3-7
3.4 QoS of Conversational Services ................................................................................................... 3-7
3.5 QoS of PoC Services .................................................................................................................... 3-8
3.6 QoS of Interactive, Background, and BE Services ....................................................................... 3-9
3.7 QoS of Streaming Services ......................................................................................................... 3-10
3.7.1 GBR Assurance .................................................................................................................. 3-10
3.7.2 Resource Preemption ..........................................................................................................3-11

4 Parameters .................................................................................................................................4-1
5 Counters ......................................................................................................................................5-1
6 Glossary ......................................................................................................................................6-1
7 Reference Documents .............................................................................................................7-1

Huawei Proprietary and Confidential

Issue 01 (2010-06-30) ii
Copyright © Huawei Technologies Co., Ltd.
 GSM BSS
GPRS/EGPRS QoS 1 Introduction

1 Introduction
1.1 Scope
This document describes PFM procedures, QoS of streaming services, QoS of conversational services,
and QoS of PoC service in the GPRS/EGPRS QoS feature.

1.2 Intended Audience

It is assumed that users of this document are familiar with GPRS basics and have a working knowledge
of GPRS telecommunication.
This document is intended for:
 Personnel working on Huawei GPRS products or systems
 System operators who need a general understanding of this feature

1.3 Change History

The change history provides information on the changes in different document versions.
There are two types of changes, which are defined as follows:
 Feature change
Feature change refers to the change in the GPRS/EGPRS QoS feature of a specific product version.
 Editorial change
Editorial change refers to the change in wording or the addition of the information that was not
described in the earlier version.

Document Issues
The document issues are as follows:
 01 (2010-06-30)
 Draft (2010-03-30)

01 (2010-06-30)
This is the first release of GBSS12.0.
Compared with issue Draft (2010-03-30) of GBSS12.0, issue 01 (2010-06-30) of GBSS12.0 incorporates
the changes described in the following table.

Change Type Change Description Parameter Change

Feature None. None
change
Editorial Parameters are presented in the None
change form of Parameter ID instead of
Parameter Name.

Draft (2010-03-30)
This is the draft release of GBSS12.0.

Huawei Proprietary and Confidential

Issue 01 (2010-06-30) 1-1
Copyright © Huawei Technologies Co., Ltd.
 GSM BSS
GPRS/EGPRS QoS 2 Overview

2 Overview
GPRS/EGPRS QoS refers to the QoS requirements of GPRS/EGPRS services in the GSM EDGE Radio
Access Network (GERAN). The QoS requirements are defined by QoS attributes, including the traffic
class, transfer delay, maximum bit rate (MBR), guaranteed bit rate (GBR), traffic handling priority (THP),
allocation/retention priority (ARP), and reliability in Release 99 (R99).
The GPRS/EGPRS QoS feature ensures that the QoS requirements of the GPRS/EGPRS services are
met, that is, the requirements of transfer delay, bandwidth, and reliability of the GPRS/EGPRS services
are met. From the perspective of users, guaranteeing the QoS requirements means improving the
service experience. From the perspective of telecom operators, the guaranteed QoS brings about the
following benefits:
 Telecom operators can customize the policies of radio resource allocation based on the QoS attributes.
These policies ensure that high-priority users occupy high bandwidth, experience high data rate, and
thus enjoy better QoS. Low-priority users, however, can share limited bandwidth and QoS.
 Sufficient bandwidth is guaranteed for the streaming services. When radio resources are insufficient,
the bandwidth requirements of high-priority users are preferentially met and thus their service
experience is improved.
 The delay requirements of conversational services and PoC services are met. Better service
experience and diversified value-added services are provided to attract more high-end users.
 Telecom operators can formulate flexible charging policies.
In R99 QoS, there are four traffic classes: conversational class, streaming class, interactive class, and
background class. These traffic classes are identified by their delay sensitive levels. The conversational
class is most sensitive to delay whereas the background class is most insensitive to delay.
 Typical conversational services are the services for real-time conversations, such as voice over IP
(VoIP), Gaming, video phone, and video conferencing tools. The characteristics of conversational
services are as follows: The transfer delay should be low; the time sequence and delay variation
between information entities (for example, packets) of the stream should be preserved.
 Typical streaming services are the real-time video stream and real-time audio stream. The
characteristics of streaming services are as follows: The time sequence and delay variation between
information entities (for example, packets) of the stream should be preserved; streaming class does
not have strict requirements on transfer delay.
 The interactive service is a classical data communication scheme. Typical interactive services include
web browsing, database retrieval, and server access. One of the characteristics of interactive services
is that a timely response to the request is required. Therefore, the round-trip delay time is one of the
key attributes. Another characteristic is that the content of the packets should be transferred at a low
bit error rate.
 The background service is another classical data communication scheme. Typical background
services include file downloading, background delivery of email, short message service (SMS), and
reception of measurement records. The characteristics of background services are as follows: The
traffic is insensitive to transfer delay; the content of the packets should be transferred at a low bit error
rate.
The Push to talk over Cellular (PoC) service belongs to the streaming class. It is a type of group call
service implemented on the GSM network. The PoC service adopts the packet switching technology and
it is carried on the GPRS/EGPRS networks. The major functional entities of the PoC service run on the
PoC server in the core network (CN). The signaling and speech signals of the PoC service are carried on
the GPRS/EGPRS networks in the form of packets and are transparently transferred from the BSS to the
CN. In contrast to the packet service, the speech signals of the PoC service require low transfer delay. If
the transfer delay is high, user experience is adversely affected.

Huawei Proprietary and Confidential

Issue 01 (2010-06-30) 2-1
Copyright © Huawei Technologies Co., Ltd.
 GSM BSS
GPRS/EGPRS QoS 2 Overview

Different traffic classes have different QoS requirements, which are defined by QoS attributes. The QoS
attributes are contained in Packet Flow Context (PFC). The BSC negotiates the QoS attributes with the
SGSN by performing the Packet Flow Management (PFM) procedures. If the MS or the SGSN does not
support the PFM procedures, the BSC should map R97/R98 QoS attributes to R99 QoS attributes to
support the handling of R97/R98 QoS attributes.
In Huawei GPRS/EGPRS QoS feature, the QoS of the following traffic is supported: streaming class,
interactive class, background class, conversational class, BE service, and PoC service.
 In the case of interactive class, background class, and BE service, the BSC configures the user priority
weight according to the traffic class, ARP, and THP of the QoS attributes. Then, the BSC allocates
radio blocks to users based on the user priority weight. High-priority users are allocated more radio
resources and thus the available radio bandwidth is high. In Huawei GPRS/EGPRS QoS feature, best
effort (BE) service refers to the service whose QoS attributes are not obtained from the BSC or the
service whose traffic class is unknown. The radio resource allocation and scheduling of this type of
service are performed on the basis of the best effort policy.
 In the case of streaming class, the BSC allocates radio blocks according to the GBR of the QoS
attributes and ensures that the streaming users have sufficient bandwidth. In addition, the BSC
supports the preemption of streaming resources. When radio resources are insufficient, high-priority
streaming services can preempt the radio blocks of low-priority streaming services. This ensures that
high-priority services can use radio resources preferentially.
 In the case of conversational class, if the MS supports reduced latency, the BSC allocates a PDCH
pair in Reduced Transmission Time Interval (RTTI) configuration to the conversational service and
activates the Fast Ack/Nack Reporting (FANR). Thus, the transfer delay is minimized.
 The PoC service belongs to the real-time packet services and it has strict requirements on bandwidth
and transfer delay. The bandwidth requirement of the PoC service is guaranteed by the GBR
mechanism of streaming class. To guarantee the low transfer delay requirement of the PoC service,
the BSC takes several measures to reduce latency, such as preferentially scheduling the PoC service,
using a low-rate coding scheme, and using the balanced uplink and downlink channel allocation policy.

Huawei Proprietary and Confidential

Issue 01 (2010-06-30) 2-2
Copyright © Huawei Technologies Co., Ltd.
 GSM BSS
GPRS/EGPRS QoS 3 Technical Description

3 Technical Description
3.1 PFM Procedures
PFM procedures, which are used for PFC management, consist of the PFC establishment procedure,
PFC modification procedure, and PFC deletion procedure. The PFM procedures are introduced in R99
QoS. The BSC negotiates the QoS attributes with the SGSN by performing the PFM procedures and
then stores the negotiated QoS attributes in the PFC.
The BSC supports the PFC function only when both GBRQOS and PFCSUP are set to Yes. The PFC
Feature Mode information element in the system information indicates whether the network side
supports PFC.

3.1.1 PFC Establishment Procedure

The PFC establishment procedure is used to establish the PFC for an MS and to specify the QoS
attributes for the uplink and downlink data transfer of the MS. The PFC establishment procedure can be
initiated by the BSC or the SGSN.

PFC Establishment Procedure Initiated by the BSC

Figure 3-1 shows the PFC establishment procedure initiated by the BSC.
Figure 3-1 PFC establishment procedure initiated by the BSC

MS BSC SGSN

UPLINK/DOWNLINK LLC PDU TRANSFER

DOWNLOAD BSS PFC

CREATE BSS PFC

CREATE BSS PFC ACK/NACK

1. If the uplink or downlink LLC PDUs transmitted between the MS and the SGSN contain a PFI but the
PFC corresponding to the PFI does not exist in the BSC, the BSC sends the SGSN a Download BSS
PFC message to request the establishment of the PFC. Before the PFC is established, the BSC
transmits uplink and downlink LLC PDUs according to the QoS attributes of BE services. If the BSC
does not receive the PFI, it does not send the Download BSS PFC message to the SGSN. In this
case, the transmission of uplink and downlink LLC PDUs is based on the QoS attributes of BE
services.

The QoS attributes of BE services are the R99 QoS attributes that are mapped from the QoS Profile carried in the DL
Unitdata message. For details, see3.2 Mapping From R97/R98 QoS Attributes to R99 QoS Attributes.

Huawei Proprietary and Confidential

Issue 01 (2010-06-30) 3-1
Copyright © Huawei Technologies Co., Ltd.
 GSM BSS
GPRS/EGPRS QoS 3 Technical Description

2. After receiving the Download BSS PFC message, the SGSN sends the BSC a Create BSS PFC
message, requesting the BSC to establish a PFC. The Create BSS PFC message contains the
ABQP, ARP, PFI, and PFT.
3. After receiving the Create BSS PFC message, the BSC creates a PFC corresponding to the PFI and
stores the ABQP, ARP, PFI, and PFT in the PFC. If the BSC successfully creates a PFC, it sends a
Create BSS PFC ACK message to the SGSN. The Create BSS PFC ACK message contains the
ABQP adjusted in the BSC. If the BSC fails to create a PFC, it sends a Create BSS PFC NACK
message to the SGSN.

PFC Establishment Procedure Initiated by the SGSN

Figure 3-2 shows the PFC establishment procedure initiated by the SGSN.
Figure 3-2 PFC establishment procedure initiated by the SGSN

MS BSC SGSN

ACTIVATE PDP CONTEXT REQUEST

CREATE BSS PFC

CREATE BSS PFC ACK/NACK

ACTIVATE PDP CONTEXT ACCEPT

After receiving the PDP context activation request from an MS, the SGSN sends the BSC a Create BSS
PFC message, requesting the BSC to establish a PFC. For details of the remaining procedure, see PFC
Establishment Procedure Initiated by the BSC.

3.1.2 PFC Modification Procedure

The PFC modification procedure is used to modify the QoS attributes in a PFC. It can be initiated by the
BSC or the SGSN.

PFC Modification Procedure Initiated by the BSC

Figure 3-3 shows the PFC modification procedure initiated by the BSC.

Huawei Proprietary and Confidential

Issue 01 (2010-06-30) 3-2
Copyright © Huawei Technologies Co., Ltd.
 GSM BSS
GPRS/EGPRS QoS 3 Technical Description

Figure 3-3 PFC modification procedure initiated by the BSC

BSC SGSN

MODIFY BSS PFC

MODIFY BSS PFC ACK

1. When the QoS requirements are not fulfilled because the usage of radio resources changes, for
example, when the available radio blocks are insufficient and thus the GBR should be decreased, the
BSC should send the SGSN a Modify BSS PFC message, requesting the SGSN to modify the ABQP.
The Modify BSS PFC message contains the Aggregate BSS QoS Profile (ABQP) that is modified in
the BSC. ABQP contains the QoS attributes of R97/R98 and R99.
2. After receiving the Modify BSS PFC message, the SGSN sends the BSC a Modify BSS PFC ACK
message, containing the ABQP acceptable to the SGSN. If the SGSN accepts the ABQP modified by
the BSC, the Modify BSS PFC ACK message contains the modified ABQP. If the SGSN does not
accept the ABQP modified by the BSC, the Modify BSS PFC ACK message contains the old ABQP.
3. After receiving the Modify BSS PFC ACK message, the BSC compares the ABQP contained in the
Modify BSS PFC ACK message with the ABQP modified by the BSC. If the two ABQPs are the same,
the QoS attributes in the PFC are successfully modified and the BSC updates the contents of the
PFC with the modified ABQP. If the two ABQPs are different, the old ABQP is still used and the
contents of the PFC remain unchanged.

PFC Modification Procedure Initiated by the SGSN

Figure 3-4 shows the PFC modification procedure initiated by the SGSN.
Figure 3-4 PFC modification procedure initiated by the SGSN

MS BSC SGSN

ACTIVATE/DEACTIVATE/MODIFY PDP CONTEXT REQUEST

CREATE BSS PFC

CREATE BSS PFC ACK

ACTIVATE/DEACTIVATE/MODIFY PDP CONTEXT ACCEPT

Huawei Proprietary and Confidential

Issue 01 (2010-06-30) 3-3
Copyright © Huawei Technologies Co., Ltd.
 GSM BSS
GPRS/EGPRS QoS 3 Technical Description

1. After receiving a PDP context activation, deactivation, or modification request from an MS, if the
SGSN finds that the contents of the PFC need to be modified, the SGSN sends the BSC a Create
BSS PFC message, requesting the BSC to modify the ABQP in the PFC. The Create BSS PFC
message contains the ABQP that is modified by the SGSN.
2. After receiving the Create BSS PFC message, if the PFC exists in the BSC, the BSC obtains the
ABQP from the message, updates the ABQP in the PFC, and then sends a Create BSS PFC ACK
message to the SGSN; if the PFC does not exist in the BSC, the BSC creates a PFC, stores the
ABQP, ARP, PFI, and PFT in the PFC, and then sends a Create BSS PFC ACK message to the
SGSN.

3.1.3 PFC Deletion Procedure

The PFC deletion procedure is used to delete the PFC of a BSC. Huawei GPRS/EGPRS QoS feature
supports the PFC deletion procedure initiated by the SGSN but not by the BSC. As specified in the
3GPP TS 23.060, when the BSC does not support the ABQP in the PFC, the BSC can initiate the PFC
deletion procedure to request the SGSN to delete or modify the PFC.
On the BSC side, when the PFT corresponding to the PFC expires or when the MS terminates the PS
services, the BSC deletes the PFC without notifying the SGSN. On the SGSN side, when the SGSN
decides to delete the PFC, the SGSN sends the BSC a Delete BSS PFC message, requesting the BSC
to delete the PFC. After receiving the Delete BSS PFC message, the BSC deletes the PFC and then
sends a Delete BSS PFC ACK message to the SGSN.

PFC Deletion Procedure Initiated by the SGSN

Figure 3-5 shows the PFC deletion procedure initiated by the SGSN.
Figure 3-5 PFC deletion procedure initiated by the SGSN

BSC SGSN

DELETE BSS PFC

DELETE BSS PFC ACK

3.2 Mapping From R97/R98 QoS Attributes to R99 QoS

Attributes
In the 3GPP standards, there are two definitions of QoS, one in the R97/R98 and the other in the R99. In
R99, the definitions of GERAN QoS attributes are the same as the definitions of UTRAN QoS attributes.
PFM procedures are introduced into R99 QoS for the BSC and the SGSN to negotiate QoS attributes. In
R97/R98 QoS, QoS attributes are negotiated between the MS and the SGSN, and the BSC is not
involved in the QoS negotiation. If the MS or the SGSN does not support the PFM procedures, that is,
the MS or the SGSN does not support R99 QoS, the BSC needs to map R97/R98 QoS attributes to R99
QoS attributes to support the R97/R98 QoS handling. After R97/R98 QoS attributes are mapped to R99
QoS attributes, the BSC handles R97/R98/R99 QoS attributes in the same manner.

Huawei Proprietary and Confidential

Issue 01 (2010-06-30) 3-4
Copyright © Huawei Technologies Co., Ltd.
 GSM BSS
GPRS/EGPRS QoS 3 Technical Description

On the BSC side, R99 QoS attributes are negotiated between the BSC and the SGSN through the PFM
procedures and are stored in the Aggregate BSS QoS Profile (ABQP) of the PFC. The ABQP contains
the QoS attributes of R97/R98 and R99. Table 3-1 lists R99 QoS attributes.
Table 3-1 R99 QoS attributes
Conversational Streaming Interactive Background
R99 QoS Attribute Class Class Class Class
Maximum bit rate Y Y Y Y
Delivery order Y Y Y Y
Maximum SDU size Y Y Y Y
SDU format Y Y - -
information
SDU error ratio Y Y Y Y
Residual bit error ratio Y Y Y Y
Delivery of erroneous Y Y Y Y
SDUs
Transfer delay Y Y - -
Guaranteed bit rate Y Y - -
Traffic handling priority - - Y -
Allocation/Retention Y Y Y Y
priority
Source statistics Y Y - -
descriptor
Signaling Indication - - Y -

In the preceding table, "Y" indicates that the attribute is used by the traffic class, and "-" indicates that the attribute is not
used by the traffic class.

When the SGSN transmits downlink LLC PDUs to the BSC, the R97/R98 QoS attribute information (QoS
Profile) is contained in the DL Unitdata message of the downlink LLC PDUs. Table 3-2 lists the R97/R98
QoS attributes.
Table 3-2 R97/R98 QoS attributes
R97/R98 QoS Attribute SGSN BSC
Delay class Y -
Reliability class Y -
Peak throughput Y Y
Precedence Y Y
Mean throughput Y -

Huawei Proprietary and Confidential

Issue 01 (2010-06-30) 3-5
Copyright © Huawei Technologies Co., Ltd.
 GSM BSS
GPRS/EGPRS QoS 3 Technical Description

In the preceding table, "Y" indicates that the attribute is present in the NE, and "-" indicates that the attribute is not present
in the NE.

In the SGSN, there are five R97/R98 QoS attributes; in the BSC, there are only two attributes: Peak
throughput and Precedence. These two attributes are obtained by the BSC from the SGSN through the
QoS Profile information element in the DL Unitdata message. The BSC needs to map these two
R97/R98 QoS attributes to the corresponding R99 QoS attributes, that is, R97/R98 Peak throughput to
R99 Maximum bit rate, and R97/R98 Precedence to R99 Allocation/Retention priority. For details of the
mapping, see the 3GPP TS 23.107.
In R99, the ARP attribute is mainly used for the preemption of streaming class resources. The ARP
attribute is not contained in the ABQP and it is transmitted from the SGSN to the BSC through a Create
BSS PFC message in the PFM procedure. If the Create BSS PFC message does not contain the ARP
attribute, the BSC cannot obtain the R99 QoS attribute ARP. In this case, the BSC needs to map
Precedence class of the ABQP to Allocation/Retention priority of R99 QoS. Therefore, the mapping
between Precedence and Allocation/Retention priority occurs in the following conditions:
 Mapping between Precedence of R97/R98 QoS and Allocation/Retention priority of R99 QoS
 Mapping between Precedence class in the ABQP and Allocation/Retention priority of R99 QoS in the
case that the ARP attribute does not exist in R99 QoS
As specified in the 3GPP standard, there are 15 priority levels for the ARP attribute. The ARP is limited to
priority levels 1, 2, and 3 for GERAN when the Gb bearer service is used. Table 3-3 describes the ARP
mapping relation.
A unified ARP level is defined to support the configuration of the user priority weight based on QoS levels.
The ARP level can be 1, 2, or 3. The priority attributes of R99 QoS and those of R97/R98 QoS should be
mapped to the ARP levels. The mapping between the ARP levels and the priority attributes is as follows:
 If the negotiated R99 QoS has the ARP attribute, the Priority level of the ARP attribute is mapped to
the ARP level.
 If the negotiated R99 QoS does not have the ARP attribute, the Precedence class in the ABQP is
mapped to the ARP level.
 If the BSC or the SGSN does not support PFC, the Precedence attribute of R97/R98 QoS is mapped
to the ARP level.
Table 3-3 ARP mapping table
Precedence Class of
ABQP Precedence of QoS
Priority Level of ARP R99 QoS Without Profile
ARP Level R99 QoS with ARP ARP (R97/R98 QoS)
1 1 1 0
2 2 2 1
3 3-15 3 2

Huawei Proprietary and Confidential

Issue 01 (2010-06-30) 3-6
Copyright © Huawei Technologies Co., Ltd.
 GSM BSS
GPRS/EGPRS QoS 3 Technical Description

3.3 QoS based on service type

The service type information is obtained from the PFC. If the MS does not support the PFC, the service
is a BE service. After obtaining the service type, the BSC schedules the services based on the service
type priority. The priority-based sequence of services in descending order is as follows:
 Layer 3 control signaling such as GMM and SM
 Conversational services and PoC services
 Interactive services, background services, BE services, and streaming services.

3.4 QoS of Conversational Services

This section describes the feature GBFD-119906 Conversational QoS.
Conversational services belong to the real-time services and have strict requirements on transfer delay.
The scheduling priority of conversational services and PoC services is higher than other services.
According to 3GPP specifications, the transfer delay of conversational services cannot exceed 80 ms.
Generally, the end-to-end transfer delay of VoIP services cannot exceed 300 ms to ensure user
satisfaction.
With the introduction of RTTI, the round-trip time (RTT) is reduced from 20 ms to 10 ms on both the Um
and Abis interfaces. With the introduction of FANR, the reaction time of the MS is minimized even if the
link quality on the Um interface is poor. Theoretically, therefore, the requirement of conversational
services for transfer delay (80 ms) can be met after RTTI and FANR are introduced. For details of RTTI
and FANR, see Latency Reduction Feature Parameter Description.
If the MS supports reduced latency and if the BSC supports RTTI and FANR, the BSC allocates a PDCH
pair in RTTI configuration to a conversational service and activates the FANR. In this manner, the delay
requirement of the conversational service is met to the maximal degree. If the MS does not support
reduced latency or if the BSC does not support RTTI or FANR, the BSC allocates PDCHs in BTTI
configuration to a conversational service and does not reject the packet access of the conversational
service. The BSC, however, does not guarantee the transfer delay required by the conversational
service.
In addition to RTTI and FANR, the following methods are used to reduce the transfer delay of
conversational services:
 The radio block scheduling delay is reduced by limiting the channel multiplexing ratio.
The parameter RTTIPDCHMULTIPLEXTHRESH specifies the PDCH multiplexing threshold in RTTI
configuration. The thresholds for both the uplink and downlink multiplexing ratios of the PDCHs in
RTTI configuration are specified by RTTIPDCHMULTIPLEXTHRESH. If the channel multiplexing ratio
of a PDCH in RTTI configuration equals the PDCH multiplexing threshold in RTTI configuration, no
more TBFs can be multiplexed on this PDCH. The maximum multiplexing ratio of the PDCH in RTTI
configuration is limited. Therefore, the maximum interval of scheduling the radio blocks on the PDCHs
in RTTI configuration is limited. As a result, the radio block scheduling delay is limited to an allowable
range.
 Specific LA/IR algorithms are adopted to reduce RLC data block retransmissions, thus reducing the
transfer delay.
A new table about the mapping between the BEP measurement reports and the coding schemes is
used for conversational services. When the signal quality on the Um interface is poor, conversational
services adopt low-rate coding schemes to reduce data retransmissions and ensure low BEP.
The characteristics of Huawei conversational QoS are as follows:

Huawei Proprietary and Confidential

Issue 01 (2010-06-30) 3-7
Copyright © Huawei Technologies Co., Ltd.
 GSM BSS
GPRS/EGPRS QoS 3 Technical Description

 Currently, RTTI and FANR are supported only when IP/HDLC transmission is used on the Abis
interface. Therefore, conversational QoS is better guaranteed in IP/HDLC transmission mode than in
other transmission modes. In addition, RTTI and FANR are enabled or disabled simultaneously.
 Conversational services do not support resource preemption or resource queuing.
 The RLC unacknowledged mode is not supported in the data transmission of conversational services.
Conversational services adopt specific LA/IR algorithms to reduce data retransmissions.

3.5 QoS of PoC Services

This section describes the feature GBFD-119905 PoC QoS.
PoC services belong to the real-time packet services and have strict requirements on bandwidth and
transfer delay. The scheduling priority of conversational services and PoC services is higher than other
services. The bandwidth requirement of PoC services is guaranteed by the GBR mechanism of
streaming class. To meet the low transfer delay requirement of PoC services, the BSC takes many
optimization measures, such as preferentially scheduling PoC services, using a low-rate coding scheme,
and using the policy of balanced channel allocation between uplink and downlink.
The BSC must identify the traffic class before processing PoC services. According to the current
protocols, the BSC cannot learn the PoC traffic class directly from the uplink and downlink packet
signaling and it can only roughly determine the PoC traffic class according to the QoS attributes. The
method of determining the PoC traffic class is as follows:
 The traffic class is the streaming class.
 Both the uplink and downlink GBRs of QoS attributes are higher than POCGBRMIN but smaller than
POCGBRMAX.
 The transfer delay of QoS attributes is shorter than POCDELAY.
 The PFI value is not the one reserved for BE services, GPRS mobility management/session
management (GMM/SM) signaling, short message service (SMS), or tunnelling of messages (TOM).
If all the preceding conditions are met, the traffic class is considered as the PoC service. To prevent the
incorrect identification of the traffic class, telecom operators should configure the following parameters
as required: POCGBRMIN, POCGBRMAX, and POCDELAY.
PoC services are of the streaming class. The BSC allocates radio blocks to a PoC service according to
the GBR of the streaming class so as to ensure the GBR for PoC services. PoC services have a strict
requirement for transfer delay. To meet the low transfer delay requirement, the BSC processes PoC
services as follows:
 Adopts a lower-rate coding scheme (for example, the data rate of the coding scheme adopted should
not be higher than that of MCS-6) to reduce the bit error rate and retransmission times, thus reducing
the transfer delay.
 Determines the LLC PDU lifetime according to the transfer delay of the QoS attributes.
 Increases the delay of releasing uplink and downlink TBFs.
 The priority of scheduling the PoC service is higher than that of scheduling other services. This helps
reduce the transfer delay of the PoC service.
PoC services run on concurrent and symmetrical uplink and downlink data flows. Therefore, the BSC
adopts the policy of balanced channel allocation between uplink and downlink. Within the multislot
capability of an MS, the BSC attempts to allocate the same number of uplink PDCHs and downlink
PDCHs to the MS. For example, for an MS of multislot class 10, the following two channel allocation
schemes can be used.

Huawei Proprietary and Confidential

Issue 01 (2010-06-30) 3-8
Copyright © Huawei Technologies Co., Ltd.
 GSM BSS
GPRS/EGPRS QoS 3 Technical Description

Channel Number of
Allocation Downlink Number of Uplink Total Number of
Scheme Timeslots Timeslots Timeslots
1 4 1 5
2 3 2 5

According to the policy of balanced channel allocation between uplink and downlink, the BSC adopts
channel allocation scheme 2 for PoC services.

3.6 QoS of Interactive, Background, and BE Services

This section describes the feature GBFD-119907 PS Service in Priority.
For interactive, background, and BE services, when PSDIFSERVICESUP is set to SUPPORT, the BSC
assigns a priority of gold, silver, or copper to each user according to the traffic class, ARP, and THP in
the QoS attributes. Then, the BSC allocates radio blocks to TBFs based on the user priority.
The gold, silver, and copper user priority maps to the three ARP levels, as shown in Table 3-4. The user
priorities in the table are default values. (GBFD-119902 QoS ARP&THP).
Table 3-4 User priority configuration
Traffic Class and THP ARP Level 1 ARP Level 2 ARP Level 3
Interactive THP1 10 6 2
services
THP2 10 6 2
THP3 10 6 2
Background services 10 6 2
BE services 10 6 2

The user priority weight is a factor for TBF scheduling, and it is configured through parameters. The
configuration principles are as follows:
 If different traffic classes have the same ARP level, the traffic classes should have decreasing user
priority weight according to the order of interactive services, background services, and BE services.
For the same traffic class, the user priority weight should be configured according to the ARP level and
THP, that is, the user priority weight is proportional to the ARP level or THP.
 For interactive services, the user priority weight is configured according to the ARP level and THP. The
configuration principles are as follows:
− For the interactive services at the same ARP level, the user priority weight is proportional to the THP.
− For the interactive services at the same THP level, the user priority weight is proportional to the ARP.
The related configuration parameters at the cell level are as follows: THP1ARP1PRIWEIGHT,
THP1ARP2PRIWEIGHT, THP1ARP3PRIWEIGHT, THP2ARP1PRIWEIGHT,
THP2ARP2PRIWEIGHT, THP2ARP3PRIWEIGHT, THP3ARP1PRIWEIGHT,
THP3ARP2PRIWEIGHT, and THP3ARP3PRIWEIGHT.

Huawei Proprietary and Confidential

Issue 01 (2010-06-30) 3-9
Copyright © Huawei Technologies Co., Ltd.
 GSM BSS
GPRS/EGPRS QoS 3 Technical Description

 For background services, the user priority weight is configured according to the ARP level. A higher
ARP level indicates a greater user priority weight. The related configuration parameters at the cell
level are BKGARP1PRIWEIGHT, BKGARP2PRIWEIGHT, and BKGARP3PRIWEIGHT.
 For BE services, the user priority weight is configured according to the ARP level. A higher ARP level
indicates a greater user priority weight. The related configuration parameters at the cell level are
BEARP1PRIWEIGHT, BEARP2PRIWEIGHT, and BEARP3PRIWEIGHT.
The conditions for enabling the user priority-based scheduling are as follows:
 The MACSCHEDULETYPE parameter is set to PFSCHEDULE(Proportion Fair Schedule);
 The PSDIFSERVICESUP parameter is set to SUPPORT;
 The TBF current rate is greater than or equal to the GBR that is specified by the
DLMINGUARANTEERATE parameter.
Here, TBF current rate refers to the current filtering rate of the TBF that carries the user data. If the TBF
uses the RTTI channel, the TBF current rate is the filtering rate of all PDCHs in the channel group where
the TBF is located during radio block scheduling. If the TBF uses dual carriers in the downlink, the TBF
current rate is the filtering rate of all PDCHs in the two carriers during radio block scheduling. When
calculating the TBF current rate, the RATEFILTERTIMEWIN parameter determines the number of radio
block scheduling periods in the rate filtering time length. A greater value of this parameter indicates a
longer length of time for rate filtering, that is, the weight of the instantaneous rate is small in the current
rate calculation and the weight of history rates is great in the current rate calculation. The opposite is
also true.
The BSC provides differentiated services for users based on the user priority weight and the Proportional
Fair (PF) algorithm. A user with higher user priority can enjoy higher service rate and more scheduling
opportunities. In this manner, the bandwidth and time delay requirements of higher priority users are
preferentially met.
The GBR value of interactive services, background services, and BE services is specified by
DLMINGUARANTEERATE. The BSC preferentially schedules users whose rate does not reach the
GBR. The scheduling is based on the DLMINGUARANTEERATE parameter, which is a minimum
guarantee rate that PS services can proceed normally. The higher the downlink minimum guarantee rate
is, the faster the user rate is improved, and thus the better the user experience is. An extremely high
downlink minimum guarantee rate, however, affects the GBR guarantee of streaming services. The MS
with a lower TBF current rate has a higher scheduling weight. In this manner, the minimum service
guarantee rate of this user is guaranteed preferentially to ensure the service continuity.

3.7 QoS of Streaming Services

This section describes the feature GBFD-119901 Streaming QoS(GBR).
In the case of streaming class, the BSC allocates radio blocks to users according to the GBR of the QoS
attributes and ensures that the data transmission rates meet the requirements of streaming class. If
streaming services support resource preemption, high-priority streaming services can preempt the radio
blocks of low-priority streaming services when radio resources are insufficient. This ensures that
high-priority services can preferentially use radio resources. If streaming services do not support
resource preemption, the GBRs are decreased; when radio resources become sufficient, the GBRs are
restored to the negotiated values. When the BSC needs to decrease or restore GBRs, it requests the
SGSN to modify the GBRs through the PFM procedures.

3.7.1 GBR Assurance

Determining Whether GBR Is Reached
The GBR assurance function preferentially schedules the users whose rate does not reach the GBR.
Whether the rate of a user reaches the GBR is determined as follows:

Huawei Proprietary and Confidential

Issue 01 (2010-06-30) 3-10
Copyright © Huawei Technologies Co., Ltd.
 GSM BSS
GPRS/EGPRS QoS 3 Technical Description

 If the TBF current rate is greater than or equal to the GBR value, the user rate reaches the GBR.
 If the TBF current rate is smaller than the GBR value, the user rate does not reach the GBR.
 The TBF current rate is the current filtering rate of the TBF that carries the user. For details, see 3.6
QoS of Interactive, Background, and BE Services. For the streaming services, when the GBRQOS
parameter is set to YES, the GBR is the downlink GBR value in the QoS attribute; when the GBRQOS
parameter is set to NO, the GBR is the value of the DLMINGUARANTEERATE parameter.

Modifying and Restoring GBRs

 GBR modification
When the number of radio resources allocated to a GBR TBF changes or the coding scheme of a GBR
TBF changes, the BSC calculates the number of budgeted radio blocks for the GBR TBF on a PDCH
based on the GBR and the current coding scheme. If the GBR cannot be reached because of
insufficient radio blocks on the PDCH, the BSC calculates the GBR (the calculated GBR is lower than
the negotiated GBR) based on the number of available radio blocks on the PDCH. In addition, the BSC
modifies the GBR in the PFC and initiates a PFC modification procedure to request the SGSN to
modify the GBR. For details, see 3.1.2 PFC Modification Procedure.
 GBR restoration
After the BSC has initiated a PFC modification procedure and the GBR on the BSC side has been
decreased, the BSC can restore the GBR in the PFC to the negotiated value and initiate a PFC
modification procedure to request the SGSN to modify the GBR when the GBR TBF uses a higher-rate
coding scheme. For details, see 3.1.2 PFC Modification Procedure.
When a GBR TBF is released or it uses a higher-rate coding scheme, if one or more PDCHs allocated
to this GBR TBF have available radio blocks and the GBR of another GBR TBF on these PDCHs is
lower than the negotiated value, the BSC reallocates radio blocks to the latter GBR TBF and initiates a
GBR restoration procedure.

3.7.2 Resource Preemption

After the OccupyStreamingSwitch parameter is set to ON, the BSC enables the preemption of
streaming resources.
The ARP attribute defined in R99 QoS contains the following information: resource allocation priority,
resource preemption, and PFC queuing. The information is mainly used for the preemption of streaming
resources and for the PFC queuing. Currently, Huawei GPRS/EGPRS QoS feature does not support the
PFC queuing of streaming services.
When radio resources are insufficient, high-priority streaming services can preempt the radio resources
occupied by low-priority streaming services, thus ensuring that the requirements of high-priority services
for GBR are met. Before preempting the resources of streaming services, the BSC allocates an optimal
channel group to a user according to the channel allocation algorithm. The streaming service preemption
weight should be added to the channel allocation algorithm and it is used to specify the priority for
allocating channel groups when radio resources are insufficient during resource preemption. The
streaming service preemption weight is determined by the preemption trigger type and the number of
PDCHs and radio blocks to be preempted. The streaming service preemption weight is directly
proportional to the priority for allocating PDCHs.
If the user supports resource preemption, the BSC enables the TBF preemption when one or more
channels of a TBF has insufficient radio blocks, or the BSC releases one or more preemptable TBFs
when the channels are insufficient to meet the GBR and multislot requirements of the preempting TBF.
The TBFs to be preempted must meet the following requirements:
 The TBFs to be preempted must be preemptable.
 The ARP of the TBFs to be preempted must be lower than the ARP of the preempting TBF.

Huawei Proprietary and Confidential

Issue 01 (2010-06-30) 3-11
Copyright © Huawei Technologies Co., Ltd.
 GSM BSS
GPRS/EGPRS QoS 3 Technical Description

 Among all the preemptable TBFs on one or more PDCHs, the TBF that is to be preempted is the one
that has the lowest ARP.
 The number of PDCHs occupied by all the TBFs to be preempted should be greater than or equal to
the number of PDCHs required by the preempting TBF so as to meet the multislot requirement of the
preempting TBF.
 The number of radio blocks occupied by all the TBFs to be preempted should be greater than or equal
to the number of radio blocks required by the preempting TBF so as to meet the GBR requirement of
the preempting TBF.
According to the preceding requirements, the BSC performs the following processing:
 If the TBFs to be preempted meet all the preceding requirements, the BSC performs the TBF
preemption when radio blocks are insufficient, or the BSC releases one or more preemptable TBFs
when the channels are insufficient.
 If the qualified TBF does not exist, the TBF preemption fails. Consequently, the access request for
service is rejected.
 If the number of radio blocks to be preempted does not meet the GBR requirement, the BSC
calculates the achievable GBR based on the total number of radio blocks occupied by all the
preemptable TBFs and then modifies the GBR in the PFC. Meanwhile, the BSC initiates a PFC
modification procedure to request the SGSN to modify the GBR.

Huawei Proprietary and Confidential

Issue 01 (2010-06-30) 3-12
Copyright © Huawei Technologies Co., Ltd.
 GSM BSS
GPRS/EGPRS QoS 4 Parameters

4 Parameters
Table 4-1 Parameter description
Parameter ID NE MML Command Description

PSDIFSERVICESUP BSC6900 SET Meaning: This parameter indicates

GCELLPSOTHERPARA whether the feature "PS Service in
(Optional) Priority" is supported.

GUI Value Range: NOTSUPPORT(Not

Support), SUPPORT(Support)
Actual Value Range: NOTSUPPORT,
SUPPORT
Unit: None
Default Value: NOTSUPPORT
MACSCHEDULETYPE BSC6900 SET Meaning: This parameter indicates the
GCELLPSOTHERPARA type of the MAC scheduling algorithm.
(Optional)
GUI Value Range:
RRSCHEDULE(Round Robin Schedule),
PFSCHEDULE(Proportion Fair
Scheduling), CIRSCHEDULE(Scheduling
Based On Carrier to Interference Ratio)
Actual Value Range: RRSCHEDULE,
PFSCHEDULE, CIRSCHEDULE
Unit: None
Default Value: RRSCHEDULE
DLMINGUARANTEERA BSC6900 SET Meaning: This parameter indicates the
TE GCELLPSOTHERPARA minimum guaranteed rate in downlink to
(Optional) ensure the normal processing of PS
services of users.

GUI Value Range: 0~50

Actual Value Range: 0~50
Unit: None
Default Value: 10
GBRQOS BSC6900 SET Meaning: Obtains the QoS parameter
GCELLPSOTHERPARA from the Aggregate BSS QoS Profile
(Optional) (ABQP) of packet flow context (PFC)
when the MS and the network support the
PFC; obtains the QoS parameter from the
uplink request originated by the MS or the
DL UNITDATA of the SGSN. GBR:
guaranteed bit rate.

GUI Value Range: NO(Not Support),

YES(Support)
Actual Value Range: NO, YES
Unit: None
Default Value: NO

Huawei Proprietary and Confidential

Issue 01 (2010-06-30) 4-1
Copyright © Huawei Technologies Co., Ltd.
 GSM BSS
GPRS/EGPRS QoS 4 Parameters

Parameter ID NE MML Command Description

PFCSUP BSC6900 ADD NSE(Optional) Meaning: Whether to support packet flow

MOD NSE(Optional) context (PFC). The PFC flow is used to
control the QoS of the packet service of
the MS.

GUI Value Range: NO(No Support),

YES(Support)
Actual Value Range: NO, YES
Unit: None
Default Value: NO
RTTIPDCHMULTIPLEX BSC6900 SET Meaning: Maximum number of RTTI
THRESH GCELLPSCHM(Optiona TBFs that can be multiplexed on the
l) PDCH. A PDCH can be assigned when
the number of RTTI TBFs on it is smaller
than the value of this parameter. This
parameter is valid only when its value is
smaller than or equal to "MSRD PDCH
DL Multiplexing Threshold".

GUI Value Range: 10~80

Actual Value Range: 10~80
Unit: None
Default Value: 30
POCGBRMIN BSC6900 SET Meaning: Minimum bandwidth of the POC
GCELLPSOTHERPARA service (push to talk over cellular). The
(Optional) transmission delay of the POC service
must be relatively small. The network side
must support the function of detecting the
POC service type and reduce the delay
through related processing to meet the
POC service requirement. For the POC
service received by the network side,
GbrValue in the ABQP must be larger
than the minimum bandwidth of the POC
service.

GUI Value Range: 6~120

Actual Value Range: 6~120
Unit: None
Default Value: 6
POCGBRMAX BSC6900 SET Meaning: Maximum bandwidth of the
GCELLPSOTHERPARA POC service (push to talk over cellular).
(Optional) The transmission delay of the POC
service must be relatively small. The
network side must support the function of
detecting the POC service type and
reduce the delay through related
processing to meet the POC service
requirement. For the POC service
received by the network side, GbrValue in

Huawei Proprietary and Confidential

Issue 01 (2010-06-30) 4-2
Copyright © Huawei Technologies Co., Ltd.
 GSM BSS
GPRS/EGPRS QoS 4 Parameters

Parameter ID NE MML Command Description

the ABQP must be lower than the
maximum bandwidth of the POC service.

GUI Value Range: 6~120

Actual Value Range: 6~120
Unit: None
Default Value: 16

POCDELAY BSC6900 SET Meaning: Maximum transmission delay of

GCELLPSOTHERPARA the POC service (push to talk over
(Optional) cellular). The transmission delay of the
POC service must be relatively small. The
network side must support the function of
detecting the POC service type and
reduce the delay through related
processing to meet the POC service
requirement. For the POC service
received by the network side, Transfer
Delay in the ABQP must be lower than
the transmission threshold of the POC
service.

GUI Value Range: 250~650

Actual Value Range: 250~650
Unit: None
Default Value: 650
THP1ARP1PRIWEIGHT BSC6900 SET Meaning: Combination of the THP1 and
GCELLPSCHM(Optiona ARP1 priority in the Interactive service.
l) THP1-ARP1 priority weight determines
the number of the budget blocks and the
block scheduling priority.

GUI Value Range: 1~10

Actual Value Range: 1~10
Unit: None
Default Value: 10
THP1ARP2PRIWEIGHT BSC6900 SET Meaning: Combination of the THP1 and
GCELLPSCHM(Optiona ARP2 priority in the Interactive service.
l) THP1-ARP2 priority weight determines
the number of the budget blocks and the
block scheduling priority.

GUI Value Range: 1~10

Actual Value Range: 1~10
Unit: None
Default Value: 6

Huawei Proprietary and Confidential

Issue 01 (2010-06-30) 4-3
Copyright © Huawei Technologies Co., Ltd.
 GSM BSS
GPRS/EGPRS QoS 4 Parameters

Parameter ID NE MML Command Description

THP1ARP3PRIWEIGHT BSC6900 SET Meaning: Combination of the THP1 and

GCELLPSCHM(Optiona ARP3 priority in the Interactive service.
l) THP1-ARP3 priority weight determines
the number of the budget blocks and the
block scheduling priority.

GUI Value Range: 1~10

Actual Value Range: 1~10
Unit: None
Default Value: 4
THP2ARP1PRIWEIGHT BSC6900 SET Meaning: Combination of the THP2 and
GCELLPSCHM(Optiona ARP1 priority in the Interactive service.
l) THP2-ARP1 priority weight determines
the number of the budget blocks and the
block scheduling priority.

GUI Value Range: 1~10

Actual Value Range: 1~10
Unit: None
Default Value: 8
THP2ARP2PRIWEIGHT BSC6900 SET Meaning: Combination of the THP2 and
GCELLPSCHM(Optiona ARP2 priority in the Interactive service.
l) THP2-ARP2 priority weight determines
the number of the budget blocks and the
block scheduling priority.

GUI Value Range: 1~10

Actual Value Range: 1~10
Unit: None
Default Value: 4
THP2ARP3PRIWEIGHT BSC6900 SET Meaning: Combination of the THP2 and
GCELLPSCHM(Optiona ARP3 priority in the Interactive service.
l) THP2-ARP3 priority weight determines
the number of the budget blocks and the
block scheduling priority.

GUI Value Range: 1~10

Actual Value Range: 1~10
Unit: None
Default Value: 3
THP3ARP1PRIWEIGHT BSC6900 SET Meaning: Combination of the THP3 and
GCELLPSCHM(Optiona ARP1 priority in the Interactive service.
l) THP3-ARP1 priority weight determines
the number of the budget blocks and the
block scheduling priority.

GUI Value Range: 1~10

Actual Value Range: 1~10
Unit: None

Huawei Proprietary and Confidential

Issue 01 (2010-06-30) 4-4
Copyright © Huawei Technologies Co., Ltd.
 GSM BSS
GPRS/EGPRS QoS 4 Parameters

Parameter ID NE MML Command Description

Default Value: 6

THP3ARP2PRIWEIGHT BSC6900 SET Meaning: Combination of the THP3 and

GCELLPSCHM(Optiona ARP2 priority in the Interactive service.
l) THP3-ARP2 priority weight determines
the number of the budget blocks and the
block scheduling priority.

GUI Value Range: 1~10

Actual Value Range: 1~10
Unit: None
Default Value: 3
THP3ARP3PRIWEIGHT BSC6900 SET Meaning: Combination of the THP3 and
GCELLPSCHM(Optiona ARP3 priority in the Interactive service.
l) THP3-ARP3 priority weight determines
the number of the budget blocks and the
block scheduling priority.

GUI Value Range: 1~10

Actual Value Range: 1~10
Unit: None
Default Value: 2
BKGARP1PRIWEIGHT BSC6900 SET Meaning: ARP1 priority in the
GCELLPSCHM(Optiona Background service. ARP1 priority weight
l) determines the number of the budget
blocks and the block scheduling priority.

GUI Value Range: 1~10

Actual Value Range: 1~10
Unit: None
Default Value: 4
BKGARP2PRIWEIGHT BSC6900 SET Meaning: ARP2 priority in the
GCELLPSCHM(Optiona Background service. ARP2 priority weight
l) determines the number of the budget
blocks and the block scheduling priority.

GUI Value Range: 1~10

Actual Value Range: 1~10
Unit: None
Default Value: 2
BKGARP3PRIWEIGHT BSC6900 SET Meaning: ARP3 priority in the
GCELLPSCHM(Optiona Background service. ARP3 priority weight
l) determines the number of the budget
blocks and the block scheduling priority.

GUI Value Range: 1~10

Actual Value Range: 1~10
Unit: None

Huawei Proprietary and Confidential

Issue 01 (2010-06-30) 4-5
Copyright © Huawei Technologies Co., Ltd.
 GSM BSS
GPRS/EGPRS QoS 4 Parameters

Parameter ID NE MML Command Description

Default Value: 1

BEARP1PRIWEIGHT BSC6900 SET Meaning: ARP1 priority in the BE service.

GCELLPSCHM(Optiona ARP1 priority weight determines the
l) number of the budget blocks and the
block scheduling priority.

GUI Value Range: 1~10

Actual Value Range: 1~10
Unit: None
Default Value: 8
BEARP2PRIWEIGHT BSC6900 SET Meaning: ARP2 priority in the BE service.
GCELLPSCHM(Optiona ARP2 priority weight determines the
l) number of the budget blocks and the
block scheduling priority.

GUI Value Range: 1~10

Actual Value Range: 1~10
Unit: None
Default Value: 4
BEARP3PRIWEIGHT BSC6900 SET Meaning: ARP3 priority in the BE service.
GCELLPSCHM(Optiona ARP3 priority weight determines the
l) number of the budget blocks and the
block scheduling priority.

GUI Value Range: 1~10

Actual Value Range: 1~10
Unit: None
Default Value: 2
RATEFILTERTIMEWIN BSC6900 SET Meaning: This parameter indicates the
GCELLPSOTHERPARA block periods selected as the time length
(Optional) for rate filtering, when calculating the
current data rate of TBF. If this parameter
is set to a higher value, the weight of the
current instantaneous rate against the
filer rate is lower whereas the weight of
the history rate against the filer rate is
higher. If this parameter is set to a lower
value, the weight of the current
instantaneous rate against the filter rate is
higher whereas the weight of the history
rate against the filer rate is lower.

GUI Value Range: 0~255

Actual Value Range: 0~255
Unit: None

Huawei Proprietary and Confidential

Issue 01 (2010-06-30) 4-6
Copyright © Huawei Technologies Co., Ltd.
 GSM BSS
GPRS/EGPRS QoS 4 Parameters

Parameter ID NE MML Command Description

Default Value: 50

OccupyStreamingSwitch BSC6900 SET Meaning: When the PDCHs are

GCELLPSOTHERPARA insufficient, the streaming service with
(Optional) high priority can preempt the PDCHs that
are seized by the streaming service with
low priority. After the PDCH resource
preemption, the streaming service with
low priority initiates the QoS negotiation
with the SGSN. If the QoS negotiation
fails, or if all the PDCHs are preempted,
then the streaming service with low
priority is disrupted.

GUI Value Range: OFF(OFF), ON(ON)

Actual Value Range: OFF, ON
Unit: None
Default Value: OFF

Huawei Proprietary and Confidential

Issue 01 (2010-06-30) 4-7
Copyright © Huawei Technologies Co., Ltd.
 GSM BSS
GPRS/EGPRS QoS 5 Counters

5 Counters
For the counters, see the BSC6900 GSM Performance Counter Reference.

Huawei Proprietary and Confidential

Issue 01 (2010-06-30) 5-1
Copyright © Huawei Technologies Co., Ltd.
 GSM BSS
GPRS/EGPRS QoS 6 Glossary

6 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.

Huawei Proprietary and Confidential

Issue 01 (2010-06-30) 6-1
Copyright © Huawei Technologies Co., Ltd.
 GSM BSS
GPRS/EGPRS QoS 7 Reference Documents

7 Reference Documents
[1] 3GPP TS 43.064: “Overall description of the GPRS Radio Interface; Stage 2”
[2] 3GPP TS 44.060: “Radio Link Control (RLC) / Medium Access Control (MAC) protocol”
[3] 3GPP TS 23.107: “Quality of Service (QoS) concept and architecture”
[4] 3GPP TS 23.979: “Push-to-talk over Cellular (PoC) services; Stage 2”
[5] 3GPP TS 48.018: “BSS GPRS Protocol (BSSGP)”
[6] 3GPP TS 23.060: “General Packet Radio Service (GPRS); Service Description; Stage 2”
[7] BSC6900 Feature List
[8] BSC6900 Optional Feature Description
[9] BSC6900 GSM Parameter Reference
[10] BSC6900 GSM MML Command Reference
[11] BSC6900 GSM Performance Counter Reference

Huawei Proprietary and Confidential

Issue 01 (2010-06-30) 7-1
Copyright © Huawei Technologies Co., Ltd.