3bk 10204 0612 dtzza - e-gsm - support of gprs and signaling in g1 band

ED 02 Released Enhanced E-GSM band handling

0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 1/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

Site VELIZY

EVOLIUM SAS

Originators M. WU

Enhanced E-GSM band handling

System : ALCATEL GSM BSS Sub-system : SYS-TLA Document Category : PRODUCT DEFINITION

ABSTRACT The "Enhanced E-GSM band handling" feature allows the support of (E)GPRS service and of all possible types of signalling channels on frequencies in E-GSM band.

Approvals

Name App.

J. ACHARDR. MAUGER SYT Manager

D. BOMY PL

J.-P. GRUAU PM


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 2/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

REVIEW Ed. 01 Proposal 01 04/11/2003 MND/TD/VAL/SYT/mwu/0358.2003/Ed.1 stored at the URL:

ftp://bssb7:bseven7@bcv68s07/projects_ftp/BSS_B9/B9_Spec_TaskForce/WG2_Tel_notGPRS/SFD/G1_band/203358_1.doc

Ed. 01 Proposal 02 10/12/2003 MND/TD/VAL/SYT/mwu/0358.2003/Ed.1 stored at the URL: ftp://bssb7:bseven7@bcv68s07/projects_ftp/BSS_B9/B9_Spec_TaskForce/WG2_Tel_notGPRS/SFD/G1_band/203373_1.doc



HISTORY Ed. 01 Proposal 01 04/11/2003 First proposal. Ed. 01 Proposal 02 28/11/2003 Updated according the review minutes

MND/TD/VAL/SYT/mwu/0358.2003/Ed.1 Ed. 01 Proposal 03 10/12/2003 Updated according the review minutes

MND/TD/VAL/SYT/mwu/0373.2003/Ed.1 Ed. 01 Proposal 04 09/01/2004 1. Updated according the review minutes

MND/TD/VAL/SYT/mwu/0382.2003/Ed.1; 2. Add OMC impact.

Ed. 01 Released 17/03/2004 1. Updated according the review minutes MND/TD/VAL/SYT/mwu/204004/Ed.1;

2. Add Methods, GCD and Engineering rules impacts; 3. Add paragraph “B8 OMC checks”

Ed. 02 Proposal 01 26/01/2007 Editorial modification. Ed. 02 Released 12/02/2007 No comment received. SFD is released after being checked by

Moderator C. LEJEUNE.


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 3/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

TABLE OF CONTENTS

1 INTRODUCTION ......................................................................................................... 8 1.1 Scope .................................................................................................................................................................... 8

1.2 Document Structure ........................................................................................................................................... 8

1.3 Definitions and pre-requisite ............................................................................................................................. 9 1.3.1 Frequency ranges .......................................................................................................................................... 9 1.3.2 B7.2 implementation (support G1 TRXs in an E-GSM network) ................................................................ 9 1.3.3 B8 implementation...................................................................................................................................... 10 1.3.4 E-GSM capable MS recognition................................................................................................................. 10 1.3.5 System Information Limitation due to support of P-GSM capable only MS.............................................. 11 1.3.6 B8 OMC checks related to the G1 band ..................................................................................................... 11

2 HIGH-LEVEL DESCRIPTION.................................................................................... 12 2.1 Functional Requirements................................................................................................................................. 12

2.1.1 Market view................................................................................................................................................ 12 2.1.2 Requirements for each business case.......................................................................................................... 13 2.1.3 Optionality .................................................................................................................................................. 13

2.2 Overall description of the proposed solutions................................................................................................ 14

2.3 Compliance to 3GPP standard ........................................................................................................................ 16

2.4 Working Assumptions ...................................................................................................................................... 16

2.5 Dependencies ..................................................................................................................................................... 16

2.6 HW Coverage.................................................................................................................................................... 17

2.7 Decision criteria ................................................................................................................................................ 18 2.7.1 Standardisation ........................................................................................................................................... 18 2.7.2 Competition ................................................................................................................................................ 18 2.7.3 Customer..................................................................................................................................................... 18 2.7.4 Gains........................................................................................................................................................... 18

2.7.4.1 Telecom gains ......................................................................................................................................... 18 2.7.4.2 Operational gains .................................................................................................................................... 19

2.7.5 Risks ........................................................................................................................................................... 19

3 SYSTEM IMPACTS................................................................................................... 20 3.1 Telecom.............................................................................................................................................................. 20

3.1.1 Functional-level description ....................................................................................................................... 20 3.1.1.1 Strategy for radio resource allocation in the E-GSM cell ....................................................................... 20

3.1.1.1.1 P-GSM capable only MSs have to be supported in the network (“EGSM_RR_Alloc_Strategy” parameter is set to “0”) ....................................................................................................................................... 20 3.1.1.1.2 All GSM900 MSs in the network are assumed to be E-GSM capable (“EGSM_RR_Alloc_Strategy” parameter is set to “1”) ....................................................................................................................................... 20

3.1.2 Telecom Specification impacts ................................................................................................................... 21 3.1.2.1 Resource allocation and management..................................................................................................... 21


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 4/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

3.1.2.1.1 P-GSM capable only MSs have to be supported in the network (“EGSM_RR_Alloc_Strategy” parameter is set to “0”) ....................................................................................................................................... 21 3.1.2.1.2 All GSM900 MSs in the network are assumed to be E-GSM capable (“EGSM_RR_Alloc_Strategy” parameter is set to “1”) ....................................................................................................................................... 21

3.1.2.2 GPRS Radio Interface - RRM sub-layer (PRH) ..................................................................................... 21 3.1.2.2.1 P-GSM capable only MSs have to be supported in the network (“EGSM_RR_Alloc_Strategy” parameter is set to “0”) ....................................................................................................................................... 22 3.1.2.2.2 All GSM900 MSs in the network are assumed to be E-GSM capable (“EGSM_RR_Alloc_Strategy” parameter is set to “1”) ....................................................................................................................................... 22

3.1.2.3 System Information Management........................................................................................................... 22 3.1.2.3.1 P-GSM capable only MSs have to be supported in the network (“EGSM_RR_Alloc_Strategy” parameter is set to “0”) ....................................................................................................................................... 22 3.1.2.3.2 All GSM900 MSs in the network are assumed to be E-GSM capable (“EGSM_RR_Alloc_Strategy” parameter is set to “1”) ....................................................................................................................................... 23

3.1.2.4 Frequency Encoding Algorithm.............................................................................................................. 23 3.1.2.5 Classmark handling................................................................................................................................. 23 3.1.2.6 Power Control and Radio Link Supervision ........................................................................................... 23 3.1.2.7 Handover Preparation ............................................................................................................................. 23

3.1.3 Interfaces .................................................................................................................................................... 24 3.1.3.1 Radio interface (05.02, 04.06, 04.60, 04.18, 24.008, etc)....................................................................... 24 3.1.3.2 Abis interface (08.58) ............................................................................................................................. 24 3.1.3.3 A interface (08.08).................................................................................................................................. 24 3.1.3.4 Gb interface (08.18)................................................................................................................................ 24 3.1.3.5 BSCGP interface..................................................................................................................................... 24 3.1.3.6 GCH interface......................................................................................................................................... 24

3.1.4 Simulations ................................................................................................................................................. 24

3.2 Operation and maintenance............................................................................................................................. 25 3.2.1 OMC-R parameters..................................................................................................................................... 25

3.2.1.1 New parameters ...................................................................................................................................... 25 3.2.1.2 Modified parameters ............................................................................................................................... 26

3.2.2 Modelisation of OMC-R parameters .......................................................................................................... 27 3.2.2.1 OMC GDMO impacts............................................................................................................................. 27 3.2.2.2 ACIE Interface impacts .......................................................................................................................... 27 3.2.2.3 OMC-BSC interface impacts .................................................................................................................. 27 3.2.2.4 OMC-MFS interface impacts.................................................................................................................. 27

3.2.3 Other parameters......................................................................................................................................... 27 3.2.4 PM counters ................................................................................................................................................ 27

3.2.4.1 Counters in the BSC ............................................................................................................................... 27 3.2.4.1.1 New PM counters............................................................................................................................. 27 3.2.4.1.2 Modified PM counters ..................................................................................................................... 28

3.2.4.2 Counters in the MFS............................................................................................................................... 28 3.2.4.2.1 New PM counters............................................................................................................................. 28 3.2.4.2.2 Modified PM counters ..................................................................................................................... 28

3.2.5 PM indicators.............................................................................................................................................. 28 3.2.5.1 New Computed indicators ...................................................................................................................... 28 3.2.5.2 Impact on existing indicators .................................................................................................................. 28

3.2.6 Migration .................................................................................................................................................... 28 3.2.6.1 OMC Migration ...................................................................................................................................... 28 3.2.6.2 BSC Migration........................................................................................................................................ 28 3.2.6.3 MFS migration........................................................................................................................................ 29

3.2.7 Java scripts.................................................................................................................................................. 29 3.2.8 Fault Management ...................................................................................................................................... 29 3.2.9 O&M Specification impacts ....................................................................................................................... 29

3.2.9.1 LCM specification .................................................................................................................................. 29 3.2.9.2 HCM specification.................................................................................................................................. 29


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 5/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

3.2.9.3 OMC/BSC MIB ...................................................................................................................................... 29 3.2.9.4 OMC/MFS MIB...................................................................................................................................... 29 3.2.9.5 OMC-R export interface for PM data ..................................................................................................... 30

3.3 Validation .......................................................................................................................................................... 30 3.3.1 Testing tools................................................................................................................................................ 30 3.3.2 Test strategy................................................................................................................................................ 30

3.3.2.1 System tests coverage ............................................................................................................................. 30 3.3.2.2 Overall strategy for system tests ............................................................................................................. 30

3.4 Methods ............................................................................................................................................................. 31 3.4.1 New PFD (Field Procedure Designs) document needed............................................................................. 31 3.4.2 Impact on existing FPD documents ............................................................................................................ 31

3.5 GCDs.................................................................................................................................................................. 31 3.5.1 New GCD (Generic Customer Documentation) needed............................................................................. 31 3.5.2 Impact on existing GCD ............................................................................................................................. 31

3.5.2.1 O&M PARAMETERS Dictionary ......................................................................................................... 31 3.5.2.2 BSS System Description......................................................................................................................... 31 3.5.2.3 A1353-RA OLH ..................................................................................................................................... 31 3.5.2.4 BSS Configuration Handbook ................................................................................................................ 31

3.6 Engineering rules .............................................................................................................................................. 31 3.6.1 New documents needed .............................................................................................................................. 31 3.6.2 Impact on existing B8 Engineering documents .......................................................................................... 31

3.6.2.1 BSS Configuration Rules........................................................................................................................ 31

4 SUBSYSTEM IMPACTS ........................................................................................... 33 4.1 BTS..................................................................................................................................................................... 33

4.2 BSC .................................................................................................................................................................... 33

4.3 Transcoder ........................................................................................................................................................ 33

4.4 MFS.................................................................................................................................................................... 33

4.5 OMC-R .............................................................................................................................................................. 33 4.5.1 HMI impacts ............................................................................................................................................... 33 4.5.2 OMC modelization ..................................................................................................................................... 33 4.5.3 Optional feature .......................................................................................................................................... 33 4.5.4 Overview of the impact upon OMC specs.................................................................................................. 34

4.6 LASER............................................................................................................................................................... 34

4.7 MPM/NPA/RNO............................................................................................................................................... 34 4.7.1 MPM/NPA.................................................................................................................................................. 34 4.7.2 RNO............................................................................................................................................................ 34

4.8 Polo..................................................................................................................................................................... 34

4.9 OEF.................................................................................................................................................................... 34

5 PERFORMANCE & SYSTEM DIMENSIONING........................................................ 35


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 6/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

5.1 Traffic model..................................................................................................................................................... 35

5.2 Performance ...................................................................................................................................................... 35

5.3 Load constraints ............................................................................................................................................... 35

6 OPEN POINTS .......................................................................................................... 36

7 IMPACTS SUMMARY ............................................................................................... 37

8 GLOSSARY............................................................................................................... 39 8.1 Abbreviations .................................................................................................................................................... 39

8.2 Terminology ...................................................................................................................................................... 40

9 ANNEX A: 3GPP STANDARD REMINDER.............................................................. 43


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 7/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

INTERNAL REFERENCED DOCUMENTS Not applicable

REFERENCED DOCUMENTS Alcatel references [1] 3BK 11203 0091 DSZZA GPRS BSS load Model and Performance Objectives - RELEASE B8 [2] 3BK 11202 0362 DSZZA Frequency encoding algorithm - RELEASE B8 [3] 3BK 10204 0171 DTZZA TFD "Full support of E-GSM band" (Note: This TFD is not

implemented) [4] 3BK 10204 0519 DTZZA SFD : E-GSM support (Note: This SFD is implemented in B7.2) [5] 3BKA55CBR137244 RFD: Enhanced E-GSM band handling [6] 3BK 11204 0294 DSZZA Logical Configuration Management 3GPP references

3GPP TS Title [7] 45.005 Radio transmission and reception - (Release 4)

RELATED DOCUMENTS Alcatel documents None. 3GPP CRs None.

PREFACE This document is the input paper for the “Enhanced E-GSM band handling” feature inside TD. It will further on be used as reference for the development of that feature in each subsystem.


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 8/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

1 INTRODUCTION

1.1 Scope The present document aims to be the basis for decision of a proposed change to be made on the BSS system. It provides all necessary information related to functional description, gains and description of the system impacts and subsystem impacts.

1.2 Document Structure The section 2 of this document presents:

• the functional requirements, • an overall description of the features, • the compliance to marketing requirements and to the 3GPP standard, • which working assumptions have been made • and the dependencies, • as well as some decision criteria such as the risk, the gain, etc associated to the features addressed

by the present SFD. The section 3 identifies the system impacts: it gives the principles and presents the functional split of the feature between subsystems. The interactions within the BSS between the various modules, layers, etc are shown as well as the interaction with the other Network Elements. Impacts on telecom and O&M Step2 specifications are also given in this section. The validation strategy is presented as well as the impacts on GCD, methods and engineering rules. The section 4 recaps the impacts for each subsystem. The section 5 addresses the performance and system dimensioning concerns. The section 6 identifies and describes the open points that have been raised in the various reviews. The section 7 is a sum up of the system impacts. The section 8 contains the glossary of the present document. Annex A contains a description of the 3GPP standard features that meet the functional requirements expressed in section 2.


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 9/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

1.3 Definitions and pre-requisite 1.3.1 Frequency ranges The 3GPP standard has specified a set of 1024 possible ARFCNs (0, … ,1023) for GSM900, DCS1800 and DCS1900. Some of those values have already been allocated to certain frequencies (see ref.[2], ref.[7]) and the following table).

Frequency span (U)ARFCNs Uplink frequencies Downlink frequencies P-GSM band 1 .. 124 890.2 to 915.0 MHz 935.2 to 960.0 MHz G1 band 975 .. 1023, 0 880.2 to 890.0 MHz 925.2 to 935.0 MHz GSM850 band 128 … 251 824.2 MHz to 848.8 MHz 869.2 MHz to 893.8 MHz DCS1800 band 512 .. 885 1710.2 to 1784.8 MHz 1805.2 to 1879.8 MHz DCS1900 band 512 .. 810 1850.2 to 1909.8 MHz 1930.2 to 1989.8 MHz

Table 1: Frequency ranges

In this SFD, the term P-GSM band refers to the primary GSM 900 band, whereas the term E-GSM band refers to the extended GSM 900 band including the P-GSM band and the extended G1 band, see also section 8.2. The term GSM900 band refers to P-GSM band, or E-GSM band, or G1 band. The ARFCNs corresponding to the R-GSM, GSM 450 and GSM 480 bands are specified in the 3GPP standard but they are not mentioned in the Table 1 because these bands are not supported by the Alcatel BSS.

1.3.2 B7.2 implementation (support G1 TRXs in an E-GSM network) Alcatel BSS B7.2 release has implemented a solution in order to support G1 TRXs in an E-GSM network:

1. both P-GSM capable only MSs (see section 8.2) and E-GSM capable MSs (see section 8.2) are supported;

2. P-GSM TRXs and G1 TRXs are defined; 3. Specific radio resource allocation strategy is implemented: P-GSM capable only MSs are allocated

with resources on P-GSM TRXs and E-GSM capable MSs are preferably allocated with resources on G1 TRXs;

4. Signaling is conveyed on P-GSM TRXs only; 5. In an E-GSM single cell, GPRS service is only supported on the (hopping or/and non-hopping) P-

GSM TRXs; 6. In an E-GSM single cell, CS service is supported on the (hopping or/and non-hopping) P-GSM TRXs

and on the (hopping or/and non-hopping) G1 TRXs; 7. In a (multi-band or mono-band) concentric cell, the (hopping or/and non-hopping) G1 TRXs can be

configured in inner or/and outer zone. Nevertheless the (hopping or/and non-hopping) G1 TRXs support only CS service;

5.8. E-GSM band is supported by all types of Alcatel GSM900 TRE (G2/G3/G4 GSM900 TRE).


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 10/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

The B7.2 implementation covers partly the Business Case 1 (section 2.1.1) with the following limitations: 1. (E)GPRS service is not supported on G1 TRXs; 2. Signaling is not supported on G1 TRXs; 3.Only one GPRS MA; 4.3. The frequency hopping shall be applied only to a set of G1 frequencies or to a set of P-GSM

frequencies. FHS mixing frequencies in P-GSM band and G1 band is not supported. In a multiband concentric cell frequencies used belong to two frequency bands. Alcatel BSS B7.2 supports the multiband concentric cell configurations described in Table 2.

OUTER ZONE INNER ZONE FREQUENCY_RANGE value (see section 3.2.1.2)

DCS1800 TRX P-GSM TRX PGSM-DCS1800 DCS1800 TRX P-GSM TRX and G1 TRX EGSM-DCS1800 DCS1800 TRX G1 TRX EGSM-DCS1800 P-GSM TRX DCS1800 TRX PGSM-DCS1800 P-GSM TRX and G1 TRX DCS1800 TRX EGSM-DCS1800

Table 2: Multi-band concentric cell configuration supported by Alcatel BSS B7.2 The B7.2 implementation covers partly the Business Case 2 (section 2.1.1) with the following limitations:

1. Only one GPRS MA; 2.1. (E)GPRS service and signaling are not supported on G1 TRXs.

The B7.2 implementation does not cover the Business Case 3 (section 2.1.1).

1.3.3 B8 implementation B8 has introduced:

1. EGPRS service; 2. pseudo non-hopping TRX (Note). Note: GPRS traffic with CS3 and CS4 coding has much better performance on the non-hopping RTS

(Radio Time Slot). The problem is that, in B7.2, except for NH cells, the number of non-hopping RTS is limited (maximum 7 in BBH and in NH/RH). In B8, “pseudo non-hopping TRX” has been introduced, i.e., a TRX in which the frequency hopping law contains only one frequency. Both the OMC and the BSC manage a “pseudo non-hopping TRX” as if it is a “true” non-hopping TRX. As a consequence, in a BBH or NH/RH cell, it is possible to configure several “pseudo non-hopping TRX” to carry CS3/CS4.

The improvements with related to B7.2 implementation (1.3.2): 1. In an E-GSM single cell, GPRS service is supported on the pseudo non-hopping P-GSM TRXs; 2. In an E-GSM single cell, EGPRS service is supported on the hopping P-GSM TRXs or/and the non-

hopping P-GSM TRXs.

1.3.31.3.4 E-GSM capable MS recognition From messages sent by the MS, the BSS determines whether it is an E-GSM capable MS or not by decoding and storing: • bit 1 of octet 4 (i.e. "FC" bit) in the Mobile Station Classmark 2 IE and/or, • "Band 2" bit in Mobile Station Classmark 3 IE. The "Band 2" bit presence is optional in Classmark 3 IE. From messages sent by the MSC, the BSS can also find the band MS ability in: • bit 1 of octet 4 (i.e. "FC" bit) in the Classmark Information Type 2 IE and/or, • "Band 2" bit in Classmark Information Type 3 IE. The "Band 2" bit presence is optional in Classmark 3

IE. In what follows, the term “Classmark” refers to either the Mobile Classmark or the Classmark Information.


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 11/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

The general rules for E-GSM MS recognition • When the information is available, it is taken into account, • As long as information is not available, the MS is considered as not supporting the G1 band, • The BSS never triggers a Classmark Interrogation procedure to obtain the E-GSM ability of an MS.

1.3.41.3.5 System Information Limitation due to support of P-GSM capable only MS In order to support the P-GSM capable only MS (Phase 1 MS) in the network, Alcatel BSS has the following limitations for the system information management: • In a GSM900 cell, SYSTEM INFORMATION TYPE 5 is built based on phase 1 specifications for phase 1

MS (P-GSM capable only MS). The SYSTEM INFORMATION TYPE 5bis is never sent; • In cells where the BCCH frequency of the serving cell is in the GSM900 band, the BSC never sends the

SI2bis message to avoid possible inter-operability issues with GSM Phase 1 MS. In case all the neighbour DCS1800 ARFCNs cannot be encoded in the SI2ter message, the serving cell becomes “misaligned” with the OMC-R and the BSC sends an error report to the OMC-R requesting the operator to decrease the number of neighbour DCS1800 ARFCNs. In this “misaligned” situation, the BSC sends anyway the SI2 and SI2ter messages. In cells where the BCCH frequency of the serving cell is not in the GSM900 band, if after the encoding the SI2 and SI2ter messages, some neighbour ARFCNs cannot be encoded in SI2bis message, the serving cell becomes “misaligned” with the OMC-R and the BSC sends an error report to the OMC-R requesting the operator to decrease the number of neighbour ARFCNs. In this “misaligned” situation, the BSC does not send the SI2bis message, but sends anyway the SI2 and possibly the SI2ter messages.

1.3.51.3.6 B8 OMC checks related to the G1 band • the BCCH frequency of an external cell cannot belong to the G1 band; • the frequencies inside an FHS must belong to the same band; • the only channel combination allowed for G1 BBTs is TCH; • all timeslots of a non-hopping BBT must use the same ARFCN; • all ARFCNs referenced within both the active and inactive frequency usage of a BBT timeslots must

belong to the same band (i.e. P-GSM, GSM850, G1, DCS1800 or DCS1900); • G1 BBTs cannot support GPRS.


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 12/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

2 HIGH-LEVEL DESCRIPTION 2.1 Functional Requirements 2.1.1 Market view

• Business Case 1: P-GSM network (see section 8.2) extension with the frequencies in G1 band The operator has mainly the frequency in the P-GSM band. Some frequencies in G1 band are added to the cells for capacity extension purpose. In this Business Case, the old Phase 1 MS may still be in use in the network. In this SFD the Phase 1 MS is named as P-GSM capable only MS.

• Business Case 2: DCS 1800 network extension with the frequencies in E-GSM band There is also an interest from customers having already a deployed 1800 network and who are granted with the frequency in the E-GSM band (without the frequency in the P-GSM band). This is the case of Dutchtone. Similar case exists in Asia. In this Business Case, all MSs used are at least Phase 2 MSs, As a consequence, they can decode G1 frequencies.

• Business Case 3: full G1 network or network with mainly the frequencies in G1 band We face market interest to be able to operate a full G1 network without any frequency in the P-GSM band in countries tackling the migration AMPS towards 2G technology (e.g. in Pakistan). Some operators have mainly the frequencies in the G1 band and few frequencies in the P-GSM band e.g. South African operator Cell-C who is granted with 7 frequencies in the P-GSM band and 33 frequencies in the G1 band). In this Business Case, all MSs used are at least Phase 2 MSs, As a consequence, they can decode G1 frequencies.


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 13/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

2.1.2 Requirements for each business case

BUSINESS CASE MARKETING REQUIREMENTS

Business Case 1 (P-GSM network extension with the frequencies in G1 band)

This business case is partly covered by Alcatel BSS B7.2 implementation (see section 1.3.2 for detail). The following improvement is required: 1. Being able to support the (E)GPRS service on E-GSMG1 TRXs of an E-GSM cell; 2. In the (multi-band or mono-band) concentric cell, being able to support the

(E)GPRS service on the E-GSM G1TRXs located in the outer zone. or in inner zone. Note that (E)GPRS service and signaling can only be supported on E-GSM TRXs of outer zone.

The P-GSM capable only MS shall be supported (Note that this requirement is not new one, it has been implemented since B7.2).

Business Case 2 and Business Case 3

This business case is partly covered by Alcatel BSS B7.2 implementation (see section 1.3.2 for detail). The following improvements are required: 1. In the E-GSM cell (section 8.2), being able to support the (E)GPRS service on E-

GSM TRXs; 2. In the E-GSM cell (section 8.2), being able to support all types of signaling

channels (BCCH, CCCH, MPDCH, etc…) on any frequency belonging to the E-GSM band;

3. In the multi-band concentric cell, being able to support E-GSM TRXs in outer zone or in inner zone (Note). Note: If DCS1800 TRXs are in outer zone and E-GSM TRXs are in inner zone,

(E)GPRS service and signaling are not supported by E-GSM TRXs. If E-GSM TRXs are in outer zone and DCS1800 TRXs are in inner zone, (E)GPRS service and signaling are supported on E-GSM TRXs;

4. In the mono-band concentric cell, being able to support E-GSM TRXs in outer zone or in inner zone. Note that (E)GPRS service and signaling can only be supported on E-GSM TRXs of outer zone;

5. It is not required to support P-GSM capable only MS (This means no specific resource allocation strategy).

2.1.3 Optionality Optionality of “Enhanced E-GSM band handling" feature is managed at the customer level as B7.2: • if the feature is licensed, the operator is allowed to activate the feature by setting the

FREQUENCY_RANGE parameter to EGSM, or PGSM-DCS1800, or EGSM-DCS1800; • otherwise the operator is not allowed to activate or deactivate the feature by setting the

FREQUENCY_RANGE parameter to related value. That means: • if an operator has already licensed for the B7.2 solution (support G1 TRXs in an E-GSM network, see

section 1.3.2) it will get the “Enhanced E-GSM band handling" feature free of charge; • otherwise the operator shall pay the license to get the “Enhanced E-GSM band handling" feature.


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 14/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

2.2 Overall description of the proposed solutions The “Enhanced E-GSM band handling” feature brings the improvements compared to the B7.2 (1.3.2) and B8 (1.3.3) implementations:

• If P-GSM capable only MSs have to be supported in the network (“EGSM_RR_Alloc_Strategy” parameter is set to “0”), then: 1. In an EGSM single cell, (E)GPRS is supported on the (pseudo) non-hopping G1 TRXs. 2. In a (multi-band or mono-band) concentric cell, (E)GPRS is supported on the (pseudo) non-

hopping G1 TRXs located in the outer zone. • If all GSM900 MS in the network are assumed to be E-GSM capable (“EGSM_RR_Alloc_Strategy”

parameter is set to “1”), then: 1. The mixing of G1 and P-GSM frequencies inside a FHS is allowed. 2. Signalling TS (BCCH and SDCCH) on E-GSM TRX is allowed. 3. In an EGSM single cell, (E)GPRS is supported on: o the hopping E-GSM TRXs; o or/and the non-hopping E-GSM TRXs; o or/and the pseudo non-hopping E-GSM TRXs.

4. In a (multi-band or mono-band) concentric cell, (E)GPRS is supported on the (pseudo) non-hopping E-GSM TRXs located in the outer zone.

2.2.1Implementation approach Two implementation approaches are possible: One step approach (section 2.2.2) or two steps approach (section 2.2.3). One step approach is less costly than two steps approach. Nevertheless, two steps approach may be necessary if Alcatel is chosen to supply the operators having mainly or only G1 frequencies (Business Case 3, section 2.1.1) in the near future. Whatever the approach chosen, all the frequencies in the P-GSM band and G1 band are considered as a whole, and all the features possible in the P-GSM band shall be possible (as far as possible) in the E-GSM band. 2.2.2One step approach With one step approach the “Enhanced E-GSM band handling" feature is implemented in one step: �To support the (E)GPRS service on E-GSM TRXs of an E-GSM cell, the radio resource allocation strategy applied for P-GSM capable

only MSs is different than that applied for E-GSM capable MSs. �An E-GSM TRX are configured with: �frequencies in G1 band only; �or mixing frequencies in P-GSM band and G1 band; �FHS mixing frequencies in P-GSM band and G1 band is supported; �Support of (E)GPRS service, without any constraint, on E-GSM TRXs; �Support of all types of signaling channels (BCCH, CCCH, MPDCH, etc…), without any constraint, on E-GSM TRXs; �Both P-GSM capable only MS and E-GSM capable MS are supported; �(E)GPRS service and signaling are only supported on E-GSM TRXs in outer zone (section 2.1.2). 2.2.3Two steps approach With two steps approach the “Enhanced E-GSM band handling" feature is split in two sub-features (ref.[5]): �Sub-feature 1: Support of E-GSM networks; �Sub-feature 2: Support of P-GSM MS in E-GSM networks. Note that the Sub-feature 1 and Sub-feature 2 are equivalent from the radio-channel configuration point of view. Their difference consists only in the strategy for radio resource allocation in the E-GSM cell (section 3.1.1.1). The “Enhanced E-GSM band handling" feature is implemented in two steps: �Step 1: Implement firstly the sub-feature 1 (section 2.2.3.1) while keeping the B7 feature.

The step 1 of two steps approach implements partly the “Enhanced E-GSM band handling" feature and covers partly the Business Case 3 (P-GSM capable only MSs are not supported). �Step 2: then implement sub-feature 2 (section 2.2.3.2) on top of sub-feature 1. Step 2 of two steps approach extends the “Enhanced

E-GSM band handling" feature to the P-GSM capable only MS. 2.2.3.1Step 1 (sub-feature 1) With step 1 of two steps approach: �the E-GSM TRX is defined as follow: �frequencies in P-GSM band only; �or frequencies in G1 band only; �or mixing frequencies in P-GSM band and G1 band. �The (E)GPRS service is supported, without any constraint, on E-GSM TRXs; �All types of signaling channels (BCCH, CCCH, MPDCH, etc…) are supported, without any constraint, on E-GSM TRXs; �P-GSM capable only MS is not supported, because contrary to the B7.2 implementation (section 1.3.2), P-GSM capable only MS is not

ensured to be allocated with P-GSM resources(no specific resource allocation strategy for P-GSM capable only MS);


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 15/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

<In case of multiband concentric cell, see section 2.2.4.1; 2.2.3.2Step 2 (sub-feature 2) The main improvement related to step 1 is: < To support the (E)GPRS service on E-GSM TRXs of an E-GSM cell, the radio resource allocation strategy applied for P-GSM capable

only MSs is different than that applied for E-GSM capable MSs. From the radio resource allocation point of view, the meaning of E-GSM TRX is changed with related to the sub-feature 1 (see section 8.2). An E-GSM TRX is re-defined as follow: <frequencies in G1 band only; <or mixing frequencies in P-GSM band and G1 band.

2.2.4Multiband concentric cell 2.2.4.1Sub-feature 1 With the Sub-feature 1, Alcatel BSS supports the multiband concentric cell configurations described in Table 3.


EGSM_RR_Alloc_Strategy value (see section 3.2.1.1)

DCS1800 TRX E-GSM TRX (see section 8.2)

EGSM-DCS1800 Not applicable E-GSM TRX (see section 8.2)

DCS1800 TRX EGSM-DCS1800 0 or 1 (Note 1)

Table 3: Multiband concentric cell configuration supported by Alcatel BSS with the Sub-feature 1 Note 1: If the EGSM_RR_Alloc_Strategy parameter is set to 0 (see section 3.2.1.1), the radio resource allocation strategy

for the E-GSM cell will be the same as that of B7.2. If the EGSM_RR_Alloc_Strategy parameter is set to 1 (see section 3.2.1.1), there is no special radio resource allocation strategy for the E-GSM cell.

2.2.4.2Sub-feature 2 With the Sub-feature 2, Alcatel BSS supports the multiband concentric cell configurations described in Table 4.


EGSM_RR_Alloc_Strategy value (see section 3.2.1.1)

DCS1800 TRX P-GSM TRX PGSM-DCS1800 Not applicable DCS1800 TRX E-GSM TRX (see

section 8.2) EGSM-DCS1800 Not applicable

P-GSM TRX DCS1800 TRX PGSM-DCS1800 Not applicable E-GSM TRX (see section 8.2)

DCS1800 TRX EGSM-DCS1800 0 or 1 (Note 1)

Table 4: Multiband concentric cell configuration supported by Alcatel BSS with the Sub-feature 2 Note 1: If the EGSM_RR_Alloc_Strategy parameter is set to 0 (see section 3.2.1.1), the radio resource allocation strategy

for in the E-GSM cell will be the newly one introduced by the Sub-feature 2 (see section 2.2.3.1). If the EGSM_RR_Alloc_Strategy parameter is set to 1 (see section 3.2.1.1), there is no special radio resource allocation strategy for the E-GSM cell.

2.3Compliance to the Marketing Requirements

FEATURE ITEM COMPLIANCE COMMENTS Sub-feature

1 Sub-feature 2

Support of G1 TRX in P-GSM network

Not applicable

Yes <G1 TRX is a special case of E-GSM TRX; <Sub-feature 1 does not support P-GSM capable only MSs, as

consequence, in case of Two steps approach with only Sub-feature 1, the B7.2 solution is used for the Business Case 1 (section 2.2.3)

Support of E-GSM TRX Yes Yes

Support of the Full G1 network (or a network in which the majority of frequencies belong to the G1 band)

Yes Yes In case of Two steps approach with only Sub-feature 1, P-GSM capable only MSs are not supported.

Mixing E-GSM and GSM 1800 frequencies in the multiband cell configurations

Yes Yes

If DCS1800 TRXs are in outer zone and E-GSM TRXs are in inner zone, (E)GPRS service and signaling are not supported by E-GSM TRXs. If E-GSM TRXs are in outer zone and DCS1800 TRXs are in inner zone, E)GPRS service and signaling are supported on E-GSM TRXs;

Mixing P-GSM and G1 frequencies in the same FHS. Yes No


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 16/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

Support of P-GSM capable only MS No Yes Hopping E-GSM PS capable TRXs are not supported, see

section 2.5. Support of E-GSM capable MS Yes Yes

2.42.3 Compliance to 3GPP standard The feature is compliant to 3GPP standard.

2.52.4 Working Assumptions 1 Considering that an important effort is needed probable to develop the multiple mobile allocations per cell

feature and there is no real need for it, the “one MA at the most used for GPRS” constraint remains valid with the “Enhanced E-GSM band handling” feature.

2 (E)GPRS service and signaling are not supported on E-GSM TRXs in inner zone (section 2.1.2); 32 The new radio resource allocation strategy (section 3.1.1.1) is based on the hypotheses that all

GSM900 (E)GPRS MSs are assumed E-GSM capable and compliant to Phase 2 of 3GPP standard. 43 For the Business Case 1 (section 2.1.1), If P-GSM capable only MSs have to be supported in the network

(“EGSM_RR_Alloc_Strategy” parameter is set to “0”), then (E)GPRS service is not only supported on hopping G1 TRXs. The reason of this constraint is as follows: • the E-GSMTo support the P-GSM capable only MS (Phase 1 MS), the Cell Channel Description in

System Information Type 1 message shall not include the G1 frequencies since Phase 1 P-GSM capable only MS may not decode it.

• In the (Packet) System Information Type 13 the GPRS MA is encoded relatively to the Cell Channel Description in System Information Type 1. That means the frequencies belonging to the G1 band are excluded.

5 There is no specific requirement on the TRX/RSL mapping algorithm. As consequence, in case of mixed hardware configuration in a cell with both G3 and G4 TREs in the same cell, it is recommended to map to E-GSM TRX on G4 TRE and P-GSM TRX on G3 TRX. To have this mapping result, the TRX_PREF_MARK parameter should be set to: �zero for the E-GSM TRXs; �non-zero value for the P-GSM TRXs.

The consequence of above recommended rule for TRX_PREF_MARK parameter is that there is no (E)GPRS service on P-GSM TRX.

2.62.5 Dependencies • The “Enhanced E-GSM band handling” feature requires the following features:

None.

• The “Enhanced E-GSM band handling” feature is enhanced by the following features: None.

• The “Enhanced E-GSM band handling” feature is incompatible with the following features: None.

• The “Enhanced E-GSM band handling” feature will be enhanced by the following future evolutions:


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 17/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

None.

• The following features decrease the interest of “Enhanced E-GSM band handling” feature: None.

2.72.6 HW Coverage System:

GSM 900 Yes DCS 1800 / DCS1900 Yes GSM 850 No

Network element: The following tables indicate the impact of Enhanced E-GSM band handling feature on the Alcatel BSS network elements. Xsw if feature supported by the NE with software impact, Xhw if feature supported by the NE with hardware impact Xsw+hw if feature supported by the NE with software and hardware impact. X: The feature is supported on the NE without hardware or software impacts. -: The feature is not supported by the NE or the NE is not concerned by the feature

Impact BTS Generation: BTS G2 with DRFU (frozen at

B7.2 level) -

BTS Mk2 with DRFU (frozen at B7.2 level)

-

A9100 (Evolium standard) - A9110 (M4M) - A9110-E (M5M) - BSC Generation: BSC G2 Xsw MFS: MFS Xsw Transmission: Alcatel TSC - Transcoder: TRAU G2 with DT16 - TRAU G2 with MT120 TRAU G2.5 (with MT120) -


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 18/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

MSC: MSC - SGSN: SGSN - Data IWF: Data IWF - HLR: HLR - O&M: OMC-R Xsw POLO Xsw OEF Xsw LASER - MPM/NPA - RNO Xsw MSTS: MSTS Xsw

2.82.7 Decision criteria

2.8.12.7.1 Standardisation 3GPP standard allows to define full EGSM cells.

2.8.22.7.2 Competition Some Alcatel competitor seems have this feature in their portfolio.

2.8.32.7.3 Customer See section 2.1.

2.8.42.7.4 Gains 2.8.4.12.7.4.1 Telecom gains None


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 19/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

2.8.4.22.7.4.2 Operational gains The “Enhanced E-GSM band handling" feature allows the operator to support the (E)GPRS feature and signalling channels on frequencies in G1 band. 2.8.52.7.5 Risks None


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 20/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

3 SYSTEM IMPACTS

3.1 Telecom

3.1.1 Functional-level description

3.1.1.1 Strategy for radio resource allocation in the E-GSM cell 3.1.1.1.1Sub-feature 1 As the P-GSM capable only MS is not supported, there is no specific radio resource allocation strategy in the E-GSM cell. 3.1.1.1.2Sub-feature 2 3.1.1.1.2.13.1.1.1.1 P-GSM capable only MSs have to be supported in the network

(“EGSM_RR_Alloc_Strategy” parameter is set to “0”) Both P-GSM capable only MS and E-GSM capable MS are supported. It is proposed to use the following resource allocation strategy in the E-GSM cell (Figure 1): - PS requests are served on E-GSM PS capable G1 TRXs (see section 8.2), then on P-GSM PS capable P-

GSM TRXs; - CS requests for EGSM capable are served first on E-GSM non-PS capable G1 TRXs, then on P-GSM non-

PS capable P-GSM TRXs, then on P-GSM PS capable P-GSM TRXs, then on E-GSM PS capable G1 TRXs.

This strategy makes sense only if all GSM900 (E)GPRS capable MSs of the related network supports the G1 band (see section 2.4).

Figure 1: Strategy for radio resource allocation (Sub-feature 2/ P-GSM capable only MS is supported). The Alcatel BSS does not reject the request from an (E)GPRS MS which is not E-GSM capable. In that case the MS will not answer to the assignment messages sent on G1 frequencies or allocating G1 frequencies to the MS. Note that in Figure 1 all TRXs are assumed PS capable.

3.1.1.1.2.23.1.1.1.2 All GSM900 MSs in the network are assumed to be E-GSM capable (“EGSM_RR_Alloc_Strategy” parameter is set to “1”)

As the P-GSM capable only MS is not supported, there is no specific radio resource allocation strategy in the E-GSM cell.Same as section 1.1.1.1.1.

E-GSMG1 TRX

E-GSMG1 TRX

P-GSM TRX

P-GSM TRX

PS allocation (from higher to lower priority)

CS allocation (from higher to lower priority)


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 21/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

3.1.2 Telecom Specification impacts 3.1.2.1 Resource allocation and management 3.1.2.1.1Sub-feature 1 The radio resource allocation and management in the E-GSM cell is the same as that of P-GSM cell.

3.1.2.1.2Sub-feature 2 3.1.2.1.2.13.1.2.1.1 P-GSM capable only MSs have to be supported in the network

(“EGSM_RR_Alloc_Strategy” parameter is set to “0”) As it is possible to mix P-GSM and G1 frequencies in the same FHS, the TRX Ranking function shall be modified accordingly: BSC has to check the frequencies in the FHS. If at least one frequency is found belonging to the G1 band, the related TRX is considered as E-GSM TRX (Note). Note: this distinction is only meaningful in cells where FREQUENCY_RANGE = EGSM or EGSM-DCS1800 and

EGSM_ALLOC_STRATEGY = 0. In the E-GSM cell, when allocating a TCH to serve CS requests, the BSC shall select the TCH in the following order (based on the TRX ranking provided to the MFS by the BSC): • For E-GSM capable MS

1. Firstly select a radio timeslot which is E-GSM capable but NOT PS capable; 2. Secondly select a radio timeslot which is neither E-GSM capable nor PS capable; 3. Thirdly select a radio timeslot which is NOT E-GSM capable but PS capable; 4. Finally select a radio timeslot which is E-GSM capable and PS capable.

• For P-GSM capable only MS 1. Firstly select a radio timeslot which is neither E-GSM capable nor PS capable. 2. Finally select a radio timeslot which is NOT E-GSM capable but PS capable.

In case of multi-band concentric cell the allocation strategy presented above applies for the outer zone only. For allocation in the inner zone, there is no change compared to B7.2.


The radio resource allocation and management in the E-GSM cell is the same as that of P-GSM cell.Same as section 1.1.1.1.1.

3.1.2.2 GPRS Radio Interface - RRM sub-layer (PRH) When allocationg PDCHs, the MFS shall select the PDCHs based on the order of TRX list provided by the BSC:

1. Firstly select a radio timeslot which is E-GSM capable and PS capable; 2. Finally select a radio timeslot which is NOT E-GSM capable but PS capable.

3.1.2.2.1Sub-feature 1 It is assumed that all the (E)GPRS MS is E-GSM capable (section 2.5). The Cell Channel Description in System Information Type 1 message can include the frequencies belonging to the E-GSM band. MFS shall be able to encode the ARFCN of the E-GSM band in the following messages: �Packet UL/DL Assignment �Packet Timeslot Re-configure �Packet System Information Type 2 �Packet System Information Type 8 �(Packet) System Information Type 13


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 22/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.


(“EGSM_RR_Alloc_Strategy” parameter is set to “0”) • The Cell Allocation in the Packet System Information Type 2 message is the same as the Cell Channel

Description in System Information Type 1 message (see section 3.1.2.3.1). As consequence the frequencies belonging to the E-GSMG1 band are excluded.

• As the (E)GPRS service is not only supported on the non-hopping E-GSMG1 TRXs of an E-GSM cell (section 2.4) the ARFCN of (pseudo) non-hopping E-GSMG1 TRX is provided directly in the following messages: ♦ Packet UL/DL Assignment ♦ Packet Timeslot Re-configure


The Cell Channel Description in System Information Type 1 message can include the frequencies belonging to the E-GSM band. MFS shall be able to encode the ARFCN of the E-GSM band in the following messages:

• Packet UL/DL Assignment • Packet Timeslot Re-configure • Packet System Information Type 2 • Packet System Information Type 8 • (Packet) System Information Type 13

Same as section 1.1.1.1.1.

3.1.2.3 System Information Management 3.1.2.3.1Sub-feature 1 �The Cell Channel Description in System Information Type 1 message can include the frequencies belonging to the E-GSM band. �In the E-GSM cell, if all the E-GSM frequencies cannot be encoded in the System Information Type 2 message, it is allowed to use the

System Information Type 2bis to encode the remaining frequencies (see section 1.3.4). �In the E-GSM cell, if all the E-GSM frequencies cannot be encoded in the System Information Type 5 message, it is allowed to use the

System Information Type 5bis messages to encode the remaining frequencies (see section 1.3.4). �The ARFCN of the E-GSM neighbour cells can be encoded with the Variable Bitmap format or Range 128/256 in SI2 message

depending on the frequency span (Note). The SI2ter/SI2bis messages will be used to encode the ARFCN of the DCS1800/DCS1900 neighbour cells. The same requirements apply for the handling of the SI5/5bis/5ter messages. Note: If the frequency span is less than 112, the Variable Bitmap is used to encode the ARFCN of the E-GSM neighbour cells;

otherwise the Range 128 or Range 256 shall be used depending on the number of neighbour frequencies (see ref.[2]). It is possible that all ARFCNs of E-GSM neighbour cells can not be encoded in the SYSTEM INFORMATION TYPE 2 if the frequency span is higher than 128 and the number of neighbour frequencies in the E-GSM band is higher than 22 (see ref.[2]). In that case, the SYSTEM INFORMATION TYPE 2bis is used to encode the remaining E-GSM ARFCN instead of the remaining DCS1800 or DCS1900 ARFCN.


(“EGSM_RR_Alloc_Strategy” parameter is set to “0”)

• the Cell Channel Description in System Information Type 1 message shall not include the G1 frequencies since P-GSM capable only MS may not decode it.; �SI13_CHANGE_MARK and GPRS Mobile Allocation IE are not included in the System Information Type 13 message (see section

2.5).


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 23/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.


• The Cell Channel Description in System Information Type 1 message can include the frequencies belonging to the E-GSM band.

• In the E-GSM cell, if all the E-GSM frequencies cannot be encoded in the System Information Type 2 message, it is allowed to use the System Information Type 2bis to encode the remaining frequencies (see section 1.3.5).

• In the E-GSM cell, if all the E-GSM frequencies cannot be encoded in the System Information Type 5 message, it is allowed to use the System Information Type 5bis messages to encode the remaining frequencies (see section 1.3.5).

• The ARFCN of the E-GSM neighbour cells can be encoded with the Variable Bitmap format or Range 128/256 in SI2 message depending on the frequency span (Note). The SI2ter/SI2bis messages will be used to encode the ARFCN of the DCS1800/DCS1900 neighbour cells. The same requirements apply for the handling of the SI5/5bis/5ter messages. Note: If the frequency span is less than 112, the Variable Bitmap is used to encode the ARFCN of the E-

GSM neighbour cells; otherwise the Range 128 or Range 256 shall be used depending on the number of neighbour frequencies (see ref.[2]). It is possible that all ARFCNs of E-GSM neighbour cells can not be encoded in the SYSTEM INFORMATION TYPE 2 if the frequency span is higher than 128 and the number of neighbour frequencies in the E-GSM band is higher than 22 (see ref.[2]). In that case, the SYSTEM INFORMATION TYPE 2bis is used to encode the remaining E-GSM ARFCN instead of the remaining DCS1800 or DCS1900 ARFCN.

Same as section 1.1.1.1.1.

3.1.2.4 Frequency Encoding Algorithm In the Alcatel BSS, the Cell Allocation regroups all the frequencies (hopping or non-hopping frequencies) involved in a non-concentric cell or in a mono-band concentric cell or in the outer zone of a multi-band concentric cell with the following E-GSM band exceptions:

• If P-GSM capable only MSs have to be supported in the network then the BSC does not include the frequencies belonging to G1 band in the Cell Allocation. Indeed the P-GSM capable only MSs support only the bitmap_0 encoding format.

• If all GSM900 MS in the network are assumed to be E-GSM capable, for the cell that is configured as NH/RH, the BSC does not include the BCCH frequency in the Cell Allocation.

Sub-feature 1 The BSC and the MFS shall be able to encode the E-GSM ARFCN in the messages sent to the MS: �For the E-GSM cell, the G1 frequencies shall NOT be excluded from the Cell Allocation. �As the frequency span may exceed 112 (up to 174), a new check is then required to be sure that all frequencies can be encoded in the

Cell Channel Description. 3.1.2.4.2Sub-feature 2 3.1.2.4.2.1P-GSM capable only MSs have to be supported in the network No impact. 3.1.2.4.2.2All GSM900 MSs in the network are assumed to be E-GSM capable Same as section 3.1.2.4.1. 3.1.2.5 Classmark handling No impact.

3.1.2.6 Power Control and Radio Link Supervision No impact.

3.1.2.7 Handover Preparation


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 24/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

• It is allowed for the operator to select the BCCH ARFCN belonging to the G1 band for BCCH_FREQUENCY parameter;

• Both FREQUENCY_RANGE and EGSM_RR_Alloc_Strategy shall be considered during the handover preparation;

• Define the E-GSM TRXs concept instead of G1 TRXs (especially for allocation strategy in the inner zone).

3.1.3 Interfaces

3.1.3.1 Radio interface (05.02, 04.06, 04.60, 04.18, 24.008, etc) Any message involving an exchange of ARFCN is impacted.

3.1.3.2 Abis interface (08.58) None.

3.1.3.3 A interface (08.08) None.

3.1.3.4 Gb interface (08.18) None.

3.1.3.5 BSCGP interface 3.1.3.5.1Sub-feature 1 No impact. 3.1.3.5.2Sub-feature 2 3.1.3.5.2.1P-GSM capable only MSs have to be supported in the network For the E-GSM cell, the GPRS MA shall not be provided by the MFS to the BSC (see working assumption 4 in section 2.5). 3.1.3.5.2.2All GSM900 MSs in the network are assumed to be E-GSM capable No impact.

3.1.3.6 GCH interface None.

3.1.4 Simulations None.


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 25/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

3.2 Operation and maintenance 3.2.1 OMC-R parameters 3.2.1.1 New parameters 3.2.1.1.1Sub-feature 1

Parameter name

Definition Sub-system

Instance Category1 / OMC-R access2

Type3 Range / default value

EGSM_RR_Alloc_Strategy

This parameter defines the radio resource allocation strategy used in E-GSM cells.

BSC BSS CDE / Displayed

Number Min: 0 (radio resource allocation strategy for case where not all GSM900 MS in the network are assumed to be E-GSM capable, i.e. P-GSM capable only MSs have to be supported in the network);

Max: 1 (radio resource allocation strategy for case where all GSM900 MS in the network are assumed to be E-GSM capable)

Def: 1 Table 5: New OMC-R parameters (Sub-feature 1)

3.2.1.1.2Sub-feature 2 Parameter name




EGSM_RR_Alloc_Strategy

This parameter defines the radio resource allocation strategy used in E-GSM cells.

BSC BSS CDE / Displayed

Number Min: 0 (radio resource allocation strategy for case where not all GSM900 MS in the network are assumed to be E-GSM capable, i.e. P-GSM capable only MSs have to be supported in the network);

Max: 1 (radio resource allocation strategy for case where all GSM900 MS in the network are assumed to be E-GSM capable)

Def: 0

Table 5: New OMC-R parameters (Sub-feature 2)

1 The valid options are: Site (CAE), Network (CDE), System (CST), Not Used (NU) 2 The valid options are: changeable, set by create, displayed, OMC local display, Virtual – changeable, Virtual – displayed. 3 The valid options are: abstract, flag, list of numbers, number, reference, threshold, timer. 4 The valid options are: Site (CAE), Network (CDE), System (CST), Not Used (NU) 5 The valid options are: changeable, set by create, displayed, OMC local display, Virtual – changeable, Virtual – displayed. 6 The valid options are: abstract, flag, list of numbers, number, reference, threshold, timer.


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 26/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

3.2.1.2 Modified parameters 3.2.1.2.1Sub-feature 1 No impact. 3.2.1.2.2Sub-feature 2

Parameter name




PLMN_FREQUENCY_BANDS (BSC)

Frequency bands used in the whole PLMN.

BSC BSS) CAE/Changeable (Note)

Number

PLMN_FREQUENCY_BANDS (MFS)

Frequency bands used in the whole PLMN.

MFS BSS CAE/Changeable (Note)

Number

Table 6: Modified OMC-R parameters Note: The check of FREQUENCY_RANGE parameter against the PLMN_FREQUENCY_BANDS parameter

(which is linked to the multi-band BSC concept) will be performed by the OMC-R in the following two cases • at the cell creation; • when FREQUENCY_RANGE parameter is modified. In order to minimise the cost in the OMC-R, when PLMN_FREQUENCY_BANDS parameter is modified; it is allowed that OMC-R does not check the FREQUENCY_RANGE parameter against the new value of PLMN_FREQUENCY_BANDS parameter.

Additional O&M information (valid except otherwise indicated for the whole section 3.2.1): • The parameter PLMN_FREQUENCY_BANDS(MFS) is considered as MFS B9 critical parameter. • The parameters EGSM_RR_Alloc_Strategy and PLMN_FREQUENCY_BANDS (BSC/MFS) can be

modified from both PRC and SC. • The parameters EGSM_RR_Alloc_Strategy and PLMN_FREQUENCY_BANDS (BSC/MFS) are

managed by the ACIE interface for both import and export directions. • None of these parameters need to be integrated within the “default filters” provided by the OMC. • For all the parameters the default value is fixed (i.e. not depending on other parameters). Additionally, the OMC should be modified so that the following conditions are accomplished:

• the BCCH frequency of an external cell is allowed to belong to the G1 band; • inside an FHS it is allowed to mix frequencies belong to the P-GSM band and the G1 band; other

mixings are not allowed; • the G1 BBTs are allowed to have channel combinations other than TCH. However, the restriction

concerning the signalling channels in the inner zone of a multi-band cell is preserved. 7 The valid options are: Site (CAE), Network (CDE), System (CST), Not Used (NU) 8 The valid options are: changeable, set by create, displayed, OMC local display, Virtual – changeable, Virtual – displayed. 9 The valid options are: abstract, flag, list of numbers, number, reference, threshold, timer.


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 27/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

• G1 BBTs can support GPRS, unless they belong to the inner zone. The above conditions should be applied in both sub-feature1 and sub-feature2.

3.2.2 Modelisation of OMC-R parameters 3.2.2.1Sub-feature 1 3.2.2.1.1OMC GDMO impacts The GDMO will be aligned with the BTP changes implied by the addition of the new parameter EGSM_RR_Alloc_Strategy. The parameter EGSM_RR_Alloc_Strategy will belong to the rnlAlcatelBSC object (RNL)/alcatelBssFunction object (EML) if the object release is B9. 3.2.2.1.2ACIE Interface impacts The parameter EGSM_RR_Alloc_Strategy is managed through the ACIE interface (export and import). 3.2.2.1.3OMC-BSC interface impacts The proposed modification is the following: the parameter EGSM_RR_Alloc_Strategy has to be added within the BSC-Parameters-Type group, as a new “egsmrrallocstrategy EGSM-RR-Alloc-Strategy OPTIONAL” field. Its type should be INTEGER. 3.2.2.1.4OMC-MFS interface impacts No impact. 3.2.2.2Sub-feature 2 The parameter PLMN_FREQUENCY_BANDS becomes OMC accessible (see section 1.1.1.1.1). From the OMC impacts point of view of it can be considered as a newly added parameter. 3.2.2.2.13.2.2.1 OMC GDMO impacts The GDMO will be aligned with the BTP changes implied by the addition of the new parameter. The parameter PLMN_FREQUENCY_BANDS will belong to the rnlAlcatelBSC object (RNL)/alcatelBssFunction object (EML). 3.2.2.2.23.2.2.2 ACIE Interface impacts The parameter PLMN_FREQUENCY_BANDS is managed through the ACIE interface (export and import). 3.2.2.2.33.2.2.3 OMC-BSC interface impacts The proposed modification is the following: for the parameter PLMN-Freq-Bands, the ‘OMC usage’ section of its description must be changed to “modify –C”. 3.2.2.2.43.2.2.4 OMC-MFS interface impacts The parameter PLMN_FREQUENCY_BANDS is managed for the aGprsBssFunction B9 object. The values of the parameters will be sent by the OMC to the MFS only if the MFS is B9 release, irrespective of the RNL objects release (B8 or B9). According to the rules used to handle the critical parameters, if the corresponding RNL object release is B8, the OMC will send the migration values. If the RNL objects release is B9, the OMC will send the actual values as they are set by the user.

3.2.3 Other parameters None.

3.2.4 PM counters 3.2.4.1 Counters in the BSC 3.2.4.1.1 New PM counters None.


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 28/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

3.2.4.1.2 Modified PM counters None.

3.2.4.2 Counters in the MFS 3.2.4.2.1 New PM counters None.

3.2.4.2.2 Modified PM counters None.

3.2.5 PM indicators

3.2.5.1 New Computed indicators None. 3.2.5.2 Impact on existing indicators None.

3.2.6 Migration EGSM_RR_Alloc_Strategy parameter shall be set to the Default value during the migration (see section 3.2.1.1). 3.2.6.1 OMC Migration 3.2.6.1.1Sub-feature 1 No impact. 3.2.6.1.2Sub-feature 2 In OMC the parameter PLMN_FREQUENCY_BANDS will be initialized with its default value for the B8 BSC instances.

3.2.6.2 BSC Migration The migration is performed through the OEF application which builds the B9 DLS. 3.2.6.2.1Sub-feature 1 After the BSC migration, the OMC retrieves the actual value of the parameter EGSM_RR_Alloc_Strategy, by the logical audit. 3.2.6.2.2Sub-feature 2 After the BSC migration, the OMC retrieves the actual value of both parameters EGSM_RR_Alloc_Strategy and PLMN_FREQUENCY_BANDS, by the logical audit. It should be noted that: • since the parameter PLMN_FREQUENCY_BANDS is BSC/MFS common, after a logical audit the OMC

should set the BSC attribute mfsAlignmentStatus on ‘misaligned’ if the value of PLMN_FREQUENCY_BANDS changes due to the uploading.

• The default value of the parameter EGSM_RR_Alloc_Strategy is changed from 1 to 0.


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 29/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

3.2.6.3 MFS migration 3.2.6.3.1Sub-feature 1 No impact. 3.2.6.3.2Sub-feature 2 The migration is performed as follows: • First the MFS is migrated. In this phase the parameter PLMN_FREQUENCY_BANDS is initialized with 0

by the MFS. • A resynchronization is performed through the OMC and consequently, the migration value of the

parameter is sent to the MFS. • Then, the BSC is migrated and the user can modify the values of PLMN_FREQUENCY_BANDS, if

needed. Their values will be downloaded to the MFS through a resynchronization operation. 3.2.7 Java scripts 3.2.7.1Sub-feature 1 A new script, CSPSPrefMarkConfigB9.js should be written in order to have the circuit/packet preference mark configuration for the B9 cells. This script should be similar to the one used for the B8 cells (CSPSPrefMarkConfig.js), but the conditions stated in section 3.2.1.2.2 should be taken into account. 3.2.7.2Sub-feature 2 No impact.

3.2.8 Fault Management This section describes the impacts of the feature(s) on the fault management (to be filled in by O&M people).

3.2.9 O&M Specification impacts

3.2.9.1 LCM specification To be completed by OMC-R expert.

3.2.9.2 HCM specification No impact.

3.2.9.3 OMC/BSC MIB To be completed by OMC-R expert.

3.2.9.4 OMC/MFS MIB To be completed by OMC-R expert.


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 30/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

3.2.9.5 OMC-R export interface for PM data To be completed by OMC-R expert.

3.3 Validation To be filled in by VAL people, when technical content of the SFD is stable.

3.3.1 Testing tools This section gives the list of tools needed to validate the feature. For each tool, it is mentioned: - if the tool is a new one - if the tool is modified compared to the previous release - if the tool is used without modification compared to the previous release Note that "tools" should include all what is external to the BSS product: so it includes mobiles, SGSN, etc.

3.3.2 Test strategy

3.3.2.1 System tests coverage This section gives a first estimate of the split between the subsystem tests and the system tests. The following points are addressed: - what is and is not to be explicitly tested at system level ? - can the feature be validated completely at sub-system level ? - what is the added value of system tests compared to sub-system tests ?

3.3.2.2 Overall strategy for system tests This section gives the guidelines that will be followed when defining the test plan. It gives, for system tests, the categories of tests that are needed to validate the features. - functional tests: tests performed with MS simulators and CORE network simulators, the purpose is to validate basic scenarios, error cases, etc. Note that the real added value of functional tests versus end to end tests needs to be addressed. - end to end tests: tests performed with real mobile and real CORE network. Purpose is to validate the feature from an end user point of view. - performance tests: this is a specific case of end to end tests with a specific purpose: measurement of the improvement brought by the feature. Note that the objective in terms of performance improvement has to be described in the technical part of the SFD. - Telecom and O&M load tests - migration tests: it should be mentioned if specific migration tests are needed because of this feature - industrialisation tests: it should be addressed in co-operation with SED team (see section on impact on methods)


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 31/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

3.4 Methods 3.4.1 New PFD (Field Procedure Designs) document needed None

3.4.2 Impact on existing FPD documents None . 3.5 GCDs 3.5.1 New GCD (Generic Customer Documentation) needed None

3.5.2 Impact on existing GCD 3.5.2.1 O&M PARAMETERS Dictionary 1 parameters to be added and 2 parameters to be modified (Note). Note: ‘O&M PARAMETERS Dictionary’ is a document extracted from Access Databases.

3.5.2.2 BSS System Description Update ‘Overview’, ‘Extended GSM’ and ‘Resource Allocation’ chapters to take into account the Enhanced E-GSM band handling feature.

3.5.2.3 A1353-RA OLH Update the ‘Logical Configuration Management Windows’ chapter to introduce the new thumbnail named “Resource Allocation”.

3.5.2.4 BSS Configuration Handbook Update the ‘Set/Update Circuit/Packet PreferenceMark Configuration Using Script’ chapter (introduction) to take into account the script for B9

3.6 Engineering rules 3.6.1 New documents needed None.

3.6.2 Impact on existing B8 Engineering documents 3.6.2.1 BSS Configuration Rules Add a warning in ‘BTS Configuration’ chapter s: in case of mixed hardware configuration in a cell with both G3 and G4 TREs in the same cell, under some conditions, the BSC does not guarantee that the PS TRXs having the highest priority for PS allocations are mapped on the G4 TREs (see section 2.4).


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 32/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

Paragraphs ‘Rules’ in ‘SDCCH Dynamic Allocation’ chapter and ‘GPRS General Dimensioning Rules’ in ‘GPRS in the BSS’ chapter have to be updated for the support of EGPRS service on E-GSM TRXs.


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 33/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

4 SUBSYSTEM IMPACTS

4.1 BTS No impact.

4.2 BSC See section 3.1.2.

4.3 Transcoder No impact.

4.4 MFS See section 3.1.2.2.

4.5 OMC-R 4.5.1 HMI impacts 4.5.1.1Sub-feature 1 No impacts. 4.5.1.2Sub-feature 2 A new thumbnail named “Resource Allocation” should be added within the “Edit BSC” screen. Inside this screen a box named “PLMN Frequency bands used” will be defined to include the parameter PLMN_FREQUENCY_BANDS. The HMI name of the parameter is proposed to be PLMN_FREQUENCY_BANDS.

4.5.2 OMC modelization See section 3.2.2.

4.5.3 Optional feature The present feature is based upon the optional feature E-GSM and no additional modifications are required to manage this issue.


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 34/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

4.5.4 Overview of the impact upon OMC specs 4.5.4.1Sub-feature 1 The following parts of the DFS LCM are impacted: �MFs-Create/Modify Baseband Transceiver: the RNL error cases should be updated according to the checks specified in section

3.2.1.2.2. �MFs-Create/Modify FHS: the RNL error cases should be updated according to the checks specified in section 3.2.1.2.2. �The chapter 5.1. should be updated according to the checks specified in section 3.2.1.2.2 of SFD. �Chapter 5.2: the release-features mapping table. 4.5.4.2Sub-feature 2 The following parts of the DFS LCM are impacted: • MF-Set BSS Telecom Parameters: the parameter PLMN_FREQUENCY_BANDS must be added to the

input list for both BSC/MFS side, sorrounded by the tags “If the feature Enhanced E-GSM band handling is supported by the aim BSC” –“Endif”.

• MF-Create cell: the RNL error cases should be updated according the checks concerning the parameter PLMN_FREQUENCY_BANDS, specified in section 1.1.1.1.1.

• MF-Logical Audit – BSC Level: the “BSC/MFS common attributes” table should be updated with the PLMN_FREQUENCY_BANDS parameter.

• The chapter 5.1. should be updated according to the checks specified in section 1.1.1.1.1.

4.6 LASER No impact.

4.7 MPM/NPA/RNO 4.7.1 MPM/NPA No impact. 4.7.2 RNO To be defined.

4.8 Polo See section 3.2.1.

4.9 OEF No impact.


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 35/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

5 PERFORMANCE & SYSTEM DIMENSIONING

5.1 Traffic model None.

5.2 Performance None.

5.3 Load constraints None.


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 36/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

6 OPEN POINTS

Open Point 1: Strategy for radio resource allocation (see section 3.1.1.2.2): Status: Closed.

Open Point 2: The instance of Flag_EGSM_RRA parameter should be BSC or Cell (see section 3.2.1.1) ? Status: Closed.

Open Point 3: Should we change the Sub-system and Category/OMC-R Access of PLMN_FREQUENCY_BANDS (BSC) and PLMN_FREQUENCY_BANDS (MFS) parameters (see section 3.2.1.2): • Category/OMC-R Access: From CDE/None (DLS) to CAE/Chageable; • Instance: From BSC/MFS to BSS. Status: Closed.

Open Point 4: Should the EGSM_RR_Alloc_Strategy be “CDE/None(DLS)”? The functionality of this parameter indicates whether all GSM900 MS in the network are assumed to be E-GSM capable or not. Modification of this parameter by the operator via OMC-R will impact the construction of Cell Channel Description and resource allocation strategy. Status: Closed.

Open Point 5: Should the PLMN_FREQUENCY_BANDS (BSC) / PLMN_FREQUENCY_BANDS (MFSC) be “CDE/None(DLS)”? Status: Closed.

Open Point 6: If the parameter EGSM_RR_Alloc_Strategy has a zero value, should the following check be performed by OMC for the E-GSM cell:

“It is not possible to create more than 18 DCS1800 adjacencies per E-GSM serving cell (FREQUENCY_RANGE has the value "2" (EGSM)), see section 1.3.5.”

Status: Closed.


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 37/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

7 IMPACTS SUMMARY

Equipments:

BTS BSC MFS TC OMC-R LASER MPM/NPA RNO OEF Polo

no yes yes no yes no no yes no yes

Interfaces: Telecom

Radio Abis A Ater BTS-TC MFS-BTS MFS-BSC Gb

yes no no no no no no no

O&M

Abis-O&M BSC-O&M TC-O&M MFS-O&M Q3

no yes no yes no

List of Impacted Step2 specification (Telecom): BSS Telecom Parameters catalogue Classmark handling Frequency Encoding Algorithm GPRS Radio Interface - RRM sub-layer (PRH) Handover Preparation LAYER 3 MESSAGE DICTIONARY - AIR INTERFACE MFS-BSC interface BSCGP layer Resource Allocation and Management System Information Management

List of Impacted Step2 specification (O&M): BSS O&M parameters GSM indicators /alerters Hardware Configuration Management OMC-R export interface for PM data Logical Configuration Management


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 38/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

Network defense OMC/BSC Interface MIB Specification


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 39/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

8 GLOSSARY

8.1 Abbreviations AMPS American Mobile Personal System ARFCN Absolute Radio Frequency Channel Number BBH Base Band Hopping BCCH Broadcast Control CHannel BSC Base Station Controller BSS Base Station Subsystem BTS Base Transceiver Station CS Circuit Service DCS1800 Digital Cellular System at 1800MHz DCS1900 Digital Cellular System at 1900MHz E-GSM Extended GSM GSM Global System for Mobile communications HW HardWare IE Information Element MA Mobile Allocation MFD Marketing Feature Description MFS Multi-BSS Fast packet Server NH Non Hopping NH/RH BCCH Non-Hopping / Radio Hopping P-GSM Primary GSM OMC-R Operations and Maintenance Center – Radio PBCCH Packet Broadcast Control Channel (P)BCCH Packet Broadcast Control Channel or/and Broadcast Control Channel PS Packet Service [(E)GPRS service] RAM Resource Allocation and Management RFD Request For Development RH Radio Hopping SDCCH Stand alone Dedicated Control CHannel SFD System Feature Description TD Technical Department of Evolium TRE TRansceiver Equipment TRX TRansceiver unit


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 40/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

8.2 Terminology Base Band Hopping

The BCCH frequency is always a hopping frequency, so the BCCH frequency is included in the Cell Allocation (ref.[6]).

BCCH band Refers to frequency band in which the (P)BCCH channel (for signalling), the SDCCH and TCH channels for CS traffic, and PDCH channels for PS traffic are configured. In mono-band or multi-band concentric cells, the BCCH band is always in outer zone.

Cell Allocation Refers to a set of all the frequencies defined in one cell. The Cell Allocation is denoted CA

E-GSM band The term E-GSM band refers to the Extended GSM 900 frequency bands including the P-GSM band and the G1 band.

E-GSM capable MS The term E-GSM capable MS refers to the mobile station that supports both P-GSM band and G1 band.

E-GSM cell The term E-GSM cell refers to the cell in which all the frequencies used belong to the E-GSM band.

E-GSM network The term E-GSM network refers to the network in which the frequencies used belong to the E-GSM band.

E-GSM TRX With the "Enhanced E-GSM band handling" feature, the term E-GSM TRX is used only in case where all GSM900 MS in the network are assumed to be E-GSM capable (“EGSM_RR_Alloc_Strategy” parameter is set to “1”). It refers to the TRX configured with:

• frequencies in P-GSM band only; • or frequencies in G1 band only; • or mixing frequencies in P-GSM band and G1 band.

<From the Logical configuration point of view, the term E-GSM TRX refers to the TRX configured with frequencies (up to 64 frequencies) belonging to the E-GSM band;

<From the radio resource allocation point of view, the meaning of E-GSM TRX is different depending on the implementation approach and the sub-feature (section 2.2).

Full G1 network The term Full G1 network refers to the network in which all the frequencies used belong to the G1 band.

G1 band The term G1 band refers to the following GSM 900 frequency band: uplink frequencies from 880.2 to 890.0 MHz and downlink frequencies from 925.2 to 935.0 MHz, see section 1.3.


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 41/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

G1 TRX With the "Enhanced E-GSM band handling" feature, the The term G1 TRX is used only in case where P-GSM capable only MSs have to be supported in the network (“EGSM_RR_Alloc_Strategy” parameter is set to “0”), it refers to the TRX configured with frequencies (up to 64 frequencies) belong to the G1 band.

GPRS Mobile Allocation The term GPRS Mobile Allocation refers to the set of RF channels and a hopping sequence number (HSN). The frequencies used in the GPRS Mobile Allocation are defined relatively to the CA.

Hopping TRX The term Hopping TRX refers to a TRX that may change its frequency on every timeslot from burst to burst (ref.[6]).

Mobile Allocation The term Mobile Allocation refers to the set of the frequencies which are used in a frequency hopping sequence. The frequencies defined in a Mobile Allocation can be defined relatively to the CA, or directly in a radio channel allocation message.

Multi-band BSC The term Multi-band BSC refers to the BSC that can support up to two frequency bands Note that the mono-band BSC is considered as a special case of Multi-band BSC). Alcatel BSS supports the Multi-band BSC with one of following configurations: 1. DCS1800 band and GSM900 band (DCS1800/P-GSM, or DCS1800/G1, or DCS1800/E-GSM); 2. DCS1900 band and GSM900 band (DCS1900/P-GSM, or DCS1900/G1, or DCS1900/E-GSM); 3. DCS1800 band and GSM850 band; 4. DCS1900 band and GSM850 band.

Mono-band Concentric Cell The term Mono-band Concentric Cell refers to the concentric cell configured with frequencies belonging to the same frequency band (ref.[6]).

Multi-band Concentric Cell The term Multi-band Concentric Cell refers to the concentric cell configured with frequencies belonging to two frequency bands.

Non-BCCH band The term Non-BCCH band refers to frequency band in which the (P)BCCH channel is NOT configured. Non-BCCH band carries only the TCH channels for CS traffic. Note that the Non-BCCH band notion is only applicable to multi-band concentric cells and is always used in inner zone by the Alcatel BSS.

Non-hopping TRX The term Non-hopping TRX refers to a TRX that uses the same frequency on every burst on every timeslot (ref.[6]).

P-GSM capable only MS The term P-GSM capable only MS refers to the mobile station that supports only the P-GSM band.


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 42/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

P-GSM band The term P-GSM band refers to the Primary GSM 900 frequency band (uplink frequencies: 890.2 to 915.0 MHz; downlink frequencies: 935.2 to 960.0 MHz), see section 1.3.

P-GSM cell The term P-GSM cell refers to the cell in which all the frequencies used belong to the P-GSM band.

P-GSM network The term P-GSM network refers to the network in which all the frequencies used belong to the P-GSM band.

P-GSM TRX The term P-GSM TRX refers to the TRX configured with frequencies (up to 64 frequencies) belonging to the P-GSM band.

Pseudo-MA The term Pseudo-MA refers to a Mobile Allocation in which the frequency hopping law contains only one frequency. A pseudo-MA actually defines a set of non-hopping channels.

Pseudo non-hopping TRX The term Pseudo non-hopping TRX refers to a TRX in which all 8 timeslots are configured with the same pseudo-MA (i.e. the same ARFCN) and with the same HSN. A pseudo non-hopping TRX is seen as a non-hopping TRX by the BSC.

Radio Hopping (Non Base Band Hopping The BCCH frequency is NOT a hopping frequency, so the BCCH frequency is NOT included in the Cell Allocation (ref.[6]).


0612_02.doc 12/02/2007

3BK 10204 0612 DTZZA 43/43

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

.

9 ANNEX A: 3GPP STANDARD REMINDER None.

END OF DOCUMENT

3bk 10204 0612 dtzza - e-gsm - support of gprs and signaling in g1 band

Documents

gruau pm ed

written authorization

document structure

taskforcewg2 history

alcatel gsm bss subsystem

table of contents

systla document category

omc impact