PLR 84566 Multi Service Layer Support IUS2.3

s
GERAN
Network Engineering
Planning Rule
Multi Service Layer Support
FRS 84566
BR 8.0
IUS 2.3 Order Level

8.07.2005
Piotr Grzybowski
Com SDC NA B1
Planning Rule FRS 84566

Trademarks:
All designations used in this document can be trademarks, the use of which by third
parties for their own purposes could violate the rights of their owners.
Copyright (C) Siemens AG 2006

Issued by the Communications Mobile Networks Group
St.-Martin-Strae 76
D-81541 Mnchen
Technical modifications possible.
Technical specifications and features are binding only insofar as
they are specifically and expressly agreed upon in a written contract.

Reason for Update

Summary:
IUS Version
Details:
Chapter/Section
Reason for Update

AFI version agreed by TS without comments, SE
comments introduced. IUS version.
Issue history
Issue
Date of Issue
Reason for Update
0.1
3.03.2004
First draft version reviewed by Szymon Nowak.

Document covers offer level.
1.0 AFI
5.03.2004
Review comments implemented. Document covers

offer level.
1.1 IUS
7.05.2004
AFI version agreed by MS P without feedback.

IUS version. Document covers offer level.
2.0 AFI
4.01.2005
Changes in chapter 2 due to new version of FRS.

Order level updated. Reviewed by Martin Kaufmann
2.1 AFI
12.05.2005
Update of the chapter 4.1.7. Feature name changed

from Improvement of Service Dependent Channel
Allocation to Multi Service Layer Support
2.2 AFI
16.05.2005
Changes in chapter 4 and 4.2.2 due to review

comments. Chapter 4.1.7 extended. Document
covers order level.
Number
Authors
In addition to the author named on the cover page the following persons have
collaborated on this document:
Name
Department
Piotr Grzybowski
COM SDC NA B1
A50016-G5000-H219-1-7618

This document consists of a total of 58 pages.
Table of Contents
1
1.1
1.2
General Information (Acquisition Level).........................................................8

Authors........................................................................................................... 8
Introduction.................................................................................................... 8
2
2.1
2.1.1
2.1.2
2.1.3
2.1.4
2.2
2.2.1
2.2.2
2.2.3
2.2.3.1
2.2.3.2
2.3
2.4
2.5
2.6
2.6.1
2.6.2
2.7
General Feature Related Part (Acquisition Level)..........................................9

Functional Feature Description (Database Level)........................................10
Service List SL.............................................................................................10
Layer LY....................................................................................................... 11
Service Layer List (SLL)...............................................................................12
SL to the LY allocation strategy....................................................................13
Parameters (Database Level)......................................................................15
New Parameters Introduced.........................................................................15
Changes of the existing parameters.............................................................22
New Measurements.....................................................................................22
MEBUTSLY: Mean number of busy channels per layer................................22
CHALNHLY: Number of channel allocation requests not served in the highest
layer or not served at all, per service type....................................................23
Motivation to Introduce the Feature..............................................................24
Interdependencies with other Features........................................................24
Interdependencies with other Technologies.................................................25
Further Issues.............................................................................................. 25
Discussion of OEM Products........................................................................25
Norms........................................................................................................... 25
Open Issues................................................................................................. 25
3
3.1
3.2
3.3
3.3.1
3.3.2
3.3.3
3.3.4
3.4
3.5
3.6
3.7
3.8
Dimensioning Aspects (Acquisition Level)....................................................26

Affected Services and Quality of Service Definitions, used Traffic Models...26
Relevant BSS Specification and Configuration Limits..................................26
Impact on Existing Dimensioning Methods...................................................27
Service list.................................................................................................... 27
Layer LY....................................................................................................... 28
Resources assignment.................................................................................28
Resources assignment example..................................................................29
Summary of Dimensioning Rules.................................................................30
Rules for Phase-Oriented Offers..................................................................31
Impact on existing Planning Manuals (PMNs)..............................................31
Impact on existing Offer Tools, possible Workarounds.................................34
Open Issues................................................................................................. 36
4
4.1
4.1.1
4.1.2
4.1.3
4.1.3.1
Implementation aspects (Realisation Level).................................................37

Ordering....................................................................................................... 37
Affected Services and Quality of Service Definitions, used Traffic Models...37
Relevant BSS Specification and Configuration Limits..................................37
Impact on Existing Planning Methods..........................................................37
Multiple reuse patterns planning..................................................................37
A50016-G5000-H219-1-7618

4.1.3.2
4.1.3.3
4.1.3.4
4.1.3.5
4.1.4
4.1.5
4.1.6
4.1.7
4.1.7.1
4.1.7.2
4.1.7.3
4.2
4.2.1
4.2.2
4.2.3
4.2.4
4.2.4.1
4.2.4.2
4.2.4.3
4.2.5
4.2.6
4.3
Services List................................................................................................. 38
Assigning layers to the services...................................................................41
Conventional allocation vs. SDCA................................................................41
Parameters setting.......................................................................................42
Summary of Planning Rules.........................................................................44
Rules for Phase-Oriented Planning..............................................................45
Impact on existing Planning Manuals (PMNs)..............................................45
Impact on existing Planning Tools, possible Workarounds...........................45
BSS parameters planning............................................................................46
Frequency planning......................................................................................46
Capacity planning......................................................................................... 47
Implementation............................................................................................. 52
Feature introduction strategy........................................................................52
Database Generation...................................................................................53
Installation requirements..............................................................................56
Evaluation of implementation.......................................................................56
Acceptance test procedures.........................................................................56
Performance measurements and counters..................................................57
Initial Tuning................................................................................................. 57
Impact on existing Network Optimisation Use Cases...................................57
Impact on existing Network Optimisation Tools............................................57
Open issues................................................................................................. 57
Abbreviations............................................................................................................... 58
A50016-G5000-H219-1-7618

List of Figures and Tables

Figure 1: SDCA resources allocation..........................................................................28
Figure 2: GERAN Offer Tool SDCA program flow........................................................35
Figure 3: Multi Reuse Pattern Strategy.......................................................................37
Figure 4: Layers of different C/I...................................................................................47
Figure 5: Carrier Layer configuration...........................................................................47
Figure 6: Cell Layer configuration...............................................................................48
Figure 7: Cell layers.................................................................................................... 48
Figure 8: Layer TRX association...............................................................................49
Figure 9: Bearer settings............................................................................................. 49
Figure 10: Cell Layers supported for Services settings...............................................50
Figure 11: Service excluded from BCCH.....................................................................50
Figure 12: Terminal Type definition..............................................................................51
Figure 13: GPRS Service Coverage probability..........................................................52
Figure 14: Terminals served for Layer 1 and Layer 2..................................................52
Table 1: BR 8.0 Service List........................................................................................ 10
Table 2: SLL example.................................................................................................. 12
Table 3: Properties...................................................................................................... 22
Table 4: Services List example....................................................................................29
Table 5: Resources assignment example....................................................................30
Table 6: SLPA and SLCA assignment..........................................................................39
Table 7: Services List for Concentric Cell....................................................................39
Table 8: Services List for Extended Cell......................................................................40
Table 9: Services List for Dual Band Standard Cell.....................................................40
Table 10: Example SLPA............................................................................................. 43
Table 11: Example SLL table.......................................................................................43
Table 12: Feature functionalities in the tool.................................................................46
A50016-G5000-H219-1-7618

References
[FRS 84566]
[FS 84566]
[FRQ 30643]
[FRQ 86558]
[FRS 457]
[PLR 457]
[FRS 534]
[PLR 534]
[FAT]
[SDCA 1]
[CR2352]
[CR1847]
[FRS 88930]
A50016-G5000-H219-1-7618
FRS Service Dependent Channel Allocation

G. Visconti, C.Sartori
11.06.2004
FS Service Dependent Channel Allocation
Loredana Poletti
27.09.2004
FRQ Service Dependent Channel Allocation Strategy
S. Weisgerber, R. Muellner
14.09.1999
FRQ Improvement on Service Dependent Channel Allocation
Gabriella Bonfadini
22.10.2002
FRS Service dependent channel allocation strategy step 1
Franco Osculati
22.01.2002
PLR Service dependent channel allocation strategy step 1
E. Tufino, T. Toniatti
28.02.2003
FRS Service Dependent Power Control and Handover
Management
L. Morini
02.02.2002
PLR Service Dependent Power Control and Handover
Management
T. Toniatti
27.05.2003
Evaluation of FAT Status Application Guidelines for FAT Use
Cases
A. Maciolek
12.02.2004
Radio and Fixed Network Planning Process Extract of PLRs
SDCA Step 1 (BR6.0)
D.Hartmann
CR Dual Band Standard cell and Service dependent channel
allocation improved handling
CR 2352
CR Change of measurement NRDEFTCH in BR7.0
CR1847
FRS 88930 : E-/GPRS enhancements : Extended Dynamic,
Flexible USF Granularity
S. Cavalli
31.03.2004

1 General Information (Acquisition Level)

1.1
Authors
Piotr Grzybowski
1.2
Piotr.Grzybowski@siemens.com
Introduction
This Planning Rule (PLR) is a Siemens internal document and thus not intended to be
handed out to customers.
It describes the feature impact on the existing offer and order process and the process
of database generation.
The reader is assumed to be familiar with the basic functions of the radio interface of
GSM network, the traffic calculations for (E)GPRS networks as well as frequency
planning aspects.
A50016-G5000-H219-1-7618

2 General Feature Related Part (Acquisition

Level)
The aim of this feature is to provide the customer with the possibility of configuration
the radio resources allocation process on cell basis in an optimized way making free
the customer to realize the best compromise between services and radio quality
needed. In order to reach this goal three new concepts are inserted in the SBS
system:
Service List (SL) - a list of services supported by the cell. For each entry a
reference to one service type is defined. In case of dual area cell (EXTENDED,
DUAL BAND, CONCENTRIC) one SL for each area has to be built in: one for the
complete/far area (SLPA - service list primary area) and one for the inner/near area
(SLCA - service list complementary area). If the cell will be dual band standard cell
(see FRS 87030 on Upgrading of the Common BCCH Implementation), the
service list will be unique (there is no need of having different services per band).
The service types are defined on release basis and are hard coded. The data base
administrator shall guarantee the consistence of the list. The order of services
insertion inside the SL refers to service priority.
Layer (LY) - a group of radio resources (TRXs) with the same expected radio
quality, a maximum 12 LY for each cell can be allocated. In case of dual area cells
or dual band standard cells the total number of layers remains 12.
Service Layer List (SLL) - a list of LY that can be used for a specific service. For
each service, at cell basis, a SLL is built, the order of the insertion of LY in the SLL
represents the priority used by the system in order to find a new resource for a
specific service. In case of single slot circuit calls, if the first LY in the SLL is
congested the second one is checked and so on till a resource is found, while in
case of multislot circuit calls another layer could be preferred even if the first one is
not congested, when a better configuration is found (higher throughput). Also in
case of packet calls a layer could be preferred with respect to an higher priority one
if a better choice is found (the exact strategy for PS channel allocation is defined in
FRS 88930).
A50016-G5000-H219-1-7618

2.1
2.1.1
Functional Feature Description (Database Level)

Service List SL
In BR 8.0 the following service types are identified:
Service
1.
2.
Description
Signaling (SDCCH) used for services requiring only Signaling Channel (SMS,
call setup, LCS)
CS speech
used for speech call applying EFR- FR- HR codec
3.
CS speech AMR FR used for speech call applying AMR FR codec
4.
CS speech AMR HR used for speech call applying AMR HR codec
5.
CS data
circuit switched single slot data call allowed to use up to

9.6 and 14.4 coding
6.
HSCSD
circuit switched Multislot calls using HSCSD
7.
GPRS
PDTCH to be allocated dynamically to GPRS services
8.
EGPRS
PDTCH to be allocated dynamically to EGPRS service
9.
ASCI
broadcast channel to be used for allocating ASCI services
Table 1: BR 8.0 Service List

The SL for each cell shall be created on cell basis in BTS object during configuration
phase assigning to each entry a service type and a list of layers to support it. The
order of insertion of services inside the SL represents the priority assigned to a service
in case of conflict for resources allocation.
In case of a dual area cell (i.e. extended or concentric single/dual band cell) also the
SLCA has to be configured assigning a SLL for all services that we want to support in
the complementary area.
Additionally the following rules are foreseen:
The SL for BR 8.0 shall contain maximum 9 entries.
If one service is not present in the SL it is intended as not supported in that cell.
Changing of the priority of services inside the SL, service adding and removing in
the SL is possible using SET command without service interruption.
If for a service an enabling / disabling flag is already foreseen, the system shall
accept to change the flag to enable only if a SLL is associated to that service.
Deletion of a service from the SL is possible only if the relevant enabling / disabling
flag is set to false.
Signaling shall be foreseen in SLPA only.
In case of dualband standard cells, signaling shall be configured in a layer
supporting the BCCH band.
10
A50016-G5000-H219-1-7618

EGPRS could be allocated only to TRXs which are EDGE capable. TRXMD
attribute inserted at TRX level have to be checked.
GPRS/EGPRS will not be included in SLCA in case of concentric cell.
2.1.2
Layer LY
The Layer (LY) shall contain radio channels (TRXs) with expected the same radio
quality and the same characteristics. The operator may decide to group TRXs having
the same expected radio quality in different layers, to support for example a service
only on a subset of TRXs, or to have them reserved for a particular service. Inside a
LY the radio resources are organized using a list based on channel combination. Each
TRX will be associated to a layer via O&M. Layers are grouped in SLL. The order of
layer insertion represents expected radio quality. Higher numbers are related to lower
expected radio quality. However TRXs organization within the layer reflects customer
targets and may be different. The selection of appropriate LYs for each service will be
performed on the basis of the radio planning and/or customer considerations.
Additionally the following rules are foreseen:
Maximum 12 layers can be created within a standard cell.
In case of dual area cells or dual band standard cells the total number of layers
remains 12.
LY0 and LY1 are used by system as default value in order to maintain the existing
behavior.
LY0 is used by the system for Signaling channel then is assigned by default to
SDCCH/8 or SDCCH/4 or TCH/SD configured as SDCCH. It is recommended to
place signaling channels on the same layer which groups TRXs of the same radio
quality.
LY1 is used as default value on traffic channels: it has to be assigned to TCH/F,
TCH/FH or TCH/SD configured as TCH.
A new LY can be added or removed from a SLL using SET command without
service interruption.
It is recommended to perform changes inside the LY during low traffic load.
Otherwise it may happen that calls queued have to be released due to service no
longer supported in the cell or several calls not allocated due to preferred layer to
be moved.
If TCH/SD are configured, for the ones included in the SDCCH_POOL the same
rule as for signaling apply.
TCH/SD within TCHSDPOOL that can be shared on demand between TCH and
SDCCH has to be grouped in an own LY.
For non hopping system it is recommended to assign to the same layer TRXs
characterized by the same re-use factor.
For hopping system it is recommended to assign to the same layer TRXs/CHANs
belonging to the same hopping laws, including list of frequencies characterized by
the same re-use factor.
A50016-G5000-H219-1-7618
11

One LY can belong to different Service Layer List (SLL) with the same or different
priority. The LY priority is valid inside the single SLL. For example
SLL1[LY4,LY1,LY2,LY3] ; SLL2[LY3,LY1,LY2,LY4].
In case of concentric cells or extended cells, a layer may exist in both subareas or
in one subarea only.
In case of dual band standard cell a layer may contain TRXs belonging to both
bands or to one band only.
2.1.3
Service Layer List (SLL)

The Service Layer List is built during configuration phase by assignment of LY list to
each service from SL. The order of LY insertion inside the SLL represents the priority
used during resource allocation; maximum 12 LY can be inserted in a SLL. A new LY
can be added or removed from a SLL using SET command without service
interruption. It is foreseen to increase or decrease the priority of one LY inside the SLL
with SET command and without service interruption.
Without service interruption in case of CS services (also for the modification of the
list of services) means that ongoing calls and/or the call in set-up phase, not waiting
for resource allocation, shall not be released or rejected due to the changes.
In case of PS services, to avoid problems due to non uniform update of TDPC and
PCU data structures the lock of PTPPKF object is necessary, and therefore in this
case there will be service interruption.
The example SLL can be built in the following way:
SL entry
Service Type
SLL
Signaling
SLL0 (LY0)
CS speech EFR-FR-HR
SLL2 (LY1,LY0)
CS speech AMR FR
SLL2 (LY1,LY0)
CS speech AMR HR
SLL2 (LY1,LY0)
CS DATA up to 9.6 and 14.4
SLL1 (LY0,LY1)
HSCSD
SLL1 (LY0,LY1)
GPRS
SLL1 (LY0,LY1)
NULL
NULL
ASCI
SLL1 (LY0,LY1)
Table 2: SLL example

In the table above data services are assigned to SLL1 and speech assigned to SLL2.
In the example, all TRXs belonging to LY0 and LY1 are supposed to support GPRS. To
avoid layering inside signaling services all the channels used for signaling are
configured on the same LY0 layer.
Feature implementation has to provide compatibility with the previous releases where
no layering was foreseen. It is obtained by assigning all TRXs to one default Service
12
A50016-G5000-H219-1-7618

Layer List (SLL0). Such an approach is applicable for NoPreference call policy. In
case call policy is different from NoPreference, 2 different layers are foreseen. The
first layer (LY0) will be reserved for BCCH only, the second one (LY1) will include all
the remaining TRXs.
The SL on a cell basis contains an SLL for each service, in case of dual area cells one
SLL for each area shall be applied. In case a service has no SLL associated (this
situation may happen during a transient phase) that service shall be intended as not
supported.
2.1.4
SL to the LY allocation strategy

If the SL for the CS service has a reference to a SLL the BSC shall try to find the
requested resource/s inside the first LY of the SLL. If the search of the requested
resource fails inside the first LY the system shall try to find the requested resources
inside the others LY of the SLL. In case of multislot circuit calls another layer could be
preferred even if the first one is not congested. It is selected according to the higher
throughput achievable. The same approach is taken in case of packet calls (the exact
strategy for PS channel allocation is defined in FRS 88930).
If no resources are available for that service, the request is satisfied applying the
same rules as used with the implementation of Service Dependent Channel Allocation
step 1 (FRS457).
In case the same LY is referenced in different SLL with different priority the resource
reallocation process shall take care to ensure that MS is kept as much as possible in
the LY with the highest priority based on service request.
In case of concentric single/dual band or extended cell the subarea is not changed
due to the fact that the preferred layer is not found, in these cells the subarea is
chosen on the basis of the radio conditions/mobile positions.
In case of dual band standard cell, the MS request will be served according to the SLL
and the MS capabilities.
In case the best layer for a service belongs to the non-BCCH band only, the single
band mobiles will never be served in preferred layer. The exact algorithm for choosing
the preferred area is indicated in the FRS 87030 relevant to the Upgrading of the
Common BCCH Implementation.
In case of dual area cells if the SL for the requested area has no LY associated for a
specific service it should be checked if the same service has a LY associated in the
other area, in this case the BSC shall try, if allowed by radio conditions and MS
capability, to move MS in the other area.
In case of dual area cells if for a specific service the allocated resources are not on the
best LY with reference to the SL (primary or complementary) the system shall try, as
soon as there are available resources in a preferred LY to reorganize , when possible
(this is the case of circuit services only), the allocation in order to move the MS on a
better LY of SLL; this means that the subarea in a cell will not be changed due to the
fact that the best layer is not found.
In case a resource is found but not in the first LY of SLL, or a multislot request is
downgraded in order to allocate resources to serve the call, the resource reallocation
process should try when possible, to move the involved circuit call to the appropriate
A50016-G5000-H219-1-7618
13

LY or to restore the best configuration for the downgraded request, the same should
apply when possible, for the downgraded ongoing circuit calls (for packet calls see the
FRS 486 and FRS 88930).
If the requested circuit switched service is not supported in a cell, in case of call set-up
a Directed Retry towards a cell supporting it, is started.
In case the request is for an internal intercell HO the cell list must be scanned in order
to find out a cell supporting the requested service.
In case of external handover a handover failure must be returned to MSC.
In case of adding LY to SLL or changing priority inside to the SLL, the resource
reallocation process must be informed of the operation, in order to take it into account
and to try to rearrange the distribution of the active services in the right LY when it is
periodically activated. The resources reallocation process shall use forced intracell
handover in order to rearrange resources inside to the cell.
It should be noticed that in case both a mobile is supporting more that one speech
codec and the same applies to the circuit pool (TRAU), in case there is more than one
layer for the various circuit services, if congestion exists for a service (e.g. AMR
FR/HR) , a resource available for the next MS codec supported should be looked for
(e.g. FR) according to the service list, in order to avoid the call drop.
In case we are associating a new channel to a LY inserted in SL for GPRS reserved
or EGPRS reserved services, the system shall accept this association only if this
channel is the first reserved on that TRX or if its adjacent to another channel
belonging to that LY.
It must be underlined that using some LY configuration (e.g. LY supporting only
speech and other LY supporting only data calls) in case of data calls the benefit of
direct assignment is lost.
When a downgrade of an ongoing packet call is needed, the PCU should receive the
request for downgrading the relevant Priority Information Element of the circuit call
(see Rec.08.08) and the information about the preferred layers in order to be able to
optimize the downgrading when possible, e.g. more than one downgradable PDCH is
found with the same total weight (see detailed information on the FRS 486 (Quality
of Service for PS services, Extended Dynamic Allocation).
The number of PDCH reserved per cell is indicated by the parameters GMANPRES
for the GPRS SLL and EMANPRES, for the EGPRS SLL. These channels are not
preemtable by circuit services on the packet ones. These channels shall be on the first
layer shared by GPRS/EGPRS and CS services. In case this first shared layer is
common to CS and both the Packet Services, the number of reserved PDCH per cell
is calculated as the sum of the two mentioned attributes. GMANPRES /EMANPRES
are now split in primary and complementary for extended cells.
If the operator reserves a layer for the packet services only, these channels being
already not preemptable by the CS shall not be count among the ones indicated by
GMANPRES/EMANPRES. The data base administrator shall guarantee that the layers
dedicated to packet services only (as well as the ones reserved for CS data multislot)
are included as the first ones in the relevant SLL.
In case of packet services the resource manager on the TDPC shall be informed if the
downgrading of the incoming call shall in any case satisfy a guaranteed bit rate (RT
14
A50016-G5000-H219-1-7618

Streaming services), in order to avoid, in case of congestion in the cell, that the
incoming call is downgraded below the service sustainable level.
User has to be aware that feature doesnt support preemption of voice calls by
(E)GPRS services, even if they have higher priority.
2.2
2.2.1
Parameters (Database Level)

New Parameters Introduced
Attributes introduced for BTS object shall be managed by CREATE SET and GET
command. By mean of these attributes it shall be possible to define which services are
supported, and for each entry of the service list of maximum 12 layers is defined
The attributes for COMPLEMENTARY area are considered valid only for dual area
cell. In other cases all service list entries are filled by a null value.
ASCILayerListPrimary ASCILLPRM
This attribute specifies the list of TRX layers assigned to ASCI VBS/VGCS services in
a single band standard cell, or in the complete/far area of a dual area cell (extended,
concentric single/dual band), or in the BCCH band of a dual band standard cell. The
TRX layers are specified in the list in decreasing order of their priority.
signallingLayerListPrimary SLLPRM
This attribute specifies the list of TRX layers assigned to services that require their
signalling channel in a single band standard cell, or in the complete/far area of a dual
area cell (extended, concentric single/dual band), or in the BCCH band of a dual band
standard cell. The TRX layers are specified in the list in decreasing order of their
priority.
AMRHalfRateLayerListPrimary AMRHRLLPRM
This attribute specifies the list of TRX layers assigned to speech calls applying AMR
HR codec in a single band standard cell, or in the complete/far area of a dual area cell
(extended, concentric single/dual band), or in the BCCH band of a dual band standard
cell. The TRX layers are specified in the list in decreasing order of their priority.
AMRHalfRateLayerListComplementary AMRHRLLCOM
HR codec in the inner/near area of dual area cell (extended, concentric single/dual
band), or in the complementary band of a dual band standard cell. The TRX layers are
specified in the list in decreasing order of their priority.
AMRFullRateLayerListPrimary AMRFRLLPRM
FR codec in a single band standard cell, or in the complete/far area of a dual area cell
AMRFullRateLayerListComplementary AMRFRLLCOM
A50016-G5000-H219-1-7618
15

FR codec in the inner/near area of dual area cell (extended, concentric single/dual
circuitSwitchedDataLayerListPrimary CRTSWDLLPRM
This attribute specifies the list of TRX layers assigned to circuit switched single slot
data calls in a single band standard cell, or in the complete/far area of a dual area cell
circuitSwitchedDataLayerListComplementary CRTSWDLLCOM
This attribute specifies the list of TRX layers assigned to circuit switched single slot
data call in the inner/near area of dual area cell (extended, concentric single/dual
circuitSwitchedSpeechLayerListPrimary CRTSWSPELLPRM
This attribute specifies the list of TRX layers assigned to the EFR, FR, and/or HR
codec in a single band standard cell, or in the complete/far area of a dual area cell
circuitSwitchedSpeechLayerListComplementary CRTSWSPELLCOM
This attribute specifies the list of TRX layers assigned to the EFR, FR, and/or HR
codec in the inner/near area of dual area cell (extended, concentric single/dual band),
or in the complementary band of a dual band standard cell. The TRX layers are
EDGELayerListPrimary ELLPRM
This attribute specifies the list of TRX layers assigned to EDGE service in a single
band standard cell, or in the complete/far area of a dual area cell (extended,
EDGELayerListComplementary ELLCOM
This attribute specifies the list of TRX layers assigned to EDGE service in the
inner/near area of dual area cell (extended, concentric single/dual band), or in the
complementary band of a dual band standard cell. The TRX layers are specified in the
list in decreasing order of their priority. Can not be true for concentric cell.
GPRSLayerListPrimary GLLPRM
This attribute specifies the list of TRX layers assigned to GPRS service in a single
band standard cell, or in the complete/far area of a dual area cell (extended,
GPRSLayerListComplementary GLLCOM
16
A50016-G5000-H219-1-7618

This attribute specifies the list of TRX layers assigned to GPRS service in the
complementary band of a dual band standard cell. The TRX layers are specified in the
list in decreasing order of their priority. Can not be true for concentric cell.
HSCSDLayerListPrimary HSCSDLLPRM
This attribute specifies the list of TRX layers assigned to circuit switched multislot calls
using HSCSD in a single band standard cell, or in the complete/far area of a dual area
cell (extended, concentric single/dual band), or in the BCCH band of a dual band
standard cell. The TRX layers are specified in the list in decreasing order of their
priority.
HSCSDLayerListComplementary HSCSDLLCOM
This attribute specifies the list of TRX layers assigned to circuit switched multislot calls
using HSCSD in the inner/near area of dual area cell (extended, concentric single/dual
gprsSupported GSUP
The attribute is no longer supported.
DowngradeStragety DGRSTRGY
This attribute has been moved from the BSC to the BTS object and describes the
downgrade strategy in use. It is operator defined and describes the type of resource
reallocation procedure to be employed according to the preferred allocation channel
selected.
layerId (layer identifier) LAYERID

This attribute specifies the group of radio resources to which the TRX belongs. It is a
list comprising a maximum of 12 items, whereby each item is a trxLayer. The attribute
must be managed in CREATE SET and GET command and it contains the indication
of the layer assigned to that TRX.
A50016-G5000-H219-1-7618
17

Name
Objec
t
ASCILayerListPrimary BTS
Unit
string
ASCILLPRM
signallingLayerList
Default
Value
MinValue: 1 = LY0
NULL
List of TRX layers RNP

assigned
to
ASCI
VBS/VGCS
services
(single band standard
cell,
or
in
the
complete/far area of a
dual area cell or in the
BCCH band of a dual
band standard cell. TRX
layers list in decreasing
order of priority.
NULL

assigned to signaling
channel (single band
standard cell, or in the
BCCH band of a dual
order of priority.
NULL

assigned to speech
calls applying AMR HR
codec (single band
BCCH band of a dual
order of priority.
NULL

assigned to speech
calls applying AMR HR
codec in the inner/near
area of dual area cell
(extended,
concentric
single/dual band), or in
the
complementary
band of a dual band
standard
cell.
TRX
order of their priority.
MaxValue: 12 =
LY11
BTS
string
MinValue: 1 = LY0
MaxValue: 12 =
LY11
SLLPRM
AMRHalfRateLayer
ListPrimary
Range (min...max)
BTS
string
MinValue: 1 = LY0
MaxValue: 12 =
LY11
AMRHRLLPRM
AMRHalfRateLayer
ListComplementary
BTS
string
MinValue: 1 = LY0
MaxValue: 12 =
LY11
AMRHRLLCOM
AMRFullRateLayer
ListPrimary
AMRFRLLPRM
18
BTS
string MinValue: 1 = LY0

MaxValue: 12 =
LY11
NULL
Description
List of TRX layers

assigned to speech
calls applying AMR FR
codec (single band
BCCH band of a dual
order of priority.
Classifi
cation
RNP
A50016-G5000-H219-1-7618

Name
AMRFullRateLayer
ListComplementary
Objec
t
BTS
Unit
Range (min...max)
Default
Value
Description
Classifi
cation
NULL
List of TRX layers

assigned to speech
calls applying AMR FR
codec in the inner/near
(extended,
concentric
the
complementary
band of a dual band
standard
cell.
TRX
RNP
NULL
List of TRX layers

assigned
circuit
switched single slot
data calls (single band
BCCH band of a dual
order of priority.
RNP
NULL
List of TRX layers

assigned
to
circuit
switched single slot
data
call
in
the
inner/near area of dual
area cell (extended,
concentric single/dual
band),
or
in
the
complementary band of
a dual band standard
cell. TRX layers list in
decreasing order of
their priority.
RNP
NULL
List of TRX layers

assigned to the EFR,
FR, and/or HR codec
cell,
or
in
the
BCCH band of a dual
order of priority.
RNP
MaxValue: 12 =
LY11
AMRFRLLCOM
circuitSwitchedData
LayerListPrimary
BTS

MaxValue: 12 =
LY11
CRTSWDLLPRM
circuitSwitchedData
LayerList
Complementary
BTS

MaxValue: 12 =
LY11
CRTSWDLLCOM
circuitSwitched
SpeechLayerList
Primary
CRTSWSPELLPRM
A50016-G5000-H219-1-7618
BTS

MaxValue: 12 =
LY11
19

Name
circuitSwitched
SpeechLayerList
Complementary
Objec
t
BTS
Unit
Range (min...max)
Default
Value
Description
Classifi
cation
NULL
List of TRX layers

FR, and/or HR codec
call in the inner/near
(extended,
concentric
the
complementary
band of a dual band
standard
cell.
TRX
RNP
NULL
List of TRX layers

FR, and/or HR codec
cell,
or
in
the
BCCH band of a dual
order of priority.
RNP
NULL
List of TRX layers

assigned
to
EDGE
service call in the
band),
or
in
the
decreasing order of
their priority. Can not be
true for concentric cell.
RNP
NULL
List of TRX layers

assigned
to
GPRS
service (single band
BCCH band of a dual
order of priority.
RNP
MaxValue: 12 =
LY11
CRTSWSPELLCOM
EDGELayerList
Primary
BTS

MaxValue: 12 =
LY11
ELLPRM
EDGELayerList
Complementary
BTS

MaxValue: 12 =
LY11
ELLCOM
GPRSLayerList
Primary
GLLPRM
20
BTS

MaxValue: 12 =
LY11
A50016-G5000-H219-1-7618

Name
GPRSLayerList
Complementary
Objec
t
BTS
Unit
Range (min...max)
Default
Value
Description
Classifi
cation
NULL
List of TRX layers

assigned
to
GPRS
service call in the
band),
or
in
the
decreasing order of
their priority. Can not be
true for concentric cell.
RNP
NULL
List of TRX layers

assigned
to
circuit
switched multislot calls
using HSCSD (single
band standard cell, or in
the complete/far area of
a dual area cell or in the
BCCH band of a dual
order of priority.
RNP
NULL
List of TRX layers

assigned
to
circuit
switched multislot calls
using HSCSD in the
band),
or
in
the
decreasing order of
their priority.
RNP
LY0
Specifies the group of

radio
resources
to
which the TRX belongs.
list
comprising
a
maximum of 12 items,
whereby each item is a
trxLayer.
RNP
MaxValue: 12 =
LY11
GLLCOM
HSCSDLayerList
Primary
BTS

MaxValue: 12 =
LY11
HSCSDLLPRM
HSCSDLayerList
Complementary
BTS

MaxValue: 12 =
LY11
HSCSDLLCOM
layerId
LAYERID
A50016-G5000-H219-1-7618
TRX
string Min Value: 0 = LY0

Max Value: 12 =
LY11
21

Name
downgradeStrategy
Objec
t
Unit
BTS
Range (min...max)
Default
Value
Description
Classifi
cation
Describes the type of

resource
reallocation
procedure
to
be
employed according to
the preferred allocation
channel selected.
RNP
MinValue: 0
DGRSTRGY
MaxValue: 4
0=
HSCSD_FIRST_DO
WNGRADE
1=
GPRS_FIRST_DO
WNGRADE
2=
DOWNGRADE_HS
CSD_ONLY
3=
DOWNGRADE_GP
RS_ONLY
4=
NO_DOWNGRADE
Table 3: Properties
2.2.2
Changes of the existing parameters

On SCAN object new measure and counters shall be added; CREATE, SET, GET,
ADD and Remove commands must be modified in order to allow the new
measurement configuration. More in detail, the following attribute values shall be
added, in the object SCANBTS to the attribute MEASLST, CHALNHLY, MEBUTSLY.
GET INFO REPORT for object BTS, BTSE and TRX shall include for each TRX the
related LY, and for each Busy Channel the service active on that channel.
2.2.3
New Measurements
To supervise this feature the existing counters have to be changed:
NAVTCH: if there are channels belonging to a layer reserved for packet services only,
these channels shall also not be counted among the number of available TCH.
NDEFPDCH: if there are configured channels, belonging to a layer reserved for packet
services only, these channels shall be counted too.
NAVPDCH: if there are configured and aligned channels, belonging to a layer
reserved for packet services only, these channels shall be counted too.
2.2.3.1
MEBUTSLY: Mean number of busy channels per layer

Description:
This measurement provides the mean number of busy

channels per layer (LY).
Object Class:
SCANBTS
Measurement Type:
MEBUTSLY
Measurement Depth: per file (reporting)
22
A50016-G5000-H219-1-7618

Reporting Layout:
meas_set field dependent = 0/1
Number of Counters: Standard cells: 36 (3*12)

Extended cells/concentric cells, single or dual band/dual band
standard cells: 72 (3*12*2)
Counter Type:
sampled mean
Counter Unit:
per service layer
Counter Sequence 1: The results for this measurement when applied to standard
cells are: 36 (3*12) counters that cover 3 different speech
types (CS FR, CS HR, CS PO) and a maximum of 12 layers,
each comprising
a group of radio resources (TRXs)
Counters 1-3*):
Mean number of busy channels for FR in LY1

Mean number of busy channels for HR in LY1
Mean number of busy channels for PO in LY1
*) Please note that these counters are available on each of the 12 layers, which
means that counters 4, 5, and 6 are for LY2, 7, 8, and 9 for
LY3, etc.
Counter Sequence 2: The results for this measurement when applied to extended
cells/concentric cells, single or dual band/dual band
standard cells 72 (3*12*2) counters that cover 3 different
speech types are: (CS FR, CS HR, CS PO) and a maximum of
12 layers, each comprising its own group of radio resources
(TRXs) for each of 2 separate areas (SLPA and SLCA) as
described below:
Counters 1-3*):
Mean number of busy channels for FR in LY1 in SLPA

Mean number of busy channels for HR in LY1 in SLPA
Mean number of busy channels for PO in LY1 in SLPA
*) Please note that these counters are available on each of the 12 layers, which
means that counters 4, 5, and 6 are for LY2, 7, 8, and 9 for LY3, etc. That means 36
counters each to cover the SLPA and SLCA areas.
2.2.3.2
CHALNHLY: Number of channel allocation requests not served in

the highest layer or not served at all, per service type
Description:
This measurement provides per service type, the number of channel

allocation requests not served in the highest priority layer, or not served
at all, even if resources are available in the cell but they are in layers
not allowed to the particular service. This measurement will step if a
request to allocate a channel is not served in the first layer (LY) of the
Service Layer List (SLL) or it is not served at all. Moreover 9 additional
counters are provided in order to counts the total number of channel
requests per service type.
Object Class:
SCANBTS
Measurement Type:
CHALNHLY
A50016-G5000-H219-1-7618
23

Measurement Depth: per file (reporting)
Reporting Layout:
meas_set field dependent = 0 only
Number of Counters: Standard cells: 27 (3*9)

Counter Type:
simple counter
Counter Unit:
per service layer
Counter Sequence:
The results for this measurement are: 27 (3*9). That means

that the 9 counters described below are available for 9 different
speech types and 3 different types of requests: served in the
highest LY, not served at all and served.
Counters 1-9*):
Signalling (SDCCH), not in the highest LY

CS speech, not in the highest LY
CS speech AMR FR, not in the highest LY
CS speech AMR HR, not in the highest LY
CS data, not in the highest LY
HSCSD, not in the highest LY
GPRS, not in the highest LY
EGPRS, not in the highest LY
ASCI, not in the highest LY
*) Please note that these counters are available for each of the following request
types: served in the highest LY, not served at all and served.
2.3
Motivation to Introduce the Feature

Based on their market strategy, different operators consider different services with
different importance. The flexible configuration capabilities offered by the proposed
approach provide means to fulfill these requirements in a flexible way.
Changes of the operators service policy e.g. due to an increasing proportion of data
traffic or introduction of new services, can be addressed by simple reconfiguration.
2.4
Interdependencies with other Features

The introduction of this feature results in a high impact in resource allocation. It must
be deeply reworked due to fragmentation of resources. It is required to enhance the
efficiency of looking for resources.
The calculation of both, the number of busy and configured traffic channels, for
features like cell load dependent half rate activation, enhanced pairing, AMR
compression HO and traffic HO should take into account that the percentage of busy
channels must now be evaluated only on the TRXs of the cell whose levels are
included into the SLLs for the relevant CS services.
In case Direct Assignment feature is enabled due to impossibility to know at first
access which service is requested (no information available in Channel Request) a
channel must be found in the Layer allowed to support speech services. In case the
service requested is different from speech, and is not allowed for the selected
24
A50016-G5000-H219-1-7618

Channel, on reception of Assignment Request the call must be moved to an
appropriate LY.
In case of dual area cell (EXTENDED, DUAL BAND, CONCENTRIC) one SL for each
area has to be built in: SLPA (service list primary area) for the primary area and SLCA
(service list complementary area) for the complementary area.
Moving speech and data calls to the preferred types of carrier is done by Forced
Intracell Handovers. Thus the enabling of this feature is very important for SDCA.
ENFOIAHO is the attribute that enables the forced intracell handover procedure.
Pre-emption, Directed Retry and Queuing allow the assignment of TCH when, due to
the unavailability of the resources, no empty channel can be found within the serving
cell. Three main procedures are possible:
Pre-emption: This is a means of releasing TCHs for high priority TCH request; a
forced HO is carried out for a pre-empted call.
Directed Retry: causes the handover to a TCH of another cell; see FRS 0528.
Queuing: allows queuing of TCH requests see FRS 0188.
New measurements types should be split accordingly, if FRS1920 New Organisation
of Performance Measurements will be implemented.
There is change in BR8.0 with respect to Horizontal/Vertical allocation. According to
the feature, it will be possible to have dedicated static resources for packet services
(i.e. dedicated layers for packet).The system will apply Horizontal Allocation on the
Reserved Channels (Dynamic Channels plus Static channels) till available even if the
results of calculation algorithm indicates VA.
2.5
Interdependencies with other Technologies

No impact on other technologies foreseen.
2.6
2.6.1
Further Issues
Discussion of OEM Products
Not considered yet.
2.6.2
Norms
Not applicable.
2.7
Open Issues
No open issues.
A50016-G5000-H219-1-7618
25

3 Dimensioning Aspects (Acquisition Level)

Nowadays mobile networks are voice dominated. In order to increase the capacity,
decrease of C/I is considered. On the other hand, data traffic, especially in case of
EDGE imposes higher requirements for C/I. Higher C/I ratio is also required for fax,
transparent data connections, as well as for CS-3 and CS-4.
One approach to address these contradicting requirements is to separate frequencies
allocated in one cell into different groups with different reuse factors. The proposed
strategy will allow the operator to assign service requests of different types (voice, fax,
data) to these different frequency groups in an optimum way, thus allowing a
significant increase of voice capacity, while maintaining optimum conditions for data.
As an example it is possible to plan one Layer with high C/I. This Layer includes the
BCCH, all SDCCHs and serves preferably data calls. Another Layer which is mainly
used for speech calls is planned with a higher reuse of frequencies, resulting in a
lower C/I, but higher capacity.
3.1
Affected Services and Quality of Service Definitions,

used Traffic Models
Feature defines layers with different quality. Services demanding higher quality and
thus better C/I ratio can be combined with appropriate TRX from the SLL. Less
demanding services as a voice could use worse channels, with lower reuse factor, and
thus higher capacity. Therefore main impact on the dimensioning phase is mostly
foreseen on the capacity. Services calculated with the use of C/I distribution are
affected.
For the no-real time applications the throughput is defined as the mean capacity of the
TCH. It is varying as functions of the C/I, and its distribution. Therefore in case of C/I
conditions degrading, and thus throughput decreased, transmission of the same
amount of data required increased amount of time.
The dimensioning of the real time services is performed by quality of service targets.
Therefore taking into account that C/I is good enough for the service, the blocking rate
is only considered. It is worth to mention that GoS targets shall be considered only
with reference to the resources pool available for particular service. It means that e.g.
blocking figures for voice shall be checked with respect to the number of TS available
to voice according to the SLL strategy.
Also features sensible to load activation thresholds shall take into account number of
resources available according to the SLL strategy.
3.2
Relevant BSS Specification and Configuration Limits

Hardware is not affected.
26
A50016-G5000-H219-1-7618

3.3
Impact on Existing Dimensioning Methods

As stated in chapter 3.1 the feature impact is mostly foreseen on the capacity. It is
related to possibility of use different reuse factors for the different quality targets of
related services. For the less-demanding services channel reuse can be higher and
thus total network capacity increased.
3.3.1
Service list
The feature proposes sets of 9 services. At the dimensioning phase some
simplification can be done. It should be possible to distinguish voice and data
services. Then services can be grouped taking into account dimensioning methods.
Signaling channels dimensioning is performed based on SDCCH traffic per user. By
default layer of best quality has to be selected for this service.
CS type services as speech and HSCSD are dimensioned the same way based on
blocking constraints. In case the same resources are designed for both services
multidimensional ErlangB formula can be used. But in case we assume flexible
services allocation this assumption is no more valid. For this reason separate
dimensioning have to be applied. Have to be noted that trunking gain is lost in this
case.
ASCI related services as more complex are not considered in standard dimensioning
tools, for this reason can be excluded from dimensioning services list.
CS speech AMR is dimensioned the same way as standard speech codec. Quality
dependent HR activation could be simulated by entering percentage of TS in HR (as
far as static simulation is considered). Codec selection dependant on channel quality
is not considered in dimensioning phase. The gain of increased resistance on worse
channel quality can be simulated via soft blocking figures. So CS speech AMR
services can be dimensioned as standard CS speech.
CS data dimensioned by blocking constraints can be treated as normal CS speech
calls.
Taking into account consideration above the following service types for dimensioning
phase can be distinguished:
1. Signaling (SDCCH)
2. CS speech
3. HSCSD
4. GPRS
5. EGPRS
Service priority is assigned by the position of service name in SL. Obviously signaling
services have to have highest priority. Priorities of voice and data services as well as
CS and PS depend on operator policy.
A50016-G5000-H219-1-7618
27

3.3.2
Layer LY
Layers shall be prepared taking into account different channel quality. The different
reuse factors can be used for each channel. High frequency reuse means short
distance between same carriers, high traffic capacity but low C/I ratio (i.e. worse
interference).
Different reuse factors allow higher capacity assuming that channels for lowdemanding quality, as a voice could be planned with higher reuse, and for the more
demanding services better quality can be achieved due to lower reuse factor.
It is required that all signaling channels shall be assigned to a default Layer (LY0) with
the best quality achievable. It is obvious that LY0 have to contain BCCH channel.
For dimensioning process approach with the first layer (LY0) reserved for BCCH, and
the second one (LY1) for all the remaining TRXs seems reasonable. Creation of
further channel groups may cause dimensioning process too complicated.
3.3.3
Resources assignment
Using the feature allows each service to connect to the corresponding channel which
fits the best service requirement towards quality. Different channel quality is related to
different C/I distributions.
Service List
LY1
T
R
LY 2
Service 1
T
R
Service 2
LY 3
LY 4
T
R
Service 3
List of services
Enabling the
enabled in a cell
area
allocation of
resources
Figure 1: SDCA resources allocation

Allocation of resources to incoming call is performed by the following algorithm:
1.
2.
3.
4.
5.
28
Identify applicable service type

Lookup respective SLL and determine Layer with highest priority
Try to allocate resources in this Layer
If no resources can be allocated, go one step down in the Layer priority list
Repeat this procedure until a channel is found or the Layer priority list is
exceeded.
A50016-G5000-H219-1-7618

6. If no resource can be allocated, preemption, directed retry and queuing
procedures shall be triggered. It depends on features enabling on the cell basis.
Allocation of resources within a Layer (step 3 of the above list) works as follows:
1. Out of the free resources within the channel group, apply already used channel
allocation algorithms to select the most appropriate resource.
2. If not enough resources are available, try to move other, ongoing calls with lower
priority within the Layer to other channel groups (priority HO). Alternatively and
depending on corresponding service type attributes, ongoing multi slot
connections might be downgraded by reducing the number of assigned time slots.
3. Finding a new resource for the call displaced by a priority HO follows the same
algorithm as described for an incoming call, however, starting one step down in the
Layer priority list for the respective service type.
4. To avoid recursive chains of priority HO, step 2 (initiation of priority HO) is only
executed to free resources for an incoming call, not for a displaced call.
It is assumed that if for a specific service the allocated resources are not on the best
LY the system shall try to move the Ms on the LY on top of SLL.
All signalling channels are assumed to be on LY0 (BCCH) carriers.
3.3.4
Resources assignment example

Let us assume the following services list:
Priority
Service Type
Signaling (SDCCH)
CS speech
GPRS
HSCSD
Table 4: Services List example

Position of the service in the service list corresponds to the service priority.
Then Layers and Service Layer List can be defined. We assume 3 TRXs in the cell:
BCCH and 2 TCH. So 2 Layers could be created:
LY0 (BCCH)
LY1 (TCH1, TCH2)
Then SLL can be created:
SLL0 (LY0)
SLL1 (LY0, LY1)
SLL2 (LY1, LY0)
A50016-G5000-H219-1-7618
29

It means that for SLL0 services will be allocated on BCCH only and in case of SLL1
system will look for resources on BCCH, and in case of channel congested will move
to TCHs. For SLL2 the services allocation will take place on TCHs and in case of
congestion on BCCH.
SLL0 is default for signaling services. SLL1 is created for data services requiring
higher quality. It should be noted that the same hopping law is recommended for
GPRS services so we assume TCHs not hopping in our example. SLL2 is designed for
less demanding services.
After creation of SL and SLL, resources assignment table can be created. It should
follow operator allocation policy. By default LY0 is reserved for signaling services.
Assumed that operator is interested in high throughputs for PS data we allocate such
a data on LY1. Voice and HSCSD are allocated on LY2. Thus following table could be
created:
Priority
Service Type
SLL
Signaling (SDCCH)
SLL0 (LY0)
CS speech
SLL2 (LY1, LY0)
GPRS
SLL1 (LY0, LY1)
HSCSD
SLL2 (LY1, LY0)
Table 5: Resources assignment example

The following scenarios for each service are possible:
Signalling as layer for this service is restricted to BCCH only and it has the
higher priority it always have to be allocated on BCCH.
CS speech TCHs have the highest priority within the SLL2, so firstly
resources are allocated on these TRXs. If the channels are congested system
looks for resources on the next layer in the SLL2 LY0 (BCCH). Apart from
signalling CS speech has the highest priority in the services list. If there are no
resources, the system will try move other, ongoing calls with lower priority within
the SL, to other channel groups (priority HO).
GPRS firstly it is allocated on LY0 (BCCH), then in case of congestion on
TCHs. It can be downgraded by voice.
HSCSD has the lowest priority.. Firstly it will be allocated on TCHs and then on
BCCH.
3.4
Summary of Dimensioning Rules

The SL for BR 8.0 shall contain maximum 9 entries.
If one service is not present in the SL is intended as not supported in that cell.
Signalling shall be foreseen in SLPA only.
GPRS/EGPRS will not be included in SLCA in case of concentric cell.
The Layer (LY) shall contain radio channels (TRXs) with expected same radio
quality and the same characteristics.
Maximum 12 layers can be created within a standard cell.
30
A50016-G5000-H219-1-7618

In case of dual area cells or dual band standard cells the total number of layers
remains 12.
LY0 and LY1 are used by system as default value in order to maintain the
existing behaviour.
It is recommended to place signalling channels on the same layer which groups
TRXs of the same radio quality.
If TCH/SD are configured, for the ones included in the SDCCH_POOL the
same rule as for signalling applies.
TCH/SD within TCHSDPOOL that can be shared on demand between TCH and
SDCCH has to be grouped in an own LY.
LY1 is used as default value on traffic channels: it has to be assigned to TCH/F,
TCH/FH or TCH/SD configured as TCH.
A new LY can be added or removed from a SLL using SET command without
service interruption.
It is recommended to perform changes inside the LY during low traffic load.
For non hopping system it is recommended to assign to the same layer TRXs
For hopping system it is recommended to assign to the same layer
TRXs/CHANs belonging to the same hopping laws, including list of frequencies
One LY can belong to different Service Layer List (SLL) with same or different
priority. The LY priority is valid inside the single SLL then the same LY inserted in
different SLL can have same, less or more priority.
It is recommended the same hopping law for all channels referenced to
HSCSD, GPRS or EDGE.
All channels belonging to Channel groups referring EDGE services shall be
allocated on carrier unit EDGE capable.
If no resource can be allocated, preemption, directed retry and queuing
procedures shall be triggered.
3.5
Rules for Phase-Oriented Offers

The feature allows changing of the operators service policy. Resources reassignment
can be triggered by increasing proportion of data traffic or introduction of new services.
It should be noted that gain achieved by tighter reuse of frequencies is related to
additional decrease of service due to new handovers.
Increasing number of services to be handled has to be inline to available resources.
The feature assumes few groups of channels with various qualities. Therefore
frequency planning process is impacted. Planner has to keep in mind that
reorganization of resources assignment may require revision of existing frequency
plan, adding new TRXs or tighten reuse for some group to increase quality of others.
3.6
Impact on existing Planning Manuals (PMNs)

Impact on BR8.0 Offer PMN is considered here. The following topics shall be
mentioned:
A50016-G5000-H219-1-7618
31

Feature overview
The aim of this feature is to provide the customer with the possibility of configuration of
the radio resources allocation process in an optimised way making free the customer
to realise the best compromise between services and radio quality needed. It is
performed by separating frequencies allocated in one cell into different groups with
different reuse factors. Then service requests of different types (voice, fax, data) can
be assigned to these different frequency groups. It allows significant increasing of
voice capacity, while maintaining optimum conditions for data.
In order to reach this goal three new concepts are inserted in the SBS system:
Service List (SL) - a list of services supported by the cell with reference to SLL
(see below) for each entry. The order of insertion service type in SL represents the
service priority and shall be used in case of resource assignment.
Layer (LY) - a group of radio resources with the same expected radio quality, a
maximum of 12 LY for each cell area can be allocated.
Service Layer List (SLL) - a list of LY that can be used for a specific service. For
each service, at cell basis, it shall be possible to build up a SLL, the order of the
insertion of LY in the SLL represents the priority used by the system in order to find
a new resource for a specific service.
Dimensioning aspects
Feature considers layers with different C/I distributions. Services demanding better C/I
ratio can be allocated on appropriate TRX of the layer from the Service Layer List
(SLL). Less demanding services could be allocated on channels with lower reuse
factor, and thus higher capacity. Therefore main impact on the dimensioning is mostly
foreseen on the capacity. Services calculated with the use of C/I distribution are
affected.
Service List
Service List for dimensioning phase should distinguish voice and data services. Then
services can be grouped taking into account dimensioning methods.
Signalling services have to be allocated on the channel of best quality.
CS type services as speech and HSCSD are dimensioned based on blocking
constraints. Services can be dimensioned together by mean of multidimensional
ErlangB formula only in case if they occupied the same resources, otherwise separate
dimensioning has to be applied.
The following service types for dimensioning phase can be distinguished:
1. Signalling (SDCCH)
2. CS speech
3. HSCSD
4. EGPRS
5. GPRS
Service priority is assigned by the position of service name in SL. Obviously signalling
services have to have highest priority. Priorities of voice and data services as well as
CS and PS depend on operator policy.
32
A50016-G5000-H219-1-7618

Layers
Layers shall be prepared taking into account different channel quality. The different
reuse factors can be used for each channel.
Different reuse factors allow higher capacity assuming that channels for lowdemanding quality, as voice could be planned with higher reuse, and for more
demanding services better quality can be achieved due to lower reuse factor.
All signalling channels shall be assigned to a default Layer (LY0) with the best quality
achievable. It is obvious that LY0 has to contain BCCH channel.
For dimensioning process simplified approach with the first layer (LY0) reserved for
BCCH, and the second one (LY1) for all the remaining TRXs seems reasonable.
Creation of further channel groups may cause dimensioning process too complicated.
Resources allocation
1. Allocation of resources to incoming call is performed by the following algorithm:
2. Identify applicable service type
3. Lookup respective SLL and determine Layer with highest priority
4. Try to allocate resources in this Layer(see below)
5. If no resources can be allocated, go one step down in the Layer priority list
6. Repeat this procedure until a channel is found or the Layer priority list is
exceeded.
7. If no resource can be allocated, preemption, directed retry and queuing
procedures shall be triggered. It depends on features enabling on the cell basis.
Allocation of resources within a Layer (step 3 of the above list) works as follows:
1. Out of the free resources within the channel group, apply already used channel
allocation algorithms to select the most appropriate resource.
2. If not enough resources are available, try to move other, ongoing calls with lower
priority within the Layer to other channel groups (priority HO). Alternatively and
depending on corresponding service type attributes, ongoing multi slot
connections might be downgraded by reducing the number of assigned time slots.
3. Finding a new resource for the call displaced by a priority HO follows the same
algorithm as described for an incoming call, however, starting one step down in the
Layer priority list for the respective service type.
4. To avoid recursive chains of priority HO, step 2 (initiation of priority HO) is only
executed to free resources for an incoming call, not for a displaced call.
Rules
Please refer to chapter 3.4.
A50016-G5000-H219-1-7618
33

3.7
Impact on existing Offer Tools, possible Workarounds

As feature considers improvements of radio resources no impact on QandD is
foreseen.
The feature is implemented into the GERAN offer tool v. 2.0. The simplified approach
suitable for offer tool is applied. SL is restricted to voice, (E)GPRS and HSCSD
services. It shall be noted that there is no possibility to define EGPRS and GPRS in
the same region. Layers are restricted to BCCH and TCH like channels. Such a
distinction is related to channel quality; tool assumes BCCH as channel of better
performance and not hopping. Taking also into account that number of each type
channels depends on services allocation, few BCCH - like channels could appear in
the region considered.
The tool allocates services to resources according to user selection. Simplified
approach of services allocation order is taken. Firstly signalling services are allocated,
then (E)GPRS and HSCSD then free resources are allocated to voice.
The number of timeslots allocated to signalling depends on the number of users
allocated within the cell. The service is statically allocated on BCCH carrier, which is
assumed to be carrier with the best quality.
Number of HSCSD reserved timeslots is defined by user. Timeslots reserved for
(E)GPRS are obtained from the calculations of (E)GPRS section.
Number of BCCH carriers is obtained taking into account number of timeslots
allocated. Number of TCH carriers is obtained taking into account total number of
TRXs and already allocated BCCHs.
The program flow for allocation of resources is presented in the figure below.
34
A50016-G5000-H219-1-7618

1. Reading allocation scenario: GPRS, HSCSD allocation

BCCH/TCH, Voice allocation BCCH/TCH/BCCH+TCH
2. Number of timeslots required for (E)GPRS and HSCSD,

Reading number of TRX: N_TRX, Assumption: 1 TS for
signalling.
5. Allocating (E)GPRS
6A. (E)GPRS on BCCH
6B. (E)GPRS on TCH
7. Allocating HSCSD
8A. HSCSD on BCCH
8B. HSCSD on TCH
9. Calculates number of BCCH carriers: N_BCCH

number of TCH carriers: N_TCH = N_TRX - N_BCCH
10. Allocating voice
11A. voice on
BCCH
Calculates
number of free
TS on BCCH
and allocating it
by voice trunks
(HR/FR)
11B. voice on
TCH
Calculates
number of free
TS on TCH and
allocating it by
voice
trunks
(HR/FR)
11C. voice on
BCCH + TCH
Calculates
number of free
TS on BCCH
and TCH and
allocating it by
voice
trunks
(HR/FR)
14. Calculating number of voice users per cell

15. Estimating signalling traffic, checking if number of TS is
enough, if not increase number of TS required for signalling
by 1 and skip to step 3
16. Writing results
Figure 2: GERAN Offer Tool SDCA program flow

The workaround for restriction of only one service type EGPRS or GPRS in one region
is to define each service in separate region.
Services prioritization within SL is not required during dimensioning phase due to fact
that it is valid for congestion management. Tool calculates resources to serve all the
services, so there is no congestion considered at the dimensioning phase.
A50016-G5000-H219-1-7618
35

3.8
Open Issues
No open issues.
36
A50016-G5000-H219-1-7618

4 Implementation aspects (Realisation Level)

4.1
Ordering
Ordering phase considers more detailed approach. Number of layers is increased, and
more services shall be taken into account comparing to dimensioning phase. In
general planning process comprise of the following steps:
Planning of the layers Multiple Reuse Patterns
Selection of the services and their priorities
Assigning layers to the services allocation strategy
4.1.1
Affected Services and Quality of Service Definitions, used Traffic

Models
See chapter 3.1.
4.1.2
Relevant BSS Specification and Configuration Limits

See chapter 3.2.
4.1.3
4.1.3.1
Impact on Existing Planning Methods

Multiple reuse patterns planning
In order to create layers of different quality Multiple Reuse Patterns (MRP) has to be
used. MRP is an extension of dedicated bands (BCCH, TCH) strategy that enables
gradual tightening of reuse. As the capacity requirements increase, more TRXs can be
installed without total frequency re-planning (assuming that there are still unused
frequency resources available).
The basic principle of MRP is to divide the available spectrum into sub-bands, each
containing a different number of carriers. These sub-bands are subsequently planned
separately. As a consequence, a network may operate with several reuse patterns
simultaneously.
Firstly BCCH and TCH carrier distinction has to be made. Then TCH spectrum is
further divided into several layers, each layer is planned separately with a different
reuse factor.
LAYER 3
<- allocated frequency band ->

LAYER 2
LAYER 1
LAYER 1 (BCCH)
LAYER 2 (TCH)
LAYER 3 (TCH)
Figure 3: Multi Reuse Pattern Strategy
A50016-G5000-H219-1-7618
37

The following rules have to be maintained during spectrum division:
The subset with the number of carriers allowing the highest C/I is used
exclusively to plan the BCCH channels.
The subset with the number of carriers allowing second highest C/I is used
exclusively to plan the first traffic (TCH) channels.
The subset with number of carriers allowing third highest C/I is used exclusively
to plan the second traffic (TCH) channels.
Please note that resources layering may results in a degraded performance e.g.
decreased hopping gain due to lower number of hopping frequencies. Carrier can
belong to the one layer only.
4.1.3.2
Services List
Before feature introduction planning process considers only distinction to speech and
data services. Now it is more complicated as we have to consider list of 9 services. It
is obvious that services list shall follow general operator policy and network
capabilities, e.g. EGPRS service cannot be selected if cell doesnt support it.
The Service List has to be configured per cell. Separate Service Lists must be
maintained per area in case of dual area cells, i.e. concentric cells using single/dual
bands or extended cells.
The Service List of the complete or far area is referred to as the Service List of the
Primary Area (SLPA). The Service List of the inner or near area is referred to as the
Service List of the Complementary Area (SLCA).
For dual band standard cells, an SLPA belongs to the area that supports the radio
frequency band using the BCCH or PBCCH. Please note that GPRS is not available in
specific cell areas, e.g. in the inner areas of concentric cell structures, although both
dual band standard cell areas support it. EGPRS needs transceivers that are capable
of satisfying its service requirements. Thus, database administrators need to maintain
the consistency of both SLPA and SLCA lists.
If the cell is Standard, Extended (far), Concentric (complete), Dual Band Standard
there is SLPA Primary List:
0)
1)
2)
3)
4)
5)
6)
7)
8)
CS EFR FR HR
CS AMR FR
CS AMR HR
CS DATA
HSCSD (not present in case of extended cell)
GPRS
EGPRS
ASCI (BCCH band in case of Dual Band Standard cell)
SIGNALLING (BCCH band in case of Dual Band Standard cell)
If the cell is extended (near), Concentric (inner), there is SLCA Complementary List:
0) CS EFR FR HR
1) CS AMR FR
38
A50016-G5000-H219-1-7618

2)
3)
4)
5)
6)
CS AMR HR
CS DATA
HSCSD
GPRS ( not present in case of concentric cell)
EGPRS (not present in case of concentric cell)
In case of Concentric Extended or Dual Band standard cell if the service is supported
in both areas, the operator has to associate a Layer List to each area: Service List
Primary Area (SLPA) and Service List Complementary Area (SLCA).
Cell Type
Primary Area
Complementary
Area
Concentric Cell
Complete
Inner
Extended Cell
Far
Near
Table 6: SLPA and SLCA assignment

There are some services that can be supported just in one area. The Service Lists that
can be created by the operator depending on the cell type and the service type are the
following:
Concentric Cell
Service Type
SLPA
SLCA
Signaling
CS speech EFR-FR-HR
CS speech AMR FR
CS speech AMR HR
CS data
HSCSD
GPRS
EGPRS
ASCI
Table 7: Services List for Concentric Cell
A50016-G5000-H219-1-7618
39

Extended Cell
Service Type
SLPA
Signaling
CS speech EFR-FR-HR
CS speech AMR FR
CS speech AMR HR
CS data
HSCSD
SLCA
GPRS
EGPRS
ASCI
Table 8: Services List for Extended Cell

Dual Band Standard Cell
Service Type
SLPA
Signaling
x (BCCH band only)
CS speech EFR-FR-HR
CS speech AMR FR
CS speech AMR HR
CS data
HSCSD
GPRS
EGPRS
ASCI
x (BCCH band only)
SLCA
Table 9: Services List for Dual Band Standard Cell

Dual Band Standard Cell behavior is like the Standard cell, but it will be possible to
define layers on two different bands (i.e. 900/1800 and 850/1900).
DMA can be applied only to layers dedicated to CS speech and with frequencies
defined within a single band i.e. layers only 900 primary band or 900 extended band
or 1800 or 850 or 1900.
ASCI has to be configured in BCCH band.
4.1.3.3
Assigning layers to the services

Assigning layers to the services shall take into account operator policy and obviously
services demands towards quality factors.
In general the following rules can be applied:
Top quality layers for signaling and GPRS/EGPRS, HSCSD services
40
A50016-G5000-H219-1-7618

Normal, medium quality layers used for EFR, FR, HR services
Low quality layers used for AMR
However strategy depends on the operator goals.
The operator will assign a list of Layers to the SLPA and the SLCA (when allowed, see
tables above). A Layer can contain resources belonging to different Areas, it means
that in a single Layer can be present TRX defined in the Primary Area and TRX
defined in the Complementary Area:
In case of Concentric cell TRXs defined in the complete area and TRX defined in the
inner area can belong to the same Layer.
In case of Extended cell a TRX can contain channels in far area (double channels) or
in near area (single channels) so it is allowed to have resources in far area and near
area in the same Layer.
The same Layer can be associated to both the SLPA and the SLCA.
The Layer sequence associated to the SLPA and the SLCA give also the priority
values among the different Layers, the first Layer has highest priority and the last one
the lowest.
4.1.3.4
Conventional allocation vs. SDCA

In the following example comparison of cell capacity is performed.
Assumptions:
10 MHz Spectrum = 48 frequencies (f)
AMR penetration: 50%
EFR penetration: 50%
BCCH planning in reuse 4/12,
Traffic 20 mErl/subscr., Blocking prob. 2%
Signaling 4 mErl/subscr., Blocking prob. 0.5%
Data services not considered
Base scenario (no SDCA):
No separation between EFR and AMR calls,
Poor quality in EFR in tight reuse for loaded cells => allocation of all voice
services in reuse 4/12
Common frequency reuse planning 4/12 for BCCH and TCH
48f - 12f (BCCH) = 36f for TCH
36/12 = 3 TCH freq.
3TCH + 1 BCCH = 4 freq./cell
32 channels (BCCH + 2 TCH carriers) - 3 signaling channels = 29 channels
19.48 Erl/cell
974 subscr./cell
Scenario with SDCA:

SDCA controls that EFR calls will still be allocated on reuse 4/12, and AMR
calls are now being allocated on reuse 1/1
EFR calls:
A50016-G5000-H219-1-7618
41

Separated frequency reuse planning 4/12 for BCCH
48f - 12f (BCCH) = 36f for TCH
2 TCH carrier in reuse 4/12 (EFR) => 36 f - 24 f = 12 f (for reuse 1/1)
AMR calls allocated on TRX planned in tight reuse
12f for TCH, reuse 1/1 => 12 TRX =>96 total traffic channels
24% fractional load => 23 used traffic channels
Number of channels required for signaling
Total: EFR (BCCH + 2 TCH carriers) + AMR (12 TCH) = 15 TRXs
5 TS required for signaling
Total capacity
4.1.3.5
EFR: 24 channels (BCCH + 2 TCH carriers) - 5 signaling channels = 19

channels
11.24 Erl per cell for reuse 4/12 => 562 subscribers with EFR
AMR: 23 used traffic channels
14.48 Erl per cell for reuse 1/1 => 724 subscribers with AMR
Cell capacity: 14.48 Erl +11.24 Erl = 25.72 Erl,
724 subscribers + 562 subscribers = 1286 subscribers
SDCA increase the cell capacity for voice calls
Parameters setting
Example
We can assume operator utilizing (E)GPRS and voice calls on AMR as well as
standard codecs. (E)GPRS traffic is relatively small, and network is oriented towards
high capacity of voice.
Firstly analysis of the required layers has to be made. Obviously non-hopping BCCH
has to provide highest quality. The second layer can be selected for standard voice
codecs, and the third one to the AMR codecs.
Then on a cell basis user has to select which TRXs belongs to respective layer.
LAYERID parameter is used to serve this purpose. Attribute specifies the group of
radio resources which the TRX belongs to.
Let us assume cell consisting of 4 TRXs.
The highest quality BCCH layer: Ly0 (TRX0)
Medium quality TCH layer: Ly1(TRX1,TRX2),
Low quality TCH layers: Ly2 (TRX3)
The following settings of the LAYERID parameter for each TRX have to be set in order
to connect them to the corresponding layer:
TRX0 LAYERID: 0
TRX1 LAYERID: 1
TRX2 LAYERID: 1
TRX3 LAYERID: 2
42
A50016-G5000-H219-1-7618

Then basing on the customer requirements we have to decide which services are
supported in the cell, aligned to the available inputs. As standard cell is considered
only primary set of parameters has to be defined (SLPA only).
Service
Acronym
Signaling
SLLPRM
CS speech EFR-FR-HR
CRTSWSPELLPRM
CS speech AMR FR
AMRFRLLPRM
GPRS
GLLPRM
EGPRS
ELLPRM
Table 10: Example SLPA

Please note that order of services insertion represents priority.
Having layers defined we have to decide on allocation strategy for each service. It is
defined by means of SLL. Top layer of the SLL is allocated first, then in case of first
layer congested further layers are used.
We decide to have (E)GPRS traffic on BCCH, standard voice codecs firstly on BCCH
and then on TCH of medium quality, AMR codecs firstly allocated on the layer of the
low quality and then on the other layers, depending on free resources. In order to do
so the following SLL are required:
SLL0 (Ly0)
SLL1 (Ly0, Ly1)
SLL2 (Ly2, Ly1, Ly0)
In this case layers order represents sequence of services allocation, not the layers
quality.
Complete SLL table for the standard cell:
Service
Ly_00
Ly_01
Ly_02
SLL
SLLPRM
No
No
SLL0
CRTSWSPELLPRM
SLL1
AMRFRLLPRM
SLL2
GLLPRM
No
SLL0
ELLPRM
No
SLL0
Table 11: Example SLL table

Please note that signaling SLLPRM has the highest priority and it always will find
resources on BCCH (SLL0).
A50016-G5000-H219-1-7618
43

Corresponding parameters settings:
e.g.: SET BTS:NAME=BTSM:0/BTS:1,,
Primary table:
SLLPRM=Ly_00,
Signaling on BCCH
CRTSWSPELLPRM=Ly_00&Ly_01,
Standard
voice
codecs,
firstly
allocated on LY2 then on LY1 and LY2
AMRFRLLPRM=Ly_02&Ly_01&Ly_00,
AMR FR codecs, firstly allocated on

LY2 then on LY1 and LY2
AMRHRLLPRM=<NULL>;
AMR HR codec not used
CRTSWDLLPRM=<NULL>;
CS data not used
HSCSDLLPRM=<NULL>;
HSCSD data not used
GLLPRM=Ly_00,
GPRS on LY0
ELLPRM=Ly_00,
EGPRS on LY0
ASCILLPRM=<NULL>;
ASCI not used
Standard cell no complementary table required

All the variables filled with NULL.
CRTSWSPELLCOM= <NULL>,
AMRFRLLCOM=<NULL>,
AMRFRLLCOM=<NULL>,
CRTSWDLLCOM=<NULL>,
HSCSDLLCOM=<NULL>,
GLLCOM=<NULL>,
ELLCOM=<NULL>;
Please note that parameters settings depend on the customer targets.
4.1.4
Summary of Planning Rules

Multiple Reuse Patterns (MRP) are used in order to create layers of different
quality
The subset with the number of carriers allowing the highest C/I is used
exclusively to plan the BCCH channels, the subset allowing second highest C/I is
used exclusively to plan the first TCH channels, subset with number of carriers
allowing third highest C/I is used exclusively to plan the second TCH channels and
so on.
A Layer can contain resources belonging to different Areas, in a single Layer
can be present TRX defined in the Primary Area and TRX defined in the
Complementary Area:
The same Layer can be associated to both the SLPA and the SLCA.
The Layer sequence associated to the SLPA and the SLCA give also the
priority values among the different Layers, the first Layer has highest priority and
the last one the lowest.
44
A50016-G5000-H219-1-7618

For dual band standard cells, an SLPA belongs to the area that supports the
radio frequency band using the BCCH or PBCCH
In case of Concentric or Extended Cell if the service is supported in both areas,
the operator has to associate a Layer List to each area: Service List Primary Area
(SLPA) and Service List Complementary Area (SLCA).
The standard cell (Also Dual Band Standard Cell) will have only the SLPA
created.
There are some services that can be supported just in one area.
Top quality layers for signaling and GPRS/EGPRS, HSCSD services
Normal, medium quality layers used for EFR, FR, HR services
Low quality layers used for AMR
4.1.5
Rules for Phase-Oriented Planning

Feature is oriented towards phase-oriented implementation. At the first phase existing
distinction on BCCH and TCH layers can be maintained. As operator expectations for
higher demanding services and capacity increase, additional layers can be build. It
requires fragmentation of existing bandwidth and frequency re-planning. At this stage
should be kept in mind that next layers extension may require further spectrum
fragmenting. Capacity oriented layers will use tight reuse and higher gains are
expected with AMR for speech services. Data services, if there is not enough
resources on BCCH may require separate layer of high C/I values.
4.1.6
Impact on existing Planning Manuals (PMNs)

See chapter 3.6.
4.1.7
Impact on existing Planning Tools, possible Workarounds

Feature planning considers two cases:
Services allocation strategy is according to customer policy. Planner has to

verify whether it is feasible and provides sufficient services availability.
Optimum allocation strategy has to be proposed by planner. It depends on the

planning targets: maximum coverage, maximum capacity etc. Different
scenarios have to be analyzed.
The feature assumes layers of different quality. Multiple Reuse Patterns (MRP)
frequency planning can be used to serve this purpose.
In the next step user defines services. Services priority is not considered in the tool
due to fact that congestion management features are not modeled (preemption,
downgrade, intracell handover).
The last step performed by user is allocation strategy definition according to customer
input or planner considerations.
Modeling of the feature shall be performed by means of Monte Carlo simulator.
However user has to be aware of some tool restrictions:
Feature requires allocation strategy on the cell basis. Cell based strategy shall
be applied by allocating different layers to the cells.
A50016-G5000-H219-1-7618
45

There is no separate signaling service in the tool. However tool behavior is
inline with the feature assumptions that signaling has the highest priority.
The feature assumes management of shared PDCHs only. In the tool dedicated
and shared pools are treated together. However as far as preemption and
downgrade is not considered in the tool they can be considered as common pool
available for PS.
ASCI broadcast services are not considered.
Tool behavior is static only preemption, downgrade intra cell handover due to
call of higher priority are not considered. It means that services priority in case of
congestion can not be considered. Order of services allocation is related to their
subsequent appearance during simulations. Due to this fact number of subscribers
served will be pessimistic. In the real network resources will be reorganized in
order to allocate incoming call. In the tool in case of resources congested call will
be rejected.
As result planner analyses Monte Carlo arrays. They give information of area where
service is supported and reasons why it is not supported.
The following mapping of the feature behavior into corresponding tool functionality is
foreseen:
Feature
Tool
Layer LY
Cell Layer
Service List SL
Services: different service for each entry from SL
Service Layer List SLL
Services: Carriers/Cell layers tab, priorities
Table 12: Feature functionalities in the tool
4.1.7.1
BSS parameters planning

The first group of parameters defines TRX to Layers associations (LayerID). It is result
of frequency planning.
Second group is related to the services available in the network. Service allocated to
the terminal in the tool means that service is active in the SL.
4.1.7.2
Frequency planning
Layers of different quality have to be created. Multiple Reuse Patterns (MRP) are used
to serve this purpose. Firstly BCCH and TCH carrier distinction has to be made. Then
TCH spectrum is further divided into several traffic layers, each layer is planned
separately with a different reuse factor.
Layers with different C/I conditions are visualized in the pictures below.
46
A50016-G5000-H219-1-7618

Figure 4: Layers of different C/I
4.1.7.3
4.1.7.3.1
Capacity planning
Layers
As already mentioned, layers of different quality are required for the feature. At least
one control and one traffic layer is needed. In TornadoN process of layer creation is
split into carrier layers and cell layers. Number of frequencies available for the carrier
layer reflects expected layer quality.
Figure 5: Carrier Layer configuration

In the next step planner defines Cell Layers and assigns appropriate carrier layers.
A50016-G5000-H219-1-7618
47

Figure 6: Cell Layer configuration

Then user introduces layers to the cell. Please note that cells may contain different
layers.
Figure 7: Cell layers

Layers organisation displayed in the Site Database doesnt correspond to the layers
priority. In the tool this functionality is moved to the services definition.
After layers allocated, frequency planning process have to be performed. Association
of the TRX to the certain layer is performed in the cell layer settings by user (LayerID
parameter).
48
A50016-G5000-H219-1-7618

Figure 8: Layer TRX association
4.1.7.3.2
Services list / SLL

Services List in the tool is defined by means of different Terminal Types for each
service. At the beginning different bearers have to be created by user. Bearer
definition covers maximum user bitrate supported by the bearer (1 TS) and minimum
required C/I on the traffic (TCH) layer. Also technology (Voice, PS) and codec type
(HR, FR, AMR) is stored here.
Figure 9: Bearer settings

Then user creates various services. They are carried by selected bearer. Layers
supporting service are selected in the Carriers/Cell layers tab. Layer allocation order is
defined by their priority. Please note that this step stands for SLL definition for that
particular service.
Example:
Parameter settings related to the Voice service for primary area:
CRTSWSPELLPRM=Ly_03&Ly_02&Ly_01
Transferred into the layers allocation in the tool settings:
A50016-G5000-H219-1-7618
49

Figure 10: Cell Layers supported for Services settings

Please note that BCCH layer always has to be supported by service in order to check
BCCH C/I objectives defined in the Terminal Type settings. Otherwise terminal will not
be served due to low control C/I. In case if Service is forbidden to allocate on BCCH
according to allocation strategy, bearers related to that service shall be excluded for
BCCH layer.
Figure 11: Service excluded from BCCH

Next step is Terminal Type definition. For our purposes we can assume that one
terminal is connected to the one service type only.
50
A50016-G5000-H219-1-7618

Figure 12: Terminal Type definition

Definition of the feature behavior in the tool is finished at this stage. Further procedure
follows normal simulations process: Terminals representing different services will be
spread by traffic array and then used by Monte Carlo during simulations.
As planning results the following arrays related to service can be analyzed:
(Note: probability stands for ratio of terminals served or failed to the total number of
connection attempts)
Coverage probability - displays probability that terminal will be served. Depends
on objectives related to layer C/I - area of service coverage depends on allocation
policy.
Probability of Low Traffic C/I Failure Array - displays probability of failures due
to high interference on the Traffic carrier. Area increases if service demanding high
C/I condition is located on the poor quality layer.
Probability of Low Control C/I Failure Array - array displays probability of
failures due to interference on the control carrier.
Probability of No Cell Timeslot (TS) Available Array - array displays the
probability of no cell timeslots available to transmit. It shows that cell capacity is
exhausted and different allocation strategy is needed or TRX upgrade.
Probability of No Terminal Timeslots (TS) Available Array - array displays the
probability of no terminal timeslots available to transmit (e.g. service demanding
high throughput is allocated to the layer of poor quality).
No servers array - represents the area where no Best Server exists due to
mobile sensitivity.
Downlink Bitrate Array - array displays the mean downlink bit rate for terminals
at each pixel for the selected services.
Cells capacity can be analyzed by means of simulator reports.
A50016-G5000-H219-1-7618
51

Example: GPRS service allocated to the Layer 1 and then to the Layer 2 of higher
quality:
Layer1
Layer2
Figure 13: GPRS Service Coverage probability
Figure 14: Terminals served for Layer 1 and Layer 2

As can be seen in table allocation of the GPRS service to the layer of better quality
results in higher number of terminals served.
4.2
4.2.1
Implementation
Feature introduction strategy
Feature allows flexible configuration capabilities. Feature is compatible with the
previous releases as far as only BCCH/TCH distinction is considered. Introduction of a
new services and changes of the operators service policy may require introduction of
the new layers and revision of the existing frequency plan. If the number of layers is
satisfied, changing of services allocation can be made by simple O&M reconfiguration.
52
A50016-G5000-H219-1-7618

4.2.2
Database Generation
Respective parameters are described in chapter 2.2. The main changes in the existing
database structure:
Modifications on old attributes

1. The DGRSTRGY shall be moved from BSC to BTS object.
2. The attribute GSUP and its related semantic checks shall be removed from TRX
object.
3. The management of CPOLICY attribute shall be removed from BSC object.
The new measures CHALNHLY, MEBUTSLY shall be added to the MEASLST in
SCANBTS object.
New attributes introduced in BTS object

The first group of these parameters specify the list of TRX layers related to each of the
services supported in a single band standard cell, or in the complete/far area of a dual
area cell (extended, concentric single/dual band), or in the BCCH band of a dual band
standard cell:
SLLPRM: signallingLayerListPrimary
CRTSWSPELLPRM: circuitSwitchedSpeechLayerListPrimary
AMRFRLLPRM: AMRFullRateLayerListPrimary
AMRHRLLPRM: AMRHalfRateLayerListPrimary
CRTSWDLLPRM: CircuitSwitchedDataLayerListPrimary
HSCSDLLPRM: HSCSDLayerListPrimary
GLLPRM: GPRSLayerListPrimary
ELLPRM: EDGELayerListPrimary
ASCILLPRM: ASCILayerListPrimary
Possible values:
<NULL>
List (sequenceOf) of max 12 items, each item is
trxLayer
LY0..LY11
Default value: NULL

Commands: CREATE, SET, GET BTS
The second group of parameters specify the different services supported in the
complementary band of a dual band standard cell:
CRTSWSPELLCOM: circuitSwitchedSpeechLayerListComplementary
AMRFRLLCOM: AMRFullRateLayerListComplementary
AMRHRLLCOM: AMRHalfRateLayerListComplementary
A50016-G5000-H219-1-7618
53

CRTSWDLLCOM: CircuitSwitchedDataLayerListComplementary
HSCSDLLCOM: HSCSDLayerListComplementary
GLLCOM: GPRSLayerListComplementary
ELLCOM: EDGELayerListComplementary
Possible values:
<NULL>
List (sequenceOf) of max 12 items, each item is
trxLayer
LY0..LY11
Default value: NULL

Commands: CREATE, SET, GET BTS
New attributes introduced in TRX object

LAYERID
This parameter specifies the group of radio resources to which the TRX belongs.
Validity range:
layerId
LY0..LY11
Default value: LY0

Commands:
CREATE TRX, GET TRX, SET TRX
New semantic checks

The following conditions must be verified:
1. CREATE BTS: On BTS creation, the SLL attributes cannot be different from NULL.
2. SET BTS xxxLLPRM/COM, SET TRX LAYERID, DELETE TRX: The SLL attributes
cannot contain empty layers, i.e. layers not assigned to any equipped TRX: in
order to assign a layer to a service, at least one equipped TRX must have this
layer in LAYERID attribute.
3. CREATE TRX, SET TRX TRXFREQ, SET TRX LAYERID: the TRX with frequency
BCCHFREQ must be assigned to LY0.
4. SET BTS SLLPRM: SLLPRM must always include LY0
5. SET BTS: HSCSD service is not supported in far areas of extended cells: in case
of extended cell (CELLTYP=EXTCELL), HSCSDLLPRM cannot be different from
NULL.
6. SET BTS: GPRS and EDGE services are not supported in inner areas of
concentric cells: in case of concentric cell (CONCELL=TRUE), GLLCOM and
ELLCOM cannot be different from NULL.
7. CREATE BTS, SET BTS ASCISER, SET BTS ASCILLPRM: In order to set the flag
ASCISER to TRUE, the primary layer list of ASCI service (ASCILLPRM) must
contain at least LY0 (in first position).
54
A50016-G5000-H219-1-7618

8. CREATE BTS, SET BTS BTSHSCSD, SET BTS HSCSDLLPRM/COM: The flag
BTSHSCSD cannot be TRUE if both HSCSDLLPRM and HSCSDLLCOM are set
at NULL.
9. CREATE PTPPKF, SET PTPPKF EGPRS, SET BTS GLLPRM/COM: the EGPRS
flag in PTPPKF object cannot be TRUE if both GLLPRM and GLLCOM are set at
NULL.
10. SET PTPPKF EEDGE, SET BTS ELLPRM/COM CREATE TRX, SET TRX
LAYERID, SET TRX TRXMD, DELETE TRX: In order to set the flag EEDGE to
TRUE, every layer assigned to the primary/complementary layer list of EDGE
service (ELLPRM/COM of BTS object) must contain:
- at least one TRX with TRXMD=EDGE, if the layer is not exclusive for EDGE
- all the TRXs with TRXMD=EDGE, if the layer is exclusive for EDGE
11. The xxxLLCOM attributes can be set at a value different from NULL only in case of
dual area cell (extended, concentric single/dual band),
12. SET BTS, SET TRX TRXAREA, SET TRX LAYERID, DELETE TRX: In concentric
cells, every layer assigned to the primary and the complementary service layer
lists for each service must contain at least one TRX belonging to the related area.
13. SET BTS xLLPRM/C, SET BTS CALLFx/BCCHFREQ, SET TRX TRXFREQ, SET
TRX LAYERID, DELETE TRX : In dual band cells, the SLLPRM or SLLCOM must
contain at least one TRX per layer with the frequency belonging to the related
band.
14. SET TRX: LAYERID can bet set only if the TRX is locked.
15. CREATE CHAN, SET CHAN POOLTYP, SET TRX LAYERID, SET BTS
xLLPRM/COM: The TRXs containing signaling channels (including TCHSD
channels with TCHSD or SDCCH pool) must belong to layers assigned to the
signaling service.
16. The semantic checks on multislot requirements for HSCSD or GPRS services
must be checked on the TRXs assigned to the related services.
17. If the BCCH TRX contains GPRS control channels (PBCCH, PCCCH), its layer
(LY0) must be assigned at least to GPRS service if TRXMD=GSM, at least to
EDGE service if TRXMD=EDGE, or to both services.
18. BTS, SET BTS DIRTCHASS, SET BTS SLLPRM: In order to enable DIRTCHASS,
of service SLLPRM must go from more to less shared.
19. SET BTS AMRFRLLPRM/COM, SET BTS AMRHRLLPRM/COM: the
primary/complementary service layer lists related to AMR FR and AMR HR
services must contain the same layers.
A50016-G5000-H219-1-7618
55

20. SET BTS HSCSDLLPRM/COM, SET BTS GLLPRM/COM, SET ELLPRM/COM:

the dedicated layer in each area must be in first position.
21. SET BTS ASCILLPRM, SET TRX LAYERID, SET TRX TRXFREQ, DELETE TRX:
In dual band standard cells, the ASCILLPRM must contain layer with at least one
TRX with the frequency belonging to the band of BCCH.
22. SET BTS GLLPRM/COM: the EGPRS flag in PTPPKF object cannot be TRUE if
both GLLPRM and GLLCOM are set at NULL.
23. SET BTS GLLPRM/COM or ELLPRM/COM, DELETE PTPPKF: the PTPPKF
object must be equipped to have the packed service set different by NULL.
Interdependencies with Parameters of Related Features
In case of Layers exclusively associated to packet services, these channels will not be
counted in the number of available TCH channels. In fact the GMANPRES and the
GASTRTH thresholds will be applied just on the TRXs shared between packet and
other services.
Network Controlled Cell Reselection process have to modify the checks in which it can
determine the band of the serving cell BCCH belong to. Coordination with the feature
of handover from GSM to UMTS due to insufficient coverage and Network Assisted
Cell Change have to be foreseen in order to synchronize identification of the various
types of band also in adjacent cells.
The mobile capabilitys is necessary, in the Dual Band Standard cells, because we
have to apply the algorithm described in FSH87030 (Upgrading of Common BCCH
Implementation) for deciding which resources assign to the mobile ( if in the BCCH
band ( primary area) or no-BCCH band ( complementary area ) ).
4.2.3
Installation requirements
Feature is software related. The only hardware requirement is to install number of
TRXs on site, allowing creation of various layers.
4.2.4
Evaluation of implementation
Not considered yet.
4.2.4.1
Acceptance test procedures

Not considered yet.
4.2.4.2
Performance measurements and counters

Not considered yet.
56
A50016-G5000-H219-1-7618

4.2.4.3
Initial Tuning
Not considered yet.
4.2.5
Impact on existing Network Optimisation Use Cases

Not considered yet.
4.2.6
Impact on existing Network Optimisation Tools

Not considered yet.
4.3
Open issues
No open issues.
A50016-G5000-H219-1-7618
57

Abbreviations
AMR
ASCI
BSC
BCCH
CS
EDGE
EGPRS
Erl
FR
GoS
GPRS
HO
HR
HSCSD
LCS
LMT
LY
MRP
MS
MSLS
MSC
O&M
PBCCH
PCCCH
PDTCH
PS
SDCA
SDCCH
SL
SLL
SLCA
SLPA
58
Advanced Multi Rate

Advanced Speech Call Items
Base Station Controller
Broadcast Control Channel
Circuit Switched
Enhanced Data Rate for GSM Evolution
Enhanced GPRS
Erlang
Full Rate
Grade of Service
General Packet Radio System
Handover
Half Rate
High Speed Circuit Switched Data
Localization Services
Local Maintenance Terminal
Layer
Multiple Reuse Patterns
Mobile Station
Mobile Switching Centre
Operation and Maintenance
Packet Broadcast Control Channel
Packet Common Control Channel
Packet Data Traffic Channel
Packet Switched service, i.e., GPRS and EGPRS
Service Dependent Channel Allocation
Slow Dedicated Control Channel
Service List
Service Layer List
service list complementary area
service list primary area
A50016-G5000-H219-1-7618

PLR 84566 Multi Service Layer Support IUS2.3

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

PLR 84566 Multi Service Layer Support IUS2.3

Încărcat de

Drepturi de autor:

Formate disponibile

s

IUS 2.3 Order Level

Planning Rule FRS 84566

Copyright (C) Siemens AG 2006

Planning Rule FRS 84566

Reason for Update

Reason for Update

Reason for Update

First draft version reviewed by Szymon Nowak.

Review comments implemented. Document covers

AFI version agreed by MS P without feedback.

Changes in chapter 2 due to new version of FRS.

Update of the chapter 4.1.7. Feature name changed

Changes in chapter 4 and 4.2.2 due to review

Planning Rule FRS 84566

General Information (Acquisition Level).........................................................8

General Feature Related Part (Acquisition Level)..........................................9

Dimensioning Aspects (Acquisition Level)....................................................26

Implementation aspects (Realisation Level).................................................37

Planning Rule FRS 84566

Planning Rule FRS 84566

List of Figures and Tables

Planning Rule FRS 84566

FRS Service Dependent Channel Allocation

Planning Rule FRS 84566

1 General Information (Acquisition Level)

Planning Rule FRS 84566

2 General Feature Related Part (Acquisition

Planning Rule FRS 84566

Functional Feature Description (Database Level)

used for speech call applying EFR- FR- HR codec

CS speech AMR FR used for speech call applying AMR FR codec

CS speech AMR HR used for speech call applying AMR HR codec

circuit switched single slot data call allowed to use up to

circuit switched Multislot calls using HSCSD

PDTCH to be allocated dynamically to GPRS services

PDTCH to be allocated dynamically to EGPRS service

broadcast channel to be used for allocating ASCI services

Table 1: BR 8.0 Service List

Planning Rule FRS 84566

Planning Rule FRS 84566

Service Layer List (SLL)

CS DATA up to 9.6 and 14.4

Table 2: SLL example

Planning Rule FRS 84566

SL to the LY allocation strategy

Planning Rule FRS 84566

Planning Rule FRS 84566

Parameters (Database Level)

Planning Rule FRS 84566

Planning Rule FRS 84566

layerId (layer identifier) LAYERID

Planning Rule FRS 84566

List of TRX layers RNP

List of TRX layers RNP

List of TRX layers RNP

List of TRX layers RNP

string MinValue: 1 = LY0

List of TRX layers

Planning Rule FRS 84566

string MinValue: 1 = LY0

List of TRX layers

List of TRX layers

List of TRX layers