GPRSEGPRS QoS(GBSS14.0_01)

GPRS/EGPRS QoS GBSS14.0

Feature Parameter Description

Issue 01

Date 2012-04-28

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2012. 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

Issue 01 (2012-04-28) Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.

i

Contents

1 About This Document .............................................................................................................. 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 Streaming QoS(GBR) .................................................................................................................... 3-1

3.1.1 GBR Assurance .................................................................................................................... 3-1

3.1.2 Resource Preemption ........................................................................................................... 3-2

3.2 PoC QoS ....................................................................................................................................... 3-2

3.3 Conversational QoS ...................................................................................................................... 3-3

3.4 PS Service in Priority and QoS ARP&THP ................................................................................... 3-4

3.5 GPRS/EGPRS Time slot multiplexing priority ............................................................................... 3-6

3.6 IM Service Efficiency Improvement ............................................................................................... 3-7

3.7 Web Browsing Service Efficiency Improvement............................................................................ 3-7

3.8 Email Service Efficiency Improvement .......................................................................................... 3-8

3.9 Streaming Media Service Resource Balancing ............................................................................. 3-8

3.10 P2P Resource Balancing ............................................................................................................ 3-9

4 Related Features ....................................................................................................................... 4-1

5 Impact on the Network............................................................................................................. 5-1

5.1 Streaming QoS(GBR) .................................................................................................................... 5-1

5.1.1 Impact on System Capacity .................................................................................................. 5-1

5.1.2 Impact on Network Performance .......................................................................................... 5-1

5.2 QoS ARP&THP ............................................................................................................................. 5-1



5.3 PoC QoS ....................................................................................................................................... 5-1



5.4 Conversational QoS ...................................................................................................................... 5-1



5.5 GPRS/EGPRS Time slot multiplexing priority ............................................................................... 5-1



5.6 PS Service in Priority .................................................................................................................... 5-2



GSM BSS




ii

5.7 IM Service Efficiency Improvement ............................................................................................... 5-2



5.8 Web Browsing Service Efficiency Improvement............................................................................ 5-2



5.9 Email Service Efficiency Improvement .......................................................................................... 5-2



5.10 Streaming Media Service Resource Balancing ........................................................................... 5-3

5.10.1 Impact on System Capacity ................................................................................................ 5-3

5.10.2 Impact on Network Performance ........................................................................................ 5-3

5.11 P2P Resource Balancing............................................................................................................. 5-3

5.11.1 Impact on System Capacity ................................................................................................ 5-3

5.11.2 Impact on Network Performance ........................................................................................ 5-3

6 Engineering Guidelines ........................................................................................................... 6-1

6.1 When to Use GPRS/EGPRS QoS ................................................................................................ 6-1

6.1.1 Streaming QoS(GBR) ........................................................................................................... 6-1

6.1.2 QoS ARP&THP ..................................................................................................................... 6-1

6.1.3 PoC QoS .............................................................................................................................. 6-1

6.1.4 Conversational QoS ............................................................................................................. 6-1

6.1.5 GPRS/EGPRS Time slot multiplexing priority ...................................................................... 6-1

6.1.6 PS Service in Priority ............................................................................................................ 6-1

6.1.7 IM Service Efficiency Improvement ...................................................................................... 6-1

6.1.8 Web Browsing Service Efficiency Improvement ................................................................... 6-1

6.1.9 Email Service Efficiency Improvement ................................................................................. 6-1

6.1.10 Streaming Media Service Resource Balancing .................................................................. 6-2

6.1.11 P2P Resource Balancing .................................................................................................... 6-2

6.2 Information to Be Collected ........................................................................................................... 6-2

6.3 Network Planning .......................................................................................................................... 6-2

6.3.1 RF Planning .......................................................................................................................... 6-2

6.3.2 Network Topology ................................................................................................................. 6-2

6.3.3 Hardware Planning ............................................................................................................... 6-2

6.4 Overall Deployment Procedure ..................................................................................................... 6-2

6.5 Deploying Streaming QoS(GBR)................................................................................................... 6-2

6.6 Deploying QoS ARP&THP ............................................................................................................ 6-2

6.7 Deploying PoC QoS ...................................................................................................................... 6-3

6.8 Deploying Conversational QoS ..................................................................................................... 6-3

6.9 Deploying GPRS/EGPRS Time slot multiplexing priority .............................................................. 6-3

6.10 Deploying PS Service in Priority ................................................................................................. 6-3

6.11 Deploying IM Service Efficiency Improvement ............................................................................ 6-3

GSM BSS




iii

6.12 Deploying Web Browsing Service Efficiency Improvement ........................................................ 6-3

6.13 Deploying Email Service Efficiency Improvement ....................................................................... 6-3

6.14 Deploying Streaming Media Service Resource Balancing .......................................................... 6-3

6.15 Deploying P2P Resource Balancing ........................................................................................... 6-3

6.16 Performance Optimization ........................................................................................................... 6-3

6.17 Troubleshooting ........................................................................................................................... 6-3

7 Parameters.................................................................................................................................. 7-1

8 Counters ...................................................................................................................................... 8-1

9 Appendix ..................................................................................................................................... 9-1

9.1 PFC Procedures ............................................................................................................................ 9-1

9.1.1 PFC Establishment Procedure ............................................................................................. 9-1

9.1.2 PFC Modification Procedure ................................................................................................ 9-2

9.1.3 PFC Deletion Procedure ....................................................................................................... 9-4

9.2 Mapping Between R97/R98 QoS Attributes and R99 QoS Attributes ........................................... 9-4

10 Glossary .................................................................................................................................. 10-1

11 Reference Documents ......................................................................................................... 11-1

GSM BSS

GPRS/EGPRS QoS 1 About This Document



1-1

1 About This Document

1.1 Scope

This document describes the General Packet Radio Service/Enhanced General Packet Radio Service (GPRS/EGPRS) QoS feature, including the technical description, related features, network impact, and engineering guidelines.

The GPRS/EGPRS QoS feature includes the following features, each of which is controlled by a license:

GBFD-119901 Streaming QoS(GBR)

GBFD-119902 QoS ARP&THP

GBFD-119905 PoC QoS

GBFD-119906 Conversational QoS

GBFD-119506 GPRS/EGPRS Time slot multiplexing priority

GBFD-119907 PS Service in Priority

GBFD-511603 IM Service Efficiency Improvement

GBFD-511604 Web Browsing Service Efficiency Improvement

GBFD-511605 Email Service Efficiency Improvement

GBFD-511606 Streaming Media Service Resource Balancing

GBFD-511607 P2P Resource Balancing

1.2 Intended Audience

This document is intended for:

Personnel who need to understand the GPRS/EGPRS QoS feature

Personnel who work with Huawei GPRS products

1.3 Change History

This section provides information about the changes in different document versions.

There are two types of changes, which are defined as follows:

Feature change: refers to a change in the GPRS/EGPRS QoS feature of a specific product version.

Editorial change: refers to a change in wording or the addition of information that was not described in the earlier version.

Document Issues

The document issue is as follows:

01 (2012-04-28)

Draft A (2012-02-15)

01 (2012-04-28)

This is the first release of GBSS14.0.

Compared with issue draft A (2012-02-15) of GBSS14.0, issue 01 (2012-04-28) of GBSS14.0 has no change.

GSM BSS

GPRS/EGPRS QoS 1 About This Document



1-2

Draft A (2012-02-15)

This is a draft.

Compared with issue 02 (2011-05-15) of GBSS13.0, draft A (2012-02-15) of GBSS14.0 incorporates the changes described in the following table.

Change Type

Change Description Parameter Change

Feature change

Added the technical description, related features, network impact, and engineering guidelines for the following features:

IM Service Efficiency Improvement

Web Browsing Service Efficiency Improvement

Email Service Efficiency Improvement

Streaming Media Service Resource Balancing

P2P Resource Balancing

None

Editorial change

Added chapters 4 "Related Features", 5 "Impact on the Network", and 6 "Engineering Guidelines" for the following features:

Streaming QoS(GBR)

QoS ARP&THP

PoC QoS

Conversational QoS

GPRS/EGPRS Time slot multiplexing priority

PS Service in Priority

None

GSM BSS

GPRS/EGPRS QoS 2 Overview



2-1

2 Overview

GPRS/EGPRS QoS refers to the quality of service (QoS) requirements of GPRS/EGPRS services in the GSM EDGE Radio Access Network (GERAN). EDGE is short for Enhanced Data rates for GSM Evolution. The QoS requirements are defined by QoS attributes in Release 99 (R99), including traffic class, transfer delay, maximum bit rate (MBR), guaranteed bit rate (GBR), traffic handling priority (THP), allocation/retention priority (ARP), and reliability.

The GPRS/EGPRS QoS feature is used to meet the QoS requirements (transfer delay, bandwidth, and reliability) of GPRS/EGPRS services. From the perspective of users, this feature improves their experience with GPRS/EGPRS services. From the perspective of telecom operators, this feature provides the following benefits:

Customizes radio resource allocation policies based on the QoS attributes to guarantee high bandwidth, high data rate, and better service quality for high-priority users. This may lead to low bandwidth and poor service quality for low-priority users.

Provides sufficient and stable bandwidth to users performing streaming services and preferentially meets QoS requirements of high-priority users when radio resources are insufficient.

Meets the delay requirements of conversational services and Push to talk over Cellular (PoC) services. This provides diversified value-added services and improves user experience to attract more high-end users.

Formulates flexible charging policies.

In R99 QoS attributes, there are four traffic classes: conversational, streaming, interactive, and background. The main division among them is how delay sensitive the traffic is. The conversational class is the most delay sensitive and the background class is the least delay sensitive.

The characteristics of the four types of services are as follows:

Typical conversational services include voice over IP (VoIP), Gaming, video telephony, and video conferencing tools. For conversational services, the transfer delay should be low, and the time sequence and delay variation between data stream information entities (for example, data packets) should be preserved.

Typical streaming services are real-time video and audio streaming media services. For streaming services, the time sequence and delay variation between data stream information entities (for example, data packets) should be preserved regardless of transfer delay.

Interactive services are meant to be used by traditional packet switched (PS) services, such as web browsing, database retrieval, and server access. For interactive services, a timely response to the request is required. Therefore, the round-trip delay (RTD) time is one of the key attributes. In addition, the content of packets should be transferred at a low bit error rate (BER).

Background services are also meant to be used by traditional PS services, such as file downloading, background delivery of emails, short message service (SMS), and reception of measurement records. For background services, the traffic is insensitive to transfer delay but the content of packets should be transferred at a low BER.

The PoC service belongs to the streaming class. It is a type of voice group call service (VGCS) implemented in the GSM system. The PoC service adopts the packet switched technology on GPRS/EGPRS networks. Major functional entities for the PoC service run on the PoC server in the core network (CN). The signaling and voice for the PoC service are carried on the GPRS/EGPRS networks by means of packets and are transparently transmitted from the base station subsystem (BSS) to the CN. Unlike common PS services, PoC services require low transfer delay in transmitting voice signals. If the transfer delay is high, user experience declines.

Different traffic classes have different QoS requirements, which are determined by specific QoS attributes. QoS attributes are contained in Packet Flow Context (PFC). The BSC negotiates with the

GSM BSS




2-2

SGSN about the QoS attributes by performing the PFC procedures. If MSs or the SGSN does not support the PFC procedures, the BSC must map Release 97 (R97) or Release 98 (R98) QoS attributes to R99 QoS attributes before handling R97 or R98 QoS attributes.

The BSC implements differentiated QoS for different types of services as follows:

For interactive, background, and best effort (BE) services, the BSC configures their user priority weight based on the traffic class, ARP, and THP in the QoS attributes. Then, the BSC allocates radio blocks to users based on the user priority weight. Higher-priority users are allocated more radio blocks and therefore have higher available radio bandwidth.

In the GPRS/EGPRS QoS feature, BE services refer to the services whose QoS attributes are not obtained from the BSC or whose traffic class is unknown. The BSC allocates or schedules radio resources for BE services based on the Best Effort policy.

For streaming services, the BSC allocates radio blocks to users based on the GBR in the QoS attributes, ensuring that the users have sufficient and stable bandwidth. In addition, the BSC supports preemption of streaming resources. If radio resources are insufficient, high-priority users are allowed to preempt the radio blocks occupied by low-priority users. This ensures that high-priority users have preferential use of radio resources.

For conversational services, if MSs support reduced latency, the BSC allocates a PDCH pair in Reduced Transmission Time Interval (RTTI) configuration to MSs and activates Fast Ack/Nack Reporting (FANR) to minimize the transfer delay.

Reduced latency refers to the use of FANR in either Basic Transmission Time Interval (BTTI) or RTTI configuration. Reduced latency capability is required for the use of MTTI configurations, as specified in 3GPP TS 44.060.

For PoC services (a type of real-time PS service), the BSC applies the GBR mechanism from the streaming class to meet the high bandwidth requirement and takes several measures to meet the low transfer delay requirement. The measures include:

Preferentially scheduling radio blocks for the PoC service

Using a low-rate coding scheme

Allocating the same number of uplink and downlink channels to an MS

For instant messaging (IM), web browsing, email, streaming media, and point-to-point (P2P) services, the BSC supports differentiated resource management.

In the GSM network where spectrum resources are limited, GSM mobile broadband (MBB) services generally have low throughput. If the BSC allocates excess channels to MSs performing MBB services based on their multislot capability, some resources may be wasted, and resource insufficiency may occur for high-value services as a result.

Telecom operators from different regions deploy different MBB services. With the sharp increase in the throughput of mobile Internet services, all telecom operators have to use more network devices, but profits do not increase in proportion to the number of network devices.

From the perspective of telecom operators, different services consume different quantities of network resources and provide different gains. In the mobile Internet era, telecom operators expect to perform differentiated management on MBB services so that they can properly use network resources. Figure 2-1 illustrates service-based differentiated QoS for PS services.

GSM BSS




2-3

Figure 2-1 Service-based differentiated QoS for PS services

GSM BSS

GPRS/EGPRS QoS 3 Technical Description



3-1

3 Technical Description

3.1 Streaming QoS(GBR)

This section describes the GBFD-119901 Streaming QoS(GBR) feature.

With this feature, the BSC allocates radio blocks to users performing streaming services based on the GBR in the QoS attributes. This ensures that the data transmission rates meet the requirements of streaming services. If streaming services support resource preemption, high-priority streaming services can preempt radio blocks occupied by low-priority streaming services when radio resources are insufficient. This ensures that high-priority streaming services preferentially use radio resources. If streaming services do not support resource preemption, the BSC reduces the GBR when radio resources are insufficient; the BSC restores the GBR when radio resources are sufficient. When the BSC needs to reduce or restore the GBR, it initiates the PFC modification procedure, requesting the SGSN to modify the GBR.

3.1.1 GBR Assurance

Determining Whether GBR Is Reached

The GBR assurance function preferentially schedules resources for a user whose data rate does not reach the GBR. Whether a user's data rate reaches the GBR is determined as follows:

If the current temporary block flow (TBF) rate is higher than or equal to the GBR, the user's data rate reaches the GBR.

If the current TBF rate is lower than the GBR, the user's data rate does not reach the GBR.

The current TBF rate refers to the current filtering rate of the TBF carrying the user data. For details, see section 3.4 "PS Service in Priority and QoS ARP&THP." For streaming services, if GBRQOS is set to YES(Yes), the max(the GBR is equal to the downlink GBR specified in the QoS attributes, DLMINGUARANTEERATE) determines the GBR; if GBRQOS is set to NO(No), the GBR is equal to the value of the DLMINGUARANTEERATE parameter.

Modifying and Restoring GBR

Modifying the GBR

When the BSC allocates radio blocks to a GBR TBF or the coding scheme used by 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 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 replaces the GBR in the PFC with the calculated value and initiates a PFC modification procedure that requests the SGSN to modify the GBR. For details about the PFC modification procedure, see section 9.1.2 PFC Modification Procedure .

Restoring the GBR

After the BSC has initiated a PFC modification procedure and the GBR on the BSC side has been reduced, the BSC restores the GBR in the PFC to the negotiated value if the GBR TBF uses a higher-rate coding scheme. In addition, the BSC initiates another PFC modification procedure, requesting the SGSN to modify the GBR. For details about the PFC modification procedure, see section 11.1.2 "PFC Modification Procedure."

When a GBR TBF is released or uses a higher-rate coding scheme, the BSC reallocates radio blocks to the latter GBR TBF and initiates a GBR restoration procedure 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 smaller than the negotiated value.

GSM BSS




3-2

3.1.2 Resource Preemption

If OccupyStreamingSwitch is set to ON(On), the BSC allows streaming services to preempt resources.

The ARP attribute defined in R99 QoS attributes contains the following information: resource allocation priority, resource preemption, and PFC queuing. Such information is mainly used for resource preemption and PFC queuing for streaming services. Currently, the GPRS/EGPRS QoS feature does not support PFC queuing for streaming services.

If radio resources are insufficient, high-priority services can preempt the radio resources occupied by low-priority services, ensuring that the GBR requirements of high-priority services are met. Before enabling resource preemption for streaming services, the BSC allocates an optimal PDCH group to a user based on the channel allocation algorithm. The channel allocation algorithm must contain the preemption weight for streaming services, specifying the priority for allocating a PDCH group during resource preemption when radio resources are insufficient. The preemption weight is determined by the cause of preemption and the numbers of PDCHs and radio blocks to be preempted. The preemption weight is proportional to the priority for allocating PDCHs.

If a user supports resource preemption, the BSC enables TBF preemption when radio blocks for one or more PDCHs of a TBF are insufficient; the BSC releases one or more preemptable TBFs when PDCHs are insufficient. This meets the GBR and multislot requirements during TBF preemption.

TBF preemption is allowed only if the following conditions are met:

TBFs support preemption.

The preempted TBF has a lower ARP than the preempting TBF.

The preempted TBF has the lowest ARP among all the preemptable TBFs on one or more PDCHs.

The number of PDCHs occupied by all the preempted TBFs is greater than or equal to the number of PDCHs required by the preempting TBFs. (This is the multislot requirement of resource preemption.)

The number of radio blocks occupied by all the preempted TBFs is greater than or equal to the number of radio blocks required by the preempting TBFs. (This is the GBR requirement of resource preemption.)

The BSC acts differently depending on whether the preceding requirements are met.

If all the preceding requirements are met, the BSC performs TBF preemption when radio blocks are insufficient; the BSC releases one or more preemptable TBFs when PDCHs are insufficient.

If the qualified TBF does not exist and the TBF reaches channel multiplex threshold, the TBF preemption fails. Consequently, the access request for service is rejected; If the qualified TBF does not exist and the TBF doesnt reach channel multiplex threshold, the TBF preemption fails. However, the access request for service isnt 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 modifies the GBR in the PFC. At the same time, the BSC initiates a PFC modification procedure, requesting the SGSN to modify the GBR.

3.2 PoC QoS

This section describes the GBFD-119905 PoC QoS feature.

PoC service is a real-time PS service. It requires high bandwidth and low transfer delay. The priorities for scheduling radio resources for PoC and conversational services are higher than those for other services. To meet the high bandwidth requirement, the BSC applies the GBR mechanism from the streaming class. To meet the low transfer delay requirement, the BSC takes several measures to reduce transfer delay, including:

GSM BSS




3-3

Preferentially scheduling radio blocks for the PoC service

Using a low-rate coding scheme

Allocating the same number of uplink and downlink channels to an MS

The BSC must identify whether the service is PoC before service processing. As defined in existing protocols, the BSC cannot identify whether the service is PoC based on the uplink and downlink packet signaling. Instead, based on the QoS attributes, the BSC identifies that the service is PoC if the following conditions are met:

The QoS traffic class is streaming class.

Both uplink and downlink QoS GBRs are greater than POCGBRMIN but smaller than POCGBRMAX.

The QoS transfer delay is lower than POCDELAY.

The Packet Flow Identifier (PFI) value (used to identify a PFC) 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).

To minimize the possibility of incorrect identification, telecom operators must set the parameters such as POCGBRMIN, POCGBRMAX, and POCDELAY based on actual network conditions.

Since the traffic class for the PoC service is the streaming class, the BSC allocates radio blocks to the PoC service based on the GBR requirements of the streaming class to ensure the GBR for the PoC service. To meet the low transfer delay requirement of the PoC service, the BSC takes the following measures:

Uses a lower-rate coding scheme (for example, a coding scheme not higher than MCS-6) to reduce the BER and data retransmission rate.

Determines the logical link control (LLC) protocol data unit (PDU) lifetime based on the transfer delay specified in the QoS attributes.

Increases the delay in releasing uplink and downlink TBFs.

Preferentially schedules radio link control (RLC)/media access control (MAC) radio blocks for the PoC service.

The PoC service requires symmetrical uplink and downlink data flow simultaneously. Therefore, the BSC attempts to allocate the same number of uplink and downlink PDCHs to an MS based on the MS multislot capability. For example, the BSC can use the two channel allocation policies described in Table 3-1 for an MS with multislot class 10.

Table 3-1 Channel allocation policies for an MS with multislot class 10

Channel Allocation Policy

Number of Downlink Timeslots

Number of Uplink Timeslots

Total Number of Timeslots

1 4 1 5

2 3 2 5

According to the policy of allocating the same number of uplink and downlink channels to an MS, the BSC adopts channel allocation policy 2 for the PoC service.

3.3 Conversational QoS

This section describes the GBFD-119906 Conversational QoS feature.

GSM BSS




3-4

Conversational service is a real-time service. It requires low transfer delay. The priorities for scheduling radio resources for PoC and conversational services are higher than those for other services. As defined in the 3GPP specifications, the transfer delay of conversational services must not exceed 80 ms. Generally, the end-to-end transfer delay of VoIP services must not exceed 300 ms. Otherwise, user satisfaction declines.

With the introduction of RTTI, the RTT is reduced from 20 ms to 10 ms on both the Um and Abis interfaces. With the introduction of FANR, the MS response time is minimized even when the Um interface quality is poor. Therefore, the requirement of conversational services for transfer delay (80 ms) can be met in theory after RTTI and FANR are introduced. For details about RTTI and FANR, see the Latency Reduction Feature Parameter Description.

If an MS supports the Latency Reduction feature, and if the BSC supports RTTI and FANR, the BSC allocates a PDCH pair in RTTI configuration to the MS performing conversational services and activates the FANR. In this manner, the conversational services are processed at the lowest possible transfer delay. If an MS does not support the Latency Reduction feature, or if the BSC does not support RTTI or FANR, the BSC allocates PDCHs in BTTI configuration to the MS performing conversational services. In this manner, the BSC allows the packet access of conversational services but the conversational services may be processed at a high transfer delay.

In addition to introducing RTTI and FANR, the BSC takes the following measures to reduce the transfer delay of conversational services:

Limits the maximum PDCH multiplexing rate to reduce the delay in scheduling radio blocks.

The thresholds for both uplink and downlink PDCH multiplexing rates in RTTI configuration are determined by the RTTIPDCHMULTIPLEXTHRESH parameter. If the PDCH multiplexing rate is equal to the threshold, TBFs cannot be multiplexed on this PDCH any more. The maximum PDCH multiplexing rate is limited. Therefore, the period for scheduling radio blocks on PDCHs is ensured so that the delay in scheduling radio blocks is limited to an allowed range.

Uses specific link adaptation/incremental redundancy (LA/IR) algorithms to reduce the number of data blocks to be retransmitted at the RLC layer.

A new table about the mapping between Bit Error Probability (BEP) measurement reports and coding schemes is used for conversational services. As a result, conversational services use low-rate coding schemes when the Um interface quality is poor, reducing the BER and data retransmission rate.

The characteristics of Huawei conversational QoS are as follows:

Currently, RTTI and FANR are supported only when the Abis interface uses IP or HDLC transmission. Therefore, conversational QoS is better ensured in IP or HDLC transmission mode than in other transmission modes. In addition, RTTI and FANR must be enabled or disabled simultaneously.

Conversational services do not support resource preemption or queuing.

Data transmission of conversational services does not support the RLC unacknowledged mode. Instead, conversational services use specific LA/IR algorithms to reduce the data retransmission rate.

3.4 PS Service in Priority and QoS ARP&THP

This section describes the GBFD-119907 PS Service in Priority and GBFD-119902 QoS ARP&THP features.

the BSC configures a priority for a user based on the traffic class, ARP, and THP in the QoS attributes if PSDIFSERVICESUP is set to SUPPORT(Support). as listed in Table 3-2, Table 3-3. The user priorities in the table are default values.

If the PFC procedures can be used, the BSC obtains QoS parameters by using the PFC procedures. Table 3-2 lists the user priority configuration.

GSM BSS




3-5

Table 3-2 User priority configuration

Traffic Class and THP ARP Level 1 ARP Level 2 ARP Level 3

Interactive services

THP1 10 6 4

THP2 8 4 3

THP3 6 3 2

Background services 4 2 1

If the PFC procedures cannot be used, the BSC uses the Precedence field of the IE QoS Profile in the DL UNITDATA message to map onto the ARP priority level. Table 3-3 lists the user priority configuration.

Table 3-3 User priority configuration

Traffic Class and THP ARP Level 1 ARP Level 2 ARP Level 3

BE services 8 4 2

The user priority weight is a factor for TBF scheduling and is configured by setting parameters. The principles for configuring user priority weight are as follows:

For different traffic classes with the same ARP level, the BSC configures user priority weight in descending order as follows: interactive services, background services, and BE services. For the same traffic class, the user priority weight for services is proportional to the ARP level or THP.

For interactive services, the BSC configures the user priority weight based on the ARP level and THP. The principles for configuring user priority weight are as follows:

For interactive services with the same ARP level, the user priority weight is proportional to the THP.

For interactive services with the same THP, the user priority weight is proportional to the ARP level.

The parameters used for configuring user priority weight for interactive services are as follows:

THP1ARP1PRIWEIGHT

THP1ARP2PRIWEIGHT

THP1ARP3PRIWEIGHT

THP2ARP1PRIWEIGHT

THP2ARP2PRIWEIGHT

THP2ARP3PRIWEIGHT

THP3ARP1PRIWEIGHT

THP3ARP2PRIWEIGHT

THP3ARP3PRIWEIGHT

For background services, the BSC configures user priority weight based on the ARP level. A higher ARP level indicates greater user priority weight. The parameters used for configuring user priority weight for background services are as follows:

BKGARP1PRIWEIGHT

BKGARP2PRIWEIGHT

BKGARP3PRIWEIGHT

GSM BSS




3-6

For BE services, the BSC configures user priority weight based on the ARP level. A higher ARP level indicates greater user priority weight. The parameters used for configuring user priority weight for BE services are as follows:

BEARP1PRIWEIGHT

BEARP2PRIWEIGHT

BEARP3PRIWEIGHT

The BSC schedules radio blocks for services based on the user priority only if the following conditions are met:

MACSCHEDULETYPE is set to PFSCHEDULE(Proportion Fair Scheduling).

PSDIFSERVICESUP is set to SUPPORT(Support).

The current TBF rate is higher than or equal to the GBR specified by DLMINGUARANTEERATE.

The current TBF rate refers to the current filtering rate of the TBF carrying the user data. If a TBF uses a PDCH pair in RTTI configuration, the current TBF rate equals the filtering rate of all PDCHs in the PDCH group where the TBF is located during radio block scheduling. If a TBF uses double carriers in the downlink, the current TBF rate equals the filtering rate of the PDCHs in the PDCH group for the two carriers during radio block scheduling. When calculating the current TBF rate, the BSC determines the timer length for rate filtering based on the number of radio block scheduling periods specified by min(RATEFILTERTIMEWIN the scheduling radio blocks number of the TBF ).

If this parameter is set to a larger value:

The timer length for rate filtering is longer.

The weight of the instantaneous rate in the current rate calculation is smaller.

The weight of historical rates in the current rate calculation is greater.

If this parameter is set to a smaller value:

The timer length for rate filtering is shorter.

The weight of the instantaneous rate in the current rate calculation is greater.

The weight of historical rates in the current rate calculation is smaller.

The BSC provides differentiated QoS for different users based on the user priority and the Proportional Fair (PF) algorithm. A user with higher priority has a higher data rate and more scheduling opportunities, so the bandwidth and transfer delay requirements of higher-priority users are preferentially met.

The GBR of interactive, background, and BE services is specified by DLMINGUARANTEERATE. The BSC schedules radio blocks based on the setting of DLMINGUARANTEERATE, which specifies the minimum guaranteed downlink rate for users to maintain PS services. The higher the minimum guaranteed downlink rate is, the faster the data rate is increased and the better the user experience is. An extremely high minimum guaranteed downlink rate, however, affects the GBR assurance of streaming services. An MS with a lower current TBF rate has greater scheduling weight, so the minimum rate for services processed by this MS is preferentially met to ensure service continuity.

3.5 GPRS/EGPRS Time slot multiplexing priority

This section describes the GBFD-119506 GPRS/EGPRS Time slot multiplexing priority feature.

When a GPRS user and an EGPRS user are multiplexed on the same PDCH, the scheduling priority for the EGPRS user can be adjusted.

If the EGPRS user has a higher priority than the GPRS user, the downlink rate of the EGPRS user increases. This improves the EGPRS user experience and increases system throughput.

GSM BSS




3-7

Uplink and downlink differentiated QoS can be implemented based on the GPRS/EGPRS user priority as follows:

Uplink differentiated QoS based on the GPRS/EGPRS user priority can be enabled by setting EgprsPriWeight to a value except 1.

A GPRS user can decode only the Uplink State Flag (USF) in GMSK modulation mode. Therefore, if an EGPRS user is scheduled in the downlink during uplink scheduling, the EGPRS user is preferentially scheduled in the uplink. This reduces the opportunities of using downlink radio blocks in Gaussian minimum shift-frequency keying (GMSK) modulation mode for the EGPRS user, increasing both the uplink and downlink rates for the EGPRS user and system throughput.

Conversational, streaming, interactive, background, and BE services require uplink differentiated QoS based on the GPRS/EGPRS user priority.

Downlink differentiated QoS based on the GPRS/EGPRS user priority can be enabled by setting MACSCHEDULETYPE to PFSCHEDULE(Proportion Fair Scheduling), PSDIFSERVICESUP to SUPPORT(Support), FORBIDEDGU to OPEN(Open), and EgprsPriWeight to a value except 1. EgprsPriWeight specifies the scheduling priority for an EGPRS user when the EGPRS user and a GPRS user are multiplexed on the same PDCH.

During downlink scheduling, if a GPRS user and an EGPRS user are multiplexed on the same PDCH, the downlink radio blocks sent to the EGPRS user must be in GMSK modulation mode when the BSC schedules uplink radio blocks for the GPRS user. This reduces the downlink rate for the EGPRS user. If the scheduling priority for the GPRS user is lower than that for the EGPRS user, the number of times that the EGPRS user uses downlink radio blocks in GMSK modulation mode reduces because uplink scheduling times for the GPRS user are less than those for the EGPRS user. In addition, downlink scheduling times for the EGPRS user are more than those for the GPRS user. This increases both the downlink rate for the EGPRS user and system throughput.

Interactive, background, and BE services require downlink differentiated QoS based on the GPRS/EGPRS user priority.

3.6 IM Service Efficiency Improvement

This section describes the GBFD-511603 IM Service Efficiency Improvement feature.

Currently, IM services account for a large portion of GSM services, but the TBF transmission duration is short because of low throughput. As a result, procedures in which no data block is transmitted, such as TBF establishment, delayed downlink TBF release, and TBF release, account for a large part of a TBF's life cycle. This wastes channel resources.

With this feature, the BSC provides the following functions to increase channel usage:

Identifies IM services from various PS services. (For example, the BSC identifies mobile QQ, Fetion, PIN, and Whats APP as IM services.)

Allocates fewer channels to process IM services based on configuration policies.

Multiplexes IM services on a PDCH.

Shortens the delay for releasing downlink TBFs.

Reduces the priority for scheduling IM services.

With this feature, some Um interface resources occupied by IM services can be released by setting resource optimization parameters. This helps increase the usage of Um interface resources.

3.7 Web Browsing Service Efficiency Improvement

This section describes the GBFD-511604 Web Browsing Service Efficiency Improvement feature.

GSM BSS




3-8

Currently, web browsing services account for a large portion of GSM services. Such services have medium throughput and a high requirement for delay.

With this feature, the BSC provides the following functions to improve the user experience with web browsing services:

Identifies web browsing services from various PS services.

Allocates an appropriate number of channels to process web browsing services.

Sets an appropriate multiplexing weight.

Sets an appropriate delay for releasing downlink TBFs.

Increases the priority for scheduling web browsing services.

With this feature, the Um-interface resource usage of web browsing services can be adjusted by setting resource optimization parameters. This helps improve user experience.

3.8 Email Service Efficiency Improvement

This section describes the GBFD-511605 Email Service Efficiency Improvement feature.

Currently, email services account for a portion of GSM services. Such services have high throughput and a low requirement for delay.

With this feature, the BSC provides the following functions to improve user experience with email services or to increase the efficiency of PDCHs to carry TBFs for email services:

Identifies email services from various PS services.

Allocates an appropriate number of channels to process email services.

Sets an appropriate multiplexing weight.

Sets an appropriate delay for releasing downlink TBFs.

Increases the priority for scheduling email services.

With this feature, the Um-interface resource usage of email services can be adjusted by setting resource optimization parameters. This helps improve user experience.

3.9 Streaming Media Service Resource Balancing

This section describes the GBFD-511606 Streaming Media Service Resource Balancing feature.

Currently, streaming media services account for a small portion of GSM services. Such services have a large throughput and a high requirement for delay, but the spectral efficiency of GSM networks is limited. Therefore, streaming media services are not recommended for GSM networks.


Identifies streaming media services from various PS services.

Reduces the number of PDCHs allocated to streaming media services.

Multiplexes more streaming media services on a PDCH.


Reduces the priority for scheduling streaming media services.

With this feature, the Um-interface resource usage of streaming media services can be adjusted by setting resource optimization parameters.

GSM BSS




3-9

3.10 P2P Resource Balancing

This section describes the GBFD-511607 P2P Resource Balancing feature.

Currently, P2P services account for a small portion of GSM services. Such services have a large throughput, but the spectral efficiency of GSM networks is limited. Therefore, P2P services are not recommended for GSM networks.


Identifies P2P services from various PS services.

Reduces the number of PDCHs allocated to P2P services.

Multiplexes more P2P services on a PDCH.


Reduces the priority for scheduling P2P services.

With this feature, the Um-interface resource usage of P2P services can be adjusted by setting resource optimization parameters.

GSM BSS

GPRS/EGPRS QoS 4 Related Features



4-1

4 Related Features

Table 4-1 Related features

Feature Prerequisite Feature Mutually Exclusive Feature Affected Feature

Streaming QoS(GBR)

GBFD-114101 GPRS

GBFD-114201 EGPRS

None None

QoS ARP&THP GBFD-114101 GPRS

GBFD-114201 EGPRS

GBFD-119506 GPRS/EGPRS Time slot multiplexing priority


None

PoC QoS GBFD-119901 Streaming QoS(GBR)

None None

Conversational QoS

GBFD-114101 GPRS

GBFD-114201 EGPRS

None If the Conversational QoS feature is used with the feature GBFD-510805 Latency Reduction, the transfer delay for conversational services is minimized.

GPRS/EGPRS Time slot multiplexing priority

GBFD-114101 GPRS

GBFD-114201 EGPRS


GBFD-119902 QoS ARP&THP None

PS Service in Priority

GBFD-114101 GPRS

GBFD-114201 EGPRS

GBFD-119902 QoS ARP&THP None


GBFD-114101 GPRS

GBFD-114201 EGPRS

The ARP1 scheduling weight, ARP2 scheduling weight, and ARP3 scheduling weight functions of this feature depend on the GBFD-119902 QoS ARP&THP or GBFD-119907 PS Service in Priority feature.

None IMPDCHMULTIPLEXWEIGHT becomes ineffective when this feature and GBFD-119407 Active TBF Allocation are enabled simultaneously.

GSM BSS




4-2



GBFD-114101 GPRS

GBFD-114201 EGPRS


None WEBPDCHMULTIPLEXWEIGHT becomes ineffective when this feature and GBFD-119407 Active TBF Allocation are enabled simultaneously.


GBFD-114101 GPRS

GBFD-114201 EGPRS


None EMAILPDCHMULTIPLEXWEIGHT becomes ineffective when this feature and GBFD-119407 Active TBF Allocation are enabled simultaneously.


GBFD-114101 GPRS

GBFD-114201 EGPRS


None STREAMPDCHMULTIPLEXWEIGHT becomes ineffective when this feature and GBFD-119407 Active TBF Allocation are enabled simultaneously.

GSM BSS




4-3



GBFD-114101 GPRS

GBFD-114201 EGPRS


None P2PPDCHMULTIPLEXWEIGHT becomes ineffective when this feature and GBFD-119407 Active TBF Allocation are enabled simultaneously.

GSM BSS

GPRS/EGPRS QoS 5 Impact on the Network



5-1

5 Impact on the Network

5.1 Streaming QoS(GBR)

5.1.1 Impact on System Capacity

N/A

5.1.2 Impact on Network Performance

N/A

5.2 QoS ARP&THP


N/A


N/A

5.3 PoC QoS


N/A


N/A

5.4 Conversational QoS


N/A


N/A

5.5 GPRS/EGPRS Time slot multiplexing priority


None


When a GPRS user and an EGPRS user are multiplexed on the same PDCH, the downlink rate of the EGPRS user can be increased by raising the scheduling priority of the EGPRS user. This improves the EGPRS user experience and increases system throughput.

GSM BSS




5-2

5.6 PS Service in Priority


N/A


N/A

5.7 IM Service Efficiency Improvement


The impact of the IM Service Efficiency Improvement feature on system capacity is as follows:

The number of activated PDCHs is reduced by about 15%.

The efficiency of PDCHs to carry TBFs (data rate per PDCH at the RLC layer) is expected to increase by about 20%.


In hot spots for PS services, the throughput on a single PDCH is about 3 to 5 kbit/s, IM services account for more than 40% of all PS services, and the data flow for IM services accounts for about 10% of the data flow for all PS services. During busy hours, the proportion of CS services is high, and the CS services using TCHHs accounts for about 30%. In addition, the TCH congestion rate is about 1%.

In such hot spots, the IM Service Efficiency Improvement feature brings the following gains:

Reduces the number of activated PDCHs by about 15%.

Increases the efficiency for PDCHs to carry TBFs (data rate per PDCH at the RLC layer) by about 20%.

Decreases the proportion of the CS services using TCHHs by 15% and increases the HQI for CS services by 0.3%, which improves the MOS.

5.8 Web Browsing Service Efficiency Improvement


This feature improves the efficiency for PDCHs to carry TBFs for web browsing services.


The user experience with web browsing services is improved.

5.9 Email Service Efficiency Improvement


This feature improves the efficiency for PDCHs to carry TBFs for email services.


The user experience with email services is improved and the efficiency of PDCHs to carry TBFs for email services is increased.

GSM BSS




5-3

5.10 Streaming Media Service Resource Balancing


This feature improves the efficiency for PDCHs to carry TBFs for streaming media services.


Some channels occupied by streaming media services are released. Therefore, the user experience with other PS services is improved.

5.11 P2P Resource Balancing


This feature improves the efficiency for PDCHs to carry TBFs for P2P services.


Some channels occupied by P2P services are released. Therefore, the user experience with other PS services is improved.

GSM BSS

GPRS/EGPRS QoS 6 Engineering Guidelines



6-1

6 Engineering Guidelines

6.1 When to Use GPRS/EGPRS QoS

6.1.1 Streaming QoS(GBR)

If you intend to meet the bandwidth requirements and improve the service experience for high-priority users when radio resources on the Um interface are insufficient, use the Streaming QoS(GBR) feature.

6.1.2 QoS ARP&THP

If you intend to configure priority weight for radio resource allocation based on the service type and user priority that allows high-priority users to use higher bandwidth, enjoy higher data rates, and experience better service quality, use the QoS ARP&THP feature.

6.1.3 PoC QoS

If you intend to enhance the real-time performance and voice quality of PoC services and improve user experience, use the PoC QoS feature. This feature can help you gain competitive edges, implement differentiated QoS for PS users, and increase your service revenue.

6.1.4 Conversational QoS

With the rapid development of IP-based services, such as VoIP, PoC, and Gaming, users have an increasingly high requirement for transfer delay. If you want users to enjoy better QoS and service experience, use the Conversational QoS feature.

6.1.5 GPRS/EGPRS Time slot multiplexing priority

If you intend to increase the data rates for EGPRS users to improve user experience with PS services and system throughput, use the GPRS/EGPRS Time slot multiplexing priority feature.

6.1.6 PS Service in Priority

Use the PS Service in Priority feature in areas where large numbers of PDCHs are occupied by PS services.

6.1.7 IM Service Efficiency Improvement

In areas with a large proportion of IM services, use the IM Service Efficiency Improvement feature and set radio resource optimization parameters for IM services based on the service evaluation result.

6.1.8 Web Browsing Service Efficiency Improvement

In areas with a large proportion of web browsing services, use the Web Browsing Service Efficiency Improvement feature and set radio resource optimization parameters for web browsing services based on the service evaluation result.

6.1.9 Email Service Efficiency Improvement

In areas with a large proportion of email services, use the Email Service Efficiency Improvement feature and set radio resource optimization parameters for email services based on the service evaluation result.

GSM BSS




6-2

6.1.10 Streaming Media Service Resource Balancing

In areas with a large proportion of streaming media services, use the Streaming Media Service Resource Balancing feature and set radio resource optimization parameters for streaming media services based on the service evaluation result.

6.1.11 P2P Resource Balancing

In areas with a large proportion of P2P services, use the P2P Resource Balancing feature and set radio resource optimization parameters for P2P services based on the service evaluation result.

6.2 Information to Be Collected

None

6.3 Network Planning

6.3.1 RF Planning

N/A

6.3.2 Network Topology

N/A

6.3.3 Hardware Planning

The hardware planning policies are as follows:

PS service processing boards and Gb interface boards need to be configured.

NIUa boards need to be configured for the following features:






A single NIUa board supports a throughput of 3.2 Gbit/s on the user plane. It can identify more than 800 protocols, and therefore is capable of identifying all PS services processed by a BSC. To ensure system reliability however, two NIUa boards are recommended.

6.4 Overall Deployment Procedure

None

6.5 Deploying Streaming QoS(GBR)

For details about how to activate, verify, and deactivate this feature, see Configuring Streaming QoS(GBR).

6.6 Deploying QoS ARP&THP

For details about how to activate, verify, and deactivate this feature, see Configuring QoS ARP&THP.

GSM BSS




6-3

6.7 Deploying PoC QoS

For details about how to activate, verify, and deactivate this feature, see Configuring PoC QoS.

6.8 Deploying Conversational QoS

None

6.9 Deploying GPRS/EGPRS Time slot multiplexing priority

For details about how to activate, verify, and deactivate this feature, see Configuring Timeslot Multiplexing Priority for GPRS/EGPRS User.

6.10 Deploying PS Service in Priority

For details about how to activate, verify, and deactivate this feature, see Configuring PS Service in Priority.

6.11 Deploying IM Service Efficiency Improvement

For details about how to activate, verify, and deactivate this feature, see Configuring IM Service Efficiency Improvement.

6.12 Deploying Web Browsing Service Efficiency Improvement

For details about how to activate, verify, and deactivate this feature, see Configuring Web Browsing Service Efficiency Improvement.

6.13 Deploying Email Service Efficiency Improvement

For details about how to activate, verify, and deactivate this feature, see Configuring Email Service Efficiency Improvement.

6.14 Deploying Streaming Media Service Resource Balancing

For details about how to activate, verify, and deactivate this feature, see Configuring Streaming Media Service Resource Balancing.

6.15 Deploying P2P Resource Balancing

For details about how to activate, verify, and deactivate this feature, see Configuring P2P Resource Balancing.

6.16 Performance Optimization

None

6.17 Troubleshooting

None

GSM BSS

GPRS/EGPRS QoS 7 Parameters



7-1

7 Parameters

Table 7-1 Parameter description

Parameter ID NE MML Command Description

BEARP1PRIWEIGHT BSC6900 SET GCELLPSCHM Meaning: Priority weight for ARP1 in Best Effort (BE) services. The value of this parameter determines the number of budget blocks and the block scheduling priority.

GUI Value Range: 1~10

Actual Value Range: 1~10

Default Value: 8

Unit: None

BEARP2PRIWEIGHT BSC6900 SET GCELLPSCHM Meaning: Priority weight for ARP2 in BE services. The value of this parameter determines the number of budget blocks and the block scheduling priority.



Default Value: 4

Unit: None

BEARP3PRIWEIGHT BSC6900 SET GCELLPSCHM Meaning: Priority weight for ARP3 in BE services. The value of this parameter determines the number of budget blocks and the block scheduling priority.



Default Value: 2

Unit: None

BKGARP1PRIWEIGHT BSC6900 SET GCELLPSCHM Meaning: Priority weight for ARP1 in background services. This parameter determines the number of budget blocks and the block scheduling priority.



Default Value: 4

Unit: None

GSM BSS




7-2


BKGARP2PRIWEIGHT BSC6900 SET GCELLPSCHM Meaning: Priority weight for ARP2 in background services. The value of this parameter determines the number of budget blocks and the block scheduling priority.



Default Value: 2

Unit: None

BKGARP3PRIWEIGHT BSC6900 SET GCELLPSCHM Meaning: Priority weight for ARP3 in background services. The value of this parameter determines the number of budget blocks and the block scheduling priority.



Default Value: 1

Unit: None

DLMINGUARANTEERATE BSC6900 SET GCELLPSOTHERPARA

Meaning: This parameter indicates the minimum guaranteed rate in downlink to ensure the normal processing of PS services of users.



Default Value: 10

Unit: None

EMAILPDCHMULTIPLEXWEIGHT BSC6900 SET GCELLPSDIFFSERVICE

Meaning: PDCH multiplexing weight for email services.

The load in a cell is calculated as follows: (Average number of MSs processing IM services multiplexed on all PDCHs x IM PDCH Multiplexing Weight/100) + (Average number of MSs processing web browsing services multiplexed on all PDCHs x Web Browsing PDCH

GSM BSS




7-3


Multiplexing Weight/100) + (Average number of MSs processing email services multiplexed on all PDCHs x Email PDCH Multiplexing Weight/100) + (Average number of MSs processing streaming media services multiplexed on all PDCHs x Streaming Media PDCH Multiplexing Weight/100) + (Average number of MSs processing P2P services multiplexed on all PDCHs x P2P PDCH Multiplexing Weight/100) + Average number of MSs processing other services multiplexed on all PDCHs.



Default Value: 100

Unit: None

EgprsPriWeight BSC6900 SET GCELLPSOTHERPARA

Meaning: Scheduling priority for EGPRS users when being multiplexed with GPRS users onto PDCHs. The larger the value of this parameter, the higher the priority for EGPRS users.



Default Value: 1

Unit: None

FORBIDEDGU BSC6900 SET BSCPSSOFTPARA Meaning: Whether to allow downlink EGPRS TBFs and uplink GPRS TBFs to be multiplexed onto the same channel.

If this parameter is set to OPEN(Open), downlink EGPRS TBFs and uplink GPRS TBFs can be multiplexed onto the same EGPRS normal channel.

Note that downlink EGPRS TBFs and uplink GPRS

GSM BSS




7-4


TBFs can be multiplexed onto the same EGPRS priority channel when "EnPDAdminOpt" is set to ON(On) and "EnEdgePriGprs" is set to YES(Yes).

If this parameter is set to CLOSE(Close), downlink EGPRS TBFs and uplink GPRS TBFs cannot be multiplexed onto the same channel.

GUI Value Range: OPEN(Open), CLOSE(Close)

Actual Value Range: OPEN, CLOSE

Default Value: OPEN(Open)

Unit: None

GBRQOS BSC6900 SET GCELLPSOTHERPARA

Meaning: Obtains the QoS parameter from the Aggregate BSS QoS Profile (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

Default Value: NO(Not Support)

Unit: None

IMPDCHMULTIPLEXWEIGHT BSC6900 SET GCELLPSDIFFSERVICE

Meaning: PDCH multiplexing weight for IM services.

The load in a cell is calculated as follows: (Average number of MSs processing IM services multiplexed on all PDCHs x IM PDCH Multiplexing

GSM BSS




7-5


Weight/100) + (Average number of MSs processing web browsing services multiplexed on all PDCHs x Web Browsing PDCH Multiplexing Weight/100) + (Average number of MSs processing email services multiplexed on all PDCHs x Email PDCH Multiplexing Weight/100) + (Average number of MSs processing streaming media services multiplexed on all PDCHs x Streaming Media PDCH Multiplexing Weight/100) + (Average number of MSs processing P2P services multiplexed on all PDCHs x P2P PDCH Multiplexing Weight/100) + Average number of MSs processing other services multiplexed on all PDCHs.



Default Value: 100

Unit: None

MACSCHEDULETYPE BSC6900 SET GCELLPSOTHERPARA

Meaning: Type of the MAC scheduling algorithm.

The value "Round Robin Schedule" indicates that all TBFs in the queue that are multiplexed on one PDCH are scheduled according to time sequence.

The value "Proportion Fair Scheduling" indicates that the TBFs scheduling is based on a universal formula and depends on factors such as user rate, Um interface quality, and the number of PDCHs occupied by users.

The value "Scheduling Based On Carrier to Interference Ratio" indicates that the TBF

GSM BSS




7-6


scheduling is based on a universal formula and depends on the Um quality.

The value "Scheduling Based On Budget" indicates that the TBF scheduling is based on a universal formula and depends on the number of users and user priority.

GUI Value Range: RRSCHEDULE(Round Robin Schedule), PFSCHEDULE(Proportion Fair Scheduling), CIRSCHEDULE(Scheduling Based On Carrier to Interference Ratio), BUDGET(Scheduling Based On Budget)

Actual Value Range: RRSCHEDULE, PFSCHEDULE, CIRSCHEDULE, BUDGET

Default Value: BUDGET(Scheduling Based On Budget)

Unit: None

OccupyStreamingSwitch BSC6900 SET GCELLPSOTHERPARA

Meaning: When the PDCHs are insufficient, the streaming service with 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

Default Value: OFF(OFF)

GSM BSS




7-7


Unit: None

P2PPDCHMULTIPLEXWEIGHT BSC6900 SET GCELLPSDIFFSERVICE

Meaning: PDCH multiplexing weight for P2P services.

The load in a cell is calculated as follows: (Average number of MSs processing IM services multiplexed on all PDCHs x IM PDCH Multiplexing Weight/100) + (Average number of MSs processing web browsing services multiplexed on all PDCHs x Web Browsing PDCH Multiplexing Weight/100) + (Average number of MSs processing email services multiplexed on all PDCHs x Email PDCH Multiplexing Weight/100) + (Average number of MSs processing streaming media services multiplexed on all PDCHs x Streaming Media PDCH Multiplexing Weight/100) + (Average number of MSs processing P2P services multiplexed on all PDCHs x P2P PDCH Multiplexing Weight/100) + Average number of MSs processing other services multiplexed on all PDCHs.



Default Value: 100

Unit: None

PFCSUP BSC6900 ADD NSE

MOD NSE

Meaning: Whether the NSE supports the Packet Flow Context (PFC) procedure that can improve Quality of Service (QoS) of packet services.

In SGSN Pool scenario, the PFC procedure will take effect when the following conditions are met:

All the NSEs to which all

GSM BSS




7-8


the PTP BVCs in the cell belong support PFC (that is, "PFC Support" is set to YES).

The SGSN supports PFC.

The "Support GBR QoS" parameter in the "SET GCELLPSOTHERPARA" command is set to YES.

GUI Value Range: NO(No Support), YES(Support)

Actual Value Range: NO, YES

Default Value: NO(No Support)

Unit: None

POCDELAY BSC6900 SET GCELLPSOTHERPARA

Meaning: Maximum transmission delay of the POC service (push to talk over 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.



Default Value: 650

Unit: None

POCGBRMAX BSC6900 SET GCELLPSOTHERPARA

Meaning: Maximum bandwidth of the POC service (push to talk over cellular). The transmission delay of the POC service must be relatively small. The network side must support the function of

GSM BSS




7-9


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 lower than the maximum bandwidth of the POC service.



Default Value: 16

Unit: None

POCGBRMIN BSC6900 SET GCELLPSOTHERPARA

Meaning: Minimum bandwidth of the POC service (push to talk over 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, GbrValue in the ABQP must be larger than the minimum bandwidth of the POC service.



Default Value: 6

Unit: None

PSDIFSERVICESUP BSC6900 SET GCELLPSOTHERPARA

Meaning: This parameter indicates whether the feature "PS Service in Priority" is supported.

GUI Value Range: NOTSUPPORT(Not Support), SUPPORT(Support)

Actual Value Range: NOTSUPPORT, SUPPORT

GSM BSS




7-10


Default Value: NOTSUPPORT(Not Support)

Unit: None

RATEFILTERTIMEWIN BSC6900 SET GCELLPSOTHERPARA

Meaning: This parameter indicates the block periods selected as the time length 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.



Default Value: 50

Unit: None

RTTIPDCHMULTIPLEXTHRESH BSC6900 SET GCELLPSCHM Meaning: Maximum number of RTTI TBFs that can be multiplexed on the 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".



Default Value: 30

Unit: None

SGSNR BSC6900 SET GCELLPSBASE Meaning: Protocol version supported by the SGSN

GUI Value Range: 0( Release 98 or older),

GSM BSS




7-11


1(Release 99 onwards)

Actual Value Range: Release 98 or older, Release 99 onwards

Default Value: 1(Release 99 onwards)

Unit: None

STREAMPDCHMULTIPLEXWEIGHT

BSC6900 SET GCELLPSDIFFSERVICE

Meaning: PDCH multiplexing weight for streaming media services.

The load in a cell is calculated as follows: (Average number of MSs processing IM services multiplexed on all PDCHs x IM PDCH Multiplexing Weight/100) + (Average number of MSs processing web browsing services multiplexed on all PDCHs x Web Browsing PDCH Multiplexing Weight/100) + (Average number of MSs processing email services multiplexed on all PDCHs x Email PDCH Multiplexing Weight/100) + (Average number of MSs processing streaming media services multiplexed on all PDCHs x Streaming Media PDCH Multiplexing Weight/100) + (Average number of MSs processing P2P services multiplexed on all PDCHs x P2P PDCH Multiplexing Weight/100) + Average number of MSs processing other services multiplexed on all PDCHs.



Default Value: 100

Unit: None

THP1ARP1PRIWEIGHT BSC6900 SET GCELLPSCHM Meaning: Priority weight for the combination of THP1 and ARP1 in interactive services. The value of this

GSM BSS




7-12


parameter determines the number of budget blocks and the block scheduling priority.



Default Value: 10

Unit: None

THP1ARP2PRIWEIGHT BSC6900 SET GCELLPSCHM Meaning: Priority weight for the combination of THP1 and ARP2 in interactive services. This parameter determines the number of budget blocks and the block scheduling priority.



Default Value: 6

Unit: None




Default Value: 4

Unit: None




Default Value: 8

Unit: None

THP2ARP2PRIWEIGHT BSC6900 SET GCELLPSCHM Meaning: Combination of the THP2 and ARP2 priority in the Interactive service. THP2-ARP2 priority weight

GSM BSS




7-13


determines the number of the budget blocks and the block scheduling priority.



Default Value: 4

Unit: None




Default Value: 3

Unit: None




Default Value: 6

Unit: None




Default Value: 3

Unit: None

THP3ARP3PRIWEIGHT BSC6900 SET GCELLPSCHM Meaning: Priority weight for the combination of THP3 and ARP3 in interactive services. This parameter determines the number of

GSM BSS




7-14


budget blocks and the block scheduling priority

GPRSEGPRS QoS(GBSS14.0_01)

Documents

Transcript of GPRSEGPRS QoS(GBSS14.0_01)