PLR BR9.0 Quality of Service Improvements

sInformation and Communication Mobile

Planning Rule

QoS improvements: RT TBF and EDA TBF multiplexing.

Release BR9.0

FRS 89997

Version number 1.0

17-03-2006

Offer Level

IUS 1.0

For internal use only!

Issued byComunicationsCom MN PG NM NE 1

St.-Martinstrasse 76D-81541 Munich© SIEMENS AG 2006

The reproduction, transmission or use of this document or its contents is not permitted without express written authority. Offenders will be liable for damages. All rights, including rights created by patent grant or registration of a utility model or design, are reserved. Technical modifications possible. Technical specifications and features are binding only in so far as they are specifically and expressly agreed upon in a written contract.

Siemens AG Planning Rule Released by: Com MN PG NM NE 1

Process Owners

Communications Version 1.0 document.doc

Mobile For internal use only! Date: 17.03.2006

Author: Szymon NowakLukasz Koszulanski Page 1 of 23 page(s)


Contents

1 GENERAL INFORMATION.............................................................................................4

1.1 AUTHORS.....................................................................................................................41.2 INTRODUCTION............................................................................................................41.3 HISTORY......................................................................................................................41.4 REFERENCES................................................................................................................41.5 ABBREVIATIONS, DEFINITIONS AND EXPLANATIONS..................................................5

2 GENERAL FEATURE RELATED PART....................................................................7

2.1 FUNCTIONAL FEATURE DESCRIPTION.........................................................................72.1.1 BR 8.0 implementation........................................................................................72.1.2 BR 9.0 implementation........................................................................................8

2.1.2.1 Basic idea of BR9.0 QoS improvements........................................................92.2 PARAMETERS.............................................................................................................142.3 MOTIVATION TO INTRODUCE THE FEATURE.............................................................142.4 INTERDEPENDENCIES WITH OTHER FEATURES..........................................................162.5 INTERDEPENDENCIES WITH OTHER TECHNOLOGIES...................................................162.6 FURTHER ISSUES........................................................................................................16

2.6.1 Discussion of OEM Products............................................................................162.6.2 Norms................................................................................................................16

2.7 OPEN ISSUES..............................................................................................................16

3 DIMENSIONING ASPECTS (ACQUISITION LEVEL)...........................................17

3.1 AFFECTED SERVICES AND QUALITY OF SERVICE DEFINITIONS, USED TRAFFIC MODELS.................................................................................................................................193.2 RELEVANT BSS SPECIFICATION AND CONFIGURATION LIMITS................................193.3 IMPACT ON EXISTING DIMENSIONING METHODS......................................................193.4 SUMMARY OF DIMENSIONING RULES........................................................................193.5 RULES FOR PHASE-ORIENTED OFFERS......................................................................193.6 IMPACT ON EXISTING PLANNING MANUALS (PMNS)...............................................193.7 IMPACT ON EXISTING OFFER TOOLS, POSSIBLE WORKAROUNDS..............................20

3.7.1 GERAN Offer tool.............................................................................................203.7.2 QandD Offer Tool.............................................................................................20

3.8 OPEN ISSUES..............................................................................................................20

4 IMPLEMENTATION ASPECTS (REALISATION LEVEL)...................................21

4.1 ORDERING.................................................................................................................214.1.1 Affected Services and Quality of Service Definitions, used Traffic Models.....214.1.2 Relevant BSS Specification and Configuration Limits......................................214.1.3 Impact on Existing Planning Methods..............................................................21


Process Owners





4.1.4 Summary of Planning Rules..............................................................................214.1.5 Rules for Phase-Oriented Planning..................................................................214.1.6 Impact on existing Planning Manuals (PMNs).................................................214.1.7 Impact on existing Planning Tools, possible Workarounds..............................21

4.2 IMPLEMENTATION......................................................................................................214.2.1 Feature introduction strategy...........................................................................214.2.2 Database Generation........................................................................................21

4.2.2.1 Interdependencies with Parameters of Related Features..............................214.2.3 Installation requirements..................................................................................214.2.4 Evaluation of implementation...........................................................................22

4.2.4.1 Acceptance test procedures...........................................................................224.2.4.2 Performance measurements and counters (O3)............................................224.2.4.3 Initial Tuning................................................................................................22

4.2.5 Impact on existing Network Optimisation Use Cases (O3)..............................224.2.6 Impact on existing Network Optimisation Tools (O3)......................................22

4.3 Open issues...............................................................................................................22


Process Owners





1 General Information

1.1 Authors

S. Nowak

L. Koszulanski: Support of MS Multislot Classes 30-33

1.2 Introduction

This is a Siemens internal document and thus not intended to be handed out to customers.

The main goal of the document is to illustrate the features, the parameterization and to give criteria for the deciding of the parameter values. Additional goal is to define the impact of the features on planning, dimensioning and performance of a mobile radio network.

The reader is assumed to be familiar with the GPRS (General Packet Radio System)/EGPRS (EDGE GPRS) service model and the QoS (Quality of Service) model for GPRS.

Persons involved in the document’s generation:

Szymon Nowak

[email protected]

Lukasz Koszulanski

[email protected]

1.3 History

Version Date Chapter Changes / Reasons

0.1 draft 26/09/05 All Draft version of the document

0.2 AFI 24/10/05 All AFI version reviewed internally within NE. Minor changes introduced.

1.0 IUS 17/03/06 All Document accepted by TS without any comments.

1.4 References


Process Owners




mailto:[email protected]

mailto:[email protected]


[PLR 88930-87477] “(E)GPRS enhancements: Extended Dynamic Allocation, Overheating Management, Extended Uplink TBF” v2.0, G.Lehmann, S.Nowak, 22.07.2005

[FRS 89997] “QoS Improvements: Real Time TBF and EDA TBF multiplexing”, v1.0,14.02.2005, C.Masseroni

[FRS 89982] “Radio Resource Manager (RRM) and Scheduler” v1.0, 01.06.2005, C.Masseroni

1.5 Abbreviations, Definitions and Explanations

Abbreviation definition, explanation

3GPP Third Generation Partnership Project

AC Admission Control

ARP Allocation Retention Priority

BCCH Broadcast Control Channel

BSC Base Station Controller

BSS Base Station Subsystem (GSM)

BTS Base Transceiver Station

CR Change Request

CS Circuit Switched

DL Downlink

EDA Extended Dynamic Allocation

EDGE Enhanced Data rate for GSM Evolution

E-GPRS GPRS with EDGE air interface

FDD Frequency Division Duplexing

FRS Feature Request Sheet

FSH Feature Sheet

GBR Guaranteed Bit Rate

GGSN Gateway GPRS Support Node

GPRS General Packet Radio Service

GSM Global System for Mobile communications


Process Owners





kbps kilo-bits per second

LMT Local Maintenance Terminal

LLC Link Layer Control

MAC Medium Access Control

MS/UE Mobile Station / User Equipment

mTBF Multiple TBF

PDCH Packet Data Channel

PDUs Packet Data Unit

PFC Packet Flow Control

PLR Planning Rule

PMN Planning Manual

PS Packet Switched

PSI Packet System Information

QoS Quality of Service

QCF Quality Control Function

RAN Radio Access Network

RC Radio Commander

RLC Radio Link Control

RRM Radio Resource Management

RTCP Real Time Control Protocol

RT Real Time

RX Receiver

RRBRT Reserved Radio Blocks Real Time

SGSN Serving GPRS Support Node

SI System Information


Process Owners





TBF Temporary Block Flow

TCP Transfer Control Protocol

TFI Temporary Flow Identifier

TSLs Timeslot

TX Transmitter

UL Uplink

USF Uplink State Flag

UMTS Universal Mobile Telecommunications System


Process Owners





2 General Feature Related Part

The BR8.0 introduced several features aiming at some QoS improvements in the (E)GPRS networks. In particular two features are of interest in the present document, namely:

- “QoS improvements for PS services”

- “Extended Dynamic Allocation”

The features’ description and their deep analyses can be found in PLR 00486 and PLR 88930&87477. In the findings below, a general overview of BR8.0 features’ functionality is necessary to have a clear understanding what sort of benefits the BR9.0 brings. A focus on scheduler’s limitations of previous release will be here regarded.

Additionally, the description of BR9.0 “Support of MS Multislot classes 30-33” feature is here described.

2.1 Functional Feature Description

2.1.1 BR 8.0 implementation

RT TBF multiplexing

The BR 8.0 “QoS support for PS services” has provided an innovation in TBF scheduling to properly support quality of service mechanism of Rel 97/98 onwards. The focus was placed on means to ensure that certain quality of service will be fulfilled especially in case of demanding RT application. Thus the TBF scheduling algorithm has been redesigned and a new scheduling entity: PFC scheduler has been introduced to better handle different applications’ requirements. Thanks to scheduler enhancements and the admission control mechanism, the RT services e.g. streaming can be dealt with in the most favourable way. The scheduler’s main task is to assure that a number of physical resources assigned to RT services are always sufficient to have the QoS requirements fulfilled. This is achieved, among others, by proper TBF/PFC multiplexing and based on the assumption that in case of RT services no multiplexing over the same PDCH of TBFs pertaining to different MS, is allowed. As a consequence the RT services always take priority over less demanding NRT services and the QoS of specific RT TBF will never be degraded by other MSs.

Even though this approach seems to be attractive since it guarantees certain amount of resources “virtually dedicated” to RT services, it leads to inefficient utilization of radio resources. Consequently, the number of RT TBF admitted in the system is also


Process Owners





limited. Furthermore, it does not assure the availability of resources for the entire user session duration.

EDA TBF multiplexing

As regards packet switched domain, there are three different methods for UL PDCHs multiplexing among different users: fixed, dynamic and extended dynamic allocation of which only two latter means are of interest in the document.

In case of dynamic allocation (BR7.0) an MS, for which an UL TBF is allocated, is forced to decode each DL block assigned to the PDCH to obtain USF and TFI and finally decide whether it is allowed to transmit in UL direction in the next (or next four) radio blocks. Extended Dynamic Allocation (BR8.0) has eliminated the need of receiving USF on each timeslot. When working in EDA mode, MS monitors all assigned PDCHs starting from the lower numbered PDCH. As soon as the MS decodes own USF on a particular PDCH it is allowed to transmit on the PDCH and all higher numbered PDCHs the MS have assigned. This has been achieved with the following constraints:

- EDA TBFs can be allocated in the horizontal mode

- EDA TBFs multiplexing is not allowed

- EDA is not supported in the far area of extended cells

In the light of this, the number of users that could exploit UL resources is severely reduced.

Together with EDA the new MS multi-slot classes 11 and 12 were introduced, supporting up to 4 TSLs in one direction and max. 5 TSLs in total (UL and DL). For further details please refer to [PLR 88930-87477].

2.1.2 BR 9.0 implementation

The BR 9.0 “QoS improvements: Multiplexing of RT and/or EDA TBFs” aims at mitigating abovementioned limitations of BR 8.0 features. The enhancements proposed in FRS 89997 have impact not only on the TBF scheduler itself but also on some other entities of which the RRM is composed of (Table 1).

BR 9.0 foresees also some further modifications in the RRM and scheduler due to introduction of e.g. mTBF, ARP etc. This is however covered in FRS 89982 and will not be treated in details.

At the moment, the BR 8.0 foresees that:

- RT TBFs can be admitted only in “virtually dedicated” mode which means the TBFs carrying streaming PFCs can not be multiplexed over the same radio resources


Process Owners





- EDA TBF can be admitted only in horizontal status; EDA TBF multiplexing is not allowed

The main drawbacks coming from such limitations have been pointed out in 2.1.1.

Table 1 RRM and scheduler model

The following paragraph provides a basic concept of BR 9.0 improvement. The focus will be placed on RRM and scheduler aspects relevant for QoS improvements as in FRS 89997. Some more detailed aspects of RRM like Channel Allocation Algorithm, multiplexing rules etc. are out of scope of this document and will not be treated further.

2.1.2.1 Basic idea of BR9.0 QoS improvements

TBF scheduler

The TBF scheduler’s task is not only to assure that RT services are properly served. It is also in charge of providing means to share bandwidth between RT traffic class


Process Owners





and NRT traffic class in such a way that both types of services are served with the best possible QoS (in terms of throughput and delay).

In order to achieve it the TBF scheduler has been split to two entities as depicted (Table 2):

- RT TBF scheduler

- NRT TBF scheduler

Table 2 TBF scheduler components

The structure of TBF scheduler, when compared to BR 8.0, has been kept. The only changes concern NRT services. NRT TBF scheduler provides some new features to support NRT services and their coexistence with RT ones. Both NRT and RT schedulers work on the same radio resources, on TRXs/TSs basis.

The new concept has been developed to ensure that both RT and NRT service are treated according to their QoS requirements. The (E)GPRS bandwidth, normally measured in kb/s, has been split into Radio Blocks per second available per TRX. The measure of bandwidth is then independent from (M)CS. The intention behind is to give an operator a possibility to easily convert radio block per second into kbit/s based on the initial (M)CS.

Example

Assume there is one TRX dedicated to (E)GPRS services with 6 TSs reserved for PS domain (Table 3)

Table 3 TSs dedicated to (E)GPRS services on a TRX


Process Owners





In the light of previous assumptions, the (E)GPRS bandwidth in terms of radio blocks is 50*6=300 RB/s. A new parameter RRBRT (Reserved Radio Blocks Real Time) has been defined to reserve the maximum number of RBs/s/TS designated for RT traffic class. The RRBRT is adjustable separately for UL and DL direction. The parameter is then used in the admission control phase.

Focus now, on Table 4 where concept of reserved radio blocks is depicted.

Table 4 Example of bandwidth split between RT and NRT TBFs

The RRBRT defines a portion of resources that can be used by RT traffic only. Consequently, the rest of RBs can be utilized by NRT traffic.

Similar to BR8.0, PFC scheduler will be involved in the scheduling phase in case a TBF carries more than 1 PFC (applicable for MS Rel 99 onwards). The structure and functionality of PFC scheduler remain as same as in BR 8.0. For further details regarding PFC scheduler please refer to PLR 00486.

As can be noticed, the new method for sharing the resources between RT and NRT TBFs does not foresee an exclusive assignment of radio resources to a specific RT


Process Owners





TBF. Thus, the radio resources can be shared among more than 1 RT TBF. Consequently, the limitation of BR8.0 has been overcome.

As far as NRT services are concerned, the multiplexing rules are based on the “old” BR8.0 approach. The allocation/scheduling weights are used to achieve adequate NRT TBFs handling.

In order to maintain a backward compatibility with BR8.0 the RT TBF multiplexing between TBFs belonging to different MSs may be blocked. This can be achieved by means of RT_MUXING_BACKWARD_COMP parameter. As long as RT_MUXING_BACKWARD_COMP=1 the RT TBF multiplexing is not allowed between TBFs of different MSs. In such a case the RT TBF multiplexing is only allowed for RT TBFs belonging to a particular MS.

Further RT TBF multiplexing constraints may come from transfer delay requirements. The suggestion is that in case of stringent demands in terms of transfer delay (PFC transfer delay smaller than 1 second) the RT TBF multiplexing (among different MSs) will not be allowed. The transfer delay constraints are determined by the system.

Admission Control

The basic idea of AC both in BR8.0 and BR9.0 is to provide the following functionality:

- verify if the required QoS profile is feasible according to the network resources

- verify if the requested QoS profile is plausible according to MS capability

If both conditions are satisfied the incoming RT PFC will be admitted. Otherwise it will be rejected and PFM procedure may be started to renegotiate QoS parameters.

In practice, the admission control mechanism affects RT services only.

When compared to BR8.0, the BR9.0 AC functionality is kept the same. However, the introduction of new method for bandwidth sharing has entailed some changes in the admission control phase. In BR8.0 the admission control is restricted only to pre-allocation phase. As a result, the radio resources are reserved for a short period of time when PFC is being admitted and there is a need to establish RT TBF. In addition, RT PFC can be admitted in the BR 8.0 only in “horizontal status”.

The BR9.0 AC overcomes all abovementioned limitations. The algorithm tries now to keep the radio resources reserved as long as RT PFC context exists in BSC. There is also no restriction concerning the “horizontal status” of the system. RT TBF will be admitted unless there are no resources to assure GBR. In such a way the RT TBFs can be multiplexed on the same radio resources as long as QoS criteria are fulfilled.


Process Owners





Quality Control Function

The new approach for QoS handling foresees also some improvements in the Quality Control Function module (Table 1) known from BR8.0. QCF is responsible for checking if the QoS provided by the system is in line with what was negotiated during PFC establishment (transfer delay, guaranteed bitrate). This is related to streaming traffic class only. In case the negotiated QoS can be no more fulfilled QCF Resource Allocation Message may be triggered and the resources re-allocation might be necessary. The BR9.0 QCF algorithm improvement is tied in with new means of bandwidth sharing between different TBFs allocated on the same radio resources. The QCF may change not only the MS configuration but also the bandwidth sharing among configured time slots (RRBRT strategy). The strategy reduces then the number of radio resources reconfigurations.

Support of MS Multislot classes 30-33

The BR9.0 "Support of MS Multislot Classes 30-33" feature introduces new MS multislot classes 30-33 that can support up to 6 TSLs in total (UL and DL), up to 4 TSLs in UL and 5 TSLs in DL direction. This feature can be used if a requested service requires more than 2 TSLs. The BSS first checks the MS capability and configuration before allocating the radio resources. MS provides information about its multislot capabilities during the GPRS/EGPRS attach procedure. If the MS supports multi-slot classes 30-33, the following combinations of TSLs in UL and DL direction can be configured by the BSC:

MS MultislotClass 30




#TSLDL #TSLUL #TSLDL #TSLUL #TSLDL #TSLUL #TSLDL #TSLUL

5 1 5 1 5 1 5 14 1 4 2 4 2 4 23 1 4 1 4 1 4 12 1 3 2 3 3 3 31 1 3 1 3 2 3 2- - 2 2 3 1 3 1- - 2 1 2 3 2 4- - 1 2 2 2 2 3- - 1 1 2 1 2 2- - - - 1 3 2 1- - - - 1 2 1 4- - - - 1 1 1 3- - - - - - 1 2- - - - - - 1 1


Process Owners





Table 5 Channel allocation for MS Multislot Class 30 - 33

2.2 Parameters

Not considered yet

2.3 Motivation to Introduce the Feature

The Real Time and EDA TBFs are already supported in BR8.0. There are however some limitations of previous release that make these features working in a way which is not efficient from the resources’ utilization point of view. Because the TBF multiplexing is not allowed for RT and EDA TBFs, the number of users who can exploit RT services or high uplink throughput is rather limited. Besides, the BR8.0 RT TBF management does not provide any means to have the radio resources reserved for the whole duration time.

BR9.0 QoS enhancements overcome these limitations. In order for system to better utilize the radio resources the RT TBF and EDA multiplexing is now supported. Furthermore, the radio resources for RT TBF are now tried to be guaranteed over whole transmission time not only during the pre-allocation phase as in BR8.0. The BR9.0 enhancement will then result in general improvements of QoS perceived by PS user.

Using the BR9.0 "Support of MS Classes 30-33" feature with the capability of 6 TSLs in total (UL and DL) and 5 TSLs in DL direction to be assigned by the network, guarantees higher bit rates per service and subscriber, i.e. a full 3G service performance by EDGE. It enables EDGE as overlay network for, or even as real alternative to, UMTS. MS multi-slot classes 30-33 allow supporting up to approx. 300 kbps at RLC/MAC Layer for DL direction services and up to 150 kbps at RLC/MAC Layer for bi-directional services.

Table 3 shows the maximum theoretical available bandwidth and the expected one for each configuration of multislot class 33. Other classes were omitted because the class 33 contains all possible combinations of channel allocation for Multislot classes 30-33.

#TSLDL #TSLUL

Theoretical RLC/MAC

DL

Thr [kbps]

Theoretical RLC/MAC

UL

Thr [kbps]

5 1 296 59,2

4 2 236,8 118,4

4 1 236,8 59,2


Process Owners





3 3 177,6 177,6

3 2 177,6 118,4

3 1 177,6 59,2

2 4 118,4 236,8

2 3 118,4 177,6

2 2 118,4 118,4

2 1 118,4 59,2

1 4 59,2 236,8

1 3 59,2 177,6

1 2 59,2 118,4

1 1 59,2 59,2

Table 3 Theoretical and Expected Throughput per MS Configuration

Theoretical available bandwidth for PS bearer service depends on Modulation Coding Scheme (MCS) used. In Table 2 the MSC9 with throughput per TSL equal to 59,2 was considered.

Note: the above cited throughputs refer to theoretical throughput; add all overhead protocols until RLC/MAC Layer to calculate the throughput offered to RLC/MAC Layer.

2.4 Interdependencies with other Features

The feature is strictly linked with FRS 89982 “Radio Resource Manager (RRM) and scheduler” where the strategy for AC, CAC etc. is defined.

2.5 Interdependencies with other technologies

Not applicable

2.6 Further Issues

Not applicable

2.6.1 Discussion of OEM Products


Process Owners





Not applicable

2.6.2 Norms

Not applicable

2.7 Open Issues

No open issues identified.


Process Owners





3 Dimensioning Aspects (Acquisition Level)

The FRS 89997 “QoS improvements: Real Time TBF and EDA TBF Multiplexing” has no impact on offer dimensioning rules. Thus no impact on offer tools is foreseen as well.

Since BR8.0 the RT traffic is already being dimensioned based on simplified analytical approach. Streaming traffic is modelled as Erlang traffic with the assumption of exponential time duration and Poisson arrival which is also reasonable in BR9.0 because the RT traffic is always assumed to be given the dedicated resources related to guaranteed bit rate. Therefore an assumption of availability of dedicated resources for streaming applications is still valid and dimensioning method is kept unchanged.

EDA TBF multiplexing has no impact on PS dimensioning phase as long as UL traffic amount is less than the traffic in DL which is still the case in existing (E)GPRS networks.

The "Support of MS Classes 30-33" feature certainly helps to achieve higher throughput in UL/DL direction as far as single user is concerned and the PS resources are available. Nevertheless, concerning the whole PS dimensioning process minor impact is expected. There is even less gain expected in case of low penetration of MSs of Classes 30-33. It has to be kept in mind that only DL direction is regarded since UL traffic is much lower than DL one.

In GOT drop 3.0 the PS simulation tables were generated based on 100 % penetration of 4 DL TS capable MSs. The possible gain from introduction of 5 DL capable MSs can be visible in case the number of PDCHs per cell is higher than 4. Such scenario was covered in GEPARD under assumptions of the mix penetration of 4 DL TS and 5 DL TS capable mobiles. Different penetration ratio was regarded including: 4 TS DL (100%), 4 TS DL (50%) + 5 TS DL (50%), 5 TS DL (100%) respectively. Table 6 keeps main GEPARD input parameters used for simulation. The results in terms of mean delay and 95%-ile delay vs. traffic served are presented in Table 7 and Table 8 respectively.

Input for the simulatordedicated PDCHs 5Data service on BCCHFrequency reuse 4/12GPRS MS RX capability Varying between 4 TS and 5 TS in DL direction#sessions 5000HTTP traffic model 5/12/0


Process Owners





Table 6 GEPARD settings for simulations run

MS RX capabilityPS traffic/cell 4 TS/5TS 100%-0% 4 TS/5TS 50%-50% 4 TS/5TS 0%-100%

23.974 5.062 5.032 5.012

35.955 4.601 4.561 4.499

47.932 4.236 4.199 4.176

Table 7 Mean delay vs. different MS RX capability

MS RX capabilityPS traffic/cell 4 TS/5TS 100%-0% 4 TS/5TS 50%-50% 4 TS/5TS 0%-100%

23.974 7.8 7.8 7.8

35.955 6.6 6.6 6.6

47.949 5.4 5.4 5.4

Table 8 95%-ile delay vs. different MS RX capability

As shown in the figure below there is no significant difference in terms of mean delay in case different MS RX capability is regarded (with only 1 TS difference). As far as 95%-ile delay is concerned no contrast at all can be observed.

Mean delay vs. MS RX capability

0

1

2

3

4

5

6

4 TS/5TS 100%-0% 4 TS/5TS 50%-50% 4 TS/5TS 0%-100%

MS RX capability

Mea

n d

elay

[s]

23.974

35.955 (kbps)

47.932 (kbps)


Process Owners





Figure 1 Mean delay vs. MS RX capability

95%-ile delay vs. MS RX capability

0123456789

4 TS/5TS 100%-0%

4 TS/5TS 50%-50%

4 TS/5TS 0%-100%

MS RX capability

Mea

n d

elay

[s]

23.974 (kbps)

35.955 (kbps)

47.932 (kbps)

Figure 2 95%-ile delay vs. MS RX capability

3.1 Affected Services and Quality of Service Definitions, used Traffic Models

Not applicable

3.2 Relevant BSS Specification and Configuration Limits

Not applicable

3.3 Impact on Existing Dimensioning Methods

Not applicable

3.4 Summary of Dimensioning Rules

Not applicable

3.5 Rules for Phase-Oriented Offers

Not applicable


Process Owners





3.6 Impact on existing Planning Manuals (PMNs)

Not applicable

3.7 Impact on existing Offer Tools, possible Workarounds

Since (E)GPRS dimensioning methods remain not affected there is no impact on the tools as well.

3.7.1 GERAN Offer tool

No impact

3.7.2 QandD Offer Tool

No impact

3.8 Open issues



Process Owners





4 Implementation aspects (Realisation Level)

4.1 Ordering

4.1.1 Affected Services and Quality of Service Definitions, used Traffic Models

Not applicable.

4.1.2 Relevant BSS Specification and Configuration Limits

The “Support of MS Multislot classes 30-33” feature must be supported by MSs Rel 6 and the CORE network (SAG core: PO5.0).

4.1.3 Impact on Existing Planning Methods

Not relevant.

4.1.4 Summary of Planning Rules

Not applicable

4.1.5 Rules for Phase-Oriented Planning

Not applicable

4.1.6 Impact on existing Planning Manuals (PMNs)

Not applicable

4.1.7 Impact on existing Planning Tools, possible Workarounds

Not applicable

4.2 Implementation

4.2.1 Feature introduction strategy

The features itself do not require any special implementation strategy. Its deployment in the network depends only on their support on both network and MS side.

4.2.2 Database Generation

4.2.2.1 Interdependencies with Parameters of Related Features

4.2.3 Installation requirements

Not applicable


Process Owners





4.2.4 Evaluation of implementation

Not applicable

4.2.4.1 Acceptance test procedures

4.2.4.2 Performance measurements and counters (O3)

4.2.4.3 Initial Tuning

4.2.5 Impact on existing Network Optimisation Use Cases (O3)

Not applicable

4.2.6 Impact on existing Network Optimisation Tools (O3)

Not applicable

4.3 Open issues



Process Owners




Date post:	28-Nov-2014
Category:	Documents
Upload:	aambonatto
View:	133 times
Download:	1 times

PLR BR9.0 Quality of Service Improvements

Documents